December 2013 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 853661] New: apparmor_parser: spelling issue: cannot
by bugzilla_noreply＠novell.com 16 Dec '13

16 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=853661 https://bugzilla.novell.com/show_bug.cgi?id=853661#c0 Summary: apparmor_parser: spelling issue: cannot Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: AppArmor AssignedTo: suse-beta(a)cboltz.de ReportedBy: ke(a)suse.com QAContact: qa-bugs(a)suse.de Found By: Documentation Blocker: --- During boot (IIRC), apparmor_parser (?) several times says something with "can not". But this should be spelled "cannot". -- 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 855704] New: tweak tool does not fit properly on screen
by bugzilla_noreply＠novell.com 16 Dec '13

16 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=855704 https://bugzilla.novell.com/show_bug.cgi?id=855704#c0 Summary: tweak tool does not fit properly on screen Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: ohering(a)suse.com QAContact: qa-bugs(a)suse.de Found By: Outsourced Testing Blocker: --- Created an attachment (id=571999) --> (http://bugzilla.novell.com/attachment.cgi?id=571999) Screenshot from 2013-12-16 19:27:04.png 13.1 x86_64 gnome desktop 800x600 as shown in the attached screenshot, tweak tool does not fit properly on screen if the VM window is 800x600. -- 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 0

[Bug 853023] New: ibus -mozc systray icon is overly large
by bugzilla_noreply＠novell.com 16 Dec '13

16 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=853023 https://bugzilla.novell.com/show_bug.cgi?id=853023#c0 Summary: ibus -mozc systray icon is overly large Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: mrkfbrn(a)yahoo.co.nz QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=569718) --> (http://bugzilla.novell.com/attachment.cgi?id=569718) mozc input icon should look like this (and did in openSUSE 12.3) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:25.0) Gecko/20100101 Firefox/25.0 The orange systray icon for mozc used for Japanese input in ibus is overly large and not particularly visually appealing. I have attached screenshots of what it should look like and what it currently looks like. 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 11

[Bug 855541] New: NVidia 331.20 ABI mismatch with xorg-x11-server-7.6_1.14.99.904-1.1.x86_64 update
by bugzilla_noreply＠novell.com 16 Dec '13

