December 2013 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 855058] New: rsyslog 7.4.7 (v7-stable) maintenance release
by bugzilla_noreply＠novell.com 17 Dec '13

17 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=855058 https://bugzilla.novell.com/show_bug.cgi?id=855058#c0 Summary: rsyslog 7.4.7 (v7-stable) maintenance release Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: All OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: Andreas.Stieger(a)gmx.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:25.0) Gecko/20100101 Firefox/25.0 http://www.rsyslog.com/rsyslog-7-4-7-v7-stable-released/ We have just released 7.4.7 of the v7-stable branch. This is a bug-fixing release. Most importantly it fixes a bug that can lead to segfault on startup and several queue-related issues. V7.4 users are advised to update to this release. Changelog for 7.4.7 (v7-stable) Version 7.4.7 [v7.4-stable] 2013-12-10 bugfix: limiting queue disk space did not work properly queue.maxdiskspace actually initializes queue.maxfilesize total size of queue files was not checked against queue.maxdiskspace for disk assisted queues. Thanks to Karol Jurak for the patch. bugfix: linux kernel-like ratelimiter did not work properly with all inputs (for example, it did not work with imdup). The reason was that the PRI value was used, but that needed parsing of the message, which was done too late. bugfix: disk queues created files in wrong working directory if the $WorkDirectory was changed multiple times, all queues only used the last value set. bugfix: legacy directive $ActionQueueWorkerThreads was not honored bugfix: segfault on startup when certain script constructs are used e.g. "if not $msg …" bugfix: imuxsock: UseSysTimeStamp config parameter did not work correctly Thanks to Tomas Heinrich for alerting us and provinding a solution suggestion. bugfix: $SystemLogUseSysTimeStamp/$SystemLogUsePIDFromSystem did not work Thanks to Tomas Heinrich for the patch. improved checking of queue config parameters on startup bugfix: call to ruleset with async queue did not use the queue closes: http://bugzilla.adiscon.com/show_bug.cgi?id=443 bugfix: if imtcp is loaded and no listeners are configured (which is uncommon), rsyslog crashes during shutdown. Reproducible: Didn't try -- 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 851865] New: evolution-ews does not properly scan inbox on Exchange server
by bugzilla_noreply＠novell.com 17 Dec '13

17 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=851865 https://bugzilla.novell.com/show_bug.cgi?id=851865#c0 Summary: evolution-ews does not properly scan inbox on Exchange server Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Major Priority: P5 - None Component: Evolution AssignedTo: bnc-team-evolution(a)forge.provo.novell.com ReportedBy: psychedct(a)gmail.com QAContact: lakhil(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:25.0) Gecko/20100101 Firefox/25.0 After installing evolution-ews and properly setting up my Microsoft Exchange account in Gnome Online Accounts, I open Evolution and it connects to the Exchange server and begins scanning the Inbox. No errors are reported, but after it finishes, recent mail is missing. New messages are not retrieved. Reproducible: Always Steps to Reproduce: 1. install evolution-ews 2. setup Microsoft Exchange account in Gnome Online Accounts 3. start Evolution Actual Results: Only a partial list of email messages in Inbox is retrieved. Expected Results: Complete list of email messages and new messages should be available. See: http://forums.opensuse.org/english/get-technical-help-here/applications/492… After downloading and installing libgnutls 3.2.6 from Factory Evolution works as expected with my employer's Microsoft Exchange server. -- 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 2

[Bug 855052] New: Opensuse installer in Xen Guest incorrectly aligns 1st partition @ 2048, rather than fdisk's (minimum) default of 4096
by bugzilla_noreply＠novell.com 17 Dec '13

