January 2014 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 684418] New: Use serif fonts for b/w (aka printed) PDFs
by bugzilla_noreply＠novell.com 09 Jan '14

09 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=684418 https://bugzilla.novell.com/show_bug.cgi?id=684418#c0 Summary: Use serif fonts for b/w (aka printed) PDFs Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Documentation AssignedTo: thomas.schraitle(a)novell.com ReportedBy: fs(a)novell.com QAContact: ke(a)novell.com CC: canadapatriot(a)yahoo.com Found By: --- Blocker: --- >From a cutomer mail (see Cc): Concerning the pdf documents, I notice that the last few versions of the manuals are all in sans-serif font. I urge you to consider getting the text body in a serif font (see 11.1 manuals). Sans-serif font is inappropriate for the body text, for it is less comfortable on the eye. On the other hand, serif font is appropriate for titles. The vast majority of print documents are in a serif font, and the pdf document should fit the purpose of printing, unlike the html 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 8

[Bug 831913] New: GlusterFS mounts fail with "doesn't support required op-version (2)"
by bugzilla_noreply＠novell.com 09 Jan '14

09 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=831913 https://bugzilla.novell.com/show_bug.cgi?id=831913#c0 Summary: GlusterFS mounts fail with "doesn't support required op-version (2)" Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 3 Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: High Availability AssignedTo: lmb(a)suse.com ReportedBy: lbeltrame(a)kde.org QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/30.0.1575.0 Safari/537.36 SUSE/30.0.1575.0 Setup: GlusterFS volume spread over 3 servers: 2 Ubuntu servers (12.04) 1 Fedora (19) All run GlusterFS 3.4. The openSUSE machine I'm using is not able to mount the volume using the native glusterFS client, only via NFS. Other servers (Ubuntu) are able to mount the volume just fine. The server logs say: [2013-07-29 09:24:20.128322] I [glusterd-handshake.c:194:_client_supports_volume] 0-glusterd: Client OPENSUSE-MACHINE_IP:1023 (1 -> 1) doesn't support required op-version (2). Rejecting volfile request. and therefore mounts fail. Reproducible: Always Steps to Reproduce: 1. Ensure the glusterFS volume on the other machines is running 2. Attempt to mount: "mount -t glusterfs MACHINE-NAME:/VOLUME_NAME /mnt Actual Results: Client side: [2013-07-29 09:29:43.788786] E [glusterfsd-mgmt.c:1573:mgmt_getspec_cbk] 0-glusterfs: failed to get the 'volume file' from server [2013-07-29 09:29:43.788873] E [glusterfsd-mgmt.c:1648:mgmt_getspec_cbk] 0-mgmt: failed to fetch volume file (key:gv0) Server side: [2013-07-29 09:24:20.128322] I [glusterd-handshake.c:194:_client_supports_volume] 0-glusterd: Client OPENSUSE-MACHINE_IP:1023 (1 -> 1) doesn't support required op-version (2). Rejecting volfile request. Expected Results: The volume should mount. Latest openSUSE Factory. -- 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 844211] New: HW detection fails for BCM43228
by bugzilla_noreply＠novell.com 09 Jan '14

09 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=844211 https://bugzilla.novell.com/show_bug.cgi?id=844211#c0 Summary: HW detection fails for BCM43228 Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: volker3204(a)paradise.net.nz QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/534.34 (KHTML, like Gecko) konqueror/4.10.5 Safari/534.34 openSUSE 12.3 is unable to handle the wireless BCM43228 in a laptop. During installation and by yast there is no reaction. There is also nothing that tells the user the manfacturer and model of the wireless chip so one can start googling. The reason may be that hwinfo fails to detect this chip properly. Contrary to what all instructions say, hwinfo --wlan NEVER PRODUCES ANY OUTPUT. The b43 is too old to handle this chip, and the bcma driver (as suggested perhaps somewhat by grepping the output of hwinfo) is also no good for this chip. The only driver that works is the one in broadcom-wl. hwinfo and yast do not produce anything useable until after this module is loaded, which is no good to the user. Reproducible: Always Steps to Reproduce: 1. Install openSUSE 12.3 on a laptop with BCM43228 wireless chip. 2. 3. Actual Results: User left hung out to dry. Expected Results: User is told what drivers exist for this chip. Adding approximately hwere to get it from would be brilliant. lspci has the only useful info: 02:00.0 Network controller: Broadcom Corporation BCM43228 802.11a/b/g/n -- 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 845648] New: libxenlight failed to create new domain
by bugzilla_noreply＠novell.com 09 Jan '14

