openSUSE Bugs June 2019

bugs@lists.opensuse.org

1 participants
3858 discussions

[Bug 1130448] cannot suspend while BT audio device is connected
by bugzilla_noreply＠novell.com 02 Jun '19

02 Jun '19

http://bugzilla.suse.com/show_bug.cgi?id=1130448 http://bugzilla.suse.com/show_bug.cgi?id=1130448#c39 --- Comment #39 from Michal Suchanek <msuchanek(a)suse.com> --- Created attachment 806598 --> http://bugzilla.suse.com/attachment.cgi?id=806598&action=edit btsnoop of wakeup on poweroff btsnoop of systam waking up after device is powered off -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1136295] yast2-control-center-qt3 No icons in yast2 or sw_single
by bugzilla_noreply＠novell.com 02 Jun '19

02 Jun '19

http://bugzilla.suse.com/show_bug.cgi?id=1136295 http://bugzilla.suse.com/show_bug.cgi?id=1136295#c4 --- Comment #4 from David Rankin <drankinatty(a)suddenlinkmail.com> --- In addition to updating the Makefile.am, we will also need to update the icon search (png|jpg) to 'svg' since yast2-theme is now installing "sclaleable" svg icons instead of .png. So for instance in yastmodules.cpp:251 there will need to be an update to QRegExp extension( "\\.(png|jpg)$", false ); >From my search, the list of changes will need to be: grep -n png * Makefile.am:20:self_icon_DATA=yast.png Makefile.in:263:self_icon_DATA = yast.png y2controlcenter.cpp:43: QString iconName( ICON_DIR "/yast.png" ); y2controlcenterview.cpp:63: // show titlebar only if title-bar-gradient.png exists y2controlcenterview.cpp:64: if ( !QPixmap( PIXMAP_DIR "/title-bar-gradient.png" ).isNull() ) y2controlcenterview.cpp:206: QPixmap titleBarGradientPixmap = QPixmap( PIXMAP_DIR "/title-bar-gradient.png" ); y2controlcenterview.cpp:220: QPixmap leftLogo( PIXMAP_DIR "/title-bar-left.png" ); y2controlcenterview.cpp:246: QPixmap rightLogo( PIXMAP_DIR "/title-bar-right.png" ); yastmodules.cpp:55:#define DEFAULT_GROUP_ICON "yast-default-group.png" yastmodules.cpp:251: QRegExp extension( "\\.(png|jpg)$", false ); // case insensitive yastmodules.cpp:253: if ( icon.find( extension ) < 0 ) // no .png or .jpg extension? yastmodules.cpp:254: icon += ".png"; // assume .png yastmodules.cpp:326: QRegExp extension( "\\.(png|jpg)$", false ); // case insensitive yastmodules.cpp:328: if ( icon.find( extension ) < 0 ) // no .png or .jpg extension? yastmodules.cpp:329: icon += ".png"; // assume .png yastmodules.cpp:540: iconfilename = "default.png"; The y2controlcenterview.cpp files are likely not icon related but I am not for sure. I can build yast2-control-center-qt3 locally, but buildservice fails with "unresolvable" errors because it can't find qt3-devel at http://download.opensuse.org/repositories/KDE:/KDE3/openSUSE_Leap_15.1/x86_…. I think we are close. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1136295] yast2-control-center-qt3 No icons in yast2 or sw_single
by bugzilla_noreply＠novell.com 02 Jun '19

02 Jun '19

http://bugzilla.suse.com/show_bug.cgi?id=1136295 http://bugzilla.suse.com/show_bug.cgi?id=1136295#c3 --- Comment #3 from David Rankin <drankinatty(a)suddenlinkmail.com> --- If I'm looking at this correctly, then the changes needed are only to the -DICON_DIR define in Makefile.am and Makefile.in, e.g. within the src directory of yast2-control-center-2.17.3.tar.bz2 you have $ grep -n '32x32' * Makefile.am:6: -DICON_DIR=\"${themedir}/current/icons/32x32/apps\" \ Makefile.in:252: -DICON_DIR=\"${themedir}/current/icons/32x32/apps\" \ Where '32x32` needs to be changed to "scaleable". The list 'yast2-theme' as a dependency and it looks like that would solve the problem. I'll try a rebuild with those files patched and report further, but that looks like the problem. Would be nice to be a simple Makefile issue and a missing link. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1137060] New: Can not run podman as non-root: Could not get runtime: could not find a working conmon binary
by bugzilla_noreply＠novell.com 02 Jun '19

