With 18.04 LTS, if you login with flashback, the volume slider in the
sound settings as well as the volume slider that drops down when
clicking the speaker indicator behave backwards even when natural
scrolling is off.
With flashback, turning natural scrolling on actually makes both volume
[Expired for nautilus (Ubuntu) because there has been no activity for 60
days.]
** Changed in: nautilus (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
[Expired for nautilus (Ubuntu) because there has been no activity for 60
days.]
** Changed in: nautilus (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
[Expired for nautilus (Ubuntu) because there has been no activity for 60
days.]
** Changed in: nautilus (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
[Expired for gnome-control-center (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: gnome-control-center (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
[Expired for nautilus (Ubuntu) because there has been no activity for 60
days.]
** Changed in: nautilus (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
Why is it still "Low Importance"?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1600622
Title:
Screen doesn't lock or go to sleep when certain Chrome tabs are open
To
Still an issue on 19.10 and 20.04
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1702071
Title:
Search spins forever, returns no results.
To manage notifications about
Dear Balint,
Thankyou for your reply concerning my login bug. Fortunately the problem
has disappeared with installation of 19.10 which I am finding to be the
best Ubuntu release since the return to gnome desktop. Many thanks to all
working on desktop Ubuntu for making it so successful.
Cheers,
https://gitlab.gnome.org/GNOME/mutter/issues/1036
let's hope they fix it
** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #1036
https://gitlab.gnome.org/GNOME/mutter/issues/1036
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
Thanks @vanvugt, I'll do so :)
--
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/1804568
Title:
click position is flipped to cursor position when in tent mode
To manage notifications
Sorry, how can I get the ID of the newly-created bugs?
--
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/1862229
Title:
gnome session crash on boot with kernel 5.3.0-29-generic
You say that the library and kernel module in Ubuntu are older than the
ones from DisplayLink.com. Can you explain why the current versions of
the module and library aren't being shipped in Focal?
I'm afraid I can't test any further in 19.10 since I've already upgraded
both of my laptops to
Bug still present in Kubuntu 19.10.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/378783
Title:
xdg-open *.desktop opens text editor
To manage notifications about this bug go
I did it for both _usr_bin_gnome-shell.1000.crash and _usr_lib_gnome-
session_gnome-session-binary.1000.crash.
--
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/1862229
Title:
** Tags added: focal
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-calendar in Ubuntu.
https://bugs.launchpad.net/bugs/1828581
Title:
/usr/bin/gnome-
Yeah, nouveau is not an option for me unfortunately, there are just too
many problems with it.
And the bug is still present for me as well.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
On 2020-02-07 16:41, Alkis Georgopoulos wrote:
> I checked with 20.04 and it appears that recent Ubuntu live CDs
> don't have boot=casper anymore; they do still have
> initrd=/casper/initrd;
I also saw that /proc/cmdline contains BOOT_IMAGE=/casper/..., so the
approach would probably have worked
Please edit the description to get rid of the profanity. Such language
will NOT get this looked at faster, but rather, will get your launchpad
account removed. If you're going to act that way, figure out a way to
fix it yourself.
--
You received this bug notification because you are a member of
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gimp (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gimp in Ubuntu.
Public bug reported:
See the full report here:
https://gitlab.gnome.org/GNOME/gimp/issues/4586
Hopefully it's already fixed upstream.
For fuck's sake this version is more than 5 years old already!
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gimp 2.8.16-1ubuntu1.1
Hi, in /var/crash I have the following files:
-rw-r- 1 giacof whoopsie 188300182 feb 1 15:34
_usr_bin_gnome-shell.1000.crash
-rw-r--r-- 1 giacof whoopsie 0 feb 1 15:38
_usr_bin_gnome-shell.1000.upload
-rw--- 1 whoopsie whoopsie37 feb 5 22:37
Do you still observe the issue on 19.10 or later?
I'm reassigning to a package more related to the potential bug.
** Package changed: shadow (Ubuntu) => gnome-shell (Ubuntu)
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you
You have been subscribed to a public bug:
Bug started immediately after upgrading to Ubuntu 19.04. Have tried all
the suggested work-arounds I can find on the web but none of them has
any effect on the problem.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: login 1:4.5-1.1ubuntu2
Re: DisplayLink monitors not detected under Xorg, I wonder if that would
have to do with https://gitlab.freedesktop.org/xorg/xserver/issues/909 ?
But that's off-topic in this report too.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
Then the main issue: freezes.
Do I understand correctly, that so far the freezes have only happened
when you have had two monitors attached to the DisplayLink dock? Never
with just one monitor?
Which DisplayLink dock do you have?
You said changing the display configuration is a sure way to
Public bug reported:
When I try to open the Gnome Control Center application, it dies
silently. When I try to open it on the terminal, this error is displayed
on the terminal:
$ gnome-control-center --verbose
can't load /usr/lib/x86_64-linux-gnu/spa/support/libspa-support.so:
What comes to the EVDI dkms version, the official DisplayLink driver
5.2.14 package contains EVDI 1.6.2. The release notes just write it out
as v1.5.0-r1-76 (a1e1135), but that sha1 refers to 1.6.2 and the code
between the official package and the 1.6.2 tag for the kernel module is
identical. So I
Xorg cursor artifacts all over everywhere: "When I use the evdi module
and library shipped with Ubuntu in 20.04, then DisplayLink works in
Xorg, but it's very glitchy, with cursor artifacts showing up constantly
all over the place on all screens, both DisplayLink and non-
DisplayLink."
I've seen
Hi Jonathan,
you seem to be having several different issues here, so I'll try to
address them individually.
First the slow updates, you wrote: "screen updates to the DisplayLink
monitor are Extremely Slow. Like I am typing in a terminal window and it
sometimes takes a second or two between when
Still happening on latest Ubuntu Focal daily image when in install-only
mode. Not sure what could be wrong, the translatable string seems to be
correct.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to the bug report.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gimp (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gimp in Ubuntu.
By the way, I don't know what happened but I don't have the bug any
more. Has there been any update recently?
--
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/1855757
Title:
[nvidia]
Yeah I would usually recommend a supported Nvidia driver instead of
Nouveau. Just trying to avoid this bug...
--
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/1855757
Title:
[nvidia]
@Daniel: the Nouveau driver may work, but, in my case, it's way slower
than the NVidia official driver, making it simply unusable for any 3D
usage.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
*If* the kernel and mesa both support your GPU adequately then you don't
need to be tied to Nvidia driver releases. Just use the built-in nouveau
driver (which also doesn't have the bug AFAIK). But unfortunately that's
a big "if" as nouveau is known to be buggy occasionally, for some GPUs.
**
I have this problem on two machines, both using the 340 Nvidia driver
and running Ubuntu 19.10.
On one machine, with a Geforce 330M, only the lockscreen gets corrupted.
On the other, running Geforce 8600M, both the lockscreen and wallpaper
get corrupted.
This didn't used to happen on 18.04, I
** Changed in: rhythmbox (Debian)
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to rhythmbox in Ubuntu.
https://bugs.launchpad.net/bugs/1313914
Title:
Rhythmbox zeitgeist plugin doesn't
Public bug reported:
Desktop wallpaper is slightly blurry in Gnome 3.34.
Upstream fix pending:
https://gitlab.gnome.org/GNOME/mutter/merge_requests/1003
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.34.3-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
39 matches
Mail list logo
