Response from Gnome:
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/542#note_519114
** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/issues #542
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/542
--
You received this bug notification because you are a
The runtime are for snaps righT? You might be able to uninstall 3.26
(unless you have snaps still using it)
You might want to report the segfault upstream, they might have a better idea
since they write the code
https://gitlab.gnome.org/GNOME/gnome-control-center/issues
--
You received this
Thanks a lot for your time, sorry I couldnt provide you with more
information. Btw is it normal that i have two different gnome runtimes
installed? I see versions 3.26 and 3.28. 3.28 is running
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Thanks for all the details, marking is unconfirmed, unsure what's going
on there but maybe someone else an idea...
** Changed in: gnome-control-center (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Drive(0): Micron 1100 SATA 256GB
Type: GProxyDrive (GProxyVolumeMonitorUDisks2)
ids:
unix-device: '/dev/sda'
themed icons: [drive-harddisk-solidstate] [drive-harddisk] [drive]
[drive-harddisk-solidstate-symbolic] [drive-harddisk-symbolic]
[drive-symbolic]
symbolic themed icons:
Weird, that looks like https://gitlab.gnome.org/GNOME/gnome-control-
center/issues/285 but that one was fixed and shouldn't impact the glib
version installed :/(
Could you give the output of "gio mount -li" and attach the "journalctl
-b 0" log from a session after triggering the issue?
** Bug
** Attachment added: "ldd.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1830223/+attachment/5266260/+files/ldd.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
** Attachment added: "dpkg.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1830223/+attachment/5266261/+files/dpkg.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
I have also sent the apport output in a previous attachment
On Fri, May 24, 2019, 2:05 PM Sebastien Bacher
wrote:
> it would have been better to user apport to open the bug ...
>
> anyway, can you provide those info manually since you didn't use the
> reporting tool
> $ which
it would have been better to user apport to open the bug ...
anyway, can you provide those info manually since you didn't use the reporting
tool
$ which gnome-control-cenhter
$ ldd -r /usr/bin/gnome-control-center
$ dpkg -l | grep libglib
--
You received this bug notification because you are a
Don't know if this is done correctly
** Attachment added: "Stack Trace from apport-retrace"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1830223/+attachment/5266191/+files/gnome_error.txt
--
You received this bug notification because you are a member of Ubuntu
** Attachment added: "gdb backtrace"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1830223/+attachment/5266192/+files/gdb_bt.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a backtrace following the
instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload
the backtrace (as an attachment) to the bug report. This will greatly
help us in tracking down
13 matches
Mail list logo
