Bug 1349346 - Crashes after iso image selected
Summary: Crashes after iso image selected
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: k3b
Version: 23
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: KDE SIG
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-06-23 09:43 UTC by Dave P
Modified: 2016-12-20 21:05 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-12-20 21:05:35 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Dave P 2016-06-23 09:43:37 UTC
Description of problem: Trying to burn F24 image. 


Version-Release number of selected component (if applicable):


How reproducible: Try to burn net-install version of current F24 ISO image


Steps to Reproduce:
1. Open app
2. Select ISO image on disk
3. Select 'OK'

Crashes

Actual results:

$ k3b
[dpawson@localhost fedora]$ k3b(11657)/kdeui (kdelibs): Attempt to use QAction "view_projects" with KXMLGUIFactory! 
k3b(11657)/kdeui (kdelibs): Attempt to use QAction "view_dir_tree" with KXMLGUIFactory! 
k3b(11657)/kdeui (kdelibs): Attempt to use QAction "view_contents" with KXMLGUIFactory! 
k3b(11657)/kdeui (kdelibs): Attempt to use QAction "location_bar" with KXMLGUIFactory! 
k3b(11657) KSambaSharePrivate::testparmParamValue: We got some errors while running testparm "Load smb config files from /etc/samba/smb.conf
Loaded services file OK.
ERROR: lock directory /var/lib/samba/lock does not exist

" 
loaded the Generic plugin 
KCrash: Application 'k3b' crashing...
KCrash: Attempting to start  from kdeinit
KCrash: Connect sock_file=/home/dpawson/.kde/socket-localhost.localdomain/kdeinit4__1
KCrash: Attempting to start  directly
KCrash failed to exec(), errno = 2




Expected results: Continue with burn


Additional info: I do not have the MP3 plugins present.

Comment 1 Milan Kerslager 2016-08-11 20:10:07 UTC
This F23 bug is probably related to F24 bug #1348795.

Comment 2 Fedora Admin XMLRPC Client 2016-11-22 14:28:23 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 3 Fedora End Of Life 2016-11-25 09:21:51 UTC
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Fedora End Of Life 2016-12-20 21:05:35 UTC
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.