March 2019 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1127907] New: obs-service-tar_scm breaks with unicode in filenames
by bugzilla_noreply＠novell.com 05 Mar '19

05 Mar '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1127907 Bug ID: 1127907 Summary: obs-service-tar_scm breaks with unicode in filenames Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.3 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: FSchreiner(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 31: ordinal not in range(128) -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1120957] [Build 20190103] keyboard language cannot be changed in textmode
by bugzilla_noreply＠novell.com 05 Mar '19

05 Mar '19

http://bugzilla.suse.com/show_bug.cgi?id=1120957 http://bugzilla.suse.com/show_bug.cgi?id=1120957#c10 --- Comment #10 from Lukas Ocilka <locilka(a)suse.com> --- modules/Keyboard.rb:515 Setting keyboard to: <french> modules/Keyboard.rb:316 keyboard model used: pc104 modules/Keyboard.rb:526 Description for keyboard <french>: <["French", $["ncurses":"fr-latin1.map.gz"]]> modules/Keyboard.rb:540 x11data=$["Apply":"-layout fr -model pc105 -option terminate:ctrl_alt_bksp", "XkbLayout":"fr", "XkbModel":"pc105", "XkbOptions":"terminate:ctrl_alt_bksp"] Setting console keyboard to: <french> modules/Keyboard.rb:994 loadkeys command: </usr/bin/loadkeys -C /dev/ttyS31 -C /dev/ttyS30 -C /dev/ttyS29 -C /dev/ttyS28 -C /dev/ttyS27 -C /dev/ttyS26 -C /dev/ttyS25 -C /dev/ttyS24 -C /dev/ttyS23 -C /dev/ttyS22 -C /dev/ttyS21 -C /dev/ttyS20 -C /dev/ttyS19 -C /dev/ttyS18 -C /dev/ttyS17 -C /dev/ttyS16 -C /dev/ttyS15 -C /dev/ttyS14 -C /dev/ttyS13 -C /dev/ttyS12 -C /dev/ttyS11 -C /dev/ttyS10 -C /dev/ttyS9 -C /dev/ttyS8 -C /dev/ttyS7 -C /dev/ttyS6 -C /dev/ttyS5 -C /dev/ttyS4 -C /dev/ttyS3 -C /dev/ttyS2 -C /dev/ttyS1 -C /dev/ttyS0 -C /dev/tty63 -C /dev/tty62 -C /dev/tty61 -C /dev/tty60 -C /dev/tty59 -C /dev/tty58 -C /dev/tty57 -C /dev/tty56 -C /dev/tty55 -C /dev/tty54 -C /dev/tty53 -C /dev/tty52 -C /dev/tty51 -C /dev/tty50 -C /dev/tty49 -C /dev/tty48 -C /dev/tty47 -C /dev/tty46 -C /dev/tty45 -C /dev/tty44 -C /dev/tty43 -C /dev/tty42 -C /dev/tty41 -C /dev/tty40 -C /dev/tty39 -C /dev/tty38 -C /dev/tty37 -C /dev/tty36 -C /dev/tty35 -C /dev/tty34 -C /dev/tty33 -C /dev/tty32 -C /dev/tty31 -C /dev/tty30 -C /dev/tty29 -C /dev/tty28 -C /dev/tty27 -C /dev/tty26 -C /dev/tty25 -C /dev/tty24 -C /dev/tty23 -C /dev/tty22 -C /dev/tty21 -C /dev/tty20 -C /dev/tty19 -C /dev/tty18 -C /dev/tty17 -C /dev/tty16 -C /dev/tty15 -C /dev/tty14 -C /dev/tty13 -C /dev/tty12 -C /dev/tty11 -C /dev/tty10 -C /dev/tty9 -C /dev/tty8 -C /dev/tty7 -C /dev/tty6 -C /dev/tty5 -C /dev/tty4 -C /dev/tty3 -C /dev/tty2 -C /dev/tty1 -C /dev/tty0 -C /dev/tty fr-latin1.map.gz> 2019-01-04 13:43:29 <3> install(3341) [bash] ShellCommand.cc(shellcommand):78 Couldn't open /dev/tty 2019-01-04 13:43:29 <1> install(3341) [Ruby] modules/Keyboard.rb:1016 Not setting X keyboard due to text mode Maybe the loadkeys call actually failed because of "Couldn't open /dev/tty"? Linuxrc cmdline was: splash=silent vga=791 video=1024x768-16 plymouth.ignore-serial-consoles console=ttyS0 console=tty IMO looks like test-specific or openQA-specific. I haven't seen any similar report from a TW user. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1113748] iotop crashes when /proc/*/status doesn't have tab character or when /proc/*/status has invalid lines
by bugzilla_noreply＠novell.com 05 Mar '19

05 Mar '19