16 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=855541 https://bugzilla.novell.com/show_bug.cgi?id=855541#c0 Summary: NVidia 331.20 ABI mismatch with xorg-x11-server-7.6_1.14.99.904-1.1.x86_64 update Classification: openSUSE Product: openSUSE Factory Version: 13.2 Milestone 0 Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: X.Org AssignedTo: bnc-team-xorg-bugs(a)forge.provo.novell.com ReportedBy: sboyce(a)blueyonder.co.uk QAContact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:26.0) Gecko/20100101 Firefox/26.0 [ 6969.136] Loading extension GLX [ 6969.136] (II) LoadModule: "nvidia" [ 6969.136] (II) Loading /usr/lib64/xorg/modules/drivers/nvidia_drv.so [ 6969.137] (II) Module nvidia: vendor="NVIDIA Corporation" [ 6969.137] compiled for 4.0.2, module version = 1.0.0 [ 6969.137] Module class: X.Org Video Driver [ 6969.137] ================ WARNING WARNING WARNING WARNING ================ [ 6969.137] This server has a video driver ABI version of 15.0 that is not supported by this NVIDIA driver. Please check http://www.nvidia.com/ for driver updates or downgrade to an X server with a supported driver ABI. [ 6969.137] ================================================================= [ 6969.137] (WW) NVIDIA: The driver will continue to load, but may behave strangely. [ 6969.137] (WW) NVIDIA: This server has an unsupported input driver ABI version (have 20.0, need < 20.0). The driver will continue to load, but may behave strangely. [ 6969.137] (II) NVIDIA dlloader X Driver 331.20 Wed Oct 30 17:16:53 PDT 2013 [ 6969.137] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs [ 6969.137] (++) using VT number 7 <stuff deleted> [ 6970.042] (--) Depth 24 pixmap format is 32 bpp [ 6970.042] (II) NVIDIA: Using 3072.00 MB of virtual memory for indirect memory [ 6970.042] (II) NVIDIA: access. [ 6970.045] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon [ 6970.045] (II) NVIDIA(0): may not be running or the "AcpidSocketPath" X [ 6970.045] (II) NVIDIA(0): configuration option may not be set correctly. When the [ 6970.045] (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will [ 6970.045] (II) NVIDIA(0): try to use it to receive ACPI event notifications. For [ 6970.045] (II) NVIDIA(0): details, please see the "ConnectToAcpid" and [ 6970.045] (II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X [ 6970.045] (II) NVIDIA(0): Config Options in the README. [ 6970.051] (II) NVIDIA(0): Setting mode "CRT-1:nvidia-auto-select" [ 6970.097] Loading extension NV-GLX [ 6970.102] (EE) [ 6970.102] (EE) Backtrace: [ 6970.102] (EE) 0: /usr/bin/Xorg (xorg_backtrace+0x48) [0x58a268] [ 6970.102] (EE) 1: /usr/bin/Xorg (0x400000+0x18df59) [0x58df59] [ 6970.102] (EE) 2: /lib64/libpthread.so.0 (0x7f57adf58000+0xf9f0) [0x7f57adf679f0] [ 6970.102] (EE) 3: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7f57a7b40000+0x4e427f) [0x7f57a802427f] [ 6970.102] (EE) 4: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7f57a7b40000+0x4eb501) [0x7f57a802b501] [ 6970.102] (EE) 5: /usr/bin/Xorg (AddScreen+0x71) [0x43b6b1] [ 6970.102] (EE) 6: /usr/bin/Xorg (InitOutput+0x3df) [0x47c58f] [ 6970.102] (EE) 7: /usr/bin/Xorg (0x400000+0x3f06b) [0x43f06b] [ 6970.102] (EE) 8: /lib64/libc.so.6 (__libc_start_main+0xf5) [0x7f57acba9b25] [ 6970.102] (EE) 9: /usr/bin/Xorg (0x400000+0x2a7fe) [0x42a7fe] [ 6970.102] (EE) [ 6970.102] (EE) Segmentation fault at address 0x18 [ 6970.102] (EE) Fatal server error: [ 6970.103] (EE) Caught signal 11 (Segmentation fault). Server aborting [ 6970.103] (EE) [ 6970.103] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 6970.103] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [ 6970.103] (EE) [ 6970.103] (EE) Server terminated with error (1). Closing log file. Reproducible: Always Steps to Reproduce: 1.When KDE starts 2. 3. Actual Results: nvidia module loads but crashes. Expected Results: KDE desktop -- 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 855659] New: New OBS project 'storage'
by bugzilla_noreply＠novell.com 16 Dec '13

16 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=855659 https://bugzilla.novell.com/show_bug.cgi?id=855659#c0 Summary: New OBS project 'storage' Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: OBS Request AssignedTo: mrueckert(a)suse.com ReportedBy: hare(a)suse.com QAContact: adrian(a)suse.com Found By: Development Blocker: --- Please create new OBS project 'storage', which will be used to hold the management / administration tools related to storage, eg: - multipath-tools - targetcli - open-iscsi - tgtd - bcache-tools - lio-utils and others. Currently these packages live in some home projects at various locations and it's very hard, if not impossible, to figure out the most recent version. -- 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 855534] New: bs_sched: prereq is incorrectly translated to BuildRequires
by bugzilla_noreply＠novell.com 16 Dec '13

16 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=855534 https://bugzilla.novell.com/show_bug.cgi?id=855534#c0 Summary: bs_sched: prereq is incorrectly translated to BuildRequires Classification: Internal Novell Products Product: openSUSE Build Service Version: master Platform: All OS/Version: Linux Status: NEW Severity: Major Priority: P5 - None Component: backend AssignedTo: mls(a)suse.com ReportedBy: jengelh(a)inai.de QAContact: adrian(a)suse.com Found By: Beta-Customer Blocker: --- What was done: $ cat z.spec Name: z Version: 0 Release: 0 Summary: z License: z PreReq: xxxx %description What was observed: $ osc build -bd openSUSE_Factory x86_64 z.spec Building z.spec for openSUSE_Factory/x86_64 Getting buildinfo from server and store to /home/jengelh/obs/zu/network/mail/zarafa/zarafa/.osc/_buildinfo-openSUSE_Factory-x86_64.xml Getting buildconfig from server and store to /home/jengelh/obs/zu/network/mail/zarafa/zarafa/.osc/_buildconfig-openSUSE_Factory-x86_64 buildinfo is broken... it says: unresolvable: nothing provides xxxx What should have happened: Don't abort with "nothing provides". PreReq does not mean BuildRequire in the scope of .spec files! -- 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 853270] New: devel:languages:python3/python3-matplotlib: Bug can't use mathtext in pdf output of matplotlib in python3
by bugzilla_noreply＠novell.com 16 Dec '13

