Konsole 1.6.3 in KDE 3.5.3 crashes after zooming text to huge size

Bug #53159 reported by Edmund Laugasson
6
Affects Status Importance Assigned to Milestone
KDE Base
Fix Released
High
kdebase (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: konsole

I reconfigured Konsole 1.6.3 in KDE 3.5.3 and put ALT++ to get text size bigger and ALT+- to get text size smaller.

When I try to zoom text as long as possible by pressing ALT and +, then Konsole just crashes. The crash will appear, when Konsole text cursor does not fit onto terminal window. Then KDE crash handler appears and it says:
Application Konsole crashed due to signal 6 (SIGABRT).

And it also says, that this SIGABRT appears, when application has bug inside it. Also it suggest me to report a bug and this is I'm doing now.
And it also says, that no back trace is not possible .

But when I try to zoom text smaller by pressing ALT and -, then it goes to some fixed small size and then stops - this is expected behaviour and so it should be. This should be also, when zooming text bigger - it should detect window size and stop zooming when it reaches its limits.

Revision history for this message
John Vivirito (gnomefreak) wrote :

Thanks for your bug report. Could you please try to obtain a
backtrace by following the instructions on
       http://wiki.ubuntu.com/DebuggingProgramCrash.
This will greatly aid us in tracking down your problem.

Changed in kdebase:
status: Unconfirmed → Needs Info
Revision history for this message
Ryan Kavanagh (ryanakca) wrote :

Your bug lacks information we would need to investigate further. We
are now going to close the bug - please reopen if you have more
information at hand.

Changed in kdebase:
status: Needs Info → Rejected
Revision history for this message
Edmund Laugasson (ed-lau) wrote :

I don't understand, what information is needed. Try to install Kubuntu 6.06 and latest KDE - you will see yourself. I use Estonian locale.

And I would like to say, that I don't have time to play several days with hunting bugs. It seems like "enterprise ready" Ubuntu 6.06 is a myth... Actually too much critical errors has been appeared in Ubuntu 6.06 in short time... I just don't understand, what's wrong....

But the fact is, that Midnigh Commander is corrupted in latest KDE...

Revision history for this message
John Vivirito (gnomefreak) wrote :

As i asked before can you give us a backtrace? If not please provide us with a strace. We need some info on what caused the crash (not a general cause) But we need this info to investigate further. Thank you for filing this bug.

i changed this back to needs info hoping to retrieve the needed info.

Changed in kdebase:
status: Rejected → Needs Info
Revision history for this message
Rocco Stanzione (trappist) wrote :

I was able to reproduce this bug and get a backtrace in kde-3.5.4 in dapper. Once the font becomes so big that the cursor no longer fits in the konsole window (!!!), enlarge it a few more times and konsole crashes. Not sure this warrants recanting enterprise-ready claims. Anyway here's the backtrace. Maybe it's more useful than it looks to me.

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 46912569803904 (LWP 16311)]
0x00002aaaab245752 in nanosleep () from /lib/libc.so.6
#0 0x00002aaaab245752 in nanosleep () from /lib/libc.so.6
#1 0x00002aaaab2455f0 in sleep () from /lib/libc.so.6
#2 0x00002aaaaba1197d in KCrash::startDrKonqi (argv=0x7fffffb27a10, argc=18)
    at kcrash.cpp:311
#3 0x00002aaaaba387d5 in KCrash::defaultCrashHandler (
    sig=<value optimized out>) at kcrash.cpp:228
#4 0x00002aaaab1e41b0 in killpg () from /lib/libc.so.6
#5 0x0000000000000000 in ?? ()

Changed in kdebase:
status: Needs Info → Confirmed
Revision history for this message
John Vivirito (gnomefreak) wrote :

Is this an issue in a fully updated system?

Revision history for this message
Yuriy Kozlov (yuriy-kozlov) wrote :

Confirmed on Feisty.

Changed in kdebase:
status: Unknown → Unconfirmed
Changed in kdebase:
status: Unconfirmed → Fix Released
Revision history for this message
Yuriy Kozlov (yuriy-kozlov) wrote :

A fix has been committed upstream, so this should be fixed in the next version of KDE.

Changed in kdebase:
status: Confirmed → Fix Committed
Revision history for this message
Yuriy Kozlov (yuriy-kozlov) wrote :

This problem is still present in KDE 3.5.6

Changed in kdebase:
status: Fix Released → In Progress
Changed in kdebase:
status: In Progress → Fix Released
Revision history for this message
Sarah Kowalik (hobbsee-deactivatedaccount) wrote :

Seems fixed in 3.5.7. Please reopen this bug if you find it still occurs.

Changed in kdebase:
status: Fix Committed → Fix Released
Changed in kdebase:
importance: Unknown → High
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.