After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 597808 - Crash when launching with -e option
Crash when launching with -e option
Status: RESOLVED FIXED
Product: brasero
Classification: Applications
Component: general
2.26.x
Other Linux
: Normal normal
: 2.26
Assigned To: Brasero maintainer(s)
Brasero maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2009-10-08 14:00 UTC by Jérôme
Modified: 2009-10-18 18:33 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Log when launching without option. OK. (50.55 KB, application/octet-stream)
2009-10-08 14:00 UTC, Jérôme
Details
Log when using -e option. KO. (47.63 KB, text/plain)
2009-10-08 14:02 UTC, Jérôme
Details

Description Jérôme 2009-10-08 14:00:28 UTC
Created attachment 145046 [details]
Log when launching without option. OK.

Command "brasero" launches the software.
Command "brasero -e" seems to do nothing (no window appears, nothing in
terminal)

According to brasero --help :
  -e, --empty        Force brasero to display the project selection page

Interestingly, without specifying any option, brasero displays the project
selection page at launch.
Comment 1 Jérôme 2009-10-08 14:02:52 UTC
Created attachment 145049 [details]
Log when using -e option. KO.
Comment 2 Jérôme 2009-10-08 14:03:53 UTC
As far as I understand the logs, they don't provide much relevant information.
Comment 3 Jérôme 2009-10-08 14:04:36 UTC
Version used :
brasero | 2.26.1-0ubuntu1 | http://archive.ubuntu.com jaunty-updates/main Packages
Comment 4 Fabio Durán Verdugo 2009-10-09 14:00:31 UTC
i can confirm in brasero in brasero 2.28.1

I think brasero, should show  the project selection
Aplications Options:
-e, --empty  Force brasero to display the project selection page
Comment 5 Philippe Rouquier 2009-10-18 18:33:18 UTC
Thanks for the report and sorry for the delay.
It turns out it was not a crash but rather the problem was that brasero did not actually start =(, it almost returned immediatly.
I fixed it in master and will backport it in 2.28 series.