| Summary: | KDE Connect stop when copy 5 pictures from my phone Android | ||
|---|---|---|---|
| Product: | [Applications] kdeconnect | Reporter: | elsa.zapataa |
| Component: | common | Assignee: | Albert Vaca Cintora <albertvaka> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | orgo_89 |
| Priority: | NOR | Keywords: | drkonqi |
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Neon | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
New crash information added by DrKonqi
attachment-15296-0.html |
||
|
Description
elsa.zapataa
2020-07-06 13:09:38 UTC
Created attachment 130672 [details]
New crash information added by DrKonqi
kdeconnectd (1.4.0) using Qt 5.14.2
- What I was doing when the application crashed:
I was trying to copy 10 files from my Android phone but the copy stopped with the first file. My phone showed an alert from KDE Connect saying that the transfer failed but in KDE desktop the notification was just like stuck so I decided to stop it and that was the exact moment when KDE Connect crashed.
-- Backtrace (Reduced):
#4 KJob::kill (this=0x563a58a221f0, verbosity=KJob::Quietly) at ./src/lib/jobs/kjob.cpp:106
#5 0x00007fd4d543635d in KJob::kill (this=0x563a58a5fed0, verbosity=verbosity@entry=KJob::EmitResult) at ./src/lib/jobs/kjob.cpp:106
#6 0x00007fd4d23d6c19 in KUiServerJobTracker::Private::_k_killJob (this=<optimized out>) at ./src/kuiserverjobtracker.cpp:62
#7 0x00007fd4d23d6d39 in KUiServerJobTracker::qt_static_metacall (_o=<optimized out>, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at ./obj-x86_64-linux-gnu/src/KF5JobWidgets_autogen/include/moc_kuiserverjobtracker.cpp:125
#8 0x00007fd4d3b9d4b9 in doActivate<false> (sender=0x563a58a057c0, signal_index=3, argv=0x7ffc1b696b80) at kernel/qobject.cpp:3882
Thank you for reporting this crash in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the crash with a recent software version? If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you! 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! 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! Created attachment 153764 [details] attachment-15296-0.html Sorry, I don't remember what was the crash, so you can close the topic. Kind regards. Elsa Zapata Le mer. 12 oct. 2022, 05:49, Justin Zobel <bugzilla_noreply@kde.org> a écrit : > https://bugs.kde.org/show_bug.cgi?id=423927 > > Justin Zobel <justin.zobel@gmail.com> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Status|REPORTED |NEEDSINFO > Resolution|--- |WAITINGFORINFO > > --- Comment #2 from Justin Zobel <justin.zobel@gmail.com> --- > Thank you for reporting this crash in KDE software. As it has been a while > since this issue was reported, can we please ask you to see if you can > reproduce the crash with a recent software version? > > If you can reproduce the issue, please change the status to "CONFIRMED" > when > replying. Thank you! > > -- > You are receiving this mail because: > You reported the bug. |