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.

Topics - ew

Pages: [1]
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....

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?

Feedback & Suggestions / VSIDO II feedback...
« on: November 05, 2013, 12:08:05 AM »
I installed VSIDO raptor two days ago. The install itself went fine. The installer didn`t recognize my gpt-disk as ususal, but my way of fooling the installer worked this time too. But after running the Welcome-script and the first reboot, it became unbootable. Kernel Panick and warning about init and "conf/conf.d/resume" with unexpected tokens in line 1, and kernel not syncing etc..etc.. I don`t know what caused this. Perhaps that I removed the usb-dummy that I used to fool the installer, without swapping off. When I did that, I got an I/O-error... but didn`t take much notice of it.

Anyway, I decided to do it all over again. Fooled the installer with the usb-dummy and installed swap to the usb. Install went fine, the welcome script and dist-upgrade also went fine. But this time I swapped off before removing the usb-dummy, and then I edited fstab to point swap to the swap-particion on my gpt-disk, which it initially doesn`t recognize. Then I also remembered the init warning from my failed boot, and I installed systemd and edited /etc/default/grub to use it. Well, then I rebooted, and this time it went right up in no time at all. No issues at all, and now I`m enjoying configuring this awesome release. I really really like it, and are especially thrilled about the default session, fluxbox and lxpanel. I hope you stay with fluxbox for a while, because this setup is awesome.

You have done a very good job with this one. It`s awesome, and it feels inventive and different. I haven`t seen anything quite like it. Perhaps because I haven`t used fluxbox that much before, and never together with lxpanel as a dock. Anyway, I really love it. Awesome job!

Feedback & Suggestions / New feedback again...YES, FINALLY...
« on: July 04, 2013, 01:26:41 AM »
Hi Vastone :)

I will not bug you any more about the lack of efi/gpt-support within VSIDO or the installer. Finally today while I was determant that this issue shouldn`t stop me from using VSIDO, I decided that I would install it permanently on a USB-Stick. So far so good. I created a MS-DOS system on the stick,with two partitions, I created one ext4-partition and a "dummy" swap-partition of the giant size of 30MB  8)

Well, then in with the VSIDO-CD containing the latest ISO, hit tab to add "acpi_osi=Linux" and then hit enter. It booted just fine, and I started the installer. It detected the two partitions on my usb-stick, as I assumed it would, because they were ms-dos and NOT gpt... Well, I chose the swap-partition on the stick as it`s mandatory, and then the next step was to choose the root-partition and then I got a bright idea. I wouldn`t choose the root-partition that I prepared on the stick, instead I chose a empty ext4-partition on my gpt-disk, thinking that it was worth a shot. My thought was that the efi/gpt issue solely relyed on the installer, and that it would be sufficient to "fool" the installer, and that everything would work if I just could get it to install. Well, it proved to be correct... It installed just fine on my gpt-partition, and I also wrote grub to this partition...

Rebooted into Ubuntu that is my bootloader and master-grub, did a "sudo update-grub", and voila, it detected VSIDO in sda9 on my gpt-disk, and added an entry in efi..., as you see here:

So now I`m a happy camper, and you can be reassured that VSIDO handles efi and gpt just fine. It`s just a question of fooling the installer to think that you are about to install it on a ms-dos disk with a "dummy" swap-partition, and then all of a sudden, it detects the gpt-partitions so that you can choose those for root, home or whatever...

Well, now I`m logging of VSIDO and my PC for tonight, looking forward to many days configuring the appearance of VSIDO on my efi-booting gpt-disk. Problem solved. At least for me:)

Feedback & Suggestions / A little feedback again:)
« on: May 22, 2013, 01:05:00 AM »
Hi Vastone,

