Bug 306127 - fallo al intentar desmontar nfs (en el proceso de nfs restart)
Summary: fallo al intentar desmontar nfs (en el proceso de nfs restart)
Status: RESOLVED DUPLICATE of bug 294374
Alias: None
Product: kdelibs
Classification: Frameworks and Libraries
Component: kded (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-09-01 09:58 UTC by julian
Modified: 2012-09-07 11:49 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description julian 2012-09-01 09:58:14 UTC
Application: kded4 ($Id$)
KDE Platform Version: 4.7.2 (4.7.2) "release 5"
Qt Version: 4.7.4
Operating System: Linux 3.1.10-1.16-desktop x86_64
Distribution: "openSUSE 12.1 (x86_64)"

-- Information about the crash:
tratando de reiniciar el servicio cliente nfs /etc/init.d/nfs restart, Shutting down NFS client services:umount: /var/lib/nfs/rpc_pipefs: device is busy. Varios minutos después, mientras redacto este informe, el notificador de dispositivos dice...falló en el intento de montar 192.xxx.xxx.xxx...
p.d.: como podría librarme de este y otros automatismos molestiiiisimos de kde 4...dos años esperando a una versión estable, y todavía tengo que mantener a salvo mi carpeta .kde para no perder la larga y tediosa configuración por la estabilidad.

The crash can be reproduced every time.

-- Backtrace:
Application: Servicio de KDE (kdeinit4), signal: Segmentation fault
[Current thread is 1 (Thread 0x7f222cf16760 (LWP 1640))]

Thread 3 (Thread 0x7f220f9b2700 (LWP 1678)):
#0  0x00007f222a589ff3 in poll () from /lib64/libc.so.6
#1  0x00007f222737dae8 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x00007f222737e312 in g_main_loop_run () from /usr/lib64/libglib-2.0.so.0
#3  0x00007f220feaa946 in ?? () from /usr/lib64/libgio-2.0.so.0
#4  0x00007f22273a2e06 in ?? () from /usr/lib64/libglib-2.0.so.0
#5  0x00007f221cbb6b74 in ?? () from /usr/lib64/libGL.so.1
#6  0x00007f222b7f9f05 in start_thread () from /lib64/libpthread.so.0
#7  0x00007f222a59310d in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f220efa5700 (LWP 1684)):
#0  0x00007f222a589ff3 in poll () from /lib64/libc.so.6
#1  0x00007f222737dae8 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x00007f222737dfa9 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#3  0x00007f222bb9b586 in QEventDispatcherGlib::processEvents (this=0x7f22000008e0, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:424
#4  0x00007f222bb6fa32 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007f222bb6fc2f in QEventLoop::exec (this=0x7f220efa4d30, flags=...) at kernel/qeventloop.cpp:201
#6  0x00007f222ba875df in QThread::exec (this=<optimized out>) at thread/qthread.cpp:498
#7  0x00007f222bb52aff in QInotifyFileSystemWatcherEngine::run (this=0xa00540) at io/qfilesystemwatcher_inotify.cpp:248
#8  0x00007f222ba8a025 in QThreadPrivate::start (arg=0xa00540) at thread/qthread_unix.cpp:331
#9  0x00007f221cbb6b74 in ?? () from /usr/lib64/libGL.so.1
#10 0x00007f222b7f9f05 in start_thread () from /lib64/libpthread.so.0
#11 0x00007f222a59310d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f222cf16760 (LWP 1640)):
[KCrash Handler]
#6  QProcessManager::remove (this=0x7f222bea0f80, process=0x8eca40) at io/qprocess_unix.cpp:308
#7  0x00007f222bb10a9a in QProcess::~QProcess (this=0x6f86f0, __in_chrg=<optimized out>) at io/qprocess.cpp:1138
#8  0x00007f222bb10ad9 in QProcess::~QProcess (this=0x6f86f0, __in_chrg=<optimized out>) at io/qprocess.cpp:1141
#9  0x00007f22244978aa in Solid::Backends::Fstab::FstabStorageAccess::slotSetupFinished (this=0xa60430, exitCode=<optimized out>) at /usr/src/debug/kdelibs-4.7.2/solid/solid/backends/fstab/fstabstorageaccess.cpp:130
#10 0x00007f222442430a in Solid::Backends::Fstab::FstabStorageAccess::qt_metacall (this=0xa60430, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=0x7fffd84f2190) at /usr/src/debug/kdelibs-4.7.2/build/solid/solid/moc_fstabstorageaccess.cpp:109
#11 0x00007f222bb835aa in QMetaObject::activate (sender=0xa8a8b0, m=<optimized out>, local_signal_index=<optimized out>, argv=0x7fffd84f2190) at kernel/qobject.cpp:3287
#12 0x00007f222bb1061f in QProcess::finished (this=<optimized out>, _t1=32, _t2=QProcess::NormalExit) at .moc/release-shared/moc_qprocess.cpp:142
#13 0x00007f222bb15326 in QProcessPrivate::_q_processDied (this=0xb93cc0) at io/qprocess.cpp:1051
#14 0x00007f222bb15929 in QProcess::qt_metacall (this=0xa8a8b0, _c=QMetaObject::InvokeMetaMethod, _id=13, _a=0x7fffd84f22f0) at .moc/release-shared/moc_qprocess.cpp:115
#15 0x00007f222bb835aa in QMetaObject::activate (sender=0xa5bc00, m=<optimized out>, local_signal_index=<optimized out>, argv=0x7fffd84f22f0) at kernel/qobject.cpp:3287
#16 0x00007f222bbcd17e in QSocketNotifier::activated (this=<optimized out>, _t1=30) at .moc/release-shared/moc_qsocketnotifier.cpp:89
#17 0x00007f222bb8b25b in QSocketNotifier::event (this=0xa5bc00, e=0x7fffd84f2960) at kernel/qsocketnotifier.cpp:317
#18 0x00007f222ad22c34 in notify_helper (e=0x7fffd84f2960, receiver=0xa5bc00, this=0x7a5f60) at kernel/qapplication.cpp:4481
#19 QApplicationPrivate::notify_helper (this=0x7a5f60, receiver=0xa5bc00, e=0x7fffd84f2960) at kernel/qapplication.cpp:4453
#20 0x00007f222ad27ac1 in QApplication::notify (this=0x7fffd84f2c10, receiver=0xa5bc00, e=0x7fffd84f2960) at kernel/qapplication.cpp:4360
#21 0x00007f222c902e36 in KApplication::notify (this=0x7fffd84f2c10, receiver=0xa5bc00, event=0x7fffd84f2960) at /usr/src/debug/kdelibs-4.7.2/kdeui/kernel/kapplication.cpp:311
#22 0x00007f222bb7082c in QCoreApplication::notifyInternal (this=0x7fffd84f2c10, receiver=0xa5bc00, event=0x7fffd84f2960) at kernel/qcoreapplication.cpp:787
#23 0x00007f222bb9ac37 in sendEvent (event=0x7fffd84f2960, receiver=<optimized out>) at kernel/qcoreapplication.h:215
#24 socketNotifierSourceDispatch (source=0x7a89d0) at kernel/qeventdispatcher_glib.cpp:110
#25 0x00007f222737d5dd in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#26 0x00007f222737ddd8 in ?? () from /usr/lib64/libglib-2.0.so.0
#27 0x00007f222737dfa9 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#28 0x00007f222bb9b51f in QEventDispatcherGlib::processEvents (this=0x616ce0, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:422
#29 0x00007f222adc5f9e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=<optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#30 0x00007f222bb6fa32 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#31 0x00007f222bb6fc2f in QEventLoop::exec (this=0x7fffd84f2ba0, flags=...) at kernel/qeventloop.cpp:201
#32 0x00007f222bb73df7 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1064
#33 0x00007f22189903c5 in kdemain () from /usr/lib64/libkdeinit4_kded4.so
#34 0x0000000000408897 in _start ()

Possible duplicates by query: bug 294374, bug 284668.

Reported using DrKonqi
Comment 1 julian 2012-09-01 10:09:36 UTC
Una vez consigo mediante consola montar el nfs y acceder a él, todavía el notificador de dispositivos insiste en que no puede montarlo ¿?¿?¿?¿?, y digo yo...como podría librarme de él (el notificador digo) que lo tengo marcado para que no monte nada, e  insiste en interrumpir el trabajo, intentando montar y desmontar...ni el administrador parece tener más pribilegios que el maldito automatismo...
Comment 2 Jekyll Wu 2012-09-01 11:02:56 UTC
Please always use English to report bugs

*** This bug has been marked as a duplicate of bug 294374 ***
Comment 3 julian 2012-09-01 13:15:01 UTC
sorry the windows bug say me "anadir comentarios" "nombre del fallo" i continue in spanish.
i dont see the duplicate with Bug 294374 no libc o libglib implicate in this bug ¿?.
Once you get through nfs mount console and access it, the device notifier still insists he can ride?????, And as I say ... could get rid of it (the notifier say) that I have it marked to not mount anything, and insists on interrupting work, trying to assemble and disassemble ... or the administrator seems to have more than the damn pribilegios automation ...
only need use google translate.
and the great cuestion is, there is any way for down the notifier service??? ... reality i want manual access to my media...i have mark only remobable, but is nfs remobable??? i dont know, but this is not a duplicate bug like 294374...
Comment 4 julian 2012-09-07 11:49:58 UTC
i dont see duplicate...but dont problem, now i write this in kde 3, i say bye kde 4... in 4.7 only 2 week, and 5 xwindows crash. more than 15 years i use kde, i havent account for forum or bug, because i locate all time solution before need call for help. 
this is a good way for lost user...old old user...
and this is one bug, in 2 week with 4.7...7...7...7 "stable"...no 4.0 or 1 beta 4.7 "stable" n+1 bug, no solved for more time, and say ¿duplicate? hehehe nplicate when n---> very much.
if possible need stop this run, and serenity and put a reality stable version of kde 4 some day. but this isnt good way for that.
i say goodbye kde4, im happy kde 3 alive¡¡¡ life the king, long life for kde3


y que se mueran los feos jajajaja...nada personal espero que entiendas...