Warning running mythtv-backend: "Authentication Rejected"

Bug #55827 reported by alraz.aXess on 2006-08-09
4
Affects Status Importance Assigned to Milestone
mythtv (Ubuntu)
Wishlist
Mario Limonciello

Bug Description

I get errors trying to run mythtv-backend in Ubuntu 6.06

here is what i get:

$ sudo /etc/init.d/mythtv-backend start
Starting MythTV server: mythbackendSession management error: Authentication Rejected, reason : None of the authentication protocols specified are supported andhost-based authentication failed

More or less the same problem when installing it:

$ sudo dpkg-reconfigure --force mythtv-backend Stopping MythTV server: mythbackend No /usr/bin/mythbackend found running; none killed.
.
Starting MythTV server: mythbackendSession management error: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed

I have a MSI TV@nywhere master capture video card, and am totally new to this linux stuff.

Some other system specs:
AMD Athlon 64 3200+
Motherboard: Abit AV8
1024 MB of RAM
Running 2.6 Kernel for AMD Athlon 64 CPU

Related branches

Mario Limonciello (superm1) wrote :

This is normal syntax when starting myth through the init script due to how sudo is handling the home directory's .qt directory. If mythbackend isn't running however AFTER this, then this is a problem, and we will need more info. Closing the bug, if you have more troubles feel free top open it backup.

Changed in mythtv:
status: Unconfirmed → Rejected
Dagmar d'Surreal (evildagmar) wrote :

What /specifically/ is sudo supposed to be "handling" in ~/.qt?

We're getting people in #MythTV-Users who are having this problem about three nights out of five, and frankly, it doesn't seem to make any sense.

Neither mythfilldatabase, nor mythbackend actually need to talk to X at /all/, so they should not need to do any session authentication. Neither mythbackend nor mythfilldatabase are running after the error appears.

Kees Cook (kees) wrote :

I'm moving this back to "confirmed" (but as "wishlist") just because it's a dire-sounding warning, and others may try to report the problem. This seems to be a known problem with the way the script runs, but is harmless. If anyone tracks down the cause, I'd be happy to adjust the packaging to fix it.

Changed in mythtv:
assignee: nobody → keescook
importance: Undecided → Wishlist
status: Rejected → Confirmed
Mario Limonciello (superm1) wrote :

I've got some further information resulting from experimentation related to this bug.

If /home/mythtv/.ICEauthority exists, is valid, and owned by mythtv - this bug doesn't crop up. Now my understanding of ICEauthority files is that they are generated on logon, so it's not exactly trivial to setup an ICEauthority file for the mythtv user that would consistently work.

Mario Limonciello (superm1) wrote :

I've got this nailed down and fixed in bzr.

Changed in mythtv:
assignee: keescook → superm1
status: Confirmed → In Progress
Changed in mythtv:
status: In Progress → Fix Committed
Changed in mythtv:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers