June 2013 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 820572] New: Java VM crashed when execute eclipse environment
by bugzilla_noreply＠novell.com 04 Jun '13

04 Jun '13

https://bugzilla.novell.com/show_bug.cgi?id=820572 https://bugzilla.novell.com/show_bug.cgi?id=820572#c0 Summary: Java VM crashed when execute eclipse environment Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 1 Platform: x86-64 OS/Version: SUSE Other Status: NEW Severity: Critical Priority: P5 - None Component: Java AssignedTo: bnc-team-java(a)forge.provo.novell.com ReportedBy: fbernasek(a)netscape.net QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=539933) --> (http://bugzilla.novell.com/attachment.cgi?id=539933) Java VM Logfile after crash User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:21.0) Gecko/20100101 Firefox/21.0 java VM crashed when execute eclipse based envionments, reason ( see log ) SIGSEGV libsoup Reproducible: Always Steps to Reproduce: 1. login 2. select IDE 3. start it 4. select help 5. IDE crashed Actual Results: java crashed Expected Results: normal work with IDE -- 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 819511] New: Scanner not working after laptop change and update from openSUSE 12.1 to 12.3
by bugzilla_noreply＠novell.com 04 Jun '13

04 Jun '13

https://bugzilla.novell.com/show_bug.cgi?id=819511 https://bugzilla.novell.com/show_bug.cgi?id=819511#c0 Summary: Scanner not working after laptop change and update from openSUSE 12.1 to 12.3 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: thorsten(a)tws-home.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:20.0) Gecko/20100101 Firefox/20.0 It is not possible to use my USB scanner anymore. I have a Lenovo N581 laptop and tried all USB 2.0 and USB 3.0 ports with different USB cables. I also put the device on the laptop-mode blacklist so, that no powersave mode is used for the scanner. In YaST2 I tried to setup the scanner. The detection sais that plustek does not recognize a scanner, but actually it always detected my scanner in previous openSUSE versions. The second detected entry is the driver "not configured" which shows my scanner. I can the configure it and it sais that the plustek driver is configured for usage. But in the end no scanning is possible with any scan program. Reproducible: Always Steps to Reproduce: 1. Plug USB Canon CanoScanLiDE 20 to the laptop 2. Configure scanner using YaST 3. Start scanimage, xsane or any other scan program Actual Results: Every tool says that there is no scanner Expected Results: Scanning should work as before. Every information was collected as root uname -a ========= Linux tuvok.tws-home.de 3.7.10-1.4-desktop #1 SMP PREEMPT Fri Apr 19 12:06:34 UTC 2013 (8ef74f8) x86_64 x86_64 x86_64 GNU/Linux lsusb ===== Bus 001 Device 005: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 003 Device 019: ID 04a9:220d Canon, Inc. CanoScan N670U/N676U/LiDE 20 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 046d:c526 Logitech, Inc. Nano Receiver Bus 001 Device 007: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 002 Device 003: ID 04f2:b2e2 Chicony Electronics Co., Ltd hwinfo --scanner ================ 19: USB 00.0: 10c00 Scanner [Created at usb.122] Unique ID: CiZ2.7cEn5TM7z0A Parent ID: uIhY.2DFUsyrieMD SysFS ID: /devices/pci0000:00/0000:00:14.0/usb3/3-3/3-3:1.0 SysFS BusID: 3-3:1.0 Hardware Class: scanner Model: "Canon CanoScan N670U/N676U/LiDE 20" Hotplug: USB Vendor: usb 0x04a9 "Canon" Device: usb 0x220d "CanoScan N670U/N676U/LiDE 20" Revision: "1.00" Speed: 12 Mbps Module Alias: "usb:v04A9p220Dd0100dcFFdsc00dpFFicFFisc00ipFFin00" Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #18 (Hub) sane-find-scanner ================= # sane-find-scanner will now attempt to detect your scanner. If the # result is different from what you expected, first make sure your # scanner is powered up and properly connected to your computer. # No SCSI scanners found. If you expected something different, make sure that # you have loaded a kernel SCSI driver for your SCSI adapter. found USB scanner (vendor=0x04a9 [Canon], product=0x220d [CanoScan]) at libusb:003:019 found USB scanner (vendor=0x0bda [Generic], product=0x0129 [USB2.0-CRW]) at libusb:001:007 # Your USB scanner was (probably) detected. It may or may not be supported by # SANE. Try scanimage -L and read the backend's manpage. # Not checking for parallel port scanners. # Most Scanners connected to the parallel port or other proprietary ports # can't be detected by this program. scanimage -L (called for the fist time after connecting the scanner) ==================================================================== device `plustek:libusb:003:020' is a Canon CanoScan N670U/N676U/LiDE20 flatbed scanner (then if takes about 2 minutes until the program returns to the command line) scanimage -L (called for the second+ time after connecting the scanner) ======================================================================= (it takes about 40 seconds until an output is written to the console) No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages). /var/log/messages ================= 2013-05-11T20:03:43.285338+02:00 tuvok kernel: [158418.735384] usb 3-2: USB disconnect, device number 21 2013-05-11T20:03:46.298343+02:00 tuvok kernel: [158421.741961] usb 3-2: new full-speed USB device number 22 using xhci_hcd 2013-05-11T20:03:46.310346+02:00 tuvok kernel: [158421.754069] usb 3-2: New USB device found, idVendor=04a9, idProduct=220d 2013-05-11T20:03:46.310363+02:00 tuvok kernel: [158421.754073] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 2013-05-11T20:03:46.310365+02:00 tuvok kernel: [158421.754076] usb 3-2: Product: CanoScan 2013-05-11T20:03:46.310366+02:00 tuvok kernel: [158421.754078] usb 3-2: Manufacturer: Canon 2013-05-11T20:03:46.372186+02:00 tuvok laptop-mode: Laptop mode 2013-05-11T20:03:46.373634+02:00 tuvok laptop-mode: enabled, not active 2013-05-11T20:03:46.396935+02:00 tuvok laptop-mode: Laptop mode 2013-05-11T20:03:46.398593+02:00 tuvok laptop-mode: enabled, not active Is there anything that I can add to this list? -- 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 712726] New: Fix error source for a SIGSEGV crash from a small OCaml test program
by bugzilla_noreply＠novell.com 04 Jun '13

