November 2017 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1062190] New: Saving of annotations and bookmarks doesn't work in Okular
by bugzilla_noreply＠novell.com 18 Sep '19

18 Sep '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1062190 Bug ID: 1062190 Summary: Saving of annotations and bookmarks doesn't work in Okular Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: ada.lovelace(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I want to save bookmarks in Okular. It should work with our Okular version and our poppler version in openSUSE Leap 42.3. The missing configuration is listed here in answer1: https://unix.stackexchange.com/questions/123226/change-and-save-pdf-annotat… Problem 1: Bookmarks and annotations won't be saved in the pdf file with "Save as..." Problem2: The workaround with "Printing pdf" doesn't work, too. Annotations should be added, but if you choose the new pdf, no annotations are added. That's only a link to the old pdf file. Ubuntu is using the same Okular version and it should work there (information in forums). So it has to be a problem with openSUSE. How it should work: I want to save all annotations and bookmarks in the pdf file. So I can send it to other people and they can use them. Both methods "Save as..." and "pdf printing" should work with annotations. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1051307] New: Canon LiDE30 Scanner not working (usb2.0 and 3.0 ports)
by bugzilla_noreply＠novell.com 18 Sep '19

18 Sep '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1051307 Bug ID: 1051307 Summary: Canon LiDE30 Scanner not working (usb2.0 and 3.0 ports) Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: x86-64 OS: openSUSE 42.3 Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: madworm_de.novell(a)spitzenpfeil.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:50.0) Gecko/20100101 Firefox/50.0 Build Identifier: Same hardware as in: ( https://bugzilla.opensuse.org/show_bug.cgi?id=1049019 ) Scanner: Bus 001 Device 008: ID 04a9:220e Canon, Inc. CanoScan N1240U/LiDE 30 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Symptoms: scanimage -L detects scanner, but does absolutely nothing otherwise. xsane doesn't see a scanning device. Yast configuration is "weird" (detects scanner, but doesn't appear to store anything. same thing next run). This feels awfully similar to a sane issue I've had with 13.2 on an Acer Laptop with USB3 ports ( https://bugzilla.opensuse.org/show_bug.cgi?id=920067 ) The scanner works OUT_OF_THE_BOX with: PartedMagic 2016_12_12 (devel) Kernel: 4.8.14-pmagic64 xsane: 0.999 sane-backend: 1.0.25 Approximate list of packages: https://partedmagic.com/parted-magic-2017-01-08/ The scanner issues keep haunting me :-( Reproducible: Always -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1021293] New: Canon LiDE20 USB scanner issues with Acer laptop [intel] + USB3.0 controller (xhci)
by bugzilla_noreply＠novell.com 18 Sep '19

18 Sep '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1021293 Bug ID: 1021293 Summary: Canon LiDE20 USB scanner issues with Acer laptop [intel] + USB3.0 controller (xhci) Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: madworm_de.novell(a)spitzenpfeil.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I'm having the very same issues with Leap 42.2 as previously with 13.2 https://bugzilla.opensuse.org/show_bug.cgi?id=920067 I thought the fixes previously added to the scanner software would've been integrated into Leap. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1009129] New: plasma update notifier does not update after updates have been applied manually
by bugzilla_noreply＠novell.com 12 Sep '19

12 Sep '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1009129 Bug ID: 1009129 Summary: plasma update notifier does not update after updates have been applied manually Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: okurz(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 701148 --> http://bugzilla.opensuse.org/attachment.cgi?id=701148&action=edit screenshot showing that zypper dup has been called in terminal but the update notifier still shows updates. ## observation when the plasma update notification icon told there are updates available I called "zypper ref && zypper dup --no-allow-vendor-change" to manually and installed updates. after that the update notification icon stilled showed available updates even though there weren't any. The update notifier only updated after a long time (still showed after many minutes. Next time I checked after at least 24h it was not showing any updates anymore. ## expected result there shouldn't be any updates shown if zypper up / dup has been called. ## further details see attached screenshot. -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 1060497] New: libelf1 is not updated, requires libebl-plugins
by bugzilla_noreply＠novell.com 12 Sep '19

12 Sep '19

http://bugzilla.suse.com/show_bug.cgi?id=1060497 Bug ID: 1060497 Summary: libelf1 is not updated, requires libebl-plugins Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Upgrade Problems Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: Ralf.Friedl(a)online.de QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- I have Tumbleweed with libelf1-0.168-5.4.x86_64 and libebl1-0.168-5.4.x86_64 installed. The command "zypper up" says "The following package update will NOT be installed: libelf1". Trying to update with "zypper up libelf1" leads to a conflict: Problem: libelf1-0.168-6.1.x86_64 requires libebl-plugins = 0.168, but this requirement cannot be provided uninstallable providers: libebl-plugins-0.168-6.1.i586[repo-oss] libebl-plugins-0.168-6.1.x86_64[repo-oss] Solution 1: replacement of libebl1-0.168-5.4.x86_64 with libebl-plugins-0.168-6.1.x86_64 Solution 2: do not install libelf1-0.168-6.1.x86_64 Solution 3: break libelf1-0.168-6.1.x86_64 by ignoring some of its dependencies Solution 1 seems to be the right choice, especially as trying to install libebl-plugins automatically removes libebl1. So the question is, why doesn't the resolver realize this? The package libebl-plugins contains the information that it obsoletes libebl and libebl1, and this information is used when explicitly installing libebl-plugins. So why not when libebl-plugins is implicitly needed for libelf1? -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1013573] New: "dracut: Could not find FONT_MAP none!" warning while rebuilding initrd
by bugzilla_noreply＠novell.com 10 Sep '19

10 Sep '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1013573 Bug ID: 1013573 Summary: "dracut: Could not find FONT_MAP none!" warning while rebuilding initrd Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: develop7(a)develop7.info QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Repro: 1. Install openSUSE Tumbleweed (snapshot 20161123 in my case) 2. run /sbin/mkinitrd as root (or wait for update that triggers rebuilding initrd) 3. Watch dracut output Expected: no FONT_MAP-related warnings and related issues Instead: see summary The issue is created because current TW snapshot is affected as well Additional info: > $ cat /etc/vconsole.conf > KEYMAP=us -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1064546] New: Firefox: Ctrl+Backspace behaviour
by bugzilla_noreply＠novell.com 09 Sep '19

09 Sep '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1064546 Bug ID: 1064546 Summary: Firefox: Ctrl+Backspace behaviour Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Firefox Assignee: bnc-team-mozilla(a)forge.provo.novell.com Reporter: jakob.jakobson13(a)posteo.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Dear developers, I stumbled upon an odd behaviour of firefox. If you are for example on the following page: https://www.swr.de/swraktuell/bw/suedbaden/-/id=1552/kbz7p6/index.html and now click into the adress bar and set the cursor behind the last letter of the internet adress, pressing Ctrl+Backspace deletes the complete adress whereas in other linux distributions and Windows one press of Ctrl+Backspace shortens the internet adress just to https://www.swr.de/swraktuell/bw/suedbaden/-/id=1552/kbz7p6/index. I find the Windows behaviour much more convinient and I wondered why firefox behaves differently in OpenSUSE. Is there any reason for that? Regards, Jakob -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1065270] New: python3-libxml2-python: segfault with malformed UTF8 strings in error messages
by bugzilla_noreply＠novell.com 09 Sep '19

09 Sep '19

http://bugzilla.suse.com/show_bug.cgi?id=1065270 Bug ID: 1065270 Summary: python3-libxml2-python: segfault with malformed UTF8 strings in error messages Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: pmonrealgonzalez(a)suse.com Reporter: jmatejek(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- libxml2 error reporting seems to return strings of a fixed byte length, leading up to the detected error. for instance, if the error comes from the following string: --- <p>нно удерживая клавишу key href="help:gnome-help/keyboard-key-super">Super</key>.</p> --- the error message reads: --- Opening and ending tag mismatch: p line 2 and key �вая клавишу key href="help:gnome-help/keyboard-key-super">Super</key> --- this message has a byte length 81, and the "и" character from "удерживая" is split in half. This works fine in Python 2, where strings are sequences of bytes. But it poses a problem for the Python 3 binding, because it tries to directly convert the error string to a PyUnicode character string, which fails the decoding. Libxml doesn't check this error and passes a NULL object to the calling Python code. Which causes a crash. -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 1046966] New: Akregator looses feed list
by bugzilla_noreply＠novell.com 08 Sep '19

08 Sep '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1046966 Bug ID: 1046966 Summary: Akregator looses feed list Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE 42.2 Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: suse-beta(a)cboltz.de QA Contact: qa-bugs(a)suse.de Found By: Beta-Customer Blocker: --- Since I installed the 20170613 tumbleweed snapshot, Akregator looses/breaks its feed list. The only good thing is that the error message mentions the exact filename (~/.local/share/akregator/data/feeds.opml) so that it's easy to restore from backup I had to restore the file twice already. I'm not 100% sure, but I wouldn't be surprised if the file gets damaged on logout/shutdown. Explicitely exiting Akregator (by pressing Ctrl-Q) seems to avoid the breakage. After restoring feeds.opml, Akregator can be started normally and shows all my feeds. This bug was confirmed by multiple users on opensuse-factory, both with Tumbleweed and with 42.2 + KDE:Frameworks5. -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 939462] New: ibus-table input methods not working
by bugzilla_noreply＠novell.com 08 Sep '19

08 Sep '19

http://bugzilla.opensuse.org/show_bug.cgi?id=939462 Bug ID: 939462 Summary: ibus-table input methods not working Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: cycharlie(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This problem exists since openSUSE 13.2, and it continues to exist in Tumbleweed and Leap. THw whole bunch of ibus-table-* input methods can be installed and added in iBus. However, when those input methods are selected, iBus failed to utilize them, iBus stays at the input method that is currently using, instead of changing into the one that I just selected. Similar problem had occured in openSUSE 13.1, which ibus-table input methods even couldn't be added to iBus (packages installed but iBus did not list them out). There was a solution for this situation, but this time that solution does not work for what happens in openSUSE 13.2/Tumbleweed/Leap. -- You are receiving this mail because: You are on the CC list for the bug.

1 3