April 2013 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 812476] New: It is not possible to install ClamTk in openSUSE 12.3
by bugzilla_noreply＠novell.com 18 Apr '13

18 Apr '13

https://bugzilla.novell.com/show_bug.cgi?id=812476 https://bugzilla.novell.com/show_bug.cgi?id=812476#c0 Summary: It is not possible to install ClamTk in openSUSE 12.3 Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Security AssignedTo: security-team(a)suse.de ReportedBy: Vojtech.Zeisek(a)opensuse.org 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 In security repo, there is nice GUI for Clamav, ClamTk. But it is not possible to install it in openSUSE 12.3, because it requires clamav-db, which is not available for 12.3. It is in update repo for 12.2. PS: Am I blind or is openSUSE 12.3 really missing in "Operating System" drop-down menu in bug entering form? Reproducible: Always Steps to Reproduce: 1. Add security repo http://download.opensuse.org/repositories/security/openSUSE_12.3/ 2. Try to install ClamTk Actual Results: ClamTk is not installed because of missing clamav-db. Expected Results: ClamTk is installable and works. -- 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 808857] New: openSUSE12.3 RC2 can NOT get updates after a fresh installation (with a working internet network)
by bugzilla_noreply＠novell.com 18 Apr '13

18 Apr '13

https://bugzilla.novell.com/show_bug.cgi?id=808857 https://bugzilla.novell.com/show_bug.cgi?id=808857#c0 Summary: openSUSE12.3 RC2 can NOT get updates after a fresh installation (with a working internet network) Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security AssignedTo: security-team(a)suse.de ReportedBy: imgui(a)qq.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:19.0) Gecko/20100101 Firefox/19.0 Update system through Apper program after a fresh installation, the system will be hinted as below: ================ A security trust relationship could not be made with the software origin. For repo /var/cache/zypp/raw/repo-ossDX00bK/suse/setup/descr/packages.DU.gz 36eba70ddf0215cdbd40ff6c423c8a7eed8479ef52af8cee4473ec3c033574f8 is requested but d438dca5c8ce1a9290fd40877ba6ffcdffc81cccff9a21da3a98c31a3305f439 was found! ================ So the fresh installed openSUSE 12.3 RC2 just can NOT get updates. Reproducible: Always Steps to Reproduce: 1. Launch Apper, 2. Click "Updates" on the interface 3. Check for new updates -- 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 807074] New: No graphical installation on AMD Radeon HD 7000
by bugzilla_noreply＠novell.com 18 Apr '13

18 Apr '13

https://bugzilla.novell.com/show_bug.cgi?id=807074 https://bugzilla.novell.com/show_bug.cgi?id=807074#c0 Summary: No graphical installation on AMD Radeon HD 7000 Classification: openSUSE Product: openSUSE Factory Version: 12.3 Beta 1 Platform: x86-64 OS/Version: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org AssignedTo: bnc-team-xorg-bugs(a)forge.provo.novell.com ReportedBy: kollix(a)aon.at QAContact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; i686 Linux; en_US, de; rv:1.9.2) Gecko/20100115 Firefox/3.6 I bought a new motherboard (ASUS F2A85-M LE) which has an integrated graphics chip "AMD Radeon HD 7000". Installation of 12.3 RC1 did not work directly because after starting the Installation option in the boot menu the screen went blank and I could not see anything. What I needed to do was to power-reset the machine and boot with "no modeset" option. This at least brought me to the textmode installation and told me that Xorg could not start. Reproducible: Always Steps to Reproduce: 1. 2. 3. Expected Results: Either - do not fail to start Xorg or - when Xorg fails, bring me directly to the textmode without the need to power-cycle -- 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 9

[Bug 810850] New: Please provide tigervnc tools
by bugzilla_noreply＠novell.com 18 Apr '13

18 Apr '13

