December 2013 - openSUSE Bugs - openSUSE Mailing Lists

[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

[Bug 851287] New: Double-click in partitioner should edit
by bugzilla_noreply＠novell.com 08 Jan '14

08 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=851287 https://bugzilla.novell.com/show_bug.cgi?id=851287#c0 Summary: Double-click in partitioner should edit Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: msvec(a)suse.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- Double click on a partition in the partitioner should edit the particular partition, at least that's what's the expected behavior. Now it just goes to the summary page which is not really useful. -- 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 853087] New: "Extend swap for suspend" in the partitioner not covered by help
by bugzilla_noreply＠novell.com 08 Jan '14

08 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=853087 https://bugzilla.novell.com/show_bug.cgi?id=853087#c0 Summary: "Extend swap for suspend" in the partitioner not covered by help 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: gp(a)suse.com QAContact: jsrain(a)suse.com Found By: Product Management Blocker: --- Installing openSUSE 13.1 and specifying a swap partition of 1 GB on a system with 2 GB memory I noticed the "Swap für Suspend erweitern" (German) checkbox, probably "Extend swap for suspend" or similar in English. Invoking "Help" to understand what this is about, I found this is not covered in the help screen at all. -- 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 851048] New: Old SSSD Variable in YaST Config
by bugzilla_noreply＠novell.com 08 Jan '14

08 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=851048 https://bugzilla.novell.com/show_bug.cgi?id=851048#c0 Summary: Old SSSD Variable in YaST Config Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: gjn(a)gjn.priv.at QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:25.0) Gecko/20100101 Firefox/25.0 After 2 Years it is time to change to the correct Variables ;) OLD krb5_kdcip (depcreated) NEW krb5_server Also the krb5_kpasswd Variable is not set :(. It can be set to krb5_server This Problem fill up only the sssd_default.log 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 11

[Bug 774379] New: no serial login offered after installation
by bugzilla_noreply＠novell.com 08 Jan '14

08 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=774379 https://bugzilla.novell.com/show_bug.cgi?id=774379#c0 Summary: no serial login offered after installation Classification: openSUSE Product: openSUSE 12.2 Version: RC 2 Platform: x86-64 OS/Version: Linux Status: NEW Severity: Critical Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: ohering(a)suse.com QAContact: jsrain(a)suse.com Found By: Outsourced Testing Blocker: --- I did a fresh installation of 12.2-rc2 on stein-schneider.arch.suse.de cmdline used for install: quiet sysrq=yes panic=9 start_shell ssh=1 sshpassword=root nosshkey vnc=1 vncpassword=password linemode=1 start_shell console=ttyS0,57600 install=http://bax.arch.suse.de/abuild_disk/install/12.2/ After Installation there was no serial login offered. If I had not used vnc+ssh a login would have been impossible! (vnc login was also not enabled, but thats another bug). -- 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 850708] New: usability issue: upper form Ok/Cancel should NOT be right over bottom Ok/Cancel
by bugzilla_noreply＠novell.com 08 Jan '14

08 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=850708 https://bugzilla.novell.com/show_bug.cgi?id=850708#c0 Summary: usability issue: upper form Ok/Cancel should NOT be right over bottom Ok/Cancel Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: i586 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: grey-olli(a)ya.ru QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 If a user is not well experienced w/ computer mouse or touchpad or uses mouse that some times does two clicks when intended to click once it is possible to misuse the installation GUI by occasionally clicking twice on the same place. This is especially dangerous and annoying when doing custom disk partitioning. Reproducible: Always Steps to Reproduce: 1. open custom partitioning 2. emulate a mistake - click twice on OK. 3. The second click will go to the underlying menu. Expected Results: It is not possible to make occasionally mistake by overclicking -- 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 856641] New: Live image does not swapoff --all before partitioning the system
by bugzilla_noreply＠novell.com 08 Jan '14

08 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=856641 https://bugzilla.novell.com/show_bug.cgi?id=856641#c0 Summary: Live image does not swapoff --all before partitioning the system Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: All OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: yast2-maintainers(a)suse.de ReportedBy: seldmail(a)gmail.com QAContact: jsrain(a)suse.com Found By: Community User Blocker: --- How to reproduce: 1) Boot openSUSE 13.1 Live image (Live KDE was used in my case, but I suppose it applies to Live GNOME as well) 2) Run the installation right from the Live image 3) Change partitioning during installation: move/remove swap partition 4) Start the installation What happens: Installation program cannot move/delete Swap partition, because it is mounted (this happens automatically, when Live image finds Swap partition in the system). As a result, an error message with error code pops-up and installation is aborted. At the moment I have neither screenshot, nor error code at hand. What should happen: First, installation program should unmount all Swap partitions used by Live image, and only then continue the installation. If I do this manually... # swapoff --all ..and then start installation, the installer works without failure and system is partitioned correctly. Additional information: I have found this bug in openSUSE 12.3 Live image installer too. -- 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 852179] New: RN: openSUSE 13.1 update wanted
by bugzilla_noreply＠novell.com 08 Jan '14

08 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=852179 https://bugzilla.novell.com/show_bug.cgi?id=852179#c0 Summary: RN: openSUSE 13.1 update wanted Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: Other OS/Version: Other Status: ASSIGNED Severity: Normal Priority: P5 - None Component: Release Notes AssignedTo: ke(a)suse.com ReportedBy: ke(a)suse.com QAContact: coolo(a)suse.com Depends on: 850058,851588 Found By: Documentation Blocker: --- collecting... -- 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 705502] New: suse-ami-tools initscripts shoudn't use $ALL target
by bugzilla_noreply＠novell.com 08 Jan '14

08 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=705502 https://bugzilla.novell.com/show_bug.cgi?id=705502#c0 Summary: suse-ami-tools initscripts shoudn't use $ALL target Classification: openSUSE Product: openSUSE 12.1 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: fcrozat(a)novell.com QAContact: qa(a)suse.de Blocks: 696902 Found By: --- Blocker: --- there is no plan in systemd to support SUSE non official $ALL LSB target in initscripts. It should be removed from /etc/init.d/amazon-late initscript in suse-ami-tools package. -- 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 849732] New: RC2 - Undefined video mode number 37e
by bugzilla_noreply＠novell.com 08 Jan '14

08 Jan '14

https://bugzilla.novell.com/show_bug.cgi?id=849732 https://bugzilla.novell.com/show_bug.cgi?id=849732#c0 Summary: RC2 - Undefined video mode number 37e Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: bam(a)NightStorm.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 During install I get a "Undefined video mode 37e and an option to "SCAN". If I select SCAN I get a list prefixed by some single character. I am asked to select an entry (confusing here: select the single "a-z" character or the video mode number?). Selecting one of the modes in the menu gives an "Undefined video mode number" (does not matter if I enter the video mode "37F" or the character "o). Reproducible: Always Steps to Reproduce: 1.After booting to installer hit "F3" and select "1920x1200" video mode 2.Get the error "Undefined video mode" with an option to "SCAN" 3.Enter "SCAN". 4.Select one of the presented modes, either by menu character (a-z) or video mode number (37E). 5.Higher modes fail, even though the display is in the correct mode (1920x1200 for me). Actual Results: Failure. After 30 seconds the presentation times out and the install continues. Expected Results: Accept the mode? -- 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