transmission doesn't remember maximized state

Bug #385982 reported by Jackflap
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
One Hundred Papercuts
Invalid
Undecided
Unassigned
Transmission
Fix Released
Unknown
transmission (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: transmission

I start transmission up, maximize it and close it.

When I start transmission up again, it doesn't start up maximized. It always reverts to the default size (which is something like half the screen), when you close it.

Revision history for this message
Michael Budde (mbudde) wrote :

Transmission does remember window size but not maximized state.

summary: - transmission doesn't remember window size when closed
+ transmission doesn't remember maximized state
Revision history for this message
Michael Budde (mbudde) wrote :

Just confirmed that this bug is present in karmic. I'm working on fixing this.

Changed in transmission (Ubuntu):
assignee: nobody → Michael Budde (mbudde)
status: New → Confirmed
Revision history for this message
Mat Tomaszewski (mat.t.) wrote :

This is an app-specific, corner issue, not really a papercut

Changed in hundredpapercuts:
status: New → Invalid
Revision history for this message
Michael Budde (mbudde) wrote :

Bug is fixed upstream.

Changed in transmission (Ubuntu):
assignee: Michael Budde (mbudde) → nobody
Revision history for this message
Jackflap (deriziotis) wrote :

Thanks for the fix Michael.

Mat, I don't see how this isn't a papercut, the definition is clear:

"A bug that will improve user experience if fixed, is small enough for users to become habituated to it, and is trivial to fix."

This bug clearly fits all 3 aspects of the definition.

Changed in transmission:
status: Unknown → Fix Released
Revision history for this message
Jackflap (deriziotis) wrote :

I've just seen your mail to ubuntu-devel-discuss redefining what a papercut is:

http://<email address hidden>/msg08529.html

Revision history for this message
Mat Tomaszewski (mat.t.) wrote : Re: [Bug 385982] Re: transmission doesn't remember maximized state

Jackflap wrote:
> Thanks for the fix Michael.
>
> Mat, I don't see how this isn't a papercut, the definition is clear:
>
> "A bug that will improve user experience if fixed, is small enough for
> users to become habituated to it, and is trivial to fix."
>
> This bug clearly fits all 3 aspects of the definition.
>
>
Not sure which definition you're referring to, please find the
guidelines here:

https://launchpad.net/hundredpapercuts

We would love to fix all these usability bugs within all the apps, but
for this project we'd like to concentrate on a system-wide bugs, rather
than those specific to certain apps–there's simply too many of them!

Thanks,
M.

Revision history for this message
Mat Tomaszewski (mat.t.) wrote :

Thanks, by the way it's good to see this fixed so quickly :)

Revision history for this message
Jackflap (deriziotis) wrote :

2009/6/12 Mat Tomaszewski <email address hidden>

> Jackflap wrote:
> > Thanks for the fix Michael.
> >
> > Mat, I don't see how this isn't a papercut, the definition is clear:
> >
> > "A bug that will improve user experience if fixed, is small enough for
> > users to become habituated to it, and is trivial to fix."
> >
> > This bug clearly fits all 3 aspects of the definition.
> >
> >
> Not sure which definition you're referring to, please find the
> guidelines here:
>
> https://launchpad.net/hundredpapercuts
>
> We would love to fix all these usability bugs within all the apps, but
> for this project we'd like to concentrate on a system-wide bugs, rather
> than those specific to certain apps–there's simply too many of them!
>
> Thanks,
> M.
>

http://blog.davebsd.com/2009/06/10/one-hundred-paper-cuts/

I suppose it's a good thing, but I can't think of any papercuts which are
'system-wide' rather than 'app-specific', so I'm hoping one day in the
future the project will have resources to address some app-specific ones as
well.

Alex

Revision history for this message
Michael Budde (mbudde) wrote :

BTW, I didn't fix this bug, the upstream author did, so credit goes to him
for fixing it so fast :-)

Revision history for this message
Charles Kerr (charlesk) wrote :

Ha! Thanks for the hat tip.

I've been working through the solvable Transmission issues in Launchpad this week. I think the next release -- 1.72 -- will close 9 or 10 Launchpad tickets. :)

Changed in transmission (Ubuntu):
status: Confirmed → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package transmission - 1.72-1ubuntu1

---------------
transmission (1.72-1ubuntu1) karmic; urgency=low

  * Merge from debian unstable (LP: #388377), remaining changes:
    - debian/control:
      + Added replaces & provides clutch (now included as part of transmission).
      + add quilt, liblaunchpad-integration and libtool to Build-Depends
    - debian/rules:
      + Create a PO template during package build.
      + re-enable quilt
      + run autoreconf for launchpad-integration
    - debian/patches/01_lpi.patch:
      + Integrate Transmission with Launchpad
    - debian/patches/20_add_X-Ubuntu-Gettext-Domain.diff:
      + Add X-Ubuntu-Gettext-Domain to .desktop file.
  * Closes Launchpad bugs:
    - Use tooltip to notify user of added torrent (LP: #217171)
    - Transmission forgets torrent when adding several (LP: #259123)
    - Unable to sort files in torrent by Progress, Download nor Priority.
      (LP: #300359)
    - "Revert" and "Remove" uses same alt-key in Torrent Tracker Details
      (LP: #311064)
    - transmission crashed with SIGSEGV in g_closure_invoke() (LP: #334104)
    - Bring transmission to the top when adding a torrent (LP: #353777)
    - Focus should not be on "Don't ask me again" when I quit Transmission
      (LP: #359268)
    - [karmic] removing download items makes property window useless
      (LP: #385334)
    - transmission doesn't remember maximized state (LP: #385982)
    - Transmission 1.71 (8646) crashes when changing download speed
      (LP: #386877)
    - transmission: event.c:875: timeout_next: Assertion `tv->tv_usec >= 0'
      failed. (LP: #387564)

transmission (1.72-1) unstable; urgency=low

  * new upstream release: (closes:#533423)
    - Can now sort the file list by priority, download, and completeness
      (closes: #517872)
    - fixed race condition adding file from browser (closes: #500195)
  * debian/control: policy 3.8.2 (no changes)

 -- Krzysztof Klimonda <email address hidden> Tue, 16 Jun 2009 02:41:48 +0200

Changed in transmission (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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