[Bug 1798166] Re: “Mouse battery low” notification can't be disabled
Clarification: this bug ist not about wrong battery Level measurements (Nobody reported that), it's about users being unable to disable notifications. The notification is shown even when in DND mode. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1798166 Title: “Mouse battery low” notification can't be disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1798166/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1798166] Re: “Mouse battery low” notification can't be disabled
If I understood correctly this bug was invalidated as a Linux bug only, not as a GNOME issue. As a GNOME (or more specifically as "gnome- settings-daemon package") it is not only valid, but its priority is set to high. It makes sense to me. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1798166 Title: “Mouse battery low” notification can't be disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1798166/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1896332] Re: SRU 3.36.6
Now, I'm waiting for the SRU team release this fix to "-updates". :) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1896332 Title: SRU 3.36.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896332/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1877209] Re: Update to 3.36.2 and SRU it
** Changed in: mutter (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1877209 Title: Update to 3.36.2 and SRU it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1877209/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)
The updated package will be released to "-updates" after the bug fixed have been verified and the package has been in "-proposed" for a minimum of 7 days. In this case, the status is: "Fix Committed" (not "Fix Released"). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1892440 Title: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)
** Changed in: mutter (Ubuntu Focal) Status: Fix Released => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1892440 Title: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1894596] Re: Night Light stays on
** Changed in: mutter (Ubuntu Groovy) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: mutter (Ubuntu Focal) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1894596 Title: Night Light stays on To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1894596/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1865226] Re: gdm-smartcard pam config needs to be updated for Ubuntu and installed
** Changed in: gdm3 (Ubuntu Groovy) Importance: Low => Medium -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1865226 Title: gdm-smartcard pam config needs to be updated for Ubuntu and installed To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1865226/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1865226] Re: gdm-smartcard pam config needs to be updated for Ubuntu and installed
It has been brought to my attention by a UA customer that they are suffering from which seems a similar situation: " Our only currently working SmartCard access from Linux, over SSSD, to AD, is on RHEL7. I was able to get SSH access on Ubuntu 20.04LTS, after adding "ad_gpo_access_control = permissive" in sssd.conf. Logging in locally fails (prompting for password, rather than PIN). It is also still prompting for the Password twice on all local login attempts. RHEL7 -> Ubuntu 20.04LTS (SSH) - Success Ubuntu 20.04LTS -> RHEL7 (SSH) - Success Ubuntu Desktop login (GDM or CLI) - Fail Ubuntu Desktop login via local username/pw - Success, but with 2 pw prompts. " -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1865226 Title: gdm-smartcard pam config needs to be updated for Ubuntu and installed To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1865226/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1875528] Re: Extra frozen / stuck mouse cursor after auto screen lock / sleep
I have the same problem. Using Wayland with an AMD R580, dual monitor and fractional scaling set to 200%. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1875528 Title: Extra frozen / stuck mouse cursor after auto screen lock / sleep To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1875528/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1897281] Re: evince suicides in 20.04 but not in 18.04
Addendum: Using Ubuntu Focal's unrar-free, I can unzip from this CPR file 144 GIF files in a blink, sizing from 425 KB to 2 MB. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1897281 Title: evince suicides in 20.04 but not in 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1897281/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
Yeah, sorry, I don't think that's a reproducer for the bug. You killed dbus, gdm and everything else, and they obligingly died on you. :) My feeling is that this bug is about a deadlock that somehow happens when dbus and/or systemd are reloaded, possibly at the same time. It looks like dbus stops responding to systemd, and so when it calls GetNameOwner() to be able to watch type=dbus units, it gets no reply and then decides to kill all type=dbus units, which is a lot of things. If that's right, it's most likely to be a dbus bug that it can get into this state. But I'm personally at a bit of a loss as to how to approach it without being able to reproduce. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1871538/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
Well, more correctly -1 means to all processes you can send to, and if you're root, well it's everyone. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1871538/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
kill(-1, SIGINT) kills all processes on the system with SIGINT, so this is hardly surprising. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1871538/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1883174] Re: Some desktop icons disappear
Ubuntu 20.04, with the same issue, sometimes a few disappear, sometimes all icons disappear. The installation was done through fresh install. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1883174 Title: Some desktop icons disappear To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1883174/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892276] Re: pdf images stretched on desktop 20.04 after previous bug fix release
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1892276 Title: pdf images stretched on desktop 20.04 after previous bug fix release To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1892276/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
By chance (while developing some netplan code), I seem to have found a reproducer for this bug... I don't know what is going on, but calling the 'Trigger' method from the attached 'dbus.c' file will kill the GDM session in a reproducible way. The invalid `kill(-1, SIGINT);` of line 21, seems to somehow crash the whole DBus/GDM and other services. So there must be some problem inside DBus's error handling, which is somehow triggered during the updates. * WARNING: calling the Trigger method via busctl will kill your GDM session * * compile: gcc -o out dbus.c `pkg-config --cflags --libs libsystemd glib-2.0` * execute: sudo ./out * trigger: sudo busctl call io.netplan.Netplan /io/netplan/Netplan io.netplan.Netplan Trigger ** Attachment added: "dbus.c" https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1871538/+attachment/5414222/+files/dbus.c -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1871538/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1808702] Re: Bubblewrap integration broke user thumbnailers
The issue is fixed in G now ** Changed in: gnome-desktop3 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/1808702 Title: Bubblewrap integration broke user thumbnailers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1808702/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1897281] [NEW] evince suicides in 20.04 but not in 18.04
Public bug reported: Description:Ubuntu 20.04.1 LTS Release:20.04 Evince does a suicide trip after unsuccessfully trying to open a CBR file. After a while it is killed. Here is my terminal output: $ evince TheCartoons.cbr Killed $ And between the line "$ evince TheCartoons.cbr" and the final "Killed", are passing many minutes. Please note that I started my report in https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1785060 not knowing exactly what "expired" there means. I did "apport-collect 1785060" there, too. Please note also that my error message (see above) is quite different from seb128 in bug 1785060. In fact, there is no error message just the statement "Killed". What gets me is that in 18.04 it is working so smooth and fast and that in 20.04 it is such a mess! P.S. I do not know whether this helps, but with Debian 11 Xfce (Buster sid, testing), evince loads and opens this CBR file correctly, albeit slowly, but okular (installed in Buster sid) yields a similar error message like that of seb128 with evince in bug 1785060: "Could not open file TheCartoons.cbr. The version of unrar on your system is not suitable for opening comicbooks" Inverted world ;-) ** Affects: evince (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1897281 Title: evince suicides in 20.04 but not in 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1897281/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1785060] Re: Evince cannot open cbr-files based on rar v5
This is what I get using the terminal: $ evince TheCartoons.cbr Killed $ And between the command and the final "Killed" are many, many minutes. During that time, evince shows an empty page, just "loading, loading, loading, ...". Typical suicide ;-) It gets me that what works so well in 18.04 is such a mess in 20.04 :-( -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1785060 Title: Evince cannot open cbr-files based on rar v5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1785060/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)
** Changed in: mutter (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1892440 Title: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1890716] Re: misidentifies .html file as Perl script when it contains JavaScript "use strict"
@Kai Kasurinen >probably fixed on shared-mime-info 2.0: >https://gitlab.freedesktop.org/xdg/shared-mime-info/-/commit/18bb7cfc6c43d710ecf60339b5dd9bd19c297cdf Yeah, well. It's if they only used the same database. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1890716 Title: misidentifies .html file as Perl script when it contains JavaScript "use strict" To manage notifications about this bug go to: https://bugs.launchpad.net/shared-mime-info/+bug/1890716/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1890716] Re: misidentifies .html file as Perl script when it contains JavaScript "use strict"
If you wrap string in the proper tags you will get the same result, but
with different offset (28 chars):
tee "index.html" <
`printf "x"%.0s {1..228}`
use strict
eol # -> text/html
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to shared-mime-info in Ubuntu.
https://bugs.launchpad.net/bugs/1890716
Title:
misidentifies .html file as Perl script when it contains JavaScript
"use strict"
To manage notifications about this bug go to:
https://bugs.launchpad.net/shared-mime-info/+bug/1890716/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1890716] Re: misidentifies .html file as Perl script when it contains JavaScript "use strict"
#ＩＮＴＲＯ After digging up for a while I've found where the issue comes from for both `.html` and `.py` (bug #1857824) files. #ＳＨＯＲＴ The culprit responsible for misidentification resides in `.xml` database which specifies how to match mime-type against input data. It can be found here [2]. #ＬＯＮＧ The `kmimetypefinder.cpp` pulls up [0] `QMimeDatabase db` apis by `db.mimeTypeForFile(...)` which in turns bootstrup `QMimeDatabasePrivate ...` XML database from .xml file.[1] If we look carefully at the content of the `"text/x-perl"` entry we would see the following: ``` ... ... ``` Did you notice the offset attribute `"0:256"`? Now if we run the following two cases we will see that files whose content contains keywords `use strict` in the range of 1..256 will be identified as `text/x-perl` script and as `text/html` if the `use trict` is located outside of such range otherwise, checkout: 💲 tee "index.html"
[Bug 1896332] Re: SRU 3.36.6
Sure, but you need to enable Proposed repositories, see https://wiki.ubuntu.com/Testing/EnableProposed Remember to disable them once updated, as otherwise you may get earlier updates that have still to be fully tested. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1896332 Title: SRU 3.36.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896332/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1845703] Re: Deleting starred files leaves behind starred file named ""
** Changed in: nautilus (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1845703 Title: Deleting starred files leaves behind starred file named "" To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1845703/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1896804] Re: CD/DVD drive detected as read only, command line and GUI programs
Hi, well, at least we got over the strange error code. > libburn : SORRY : Timeout exceed (3 ms). Retry canceled. > libburn : SORRY : Command: READ DISC INFORMATION #63,[2 04 00] : 51 00 > 00 00 00 00 00 00 22 00 : dxfer_len= 34 The command READ DISC INFORMATION was retried 63 times. The last failure was because of a timeout of 30 seconds. The failed command does not cause much effort in the drive. It is just an inquiry about the overall state of the loaded medium. Normally it is done within less than a millisecond. The drive seems to have announced that there is a medium loaded. Else libburn would not have had interest in the medium state. As it seems now, this drive is quite unusable. See below for a deeper inspection of what is going on between it and libburn. > Drive type : vendor 'HL-DT-ST' product 'DVDRAM GH20NS10' revision 'EL00' Googling "GH20NS10" "EL00" shows that this drive is around since 2007. How old is yours ? When was last it was re-cabled or moved to another box ? Do you have an opportunity to test it with MS-Windows without touching the hardware ? It would be quite astonishing if it worked right now with the same medium loaded as with your above xorriso run. -- Let's break out the big gear and add command -scsi_log "on" to the xorriso run. Because the output on standard error channel will be very verbous, we catch it in a file in /tmp while still showing it on terminal: ./xorriso/xorriso -scsi_log on -outdev /dev/sr0 -toc 2>&1 \ | tee -i /tmp/xorriso.log (I write this as two lines with a "\" at the end of the first, because the bug tracker breaks up oversized lines. You may write it in one line without that "\": ./xorriso/xorriso -scsi_log on -outdev /dev/sr0 -toc 2>&1 | tee -i /tmp/xorriso.log ) This will log the SCSI commands and their replies as they go forth and back between libburn and the drive. Add the emerging file /tmp/xorriso.log as attachment to your next comment. If the attachment is rejected for any reason, send the file to scdbac...@gmx.net as mail body or as attachment. It will be interesting to see all error replies and the timing of command execution. -- Have a nice day :) Thomas -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to brasero in Ubuntu. https://bugs.launchpad.net/bugs/1896804 Title: CD/DVD drive detected as read only, command line and GUI programs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/1896804/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1896804] Re: CD/DVD drive detected as read only, command line and GUI programs
Correction: The single command READ DISC INFORMATION probably did not timeout, but was repeated with intermediate waiting until 30 seconds had elapsed. So the drive probably reacts swiftly but always says that it is not yet ready. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to brasero in Ubuntu. https://bugs.launchpad.net/bugs/1896804 Title: CD/DVD drive detected as read only, command line and GUI programs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/1896804/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)
I tested the ThinkPad (Nvidia Graphics), after upgrading libmutter-6-0, gir1.2-mutter-6, mutter and mutter-common in proposed, this issue is gone. Thanks! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1892440 Title: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1897211] Re: Ubuntu not loading/detecting discrete GPU after update
Thank you for taking the time to report this issue and helping to make Ubuntu better. Examining the information you have given us, this does not appear to be a bug report so we are closing it and converting it to a question in the support tracker. We understand the difficulties you are facing, but it is better to raise problems you are having in the support tracker at https://answers.launchpad.net/ubuntu if you are uncertain if they are bugs. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org. For help on reporting bugs, see https://help.ubuntu.com/community/ReportingBugs. ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-control-center (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1897211 Title: Ubuntu not loading/detecting discrete GPU after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1897211/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1896332] Re: SRU 3.36.6
I am on focal, with the 'developer options' pre-release option ticked (and repos re-reloaded). I'm not seeing any proposed updates. Is it available to the public or not? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1896332 Title: SRU 3.36.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896332/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1896804] Re: CD/DVD drive detected as read only, command line and GUI programs
Hi Thomas. did the alteration to spc.c and ran make. ububnu is still seeing the drive as read only. see the output below. chris@chris-A320M-S2H-V2:~/xorriso/xorriso-1.5.3$ ./xorriso/xorriso -outdev /dev/sr0 -toc GNU xorriso 1.5.3 : RockRidge filesystem manipulator, libburnia project. libburn : SORRY : Timeout exceed (3 ms). Retry canceled. libburn : SORRY : Command: READ DISC INFORMATION #63,[2 04 00] : 51 00 00 00 00 00 00 00 22 00 : dxfer_len= 34 xorriso : NOTE : Disc status unsuitable for writing Drive current: -outdev '/dev/sr0' Media current: is not recognizable Media status : is not recognizable xorriso : NOTE : Tolerated problem event of severity 'SORRY' Drive current: -outdev '/dev/sr0' Drive access : exclusive:unrestricted Drive type : vendor 'HL-DT-ST' product 'DVDRAM GH20NS10' revision 'EL00' Drive id : 'K1386NK4932 ' Media current: is not recognizable Media status : is not recognizable Media blocks : 0 readable , 0 writable , 0 overall TOC layout : Idx , sbsector , Size , Volume Id xorriso : SORRY : Cannot obtain Table Of Content xorriso : NOTE : Tolerated problem event of severity 'SORRY' xorriso : NOTE : -return_with SORRY 32 triggered by problem severity SORRY Regards Chris On Thu, 2020-09-24 at 16:09 +, Thomas Schmitt wrote: > Hi, > > > libburn : SORRY : Asynchronous SCSI error on waiting after START > > UNIT > > (+ LOAD) [6 28 81] Drive event. Unknown ASCQ with drive event ASC > > 28. > > Grr. A higher level intervened. > > In line 198 of file > > ~/xorriso/xorriso-1.5.3/libburn/spc.c > > there is > > if (key == 0x6 && asc == 0x28 && ascq == > 0x00) > > which should be shortened to > > if (key == 0x6 && asc == 0x28) > > Do you feel apt to make this code change and then run > > make > > again ? > (Else i would upload a new tarball.) > > This time i simulated the drive reply 0x6, 0x28, 0x81 in the waiting > loop > from where the message stems. Without " && ascq == 0x00" in line 198 > it > works for me. So now it is up to your drive to tell me where else > this > unexpected error code creates mistrust, or what other interesting > replies > it has to offer. > > Have a nice day :) > > Thomas > -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to brasero in Ubuntu. https://bugs.launchpad.net/bugs/1896804 Title: CD/DVD drive detected as read only, command line and GUI programs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/1896804/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
