[Bug 623282] New: Yast2 NFS module mount new directory gives segmentation fault
http://bugzilla.novell.com/show_bug.cgi?id=623282 http://bugzilla.novell.com/show_bug.cgi?id=623282#c0 Summary: Yast2 NFS module mount new directory gives segmentation fault Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: georgosn@yahoo.com QAContact: jsrain@novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.6) Gecko/20100626 SUSE/3.6.6-1.2 Firefox/3.6.6 Dear all, I'm trying to establish NFS mounts for my SOHO NAS 500 as I used to with other versions of OpenSuse. I go to Yast, I find my SOHO server and my exported directory. I put rw for options and Add it to the list. When I exit NFS module (during Start services) it takes a long time and then I get the following from Yast in a pop up: YaST got signal 11 at YCP file Service.ycp:77 /sbin/yast2: line 399: 13095 Segmentation fault $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS I don't know much but Segmentation fault seems a bug and couldn't find the line number on any other bug. my system is an AMD 905e with 4GB RAM. I use the 64bit of OpenSuse 11.3 Final. I didn't have the problem with 11.2. Reproducible: Always Steps to Reproduce: 1.Go to Yast NFS module 2.add a new NFS mount 3.click ok Actual Results: Pop up with: YaST got signal 11 at YCP file Service.ycp:77 /sbin/yast2: line 399: 13095 Segmentation fault $ybindir/y2base $module "$@" "$SELECTED_GUI" $Y2_GEOMETRY $Y2UI_ARGS Expected Results: Mounted NFS resource -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=623282
http://bugzilla.novell.com/show_bug.cgi?id=623282#c
yang xiaoyu
http://bugzilla.novell.com/show_bug.cgi?id=623282
http://bugzilla.novell.com/show_bug.cgi?id=623282#c2
Jiri Srain
http://bugzilla.novell.com/show_bug.cgi?id=623282
http://bugzilla.novell.com/show_bug.cgi?id=623282#c3
--- Comment #3 from nikolaos georgosopoulos
http://bugzilla.novell.com/show_bug.cgi?id=623282
http://bugzilla.novell.com/show_bug.cgi?id=623282#c4
nikolaos georgosopoulos
http://bugzilla.novell.com/show_bug.cgi?id=623282
http://bugzilla.novell.com/show_bug.cgi?id=623282#c5
Jiri Srain
http://bugzilla.novell.com/show_bug.cgi?id=623282
http://bugzilla.novell.com/show_bug.cgi?id=623282#c6
--- Comment #6 from nikolaos georgosopoulos
http://bugzilla.novell.com/show_bug.cgi?id=623282
http://bugzilla.novell.com/show_bug.cgi?id=623282#c7
nikolaos georgosopoulos
http://bugzilla.novell.com/show_bug.cgi?id=623282
http://bugzilla.novell.com/show_bug.cgi?id=623282#c8
Jiri Srain
http://bugzilla.novell.com/show_bug.cgi?id=623282
http://bugzilla.novell.com/show_bug.cgi?id=623282#c9
Martin Vidner
why is the log missing the backtrace in case of segfault? It is not missing, it is in Yast_logs/signal in comment 4.
Thomas, here is a part of the backtrace, perhaps it is related to the file selection dialog: /usr/lib64/libQtDBus.so.4(+0x42855)[0x7fcb14c19855] /usr/lib64/libQtCore.so.4(QMetaObject::activate(QObject*, QMetaObject const*, int, void**)+0x25f)[0x7fcb1b68ca1f] /usr/lib64/libQtCore.so.4(QObject::destroyed(QObject*)+0x2f)[0x7fcb1b68cddf] /usr/lib64/libQtCore.so.4(QObject::~QObject()+0xa5)[0x7fcb1b68db85] /usr/lib64/libkio.so.5(KIO::Scheduler::~Scheduler()+0x9)[0x7fcb16befe59] -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=623282
https://bugzilla.novell.com/show_bug.cgi?id=623282#c10
Thomas Göttlicher
participants (1)
-
bugzilla_noreply@novell.com