Hello All,
I recently noticed a systematic bug on my openSUSE_Leap_42.3, that seems to me easy to fix for the specialists. I mounted a partition and opened a 'pdf' file belonging to this partition in a Konqueror window, and then I recorded the KDE3 session. When I reopen the session while the previously mentioned partion is not mounted, Konqueror systematically crashes.
I am writing this email for all purposes. But I do not wish an answer. Thank you for your attention.
Patrick
On 06/08/2019 08:44 PM, Patrick Serru wrote:
Hello All, I recently noticed a systematic bug on my openSUSE_Leap_42.3, that seemsto me easy to fix for the specialists. I mounted a partition and opened a 'pdf' file belonging to this partition in a Konqueror window, and then I recorded the KDE3 session. When I reopen the session while the previously mentioned partion is not mounted, Konqueror systematically crashes.
I am writing this email for all purposes. But I do not wish an answer.Thank you for your attention.
Patrick
Hi Patrick,
Thanks. I am curios, do you ever remember save/restore session saving active mounts to ksmserverrc? It may have, but I can't ever recall having used it. The reason I'm curios is session manager can restart running applications, etc..., but mount is usually a one-shot call and there is nothing to tell you it is running.
NFS shares are captured in knfsshare, but I don't know where or what would capture active mounts like USB/etc.. konquerorrc captures directory history, etc..., but I don't see an active mounts block.
Let me know if you have more information. I'm happy to look further.
Le dimanche 09 juin 2019, David C. Rankin a écrit :
On 06/08/2019 08:44 PM, Patrick Serru wrote:
Hello All, I recently noticed a systematic bug on my openSUSE_Leap_42.3, thatseems to me easy to fix for the specialists. I mounted a partition and opened a 'pdf' file belonging to this partition in a Konqueror window, and then I recorded the KDE3 session. When I reopen the session while the previously mentioned partion is not mounted, Konqueror systematically crashes.
I am writing this email for all purposes. But I do not wish ananswer. Thank you for your attention.
Patrick
Hi Patrick,
Thanks. I am curios, do you ever remember save/restore session saving active mounts to ksmserverrc? It may have, but I can't ever recall having used it. The reason I'm curios is session manager can restart running applications, etc..., but mount is usually a one-shot call and there is nothing to tell you it is running.
NFS shares are captured in knfsshare, but I don't know where or what would capture active mounts like USB/etc.. konquerorrc captures directory history, etc..., but I don't see an active mounts block.
Let me know if you have more information. I'm happy to look further.
-- David C. Rankin, J.D.,P.E.
------------------------- Hello David,
I dont understand your question. But I sould have to give the following details :
The first dialog open, titled "Erreur - Konqueror", says : Impossible d'ouvrir « file:///linux/7-samsung_sav/.../blabla.PDF ». (Unable to open « file:///linux/7-samsung_sav/.../blabla.PDF »")
Then, the apropriate tab of the crash dialog gives information that I join in a separate file (because some lines are very wide).
The first line says in french, something like: "Verification at startup of the system configuration deactivated." I wonder how I could configure KDE3 (or whatever else if KDE3 is not concerned) to star this checking !
Sincerely,
Patrick
On 06/09/2019 10:57 AM, Patrick Serru wrote:
Hello David, I dont understand your question. But I sould have to give the followingdetails :
The first dialog open, titled "Erreur - Konqueror", says :Impossible d'ouvrir « file:///linux/7-samsung_sav/.../blabla.PDF ». (Unable to open « file:///linux/7-samsung_sav/.../blabla.PDF »")
Then, the apropriate tab of the crash dialog gives information that I joinin a separate file (because some lines are very wide).
The first line says in french, something like:"Verification at startup of the system configuration deactivated." I wonder how I could configure KDE3 (or whatever else if KDE3 is not concerned) to star this checking !
OK, now I understand. You mounted a partition, looked at a pdf, then saved the sesson (I guess with the pdf open?) and now when you open konqueror without the partition mounted, it crashes.
Also, when you say "I recorded the KDE3 session.", how exactly did you record it? Saving with session manager? Saving the konqueor profile filemanagement? Or, really recording some animation of what you did on your desktop? (if so -- with what?) If it was saving the konqueror profile, you can probably delete the [History] information from ~/.kde/share/config/konquerorrc
I don't know how much empty space you have on your drive, but it would help if you could load a few -debug packages so a complete backtrace can be captured. For example, everywhere you see '?" in the kcrash backtrace, that is missing information that would come from the -debug files. For example, this information is all missing:
#15 0x000000000040879d in ?? () #16 0x0000000000409371 in ?? () #17 0x000000000040991c in ?? () #18 0x0000000000405cd9 in ?? () #19 0x00007f137e854feb in __libc_start_main () from /lib64/libc.so.6 #20 0x00000000004065c9 in ?? ()
My guess is the installing following -debuginfo packages would probably fill in most of the missing information:
qt3-debuginfo kdebase3-apps-debuginfo kdebase3-debuginfo kdelibs3-debuginfo
The symbol files shouldn't be more than 50M or so, and you can remove them after you capture a clean kcrash backtrace. Let me know if this makes sense and if you can load the packages and try and capture a full backtrace.
Le dimanche 09 juin 2019, David C. Rankin a écrit :
OK, now I understand. You mounted a partition, looked at a pdf, then saved the sesson (I guess with the pdf open?) and now when you open konqueror without the partition mounted, it crashes.
Also, when you say "I recorded the KDE3 session.", how exactly did you record it? Saving with session manager? Saving the konqueor profile filemanagement? Or, really recording some animation of what you did on your desktop? (if so -- with what?) If it was saving the konqueror profile, you can probably delete the [History] information from ~/.kde/share/config/konquerorrc
I don't know how much empty space you have on your drive, but it would help if you could load a few -debug packages so a complete backtrace can be captured. For example, everywhere you see '?" in the kcrash backtrace, that is missing information that would come from the -debug files. For example, this information is all missing:
#15 0x000000000040879d in ?? () #16 0x0000000000409371 in ?? () #17 0x000000000040991c in ?? () #18 0x0000000000405cd9 in ?? () #19 0x00007f137e854feb in __libc_start_main () from /lib64/libc.so.6 #20 0x00000000004065c9 in ?? ()
My guess is the installing following -debuginfo packages would probably fill in most of the missing information:
qt3-debuginfo kdebase3-apps-debuginfo kdebase3-debuginfo kdelibs3-debuginfo
The symbol files shouldn't be more than 50M or so, and you can remove them after you capture a clean kcrash backtrace. Let me know if this makes sense and if you can load the packages and try and capture a full backtrace.
-- David C. Rankin, J.D.,P.E.
-------------------------------------- Yes, this is correct. Of course, I solved the problem just puting a "mount /linux/7-samsung_sav/" in my .profile file.
The partition is the KDE3 partition, the KDE menu is changing when we activate the option like done in the snapshot jointed.
hoping it helps...
Patrick
On 06/09/2019 11:35 PM, Patrick Serru wrote:
Vérification au démarrage de la configuration du système désactivée.
[Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". [KCrash handler] #5 0x00007f58c4e2b687 in QTabBar::currentTab (this=0x1c88140) at ../include/qptrlist.h:111 #6 0x00007f58c4e2e383 in QTabWidget::currentPageIndex (this=this@entry=0x1c85c70) at widgets/qtabwidget.cpp:596 #7 0x00007f58c4e2f4d9 in QTabWidget::currentPage (this=this@entry=0x1c85c70) at widgets/qtabwidget.cpp:577 #8 0x00007f58c0370fb6 in KonqViewManager::loadItem (this=this@entry=0x1950f60, cfg=..., parent=parent@entry=0x1a810e0, name=..., defaultURL=..., openURL=openURL@entry=true, openAfterCurrentPage=openAfterCurrentPage@entry=false) at konqueror/konq_viewmgr.cc:1643 #9 0x00007f58c0370ce3 in KonqViewManager::loadItem (this=this@entry=0x1950f60, cfg=..., parent=0x187c290, name=..., defaultURL=..., openURL=<optimized out>, openAfterCurrentPage=openAfterCurrentPage@entry=false) at konqueror/konq_viewmgr.cc:1615 #10 0x00007f58c03733d4 in KonqViewManager::loadViewProfile (this=0x1950f60, cfg=..., filename=..., forcedURL=..., req=..., resetWindow=resetWindow@entry=false, openURL=openURL@entry=true) at konqueror/konq_viewmgr.cc:1212
Yes Patrick, that helps,
It looks like there should be a few additional checks in konqueror/konq_viewmgr.cc that validates whether the name or defaultURL are found and if not handle that rather than triggering a kcrash. This will at least preserve the backtrace for the next time there is a change to look at the code.
(I wouldn't be adverse to setting up a bug-squashing weekend to coordinate with whoever is maintaining and building KDE3 to try and address some of these issues)
Le jeudi 20 juin 2019, David C. Rankin a écrit :
On 06/09/2019 11:35 PM, Patrick Serru wrote:
Vérification au démarrage de la configuration du système désactivée.
[Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". [KCrash handler] #5 0x00007f58c4e2b687 in QTabBar::currentTab (this=0x1c88140) at ../include/qptrlist.h:111 #6 0x00007f58c4e2e383 in QTabWidget::currentPageIndex (this=this@entry=0x1c85c70) at widgets/qtabwidget.cpp:596 #7 0x00007f58c4e2f4d9 in QTabWidget::currentPage (this=this@entry=0x1c85c70) at widgets/qtabwidget.cpp:577 #8 0x00007f58c0370fb6 in KonqViewManager::loadItem (this=this@entry=0x1950f60, cfg=..., parent=parent@entry=0x1a810e0, name=..., defaultURL=..., openURL=openURL@entry=true, openAfterCurrentPage=openAfterCurrentPage@entry=false) at konqueror/konq_viewmgr.cc:1643 #9 0x00007f58c0370ce3 in KonqViewManager::loadItem (this=this@entry=0x1950f60, cfg=..., parent=0x187c290, name=..., defaultURL=..., openURL=<optimized out>, openAfterCurrentPage=openAfterCurrentPage@entry=false) at konqueror/konq_viewmgr.cc:1615 #10 0x00007f58c03733d4 in KonqViewManager::loadViewProfile (this=0x1950f60, cfg=..., filename=..., forcedURL=..., req=..., resetWindow=resetWindow@entry=false, openURL=openURL@entry=true) at konqueror/konq_viewmgr.cc:1212
Yes Patrick, that helps,
It looks like there should be a few additional checks in konqueror/konq_viewmgr.cc that validates whether the name or defaultURL are found and if not handle that rather than triggering a kcrash. This will at least preserve the backtrace for the next time there is a change to look at the code.
(I wouldn't be adverse to setting up a bug-squashing weekend to coordinate with whoever is maintaining and building KDE3 to try and address some of these issues)
-- David C. Rankin, J.D.,P.E.
-------------------------- Hello All, hello DAvid,
This is good news.
I know another bug that should be easy to fix, I believe. it always triggers on my OpenSUSE Leap 42.3 (+ KDE3). When Konsole is open (and has been used), Ctrl + Q freezes Konsole, which stops responding, and closing the window specifies that by proposing to kill the process. I admit that I like this bug, because in this case, $HOME/.bash_history is not updated.
Thank you for helping KDE3 to continue living.
Sincerely,
Patrick Serru
-
David C. Rankin -
Patrick Serru