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 - ew

Pages: 1 [2] 3 4 5
Feedback & Suggestions / Once again back here...
« on: January 15, 2014, 02:28:07 AM »
Once again back see how the new release is, and it`s awesome as usual. Easy, fast and flawless installation, and VSIDO even made kernel 3.12-1 work for me. Which I`ve only achieved in one of my many other installs, but  I can`t seem to duplicate it. But with VSIDO it was no issue at all. Strange, but good strange :D

Anyway, I`m not sure if I will stick with Fluxbox, but I`ll give it a chance... It`s not that I don`t like it, but I do know openbox in and out, and I`m unsure if there is any point in trying to learn Fluxbox, when the end result will be pretty much the same. So if I decide to go for Fluxbox, it will be because I`ve left openbox behind me, and I`m not sure that I will do that yet. I`m still naive enough to hope for some development in openbox and tint2  ::)

You`ve done a very good job with the installer. This is probably the easiest and fastest installation I`ve ever experienced. I will stick around for a bit this time, to see if VSIDO could be a better base for my projects than Crunchbang. Being on Sid, and low in size, it`s already a better starting-point....

Ok. I`ll do this, and have another go at trying to like spacefm. I also missed the right-click actions, so I kind of made the easy way out by making Thunar the default FM, because I know how to configure Thunar to my liking :D I also used to like PCManFM, but SpaceFM hasn`t done it for me yet...

General Support / Re: Problems with locales & twice wicd launched
« on: November 20, 2013, 01:55:09 AM »
I have solved the two wicd-tray icons in openbox, at least for me.

As previously said in this thread, fluxbox doesn`t read from /etc/xdg/ autostart, so just remove the wicd-tray.desktop file from that location. As root cut and paste it somewhere so that you have a backup of the file if you ever should need it. When you have removed it for /etc/xdg/autostart, then logout and back in, just to test that it still works. If it does work, logout and change session to openbox and login.

In "~/.config/ openbox/", enable the wicd-tray entry, by uncommenting it, and save the file. Logout and back in to test that it works... If that works, then logout again, and switch session to xfce4, and login.

Right-click your xfce4-desktop, choose Settings/Session And Startup/ Application Autostart.... Click add, give it a name like wicd-tray or something, and in the command-field put this without the quotes "wicd-gtk --tray". Click ok, and logout and back in, to see that it works.... It works perfect for me, and what could break it is if a update/upgrade some day will put a new wicd-tray-desktop in /etc/xdg/autostart, but in that case, it`s just to delete it again...

The last session I haven`t looked at. Actually, I have nerver logged into it. But I suppose you can manuallyt set if for that session too..

Feedback & Suggestions / Re: VSIDO II feedback...
« on: November 20, 2013, 01:13:24 AM »
Diskmanager is awesome, and unless your adding stuff to mount to tmpfs, editing fstab is made tedious once you start implementing diskmanager.  I agree that it would probably tend to be more confusing to the new user without the use of diskmanager.  Makes it quick work indeed to set it and forget it with fstab!

I tried it now. But I don`t know if I like it, lol. It did it`s job very well, and was easy to understand. My problem is that anyone could use it, and that isn`t cool... lol. Just kidding. It was awesome.

Feedback & Suggestions / Re: VSIDO II feedback...
« on: November 19, 2013, 12:20:52 PM »
I do not see the need to create a mount point a big need during the install, in fact I find it more a confusing to a user than anything, especially to a new user

Disk Manager is installed in VSIDO and there is no simpler tool than that to do a one time creation of a mount point and forever forget about it

I will be working on the installer eventually to have it see more things, but for now it is getting the job done quite nicely

Yes, it sure is doing the job nicely. As for Disk Manager,  I have to admit that I haven`t tried it. I always need to edit fstab all the time regardless, because I`m multibooting, and most new installs tend to change one or more of my existing uuid`s. For example the uuid of the swap partititon is always changed, so that the other distros no longer boots if swap is mounted in that distro. I have to nano my way to fstab from tty to change the uuid`s. I`m quite used to doing that, so fstab doesn`t scare me that much... And you are probably right. Less options are less confusing for users. I`ve never thought of it that way...

By the way, it looks like it should have been you that forks remastersys, not OS4. Because, nothing much has happened with System Imager.

Feedback & Suggestions / Re: VSIDO II feedback...
« on: November 19, 2013, 03:02:58 AM »
^ Thanks for the feedback...

I have already eliminated the need for root and user passwords to be different from the current VSIDO remastersys installer..

Are you suggesting that you are still seeing it?

BTW, all VSIDO remastersys files are on every VSIDO install

Nope. I just used different passwords out of habit, so I didn`t try to use the same passwords. So you fixed this too? Awesome :)

Yes, I see the files and will start the  task of comparing them with the original sources to see what you`ve done. I could just copy yours, but I wouldn`t learn to much that way. But rest assure, your files are securly stored... in case I don`t manage to do it myself :D

I see that you also have fixed the installer so that it adds the user to the "sudo"-group. That was another fix I had planned to do, but you`re obviously way ahead of me :)

I have a big change for the script that some might do at some point, but not me at this stage. Not capable to. It`s about adding the possibily to setup mount of other partitions during the install, also including custom mount points. Like me, who always has a shared data-partition mounted in /media/fileshare. It would be nice to be able to do this during the install. Especially for the unskilled users. But as far as I can see from the current scripts, this seems to be a rather big coding-job. If not, it probably would already have been implemented :)

Feedback & Suggestions / Re: VSIDO II feedback...
« on: November 19, 2013, 01:39:56 AM »
More feedback. I Installed VSIDO today with the no-swap installer. Worked perfect. Awesome job with the installer :)

Now there are just one thing with the remastersys-installer that I will try to fix for my remaster of other distros. Remove the need to use a different password for the user and root during install, so that the user don`t have to change the user-password after the install is finished. But obviously, this isn`t a big deal. "sudo passwd user" isn`t all that hard to do :)