02 Jun '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1137060 Bug ID: 1137060 Summary: Can not run podman as non-root: Could not get runtime: could not find a working conmon binary Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Containers Assignee: containers-bugowner(a)suse.de Reporter: tbechtold(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When trying to run podman as normal user (after adding entries to /etc/subuid - see https://bugzilla.opensuse.org/show_bug.cgi?id=1137059 ), I get XXX@t440p-laptop:~> podman images Could not get runtime: could not find a working conmon binary (configured options: [/usr/libexec/podman/conmon /usr/libexec/crio/conmon /usr/local/lib/podman/conmon /usr/local/libexec/crio/conmon /usr/bin/conmon /usr/sbin/conmon /usr/lib/crio/bin/conmon]): invalid argument Doing the same as root works: XXX@t440p-laptop:~> sudo podman images REPOSITORY TAG IMAGE ID CREATED SIZE ... ... -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1137056] Automatically add a custom generated key to initrd when installing to LVM/LUKS
by bugzilla_noreply＠novell.com 02 Jun '19

02 Jun '19

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

1 0

[Bug 1108977] Tracker bug for known incompatibilities with OpenSSL 1.1.1
by bugzilla_noreply＠novell.com 01 Jun '19

01 Jun '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1108977 Bug 1108977 depends on bug 1135550, which changed state. Bug 1135550 Summary: Programs using libopenssl crash under Russian/Ukrainian locales since the update to OpenSSL 1.1.1b http://bugzilla.opensuse.org/show_bug.cgi?id=1135550 What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1135550] New: After last update (kernel 5.1.2-1) several program get segmentation fault error
by bugzilla_noreply＠novell.com 01 Jun '19

01 Jun '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1135550 Bug ID: 1135550 Summary: After last update (kernel 5.1.2-1) several program get segmentation fault error 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: virex(a)mail.ru QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- After last update (kernel 5.1.2-1) several program get segmentation fault error for example mc deadbeef soundconverter qmmp -- You are receiving this mail because: You are on the CC list for the bug.

1 50

[Bug 1137055] New: Build20190529: wine-32bit uninstallable, version 4.9-1.15 was not published?
by bugzilla_noreply＠novell.com 01 Jun '19

01 Jun '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1137055 Bug ID: 1137055 Summary: Build20190529: wine-32bit uninstallable, version 4.9-1.15 was not published? Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: okurz(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- ## Observation As reported in https://lists.opensuse.org/opensuse-factory/2019-06/msg00005.html https://download.opensuse.org/tumbleweed/repo/oss/x86_64/?P=wine* looks incomplete indeed with wine-4.8-1.1.x86_64.rpm 14-May-2019 13:03 wine-4.9-1.15.x86_64.rpm 30-May-2019 12:38 wine-32bit-4.8-1.1.x86_64.rpm 14-May-2019 12:41 I am not sure how I should read https://build.opensuse.org/package/show/openSUSE:Factory/wine but at least https://build.opensuse.org/package/live_build_log/openSUSE:Factory/wine/sta… shows that RPMS/x86_64/wine-32bit-4.9-1.15.x86_64.rpm is correctly generated but was not published as part of the past two snapshots 20190527 or 20190529 it seems. ## Reproducible yes ``` docker run -it --rm opensuse/tumbleweed 'zypper -n in wine wine-32bit' ``` yields ``` Problem: nothing provides wine-32bit = 4.9 needed by wine-4.9-1.15.x86_64 Solution 1: do not install wine-4.9-1.15.x86_64 Solution 2: break wine-4.9-1.15.x86_64 by ignoring some of its dependencies ``` -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1137054] New: Python Appindicator segfaults on Tumbleweed - fine on Leap
by bugzilla_noreply＠novell.com 01 Jun '19

