December 2014 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 900001] New: Lock screen freezes Shell
by bugzilla_noreply＠novell.com 10 Aug '17

10 Aug '17

http://bugzilla.opensuse.org/show_bug.cgi?id=900001 Bug ID: 900001 Summary: Lock screen freezes Shell Classification: openSUSE Product: openSUSE Factory Version: 13.2 Beta 1 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Critical Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: roger.luedecke(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When returning to computer after screen dims. Lock screen almost always is unresponsive though the indicators on the shell in the upper right may be responsive. I turned off the lock, and now it will go to desktop but the entire interface freezes there. This happens every time. -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 849735] New: Xorg is leaking large amounts of memory
by bugzilla_noreply＠novell.com 08 Aug '17

08 Aug '17

https://bugzilla.novell.com/show_bug.cgi?id=849735 https://bugzilla.novell.com/show_bug.cgi?id=849735#c0 Summary: Xorg is leaking large amounts of memory Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: X.Org AssignedTo: bnc-team-xorg-bugs(a)forge.provo.novell.com ReportedBy: Antoine.Saroufim(a)gmail.com QAContact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:25.0) Gecko/20100101 Firefox/25.0 The X.org process is leaking a large amount of memory. It can go up to 2.5 gbs. Reproducible: Sometimes Steps to Reproduce: 1. 2. 3. Expected Results: Xorg should not leak large amounts of memory I've noticed that using Wine allows it to leak memory. I'm not sure if this is the only cause. It doesn't always leak memory with wine. I'm using the Nvidia proprietary drivers. That also could affect this. -- 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 624196] New: Request for opencv to be built with TBB support
by bugzilla_noreply＠novell.com 05 Aug '17

05 Aug '17

http://bugzilla.novell.com/show_bug.cgi?id=624196 http://bugzilla.novell.com/show_bug.cgi?id=624196#c0 Summary: Request for opencv to be built with TBB support Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: Macintosh OS/Version: openSUSE 11.2 Status: NEW Severity: Enhancement Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: alexjironkin(a)gmail.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.2.7) Gecko/20100714 SUSE/3.6.7-1.1 Firefox/3.6.7 Since version OpenCV 2.1, which comes as part of the base packages now in 11.3 I think, OpenMP has been replaced by TBB. However OpenCV buid without that support on opensuse 11.2. Using TBB will greatly enhance all application using OpenCV e.g. digikam. Reproducible: Always Steps to Reproduce: 1. 2. 3. The request is to have either a separate package or enable OpenCV with TBB. Ubuntu 10.4 packages already do that so its stable enough to work with. -- Configure bugmail: http://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 785437] New: openSUSE:12.2/freerdp: Bug
by bugzilla_noreply＠novell.com 04 Aug '17

04 Aug '17

https://bugzilla.novell.com/show_bug.cgi?id=785437 https://bugzilla.novell.com/show_bug.cgi?id=785437#c0 Summary: openSUSE:12.2/freerdp: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: 3rd party software AssignedTo: gber(a)opensuse.org ReportedBy: bruno(a)ioda-net.ch QAContact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- With new version and certainly linked to the "hack" of shared lib Trying to launch an xfreerdp connection on a remote win7-64 working machine ( still accessible with xfreerdp 0.8.2 & openSUSE 12.1) There's now a error message me@linux:~> /usr/bin/xfreerdp -z -a 32 -k 0x0000100C --plugin cliprdr --plugin rdpsnd --gdi hw --rfx --ignore-certificate --no-nla -0 -g 1300x700 -f -n me.local -u administrator -d test2012-64 test2012-64 loading plugin cliprdr loading plugin rdpsnd connected to test2012-64:3389 /usr/bin/xfreerdp: symbol lookup error: /usr/lib64/libfreerdp-1_0/rdpsnd_pulse.so: undefined symbol: pa_threaded_mainloop_new Please verify, thanks -- 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 22

