syndock crashes at the end of session.

[jkogut]

ubuntu: 7.04

Ksynaptics:
Version: 0.3.1-2ubuntu1
Architecture: i386
Maintainer: Ubuntu MOTU Developers <email address hidden>

debug:

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
.
.
.
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1232488752 (LWP 5293)]
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6 0x00000000 in ?? ()
#7 0xb6731772 in SynDock::~SynDock () from /usr/lib/libkdeinit_syndock.so
#8 0xb67335ca in kdemain () from /usr/lib/libkdeinit_syndock.so
#9 0xb6751604 in kdeinitmain () from /usr/lib/kde3/syndock.so
#10 0x0804e6bf in ?? ()
#11 0x00000001 in ?? ()
#12 0x080a32d0 in ?? ()
#13 0x00000001 in ?? ()
#14 0x00000000 in ?? ()

Cheers,
Jan

[Rich Johnson (nixternal)]

confirming due to duplicate report.

[Rich Johnson (nixternal)]

Bug 119644 is a duplicate of this report, however he provides the steps in order to reproduce this bug. It just happened to me as well. Here is the snipped from 119644 so you don't have to click the bug link:
-------------------------
I saw there was a similar bug posted already, but I'm not sure if it's the same, as mine seems definitely related to stand-by/resuming. It does not occur when I kill X with Ctrl + Alt + Backspace or any other way.
I am on a Dell Inspiron 6000 on a fully updated version of Feisty.
Every time I stand-by, the scrolling of my touchpad stops working. Logging out crashes ksynaptics, and when I log back in, ksynaptics tells me "Shared Memory is not accessible, please edit SHMConfig = "On" in Xorg.conf". But, my xorg.conf file hasn't changed, and the SHMConfig = on is already set. Also, if I manually quit ksynaptics, it will also crash. The only way to get it working again is to completely reboot.
This happens to me 100% of the time on stand-by, and essentially makes stand-by useless (because I will just have to reboot to get my touchpad working correctly anyway)
Steps to Reproduce:
 1) Stand-by with ksynaptics running
 2) Resume
 3) Logout or quit ksynaptics
---------------------------

[Rich Johnson (nixternal)]

Actually, I am going to set this to high, as it breaks functions making a user have to reboot in order to regain control leading to possible data loss if application(s) are opened when this occurs.

[Rich Johnson (nixternal)]

KSynaptics in Gutsy doesn't cause this crash...why the version in Gutsy never made it into Feisty is beyond me.

[mpausch (manfred-pausch)]

When I set SHMConfig=On the error does not occur.

I did not try Standby/Resume like described in https://bugs.launchpad.net/ubuntu/+source/ksynaptics/+bug/119644
Probably I try it in the next days.

[Jonathan Thomas (echidnaman)]

Reported fixed in Gutsy, closing since Feisty is no longer supported.