09 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=845648 https://bugzilla.novell.com/show_bug.cgi?id=845648#c0 Summary: libxenlight failed to create new domain Classification: openSUSE Product: openSUSE Factory Version: 13.1 Beta 1 Platform: x86-64 OS/Version: SUSE Other Status: NEW Severity: Major Priority: P5 - None Component: Xen AssignedTo: jdouglas(a)suse.com ReportedBy: thomas.e.schreiner(a)t-online.de 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 After solving the problem of broken virtual machine manager (VMM) in case of not runnimg libvirtd, because qemu has not been installed by yast, I tried to install a test-instance OS13.1RC1, using VMM. After doing the configuration and short after starting the installation, I got an errormessage ( see picture Error2.png). Hardware-Info : Notebook with 16 GB Core, Intel(R) Core(TM) i7-3630QM CPU @ 2.40GHz, 500GB ssd plis 700GB SATA HD, Realtek RTL8111/8168B PCI Express Gigabit Ethernet controller, Intel VGA compatible controller plus NVIDIA Corporation Device 11a7. Reproducible: Always Steps to Reproduce: 1.installing qemu - Universal CPU emulator, libvirt-daemon-qemu, libvirt-daemon-driver-qemu and other packages needed for libvirtd. 2.starting virtual machine manager, click VM-Install, click Forward to install operating system openSUSE 13 and configuring hardware requirements. 3.two or three seconds after pressing the OK butten I got the errormessage. Actual Results: Installation of VM stopped as you see at the screenshot. Ahter pressing the OK button of the error message, you fall back into the configuration menue. Expected Results: written Configfile in /etc/xen/vm : name="OS13.1RC1" description="Test" uuid="1cff93f1-e177-d55e-d87c-b4e6286c084f" memory=2048 maxmem=2048 vcpus=2 on_poweroff="destroy" on_reboot="destroy" on_crash="destroy" localtime=0 keymap="de" builder="linux" kernel="/tmp/kernel.PDLID9" ramdisk="/tmp/install-initrd.IlthEQ" extra=" install=hd:/dev/xvdb " disk=[ 'file:/var/lib/xen/images/OS_13.1_RC1.raw,xvda,w', 'file:/var/lib/xen/images/openSUSE-13.1-DVD-Build0041-x86_64.iso,xvdb:cdrom,r', ] vif=[ 'mac=00:16:3e:22:03:7e,bridge=br0', ] vfb=['type=vnc,vncunused=1'] Starting this config with command :xl create OS13.1RC1 gives the result : Parsing config from OS13.1RC1 libxl: error: libxl_dom.c:353:libxl__build_pv: xc_dom_kernel_file failed: No such file or directory libxl: error: libxl_create.c:900:domcreate_rebuild_done: cannot (re-)build domain: -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 58

[Bug 853814] New: Upgrade issues with rename old distro name to new
by bugzilla_noreply＠novell.com 09 Jan '14

09 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=853814 https://bugzilla.novell.com/show_bug.cgi?id=853814#c0 Summary: Upgrade issues with rename old distro name to new Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: fricker(a)bk.ru QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/30.0.1599.114 Chrome/30.0.1599.114 Safari/537.36 Upgrade system with build-in function in Yast. 1) in grub2 menu distro still have name opensuse 12.3 2) on upgrade process it just remove all old repos!! Why? Better try find out if new version is exists and add it if not suspend old one or ask about it(some custom repos not depends on version) Reproducible: Always Steps to Reproduce: 1. have previous version opensuse 2. choose upgrade version in yast installer 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 7

[Bug 857827] New: Standard shutdown doesn't power off system on Fujitsu W520
by bugzilla_noreply＠novell.com 09 Jan '14

