Bug 30960

Summary:	Error report in journal about mandi
Product:	Mageia	Reporter:	papoteur <yvesbrungard>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED INVALID	QA Contact:
Severity:	minor
Priority:	Normal	CC:	davidwhodgins, lewyssmith
Version:	8
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:

Description papoteur 2022-10-13 09:45:48 CEST

Description of problem:
failed to acquire monitor on DBus: org.freedesktop.DBus.Error.ServiceUnknown: The name org.mageia.monitoring was not provided by any .service files#012 (is mandi started?)

See https://www.mageialinux-online.org/forum/topic-29230-1+probleme-de-demarrage.php#m305200

Comment 1 Dave Hodgins 2022-10-13 18:50:32 CEST

The error message just means mandi is installed, but disabled (which is it's
default on installation).

Despite dbus calling it an error, it's a warning that can be ignored.

Alternatively mandi can be enabled to generate useless warnings about
things that have been blocked. Those things require no action, since they've
been correctly blocked.

I normally uninstall mandi except when testing it.

CC: (none) => davidwhodgins

Comment 2 Dave Hodgins 2022-10-13 19:01:10 CEST

I've read the deepl.com translation of the forum posting. The dbus error
has nothing to do with the black screen. That's likely a graphics card
driver problem.

Assuming the problem is with one of the nvidia drivers, I recommend switching
to a tty (alt+ctrl+f2 or f3 etc.), login as root, and use drakconf to switch
the display from using the detected video driver to using Xorg/nouveau,
and then either restart X or reboot.

Comment 3 Lewis Smith 2022-10-13 21:29:13 CEST

I have looked at the post URL'd comment 0, which is at the end of a large topic about a different startup problem.

The user implies black screen after he has logged in, i.e. the display manager is working. Also, that his initial session was ? OK: he used 'change user':
"le problème démarre là et non après ma connexion): j'utilise changer d'utilisateur;"
"The problem starts there and not after my ? login; I use change user".

"après avoir cliqué sur l'utilisateur proposé par défaut puis tapé mon mot de passe"
"after having clicked on the default user then typing the password".

He also complains that once logged in (?), the interface responds poorly, mouse wheel does not always work, Ctrl behaves as a 'zoom' key for some applications.

It is difficult to know exactly what leads up to the problem. A more precise description of events might help, from the first login. What works or not, do things go wrong only after change user? The kbd/mouse problem looks more X than the graphics driver.

It would help to know more: to tell us about his system, the output of:
 $ inxi -MSGxx
which will include desktop and display manager.

and perhaps *attach* /var/log/Xorg.0.log from a bad session.

CC: (none) => lewyssmith

Comment 4 papoteur 2022-10-14 09:16:56 CEST

Thanks both for your answers.
Thus I will close this report.

Status: NEW => RESOLVED
Resolution: (none) => INVALID

Comment 5 Lewis Smith 2022-10-16 19:32:42 CEST

Yves, no need yet to close this bug. The user has a problem. It is just that his description of his problem was too 'flou' to follow up.