Bug 227453

#Translation:
When I select a widget to share in the network, the message "Add to the current activity" is shown. If you leave the window (when you put the password and other information) Plasma will crash.

@Raul: esto pasa con cualquier widget ?
Gracias

I can confirm this bug (same software versions of KDE for kubuntu etc...) in my netbook and in my computer

I try to share I "Notes" plasmoid in the netbook... crash when I click to add it in the computer.
I re-try again and I get the same result but other times I can get a put your password  in the netbook and crash (in the computer), finally, trying it a lot of times in a row I got a password box in the computer and I got a Notes widget but with no data and with default yellow theme (the shared notes in the netbook is blue and I have a text "hello world!"). No data is updated If I try to write in the netbook or in teh computer widget.

I tried this time a folder view with the 2 options of share widgets enabled and I was able to add it but they are broken because not showed nothing, only a big folder icon of my home folder, no folderview of the netbook in my computer.

Another thing is that there is no human way to add shared widgets if they aren't in the notifications widget... the shared widget that appear in the Dolphin -> Network is useless :S

On Jueves 18 Febrero 2010 17:56:25 Dario Andres escribió:
> https://bugs.kde.org/show_bug.cgi?id=227453
> 
> 
> Dario Andres <andresbajotierra@gmail.com> changed:
> 
>            What    |Removed                     |Added
> ---------------------------------------------------------------------------
> - CC|                            |andresbajotierra@gmail.com
> Summary|Compartiendo widgets con la |Plasma crashes when sharing
> 
>                    |red                         |a widget over the network
>                    |
>                    |                            |[Plasma::Applet::containme
>                    |                            |n t,
>                    |                            |Plasma::Containment::addAp
>                    |                            |p let,
>                    |                            |PlasmaApp::plasmoidAccessF
>                    |                            |i nished]
> 
> --- Comment #1 from Dario Andres <andresbajotierra gmail com>  
2010-02-18
> 17:56:23 --- #Translation:
> When I select a widget to share in the network, the message "Add to the
> current activity" is shown. If you leave the window (when you put the
> password and other information) Plasma will crash.
> 
> @Raul: esto pasa con cualquier widget ?
> Gracias

Si, primero selecciono la configuracion de algun widget y le pongo usar en 
la red, acepto los cambios, y el escritorio me avisa con un mensaje y un 
boton, pulsas el boton para la configuración de la clave y demás, estoy un 
ratillo con la ventana esa nueva abierta, y crashhh!!!!, aki te mando otro 
backtrace de esos, un saludo!!

#en (translating~ comment 3):
When I try to configure any widget and I enable the network sharing, the desktop notifies me with a message and a button. If you presse the button, a window will appear. If you leave that window alone a moment Plasma will crash

From bug 227669:
When I add a remote plasmoid, that was shared over the network and discovered
via Zeroconf/Bonjour, the whole plasma-desktop crashes.

*** Bug 227669 has been marked as a duplicate of this bug. ***

- Is this still happening on KDE SC 4.4.1 ?
Regards

On Domingo 21 Marzo 2010 22:06:38 Dario Andres escribió:
> https://bugs.kde.org/show_bug.cgi?id=227453
> 
> 
> 
> 
> 
> --- Comment #7 from Dario Andres <andresbajotierra gmail com>  
2010-03-21
> 22:06:34 --- - Is this still happening on KDE SC 4.4.1 ?
> Regards


Si, todavia sigue ocurriendo, envio el traza inversa del error:

Application: Área de trabajo de Plasma (kdeinit4), signal: Segmentation fault
The current source language is "auto; currently c".
[Current thread is 1 (Thread 0x7f43eb5bf7f0 (LWP 12740))]

Thread 3 (Thread 0x7f43b6b0e910 (LWP 1932)):
#0  0xffffffffff60017b in ?? ()
#1  0x00007f43b6b0dc60 in ?? ()
#2  0x00007fff2f9c9782 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 2 (Thread 0x7f43c0dcf910 (LWP 1937)):
#0  0x00007f43e98050bc in __pthread_mutex_lock (mutex=0x96f1ed8) at 
pthread_mutex_lock.c:62
#1  0x00007f43e4d8c423 in g_main_context_iterate (context=0x96f1ed0, 
block=<value optimized out>, dispatch=<value optimized out>, self=<value 
optimized out>)
    at /build/buildd/glib2.0-2.22.3/glib/gmain.c:2557