17 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=855052 https://bugzilla.novell.com/show_bug.cgi?id=855052#c0 Summary: Opensuse installer in Xen Guest incorrectly aligns 1st partition @ 2048, rather than fdisk's (minimum) default of 4096 Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: yast2-maintainers(a)suse.de ReportedBy: ar16(a)imapmail.org QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:26.0) Gecko/20100101 Firefox/26.0 @ 13.1 Xen Dom0 host, create LV install targets lvcreate -L 160M -n test_boot /dev/VG0 lvcreate -L 4G -n test_root /dev/VG0 lvcreate -L 512M -n test_swap /dev/VG0 insert opensuse 131 install iso (openSUSE-13.1-DVD-x86_64) edit Guest template for HVM vi template_131.cfg name = 'os131-template' builder = 'hvm' acpi = 1 apic = 1 boot = 'd' disk = [ 'phy:/dev/VG0/test_boot,hda,w', 'phy:/dev/VG0/test_swap,hdb,w', 'phy:/dev/VG0/test_root,hdc,w', 'phy:/dev/sr1,hdd:cdrom,r', ] vif = [ 'mac=00:16:3E:52:00:02, model=rtl8139, type=ioemu, bridge=br0, vifname=vif0',] vnc = 0 sdl = 0 stdvga = 1 serial = 'pty' ... launch the Guest xl create template.cfg @ vnc window, run OpenSUSE Installer, selectin custom partition, specifying target partitions, from above @ complete, Guest automatically shuts down relaunch Guest xl create template.cfg @ vnc window, continue with OpenSUSE Installer, 2nd pass, finish config. shutdown -h now @ Host, examine lvs | grep -i os131 | grep test test_boot VG0 -wi-a---- 160.00m test_root VG0 -wi-a---- 4.00g test_swap VG0 -wi-a---- 512.00m note that the created partitions are aligned at sector 2048 kpartx -av /dev/VG0/test__root add map VG0-test_root1 (253:10): 0 8386560 linear /dev/VG0/test_root 2048 kpartx -av /dev/VG0/test__boot add map VG0-test_boot1 (253:11): 0 325632 linear /dev/VG0/test_boot 2048 kpartx -av /dev/VG0/test__swap add map VG0-test_swap1 (253:12): 0 1046528 linear /dev/VG0/test_swap 2048 If you attempt to in-place grow any of those partitions using kpartx+fdisk, requiring partition reassignment, fdisk will default to a MINIMUM 1st sector alignment of 4096 -- 2048 is NOT an option. If 4096 is chosen for new partion, resulting copy will subsequently refuse to launch, as sector information between 2048 & 4096 has been lost/corrupted. Manually creating 4096-aligned partitions, and rsync'ing contents, allows a 'recovery' lvcreate -L 160M -n testNEW_boot /dev/VG0 lvcreate -L 4G -n testNEW_root /dev/VG0 lvcreate -L 512M -n testNEW_swap /dev/VG0 for each of testNEW_boot, testNEW_root, testNEW_swap fdisk /dev/VG0/XX <<EOF d n p 1 4096 a w EOF then kpartx -av /dev/VG0/testNEW_boot kpartx -av /dev/VG0/testNEW_root kpartx -av /dev/VG0/testNEW_swap mkfs.ext4 /dev/mapper/VG0-testNEW_boot1 mkfs.ext4 /dev/mapper/VG0-testNEW_root1 mkswap /dev/mapper/VG0-testNEW_swap1 kpartx -av /dev/VG0/test_boot kpartx -av /dev/VG0/test_root kpartx -av /dev/VG0/test_swap mount /dev/mapper/VG0-test_boot1 /mnt/testb mount /dev/mapper/VG0-test_root1 /mnt/testr mount /dev/mapper/VG0-testNEW_boot1 /mnt/testNEWb mount /dev/mapper/VG0-testNEW_root1 /mnt/testNEWr cd /mnt rsync -aHv /mnt/testb/ /mnt/testNEWb/ rsync -aHv /mnt/testr/ /mnt/testNEWb ... and launching 'newly-aligned' Guest now works Reproducible: Always 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 3

[Bug 853341] New: Invalid console screen resolution in installation boot
by bugzilla_noreply＠novell.com 17 Dec '13

17 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=853341 https://bugzilla.novell.com/show_bug.cgi?id=853341#c0 Summary: Invalid console screen resolution in installation boot Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: yast2-maintainers(a)suse.de ReportedBy: fpmse(a)bluewin.ch QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:25.0) Gecko/20100101 Firefox/25.0 Connected monitor has a maximal resolution of 1024x768. With the 13.1 installation DVD iso from here http://software.opensuse.org/131/en press F3, select '1024x768', 'Installation', after some seconds of boot process the resolution will be switched to a higher resolution than 1024x768, the monitor shows 'CANNOT DISPLAY THIS VIDEO MODE'. CPU: AMD Athlon XP 3000+ Video card: AMD/ATI Radeon 9200 SE Reproducible: Always -- 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 1

