After installing kde from the beta 3 pre-release iso, with several applications running, I encountered the following error ... [dave@i3 ~]$ reboot Error getting authority: Error initializing authority: GDBus.Error:org.freedesktop.DBus.Error.LimitsExceeded: The maximum number of active connections for UID 500 has been reached (g-dbus-error-quark, 8) Assertion 'bus' failed at src/shared/dbus-common.c:1257, function bus_method_call_with_reply(). Aborting. Aborted According to https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/492941 the max_connections_per_user setting in /etc/dbus-1/session.conf is being ignored, and needs to be set in /etc/dbus-1/system.conf too.
Whiteboard: (none) => 3beta1
I recreated this error, with a kde install from the x86-64 dvd, by opening all applications on the panel, plus a konsole, where the reboot command generated the same error.
On second set of ISOs: 1. x86_64 KDE on VBox 2. x86_64 KDE on real hardware Can not reproduce the error. I opened up 30 applications including konsole, changed to root in the konsole and typed 'reboot' - no error nor unusual behavior like David's description. Repeated twice.
CC: (none) => molch.b
Interesting. I receive this error right after login (without starting a number of programs). Adding max_connections_per_user setting in /etc/dbus-1/system.conf removes the error.
CC: (none) => curtis_mageia
In my case, on a clean install of Beta1, my USB key is not detected AT ALL. On clicking the icon in the system tray, I see "No devices available." Moving the device from a hub to a USB port that is known to support booting makes no difference.
CC: (none) => laidlaws
Further observation: when I log into KDE with the key already plugged in, KDE detects it, pops up its dialog box, then loses it completely.
Assignee: bugsquad => mageia
*** Bug 8473 has been marked as a duplicate of this bug. ***
CC: (none) => junk_no_spam
(In reply to comment #4) > In my case, on a clean install of Beta1, my USB key is not detected AT ALL. On > clicking the icon in the system tray, I see "No devices available." Moving the > device from a hub to a USB port that is known to support booting makes no > difference. You might want to try my solution. https://bugs.mageia.org/show_bug.cgi?id=8473#c2
Yes, that cured the immediate problem, but Dolphin took ages to load. No similar issue in Xfce. The Dolphin icon was showing there too, but the standard file manager is Thunar. I may need to clear my Sessions cache again. The fix for USB drives didn't cure the CD-ROM issue, which is a separate bug. I got around that just before the fresh install, by commenting out the line in fstab. The CD-ROM drive was then handled in the same fashion as a USB key, and mounted in /run/media. Not perfect, but more convenient.
I was about to file a bug about the devices section of the places panel in Dolphin being missing, when I came across this. I was also getting no notifications about inserted media. https://bugs.mageia.org/show_bug.cgi?id=8527 The dbus config changes suggested here https://bugs.mageia.org/show_bug.cgi?id=8473#c2 fixed both issues.
CC: (none) => zen25000
(In reply to comment #8) > The fix for USB drives didn't cure the CD-ROM issue, which is a separate bug. > I got around that just before the fresh install, by commenting out the line in > fstab. The CD-ROM drive was then handled in the same fashion as a USB key, and > mounted in /run/media. Not perfect, but more convenient. I posted a comment to that effect to a different bug, but can't find it. "My bugs" are only bugs I started. Is there a way of listing those I am on the CC list for?
Have a read here - it's the same as clicking the "?" next to search button above: https://bugs.mageia.org/page.cgi?id=quicksearch.html The config changes in #9 also fix another issue where the shutdown and reboot options are missing from the menu -> leave options. I have increased priority and severity on this as it breaks major features in a clean installation of current Cauldron.
Priority: Normal => HighSeverity: normal => major
Priority: High => release_blocker
*** Bug 8527 has been marked as a duplicate of this bug. ***
Summary: dbus max_connections_per_user is too low. => dbus max_connections_per_user is too low. (make also kde auto mounting not working)
This bug seems to happen only with KDE. This could be related to the new udisks 2 solid backend, and this is perhaps already fixed in KDE 4.9.95 (= KDE 4.10 RC1). cf. this upstream commit https://projects.kde.org/projects/kde/kdelibs/repository/revisions/be5ca0c8406d82af0cfb8f8a250410399873b76d "Cache UDisks2 Device DBus connections Cache the QDBusInterface connection for each UDI so that it's not recreated every time Solid::Device is constructed. This greatly reduces the number of DBus calls and makes the UDisks2 backend much faster" regards, Luc
CC: (none) => balcaen.john, lmenut, nicolas.lecureuilSource RPM: dbus-1.6.8-2.mga3.src.rpm => dbus-1.6.8-2.mga3.src.rpm, kdelibs4-4.9.90-1.mga3.src.rpm ?
Blocks: (none) => 8381
Blocks: (none) => 8519
*** Bug 8381 has been marked as a duplicate of this bug. ***
CC: (none) => ftg
That looks like a likely candidate Luc. We already have 4.9.95 and it looks like .97 is committed if not yet submitted. Anyone have confirmation that this solves things?
I am running Xfce with KDE add-ons enabled. I did a standard KDE install then added XFCE. I still need to use a full "mount" command to mount the CD-ROM. If ypou would like me to test that it is the KDE association, I am quite willing to try. Just tell me what to do, but I have no Cauldron until Bug 8614 is fixed.
Seeing as no-one has complained of late, I guess the updated KDE solved things right?
I just tested my failure condition on a clean 64bit beta2 and did not have the errors. Hate to ask, but could you glance at b u g 8852 and verify it is not a dracut bug.
OK, closing this bug now. (PS had a look at 8852, but I'm not really overly familiar with all the different display-fu - I always stick to intel display stuff and shun any nvidia or amd h/w)
Status: NEW => RESOLVEDResolution: (none) => FIXED