October 2019 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1149511] New: "zypper --releasever" does not work
by bugzilla_noreply＠novell.com 07 Oct '19

07 Oct '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1149511 Bug ID: 1149511 Summary: "zypper --releasever" does not work Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: All OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: libzypp Assignee: zypp-maintainers(a)suse.de Reporter: tonysu(a)su-networking.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Applies to zypper running in at least LEAP 42.3. 15.0 and 15.1, likely all versions of openSUSE Example which should work zypper --releasever 15.1 --gpg-auto-import-keys ref The above command according to the zypper MAN page is supposed to set all enabled repositories to the given release version, in the above example "15.1" The actual result is that nothing is changed, the repo.d file data remains exactly as before. A related minor issue is that even should the URLs be modified, the MAN page and Help do that say whether the labels are also modified or not. If not, then the URL would point to the new version while the name would say it still belonged to the previous version. -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1148128] New: xfce4-power-manager doesn't lock screen on laptop lid close with xlock
by bugzilla_noreply＠novell.com 07 Oct '19

07 Oct '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1148128 Bug ID: 1148128 Summary: xfce4-power-manager doesn't lock screen on laptop lid close with xlock Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Xfce Assignee: bnc-team-xfce(a)forge.provo.novell.com Reporter: ginkobonsai(a)gmx.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I like to use i3lock instead of xscreensaver, so I removed xscreensaver from my TW 20190822 and installed i3lock and i3lock-xlock-compat. I also set xfce's LockCommand to /usr/bin/xlock in order to use it: xfconf-query -c xfce4-session -p /general/LockCommand -s "/usr/bin/xlock" --create -t string Now the xfce action buttons lock my screen perfectly fine, but closing my laptop's lid does nothing. Laptop lid actions set in the Power Manager settings are "Lock screen" for both battery and plugged in. Running the power manager in debug mode and opening/closing the lid twice produces this: xfce4-power-manager --no-daemon --debug > pm.log 2>&1 [...] TRACE[xfpm-power-common.c:189] get_device_icon_name(): icon_suffix -symbolic, icon_base_length 20, upower_icon battery-full-charged-symbolic TRACE[xfpm-manager.c:725] xfpm_manager_tray_update_icon(): updating icon TRACE[xfpm-manager.c:709] xfpm_manager_tray_update_tooltip(): updating tooltip TRACE[xfpm-manager.c:442] xfpm_manager_lid_changed_cb(): LID close event: ((XfpmLidTriggerAction) LID_TRIGGER_LOCK_SCREEN) TRACE[xfpm-manager.c:475] xfpm_manager_lid_changed_cb(): LID opened: ((XfpmLidTriggerAction) LID_TRIGGER_LOCK_SCREEN) TRACE[xfpm-dpms.c:279] xfpm_dpms_force_level(): start TRACE[xfpm-dpms.c:311] xfpm_dpms_force_level(): No need to change DPMS mode, current_level=0 requested_level=0 TRACE[xfpm-manager.c:442] xfpm_manager_lid_changed_cb(): LID close event: ((XfpmLidTriggerAction) LID_TRIGGER_LOCK_SCREEN) TRACE[xfpm-manager.c:475] xfpm_manager_lid_changed_cb(): LID opened: ((XfpmLidTriggerAction) LID_TRIGGER_LOCK_SCREEN) TRACE[xfpm-dpms.c:279] xfpm_dpms_force_level(): start TRACE[xfpm-dpms.c:311] xfpm_dpms_force_level(): No need to change DPMS mode, current_level=0 requested_level=0 [...] Running xfconf-query -c xfce4-power-manager -p /xfce4-power-manager/logind-handle-lid-switch gives: false Looks to me like xfce4-power-manager doesn't use /general/LockCommand? Is there a workaround to tell xfce4-power-manager to use xlock to lock the screen on laptop lid close? -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1123248] ACPI error
by bugzilla_noreply＠novell.com 07 Oct '19

07 Oct '19

http://bugzilla.suse.com/show_bug.cgi?id=1123248 Jean Delvare <jdelvare(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jdelvare(a)suse.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1153200] New: [Build 20191004] Hostname with dot is not displayed in qt version of yast2 network module
by bugzilla_noreply＠novell.com 07 Oct '19

