Bug 272092 - Kamoso crashes when starting with 'ASSERT: "ptr.m_class"'
Summary: Kamoso crashes when starting with 'ASSERT: "ptr.m_class"'
Status: RESOLVED WORKSFORME
Alias: None
Product: kamoso
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR crash
Target Milestone: ---
Assignee: Alex Fiestas
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2011-04-30 21:22 UTC by acidrums4
Modified: 2018-10-27 03:34 UTC (History)
1 user (show)

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


Attachments
strace, drkonqi output (251.99 KB, application/x-bzip2)
2011-08-24 00:11 UTC, Tamás Gere
Details

Note You need to log in before you can comment on or make changes to this bug.
Description acidrums4 2011-04-30 21:22:12 UTC
Version:           unspecified (using KDE 4.6.2) 
OS:                Linux

Every time I try to run Kamoso, it crashes. I get the following:

% kamoso
ASSERT: "ptr.m_class" in file /var/tmp/portage/media-sound/qt-gstreamer-0.10.1/work/qt-gstreamer-0.10.1/src/QGst/Ui/../../QGlib/refpointer.h, line 332
KCrash: Application 'kamoso' crashing...
KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit
sock_file=/home/mp/.kde4/socket-localhost/kdeinit4__0
QSocketNotifier: Invalid socket 13 and type 'Read', disabling...
zsh: suspended (signal)  kamoso
[1]  + exit 253   kamoso
%

I’m using Qt-Gstreamer-0.10.0 and Kamoso from Git. Both of them are installed with Portage. I tried installing Qt-Gstreamer from Git but I get the same problem (only changes the location from 'refpointer.h' to the location where I fetched Qt-Gstreamer).

Maybe is a problem related to Qt-Gstreamer; I think that by reading the output. Also, googling around, I only could found this pastebin text with a similar crash (related with an unknow app): http://pastebin.com/cw1EjzUC.

Reproducible: Always

Steps to Reproduce:
1. Try to execute Kamoso from CLI.

Actual Results:  
Kamoso crashes with exit 253.

Expected Results:  
Kamoso would start and work correctly.

Don't know if relevant, but my phonon backend is Gstreamer. My camera is configured to work with the UVC modules from kernel; it works well with Kopete, VLC, gstreamer (gst-launch) and ffmpeg.
Comment 1 Alex Fiestas 2011-05-29 21:34:55 UTC
Hi, can you try to reproduce this bug with Kamoso 2.X ?

Thanks!
Comment 2 acidrums4 2011-05-29 22:07:54 UTC
I've just compiled 'kamoso-2.0-beta1' (but when adding '-v' to CLI, says that it's version is 1.90) but I get the same result.
Comment 3 Alex Fiestas 2011-05-29 22:10:19 UTC
You should try Kamoso 2.0.2 (or the last code from the 2.0 branch), thanks.
Comment 4 acidrums4 2011-05-29 22:42:44 UTC
I've tried with 2.0.1 from ftp://ftp.kde.org/pub/kde/stable/kamoso/2.0.1/src/ (I cannot found 2.0.2), but I got the same.
Comment 5 acidrums4 2011-06-04 14:10:50 UTC
Today I've tried with the 2.0.2 version (Velazquez). I got the same issue...
Comment 6 Tamás Gere 2011-08-24 00:11:45 UTC
Created attachment 63082 [details]
strace, drkonqi output
Comment 7 Tamás Gere 2011-08-24 00:12:00 UTC
Hi!

I got same problem. Same result on my home computer and desktop at my workplace. 
Different hardware, but quite similar setup: amd64 gentoo, with lastest stuff: 4.7 kde, qt 4.7, gstreamer 0.10.35, qt-gstreamer 0.10.1, however I'm pulling git vers, compile and try since like 6 months, but no success. Before this half year, I got working kamoso, version 1 and 2 too. But something went wrong, I don't know what, now I can't run any version.

I can attach strace (with some bizarre result) and konqui output.
Comment 8 Tamás Gere 2011-08-24 00:17:00 UTC
Ah, forgot to say: application starts and working without error if no camera plugged in.
Comment 9 acidrums4 2011-12-27 22:35:01 UTC
I'd just emerged Kamoso again (with Qt-Gstreamer-0.10.1 from Portage, and Kamoso-git from Portage. Finally it runs (and finally I know Kamoso), but it doesn't detect my camera at all (an UVC Microdia Sonix USB 2.0 Camera).
Comment 10 Tamás Gere 2012-01-02 17:02:07 UTC
Kamoso always run, once I remove kernel module. So no change atm.
Comment 11 Alex Fiestas 2013-02-24 13:56:36 UTC
Sorry for the late late reply, we haven't manage to invest too much time in Kamoso during the last year but that is now changing :)

Are you still able to reproduce the crash? if so, can you enable all output in "kdebugdialog" and execute it in a terminal to attach the output here?

Thanks !
Comment 12 Andrew Crouthamel 2018-09-24 02:09:38 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 13 Andrew Crouthamel 2018-10-27 03:34:25 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!