09 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=857827 https://bugzilla.novell.com/show_bug.cgi?id=857827#c0 Summary: Standard shutdown doesn't power off system on Fujitsu W520 Classification: openSUSE Product: openSUSE Factory Version: 13.2 Milestone 0 Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: matthias(a)hopf.in QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:26.0) Gecko/20100101 Firefox/26.0 I have a Fujitsu Workstation W520. When shutting down the machine (e.g. via "halt"), power will not be switched off, the last message on the screen states "reboot: System halted", and I need to manually switch off by holding the power key for a few seconds. Interestingly, powering off works fine with "halt -p -f", as well as with the less rude "systemctl -f poweroff". Powering off also works fine on Win7. Rebooting works fine, so does suspend. BIOS has been updated to the latest version 4.6.5.3 R1.22.0. TPM is enabled, in case this has any influence on ACPI (which I doubt in this case). I tested with openSUSE kernels 3.11.6, 3.12.6, als well as with a vanilla kernel 3.13.0-rc4, and SLE 11-SP2 kernel default-3.0.101-35.1.gf9ea730. But it seems this is not kernel related. So was does systemd do differently for regular shutdown versus "systemctl -f poweroff"? Especially, as the final target seems to be reached? Setting to major, as the machine continues to run and draw power. Reproducible: Always Steps to Reproduce: 1. sudo halt Actual Results: reboot: System halted System is NOT powered down. Expected Results: System IS powered down. -- 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 829702] New: libboost_regex in Boost v1.53 missing link to libicuuc when installed via YaST
by bugzilla_noreply＠novell.com 08 Jan '14