[Bug 903753] New: usb_modeswitch-2.1.1-2.3.1.x86_64 is incompatible with usb_modeswitch-data-2.1.1-2.3.1.noarch
by bugzilla_noreply＠novell.com 02 Aug '17

02 Aug '17

http://bugzilla.opensuse.org/show_bug.cgi?id=903753 Bug ID: 903753 Summary: usb_modeswitch-2.1.1-2.3.1.x86_64 is incompatible with usb_modeswitch-data-2.1.1-2.3.1.noarch Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: bpesavento(a)infinito.it QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- In 13.2-OSS repo, package usb_modeswitch-2.1.1-2.3.1.x86_64 is incompatible with matching package usb_modeswitch-data-2.1.1-2.3.1.noarch. Huawei 3G dongles do not switch out of "CD-mode" with thiis setup. With the first one, usb_modeswitch -e yields: * usb_modeswitch: handle USB devices with multiple modes * Version 2.1.1 (C) Josua Dietze 2014 * Based on libusb1/libusbx while the second contains file 40-usb_modeswitch.rules which reads: # Part of usb-modeswitch-data, version 20140529 # # Works with usb_modeswitch versions >= 2.2.0 (introduction of HuaweiNewMode) A workaround is installing usb_modeswitch-data-2.1.1-2.1.6.noarch (from 13.2RC1) whose file 40-usb_modeswitch.rules reads: # Part of usb-modeswitch-data, version 20140327 # # Works with usb_modeswitch versions >= 2.1.0 (introduction of StandardEject) Versions 5.1 and 14.1 available in additional repos as of today are affected too. -- You are receiving this mail because: You are on the CC list for the bug.

1 10

[Bug 909962] New: bootscreen asking for passphrase not explanatory
by bugzilla_noreply＠novell.com 01 Aug '17

01 Aug '17

http://bugzilla.opensuse.org/show_bug.cgi?id=909962 Bug ID: 909962 Summary: bootscreen asking for passphrase not explanatory Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: aschnell(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The bootscreen asking for the passphrase of an encrypted partition is not explanatory. See attached screenshot of 13.2 and in comparison of 12.3. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 907719] New: Konqueror and rekonq do not use initially configured fonts
by bugzilla_noreply＠novell.com 01 Aug '17

01 Aug '17

http://bugzilla.opensuse.org/show_bug.cgi?id=907719 Bug ID: 907719 Summary: Konqueror and rekonq do not use initially configured fonts Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Applications Assignee: kde-maintainers(a)suse.de Reporter: nrickert(a)ameritech.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:33.0) Gecko/20100101 Firefox/33.0 Build Identifier: Here's a link to a forum thread on this issue: https://forums.opensuse.org/showthread.php/503103-CODE-blocks-are-broken-in… I noticed that code blocks were not working correctly in "konqueror" and "rekonq" and reported that at the forum. The suggestion was made, that I change the konqueror fixed font from its default ("Liberation Mono") to something like Courier which was known to be fixed width. I tried that. It fixed the problem. Then I changed back to "Liberation Mono", and the problem stayed fixed. It seems that before I configured that font, it was not actually using the "Liberation Mono" that its configuration said it was using. This looks like a problem with initial setup of "konqueror". And "rekonq" has the same problem -- maybe "akregator" has the problem too, but I didn't try to check that. I'm not sure if this is an opensuse bug or an upstream KDE bug. But I'll start here. Reproducible: Always -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 907672] New: Bootloader grub2-efi installation fails - unable to boot from EFI disk later
by bugzilla_noreply＠novell.com 01 Aug '17

01 Aug '17

