January 2017 - 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 1011175] New: Using FF and the plugin downthemall: clicking on metalink downloads the wrong iso
by bugzilla_noreply＠novell.com 12 Jun '18

12 Jun '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1011175 Bug ID: 1011175 Summary: Using FF and the plugin downthemall: clicking on metalink downloads the wrong iso Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Download Infrastructure Assignee: lars.vogdt(a)suse.com Reporter: stakanov(a)freenet.de QA Contact: lars.vogdt(a)suse.com Found By: --- Blocker: --- Created attachment 702838 --> http://bugzilla.opensuse.org/attachment.cgi?id=702838&action=edit Wrong iso downloads Downthemall is a widespread plugin in FF to download files. I do not know if the problem exists also in windows (somebody could check) but clicking on the metalink link of the download page downloads the wrong file (torrent) and then the checksum is of course wrong. If a person coming from the windows word experiences this problem too, it could be a valid barrier when trying to make first steps in our universe. Steps to reproduce: use FF e downthemall plugin. Click on metalink, the plugin will download the torrent version of the iso instead of selecting correctly the meta4. (Checked only for Linux, do not know about windows, do not possess a copy) In attachment I put a screen-shot. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1008840] New: Bluetooth Tumbleweed: Adapter softlocked after every suspend or reboot. Pairing compromised?
by bugzilla_noreply＠novell.com 12 Jun '18

12 Jun '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1008840 Bug ID: 1008840 Summary: Bluetooth Tumbleweed: Adapter softlocked after every suspend or reboot. Pairing compromised? Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: 32bit OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: stakanov(a)freenet.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This is possibly connected/related to Bug 1006601. Take a Wind U100 Netbook. This has a BT centrino combi wireless card, it runs exclusively 32 bit software (Atom). After boot the BT in TW is deactivated. It appears powered but is "softlocked". There is no possibility to unlock it in KDE. After a lot of trials I found out that it is possible to overcome this. You have to: log in graphically to KDE as root. You do not have to perform any action, from the very login you see BT activated. So, you log out. You log in as your user. NOW BT is activated, can pair correctly. Does work as expected. Now do the suspend or the shutdown, and restart. BT will be blocked in all normal users. Softblock again. If you login/out without any further action(!) once(!) in the kde desktop as rootuser everything works...again. Therefore: it seemed to me that there was a permission problem in the 32 bit version of TW (latest). HOWEVER, there is a glitch. When you do this after a reboot or suspend, the BT works. (e.g. Obex etc) but the pairing is lost. The mouse previously paired will not be able to connect any more. (Mouse not ready). If you put the very mouse in the pairing mode and repair it, for the session (and limited to it) the BT mouse will work then. It is possible that this second fact is a separate bug, but as I do have to follow this admittedly complicated procedure every time I start the system I cannot know if the pairing problem would present also without the "kde-root-login" step. Expected behaviour: BT is a consolidated and widespread technology that is key for smartphones, earphones, viva-voce and mouse / keyboard devices for mobile hardware. It should be simple to set up, work absolutely reliable (many devices need BT support of mouse an keyboard to be usable). P.S. The root login was found after a lot of other trials. The bug presented previous to any root login in any desktop environment on a fresh install with all updates. I can therefore exclude that the whole problem is circular (that is that the root DE loging is the very cause of the permission problem. Permissions (or function?) with softlock was present PRIOR to all trial and checks on a fresh standard install. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 998553] New: Can not copy files from Dolphin to a Samba share. Copying from Krusader works without a hitch.
by bugzilla_noreply＠novell.com 10 Jun '18

10 Jun '18

http://bugzilla.opensuse.org/show_bug.cgi?id=998553 Bug ID: 998553 Summary: Can not copy files from Dolphin to a Samba share. Copying from Krusader works without a hitch. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Major Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: kiv(a)mail.orbitel.bg QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I am using Dolphin 16.08.0 from openSUSE Tumbleweed. Recently by trying to copy from a local directory to a Samba share I fount it does not work. Nor drag and drop works, nor Ctrl+V and in the right mouse click menu paste option is not possible to use trying to copy files from my computer to the share. Mean time I can use same Dolphin to browse the share and can drag & drop or copy files from the same share on the Samba server to my local folders. In past from time to time when drag & drop files to same Samba share it happen to found some times it did not work. But in such cases I could copy and paste files there to do my job. I thing this is a bug in Dolphin because Konqueror works fine, coping the same files to the same Samba share without any problem. My feeling is Dolphin got this bug by some of the last updates. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[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 1017067] New: Buttons of Wacom Bamboo Touch (CTH-460) not recognized (not working)
by bugzilla_noreply＠novell.com 07 Jun '18

07 Jun '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1017067 Bug ID: 1017067 Summary: Buttons of Wacom Bamboo Touch (CTH-460) not recognized (not working) Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: All OS: openSUSE 42.2 Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: Ulrich.Windl(a)rz.uni-regensburg.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When connecting a Wacom Bamboo Touch (CHT-460), it is recognized as 'Wacom BambooPT 2FG 4x5 Pad'. When I press one of the buttons on the tablet, an error message appears in the session log: (gnome-settings-daemon:5731): wacom-plugin-WARNING **: Could not find matching button for '1' on 'Wacom BambooPT 2FG 4x5 Pad' (gnome-settings-daemon:5731): wacom-plugin-WARNING **: Could not find matching button for '3' on 'Wacom BambooPT 2FG 4x5 Pad' (gnome-settings-daemon:5731): wacom-plugin-WARNING **: Could not find matching button for '9' on 'Wacom BambooPT 2FG 4x5 Pad' (gnome-settings-daemon:5731): wacom-plugin-WARNING **: Could not find matching button for '8' on 'Wacom BambooPT 2FG 4x5 Pad' (There are four buttons on the tablet. See page 7 of http://cdn.wacom.com/f/manuals/en/bamboo-users-manual.pdf: It's not exactly the same, but the buttons look like that. See page 34 what the buttons should do by default) Especially the ability to toggle touch on and off would be great when using the pen, because otherwise any touch of the surface will generate undesired events. For touch only, the left and right click are also essential. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[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