Netspeed does not keep it's Desklet position when the dock starts.

Bug #705234 reported by towheedm
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cairo-Dock Plug-ins
Incomplete
Low
Fabounet

Bug Description

I normally keep the desklet's position at x=0 and y=-96. The dock is set to startup automatically on login with the no OpenGL option. After the dock starts the desklet's position is set to x=-623 and y=1. If the dock is stopped and restarted within the session, these values are set to x=191 and y=1. These values were taken from the netspeed.conf file. This happens even if the lock position option is set.

Tried it with both the stable 2.2.0 and the 2.2.1~0beta1 releases.

I'm using Ubuntu Maverick and my screen is set to 1280x1024. The debug.txt file is attached.

Revision history for this message
towheedm (towheedm) wrote :
Revision history for this message
Matthieu Baerts (matttbe) wrote :

Hello,

Thank you for this bug report!
Does it happen only with Netspeed?

What's your WM? (Compiz, Metacity, Kwin?)

What does it happen if you set these values to x=191 and y=1 and then you stop and restart the dock?
Is the desklet out of the screen? Can you try with another WM? (e.g. with metacity: metacity --replace)

Changed in cairo-dock-plug-ins:
assignee: nobody → Fabounet (fabounet03)
importance: Undecided → Low
Revision history for this message
towheedm (towheedm) wrote :

The WM I'm using is Compiz. I did the following according to your request:

1. Set x=191 and y=1. This was done by changing the values directly in the netspeed.conf file. Restarted the dock and the desklet remained at the set position. Did it 3 times and the position did not change.

2. Logged out of the session and then back in. The position changed to x=121 and y=1. Restarted the dock several times and the position remained at x=121 and y=1.

3. Set the WM to Metacity. Set the position to x=191 and y=1. Restarted the dock several times and the desklet remained at the set position.

4. Logged out of the session and back in. The desklet position remained at x=191 and y=1. Did this twice and the position remained at 191,1.

5. Switched the WM back to Compiz. Restarted the dock and the desklet position remained at 191,1.

6. Logged out and back in. The position changed to x=166 and y=1.

7. Left the position set to 166,1 and logged out and back in. The position changed to x=24 and y=1.

8. Left the position set to 24,1 and logged out and back in. The position changed to x=0 and y=1.

9. Left the position set to 0,1 and logged out and back in. The position changed to x=166 and y=1.

10. Left the position set to 166,1 and logged out and back in. The position changed to x=0 and y=1.

11. Left the position set to 0,1 and logged out and back in. The position changed to x=166 and y=1.

I also have the Network-Monitor, Disks and System Monitor set as desklets. Their respective positions remain the same always.

Note also that I use CD 2.2.0 in Karmic and netspeed remains at the set position of x=0 and y=-96 (lower left edge of the screen).

Revision history for this message
Fabounet (fabounet03) wrote : Re: [Bug 705234] Re: Netspeed does not keep it's Desklet position when the dock starts.

thanks a lot for these tests !
so it seems only Compiz is concerned by this problem.
where are your other desklets ? I think that maybe they overlap on startup
(because the screen size is not correct before Compiz has fully started).
Metacity probably starts faster, that would explain why the problem doesn't
occur with it.

2011/1/21 towheedm <email address hidden>

> The WM I'm using is Compiz. I did the following according to your
> request:
>
> 1. Set x=191 and y=1. This was done by changing the values directly in
> the netspeed.conf file. Restarted the dock and the desklet remained at
> the set position. Did it 3 times and the position did not change.
>
> 2. Logged out of the session and then back in. The position changed to
> x=121 and y=1. Restarted the dock several times and the position
> remained at x=121 and y=1.
>
> 3. Set the WM to Metacity. Set the position to x=191 and y=1.
> Restarted the dock several times and the desklet remained at the set
> position.
>
> 4. Logged out of the session and back in. The desklet position
> remained at x=191 and y=1. Did this twice and the position remained at
> 191,1.
>
> 5. Switched the WM back to Compiz. Restarted the dock and the desklet
> position remained at 191,1.
>
> 6. Logged out and back in. The position changed to x=166 and y=1.
>
> 7. Left the position set to 166,1 and logged out and back in. The
> position changed to x=24 and y=1.
>
> 8. Left the position set to 24,1 and logged out and back in. The
> position changed to x=0 and y=1.
>
> 9. Left the position set to 0,1 and logged out and back in. The
> position changed to x=166 and y=1.
>
> 10. Left the position set to 166,1 and logged out and back in. The
> position changed to x=0 and y=1.
>
> 11. Left the position set to 0,1 and logged out and back in. The
> position changed to x=166 and y=1.
>
> I also have the Network-Monitor, Disks and System Monitor set as
> desklets. Their respective positions remain the same always.
>
> Note also that I use CD 2.2.0 in Karmic and netspeed remains at the set
> position of x=0 and y=-96 (lower left edge of the screen).
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/705234
>
> Title:
> Netspeed does not keep it's Desklet position when the dock starts.
>
> Status in Cairo-Dock : Plug-ins:
> New
>
> Bug description:
> I normally keep the desklet's position at x=0 and y=-96. The dock is
> set to startup automatically on login with the no OpenGL option.
> After the dock starts the desklet's position is set to x=-623 and y=1.
> If the dock is stopped and restarted within the session, these values
> are set to x=191 and y=1. These values were taken from the
> netspeed.conf file. This happens even if the lock position option is
> set.
>
> Tried it with both the stable 2.2.0 and the 2.2.1~0beta1 releases.
>
> I'm using Ubuntu Maverick and my screen is set to 1280x1024. The
> debug.txt file is attached.
>
>
>

