Bug 176130
| Summary: | Create new folder dialog doesn't take the currently highlighted folder as the default | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 4 | Reporter: | Suzanne Hillman <shillman> |
| Component: | evolution | Assignee: | Matthew Barnes <mbarnes> |
| Status: | CLOSED UPSTREAM | QA Contact: | Ben Levenson <benl> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.0 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2006-12-31 02:47:50 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Suzanne Hillman
2005-12-19 17:49:53 UTC
Changing to note x86_64, but I suspect that this one is not specific to the viper I'm testing it on, nor specific to x86_64. Works for me on my test x86_64 box, running RHEL4 U2 with evolution upgraded to evolution-2.0.2-25 Hmm. With further investigation, this appears to be only a problem if I've a top level folder like "On This Computer" selected and try to create a new folder. The subfolders of "On This Computer" seem to work fine if selected and then one tries to create a new folder, and I have verified that creating a folder under "On This Computer" does actually work (so it's not a result of the problem where it lets you try to create folders where you aren't actually able to do so). Reproduced as you describe on RHEL4 U2; not a regression; reassigning as a RHEL4 bug. This problem was also reported upstream: http://bugzilla.gnome.org/show_bug.cgi?id=339629 I investigated this some months ago and found that the problem does not appear trivial to fix as I had originally thought. It looks like it will involve changing libcamel in ways that may break its API. Since this bug was never proposed for a RHEL-4 update, I'm resolving this as UPSTREAM. Please refer to the upstream bug report for further updates. |