July 2013 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 816791] New: ACPI Warning: SystemIO conflicts with Region
by bugzilla_noreply＠novell.com 20 Jul '13

20 Jul '13

https://bugzilla.novell.com/show_bug.cgi?id=816791 https://bugzilla.novell.com/show_bug.cgi?id=816791#c0 Summary: ACPI Warning: SystemIO conflicts with Region Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: m7979(a)hotmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:19.0) Gecko/20100101 Firefox/19.0 Asus P7H55-M/USB3 motherboard with dual ethernet controllers (rtl8110/8169 & Intel e1000) dmesg reports a failure starting this device. (This worked ok on openSUSE 12.2). RTL port works ok, Intel port does not work (and is the prefered port since it has better performance). lsmod shows e1000e driver gets loaded. Networking fails to work if cable is connected to the e1000 port. >From dmesg: [ 3.222249] e1000e: Intel(R) PRO/1000 Network Driver - 2.1.4-k [ 3.222251] e1000e: Copyright(c) 1999 - 2012 Intel Corporation. [ 3.222275] e1000e 0000:00:19.0: setting latency timer to 64 [ 3.222335] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservati ve mode [ 3.222371] e1000e 0000:00:19.0: irq 66 for MSI/MSI-X [ 3.227355] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded [ 3.227390] r8169 0000:08:02.0 (unregistered net_device): not PCI Express [ 3.227605] r8169 0000:08:02.0 eth0: RTL8169sc/8110sc at 0xffffc90007a96000, f4:6d:04:b0:5c:6d, XID 18000000 IRQ 16 [ 3.227607] r8169 0000:08:02.0 eth0: jumbo features [frames: 7152 bytes, tx checksumming: ok] [ 3.481572] e1000e 0000:00:19.0 eth1: (PCI Express:2.5GT/s:Width x1) f4:6d:04:b0:54:94 [ 3.481575] e1000e 0000:00:19.0 eth1: Intel(R) PRO/1000 Network Connection [ 3.481610] e1000e 0000:00:19.0 eth1: MAC: 10, PHY: 11, PBA No: FFFFFF-0FF [ 3.481690] mei 0000:00:16.0: setting latency timer to 64 [ 3.481744] mei 0000:00:16.0: irq 67 for MSI/MSI-X [ 3.488521] ACPI Warning: 0x0000000000000540-0x000000000000054f SystemIO conflicts with Region \_SB_.PCI0.SBRG.GPBX 1 (20120913/utaddress-251) [ 3.488527] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 3.488529] ACPI Warning: 0x0000000000000530-0x000000000000053f SystemIO conflicts with Region \_SB_.PCI0.SBRG.GPBX 1 (20120913/utaddress-251) [ 3.488531] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 3.488533] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \_SB_.PCI0.SBRG.GPBX 1 (20120913/utaddress-251) [ 3.488535] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver Same issue reported here: https://bugzilla.redhat.com/show_bug.cgi?id=849773 Reproducible: Always Steps to Reproduce: 1.connect network cable to e1000 port 2.boot system 3.find error messages (above) in dmesg. 4. network does not connect Actual Results: No network connectivity -- 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.

1 4

[Bug 805300] New: X server locks up after a random time of gaming.
by bugzilla_noreply＠novell.com 20 Jul '13

20 Jul '13

