June 2019 - openSUSE Bugs - openSUSE Mailing Lists

[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#c6 --- Comment #6 from Stasiek Michalski <hellcp(a)mailbox.org> --- Eh, in case of qt5 control center, it doesn't use a set directory, instead relying on DE setting icon theme and using a native qt function (that exist since qt4) to set icon from icon theme. I have no idea how this should be solved for ycc-qt3, but there is probably a reason why it and qt3 are no longer supported ;) -- 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#c5 --- Comment #5 from David Rankin <drankinatty(a)suddenlinkmail.com> --- I believe I have found the bottom line and there are two-options. (1) restore the png icons from yast2-opensuse-branding available in 15.0 as part of yast-theme; or (2) write a .svg handler and renderer to Qimage in Qt3 so you can use QimageConvertTo to create a Qpixmap from the rendered Qimage. Why? QImageIO contains a QIODevice object that is used for image data I/O. The programmer can install new image file formats in addition to those that Qt provides. Qt currently supports the following image file formats: PNG, BMP, XBM, XPM and PNM. It may also support JPEG, MNG and GIF, if specially configured during compilation. The different PNM formats are: PBM (P1 or P4), PGM (P2 or P5), and PPM (P3 or P6). There is no native support for .svg images or icons in Qt3. I don't know how difficult option (1) is, but there are a number of svg handling Qt3 apps the .svg image read and render -- like scribus where the .svg code could be pulled. Or (2) simply include the yast .png icons along with the .svg images in the current yast2-theme package. (they are only a few 100k of size total, so the impact would be negligible and restore icons for yast2-control-center-qt3 without having to patch anything or add svg rendering code. You guys make the call. I already have yast2-control-center-qt3 building, so I'm happy to help and verify whatever way you want to go. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[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#c40 Michal Suchanek <msuchanek(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED |--- --- Comment #40 from Michal Suchanek <msuchanek(a)suse.com> --- This is not working entirely. When device is connected, system is suspended, and device is powered off the system wakes up. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1106082] New: a locked package is in the list of package to update
by bugzilla_noreply＠novell.com 02 Jun '19

02 Jun '19

http://bugzilla.opensuse.org/show_bug.cgi?id=1106082 Bug ID: 1106082 Summary: a locked package is in the list of package to update Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: epistemepromeneur(a)free.fr QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- for some purpose i lock a package with the software manager according to avoid any update then i ask to software update plasmoid to check if there is updates then in the list of the packages to update there is the locked package ! it must not be in this list. note: i checked that it is not updated when clicking "install update" -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[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