What also happens is if you move a window the busy cursor halts. But
this is just temporary, opening a new window causes it to start up
again. So only way to really stop is too log out.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Any info on when's that going to be released? Can't find it.
--
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/1812266
Title:
Keyboard layout indicator does not indicate current
[Expired for rhythmbox (Ubuntu) because there has been no activity for
60 days.]
** Changed in: rhythmbox (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to rhythmbox in Ubuntu.
[Expired for rhythmbox (Ubuntu) because there has been no activity for
60 days.]
** Changed in: rhythmbox (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to rhythmbox in Ubuntu.
Reported upstream:
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1075
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1075
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1075
** Also affects: gnome-shell via
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1075
Using the supplied instructions I can't reproduce the bug.
Any more hints?
** Package changed: wayland (Ubuntu) => mutter (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
Ah, yes I can reproduce it now. You have to open the text file by
clicking on it, and not after opening gedit.
** Also affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gnome-shell (Ubuntu)
Status: New => Confirmed
** Changed in: mutter (Ubuntu)
Please try live booting Ubuntu 19.04 and tell us if it has the same bug:
http://cdimages.ubuntu.com/daily-live/current/
If the bug is still present in 19.04 then please report it to the GNOME
developers here:
https://gitlab.gnome.org/GNOME/gnome-shell/issues
** Package changed: gdm3
Looks similar to bug 1820500.
** Summary changed:
-
/usr/bin/gnome-shell:11:js::PrimitiveTypeFlag:js::TypeSet::hasType:js::HasTrackedPropertyType:js::AddTypePropertyId:js::AddTypePropertyId
+ gnome-shell crashed with SIGSEGV in js::PrimitiveTypeFlag from
js::TypeSet::hasType from
Looks similar to bug 1820556.
** Summary changed:
- Agnome-shell crashed with SIGSEGV in js::PrimitiveTypeFlag()
+ gnome-shell crashed with SIGSEGV in js::PrimitiveTypeFlag()
** Information type changed from Private to Public
** Summary changed:
- gnome-shell crashed with SIGSEGV in
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
gnome-shell. This problem was most recently seen with package version
3.31.92-1ubuntu1, the problem page at
https://errors.ubuntu.com/problem/456e79f19058d9510c30dd6f41d00f2822174432
contains
You have been subscribed to a public bug:
Test case:
Fresh 19.04 daily current image, updated
Log in to a wayland session, open a single tesxt file in gedit
Move cursor out of gedit window or close gedit
What happens:
get busy cursor forever. Only way to stop is to either logout or open 2 files
** Tags added: multimonitor
--
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/1820423
Title:
monitors.xml is not parsed or applied correctly after reboot or
shutdown
To manage
** Summary changed:
- Firefox icon missing
+ Firefox icon is blank in the launcher
** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
Status: New => Confirmed
--
You received
Tracking in:
https://errors.ubuntu.com/problem/52cd7eaa22c6b950716ba83212632fd706353971
** Summary changed:
- gnome-shell crashed with SIGABRT
+ gnome-shell crashed with SIGABRT. Assertion failure in
meta_gpu_kms_flip_crtc: "monitor_manager->power_save_mode == META_POWER_SAVE_ON"
**
** Also affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
--
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/1820423
Title:
monitors.xml is not parsed or applied
*** This bug is a duplicate of bug 1820331 ***
https://bugs.launchpad.net/bugs/1820331
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
gnome-shell. This problem was most recently seen with package version
3.32.0-1ubuntu1, the problem page
*** This bug is a duplicate of bug 1820331 ***
https://bugs.launchpad.net/bugs/1820331
** This bug has been marked a duplicate of bug 1820331
gnome-shell crashed with SIGABRT. Assertion failure in
meta_gpu_kms_flip_crtc: "monitor_manager->power_save_mode == META_POWER_SAVE_ON"
--
You
Thanks.
It looks like gnome-shell is generally doing the right thing. It notices
an app is trying to place itself over the full screen and accepts that
as a old-style fullscreen request. Nothing unusual there. Gnome Shell is
behaving correctly for a window manager.
The only problem here is that
Can you select the session you want on the login screen by clicking on
the cog/gear icon?
** Package changed: xorg (Ubuntu) => gdm3 (Ubuntu)
** Changed in: gdm3 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
You have been subscribed to a public bug:
Failure to display prior desktop login GUI (Cinnamon).
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
Uname: Linux 4.15.0-46-generic i686
.tmp.unity_support_test.0:
** Also affects: gnome-documents (Ubuntu)
Importance: Undecided
Status: 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/1819193
Title:
Document search does not
fessmage,
You don't have the fix installed. The fix is in version:
3.28.3+git20190124-0ubuntu18.04.1
(per comment #37) but is not released yet.
You can download the .debs to try the fix from:
https://launchpad.net/ubuntu/+source/gnome-
Thanks.
That reminds me, make sure you don't have 'tlp' installed. Because that
would be bug 1574311 instead.
** Tags added: disco
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-bluetooth in Ubuntu.
Can you please try some newer kernels?
https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Incomplete
** Changed in: gnome-shell (Ubuntu)
Status: Confirmed
I just noticed you said "Cannot access the system remotely as well.",
which suggests a kernel problem.
Looking at your original kernel log you have:
[ 15.680794] [drm:si_dpm_set_power_state [radeon]] *ERROR* si_enable_smc_cac
failed
[ 15.712514] [drm:si_dpm_set_power_state [radeon]] *ERROR*
I forgot to mention that multi-monitors still won't work properly in
Wayland sessions. You'll only get the speed of the slowest monitor. But
a fix for that is coming eventually:
https://gitlab.gnome.org/GNOME/mutter/merge_requests/73
If you experience the problem in Xorg then that's a new
Marco,
You are missing the fix for this bug. See comment #23.
--
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/1774957
Title:
Network icons in status menu disappearing
To
Remember this bug is closed for Gnome Shell per comment #126.
But I understand that maybe some people are still experiencing similar
problems. It appears to me one such similar problem that wouldn't have
been fixed here is with laptop display switching where the set of
connected displays changes
** 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/1817924
Title:
apps launched from gnome shell do not get input focus
** Package changed: gnome-settings-daemon (Ubuntu) => gdm3 (Ubuntu)
** Summary changed:
- OSK Enter and backspace keys don't work
+ OSK Enter and backspace keys don't work in some text fields
** Description changed:
- The enter and backspace keys on the Ubuntu On-screen keyboard don't
- work.
** Bug watch added: gitlab.gnome.org/GNOME/gtk/issues #1749
https://gitlab.gnome.org/GNOME/gtk/issues/1749
** Changed in: gnome-shell
Status: Fix Released => Unknown
** Changed in: gnome-shell
Remote watch: gitlab.gnome.org/GNOME/gnome-shell/issues #1043 =>
** Changed in: gnome-shell
Status: New => Fix Released
--
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/1817924
Title:
apps launched from gnome shell do not get input
Public bug reported:
The enter and backspace keys on the Ubuntu On-screen keyboard don't
work. They don't work on Chromium and the apps menu, but work in gedit.
Ubuntu 18.10
** Affects: gnome-settings-daemon (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug
Same happens now here in ubuntu 18.04.2 LTS.
When the system locks, I'm logged out and all applications (programs) stop.
This behaviour came after a reboot, so maybe any updated module may be the
culprit.
It seems that the gnome shell crashes.
See attached syslog.
** Attachment added:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-shell (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
> I'm on 18.10 with dual monitors, and I'm still capped at 60hz on my
144hz display. However, if I disable my second display (it only supports
60hz), I my main gets 144hz as expected.
Is that with both dislays attached to an nvidia graphics card ? If so,
then what version of the nvidia driver,
I'm on 18.10 with dual monitors, and I'm still capped at 60hz on my
144hz display. However, if I disable my second display (it only
supports 60hz), I my main gets 144hz as expected.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Ubuntu 18.04.2 LTS, x86 (newest version available for this arch)
iio-sensor-proxy: 2.4-2
** Tags added: x86
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to iio-sensor-proxy in Ubuntu.
https://bugs.launchpad.net/bugs/1767650
Title:
39 matches
Mail list logo