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 s
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
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
** 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 noti
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
D
** 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
** 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
** 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
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 = permi
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
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
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
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 timeo
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 duri
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 Ubunt
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-de
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 so
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:
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
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
** 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
@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 Bu
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 shar
#ＩＮＴＲＯ
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].
#ＬＯＮＧ
T
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
Desk
** 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
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 la
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 o
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.l
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
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 Ubunt
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 : S
32 matches
Mail list logo