I`ve tried the newest ISO, I never give up, as I really want to run VSIDO. Well, I booted the live-cd with some adjustment to the kernel-parameters. I`m used to that, and need to do it for all new kernels, so that`s ok. Not a VSIDO-issue, not a Debian-issue, but a Linux-issue that applies to every distro with new kernels on my hardware.

As for the installer, I see that swap is still required, and that`s fine. I created a root-partition, and a swap-partition, but when I closed GParted, the installer couldn`t detect any swap, and I had no other choice than to quit the installation. I assume that the issue is as before, that the installer(remastersys) doesn`t detect gpt-partitions. I`m, not using EFI anymore, but I`m still using GPT, and that seems to be incompatible with the VSIDO-installer/ remastersys. If anyone has successfully installed VSIDO on a GPT-disk, then I would like to know how they did it, besides the obvious, which is to convert the disk to MBR. I would do that if I was to run VSIDO exclusively on my disk, but as we all know. I`m running several distros, and several installs of the same distro...

So just give me a shout if at any point there are changes in the installer or remastersys, that makes it likely that gpt-partitions will be detected, and I will have another go at it..., because I really, really like VSIDO, and want it to be my primary xfce-distro :)

Feedback & Suggestions / The live installer...
« on: April 09, 2013, 10:56:00 PM »
I`m currently trying to install VSIDO, and ran into problems with the installer. It seems like having a swap is required, and installing on an ssd as I`m doing, you really don`t want no swap... You want to swap only in RAM, to prolong the life of the SSD. Well, I spilt the partition to create a swap partition(can remove it later), but the installer now refuses to detect the swap, and I have to quit the installation. I have rebooted several times, but same things happen. It doesn`t detect my swap and I have to quit. I will find a way regardless. I have booted up in Ubuntu and prepared the partitions from here, hoping that the VSIDO live installer will detect it at next attempt. But you should really think about making the swap optional in the installer, because less and less people use it. Just my 2 cents, if I succeed with my next attempt to install it, I probably will think that this is a minor issue:)

Introductions / Well, then I guess that I`m here....
« on: April 09, 2013, 07:46:35 PM »
Been visting a few times, but left again because my intel hd graphics didn`t like the new kernels. After months of struggle and ranting in the #!-forum, Debian Joe asked me if it was my intel graphics that was the issue, and in that case he had posted a workaround some time ago. Off I went with little faith, but it turned out that the fix worked perfect for me. The worst part is that it was an easy fix. I should have been able to solve it myself. Well, I cant help that I`m a bit slow, but that fix prepared me to haunt the VSIDO-forum. If you need to blaime anyone, blaim Debian Joe. Without him and his workaround, I wouldn`t have been here now:)

Anything about me? Well, im well into my midlife crisis, and whether Linux is the solution or the cause, I guess time will tell. I`ve worked with computers for 30 years, mainly with hardware and repairs, and of course also software related issues, but only on various MS-OS. Fiddled a bit with html-coding and php, but nothing advanced. Then W8 came, and for my personal use I didn`t want to participate in an OS that looked like the teletubbies was on vacation in legoland, so then I started to experiment a little with an ooooooooooold laptop, and therefore searched for lightweight distros, and the first I tried was WattOS, which was fine.

The next one I tried was Peppermint, and I liked even better, and then I saw the famous #!-Disclaimer, and just had to try that, and felt instantly at home. Been there since, but of course multibooting and hopping between distros like crazy. So I`m new, but I`ve been trough a lot. My route is probably different than most. I didn` start out with Ubuntu or the big ones, but I went directly from Windows to openbox, which I`m happy that I did, because If I had started with Ubuntu, then I probably never would have discovered all the smaller exiting Debian-based distros.

Well, I guess that`s it. I`m a linux-noob, but relatively experienced for my short time in the Linux-world. You could say that I`m addicted. It`s only my two dogs that can get me away from the pc now and then. I don`t even watch television any more, and have no time for gaming. It`s linux, linux, and just linux..., and I don`t seem to get tired off it, like I`ve done with other all-consuming hobbies. My problem is that I never can do anything halfways. Either I`m commited, or I`m not:)

General Support / libglib2.0-0....accountservice
« on: February 11, 2013, 11:31:14 AM »

I just installed VSIDO and did the dist-upgrade in the post-installation script. 3 packages are being kept back.... How to solve this?
Code: [Select]
The following packages have been kept back:
  accountsservice libaccountsservice0 orage
0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
ew@vsido-g580:~$ sudo apt-get install accountsservice libaccountsservice0 orage
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 accountsservice : Depends: libglib2.0-0 (>= 2.34) but 2.33.12+really2.32.4-5 is to be installed
 libaccountsservice0 : Depends: libglib2.0-0 (>= 2.34) but 2.33.12+really2.32.4-5 is to be installed
 orage : Depends: xfce4-panel (< 4.9) but 4.10.0-1.1 is to be installed
E: Unable to correct problems, you have held broken packages.

Pages: [1]