[Bug 853645] New: System soft locks when using AMD FirePro V3800 (Radeon)
by bugzilla_noreply＠novell.com 17 Dec '13

17 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=853645 https://bugzilla.novell.com/show_bug.cgi?id=853645#c0 Summary: System soft locks when using AMD FirePro V3800 (Radeon) Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: X.Org AssignedTo: bnc-team-xorg-bugs(a)forge.provo.novell.com ReportedBy: jpdrawneek(a)nationaltheatre.org.uk QAContact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/31.0.1650.57 Safari/537.36 Got a HP z210 Desktop with a V3800 Graphics Card. Worked perfectly with Xorg Radeon Drivers in OpenSuSE 12.1/12.2/12.3. Updated to 13.1 and the screen goes black and keyboard locks on boot. Boot into init 3 and system seems fine, run startx and the screen goes black and keyboard locks. Unsure if I can ssh into the box, need to test, but it does do ACPI power off so its not hard locked. Tried a LiveCD/USB but that too locked. Ideas on what to do next to help debug? Reproducible: Always Steps to Reproduce: 1.Have a V3800 card in system 2.Graphicly boot 3. Actual Results: Screen goes black and keyboard locks Expected Results: Graphical login displayed https://bugzilla.novell.com/show_bug.cgi?id=842806 Both cards seem to be "Redwood" chips, could be an issue with this family? -- 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 2

[Bug 846237] New: Computer hangs while booting from OS installed to USB drive
by bugzilla_noreply＠novell.com 17 Dec '13

17 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=846237 https://bugzilla.novell.com/show_bug.cgi?id=846237#c0 Summary: Computer hangs while booting from OS installed to USB drive Classification: openSUSE Product: openSUSE 13.1 Version: RC 1 Platform: i386 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader AssignedTo: jsrain(a)suse.com ReportedBy: smartcatxxx(a)yahoo.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Firefox/24.0 I have installed openSUSE 13.1 RC 1 to an external USB drive. The installation completed successfully, with no reported errors. When I rebooted the machine and selected in the BIOS to have it boot from the USB drive, the bootloader hangs. Booting in safe mode reveals that it cannot mount the / partition and just sits there and waits for it to show up. I have performed an identical installation using openSUSE 12.3 and that was successful and booted just fine. Hence, this is somethings specific to 13.1. Reproducible: Always Steps to Reproduce: 1. Old Pentium 4 desktop computer with 2 GB RAM, which can boot from USB. 2. Remove all hard drives (so they would not interfere with the installation) then connect 8GB USB stick 3. Install openSUSE to the USB. Partitioning: /dev/sda /dev/sda1 /boot /dev/sda2 swap /dev/sda3 / (root) 4. Chose grub as bootloader and select to install it to MBR. 5. Complete the installation. 6. Reboot the computer. It starts booting up to the point where it shows the standard black and green opensuse desktop background then nothing else happens. No menus and no mouse cursor show up, and the system does not take any keyboard input. Basically it's dead. I have booted again this time in failsafe mode, some text scrolls quickly on the screen and this is the last message before getting stuck: Waiting for device /dev/disk/by-id-usb/Generic_STORAGE_DEVICE_000000000272-0:0-part3 to appear: ............... Could not find /dev/disk/by-id-usb/Generic_STORAGE_DEVICE_000000000272-0:0-part3. Want me to fall back to /dev/disk/by-id-usb/Generic_STORAGE_DEVICE_000000000272-0:0-part3? (Y/n) Typing in Y or n does nothing. I have plugged the USB stick on 2 laptops, an old dual core Dell and a newer Dell laptop with UEFI, and again the bootloader gets stuck at the same point. Note, openSUSE 12.3 and XUbuntu 13.04 install and boot just fine, using the same installation procedure. Someone in the forums suggested that the 3.11 kernel may be the culprit. -- 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 758103] New: [Kernel:Head][pci/sdhci-pci] XPS15z card reader requires manual intervention to work
by bugzilla_noreply＠novell.com 17 Dec '13

