Bug 406046 - Buenas tardes, el programa es genial y lo ocupo a diario, el problema es que desde la última actualización el programa se cierra y desconoce mi teléfono.
Summary: Buenas tardes, el programa es genial y lo ocupo a diario, el problema es que ...
Status: RESOLVED DUPLICATE of bug 400010
Alias: None
Product: kdeconnect
Classification: Applications
Component: common (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Albert Vaca Cintora
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-03-30 13:44 UTC by Osvaldo Painequeo
Modified: 2019-04-02 16:19 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
attachment-9695-0.html (1.59 KB, text/html)
2019-03-30 23:02 UTC, Osvaldo Painequeo
Details
attachment-14382-0.html (11.44 KB, text/html)
2019-04-01 02:10 UTC, Osvaldo Painequeo
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Osvaldo Painequeo 2019-03-30 13:44:14 UTC
SUMMARY


STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

Buenas tardes, el programa es genial y lo ocupo a diario, el problema es que desde la última actualización el programa se cierra y desconoce mi teléfono.
Comment 1 Erik Duisters 2019-03-30 18:21:09 UTC
Please use english when filing a bug report and please also specify:

a: What version of android are you using
b: The version of kdeconnect running on your desktop/laptop
c: The version of kdeconnect running on your phone
Comment 2 Osvaldo Painequeo 2019-03-30 23:02:43 UTC
Created attachment 119169 [details]
attachment-9695-0.html

Version de Android :7.0
The version of kdeconnect running on my phone: 1.12.6
The version of kdeconnect running on my desktop/laptop:
1.3.4+p18.04+git20190325.1339-0


El sáb., 30 mar. 2019 a las 15:21, Erik Duisters (<bugzilla_noreply@kde.org>)
escribió:

> https://bugs.kde.org/show_bug.cgi?id=406046
>
> Erik Duisters <e.duisters1@gmail.com> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>                  CC|                            |e.duisters1@gmail.com
>
> --- Comment #1 from Erik Duisters <e.duisters1@gmail.com> ---
> Please use english when filing a bug report and please also specify:
>
> a: What version of android are you using
> b: The version of kdeconnect running on your desktop/laptop
> c: The version of kdeconnect running on your phone
>
> --
> You are receiving this mail because:
> You reported the bug.
Comment 3 Erik Duisters 2019-03-31 11:39:57 UTC
Assuming it's kdeconnectd on the desktop that is crashing can you try running it in a terminal and see if there are any interesting log messages?
Comment 4 Osvaldo Painequeo 2019-04-01 02:10:58 UTC
Created attachment 119191 [details]
attachment-14382-0.html

*La aplicación se detiene y aparece lo siguiente:*



Application: kdeconnectd (kdeconnectd), signal: Segmentation fault

Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

[Current thread is 1 (Thread 0x7f3c63b50040 (LWP 2758))]


Thread 4 (Thread 0x7f3c43fff700 (LWP 2777)):

#0 0x00007f3c60f40bf9 in __GI___poll (fds=0x7f3c3c004a10, nfds=1,
timeout=9151) at ../sysdeps/unix/sysv/linux/poll.c:29

#1 0x00007f3c5bc2a539 in ?? () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0

#2 0x00007f3c5bc2a64c in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0

#3 0x00007f3c6187ba5b in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5

#4 0x00007f3c6181fdda in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5

#5 0x00007f3c6164abca in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5

#6 0x00007f3c61655aeb in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5

#7 0x00007f3c5d6f96db in start_thread (arg=0x7f3c43fff700) at
pthread_create.c:463

#8 0x00007f3c60f4d88f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95


Thread 3 (Thread 0x7f3c48b64700 (LWP 2771)):

#0 0x00007f3c60f3c0b4 in __GI___libc_read (fd=7, buf=0x7f3c48b63b60,
nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27

#1 0x00007f3c5bc6ecd0 in ?? () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0

#2 0x00007f3c5bc2a027 in g_main_context_check () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0

#3 0x00007f3c5bc2a4e0 in ?? () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0

#4 0x00007f3c5bc2a64c in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0

#5 0x00007f3c6187ba5b in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5

#6 0x00007f3c6181fdda in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5

#7 0x00007f3c6164abca in QThread::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5

#8 0x00007f3c6003de45 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5DBus.so.5

#9 0x00007f3c61655aeb in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5

#10 0x00007f3c5d6f96db in start_thread (arg=0x7f3c48b64700) at
pthread_create.c:463

#11 0x00007f3c60f4d88f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95


Thread 2 (Thread 0x7f3c51c37700 (LWP 2767)):

#0 0x00007f3c60f40bf9 in __GI___poll (fds=0x7f3c51c36ca8, nfds=1,
timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29