http://bugzilla.suse.com/show_bug.cgi?id=1113748 http://bugzilla.suse.com/show_bug.cgi?id=1113748#c7 Michael Vetter <mvetter(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|mvetter(a)suse.com |ldevulder(a)suse.com --- Comment #7 from Michael Vetter <mvetter(a)suse.com> --- Reassigning to Loic. I think he did everything already, only needs to close or reassign to security. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1055749] LXQT: no icons in programs' menu for newly installed programs
by bugzilla_noreply＠novell.com 05 Mar '19

05 Mar '19

http://bugzilla.suse.com/show_bug.cgi?id=1055749 http://bugzilla.suse.com/show_bug.cgi?id=1055749#c1 Michael Vetter <mvetter(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #1 from Michael Vetter <mvetter(a)suse.com> --- Can't reproduce this anymore on current LXQt 0.14.1. Assuming it's fixed. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1100155] LXQt themes - No contrast for icons on Desktop
by bugzilla_noreply＠novell.com 05 Mar '19

05 Mar '19

http://bugzilla.suse.com/show_bug.cgi?id=1100155 http://bugzilla.suse.com/show_bug.cgi?id=1100155#c1 Michael Vetter <mvetter(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS --- Comment #1 from Michael Vetter <mvetter(a)suse.com> --- I cannot remember having such an issue myself. Tested now on LXQt 0.14.1 (Tumbleweed) I also can't reproduce. I tend to close this issue because 0.14.1 will be in Leap 15.1. Could you attach a screenshot of this issue if it still occurs for you? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1100155] LXQt themes - No contrast for icons on Desktop
by bugzilla_noreply＠novell.com 05 Mar '19

05 Mar '19

http://bugzilla.suse.com/show_bug.cgi?id=1100155 Michael Vetter <mvetter(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|LXDE |LXQt -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1127849] Zypper segfaults in official openSUSE docker image (opensuse/ namespace)
by bugzilla_noreply＠novell.com 05 Mar '19

05 Mar '19

http://bugzilla.suse.com/show_bug.cgi?id=1127849 http://bugzilla.suse.com/show_bug.cgi?id=1127849#c7 --- Comment #7 from Richard Palethorpe <richard.palethorpe(a)suse.com> --- In gitlab it is quite easy to use our own test runners where we have control over the host. Github is another matter, especially as we are talking about an upstream project where it might not be so easy to get access to cloud.suse.de where I am hosting the runners. However we might be able to get some public cloud hosting from the Linux Foundation. This also leads into using Cyrils new test runner to run the actual LTP test cases in CI, but that needs to be either on bare metal or on a host which is guaranteed to support nested virtualization. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1127849] Zypper segfaults in official openSUSE docker image (opensuse/ namespace)
by bugzilla_noreply＠novell.com 05 Mar '19

05 Mar '19

http://bugzilla.suse.com/show_bug.cgi?id=1127849 http://bugzilla.suse.com/show_bug.cgi?id=1127849#c6 --- Comment #6 from Petr Vorel <petr.vorel(a)suse.com> --- (In reply to Richard Brown from comment #5) > Ok but how is that going to work? There is no kernel in our OCI > containers..so upstream LTP actually want a situation where openSUSE LTP is > run against unknown, unvetted, arbitrary kernels from their CI host? > That seems like an invitation for the sort of unexplained problems as you > currently see here.. That LTP CI is for LTP itself, i.e. for building LTP. But that's a bit OT to the bug. It'd be nice these bugs were caught before they reach users. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1111950] maildir-utils .elc varies between builds from parallelism
by bugzilla_noreply＠novell.com 05 Mar '19

05 Mar '19

http://bugzilla.suse.com/show_bug.cgi?id=1111950 http://bugzilla.suse.com/show_bug.cgi?id=1111950#c3 --- Comment #3 from Swamp Workflow Management <swamp(a)suse.de> --- This is an autogenerated message for OBS integration: This bug (1111950) was mentioned in https://build.opensuse.org/request/show/681670 Factory / maildir-utils -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1127849] Zypper segfaults in official openSUSE docker image (opensuse/ namespace)
by bugzilla_noreply＠novell.com 05 Mar '19

05 Mar '19

http://bugzilla.suse.com/show_bug.cgi?id=1127849 http://bugzilla.suse.com/show_bug.cgi?id=1127849#c5 --- Comment #5 from Richard Brown <rbrown(a)suse.com> --- (In reply to Petr Vorel from comment #3) > (In reply to Richard Brown from comment #2) > > If you want reliable testing, use a reliable test host instead of those with > > old/obsolete hosts (the current leading hypothesis for this failure) > > > > I can recommend openQA ;) > Well, this idea that openQA is suitable for everything is simply wrong and > IMHO hurts openQA. Anyway, we do have LTP tests in openQA, but that's for > testing openSUSE/SLES. openSUSE images in travis are for LTP upstream CI > testing, using openQA wouldn't be the best solution nor acceptable for > upstream. Ok but how is that going to work? There is no kernel in our OCI containers..so upstream LTP actually want a situation where openSUSE LTP is run against unknown, unvetted, arbitrary kernels from their CI host? That seems like an invitation for the sort of unexplained problems as you currently see here.. -- You are receiving this mail because: You are on the CC list for the bug.

1 0