08 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=829702 https://bugzilla.novell.com/show_bug.cgi?id=829702#c0 Summary: libboost_regex in Boost v1.53 missing link to libicuuc when installed via YaST Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: andrewtbouchard(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/28.0.1500.68 Safari/537.36 I am running openSUSE 12.3, which installs with Boost v1.49 and just used YaST to update Boost to v1.53 along with a number of associated libraries. But when I go to install ROS, which uses libboost_regex, I get a series of errors that all look like the following: /usr/lib64/gcc/x86_64-suse-linux/4.7/../../../../lib64/libboost_regex-mt.so: undefined reference to `u_tolower_51' After talking with someone on the Boost IRC channel who was very helpful, I was able to use readelf to look at the Version needs section of libboost_regex.so.1.53.0 and determine that libicuuc.so is not linked, which provides those missing references. I reported the bug on the Boost bug tracker, but apparently they do not do the packaging for openSUSE, and the issue is isolated to just this distribution. I wish that I could offer a fix, but I'm way out of my depth here. If someone could please fix this linking issue and let me know how to do so on my system, I would greatly appreciate it. Thanks very much. Reproducible: Always Steps to Reproduce: 1. Uninstall Boost components using YaST 2. Re-install Boost components using YaST 3. Attempt to build ROS Actual Results: ==> Processing catkin package: 'pluginlib' ==> Building with env: '/opt/ros/groovy/env.sh' Makefile exists, skipping explicit cmake invocation... ==> make cmake_check_build_system in '/home/abouchard/ros_catkin_ws/build_isolated/pluginlib' ==> make -j2 -l2 in '/home/abouchard/ros_catkin_ws/build_isolated/pluginlib' Linking CXX executable /home/abouchard/ros_catkin_ws/devel_isolated/pluginlib/lib/pluginlib/plugin_tool /usr/lib64/gcc/x86_64-suse-linux/4.7/../../../../lib64/libboost_regex-mt.so: undefined reference to `u_tolower_51' /usr/lib64/gcc/x86_64-suse-linux/4.7/../../../../lib64/libboost_regex-mt.so: undefined reference to `u_isblank_51' /usr/lib64/gcc/x86_64-suse-linux/4.7/../../../../lib64/libboost_regex-mt.so: undefined reference to `u_charType_51' /usr/lib64/gcc/x86_64-suse-linux/4.7/../../../../lib64/libboost_regex-mt.so: undefined reference to `u_charFromName_51' /usr/lib64/gcc/x86_64-suse-linux/4.7/../../../../lib64/libboost_regex-mt.so: undefined reference to `icu_51::Locale::Locale(icu_51::Locale const&)' /usr/lib64/gcc/x86_64-suse-linux/4.7/../../../../lib64/libboost_regex-mt.so: undefined reference to `u_isspace_51' /usr/lib64/gcc/x86_64-suse-linux/4.7/../../../../lib64/libboost_regex-mt.so: undefined reference to `icu_51::Locale::Locale()' /usr/lib64/gcc/x86_64-suse-linux/4.7/../../../../lib64/libboost_regex-mt.so: undefined reference to `icu_51::Locale::~Locale()' /usr/lib64/gcc/x86_64-suse-linux/4.7/../../../../lib64/libboost_regex-mt.so: undefined reference to `icu_51::Collator::createInstance(icu_51::Locale const&, UErrorCode&)' /usr/lib64/gcc/x86_64-suse-linux/4.7/../../../../lib64/libboost_regex-mt.so: undefined reference to `u_digit_51' collect2: error: ld returned 1 exit status make[2]: *** [/home/abouchard/ros_catkin_ws/devel_isolated/pluginlib/lib/pluginlib/plugin_tool] Error 1 make[1]: *** [CMakeFiles/plugin_tool.dir/all] Error 2 make: *** [all] Error 2 Traceback (most recent call last): File "./src/catkin/bin/../python/catkin/builder.py", line 722, in build_workspace_isolated number=index + 1, of=len(ordered_packages) File "./src/catkin/bin/../python/catkin/builder.py", line 497, in build_package install, force_cmake, quiet, last_env, cmake_args, make_args + catkin_make_args File "./src/catkin/bin/../python/catkin/builder.py", line 353, in build_catkin_package run_command(make_cmd, build_dir, quiet) File "./src/catkin/bin/../python/catkin/builder.py", line 198, in run_command raise subprocess.CalledProcessError(proc.returncode, ' '.join(cmd)) CalledProcessError: Command '/opt/ros/groovy/env.sh make -j2 -l2' returned non-zero exit status 2 <== Failed to process package 'pluginlib': Command '/opt/ros/groovy/env.sh make -j2 -l2' returned non-zero exit status 2 Reproduce this error by running: ==> /opt/ros/groovy/env.sh make -j2 -l2 Command failed, exiting. Expected Results: What should happen is that the libboost_regex-mt.so should build with the links to the references in icu. I can provide more information if requested, but I'm not sure what would be helpful. In parallel, I'm going to attempt to install this Boost library from source and see if I can fix it manually, but like I said, I'm out of my depth here. -- 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 856653] New: Kernel crashes when using Fn+F[89] (brightness down/up) on FSC AMILO Xi 2550
by bugzilla_noreply＠novell.com 08 Jan '14

08 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=856653 https://bugzilla.novell.com/show_bug.cgi?id=856653#c0 Summary: Kernel crashes when using Fn+F[89] (brightness down/up) on FSC AMILO Xi 2550 Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: DOlsson(a)WEB.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=572827) --> (http://bugzilla.novell.com/attachment.cgi?id=572827) Photo of kernel crash traceback. User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:26.0) Gecko/20100101 Firefox/26.0 Every time trying to in- or decrease the backlight brightness using the Fn+F[89] keys, the kernel (kernel-desktop-3.7.10-1.16.1.x86_64) crashes hard! The crash happens independently of whether I use the keys in a graphical or console display. My notebook is a FSC (Fujitsu Siemens Computer) AMILO Xi 2550/F44 with the graphic controller: $ /sbin/lspci | grep -i vga 01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RV630 [Mobility Radeon HD 2600 XT] $ /sbin/lspci -vvs 01:00.0 01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RV630 [Mobility Radeon HD 2600 XT] (prog-if 00 [VGA controller]) Subsystem: Fujitsu Technology Solutions Device 1107 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 48 Region 0: Memory at d0000000 (64-bit, prefetchable) [size=256M] Region 2: Memory at cfef0000 (64-bit, non-prefetchable) [size=64K] Region 4: I/O ports at 2000 [size=256] [virtual] Expansion ROM at cfe00000 [disabled] [size=128K] Capabilities: <access denied> Kernel driver in use: radeon Have tried with: 1) acpi_backlight=vendor 2) acpi_osi="!Windows 2012" but all in vain -- i.e. all results in the same kind of kernel crash. Interesting enough, when running my graphical KDE environment, the KDE window manager is capable of handling the backlight correctly, e.g. by dimming the backlight, when the screen has not been used for a while, just as it is capable of increasing the backlight, when hitting a key. Using the slider in the Battery Power Monitor also works without any problems. Using "sudo echo <number> >/sys/class/backlight/acpi_video0/brightness" also works most of the time. Most of the time, because the kernel may crash from time to time, if using this setting too fast! Reproducible: Always Steps to Reproduce: 1. Boot openSUSE 12.3 (fresh install with newest updates + KDE 4.11) on a FSC notebook model AMILO Xi 2550 with a ADM Mobility Radeon HD 2600 XT graphic controller. 2. Switch either to a text console or to the KDE graphic display and use key Fn+F8 (brightness down) or Fn+F9 (brightness up). 3. Observe the kernel crash with a "BUG: unable to handle kernel NULL pointer dereference at 0000000000000028". Actual Results: Kernel crashes with a BUG: unable to handle kernel NULL pointer dereference at 0000000000000028 Expected Results: The backlight brightness should have been decreased. Attached is a photo of the kernel crash traceback. -- 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 836220] New: WiFi dies and kernel oopses.
by bugzilla_noreply＠novell.com 08 Jan '14