#1 0x00007f3c5a0f1747 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1

#2 0x00007f3c5a0f336a in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1

#3 0x00007f3c54bf80c9 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5

#4 0x00007f3c61655aeb in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5

#5 0x00007f3c5d6f96db in start_thread (arg=0x7f3c51c37700) at
pthread_create.c:463

#6 0x00007f3c60f4d88f in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95


Thread 1 (Thread 0x7f3c63b50040 (LWP 2758)):

[KCrash Handler]

#6 0x00007f3c616d1f10 in operator==(QString const&, QString const&) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5

#7 0x00007f3c6318825c in KNotification::setTitle(QString const&) () from
/usr/lib/x86_64-linux-gnu/libKF5Notifications.so.5

#8 0x00007f3c40987b8f in ?? () from
/usr/lib/x86_64-linux-gnu/qt5/plugins/kdeconnect/kdeconnect_notifications.so

#9 0x00007f3c40990cb5 in ?? () from
/usr/lib/x86_64-linux-gnu/qt5/plugins/kdeconnect/kdeconnect_notifications.so

#10 0x00007f3c4098c37f in ?? () from
/usr/lib/x86_64-linux-gnu/qt5/plugins/kdeconnect/kdeconnect_notifications.so

#11 0x00007f3c6375a770 in Device::privateReceivedPacket(NetworkPacket
const&) () from /usr/lib/x86_64-linux-gnu/libkdeconnectcore.so.1

#12 0x00007f3c61850bdf in QMetaObject::activate(QObject*, int, int, void**)
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5

#13 0x00007f3c63762765 in ?? () from
/usr/lib/x86_64-linux-gnu/libkdeconnectcore.so.1

#14 0x00007f3c637377cf in LanDeviceLink::dataReceived() () from
/usr/lib/x86_64-linux-gnu/libkdeconnectcore.so.1

#15 0x00007f3c61850bdf in QMetaObject::activate(QObject*, int, int, void**)
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5

#16 0x00007f3c63740536 in SocketLineReader::dataReceived() () from
/usr/lib/x86_64-linux-gnu/libkdeconnectcore.so.1

#17 0x00007f3c61850bdf in QMetaObject::activate(QObject*, int, int, void**)
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5

#18 0x00007f3c60bcbcf8 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Network.so.5

#19 0x00007f3c60bb02e1 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Network.so.5

#20 0x00007f3c61850ac5 in QMetaObject::activate(QObject*, int, int, void**)
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5

#21 0x00007f3c60b78b73 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Network.so.5

#22 0x00007f3c60b78c24 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Network.so.5

#23 0x00007f3c60b8c4e1 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Network.so.5

#24 0x00007f3c62615e8c in QApplicationPrivate::notify_helper(QObject*,
QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5

#25 0x00007f3c6261d45f in QApplication::notify(QObject*, QEvent*) () from
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5

#26 0x00007f3c61821aa8 in QCoreApplication::notifyInternal2(QObject*,
QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5

#27 0x00007f3c6187c69d in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5

#28 0x00007f3c5bc2a387 in g_main_context_dispatch () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0

#29 0x00007f3c5bc2a5c0 in ?? () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0

#30 0x00007f3c5bc2a64c in g_main_context_iteration () from
/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0

#31 0x00007f3c6187ba3f in
QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>)
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5

#32 0x00007f3c54c84211 in ?? () from
/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5

#33 0x00007f3c6181fdda in
QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5

#34 0x00007f3c61828f90 in QCoreApplication::exec() () from
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5

#35 0x0000556abe5a7034 in ?? ()

#36 0x00007f3c60e4db97 in __libc_start_main (main=0x556abe5a6f30, argc=1,
argv=0x7fff2a6c4938, init=<optimized out>, fini=<optimized out>,
rtld_fini=<optimized out>, stack_end=0x7fff2a6c4928) at
../csu/libc-start.c:310

#37 0x0000556abe5a709a in _start ()



El dom., 31 mar. 2019 a las 8:39, Erik Duisters (<bugzilla_noreply@kde.org>)
escribió:

> https://bugs.kde.org/show_bug.cgi?id=406046
>
> Erik Duisters <e.duisters1@gmail.com> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>          Resolution|---                         |WAITINGFORINFO
>              Status|REPORTED                    |NEEDSINFO
>
> --- Comment #3 from Erik Duisters <e.duisters1@gmail.com> ---
> Assuming it's kdeconnectd on the desktop that is crashing can you try
> running
> it in a terminal and see if there are any interesting log messages?
>
> --
> You are receiving this mail because:
> You reported the bug.
Comment 5 Christoph Feck 2019-04-02 16:19:36 UTC

*** This bug has been marked as a duplicate of bug 400010 ***