General Support / Re: Problems with locales & twice wicd launched
« on: November 18, 2013, 11:33:17 PM »
I don`t know if it`s that easy, because it`s only a issue in openbox-session. Not in fluxbox-session. But of course, it might be that Vastone has left it out of the fluxbox-autostart, but forgotten to do the same for the openbox-session. Anyway, I`m only guessing because it isn`t installed with me right now. I`ll do that now...

General Support / Re: Problems with locales & twice wicd launched
« on: November 18, 2013, 03:38:53 PM »
As for the multiple wicd-gtk icons in openbox-session, I recall having that issue too, but as I should wipe my hdd to create a new partition-scheme, I didn`t bother to fix it. But I`m going to reinstall VSIDO a little later this evening, and rest assure. I will solve that issue, because someone as OCD as me can`t live with duplicate icons in the tray. I will report back when I fix it. Today, tomorrow or next year, but it will be fixed :D

General Support / Re: Problems with locales & twice wicd launched
« on: November 18, 2013, 03:26:06 PM »
I use these commands for all that keyboard-stuff.

"sudo dpkg-reconfigure keyboard-configuration"
"sudo dpkg-reconfigure console-setup" or "sudo dpkg-reconfigure console-data" ,
depending on which packages are installed on the system.

In addition(to generate locales):
"sudo dpkg-reconfigure locales"

If you play around with those, you should be able to fix it.

WM Designs and Discussions / Re: lxpanel-taskbar icons
« on: November 08, 2013, 09:35:13 PM »
I would do a search of all spotify files on the computer, locate all of the icons form that search and then replace that one with a quality one

Good advice. I`ll do that. Hopefully there will not be to many of those to replace :)

There`s another tiny issue with my bottom lxpanel. It seems that the taskbar icons is slightly smaller, than the launcher icons. There is a few pixels more space below the task-icons. Is this something that`s known and intended, or only something that happens with me?

WM Designs and Discussions / Re: lxpanel-taskbar icons
« on: November 08, 2013, 12:27:37 PM »
Strange. I`m aware of that, but I have a issue where this isn`t respected. This app hasn`t got an icon in Linux-Lex, so I had to set it manually.

As an example, this is from my lxpanel-config:
Code: [Select]
Button {

And in the spotify.desktop:
Code: [Select]
But the result is unexpected, as the launcher-icon looks good,
while the taskbar-icon looks horrible. As you can see in this shot:

WM Designs and Discussions / lxpanel-taskbar icons
« on: November 08, 2013, 01:36:08 AM »
Does anyone know where the taskbar icons in lxpanel is fetched from? Because all the launcher icons are fine, and there I can manually choose those that aren`t by editing the desktop-files. But what about the task-icons? For some apps the resolution on the task-icons is way to low to look good in a panel with big icons/buttons. So do I have to look around to manually replace small icons with larger ones in any location where it might be fetched from, or is there a way to detect where the origin is?

WM Designs and Discussions / Re: FluxBox Slit
« on: November 08, 2013, 12:29:47 AM »
Oh how stupid I am. The "minimize all windows" button already exists, and can be added by the configuration gui in lxpanel. At first it seems that it only minimizes the windows, but then I noticed the "Minimize All Windows-settings" when I right-clicked the panel, and  it turned out that it could be set to toggle. So now everything is fine, and I will continue to use the lxpanel. :D 

WM Designs and Discussions / Re: FluxBox Slit
« on: November 07, 2013, 09:31:35 PM »
That syntax is wrong. You can have -

Code: [Select]
Mod4 d :Lower
Mod4 Shift d :MacroCmd {Raise} {Focus}

Something like you have will need to be written as a key chain like emacs -

modifiers-1 key-1 modifiers-2 key-2 :'command' [arguments ...]

Ok, thanks. That works to lower a window and raise it again, if another window isn`t opened while that window is lowered. So I guess it works as it should. But it`s not quite what I look for. I want to use "ShowDesktop" (minimize all windows), but I want to do so without closing the lxpanel. If I set lxpanel to the desktop-layer, then everything works as I want it to, with the exception that fullscreen winows covers it, which I obviously want them to(autohide dock). But in this state it isn`t possible to raise the panel. If the panel isn`t covered by a window, and I set Chromium to open slightly above the panel, then it works fine. But then the panel becomes just a launcher/taskbar, not a autohide-dock.

So what I`m looking for, is how to set lxpanel so that it doesn`t get affected at all by the window-manger(fb), but remains in the same state regardless. Which seems to work if the lxpanel is set to the desktop-layer. But I need the same behaviour when it`s set to the top layer, because setting it to "dock" and try to put it in the "slit" doesn`t work.

Edit. No need to worry about it. I`m usually not into the docks, as they are just bling to me. I don`t use them, so I`ll configure it as a 30 pixel high bar instead, and have it always raised. That solves it, and is more my kind of thing. I took a look at fbpanel, and installed it. It seems very light and also has the options that I need, so perhaps I will use fbpanel for the fb-session. But before I do that, I will try to configure the lxpanel to my liking. If I don`t manage to do that, then I just replace it. It`s cleaner and easier to have the same panels in all sessions, but it`s more interesting to have a totally different setup in all sessions.

Pages: 1 [2] 3 4 5