December 2016 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 947161] New: Attempt the goal to have a default setup without any -32bit packages installed
by bugzilla_noreply＠novell.com 24 Jun '19

24 Jun '19

http://bugzilla.opensuse.org/show_bug.cgi?id=947161 Bug ID: 947161 Summary: Attempt the goal to have a default setup without any -32bit packages installed Classification: openSUSE Product: openSUSE Factory Version: 201505* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- A standard x86_64 machine should not have to pull in any -32bit packages. Those are compatibility layers, generally provided for backwards compatibility with binary-only modules. The goal is to eliminate the installation of *-32bit by default (the goal is NOT to eliminate the presence of the *-32bit packages!) This might actually solve issues like ug 799367 as well -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1014999] New: Display freezes randomly on Leap 42.2 running KDE Plasma (plasmashell 5.8.x)
by bugzilla_noreply＠novell.com 17 Jun '19

17 Jun '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1014999 Bug ID: 1014999 Summary: Display freezes randomly on Leap 42.2 running KDE Plasma (plasmashell 5.8.x) Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: x86-64 OS: openSUSE 42.2 Status: NEW Severity: Major Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: nsleasy(a)hotmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:50.0) Gecko/20100101 Firefox/50.0 Build Identifier: The computer/display locks up at random intervals running openSUSE Leap 42.2 KDE Plasma (plasmashell 5.8.x). When this happens, the mouse pointer still works, but the user is unable to do anything with it. The keyboard is locked completely and the only remedy is to do a hard shutdown (forced power down) and fresh boot. This problem does not seem to occur at all running GNOME, Cinnamon or Xfce. I've eliminated the display manager as the issue because the display also freezes randomly running KDE Plasma 5.8.3 from LIGHTDM rather than SDDM. The following additional information is relevant: plasmashell 5.5.x on openSUSE Leap 42.1 -- works fine plasmashell 5.5.x on Kubuntu 16.04 -- works fine plasmashell 5.5.x on Fedora 23 -- works fine plasmashell 5.6.x on LinuxMint 18 -- works fine plasmashell 5.8.x on openSUSE Leap 42.2 -- screen freezes ~> plasmashell -v plasmashell 5.8.3 This is, potentially, a KDE Plasma 5.8.x bug rather than openSUSE per se, but opening it here under openSUSE Leap 42.2. Please let me know if this should be filed directly with the KDE team. Reproducible: Always Steps to Reproduce: 1. Run KDE Plasma 5.8.3 under openSUSE Leap 42.2 2. Use computer normally 3. After a seemingly random period of time, the screen freezes and the user must do a a hard boot Actual Results: See above Expected Results: See above See above -- You are receiving this mail because: You are on the CC list for the bug.

1 26

[Bug 1008289] New: system does not boot with EFI and MS-DOS partition table
by bugzilla_noreply＠novell.com 13 Jun '19

13 Jun '19

http://bugzilla.suse.com/show_bug.cgi?id=1008289 Bug ID: 1008289 Summary: system does not boot with EFI and MS-DOS partition table Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Bootloader Assignee: jsrain(a)suse.com Reporter: aschnell(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- The system does not boot with EFI and MS-DOS partition table. How to reproduce: Start installation on a EFI system that has one disk and an empty MS-DOS partition table on that disk. -- You are receiving this mail because: You are on the CC list for the bug.

1 21

[Bug 1016931] New: nrpe reload does not work
by bugzilla_noreply＠novell.com 05 Jun '19

05 Jun '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1016931 Bug ID: 1016931 Summary: nrpe reload does not work 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: sweet_f_a(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- "rcnrpe reload" does not work since we are using a systemd service file. Failed to reload nrpe.service: Job type reload is not applicable for unit nrpe.service. The init script of openSUSE 13.1 worked fine just sending SIGHUP. BTW what are all these file good for? /usr/lib/systemd/system/nrpe.service /usr/lib/systemd/system/nrpe@.service /usr/lib/systemd/system/nrpe.socket nrpe.socket does not seem do be used. nrpe@.service, whatever it's good for, contains wrong binary and config file paths. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 901115] New: yast2-network overwrites postfix configuration
by bugzilla_noreply＠novell.com 05 Jun '19

05 Jun '19

http://bugzilla.suse.com/show_bug.cgi?id=901115 Bug ID: 901115 Summary: yast2-network overwrites postfix configuration Classification: openSUSE Product: openSUSE Factory Version: 201410* Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: lmb(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 609975 --> http://bugzilla.suse.com/attachment.cgi?id=609975&action=edit main.cf mods caused by yast2 network After a long time, I used yast2-network to change something in the network configuration of my node. (Changed the hostname.) As a result, my postfix main.cf was overwritten and rendered unusuable. I'm entirely unsure why some of these parameters were touched - why would it unset mailbox_command, set mailbox_transport, unset relay_host? Yes, this was facilitated by me having /etc/sysconfig/mail:MAIL_CREATE_CONFIG="yes" at the default value, but normally, none of the yast2 tools overwrites manually modified files silently, without even creating an in-place backup. Especially since this looks as if unrelated parameters were touched. I might have understood rewriting "mydestination", but the other parameters make absolutely no sense. I'm attaching the diff here - I restored the main.cf from backup. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 965304] New: Change gnome-ppp on gtk-ppp
by bugzilla_noreply＠novell.com 23 May '19

23 May '19

