February 2017 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 994322] New: bye-bye, grub_installdevice
by bugzilla_noreply＠novell.com 22 Dec '18

22 Dec '18

http://bugzilla.suse.com/show_bug.cgi?id=994322 Bug ID: 994322 Summary: bye-bye, grub_installdevice Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: yast-internal(a)suse.de Reporter: snwint(a)suse.com QA Contact: jsrain(a)suse.com Found By: Development Blocker: --- [follow-up from bug 979002] plan: Get rid of /etc/default/grub_installdevice for i386-pc target. use-case: To avoid complications when device names are not stable (see bug above). For example when drivers change or VMs are moved around. Also, yast will only propose configurations where grub resides in the disk with the /boot partition - so the assumption below should ideally always be true. how: /usr/lib/bootloader/grub2/install replaces missing entries with defaults: - device = disk where /boot/grub2/i386-pc/ lives - there are other entries like 'activate' or 'generic_mbr'; they can be dropped as they are not used anyway by /usr/lib/bootloader/grub2/install So, basically yast should only create grub_installdevice when grub is installed to a non-default device. -- You are receiving this mail because: You are on the CC list for the bug.

1 29

[Bug 1017767] New: KIO slave: invalid address (URL)
by bugzilla_noreply＠novell.com 21 Dec '18

21 Dec '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1017767 Bug ID: 1017767 Summary: KIO slave: invalid address (URL) Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: axel.braun(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When plugging in a USB-stick, the 'device manager' offers to open the device with file manager. If you click the option, you get the a.m. error messages. In fact the device seems to get mounted automatically, *although* the option 'Automatic mount of devices (Wechselmedien)' is *not* set. In Dolphin the device is shown and can be used. This seems to be a new issue in 42.2, as it was not in 42.1 -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1015858] New: Region settings offers en_CH which is not provided by system
by bugzilla_noreply＠novell.com 19 Dec '18

19 Dec '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1015858 Bug ID: 1015858 Summary: Region settings offers en_CH which is not provided by system Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: m.a.zulliger(a)bluewin.ch QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Settings->Configure Desktop->Regional Settings->Formats->Region offers "Switzerland - English (en_CH)". However, this locale is not provided by the system as $ locale -a | grep en_CH comes up empty. When en_CH is selected, this leads to problems such as files with special characters no longer being readable by KDE applications and copy errors / files not found on ext4 disks migrated from another system. $ locale will show errors: locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_MESSAGES to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory locale-gen, which is available in other distros does not seem available, so en_CH cannot be generated. Please provide en_CH and/or the tools to create it as part of tumbleweed. Also suggested: - Have KDE settings trigger installation or generation of locale not already available - Or in the worst case have KDE settings not offer locale that are not available -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 960239] New: KDE software update widget not translated
by bugzilla_noreply＠novell.com 19 Dec '18

19 Dec '18

http://bugzilla.opensuse.org/show_bug.cgi?id=960239 Bug ID: 960239 Summary: KDE software update widget not translated Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: arnold.mesper(a)yandex.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The software update widget in KDE is not translated into German - the other widgets in the right bottom corner near the clock are showing the German text. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 960153] New: Network manager and DNS forwarders don't work together
by bugzilla_noreply＠novell.com 16 Dec '18

16 Dec '18

http://bugzilla.suse.com/show_bug.cgi?id=960153 Bug ID: 960153 Summary: Network manager and DNS forwarders don't work together Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: jack(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 660275 --> http://bugzilla.suse.com/attachment.cgi?id=660275&action=edit My /etc/sysconfig/network/config file I'm using Networkmanager to manage my network connection including updating /etc/resolv.conf (since this is a laptop which I connect at different places). As I need to use openvpn to connect to SUSE internal network, I'm using dnsmasq to forward resolving of SUSE domain names to SUSE name servers and the rest is resolved through the local name server. This used to work fine with 13.2. Now I have updated to 42.1 and my resolv.conf contains: # Generated by NetworkManager search suse.cz suse.de nameserver 192.168.2.1 When 'netconfig update' is run, it complains that resolv.conf has been updated manually and so it won't touch it. I have to run 'netconfig update -f' to force updating /etc/resolv.conf and then my DNS setup starts working again. So apparently some cooperation between NetworkManager and netconfig has been broken with 42.1... -- You are receiving this mail because: You are on the CC list for the bug.

1 45

[Bug 932331] New: YaST rspec tests do not give any hint to file that cannot be loaded
by bugzilla_noreply＠novell.com 16 Dec '18

16 Dec '18

http://bugzilla.suse.com/show_bug.cgi?id=932331 Bug ID: 932331 Summary: YaST rspec tests do not give any hint to file that cannot be loaded Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: aschnell(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Tests for two files in https://github.com/aschnell/yast-snapper fail if the regex in SnapperDbus.rb is constructed wrong, e.g. remove the n option from "ret.gsub!(/(\\|[\x80-\xff])/n)". All tests using SnapperDbus.rb fail but rspec does not give a hint that something is wrong with the file SnapperDbus.rb, thus making analysing the problem harder than necessary. -- You are receiving this mail because: You are on the CC list for the bug.

1 24

[Bug 1023728] New: openSUSE:Factory/rabbitmq-server fails to build
by bugzilla_noreply＠novell.com 15 Dec '18

