Bug 128246 - kate crashes and doesn't save modifications on file.
Summary: kate crashes and doesn't save modifications on file.
Status: RESOLVED DUPLICATE of bug 119435
Alias: None
Product: kate
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR crash
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-05-29 15:33 UTC by Pierre Habouzit
Modified: 2006-06-02 03:04 UTC (History)
0 users

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

Attachments
crash backtrace (5.80 KB, text/plain)
2006-05-29 15:34 UTC, Pierre Habouzit 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Pierre Habouzit 2006-05-29 15:33:55 UTC 
Version:            (using KDE KDE 3.5.2)
Installed from:    Debian testing/unstable Packages

From debian bug http://bugs.debian.org/368504
=============================================

Kate sometimes crashes when the user clicks on 'save'. his exact report is:

| I opened a file. Used the collapsable markers. Then I opened a new
| window with the same file. I edited this latter and when I wanted to
| save I got the attached backtrace and a progress floating window
| indicating the source and the destination writing. But it never disappeared.
| I had to press "Cancel", but the changes weren't saved.

another user claimed to have such problems also.

attached a backtrace
Comment 1 Pierre Habouzit 2006-05-29 15:34:59 UTC 
Created attachment 16329 [details]
crash backtrace
Comment 2 Raúl 2006-05-29 15:44:56 UTC 
As I reported into debian BTS, the problem happens either in kate and kwrite. Even in a quite simple edition. 
Versions:
kwrite 4.5.2 in kde 3.5.2.
kate 2.5.2 on kde 3.5.2
Comment 3 Raúl 2006-05-29 15:53:57 UTC 
I'm sorry but this seems a duplicate of #119435.
Comment 4 Dominik Haumann 2006-05-29 17:04:12 UTC 
Yup, duplicate of bug #119435, backtraces are the same (ignoring parameters).

Strange part in this backtrace is:

#35 0xa7ad1529 in KAccelPrivate::menuItemActivated (this=0x0)
    at kaccelprivate.moc:110

*** This bug has been marked as a duplicate of 119435 ***
Comment 5 Hamish Rodda 2006-06-02 03:04:11 UTC 
A valgrind log of this crash might tell us more why there are some null "this" objects when signals are being emitted (inside moc)