After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 721759 - The 'Star' and the menu in the conversation isn't show
The 'Star' and the menu in the conversation isn't show
Status: RESOLVED FIXED
Product: geary
Classification: Other
Component: conversations
master
Other Mac OS
: Normal normal
: 0.6.0
Assigned To: Geary Maintainers
Geary Maintainers
Depends on: 720771
Blocks:
 
 
Reported: 2014-01-08 00:16 UTC by Yosef Or Boczko
Modified: 2014-01-20 19:43 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Screenshot (216.58 KB, image/png)
2014-01-08 00:17 UTC, Yosef Or Boczko 		Details

Description Yosef Or Boczko 2014-01-08 00:16:02 UTC 
With gtk+ from git, the Star button and the menu button
in each conversation isn't show.
When the mouse hover on the button, I see just the border
of the button.

See the screenshot.
Comment 1 Yosef Or Boczko 2014-01-08 00:17:06 UTC 
Created attachment 265621 [details]
Screenshot
Comment 2 Jim Nelson 2014-01-08 00:44:06 UTC 
Have you pulled from master lately?  I think this was fixed with bug #721000.
Comment 3 Yosef Or Boczko 2014-01-08 00:51:18 UTC 
In fact, this happened more than three month.
A few weeks, instead to see nothing, I was see
a non-image icon instead the starred-symbolic and the
go-down-symbolic.
Today, after pulled the commits from bug #721000,
I see nothing again
Comment 4 Jim Nelson 2014-01-08 20:03:05 UTC 
I wonder if the image files aren't being installed.  Are you running from a build directory or when it's installed?  If you run from the build directory, do you seem them?
Comment 5 Yosef Or Boczko 2014-01-08 20:39:26 UTC 
(In reply to comment #4)
> I wonder if the image files aren't being installed.  Are you running from a
> build directory or when it's installed?  If you run from the build directory,
> do you seem them?

I sure the image files are installed.
I installed geary (from git master) to the main system (ArchLinux, PKGBUILD).
Comment 6 Jim Nelson 2014-01-08 20:45:03 UTC 
Can you build Geary from tarball or git and run from the build directory, i.e.

$ ./geary
Comment 7 Yosef Or Boczko 2014-01-08 20:59:24 UTC 
(In reply to comment #6)
> Can you build Geary from tarball or git and run from the build directory, i.e.
> 
> $ ./geary

When I mean I see a bug, this mean I see the bug.
Of course I run geary build from git, this happen also when
I launch geary from the build directory, and also after
the installing, when I launch geary from gnome-shell.
Comment 8 Jim Nelson 2014-01-10 20:59:36 UTC 
I ask because Geary actually picks load paths at runtime for resources depending on whether it's executing from the build directory or install directory.

Do you see anything in the log about this?  Geary should display a warning message when it fails to load a resource.
Comment 9 Yosef Or Boczko 2014-01-14 07:15:50 UTC 
I not see anything in the log about this.
Comment 10 Jim Nelson 2014-01-16 19:44:19 UTC 
If you switch to English (or another LTR language), does the problem persist?
Comment 11 Yosef Or Boczko 2014-01-16 20:50:32 UTC 
(In reply to comment #10)
> If you switch to English (or another LTR language), does the problem persist?

Yes, also in LTR the problem exist.
Comment 12 Jim Nelson 2014-01-20 19:43:19 UTC 
Yosef, I'm assuming that the commit to bug #720771 fixes your problem, so closing.  If you still see the issue, please let us know.