|
Bugzilla – Full Text Bug Listing |
| Summary: | yast2 inst_source segfaults | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.2 | Reporter: | Kevin Ivory <Ivory> |
| Component: | libzypp | Assignee: | Marius Tomaschewski <mt> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Stanislav Visnovsky <visnov> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | andreas.hanke, jstalnak, schubi |
| Version: | Beta 1 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
/var/log/YaST2/*
gzipped gdb output gzipped strace output |
||
|
Description
Kevin Ivory
2006-11-01 17:09:53 UTC
Created attachment 103349 [details]
/var/log/YaST2/*
This sounds like deep inside libzypp. -> zypp maintainers I guess thats fixed already. Marius ? Yes, the dbus_connection_close() calls are fixed (removed) in zypp SVN head; see also Bug #216035. But I don't know where the SEGV is from - can't see it in the log (AFAIK they're logged by genericfrontend.cc signal handler) or reproduce it. Can you try to reproduce it and create a core file? Start YaST2 using this commands: $ ulimit -c unlimited $ /sbin/yast2 After a SEGV there should be a 'core' (or 'core.*') file. Please use gdb to read out the core file: $ gdb --core=./core /sbin/yast2 Type the commands "where" and "quit" in gdb and provide the output. See also: http://en.opensuse.org/Bugs:An_application_crashed The SEGV is reproducible on my system. The output of "strace yast inst_source" and gdb/where with core follow. Created attachment 104016 [details]
gzipped gdb output
Created attachment 104017 [details]
gzipped strace output
Upgraded from 10.2 Alpha2 to Beta1 yesterday afternoon and YAST software modules are hosed. I get no error dialogs when using Yast (the KDE gui) at all -- the modules start then they go away without error reporting. If I run /sbin/yast from konsole, then I see the same error reported here for the Installation Source module. Also, I get a seg fault when trying to run the Software Management module: /sbin/yast: line 267: 22600 Segmentation fault $ybindir/y2base menu clncurses $NCTHREADS. This all, of course, worked in 10.2 Alpha 2. Let me know if I can provide you any data to use in trouble-shooting (i.e., would it be helpgul to have the core information from my install to go with what's already been uploaded? I'm sorry -- I didn't say that right <grrr>. I get no errors running the kde gui from within kde. If I run the gui with /sbin/yast2, I get the dcop error for the installation-source module (reported as console stderr output I think): . Command: /sbin/yast2 inst_source & Applications must not close shared connections - see dbus_connection_close() docs. This is a bug in the application. Applications must not close shared connections - see dbus_connection_close() docs. This is a bug in the application. Segmentation fault at /usr/share/YaST2/clients/inst_source.ycp:542 /sbin/yast2: line 267: 24214 Segmentation fault $ybindir/y2base $module "$@" "$SELECTED_GUI" "$Y2_GEOMETRY" $Y2QT_ARGS . If I run /sbin/yast (NOT the kde gui) I do not get the above error, I get the ncurses seg fault error and it's the same for both software management and installation source modules. should be fixed -- see Bug #216545 and #216035. *** This bug has been marked as a duplicate of bug 216545 *** |