Page MenuHomeSolus
Create Task
Maniphest T7974

gnome-multi-writer segfault
Closed, InvalidPublic
Actions

Description

gnome-multi-writer don't launch after last update

$ gnome-multi-writer

(gnome-multi-writer:1863): GLib-GObject-CRITICAL **: 22:02:48.006: g_object_ref: assertion 'old_val > 0' failed

(gnome-multi-writer:1863): Gmw-CRITICAL **: 22:02:48.006: gmw_device_set_order_process: assertion 'GMW_IS_DEVICE (self)' failed

(gnome-multi-writer:1863): Gmw-CRITICAL **: 22:02:48.006: gmw_device_get_block_path: assertion 'GMW_IS_DEVICE (self)' failed

(gnome-multi-writer:1863): GLib-GObject-CRITICAL **: 22:02:48.006: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Erreur de segmentation

Related Objects

Event Timeline

pizux created this task.May 19 2019, 8:05 PM
Herald added a project: Lacks Project. · View Herald TranscriptMay 19 2019, 8:05 PM
Staudey added a subscriber: Staudey.May 20 2019, 8:59 PM

Oh yeah, interesting. It launches fine when no USB-Stick is inserted. If you try to launch it with one inserted, it crashes with the above error messages. The same thing happens if you plug in a USB stick while the program is running.

Staudey added a comment.May 20 2019, 9:20 PM

Note: This was already reported in T7902 and upstream at https://gitlab.gnome.org/GNOME/gnome-multi-writer/issues/8

JoshStrobl closed this task as Invalid.May 27 2019, 8:29 AM
JoshStrobl added a subscriber: JoshStrobl.

This is fixed in the new GNOME Multi Writer that'll get pushed to unstable today. Either way, was an upstream issue.

Copyright © 2015-2021 Solus Project. The Solus logo is Copyright © 2016-2021 Solus Project. All Rights Reserved.