On Thu, 2005-03-03 at 14:17 +, Matthew T. Atkinson wrote:
'ello,
On Fri, 2005-01-07 at 20:04 -0500, Harvey Ussery wrote:
I recently reinstalled Sarge PPC on a G4 iMac. Each time I boot up now,
I get an error warning:
I think I need pinching -- I just logged into GNOME and the error
'ello,
On Fri, 2005-01-07 at 20:04 -0500, Harvey Ussery wrote:
I recently reinstalled Sarge PPC on a G4 iMac. Each time I boot up now,
I get an error warning:
I think I need pinching -- I just logged into GNOME and the error didn't
appear. I rebooted just to make sure I hadn't clicked OK out
On Wed, Feb 23, 2005 at 11:07:08PM +0100, Martin Lohmeier wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Lohmeier wrote:
| Check the BTS : http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=296437
|
| The permissions are not included in the rule files.
To get it working a
On Thu, Feb 24, 2005 at 05:19:59PM +, Ben Hill wrote:
On Thu, 2005-02-24 at 15:49 +0100, Sven Luther wrote:
Like said, this has been fixed in control-center, so what about testing the
real fix instead of using lousy workarounds ? I and others lost enough time
making sure the fix got in,
Ben Hill wrote:
On Thu, 2005-02-24 at 10:28 -0800, Eric Gaumer wrote:
This shouldn't break anything serious enough to not be able to use Sid. What
exactly do you
mean by a bunch of stuff?
The main thing was all the system icons turned into the default bit of
paper. I can remember reading the
When starting GNOME on my PowerBook, I'm getting a pop-up complaining
about the wrong permission for /dev/pmu.
I've found a post about it here:
http://lists.debian.org/debian-powerpc/2005/01/msg00235.html
...and added:
pmu:root:video:0660
to /etc/udev/permissions.d/udev.permissions
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Ben,
Ben Hill wrote:
| When starting GNOME on my PowerBook, I'm getting a pop-up complaining
| about the wrong permission for /dev/pmu.
|
| I've found a post about it here:
|
| http://lists.debian.org/debian-powerpc/2005/01/msg00235.html
On Wed, Feb 23, 2005 at 09:36:49PM +, Ben Hill wrote:
When starting GNOME on my PowerBook, I'm getting a pop-up complaining
about the wrong permission for /dev/pmu.
I've found a post about it here:
http://lists.debian.org/debian-powerpc/2005/01/msg00235.html
...and added
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Lohmeier wrote:
| Check the BTS : http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=296437
|
| The permissions are not included in the rule files.
To get it working a /etc/udev/rules.d/local.rules with the following
content:
KERNEL=pmu,
On Mon, Jan 10, 2005 at 09:03:33AM +0100, Sjoerd Simons wrote:
On Mon, Jan 10, 2005 at 03:17:22AM +0200, Martin-Éric Racine wrote:
On Sun, 9 Jan 2005, Christoph Hellwig wrote:
On Sun, Jan 09, 2005 at 08:48:39PM +0100, Sven Luther wrote:
just kill this warning. Debian works just fine
On Mon, Jan 10, 2005 at 03:17:22AM +0200, Martin-Éric Racine wrote:
On Sun, 9 Jan 2005, Christoph Hellwig wrote:
On Sun, Jan 09, 2005 at 08:48:39PM +0100, Sven Luther wrote:
just kill this warning. Debian works just fine without backlight
control on both my ibook and the g5. And it's
On Mon, Jan 10, 2005 at 09:21:08AM +0100, Sven Luther wrote:
On Mon, Jan 10, 2005 at 09:03:33AM +0100, Sjoerd Simons wrote:
On Mon, Jan 10, 2005 at 03:17:22AM +0200, Martin-Éric Racine wrote:
On Sun, 9 Jan 2005, Christoph Hellwig wrote:
On Sun, Jan 09, 2005 at 08:48:39PM +0100, Sven
On Mon, 10 Jan 2005, Sjoerd Simons wrote:
The error message won't appear if your user has access to the pmu,
Stop. That's already wrong. Users should not have direct control. Install
pbbuttonsd instead.
--
Martin-Éric Racine, ICT Consultant
http://www.iki.fi/q-funk/
On Mon, Jan 10, 2005 at 09:57:46AM +0100, Sjoerd Simons wrote:
On Mon, Jan 10, 2005 at 09:21:08AM +0100, Sven Luther wrote:
On Mon, Jan 10, 2005 at 09:03:33AM +0100, Sjoerd Simons wrote:
On Mon, Jan 10, 2005 at 03:17:22AM +0200, Martin-Éric Racine wrote:
On Sun, 9 Jan 2005, Christoph
On Mon, 10 Jan 2005, Sven Luther wrote:
On Mon, Jan 10, 2005 at 09:57:46AM +0100, Sjoerd Simons wrote:
As said just change the current pmu patch in the package to do g_warning
instead of acme_error, which is trivial. No need to making a lot of fuss
about
So let's do it ? Do you
Do we already have a bug against udev to have the above line per default, or
otherwise finally fix this issue ?
There were some objections to it the last time it was mentioned. I
Yep. Allowing arbitrary users to talk to the PMU directly is a Bad Thing
(TM). Upstream (Gnome) needs to get a
The error message won't appear if your user has access to the pmu, which is
the
case on my system. But that's ofcourse wrong to do by default.
What do you respond to Christoph's critic, which was if i remember well :
no unaudited gnome app should have such direct access to my
Greetings,
Please see my extensive overview of the situation, added to bugs 281952, 284328.
--
Martin-Éric Racine, ICT Consultant
http://www.iki.fi/q-funk/
On Mon, 10 Jan 2005, Michael Schmitz wrote:
There's not much you can do about that - remember that access to /dev/pmu
means the console user (if you restrict access by means of some console
group) can result in PMU communications hiccup, and when the PMU finds the
host has borked the
There's not much you can do about that - remember that access to /dev/pmu
means the console user (if you restrict access by means of some console
group) can result in PMU communications hiccup, and when the PMU finds the
host has borked the communications, it will shut down power after
On Mon, Jan 10, 2005 at 12:43:13PM +0100, Frederic Peters wrote:
Martin-Éric Racine wrote:
On Mon, Jan 10, 2005 at 09:57:46AM +0100, Sjoerd Simons wrote:
As said just change the current pmu patch in the package to do
g_warning instead of acme_error, which is trivial. No need to
On Mon, 10 Jan 2005, Sjoerd Simons wrote:
On Mon, Jan 10, 2005 at 12:43:13PM +0100, Frederic Peters wrote:
My proposed fix is very simple, but apparently some people didn't understand
it. If acme_error is changed to a g_warning, then in case
gnome-settings-daemon can't access the pmu (for
On Sun, Jan 09, 2005 at 02:33:58AM +0200, Martin-Éric Racine wrote:
On Sat, 8 Jan 2005, Sven Luther wrote:
On Fri, Jan 07, 2005 at 11:48:41PM -0800, Brad Boyer wrote:
On Sat, Jan 08, 2005 at 07:32:32AM +0100, Sven Luther wrote:
Do we already have a bug against udev to have the above
On Sun, 9 Jan 2005, Sven Luther wrote:
On Sun, Jan 09, 2005 at 02:33:58AM +0200, Martin-Éric Racine wrote:
The ACME fix exists and is already patched into Ubuntu packages for Warty,
according to Sebastien Bacher. For some reason, it's not applied in Debian.
So, let's apply it ASAP.
severity 284328 serious
thanks
On Sun, Jan 09, 2005 at 07:01:21PM +0200, Martin-Éric Racine wrote:
On Sun, 9 Jan 2005, Sven Luther wrote:
On Sun, Jan 09, 2005 at 02:33:58AM +0200, Martin-Éric Racine wrote:
The ACME fix exists and is already patched into Ubuntu packages for Warty,
On Sat, Jan 08, 2005 at 07:40:48PM +0100, Christoph Hellwig wrote:
On Fri, Jan 07, 2005 at 11:48:41PM -0800, Brad Boyer wrote:
On Sat, Jan 08, 2005 at 07:32:32AM +0100, Sven Luther wrote:
Do we already have a bug against udev to have the above line per default,
or
otherwise finally
= g_error_new_literal (ACME_FBLEVEL_ERROR,
ACME_FBLEVEL_ERROR_WRONG_PERMS,
_(Wrong permission for
'/dev/pmu' device));
return NULL;
}
foo = ioctl(fd, PMU_IOC_GRAB_BACKLIGHT, 0
for
'/dev/pmu' device));
just kill this warning. Debian works just fine without backlight
control on both my ibook and the g5. And it's really not worth giving
hardware control to an unadited GUI program.
,
ACME_FBLEVEL_ERROR_WRONG_PERMS,
_(Wrong permission for
'/dev/pmu' device));
just kill this warning. Debian works just fine without backlight
control on both my ibook and the g5. And it's really not worth giving
hardware control to an unadited GUI program.
What exactly
,
_(Wrong permission for
'/dev/pmu' device));
just kill this warning. Debian works just fine without backlight
control on both my ibook and the g5. And it's really not worth giving
hardware control to an unadited GUI program.
Having been trying various ways
On Fri, Jan 07, 2005 at 01:17:46PM -0800, Matt Weber wrote:
On Fri, 2005-01-07 at 20:04 -0500, Harvey Ussery wrote:
I recently reinstalled Sarge PPC on a G4 iMac. Each time I boot up now,
I get an error warning:
Error: Wrong permission for 'dev/pmu' device
I've tracked thru
On Sat, Jan 08, 2005 at 07:32:32AM +0100, Sven Luther wrote:
Do we already have a bug against udev to have the above line per default, or
otherwise finally fix this issue ?
There were some objections to it the last time it was mentioned. I
believe there were some questions about it being a bad
On Fri, Jan 07, 2005 at 11:48:41PM -0800, Brad Boyer wrote:
On Sat, Jan 08, 2005 at 07:32:32AM +0100, Sven Luther wrote:
Do we already have a bug against udev to have the above line per default, or
otherwise finally fix this issue ?
There were some objections to it the last time it was
Matt Weber wrote:
On Fri, 2005-01-07 at 20:04 -0500, Harvey Ussery wrote:
I recently reinstalled Sarge PPC on a G4 iMac. Each time I boot up now,
I get an error warning:
Error: Wrong permission for 'dev/pmu' device
I had this problem also. If I remember correctly
Brad Boyer wrote:
Just for completeness, I'll note that the PMU has very little to do
with sound or video as implied in previous posts. It's best for
people not to get more confused than already happens.
That's right, as I discovered when correcting the error message re
/dev/pmu.
On Fri, Jan 07, 2005 at 11:48:41PM -0800, Brad Boyer wrote:
On Sat, Jan 08, 2005 at 07:32:32AM +0100, Sven Luther wrote:
Do we already have a bug against udev to have the above line per default, or
otherwise finally fix this issue ?
There were some objections to it the last time it was
On Sat, 8 Jan 2005, Sven Luther wrote:
On Fri, Jan 07, 2005 at 11:48:41PM -0800, Brad Boyer wrote:
On Sat, Jan 08, 2005 at 07:32:32AM +0100, Sven Luther wrote:
Do we already have a bug against udev to have the above line per default,
or
otherwise finally fix this issue ?
There
I recently reinstalled Sarge PPC on a G4 iMac. Each time I boot up now,
I get an error warning:
Error: Wrong permission for 'dev/pmu' device
I've tracked thru the system all the ref books on hand, also various
linux sites online. Conclusion so far is that this permission problem on
/dev
On Fri, 2005-01-07 at 20:04 -0500, Harvey Ussery wrote:
I recently reinstalled Sarge PPC on a G4 iMac. Each time I boot up now,
I get an error warning:
Error: Wrong permission for 'dev/pmu' device
I've tracked thru the system all the ref books on hand, also various
linux sites online
On 07/11/2004 at 23:24 -0500, Barry Hawkins wrote:
The only meaningful results from the Google search is this message from
Kiko Piris in a July 2004 thread:
http://lists.debian.org/debian-powerpc/2004/07/msg00462.html
In that message I was simply answering that 600 permissions of /dev/pmu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kiko Piris wrote:
| On 07/11/2004 at 23:24 -0500, Barry Hawkins wrote:
[...]
|Applying Kiko's recommendation did not change the situation.
|
|
| Of course, because, AFAICS, the problem is not with the permissions of
| /dev/pmu, the problem is the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Schmitz wrote:
|~Do any of you with more history with Gnome have some info on the
|proper way to handle the /dev/pmu error when Gnome starts up? I have
|
|
| The proper way to handle this is to change the corresponding Gnome applet
| to
On Sun, 2004-11-07 at 23:04 -0500, Barry Hawkins wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Schmitz wrote:
|~Do any of you with more history with Gnome have some info on the
|proper way to handle the /dev/pmu error when Gnome starts up? I have
|
|
| The proper way
the issue.
Searching Google for wrong permission /dev/pmu only yields a total of
26 results, all but 8 of which are screened for being duplicates:
http://www.google.com/search?q=wrong+permission+%2Fdev%2Fpmustart=0start=0ie=utf-8oe=utf-8client=firefoxrls=org.mozilla:en-US:unofficial
The only meaningful
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michel Dnzer wrote:
| On Sun, 2004-11-07 at 23:04 -0500, Barry Hawkins wrote:
[...]
|I have removed all applets I enabled on my own, and the issue still
|persists. Does anyone have recommendations for how to plainly and
|simply isolate the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
List,
~Do any of you with more history with Gnome have some info on the
proper way to handle the /dev/pmu error when Gnome starts up? I have
seen posts on Debian lists and elsewhere with folks changing the
permissions on /dev/pmu manually, and
~Do any of you with more history with Gnome have some info on the
proper way to handle the /dev/pmu error when Gnome starts up? I have
The proper way to handle this is to change the corresponding Gnome applet
to cope with readonly access to /dev/pmu. Plain and simple.
Michael
On Fri, Nov 05, 2004 at 10:21:36AM -0500, Barry Hawkins wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
List,
~Do any of you with more history with Gnome have some info on the
proper way to handle the /dev/pmu error when Gnome starts up? I have
seen posts on Debian lists and
48 matches
Mail list logo