http://bugzilla.opensuse.org/show_bug.cgi?id=907672 Bug ID: 907672 Summary: Bootloader grub2-efi installation fails - unable to boot from EFI disk later Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: IA64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: jsrain(a)suse.com Reporter: woa46(a)yahoo.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 615396 --> http://bugzilla.opensuse.org/attachment.cgi?id=615396&action=edit strace run of successful invocation of efibootmgr I have a problem with grub2-efi that is similar to Bug 822770. On initial installation, the bootloader installation produced the message about an error in the bootloader system and gave the option of retrying or ignoring it. I tried one retry and it didn't work, so I ignored it. The system did not boot when the installation disk was removed and I booted the rescue system. On typing efibootmgr, I got the following output: BootCurrent: 0002 Timeout: 2 seconds BootOrder: 2002,2003,2001 Boot0000* EFI Network 0 for IPv4 (C4-54-44-04-C9-78) Boot0001* EFI Network 0 for IPv6 (C4-54-44-04-C9-78) Boot0002* EFI DVD/CDROM (MATSHITABD-MLT UJ272) Boot2001* EFI USB Device Boot2002* EFI DVD/CDROM Boot2003* EFI Network I typed: efibootmgr -c -d /dev/sdc -p 2 -L opensuse -l \\EFI\\opensuse\\grubx64.efi It failed with ENOSPC which indicates that the Bios EFI subsystem is out of resources. After this, I tried a number of things and sometimes the same command would succeed with Boot0003 correctly installed. After this, I reflashed the Bios and the command would succeed with the following output: Timeout: 0 seconds BootOrder: 0004,0003,2003,2001,2002 Boot0000* EFI USB Device (KingstonDataTraveler 3.0) Boot0001* EFI Network 0 for IPv4 (C4-54-44-04-C9-78) Boot0002* EFI Network 0 for IPv6 (C4-54-44-04-C9-78) Boot0003* opensuse-secureboot Boot2001* EFI USB Device Boot2002* EFI DVD/CDROM Boot2003* EFI Network Boot0004* opensuse A verbose run of efibootmgr gives the following output: BootCurrent: 0000 Timeout: 0 seconds BootOrder: 0004,0003,2001,2003,2002 Boot0000* EFI USB Device (KingstonDataTraveler 3.0) ACPI(a0341d0,0)PCI(1d,0)USB(0,0)USB(0,0)HD(1,800,200001,5b8c0aab)RC Boot0001* EFI Network 0 for IPv4 (C4-54-44-04-C9-78) ACPI(a0341d0,0)PCI(1c,3)PCI(0,0)MAC(c4544404c978,0)IPv4(0.0.0.0:0<->0.0.0.0:0,0, 0RC Boot0002* EFI Network 0 for IPv6 (C4-54-44-04-C9-78) ACPI(a0341d0,0)PCI(1c,3)PCI(0,0)MAC(c4544404c978,0)030d3c000000000000000000000000000000000000000000000000000000000000000000000000000000004000000000000000000000000000000000RC Boot0003* opensuse-secureboot HD(1,800,200001,5b8c0aab)File(\EFI\opensuse\shim.efi) Boot2001* EFI USB Device RC Boot2002* EFI DVD/CDROM RC Boot2003* EFI Network RC Boot0004* opensuse HD(2,200800,32000,30ef0665-2a13-11e3-a895-a67aabe62594)File(\EFI\opensuse\grubx64.efi) (by now, I was booting off of a flash drive) I made an strace of a successful run of efibootmgr and have left it in the attachment efibootmgr.strace. Again, when I try to boot off of the disk, it indicates that there is no bootable device and when I boot off of the rescue system, the opensuse boot that I just installed is not there. It appears that for some reason, the EFI subsystem of the Bios is deleting the disk boot on system reboot. Or else, the ops->set_variable command of the EFI efi_runtime_services_64_t table is accepting the command to set the variable and silently discarding it. There is another problem that appears to be with the EFI subsystem. The intel_bios_dumper command fails with EIO. An strace of this command in operation is in the attachment for bios.strace. Finally, I tried to set up a windows boot on my flash drive with the following grub2 code: menuentry 'Windows Boot Manager (on /dev/sdc2)' { insmod chain insmod part_gpt insmod fat search --fs-uuid --set=root 62a3-a7b0 set prefix=(${root})/EFI/Microsoft/Boot echo $prefix: ls $prefix chainloader $prefix/bootmgfw.efi } On booting this entry, it properly lists the contents of the /EFI/Microsoft/Boot directory, but then fails on the invocation of the chainloader command with the message "not a valid root device". At the lower level in the grub2-efi code, it is making a call to the ops->open_protocol function of the efi_boot_services_64_t table. I cannot get the returned status with strace since this is a boot program. On conlusion, it appears that the EFI subsystem of the Bios is not performing correctly. Whether this is configuration issue or there is a more serious problem. I thought that at the minimum, your technical support staff would be able to find out why it is deleting the new boot entry on boot. I would think that this problem has occurred before during development. I thank you sincerely for any help that you can provide. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 905808] New: MATE / caja gone mad
by bugzilla_noreply＠novell.com 01 Aug '17