08 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=836220 https://bugzilla.novell.com/show_bug.cgi?id=836220#c0 Summary: WiFi dies and kernel oopses. Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: i586 OS/Version: openSUSE 12.3 Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: carlos.e.r(a)opensuse.org QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=553804) --> (http://bugzilla.novell.com/attachment.cgi?id=553804) messages log Pentium IV Laptop, oS 12.3 32 bits. Text mode. System fully patched. While doing largish downloads, the wifi dies and kernel dumps call traces, several times. Attached goes the message log of one session, from boot to halt. When this happens, halt is problematic, but not logged: systemd baulks because /var/lock is busy and will not umount. System does not power off. Halt works if there has been no network crash. Info: AmonLanc:~/Bugzilla # hwinfo --netcard 23: PCI 10c.0: 0200 Ethernet controller [Created at pci.319] Unique ID: rBUF.3ZQ1cNlR6F7 Parent ID: 6NW+.ccU5FZC1tz2 SysFS ID: /devices/pci0000:00/0000:00:1e.0/0000:01:0c.0 SysFS BusID: 0000:01:0c.0 Hardware Class: network Model: "National DP83815 (MacPhyter) Ethernet Controller" Vendor: pci 0x100b "National Semiconductor Corporation" Device: pci 0x0020 "DP83815 (MacPhyter) Ethernet Controller" SubVendor: pci 0x1584 "Uniwill Computer Corp" SubDevice: pci 0x9011 Driver: "natsemi" Driver Modules: "natsemi" Device File: eth0 I/O Ports: 0xc800-0xc8ff (rw) Memory Range: 0xdfdfe000-0xdfdfefff (rw,non-prefetchable) Memory Range: 0xdfde0000-0xdfdeffff (ro,non-prefetchable,disabled) IRQ: 17 (6 events) HW Address: 00:03:0d:05:17:fc Link detected: no Module Alias: "pci:v0000100Bd00000020sv00001584sd00009011bc02sc00i00" Driver Info #0: Driver Status: natsemi is active Driver Activation Cmd: "modprobe natsemi" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #15 (PCI bridge) 39: USB 00.0: 0282 WLAN controller [Created at usb.122] Unique ID: Uc5H.KDHpt7NkXbE Parent ID: k4bc.9T1GDCLyFd9 SysFS ID: /devices/pci0000:00/0000:00:1d.7/usb1/1-4/1-4:1.0 SysFS BusID: 1-4:1.0 Hardware Class: network Model: "ASUSTek ASUS EZ N Network Adapter" <======================= Hotplug: USB Vendor: usb 0x0b05 "ASUSTek Computer, Inc." Device: usb 0x1786 "ASUS EZ N Network Adapter" Revision: "2.00" Serial ID: "00e04c000001" Driver: "r8712u" Driver Modules: "r8712u" Device File: wlan0 Features: WLAN Speed: 480 Mbps HW Address: 08:60:6e:63:f6:3c Link detected: yes WLAN channels: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 WLAN frequencies: 2.412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 2.457 2.462 2.467 2.472 2.484 WLAN bitrates: 1 2 5.5 11 WLAN encryption modes: TKIP CCMP WLAN authentication modes: open wpa-psk wpa-eap Module Alias: "usb:v0B05p1786d0200dc00dsc00dp00icFFiscFFipFFin00" Driver Info #0: Driver Status: r8712u is active Driver Activation Cmd: "modprobe r8712u" Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #38 (Hub) AmonLanc:~/Bugzilla # -- 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 13

