Bug 375202 - Crashes after a few seconds
Summary: Crashes after a few seconds
Status: RESOLVED WORKSFORME
Alias: None
Product: krdc
Classification: Applications
Component: RDP (other bugs)
Version First Reported In: unspecified
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: Urs Wolfer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-01-17 22:21 UTC by LeoJusz
Modified: 2021-02-10 04:33 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description LeoJusz 2017-01-17 22:21:29 UTC
After RDPing into a Windows 10 machine it crashes. Running it from CLI i get:
$ KBookmarkMenu::slotBookmarksChanged groupAddress:  "/0"
Comment 1 Christoph Feck 2017-01-18 15:49:09 UTC
If this is reproducible, please add the backtrace for the crash. For more information, please read https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
Comment 2 LeoJusz 2017-01-19 05:11:06 UTC
(In reply to Christoph Feck from comment #1)
> If this is reproducible, please add the backtrace for the crash. For more
> information, please read
> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/
> How_to_create_useful_crash_reports

This is what i get:

(gdb) run
Starting program: /usr/bin/krdc 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0x7fffe1ec3700 (LWP 9777)]
[New Thread 0x7fffdb957700 (LWP 9778)]
KBookmarkMenu::slotBookmarksChanged groupAddress:  "/0"
Comment 3 Christoph Feck 2017-01-24 22:58:11 UTC
If gdb shows its (gdb) prompt again after the crash, please use the "bt" command to actually show the backtrace, and add it here.
Comment 4 Justin Zobel 2020-12-17 05:26:17 UTC
Thank you for the crash report.

As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved.

I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved/worksforme" when you respond, thank you.
Comment 5 Justin Zobel 2021-01-11 23:08:42 UTC
Status correction.
Comment 6 Bug Janitor Service 2021-01-26 04:33:16 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
mark the bug 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 7 Bug Janitor Service 2021-02-10 04:33:17 UTC
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!