** Summary changed:
- gnome-shell crashed with SIGTRAP in _g_log_abort() from
g_log_default_handler() from default_log_handler() from g_logv("Function
AsyncReadyCallback terminated with uncatchable exception") from g_log()
+ gnome-shell crashed with SIGTRAP in _g_log_abort() from
I can reproduce this bug by creating a guest OS using a 18.04.1 .iso I
downloaded last year and attempting to update.
I created another guest OS using the 18.04.2 .iso I downloaded yesterday works
fine after updating.
--
You received this bug notification because you are a member of Ubuntu
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.
Using VirtualBox 6 and VMSVGA as recommended by Eric I still can't
reproduce the bug. But I think I can see why now: Ubuntu 18.04.2 comes
with kernel 4.18
Let me try 18.04.1...
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter
It seems I stumbled on a workaround. Just install the kernel that comes
in the 18.04.2 ISO:
https://launchpad.net/ubuntu/+source/linux-hwe
** Also affects: linux-hwe (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-hwe (Ubuntu Bionic)
Status: New => Fix Released
*** This bug is a duplicate of bug 1736664 ***
https://bugs.launchpad.net/bugs/1736664
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1736664, so it is being marked as such. Please
Please use journalctl to get the ProcessID (in the example you posted
above that would be "4764" or "4983" or "16717", then make sure that
debug packages are installed for evolution and glib2 and get a
stacktrace of that crash via the command:
coredumpctl gdb ProcessID
(please replace ProcessID
Oh sorry, I forgot to include the info you requested. I am using Ubuntu
Linux 18.04.2 and I don't use "nautilus". I always open djvu files using
the command "evince filename,djvu" from within terminal. Well, sometimes
I use "djview filename.djvu" (when I want to find out the resolution),
but
Oops, typo in the previous comment: I wrote "evince filename,djvu" but
of course I meant "evince filename.djvu", i.e. with dot "." rather than
comma ",".
** Bug watch added: Debian Bug tracker #876710
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876710
** Bug watch added: Red Hat
Here are the links to the posts where this bug is mentioned:
https://ubuntuforums.org/showthread.php?t=2390953=2
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876710
https://bugzilla.redhat.com/show_bug.cgi?id=1507305
--
You received this bug notification because you are a member of
Also, here is some useful info for you:
$ apt list --installed | grep djvu
WARNING: apt does not have a stable CLI interface. Use with caution in
scripts.
djvubind/bionic,bionic,now 1.2.1-5 all [installed]
djvulibre-bin/bionic,now 3.5.27.1-8 amd64 [installed,automatic]
Thank you for your bug report. What version of Ubuntu are you using? How
does it fail to open the files is it just that nautilus doesn't list is
as an option? Can you add a file ewample to the bug?
** Changed in: evince (Ubuntu)
Importance: Undecided => Low
** Changed in: evince (Ubuntu)
That's a feature, see bug #38512
** Changed in: rhythmbox (Ubuntu)
Status: Confirmed => Invalid
--
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/1584465
Title:
I closed
Public bug reported:
Every time I upgrade evince (as part of "sudo apt update; sudo apt
upgrade") I have to remember to edit the file /usr/lib/x86_64-linux-
gnu/evince/4/backends/djvudocument.evince-backend and add
"image/vnd.djvu" to the end of MimeType list. If I don't do this then
evince is
Which calendar type is this about? Local? Remote? Google? EWS? Something
else?
Are those meetings created by yourself? If not, are those meetings
created by someone in the same timezone?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
No problem here parsing and displaying the line
Date: Thu, 31 Jan 2019 19:15:39 + (UTC)
in Evolution 3.32.3.
This should not be reported upstream until there is a testcase (exported
email message) and until successfully re-tested in a version supported
by upstream developers (currently:
** Description changed:
+ * Impact
+ Sometime multimedia keys stop working
+
+ * Test case
+ - start playing an audio file in VLC/totem/smplayer
+ - pause
+ - open a video in another player
+ - exit the other player
+ - try to resume the music play from the first one using the play key
+
+ ->
And the problem is indeed the kernel advertising
DRM_CAP_TIMESTAMP_MONOTONIC but instead of using CLOCK_MONOTONIC it is
really using CLOCK_REALTIME. This confirms kernel commit 37efe80ce85f is
the fix, but it may well have some prerequisite commits we haven't fully
worked out...
This bug was fixed in the package glib2.0 - 2.60.4-1
---
glib2.0 (2.60.4-1) experimental; urgency=medium
* New upstream release (LP: #1832457)
+ Fixes to improved network status detection with NetworkManager (#1788)
+ Leak fixes to some `glib-genmarshal` generated code
+
Workaround for mutter proposed here:
https://code.launchpad.net/~vanvugt/ubuntu/+source/mutter/+git/mutter/+merge/369083
--
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
** Merge proposal linked:
https://code.launchpad.net/~vanvugt/ubuntu/+source/mutter/+git/mutter/+merge/369083
--
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:
UPDATE: No, removing djvulibre-desktop solved the problem only for the
_multipage_ DjVu files, but not for the single-page ones. So, for a
single-page djvu files I still get the above-mentioned error message,
unless I manually add "image/vnd.djvu" to the end of MimeTypes in
This bug was fixed in the package gnome-settings-daemon -
3.32.1-1ubuntu2
---
gnome-settings-daemon (3.32.1-1ubuntu2) eoan; urgency=medium
* debian/patches/ubuntu_ibus_configs.patch:
- Always call add_ibus_sources_from_locale() during the first run
of g-s-d. This ensures
Will also build a kernel 4.15 with 37efe80ce85f and see the outcome.
Should be able to provide an update by EOD.
--
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
In the .H files of the libappindicator I have found 2 authors' e-mails:
Ted Gould and Cody Russell
. I have written email and received the
email-daemon answer that this e-mails are not valid. I see the problem
and want to know who can help me to find the decision.
Could you be so kind to direct
Here is the last of the output after running the first test repo update
command in comment #73 on the Bug1832138VM.zip VM I built.
I'm guessing either there is an integrity issue upstream or more likely
there is a missing step so that a system that has been using the default
repo settings is
** Changed in: gdm3 (Ubuntu)
Status: Confirmed => Won't Fix
** Changed in: mutter (Ubuntu)
Status: Confirmed => Triaged
** Changed in: mutter (Ubuntu)
Status: Triaged => In Progress
** Tags added: fixed-in-3.33.3 fixed-upstream
--
You received this bug notification
Great for the quick feedback.
I have until June 26th to submit the patch for the next cycle[0]
It's giving me a couple of more days to get other impacted users
feedback.
[0] - https://kernel.ubuntu.com/
- Eric
--
You received this bug notification because you are a member of Ubuntu
Desktop
** Description changed:
+ [Impact]
+
+ With most recent version of mutter installed.
+ If running kernel is in the 4.15 serie (using the vmwgfx video kernel drive)
and if the login screen uses wayland, then the login prompt doesn't appears.
+ All we see is the purple background with ubuntu at
Eric,
your new test kernel works for... and screen-resizing works this time too.
To confirm, I am running the correct kernel build;
uname -a
Linux ubuntuvm1 4.15.0-53-generic #57+hf231164v20190620b11-Ubuntu SMP
Thu Jun 20 13:18:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
--
You received this
After building and testing:
"
9c5f23a4a699 drm/vmwgfx: use monotonic event timestamps
c78b765c2de0 UBUNTU: Ubuntu-4.15.0-53.57
"
the above seems to do the trick ^ which will make the SRU easier (only one
commit).
I just don't know why the kernel git bisect testing found another commit, but
Here the journalctl info
I tested the Hotspot option with or without docking station.
Let me know if you need anything else
** Attachment added: "journal.zip"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1833471/+attachment/5271861/+files/journal.zip
--
You received
Removing packages from eoan:
gnome-vfs 1:2.24.4-6.1ubuntu2 in eoan
libgnomevfs2-0 1:2.24.4-6.1ubuntu2 in eoan amd64
libgnomevfs2-0 1:2.24.4-6.1ubuntu2 in eoan arm64
libgnomevfs2-0 1:2.24.4-6.1ubuntu2 in eoan armhf
Removing packages from eoan:
libbonoboui 2.24.5-4 in eoan
libbonoboui2-0 2.24.5-4 in eoan amd64
libbonoboui2-0 2.24.5-4 in eoan arm64
libbonoboui2-0 2.24.5-4 in eoan armhf
libbonoboui2-0 2.24.5-4 in eoan i386
Removing packages from eoan:
orbit2 1:2.14.19-4 in eoan
liborbit-2-0 1:2.14.19-4 in eoan amd64
liborbit-2-0 1:2.14.19-4 in eoan arm64
liborbit-2-0 1:2.14.19-4 in eoan armhf
liborbit-2-0 1:2.14.19-4 in eoan i386
Removing packages from eoan:
libbonobo 2.32.1-3 in eoan
libbonobo2-0 2.32.1-3 in eoan amd64
libbonobo2-0 2.32.1-3 in eoan arm64
libbonobo2-0 2.32.1-3 in eoan armhf
libbonobo2-0 2.32.1-3 in eoan i386
Removing packages from eoan:
libgnome 2.32.1-6 in eoan
libgnome-2-0 2.32.1-6 in eoan amd64
libgnome-2-0 2.32.1-6 in eoan arm64
libgnome-2-0 2.32.1-6 in eoan armhf
libgnome-2-0 2.32.1-6 in eoan i386
libgnome-2-0
Removing packages from eoan:
libgnome-keyring 3.12.0-1build1 in eoan
gir1.2-gnomekeyring-1.0 3.12.0-1build1 in eoan amd64
gir1.2-gnomekeyring-1.0 3.12.0-1build1 in eoan arm64
gir1.2-gnomekeyring-1.0 3.12.0-1build1 in eoan armhf
Additional confirmation...
Working under VMware Workstation v12.5.7 running kernel 4.15.0.52:
Having performed the workaround of uncommenting the
WaylandEnable=false...
- Re-commented the line & rebooted to experience the hang with the
Ubuntu logo before the login screen
- Using your
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => Critical
** Changed in: linux (Ubuntu Bionic)
Importance: Critical => High
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
Detailled instructions on how to use my ppa :
$ sudo add-apt-repository ppa:slashd/kernel-builder
$ sudo apt-get update
$ sudo apt install linux-image-unsigned-4.15.0-53-generic
linux-modules-4.15.0-53-generic linux-modules-extra-4.15.0-53-generic
then reboot, and once login you can confirm if
Ok, including my own testing we got 4 positive feedback.
With that being said, I have just submitted the patch to our kernel team a few
minutes ago.
This will be part of the next cycle 01-July through 21-July.
Thanks for the pre-SRU testing, we will need you guys one more time
during the
There is a PR open to fix this: https://gitlab.gnome.org/GNOME/gnome-
shell/merge_requests/587
--
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/1832792
Title:
App-switcher icons
There is a PR open to fix this: https://gitlab.gnome.org/GNOME/gnome-
shell/merge_requests/587
--
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/1831161
Title:
App-switcher icons
In isolation I don't think it's correct to say that Wayland sessions
have "no external monitors". Wayland sessions do work with external
monitors on the Nvidia driver if you have nvidia-drm.modeset=1. I've
confirmed this on a desktop at least.
It sounds like you're describing some other
** Description changed:
[Impact]
With most recent version of mutter installed.
If running kernel is in the 4.15 serie (using the vmwgfx video kernel driver)
and if the login screen uses wayland, then the login prompt doesn't appears.
All we see is the purple background with ubuntu in
I think his point was to isolate the problem as being gdm3's wayland code.
If you need modeset=1 for wayland, then why is there any effort to support
nvidia and wayland under gnome, since it won't work (or are only optimus
systems affected by this?)
my point was that you marked this as invalid,
*** This bug is a duplicate of bug 1833558 ***
https://bugs.launchpad.net/bugs/1833558
** This bug has been marked a duplicate of private bug 1833558
--
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 1833558 ***
https://bugs.launchpad.net/bugs/1833558
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
Additional confirmation...
Looks like this updated kernel fixes the issue on the affected test VM I
created.
Using the detailed directions in comment #75, I was able to install the
new test kernel and reboot.
Verified the expected version value with uname and then installed the
packages that
** Description changed:
[Impact]
With most recent version of mutter installed.
If running kernel is in the 4.15 serie (using the vmwgfx video kernel driver)
and if the login screen uses wayland, then the login prompt doesn't appears.
All we see is the purple background with ubuntu in
What we know about this bug is that gdm3, nvidia and modeset=1 is broken
under configurations which are not broken when sddm and lightdm are
used.
we know that gdm3 sessions with external monitors work with root
permissions.
we know that gdm3 compiled with wayland also works (according to the
"gdm3 compile without wayland", I meant
--
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/1716857
Title:
nvidia-drm.modeset=1 results in no monitors detected by Xorg
To manage
just one last thing, possibly you are not aware that 19.04 Ubuntu wayland
sessions have exactly the same problem: no external monitors. While this
bug refers to Xorg, the problem is not limited to Xorg. At least on my
Optimus laptop. And when I use its multiplexor to go into pure Nvidia mode,
no
gnome-shell!587 only says it fixes gnome-shell#1325. If you think it
also fixes gnome-shell#1370 then you should probably add a comment here:
https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/587
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
> If you need modeset=1 for wayland, then why is there any effort to support
nvidia and wayland under gnome, since it won't work (or are only optimus
systems affected by this?)
I don't understand the question, sorry. The statement "it won't work" is
wrong. Wayland does work. This bug is about
Actually, maybe those other DMs don't run as root. My memory is failing.
So again maybe we do want a similar workaround in gdm3. But that doesn't
seem to be the root cause of the bug.
** Changed in: gdm3 (Ubuntu)
Status: Invalid => Opinion
** No longer affects: mutter (Ubuntu)
--
You
It appears there's only one caller of this function in gnome-shell:
js/ui/osdMonitorLabeler.js:let monitor =
this._monitorManager.get_monitor_for_connector(connector);
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** Changed in: mutter (Ubuntu)
Tracking in:
https://errors.ubuntu.com/problem/6651d911f833729ccc39cf01ed5e393b95cb0c3f
** Description changed:
+ https://errors.ubuntu.com/problem/6651d911f833729ccc39cf01ed5e393b95cb0c3f
+
gnome shell crashes when I go to Settings -> Devices -> Displays
ProblemType: Crash
I should add that the "fix" I reported is only a narrow fix. The
internal display works. But external displays don't work if you have
nvidia drivers, gdm3 and if you are using modeset=1
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
Compiling gdm3 without wayland isn't a fix. It's a workaround, and kind
of pointless. It's pointless because the most common reason for using
nvidia-drm.modeset=1 is to get Wayland support. I know there are other
reasons for wanting nvidia-drm.modeset=1 such as avoiding tearing in
PRIME setups.
cdebconf-terminal also build-depends on libvte-dev, this should be
resolved first before we do an Ubuntu-specific removal.
** Also affects: cdebconf-terminal (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop
I already did that test ^ using the upstream kernel with 37efe80ce85f
being the HEAD, but "37efe80ce85f" - 1 was working as well, so I didn't
continue to pursue that commit, since it wasn't the first introduction
of the fix.
But based on last duflu update, I as I said I will now give a try again
63 matches
Mail list logo
