Bug 137572 - Assertion "new_prio == -1 || (new_prio >= __sched_fifo_min_prio && new_prio <= __sched_fifo_max_prio)" failed.
Summary: Assertion "new_prio == -1 || (new_prio >= __sched_fifo_min_prio && new_prio <...
Status: RESOLVED WORKSFORME
Alias: None
Product: kfile-plugins
Classification: Applications
Component: pdf (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Albert Astals Cid
URL:
Keywords: investigated, triaged
: 140117 (view as bug list)
Depends on:
Blocks:
 
Reported: 2006-11-19 14:42 UTC by Florian Faber
Modified: 2018-10-27 03:44 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Florian Faber 2006-11-19 14:42:53 UTC
Version:           konqueror 3.5.5 (using KDE KDE 3.5.5)
Installed from:    Unspecified Linux
Compiler:          gcc (GCC) 4.1.1 (Gentoo 4.1.1-r2)
 CFLAGS="-O2 -march=k8 -pipe -ggdb"
OS:                Linux

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 47496202499328 (LWP 12650)]
[KCrash handler]
#5  0x00002b3292264795 in *__GI_raise (sig=<value optimized out>)
    at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#6  0x00002b3292265a2e in *__GI_abort () at abort.c:88
#7  0x00002b329225e136 in *__GI___assert_fail (
    assertion=0x2b32915921d8 "new_prio == -1 || (new_prio >= __sched_fifo_min_prio && new_prio <= __sched_fifo_max_prio)", file=0x2b32915921cc "tpp.c", 
    line=63, function=0x2b32915922b0 "__pthread_tpp_change_priority")
    at assert.c:78
#8  0x00002b3291590a52 in __pthread_tpp_change_priority (previous_prio=-1, 
    new_prio=0) at tpp.c:61
#9  0x00002b329158a408 in __pthread_mutex_lock (mutex=0x3c05af8)
    at pthread_mutex_lock.c:379
#10 0x00002b3297c8e6d0 in GlobalParams::getErrQuiet (this=0x3c059c0)
    at GlobalParams.cc:1667
#11 0x00002b3297c64d15 in error (pos=603690, 
    msg=0x2b3297cfe380 "Illegal character '%c'") at Error.cc:43
#12 0x00002b3297ca8650 in Lexer::getObj (this=0x1c568e0, obj=0x17635c0, 
    objNum=-1) at Lexer.cc:449
#13 0x00002b3297cbc8ef in XRef::readXRef (this=0x3218470, pos=0x7fff1c93e86c)
    at XRef.cc:319
#14 0x00002b3297cbcf8d in XRef (this=0x3218470, strA=<value optimized out>)
    at XRef.cc:235
#15 0x00002b3297cb25f5 in PDFDoc::setup (this=0x4449270, ownerPassword=0x0, 
    userPassword=0x0) at PDFDoc.cc:191
#16 0x00002b3297cb2867 in PDFDoc (this=0x4449270, 
    fileNameA=<value optimized out>, ownerPassword=0x0, userPassword=0x0, 
    guiDataA=<value optimized out>) at PDFDoc.cc:104
#17 0x00002b3297adc878 in Poppler::Document::load (
    filePath=<value optimized out>) at poppler-private.h:62
#18 0x00002b32979d24ac in KPdfPlugin::readInfo (this=0x4234eb0, 
    info=@0x7fff1c93ed50) at kfile_pdf.cpp:62
#19 0x00002b328e64844e in KFileMetaInfo::init (this=0x7fff1c93ee30, 
    url=@0x7fff1c93ede0, mimeType=<value optimized out>, what=1)
    at kfilemetainfo.cpp:334
#20 0x00002b328e6485f0 in KFileItem::metaInfo (this=<value optimized out>, 
    autoget=<value optimized out>) at kfileitem.cpp:1042
#21 0x00002b328e64882c in KFileItem::getToolTipText (this=0x3ee59b0, 
    maxcount=6) at kfileitem.cpp:755
#22 0x00002b32924c80ae in KonqFileTip::showTip (this=0x2c59220)
    at konq_filetip.cc:232
#23 0x00002b32924c8201 in KonqFileTip::qt_invoke (this=0x2c59220, _id=48, 
    _o=0x7fff1c93f480) at konq_filetip.moc:97
#24 0x00002b328fd6b9ac in QObject::activate_signal (this=0x442c8f0, 
    clist=<value optimized out>, o=0x7fff1c93f480) at kernel/qobject.cpp:2356