07 Oct '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1153200 Bug ID: 1153200 Summary: [Build 20191004] Hostname with dot is not displayed in qt version of yast2 network module Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Minor Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: riafarov(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- Created attachment 820678 --> http://bugzilla.opensuse.org/attachment.cgi?id=820678&action=edit YaST logs ## Overview When having dot in the hostname, yast2 network shows error that such name is invalid. However in case of ncurses, this name is shown in the field and in case of X11, text field is empty, which might be confusing for the user. ## Steps to reproduce 1. Set hostname to something with dots in name, e.g. dot.dot (sudo hostnamectl set-hostname dot.dot) 2. Run yast2 network in ncurses - hostname is displayed, error is shown when trying to switch the tab or save the config 3. Run yast2 network with X11 - hostname is not diplayed, error is shown when trying to switch the tab or save the config Other part of the issue is that yast complains about dot even when it's FQDN, which is wrong. As we are calling `hostname --fqdn`, in such case dot is acceptable symbol. Please find logs and screenshots in the attachment. 2019-10-07 05:53:21 <1> susetest(5685) [Ruby] lib/cheetah.rb:158 Executing "/usr/bin/hostname --fqdn". 2019-10-07 05:53:21 <1> susetest(5685) [Ruby] lib/cheetah.rb:206 Standard output: susetest.default ... 2019-10-07 05:53:21 <1> susetest(5685) [Ruby] lib/cheetah.rb:158 Executing "/usr/bin/hostname --fqdn". 2019-10-07 05:53:21 <1> susetest(5685) [Ruby] lib/cheetah.rb:206 Standard output: susetest.default -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1121956] [BuildCycle] hamcrest, jmock
by bugzilla_noreply＠novell.com 07 Oct '19

07 Oct '19

http://bugzilla.suse.com/show_bug.cgi?id=1121956 http://bugzilla.suse.com/show_bug.cgi?id=1121956#c1 Fridrich Strba <fstrba(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #1 from Fridrich Strba <fstrba(a)suse.com> --- fixed -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1121958] [BuildCycle] java-cup, jflex, qdox
by bugzilla_noreply＠novell.com 07 Oct '19

07 Oct '19

http://bugzilla.suse.com/show_bug.cgi?id=1121958 http://bugzilla.suse.com/show_bug.cgi?id=1121958#c1 Fridrich Strba <fstrba(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #1 from Fridrich Strba <fstrba(a)suse.com> --- fixed -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1133135] LTO: java-1_8_0-openjdk build fails
by bugzilla_noreply＠novell.com 07 Oct '19

07 Oct '19

http://bugzilla.suse.com/show_bug.cgi?id=1133135 http://bugzilla.suse.com/show_bug.cgi?id=1133135#c9 Fridrich Strba <fstrba(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #9 from Fridrich Strba <fstrba(a)suse.com> --- Fixed -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1133084] [META] GCC + LTO package failures
by bugzilla_noreply＠novell.com 07 Oct '19

07 Oct '19

http://bugzilla.suse.com/show_bug.cgi?id=1133084 Bug 1133084 depends on bug 1133135, which changed state. Bug 1133135 Summary: LTO: java-1_8_0-openjdk build fails http://bugzilla.suse.com/show_bug.cgi?id=1133135 What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1143134] Can't install java-10-openjdk
by bugzilla_noreply＠novell.com 07 Oct '19

07 Oct '19

http://bugzilla.suse.com/show_bug.cgi?id=1143134 http://bugzilla.suse.com/show_bug.cgi?id=1143134#c1 Fridrich Strba <fstrba(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Fridrich Strba <fstrba(a)suse.com> --- Duplicate *** This bug has been marked as a duplicate of bug 1137382 *** -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1137382] java-11-openjdk obsoletes java-10-openjdk
by bugzilla_noreply＠novell.com 07 Oct '19

07 Oct '19

http://bugzilla.suse.com/show_bug.cgi?id=1137382 http://bugzilla.suse.com/show_bug.cgi?id=1137382#c4 Fridrich Strba <fstrba(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bnacht(a)web.de --- Comment #4 from Fridrich Strba <fstrba(a)suse.com> --- *** Bug 1143134 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