The issue is gone after upgrading gnome-control-center.
---
Bionic: ubuntu-18.04.2-desktop-amd64.iso
Xenial: ubuntu-gnome-16.04.5-desktop-amd64.iso
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
** Tags removed: verification-needed-xenial
** Tags added:
[Expired for file-roller (Ubuntu) because there has been no activity for
60 days.]
** Changed in: file-roller (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to file-roller in Ubuntu.
[Expired for file-roller (Ubuntu) because there has been no activity for
60 days.]
** Changed in: file-roller (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to file-roller in Ubuntu.
** 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/1831555
Title:
gnome-shell crashed with SIGTRAP in
** Changed in: snapd-glib (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to snapd-glib in Ubuntu.
https://bugs.launchpad.net/bugs/1698984
Title:
Add snapd-glib to Ubuntu 14.04 LTS
** Summary changed:
- When Firefox is appeared and I open gno-menu, I will see shade of Firefox at
background
+ Ghost of an app window (like Firefox) is visible in the AO search background
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
** Tags added: visual-quality
**
** Summary changed:
- gnome-shell crashed with SIGSEGV in g_type_check_instance_is_a()
+ gnome-shell crashed with SIGSEGV in g_type_check_instance_is_a() from
g_file_get_parent() from _st_theme_resolve_url() from
_st_theme_node_ensure_background() from st_theme_node_paint_equal()
**
** Summary changed:
- gnome-shell crashed with SIGSEGV in g_type_check_instance_is_a()
+ gnome-shell crashed with SIGSEGV in g_type_check_instance_is_a() from
atk_object_notify_state_change()
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Won't Fix
--
You received this bug
*** This bug is a duplicate of bug 1833098 ***
https://bugs.launchpad.net/bugs/1833098
Thanks. We can track this in bug 1833098 now.
** This bug has been marked a duplicate of private bug 1833098
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which
Yes it makes sense if the shell crashes then very likely you have no
Xorg server to run xrandr against :)
--
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/1722886
Title:
Include
Ah, OK, thanks. No news since 2018-08 then - I was hoping the GNOME
GitLab would have something new :(
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1685754
Title:
@malix0 The MyPaint package is inherited from Debian. They typically do
not package alpha or beta packages, but only final releases since the
focus is on stability as opposed to having the latest thing. Therefore,
this is likely not to happen until MyPaint has released 2.0.0.
--
You received
I'll do my best to provide a test kernel by tomorrow, for impacted user
to test, and confirm it works before I submit it to the Ubuntu kernel
team.
Stay tuned.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
Now that MyPaint 2.0.0-alpha is available, it's worth packaging it?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gimp in Ubuntu.
https://bugs.launchpad.net/bugs/1803924
Title:
Gimp conflict with MyPaint
To manage notifications
904efd9e3f4c8f288b1279a316eed8e177190c8f^ (AKA
ac3069e67f5659131d7ac5f54d966005bbc40af8) have the problem, but
ac3069e67f5659131d7ac5f54d966005bbc40af8 doesn't.
So the kernel bisection is completed and found the right good commit
which is:
904efd9e3f4c8f288b1279a316eed8e177190c8f^ (AKA
ac3069e67f5659131d7ac5f54d966005bbc40af8) have the problem, but
904efd9e3f4c8f288b1279a316eed8e177190c8f doesn't.
So the kernel bisection is completed and found the right good commit
which is:
https://github.com/torvalds/linux/commit/904efd9e3f4c8f288b1279a316eed8e177190c8f
--
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
wbug: With Bug
wnbug: With No Bug
git bisect start '--term-old=wbug' '--term-new=wnbug' '--'
'drivers/gpu/drm/vmwgfx'
# wbug: [62e9ccfaaedffd057e921fca976f9f7f71c9b254] Linux 4.16.18
git bisect wbug 62e9ccfaaedffd057e921fca976f9f7f71c9b254
# wnbug: [37efe80ce85f76b3b30d7b4ea40550e6a5a5b71a]
** Changed in: linux (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
Currently, the upstream issue has NOT been migrated to GNOME GitLab yet,
but is still being tracked at
https://bugzilla.gnome.org/show_bug.cgi?id=780622
** Bug watch added: bugzilla.gnome.org/ #780622
https://bugzilla.gnome.org/show_bug.cgi?id=780622
--
You received this bug notification
And bionic?
--
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/1774587
Title:
nautilus crashes in recent_thread_func -> is_file_valid_recursive ->
g_local_file_query_info ->
Thanks for your work!
--
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/1774587
Title:
nautilus crashes in recent_thread_func -> is_file_valid_recursive ->
g_local_file_query_info
** Description changed:
https://errors.ubuntu.com/problem/7c06cf06fd970ce31033f0d775b3adf97559e4ea
-
- ---
-
- .
-
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: nautilus 1:3.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux
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.
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 gnome-shell in Ubuntu.
"20fb5a635a0c" also works just fine on my side, will continue with the
kernel bisect.
--
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
Building a kernel with "37efe80ce85f drm/vmwgfx: use monotonic event
timestamps" being the HEAD doesn't exhibit the issue.
I'm now building and about to test 37efe80ce85f^1 (AKA 20fb5a635a0c) to confirm.
In theory it should fails with "20fb5a635a0c" if "37efe80ce85f" is the one.
- Eric
--
You
Just crashed again. Submitted a new bug report.
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1833098
--
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/1832856
Title:
Does anyone know where this bug is being tracked upstream now? GNOME has
migrated from Bugzilla to GitLab, and I haven't been able to find the
GitLab version of the Bugzilla bug.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Just had another crash. Tried to send the report but Apport shows me the
attached message.
** Attachment added: "Apport error"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832856/+attachment/5271168/+files/Screenshot%20from%202019-06-17%2014-08-52.png
--
You received this bug
Xrandr output is missing from logs currently, but in any case the
configuration is something that we might try to apply anyways also
outside X11, so better to have this anyways.
** Description changed:
When a bug is submitted to ubuntu about gnome-shell it would be
convenient to have such
Please, look. It is shade of Firefox.
пн, 17 июн. 2019 г., 5:30 Daniel van Vugt
:
> Can you please reword that? I don't understand (and can't see in the
> video) what the problem is here.
>
> ** Changed in: gnome-shell (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug
*** This bug is a duplicate of bug 1800196 ***
https://bugs.launchpad.net/bugs/1800196
Thanks for pointing me in the right direction Daniel, I'll follow the
other bug report. Have a nice day!
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Hola.
Acabo de firmar la petición "Comunidad Educativa : Que la Junta de
Andalucía Admita la titulación de Filología Árabe para poder ser profesor"
y pensé que te podría interesar.
Estamos intentando conseguir 100 firmas y necesitamos todo el apoyo que
podamos conseguir. Puedes leer más y firmar
** Description changed:
+ https://errors.ubuntu.com/problem/b9099237efc0ed3a713ac34e260c33a215c4599d
+
Crashes when updating extensions using gnome-tweaks on Gnome 3.32+
ProblemType: Crash
DistroRelease: Ubuntu 19.04
Package: gnome-shell 3.32.0+git20190410-1ubuntu1
*** This bug is a duplicate of bug 1825727 ***
https://bugs.launchpad.net/bugs/1825727
** This bug has been marked a duplicate of private bug 1825727
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
*** This bug is a duplicate of bug 1825727 ***
https://bugs.launchpad.net/bugs/1825727
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.2-1ubuntu1, the problem page
Thanks. Unfortunately that page is showing an unreadable stack trace. It
also says that the gnome-shell binary file has changed (update
installed) since the crash occurred so it can't be retraced/reported.
Please reproduce the crash again and repeat the steps from comment #2.
--
You received
** Changed in: gdm3 (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** Changed in: mutter (Ubuntu)
Status: New => Triaged
** Changed in: mutter (Ubuntu)
Importance: Undecided => High
**
*** This bug is a duplicate of bug 1825727 ***
https://bugs.launchpad.net/bugs/1825727
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1825727, so is being marked as such.
Btw, I forced the report on the latest crash and that report is
available at
https://errors.ubuntu.com/user/e049722ec528a0ea58304d6b1ba3374e27d4ea39c9bf68afdac98ec882abe5298545fe4527c2cce5895b5b3ad6e493e0853330a2881fd4285e4d43d6c5e2dfa3
--
You received this bug notification because you are a
** Changed in: gnome-shell (Ubuntu)
Status: Invalid => Incomplete
--
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/1832856
Title:
Gnome-shell crashes frequently in gnome-
As I stated in the OP, I initially talked with the wsmatrix maintainer
and, as he suggested, disabled the extension for a while and the crashes
continued.
I will try disabling the extension once again and following your
directions in #2 to report new crashes.
--
You received this bug
The status for mutter will remain incomplete till someone tries the
suggestion from comment #31.
Sorry, I still can't reproduce this bug myself.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
The problem I mentioned in comment #15 is now logged as bug 1833045.
It's clearly different to this one.
--
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
Public bug reported:
Ubuntu on Wayland login option is missing on random boots in VMware.
This seems to be a persistent problem with Ubuntu 18.04, but seems to
have been fixed at least in 19.04.
In 18.04 where the bug does exist, upgrading the kernel to 5.1 doesn't
seem to help. This looks and
Fix in progress: https://gitlab.gnome.org/GNOME/gnome-
shell/merge_requests/486
--
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/1717453
Title:
Shell menus (panel, dock, window)
Please test latest mainline kernel:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2-rc5/
If the issue persists, please file an upstream bug at
https://bugs.freedesktop.org/
Product: DRI
Component: DRM/intel
--
You received this bug notification because you are a member of Ubuntu
Desktop
Note that not all performance improvements will ever make it into Ubuntu
18.04.
If you want higher performance right now then please use Ubuntu 19.04
instead. And Ubuntu 19.10 will be even faster (_after_ it gets mutter
3.33.3 or later).
Do you find that Ubuntu 19.04 has this same bug?
**
May be you can't see this sad picture. After I launch a few huge apps
animation will freeze, button press response is very slow. I can say that
Unity shell on this PC is more performance and doesn't have such problems.
пн, 17 июн. 2019 г., 5:30 Daniel van Vugt
:
> It sounds like you're trying to
50 matches
Mail list logo
