June 2019 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1137578] Using sudo the first time results in multiple errors
by bugzilla_noreply＠novell.com 07 Jun '19

07 Jun '19

http://bugzilla.suse.com/show_bug.cgi?id=1137578 http://bugzilla.suse.com/show_bug.cgi?id=1137578#c3 --- Comment #3 from Matthias Gerstner <matthias.gerstner(a)suse.com> --- So I just made a fresh installation of leap 15.1 and sudo works fine there. So the problem msut be something you installed or configured afterwards. Please provide the following information for allowing deeper analysis: 1) the content of your /etc/suoders 2) the output of `ls -l /etc/suoders` 3) the output of `ls -l /usr/bin/sudo` 4) the output of the `groups` command run as the user you're using sudo with 5) the output of the `id` command run as the user you're using sudo with 6) the output of `journalctl | grep sudo` run as root after the sudo error occured Thank you. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1136927] [Build 20190528] System does not use same network names after update
by bugzilla_noreply＠novell.com 07 Jun '19

07 Jun '19

http://bugzilla.suse.com/show_bug.cgi?id=1136927 http://bugzilla.suse.com/show_bug.cgi?id=1136927#c16 --- Comment #16 from Oliver Kurz <okurz(a)suse.com> --- https://openqa.opensuse.org/tests/952007#step/check_network/3 looks like it worked! The network seems to be intact. Please crosscheck the openQA results if they correspond to your expectation. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1092845] YaST displays wrong title for applications in Gnome
by bugzilla_noreply＠novell.com 07 Jun '19

07 Jun '19

http://bugzilla.suse.com/show_bug.cgi?id=1092845 http://bugzilla.suse.com/show_bug.cgi?id=1092845#c19 Steffen Winterfeldt <snwint(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |FIXED --- Comment #19 from Steffen Winterfeldt <snwint(a)suse.com> --- Seems we can close this bug. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1116584] libyui-qt* missing after latest TW upgrade
by bugzilla_noreply＠novell.com 07 Jun '19

07 Jun '19

http://bugzilla.suse.com/show_bug.cgi?id=1116584 http://bugzilla.suse.com/show_bug.cgi?id=1116584#c14 Steffen Winterfeldt <snwint(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |stephan.barth(a)suse.com --- Comment #14 from Steffen Winterfeldt <snwint(a)suse.com> --- *** Bug 1137328 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1134320] New: gpg does not work anymore
by bugzilla_noreply＠novell.com 07 Jun '19

07 Jun '19

