September 2019 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1112998] ibus-libpinyin: emoji come to the candidate lists if it was switched to the traditional input method
by bugzilla_noreply＠novell.com 02 Sep '19

02 Sep '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1112998 http://bugzilla.opensuse.org/show_bug.cgi?id=1112998#c1 Cliff Zhao <qzhao(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FEATURE --- Comment #1 from Cliff Zhao <qzhao(a)suse.com> --- This is a feature, not a bug, if you interest on it, please open issue for upstream. Thanks! -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1022744] New: Infinite loop during boot because of USB device in kernel 4.9.6
by bugzilla_noreply＠novell.com 02 Sep '19

02 Sep '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1022744 Bug ID: 1022744 Summary: Infinite loop during boot because of USB device in kernel 4.9.6 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-maintainers(a)forge.provo.novell.com Reporter: martin.jakl(a)qbicon.cz QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.76 Safari/537.36 Build Identifier: I have motherboard with some problematic USB device, I don't know what it is, probably something internal, but windows also show one not working device. Until kernel 4.9.4 at the beginning of boot there was some message about not working USB device, but it booted and everything worked. In kernel 4.9.5 something changed and there was a loop of messages usb usb1-port2: unable to enumerate USB device usb usb2-port1: Cannot enable. Maybe the USB cable is bad? at first for 3 minutes connected with systemd-udev-settle messages and then another another 3 minutes with lvm2, after that it started, but dmesg was flooded with these messages. I masked systemd-udev-settle and turned off lvm2 and added cron job at @reboot to do: echo '0000:00:14.0' > /sys/bus/pci/drivers/xhci_hcd/unbind echo '0000:00:14.0' > /sys/bus/pci/drivers/xhci_hcd/bind after these changes I was able to boot in reasonable time and everything worked. But 4.9.6 changed something again and during boot, there is only infinite cycle of: usb usb1-port2: unable to enumerate USB device usb usb2-port1: Cannot enable. Maybe the USB cable is bad? I've waited for 15 minutes, but nothing changed. I've also tried 4.10.rc5 and it behaved the same as 4.9.6. Reproducible: Always Actual Results: Unable to boot with kernel 4.9.6. Expected Results: To be able to boot. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1135647] Missing ipv6 assignment with upgrade leap 15.0 to 15.1?
by bugzilla_noreply＠novell.com 02 Sep '19

02 Sep '19

http://bugzilla.suse.com/show_bug.cgi?id=1135647 http://bugzilla.suse.com/show_bug.cgi?id=1135647#c29 --- Comment #29 from andreas bittner <abittner(a)opensuse.org> --- just rebooted the machine (with the lacking public ipv6 assignment) and checking those sysctl files. this machine has these two lines: net.ipv4.ip_forward = 1 net.ipv6.conf.all.forwarding = 0 /etc/sysctl.conf lines 1-24/24 (END) and nothing in /etc/sysctl.d/ directory. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1135647] Missing ipv6 assignment with upgrade leap 15.0 to 15.1?
by bugzilla_noreply＠novell.com 02 Sep '19

02 Sep '19

http://bugzilla.suse.com/show_bug.cgi?id=1135647 http://bugzilla.suse.com/show_bug.cgi?id=1135647#c28 --- Comment #28 from andreas bittner <abittner(a)opensuse.org> --- I noticed this bug from July 2019: https://bugzilla.opensuse.org/show_bug.cgi?id=1138365 named Bug 1138365 - No ipv6 address when masquerade enable maybe a hinto into the same direction? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1135647] Missing ipv6 assignment with upgrade leap 15.0 to 15.1?
by bugzilla_noreply＠novell.com 02 Sep '19

02 Sep '19

http://bugzilla.suse.com/show_bug.cgi?id=1135647 http://bugzilla.suse.com/show_bug.cgi?id=1135647#c27 --- Comment #27 from andreas bittner <abittner(a)opensuse.org> --- and I do NEED ipv4 forwarding (NAT translation) to from its secondary networking interface, and I (currently) only need ipv6 functionality on its main ethernet interface where it is connected to the outside network. this worked perfectly fine in the past opensuse leap and before versions. I was able to happily nat/ipv4 route to/from multiple ethernet interfaces regardless of ipv6 functionality. these two stacks and protocols didnt interfere with another. seemingly there is something seriously wrong here that an ipv4 routing/nating functionality would hinder or completely disable ipv6 simple public unicast ipv6 assignment by RA via the provider/upstream router etc. why? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1135647] Missing ipv6 assignment with upgrade leap 15.0 to 15.1?
by bugzilla_noreply＠novell.com 02 Sep '19

