[Expired for tracker (Ubuntu) because there has been no activity for 60
days.]
** Changed in: tracker (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to tracker 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 spice-vdagent (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: spice-vdagent (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to spice-vdagent in Ubuntu.
I was able to reproduce the problem with 4.15.0-51, but problem seems to
be gone using the hwe kernel 4.18.0-21-generic.
I'll do a kernel bisection and try to find the commit which fixes the situation.
I'll also ask another impacted user to confirm if v4.18 works fine too, to
double-check my
** Changed in: gnome-shell
Status: Unknown => 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/1832875
Title:
On-screen keyboard lacks several French layouts
Hello Mitar, or anyone else affected,
Accepted gnome-control-center into bionic-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/gnome-control-center/1:3.28.2-0ubuntu0.18.04.5 in a few hours, and then
in the -proposed repository.
Please help us by
Hello ethan.hsieh, or anyone else affected,
Accepted gnome-control-center into bionic-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/gnome-control-center/1:3.28.2-0ubuntu0.18.04.5 in a few hours, and then
in the -proposed repository.
Please help us
Hello ethan.hsieh, or anyone else affected,
Accepted gnome-control-center into xenial-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/gnome-control-center/1:3.18.2-1ubuntu6.1 in a few hours, and then in
the -proposed repository.
Please help us by
Public bug reported:
I am getting this error in my log, Ubuntu 18.04:
Cannot access vdagent virtio channel /dev/virtio-
ports/com.redhat.spice.0
** Affects: gnome-session (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1832903
and then change the status of the bug to 'Confirmed'.
If, due to the
Public bug reported:
After an upgrade from xenial to 18.04.2 OR 18.04.1 to 18.04.2 ,the login
screen doesn't work if 'Wayland' is in use (default) and if video kernel
driver is 'vgwfx'.
It looks like the login screen got stuck, doesn't exit, and doesn't
fallback to 'x11' by itself in case of
** Description changed:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
gnome-shell. This problem was most recently seen with package version
3.28.4-0ubuntu18.04.1, the problem page at
https://errors.ubuntu.com/problem/d3f9725b7fae2763643521acfc58c734f829dd64
*** This bug is a duplicate of bug 1832869 ***
https://bugs.launchpad.net/bugs/1832869
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.28.4-0ubuntu18.04.1, the
*** This bug is a duplicate of bug 1832869 ***
https://bugs.launchpad.net/bugs/1832869
** This bug has been marked a duplicate of bug 1832869
gnome-shell crashed in g_hash_table_iter_next meta_display_list_windows
meta_workspace_list_windows
--
You received this bug notification because
** Changed in: gnome-shell (Ubuntu)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
** Changed in: gnome-shell (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
** Changed in: accountsservice
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/1832865
Title:
gnome-shell crashes on g_str_hash ->
I can confirm this is still happening in Ubuntu 19.04.
--
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/1723117
Title:
Desktop icons goes under the Dock, if the Dock is set to
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
The crash is happening since gnome-shell/mutter 3.28.3+git20190124.
I wasn't able to track-down the issue since we're missing Javascript
stacktrace so, for people who can replicate this, we'd need to get a
trace.
You can have one following what said in
https://is.gd/wiki_gnome_shell_crash_debug
Public bug reported:
The on-screen keyboard in Gnome Shell is not localized (at least for
some locales), and always displays a QWERTY keyboard, independently of
the selected layout.
See upstream issue https://gitlab.gnome.org/GNOME/gnome-shell/issues/997
** Affects: gnome-shell
Importance:
*** This bug is a duplicate of bug 1832869 ***
https://bugs.launchpad.net/bugs/1832869
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.1-1ubuntu1, the problem page
*** This bug is a duplicate of bug 1832869 ***
https://bugs.launchpad.net/bugs/1832869
** This bug has been marked a duplicate of bug 1832869
/usr/bin/gnome-shell:11:g_hash_table_iter_next:meta_display_list_windows:meta_workspace_list_windows:ffi_call_SYSV:ffi_call
--
You received this
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.28.4-0ubuntu18.04.1, the problem page at
https://errors.ubuntu.com/problem/d3f9725b7fae2763643521acfc58c734f829dd64
*** This bug is a duplicate of bug 1832869 ***
https://bugs.launchpad.net/bugs/1832869
** This bug has been marked a duplicate of bug 1832869
/usr/bin/gnome-shell:11:g_hash_table_iter_next:meta_display_list_windows:meta_workspace_list_windows:ffi_call_SYSV:ffi_call
--
You received this
*** This bug is a duplicate of bug 1832869 ***
https://bugs.launchpad.net/bugs/1832869
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.28.4-0ubuntu18.04.1, the
*** This bug is a duplicate of bug 1832869 ***
https://bugs.launchpad.net/bugs/1832869
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.28.4-0ubuntu18.04.1, the
*** This bug is a duplicate of bug 1832869 ***
https://bugs.launchpad.net/bugs/1832869
** This bug has been marked a duplicate of bug 1832869
/usr/bin/gnome-shell:11:g_hash_table_iter_next:meta_display_list_windows:meta_workspace_list_windows:ffi_call_SYSV:ffi_call
--
You received this
** Changed in: gnome-shell (Ubuntu)
Status: New => Triaged
--
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/1826918
Title:
gnome-shell crashed with SIGSEGV in
Not a gnome-shell issue, but an accountsservice one.
** Summary changed:
-
/usr/bin/gnome-shell:11:g_str_hash:g_hash_table_hash_to_index:g_hash_table_lookup_node:g_hash_table_lookup:update_user
+ gnome-shell crashes on g_str_hash -> g_hash_table_hash_to_index ->
g_hash_table_lookup_node ->
Here is the Stacktrace from the Error Report:
#0 g_application_impl_get_dbus_object_path (impl=0x0) at
../../../gio/gapplicationimpl-dbus.c:855
No locals.
#1 0x7f1d99b3afa4 in g_application_get_dbus_object_path
(application=) at ../../../gio/gapplication.c:2108
__FUNCTION__ =
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.1-1ubuntu1~19.04.1, the problem page at
https://errors.ubuntu.com/problem/1a63c83d1c90f48036a2f839bf608738eefde4c8
Public bug reported:
After the update to 3.32.1 gnome-shell crashes frequently. Before, on
3.32.0, I had no crashes and had a stable desktop. Now, I get 3-4
crashes a day, on average.
Here is log snippet on the crash:
Jun 14 14:59:20 falcon org.gnome.Shell.desktop[7076]: GNOME Shell crashed
The same problem.
Ubuntu 18.04
QT Creator (gdb 8.2)
gnome-shell 3.28.4
Repeatedly warning "MyApp is not responding" under debugging
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
** Changed in: exo
Status: Confirmed => Fix Released
--
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/1778069
Title:
[xfce] nautilus don't open files if set as default file
Resolved with the following commits:
https://git.xfce.org/xfce/exo/commit/?id=404a7ef73246b73cb4cd2a4ab8cc10e1a02d6b74
Always terminates the mimetype associations with ";"
https://git.xfce.org/xfce/exo/commit/?id=48e12f1d5f31e576f7017c50785032ef6d22cfd1
Removes bad entries that should no longer
Fixed with https://gitlab.gnome.org/GNOME/gnome-
shell/merge_requests/576/
** Changed in: gnome-shell (Ubuntu)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
** Changed in: gnome-shell (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because
This happens to me periodically with Ubuntu 16.04.6 LTS, Kernel
4.14.114.
External HDMI 1080p TV nVidia GTX 970M driven
External HDMI 4K TV i915 Thunderbolt3 USB-C driven
Internal Dell 1080p LCD i915 driven
Method:
1) close laptop lid with power & systemd set to "do nothing"
2) external
Daniel
After uncommenting the Wayland option the login appears, I can log in
but the desktop refuses to resize. This was working previously. Entering
full screen however works and doesn't crash the system.
The crash with kernel option nomodeset when resizing or attempting
fullscreen is probably
For me the login screen hangs as the Ubuntu logo at the bottom of the
screen fades in.
The crashes are here
https://errors.ubuntu.com/user/9918ca952fad5050e5d19cd326c70f270fae7631e330cf3c0c0ee4c728f149c2412b9c7bbdbfed5f6d72b3f62f187ada199b6d5ac8043b4329d0bbe352b51487
--
You received this bug
*** This bug is a duplicate of bug 1424201 ***
https://bugs.launchpad.net/bugs/1424201
Thank you. I wish you make Ubuntu 19.10 and next LTS release the most
stable and fast. I will continue test and find new bugs.
--
You received this bug notification because you are a member of Ubuntu
Looking at hungboot.txt I am starting to think maybe the login screen
('gnome-shell' process) is actually running in Wayland mode but failing
to display. That would explain a lot...
Pat, can you please reproduce the bug again and while it is happening:
1. SSH into the VM.
2. Run 'pidof
Please, I shot this: https://photos.app.goo.gl/DHtcN9ZrHLVR8Ne98
пт, 14 июн. 2019 г. в 12:05, Daniel van Vugt :
> Also, before locking the screen please open a Terminal window and run
> 'top' then take a screenshot of the window and attach it to this bug.
>
> ** Changed in: gdm3 (Ubuntu)
>
I have been trying to reproduce this bug in VMware but have not been
able to. Ubuntu 18.04 always starts up with a login screen successfully
for me.
What it does not do successfully is offer the "Ubuntu on Wayland" option
most of the time. So I expect that's the same root cause as this bug.
Jussi,
That sounds like maybe a different bug. Although "commenting out the
Wayland" is also not what you need to do. You need to change:
#WaylandEnable=false
to:
WaylandEnable=false
If that doesn't fix the problem for you then you have a different bug.
In that case please open a new bug
Are you able to make another video without Firefox running?
** Changed in: gdm3 (Ubuntu)
Status: Incomplete => New
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Also, before locking the screen please open a Terminal window and run
'top' then take a screenshot of the window and attach it to this bug.
** Changed in: gdm3 (Ubuntu)
Status: New => Incomplete
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
--
You received this
*** This bug is a duplicate of bug 1424201 ***
https://bugs.launchpad.net/bugs/1424201
> Shell works slowly with efforts also without Firefox launching.
Yes, we know. But that's not an exact bug as much as an observation that
performance is poor. For the type of issues you describe I have
It's not depend by Firefox
пт, 14 июн. 2019 г., 11:40 Daniel van Vugt
:
> Also, does the bug still occur if you close Firefox before locking the
> screen?
>
> If not then this may be related to bug 1832816.
>
> ** Summary changed:
>
> - Ubuntu 19.10 (alpha) lockscreen freezes
> + Locking and
I don't use any Gnome Extensions. It's clear system after installation.
If I switch button "Auto login" I don't see any changes with bug.
пт, 14 июн. 2019 г., 11:20 Daniel van Vugt
:
> Also, does the bug still occur if you disable this?
>
> AutomaticLoginEnable=true
>
> --
> You received this
*** This bug is a duplicate of bug 1424201 ***
https://bugs.launchpad.net/bugs/1424201
Shell works slowly with efforts also without Firefox launching.
пт, 14 июн. 2019 г., 11:30 Daniel van Vugt
:
> *** This bug is a duplicate of bug 1424201 ***
> https://bugs.launchpad.net/bugs/1424201
Also, does the bug still occur if you close Firefox before locking the
screen?
If not then this may be related to bug 1832816.
** Summary changed:
- Ubuntu 19.10 (alpha) lockscreen freezes
+ Locking and unlocking the screen is slow and stuttery
** Tags added: performance
--
You received this
** Changed in: mutter (Ubuntu Bionic)
Status: Confirmed => In Progress
--
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:
Login screen never appears on vmwgfx but
*** This bug is a duplicate of bug 1424201 ***
https://bugs.launchpad.net/bugs/1424201
** Summary changed:
- Ubuntu 19.10 Gnome Desktop works with freezes and efforts
+ Gnome Shell is slow and stuttery while Firefox is loading/playing YouTube
--
You received this bug notification because
*** This bug is a duplicate of bug 1424201 ***
https://bugs.launchpad.net/bugs/1424201
It appears the problem is probably that your web browser is using all
the CPU power to display YouTube's auto-playing front page. Because our
web browsers don't support hardware video decoding (LP:
Also, does the bug still occur if you disable this?
AutomaticLoginEnable=true
--
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/1832812
Title:
Ubuntu 19.10 (alpha) lockscreen
Can you confirm you are not using any gnome-shell extensions?
** Changed in: gdm3 (Ubuntu)
Status: New => Incomplete
** Also affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
--
You received
The bug is marked as "fix released" so as far as we know the issue is
closed.
If you still experience problems then please open a new bug by running:
ubuntu-bug gnome-shell
and mention that it seems to be related to bug 1812266.
--
You received this bug notification because you are a member
I have currently installed: gnome-shell 3.28.4-0ubuntu18.04.1.
After more than five months, this bug is still in my installation of Ubuntu
18.04.2 LTS and annoys me every single day.
I am really disappointed.
Can somebody explain to me in simple language why the bug fix is still not
released?
Public bug reported:
Details in my video: https://photos.app.goo.gl/HeGFUeWzDeGmThYp8
Device: HP 250 G6 Notebook, Intel Celeron N3350, integrated video card, 4 GB
DDR3 RAM, 128 GB SSD Samsung.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-shell 3.32.2-1ubuntu1
Public bug reported:
Details in my video: https://photos.app.goo.gl/x45Razdc2d3TPqCF8
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gdm3 3.32.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
Uname: Linux 5.0.0-16-generic x86_64
ApportVersion: 2.20.11-0ubuntu3
Device: HP 250 G6 Notebook, Intel Celeron N3350, integrated video card,
4 GB RAM DDR3, 128 GB SSD Samsung.
--
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/1832812
Title:
Ubuntu 19.10
How to reproduce this ?
Previously crash was in `nautilus_window_slot_get_location` which is now
fixed upstream.
With 3.32.1-1ubuntu1, I can't reproduce with G_MESSAGES_DEBUG=all
/usr/bin/nautilus. Can you copy/paste error as I don't have access?
But we don't really to update windows locations
62 matches
Mail list logo
