Bug 1329946 - Missing buttons on main window
Summary: Missing buttons on main window
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: hamster-time-tracker
Version: 23
Hardware: x86_64
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Ankur Sinha (FranciscoD)
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-25 07:32 UTC by Miklos Szeredi
Modified: 2016-12-20 20:07 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-12-20 20:07:51 UTC
Type: Bug


Attachments (Terms of Use)
screenshot (8.95 KB, image/png)
2016-04-25 07:32 UTC, Miklos Szeredi
no flags Details

Description Miklos Szeredi 2016-04-25 07:32:18 UTC
Created attachment 1150262 [details]
screenshot

Description of problem:
I cannot start/stop work with hamster as the buttons to do so seem to be missing.

Version-Release number of selected component (if applicable):
hamster-time-tracker-2.0-0.7.rc1.fc23.noarch

How reproducible:


Steps to Reproduce:
1. Start hamster
2.
3.

Actual results:
No starts/top buttons

Expected results:
start/stop buttons

Additional info:

Comment 1 Raphael Groner 2016-04-25 07:43:20 UTC
What desktop do you use? Gnome, Plasma, other?

Comment 2 Miklos Szeredi 2016-04-25 07:49:36 UTC
The default one that fedora installed.  Looks like gnome:

mszeredi  2485  0.3  3.2 2161016 392900 tty2   SLl+ Apr22  12:36 /usr/bin/gnome-shell

Comment 3 Raphael Groner 2016-04-25 08:28:25 UTC
Do other Gnome / Gtk3 applications show all window elements? Maybe your theme installation is somehow f*cked up.

Comment 4 Miklos Szeredi 2016-04-25 08:39:48 UTC
Everything else works fine.  This is the default theme.

I installed fedora last week and didn't do much tweaking (one thing that I did tweak is "scaling factor" but resetting this doesn't seem to fix the issue).

Comment 5 Raphael Groner 2016-04-25 09:00:15 UTC
Can you try in Xfce, to test if it's Gtk3 related? Xfce bases mostly still on Gtk2.

Comment 6 Ankur Sinha (FranciscoD) 2016-04-25 09:13:59 UTC
I think this is how the current UI is - there's work being done on porting it all to gtk3, but a new release hasn't yet been made with further improvements. Checkout: https://github.com/projecthamster/hamster/issues/310

Comment 7 Miklos Szeredi 2016-04-25 09:46:03 UTC
Okay, so this is a half finished port to gtk3.

Possible fix is to downgrade to gtk2 version until the port is sufficiently usable?

Comment 8 Raphael Groner 2016-04-25 09:58:10 UTC
(In reply to Miklos Szeredi from comment #7)
> Okay, so this is a half finished port to gtk3.
> 
> Possible fix is to downgrade to gtk2 version until the port is sufficiently
> usable?

Hmm, bad news. We can not downgrade to an older gtk2 commit or release. We saw a lot of security issues, that's the reason I updated the package. Raising severity.

Comment 9 Felix Schwarz 2016-04-25 10:44:10 UTC
(In reply to Miklos Szeredi from comment #7)
> Okay, so this is a half finished port to gtk3.

Yes. The upstream plan was that time tracking actions should happen in a way which is more integrated with the desktop. There are a couple of shell plugins (IIRC some are also in Fedora) which allow you to start/stop time tracking. However even with a shell plugin the new version does not provide all features of the old one (mostly when it comes to the activity overview/filtering).

I'm working on bringing back the old ui (either as a separate plugin or directly integrated upstream) but my time is very limited so there is no ETA).

> Possible fix is to downgrade to gtk2 version until the port is sufficiently
> usable?

At least for individual users, yes. dnf downgrade should work.

(In reply to Raphael Groner from comment #8)
> Hmm, bad news. We can not downgrade to an older gtk2 commit or release. We
> saw a lot of security issues, that's the reason I updated the package.

To be fair I don't think these were highly important securiy issues. More like "hamster would crash for unexpected/broken items in the local sqlite db" which happened sometimes due to bugs in hamster itself.

Comment 10 Raphael Groner 2016-04-25 11:22:26 UTC
(In reply to Felix Schwarz from comment #9)
…
> To be fair I don't think these were highly important securiy issues. More
> like "hamster would crash for unexpected/broken items in the local sqlite
> db" which happened sometimes due to bugs in hamster itself.

Sure. But we'll obviously run into the same bugs again with new reports, I do not want to confuse users with useless down- and upgrades. That's heavily discouraged and unlikely in Fedora.

Comment 11 Fedora End Of Life 2016-11-25 07:27:54 UTC
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 12 Fedora End Of Life 2016-12-20 20:07:51 UTC
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.