I am seeing issues with dialogue boxes not showing lines around boxes as they should and even complete boxes appearing to disappear because of this...
It seems like an icon issue but I cannot decipher what is missing or has been removed
Could use an assist on this one...
I will get an image in a minute to show what I mean
This is what it is supposed to look like
(http://www.zimagez.com/miniature/screenshot2016-05-3014-59-38.png) (http://www.zimagez.com/zimage/screenshot2016-05-3014-59-38.php)
This is now what it looks like
(http://www.zimagez.com/miniature/screenshot2016-05-3014-57-36.png) (http://www.zimagez.com/zimage/screenshot2016-05-3014-57-36.php)
Unacceptable....
I don't know what the installer uses for the dialogs. Obviously it's not dialog. Is it zenity (or anything else GTK3)? If it is the case, the issues might be coming from that side. GTK3 is giving problems once again.
The installer uses Glade... this is just one example though. When any password dialog box comes up for anything (spacefm, synaptic, etc) you see the same thing
Funny though, the vsido-exit dialog box is fine
I also tried the Semplice Zuki themes and found nothing worked
Give the following a go. Rumoured to be working with latest gtk versions. And yes, it is a gtk issue. Theme maintainers need to update their themes big time.
http://download.opensuse.org/repositories/home:/Horst3180/Debian_8.0/all/arc-theme_1464640864.d9d1772_all.deb
Cheers!!!
Thanks for the file and info hakerdefo but it still does not solve the issue...
It affects both the glade and yad installer scripts making installation if VSIDO all but impossible
What does the vsido-exit script use? I see in the script that it imports pygtk and gtk. Is this a python vs. glade/yad difference, or can your installer scripts be changed so that they function the same way?
Change the installer to gtk2 is what I'm thinking here, maybe.
times like this make me wish I could actually code.
vsido-exit is a bash script that works on the same principals that keeps fluxbox themes working through this... if you change the fluxbox theme, that then changes the vsido-exit. I raise this point just to say that both the exit script and fluxbox themes seem to be hardened against this kind of change and maybe better coded
I know nothing of this type of coding either... and that is the frustration. I can see it, I can identify it but I cannot fix it
Looks like a gtk 3 issue.
If there was an update, Gtk 3.20 breaks many themes.
The ones that work with 3.20:
https://github.com/lassekongo83/zuki-themes/tree/master/Zukitwo (https://github.com/lassekongo83/zuki-themes/tree/master/Zukitwo)
https://github.com/andreisergiu98/arc-flatabulous-theme (https://github.com/andreisergiu98/arc-flatabulous-theme)
Quotevsido-exit is a bash script
Have you changed it, boss? It used to be a python script. And if I'm not wrong it loads (asks for?) GTK2.
QuoteI raise this point just to say that both the exit script and fluxbox themes seem to be hardened against this kind of change and maybe better coded
That's one of the great things about fluxbox. The styles themselves are toolkit agnostic, pretty simple and coded in a small bunch of plain text. That's just great features, IMO.
QuoteI know nothing of this type of coding either... and that is the frustration. I can see it, I can identify it but I cannot fix it
Me neither... ::)
Hope GTK3 settles down a bit soon. Personally I try to avoid GTK3 like the pest in all my systems due to the constant breakages and funny behaviors. Way before this nasty last update.
QuoteI know nothing of this type of coding either... and that is the frustration. I can see it, I can identify it but I cannot fix it
Quote
Me neither... ::)
Hope GTK3 settles down a bit soon. Personally I try to avoid GTK3 like the pest in all my systems due to the constant breakages and funny behaviors. Way before this nasty last update.
Downloaded the test iso and tested the installer. It's definitely the theme. Buttons and dialogs are there and can be used/clicked.
The same thing with yad since it uses Gtk 3. Some claim similar with firefox.
The Gtk had a major update with 3.20. Everything went to CSS. All the themes need to get ported.
QuoteSome claim similar with firefox.
Firefox 46.x and above, yes. The 45.x.x ESR series that Debian is packaging is good (on my systems anyway).
Yes, the switch to GTK3 happened with the Firefox 46. Any older versions are GTK2. (The reason why I switched to Palemoon).
From this epic rant - (http://vsido.org/index.php?topic=1178.msg13282#msg13282)
Quote....they've broken everything prior to gtk3 3.20...
begs the question, can you use apt-pinning or something to keep Vsido downgraded/frozen to gtk 3.1x so that the themes and your dialogue boxes work as intended and get your iso's released until the gtk3 issue is resolved?
Quote from: misko_2083 on June 02, 2016, 02:24:54 AM
Looks like a gtk 3 issue.
If there was an update, Gtk 3.20 breaks many themes.
The ones that work with 3.20:
https://github.com/lassekongo83/zuki-themes/tree/master/Zukitwo (https://github.com/lassekongo83/zuki-themes/tree/master/Zukitwo)
https://github.com/andreisergiu98/arc-flatabulous-theme (https://github.com/andreisergiu98/arc-flatabulous-theme)
The first one does not have any files to download from github
The second one requires libgtk-3-dev to install which requires 128 MiB of NEW gtk3 shit to install...
Me NO WANT TO INSTALL GTK3 shit to get a menu to fucking work
Sorry for yelling and the language...
Nothing to see here, carry on...
???
Quote from: VastOne on June 07, 2016, 11:20:41 PM
The second one requires libgtk-3-dev to install which requires 128 MiB of NEW gtk3 shit to install...
Me NO WANT TO INSTALL GTK3 shit to get a menu to fucking work
Sorry for yelling and the language...
Nothing to see here, carry on...
???
I think there is a lot to see here!! I want to rename it from GTK+ to GTK-
I just checked, and I've been using VSIDO since mid 2012 sometime. No problems at all. That the gtk+ team did this with no thought in mind for the end user goes beyond the pale. When they made the decision to move to CSS, they should also have made the move to provide theme developers at a minimum, some way to "rescue" their current themes rather than just abandoning ALL of them to the dust-bin of history. They had to know it was going to break lots of things. If they didn't, then shame on them, and if they did, and did it anyway, then shame on us as a community.
I've looked at a lot of themes over the last few months. As PackRat mentioned, this first popped up in Arch (which I just so happened to be running at the time, to my great chagrin, and at great cost) it also happened everywhere else. This was not an issue of 'sometime' breakage in an unstable (re: Sid) distro. This was breakage on a level that affected most all distro's! That is why I was "ranting and raving" and "yelling and screaming" with my earlier post.
Hey, if I compile an RC version of the Kernel, and it breaks my OS, then it's my bad! If I do an upgrade on my distro, and YOU (gtk+ dev's) broke my distro, then WTF?
As I type this, I'm hoping I've come up with a workable solution. I've been pondering since I saw the 'apt-pinning' post VastOne made above. (or somewhere close by!) It triggered a thought... (I haven't rebooted yet, so it may have all been a huge SELF-DESTRUCT, crash and burn kind of thing!) :(
I'll post back here after a reboot and let you all know the results, and if it works, I'll tell what I did...
Quote from: VastOne on June 07, 2016, 11:20:41 PM
The first one does not have any files to download from github
The second one requires libgtk-3-dev to install which requires 128 MiB of NEW gtk3 shit to install...
Me NO WANT TO INSTALL GTK3 shit to get a menu to fucking work
Sorry for yelling and the language...
Nothing to see here, carry on...
???
Sorry wrong link for the first theme
https://github.com/lassekongo83/zuki-themes (https://github.com/lassekongo83/zuki-themes)
About the second theme:
libgtk-3-dev, pkg-config, automake and autoconf are dependancies for the build. Since the theme supports various versions of gtk, the version installed on the system needs to be detected in order to build the themes. Depending on the version of libgtk-3-dev autogen.sh script takes care of all of the preparation activities for you, dealing with dozens of configuration issues. Once you build and install, the themes are in in /usr/share/themes/ directory
You can copy those themes and use them on another computer without the libgtk-3-dev and other deps installed.
The only dependancies needed to display the themes properly are "gtk2-engines-murrine" and "gnome-themes-standard" packages.
As for Gtk 3.20, yeah, the devs are making things more complicated.
Hopefully, the Gtk 4 will bring the theme stability as the devs promised.
Quote from: PackRat on June 02, 2016, 02:54:04 PM
QuoteSome claim similar with firefox.
Firefox 46.x and above, yes. The 45.x.x ESR series that Debian is packaging is good (on my systems anyway).
Many themes will become deprecated because of all this changes.
Firefox is becoming heavy.
Found a lightweight open source browser.
https://minbrowser.github.io/min/ (https://minbrowser.github.io/min/)
Some description here:
http://www.omgubuntu.co.uk/2016/05/minimal-web-browser-linux (http://www.omgubuntu.co.uk/2016/05/minimal-web-browser-linux)
The interface is a little strange, you need some time to get use to it.
It's preety fast, especialy when playing youtube videos (but no flash).
Speaking of youtube, I've changed the script damo from BunsenLabs made so that it can do multiple downloads.
It's the yad youtube-dl wrapper that cleans up *.part files if you cancel the download.
https://github.com/Misko-2083/scripts/blob/master/youtube (https://github.com/Misko-2083/scripts/blob/master/youtube)
lol
This is going way off the subject... :D
Quote from: misko_2083 on June 08, 2016, 12:22:56 PM
Quote from: PackRat on June 02, 2016, 02:54:04 PM
QuoteSome claim similar with firefox.
Firefox 46.x and above, yes. The 45.x.x ESR series that Debian is packaging is good (on my systems anyway).
Many themes will become deprecated because of all this changes.
Firefox is becoming heavy.
Found a lightweight open source browser.
https://minbrowser.github.io/min/ (https://minbrowser.github.io/min/)
Some description here:
http://www.omgubuntu.co.uk/2016/05/minimal-web-browser-linux (http://www.omgubuntu.co.uk/2016/05/minimal-web-browser-linux)
The interface is a little strange, you need some time to get use to it.
It's preety fast, especialy when playing youtube videos (but no flash).
Speaking of youtube, I've changed the script damo from BunsenLabs made so that it can do multiple downloads.
It's the yad youtube-dl wrapper that cleans up *.part files if you cancel the download.
https://github.com/Misko-2083/scripts/blob/master/youtube (https://github.com/Misko-2083/scripts/blob/master/youtube)
lol
This is going way off the subject... :D
Does the deb package of Min work on Debian? And that youtube script is a nice one!
Cheers!!!
Quote from: misko_2083 on June 08, 2016, 11:26:29 AM
...The only dependancies needed to display the themes properly are "gtk2-engines-murrine" and "gnome-themes-standard" packages.
They could be the reasons why the themes that are supposed to work with latest GTK are not working on vsido.
http://vsido.org/index.php?topic=1178.msg13292#msg13292
I tested an old ISO of vsido and these two packages were missing!
Cheers!!!
^ I install them in the current builds and test them... same failures
Quote from: jediI'll post back here after a reboot and let you all know the results, and if it works, I'll tell what I did...
Sorry for the delay!
What I did...
Installed a PRE Mar17_VSIDO ISO. Allowed no updates. It wanted to update over 700 items. (ugh...)
FIRST AND MOST IMPORTANT: In a terminal, immediately after installing an older version of VSIDO as pointed out above, (Mar 17th or before!!!!)
sudo echo "libgtk-3-0" hold | sudo dpkg --set-selectionsThis puts GTK+ '3.18.9-1' on HOLD until such time as you decide you want to upgrade to GTK+ 3.20. To determine your current version of GTK+, run the following command;
sudo dpkg-query -W libgtk-3-binI did not run the vsido-welcome script. I installed manually all the things I use personally. Everything is running perfectly with no issues at all. To me this was an easy fix as VSIDO installs in less than 5 minutes and you can have everything back the way you like by simply backing up your data and restoring when done!
I did do an 'update' and a 'dist-upgrade' when I finished the above. Took a long time to complete, as I have a rather slow connection, but it did complete and everything is now up-to-date with the exception of GTK+, which is of course 'holding' at 3.18.9-1 8)
(http://www.zimagez.com/miniature/holdgtk3.jpg) (http://www.zimagez.com/zimage/holdgtk3.php)
When you do your 'dist-upgrades', you should now see the above in your terminal.
This is an extreme 'fix' I know, but I was not going to go another day without my VSIDO, and running my favorite themes! As always, if you decide to go this route, MAKE SURE you have backed up your data!
??? W H A T? ???
How can you not have been keeping your previous ISO images as historical keep-sakes? :D
If the above route is how you want to go, and you have no 'older' ISO to utilize, then we will certainly make one available for download at the VSIDO download page. Just ask and it will done...
It WILL be a very long FIRST, 'dist-upgrade', so be warned!
For those wondering, I've been going for several days this way now and all is VSIDO perfection! 8)
Hey jedi,
Thanks for this workaround!
Cheers!!!
Quote from: VastOne on June 10, 2016, 02:07:43 AM
^ I install them in the current builds and test them... same failures
I don't know, if i got all right, but the starting problem for sure is a a gtk3 one (the same happens for many themes manjaro comunity driven edition used to use). Though, one the which seems to handle that problem fine seems to be vertex, which can be found here: https://github.com/horst3180/vertex-theme
Cheers.
Hello emninger and welcome to VSIDO and our community, we are glad to have you
I have switched VSIDO to Vertex-Dark, it is a very nice theme and solves the basic gtk3 things that were missing (specifically password dialogue box and spacefm views)
It does not however correct any bash / yad / glade scripts... these are all still not showing as their dialogue boxes as they should
I am going to finally release new ISO's with these themes and instructions on how to install VSIDO with these issues, including images
Thanks for pointing out Vertex, it is nice... (If someone else had already suggested it, I apologize for the slight)
;D
Glad once out of hundred, i could be a bit useful. ;) In any case, gtk3 is a mess ... :-( :-(
Personally, i try to stay as close as possible with gtk2 ;) (OTOH, i really do not have any experience with qt4 or 5; once, when i played a bit around with lxqt i was not so affascinated, but ... )
Qt is currently a bit of a mess too. The transition to Qt5 is still going and far from complete. The mix of Qt4 and Qt5 is not as crazy as the GTKs blend and in most cases it's really hard to avoid mixing them both with GTK too. I like Qt and I often do "experiments" to build systems mostly Qt, but IMO trying to stay as much GTK2 as possible is the best toolkit option these days.
Can finally mark this damn thing solved... and I am mad as hell about it
The installers use sudo...
When I was testing themes I was changing the normal user themes expecting the menus to work
See my mistake?
sudo lxappearance and now all menus on installation ISO's look normal again (as soon as I build the next ones)
This has been a major mind fuck for me for 6 months... and a damned garage trip solved it by I will not say (Jedi) who
Mad as hell... :'(
For absolute transparency I wanted to let you VSIDO kids know just how dire this situation was to me over the last 6 months
Along with this issue and the bloat of Debian almost doubling the VSIDO ISO, I was at my wits end with Debian. Lately it just has not been any fun and I am constantly tired and frustrated
I was ready to shitcan this entire project at the end of this year but now see a little more light and at least I can laugh about part of it
Anyway that's where your good old V-Ger has been and am at now.. ready to go on for a little while longer
I was suspecting this, boss. Not strange wanting to throw the towel with the current Debian/Linux situation. It's somewhat better now, though still not what it used to be. I fully understand your frustration.
You were not the only one about to jump away from Debian to some place else. But the alternatives I was considering and testing over the last months were not fully convincing (Void, Arch, Slackware, BSDs...) for different reasons, so here we are, still on Debian.
Glad the situation eased and you found the motivation to keep going and keeping Vsido alive... Besides I don't use it as my main system (GTK3, systemd, etc...) I still love this cool and well thought little distro you put together.
Thanks Snap.. it's appreciated...
Never really built this for anyone but me and for those who appreciate and support it in any way makes it a pure joy to be around
Whatever the reasons behind, a good job is a good job. You can feel love and care put in making Vsido.
For me there are two kind of distros, those that make you jump away just minutes after install them and those that make you want to explore them further and spending good whiles on them. Vsido belongs to that second category.