https://bugzilla.novell.com/show_bug.cgi?id=805300 https://bugzilla.novell.com/show_bug.cgi?id=805300#c0 Summary: X server locks up after a random time of gaming. Classification: openSUSE Product: openSUSE 12.3 Version: RC 1 Platform: x86-64 OS/Version: SUSE Other Status: NEW Severity: Critical Priority: P5 - None Component: X.Org AssignedTo: bnc-team-xorg-bugs(a)forge.provo.novell.com ReportedBy: novell.com(a)marekpasnikowski.name QAContact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- Created an attachment (id=526135) --> (http://bugzilla.novell.com/attachment.cgi?id=526135) dmesg output User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/534.34 (KHTML, like Gecko) rekonq/2.1 Safari/534.34 I use FirePro V3700. glxinfo | grep OpenGL OpenGL vendor string: X.Org OpenGL renderer string: Gallium 0.4 on AMD RV620 OpenGL version string: 3.0 Mesa 9.0.2 OpenGL shading language version string: 1.30 After a random time (it can be quite long) X server locks up and display starts flickering. Reproducible: Always Steps to Reproduce: Play a 3D game on Radeon V3700. Actual Results: Relevant snippet of dmesg: [ 3630.449209] radeon 0000:02:00.0: GPU lockup CP stall for more than 10000msec [ 3630.449223] radeon 0000:02:00.0: GPU lockup (waiting for 0x0000000000035101 last fence id 0x0000000000035100) [ 3630.450306] radeon 0000:02:00.0: Saved 185 dwords of commands on ring 0. [ 3630.450316] radeon 0000:02:00.0: GPU softreset: 0x00000003 [ 3630.462480] radeon 0000:02:00.0: R_008010_GRBM_STATUS = 0xA0003030 [ 3630.462483] radeon 0000:02:00.0: R_008014_GRBM_STATUS2 = 0x00000003 [ 3630.462484] radeon 0000:02:00.0: R_000E50_SRBM_STATUS = 0x200000C0 [ 3630.462486] radeon 0000:02:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 [ 3630.462488] radeon 0000:02:00.0: R_008678_CP_STALLED_STAT2 = 0x00000000 [ 3630.462490] radeon 0000:02:00.0: R_00867C_CP_BUSY_STAT = 0x00020186 [ 3630.462492] radeon 0000:02:00.0: R_008680_CP_STAT = 0x80028645 [ 3630.462494] radeon 0000:02:00.0: R_008020_GRBM_SOFT_RESET=0x00007FEE [ 3630.477453] radeon 0000:02:00.0: R_008020_GRBM_SOFT_RESET=0x00000001 [ 3630.492412] radeon 0000:02:00.0: R_008010_GRBM_STATUS = 0xA0003030 [ 3630.492414] radeon 0000:02:00.0: R_008014_GRBM_STATUS2 = 0x00000003 [ 3630.492416] radeon 0000:02:00.0: R_000E50_SRBM_STATUS = 0x200080C0 [ 3630.492418] radeon 0000:02:00.0: R_008674_CP_STALLED_STAT1 = 0x00000000 [ 3630.492420] radeon 0000:02:00.0: R_008678_CP_STALLED_STAT2 = 0x00000000 [ 3630.492421] radeon 0000:02:00.0: R_00867C_CP_BUSY_STAT = 0x00000000 [ 3630.492423] radeon 0000:02:00.0: R_008680_CP_STAT = 0x80100000 [ 3630.496610] radeon 0000:02:00.0: GPU reset succeeded, trying to resume [ 3630.513495] [drm] probing gen 2 caps for device 10de:3e8 = 1/0 [ 3630.515180] [drm] PCIE GART of 512M enabled (table at 0x0000000000040000). [ 3630.515218] radeon 0000:02:00.0: WB disabled [ 3630.515222] radeon 0000:02:00.0: fence driver on ring 0 use gpu addr 0x0000000010000004 and cpu addr 0xffff880035232004 [ 3630.515224] radeon 0000:02:00.0: fence driver on ring 3 use gpu addr 0x0000000010000c0c and cpu addr 0xffff880035232c0c [ 3630.546315] [drm] ring test on 0 succeeded in 1 usecs [ 3630.546371] [drm] ring test on 3 succeeded in 1 usecs [ 3630.553355] [drm] ib test on ring 0 succeeded in 0 usecs [ 3630.553392] [drm] ib test on ring 3 succeeded in 1 usecs [ 3641.023715] radeon 0000:02:00.0: GPU lockup CP stall for more than 10000msec [ 3641.023729] radeon 0000:02:00.0: GPU lockup (waiting for 0x0000000000035109 last fence id 0x0000000000035105) [ 3641.254434] radeon 0000:02:00.0: couldn't schedule ib [ 3641.254446] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB ! [ 3641.254858] radeon 0000:02:00.0: couldn't schedule ib [ 3641.254865] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB ! [ 3641.255420] radeon 0000:02:00.0: couldn't schedule ib [ 3641.255428] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB ! [ 3641.256433] radeon 0000:02:00.0: couldn't schedule ib [ 3641.256441] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB ! [ 3641.257095] radeon 0000:02:00.0: couldn't schedule ib [ 3641.257105] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB ! [ 3641.258179] radeon 0000:02:00.0: couldn't schedule ib [ 3641.258190] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB ! [ 3641.258743] radeon 0000:02:00.0: couldn't schedule ib [ 3641.258750] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB ! [ 3641.260073] radeon 0000:02:00.0: couldn't schedule ib [ 3641.260081] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB ! [ 3641.262625] radeon 0000:02:00.0: couldn't schedule ib [ 3641.262636] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB ! [ 3641.262874] radeon 0000:02:00.0: couldn't schedule ib [ 3641.262879] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB ! [ 3641.263180] radeon 0000:02:00.0: couldn't schedule ib [ 3641.263186] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB ! [ 3641.263459] radeon 0000:02:00.0: couldn't schedule ib [ 3641.263465] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB ! [ 3641.270927] radeon 0000:02:00.0: couldn't schedule ib [ 3641.270941] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB ! [ 3641.277794] radeon 0000:02:00.0: couldn't schedule ib [ 3641.277806] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB ! [ 3644.781769] radeon 0000:02:00.0: couldn't schedule ib [ 3644.781781] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB ! [ 3644.842193] radeon 0000:02:00.0: couldn't schedule ib [ 3644.842200] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB ! [ 3644.842608] radeon 0000:02:00.0: couldn't schedule ib [ 3644.842611] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB ! [ 3644.848181] radeon 0000:02:00.0: couldn't schedule ib [ 3644.848189] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB ! [ 3649.445044] type=1400 audit(1361556808.900:44): apparmor="DENIED" operation="change_hat" info="unconfined" error=-1 pid=740 comm="login" [ 3653.936506] radeon 0000:02:00.0: couldn't schedule ib [ 3653.936513] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB ! [ 3653.937310] radeon 0000:02:00.0: couldn't schedule ib [ 3653.937326] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB ! [ 3653.938382] radeon 0000:02:00.0: couldn't schedule ib [ 3653.938392] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB ! [ 3653.938813] radeon 0000:02:00.0: couldn't schedule ib [ 3653.938820] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB ! [ 3653.940005] radeon 0000:02:00.0: couldn't schedule ib [ 3653.940014] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB ! [ 3653.941092] radeon 0000:02:00.0: couldn't schedule ib [ 3653.941104] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB ! [ 3653.942288] radeon 0000:02:00.0: couldn't schedule ib [ 3653.942301] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB ! [ 3653.942902] radeon 0000:02:00.0: couldn't schedule ib [ 3653.942910] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB ! [ 3653.947214] radeon 0000:02:00.0: couldn't schedule ib [ 3653.947226] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB ! [ 3653.952740] radeon 0000:02:00.0: couldn't schedule ib [ 3653.952754] [drm:radeon_cs_ib_chunk] *ERROR* Failed to schedule IB ! Expected Results: Nothing, crash free gaming. I am willing to cooperate in order to solve this problem. With instructions, I can do any all test needed. Also: uname -a Linux hirager-5.site 3.8.0-2-desktop #1 SMP PREEMPT Wed Feb 20 16:06:07 UTC 2013 (86d0404) x86_64 x86_64 x86_64 GNU/Linux The kernel is from one of official OpenSUSE repos (not sure which one anymore, had HEAD in URL or name.). I updated it with hope of getting rid of the crashes. I didn't downgrade because of its radeon improvements. -- 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.