17 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=758103 https://bugzilla.novell.com/show_bug.cgi?id=758103#c0 Summary: [Kernel:Head][pci/sdhci-pci] XPS15z card reader requires manual intervention to work Classification: openSUSE Product: openSUSE 12.1 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: crrodriguez(a)opensuse.org QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi: This is a follow up to an issue with the card reader of this laptop we discussed in the opensuse-kernel list a while ago, now with full info. The following card-reader 5: PCI 500.0: 0880 System peripheral [Created at pci.319] Unique ID: Ddhb.dfbfMGO0Ij9 Parent ID: QSNP.VdJa1LlJ33D SysFS ID: /devices/pci0000:00/0000:00:1c.4/0000:05:00.0 SysFS BusID: 0000:05:00.0 Hardware Class: unknown Model: "JMicron System peripheral" Vendor: pci 0x197b "JMicron Technology Corp." Device: pci 0x2392 SubVendor: pci 0x1028 "Dell" SubDevice: pci 0x0446 Revision: 0x30 Driver: "sdhci-pci" Driver Modules: "sdhci_pci" Memory Range: 0xf1900000-0xf19000ff (rw,non-prefetchable) IRQ: 16 (741 events) Module Alias: "pci:v0000197Bd00002392sv00001028sd00000446bc08sc80i00" Driver Info #0: Driver Status: sdhci_pci is active Driver Activation Cmd: "modprobe sdhci_pci" Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #16 (PCI bridge) 26: PCI 500.2: 0805 SD Host controller [Created at pci.319] Unique ID: yGgG.iSo8XH1EHdB Parent ID: QSNP.VdJa1LlJ33D SysFS ID: /devices/pci0000:00/0000:00:1c.4/0000:05:00.2 SysFS BusID: 0000:05:00.2 Hardware Class: unknown Model: "JMicron SD Host controller" Vendor: pci 0x197b "JMicron Technology Corp." Device: pci 0x2391 SubVendor: pci 0x1028 "Dell" SubDevice: pci 0x0446 Revision: 0x30 Memory Range: 0xf1900100-0xf19001ff (rw,non-prefetchable) IRQ: 16 (741 events) Module Alias: "pci:v0000197Bd00002391sv00001028sd00000446bc08sc05i01" Driver Info #0: Driver Status: sdhci_pci is active Driver Activation Cmd: "modprobe sdhci_pci" Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #16 (PCI bridge) 27: PCI 500.3: 0880 System peripheral [Created at pci.319] Unique ID: pb96.84YPrqVjp5A Parent ID: QSNP.VdJa1LlJ33D SysFS ID: /devices/pci0000:00/0000:00:1c.4/0000:05:00.3 SysFS BusID: 0000:05:00.3 Hardware Class: unknown Model: "JMicron System peripheral" Vendor: pci 0x197b "JMicron Technology Corp." Device: pci 0x2393 SubVendor: pci 0x1028 "Dell" SubDevice: pci 0x0446 Revision: 0x30 Driver: "jmb38x_ms" Driver Modules: "jmb38x_ms" Memory Range: 0xf1900200-0xf19002ff (rw,non-prefetchable) IRQ: 16 (741 events) Module Alias: "pci:v0000197Bd00002393sv00001028sd00000446bc08sc80i00" Driver Info #0: Driver Status: jmb38x_ms is active Driver Activation Cmd: "modprobe jmb38x_ms" Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #16 (PCI bridge) 28: PCI 500.4: 0880 System peripheral [Created at pci.319] Unique ID: hwex.fUU9KPdQLUA Parent ID: QSNP.VdJa1LlJ33D SysFS ID: /devices/pci0000:00/0000:00:1c.4/0000:05:00.4 SysFS BusID: 0000:05:00.4 Hardware Class: unknown Model: "JMicron System peripheral" Vendor: pci 0x197b "JMicron Technology Corp." Device: pci 0x2394 SubVendor: pci 0x1028 "Dell" SubDevice: pci 0x0446 Revision: 0x30 Memory Range: 0xf1900300-0xf19003ff (rw,non-prefetchable,disabled) IRQ: 255 (no events) Module Alias: "pci:v0000197Bd00002394sv00001028sd00000446bc08sc80i00" Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #16 (PCI bridge) Only appears to work under special circunstancies. - When an memory card is plugged in *before* power up. - When one manually issue echo 1 > /sys/bus/pci/rescan After that, the reader appears : 125.742398] pci 0000:05:00.0: [197b:2392] type 00 class 0x088000 [ 125.742428] pci 0000:05:00.0: reg 10: [mem 0x00000000-0x000000ff] [ 125.742705] pci 0000:05:00.2: [197b:2391] type 00 class 0x080501 [ 125.742732] pci 0000:05:00.2: reg 10: [mem 0x00000000-0x000000ff] [ 125.742978] pci 0000:05:00.3: [197b:2393] type 00 class 0x088000 [ 125.743004] pci 0000:05:00.3: reg 10: [mem 0x00000000-0x000000ff] [ 125.743247] pci 0000:05:00.4: [197b:2394] type 00 class 0x088000 [ 125.743273] pci 0000:05:00.4: reg 10: [mem 0x00000000-0x000000ff] [ 125.744809] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment [ 125.744816] pci 0000:05:00.0: BAR 0: assigned [mem 0xf1900000-0xf19000ff] [ 125.744823] pci 0000:05:00.2: BAR 0: assigned [mem 0xf1900100-0xf19001ff] [ 125.744829] pci 0000:05:00.3: BAR 0: assigned [mem 0xf1900200-0xf19002ff] [ 125.744835] pci 0000:05:00.4: BAR 0: assigned [mem 0xf1900300-0xf19003ff] [ 125.751447] jmb38x_ms 0000:05:00.3: enabling device (0000 -> 0002) [ 125.753996] sdhci: Secure Digital Host Controller Interface driver [ 125.753998] sdhci: Copyright(c) Pierre Ossman [ 125.754882] sdhci-pci 0000:05:00.0: SDHCI controller found [197b:2392] (rev 30) [ 125.754899] sdhci-pci 0000:05:00.0: enabling device (0000 -> 0002) [ 125.754959] 0000:05:00.0 supply vmmc not found, using dummy regulator [ 125.755010] Registered led device: mmc0:: [ 125.756678] mmc0: SDHCI controller on PCI [0000:05:00.0] using DMA [ 125.756688] sdhci-pci 0000:05:00.0: could not set regulator OCR (-22) [ 125.756729] sdhci-pci 0000:05:00.2: SDHCI controller found [197b:2391] (rev 30) [ 125.756741] sdhci-pci 0000:05:00.2: enabling device (0000 -> 0002) [ 125.756749] sdhci-pci 0000:05:00.2: Refusing to bind to secondary interface. [ 126.141259] mmc0: new SD card at address 1f10 [ 126.145072] mmcblk0: mmc0:1f10 SD02G 1.91 GiB (ro) [ 126.145971] mmcblk0: p1 Will be cool if it can be investigated if this a kernel, udev or bios bug. Cheers. -- 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 12