01 Aug '17

http://bugzilla.opensuse.org/show_bug.cgi?id=905808 Bug ID: 905808 Summary: MATE / caja gone mad Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: nrickert(a)ameritech.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:33.0) Gecko/20100101 Firefox/33.0 Build Identifier: This is a second computer where I have installed MATE. When I login to MATE, the panel is filled with a gazillion "caja" icons. The number seems to be ever growing. There is only one caja process running, as far as I can see. It is at around 88% of cpu. I had to use CTRL-ALT-BACKSPACE to abort the X-session. This did not happen for my first MATE install, so I'll list the main differences. First install (behaves properly): Intel video, only MATE desktop is installed. Second install (behaves badly): Nvidia video with the "nvidia" 304.123 driver, installed via the "nvidia" repo. KDE, Gnome, XFCE, LXDE all installed in addition to MATE. I'm guessing that it is the nvidia graphics causing the problem, but that is only a guess. I will attach a copy of ".xsession-errors-:0" Reproducible: Didn't try This happens for every login. I was able to add a MATE menu to the panel. Using "logout" from the menu does not terminate the session. I had to use CTRL-ALT-BACKSPACE for that. -- You are receiving this mail because: You are on the CC list for the bug.

1 15

[Bug 901006] New: konqueror is crashing (as are rekonq and qupzilla)
by bugzilla_noreply＠novell.com 01 Aug '17

01 Aug '17

http://bugzilla.opensuse.org/show_bug.cgi?id=901006 Bug ID: 901006 Summary: konqueror is crashing (as are rekonq and qupzilla) Classification: openSUSE Product: openSUSE Factory Version: NO 13.2 BUGS!! Hardware: PC OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Applications Assignee: kde-maintainers(a)suse.de Reporter: nrickert(a)ameritech.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:32.0) Gecko/20100101 Firefox/32.0 Build Identifier: Konqueror Version 4.14.1 Using KDE Development Platform 4.14.1 from factory snapshot 20141011 (x86_64) konqueror crashes make the application useless. If I open konqueror, and browse to: http://www.patheos.com/blogs/friendlyatheist/ it will crash with a segfault. Both "rekonq" and "qupzilla" behave similarly. This used to work. As best I remember, it started failing after the update to the 20140928 factory snapshot. The KDE bug reporter says that this is the stack trace: Application: Konqueror (konqueror), signal: Segmentation fault [Current thread is 1 (process 12308)] Thread 1 (process 12308): #0 0x00007fb1be9c06cd in ?? () #1 0x0000000000000000 in ?? () It also indicates that this is useless. I have enabled the debug repo, but the KDE reporter cannot find debug symbols. I have installed "kdelibs4-debuginfo", but the crash reporter still cannot find debug symbols. It reports that they are needed for "kdeinit4" which does seem to be in "kdelibs4". Reproducible: Always Steps to Reproduce: 1. start konqueror 2. browse to www.patheos.com 3. Actual Results: konqueror crashes Expected Results: konqueror should show the page This happens on three different computer running factory. Two of them use Intel graphics, and the third uses Nvidia graphics (with nvidia driver). So probably not related to the graphics. -- You are receiving this mail because: You are on the CC list for the bug.

1 11