15 Dec '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1023728 Bug ID: 1023728 Summary: openSUSE:Factory/rabbitmq-server fails to build Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The package rabbitmq-server fails to build in openSUSE:Factory. Earlier notifications by email to the bugowner and Maintainer have remained without reaction / fix. If the package is not being fixed within 2 weeks, it will be scheduled for removal from Tumbleweed -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1024301] New: icewm-session doesn't load fcitx applet to the icewmtray
by bugzilla_noreply＠novell.com 14 Dec '18

14 Dec '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1024301 Bug ID: 1024301 Summary: icewm-session doesn't load fcitx applet to the icewmtray Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: x86-64 OS: openSUSE 42.2 Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: btwothree0tom(a)tom.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:51.0) Gecko/20100101 Firefox/51.0 Build Identifier: System was installed without X, minimal X was installed by hand, icewm-session is started with xinitrc, fcitx daemon intended to start the tray icon (applet) is prefixed in the xinitrc file with sleep interval. Reproducible: Always Steps to Reproduce: 1. startx after login 2. 3. Actual Results: all applets load but fcitx Expected Results: fcitx apllet would load in a given time interval, specified in xinitrc file nm-applet, notification-daemon applet both load to the icewmtray as they should (for purpose of testing the icewmtray viability altogether). fcitx applet would load to stalonetray added to xinitrc (for purpose of testing if the applet is missing altogether). could it possibly be some sort of blacklisting on the opensuse side of things? some patch maybe? starting fcitx daemon by hand from the terminal doesn't seem to cause any errors. first submitted to the forum, link https://forums.opensuse.org/showthread.php/522234-icewm-session-doesn-t-loa… As a follow up to my last forum message i did try tumbleweed with the same setup, and it resulted with the similar outcome, so that theory (of differnet package sources) turned out to be worthless Thanks for your time and efforts! Cheers -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1020259] New: dirmngr is broken on IPv4-less systems
by bugzilla_noreply＠novell.com 12 Dec '18

12 Dec '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1020259 Bug ID: 1020259 Summary: dirmngr is broken on IPv4-less systems Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: jengelh(a)inai.de QA Contact: qa-bugs(a)suse.de CC: tchvatal(a)suse.com Found By: --- Blocker: --- gpg2-2.1.17 on Tumbleweed: $ cat /etc/resolv.conf nameserver 2a01:4f8:0:a0a1::add:1010 nameserver 2a01:4f8:0:a102::add:9999 nameserver 2a01:4f8:0:a111::add:9898 $ host hkps.pool.sks-keyservers.net hkps.pool.sks-keyservers.net has address 92.43.111.21 hkps.pool.sks-keyservers.net has address 51.15.53.138 hkps.pool.sks-keyservers.net has address 163.172.29.20 hkps.pool.sks-keyservers.net has address 216.66.15.2 hkps.pool.sks-keyservers.net has address 209.135.211.141 hkps.pool.sks-keyservers.net has address 37.191.238.78 hkps.pool.sks-keyservers.net has address 193.224.163.43 hkps.pool.sks-keyservers.net has address 212.12.48.27 hkps.pool.sks-keyservers.net has address 130.206.1.8 hkps.pool.sks-keyservers.net has address 18.9.60.141 hkps.pool.sks-keyservers.net has IPv6 address 2001:bc8:2515::1 hkps.pool.sks-keyservers.net has IPv6 address 2001:470:1:116::6 hkps.pool.sks-keyservers.net has IPv6 address 2001:738:0:600:216:3eff:fe02:42 hkps.pool.sks-keyservers.net has IPv6 address 2001:720:418:caf1::8 hkps.pool.sks-keyservers.net has IPv6 address 2001:bc8:4700:2300::10:f15 hkps.pool.sks-keyservers.net has IPv6 address 2a00:14b0:4200:3000:27::27 hkps.pool.sks-keyservers.net has IPv6 address 2606:9500:201:1::141 hkps.pool.sks-keyservers.net has IPv6 address 2a01:4a0:59:1000:223:9eff:fe00:100f $ dirmngr < dirmngr[11549]: error opening '/home/jng/.gnupg/dirmngr_ldapservers.conf': No such file or directory < dirmngr[11549.0]: permanently loaded certificates: 0 < dirmngr[11549.0]: runtime cached certificates: 0 < # Home: /home/jng/.gnupg < # Config: [none] < OK Dirmngr 2.1.17 at your service KEYSERVER hkps://hkps.pool.sks-keyservers.net < OK KS_SEARCH Whatever < dirmngr[11549.0]: command 'KS_SEARCH' failed: Server indicated a failure <Unspecified source> < ERR 219 Server indicated a failure <Unspecified source> This causes downstream components to appear broken too (e.g. `gpg --recv-keys`). Adding "nameserver 8.8.8.8" to resolv.conf works around the issue, and ONLY if it comes before any IPv6 name server. This is a regression from Leap 42.2, where gpg --recv-keys works despite only having IPv6 nameservers listed. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 900073] New: AUDIT-0: review the OBS CGIs
by bugzilla_noreply＠novell.com 04 Dec '18

04 Dec '18

http://bugzilla.suse.com/show_bug.cgi?id=900073 Bug ID: 900073 Summary: AUDIT-0: review the OBS CGIs Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Infrastructure Assignee: mrueckert(a)suse.com Reporter: krahmer(a)suse.com QA Contact: lrupp(a)suse.com Found By: --- Blocker: --- https://github.com/openSUSE/open-build-service -- You are receiving this mail because: You are on the CC list for the bug.

1 3