[Bug 772546] New: [Kernel:stable| net:ipv6] BUG: unable to handle kernel paging request at 000000010233f0ff
by bugzilla_noreply＠novell.com 17 Dec '13

17 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=772546 https://bugzilla.novell.com/show_bug.cgi?id=772546#c0 Summary: [Kernel:stable| net:ipv6] BUG: unable to handle kernel paging request at 000000010233f0ff Classification: openSUSE Product: openSUSE 12.2 Version: RC 1 Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: crrodriguez(a)opensuse.org QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- I have one machine crashing after this: <1>[147390.351498] BUG: unable to handle kernel paging request at 000000010233f0ff <1>[147390.352584] IP: [<ffffffff81457e1b>] dst_release+0x1b/0x80 <4>[147390.353430] PGD 0 <4>[147390.353749] Oops: 0002 [#1] SMP <4>[147390.354264] CPU 1 <4>[147390.354567] Modules linked in: binfmt_misc bluetooth act_police cls_basic cls_flow cls_fw cls_u32 sch_tbf sch_prio sch_htb sch_hfsc sch_ingress sch_sfq bridge stp xt_statistic xt_CT xt_LOG xt_connlimit xt_realm xt_addrtype iptable_raw ip6_queue xt_time xt_TCPMSS xt_sctp ip6t_REJECT nf_conntrack_ipv6 xt_comment ip6table_raw ip6table_mangle xt_recent xt_policy ipt_ULOG ipt_REJECT ipt_REDIRECT ipt_NETMAP ipt_MASQUERADE ipt_ECN ipt_CLUSTERIP ipt_ah xt_set ip_set nf_nat_tftp nf_nat_snmp_basic nf_conntrack_snmp nf_nat_sip nf_nat_pptp nf_nat_proto_gre nf_nat_irc nf_nat_h323 nf_nat_ftp nf_nat_amanda ts_kmp nf_conntrack_amanda nf_conntrack_sane nf_conntrack_tftp nf_conntrack_sip nf_conntrack_proto_udplite nf_conntrack_proto_sctp nf_conntrack_pptp nf_conntrack_proto_gre nf_conntrack_netlink nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_irc nf_conntrack_h323 nf_conntrack_ftp xt_TPROXY nf_tproxy_core nf_defrag_ipv6 xt_tcpmss xt_pkttype xt_physdev xt_owner xt_NFQUEUE xt_NFLOG nfnetlink_log xt_multiport xt_mark xt_mac xt_limit xt_length xt_iprange xt_helper xt_hashlimit xt_DSCP xt_dscp xt_dccp xt_conntrack xt_connmark xt_CLASSIFY xt_AUDIT ip6table_filter ip6_tables xt_tcpudp xt_state iptable_nat nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack iptable_mangle nfnetlink iptable_filter ip_tables x_tables cachefiles fscache af_packet edd eeepc_wmi asus_wmi sparse_keymap rfkill acpi_cpufreq mperf pci_hotplug coretemp crc32c_intel ghash_clmulni_intel aesni_intel e1000e cryptd wmi mei(C) xhci_hcd aes_x86_64 i2c_i801 iTCO_wdt pcspkr joydev iTCO_vendor_support microcode autofs4 usbhid i915 drm_kms_helper drm ehci_hcd i2c_algo_bit usbcore usb_common video button scsi_dh_hp_sw scsi_dh_alua scsi_dh_emc scsi_dh_rdac scsi_dh fan processor thermal thermal_sys megaraid_sas <4>[147390.380296] <4>[147390.380524] Pid: 0, comm: swapper/1 Tainted: G C 3.4.5-1-default #1 System manufacturer System Product Name/P8B WS <4>[147390.382259] RIP: 0010:[<ffffffff81457e1b>] [<ffffffff81457e1b>] dst_release+0x1b/0x80 <4>[147390.383472] RSP: 0018:ffff88041f243ce0 EFLAGS: 00010202 <4>[147390.384272] RAX: ffff8803f7fd4ce8 RBX: 000000010233f07f RCX: 0000000000000000 <4>[147390.385344] RDX: 000000010231a68f RSI: ffff8803f7fd4ce8 RDI: 000000010233f07f <4>[147390.386417] RBP: 00000000ffffffff R08: 00000000000000be R09: ffff88041f243cb0 <4>[147390.387488] R10: ffffffffa04e62e0 R11: ffff8803466dc086 R12: ffff8803466dc086 <4>[147390.388560] R13: 0000000000000000 R14: 00000000000005aa R15: ffff88037ffb5940 <4>[147390.389631] FS: 0000000000000000(0000) GS:ffff88041f240000(0000) knlGS:0000000000000000 <4>[147390.390846] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b <4>[147390.391709] CR2: 000000010233f0ff CR3: 0000000001a0b000 CR4: 00000000000407e0 <4>[147390.392780] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 <4>[147390.393852] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 <4>[147390.394924] Process swapper/1 (pid: 0, threadinfo ffff88040abb4000, task ffff88040abb2300) <4>[147390.396164] Stack: <4>[147390.396467] 0000000002000000 00000000000249f0 ffff8803466dc096 ffffffff814f069a <4>[147390.397634] ffff8803fa558000 ffff8803466dc096 ffff8803466dc086 ffffffff81d5fb40 <4>[147390.398799] 00000000000005aa ffff8803fa558000 000000000000003a ffffffff814f0bda <4>[147390.444946] Call Trace: <4>[147390.490466] [<ffffffff814f069a>] rt6_do_pmtu_disc+0x27a/0x330 <4>[147390.536432] [<ffffffff814f0bda>] rt6_pmtu_discovery+0x3a/0x70 <4>[147390.536438] [<ffffffff81500233>] icmpv6_rcv+0x3c3/0x4a0 <4>[147390.536444] [<ffffffff814e42f7>] ip6_input_finish+0x157/0x380 <4>[147390.536450] [<ffffffff81450ca3>] __netif_receive_skb+0x493/0x510 <4>[147390.536457] [<ffffffff81451711>] process_backlog+0xa1/0x170 <4>[147390.536461] [<ffffffff81451571>] net_rx_action+0x121/0x220 <4>[147390.536468] [<ffffffff810460ad>] __do_softirq+0x9d/0x1f0 <4>[147390.536475] [<ffffffff8155bc0c>] call_softirq+0x1c/0x30 <4>[147390.536480] [<ffffffff81004195>] do_softirq+0x65/0xa0 <4>[147390.536485] [<ffffffff8104647e>] irq_exit+0x8e/0xb0 <4>[147390.536490] [<ffffffff8155b6da>] call_function_single_interrupt+0x6a/0x70 <4>[147390.536499] [<ffffffff8131d2c9>] intel_idle+0xe9/0x160 <4>[147390.536506] [<ffffffff81418a3e>] cpuidle_idle_call+0x9e/0x280 <4>[147390.536513] [<ffffffff8100b53f>] cpu_idle+0x7f/0xd0 <4>[147390.536516] Code: ff 86 80 00 00 00 48 89 77 58 c3 0f 1f 44 00 00 48 83 ec 18 48 85 ff 48 89 5c 24 08 48 89 6c 24 10 48 89 fb 74 16 bd ff ff ff ff <f0> 0f c1 af 80 00 00 00 83 ed 01 78 41 85 ed 74 14 48 8b 5c 24 <1>[147390.536538] RIP [<ffffffff81457e1b>] dst_release+0x1b/0x80 <4>[147390.536542] RSP <ffff88041f243ce0> <4>[147390.536543] CR2: 000000010233f0ff I have a kdump but it is huge and I am not sure if that would really help.. -- 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 10

