Opened 8 years ago

Closed 8 years ago

#4905 closed defect (invalid)

Display icon invisible

Reported by: SAMdroid Owned by:
Priority: Normal Milestone: Unspecified
Component: Sugar Version: Unspecified
Severity: Minor Keywords:
Cc: Quozl Distribution/OS: OLPC
Bug Status: Unconfirmed


The display icon in the frame takes up space and is clickable, however it is invisible!

Tested on xo4 with olpc os 14 and sugar 0.107.0.olpc.

From the log: "No icon with the name brightness-100 was found in the theme"

Please see the picture attached.

Attachments (1)

2015-11-01-071706.jpg (302.7 KB) - added by SAMdroid 8 years ago.
Picture of the issue

Download all attachments as: .zip

Change History (6)

Changed 8 years ago by SAMdroid

Picture of the issue

comment:1 Changed 8 years ago by ignacio

(Just for be sure)

Can you check if brightness-100.svg is in /usr/share/icons/sugar/scalable/device in the XO, and check if its on sugar-build/build/out/share/icons/sugar/scalable/device (or something like that, I don't have sugar-build right now) (the file should be there)

comment:2 Changed 8 years ago by SAMdroid

There is no icon file on the xo. However there is inside sugar-build. Maybe a packaging error?

comment:3 Changed 8 years ago by ignacio

Can you attach the output of

# yum install tree
tree /usr/share/icons/sugar/scalable

it could be useful for compare sugar-build version and the xo one

comment:4 Changed 8 years ago by quozl

Assuming you used the packages in the way you described in #4903, you've merely forgotten to include the sugar-artwork package, which has these icons. Please try upgrading this package to match the others, restart, and see if the icon is present.

If that solves the problem, then perhaps Sugar needs to use some default icon for missing icon?

Last edited 8 years ago by quozl (previous) (diff)

comment:5 Changed 8 years ago by SAMdroid

  • Resolution set to invalid
  • Status changed from new to closed

No, sugar should not aim to deal with then the user circumvents normal methods (eg. dnf update) and ends up with a mucked up system. It's very valid to assume that the user can actually use a package manager correctly, or that the packager set the right deps.

So yeah, it was my fault for not downloading the right packages.

Note: See TracTickets for help on using tickets.