June 2015 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 929899] New: something is wrong with ruby requires in YaST packages
by bugzilla_noreply＠novell.com 15 Mar '18

15 Mar '18

http://bugzilla.suse.com/show_bug.cgi?id=929899 Bug ID: 929899 Summary: something is wrong with ruby requires in YaST packages Classification: openSUSE Product: openSUSE Factory Version: 201503* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: aschnell(a)suse.com Reporter: aschnell(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- See discussion on yast-devel mailing list today and PBI https://trello.com/c/UdOTBSOZ/178-1-fix-rubygem-dependencies-for-ruby-2-2. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 908451] New: GRUB update removes custom themes
by bugzilla_noreply＠novell.com 11 Mar '18

11 Mar '18

http://bugzilla.opensuse.org/show_bug.cgi?id=908451 Bug ID: 908451 Summary: GRUB update removes custom themes Classification: openSUSE Product: openSUSE Factory Version: 201412* Hardware: Other OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: jsrain(a)suse.com Reporter: jon(a)grossart.net QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- I'm using Tumbleweed, and I've seen this happen across multiple installs. 1. create an optional theme in /boot/grub2/themes (not installed via the package manager) 2. set the theme via YaST2 > Boot loader 3. reboot 4. theme shows up 5. have a system update for grub (not sure if just the update grub command will clobber it or if it's a package upgrade) 6. reboot 7. theme is back to the default theme and custom theme has been removed from /boot/grub2/themes -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 926792] New: release-notes-openSUSE requires google-opensans-fonts
by bugzilla_noreply＠novell.com 07 Mar '18

07 Mar '18

http://bugzilla.opensuse.org/show_bug.cgi?id=926792 Bug ID: 926792 Summary: release-notes-openSUSE requires google-opensans-fonts Classification: openSUSE Product: openSUSE Factory Version: 201503* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Release Notes Assignee: ke(a)suse.com Reporter: mrmazda(a)earthlink.net QA Contact: coolo(a)suse.com CC: rsalevsky(a)suse.de Found By: --- Blocker: --- Mailing list discussion: http://lists.opensuse.org/opensuse-packaging/2015-04/msg00069.html Specimens of fonts at issue: https://www.google.com/fonts/specimen/Open+Sans Trying to zypper rm google-opensans-fonts wants to remove opensuse-release-notes. Unless google-opensans-fonts contains *necessary* fonts unavailable elsewhere, fonts that if unavailable would break functionality, suggests or recommends for google-opensans-fonts is OK, but not requires. Theming does not create necessity or functionality. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 918654] New: ndpmon stops silently to work
by bugzilla_noreply＠novell.com 04 Mar '18

04 Mar '18