[Bug 808567] New: powermanager leaks suspendJob
by bugzilla_noreply＠novell.com 17 Dec '13

17 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=808567 https://bugzilla.novell.com/show_bug.cgi?id=808567#c0 Summary: powermanager leaks suspendJob Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 0 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Workspace AssignedTo: crrodriguez(a)opensuse.org ReportedBy: jslaby(a)suse.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- See the original report at: https://bugs.kde.org/show_bug.cgi?id=316473 This is caused by powerdevil-logind.patch in openSUSE. The Resuming signal from upower never comes when suspending via login1. So there are severe leaks. -- 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 3

[Bug 846897] New: Changes for more complete integration with systemd break Apache when build in chroots
by bugzilla_noreply＠novell.com 17 Dec '13

17 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=846897 https://bugzilla.novell.com/show_bug.cgi?id=846897#c0 Summary: Changes for more complete integration with systemd break Apache when build in chroots Classification: openSUSE Product: openSUSE 13.1 Version: RC 1 Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Apache AssignedTo: crrodriguez(a)opensuse.org ReportedBy: thardeck(a)suse.com QAContact: qa-bugs(a)suse.de CC: draht(a)suse.com Found By: Development Blocker: --- If I build openSUSE 13.1 with Kiwi and include Apache the service does hang after starting. If I remove Apache in the running image and reinstall it, it does work fine. There is no systemd in a chrooted environment that's why the setting isn't set but systemd still waits for a notify so starting the service doesn't work. The source for the issue is this change: - Include mod_systemd for more complete integration with systemd, turn the service to Typé=notify as required https://build.opensuse.org/package/rdiff/Apache/apache2?linkrev=base&rev=379 There should be a check for the distribution in the spec file and not in apache-20-22-upgrade . -- 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 10