Revision history for this message
towheedm (towheedm) wrote :

The System Monitor is located at the lower right edge of the screen, Network-Monitor is located at the upper left edge of the screen and the Disk desklet is located just below the Network-Monitor.

I don't think it's an overlap problem because it happens even with netspeed as the only desklet running.

Revision history for this message
towheedm (towheedm) wrote :

Did some more testing, this one may be a security issue. Can't say if it's the dock or Maverick yet. Here's what I just did.

1. Since it seems that the x and y values in the netspeed.conf file is being changed, I decided to make the file read-only. Did this with "chmod -w ~/.config/cairo-dock/current_theme/plug-ins/netspeed/netspeed.conf".

2. Verified the change was successful with "ls -all ~/.config/cairo-dock/current_theme/plug-ins/netspeed/netspeed.conf". It returned "-r--r--r-- 1 towheed towheed 3632 2011-01-21 08:16 /home/towheed/.config/cairo-dock/current_theme/plug-ins/netspeed/netspeed.conf".

3. Restarted the dock, netspeed position changed to x=191 and y=1. Checked the permissions on the conf file and it reverted to a read and write permission (-rw-r--r-- 1 towheed towheed 3632 2011-01-21 08:18 /home/towheed/.config/cairo-dock/current_theme/plug-ins/netspeed/netspeed.conf).

Revision history for this message
Fabounet (fabounet03) wrote :

I wonder if the file is not overwritten.
could you please try to change something in the comments (the lines that
starts with a #, except the first line)
and see if this changes or not ? thanks!

2011/1/21 towheedm <email address hidden>

> Did some more testing, this one may be a security issue. Can't say if
> it's the dock or Maverick yet. Here's what I just did.
>
> 1. Since it seems that the x and y values in the netspeed.conf file is
> being changed, I decided to make the file read-only. Did this with
> "chmod -w ~/.config/cairo-dock/current_theme/plug-
> ins/netspeed/netspeed.conf".
>
> 2. Verified the change was successful with "ls -all ~/.config/cairo-
> dock/current_theme/plug-ins/netspeed/netspeed.conf". It returned "-r--r
> --r-- 1 towheed towheed 3632 2011-01-21 08:16 /home/towheed/.config
> /cairo-dock/current_theme/plug-ins/netspeed/netspeed.conf".
>
> 3. Restarted the dock, netspeed position changed to x=191 and y=1.
> Checked the permissions on the conf file and it reverted to a read and
> write permission (-rw-r--r-- 1 towheed towheed 3632 2011-01-21 08:18
> /home/towheed/.config/cairo-dock/current_theme/plug-
> ins/netspeed/netspeed.conf).
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/705234
>
> Title:
> Netspeed does not keep it's Desklet position when the dock starts.
>
> Status in Cairo-Dock : Plug-ins:
> New
>
> Bug description:
> I normally keep the desklet's position at x=0 and y=-96. The dock is
> set to startup automatically on login with the no OpenGL option.
> After the dock starts the desklet's position is set to x=-623 and y=1.
> If the dock is stopped and restarted within the session, these values
> are set to x=191 and y=1. These values were taken from the
> netspeed.conf file. This happens even if the lock position option is
> set.
>
> Tried it with both the stable 2.2.0 and the 2.2.1~0beta1 releases.
>
> I'm using Ubuntu Maverick and my screen is set to 1280x1024. The
> debug.txt file is attached.
>
>
>

Revision history for this message
towheedm (towheedm) wrote :

The file is not being overwritten. The added comments remained in the modified file. The only thing that changes are the x= and y= lines.

Another thing is that the owner of the netspeed.conf file is being changed to the user that the dock is run as, ie: sudo cairo-dock -c changes the owner of the file to root. Similarly sudo -u username cairo-dock -c changes the owner to the specified username.

Revision history for this message
towheedm (towheedm) wrote :

Another thing is that the file is not touched if netspeed is set to be an icon in the dock.

Revision history for this message
Matthieu Baerts (matttbe) wrote :

Hello! (and sorry for this very long delay!)

Do you still have this bug with the latest stable version? (3.3.0)

Changed in cairo-dock-plug-ins:
status: New → Incomplete
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.