http://bugzilla.opensuse.org/show_bug.cgi?id=918654 Bug ID: 918654 Summary: ndpmon stops silently to work 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: tschaefer(a)t-online.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Using the following paket: rpm -qi ndpmon Name : ndpmon Version : 1.4.0 Release : 8.1 Architecture: x86_64 Install Date: Do 11 Dez 2014 11:11:33 CET Group : Productivity/Networking/Diagnostic Size : 1304023 License : LGPL-2.1+ Signature : DSA/SHA1, Mi 15 Okt 2014 17:26:58 CEST, Key ID ff9db4771bce05ef Source RPM : ndpmon-1.4.0-8.1.src.rpm Build Date : Mi 15 Okt 2014 17:26:32 CEST Build Host : cloud118 Relocations : (not relocatable) Vendor : obs://build.opensuse.org/home:gregfreemyer:Tools-for-forensic-boot-cd URL : http://ndpmon.sourceforge.net/ Summary : IPv6 Neighbor Discovery Protocol Monitor Description : NDPMon, Neighbor Discovery Protocol Monitor, is a tool working with ICMPv6 packets. NDPMon observes the local network to see if nodes using neighbor discovery messages behave properly. When it detects a suspicious Neighbor Discovery message, it notifies the administrator by writing in the syslog and in some cases by sending an email report. Distribution: home:gregfreemyer:Tools-for-forensic-boot-cd / openSUSE_13.2 ndpmon starts and is running for a while: systemctl status ndpmon.service ndpmon.service - LSB: IPv6 Neighbor Discovery Protocol Monitor Loaded: loaded (/etc/init.d/ndpmon) Active: active (running) since Do 2015-02-19 15:58:57 CET; 44s ago Process: 19017 ExecStop=/etc/init.d/ndpmon stop (code=exited, status=0/SUCCESS) Process: 19028 ExecStart=/etc/init.d/ndpmon start (code=exited, status=0/SUCCESS) CGroup: /system.slice/ndpmon.service └─19035 /usr/sbin/ndpmon Feb 19 15:59:32 pflaume ndpmon[19028]: ------------------ Feb 19 15:59:32 pflaume ndpmon[19028]: ----- ND_NEIGHBOR_ADVERT ----- Feb 19 15:59:32 pflaume ndpmon[19028]: Reset timer for 0:19:99:f3:0:42 fe80:0:0:0:219:99ff:fef3:42 Feb 19 15:59:32 pflaume ndpmon[19028]: ------------------ Feb 19 15:59:33 pflaume ndpmon[19028]: ----- ND_NEIGHBOR_SOLICIT ----- Feb 19 15:59:33 pflaume ndpmon[19028]: Reset timer for b4:b5:2f:f3:b5:ac fe80:0:0:0:b6b5:2fff:fef3:b5ac Feb 19 15:59:33 pflaume ndpmon[19028]: ------------------ Feb 19 15:59:33 pflaume ndpmon[19028]: ----- ND_NEIGHBOR_ADVERT ----- Feb 19 15:59:33 pflaume ndpmon[19028]: Reset timer for 0:19:99:f3:0:42 fe80:0:0:0:219:99ff:fef3:42 Feb 19 15:59:33 pflaume ndpmon[19028]: ------------------ But after some time/days: there are no mails and the state is: systemctl status ndpmon.service ndpmon.service - LSB: IPv6 Neighbor Discovery Protocol Monitor Loaded: loaded (/etc/init.d/ndpmon) Active: active (running) since Mo 2015-02-09 16:22:46 CET; 1 weeks 2 days ago Process: 762 ExecStart=/etc/init.d/ndpmon start (code=exited, status=0/SUCCESS) CGroup: /system.slice/ndpmon.service └─809 /usr/sbin/ndpmon Feb 19 15:58:31 pflaume ndpmon[762]: Ethernet type 0 is not an IPv6 packet Feb 19 15:58:31 pflaume ndpmon[762]: ------------------ Feb 19 15:58:31 pflaume ndpmon[762]: Ethernet type 0 is not an IPv6 packet Feb 19 15:58:31 pflaume ndpmon[762]: ------------------ Feb 19 15:58:32 pflaume ndpmon[762]: Ethernet type 0 is not an IPv6 packet Feb 19 15:58:32 pflaume ndpmon[762]: ------------------ Feb 19 15:58:32 pflaume ndpmon[762]: Ethernet type 0 is not an IPv6 packet Feb 19 15:58:32 pflaume ndpmon[762]: ------------------ Feb 19 15:58:44 pflaume ndpmon[762]: Ethernet type 0 is not an IPv6 packet Feb 19 15:58:44 pflaume ndpmon[762]: ------------------ I don't know, what is going wrong here. I have seen that there is a complete new version at http://ndpmon.sourceforge.net/ Or can somebody recommend alternatives? -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 907387] New: nut systemd service file (nut-driver.service) has wrong ExecStart/Stop entry.
by bugzilla_noreply＠novell.com 03 Mar '18

03 Mar '18

http://bugzilla.opensuse.org/show_bug.cgi?id=907387 Bug ID: 907387 Summary: nut systemd service file (nut-driver.service) has wrong ExecStart/Stop entry. Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: All OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: ivar_nikolaisen(a)hotmail.com 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: The nut-driver service file (/usr/lib/systemd/system/nut-driver.service) does not work because the service file is incorrect. It currently has the following settings under [Service]: ExecStart=/upsdrvctl start ExecStop=/upsdrvctl stop These are obviously not correct full paths to the upsdrvctl executable. On my machine, I have found the executable located at /usr/lib/ups/driver/upsdrvctl, and nut seems to work correctly if I change to this path (that is, after doing systemctl start nut-server.service, my UPS is identified correctly and I can query it using the upsc utility). Reproducible: Always -- You are receiving this mail because: You are on the CC list for the bug.

1 18

[Bug 904731] New: parcellite is started in KDE together with klipper
by bugzilla_noreply＠novell.com 28 Feb '18

28 Feb '18

http://bugzilla.opensuse.org/show_bug.cgi?id=904731 Bug ID: 904731 Summary: parcellite is started in KDE together with klipper Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: comes(a)naic.edu QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- If I login using the KDE desktop and parcellite is installed, then both clipboard manager klipper and parcellite are started and visible in the tray. To fix the problem just add in /etc/xdg/autostart/parcellite-startup.desktop: NotShowIn=KDE; Bug present in 13.1 and 13.2. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 862739] New: openvpn creates non-functional client config
by bugzilla_noreply＠novell.com 26 Feb '18

