Hide Forgot
Description of problem: I have a USB Guitar Link interface: [ 675.762157] usb 4-2: new full-speed USB device number 3 using uhci_hcd [ 675.953352] usb 4-2: New USB device found, idVendor=08bb, idProduct=2902 [ 675.953366] usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 675.953374] usb 4-2: Product: USB Audio CODEC [ 675.953381] usb 4-2: Manufacturer: Burr-Brown from TI [ 675.960276] input: Burr-Brown from TI USB Audio CODEC as /devices/pci0000:00/0000:00:1a.1/usb4/4-2/4-2:1.3/input/input22 [ 675.960398] hid-generic 0003:08BB:2902.0001: input,hidraw0: USB HID v1.00 Device [Burr-Brown from TI USB Audio CODEC ] on usb-0000:00:1a.1-2/input3 [ 676.098682] usbcore: registered new interface driver snd-usb-audio I set up JACK to use the input of the GuitarLink for recording and to use the notebook's internal soundcard for output. I saved these settings in qjackctl. I then started Ardour3 and went through the initial setup, which asked me to select a sound device - I selected the GuitarLink. This stepped somehow reconfigured my JACK session, although qjackctl setup still had my original input/output settings, the routing only presented me with the guitar link inputs and outputs. I then stopped JACK, quit qjackctl and disconnected the GuitarLink USB card from my notebook. I then again started qjackctl - and this is where the coredump happened. I believe qjackctl is trying to use the saved session which is based on hardware that is no longer available (because I disconnected it). Version-Release number of selected component: qjackctl-0.3.10-2.fc20 Additional info: reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: qjackctl crash_function: __cxxabiv1::__gxx_personality_v0 executable: /usr/bin/qjackctl kernel: 3.12.5-302.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #5 __cxxabiv1::__gxx_personality_v0 at ../../../../libstdc++-v3/libsupc++/eh_personality.cc:664 #6 _Unwind_ForcedUnwind_Phase2 at ../../../libgcc/unwind.inc:175 #7 _Unwind_ForcedUnwind at ../../../libgcc/unwind.inc:207 #8 __pthread_unwind at unwind.c:129 #9 __do_cancel at ../nptl/pthreadP.h:280 #10 sigcancel_handler at nptl-init.c:214 #12 strchrnul at ../sysdeps/x86_64/strchrnul.S:34 #13 __find_specmb at printf-parse.h:108 #14 _IO_vfprintf_internal at vfprintf.c:1308 #15 _IO_vsnprintf at vsnprintf.c:119
Created attachment 840192 [details] File: backtrace
Created attachment 840193 [details] File: cgroup
Created attachment 840194 [details] File: core_backtrace
Created attachment 840195 [details] File: dso_list
Created attachment 840196 [details] File: environ
Created attachment 840197 [details] File: limits
Created attachment 840198 [details] File: maps
Created attachment 840199 [details] File: open_fds
Created attachment 840200 [details] File: proc_pid_status
Created attachment 840201 [details] File: var_log_messages
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 '20'. 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 20 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.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.