#2  0x00007f43e4d8c6c0 in IA__g_main_context_iteration 
(context=0x96f1ed0, may_block=1) at 
/build/buildd/glib2.0-2.22.3/glib/gmain.c:2654
#3  0x00007f43e9baf386 in QEventDispatcherGlib::processEvents 
(this=0x97e24a0, flags=<value optimized out>) at 
kernel/qeventdispatcher_glib.cpp:414
#4  0x00007f43e9b84732 in QEventLoop::processEvents (this=<value 
optimized out>, flags=) at kernel/qeventloop.cpp:149
#5  0x00007f43e9b84b0c in QEventLoop::exec (this=0x7f43c0dcef70, flags=) 
at kernel/qeventloop.cpp:201
#6  0x00007f43e9a8ed59 in QThread::exec (this=<value optimized out>) at 
thread/qthread.cpp:487
#7  0x00007f43e1c10621 in Jolie::ClientThread::run (this=0x96f9e10) at 
../../plasma/private/qtjolie-branch/qtjolie/clientthread.cpp:86
#8  0x00007f43e9a91775 in QThreadPrivate::start (arg=0x96f9e10) at 
thread/qthread_unix.cpp:248
#9  0x00007f43e9802a04 in start_thread (arg=<value optimized out>) at 
pthread_create.c:300
#10 0x00007f43e85c680d in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#11 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f43eb5bf7f0 (LWP 12740)):
[KCrash Handler]
#5  0x00007f43e92fd484 in QGraphicsItem::parentItem (this=0x972c040) at 
graphicsview/qgraphicsitem.cpp:1453
#6  0x00007f43e1b02af9 in Plasma::Applet::containment (this=0x972c030) 
at ../../plasma/applet.cpp:1407
#7  0x00007f43e1b22843 in Plasma::Containment::addApplet 
(this=0x1955160, applet=0x972c030, pos=..., delayInit=false) at 
../../plasma/containment.cpp:911
#8  0x00007f43dc9918b6 in PlasmaApp::plasmoidAccessFinished 
(this=<value optimized out>, job=0x972c320) at 
../../../../plasma/desktop/shell/plasmaapp.cpp:1207
#9  0x00007f43dc996b1e in PlasmaApp::qt_metacall (this=0x13bd1b0, 
_c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, 
_a=0x7fff2f812f20) at ./plasmaapp.moc:157
#10 0x00007f43e9b98c0f in QMetaObject::activate (sender=0x143d750, 
m=<value optimized out>, local_signal_index=<value optimized out>, 
argv=0xa) at kernel/qobject.cpp:3293
#11 0x00007f43e1ba800f in Plasma::AccessManager::finished 
(this=0x972c040, _t1=0x972c320) at ./accessmanager.moc:102
#12 0x00007f43e1baa058 in Plasma::AccessManagerPrivate::slotJobFinished 
(this=0x143d750, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized 
out>, _a=0x7fff2f8130a0)
    at ../../plasma/remote/accessmanager.cpp:126
#13 Plasma::AccessManager::qt_metacall (this=0x143d750, 
_c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, 
_a=0x7fff2f8130a0) at ./accessmanager.moc:88
#14 0x00007f43e9b98c0f in QMetaObject::activate (sender=0x972c320, 
m=<value optimized out>, local_signal_index=<value optimized out>, 
argv=0xa) at kernel/qobject.cpp:3293
#15 0x00007f43eb035eff in KJob::finished (this=0x972c040, _t1=0x972c320) 
at ./kjob.moc:173
#16 0x00007f43eb036035 in KJob::emitResult (this=0x972c320) at 
../../kdecore/jobs/kjob.cpp:310
#17 0x00007f43e1bab4c2 in Plasma::AccessAppletJobPrivate::slotTimeout() 
() from /usr/lib/libplasma.so.3
#18 0x00007f43e1bab29b in Plasma::AccessAppletJob::qt_metacall 
(this=0x972c320, _c=QMetaObject::InvokeMetaMethod, _id=0, 
_a=0x7fff2f813220) at ./accessappletjob.moc:81
#19 0x00007f43e9b98c0f in QMetaObject::activate (sender=0x9723030, 
m=<value optimized out>, local_signal_index=<value optimized out>, 
argv=0xa) at kernel/qobject.cpp:3293
#20 0x00007f43e9ba03ff in QSingleShotTimer::timerEvent (this=0x9723030) 
at kernel/qtimer.cpp:308
#21 0x00007f43e9b95863 in QObject::event (this=0x9723030, 
e=0x7fff2f813980) at kernel/qobject.cpp:1212
#22 0x00007f43e8d2412c in QApplicationPrivate::notify_helper 
(this=0x13d3710, receiver=0x9723030, e=0x7fff2f813980) at 
kernel/qapplication.cpp:4300
#23 0x00007f43e8d2a71b in QApplication::notify (this=0x13bd1b0, 
receiver=0x9723030, e=0x7fff2f813980) at kernel/qapplication.cpp:4183
#24 0x00007f43ea0cdd76 in KApplication::notify (this=0x13bd1b0, 
receiver=0x9723030, event=0x7fff2f813980) at 
../../kdeui/kernel/kapplication.cpp:302
#25 0x00007f43e9b85e0c in QCoreApplication::notifyInternal 
(this=0x13bd1b0, receiver=0x9723030, event=0x7fff2f813980) at 
kernel/qcoreapplication.cpp:704
#26 0x00007f43e9bb2a62 in QCoreApplication::sendEvent (this=0x13d6ca0) 
at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#27 QTimerInfoList::activateTimers (this=0x13d6ca0) at 
kernel/qeventdispatcher_unix.cpp:603
#28 0x00007f43e9baf668 in timerSourceDispatch (source=<value optimized 
out>) at kernel/qeventdispatcher_glib.cpp:184
#29 idleTimerSourceDispatch (source=<value optimized out>) at 
kernel/qeventdispatcher_glib.cpp:231
#30 0x00007f43e4d88bce in g_main_dispatch (context=0x13d5d20) at 
/build/buildd/glib2.0-2.22.3/glib/gmain.c:1960
#31 IA__g_main_context_dispatch (context=0x13d5d20) at 
/build/buildd/glib2.0-2.22.3/glib/gmain.c:2513
#32 0x00007f43e4d8c598 in g_main_context_iterate (context=0x13d5d20, 
block=<value optimized out>, dispatch=<value optimized out>, self=<value 
optimized out>)
    at /build/buildd/glib2.0-2.22.3/glib/gmain.c:2591