26 Feb '18

https://bugzilla.novell.com/show_bug.cgi?id=862739 https://bugzilla.novell.com/show_bug.cgi?id=862739#c0 Summary: openvpn creates non-functional client config Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: per(a)computer.org QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:11.0) Gecko/20100101 Firefox/11.0 I have recently upgraded our local openvpn endpoint to 13.1, which also meant upgrading openvpn to 2.3.2 . I copied over our existing configuration and added "topology subnet". The new configuration no longer works, it seems to be handing out an invalid client config. Previous config that worked: 2013-07-30T17:02:44.084956+02:00 toshi1 openvpn[5616]: PUSH: Received control message: 'PUSH_REPLY,route 192.168.0.0 255.255.0.0,route 192.168.13.1,ping 10,ping-restart 120,ifconfig 192.168.13.9 192.168.13.10' Current config which doesn't work: 2014-02-07T09:56:14.797888+01:00 toshi1 openvpn[8133]: PUSH: Received control message: 'PUSH_REPLY,route 192.168.0.0 255.255.240.0,topology p2p,ping 10,ping-restart 120,ifconfig 255.255.255.0 192.168.13.10' The "ifconfig 255.255.255.0 192.168.13.10" part looks particularly dodgy and presumably leads to this faulty network config: 4: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 100 link/none inet 255.255.255.0 peer 192.168.13.10/32 scope global tun0 valid_lft forever preferred_lft forever It is correctable by amending the addresses: ip addr add 192.168.13.9 peer 192.168.13.10 dev tun0 ip addr del 255.255.255.0/32 dev tun0 Reproducible: Always -- 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 4

[Bug 931987] New: VUL-0: CVE-2013-7441: nbd: NBD server terminates on SIGPIPE during negotiation
by bugzilla_noreply＠novell.com 26 Feb '18

26 Feb '18

http://bugzilla.suse.com/show_bug.cgi?id=931987 Bug ID: 931987 Summary: VUL-0: CVE-2013-7441: nbd: NBD server terminates on SIGPIPE during negotiation Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: ms(a)suse.com Reporter: abergmann(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: Security Response Team Blocker: --- rh#1224074 / CVE-2013-7441 -------------------------------------------- A denial of service flaw was found in nbd: "The listener/root server process terminates on SIGPIPE during negotiation. This is hardly the desired behavior, since any malfunctioning client can brought the listener server down by closing the socket unexpectedly." Additional information: http://sourceforge.net/p/nbd/mailman/message/30410146/ Upstream patch: https://github.com/yoe/nbd/commit/741495cb08503fd32a9d22648e63b64390c601f4 -------------------------------------------- References: https://bugzilla.redhat.com/show_bug.cgi?id=1224074 http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2013-7441 http://seclists.org/oss-sec/2015/q2/516 http://people.canonical.com/~ubuntu-security/cve/2013/CVE-2013-7441.html -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 909625] New: security update fails to install with update applet
by bugzilla_noreply＠novell.com 26 Feb '18

26 Feb '18

http://bugzilla.opensuse.org/show_bug.cgi?id=909625 Bug ID: 909625 Summary: security update fails to install with update applet Classification: openSUSE Product: openSUSE 13.1 Version: Final Hardware: x86-64 OS: All Status: NEW Severity: Normal Priority: P5 - None Component: Maintenance Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: c.forrest(a)exeter.ac.uk QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:34.0) Gecko/20100101 Firefox/34.0 Build Identifier: patch:openSUSE-2014-746-1.noarch conflicts with MozillaFirefox-branding-upstream.x86_64 < 34.0.5-50.3 provided by MozillaFirefox-branding-upstream-34.0.5-1.2.x86_64 Reproducible: Always Steps to Reproduce: 1. select to install security update in updater applet 2. 3. Actual Results: update fails to install Expected Results: update should have installed can be resolved by using Yast online update which offers conflict resolution of changing to opensuse branding. This affects both 32 bit and x64 versions of 13.1. Will likely affect all Suse versions as it is a conflict with the Mozilla upstream branding. Reverting to opensuse branding allows the openSUSE-2014-746-1.noarch update to install fine -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 925088] New: YAST warning of low disk space in unrelated mounted partition with more than 800 GB free
by bugzilla_noreply＠novell.com 23 Feb '18

23 Feb '18