01 Jun '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1137054 Bug ID: 1137054 Summary: Python Appindicator segfaults on Tumbleweed - fine on Leap Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: richard.eigenmann(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Have been experimenting with system tray icons and came across a very simple Python example how to use them. It worked fine on my openSUSE Leap desktop and segfaults on my Tumbleweed laptop. Both fully updated as of today (1 June 2019). Here is the Python code that puts an avatar in the system tray with a menu item to open up a zenity info dialog with your user name or shut down the script: #!/usr/bin/python3 # Inspiration: https://fosspost.org/tutorials/custom-system-tray-icon-indicator-linux # Install: sudo zypper in typelib-1_0-AppIndicator3-0_1 # Install: sudo zypper in zenity import os import gi gi.require_version('Gtk', '3.0') gi.require_version('AppIndicator3', '0.1') from gi.repository import Gtk as gtk, AppIndicator3 as appindicator def main(): indicator = appindicator.Indicator.new("systrayExperiment", "avatar-default-symbolic", appindicator.IndicatorCategory.APPLICATION_STATUS) indicator.set_status(appindicator.IndicatorStatus.ACTIVE) indicator.set_menu(menu()) indicator.set_title("Cute Systray Experiment") gtk.main() def menu(): menu = gtk.Menu() command_hello = gtk.MenuItem('Say Hello') command_hello.connect('activate', hello) menu.append(command_hello) exittray = gtk.MenuItem('Exit Tray') exittray.connect('activate', quit) menu.append(exittray) menu.show_all() return menu def hello(_): os.system("/usr/bin/zenity --info --text \"Hello, $(whoami)!\"") def quit(_): gtk.main_quit() if __name__ == "__main__": main() Output from Tumbleweed: me@laptop:~> ./minimalAppIndicator.py (process:3049): Gtk-CRITICAL **: 16:37:30.781: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed ./minimalAppIndicator.py:14: Warning: invalid (NULL) pointer instance indicator = appindicator.Indicator.new("systrayExperiment", "avatar-default-symbolic", appindicator.IndicatorCategory.APPLICATION_STATUS) ./minimalAppIndicator.py:14: Warning: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed indicator = appindicator.Indicator.new("systrayExperiment", "avatar-default-symbolic", appindicator.IndicatorCategory.APPLICATION_STATUS) (process:3049): Gtk-CRITICAL **: 16:37:30.784: _gtk_style_provider_private_get_settings: assertion 'GTK_IS_STYLE_PROVIDER_PRIVATE (provider)' failed (process:3049): Gtk-CRITICAL **: 16:37:30.784: _gtk_style_provider_private_get_settings: assertion 'GTK_IS_STYLE_PROVIDER_PRIVATE (provider)' failed (process:3049): Gtk-CRITICAL **: 16:37:30.784: _gtk_style_provider_private_get_settings: assertion 'GTK_IS_STYLE_PROVIDER_PRIVATE (provider)' failed Segmentation fault (core dumped) -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1136436] New: btrfs mainainance crashed and left system unbootable
by bugzilla_noreply＠novell.com 01 Jun '19

01 Jun '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1136436 Bug ID: 1136436 Summary: btrfs mainainance crashed and left system unbootable 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: P.Suetterlin(a)royac.iac.es QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Last night my Tumbleweed system (20190520) performed the regular btrfs maintainance. I was working at that time, and noticed that the application I used did not respond anymore. Other stuff seemed to continue working (e.g., bringing an editor window in front). So I thought its the application and tried to terminate it, but nothing happened. Short after that everything on the screen became unresponsive, keyboard LEDS didn't react on state change etc. I finally pressed the power button to restart the system (laptop, no reset). However, the boot did not succeed. It hang, systemd reporting its waiting for four processes. Two of those were 'flush journal to persistent memory' and 'save rfkill switch state'. For some time the console display showed those jobs in a loop, then it would also stop and become unresponsive. This was consistent, I tried some three times or so. So I finally booted from an USB rescue stick. I could mount the FS without problems. Not knowing better, I ran a 'btrfs scrub' on it, which finished after some 1-2 minutes without errors. Not sure what to do next, I rebooted from the hard disk - and the system came up clean. By now I assume the crashes/hangs were only temporary(?) and the system might have returned after longer waits, but I'm not absolutely sure. However, looking at the logfile from the first hang I found some issue where balancing failed with a 'no space left on device (although it has/had 5.6G free when starting). More alarming was this one: May 27 00:02:10 woodstock.pitnet btrfs-balance.sh[17806]: Done, had to relocate 1 out of 84 chunks May 27 00:02:10 woodstock.pitnet kernel: BTRFS info (device sda2): balance: start -musage=10 -susage=10 May 27 00:02:10 woodstock.pitnet kernel: BTRFS info (device sda2): relocating block group 398848950272 flags system May 27 00:02:10 woodstock.pitnet kernel: BTRFS info (device sda2): relocating block group 398815395840 flags metadata May 27 00:02:10 woodstock.pitnet kernel: assertion failed: root, file: fs/btrfs/relocation.c, line: 804 May 27 00:02:10 woodstock.pitnet kernel: ------------[ cut here ]------------ May 27 00:02:10 woodstock.pitnet kernel: kernel BUG at fs/btrfs/ctree.h:3518! Unfortunately the log ends with this line, so no more info. The full system log starting with the btrfs maintainance call is available at http://paste.opensuse.org/24906643 (1 month lifetime - should I rather attach it?) -- You are receiving this mail because: You are on the CC list for the bug.

1 2

Jump to page:

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openSUSE Bugs June 2019