August 2015 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 917972] New: zypper ps truncates file names
by bugzilla_noreply＠novell.com 01 Aug '17

01 Aug '17

http://bugzilla.opensuse.org/show_bug.cgi?id=917972 Bug ID: 917972 Summary: zypper ps truncates file names Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: zypp-maintainers(a)forge.provo.novell.com Reporter: arvidjaar(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 623317 --> http://bugzilla.opensuse.org/attachment.cgi?id=623317&action=edit Screenshot of zypper ps output See attached screenshot. There is no option to wrap names as far as I can tell. This was different in 13.1 where names were wrapped. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 911685] New: Tumbleweed sha256 checksum files are using full path
by bugzilla_noreply＠novell.com 01 Aug '17

01 Aug '17

http://bugzilla.opensuse.org/show_bug.cgi?id=911685 Bug ID: 911685 Summary: Tumbleweed sha256 checksum files are using full path Classification: Internal Novell Products Product: openSUSE Build Service Version: master Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: build process Assignee: mls(a)suse.com Reporter: nrickert(a)ameritech.net QA Contact: adrian(a)suse.com Found By: --- Blocker: --- This may be misclassified (sorry). I was asked to report as a bug against Kiwi. The sha256 checksum files being built for Tumbleweed contain a full path which is not appropriate to the user. Example: The downloaded file "openSUSE-Tumbleweed-DVD-x86_64-Snapshot20150103-Media.iso.sha256" contains the line 5b47a0cc7eabdb4f3f3304c7e4fc363af4a87a11774ae5a0dac45d9632ddb681 /var/cache/obs/worker/root_2//usr/src/packages/KIWIROOT/main/openSUSE-Tumbleweed-DVD-x86_64-Snapshot20150103-Media.iso It should, instead, be using the line 5b47a0cc7eabdb4f3f3304c7e4fc363af4a87a11774ae5a0dac45d9632ddb681 openSUSE-Tumbleweed-DVD-x86_64-Snapshot20150103-Media.iso -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[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

[Bug 810239] New: midnight commander makes zfs-fuse userland not responding for approx. 30 min
by bugzilla_noreply＠novell.com 31 Jul '17

31 Jul '17

https://bugzilla.novell.com/show_bug.cgi?id=810239 https://bugzilla.novell.com/show_bug.cgi?id=810239#c0 Summary: midnight commander makes zfs-fuse userland not responding for approx. 30 min 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: kaspernasebaer(a)gmx.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=530394) --> (http://bugzilla.novell.com/attachment.cgi?id=530394) tail of strace log when mc hangs User-Agent: Opera/9.80 (Windows NT 6.1; WOW64) Presto/2.12.388 Version/12.14 When browsing huge datasets (>1TB) by using midnight commander, in some cases zfs-fuse userland is not responding anymore for some period of time (approx. 30min) and then recovers without any error messages in the logs. "# ls /pool" or "# zfs list" dont show any result and may be aborted by ctrl+C. Samba shares on the zfs volume are not accessible. Reproducible: Sometimes Steps to Reproduce: 1. create zfs-fuse pool containing a certain amount data and directories (~>1TB) 2. use midnight commander and navigate through directories 3. Sometimes the zfs-fuse filesystem stops responding. Actual Results: Midnight commander just "hangs" for a longer period of time and then continues without any error messages. The zfs-fuse driver remains active approx. 3.5% CPU. The hard disc drives do not appear to be busy during hang. Running midnight commander by strace shows that it appears to be calling "stat" and is just waiting for the result for approx. 30 min and then continues without showing any error. Expected Results: No hang or at least report an error/timeout. My impression is that this usually happens shortly after "chdir" is issued. I have added the tail of some strace output when running midnight commander. We are experiencing this bug on two different machines, both are 64bit and multi core and have 12-48GB of memory. One machine is using local discs, the other one is using an iSCSI device. The datasets are between 2TB and 48TB. No dedup and no compression is used. Updating to the most recent software from the openSuSE repos did not solve the problem. Shutting down and starting the zfs-fuse daemon of the 2TB dataset on local drives sometimes takes some period of time (1-2h) which appears quite long. Strangely, we were _not_ able to trigger this bug by running multiple processes in parallel like kernel builds or e.g. "find /pool -type d -exec ls -la '{}' \; >> /dev/null ; " or "find /pool -type f -exec stat '{}' \; >> /dev/null " or by using bonnie++. -- 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 842998] New: Midnight Commander doesn't have an icon on the GNOME Activities overlay
by bugzilla_noreply＠novell.com 31 Jul '17

31 Jul '17

https://bugzilla.novell.com/show_bug.cgi?id=842998 https://bugzilla.novell.com/show_bug.cgi?id=842998#c0 Summary: Midnight Commander doesn't have an icon on the GNOME Activities overlay Classification: openSUSE Product: openSUSE Factory Version: 13.1 Beta 1 Platform: VMWare OS/Version: Windows 7 Status: NEW Severity: Minor Priority: P5 - None Component: Usability AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: danilo.cominotti(a)outlook.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=560690) --> (http://bugzilla.novell.com/attachment.cgi?id=560690) Screenshot of Midnight Commander entries on the GNOME Activities Overlay User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/29.0.1547.66 Safari/537.36 When I scroll down to the second page of applications from the GNOME Activities overlay, Midnight Commander doesn't have any icon -- there's just its text label. If I right-click it and choose "Add to Favorites", there also won't be an icon on the left side of the overlay. Reproducible: Always Steps to Reproduce: 1. Launch the GNOME Activities overlay. 2. Click "Show Applications" on the left side. 3. Scroll down to the second page. 4. See the entry for Midnight Commander. Actual Results: There is no icon for Midnight Commander. Also, if I right-click it and choose "Add to Favorites", there won't be an icon on the favorites bar on the left side of the overlay. Expected Results: An icon for Midnight Commander should be displayed on the GNOME Activities overlay. -- 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 904863] New: Application:Geo: Looking for Software Package Mapserver 6.4.1-1.5 for SLES 11 and openSUSE 13.2
by bugzilla_noreply＠novell.com 30 Jul '17

30 Jul '17

http://bugzilla.novell.com/show_bug.cgi?id=904863 Bug ID: 904863 Summary: Application:Geo: Looking for Software Package Mapserver 6.4.1-1.5 for SLES 11 and openSUSE 13.2 Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: SLES 11 Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: opensuse-communityscreening(a)forge.provo.novell.com Reporter: klaus.braun(a)geographie.uni-freiburg.de QA Contact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- Dear all, I am interested to use the software "Mapserver" on my SLES 11 SP3, but I could not find it in the appropriate repository Application:Geo, and even in the branch for openSUSE_13.2 I couldn't find it. For older versions of openSUSE it was available and I would like to ask if there is a chance that this software will come back to the repo for SLES 11 SP 3 and / or openSUSE 13.2. Thanks for any answer Klaus -- You are receiving this mail because: You are on the CC list for the bug.

1 4