Bug 330782 - Mixer crashed after selecting "Ausdio-Einrichtung" in "Einstellungen"
Summary: Mixer crashed after selecting "Ausdio-Einrichtung" in "Einstellungen"
Status: RESOLVED WORKSFORME
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_phonon (show other bugs)
Version: 4.12.1
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Harald Sitter
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2014-02-05 07:43 UTC by GS
Modified: 2015-09-28 08:37 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description GS 2014-02-05 07:43:49 UTC
Application: kcmshell4 (4.12.1)
KDE Platform Version: 4.12.1
Qt Version: 4.8.5
Operating System: Linux 3.11.6-4-pae i686
Distribution: "openSUSE 13.1 (Bottle) (i586)"

-- Information about the crash:
- What I was doing when the application crashed:
Testing Skpe. The microphone didn't work. So I tried to start pavucontrol, which didn't start at all. After that I opened the KMix with the result of the crash mentionned above.

- Unusual behavior I noticed:
pavucontrol is installed, but cannot be started.

-- Backtrace:
Application: KDE-Kontrollmodul (kcmshell4), signal: Segmentation fault
Using host libthread_db library "/lib/libthread_db.so.1".
[KCrash Handler]
#6  0xb7650fe6 in __strlen_sse2_bsf () from /lib/libc.so.6
#7  0xb6bf80b8 in qstrlen (str=0x1 <Address 0x1 out of bounds>) at ../../src/corelib/tools/qbytearray.h:80
#8  QString::fromUtf8 (str=0x1 <Address 0x1 out of bounds>, size=-1) at tools/qstring.cpp:4018
#9  0xb1dea974 in ?? () from /usr/lib/kde4/kcm_phonon.so
#10 0xb1deb562 in ?? () from /usr/lib/kde4/kcm_phonon.so
#11 0xb1d0ae9b in context_get_card_info_callback (pd=pd@entry=0x8507ef8, command=command@entry=2, tag=tag@entry=3, t=t@entry=0x81ec7f0, userdata=userdata@entry=0x81ec0f0) at pulse/introspect.c:943
#12 0xb1c94de3 in run_action (pd=0x8507ef8, r=0x8587390, command=2, ts=0x81ec7f0) at pulsecore/pdispatch.c:279
#13 0xb1c951e8 in pa_pdispatch_run (pd=0x8507ef8, packet=packet@entry=0x85d0490, creds=creds@entry=0x83a37a8, userdata=userdata@entry=0x851cfe8) at pulsecore/pdispatch.c:331
#14 0xb1cfd924 in pstream_packet_callback (p=p@entry=0x83a3600, packet=0x85d0490, creds=0x83a37a8, userdata=0x851cfe8) at pulse/context.c:335
#15 0xb1c99cb9 in do_read (p=0x83a3600) at pulsecore/pstream.c:830
#16 do_pstream_read_write (p=0x83a3600) at pulsecore/pstream.c:185
#17 0xb1c84a7f in callback (m=0x858bccc, e=0x83a37c0, fd=11, f=PA_IO_EVENT_INPUT, userdata=0x83a7440) at pulsecore/iochannel.c:160
#18 0xb1cebaf7 in dispatch_func (source=0x858bc98, callback=0x0, userdata=0x0) at pulse/glib-mainloop.c:584
#19 0xb592e7de in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#20 0xb592eb88 in ?? () from /usr/lib/libglib-2.0.so.0
#21 0xb592ec48 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#22 0xb6cec5ef in QEventDispatcherGlib::processEvents (this=this@entry=0x818c5d0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#23 0xb627651e in QGuiEventDispatcherGlib::processEvents (this=0x818c5d0, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#24 0xb6cbba03 in QEventLoop::processEvents (this=this@entry=0xbfde1cf8, flags=...) at kernel/qeventloop.cpp:149
#25 0xb6cbbd29 in QEventLoop::exec (this=this@entry=0xbfde1cf8, flags=...) at kernel/qeventloop.cpp:204
#26 0xb66f75d1 in QDialog::exec (this=0x83082e0) at dialogs/qdialog.cpp:562
#27 0xb7784ff9 in kdemain () from /usr/lib/libkdeinit4_kcmshell4.so
#28 0x080485bb in ?? ()
#29 0xb75e69d3 in __libc_start_main () from /lib/libc.so.6
#30 0x080485de in _start ()

The reporter indicates this bug may be a duplicate of or related to bug 326601.

Possible duplicates by query: bug 328384, bug 328344, bug 326601.

Reported using DrKonqi
Comment 1 Albert Astals Cid 2015-09-26 13:42:13 UTC
systemsettings 4 is no longer supported, we do only support version 5

I can not reproduce this crash with the following combinations
  systemsettings 5.4.1 + Qt 5.5.0
  systemsettings 5.3.2 + Qt 5.4.1
Can you still reproduce this hang on version 5?

If you can still reproduce the crash could you please install valgrind and then run
   valgrind systemsettings5
in a terminal, try to reproduce the crash and add here the valgrind output?
Comment 2 GS 2015-09-28 08:31:05 UTC
Sorry, I can't reproduce this error. It seems to have disappeared, since I changed to opsenSuse 13.1 64 Bit.

I suggest to close this item.