[2.5.19/20] KDE panel (kicker) not starting up

[2.5.19/20] KDE panel (kicker) not starting up

[bvermeul]

The KDE panel (kicker) from KDE 3.0 (RedHat 7.3 issue) refuses to start
up. I get a SIGPIPE in DCOP, and a SIGSEGV in kicker.
This looks like something changed in regards to permissions, 'cause when I 
start KDE as root, it does work.

Does anyone know what's happening?

Regards,

Bas Vermeulen

-- 
"God, root, what is difference?" 
	-- Pitr, User Friendly

"God is more forgiving." 
	-- Dave Aronson

Re: [2.5.19/20] KDE panel (kicker) not starting up

[Peter Wächtler]

bvermeul@devel.blackstar.nl wrote:
> The KDE panel (kicker) from KDE 3.0 (RedHat 7.3 issue) refuses to start
> up. I get a SIGPIPE in DCOP, and a SIGSEGV in kicker.
> This looks like something changed in regards to permissions, 'cause when I 
> start KDE as root, it does work.
> 

check the permissions of /tmp/{kde|ksocket}-$(LOGNAME)

Re: [2.5.19/20] KDE panel (kicker) not starting up

[Adam Trilling]

Make sure you have read and write perms on your home directory.  I had
that happen due to a misplaced chown -R once.

This is not a kernel question, however, and probably shouldn't be on this
list.

adam

On Mon, 3 Jun 2002 bvermeul@devel.blackstar.nl wrote:

> The KDE panel (kicker) from KDE 3.0 (RedHat 7.3 issue) refuses to start
> up. I get a SIGPIPE in DCOP, and a SIGSEGV in kicker.
> This looks like something changed in regards to permissions, 'cause when I
> start KDE as root, it does work.
>
> Does anyone know what's happening?
>
> Regards,
>
> Bas Vermeulen
>
> --
> "God, root, what is difference?"
> 	-- Pitr, User Friendly
>
> "God is more forgiving."
> 	-- Dave Aronson
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>


Adam Trilling
agt10@columbia.edu


char m[9999],*n[99],*r=m,*p=m+5000,**s=n,d,c;main(){for(read(0,r,4000);c=*r;
r++)c-']'||(d>1||(r=*p?*s:(--s,r)),!d||d--),c-'['||d++||(*++s=r),d||(*p+=c==
'+',*p-=c=='-',p+=c=='>',p-=c=='<',c-'.'||write(2,p,1),c-','||read(2,p,1));}

Re: [2.5.19/20] KDE panel (kicker) not starting up

[Andrey Panin]

[-- Attachment #1: Type: text/plain, Size: 254 bytes --]


On my machine kicker showed a message about inability to parse IIRC 
/proc/meminfo before dying, so the kernel can be involved.

-- 
Andrey Panin            | Embedded systems software engineer
pazke@orbita1.ru        | PGP key: wwwkeys.eu.pgp.net

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

Re: [2.5.19/20] KDE panel (kicker) not starting up

[bvermeul]

On Mon, 3 Jun 2002, Adam Trilling wrote:

> Make sure you have read and write perms on your home directory.  I had
> that happen due to a misplaced chown -R once.
> 
> This is not a kernel question, however, and probably shouldn't be on this
> list.

Everythink works using 2.5.17. So I think this *is* a kernel question.
I've had the same problem with 2.5.19 (and couldn't get 2.5.18 working 
properly)

Bas Vermeulen

-- 
"God, root, what is difference?" 
	-- Pitr, User Friendly

"God is more forgiving." 
	-- Dave Aronson

Re: [2.5.19/20] KDE panel (kicker) not starting up

[Diego Calleja]

On Mon, 3 Jun 2002 17:59:08 +0400
Andrey Panin <pazke@orbita1.ru> escribió:

> 
> On my machine kicker showed a message about inability to parse IIRC 
> /proc/meminfo before dying, so the kernel can be involved.

