https://bugzilla.novell.com/show_bug.cgi?id=810127 https://bugzilla.novell.com/show_bug.cgi?id=810127#c1 Thomas Fehr changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |lukebryan@bdumail.com AssignedTo|fehr@suse.com |yast2-maintainers@suse.de --- Comment #1 from Thomas Fehr 2013-03-19 10:45:01 UTC --- I do not see why this is assigned to me. I deoubt this hand is in any way storage related. Would bet it is another hang of "systemctl" call. Please provide YaST logs, see http://en.opensuse.org/openSUSE:Bugreport_YaST. In addition the output of "pstree -ap" would be very helpful. -- Configure bugmail: https://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=810127 https://bugzilla.novell.com/show_bug.cgi?id=810127#c3 --- Comment #3 from Lou Bryan 2013-03-20 15:20:00 UTC --- Created an attachment (id=530684) --> (http://bugzilla.novell.com/attachment.cgi?id=530684) requested pstree -ap > pstree The requested pstree -ap > pstree. You have both requested files now. I agree that this is probably not a storage issue, because I told it to use the whole disk. -- Configure bugmail: https://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=810127 https://bugzilla.novell.com/show_bug.cgi?id=810127#c5 John Tallett changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tallettjohn@yahoo.ca --- Comment #5 from John Tallett 2013-04-11 19:51:03 UTC --- I too am experiencing this identical problem on a 32 bit machine. If want more logs let me know and I'll send you mine. -- Configure bugmail: https://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=810127 https://bugzilla.novell.com/show_bug.cgi?id=810127#c Alberto Planas Dominguez changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard| | GOLD -- Configure bugmail: https://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=810127 https://bugzilla.novell.com/show_bug.cgi?id=810127#c7 --- Comment #7 from Lou Bryan 2013-11-20 17:37:43 UTC --- This is also happening trying to install openSUSE 13.1. I changed the version of the bug from 12.3 to 13.1. Is this going to be fixed? -- Configure bugmail: https://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=810127 https://bugzilla.novell.com/show_bug.cgi?id=810127#c9 Lukas Ocilka changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |lukebryan@bdumail.com AssignedTo|locilka@suse.com |tgoettlicher@suse.com --- Comment #9 from Lukas Ocilka 2013-11-22 15:46:58 UTC --- Obviously Yast, as checked in log, Yast was already running and showing Qt UI. Maybe Qt/X error? 2013-03-20 10:08:27 YQUI.cc(processCommandLineArgs):297 Qt argument: --fullscreen .. YQUI.cc(qMessageHandler):715 <libqt-warning> QLayout: Attempting to add QLayout "" to QFrame "work_area", which already has a layout YPushButton.cc(setFunctionKey):188 Guessing button role YOKButton for YPushButton "Next" at 0xb51cbf34 from function key F10 (here it shows Next button) YQUI.cc(qMessageHandler):715 <libqt-warning> YaST2: Fatal IO error: client killed YQUI.cc(qMessageHandler):730 Client killed. Possibly caused by X server shutdown or crash. YUI.cc(~YUITerminator):525 Shutting down UI YUI.cc(~YUI):88 shutdownThreads() was never called! YUI.cc(~YUI):89 shutting down now - this might segfault 2013-03-20 10:34:43 Trying again after reboot 2013-03-20 10:40:19 The same 2013-03-20 10:42:35 Again, etc. Thomas, any idea how to debug this issue? There is no Yast/y2base in pstree Lou, if you can reproduce it on 13.1, can you attach logs from 13.1, please? -- Configure bugmail: https://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=810127 https://bugzilla.novell.com/show_bug.cgi?id=810127#c11 --- Comment #11 from Spirit Steele 2014-01-13 11:34:38 UTC --- Created an attachment (id=574160) --> (http://bugzilla.novell.com/attachment.cgi?id=574160) hardware info My original comment got lost with the submission of the installation logs. I installed 13.1 from the downloaded DVD. There was speculation that this bug only occurs on AMD machines. Mine is an Intel machine. 12.3 ran fine (except for multimedia), but when I installed 13.1, it hung up at the system configuration. The last line on the ctrl-alt-f4(?) screen was "starting yast2" and the last line on the ctrl-alt-f10 screen was "could not load bcma firmware" or something very similar (I may have mixed up the letters bcma). I tried the network install, but got exactly the same results. I also tried installing different kernels(shot in the dark): pae, default and desktop, but it made no difference. In the end I aborted the system configuration, logged in as root, and completed it manually. There were additional problems setting up the network, but that doesn't belong here. I'm also submitting my hardware info in case it's relevant. Please mention it in the comments if you would like me to run through the installation again with the debug info turned on. -- Configure bugmail: https://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=810127 https://bugzilla.novell.com/show_bug.cgi?id=810127#c13 Martin Vidner changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium --- Comment #13 from Martin Vidner 2014-04-30 10:24:48 CEST --- The two reports that the installation hangs have very different causes. Spirit: the command that hangs is "ip link set wlp7s0 up"

