** Changed in: ubuntukylin
Status: New => Confirmed
** Also affects: fcitx (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to fcitx in Ubuntu.
*** This bug is a duplicate of bug 1798790 ***
https://bugs.launchpad.net/bugs/1798790
I apologize if I caused any confusion, to me I'm experiencing the same
problem as the other people commenting here after getting this update.
System won't boot, so I'm not sure how it's different, I Have
@ruediger.kupper
It is still definitely present on 18.04. All apps open in the secondary
monitor of all workspaces collapse onto the secondary monitor when the super
key is pushed for the activity overview (but go back to their original
workspaces when you push it again.)
--
You received
In your video it looks like you are typing "ubuntu" and gnome-shell is
too slow to display much of the typing. So this is a performance
problem, and unsurprising if it's during an operation that requires
gnome-shell to perform disk IO like searching.
** Tags added: performance
--
You received
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mutter (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gdm3 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
If I had to guess then I would guess the most likely cause is the
changes I made in the latest update:
https://launchpad.net/ubuntu/+source/mutter/3.28.4-0ubuntu18.04.1
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in
** Changed in: gnome-shell
Status: Unknown => New
--
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/1832317
Title:
A quick type in the Gnome 3 search sticks
To manage
Public bug reported:
Details in my video: https://photos.app.goo.gl/h1eDdgkdJLDTDKH67
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-shell 3.32.1-1ubuntu1~19.04.1
ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
Uname: Linux 5.0.0-16-generic x86_64
ApportVersion:
** Tags added: fixed-in-3.33.3 fixed-upstream
--
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/1814125
Title:
[nvidia] gnome-shell eats 100% cpu when seconds display is on and
Yes, it is a bug. Thanks for reporting it.
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1246
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1246
** Also affects: gnome-shell via
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1246
Importance: Unknown
Anyone doesn't notice this bug, that I had opened. Please check it. It's
critical error: https://bugs.launchpad.net/bugs/1831374
вт, 11 июн. 2019 г., 13:10 Bug Watch Updater
<1832...@bugs.launchpad.net>:
> ** Changed in: gnome-shell
>Status: Unknown => New
>
> --
> You received this bug
Thank you for your bug report report. Could you add your "journalctl -b
0 "log to the bug after getting the issue?
** Changed in: nautilus (Ubuntu)
Importance: Undecided => Low
** Changed in: nautilus (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because
Thank you for your bug report, that has been reported upstream before
but they didn't comment on it
** Changed in: file-roller (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: file-roller (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a
I don't understand you in "and unsurprising if it's during an operation
that requires
gnome-shell to perform disk IO like searching". What does it mean? Do such
freezes look like norm? I believe it's a problem and we should solve it. I
want to add, that I will not see such problems if I print a
Seems like a bionic updates regression. Duplicate bug 1832320 confirms
the same date.
** Tags added: regression-update
--
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/1832138
Title:
This bug is nearly 3 years old. Can you say if you think GNOME 3.32 in
Ubuntu 19.04 performs adequately now?
** Changed in: ubuntu-gnome
Status: New => Incomplete
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
** Changed in: tracker (Ubuntu)
Status: New =>
Hello,
Try to remove the snap package:
snap remove gnome-calculator
And install the deb package:
apt-get install gnome-calculator
I have experimented this on Ubuntu 18.04 and 19.04 and it seem to be really
faster.
I have experienced many speed problems with snap apps. And some was really
Public bug reported:
this is about the application Archive manager (I do not like generic
names btw. makes searching a pita) in gnome 3 as used by Ubuntu 18.04
If I open an archive and extract the contents, I get a window with two
options: close and show the files. I always want to press both
** Changed in: evolution-data-server
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution-data-server in Ubuntu.
https://bugs.launchpad.net/bugs/1828124
Title:
Ok, noted Sebastien. I do plan to SRU it myself, so I re-added a bionic
task and assigned it to me.
** Also affects: gnome-settings-daemon (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: gnome-settings-daemon (Ubuntu Bionic)
Importance: Undecided => High
** Changed
@Gunnar, we discussed it in the meeting and decided it was not important
to rls track, that doesn't mean it can't be fixed/SRUed though (also in
the futur, please don't do direct nomination without assignement, either
you plan to fix it yourself and then you can assign the bug to you or
use
I posted too soon. It turns out that in my case the error was a red-herring.
I loaded a backed up VM without the latest Ubuntu updates and I am able to log
in fine even though the syslog still contains the error:
CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error calling
On Tue, Jun 11, 2019 at 02:07:14AM -, Daniel van Vugt wrote:
> What model machine are you seeing this bug on?
A Lenovo T450s, while it has a fingerprint reader I've no interest in
using it.
--
Brian Murray
--
You received this bug notification because you are a member of Ubuntu
Desktop
** No longer affects: gnome-settings-daemon (Ubuntu Bionic)
--
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/1786344
Title:
Default IBus input method ignored in live
Same issue after an update this morning on Ubuntu 18.04. Running Ubuntu
in a VMWare Workstation. My login screen never appears after startup.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
** Merge proposal linked:
https://code.launchpad.net/~gunnarhj/ubuntu/+source/gnome-settings-daemon/+git/gnome-settings-daemon/+merge/368657
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
This was definitely fixed in revision 70. The specific fix was actually
building it based on core18/bionic with a newer version of GTK. This is
a new bug that I'll look into.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Public bug reported:
Over the last two releases I've noticed that if you have an audio player
such as Clementine running, pause the audio playback and watch a video
via VLC or SMPlayer and then close the video player and try to use the
media keys again, the following is logged to journald:
CONFIRMED: Same situation running 18.04.2 on VMWare 12.5.9. After
uncommenting the WaylandEnable=false line and rebooting, then I see the
login prompt as expected and I can then log in and use the system
normally again.
--
You received this bug notification because you are a member of Ubuntu
** Merge proposal unlinked:
https://code.launchpad.net/~gunnarhj/ubuntu/+source/gnome-settings-daemon/+git/gnome-settings-daemon/+merge/368657
** Merge proposal unlinked:
https://code.launchpad.net/~gunnarhj/ubuntu/+source/gnome-settings-daemon/+git/gnome-settings-daemon/+merge/368409
--
Thank you for your bug report, could you also send it upstream on
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues ?
** Changed in: gnome-settings-daemon (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
** Merge proposal linked:
https://code.launchpad.net/~gunnarhj/ubuntu/+source/gnome-settings-daemon/+git/gnome-settings-daemon/+merge/368678
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
** Changed in: evolution-data-server (Ubuntu)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to evolution-data-server in Ubuntu.
https://bugs.launchpad.net/bugs/1828124
Title:
** Description changed:
+ [Impact]
+
+ If you
+
+ * start your computer with a bootable USB stick or DVD with the
+ 18.04.2 desktop ISO
+
+ * wait until Ubiquity's welcome screen shows up (only possible on
+ systems with legacy BIOS; bug #1766047)
+
+ * select a language which requires an
bahner@venus:~$ gnome-control-center
(gnome-control-center:14031): display-cc-panel-WARNING **: 00:05:00.218:
no sunset data, using 16,00
(gnome-control-center:14031): display-cc-panel-WARNING **: 00:05:00.218:
no sunrise data, using 8,00
(gnome-control-center:14031): GLib-GObject-CRITICAL **:
Thanks. I see now that you filed this bug from a Unity session, and I
can reproduce the problem on Unity. The problem is that AFAIK gnome-
control-center is not designed to work with Unity; unity-control-center
is there for reasons.
Why are you using gnome-control-center on Unity?
** Changed in:
David, see bug 1832138.
--
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/1736011
Title:
CRITICAL: Unable to create a DBus proxy for GnomeScreensaver: Error
calling
** Changed in: mutter (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Also affects: mutter (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: gdm3 (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: mutter (Ubuntu Eoan)
Public bug reported:
I believe this is a regression for
#1740869 is not responding window is constantly showing when
debugging a program
I'm debugging my c++ sdl2 program in gdb and when I hit a breakpoint
this window shows up and I can't get it to stop asking me to close the
program.
Now tracking in bug 1832426 :(
--
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/1740869
Title:
is not responding window is constantly showing when
debugging a program
To
** Description changed:
- I believe this is a regression for
- #1740869 is not responding window is constantly showing when
debugging a program
+ I believe this is a regression for bug 1740869:
+ is not responding window is constantly showing when debugging a
program
I'm
42 matches
Mail list logo