https://bugzilla.novell.com/show_bug.cgi?id=810850 https://bugzilla.novell.com/show_bug.cgi?id=810850#c0 Summary: Please provide tigervnc tools Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 0 Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: X.Org AssignedTo: bnc-team-xorg-bugs(a)forge.provo.novell.com ReportedBy: mkoegler(a)auto.tuwien.ac.at QAContact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20121208 Iceape/2.0.11 OpenSuSE switched xorg-x11-Xvnc to the tigervnc codebase, which also includes encryption support. The build currently compiles the tigervnc client programs too, but throws them away. Please provide the tigervnc client programs as rpm package too. 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 2

[Bug 768788] New: [systemd][3 on cmdline] X session tty locations not predictable (:1 not always on tty8; :0 not always on tty7)
by bugzilla_noreply＠novell.com 18 Apr '13

18 Apr '13

https://bugzilla.novell.com/show_bug.cgi?id=768788 https://bugzilla.novell.com/show_bug.cgi?id=768788#c0 Summary: [systemd][3 on cmdline] X session tty locations not predictable (:1 not always on tty8; :0 not always on tty7) Classification: openSUSE Product: openSUSE 12.2 Version: Beta 2 Platform: x86 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: mrmazda(a)earthlink.net QAContact: qa-bugs(a)suse.de CC: fcrozat(a)suse.com Found By: --- Blocker: --- Not new in 12.2B2. I don't remember how far back this began, but possibly when systemd first appeared in ~12.1M3 last summer. Neither splashy nor bootsplash are installed on any of my systems. All my Grub stanzas include splash=verbose on cmdline. AFAICT, plymouth though installed never appears to run, which is my strong preference. To reproduce [i945G host gx62b]: 1-boot (with 3 on cmdline) 2-login on tty2 3-login on tty3 4-login on tty4 5-# init 5 on tty3 6-login in KDM3 7-$ startx -- :1 on tty4 Actual results: 1-KDM is on tty7 2-:1 X session is on tty5 Expected results: 1-KDM is on tty7 2-:1 X session is on tty8 Alternate reproduce [rv380 host big31]: 1-boot (with 3 on cmdline) 2-login on tty3 3-# startx Actual results: 1-KDE4 session is on tty2 2-login prompts on tty1, tty2, tty4, tty5, tty6, tty7, tty8, tty9 after KDE4 exited Expected results: 1-KDE4 session is on tty7 2-login prompts only on tty1, tty2, tty4, tty5, tty6 after KDE4 exited Alternate 2 reproduce [rv380 host big31]: 1-boot (with 3 on cmdline) 2-login on tty2 3-login on tty3 4-login on tty4 5-# startx on tty3 6-$ startx -- :1 on tty4 Actual results: 1-root's KDE4 is on tty6 2-:1 X session is on tty7 3-no login prompt on tty6 after KDE exited Expected results: 1-root's KDE4 is on tty7 2-:1 X session is on tty8 3-login prompt on tty6 after KDE exited Note: I don't expect this to matter, as I've not tested stock, but noting in case it might. I have /lib/systemd/system/getty(a)tty1.service as a symlink to /etc/systemd/system/getty(a)tty1.service, which contains two non-default lines: ExecStart=-/sbin/agetty %I 38400 --noclear TTYVTDisallocate=no Default omits --noclear and has yes for ...allocate. cf. bug 721660 -- 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 17

[Bug 807942] New: wireshark update to 1.8.6
by bugzilla_noreply＠novell.com 18 Apr '13

18 Apr '13