04 Jun '13

https://bugzilla.novell.com/show_bug.cgi?id=712726 https://bugzilla.novell.com/show_bug.cgi?id=712726#c0 Summary: Fix error source for a SIGSEGV crash from a small OCaml test program Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Normal Priority: P5 - None Component: Development AssignedTo: pth(a)novell.com ReportedBy: Markus.Elfring(a)web.de QAContact: qa(a)suse.de Found By: --- Blocker: --- The compilation of a source file which contains only the instruction 'let _ = Printf.printf "hello\n"' works by the the command 'ocamlopt -o foo foo.ml'. But I get the error message 'Speicherzugriffsfehler' if I try the execution of the generated program './foo' from my test directory. The tool "GNU gdb (GDB) SUSE (7.2-3.3)" shows only a little bit more information at the moment: Program received signal SIGSEGV, Segmentation fault. 0x000000000062ee00 in strcpy@@GLIBC_2.2.5 () Does the package "camlp4/ocaml 3.12.0-2.1" need corresponding improvements? -- 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 23

[Bug 809277] AUDIT-0: udisks2: udisks 2.0.9x review of new polkit privileges
by bugzilla_noreply＠novell.com 04 Jun '13

04 Jun '13

https://bugzilla.novell.com/show_bug.cgi?id=809277 https://bugzilla.novell.com/show_bug.cgi?id=809277#c6 Marcus Meissner <meissner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #6 from Marcus Meissner <meissner(a)suse.com> 2013-06-04 03:44:19 UTC --- is actually in polkit-default-privs in factory already. -- 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 809277] AUDIT-0: udisks2: udisks 2.0.9x review of new polkit privileges
by bugzilla_noreply＠novell.com 04 Jun '13

04 Jun '13

https://bugzilla.novell.com/show_bug.cgi?id=809277 https://bugzilla.novell.com/show_bug.cgi?id=809277#c Marcus Meissner <meissner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Group|novellonly | -- 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 765270] talloc declared LGPL-3.0+ but contains GPL-3.0+ licenses
by bugzilla_noreply＠novell.com 04 Jun '13

04 Jun '13

https://bugzilla.novell.com/show_bug.cgi?id=765270 https://bugzilla.novell.com/show_bug.cgi?id=765270#c19 --- Comment #19 from David Disseldorp <ddiss(a)suse.com> 2013-06-04 03:28:19 UTC --- FWIW, the license ambiguity has been fixed upstream via https://bugzilla.samba.org/show_bug.cgi?id=8997 . -- 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 738520] New: Using bluez to disable Bluetooth USB device leaves it unusable
by bugzilla_noreply＠novell.com 04 Jun '13

04 Jun '13