1 11

[Bug 794235] New: Update not working except in failsafe mode
by bugzilla_noreply＠novell.com 19 Jul '13

19 Jul '13

https://bugzilla.novell.com/show_bug.cgi?id=794235 https://bugzilla.novell.com/show_bug.cgi?id=794235#c0 Summary: Update not working except in failsafe mode Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: i586 OS/Version: openSUSE 11.4 Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: roger.luedecke(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:16.0) Gecko/20100101 Firefox/16.0 WHen running update via zypper, YaST or PackageKit it freezes. Under zypper it shows that it always chokes on certain same packages. It will download the RPM up to 72 or 98 percent and go no further. Attempting to download manually via Firefox or wget fails entirely. This affects installation of software as well. After researching similar issues, I found it could be run properly only when openSUSE is booted in failsafe mode. 01:0c.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev 78) Reproducible: Always I suspect this problem has to do with the driver for the hardware NIC. -- 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.

1 4

[Bug 821014] New: [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -35!
by bugzilla_noreply＠novell.com 19 Jul '13

19 Jul '13

https://bugzilla.novell.com/show_bug.cgi?id=821014 https://bugzilla.novell.com/show_bug.cgi?id=821014#c0 Summary: [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -35! Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: X.Org AssignedTo: bnc-team-xorg-bugs(a)forge.provo.novell.com ReportedBy: ohering(a)suse.com QAContact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: Outsourced Testing Blocker: --- I have a dell optiplex 980 which has this video card: 01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RV620 LE [Radeon HD 3450] 01:00.0 0300: 1002:95c5 (prog-if 00 [VGA controller]) Subsystem: 1028:0342 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 46 Region 0: Memory at e0000000 (64-bit, prefetchable) [size=256M] Region 2: Memory at f7df0000 (64-bit, non-prefetchable) [size=64K] Region 4: I/O ports at dc00 [size=256] Expansion ROM at f7e00000 [disabled] [size=128K] Capabilities: <access denied> Kernel driver in use: radeon In KDE I accidently selected suspend-to-ram. The system went to sleep and came back fine. Except that the display was broken. There was a flooding of this in dmesg: [drm:radeon_cs_ioctl] *ERROR* Failed to parse relocation -35! I build my own xf86-video-ati-7.1.0 from project="X11:XOrg", which fixed the suspend to ram for me. Google indicates that this happens also with just switching VTs. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1085751 https://bugzilla.redhat.com/show_bug.cgi?id=901984 Maybe 12.3 can get a newer (or fixed) xf86-video-ati package to fix this. -- 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.

1 4

[Bug 806568] New: zypp doesn't make use of set packagesdir
by bugzilla_noreply＠novell.com 19 Jul '13

19 Jul '13

https://bugzilla.novell.com/show_bug.cgi?id=806568 https://bugzilla.novell.com/show_bug.cgi?id=806568#c0 Summary: zypp doesn't make use of set packagesdir Classification: openSUSE Product: openSUSE 12.3 Version: RC 1 Platform: i586 OS/Version: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: ma(a)suse.com ReportedBy: lmuelle(a)suse.com QAContact: jsrain(a)suse.com Found By: Development Blocker: No I've tried to use packagesdir = /home/cache/zypp/packages/ as /var/cache/zypp/packages/ didn't had enough space left. Independent of the applied setting calling zypper dup downloaded the RPM files to /var/cache/zypp/packages/ -- 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.

1 11

[Bug 804219] New: zypper: changing arch of package impossible
by bugzilla_noreply＠novell.com 19 Jul '13

19 Jul '13

https://bugzilla.novell.com/show_bug.cgi?id=804219 https://bugzilla.novell.com/show_bug.cgi?id=804219#c0 Summary: zypper: changing arch of package impossible Classification: openSUSE Product: openSUSE 12.3 Version: RC 1 Platform: x86-64 OS/Version: Linux Status: NEW Severity: Minor Priority: P5 - None Component: libzypp AssignedTo: zypp-maintainers(a)forge.provo.novell.com ReportedBy: jengelh(a)inai.de QAContact: qa-bugs(a)suse.de Found By: Beta-Customer Blocker: --- Created an attachment (id=525034) --> (http://bugzilla.novell.com/attachment.cgi?id=525034) /var/log/zyp* after zypper in --debug-solver - (create a directory first before extraction) Specifying the arch during installation of a NEW package seems possible in zypper, # zypper in -v openobex.i586 Loading repository data... Reading installed packages... 'openobex.i586' not found in package names. Trying capabilities. Resolving package dependencies... The following NEW packages are going to be installed: libopenobex1 1.5-13.1.2 i586 base openSUSE libusb-0_1-4-32bit 0.1.13-21.1.2 x86_64 base openSUSE 2 new packages to install. Overall download size: 46.2 KiB. After the operation, additional 106.5 KiB will be used. Continue? [y/n/?] (y): ^C (Is this the correct syntax to specify a specific arch?) However, arch changing for an existing package seems not implemented any longer (since bnc#632743), # zypper in MozillaFirefox.i586 Loading repository data... Reading installed packages... Resolving package dependencies... Nothing to do. -- 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.

1 7

[Bug 727997] New: fuser -n tcp <socket> fails on open network tcp socket
by bugzilla_noreply＠novell.com 19 Jul '13

19 Jul '13

https://bugzilla.novell.com/show_bug.cgi?id=727997 https://bugzilla.novell.com/show_bug.cgi?id=727997#c0 Summary: fuser -n tcp <socket> fails on open network tcp socket Classification: openSUSE Product: openSUSE 12.1 Version: Beta 1 Platform: VMWare OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: d.a.van.delft(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; nl; rv:1.9.2.23) Gecko/20110920 SUSE/3.6.23-0.2.1 Firefox/3.6.23 Doesn't happen always. Sometimes after the system has been up for a while, fuser stops working correctly: srv096:~ # netstat -l -n -t -p | grep 7002 tcp 0 0 0.0.0.0:7002 0.0.0.0:* LISTEN 2026/java srv096:~ # /bin/fuser -n tcp 7002 srv096:~ # /bin/fuser 7002/tcp srv096:~ # /usr/bin/lsof -i tcp:7002 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME java 2026 acceptatie 71u IPv4 15182 0t0 TCP *:afs3-prserver (LISTEN) Both netstat and lsof show the 7002 socket present, but fuser returns none, and, not shown here, with exit status 1. Reproducible: Sometimes Steps to Reproduce: 1. 2. 3. -- 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.

1 42

[Bug 744665] New: xemacs barfs on ycp files
by bugzilla_noreply＠novell.com 19 Jul '13

19 Jul '13

https://bugzilla.novell.com/show_bug.cgi?id=744665 https://bugzilla.novell.com/show_bug.cgi?id=744665#c0 Summary: xemacs barfs on ycp files Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: marc(a)marcchamberlin.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:9.0) Gecko/20100101 Firefox/9.0 When opening a .ycp file with xemacs, I often get the following complaint - (1) (local-variables/warning) Error in File local-variables: Symbol's function definition is void: ycp-mode Backtrace follows: ycp-mode() # bind (val var) hack-one-local-variable(mode ycp) # bind (val var str continue prefix prefixlen suffix start enable-local-eval) # (unwind-protect ...) # bind (force) hack-local-variables-last-page(nil) # bind (force) hack-local-variables(nil) #<compiled-function nil "...(5)" [find-file hack-local-variables] 2>() # (unwind-protect ...) call-with-condition-handler(#<compiled-function (__call_trapping_errors_arg__) "...(17)" [__call_trapping_errors_arg__ errstr error-message-string lwarn local-variables warning "Error in %s: %s\n\nBacktrace follows:\n\n%s" "File local-variables" backtrace-in-condition-handler-eliminating-handler] 8> #<compiled-function nil "...(5)" [find-file hack-local-variables] 2>) # (condition-case ... . ((error))) # bind (find-file) normal-mode(t) # bind (nomodes after-find-file-from-revert-buffer noauto warn error) after-find-file(nil t) # (unwind-protect ...) # bind (inhibit-read-only error number truename rawfile nowarn filename buf) find-file-noselect-1(#<buffer "BootCommon.ycp"> "/home/marc/yast2/SuSE-Linux-11_4-Branch/bootloader/src/modules/BootCommon.ycp" nil nil "/home/marc/yast2/SuSE-Linux-11_4-Branch/bootloader/src/modules/BootCommon.ycp" (12033803 2066)) byte-code("..." [number truename rawfile nowarn filename buf set-buffer-major-mode find-file-noselect-1] 7) # (condition-case ... . ((t (byte-code "Â!Ã @ A\"" [buf data kill-buffer signal] 3)))) # bind (number truename buf wildcards rawfile nowarn filename) find-file-noselect("/home/marc/yast2/SuSE-Linux-11_4-Branch/bootloader/src/modules/BootCommon.ycp" nil nil nil) # bind (coding-system-for-read wildcards codesys filename) find-file("/home/marc/yast2/SuSE-Linux-11_4-Branch/bootloader/src/modules/BootCommon.ycp") # bind (dir file-count line end-of-options file-p arg tem) command-line-1() # bind (command-line-args-left) command-line() # (condition-case ... . ((t (byte-code " Â" [error-data data nil] 1)))) # bind (error-data) normal-top-level() # (condition-case ... . error) # (catch top-level ...) Reproducible: Sometimes Steps to Reproduce: 1.Open a .ycp file with xemacs 2. 3. Actual Results: see above Expected Results: Expect xemacs to handle ycp-mode. Emacs seems to do better, but not always clean either. -- 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.

1 5

[Bug 799739] New: Emacs cannot type in italics.
by bugzilla_noreply＠novell.com 19 Jul '13

19 Jul '13

https://bugzilla.novell.com/show_bug.cgi?id=799739 https://bugzilla.novell.com/show_bug.cgi?id=799739#c0 Summary: Emacs cannot type in italics. Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: i686 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: kete(a)ninthfloor.org QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:18.0) Gecko/20100101 Firefox/18.0 Somewhere in the site lisp, italics are disabled. Italicizing words underlines them instead. Incidentally, underlining words also underlines them as well. Reproducible: Always Steps to Reproduce: 1. Find a file. 2. Select text. 3. Press M-o i. In org-mode, type slashes around text. Actual Results: The text will be underlined instead. Expected Results: italicized text If you start Emacs with site lisp disabled (`emacs -Q' in a terminal), then italics will work. Site lisp is a distribution's custom files in the /usr directory. -- 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.

1 4

[Bug 820876] New: libvirtd crashes while starting a Xen VM
by bugzilla_noreply＠novell.com 19 Jul '13

19 Jul '13

https://bugzilla.novell.com/show_bug.cgi?id=820876 https://bugzilla.novell.com/show_bug.cgi?id=820876#c0 Summary: libvirtd crashes while starting a Xen VM Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: Other OS/Version: openSUSE 12.3 Status: NEW Severity: Major Priority: P5 - None Component: Xen AssignedTo: jdouglas(a)suse.com ReportedBy: rschaffner(a)novell.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- While starting a openSUSE VM, I can repeatedly cause libvirtd to crash. I was originally doing this with an opensuse 12.1 VM but after upgrading the VM to opensuse 12.3, I was still able to cause libvirtd to crash. I've since done a fresh openSUSE 12.2 install (didn't have a 12.3 iso handy) and I can still cause the crash. homevhst01:~ # rclibvirtd status Checking status of libvirtd running libvirtd.service - Virtualization daemon Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled) Active: active (running) since Mon, 2013-05-20 23:11:52 CDT; 16min ago Main PID: 9563 (libvirtd) CGroup: name=systemd:/system/libvirtd.service ├ 2742 /usr/lib/xen/bin/qemu-system-i386 -xen-domid 1 -chardev socket,id=libxl-cmd,... ├ 9563 /usr/sbin/libvirtd --listen ├ 14586 /usr/lib/xen/bin/qemu-system-i386 -xen-domid 5 -chardev socket,id=libxl-cmd,... ├ 17143 /usr/lib/xen/bin/qemu-system-i386 -xen-domid 6 -chardev socket,id=libxl-cmd,... └ 17636 /usr/lib/xen/bin/qemu-system-i386 -xen-domid 10 -chardev socket,id=libxl-cmd... May 20 23:11:52 homevhst01 libvirtd[9563]: [499B blob data] May 20 23:11:52 homevhst01 libvirtd[9563]: [499B blob data] May 20 23:11:52 homevhst01 libvirtd[9563]: unknown OS type hvm May 20 23:28:22 homevhst01 tapdisk2[9333]: received 'pid' message (uuid = 0) May 20 23:28:22 homevhst01 tapdisk2[9333]: sending 'pid response' message (uuid = 0) May 20 23:28:22 homevhst01 tapdisk2[9333]: received 'list' message (uuid = 65535) May 20 23:28:22 homevhst01 tapdisk2[9333]: sending 'list response' message (uuid = 65535) May 20 23:28:22 homevhst01 tapdisk2[9333]: sending 'list response' message (uuid = 65535) May 20 23:28:22 homevhst01 tapdisk2[9333]: received 'close' message (uuid = 0) May 20 23:28:22 homevhst01 tapdisk2[9333]: closed image /srv/tmpisos/openSUSE-12.2-DVD-x86_64.iso (...: 0) homevhst01:~ # virsh start source error: Failed to start domain source error: End of file while reading data: Input/output error error: Failed to reconnect to the hypervisor homevhst01:~ # rclibvirtd status Checking status of libvirtd dead libvirtd.service - Virtualization daemon Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled) Active: failed (Result: signal) since Mon, 2013-05-20 23:29:12 CDT; 4s ago Process: 9563 ExecStart=/usr/sbin/libvirtd $LIBVIRTD_ARGS (code=killed, signal=SEGV) CGroup: name=systemd:/system/libvirtd.service ├ 2742 /usr/lib/xen/bin/qemu-system-i386 -xen-domid 1 -chardev socket,id=libxl-cmd,... ├ 10294 tapdisk2 ├ 10317 /usr/lib/xen/bin/qemu-system-i386 -xen-domid 21 -chardev socket,id=libxl-cmd... ├ 14586 /usr/lib/xen/bin/qemu-system-i386 -xen-domid 5 -chardev socket,id=libxl-cmd,... ├ 17143 /usr/lib/xen/bin/qemu-system-i386 -xen-domid 6 -chardev socket,id=libxl-cmd,... └ 17636 /usr/lib/xen/bin/qemu-system-i386 -xen-domid 10 -chardev socket,id=libxl-cmd... May 20 23:29:12 homevhst01 libvirtd[9563]: 2013-05-21 04:29:12.286+00009563: debug : virEventPollDi...w=10 May 20 23:29:12 homevhst01 libvirtd[9563]: 2013-05-21 04:29:12.286+00009563: debug : virEventPollDi...w=11 May 20 23:29:12 homevhst01 libvirtd[9563]: 2013-05-21 04:29:12.286+00009563: debug : virEventPollDi...w=12 May 20 23:29:12 homevhst01 libvirtd[9563]: 2013-05-21 04:29:12.286+00009563: debug : virEventPollDi...w=13 May 20 23:29:12 homevhst01 libvirtd[9563]: 2013-05-21 04:29:12.286+00009563: debug : virEventPollDi...w=14 May 20 23:29:12 homevhst01 libvirtd[9563]: 2013-05-21 04:29:12.286+00009563: debug : virEventPollDi...w=19 May 20 23:29:12 homevhst01 libvirtd[9563]: 2013-05-21 04:29:12.286+00009563: debug : virEventPollDi...w=20 May 20 23:29:12 homevhst01 libvirtd[9563]: 2013-05-21 04:29:12.287+00009563: debug : virEventPollDi...ts=1 May 20 23:29:12 homevhst01 libvirtd[9563]: /lib64/libpthread.so.0(+0x7e0f)[0x7fcf6d605e0f] May 20 23:29:12 homevhst01 libvirtd[9563]: ====== end of log ===== homevhst01:~ # The server homevhst01 is openSUSE 12.3 running the latest updates. homevhst01:~ # rpm -qa | grep virt virt-manager-0.9.4-4.3.1.x86_64 python-virtinst-0.600.3-2.2.1.x86_64 virt-utils-1.1.9-6.1.1.x86_64 libvirt-1.0.2-1.3.1.x86_64 libvirt-client-1.0.2-1.3.1.x86_64 libvirt-python-1.0.2-1.3.1.x86_64 virt-viewer-0.5.4-4.1.1.x86_64 homevhst01:~ # rpm -qa | grep -i xen xen-kmp-desktop-4.2.1_12_k3.7.10_1.1-1.8.1.x86_64 kernel-xen-3.7.10-1.4.1.x86_64 xen-tools-4.2.1_12-1.8.1.x86_64 kernel-xen-3.7.10-1.1.1.x86_64 xen-doc-pdf-4.2.1_12-1.8.1.x86_64 xen-libs-4.2.1_12-1.8.1.x86_64 xen-4.2.1_12-1.8.1.x86_64 patterns-openSUSE-xen_server-12.3-7.10.1.x86_64 xen-doc-html-4.2.1_12-1.8.1.x86_64 homevhst01:~ # This only seems to happen on my openSUSE VMs. I run several SLES 11 based VMs that don't have this problem. After libvirtd crashed, I can see the VM under xl. Most of the time it is in a paused state and I can use "xl unpause" to start the VM. Sometimes the VM has actually started. homevhst01:~ # xl list source Name ID Mem VCPUs State Time(s) source 21 768 1 --p--- 0.0 homevhst01:~ # xl unpause source homevhst01:~ # xl list source Name ID Mem VCPUs State Time(s) source 21 768 1 -b---- 0.8 homevhst01:~ # -- 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.

1 7