Bug 730353 - no default values
Summary: no default values
Alias: None
Product: Fedora
Classification: Fedora
Component: thunar-volman
Version: 15
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Christoph Wickert
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2011-08-12 15:10 UTC by Heiko Adams
Modified: 2012-08-07 19:48 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2012-08-07 19:48:40 UTC

Attachments (Terms of Use)
screenshot (31.74 KB, image/png)
2011-08-12 15:10 UTC, Heiko Adams
no flags Details

Description Heiko Adams 2011-08-12 15:10:10 UTC
Created attachment 518047 [details]

Description of problem:
After installing thunar-volman and opening these settings window there aren't any default values set.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. install thunar-volman
2. open volume settings
Actual results:
no default values for commands to execute i.e. a printer is connected are set

Expected results:
default values should be set for all options even if the option is disabled.

Additional info:

Comment 1 Kevin Fenzi 2011-08-12 19:12:28 UTC
What should be the default value that you would expect there? 

It's basically anything the end user wants when a printer is attached. 
There's not much way of knowing what they might want...

Comment 2 Heiko Adams 2011-08-12 19:27:13 UTC
AFAIR there haven been default values at least on Xfce 4.6. For a printer it makes sense i.e. to install this printer if it gets connected like windows does.

Comment 3 Kevin Fenzi 2011-08-12 19:41:59 UTC
Cups should take care of that automatically. It did here without thunar-volman getting involved at all.

Comment 4 Fedora End Of Life 2012-08-07 19:48:42 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:

Note You need to log in before you can comment on or make changes to this bug.