Bug 380994 - Poor displaying of errors from packagekit
Summary: Poor displaying of errors from packagekit
Status: RESOLVED FIXED
Alias: None
Product: frameworks-kirigami
Classification: Frameworks and Libraries
Component: general (other bugs)
Version First Reported In: Master
Platform: Arch Linux Linux
: NOR normal
Target Milestone: Not decided
Assignee: Marco Martin
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-06-08 21:27 UTC by Matthew Trescott
Modified: 2017-06-19 16:04 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Screenshot of bug (171.77 KB, image/png)
2017-06-08 21:27 UTC, Matthew Trescott 		Details
journald record (33.87 KB, text/plain)
2017-06-09 00:59 UTC, Matthew Trescott 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Matthew Trescott 2017-06-08 21:27:56 UTC 
Created attachment 106002 [details]
Screenshot of bug

In this case, the error was about conflicting files, but the popup gave no sort of indication...
Comment 1 Aleix Pol 2017-06-09 00:31:11 UTC 
Can you reproduce? If so, it would be useful if you could run discover from the console and tell me what output you get there.
Comment 2 Matthew Trescott 2017-06-09 00:59:09 UTC 
Created attachment 106004 [details]
journald record

I got the output from journald. Some of this is me using pkcon update, some is from Discover. I removed irrelevant parts from other processes.
Comment 3 Marco Martin 2017-06-09 10:34:43 UTC 
Git commit 59670d351219fbe51640a9a1a359ce6f6e972be1 by Marco Martin.
Committed on 09/06/2017 at 10:34.
Pushed by mart into branch 'master'.

Passive notifications can be 4 lines

also, elide when they are really too big

M  +2    -1    examples/gallery/contents/ui/gallery/ButtonGallery.qml
M  +3    -1    src/controls/templates/private/PassiveNotification.qml

https://commits.kde.org/kirigami/59670d351219fbe51640a9a1a359ce6f6e972be1
Comment 4 Aleix Pol 2017-06-19 16:04:55 UTC 
I confirm this error message looks okay now. Thanks marco!