Bug 440279
| Summary: | PK "Transaction Error" dialog doesn't put its details in a scrollable box | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Will Woods <wwoods> | ||||||
| Component: | gnome-packagekit | Assignee: | Robin Norwood <robin.norwood> | ||||||
| Status: | CLOSED NEXTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | low | Docs Contact: | |||||||
| Priority: | low | ||||||||
| Version: | rawhide | CC: | lordmorgul | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | All | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2008-05-06 17:05:19 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: | |||||||||
| Attachments: |
|
||||||||
|
Description
Will Woods
2008-04-02 16:08:03 UTC
Created attachment 300088 [details]
Screenshot of dialog going off the bottom of the screen.
Hmmm. Do you think we should put the backtrace in a treeview or something? Or just truncate it? Treeview or something. There might have been conflicts with other packages, but I'll never know, because the window was cut off while it was still listing all the gnome-applet conflicts. We need to be able to scroll through the entire output. Ideally it'd be something like: Details > The following packages had problems: uw-imap, cyrus-imapd: file conflicts > gnome-applets-$v-$r.$a, gnome-applets-$v2-$r2.$a2: file conflicts > hal: corrupt file > Where the '>' represents the arrow thingy to expand details. The package-specific details would contain all the error messages for (I need to learn gtk terminology better, sorry) The package name(s) listed would be: 1) Two simple package names, if the two affected packages have different names 2) Two full package identifiers, if the package names are the same, or 3) The simple package name, if the problem only affects one package But, yeah, that's much trickier. The immediate need is to be able to read the entire message so I can figure out which packages had problems. Created attachment 302275 [details]
what's in git
This is what I've added to git master - it's not quite a sane UI yet (we have
to work on the backend for that) but at least the dialog is not huuuuuge now.
*** Bug 443278 has been marked as a duplicate of this bug. *** |