August 2016 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 959704] New: When upgrading (zypper dup), grub looses the default option
by bugzilla_noreply＠novell.com 13 Jun '18

13 Jun '18

http://bugzilla.opensuse.org/show_bug.cgi?id=959704 Bug ID: 959704 Summary: When upgrading (zypper dup), grub looses the default option Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: jsrain(a)suse.com Reporter: elchevive68(a)gmail.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Hi, In my grub I have set as default other system than openSUSE, Win10. But sometimes after a zypper dup, the default option is overriden to Tumbleweed. To restore the correct behaviour I have to run mkinitrd manually after zypper dup. I guess that some packages that recreates the mkinitrd doesn't run it in "full mode". The last update the following packages where upgraded: aaa_base aaa_base-extras audit chromium chromium-desktop-kde chromium-ffmpeg dolphin dolphin-partenblend-enfuse freshplayerplugin ft2demos gettext-runtime insserv-compat krb5 krb5-32bit libass5 libaudit1 libaudit1-32bit libauparse0 libblkid1 libcap-ng0 libdmtx0 libdolphinvcs5 libevdev2 libfdisk1 libfreetype6 libgbm1 liblirc_client0 liblmdb-0_9_16 libmicrohttpd12 libmount1 libncurses5 libncurses5-32bit libncurses6 libopenssl1_0_0 libopenssl1_0_0-32bit libpci3 libqca2 libreoffice libreoffice-base libreoffice-base-drivers-mysql libreoffice-branding-upstream libreoffice-calc libreoffice-draw libreoffice-filters-optional libreoffice-icon-theme-breeze libreoffice-icon-theme-galaxy libreoffice-icon-theme-hicontrast libreoffice-icon-theme-oxygen libreoffice-icon-theme-sifr libreoffice-impress libreoffice-kde4 libreoffice-l10n-en libreoffice-l10n-pt-BR libreoffice-mailmerge libreoffice-math libreoffice-pyuno libreoffice-writer libsmartcols1 libsoxr0 libuuid1 libvdpau_nouveau libvdpau_r300 libvdpau_r600 libvdpau_radeonsi libvlc5 libvlccore8 libwayland-egl1 libzypp man-pages Mesa Mesa-libEGL1 Mesa-libGL1 Mesa-libglapi0 mtools ncurses-utils openssl openSUSE-release openSUSE-release-ftp pciutils perl perl-Archive-Zip perl-base perl-libwww-perl perl-Net-DNS perl-XML-LibXML perl-XML-Simple polkit-default-privs python3-py python-cryptography shim systemd-presets-branding-openSUSE sysvinit-tools terminfo terminfo-base util-linux util-linux-systemd vlc vlc-codecs vlc-noX vlc-noX-lang vlc-qt xdg-utils zypper zypper-aptitude zypper-log Regards -- You are receiving this mail because: You are on the CC list for the bug.

1 11

[Bug 957372] New: Software repository list is not sorted by name
by bugzilla_noreply＠novell.com 12 Jun '18

12 Jun '18

http://bugzilla.suse.com/show_bug.cgi?id=957372 Bug ID: 957372 Summary: Software repository list is not sorted by name Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: hguo(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- When user has a long list of software repositories, and majority of them share identical priority, the list becomes difficult to navigate since it is only sorted by priority, not by name. It would be easier for end user if the list is sorted by both priority and name. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 982942] New: improve quality of yast C++ code by fixing warnings given by Clang
by bugzilla_noreply＠novell.com 07 Jun '18

07 Jun '18

http://bugzilla.suse.com/show_bug.cgi?id=982942 Bug ID: 982942 Summary: improve quality of yast C++ code by fixing warnings given by Clang Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: CONFIRMED Severity: Normal Priority: P5 - None Component: YaST2 Assignee: mvidner(a)suse.com Reporter: mvidner(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- This is part of a long term effort to find bugs early and thus make them less expensive. I want to look at potentially buggy code as reported by - GCC warnings - Clang warnings - Clang static analysis - Coverity static analysis and fix the buggy code, even fix the non-buggy code not to produce warning noise. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 932306] New: valgrind reports memory errors during the installation
by bugzilla_noreply＠novell.com 07 Jun '18

07 Jun '18

http://bugzilla.suse.com/show_bug.cgi?id=932306 Bug ID: 932306 Summary: valgrind reports memory errors during the installation Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: mvidner(a)suse.com QA Contact: jsrain(a)suse.com Found By: Development Blocker: --- To debug bug 929806 (boo#929806) I ran the installation with y2base instrumented with valgrind. Some errors were reported. Logs will follow (once I re-run the thing, because I forgot to use startshell=1 and they got lost). -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 944012] New: yast2-printer: /usr/lib/YaST2/bin/cups_client_only hangs about 30 seconds at "lpstat -h -p"
by bugzilla_noreply＠novell.com 07 Jun '18

07 Jun '18

