Ubuntu
file-roller package

file-roller crashed with signal 5 in g_object_new_valist()

Bug #2025531 reported by Joe Winkler

This bug report was marked for expiration 184 days ago. (find out why)

72
This bug affects 13 people
Affects Status Importance Assigned to Milestone
file-roller (Ubuntu)
Incomplete
High
Unassigned

Bug Description

While edubuntu-mantic parallel installing
kubuntu kde-desktop ubuntucinnamon-desktop:

E: /tmp/apt-dpkg-install-iBrOhl/518-kubuntu-settings-desktop_1%3a23.04.5_all.deb:

»/etc/skel/.face«

tried to override because of

desktop-base 12.0.6ubuntu1

ProblemType: Crash
DistroRelease: Ubuntu 23.10
Package: file-roller 43.0-1
ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
Uname: Linux 6.3.0-7-generic x86_64
ApportVersion: 2.26.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Jul 1 14:35:45 2023
ExecutablePath: /usr/bin/file-roller
InstallationDate: Installed on 2023-07-01 (0 days ago)
InstallationMedia: Edubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230629)
ProcCmdline: /usr/bin/file-roller --service
ProcEnviron:
 LANG=de_DE.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
Signal: 5
SourcePackage: file-roller
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_new_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_new () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: file-roller crashed with signal 5 in g_object_new_valist()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users
separator:

My solution in synaptic was:
uninstall kubuntu-desktop and kubuntu-settings-desktop

See original description
Revision history for this message
Joe Winkler (winjoe) wrote :
Joe Winkler (winjoe)
description: updated
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_settings_set_property (object=0x55584dd22340, prop_id=<optimized out>, value=<optimized out>, pspec=<optimized out>) at ../../../gio/gsettings.c:596
 object_set_property (object=object@entry=0x55584dd22340, pspec=0x55584dd21080, value=0x7ffc7ccfb250, nqueue=nqueue@entry=0x0, user_specified=<optimized out>) at ../../../gobject/gobject.c:1812
 g_object_new_internal (class=class@entry=0x55584dd203a0, params=params@entry=0x7ffc7ccfb150, n_params=n_params@entry=1) at ../../../gobject/gobject.c:2291
 g_object_new_valist (object_type=<optimized out>, first_property_name=first_property_name@entry=0x7f5ce830b23e "schema-id", var_args=var_args@entry=0x7ffc7ccfb420) at ../../../gobject/gobject.c:2585
 g_object_new (object_type=<optimized out>, first_property_name=first_property_name@entry=0x7f5ce830b23e "schema-id") at ../../../gobject/gobject.c:2058

tags: removed: need-amd64-retrace
Joe Winkler (winjoe)
description: updated
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. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:

1. The specific steps or actions you took that caused you to encounter the problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).

Please also ensure that you include the release and flavour of Ubuntu that you are using.

Thank you!

Changed in file-roller (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
information type: Private → Public
Revision history for this message
Scott Kostyshak (scott-kostyshak) wrote :

This just happened to me also, after a fresh install of 23.10 daily. It happened during an install script, and it happened in particular while my install script was installing packages via `sudo apt-get install`. Unfortunately, I cannot reproduce.

Revision history for this message
XA Hydra (xa-hydra) wrote :

Triggered for me in 23.10 during routine system updates

Revision history for this message
Phil Wyett (kathenas) wrote (last edit ):

Triggered for me in 23.10 during routine system updates.

Problem on two 23.10 VMs.

Revision history for this message
BertN45 (lammert-nijhof) wrote :

First it happened after system update of the VBox VM and again after the reboot, just at the moment I wanted to shut down the system. I only did run the following script:

sudo snap refresh
sudo apt autoremove -y
sudo apt autoclean
sudo apt clean
sudo journalctl --vacuum-time=3d
if [ "$1" = "-z" ];
then
  echo "Start Zeroing"
  dd if=/dev/zero of=/home/bertadmin/zeroes
  rm /home/bertadmin/zeroes
else
  echo "No Zeroing"
fi

Sebastien Bacher (seb128)
Changed in file-roller (Ubuntu):
importance: Low → High
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

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