http://bugzilla.opensuse.org/show_bug.cgi?id=925088 Bug ID: 925088 Summary: YAST warning of low disk space in unrelated mounted partition with more than 800 GB free Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Minor Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: brunomcl(a)yahoo.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- This started happening after a disk reorg+addition I did a month ago. Yast software manager download and install the packages OK, but give this warning before installing each package if I don't tick "don't show this warning again": "The disk space in partition /home/shares/Gravados/Series\040Concluidas/ is almost full. Continue installation?" The relevant lines of fstab are shown below, with UUIDs substituted for sdXX for better understanding. the \040 code translate to a blank space in the mount directory. Yast partitioner would choke on them (or the accents), but the names could be directly edited in fstab and work fine after rebooting: Code: ... sdd1 /home/shares ext4 noatime,data=writeback,acl,nodiratime 1 2 ... sde1 /home/shares/Gravados/Series ext4 noatime,data=writeback,acl,user_xattr,nodiratime 1 2 sdc1 /home/shares/Gravados/Series\040em\040Inglês ext4 noatime,data=writeback,acl,user_xattr,nodiratime 1 2 sdf1 /home/shares/Gravados/Series\040Concluidas/ ext4 noatime,data=writeback,acl,user_xattr,nodiratime 1 2 Lots of free space: Code: > df -h Sist. Arq. Tam. Usado Disp. Uso% Montado em /dev/sda6 20G 11G 8,0G 58% / devtmpfs 7,9G 4,0K 7,9G 1% /dev tmpfs 7,9G 96K 7,9G 1% /dev/shm tmpfs 7,9G 2,3M 7,9G 1% /run tmpfs 7,9G 0 7,9G 0% /sys/fs/cgroup /dev/sdb1 100G 30G 71G 30% /windowsD /dev/sdb6 990M 162M 761M 18% /var/log /dev/sdb5 976M 346M 563M 39% /tmp /dev/sda2 90G 23G 68G 25% /windowsC /dev/sda7 118G 69G 44G 62% /home /dev/sdb3 718G 544G 139G 80% /home/arquivos /dev/sdb2 99G 54G 40G 58% /home/trabalho /dev/sdd1 1,8T 790G 951G 46% /home/shares /dev/sdc1 917G 666G 251G 73% /home/shares/Gravados/Series em Inglês /dev/sdf1 1,8T 1022G 812G 56% /home/shares/Gravados/Series Concluidas /dev/sde1 1,8T 888G 946G 49% /home/shares/Gravados/Series No warning message during install with Yast Online Update or KDE's packagekit front-end program updater. >From this comment in the forum it seems related to the space in the mount name: https://forums.opensuse.org/showthread.php/506145-YAST-warning-of-low-disk-… I haven't noticed any adverse effect except for the warning message. y2log part relevant to the last warning received: :~> cat y2log | grep Concluidas 2015-03-30 19:02:06 <2> bruno-03(29012) [zypp] DiskUsageCounter.cc(detectMountPoints):282 Unable to statvfs(/home/shares/Gravados/Series\040Concluidas); errno 2 2015-03-30 19:14:59 <2> bruno-03(11245) [zypp] DiskUsageCounter.cc(detectMountPoints):282 Unable to statvfs(/home/shares/Gravados/Series\040Concluidas); errno 2 2015-03-30 19:16:30 <1> bruno-03(11245) [Ruby] modules/PackageInstallation.rb:223 CommitPackages (0,0): Pkg::TargetGetDU() $["/":[20511356, 11276812, 11291073, 0], "/home":[123723748, 62334000, 62334000, 0], "/home/arquivos":[752813152, 583747320, 583747320, 0], "/home/shares":[1922728752, 842811676, 842811676, 0], "/home/shares/Gravados/Series":[1922728752, 941632712, 941632712, 0], "/home/shares/Gravados/Series\\040Concluidas":[0, 0, 0, 0], "/home/shares/Gravados/Series\\040em\\040Ingl\u00EAs":[0, 0, 0, 0], "/home/trabalho":[103081248, 56036856, 56036856, 0], "/tmp":[999320, 5932, 5932, 0], "/var/log":[1013688, 173700, 173700, 0], "/windowsD":[104857596, 30891128, 30891128, 0]] 2015-03-30 19:16:30 <2> bruno-03(11245) [Ruby] modules/SlideShowCallbacks.rb:322 Not enought free space in /home/shares/Gravados/Series\040Concluidas (//home/shares/Gravados/Series\040Concluidas): available: -1, required: 0 Full y2log file (9.5 MB) available if necessary. -- You are receiving this mail because: You are on the CC list for the bug.

1 7