[konqueror] [Bug 487952] Konqueror crashes on session restore
https://bugs.kde.org/show_bug.cgi?id=487952 --- Comment #1 from Kevin Wolf --- Created attachment 170081 --> https://bugs.kde.org/attachment.cgi?id=170081=edit New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace. -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 487952] New: Konqueror crashes on session restore
https://bugs.kde.org/show_bug.cgi?id=487952 Bug ID: 487952 Summary: Konqueror crashes on session restore Classification: Applications Product: konqueror Version: 24.02.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konq-b...@kde.org Reporter: kw...@redhat.com Target Milestone: --- Application: konqueror (24.02.2) Qt Version: 6.7.1 Frameworks Version: 6.2.0 Operating System: Linux 6.8.10-300.fc40.x86_64 x86_64 Windowing System: X11 Distribution: "Fedora Linux 40 (Forty)" DrKonqi: 6.0.5 [CoredumpBackend] -- Information about the crash: I configured KDE so that when I log in it should restore all applications that were running on the last logout. Since I upgraded to Fedora 40 (and reverted to X11 to have session restore working at all), every time I have Konqueror running when logging out, it is restarted after login and then crashes immediately, presumably while trying to restore the state of the open tabs (something like between one and three tabs). The crash can be reproduced every time. -- Backtrace (Reduced): #5 QString::compare (cs=Qt::CaseSensitive, this=0x7f006373696d, s=...) at /usr/include/qt6/QtCore/qstring.h:1444 #6 compareEntryKeyViews (k1=..., k2=...) at /usr/src/debug/kf6-kconfig-6.2.0-1.fc40.x86_64/src/core/kconfigdata_p.h:196 #7 operator< (k1=..., k2=...) at /usr/src/debug/kf6-kconfig-6.2.0-1.fc40.x86_64/src/core/kconfigdata_p.h:219 #8 KEntryKeyCompare::operator() (this=0x7f0918004050, k1=..., k2=...) at /usr/src/debug/kf6-kconfig-6.2.0-1.fc40.x86_64/src/core/kconfigdata_p.h:243 #9 std::_Rb_tree, std::_Select1st >, KEntryKeyCompare, std::allocator > >::_M_lower_bound_tr (this=0x7f0918004050, __k=...) at /usr/include/c++/14/bits/stl_tree.h:1334 Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 462270] Neochat forgets connected accounts, starts with infinite loading screen and crashes when trying to log into an account
https://bugs.kde.org/show_bug.cgi?id=462270 --- Comment #10 from Kevin Wolf --- I don't think my report was a full duplicate, actually. What would seem to make sense to me is keeping this one for accounts being deleted after any failure to connect to them, because that's what both of our cases seem to have in common. And then reopen mine for handling unreachable servers better, so that NeoChat doesn't hang in the loading screen or crash later just because one of multiple accounts can't connect. -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 467649] New: Highlighting NeoChat window in taskbar on notification doesn't work
https://bugs.kde.org/show_bug.cgi?id=467649 Bug ID: 467649 Summary: Highlighting NeoChat window in taskbar on notification doesn't work Classification: Applications Product: NeoChat Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: kw...@redhat.com CC: c...@carlschwan.eu Target Milestone: --- SUMMARY I configured NeoChat's notifications so that a notificaton should be displayed and the window should be highlighted. I do successfully receive the notification popup, but the window is not highlighted. $ cat ~/.config/neochat.notifyrc [Event/invite] Action=Popup|Taskbar Execute= Logfile= Sound= TTS= [Event/message] Action=Popup|Taskbar Execute= Logfile= Sound= TTS= STEPS TO REPRODUCE 1. Configure NeoChat to enable all notifications on mentions 2. In the KDE system settings, change the NeoChat notifications to do both a popup and taskbar highlighting 3. Switch to some other window so that NeoChat isn't active 4. Let someone mention your name in a chat room (or do so with a second account and client) OBSERVED RESULT A notification popup shows that I was mentioned, but the taskbar entry is not highlighted. EXPECTED RESULT I should receive both the popup and the taskbar highlighting. SOFTWARE/OS VERSIONS NeoChat: Built from git Operating System: Fedora Linux 37 KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 6.1.18-200.fc37.x86_64 (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 467434] New: NeoChat crashes and accounts are deleted from config when server is unreachable on startup
https://bugs.kde.org/show_bug.cgi?id=467434 Bug ID: 467434 Summary: NeoChat crashes and accounts are deleted from config when server is unreachable on startup Classification: Applications Product: NeoChat Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: kw...@redhat.com CC: c...@carlschwan.eu Target Milestone: --- Application: neochat (23.03.70) (Compiled from sources) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.15-200.fc37.x86_64 x86_64 Windowing System: X11 Distribution: Fedora Linux 37 (Thirty Seven) DrKonqi: 5.27.2 [KCrashBackend] -- Information about the crash: I have two accounts configured in NeoChat: My public matrix.org account, and an account on a company internal home server that is only reachable through VPN. When I first encountered a probably related problem yesterday, KDE session restore started NeoChat before I had connected to the VPN, and today I reproduced this scenario intentionally manually (a few times to be sure). The result is that the server name doesn't resolve, and apparently NeoChat doesn't handle this error condition well at all. After displaying "Loading..." for a while, it doesn't only crash, but afterwards both accounts are deleted from ~/.config/KDE/neochat.conf! Note that at this point, it had already successfully connected to the matrix.org account. However, the unreachable server is stored as ActiveConnection in ~/.config/neochatrc. These are the last few log messages: quotient.jobs: Sent GET https://matrix-client.matrix.org/_matrix/client/v3/notifications quotient.jobs.sync: Sent GET https://matrix-client.matrix.org/_matrix/client/r0/sync quotient.jobs.sync: "SyncJob-2" destroyed quotient.jobs: 200 <- GET https://matrix-client.matrix.org/_matrix/client/v3/notifications quotient.jobs: "GetNotificationsJob" destroyed quotient.jobs: Retrying "GetTokenOwnerJob" quotient.jobs: Sent GET https:///_matrix/client/v3/account/whoami quotient.jobs: No valid HTTP headers from GET https:///_matrix/client/v3/account/whoami quotient.jobs: Error body (truncated if long): quotient.jobs: "GetTokenOwnerJob" status NetworkError: Host not found Qt Quick Layouts: Detected recursive rearrange. Aborting after two iterations. Qt Quick Layouts: Detected recursive rearrange. Aborting after two iterations. ASSERT: "Controller::instance().activeConnection()" in file /home/kwolf/source/kde/neochat/src/roommanager.cpp, line 87 KCrash: Application 'neochat' crashing... The behaviour looks different when the reachable server is the ActiveConnection. Then I already get to the normal view for the matrix.org account and can read rooms etc. while it's still trying to connect to the unreachable server. Once it finally fails, the room list goes away and the "Join some rooms to get started" message is displayed instead. Scrolling a bit in the still active room crashes in LinkPreviewer::setUrl() because Controller::instance().activeConnection() returns a nullptr now. I can submit a separate bug report for this if necessary. The crash can be reproduced every time. -- Backtrace: Application: NeoChat (neochat), signal: Aborted [KCrash Handler] #4 0x7fa4c6aafe5c in __pthread_kill_implementation () at /lib64/libc.so.6 #5 0x7fa4c6a5fa76 in raise () at /lib64/libc.so.6 #6 0x7fa4c6a497fc in abort () at /lib64/libc.so.6 #7 0x7fa4c70b14e5 in qt_message_output(QtMsgType, QMessageLogContext const&, QString const&) [clone .cold] () at /lib64/libQt5Core.so.5 #8 0x7fa4c70b0828 in qt_assert_x(char const*, char const*, char const*, int) () at /lib64/libQt5Core.so.5 #9 0x00615432 in RoomManager::loadInitialRoom() (this=0x8966a0 ) at /home/kwolf/source/kde/neochat/src/roommanager.cpp:87 #10 0x0046802e in RoomManager::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) (_o=0x8966a0 , _c=QMetaObject::InvokeMetaMethod, _id=10, _a=0x7fff8bee7ad0) at /home/kwolf/source/kde/neochat/build/src/neochat_autogen/EWIEGA46WW/moc_roommanager.cpp:177 #11 0x00468a89 in RoomManager::qt_metacall(QMetaObject::Call, int, void**) (this=0x8966a0 , _c=QMetaObject::InvokeMetaMethod, _id=10, _a=0x7fff8bee7ad0) at /home/kwolf/source/kde/neochat/build/src/neochat_autogen/EWIEGA46WW/moc_roommanager.cpp:380 #12 0x7fa4c9ce96e3 in QQmlObjectOrGadget::metacall(QMetaObject::Call, int, void**) const () at /lib64/libQt5Qml.so.5 #13 0x7fa4c9bc06ad in CallPrecise(QQmlObjectOrGadget const&, QQmlPropertyData const&, QV4::ExecutionEngine*, QV4::CallData*, QMetaObject::Call) () at /lib64/libQt5Qml.so.5 #14 0x7fa4c9bc3a60 in QV4::QObjectMethod::callInternal(QV4::Value const*, QV4::Value const*, int) const () at /lib64/libQt5Qml.so.5 #15
[NeoChat] [Bug 467327] New: NeoChat crash while rejecting invitation from notification
https://bugs.kde.org/show_bug.cgi?id=467327
Bug ID: 467327
Summary: NeoChat crash while rejecting invitation from
notification
Classification: Applications
Product: NeoChat
Version: unspecified
Platform: Compiled Sources
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: General
Assignee: fe...@posteo.de
Reporter: kw...@redhat.com
CC: c...@carlschwan.eu
Target Milestone: ---
Application: neochat (23.03.70)
(Compiled from sources)
Qt Version: 5.15.8
Frameworks Version: 5.103.0
Operating System: Linux 6.1.15-200.fc37.x86_64 x86_64
Windowing System: X11
Distribution: Fedora Linux 37 (Thirty Seven)
DrKonqi: 5.27.2 [KCrashBackend]
-- Information about the crash:
I ran into this crash when I got a bunch of invitations (after setting up a
Matrix bridge) and clicked through each notification accepting or rejecting it.
The stack trace suggests that I rejected this one, and I remember that I did
reject an invitation shortly before it crashed, so I'm willing to believe it.
While processing the rest of the invitations after restarting NeoChat, I
couldn't reproduce the crash or figure out what the exact conditions are for
it. Accepting and rejecting other invitations from the notifications worked
fine.
NeoChat is compiled from git commit 39388e204ede5d8b8a570c12258207901d12abfb.
It may or may not be useful, but the id for m_lastCurrentRoom looks suspicious
if it's not only related to the warning:
(gdb) p *room.d.id.d
$23 = { = {ref = {atomic = {_q_value = std::atomic = { 8 }}},
size = 42, alloc = 43, capacityReserved = 0, offset = 24, static shared_null =
{{ref = {atomic = {
_q_value = std::atomic = { -1 }}}, size = 0, alloc = 0,
capacityReserved = 0, offset = 24, static shared_null = }, {ref = {
atomic = {_q_value = std::atomic = { 0 }}}, size = 0, alloc = 0,
capacityReserved = 0, offset = 0,
static shared_null = }}}, }
(gdb) p *m_lastCurrentRoom.d.id.d
warning: RTTI symbol not found for class 'QQmlPropertyPrivate'
Cannot access memory at address 0x10009
(gdb) p m_lastCurrentRoom.d.id
warning: RTTI symbol not found for class 'QQmlPropertyPrivate'
$24 = {d = 0x10009}
(gdb) p *m_lastCurrentRoom
warning: RTTI symbol not found for class 'QQmlPropertyPrivate'
$27 = { = { = {}, static
staticMetaObject = {d = {superdata = {direct = 0x7f3045d553e0
},
stringdata = 0x7f3048196cc0
<_ZL33qt_meta_stringdata_Quotient__Room.lto_priv.0>, data = 0x7f30481957c0
<_ZL27qt_meta_data_Quotient__Room.lto_priv.0>,
static_metacall = 0x7f3048100140
,
relatedMetaObjects = 0x0, extradata = 0x0}}, d = 0x7f2fb038cfe0},
static staticMetaObject = {d = {superdata = {direct = 0x7f30481f3060
}, stringdata = 0x6e2300
,
data = 0x6e3be0 , static_metacall = 0x462cd0
,
relatedMetaObjects = 0x883110 , extradata
= 0x0}}, highlights = {q_hash = {{d = 0xb03a968, e = 0xb03a968}}},
m_hasFileUploading = 144,
m_fileUploadingProgress = 0, m_currentPushNotificationState = 21778304,
m_pushNotificationStateUpdating = false, m_chatBoxText = {d = 0x7fff0b521560},
m_editText = {d = 0x95286d0},
m_chatBoxReplyId = {d = 0x862b910}, m_chatBoxEditId = {d = 0x27060200260006},
m_chatBoxAttachmentPath = {d = 0x10f00001c}, m_mentions = {d = 0x0},
m_editMentions = {
d = 0x7f3048a980d0 }, m_savedText = {d = 0x},
m_polls = {f = 0x, l = 0x0,
hash = {{d = 0x0, e = 0x0}}, mx = -1707250198, total = 0}}
The reporter is unsure if this crash is reproducible.
-- Backtrace:
Application: NeoChat (neochat), signal: Segmentation fault
[KCrash Handler]
#4 0x7f3045968450 in operator==(QString const&, QString const&) () at
/lib64/libQt5Core.so.5
#5 0x006167c8 in RoomManager::leaveRoom(NeoChatRoom*) (this=0x8966a0
, room=0xa086720) at
/home/kwolf/source/kde/neochat/src/roommanager.cpp:264
#6 0x00654ebc in operator()() const (__closure=0x64e1a30) at
/home/kwolf/source/kde/neochat/src/notificationsmanager.cpp:121
#7 0x00658bf3 in QtPrivate::FunctorCall,
QtPrivate::List<>, void,
NotificationsManager::postInviteNotification(NeoChatRoom*, const QString&,
const QString&, const QImage&):: >::call(struct {...} &, void **)
(f=..., arg=0x7fff0b520a80) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:146
#8 0x00658a69 in
QtPrivate::Functor,
0>::call, void>(struct {...} &, void *, void **) (f=...,
arg=0x7fff0b520a80) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:256
#9 0x00658842 in
QtPrivate::QFunctorSlotObject, 0,
QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *,
void **, bool *) (which=1, this_=0x64e1a20, r=0x896b40
, a=0x7fff0b520a80, ret=0x0) at
/usr/include/qt5/QtCore/qobjectdefs_impl.h:443
#10 0x7f3045ad0e96 in void doActivate(QObject*, int, void**) () at
/lib64/libQt5Core.so.5
[NeoChat] [Bug 466930] New: URL that contains email-like pattern is split into two links
https://bugs.kde.org/show_bug.cgi?id=466930
Bug ID: 466930
Summary: URL that contains email-like pattern is split into two
links
Classification: Applications
Product: NeoChat
Version: unspecified
Platform: Compiled Sources
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: General
Assignee: fe...@posteo.de
Reporter: kw...@redhat.com
CC: c...@carlschwan.eu
Target Milestone: ---
SUMMARY
URLs and email addresses in messages are automatically converted to links. When
the URL contains a pattern that looks like an email address, instead of
creating the intended single link, both parts are converted into links
individually.
STEPS TO REPRODUCE
1. Write a message that contains a link like
https://lore.kernel.org/lkml/CAHk-=wio46vc4t6xxd-sfqjopwfm_u515jm3suzmkgxqtea...@mail.gmail.com/
2. Observe how the message is displayed, and hover with the mouse over it to
see the links
OBSERVED RESULT
The URL is split in three parts:
1. An https:// URL, displayed as a link, but covering only the first half
("https://lore.kernel.org/lkml/CAHk-=; in the example above)
2. A mailto: link for the email-like pattern
("wio46vc4t6xxd-sfqjopwfm_u515jm3suzmkgxqtea...@mail.gmail.com")
3. The remainder is plain text without a link ("/")
EXPECTED RESULT
There should be only one clickable link for the full https:// URL that contains
the text of all three parts.
SOFTWARE/OS VERSIONS
NeoChat: git master (commit 39388e20)
Operating System: Fedora Linux 37
KDE Plasma Version: 5.27.2
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
--
You are receiving this mail because:
You are watching all bug changes.