http://bugzilla.suse.com/show_bug.cgi?id=1134320 Bug ID: 1134320 Summary: gpg does not work anymore Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: werner(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I currently try to read an encrypted file with gpg --no-batch --pinentry-mode ask -d <myfile.gpg> this break at the point where the gpg read from file descriptor 6 which is the open socket to the running gpg-agent. This works flawless on Leap 15.0 but on Tumbleweed I see in the strace that at the end the gpg send some commands to the gpg-agent but never ever gets an answer hence this hanging read: write(6, "HAVEKEY XXXXXXXXXXXXXXXXXXXXXXX"..., 89) = 89 write(6, "\n", 1) = 1 read(6, "OK\n", 1002) = 3 write(6, "HAVEKEY XXXXXXXXXXXXXXXXXXXXXXXXXXX"..., 48) = 48 write(6, "\n", 1) = 1 read(6, "OK\n", 1002) = 3 openat(AT_FDCWD, "/etc/localtime", O_RDONLY|O_CLOEXEC) = 7 fstat(7, {st_mode=S_IFREG|0644, st_size=2326, ...}) = 0 fstat(7, {st_mode=S_IFREG|0644, st_size=2326, ...}) = 0 read(7, "TZif2\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\t\0\0\0\t\0\0\0\0"..., 4096) = 2326 lseek(7, -1467, SEEK_CUR) = 859 read(7, "TZif2\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\t\0\0\0\t\0\0\0\0"..., 4096) = 1467 close(7) = 0 write(6, "RESET", 5) = 5 write(6, "\n", 1) = 1 read(6, "OK\n", 1002) = 3 write(6, "SETKEY XXXXXXXXXXXXXXXXXXXXXXXXX"..., 47) = 47 write(6, "\n", 1) = 1 read(6, "OK\n", 1002) = 3 write(6, "SETKEYDESC Please+enter+the+pass"..., 210) = 210 write(6, "\n", 1) = 1 read(6, "OK\n", 1002) = 3 write(6, "PKDECRYPT", 9) = 9 write(6, "\n", 1) = 1 read(6, "S INQUIRE_MAXLEN 4096\nINQUIRE CI"..., 1002) = 41 write(6, "D (7:enc-valXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX..., 552) = 552 write(6, "END", 3) = 3 write(6, "\n", 1) = 1 Here i have replaced the keys with XX ... in comparision with Leap 15.0 I see openat(AT_FDCWD, "$HOME/.gnupg/pubring.gpg", O_RDONLY) = 5 lseek(5, 7833322, SEEK_SET) = 7833322 and the encrypted content (I've also replaced here the home directory with $ĦOME) ... Does gpg-agent read the ~/.gnupg/gpg-agent.conf where I've set pinentry-program /usr/bin/pinentry-curses -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1116584] libyui-qt* missing after latest TW upgrade
by bugzilla_noreply＠novell.com 07 Jun '19

07 Jun '19

1 0

[Bug 1137342] VERSION variable at /etc/os-release contains an extra whitespace
by bugzilla_noreply＠novell.com 07 Jun '19

07 Jun '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1137342 http://bugzilla.opensuse.org/show_bug.cgi?id=1137342#c6 Julio González Gil <jgonzalez(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS --- Comment #6 from Julio González Gil <jgonzalez(a)suse.com> --- I just submitted: https://build.opensuse.org/request/show/708256 (Leap 15.1) https://build.opensuse.org/request/show/708259 (Factory) I hope I didn't make any mistakes at the MR/SR, but if I did... just ping. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1133312] Dependencies for Vagrant are broken
by bugzilla_noreply＠novell.com 07 Jun '19

07 Jun '19

http://bugzilla.suse.com/show_bug.cgi?id=1133312 http://bugzilla.suse.com/show_bug.cgi?id=1133312#c17 --- Comment #17 from Andrew Wood <andrew(a)fluidgravity.co.uk> --- (In reply to Dan Čermák from comment #16) > (In reply to Andrew Wood from comment #15) > > > > vagrant-vbguest installs successfully with zypper. > > > > I also need vagrant-hosts and vagrant-scp, but "vagrant plugin install ..." > > complains about conflicting dependencies for fog-core again. > > > > Can you add these too? > > > > Thanks. > > I'll put these two on my Todo list, but cannot promise an ETA. Ok, thank you. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1121654] New: Warning: modules_install: missing 'System.map' file. Skipping depmod
by bugzilla_noreply＠novell.com 07 Jun '19

07 Jun '19

http://bugzilla.suse.com/show_bug.cgi?id=1121654 Bug ID: 1121654 Summary: Warning: modules_install: missing 'System.map' file. Skipping depmod Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: lyan(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When I am trying to install a modules, it keeps reporting this warning and failed my installment, but I could see System.map* file is under /boot. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1118868] kernel panic on shutdown
by bugzilla_noreply＠novell.com 07 Jun '19

07 Jun '19

http://bugzilla.suse.com/show_bug.cgi?id=1118868 http://bugzilla.suse.com/show_bug.cgi?id=1118868#c10 Jiri Slaby <jslaby(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |jslaby(a)suse.com Resolution|--- |FIXED --- Comment #10 from Jiri Slaby <jslaby(a)suse.com> --- So I assume this is gone since 4.20, right? -- You are receiving this mail because: You are on the CC list for the bug.

1 0