openSUSE Bugs December 2019

bugs@lists.opensuse.org

1 participants
3702 discussions

[Bug 1138135] New: gui version of yast's automatic update configuration fails to change anything
by bugzilla_noreply＠novell.com 10 Jan '23

10 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1138135 Bug ID: 1138135 Summary: gui version of yast's automatic update configuration fails to change anything Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: dpbasti(a)wp.pl QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- I enter the automatic update configuration from gui and enable it. I click on OK - it closes as if everything was fine. I enter the automatic update configuration again and I see it is disabled - so all my changes were disregarded So I switch to console yast. I enable auto update in the config - click ok and now i get prompted to trust pgp keys for certain repos. After having dont that and and reruning the console yast auto update config again I see that now the changes persisted. I now tried to lunch gui version and it also shows auto update as enabled. I tired to disable this feature in gui to check if gui yast can do it. It failed t apply changes again. COnclusion: FOr some reason gui yast auto update config fails to save that the feature is enabled or disabled. -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1104571] New: 3g 4g modem connects but no traffic possible
by bugzilla_noreply＠novell.com 10 Jan '23

10 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1104571 Bug ID: 1104571 Summary: 3g 4g modem connects but no traffic possible Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: dpbasti(a)wp.pl QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hi I have a dual boot Opensuse Leap15/Ubuntu 18.04 system on HP G2 laptop with 4g modem. In ubuntu all works fine In opensuse I added the connection in KDE - all default options -my carrier was listed. The modem get's connected - receives default route, IP assignment, DNS but for some reason no data is being sent/received - not even a simple ping 8.8.8.8 works here are the params ip addr show 5: wwan0: <BROADCAST,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000 link/ether 7a:c6:53:8c:bf:03 brd ff:ff:ff:ff:ff:ff inet 100.101.44.242/30 brd 100.101.44.243 scope global noprefixroute wwan0 valid_lft forever preferred_lft forever ip route show default via 100.101.44.241 dev wwan0 proto static metric 20700 100.101.44.240/30 dev wwan0 proto kernel scope link src 100.101.44.242 metric 700 and also the logs of netowork manager sie 11 07:37:55 laprus NetworkManager[1843]: <info> [1533965875.2045] device (cdc-wdm0): Activation: starting connection 'Play Online' (f77e62a8-66e0-4f34-b70e-f54a907a0630) sie 11 07:37:55 laprus NetworkManager[1843]: <info> [1533965875.2046] audit: op="connection-activate" uuid="f77e62a8-66e0-4f34-b70e-f54a907a0630" name="Play Online" pid=3812 uid=1000 result="success" sie 11 07:37:55 laprus NetworkManager[1843]: <info> [1533965875.2047] device (cdc-wdm0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') sie 11 07:37:55 laprus NetworkManager[1843]: <info> [1533965875.2048] manager: NetworkManager state is now CONNECTING sie 11 07:37:55 laprus ModemManager[1580]: <info> Simple connect started... sie 11 07:37:55 laprus ModemManager[1580]: <info> Simple connect state (4/8): Wait to get fully enabled sie 11 07:37:55 laprus ModemManager[1580]: <info> Simple connect state (5/8): Register sie 11 07:37:55 laprus ModemManager[1580]: <info> Simple connect state (6/8): Bearer sie 11 07:37:55 laprus ModemManager[1580]: <info> Simple connect state (7/8): Connect sie 11 07:37:55 laprus ModemManager[1580]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> connecting) sie 11 07:37:55 laprus NetworkManager[1843]: <info> [1533965875.2087] modem["cdc-wdm0"]: modem state changed, 'registered' --> 'connecting' (reason: user-requested) sie 11 07:37:55 laprus kdeinit5[3768]: networkmanager-qt: virtual void NetworkManager::ActiveConnectionPrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "StateFlags" sie 11 07:37:55 laprus plasmashell[3812]: networkmanager-qt: virtual void NetworkManager::ActiveConnectionPrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "StateFlags" sie 11 07:37:55 laprus kdeinit5[3768]: plasma-nm: Unhandled active connection state change: 1 sie 11 07:37:55 laprus plasmashell[3812]: plasma-nm: Item "Play Online" : active connection state changed to 1 sie 11 07:37:55 laprus plasmashell[3812]: plasma-nm: NetworkManager state changed to 4 sie 11 07:37:55 laprus plasmashell[3812]: plasma-nm: Item "Play Online" : active connection changed to 1 sie 11 07:37:55 laprus ModemManager[1580]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> connected) sie 11 07:37:55 laprus ModemManager[1580]: <info> Simple connect state (8/8): All done sie 11 07:37:55 laprus NetworkManager[1843]: <info> [1533965875.3919] modem["cdc-wdm0"]: modem state changed, 'connecting' --> 'connected' (reason: user-requested) sie 11 07:37:55 laprus NetworkManager[1843]: <info> [1533965875.3936] device (cdc-wdm0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') sie 11 07:37:55 laprus NetworkManager[1843]: <info> [1533965875.3939] device (cdc-wdm0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed') sie 11 07:37:55 laprus NetworkManager[1843]: <info> [1533965875.3942] modem-broadband[cdc-wdm0]: IPv4 static configuration: sie 11 07:37:55 laprus NetworkManager[1843]: <info> [1533965875.3943] modem-broadband[cdc-wdm0]: address 100.101.44.242/30 sie 11 07:37:55 laprus NetworkManager[1843]: <info> [1533965875.3943] modem-broadband[cdc-wdm0]: gateway 100.101.44.241 sie 11 07:37:55 laprus avahi-daemon[1565]: Joining mDNS multicast group on interface wwan0.IPv4 with address 100.101.44.242. sie 11 07:37:55 laprus NetworkManager[1843]: <info> [1533965875.3943] modem-broadband[cdc-wdm0]: DNS 185.89.185.2 sie 11 07:37:55 laprus avahi-daemon[1565]: New relevant interface wwan0.IPv4 for mDNS. sie 11 07:37:55 laprus NetworkManager[1843]: <info> [1533965875.3943] modem-broadband[cdc-wdm0]: DNS 89.108.202.21 sie 11 07:37:55 laprus avahi-daemon[1565]: Registering new address record for 100.101.44.242 on wwan0.IPv4. sie 11 07:37:55 laprus kdeinit5[3768]: networkmanager-qt: virtual void NetworkManager::ActiveConnectionPrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "StateFlags" sie 11 07:37:55 laprus avahi-daemon[1565]: Joining mDNS multicast group on interface wwan0.IPv6 with address fe80::16b5:7d4d:10ab:f6ae. sie 11 07:37:55 laprus NetworkManager[1843]: <info> [1533965875.3956] device (cdc-wdm0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed') sie 11 07:37:55 laprus avahi-daemon[1565]: New relevant interface wwan0.IPv6 for mDNS. sie 11 07:37:55 laprus avahi-daemon[1565]: Registering new address record for fe80::16b5:7d4d:10ab:f6ae on wwan0.*. sie 11 07:37:55 laprus kdeinit5[3768]: networkmanager-qt: virtual void NetworkManager::ActiveConnectionPrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "StateFlags" sie 11 07:37:55 laprus NetworkManager[1843]: <info> [1533965875.3970] device (cdc-wdm0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed') sie 11 07:37:55 laprus NetworkManager[1843]: <info> [1533965875.3971] device (cdc-wdm0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed') sie 11 07:37:55 laprus NetworkManager[1843]: <info> [1533965875.3972] manager: NetworkManager state is now CONNECTED_LOCAL sie 11 07:37:55 laprus NetworkManager[1843]: <info> [1533965875.4262] manager: NetworkManager state is now CONNECTED_SITE sie 11 07:37:55 laprus NetworkManager[1843]: <info> [1533965875.4263] policy: set 'Play Online' (wwan0) as default for IPv4 routing and DNS sie 11 07:37:55 laprus nscd[1604]: 1604 monitored file `/etc/resolv.conf` was written to sie 11 07:37:55 laprus plasmashell[3812]: networkmanager-qt: virtual void NetworkManager::ActiveConnectionPrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "StateFlags" sie 11 07:37:55 laprus plasmashell[3812]: networkmanager-qt: virtual void NetworkManager::ActiveConnectionPrivate::propertyChanged(const QString&, const QVariant&) Unhandled property "StateFlags" sie 11 07:37:55 laprus NetworkManager[1843]: nisdomainname: you must be root to change the domain name sie 11 07:37:55 laprus NetworkManager[1843]: <info> [1533965875.5272] device (cdc-wdm0): Activation: successful, device activated. -- You are receiving this mail because: You are on the CC list for the bug.

2 5

[Bug 1114273] New: Broadband connection established but all packages dropped
by bugzilla_noreply＠novell.com 10 Jan '23

10 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1114273 Bug ID: 1114273 Summary: Broadband connection established but all packages dropped Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: dpbasti(a)wp.pl QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I tested https://bugzilla.opensuse.org/show_bug.cgi?id=1104571 on 2018.10.31 Tumbleweeed. The same result as on Leap15. All RX and all TX packages are dropped Connection is established, signal strength is good, IP is obtained, Routing is set to default gw received from 4g modem, DNS servers are also received. Cannot even ping gateway. The same setup works as soon as I boot Ubuntu with no different settings in NetworkManager. wwan0: flags=4291<UP,BROADCAST,RUNNING,NOARP,MULTICAST> mtu 1500 inet 10.111.71.20 netmask 255.255.255.248 broadcast 10.111.71.23 inet6 fe80::73fb:926a:b538:f135 prefixlen 64 scopeid 0x20<link> ether 7a:c6:53:8c:bf:03 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 1280 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 42 dropped 0 overruns 0 carrier 0 collisions 0 -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1123557] New: network:vpn/openvpn: Bug --suppress-timestamps unneeded in systemd unit file?
by bugzilla_noreply＠novell.com 09 Jan '23

09 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1123557 Bug ID: 1123557 Summary: network:vpn/openvpn: Bug --suppress-timestamps unneeded in systemd unit file? Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: 3rd party software Assignee: max(a)suse.com Reporter: jon.brightwell(a)zpg.co.uk QA Contact: bnc-team-screening(a)forge.provo.novell.com CC: nirmoy.das(a)suse.com Found By: --- Blocker: --- It makes logging hard (no timestamps!) and doesn't seem to affect journalctl. I changed mine to ExecStart=/usr/sbin/openvpn --daemon --writepid /run/openvpn/%i.pid --cd /etc/openvpn/ --config %i.conf Does it also need a wait so it doesn't spit of these openvpn(a)lab.service: PID file /run/openvpn/lab.pid not readable (yet?) after start: No such file or directory -- You are receiving this mail because: You are on the CC list for the bug.

2 1

[Bug 1052765] New: net-snmp still use SysVinit boot scripts
by bugzilla_noreply＠novell.com 06 Jan '23

06 Jan '23

http://bugzilla.suse.com/show_bug.cgi?id=1052765 Bug ID: 1052765 Summary: net-snmp still use SysVinit boot scripts Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: All OS: openSUSE Factory Status: NEW Severity: Critical Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: werner(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Please port the boot script AFAP to systemd units: rpm -ql net-snmp | grep init\\.d /etc/init.d/snmpd /etc/init.d/snmptrapd this because as net-snmp will also reach SLES15 -- You are receiving this mail because: You are on the CC list for the bug.

2 4

[Bug 1133423] New: AutoYaST: repository priority not working in add-on section
by bugzilla_noreply＠novell.com 04 Jan '23

04 Jan '23

http://bugzilla.suse.com/show_bug.cgi?id=1133423 Bug ID: 1133423 Summary: AutoYaST: repository priority not working in add-on section Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers(a)suse.de Reporter: apoulat(a)vitechnology.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 803606 --> http://bugzilla.suse.com/attachment.cgi?id=803606&action=edit add-on.xml Hi, I've just seen that, for example with attached add-on.xml given to AutoYaST, with, as you can see one repository with priority 20 and another with priority 10, they both, after install, have a (default) 99 priority (checked with "zypper -lr -p" command). See documentation about that here: https://doc.opensuse.org/projects/autoyast/#idm139966593990112 Note: I'm not sure on how <product> and <product_dir> tags are relevant then I tried without them and there is still the same issue. Thanks -- You are receiving this mail because: You are on the CC list for the bug.

2 7

[Bug 1029961] New: [META] Finalize /bin -> /usr/bin merge
by bugzilla_noreply＠novell.com 03 Jan '23

03 Jan '23

http://bugzilla.opensuse.org/show_bug.cgi?id=1029961 Bug ID: 1029961 Summary: [META] Finalize /bin -> /usr/bin merge Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: daniel.molkentin(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Some packages still install files to /bin that are not symlinks. A "find /bin -type f -exec rpm -qf {} \; | sort -u" on a recent TW yields: bash-4.4-95.1.x86_64 dbus-1-1.10.16-1.1.x86_64 keyutils-1.5.9-5.33.x86_64 ksh-93v-6.15.x86_64 net-tools-deprecated-1.60-770.1.x86_64 procps-3.3.12-3.1.x86_64 psmisc-22.21-6.9.x86_64 rpm-4.13.0.1-1.1.x86_64 sash-3.8-2.8.x86_64 sysvinit-tools-2.88+-103.1.x86_64 tar-1.29-3.1.x86_64 tcsh-6.20.00-3.1.x86_64 util-linux-2.29.1-1.1.x86_64 vim-8.0.324-2.1.x86_64 These packages should all install their binaries to %_bindir, i.e. /usr/bin, and have a symlink in /bin. This would finalize the /bin deprecation. I am opening bugs for each of the packages. Once they are all closed, I'll close this one. -- You are receiving this mail because: You are on the CC list for the bug.

2 67

[Bug 1106751] New: iptables does not work with kernel-default-base
by bugzilla_noreply＠novell.com 23 Dec '22

23 Dec '22

http://bugzilla.suse.com/show_bug.cgi?id=1106751 Bug ID: 1106751 Summary: iptables does not work with kernel-default-base 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: fvogt(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Initially reported as https://github.com/kubic-project/automation/pull/474#issuecomment-417329301 Docker (and cri-o) do not work in Kubic VM images as iptables does not work: g47:~ # iptables -L iptables: No chain/target/match by that name. -- You are receiving this mail because: You are on the CC list for the bug.

2 49

[Bug 944832] New: installing updates during shutdown causes reboot
by bugzilla_noreply＠novell.com 22 Dec '22

22 Dec '22

http://bugzilla.suse.com/show_bug.cgi?id=944832 Bug ID: 944832 Summary: installing updates during shutdown causes reboot Classification: openSUSE Product: openSUSE Distribution Version: 42.1 Milestone 2 Hardware: x86-64 OS: Linux Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: ohering(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- fresh leap milestone 2. I switched from the iso install source to the online oss repo. This repo had a few differend packages compared to the iso. The gnome software installer recognized them as updates. Once I had to shutdown the system it offered a knob to install pending updates, then shutdown. I enabled that box, and hit return. I think nothing was downloaded, but the box did a reboot instead of the expected shutdown. If that feature is not ready yet I suggest to hide it for the time being to really and always do a reliable powerdown if that was requested. -- You are receiving this mail because: You are on the CC list for the bug.

2 8

[Bug 1093592] New: redshift doesn't work after geoclue2 update
by bugzilla_noreply＠novell.com 16 Dec '22

16 Dec '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1093592 Bug ID: 1093592 Summary: redshift doesn't work after geoclue2 update Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: dmarcoux(a)posteo.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 770512 --> http://bugzilla.opensuse.org/attachment.cgi?id=770512&action=edit redshift error Hello, I updated to the latest snapshot (2018 05 15) and since then, redshift with geoclue2 doesn't work. After launching, it displays an error (see attachment). This wasn't happening with the previous snapshot I had, but I'm not sure which one. The issue seems to arise due to changes within the recent revisions of the geoclue2 package, so as far as 2 months ago. So by looking at the snapshots, I suspect it is in one of those: - 2018 03 04 - 2018 04 24 - 2018 05 11 - 2018 05 13 The workaround is to provide the latitude and longitude manually with the option -l. -- You are receiving this mail because: You are on the CC list for the bug.

2 9

← Newer
1
...
4
5
6
7
8
9
10
...
371
Older →

Jump to page:

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Bugs December 2019