#25 0x00002b328fd6c653 in QObject::activate_signal (this=0x316a, 
    signal=<value optimized out>) at kernel/qobject.cpp:2325
#26 0x00002b328fd8ac35 in QTimer::event (this=0x442c8f0, e=0x316a)
    at kernel/qtimer.cpp:219
#27 0x00002b328fd15825 in QApplication::internalNotify (
    this=<value optimized out>, receiver=0x442c8f0, e=0x7fff1c93f720)
    at kernel/qapplication.cpp:2635
#28 0x00002b328fd16427 in QApplication::notify (this=0x7fff1c93fa50, 
    receiver=0x442c8f0, e=0x7fff1c93f720) at kernel/qapplication.cpp:2358
#29 0x00002b328f150d2f in KApplication::notify (this=0x7fff1c93fa50, 
    receiver=0x442c8f0, event=0x7fff1c93f720) at kapplication.cpp:550
#30 0x00002b328fd0bf62 in QEventLoop::activateTimers (
    this=<value optimized out>) at kernel/qapplication.h:496
#31 0x00002b328fcccec2 in QEventLoop::processEvents (this=0x5893f0, flags=0)
    at kernel/qeventloop_x11.cpp:389
#32 0x00002b328fd2a002 in QEventLoop::enterLoop (this=0x316a)
    at kernel/qeventloop.cpp:198
#33 0x00002b328fd29eb2 in QEventLoop::exec (this=0x316a)
    at kernel/qeventloop.cpp:145
#34 0x00002b32927d5dce in kdemain (argc=<value optimized out>, 
    argv=<value optimized out>) at konq_main.cc:206
#35 0x0000000000407766 in launch (argc=2, _name=0x546008 "konqueror", 
    args=0x54601a "", cwd=0x0, envc=1, envs=0x54602f "", reset_env=false, 
    tty=0x0, avoid_loops=false, 
    startup_id_str=0x546038 "faberon;1163937207;725611;12165_TIME1070490")
    at kinit.cpp:673
#36 0x00000000004080b2 in handle_launcher_request (sock=9) at kinit.cpp:1240
#37 0x00000000004084b2 in handle_requests (waitForPid=0) at kinit.cpp:1443
#38 0x00000000004094b3 in main (argc=5, argv=0x7fff1c940d18, 
    envp=0x7fff1c940d48) at kinit.cpp:1909
#39 0x00002b3292252374 in __libc_start_main (main=0x408cf0 <main>, argc=5, 
    ubp_av=0x7fff1c940d18, init=<value optimized out>, 
    fini=<value optimized out>, rtld_fini=<value optimized out>, 
    stack_end=0x7fff1c940d08) at libc-start.c:238
#40 0x0000000000404de9 in _start ()
Current language:  auto; currently c


No idea how to reproduce.
Comment 1 Tommi Tervo 2006-12-08 17:58:14 UTC
Adding Rolf to CC field, Pino thinks that this may be kfile_pdf bug.
Comment 2 Albert Astals Cid 2006-12-10 23:42:12 UTC
Pino is as most of the times right, this is a kfile_pdf problem, well, more a poppler bug, but that is almost impossible for the user to know :-D

Florian, this crash most probably happened while using konqueror and hovering the mouse over a pdf file, can you please try to find which file it was and attach the file to this bug report?
Comment 3 Florian Faber 2006-12-11 10:01:02 UTC
Sorry, I really cannot remember which file it was. I will watch for upcoming crashes and send you the file, if it happens again.
Comment 4 Albert Astals Cid 2007-03-15 21:39:11 UTC
*** Bug 140117 has been marked as a duplicate of this bug. ***
Comment 5 Pino Toscano 2007-03-25 23:41:34 UTC
Which kernel version were you using when the crash happened?
Comment 6 Florian Faber 2007-03-26 08:00:39 UTC
2006-11-19.. that could've been 2.6.18-r1 (Gentoo).
Comment 7 Christoph Feck 2011-12-20 02:58:17 UTC
This crash report is at least 4 years old and there were no further comments or status updates since then.

Therefore we believe that this crash is already fixed in KDE 4 or the backtrace is no longer applicable to KDE 4.

If the crash still happens with a recent KDE version (4.7.4 or 4.8), please add an updated backtrace or provide steps to reproduce. For more information, see http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

(To prevent automatic closing of this bug in the future, please set the bug status to ASSIGNED or NEW)
Comment 8 Andrew Crouthamel 2018-09-22 02:09:33 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 9 Andrew Crouthamel 2018-10-27 03:44:10 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!