https://bugzilla.novell.com/show_bug.cgi?id=738520 https://bugzilla.novell.com/show_bug.cgi?id=738520#c0 Summary: Using bluez to disable Bluetooth USB device leaves it unusable Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: sourtooth(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20100101 Firefox/8.0 On my system, with a ASUSTek Computer, Inc. BT-253 Bluetooth Adapter, if I use Bluedevil (part of KDE 4 Workspace) to disable my Bluetooth adapter it is not possible to re-enable it. Further, it is not possible to clear this invalid state other than by taking the following steps, as root: 1) Kill bluetoothd 2) Remove all files/folders under /var/lib/bluetooth 3) Reboot the system, then enter the BIOS configuration 4) Disable the Bluetooth device using BIOS I/O Security features 5) Boot into openSUSE 6) Reboot the system, entering the BIOS configuration again 7) Enable the Bluetooth device at the BIOS level again 8) Boot back into openSUSE - Bluetooth device is now usable again It should be noted that if one does not remove the contents of /var/lib/bluetooth/ then bluetoothd will re-disable the device on startup, leaving it unusable again. It should also be noted that booting into an operating system of any form in between disabling and re-enabling the bluetooth device in the BIOS is crucial, otherwise the steps will have no impact. Symptoms: hcitool dev reports no devices, despite the bluetooth adapter being visible in lsusb and dbus tree of bluetoothd. In some cases, booting the system might fail after the root file system is mounted due to failures to read USB device descriptors from the Bluetooth device. Until the above procedure is performed, all operating systems will not be able to see the Bluetooth device, including Windows 7 which will claim the device is malfunctioning. Reproducible: Always Steps to Reproduce: 1. Disable bluetooth device using Bluedevil Actual Results: Bluetooth device rendered unusable Expected Results: Bluetooth device is merely disabled, and can be re-enabled easily. Rebooting into other operating systems should allow Bluetooth to be functional there as well. -- 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 794705] AUDIT-0: Request review of package lightdm-kde-greeter in repo KDE:Distro:Factory
by bugzilla_noreply＠novell.com 04 Jun '13

04 Jun '13

https://bugzilla.novell.com/show_bug.cgi?id=794705 https://bugzilla.novell.com/show_bug.cgi?id=794705#c5 --- Comment #5 from Sebastian Krahmer <krahmer(a)suse.com> 2013-06-04 03:04:15 UTC --- I cannot see that it exposes any DBUS services, it seems to be somehow started as plugin (probably by some other DBUS service) and just checks for org.kde.kcontrol.kcmlightdm.save. As this is auth_admin_keep, it can get that polkit permission. However the greeter itself seems to be vulnerable to race condition: void GreeterWindow::screenshot() { QPixmap pix = QPixmap::grabWindow(winId()); QString path = QDir::temp().absoluteFilePath("lightdm-kde-greeter-screenshot.png"); bool ok = pix.save(path); if (ok) { kDebug() << "Saved screenshot as" << path; } else { kWarning() << "Failed to save screenshot as" << path; } } looks like you can smash arbitrary files with this (Ctrl+Alt+S for screendump), depending on how safe QPixmap handles its files, but I doubt its secure. -- 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 822409] New: CanoScan N650U not recognised and horrible terrible sounds emitted, I fear it might damage the scanner
by bugzilla_noreply＠novell.com 04 Jun '13

04 Jun '13

https://bugzilla.novell.com/show_bug.cgi?id=822409 https://bugzilla.novell.com/show_bug.cgi?id=822409#c0 Summary: CanoScan N650U not recognised and horrible terrible sounds emitted, I fear it might damage the scanner Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: Other OS/Version: openSUSE 12.3 Status: NEW Severity: Critical Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: petr.danecek(a)gmail.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:21.0) Gecko/20100101 Firefox/21.0 When trying to autodetect CanoScan N650U, yast fails and scanner starts to make horrible noises. Here are some outputs to help diagnose the problem. What else I could try? It works normally in Windows. > lsusb | grep Cano Bus 005 Device 006: ID 04a9:2206 Canon, Inc. CanoScan N650U/N656U > sane-find-scanner # No USB scanners found. If you expected something different, make sure that # you have loaded a kernel driver for your USB host controller and have setup # the USB system correctly. See man sane-usb for details. > dmesg | tail [22325.410195] usb 5-1: new full-speed USB device number 6 using uhci_hcd [22325.571683] usb 5-1: New USB device found, idVendor=04a9, idProduct=2206 [22325.571689] usb 5-1: New USB device strings: Mfr=64, Product=77, SerialNumber=0 [22325.571693] usb 5-1: Product: CanoScan [22325.571696] usb 5-1: Manufacturer: Canon 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 2

[Bug 775697] New: Bluetooth device BMC20702A0 is not recognized
by bugzilla_noreply＠novell.com 04 Jun '13

04 Jun '13

https://bugzilla.novell.com/show_bug.cgi?id=775697 https://bugzilla.novell.com/show_bug.cgi?id=775697#c0 Summary: Bluetooth device BMC20702A0 is not recognized Classification: openSUSE Product: openSUSE 12.2 Version: RC 2 Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: resler(a)cs.cas.cz QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=502138) --> (http://bugzilla.novell.com/attachment.cgi?id=502138) Patch for btusb.c User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20100101 Firefox/14.0.1 Broadcom Bluetooth 4.0 USB device BMC20702A0 is used e.g. in Lenovo IdeaPad Z580 notebooks. Command lsusb lists it as "Lite-On Technology Corp." and its USB id is 04ca:2003. The device is not registered in btusb.c in struct btusb_table. After registration, the device is recognized and it works fine. I append the path for btusb.c. Reproducible: Always Steps to Reproduce: 1. 2. 3. Actual Results: No BT device is recognized by system. Expected Results: BT device is recognized and it 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 14