August 2017 - openSUSE Bugs - openSUSE Mailing Lists

[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 564304] growisofs can not burn sata dvd
by bugzilla_noreply＠novell.com 01 Aug '17

01 Aug '17

http://bugzilla.opensuse.org/show_bug.cgi?id=564304 http://bugzilla.opensuse.org/show_bug.cgi?id=564304#c19 Carlos Robinson <carlos.e.r(a)opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #19 from Carlos Robinson <carlos.e.r(a)opensuse.org> --- Using Leap 42.2 now. Wodim has disappeared from the system and or the distribution, using cdrtools-3.01-2.15.x86_64 instead, and I don't recall having issues since years. Closing report. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 439717] Spanish keyboard, key '~' is no longer dead key
by bugzilla_noreply＠novell.com 01 Aug '17

01 Aug '17

http://bugzilla.opensuse.org/show_bug.cgi?id=439717 http://bugzilla.opensuse.org/show_bug.cgi?id=439717#c6 Carlos Robinson <carlos.e.r(a)opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #6 from Carlos Robinson <carlos.e.r(a)opensuse.org> --- Leap 42.2 one keypress. This behaviour has stuck for several years, so behaviour seems to have stabilized. Closing. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 538789] Thunderbird does not sync correctly to remote imap server.
by bugzilla_noreply＠novell.com 01 Aug '17

01 Aug '17

http://bugzilla.opensuse.org/show_bug.cgi?id=538789 http://bugzilla.opensuse.org/show_bug.cgi?id=538789#c7 Carlos Robinson <carlos.e.r(a)opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #7 from Carlos Robinson <carlos.e.r(a)opensuse.org> --- Apparently this is not happening now. Closing. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[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 854353] YaST incorrectly removes UEFI boot variables on installation and kernel update.
by bugzilla_noreply＠novell.com 01 Aug '17

01 Aug '17

http://bugzilla.opensuse.org/show_bug.cgi?id=854353 http://bugzilla.opensuse.org/show_bug.cgi?id=854353#c9 Neil Rickert <nwr10cst-oslnx(a)yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |NORESPONSE Flags|needinfo?(dexter.1234@hotma | |il.com) | --- Comment #9 from Neil Rickert <nwr10cst-oslnx(a)yahoo.com> --- No response for 2 years. I'm clearing the "needinfo". What's left is mainly a difference of opinion. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 331259] pow() returns wrong result on x86_64
by bugzilla_noreply＠novell.com 01 Aug '17

01 Aug '17

http://bugzilla.opensuse.org/show_bug.cgi?id=331259 http://bugzilla.opensuse.org/show_bug.cgi?id=331259#c2 Christos Gourdoupis <xrigou(a)otenet.gr> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |xrigou(a)otenet.gr Resolution|--- |WORKSFORME --- Comment #2 from Christos Gourdoupis <xrigou(a)otenet.gr> --- I compiled the program on current Tumbleweed x86_64 and it works fine. Possible CPU erratum? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 986538] kmail/akonadi keeps asking to accept expired certificate
by bugzilla_noreply＠novell.com 01 Aug '17

01 Aug '17

http://bugzilla.novell.com/show_bug.cgi?id=986538 http://bugzilla.novell.com/show_bug.cgi?id=986538#c1 Robby Engelmann <robby.engelmann(a)igfs-ev.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |robby.engelmann(a)igfs-ev.de Resolution|--- |WORKSFORME --- Comment #1 from Robby Engelmann <robby.engelmann(a)igfs-ev.de> --- to cancel is no response to the question, there should be a deny-option. As far as I remember, this worked for me last time I had such an issue. If I am wrong, please reopen the bug -- You are receiving this mail because: You are on the CC list for the bug.

1 0