gnome control center segmentation fault when clicking details tab

Bug #1830223 reported by Ioannis Vardas
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-control-center (Ubuntu)
New
Low
Unassigned

Bug Description

Description: Ubuntu 18.04.2 LTS
Release: 18.04
gnome-control-center:
  Installed: 1:3.28.2-0ubuntu0.18.04.4
  Candidate: 1:3.28.2-0ubuntu0.18.04.4
  Version table:
 *** 1:3.28.2-0ubuntu0.18.04.4 500
        500 http://gr.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     1:3.28.1-0ubuntu1 500
        500 http://gr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

When opening the gnome-control-center it may close after some seconds. Additionally, if I open "Details" tab it closes and returns a segmentation fault. I know this issue is not new but I have
experienced it now.

Revision history for this message
Sebastien Bacher (seb128) wrote :

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 your problem.

Changed in gnome-control-center (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Ioannis Vardas (ioannisvardas) wrote :

Don't know if this is done correctly

Revision history for this message
Ioannis Vardas (ioannisvardas) wrote :
Revision history for this message
Sebastien Bacher (seb128) 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 gnome-control-cenhter
$ ldd -r /usr/bin/gnome-control-center
$ dpkg -l | grep libglib

Revision history for this message
Ioannis Vardas (ioannisvardas) wrote : Re: [Bug 1830223] Re: gnome control center segmentation fault when clicking details tab

I have also sent the apport output in a previous attachment

On Fri, May 24, 2019, 2:05 PM Sebastien Bacher <email address hidden> 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 gnome-control-cenhter
> $ ldd -r /usr/bin/gnome-control-center
> $ dpkg -l | grep libglib
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1830223
>
> Title:
> gnome control center segmentation fault when clicking details tab
>
> Status in gnome-control-center package in Ubuntu:
> Incomplete
>
> Bug description:
> Description: Ubuntu 18.04.2 LTS
> Release: 18.04
> gnome-control-center:
> Installed: 1:3.28.2-0ubuntu0.18.04.4
> Candidate: 1:3.28.2-0ubuntu0.18.04.4
> Version table:
> *** 1:3.28.2-0ubuntu0.18.04.4 500
> 500 http://gr.archive.ubuntu.com/ubuntu bionic-updates/main
> amd64 Packages
> 100 /var/lib/dpkg/status
> 1:3.28.1-0ubuntu1 500
> 500 http://gr.archive.ubuntu.com/ubuntu bionic/main amd64
> Packages
>
> When opening the gnome-control-center it may close after some seconds.
> Additionally, if I open "Details" tab it closes and returns a segmentation
> fault. I know this issue is not new but I have
> experienced it now.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1830223/+subscriptions
>

Revision history for this message
Ioannis Vardas (ioannisvardas) wrote :
Revision history for this message
Ioannis Vardas (ioannisvardas) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

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?

Changed in gnome-control-center (Ubuntu):
status: Incomplete → New
status: New → Incomplete
Revision history for this message
Ioannis Vardas (ioannisvardas) wrote :

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: [drive-harddisk-solidstate-symbolic] [drive-harddisk-symbolic] [drive-symbolic] [drive-harddisk-solidstate] [drive-harddisk] [drive]
  is_removable=0
  is_media_removable=0
  has_media=1
  is_media_check_automatic=1
  can_poll_for_media=0
  can_eject=0
  can_start=0
  can_stop=0
  start_stop_type=shutdown
  sort_key=00coldplug/00fixed/sd____a
  Volume(0): 185 GB Volume
    Type: GProxyVolume (GProxyVolumeMonitorUDisks2)
    ids:
     class: 'device'
     unix-device: '/dev/sda4'
     uuid: 'AAF8C0AAF8C0765B'
    uuid=AAF8C0AAF8C0765B
    themed icons: [drive-harddisk-solidstate] [drive-harddisk] [drive] [drive-harddisk-solidstate-symbolic] [drive-harddisk-symbolic] [drive-symbolic]
    symbolic themed icons: [drive-harddisk-solidstate-symbolic] [drive-harddisk-symbolic] [drive-symbolic] [drive-harddisk-solidstate] [drive-harddisk] [drive]
    can_mount=1
    can_eject=0
    should_automount=0
    sort_key=gvfs.time_detected_usec.1558706367193360
Drive(1): HGST HTS721010A9E630
  Type: GProxyDrive (GProxyVolumeMonitorUDisks2)
  ids:
   unix-device: '/dev/sdb'
  themed icons: [drive-harddisk] [drive] [drive-harddisk-symbolic] [drive-symbolic]
  symbolic themed icons: [drive-harddisk-symbolic] [drive-symbolic] [drive-harddisk] [drive]
  is_removable=0
  is_media_removable=0
  has_media=1
  is_media_check_automatic=1
  can_poll_for_media=0
  can_eject=0
  can_start=0
  can_stop=0
  start_stop_type=shutdown
  sort_key=00coldplug/00fixed/sd____b
  Volume(0): Storage
    Type: GProxyVolume (GProxyVolumeMonitorUDisks2)
    ids:
     class: 'device'
     unix-device: '/dev/sdb1'
     uuid: 'bdb1510a-fa72-46fc-a750-d189bfdad213'
     label: 'Storage'
    uuid=bdb1510a-fa72-46fc-a750-d189bfdad213
    themed icons: [drive-harddisk] [drive] [drive-harddisk-symbolic] [drive-symbolic]
    symbolic themed icons: [drive-harddisk-symbolic] [drive-symbolic] [drive-harddisk] [drive]
    can_mount=1
    can_eject=0
    should_automount=0
    sort_key=gvfs.time_detected_usec.1558706367193231
Drive(2): HL-DT-ST DVD+/-RW GU90N
  Type: GProxyDrive (GProxyVolumeMonitorUDisks2)
  ids:
   unix-device: '/dev/sr0'
  themed icons: [drive-optical] [drive] [drive-optical-symbolic] [drive-symbolic]
  symbolic themed icons: [drive-optical-symbolic] [drive-symbolic] [drive-optical] [drive]
  is_removable=1
  is_media_removable=1
  has_media=0
  is_media_check_automatic=1
  can_poll_for_media=0
  can_eject=1
  can_start=0
  can_stop=0
  start_stop_type=shutdown
  sort_key=00coldplug/11removable/sr0

Revision history for this message
Sebastien Bacher (seb128) wrote :

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
Revision history for this message
Ioannis Vardas (ioannisvardas) wrote :

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

Revision history for this message
Sebastien Bacher (seb128) wrote :

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

Revision history for this message
Ioannis Vardas (ioannisvardas) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.