yes, /proc/meminfo might have changed?. i've a gnome applet which shows
cpu, mem and swap usage. Under 2.5 tree, i only can see the cpu usage.
Others doesn't work

Re: [2.5.19/20] KDE panel (kicker) not starting up

[Greg KH]

On Mon, Jun 03, 2002 at 08:34:44PM +0200, bvermeul@devel.blackstar.nl wrote:
> On Mon, 3 Jun 2002, Adam Trilling wrote:
> 
> > Make sure you have read and write perms on your home directory.  I had
> > that happen due to a misplaced chown -R once.
> > 
> > This is not a kernel question, however, and probably shouldn't be on this
> > list.
> 
> Everythink works using 2.5.17. So I think this *is* a kernel question.
> I've had the same problem with 2.5.19 (and couldn't get 2.5.18 working 
> properly)

Just to add one more "me too" here, I've seen the same thing here.

2.5.18 worked just fine from what I remember.

greg k-h

Re: [2.5.19/20] KDE panel (kicker) not starting up

[Dave Jones]

On Tue, Jun 04, 2002 at 08:49:45PM -0700, Greg KH wrote:
 > > Everythink works using 2.5.17. So I think this *is* a kernel question.
 > > I've had the same problem with 2.5.19 (and couldn't get 2.5.18 working 
 > > properly)
 > 
 > Just to add one more "me too" here, I've seen the same thing here.
 > 2.5.18 worked just fine from what I remember.

Wasn't this attributed to the /proc/meminfo format changing ?

        Dave

-- 
| Dave Jones.        http://www.codemonkey.org.uk
| SuSE Labs

Re: [2.5.19/20] KDE panel (kicker) not starting up

[bvermeul]

On Wed, 5 Jun 2002, Dave Jones wrote:

> On Tue, Jun 04, 2002 at 08:49:45PM -0700, Greg KH wrote:
>  > > Everythink works using 2.5.17. So I think this *is* a kernel question.
>  > > I've had the same problem with 2.5.19 (and couldn't get 2.5.18 working 
>  > > properly)
>  > 
>  > Just to add one more "me too" here, I've seen the same thing here.
>  > 2.5.18 worked just fine from what I remember.
> 
> Wasn't this attributed to the /proc/meminfo format changing ?

If it is, that doesn't explain why when using KDE as root everything works 
perfectly. That (at least in my eyes) can't be explained by a change in 
format in /proc/meminfo. I could be wrong of course.

Bas Vermeulen

-- 
"God, root, what is difference?" 
	-- Pitr, User Friendly

"God is more forgiving." 
	-- Dave Aronson

Re: [2.5.19/20] KDE panel (kicker) not starting up

[Melchior FRANZ]

* bvermeul@devel.blackstar.nl -- Tuesday 04 June 2002 07:14:20:
> * On Mon, 3 Jun 2002, Adam Trilling wrote:
> > Make sure you have read and write perms on your home directory.  I had
> > that happen due to a misplaced chown -R once.
> > 
> > This is not a kernel question, however, and probably shouldn't be on this
> > list.
> 
> Everythink works using 2.5.17. So I think this *is* a kernel question.

I don't have the slightest doubt that it is a kernel bug: I observed the
same with the /dev/hdc device (the CDROM). Playing Audio-CD's doesn't work
since 2.5.19. It worked for years now with the same permissions, and giving
more liberal rights doesn't help either. It always returns with EACCES!

  open("/dev/cdrom", O_RDONLY|O_NONBLOCK) = 3
  ioctl(3, CDROMVOLREAD, 0xbffff1f8)      = -1 EACCES (Permission denied)
  ioctl(3, CDROMSUBCHNL, 0xbffff1fc)      = -1 EACCES (Permission denied)

It works, however, for root! Could this be some broken capability
settings? 

m.



PS: Sorry if this message creates a new thread. I'm not subscribed to
    the list and read it via usenet-mirror.