[Expired for libpam-foreground (Ubuntu) because there has been no
activity for 60 days.]
--
security policy error with hald after latest updates
https://bugs.launchpad.net/bugs/58165
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
Might this have something to do with /var/run being a tmpfs, and the
/var/run/console directory not being created by anything, so libpam-
foreground doesn't have a place to store its files?
--
security policy error with hald after latest updates
https://launchpad.net/bugs/58165
--
ubuntu-bugs
I would suppose that any pam configuration that had sufficient for any
module before pam_foreground would prevent pam_foreground from taking
effect.
--
security policy error with hald after latest updates
https://launchpad.net/bugs/58165
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
have some additional info:
i've managed to apply some pending upgrades on the server, i've upgraded
to latest kernel as today and after restarting the system i've got this
message. i believe it can be the root of the hal problem
[EMAIL PROTECTED]:/var/run # /etc/init.d/dbus start
* Starting
well, because this became a big issue for me and my users i googled a
lot and finally got this solved...
the segfault issue was caused by a previos mod to hald.conf trying to
solve the original issue, after comparing between the bad an sane system
i've managed to found the problem
and after
Ah, reopening. Do you still know what was in /var/run/console before,
and can you reproduce this bug?
** Changed in: hal (Ubuntu)
Sourcepackagename: hal = libpam-foreground
Status: Rejected = Needs Info
--
security policy error with hald after latest updates
Martin,
As I said before, it's extremely erratic and difficult to reproduce. The
contents in /var/run/console looked correct before, compared to what's on my
other functional Ubuntu boxes, and when it's recreated on reboot it's
basically recreated identically as before, but somehow it works when
the user on all the systems exists on plugdev
[EMAIL PROTECTED]:~$ id
uid=1(andres.mujica) gid=513(Domain Users)
grupos=4(adm),20(dialout),24(cdrom),25(floppy),29(audio),30(dip),44(video),46(plugdev),107(lpadmin),108(scanner),109(admin),119(fuse),513(Domain
On one of my systems where this problem recurred, removing and mkdir'ing
/var/run/console, then rebooting fixed the problem
--
security policy error with hald after latest updates
https://launchpad.net/bugs/58165
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
This looks like your user is not in the 'plugdev' group, thus does not
have the privilege to mount removable devices. The quick shell fix:
sudo adduser `id -un` plugdev
Please report back if it still does not work.
** Changed in: hal (Ubuntu)
Status: Confirmed = Rejected
--
security
well i've got 3 machines, only one of them doesn't have this problem.
The rest of them has the problem.
any suggestion in how we can compare the systems?
maybe that way we can found the problem..
--
security policy error with hald after latest updates
https://launchpad.net/bugs/58165
--
i'm attaching 3 files:
dpkg -l off the 3 systems
dpkg-unaffected
dpkg-affected-system-1 and 2.
maybe it can help somehow...
** Attachment added: dpkg -l unaffected
http://librarian.launchpad.net/4182632/dpkg-unaffectedsystem
--
security policy error with hald after latest updates
** Attachment added: dpkg -l affected system 1
http://librarian.launchpad.net/4182633/dpkg-affected-system-1
--
security policy error with hald after latest updates
https://launchpad.net/bugs/58165
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Attachment added: dpkg -l system 2
http://librarian.launchpad.net/4182634/dpkg-affected-system-2
--
security policy error with hald after latest updates
https://launchpad.net/bugs/58165
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
all systems updated to latest updates from sept 06
--
security policy error with hald after latest updates
https://launchpad.net/bugs/58165
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
well i can say that i do not have upstart
[EMAIL PROTECTED]:~ # dpkg -l | grep upstart
[EMAIL PROTECTED]:~ # dpkg -l | grep sysvinit
ii sysvinit 2.86.ds1-6ubuntu32
System-V like init
[EMAIL PROTECTED]:~ # dpkg -l | grep start
ii
have you checked this?
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=377689
they talk about the issue in depth
i would try theirs recomendation and report back about it
--
security policy error with hald after latest updates
https://launchpad.net/bugs/58165
--
ubuntu-bugs mailing list
I think that it is now increasingly clear that this has nothing to do
with upstart
** Changed in: upstart (Ubuntu)
Status: Confirmed = Rejected
--
security policy error with hald after latest updates
https://launchpad.net/bugs/58165
--
ubuntu-bugs mailing list
Another confirmation on another edgy box -- after the latest dist-
upgrade it broke hal in the same way. Only this time, the packages
upgraded were upstart and upstart-compat-sysv.
Could this be upstart related?
I reverted from upstart to sysvinit, but it did NOT resolve the problem.
** Also
I was able to recreate this on another machine by installing a kubuntu
knot2 livecd, then installing upstart + upstart-compat-sysv, then dist-
upgrading.
As a result, I'm marking upstart as affected. I will investigate further
to see if upstart is really involved, but it looks like a suspect
I was able to recreate this on another machine by installing a kubuntu
knot2 livecd, then installing upstart + upstart-compat-sysv, then dist-
upgrading.
As a result, I'm marking upstart as affected. I will investigate further
to see if upstart is really involved, but it looks like a suspect
This is a little random...
Upstart technically just runs hal the same way that sysvinit used to,
except for one small detail ... the stdin/out/err of the init script
will be /dev/null instead of /dev/console.
Try adding console output to /etc/event.d/rc2 and see whether that
fixes the problem.
Yes, adding console output does fix this problem for me. It seems like
that does make a difference to hal, or the lack of console output
somehow screws up libpam-foreground or something?
Either way, it now seems like an upstart bug and not a hal bug anymore.
** Changed in: upstart (Ubuntu)
Reject the hal portion of this bug for now -- doesn't seem to be hal's
fault.
** Changed in: hal (Ubuntu)
Status: Confirmed = Rejected
--
security policy error with hald after latest updates
https://launchpad.net/bugs/58165
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I disagree ... hal shouldn't need a console when started -- the right
fix is to find out why that breaks it
** Changed in: hal (Ubuntu)
Status: Rejected = Confirmed
--
security policy error with hald after latest updates
https://launchpad.net/bugs/58165
--
ubuntu-bugs mailing list
Hmm, that's not it... After a few more updates rolled in, I tried to
reproduce this bug on another system. I could not. Coming to think of
it, with the other system I did do a dist-upgrade AND apply the console
option at the same time, which fixed the problem.
When I get home, I'll play with
Confirmed on latest edgy dist-upgrade, with kubuntu-desktop and ubuntu-
desktop installed. In addition, knetworkmanager refuses to interface
with its backend for the same reason.
Strangely, I have another edgy, pure kubuntu box that does not exhibit
this behavior.
Nonetheless, I think this
attached screenshoot for the error
--
security policy error with hald after latest updates
https://launchpad.net/bugs/58165
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
28 matches
Mail list logo