#33 0x00007f43e4d8c6c0 in IA__g_main_context_iteration 
(context=0x13d5d20, may_block=1) at 
/build/buildd/glib2.0-2.22.3/glib/gmain.c:2654
#34 0x00007f43e9baf333 in QEventDispatcherGlib::processEvents 
(this=0x134b1c0, flags=<value optimized out>) at 
kernel/qeventdispatcher_glib.cpp:412
#35 0x00007f43e8dd3f0e in QGuiEventDispatcherGlib::processEvents 
(this=0x972c040, flags=<value optimized out>) at 
kernel/qguieventdispatcher_glib.cpp:204
#36 0x00007f43e9b84732 in QEventLoop::processEvents (this=<value 
optimized out>, flags=) at kernel/qeventloop.cpp:149
#37 0x00007f43e9b84b0c in QEventLoop::exec (this=0x7fff2f813c20, flags=) 
at kernel/qeventloop.cpp:201
#38 0x00007f43e9b8884b in QCoreApplication::exec () at 
kernel/qcoreapplication.cpp:981
#39 0x00007f43dc97f0a2 in kdemain (argc=<value optimized out>, 
argv=<value optimized out>) at ../../../../plasma/desktop/shell/main.cpp:112
#40 0x0000000000406fb8 in launch (argc=1, _name=<value optimized out>, 
args=<value optimized out>, cwd=<value optimized out>, envc=0, 
envs=<value optimized out>, reset_env=false, tty=0x0, 
    avoid_loops=false, startup_id_str=0x40a499 "0") at 
../../kinit/kinit.cpp:717
#41 0x0000000000407c70 in handle_launcher_request (sock=8, 
who=<value optimized out>) at ../../kinit/kinit.cpp:1209
#42 0x0000000000408121 in handle_requests (waitForPid=0) at 
../../kinit/kinit.cpp:1402
#43 0x0000000000408df2 in main (argc=4, argv=<value optimized out>, 
envp=<value optimized out>) at ../../kinit/kinit.cpp:1841

*** Bug 235331 has been marked as a duplicate of this bug. ***

Created attachment 53119 [details]
New crash information added by DrKonqi

plasma-desktop (0.3) on KDE Platform 4.5.3 (KDE 4.5.3) using Qt 4.7.0

- What I was doing when the application crashed:

I added remote plasmoid "Now playing" and then plasma crashed

-- Backtrace (Reduced):
#7  Plasma::Applet::containment (this=0x7ffffff7) at ../../plasma/applet.cpp:1472
#8  0x00b8da82 in Plasma::Containment::addApplet (this=0x9dc8dc0, applet=0x7ffffff7, pos=..., delayInit=false) at ../../plasma/containment.cpp:932
[...]
[...]
[...]
[...]
#13 0x00c2d173 in Plasma::AccessManager::finished (this=0x9ba1750, _t1=0xb0e6858) at ./accessmanager.moc:102
#14 0x00c2f434 in slotJobFinished (this=0x9ba1750, _c=QMetaObject::InvokeMetaMethod, _id=7, _a=0xbfd51458) at ../../plasma/remote/accessmanager.cpp:126
#15 Plasma::AccessManager::qt_metacall (this=0x9ba1750, _c=QMetaObject::InvokeMetaMethod, _id=7, _a=0xbfd51458) at ./accessmanager.moc:88