[Bug 799741] New: No USB with VirtualBox 4.1.22 nor 4.2.6, although following the usual practices
by bugzilla_noreply＠novell.com 08 Jan '14

08 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=799741 https://bugzilla.novell.com/show_bug.cgi?id=799741#c0 Summary: No USB with VirtualBox 4.1.22 nor 4.2.6, although following the usual practices Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: hpj(a)urpla.net QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 Neither after installation VirtualBox from 12.2 distro nor from Virtualization repo, USB is operational. Reproducible: Always Steps to Reproduce: 1. Install virtualbox-{,qt-}4.1.22-1.6.1.x86_64, virtualbox-host-kmp-desktop-4.1.22_k3.4.6_2.10-1.6.1.x86_64 2. add yourself to vboxusers group 3. uncomment both lines starting with SUBSYSTEM in /etc/udev/rules.d/60-vboxdrv.rules, reboot Actual Results: No USB devices available Expected Results: Some USB devices should appear Given the procedure from above, everything is well as root: # VBoxManage list usbhost Host USB Devices: UUID: 781437c5-20fe-4f32-84db-00fd67d14191 VendorId: 0x046a (046A) ProductId: 0x0001 (0001) Revision: 0.38 (0038) Manufacturer: Cherry GmbH Address: sysfs:/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.6//device:/dev/bus/usb/002/004 Current State: Busy UUID: e10727b2-c725-4f0b-89da-fa3a51e4eacc VendorId: 0x046d (046D) ProductId: 0x08cc (08CC) Revision: 0.5 (0005) SerialNumber: 021CCCA2 Address: sysfs:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5//device:/dev/bus/usb/001/003 Current State: Busy UUID: 90f55d66-b641-4747-803b-009e6a0b7198 VendorId: 0x046d (046D) ProductId: 0xc51b (C51B) Revision: 70.0 (7000) Manufacturer: Logitech Product: USB Receiver Address: sysfs:/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5//device:/dev/bus/usb/002/003 Current State: Busy UUID: a6e31dba-dedf-4bf4-8aac-173449e8973f VendorId: 0x04b8 (04B8) ProductId: 0x0119 (0119) Revision: 1.0 (0100) Manufacturer: EPSON Product: EPSON Scanner Address: sysfs:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.6//device:/dev/bus/usb/001/004 Current State: Available UUID: bd712d55-18b6-4131-9695-88c1e4233e36 VendorId: 0x0781 (0781) ProductId: 0x5406 (5406) Revision: 2.0 (0200) Manufacturer: SanDisk Product: U3 Cruzer Micro SerialNumber: 2243401663D29C63 Address: sysfs:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3//device:/dev/bus/usb/001/005 Current State: Available but not for me as a user: hp@xrated:~> VBoxManage list usbhost Host USB Devices: <none> although: hp@xrated:~> id uid=1000(hp) gid=2222(lisa) Gruppen=2222(lisa),17(audio),20(cdrom),33(video),125(vboxusers),513(domuser),1000(users), 7 more... I'm member of 125(vboxusers). VBox devices are in place: hp@xrated:~> l -R /dev/vboxusb/ /dev/vboxusb/: insgesamt 0 drwxr-xr-x 4 root vboxusers 80 21. Jan 22:51 ./ drwxr-xr-x 21 root root 4900 21. Jan 22:53 ../ drwxr-xr-x 2 root root 140 21. Jan 22:53 1/ drwxr-xr-x 2 root root 120 21. Jan 22:51 2/ /dev/vboxusb/1: insgesamt 0 drwxr-xr-x 2 root root 140 21. Jan 22:53 ./ drwxr-xr-x 4 root vboxusers 80 21. Jan 22:51 ../ lrwxrwxrwx 1 root root 21 21. Jan 22:51 1 -> ../../bus/usb/001/001 lrwxrwxrwx 1 root root 21 21. Jan 22:51 2 -> ../../bus/usb/001/002 lrwxrwxrwx 1 root root 21 21. Jan 22:51 3 -> ../../bus/usb/001/003 lrwxrwxrwx 1 root root 21 21. Jan 22:51 4 -> ../../bus/usb/001/004 lrwxrwxrwx 1 root root 21 21. Jan 22:53 5 -> ../../bus/usb/001/005 /dev/vboxusb/2: insgesamt 0 drwxr-xr-x 2 root root 120 21. Jan 22:51 ./ drwxr-xr-x 4 root vboxusers 80 21. Jan 22:51 ../ lrwxrwxrwx 1 root root 21 21. Jan 22:51 1 -> ../../bus/usb/002/001 lrwxrwxrwx 1 root root 21 21. Jan 22:51 2 -> ../../bus/usb/002/002 lrwxrwxrwx 1 root root 21 21. Jan 22:51 3 -> ../../bus/usb/002/003 lrwxrwxrwx 1 root root 21 21. Jan 22:51 4 -> ../../bus/usb/002/004 acls, set by udev, are fine: hp@xrated:~> getfacl -R /dev/vboxusb/{1,2}/* getfacl: Entferne führende '/' von absoluten Pfadnamen # file: dev/vboxusb/1/1 # owner: root # group: root user::rw- group::rw- group:vboxusers:rw- mask::rw- other::r-- # file: dev/vboxusb/1/2 # owner: root # group: users user::rw- group::rw- group:vboxusers:rw- mask::rw- other::--- # file: dev/vboxusb/1/3 # owner: root # group: root user::rw- group::rw- group:vboxusers:rw- mask::rw- other::r-- # file: dev/vboxusb/1/4 # owner: root # group: lp user::rw- group::rw- group:vboxusers:rw- mask::rw- other::r-- # file: dev/vboxusb/1/5 # owner: root # group: root user::rw- group::rw- group:vboxusers:rw- mask::rw- other::r-- # file: dev/vboxusb/2/1 # owner: root # group: root user::rw- group::rw- group:vboxusers:rw- mask::rw- other::r-- # file: dev/vboxusb/2/2 # owner: root # group: users user::rw- group::rw- group:vboxusers:rw- mask::rw- other::--- # file: dev/vboxusb/2/3 # owner: root # group: root user::rw- group::rw- group:vboxusers:rw- mask::rw- other::r-- # file: dev/vboxusb/2/4 # owner: root # group: root user::rw- group::rw- group:vboxusers:rw- mask::rw- other::r-- The correct extpack is installed: hp@xrated:~> VBoxManage list extpacks Extension Packs: 1 Pack no. 0: Oracle VM VirtualBox Extension Pack Version: 4.1.22 Revision: 80657 Description: USB 2.0 Host Controller, VirtualBox RDP, PXE ROM with E1000 support. VRDE Module: VBoxVRDP Usable: true Why unusable: I've red pretty much every openSUSE USB problem related to virtualbox, but nothing fits. It's something unusual, although I manage a few remote users, that suffer from the very same issue. The same behavior happens with current version 4.2.6. Stracing both "VBoxManage list usbhost" invocations differ significantly, but doesn't reveal real hints to the issue. IPC Communication seems to flow though a named pipe, which fails on the first connect, but succeeds on the second attempt. For some reason, as a user it tries to access /dev/vboxusb/001/005, while the node is at /dev/vboxusb/1/5, but that would fail for the root case in equal ways, wouldn't it? An upstream report is rightfully closed as being somebody elses problem. https://www.virtualbox.org/ticket/11199 I'm stuck. Somebody with more ideas? I'm able to provide any necessary additional info, if requested. -- 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