January 2021 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1179537] earlyoom pulls in heavy dependencies
by bugzilla_noreply＠suse.com 04 Jan '21

04 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1179537 https://bugzilla.suse.com/show_bug.cgi?id=1179537#c4 Mindaugas Baranauskas <opensuse.lietuviu.kalba(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #4 from Mindaugas Baranauskas <opensuse.lietuviu.kalba(a)gmail.com> --- accepted in factory: https://build.opensuse.org/request/show/860247 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1076613] audit error message
by bugzilla_noreply＠suse.com 04 Jan '21

04 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1076613 https://bugzilla.suse.com/show_bug.cgi?id=1076613#c10 Enzo Matsumiya <ematsumiya(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(freek(a)opensuse.or | |g) --- Comment #10 from Enzo Matsumiya <ematsumiya(a)suse.com> --- Is this still reproducible with the latest audit package in openSUSE? aarch64 build was specifically enabled only in the latest release. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1179974] New: Keepass doesn't start, mono error
by bugzilla_noreply＠suse.com 04 Jan '21

04 Jan '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1179974 Bug ID: 1179974 Summary: Keepass doesn't start, mono error Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.2 Hardware: x86-64 OS: openSUSE Leap 15.2 Status: NEW Severity: Major Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: adrian.fita(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Hello. Keepass fails to start. The following errors appear in terminal: adrian@10:~> keepass No protocol specified No protocol specified No protocol specified System.ArgumentException: A null reference or invalid value was found [GDI+ status: InvalidParameter] at System.Drawing.GDIPlus.CheckStatus (System.Drawing.Status status) [0x00098] in <ecd2d61b095b49809f8ad64ab2df023e>:0 at System.Drawing.Bitmap..ctor (System.Int32 width, System.Int32 height, System.Drawing.Imaging.PixelFormat format) [0x00016] in <ecd2d61b095b49809f8ad64ab2df023e>:0 at System.Drawing.Bitmap..ctor (System.Drawing.Image original, System.Int32 width, System.Int32 height) [0x00000] in <ecd2d61b095b49809f8ad64ab2df023e>:0 at System.Drawing.Bitmap..ctor (System.Drawing.Image original, System.Drawing.Size newSize) [0x00010] in <ecd2d61b095b49809f8ad64ab2df023e>:0 at (wrapper remoting-invoke-with-check) System.Drawing.Bitmap..ctor(System.Drawing.Image,System.Drawing.Size) at System.Windows.Forms.XplatUIX11.DefineCursor (System.Drawing.Bitmap bitmap, System.Drawing.Bitmap mask, System.Drawing.Color cursor_pixel, System.Drawing.Color mask_pixel, System.Int32 xHotSpot, System.Int32 yHotSpot) [0x00045] in <2a828bf8ac8a4442afef88c9b7c44b75>:0 at System.Windows.Forms.XplatUI.DefineCursor (System.Drawing.Bitmap bitmap, System.Drawing.Bitmap mask, System.Drawing.Color cursor_pixel, System.Drawing.Color mask_pixel, System.Int32 xHotSpot, System.Int32 yHotSpot) [0x00000] in <2a828bf8ac8a4442afef88c9b7c44b75>:0 at System.Windows.Forms.Cursor.CreateCursor (System.IO.Stream stream) [0x00058] in <2a828bf8ac8a4442afef88c9b7c44b75>:0 at System.Windows.Forms.Cursor..ctor (System.Type type, System.String resource) [0x0001e] in <2a828bf8ac8a4442afef88c9b7c44b75>:0 at System.Windows.Forms.Cursors.get_SizeNWSE () [0x00014] in <2a828bf8ac8a4442afef88c9b7c44b75>:0 at System.Windows.Forms.SizeGrip..ctor (System.Windows.Forms.Control CapturedControl) [0x00006] in <2a828bf8ac8a4442afef88c9b7c44b75>:0 at (wrapper remoting-invoke-with-check) System.Windows.Forms.SizeGrip..ctor(System.Windows.Forms.Control) at System.Windows.Forms.ScrollableControl.CreateScrollbars () [0x000c2] in <2a828bf8ac8a4442afef88c9b7c44b75>:0 at System.Windows.Forms.ScrollableControl..ctor () [0x000b0] in <2a828bf8ac8a4442afef88c9b7c44b75>:0 at System.Windows.Forms.ContainerControl..ctor () [0x0000e] in <2a828bf8ac8a4442afef88c9b7c44b75>:0 at System.Windows.Forms.Form..ctor () [0x00012] in <2a828bf8ac8a4442afef88c9b7c44b75>:0 at KeePass.Forms.MainForm..ctor () [0x00113] in <487f27be0d384fe4aa3672a39fab9420>:0 at (wrapper remoting-invoke-with-check) KeePass.Forms.MainForm..ctor() at KeePass.Program.MainPriv (System.String[] args) [0x004c4] in <487f27be0d384fe4aa3672a39fab9420>:0 adrian@10:~> I'm running OpenSuse 15.2 in QEMU. All the available updates as of this time are installed. mono-core, mono-data, mono-winforms, mono-winfxcore are at version 6.8.0-lp152.4.2. Keepass is at version 2.38-lp152.3.63. -- You are receiving this mail because: You are on the CC list for the bug.

1 5

[Bug 1173718] VUL-1: libmicrohttpd: buffer overflow issue in URL parser
by bugzilla_noreply＠suse.com 04 Jan '21

04 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1173718 https://bugzilla.suse.com/show_bug.cgi?id=1173718#c9 --- Comment #9 from Andreas Stieger <Andreas.Stieger(a)gmx.de> --- https://build.opensuse.org/package/show/openSUSE:Factory:Staging:I/pcp (linked package) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1173718] VUL-1: libmicrohttpd: buffer overflow issue in URL parser
by bugzilla_noreply＠suse.com 04 Jan '21

04 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1173718 https://bugzilla.suse.com/show_bug.cgi?id=1173718#c8 --- Comment #8 from David Disseldorp <ddiss(a)suse.com> --- (In reply to Dominique Leuenberger from comment #5) ... > pcp fails with similar errors; so in order to have this sec review fixed > (and the SR acceptable to TW) we need at least those two packages fixed in > parallel - or mhd not changing API Thanks for the ping. I don't see PCP in openSUSE:Factory:Staging:I - do you have a link for these? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1173718] VUL-1: libmicrohttpd: buffer overflow issue in URL parser
by bugzilla_noreply＠suse.com 04 Jan '21

04 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1173718 https://bugzilla.suse.com/show_bug.cgi?id=1173718#c7 Andreas Stieger <Andreas.Stieger(a)gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |IN_PROGRESS --- Comment #7 from Andreas Stieger <Andreas.Stieger(a)gmx.de> --- From https://lists.gnu.org/archive/html/libmicrohttpd/2020-06/msg00013.html > Furthermore, the release introduces an 'enum MHD_Result' instead of > #defines for MHD_YES/MHD_NO. This is intended to make it easier to check > for certain API misuse bugs by providing better types (not everything is > an 'int'). While this does NOT change the binary API, this change > _will_ cause compiler warnings for all legacy code -- until 'int' is > replaced with 'enum MHD_Result'. > > If you want your code to build without warnings on both older and newer > MHD releases, you may want to introduce a MHD_RESULT as done here: > > https://git.gnunet.org/gnunet.git/tree/src/include/gnunet_mhd_compat.hml So a compatibility stub would be: #if MHD_VERSION >= 0x00097002 #define MHD_RESULT enum MHD_Result #else #define MHD_RESULT int #endif -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1179325] python-SQLAlchemy: Deprecated syntax used for PostgreSQL check constraints: `consrc`
by bugzilla_noreply＠suse.com 04 Jan '21

04 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1179325 https://bugzilla.suse.com/show_bug.cgi?id=1179325#c2 Matej Cepl <mcepl(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #2 from Matej Cepl <mcepl(a)suse.com> --- Not applicable, the changed code is already present in 1.3.22. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1180493] MultiOS Flatpak Installation
by bugzilla_noreply＠suse.com 04 Jan '21

04 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1180493 https://bugzilla.suse.com/show_bug.cgi?id=1180493#c6 --- Comment #6 from S��awomir Lach <slawek(a)lach.art.pl> --- Please, read this: https://docs.flatpak.org/en/latest/tips-and-tricks.html#adding-a-custom-ins… -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1180493] MultiOS Flatpak Installation
by bugzilla_noreply＠suse.com 04 Jan '21

04 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1180493 https://bugzilla.suse.com/show_bug.cgi?id=1180493#c5 --- Comment #5 from S��awomir Lach <slawek(a)lach.art.pl> --- You misunderstood me. Flatpak have two installations, by default (user and system), but allow to add new. I asks to allow (using Yast2) to add one new installation. Imagine we mount flatpak partition on /var/flatpak-multios and add entry to special configuration file (I will search, where it's placed) for this new installation. I do this configuration on some small distro and OpenSUSE. Next I installed my shop client on this installation and can use single shop installation on both systems. Idea is to add /var/flatpak-multios (or whatever) to flatpak configuration file and ask (during system installation/configuration, which partition mount to this mount point). So idea is basically to add new installation (in flatpak dictionary: place where to put flatpak binaries/metadata/repodata/etc.). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1180491] "Panic on CPU 0: IO-APIC + timer doesn't work!"
by bugzilla_noreply＠suse.com 04 Jan '21

04 Jan '21

https://bugzilla.suse.com/show_bug.cgi?id=1180491 https://bugzilla.suse.com/show_bug.cgi?id=1180491#c2 --- Comment #2 from P <opensuse(a)pohw.nl> --- (In reply to Jan Beulich from comment #1) > See https://lists.xen.org/archives/html/xen-devel/2020-12/msg01793.html for > the most recent upstream report of this. As per the reply there, a fix is in > the works. Thanks for the quick reply, Jan. -- You are receiving this mail because: You are on the CC list for the bug.

1 0