https://bugzilla.novell.com/show_bug.cgi?id=807942 https://bugzilla.novell.com/show_bug.cgi?id=807942#c0 Summary: wireshark update to 1.8.6 Classification: openSUSE Product: openSUSE 12.3 Version: RC 2 Platform: All OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Security AssignedTo: security-team(a)suse.de ReportedBy: Andreas.Stieger(a)gmx.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:19.0) Gecko/20100101 Firefox/19.0 A bugfix release for Wireshark fixes security issues and bugs. >From https://www.wireshark.org/docs/relnotes/wireshark-1.8.6.html The TCP dissector could crash. wnpa-sec-2013-10 CVE-2013-2475 The HART/IP dissectory could go into an infinite loop. wnpa-sec-2013-11 CVE-2013-2476 The CSN.1 dissector could crash. wnpa-sec-2013-12 CVE-2013-2477 The MS-MMS dissector could crash. wnpa-sec-2013-13 CVE-2013-2478 The MPLS Echo dissector could go into an infinite loop. wnpa-sec-2013-14 CVE-2013-2479 The RTPS and RTPS2 dissectors could crash. wnpa-sec-2013-15 CVE-2013-2480 The Mount dissector could crash. wnpa-sec-2013-16 CVE-2013-2481 The AMPQ dissector could go into an infinite loop. wnpa-sec-2013-17 CVE-2013-2482 The ACN dissector could attempt to divide by zero. wnpa-sec-2013-18 CVE-2013-2483 The CIMD dissector could crash. wnpa-sec-2013-19 CVE-2013-2484 The FCSP dissector could go into an infinite loop. wnpa-sec-2013-20 CVE-2013-2485 The RELOAD dissector could go into an infinite loop. wnpa-sec-2013-21 CVE-2013-2486 CVE-2013-2487 The DTLS dissector could crash. wnpa-sec-2013-22 CVE-2013-2488 Reproducible: Always Some of these also affect the oldstable 1.6.x series (in SLE) for which 1.6.14 is available. https://www.wireshark.org/docs/relnotes/wireshark-1.6.14.html -- 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 14

[Bug 800981] New: No KMS setting required on Dell XPS12 Duo, but was not required to install 12.2
by bugzilla_noreply＠novell.com 18 Apr '13

18 Apr '13

https://bugzilla.novell.com/show_bug.cgi?id=800981 https://bugzilla.novell.com/show_bug.cgi?id=800981#c0 Summary: No KMS setting required on Dell XPS12 Duo, but was not required to install 12.2 Classification: openSUSE Product: openSUSE Factory Version: 12.3 Beta 1 Platform: x86-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: philip(a)pjtait.org QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.1 (KHTML, like Gecko) Chrome/21.0.1180.89 Safari/537.1 Just received delivery of a Dell XPS12 Duo. openSUSE 12.2 installed flawlessly, everything worked except for the touchscreen. Tried installing 12.3 beta 1 to see if the touchscreen would work out of the box (like it does for Ubuntu 12.10). However, it was necessary to use the "No KMS" installation setting, otherwise the screen blanked after the first page of boot messages. Reproducible: Always Steps to Reproduce: 1.Insert USB flash drive with 12.3 beta 1 2.Boot, and use F12 menu to select USB drive (requires legacy setting in BIOS setup). 3.Select Installation without changing settings. Actual Results: Screen displays a page of text messages, then goes blac, unlike 12.2 which is flawless. Expected Results: Should have displayed normal splash screen like 12.2 does, and proceed to installation configuration screens, like 12.2 -- 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 815199] New: kiwi: allow to skip the md5 check after image installation
by bugzilla_noreply＠novell.com 18 Apr '13

18 Apr '13

https://bugzilla.novell.com/show_bug.cgi?id=815199 https://bugzilla.novell.com/show_bug.cgi?id=815199#c0 Summary: kiwi: allow to skip the md5 check after image installation Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: System Imaging AssignedTo: ms(a)suse.com ReportedBy: ms(a)suse.com QAContact: adrian(a)suse.com Found By: --- Blocker: --- Community feedback - Make it faster. In over 16 months of using kiwi, I've never had an image fail verification. I really would like to have a flag to disable the verification (chksum) of the image during development. Great for production but a nuisance during development. -- 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 814492] New: glade3 crash when open ui file
by bugzilla_noreply＠novell.com 18 Apr '13

18 Apr '13

