"dbus-daemon: Rejected send message" for indicator-applet spams /var/log/auth.log
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Indicator Applet |
Fix Released
|
Low
|
Ted Gould | ||
indicator-applet (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Bug Description
Binary package hint: indicator-applet
I get loads of these in /var/log/auth.log (about two every second) when indicator-applet is running.
Mar 21 22:25:14 kohjinsha dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.32" (uid=1000 pid=3184 comm="/
This is on a fairly fresh Jaunty with indicator-applet 0.1.3-0ubuntu1
Related branches
summary: |
- dbus-daemon: rejected send message for indicator-applet + dbus-daemon: rejected send message for indicator-applet spams syslog |
summary: |
- dbus-daemon: rejected send message for indicator-applet spams syslog + "dbus-daemon: Rejected send message" for indicator-applet spams + /var/log/auth.log |
Daniel T Chen (crimsun) wrote : | #1 |
Changed in indicator-applet (Ubuntu): | |
importance: | Undecided → Medium |
status: | New → Confirmed |
JP Vossen (jp-jpsdomain) wrote : | #2 |
I'm getting tons of these as well, on a clean install, brand new, fully-updated-as-of yesterday (2009-03-29) Jaunty VM, except they seem to be cron related. I know nothing about DBus, so I'm not sure if this is a symptom of the same problem and belongs here, or a related problem that wants a cron bug...
I do have 3 active cron jobs for root, but 2 are once a week and one is every 25 mins, none of which match the time pattern here:
Mar 30 16:45:01 ubuntu-904 dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.32" (uid=1000 pid=4091 comm="/
Mar 30 16:50:01 ubuntu-904 dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.32" (uid=1000 pid=4091 comm="/
Mar 30 16:55:02 ubuntu-904 dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.32" (uid=1000 pid=4091 comm="/
Mar 30 17:00:01 ubuntu-904 dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.32" (uid=1000 pid=4091 comm="/
Mar 30 17:00:01 ubuntu-904 dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.32" (uid=1000 pid=4091 comm="/
Mar 30 17:02:01 ubuntu-904 dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.32" (uid=1000 pid=4091 comm="/
JP Vossen (jp-jpsdomain) wrote : | #3 |
OK, some more, hope this is useful and the right place.
I filtered the noise above out [1] and have now noticed a much small amount of these:
Mar 31 08:05:05 ubuntu-904 dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.32" (uid=1000 pid=4091 comm="/
Mar 31 08:05:56 ubuntu-904 kernel: [101220.020438] type=1502 audit(123850115
Mar 31 08:06:40 ubuntu-904 syslogd 1.5.0#5ubuntu3: restart.
Mar 31 08:35:10 ubuntu-904 dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.32" (uid=1000 pid=4091 comm="/
Mar 31 08:35:10 ubuntu-904 dhclient: DHCPREQUEST of 192.168.1.100 on eth0 to 192.168.1.11 port 67
Mar 31 08:35:10 ubuntu-904 dhclient: DHCPACK of 192.168.1.100 from 192.168.1.11
I even got some like this when manually testing my regex [1]!
Mar 31 03:17:09 ubuntu-904 dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.32" (uid=1000 pid=4091 comm="/
_______
[1] Logcheck regex to filter out my most noisy (cron) message:
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ dbus-daemon: Rejected send message, [0-9]+ matched rules; type="method_call", sender=":[0-9.]+" \(uid=[0-9]+ pid=[0-9]+ comm="/
Ted Gould (ted) wrote : | #4 |
Basically what happens here i that we're fighting the possibility of a race condition by getting the property on people who just pop onto the bus. We need to fight this better.
Changed in indicator-applet: | |
assignee: | nobody → Ted Gould (ted-gould) |
importance: | Undecided → Low |
milestone: | none → 0.2 |
status: | New → Confirmed |
Ted Gould (ted) wrote : | #5 |
We are now detecting whether people are exporting the interface on the bus by looking at the introspection data and seeing if they say they are. This fixes most of this problem, but there are still some services that are blocking their introspection data. This is incorrect. D-feet also has this problem and causes the auth.log entries on these servers. I'm marking this fix committed because at this point I think that *we're* doing it correctly. The rest of the fix is on their side.
Changed in indicator-applet: | |
status: | Confirmed → Fix Committed |
Stephen Crowley (crow-crowlogic) wrote : | #6 |
- AllowDBusPropertiesGetMethodCall.patch Edit (465 bytes, text/plain)
Adding this line to /etc/dbus-
<allow send_interface=
mingtien (weisielei) wrote : | #7 |
Hi Stephen,
Just FYI -- in my configuration (Jaunty release 23 Apr.) this actually causes dbus to fail -- the result is that after a reboot, all related devices (keyboard, mouse, etc.) are frozen :-D
Peter Cooper (pcooper-gaitor) wrote : | #8 |
Hi, I have this problem as well, have we an approved work around for it?
Brownout (brownout) wrote : | #9 |
Sure, kill indicator-applet while waiting for a fix.
dl9sau (thomas-x-berg) wrote : | #10 |
Still present in Ubuntu Jaunty amd64.
Since 2009-05-03 03:12 up to now (2009-05-05 20:05) there are 552 such messages from indicator-applet in auth.log. From 61 different programs:
grep dbus-daemo /var/log/
61 163 2324
I regard the logging of the commands as privacy issue. I.e.
comm="pidgin ")).
And I have even more concerns about the logging of the command line arguments of the programs as privacy issue:
comm="epiphany-
comm="vlc ....somefile"))
etc..
I respect that it *may* be needed for debuging. But it _has_ to be an opt-in option.
Brownout (brownout) wrote : | #11 |
auth.log is 0640 I don't see any privacy issue.
Tremaine Lea (tremaine) wrote : | #12 |
Getting a fair number of these myself - 282 for May 15 just grepping for indicator-applet
et/indicator-applet --oaf-a") interface=
auth.log.0:May 15 07:39:01 quad dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.38" (uid=1000 pid=5157 comm="/
auth.log.0:May 15 07:40:01 quad dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.38" (uid=1000 pid=5157 comm="/
auth.log.0:May 15 07:42:11 quad dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.38" (uid=1000 pid=5157 comm="/
auth.log.0:May 15 07:50:01 quad dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.38" (uid=1000 pid=5157 comm="/
tlea@quad:/var/log$ sudo grep indicator-applet * |grep "May 15" | wc -l
282
tlea@quad:/var/log$ ps aux |grep 5157
tlea 5157 0.0 0.1 226200 6392 ? S May08 0:06 /usr/lib/
tlea 17562 0.0 0.0 7524 892 pts/1 R+ 02:43 0:00 grep 5157
Yufei (yufei) wrote : | #13 |
This also causes sudo failed.
If you sudo, it will prompt:
<USRENAME> is not allowed to run sudo on <HOSTNAME>. This incident will be reported.
the auth.log:
May 19 13:31:17 <hostname> dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.1756" (uid=1000 pid=11567 comm="/
Anand Kumria (wildfire) wrote : | #14 |
Ted,
Are you able to put together a version that could go into 9.04 so that the rejection message is no longer being logged? I think that only revision 291 needs to be applied and the problem would be cleared up.
Correct?
Thanks,
Anand
Ted Gould (ted) wrote : Re: [Bug 346513] Re: "dbus-daemon: Rejected send message" for indicator-applet spams /var/log/auth.log | #15 |
On Thu, 2009-05-21 at 12:31 +0000, Anand Kumria wrote:
> Are you able to put together a version that could go into 9.04 so that
> the rejection message is no longer being logged? I think that only
> revision 291 needs to be applied and the problem would be cleared up.
>
> Correct?
No because it turns out that the DBus system bus gets authorization
errors on DBus introspection as well. I think that's a bug, but I have
to fix that one now too :(
raducu (radu-bulboaca) wrote : | #16 |
This bug (or something similar) is causing failed accesses to the keyring and breaks pidgin, the network applet, firefox bookmarks, etc... (basically crippling the system).
I've seen it on my setup on a dist-upgrade from 8.10 to 9.04 and two separate times on clean 9.04 installs.
Please let me know if logs/system details would help.
Thanks,
Radu
spliffster (spliffster) wrote : | #17 |
I am experiencing the same problems on two systems. One system was upgraded to jaunty, the other one is a fresh install of jaunty.
When using polkit-
here goes:
Jul 14 20:24:15 splatter dbus-daemon: Rejected send message, 2 matched rules; type="method_call", sender=":1.603" (uid=1000 pid=19434 comm="bluetooth
Jul 14 20:24:15 splatter dbus-daemon: Rejected send message, 2 matched rules; type="method_call", sender=":1.603" (uid=1000 pid=19434 comm="bluetooth
Jul 14 20:24:17 splatter dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.611" (uid=1000 pid=19493 comm="/
Jul 14 20:24:17 splatter dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.611" (uid=1000 pid=19493 comm="/
Jul 14 20:24:17 splatter dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.611" (uid=1000 pid=19493 comm="/
Jul 14 20:24:17 splatter dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.611" (uid=1000 pid=19493 comm="/
Jul 14 20:24:17 splatter dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.611" (uid=1000 pid=19493 comm="/
Jul 14 20:24:17 splatter dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.611" (uid=1000 pid=19493 comm="/
arky (arky) wrote : | #18 |
On my karmic machine I get these errors.
Jul 15 22:33:14 karmic-kola dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.51" (uid=1001 pid=3423 comm="/
applet/
=3946 comm="/
Jul 15 22:33:15 karmic-kola dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.51" (uid=1001 pid=3423 comm="/
applet/
=3947 comm="/
Jul 15 22:33:15 karmic-kola dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.51" (uid=1001 pid=3423 comm="/
applet/
=3950 comm="/
Jul 15 22:34:37 karmic-kola dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.51" (uid=1001 pid=3423 comm="/
applet/
=2972 comm="/bin/login -- "))
Jul 15 22:34:51 karmic-kola login[2247]: pam_unix(
Jul 15 22:34:51 karmic-kola dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.51" (uid=1001 pid=3423 comm="/
applet/
=2247 comm="/bin/login -- "))
Blue (g-riky) wrote : | #19 |
i got this problem too.
Jul 31 00:00:14 nb-riccardo dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.38" (uid=1000 pid=4111 comm="/
Jul 31 00:00:14 nb-riccardo dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.38" (uid=1000 pid=4111 comm="/
Jul 31 00:00:14 nb-riccardo dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.38" (uid=1000 pid=4111 comm="/
Jul 31 00:00:14 nb-riccardo dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.38" (uid=1000 pid=4111 comm="/
Jul 31 00:00:14 nb-riccardo dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.38" (uid=1000 pid=4111 comm="/
Jul 31 00:00:14 nb-riccardo dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.38" (uid=1000 pid=4111 comm="/
Jul 31 00:00:14 nb-riccardo dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.38" (uid=1000 pid=4111 comm="/
Jul 31 00:00:14 nb-riccardo dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.38" (uid=1000 pid=4111 comm="/
Jul 31 00:00:14 nb-riccardo dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.38" (uid=1000 pid=4111 comm="/
David Groos (djgroos) wrote : | #20 |
Hi--I've got hundreds of these also. It'd be nice to not see them...
Aug 15 04:50:01 ssss CRON[27271]: pam_unix(
Aug 15 04:50:01 ssss dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.60" (uid=1000 pid=5663 comm="/
Aug 15 04:50:02 ssss CRON[27271]: pam_unix(
Aug 15 05:00:01 ssss CRON[28011]: pam_unix(
Aug 15 05:00:01 ssss CRON[28010]: pam_unix(
Aug 15 05:00:01 ssss dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.60" (uid=1000 pid=5663 comm="/
Hope this is helpful.
Changed in indicator-applet: | |
status: | Fix Committed → Fix Released |
status: | Fix Released → Fix Committed |
Changed in indicator-applet: | |
status: | Fix Committed → Fix Released |
stickman (herman-cictr) wrote : | #21 |
Sorry if I'm missing something obvious here. Is there in fact a fix?
I did try pasting <allow send_interface=
After enabling backports and pre-release updates I managed to vastly reduce the number of these messages that get logged but I am still getting the message:
Sep 1 12:30:01 gutenberg dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.34" (uid=1000 pid=3193 comm="/
every time CRON runs or I try doing something like su.
Todd Chaffee (tc-toddbiz) wrote : | #22 |
I have a freshly installed version of jaunty with all upgrades applied and I am getting this error too. Am I missing something about how to apply the fix or is it not yet available?
Mr Freeze (rockula-mike) wrote : | #23 |
Interesting how slowly things trickle down to the end user. Fix committed 34 days ago, fix released 17 days ago, bug reported 181 days ago. I'm not complaining as much as just wondering why. Anyone have an explanation? (And I do have proposed and backports enabled for updates.)
Unhban (david-norris) wrote : | #24 |
I too am confused about this fix being released. I saw it had been released many days ago, but where? This site is very untuative to use. Can someone please say where to get the fix!
Unh.
Ted Gould (ted) wrote : | #25 |
The upstream version of indicator-applet has been uploaded to Karmic.
Changed in indicator-applet (Ubuntu): | |
status: | Confirmed → Fix Released |
Changed in indicator-applet: | |
status: | Fix Released → Incomplete |
Changed in indicator-applet (Ubuntu): | |
status: | Fix Released → Incomplete |
Changed in indicator-applet: | |
status: | Incomplete → Fix Released |
Changed in indicator-applet (Ubuntu): | |
status: | Incomplete → Fix Released |
Raubvogel (raubvogel) wrote : | #26 |
Will it be backported to Jaunty?
Ted Gould (ted) wrote : | #27 |
On Fri, 2009-10-16 at 20:39 +0000, Raubvogel wrote:
> Will it be backported to Jaunty?
I have no plans to do so, but I don't believe that it has many new
dependencies that would make it a difficult backport. I'd be happy to
answer questions for anyone who'd like to backport it.
Mr Freeze (rockula-mike) wrote : | #28 |
So what exactly does it take to get something that the users want backported to be backported? Do we need a petition, and if so, how many people? There are over 100 names listed at the right of this page already. And I'm sure everyone knows that there are many who merely bookmark the page and don't subscribe to the bug. If it's not so hard to backport it, and you have the time to answer questions for someone else wants to backport it....then why on Earth don't you just do it yourself and be finished with it? Is it bureaucracy, politics within Ubuntu, blame game being played between developers? It's simple things like this bug that multiply and get swept under the rug that probably hurts Ubuntu the most. You get 15 or 20 small, nagging bugs on your system and you begin to wonder if you shouldn't just switch to a better version of linux that "just works". I'm not singling any one person out...just making a general observation of what I see going on with Ubuntu concerning bugs that are not deemed "critical", etc.
Thank you for your time and for doing what you do Ted.
Sebastien Bacher (seb128) wrote : | #29 |
> Do we need a petition, and if so, how many people?
because a petition will solve the fact that the current team work manpower to work on backporting this change?
Sebastien Bacher (seb128) wrote : | #30 |
the number of subscribers doesn't make the bug being one users run into often or an annoying one, it's just some spamming in logs nothing really brocken or stopping you to work on your computer too
Mr Freeze (rockula-mike) wrote : | #31 |
Thanks Sebastien,
Point taken. You guys don't have the manpower to take care of something that is BROKEN (not working properly, spitting out endless ERROR messages) unless it causes the computer to BREAK completely.
ljohan (johan-pean) wrote : | #32 |
I'm also experiencing this problem. A work-around or fix for Jaunty would be very appreciated since this affects my every-day work.
mmdanziger (mmdanziger) wrote : | #33 |
Don't know too much about the history of this bug. I just did a clean install of kubuntu 9.10 and i'm getting similar messages. Though it doesn't appear to be fatal, seeing something that is obviously wrong repeating itself all the time is a bit disturbing, especially since for all I know, it is affecting something in system performance. Maybe this is a plasma-desktop bug? It seems to be the same as the one documented above. Anyhow, I get stuff like:
Nov 10 17:04:01 cleverbox dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.20" (uid=1000 pid=1675 comm="kdeinit4: plasma-desktop [kdeinit]") interface=
Nov 10 17:04:01 cleverbox dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.20" (uid=1000 pid=1675 comm="kdeinit4: plasma-desktop [kdeinit]") interface=
Nov 10 17:04:01 cleverbox dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.20" (uid=1000 pid=1675 comm="kdeinit4: plasma-desktop [kdeinit]") interface=
Nov 10 17:04:01 cleverbox dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.20" (uid=1000 pid=1675 comm="kdeinit4: plasma-desktop [kdeinit]") interface=
Nov 10 17:04:01 cleverbox dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.20" (uid=1000 pid=1675 comm="kdeinit4: plasma-desktop [kdeinit]") interface=
Nov 10 17:04:01 cleverbox dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.20" (uid=1000 pid=1675 comm="kdeinit4: plasma-desktop [kdeinit]") interface=
Nov 10 17:04:01 cleverbox dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.20" (uid=1000 pid=1675 comm="kdeinit4: plasma-desktop [kdeinit]") interface=
Nov 10 17:04:01 cleverbox dbus-daemon: Rejected send message, 2 matched rules; type="method_call", sender=":1.20" (uid=1000 pid=1675 comm="kdeinit4: plasma-desktop [kdeinit]") interface=
Kenyon Ralph (kralph) wrote : | #34 |
On 2009-11-
> Don't know too much about the history of this bug. I just did a clean
> install of kubuntu 9.10 and i'm getting similar messages. Though it
> doesn't appear to be fatal, seeing something that is obviously wrong
> repeating itself all the time is a bit disturbing, especially since for
> all I know, it is affecting something in system performance. Maybe this
> is a plasma-desktop bug? It seems to be the same as the one documented
> above. Anyhow, I get stuff like:
>
> Nov 10 17:04:01 cleverbox dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.20" (uid=1000 pid=1675 comm="kdeinit4: plasma-desktop [kdeinit]") interface=
This is a bug about indicator-applet. Your log messages appear to be
unrelated.
--
Kenyon Ralph
Psy[H[] (vovik-wfa) wrote : | #35 |
Ubuntu 9.10 with up to date upgrades, getting this:
Nov 28 23:08:16 mindthunder dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.107" (uid=1000 pid=12356 comm="/
Nov 28 23:08:16 mindthunder dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.107" (uid=1000 pid=12356 comm="/
Nov 28 23:08:16 mindthunder dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.107" (uid=1000 pid=12356 comm="/
Nov 28 23:08:16 mindthunder dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.107" (uid=1000 pid=12356 comm="/
Nov 28 23:08:16 mindthunder dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.107" (uid=1000 pid=12356 comm="/
Nov 28 23:08:16 mindthunder dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.107" (uid=1000 pid=12356 comm="/
Nov 28 23:08:16 mindthunder dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.107" (uid=1000 pid=12356 comm="/
Nov 28 23:08:16 mindthunder dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.107" (uid=1000 pid=12356 comm="/
Nov 28 23:08:16 mindthunder dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.107" (uid=1000 ...
knisleyjw (knisleyjw) wrote : | #36 |
Also Kubunutu 9.10 w/all updates, getting a whole lot of error messages prefixed with:
dbus-daemon: Rejected send message, 1 matched rules; type="method_call", sender=":1.21" (uid=1000 pid=4557 comm="kdeinit4: plasma-desktop [kdeinit]") interface=
(uid=1000 pid=11355 comm="/
(uid=0 pid=11349 comm="/
So I'm not sure if these are the only things that might require superuser? Just trying to look for a common thread, because this is driving me bonkers.
Now I know that people say "Oh, pssh. Logging. You can skip over that" but my logwatch is now 350k from when it was about 10-20 on Jaunty. I missed several dozen EDAC errors on a new server buried in this soup. Logging is important when managing servers -- it helps you tell when something is about to go wrong.
I'm not actually sure if this is still being looked at, given that it's marked as completed. I hope it is.
Kenyon Ralph (kralph) wrote : Re: [Bug 346513] "dbus-daemon: Rejected send message" for indicator-applet spams /var/log/auth.log | #37 |
Your log message has nothing to do with this bug report. This bug report
is about indicator-applet, not plasma-desktop.
On 2009-12-
> Also Kubunutu 9.10 w/all updates, getting a whole lot of error messages
> prefixed with:
>
> dbus-daemon: Rejected send message, 1 matched rules; type="method_call",
> sender=":1.21" (uid=1000 pid=4557 comm="kdeinit4: plasma-desktop
> [kdeinit]") interface=
> member="Introspect" error name="(unset)" requested_reply=0
> destination=
knisleyjw (knisleyjw) wrote : | #38 |
You're absolutely right and I'm terribly sorry. Can you tell me if this is a plasma-desktop issue or a dbus issue, as other people seem to be having the same problem and I'd rather have proper routing than "go away."
Bill (hudacek) wrote : | #39 |
I applied Stephen's patch (comment #6) and rebooted (I've found trying to restart dbus causes all kinds of havoc.....in the past anyway...so I'm "once burned, twice shy"). Don't just add the directive he gives; make sure it gets added where he shows it being placed in the file.
All USB ports work, and now there are zero logged messages.
I'm no dbus expert, so I don't know if there are implications, security or otherwise. But now my daily status messages will be about 9KB, rather than 350KB! What a nightmare to read through the tons of useless information...now I actually see the useful messages from the 'secure' group.
I'm on Jaunty, BTW, where there has been no patch. This is an effective workaround.
/Bill
jhthayer (jhthayer) wrote : | #40 |
Since my machine (Kubuntu 9.10) IS broken by something like this, I am posting to this bug, though it could be a different one, messages are much the same.
Machine suddenly wouldn't accept login (kdm), messed about, got into command line using Ctrl-Alt-F1, logged in, then told upstart to stop kdm, used sudo startx to start up a root session, checked Auth.log and found surfeit of these error messages which seem to be broadcast (for Introspection?) by Plasma desktop, but which appear to start prior to my command-line login, and thus make me suspect they're connected with the blocking of the KDM login. Will attach logs if you're at all interested.
Though I may have done something to precipitate this, I have no idea what it might have been, and am a bit floundering trying to deal with dbus and friends.
Nanci (nanci-d) wrote : | #41 |
This problem is still occurring with 12.04 LTS Ubuntu, and so should not be claimed to be fixed. I have a standard install of 12.04 on a virgin (no other OS ever installed) and have instances of this error in my error log. Please advise what config changes I must make to alter my server from standard distribution of 12.04 to eliminate this error. Thanks!
Confirmed with amd64 on:
1) a fresh installation of 9.04 using default settings and a new user, and
2) a distribution upgrade from 8.04.2 to 8.10 to 9.04 using default settings and a new user, and
3) a distribution upgrade from 8.04.2 to 8.10 to 9.04 using an existing user.