By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 1476 - [Regression] Cannot use File->Open
Summary: [Regression] Cannot use File->Open
Status: RESOLVED FIXED
Alias: None
Product: TDE
Classification: Unclassified
Component: tdelibs (show other bugs)
Version: R14.0.0 [Trinity]
Hardware: Other Linux
: P1 blocker
Assignee: Timothy Pearson
URL:
Depends on:
Blocks:
 
Reported: 2013-04-22 15:33 CDT by Darrell
Modified: 2013-04-23 14:10 CDT (History)
3 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:

Attachments
Backtrace of kate crash (3.99 KB, application/octet-stream)
2013-04-22 15:33 CDT, Darrell 		Details
Backtrace of kwrite crash (3.97 KB, text/plain)
2013-04-22 15:33 CDT, Darrell 		Details
Backtrace of kompare (5.23 KB, application/octet-stream)
2013-04-22 16:03 CDT, Darrell 		Details
Backtrace of kate after full, clean rebuild of all packages. (3.55 KB, application/octet-stream)
2013-04-22 23:42 CDT, Darrell 		Details
Backtrace of kwrite after full, clean rebuild of all packages. (3.97 KB, application/octet-stream)
2013-04-22 23:42 CDT, Darrell 		Details
Backtrace of kompare after full, clean rebuild of all packages. (5.23 KB, application/octet-stream)
2013-04-22 23:42 CDT, Darrell 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Darrell 2013-04-22 15:33:35 CDT 
Created attachment 1176 [details]
Backtrace of kate crash

When kate or kwrite are opened by selecting a text file in konqueror, the File -> Open menu option causes a crash.

When either text editor is opened outside of selecting a text file, then the crash does not occur.

I'll attach backtraces.
Comment 1 Darrell 2013-04-22 15:33:56 CDT 
Created attachment 1177 [details]
Backtrace of kwrite crash
Comment 2 Darrell 2013-04-22 15:46:03 CDT 
Um, not to belabor the Blocker status, but this bug hurts. This is seriously impacting my use of Trinity. :)
Comment 3 Timothy Pearson 2013-04-22 15:52:02 CDT 
(In reply to comment #2)
> Um, not to belabor the Blocker status, but this bug hurts. This is seriously
> impacting my use of Trinity. :)

This is very odd.  There is a Q_ASSERT(listers) above the crashing code that *should* be fired before the crash can even occur.

What GIT hash did you build tdelibs from?
Comment 4 Darrell 2013-04-22 16:03:28 CDT 
Created attachment 1178 [details]
Backtrace of kompare

Looks like more than kate and kwrite are affected. Attached is a backtrace for kompare.
Comment 5 Darrell 2013-04-22 16:09:30 CDT 
> What GIT hash did you build tdelibs from?
Fairly recent. Just a thought. I rebuilt tdelibs to test the patch for bug report 1364 and I was not having this problem before then. I only rebuilt tdelibs but I recall performing a git pull of tdelibs after my last built run. Today, although I rebuilt tdelibs, I did not rebuild other modules. Wild guess: the dirlister patching requires all other modules to be rebuilt too?

Let me restore to my previous tdelibs so I have some sanity. :) Then I'll run my usual full package set run.

If that makes sense then let's leave this report alone for today until I get the full package set rebuilt.
Comment 6 Timothy Pearson 2013-04-22 16:10:50 CDT 
(In reply to comment #5)
> > What GIT hash did you build tdelibs from?
> Fairly recent. Just a thought. I rebuilt tdelibs to test the patch for bug
> report 1364 and I was not having this problem before then. I only rebuilt
> tdelibs but I recall performing a git pull of tdelibs after my last built run.
> Today, although I rebuilt tdelibs, I did not rebuild other modules. Wild guess:
> the dirlister patching requires all other modules to be rebuilt too?
> 
> Let me restore to my previous tdelibs so I have some sanity. :) Then I'll run
> my usual full package set run.
> 
> If that makes sense then let's leave this report alone for today until I get
> the full package set rebuilt.

Try rebuilding tdelibs from latest GIT, as some patches did go in within the past few days for this type of crash.
Comment 7 Darrell 2013-04-22 16:25:01 CDT 
I just did a git pull of tdelibs. Everything is up to date. I'll perform a full rebuild and see what happens.
Comment 8 Timothy Pearson 2013-04-22 22:43:04 CDT 
I can confirm this report, only in my binaries the Q_ASSERT line fires as it is supposed to.  This yields the same result (a crash), but removes some of the mystery. :-)
Comment 9 Darrell 2013-04-22 23:39:55 CDT 
>I can confirm this report
Ok. I just finished a full rebuild of all packages, starting with TQt3, and the crashes still occur. The backtraces look similar to the originals, but I'll post new ones anyway.
Comment 10 Darrell 2013-04-22 23:42:02 CDT 
Created attachment 1180 [details]
Backtrace of kate after full, clean rebuild of all packages.
Comment 11 Darrell 2013-04-22 23:42:25 CDT 
Created attachment 1181 [details]
Backtrace of kwrite after full, clean rebuild of all packages.
Comment 12 Darrell 2013-04-22 23:42:50 CDT 
Created attachment 1182 [details]
Backtrace of kompare after full, clean rebuild of all packages.
Comment 13 Timothy Pearson 2013-04-23 00:16:56 CDT 
This should be resolved in GIT hash 8188a65; if not, please let me know!

I am leaving this report open as I have not tested this patch as thoroughly as I would like.  Please close it if the issue is resolved. :-)

Thanks!
Comment 14 Darrell 2013-04-23 08:57:25 CDT 
Just rebuilt. Thus far all is calm. All three apps that I reported backtraces no longer crash. Let's see how this goes for a bit before closing. :)

Thank you!
Comment 15 Darrell 2013-04-23 14:10:04 CDT 
Been quiet and uneventful all day. No crashes. Tagging as resolved.

Thank you!