adesklets don't work with the -w option

[Gianluca Borello]

Binary package hint: adesklets

When i start adesklets 0.6.1-2build1 using the -w parameter, it says:

gighi@sedonc:~$ adesklets -w nautilus
ERROR: User name does not exist.
********* simple selection ********* ********* selection by list *********
-A all processes -C by command name
-N negate selection -G by real group ID (supports names)
-a all w/ tty except session leaders -U by real user ID (supports names)
-d all except session leaders -g by session OR by effective group name
-e all processes -p by process ID
T all processes on this terminal -s processes in the sessions given
a all w/ tty, including other users -t by tty
g OBSOLETE -- DO NOT USE -u by effective user ID (supports names)
r only running processes U processes for specified users
x processes w/o controlling ttys t by tty
*********** output format ********** *********** long options ***********
-o,o user-defined -f full --Group --User --pid --cols --ppid
-j,j job control s signal --group --user --sid --rows --info
-O,O preloaded -o v virtual memory --cumulative --format --deselect
-l,l long u user-oriented --sort --tty --forest --version
-F extra full X registers --heading --no-heading --context
                    ********* misc options *********
-V,V show version L list format codes f ASCII art forest
-m,m,-L,-T,H threads S children in sum -y change -l format
-M,Z security data c true command name -c scheduling class
-w,w wide output n numeric WCHAN,UID -H process hierarchy

The problem is in /usr/share/adesklets/adesklets_frontend.sh, line 214:

test -z "`ps -u $UID -U $UID -o comm | sed -n "/$2/p"`" || break

The script look at the variable UID, which is not exported by default in the
environment.

Look at this:
gighi@sedonc:~$ export UID && adesklets --nautilus -w nautilus
gighi@sedonc:~$

Now it works.
What can we do to avoid this?
Replacing $UID with $USER could be a good idea? ($USER is exported by default in Ubuntu).

PS: Sorry for my poor english :-)

[Daniel T Chen (crimsun)]

Is this symptom still reproducible in 8.10 beta?

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.