16 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=853270 https://bugzilla.novell.com/show_bug.cgi?id=853270#c0 Summary: devel:languages:python3/python3-matplotlib: Bug can't use mathtext in pdf output of matplotlib in python3 Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software AssignedTo: speilicke(a)suse.com ReportedBy: arun(a)gmx.de QAContact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- Running into a mathtext error when writing pdf files Here is how to reproduce the error: import matplotlib from matplotlib import pyplot as plt from matplotlib.backends.backend_pdf import PdfPages import numpy as np with PdfPages('test.pdf') as pdf: a = np.arange(20) s = np.sin(a) fig = plt.figure() plt.xlabel(r"test $\mu$ ") plt.plot(a,s) pdf.savefig() fails with a lot of error messages, ending in: RuntimeError: maximum recursion depth exceeded in __instancecheck__ changing plt.xlabel(r"test $\mu$ ") to plt.xlabel(r"test ") removes the crash. Could be related to pyparsing? When I use the 2.7 python version this doesn't happen. I'm running 13.1/Tumbleweed with python3-matplotlib installed from dlp3 at the moment. -- 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 8

[Bug 845909] New: VPN connection can not be started from plasma-nm-openconnect
by bugzilla_noreply＠novell.com 16 Dec '13

16 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=845909 https://bugzilla.novell.com/show_bug.cgi?id=845909#c0 Summary: VPN connection can not be started from plasma-nm-openconnect Classification: openSUSE Product: openSUSE 13.1 Version: RC 1 Platform: All OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: robert.munteanu(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 I've defined a VPN connection based on OpenConnect - just the gateway is filled in. If I try to connect from the Network Management applet, nothing happens. The only relevant bit that I see in the /var/log/NetworkManager is: <warn> connection /org/freedesktop/NetworkManager/Settings/2 failed to activate: (2) The VPN service 'org.freedesktop.NetworkManager.openconnect' was not installed. Both openconnect and nm-plasma-openconnect are installed: openconnect-4.08-2.1.2.x86_64 plasma-nm-openconnect-0.9.3.0-2.1.x86_64 Connecting using the CLI works fine. 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 6

[Bug 850882] New: libvirtd can't start kvm instance when apparmor is running
by bugzilla_noreply＠novell.com 16 Dec '13

16 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=850882 https://bugzilla.novell.com/show_bug.cgi?id=850882#c0 Summary: libvirtd can't start kvm instance when apparmor is running Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: AppArmor AssignedTo: jfehlig(a)suse.com ReportedBy: rhafer(a)suse.com QAContact: qa-bugs(a)suse.de Found By: Development Blocker: --- Created an attachment (id=567844) --> (http://bugzilla.novell.com/attachment.cgi?id=567844) journalctl output after trying to launch a VM Starting a VM using virsh on the latest 13.1 code give me: virsh # start sles-11-sp3 error: Failed to start domain sles-11-sp3 error: Child quit during startup handshake: Input/output error This seems to be related to apparmor (see attached log). -- 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 849524] New: Xen doesn't start domain with AppArmor
by bugzilla_noreply＠novell.com 16 Dec '13

16 Dec '13

https://bugzilla.novell.com/show_bug.cgi?id=849524 https://bugzilla.novell.com/show_bug.cgi?id=849524#c0 Summary: Xen doesn't start domain with AppArmor Classification: openSUSE Product: openSUSE 13.1 Version: RC 2 Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: AppArmor AssignedTo: suse-beta(a)cboltz.de ReportedBy: vbotka(a)suse.com QAContact: qa-bugs(a)suse.de Found By: Product Management Blocker: --- # uname -a Linux probook 3.11.6-4-xen #1 SMP Wed Oct 30 18:04:56 UTC 2013 (e6d4a27) x86_64 x86_64 x86_64 GNU/Linux # virsh start SUSEManager error: Failed to start domain SUSEManager error: internal error: libxenlight failed to create new domain 'SUSEManager' # cat /var/log/xen/bootloader.4.log libxl: cannot execute /usr/lib64/xen/bin/pygrub: Permission denied With AppArmor disabled the domain starts. -- 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