First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 98677
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Jonathan Smith <smithj@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Thomas Tuttle <gentoo@ttuttle.net>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 98677 depends on: Show dependency tree
Bug 98677 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2005-07-11 07:41 0000
The current version of 3ddesktop (http://desk3d.sourceforge.net/) has a bug in
it where every other time you run 3ddesk with the --nozoom option and a
--goto(row,column,left,right,up,down) option, it doesn't exit automatically. 
(It acts as if you had passed --dontexit.)

There is a bug fix in versions 0.2.8 and above.  I am running 0.2.9, and it
seems perfectly stable.  Can someone please create an ebuild (probably just a
version bump would be sufficient, nothing much has changed) for the new version?

Thanks.

Reproducible: Always
Steps to Reproduce:
1. Emerge 3ddesktop-0.2.7.
2. Start the daemon (`3ddeskd`).
3. Run 3ddesk --nozoom --gotoright several times.

Actual Results:  
Every other time you run `3ddesk --nozoom --gotoright`, it doesn't automatically
return (as if you used the options `3ddesk --nozoom --gotoright --dontexit`). 
If you don't pass --nozoom, it works fine.  ('--gotoright' can be substituted
with any of the '--goto...' options.)

Expected Results:  
It should exit on every execution of `3ddesk --nozoom --gotoright`.

The new version is available from the same place as the old, and appears to be
just a bugfix/enhancement release with no substantial changes.  It should be
able to work with the same ebuild.

------- Comment #1 From Thomas Tuttle 2005-07-11 07:43:51 0000 -------
Whoops, I just noticed that 0.2.9 is in portage already.  I guess it needs to
be
marked stable then.

------- Comment #2 From Jonathan Smith 2005-07-11 10:13:40 0000 -------
0.2.9 was only added to the tree 11 days ago. policy states that 30 days must
elapse before marking stable unless a major bug or security problem is found. 

since 0.2.8 solves this problem, i will mark it stable, even though it is
technically 3 days early

x86, amd64 stable, and ppc is currently testing

First Last Prev Next    No search results available      Search page      Enter new bug