[kamoso] [Bug 356133] crash when starting - segmentation fault

[Lisa via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356133

--- Comment #15 from Lisa  ---
Created attachment 99372
  --> https://bugs.kde.org/attachment.cgi?id=99372=edit
Shutting down gracefully at startup in case of missing plugin.

As promised, a patch for improved error handling. Let me know about it :)

-- 
You are receiving this mail because:
You are watching all bug changes.

[kamoso] [Bug 356133] crash when starting - segmentation fault

[Lisa via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356133

--- Comment #14 from Lisa  ---
On Chakra, the bad plugins for gstreamer1.0 are also in their own package; once
installed that, kamoso starts up without issues.

I have added the gst-plugins-bad package as a dependency of kamoso, other
packagers should do the same for their distros (e.g. Archlinux).

Error handling inside kamoso could be improved, if there are no objections I'll
send a patch for that later on.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kamoso] [Bug 356133] crash when starting - segmentation fault

[Lisa via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356133

--- Comment #13 from Lisa  ---
Regarding my comment "but I still cannot get kamoso to find it, i.e.
QGst::ElementFactory::find fails too, not just ::make.", that is because on
Chakra kamoso uses gstreamer-1.0 and not gstreamer-0.10. 

For some reason gstreamer-1.0 does not have the plugin on my system (as shown
by gst-inspect-1.0).

-- 
You are receiving this mail because:
You are watching all bug changes.

[kamoso] [Bug 356133] crash when starting - segmentation fault

[Lisa via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356133

--- Comment #12 from Lisa  ---
More information: the crash is caused by the fact that the element factory
"wrappercamerabinsrc" does not exist on the system, therefore a null element is
returned.

This should be part of gstreamer-bad-plugins. Before installing the bad plugins
I run "gst-inspect-0.10 | grep camera" and got an empty output. After
installing them, I get this:

camerabin2:  camerabin2: CameraBin2
camerabin2:  wrappercamerabinsrc: V4l2 camera src element for camerabin
camerabin2:  viewfinderbin: Viewfinder Bin
bayer:  bayer2rgb: Bayer to RGB decoder for cameras
camerabin:  camerabin: Camera Bin

but I still cannot get kamoso to find it, i.e. QGst::ElementFactory::find fails
too, not just ::make.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kamoso] [Bug 356133] crash when starting - segmentation fault

[Lisa via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=356133

Lisa  changed:

   What|Removed |Added

 CC||syn.shai...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

[konversation] [Bug 360490] Crash after closing "DCC status" tab

[Lisa via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360490

--- Comment #3 from Lisa  ---
The discrepancy originates at one of the calls to removeTab (likely the one
inside closeDccPanel) and m_popupViewIndex is never updated, so it becomes out
of bounds.

I attached a patch that works both as a quick fix for this crash and as a "safe
default" in the general case: canMoveView{Left,Right} detect the invalid
pointer and return "false", causing the view to shift to the first tab in the
list rather than to the adjacent one. A minor annoyance compared to the crash.

It is not the "proper" fix to this issue though, so I'll leave to the owners
the decision on what to do with it.

-- 
You are receiving this mail because:
You are watching all bug changes.

[konversation] [Bug 360490] Crash after closing "DCC status" tab

[Lisa via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360490

--- Comment #2 from Lisa  ---
Created attachment 98777
  --> https://bugs.kde.org/attachment.cgi?id=98777=edit
Quick patch to circumvent crashes

-- 
You are receiving this mail because:
You are watching all bug changes.

[knemo] [Bug 360582] New: Version 0.7.7 crashes at startup with wireless_tools 30.pre9

[Lisa via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360582

Bug ID: 360582
   Summary: Version 0.7.7 crashes at startup with wireless_tools
30.pre9
   Product: knemo
   Version: unspecified
  Platform: Chakra
OS: Linux
Status: UNCONFIRMED
  Severity: minor
  Priority: NOR
 Component: general
  Assignee: jst...@mehercule.net
  Reporter: syn.shai...@gmail.com

knemo depends on wireless_tools for some shared libraries.

If built against wireless_tools v29, it works without issues.
If built against wireless_tools v30.pre9, it segfaults at startup.

Reproducible: Always

Steps to Reproduce:
1. Install wireless_tools v30-pre9
2. Launch knemo from a terminal

Actual Results:  
Segmentation fault (core dumped).

Expected Results:  
The program is launched as usual.

I have run the broken knemo with gdb:

(gdb) run
Starting program: /usr/bin/knemo 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
0x71605a45 in QMetaObject::className() const () from
/usr/lib/libQt5Core.so.5

-- 
You are receiving this mail because:
You are watching all bug changes.

[konversation] [Bug 360490] New: Crash after closing "DCC status" tab

[Lisa via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360490

Bug ID: 360490
   Summary: Crash after closing "DCC status" tab
   Product: konversation
   Version: 1.6
  Platform: Chakra
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: dcc
  Assignee: b.buschin...@googlemail.com
  Reporter: syn.shai...@gmail.com
CC: konversation-de...@kde.org

To reproduce, send a file to a user. A new "DCC status" tab will open with the
related information. If you right click on the tab and click Close,
konversation segfaults. The regular log only shows a description of the content
of the tab and then Segmentation fault.

The tab itself works fine, this happens regardless of other operations I do
there (e.g. aborting a send).

Reproducible: Always

Steps to Reproduce:
1. Send a file to a user.
2. Close the "DCC status" tab.

Actual Results:  
Segmentation fault.

Expected Results:  
The tab closes and konversation keeps going.

-- 
You are receiving this mail because:
You are watching all bug changes.