From Hwinfo: 31: PCI 700.0: 0282 WLAN controller [Created at pci.319] Unique ID: eS2I.+_yeFkco2S1 Parent ID: Z7uZ.8ShE01IgZP4 SysFS ID: /devices/pci0000:00/0000:00:1c.3/0000:07:00.0 SysFS BusID: 0000:07:00.0 Hardware Class: network Model: "Broadcom WLAN controller" Vendor: pci 0x14e4 "Broadcom" Device: pci 0x4357 SubVendor: pci 0x105b "Foxconn International, Inc." SubDevice: pci 0xe021 Revision: 0x01 Driver: "bcma-pci-bridge" Driver Modules: "bcma" Device File: wlp7s0 Features: WLAN Memory Range: 0x80400000-0x80403fff (rw,non-prefetchable) IRQ: 19 (6881 events) HW Address: 18:f4:6a:6e:d7:0d Link detected: no WLAN channels: 1 2 3 4 5 6 7 8 9 10 11 WLAN frequencies: 2.412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 2.457 2.462 WLAN encryption modes: WEP40 WEP104 TKIP CCMP WLAN authentication modes: open sharedkey wpa-psk wpa-eap Module Alias: "pci:v000014E4d00004357sv0000105Bsd0000E021bc02sc80i00" Driver Info #0: Driver Status: bcma is active Driver Activation Cmd: "modprobe bcma" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #19 (PCI bridge)

Spirit, please split off a new bug (use the Copy to New button) and assign to ms@suse.com, maintainer of iputils.rpm -- Configure bugmail: https://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=810127 https://bugzilla.novell.com/show_bug.cgi?id=810127#c Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED AssignedTo|bnc-team-xorg-bugs@forge.pr |xorg-maintainer-bugs@forge. |ovo.novell.com |provo.novell.com -- Configure bugmail: https://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=810127 https://bugzilla.novell.com/show_bug.cgi?id=810127#c16 Martin Vidner changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mvidner@suse.com InfoProvider|mvidner@suse.com |lukebryan@bdumail.com --- Comment #16 from Martin Vidner 2014-04-30 14:20:16 CEST --- There are two reports in this bug, I am referring to the logs from comment 2: var/log/Xorg.0.log [ 23.878] (--) PCI:*(0:1:0:0) 1039:6300:1039:6300 rev 49, Mem @ 0xd0000000/134217728, 0xdfee0000/131072, I/O @ 0x0000ac00/128 and comment 3: systemd,1 showopts x11failsafe Well, I may have been too quick to label it an X problem. My reasoning was that if x11failsafe was needed for the system to run then probably X crashed without that parameter. But let's hear that from the reporter. Lou, is that the case? -- Configure bugmail: https://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=810127 https://bugzilla.novell.com/show_bug.cgi?id=810127#c18 --- Comment #18 from Stefan Dirsch 2014-04-30 12:51:17 UTC --- Speaking about the SiS gfx card. So we found another hardware archaeologist, who would like to run a current OS on such a platform. Instead of trying to fix a driver for ancient hardware I suggest to give the reporter a way to somewhat still make use of this machine. Instead of selecting the failsafe boot entry adding x11failsafe plymouth.enable=0 vga=791 to the first regular boot entry should do the trick and enables a GUI in 1024x768@16bpp. The second report here is for a NVIDIA gfx card and is unrelated to the SiS X driver. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.