http://bugzilla.suse.com/show_bug.cgi?id=1145623http://bugzilla.suse.com/show_bug.cgi?id=1145623#c2
--- Comment #2 from Nicolas Morey-Chaisemartin <nmoreychaisemartin(a)suse.com> ---
Tried to run your test on my system and an OBS Tumbleweed chroot and could not
reproduce your results.
- What arch are you running on ?
- What exact package of openmpi3 are you using ?
- Do you have any fortran flags set by any chances ?
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1157462http://bugzilla.suse.com/show_bug.cgi?id=1157462#c10
--- Comment #10 from Dr. Werner Fink <werner(a)suse.com> ---
(In reply to Simon Lees from comment #9)
> (In reply to Dr. Werner Fink from comment #8)
> > SR#752324 -- could one have a review? Other than me!
>
> Sorry due to timezones I was done for Friday when you sent this, doing the
> update was on my today list if I hadn't heard a good reason to keep
> --enable-asserts.
>
> I this using --disable-asserts would be better then adding another patch,
> its also now how debian handle it.
> https://salsa.debian.org/utopia-team/dbus/blob/debian/master/debian/rules
The udeb_configure_flags rule with --disable-asserts is used for the udeb
packages and those type of packages are only for internal build system for
debian packages.
The patch is also from debian (not utopia!) and is really simple: do not debug
within a running system (no exit(3) nor abort(3) in system libraries):
--- a/dbus/dbus-internals.c
+++ b/dbus/dbus-internals.c
@@ -185,7 +185,7 @@ const char *_dbus_no_memory_message = "Not enough memory";
static dbus_bool_t warn_initted = FALSE;
static dbus_bool_t fatal_warnings = FALSE;
-static dbus_bool_t fatal_warnings_on_check_failed = TRUE;
+static dbus_bool_t fatal_warnings_on_check_failed = FALSE;
static void
init_warnings(void)
could you please explain what is wrong with this approach? If you like to debug
you are able to set the environment variable DBUS_FATAL_WARNINGS to 1.
Currently we do not set DBUS_FATAL_WARNINGS at all, that is with the current
default all customers and users out there do debugging their systems and do not
know about nor can handle this. This causes a lot of trouble and bugzilla
entries.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1157847http://bugzilla.suse.com/show_bug.cgi?id=1157847#c4
--- Comment #4 from Pavol Cupka <palica(a)liguros.net> ---
Thanks for looking into this. It is a legacy-pc-bios system.
I don't have any explanation as how this happened. I can provide more
information, but don't know what would be needed.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1158114
Alynx Zhou <alynx.zhou(a)suse.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |alynx.zhou(a)suse.com
Assignee|bnc-team-screening(a)forge.pr |hmacht(a)suse.com
|ovo.novell.com |
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1158074
Alynx Zhou <alynx.zhou(a)suse.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |alynx.zhou(a)suse.com
Assignee|bnc-team-screening(a)forge.pr |tchvatal(a)suse.com
|ovo.novell.com |
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1157504http://bugzilla.suse.com/show_bug.cgi?id=1157504#c2
Jai Seok Ahn <jaisahn(a)pusan.ac.kr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags|needinfo?(jaisahn(a)pusan.ac. |
|kr) |
--- Comment #2 from Jai Seok Ahn <jaisahn(a)pusan.ac.kr> ---
(In reply to Stefan Brüns from comment #1)
> Cura "allows" to connect to an Ultimaker account.
>
> When there is no authentication data (e.g. on first start, or when the user
> just does not want to use an Ultimaker account), the account handling code
> returns a python "None" object (with an account, it would return a "dict").
>
> Later, some Qt slot handler tries to convert the None object to a
> QVariantMap, which fails.
>
>
> Can you try with the package from:
> https://download.opensuse.org/repositories/home:/StefanBruens:/branches:/KDE:
> /Qt:/5.13/
I installed and replaced with python-qt5, python2-qt5, and python3-qt5 (version
5.13.1-158.8) from the above repo, and Cura starts and works now.
It goes with a bit low-resolution graphics mode to me, but I can handle it.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1095111
Swamp Workflow Management <swamp(a)suse.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Whiteboard|obs:running:11597:moderate |
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1095597
Swamp Workflow Management <swamp(a)suse.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Whiteboard|obs:running:11597:moderate |
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1092953
Swamp Workflow Management <swamp(a)suse.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Whiteboard|obs:running:11597:moderate |
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1102987
Swamp Workflow Management <swamp(a)suse.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Whiteboard|obs:running:11597:moderate |
--
You are receiving this mail because:
You are on the CC list for the bug.