Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - misko_2083

Pages: 1 [2] 3 4 5
General Support / Re: Dialogue box issues
« on: June 08, 2016, 12:22:56 PM »
Some 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.

Some description here:

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.
This is going way off the subject...  :D

General Support / Re: Dialogue box issues
« on: June 08, 2016, 11:26:29 AM »
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
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 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.

General Support / Re: Dialogue box issues
« on: June 02, 2016, 02:49:03 PM »
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

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.

General Support / Re: Dialogue box issues
« 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:

Artwork & Screenshots / Re: Februar 2016 Screenshot Tema
« on: February 09, 2016, 07:41:24 PM »
Playing with square icons  :)

Our friend misko_2083 has discussed it on another forum and has a solution

Google knows too much about me :D
Anyway, that was a quick fix, removing guest utils will do the job. No need for that on metal.
Code: [Select]
sudo apt purge virtualbox-guest-x11 virtualbox-guest-utils virtualbox-guest-dkms

How To's / Re: How To: Building the VSIDO Installer
« on: February 04, 2016, 05:27:34 PM »
@VastOne I'm glad you are sharing this with everyone. That's what FOSS is all about.
Just noticed dependancies.
Filip has made changes with dependancies. One is a switch from reiser4progs to reiserfsprogs.
Reiser4 and reiserfs are not the same fs. The switch from reiser4 to reiserfs happened because reiser4 kernel module is not mainlined yet, and therefore doesn't exist in the Debian kernel.
One can actually create/format a reiser4 partition, but can't use it without manually compiling the kernel module first.
Filip also added xfsprogs, jfsutils and btrfs-tools. Changes are here

VSIDO Changes / Re: New Test ISO's
« on: February 04, 2016, 05:10:39 PM »
vga=x is 'supposed' to be deprecated in grub2...

I won't tell anyone if you don't...  :o
Your secret is safe VastOne :)

VSIDO Changes / Re: VSIDO new linstaller Discussion
« on: February 01, 2016, 03:34:23 PM »
@VastOne thank you for reporting
We'll see what's going on.

Introductions / Re: howdy
« on: February 01, 2016, 03:26:49 PM »
Wlcome a.

The question is strange.
I didn't know it was regarding a TV series. :)
Birds Of Prey
Seems like Batgirl can't fly after all.  :D

VSIDO Changes / Re: VSIDO new linstaller Discussion
« on: February 01, 2016, 12:18:09 AM »
As Dragan said:
Some packages will have to be installed for xfs, hfs+ and raiserfs file systems. Tools to format and mount partitions.
For hfs hfsutils. hfsprogs is allready installed

VSIDO Discussions / Re: TRIOS linstaller questions
« on: January 30, 2016, 05:04:19 PM »
^ Fantastic... Let me know when they are there and I can begin the testing.  Also keep in mind I am available at any time for any type of testing your team may need.  I do not know code as well as you all but I can track down issues and troubleshoot as well as anyone... though Misko is incredible and tough to beat!  :)
I was just lucky. :D

@Mr. Spock "Live long and prosper."  ;D

          @PackRat thank you for reporting @memory info

           @Disk info That needs a fix too now it says "200G MB"

@Filip nice @args. Easier to do it in *-base, turning refind part the same way could be usefull

VSIDO Discussions / Re: TRIOS linstaller questions
« on: January 29, 2016, 07:39:26 PM »
Here is the log. I am able to recreate this issue every time by choosing and excepting the 'default' partition setup

For whatever reasons, this grub install is not implementing the default setup of net.ifnames=0 that is there on the livecd session and is default within the VSIDO squashfs

I can recreate it every time.. If this issue is solved, I believe we can use this installer
Found it. :)
Line 189
need to change that from
Code: [Select]
sys.stdout.write("GRUB_CMDLINE_LINUX_DEFAULT=\"quiet resume=%s\"\n" % swap)to
Code: [Select]
sys.stdout.write("GRUB_CMDLINE_LINUX_DEFAULT=\"net.ifnames=0 quiet resume=%s\"\n" % swap)And it should work. The function changes /etc/default/grub

Tested and it worked here.  :D
Also here:
I've commented out lines # 53, 54, and 55 and refind error isn't in the installation log after the install.

VSIDO Discussions / Re: TRIOS linstaller questions
« on: January 29, 2016, 06:17:54 PM »
^ @log refind isn't a big issue here
commenting out that line containing refind, that are used to display a message update a progress bar fixes that.
I think this here might be an issue:
Code: [Select]
  /run/lvm/lvmetad.socket: connect failed: No such file or directory
  WARNING: Failed to connect to lvmetad. Falling back to internal scanning.

VSIDO Discussions / Re: TRIOS linstaller questions
« on: January 28, 2016, 09:00:57 PM »
Could you also check on the live-cd?  Before the live-cd loads, please tab and edit and confirm that it is or is not on the same line

Thanks mate
It's right there on live-cd.

Pages: 1 [2] 3 4 5