https://bugzilla.novell.com/show_bug.cgi?id=814492 https://bugzilla.novell.com/show_bug.cgi?id=814492#c0 Summary: glade3 crash when open ui file Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: bili(a)suse.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- $ glade-3 weather-settings.ui GladeUI-Message: No displayable values for property GtkToolPalette::icon-size GladeUI-Message: No displayable values for property GtkToolItemGroup::ellipsize GladeUI-Message: No displayable values for property GtkToolItemGroup::header-relief (glade-3:3882): GLib-GObject-ERROR **: cannot create instance of abstract (non-instantiatable) type `GtkBox' Trace/breakpoint trap (core dumped) When I use glade which is glade2, it works fine. -- 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 653788] New: Error restoring saved x86 domU images on x86-64 dom0
by bugzilla_noreply＠novell.com 18 Apr '13

18 Apr '13

https://bugzilla.novell.com/show_bug.cgi?id=653788 https://bugzilla.novell.com/show_bug.cgi?id=653788#c0 Summary: Error restoring saved x86 domU images on x86-64 dom0 Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Major Priority: P5 - None Component: Xen AssignedTo: jdouglas(a)novell.com ReportedBy: carlos(a)keysoft.pt QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Opera/9.80 (Windows NT 6.1; U; en-GB) Presto/2.6.37 Version/10.70 Dom-0 has XENDOMAINS_RESTORE=true and on shutdown the three domU's (windows2008, suse11.3 x64 and suse-11.2 x86) are saved to /var/lib/xen/save. For some time now (I think since the upgrade of dom0 from 11.2 to 11.3), the suse-11.2 x86 domU always fails to restore on reboot. Manual restore with "xm restore" also fails for this domU. Last week I created a new suse-11.3 x86 domU and today rebooted the dom0. Result: both x86 domU's failed to restore on reboot. xm start works ok for both x86 domU's that fail to restore. uname -a: dom0: Linux zeus 2.6.34.7-0.5-xen #1 SMP 2010-10-25 08:40:12 +0200 x86_64 x86_64 x86_64 GNU/Linux suse-11.2 x86 domU: Linux mail 2.6.31.14-0.4-xen #1 SMP 2010-10-25 08:45:30 +0200 i686 i686 i386 GNU/Linux suse-11.3 x86 domU: Linux ksdev 2.6.34.7-0.5-xen #1 SMP 2010-10-25 08:40:12 +0200 i686 i686 i386 GNU/Linux suse-11.3 x64 domU: Linux suse112 2.6.34.7-0.5-xen #1 SMP 2010-10-25 08:40:12 +0200 x86_64 x86_64 x86_64 GNU/Linux short resume of the error on xend.log for a 'xm restore saved-image' for the suse-11.3 x86 domU: [2010-11-15 22:07:18 4161] DEBUG (balloon:191) Balloon: tmem relinquished -1 KiB of 507328 KiB requested. [2010-11-15 22:07:18 4161] DEBUG (balloon:245) Balloon: 16960 KiB free; 0 to scrub; need 524288; retries: 20. [2010-11-15 22:07:18 4161] DEBUG (balloon:259) Balloon: setting dom0 target to 2709 MiB. [2010-11-15 22:07:18 4161] DEBUG (XendDomainInfo:1512) Setting memory target of domain Domain-0 (0) to 2709 Mi B. [2010-11-15 22:07:18 4161] DEBUG (balloon:245) Balloon: 221760 KiB free; 0 to scrub; need 524288; retries: 20. [2010-11-15 22:07:18 4161] DEBUG (balloon:259) Balloon: setting dom0 target to 2705 MiB. [2010-11-15 22:07:18 4161] DEBUG (XendDomainInfo:1512) Setting memory target of domain Domain-0 (0) to 2705 MiB. [2010-11-15 22:07:18 4161] DEBUG (XendCheckpoint:380) [xc_restore]: /usr/lib64/xen/bin/xc_restore 28 6 1 2 0 0 0 0 [2010-11-15 22:07:18 4161] INFO (XendCheckpoint:482) xc_domain_restore start: p2m_size = 20800 [2010-11-15 22:07:18 4161] INFO (XendCheckpoint:482) Reloading memory pages: 0% [2010-11-15 22:07:40 4161] INFO (XendCheckpoint:482) ERROR Internal error: Error when reading batch size [2010-11-15 22:07:40 4161] INFO (XendCheckpoint:482) ERROR Internal error: error when buffering batch, finishing [2010-11-15 22:07:40 4161] INFO (XendCheckpoint:482) [2010-11-15 22:07:40 4161] INFO (XendCheckpoint:4100% [2010-11-15 22:07:40 4161] INFO (XendCheckpoint:482) Memory reloaded (0 pages) [2010-11-15 22:07:40 4161] DEBUG (XendDomainInfo:3115) XendDomainInfo.destroy: domid=6 [2010-11-15 22:07:40 4161] DEBUG (XendDomainInfo:2455) No device model [2010-11-15 22:07:40 4161] DEBUG (XendDomainInfo:2457) Releasing devices [2010-11-15 22:07:40 4161] DEBUG (XendDomainInfo:2463) Removing vif/0 [2010-11-15 22:07:40 4161] DEBUG (XendDomainInfo:1293) XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0 [2010-11-15 22:07:40 4161] DEBUG (XendDomainInfo:2463) Removing vkbd/0 [2010-11-15 22:07:40 4161] DEBUG (XendDomainInfo:1293) XendDomainInfo.destroyDevice: deviceClass = vkbd, devic e = vkbd/0 [2010-11-15 22:07:40 4161] DEBUG (XendDomainInfo:2463) Removing tap/51712 [2010-11-15 22:07:40 4161] DEBUG (XendDomainInfo:1293) XendDomainInfo.destroyDevice: deviceClass = tap, device = tap/51712 [2010-11-15 22:07:40 4161] DEBUG (XendDomainInfo:2463) Removing tap/51728 [2010-11-15 22:07:40 4161] DEBUG (XendDomainInfo:1293) XendDomainInfo.destroyDevice: deviceClass = tap, device = tap/51728 [2010-11-15 22:07:41 4161] DEBUG (XendDomainInfo:2463) Removing console/0 [2010-11-15 22:07:41 4161] DEBUG (XendDomainInfo:1293) XendDomainInfo.destroyDevice: deviceClass = console, de vice = console/0 [2010-11-15 22:07:41 4161] DEBUG (XendDomainInfo:2463) Removing vfb/0 [2010-11-15 22:07:41 4161] DEBUG (XendDomainInfo:1293) XendDomainInfo.destroyDevice: deviceClass = vfb, device = vfb/0 [2010-11-15 22:07:41 4161] ERROR (XendCheckpoint:416) /usr/lib64/xen/bin/xc_restore 28 6 1 2 0 0 0 0 failed Traceback (most recent call last): File "/usr/lib64/python2.6/site-packages/xen/xend/XendCheckpoint.py", line 384, in restore forkHelper(cmd, fd, handler.handler, True) File "/usr/lib64/python2.6/site-packages/xen/xend/XendCheckpoint.py", line 470, in forkHelper raise XendError("%s failed" % string.join(cmd)) XendError: /usr/lib64/xen/bin/xc_restore 28 6 1 2 0 0 0 0 failed [2010-11-15 22:07:41 4161] ERROR (XendDomain:1188) Restore failed Traceback (most recent call last): File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomain.py", line 1172, in domain_restore_fd dominfo = XendCheckpoint.restore(self, fd, paused=paused, relocating=relocating) File "/usr/lib64/python2.6/site-packages/xen/xend/XendCheckpoint.py", line 417, in restore raise exn XendError: /usr/lib64/xen/bin/xc_restore 28 6 1 2 0 0 0 0 failed No qemu-dm-xxx.log file is generated when the domU fails to restore. 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 25