http://bugzilla.opensuse.org/show_bug.cgi?id=965304 Bug ID: 965304 Summary: Change gnome-ppp on gtk-ppp Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: roman_romul(a)mail.ru QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- GTK PPP is an easy to use graphical dialup connection configuring and dialing tool with system tray icon support. It uses GTK+ for its graphical interface and integrates well in GNOME desktop environment. It also uses WvDial dialer as its backend, providing simple configuration via config files. You can also use plain wvdial if you don't have X running. GTK PPP is GTK3 fork of GNOME PPP. https://sourceforge.net/projects/gtk-ppp/ Gnome-ppp was for OpenSuSE 12.X -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 997935] New: api returns HTTP 500 if a PUT request does not contain a Content-type: header
by bugzilla_noreply＠novell.com 14 May '19

14 May '19

http://bugzilla.suse.com/show_bug.cgi?id=997935 Bug ID: 997935 Summary: api returns HTTP 500 if a PUT request does not contain a Content-type: header Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: BuildService Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: mmarek(a)suse.com QA Contact: adrian(a)suse.com CC: afaerber(a)suse.com, jslaby(a)suse.com Found By: --- Blocker: --- The external Kernel:* and internal Devel:Kernel:* projects stopped updating recently, because the upload script is receiving HTTP 500 now. It can also be reproduced by curl: $ curl -n -T data.xml 'https://api.suse.de/source/home:michal-m:test/_meta?force=1' 500 Internal Server Error If you are the administrator of this website, then please read this web application's log file and/or the web server's log file to find out what went wrong. It does work with 'osc api -M PUT -f data.xml'. The difference turns out to be the Content-type header, which osc sends. I will fix the script to also send the header, but please fix the server so that it is not as picky. Ironically, the header value is not used anywhere: osc sends application/octet-stream when uploading XML and the server accepts anything: $ curl -n -T data.xml -H 'Content-type: yada/dada' 'https://api.suse.de/source/home:michal-m:test/_meta?force=1' <status code="ok"> <summary>Ok</summary> </status> -- You are receiving this mail because: You are on the CC list for the bug.

1 17

[Bug 1013916] New: No Spice client in spice-client package?
by bugzilla_noreply＠novell.com 14 May '19

14 May '19

http://bugzilla.suse.com/show_bug.cgi?id=1013916 Bug ID: 1013916 Summary: No Spice client in spice-client package? Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications Assignee: cbosdonnat(a)suse.com Reporter: lpechacek(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After reading the package description, I was surprised to find only documentation in spice-client package. Shoudln't there be a Spice client application included? lpechacek@fm:~> rpm -qil spice-client Name : spice-client Version : 0.12.7 Release : 1.4 Architecture: x86_64 Install Date: Tue 06 Dec 2016 12:54:37 PM CET Group : Productivity/Networking/Other Size : 43350 License : LGPL-2.1+ Signature : RSA/SHA256, Fri 07 Oct 2016 09:13:26 PM CEST, Key ID b88b2fd43dbdc284 Source RPM : spice-0.12.7-1.4.src.rpm Build Date : Fri 07 Oct 2016 09:12:42 PM CEST Build Host : build15 Relocations : (not relocatable) Packager : http://bugs.opensuse.org Vendor : openSUSE URL : http://www.spice-space.org/ Summary : SPICE client Description : The SPICE client provides access to a remote machine's display and devices. Distribution: openSUSE Leap 42.2 /usr/share/doc/packages/spice-client /usr/share/doc/packages/spice-client/AUTHORS /usr/share/doc/packages/spice-client/COPYING /usr/share/doc/packages/spice-client/NEWS /usr/share/doc/packages/spice-client/README -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 991188] New: Extra \n's in shim-install --help output
by bugzilla_noreply＠novell.com 14 May '19

14 May '19

http://bugzilla.suse.com/show_bug.cgi?id=991188 Bug ID: 991188 Summary: Extra \n's in shim-install --help output Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem Assignee: glin(a)suse.com Reporter: lpechacek(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- fmn:~ # shim-install --help Usage: shim-install [OPTION] [INSTALL_DEVICE] Install Secure Boot Loaders on your drive.\n --directory=DIR use images from DIR.\n --grub-probe=FILE use FILE as grub-probe.\n --removable the installation device is removable.\n --bootloader-id=ID the ID of bootloader.\n --efi-directory=DIR use DIR as the EFI System Partition root.\n --config-file=FILE use FILE as config file, default is /boot/grub2/grub.cfg.\n --clean remove all installed files and configs.\n INSTALL_DEVICE must be system device filename.\n -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 991187] New: shim-install keeping silent about obvious errors
by bugzilla_noreply＠novell.com 14 May '19

14 May '19

http://bugzilla.suse.com/show_bug.cgi?id=991187 Bug ID: 991187 Summary: shim-install keeping silent about obvious errors Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: Basesystem Assignee: glin(a)suse.com Reporter: lpechacek(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- In my custom installation shim-install failed during installation. The only information installer relayed was exit code 1. After re-running shim-install on the installed system I got the same result. fmn:~ # shim-install --config-file=/boot/grub2/grub.cfg fmn:~ # echo $? 1 Running shim-install with Bash debugging enabled has shown the root cause. fmn:~ # bash -x /usr/sbin/shim-install --config-file=/boot/grub2/grub.cfg ... + bootdir=/boot + '[' -n '' ']' + test -n '' + test -d /boot/efi + test -d /boot/EFI + test -n '' + test -n '' + test -n '' + exit 1 I forgot to instruct the installer to mount EFI partition during installation. I would welcome a more verbose message from shim-install in this case for the sake of reduced debugging time. -- You are receiving this mail because: You are on the CC list for the bug.

1 4