January 2017 - openSUSE Bugs - openSUSE Mailing Lists

[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

[Bug 917431] New: less doesn't open gzip'ed files unpacked anymore
by bugzilla_noreply＠novell.com 13 May '19

13 May '19

http://bugzilla.suse.com/show_bug.cgi?id=917431 Bug ID: 917431 Summary: less doesn't open gzip'ed files unpacked anymore Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: stephan.barth(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When looking at files with less like ARCHIVES.gz it unpacked it automatically. Since the recent updates this doesn't work anymore: # less ARCHIVES.gz "ARCHIVES.gz" may be a binary file. See it anyway? I tried to debug it a bit with "set -x", which didn't help. The funny thing is, that after issuing "set +x" less works as expected again. Using su (to root for example) breaks it again. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 984778] New: zypper (unlike YaST) gives no reboot warning after updating the kernel
by bugzilla_noreply＠novell.com 13 May '19

13 May '19

http://bugzilla.opensuse.org/show_bug.cgi?id=984778 Bug ID: 984778 Summary: zypper (unlike YaST) gives no reboot warning after updating the kernel Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: x86-64 OS: openSUSE 42.1 Status: NEW Severity: Normal Priority: P5 - None Component: libzypp Assignee: zypp-maintainers(a)forge.provo.novell.com Reporter: antoine.mechelynck(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: Community User Blocker: --- After updating the kernel, zypper doesn't warn the user that a reboot is necessary (YaST does). Even "zypper ps" says "No processes using deleted files found" in that case, because the "old" kernel is left lying around in /boot. (I noticed it today when "zypper up" upgraded my kernel from 4.1.24-19 to 4.1.26-21 from the Leap 42.1 Update-Test repository.) -- You are receiving this mail because: You are on the CC list for the bug.

1 25

[Bug 993426] New: [regression on kernel 4.7.0] cannot use tftp over NAT
by bugzilla_noreply＠novell.com 10 May '19

10 May '19

http://bugzilla.opensuse.org/show_bug.cgi?id=993426 Bug ID: 993426 Summary: [regression on kernel 4.7.0] cannot use tftp over NAT Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: luizluca(a)tre-sc.jus.br QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hello, Since kernel 4.7.0, I cannot use tftp over NAT. The last known working kernel is 4.6.4-2.2. I have helper modules loaded (nf_nat_tftp, nf_conntrack_tftp) but it seems that conntrack is not able "to track" tftp "sessions". I can see the package from internal machine entering the internal interface: UDP from internal-machine-ip:2071 to tftp-server:69 Leaving the external interface: UDP from opensuse-ip:2071 to tftp-server:69 And the answer: UDP from tftp-server:35088 to opensuse-ip:2071 But the firewall blocks it as an unknown traffic: SFW2-INext-DROP-DEFLT IN=eth0 OUT= MAC=f0:4d:a2:e6:9a:76:00:1e:bd:44:41:57:08:00 SRC=tftp-server DST=opensuse-ip LEN=42 TOS=0x00 PREC=0x00 TTL=63 ID=14088 DF PROTO=UDP SPT=35088 DPT=2071 LEN=22 I do have the default "accept ctstate ESTABLISHED" generated by SUSEFirewall. "conntrack -L" shows me: udp 17 20 src=internal-machine-ip dst=tftp-server sport=2071 dport=69 [UNREPLIED] src=tftp-server dst=opensuse-ip sport=69 dport=2071 mark=0 use=1 My test internal machine is an vbox VM. However, as I'm using host-only interface with Linux DHCP and NAT (and not vbox one), the virtualization might not be significant. If I reboot the machine using the 4.6.x kernel and reinstall only the vbox module (to match the kernel version), tftp starts to work again. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 606436] New: Incorrect VTY charset?
by bugzilla_noreply＠novell.com 09 May '19

09 May '19

http://bugzilla.novell.com/show_bug.cgi?id=606436 http://bugzilla.novell.com/show_bug.cgi?id=606436#c0 Summary: Incorrect VTY charset? Classification: openSUSE Product: openSUSE 11.3 Version: Milestone 6 Platform: All OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: nice(a)titanic.nyme.hu QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US) AppleWebKit/5332 (KHTML, like Gecko) Chrome/5.0.342.9 Safari/533.2 I installed openSUSE 11.3 Milestone 6 in the hungarian language. Interestingly when using the text-mode virtual terminals, (at least) two letters of the hungarian alphabet are displayed incorrectly: I get õ instead of ő, and û instead of ű. This is the same as displaying a hungarian text file (written in iso-8859-2) using iso-8859-1. Isn't it unicode? Or are just the characters wrongly positioned in the charset table? Also see: http://bugzilla.novell.com/show_bug.cgi?id=605575 Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 10

[Bug 986534] New: mutt unconditionally segfaults when displaying a message
by bugzilla_noreply＠novell.com 09 May '19

09 May '19

http://bugzilla.suse.com/show_bug.cgi?id=986534 Bug ID: 986534 Summary: mutt unconditionally segfaults when displaying a message Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: lpechacek(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- $ gdb mutt (gdb) run -F /dev/shm/muttrc <select a message to display....> Fetching message... 0K/3.9K (0%) Program received signal SIGSEGV, Segmentation fault. __strlen_ia32 () at ../sysdeps/i386/i586/strlen.S:94 94 movl (%eax), %ecx /* get word (= 4 bytes) in question */ Missing separate debuginfos, use: zypper install cyrus-sasl-crammd5-debuginfo-2.1.26-12.3.i586 cyrus-sasl-debuginfo-2.1.26-12.3.i586 cyrus-sasl-digestmd5-debuginfo-2.1.26-12.3.i586 cyrus-sasl-gssapi-debuginfo-2.1.26-12.3.i586 cyrus-sasl-plain-debuginfo-2.1.26-12.3.i586 glibc-locale-debuginfo-2.23-4.1.i586 krb5-debuginfo-1.14.2-1.2.i586 libassuan0-debuginfo-2.4.2-1.2.i586 libcom_err2-debuginfo-1.42.13-3.4.i586 libdb-4_8-debuginfo-4.8.30-31.60.i586 libffi4-debuginfo-5.3.1+r234891-1.20.i586 libgcc_s1-gcc6-debuginfo-6.1.1+r236988-1.1.i586 libgdbm4-debuginfo-1.12-1.1.i586 libgio-2_0-0-debuginfo-2.48.1-1.1.i586 libglib-2_0-0-debuginfo-2.48.1-1.1.i586 libgmime-2_6-0-debuginfo-2.6.20-4.4.i586 libgmodule-2_0-0-debuginfo-2.48.1-1.1.i586 libgobject-2_0-0-debuginfo-2.48.1-1.1.i586 libgpg-error0-debuginfo-1.22-1.1.i586 libgpgme11-debuginfo-1.6.0-2.3.i586 libidn11-debuginfo-1.32-1.4.i586 libkeyutils1-debuginfo-1.5.9-5.5.i586 libncurses5-debuginfo-6.0-9.1.i586 libnotmuch4-debuginfo-0.20.2-1.4.i586 libopenssl1_0_0-debuginfo-1.0.2h-1.2.i586 libpcre1-debuginfo-8.38-1.55.i586 libsasl2-3-debuginfo-2.1.26-12.2.i586 libselinux1-debuginfo-2.3-5.81.i586 libstdc++6-gcc6-debuginfo-6.1.1+r236988-1.1.i586 libtalloc2-debuginfo-2.1.6-1.2.i586 libuuid1-debuginfo-2.28-2.1.i586 libxapian22-debuginfo-1.2.23-1.2.i586 libz1-debuginfo-1.2.8-11.58.i586 (gdb) bt #0 __strlen_ia32 () at ../sysdeps/i386/i586/strlen.S:94 #1 0xb7a397f1 in __GI__IO_fputs (str=0x12430 <error: Cannot access memory at address 0x12430>, fp=0x802015a8) at iofputs.c:33 #2 0x800248a6 in mutt_copy_header (in=0x80201708, h=0x80303c30, out=0x802015a8, flags=786582, prefix=0x0) at copy.c:435 #3 0x80024cba in _mutt_copy_message (fpout=0x802015a8, fpin=0x80201708, hdr=0x80303c30, body=0x80303c98, flags=76, chflags=786582) at copy.c:653 #4 0x80025387 in mutt_copy_message (fpout=0x802015a8, src=0x801dc1b0, hdr=0x80303c30, flags=76, chflags=786582) at copy.c:770 #5 0x8001d5ab in mutt_display_message (cur=0x80303c30) at commands.c:152 #6 0x8002c500 in mutt_index_menu () at curs_main.c:1867 #7 0x8000e5f3 in main (argc=<optimized out>, argv=<optimized out>) at main.c:886 (gdb) frame 2 #2 0x800248a6 in mutt_copy_header (in=0x80201708, h=0x80303c30, out=0x802015a8, flags=786582, prefix=0x0) at copy.c:435 435 fputs (nm_header_get_tags(h), out); (gdb) print *((struct nm_hdrdata *) h->data) $1 = {folder = 0x41 <error: Cannot access memory at address 0x41>, tags = 0x12430 <error: Cannot access memory at address 0x12430>, tags_transformed = 0x0, tag_list = 0x19, oldpath = 0x6863694d <error: Cannot access memory at address 0x6863694d>, virtual_id = 0x206c6561 <error: Cannot access memory at address 0x206c6561>, magic = 2054447437} (gdb) shell cat /dev/shm/muttrc set spoolfile=imaps://imap.suse.de/INBOX set imap_user=lpechacek set imap_pass="ThePassword" source /etc/skel/.muttrc (gdb) Rebuilding Mutt without Notmuch support makes Mutt work fine again. Index: mutt.spec =================================================================== --- mutt.spec (revision 71) +++ mutt.spec (working copy) @@ -205,7 +205,7 @@ --enable-mailtool \ --enable-compressed \ --enable-sidebar \ -%if 0%{?is_opensuse} +%if 0%{?is_opensuse} && 0 --enable-notmuch \ %endif --enable-hcache \ -- You are receiving this mail because: You are on the CC list for the bug.

1 17

[Bug 988721] New: KDE:Extra/quick-usb-formatter: Bug
by bugzilla_noreply＠novell.com 08 May '19

08 May '19

http://bugzilla.opensuse.org/show_bug.cgi?id=988721 Bug ID: 988721 Summary: KDE:Extra/quick-usb-formatter: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: kde-maintainers(a)suse.de Reporter: jrcolvin(a)gmail.com QA Contact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- Running on OpenSuse Leap 42.1 with the KDE desktop, Repository used KDE EXTRA. quick-usb-formatter 0.6-1.1-x86_64 I have installed the application through YAST using the KDE Extra repository. All dependencies should be installed. There seems to be a dependency error. Konsole output: anon@laptop:~> quickusbformatter **** FORMATTING AS FAT 32 EXEC COMMAND : "mkdosfs" , ARGS: ("-n", "'usbname'", "-v", "/dev/sdb1") Debug message from helper: Executing: /bin/bash -c "mkdosfs -n 'usbname' -v /dev/sdb1" Debug message from helper: ERROR OUTPUT : "/bin/bash: mkdosfs: command not found " Debug message from helper: OUTPUT: "" Debug message from helper: EXIT CODE : 127 Debug message from helper: ERROR : "Unknown error" Debug message from helper: Current Dir : "" Debug message from helper: Current env : ("DBUS_STARTER_ADDRESS=unix:path=/var/run/dbus/system_bus_socket", "DBUS_STARTER_BUS_TYPE=system", "HOME=/root") -- You are receiving this mail because: You are on the CC list for the bug.

1 8