It has been fixed in Fedora and Arch, where is the fix for Ubuntu?
--
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/1847551
Title:
Mutter 3.34.1 broke Night Light, screen color profil
Is there a testing package including the fix that we could test please?
--
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/1847551
Title:
Mutter 3.34.1 broke Night Light, screen color p
In gnome-shell itself, in overview mode and either as favorite or not.
--
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/1831384
Title:
.desktop files not working in Ubuntu 19.04
Log in journalctl:
gnome-shell[610]: g_environ_setenv: assertion 'value != NULL' failed
--
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/1831384
Title:
.desktop files not workin
** Package changed: ubuntu => gnome-shell (Ubuntu)
--
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/1831384
Title:
.desktop files not working in Ubuntu 19.04 Gnome
To manage not
upstream bug report confirms that this is a bug in Ubuntu:
https://gitlab.gnome.org/GNOME/gnome-terminal/issues/132
** Bug watch added: gitlab.gnome.org/GNOME/gnome-terminal/issues #132
https://gitlab.gnome.org/GNOME/gnome-terminal/issues/132
--
You received this bug notification because you
Same issue here, reported there:
https://bugzilla.redhat.com/show_bug.cgi?id=1278944
It is not consistent between disks, even when there are from the same vendor or
the same model.
Of course, the controller may be totally different.
Note that it all cases, they spin down correctly under Mac OS o
I described there : https://bugzilla.redhat.com/show_bug.cgi?id=1278944
or there : https://bugs.freedesktop.org/show_bug.cgi?id=71802
I don't think it is related only to USB 3 or Nautilus. It is a larger
udisk or kernel issue with some micro-controllers...
** Bug watch added: Red Hat Bugzilla #12
Public bug reported:
Evolution randomly crashes, even when it is left open with no user
interaction.
Here is the backtrace :
$ evolution
*** glibc detected *** evolution: free(): invalid pointer: 0x7fd0cc1031c0
***
=== Backtrace: =
/lib/x86_64-linux-gnu/libc.so.6(+0x78a96)[0x7fd
Simply, it has always been a show-stopper for me.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/13983
Title:
Evolution virtual trash / "real" trash on IMAP server
To manage notifica
Same problem here.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/819156
Title:
regression: totem do not disables screensaver
To manage notifications about this bug go to:
https://b
As far as I am concerned, it has been solved using the IMAP+ protocol, as soon
as Evolution started to support it.
It can be reproduced anytime using the basic IMAP protocol though, so I am not
sure if it is an expected behavior or a workaround.
Anyway, I definitely adopted Thunderbird which doe
I am having this problem on one of my maverick machines.
--
Fails repeatably with "DBus error org.gtk.Private.RemoteVolumeMonitor.NotFound:
The given volume was not found"
https://bugs.launchpad.net/bugs/458334
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, w
And what's weired is that pinging is allowed on my server, so I don't
know what Evolution is actually trying to do...
--
Ping imap locks up evolution for ~30 sec
https://bugs.launchpad.net/bugs/637568
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is sub
It also affects me, on Maverick.
--
Ping imap locks up evolution for ~30 sec
https://bugs.launchpad.net/bugs/637568
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution in ubuntu.
--
desktop-bugs mailing list
desktop-bugs@lists.ubu
This bug had disappeared for me until Lucid, but it came back with 10.10.
Was it patched or fixed accordingly ?
--
Error with pinging an imap server, when I work offline
https://bugs.launchpad.net/bugs/38154
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
This bug had disappeared for me until Lucid, but it came back with 10.10.
Was it patched or fixed accordingly ?
--
Error with pinging an imap server, when I work offline
https://bugs.launchpad.net/bugs/38154
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
Nothing in syslog, but there is a line in .xsession-error :
** (totem:7460): WARNING **: Detected that GNOME screensaver has left
the bus closing
--
gnome-screensaver fails marking the session as idle
https://bugs.launchpad.net/bugs/200960
You received this bug notification because you are a mem
I don't have any /var/crash, and nothing from the terminal.
It just starts the daemon and in general it will work well the first few
times.
--
gnome-screensaver fails marking the session as idle
https://bugs.launchpad.net/bugs/200960
You received this bug notification because you are a member of
I have seen this problem with :
- a NVidia NVS 140 M card, using the Nvidia driver (169.09)
- an Intel 945 GM card, and the intel driver
--
gnome-screensaver fails marking the session as idle
https://bugs.launchpad.net/bugs/200960
You received this bug notification because you are a member of U
David, I have sometimes experienced what you mention (in a train), but I
think this is an issue we can live with.
In that case the problem is not g-p-m but the power source. I think that
there is no easy way to deal with it, and we should not have something
too complex for such some extreme and ra
Keenan, that's exactly what I thought.
I don't have an ambient light sensor, so I have no experience using it.
However, I tend to believe that the sensor should deal with the
temporary setting only...
--
Backlight no longer under my control on battery
https://bugs.launchpad.net/bugs/131885
You r
I guess what I think is joining what Kyle says, but to be sure I clarify
what I meant :
There are 2 different settings :
- the defaults values that g-p-m applies when the power state changes
- the current value in each power state, which is temporary for the current
state
The scenario :
g-p-m
Thank you for this patch, quite an improvement.
However I disagree with the point of view of Keenan, I think the big
issue is that the gnome brightness setting is still not synchronized
with the hardware setting (set with the keyboard).
This is pretty confusing for the user to set brightness to
Public bug reported:
Binary package hint: gnome-screensaver
I have seen this bug for months.
Randomly but very often, Gnome-Screensaver seems to freeze and stop
marking the session as idle.
As a result :
- the screensaver never appears;
- and the most annoying, gnome-power-manager never suspe
Confirmed with my brand new Thinkpad T61.
This is a rather important issue, and it does not seem to evoluate at all !
--
Backlight no longer under my control on battery
https://bugs.launchpad.net/bugs/131885
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
26 matches
Mail list logo