02 Sep '19

http://bugzilla.suse.com/show_bug.cgi?id=1135647 http://bugzilla.suse.com/show_bug.cgi?id=1135647#c26 --- Comment #26 from andreas bittner <abittner(a)opensuse.org> --- Just make it it clear, I am not completely stupid ;) I am NOT using/setting forwarding for IPV6 of course. I just checked, on the machine, that doesnt get public ipv6 assigned (since the upgade to leap 15.1). yast2 network routing settings, shows those two checkboxes. this machine DOES act as an ipv4 NAT router, but is only acting as an ipv6 normal client/participant in an dual stacked ipv4/ipv6 network from an xdsl provider. I did have working proper ipv4 nated network on the second interface of this machine and properly working ipv6 to/from this machine and to the global ipv6 unicast internet. Since the upgrade to leap 15.1 this machine doesnt have public ipv6 unicast addresses assigned any more. currently it has: ip -c add 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 40:61:86:00:bd:01 brd ff:ff:ff:ff:ff:ff inet 192.168.15.254/24 brd 192.168.15.255 scope global eth0 valid_lft forever preferred_lft forever inet6 fe80::4261:86ff:fe00:bd01/64 scope link valid_lft forever preferred_lft forever 3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 60:a4:4c:44:4f:10 brd ff:ff:ff:ff:ff:ff inet 192.168.178.21/24 brd 192.168.178.255 scope global eth1 valid_lft forever preferred_lft forever inet6 fe80::62a4:4cff:fe44:4f10/64 scope link valid_lft forever preferred_lft forever ip route show default via 192.168.178.1 dev eth1 proto dhcp 192.168.15.0/24 dev eth0 proto kernel scope link src 192.168.15.254 192.168.178.0/24 dev eth1 proto kernel scope link src 192.168.178.21 ip -6 route show fe80::/64 dev eth1 proto kernel metric 256 pref medium fe80::/64 dev eth0 proto kernel metric 256 pref medium yast global options have the ipv6 enable ckeckbox activated. what now? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1149038] gpg2 freeze on verification of email
by bugzilla_noreply＠novell.com 02 Sep '19

02 Sep '19

http://bugzilla.suse.com/show_bug.cgi?id=1149038 http://bugzilla.suse.com/show_bug.cgi?id=1149038#c1 Matthias Gerstner <matthias.gerstner(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |matthias.gerstner(a)suse.com Assignee|security-team(a)suse.de |pmonrealgonzalez(a)suse.com --- Comment #1 from Matthias Gerstner <matthias.gerstner(a)suse.com> --- I tried the reproducer but nothing happens for me so maybe some ingredient is missing. The issue may be related to CVE-2019-13050 and the fix for it. Is the traceback in comment 0 from PID 31491 or from the `gpg2 --verify` process running the foreground? I'm assigning the bug to the gpg2 maintainer for further investigation. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1144060] Please add "pam_keyinit.so" to the /etc/pam.d/... configuration file(s)
by bugzilla_noreply＠novell.com 02 Sep '19

02 Sep '19

http://bugzilla.suse.com/show_bug.cgi?id=1144060 http://bugzilla.suse.com/show_bug.cgi?id=1144060#c3 --- Comment #3 from Michael Vetter <mvetter(a)suse.com> --- I assume there is not yet a way to test this, right? I created SR#727741 maybe you can take a look at it before I accept it to the devel repo. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1143125] systemd-vconsole-setup.service succeeds and fails several times on each boot
by bugzilla_noreply＠novell.com 02 Sep '19

02 Sep '19

http://bugzilla.suse.com/show_bug.cgi?id=1143125 http://bugzilla.suse.com/show_bug.cgi?id=1143125#c23 --- Comment #23 from Martin Liška <martin.liska(a)suse.com> --- (In reply to Andreas Schwab from comment #22) > Probably missing GNU_STACK header. No, that's not the case: i586:/home/marxin # readelf -l -W /usr/bin/gzip | grep GNU_STACK GNU_STACK 0x000000 0x00000000 0x00000000 0x00000 0x00000 RW 0x10 i586:/home/marxin # readelf -l -W /lib/libc.so.6 | grep GNU_STACK GNU_STACK 0x000000 0x00000000 0x00000000 0x00000 0x00000 RW 0x10 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1144060] Please add "pam_keyinit.so" to the /etc/pam.d/... configuration file(s)
by bugzilla_noreply＠novell.com 02 Sep '19

02 Sep '19

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

1 0