Created attachment 57281 [details]
New crash information added by DrKonqi

plasma-desktop (0.4) on KDE Platform 4.6.00 (4.6.0) using Qt 4.7.0

- What I was doing when the application crashed:
Also happened when sharing the "Now Playing" widget.
This did not happen however before I upgraded to 4.6(4.5.2)

- Unusual behavior I noticed:
Now playing spawns on the client machine, it however does not display any information from the host machine.

When sharing "System Information Widget" afterwards it creates a crash.

-- Backtrace (Reduced):
#6  Plasma::Applet::containment (this=0x6f7461636f6c6c61) at ../../plasma/applet.cpp:1497
#7  0x00007f860e1c2713 in Plasma::Containment::addApplet (this=0x2b6cbc0, applet=0x6f7461636f6c6c61, pos=..., delayInit=false) at ../../plasma/containment.cpp:867
#8  0x00007f860e9a99f6 in PlasmaApp::plasmoidAccessFinished (this=<value optimized out>, job=0x4630ae0) at ../../../../plasma/desktop/shell/plasmaapp.cpp:1334
#9  0x00007f860e9afb14 in PlasmaApp::qt_metacall (this=0x25cca80, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff66502b60) at ./plasmaapp.moc:169
[...]
#11 0x00007f860e2515ef in Plasma::AccessManager::finished (this=0x6f7461636f6c6c61, _t1=0x4630ae0) at ./accessmanager.moc:102

*** Bug 271915 has been marked as a duplicate of this bug. ***

Git commit a53aac070a28c63fbe36a171df1fe1de40b73fb7 by Aaron Seigo.
Committed on 28/04/2011 at 21:48.
Pushed by aseigo into branch 'KDE/4.6'.

initialize the value of applet

BUG:227453

M  +8    -2    plasma/remote/accessappletjob.cpp     

http://commits.kde.org/kdelibs/a53aac070a28c63fbe36a171df1fe1de40b73fb7

Git commit 1f71744268f4e18445f41ee2acd86a442041d3dc by Aaron Seigo.
Committed on 28/04/2011 at 21:48.
Pushed by aseigo into branch 'master'.

initialize the value of applet

BUG:227453

M  +8    -2    plasma/remote/accessappletjob.cpp     

http://commits.kde.org/kdelibs/1f71744268f4e18445f41ee2acd86a442041d3dc

*** Bug 276142 has been marked as a duplicate of this bug. ***

Created attachment 65879 [details]
New crash information added by DrKonqi

plasma-desktop (0.4) on KDE Platform 4.6.00 (4.6.0) "release 6" using Qt 4.7.1

- What I was doing when the application crashed: I was trying to add a remote plasmoid from a desktop to a laptop with zeroconf-protocol. The plasmoid I have on desktop is "Computer temperature". I have checked "Publish" and "Let all use plasmoid". I want follow my desptop temperature from my laptop on the LAN. My KDE version is 4.6.

-- Backtrace (Reduced):
#7  Plasma::Applet::containment (this=0x7ffffff7) at /usr/src/debug/kdelibs-4.6.0/plasma/applet.cpp:1497
#8  0xb4d6197f in Plasma::Containment::addApplet (this=0x83b1b78, applet=0x7ffffff7, pos=..., delayInit=false) at /usr/src/debug/kdelibs-4.6.0/plasma/containment.cpp:867
#9  0xb268c227 in PlasmaApp::plasmoidAccessFinished (this=0x80b6400, job=0x8b41b30) at /usr/src/debug/kdebase-workspace-4.6.0/plasma/desktop/shell/plasmaapp.cpp:1334
#10 0xb2693542 in PlasmaApp::qt_metacall (this=0x80b6400, _c=QMetaObject::InvokeMetaMethod, _id=31, _a=0xbfe1b578) at /usr/src/debug/kdebase-workspace-4.6.0/build/plasma/desktop/shell/plasmaapp.moc:169
[...]
#13 0xb4df0a45 in Plasma::AccessManager::finished (this=0x8168b28, _t1=0x8b41b30) at /usr/src/debug/kdelibs-4.6.0/build/plasma/accessmanager.moc:102

*** Bug 279939 has been marked as a duplicate of this bug. ***