http://bugzilla.opensuse.org/show_bug.cgi?id=944012 Bug ID: 944012 Summary: yast2-printer: /usr/lib/YaST2/bin/cups_client_only hangs about 30 seconds at "lpstat -h -p" Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: All OS: SUSE Other Status: NEW Severity: Minor Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: jsmeix(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- when yast2-printer calls /usr/lib/YaST2/bin/cups_client_only without any parameter the script hangs for about 30 seconds at lpstat -h -p I noticed it with CUPS 2.1.0: ---------------------------------------------------------------------------- # time lpstat -h -p lpstat: No such file or directory real 0m35.051s user 0m0.004s sys 0m0.014s # time lpstat -p printer hl5150ljet4 is idle. enabled since Tue 01 Sep 2015 14:01:39 CEST real 0m0.017s user 0m0.008s sys 0m0.007s ---------------------------------------------------------------------------- The reason is in /usr/lib/YaST2/bin/cups_client_only that the line ---------------------------------------------------------------------------- if lpstat -h $SERVERNAME -p ---------------------------------------------------------------------------- is called with empty $SERVERNAME. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 992924] New: Static IP address not set up on network interface on boot when selected - yast issue as wicked can be configured
by bugzilla_noreply＠novell.com 06 Jun '18

06 Jun '18

http://bugzilla.opensuse.org/show_bug.cgi?id=992924 Bug ID: 992924 Summary: Static IP address not set up on network interface on boot when selected - yast issue as wicked can be configured Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: i686 OS: openSUSE 42.1 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: mr(a)ramendik.ru QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- This is related to older bug 911562 but now it is a YaST issue, as wicked does provide a way to configure things to work. I am using wicked. In YaST Network Servcies, for eth0, I have a static IP address and, on the General tab, "Activate Device" is set to "At Boot Time". This should mean that the device gets the IP address at boot time. (The IP address is needed because I want to configure dhcpd for this interface). However, as I do not have anything connected to it, the IP address is not assigned and, in YaST, DHCP configuration fails. After some mailing list help and some googling, I have edited the /etc/sysconfig/network/ifcfg-eth0 file and added the following line: LINK_REQUIRED=no Then I rebooted the machine. Now the eth0 interface has an IP address and the DHCP server restarts successfully. I think that if YaST provides the "at boot time" option, by default it should really be "at boot time". There already is a separate option for "at cable connection". So, YaST should use the LINK_REQUIRED=no for "at boot time". -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 947782] New: High CPU usage by plasmashell and kactivitymanager
by bugzilla_noreply＠novell.com 02 Jun '18

02 Jun '18

http://bugzilla.opensuse.org/show_bug.cgi?id=947782 Bug ID: 947782 Summary: High CPU usage by plasmashell and kactivitymanager Classification: openSUSE Product: openSUSE Factory Version: 2015* Hardware: 64bit OS: SUSE Other Status: NEW Severity: Major Priority: P5 - None Component: KDE4 Workspace Assignee: kde-maintainers(a)suse.de Reporter: fkereki(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 649259 --> http://bugzilla.opensuse.org/attachment.cgi?id=649259&action=edit Output of "top" showing high %CPU for plasmashell and kactivitymanager At times, plasmashell %CPU usage goes to 100%, and kactivitymanager also suffers a similar problem. The attached screenshot was taken at a time when no applications (other than ksnapshot, obviously!) were running. Sometimes the slowdown is so long that killing the sessions becomes mandatory. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 981272] New: Alt-Tab doesn't always work
by bugzilla_noreply＠novell.com 30 May '18

30 May '18

http://bugzilla.opensuse.org/show_bug.cgi?id=981272 Bug ID: 981272 Summary: Alt-Tab doesn't always work Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: per(a)computer.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- It's difficult to describe the problem, it really is just "Alt-Tab doesn't always work". Sometimes I have to press it twice, three times, sometimes I have to keep it pressed and wait for it to repeat. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 966999] New: IPv6 Privacy Extensions don't work with NetworkManager
by bugzilla_noreply＠novell.com 30 May '18

30 May '18

http://bugzilla.opensuse.org/show_bug.cgi?id=966999 Bug ID: 966999 Summary: IPv6 Privacy Extensions don't work with NetworkManager Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: x86-64 OS: openSUSE 42.1 Status: NEW Severity: Major Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: mcflyers(a)onlinehome.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:44.0) Gecko/20100101 Firefox/44.0 Build Identifier: IPv6 Privacy Extensions don't work with NetworkManager in Leap 42.1 Reproducible: Always I tested it on native machine, also in a virtual machine with Virtualbox -- You are receiving this mail because: You are on the CC list for the bug.

1 32

[Bug 944760] New: Nouveau driver make openSUSE13.2/Tumbleweed installation fail
by bugzilla_noreply＠novell.com 28 May '18

28 May '18

http://bugzilla.suse.com/show_bug.cgi?id=944760 Bug ID: 944760 Summary: Nouveau driver make openSUSE13.2/Tumbleweed installation fail Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: fbui(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 646446 --> http://bugzilla.suse.com/attachment.cgi?id=646446&action=edit kernel oops due to nouveau driver Hello, When installing Tumbleweed or openSUSE13.2 on my laptop, Lenovo Thinkpad W541, the installation process fails due to nouveau driver. Please find attach the oops and lscpi output. As a workaround, one can pass 'brokenmodules=nouveau' to the kernel command line. Thanks -- You are receiving this mail because: You are on the CC list for the bug.

1 10