Once again, using Fluxbox.

Long story short: I had to re-install my Fluxbox partition after I decreased my swap partition. I spent most of last night and today tweaking the Fluxbox menu (switching icons to Faenza and adding/deleting entries). I did restart Flux multiple times during this.

Then I played with the tint2 panels, and went with a basic setup. While trying to set up a weather Conky and get it to autostart, I logged out of the session, and when I tried to log back in, it takes me back to lightdm login. I can't get back into Fluxbox.   

I'm writing this from the Openbox session. Set the desktop up like what I had done in Fluxbox, and I can log in and out at will.

So, is this a Fluxbox problem or a lightdm problem? 

Any one know how I can get back into Flux?

working great with no problemos on the Xfce install.

Now to upgrade on the Fluxbox install.

ooh, goosebumps 

-- Jeff

Hi, Colonel Panik (love the nomenclature).

If you like Debian, then you're going to love VSIDO. By all means, USE the wget commands to download, or else you'll only have a shell. Wget works every time.

-- Jeff

About frikkin' time!

I was beginning to think that the Liquorix kernel that I came to love and admire was dead at 3.7    Big leap forward, but I'm eager to try it out.

Will have to wait until later, since it's nearly 4.a.m. and I need to get some sleep.

Thanks for posting. My last smxi was just a few days ago, and I was depressed that we were still on 3.7.

Here's my first custom built box, from about a month ago. Previously, I had a dual-core Athlon 64X2 HP, which has lasted for about 4 years. It'll now be my roommates. I wanted at least a quad core for the build, and couldn't pass up the 6 core when I saw it. I'm of modest means and the tax refund would only go so far   I went with the ECS mobo, just because the HP had one, and I knew it could take an environmental beating.

System:    Host:  Kernel: 3.7.0-10.dmz.2-liquorix-amd64 x86_64 (64 bit)
           Desktop: Fluxbox 1.3.5 Distro: VSIDO
Machine:   Mobo: ECS model: A970M-A DELUXE version: 1.0 Bios: American Megatrends version: 4.6.5 date: 11/09/2012
CPU:       Hexa core AMD FX-6300 Six-Core (-MCP-) cache: 12288 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm)
           Clock Speeds: 1: 1400.00 MHz 2: 3500.00 MHz 3: 1400.00 MHz 4: 1400.00 MHz 5: 1400.00 MHz 6: 1400.00 MHz
Graphics:  Card: NVIDIA Device 0fc6 [GTX 650] X.org: 1.12.4 driver: nvidia tty size: 80x24 Advanced Data: N/A for root
Audio:     Card-1: NVIDIA Device 0e1b driver: snd_hda_intel Sound: ALSA ver: k3.7.0-10.dmz.2-liquorix-amd64
           Card-2: Advanced Micro Devices [AMD] nee ATI SBx00 Azalia (Intel HDA) driver: snd_hda_intel
Network:   Card-1: Realtek RTL8111/8168B PCI Express Gigabit Ethernet controller driver: r8169
           IF: eth0 state: down mac: <filter>
           Card-2: Atheros AR9300 Wireless LAN adaptor driver: ath9k
           IF: wlan0 state: up mac: <filter>
Drives:    HDD Total Size: 2000.4GB (12.7% used) 1: id: /dev/sda model: SAMSUNG_HD501LJ size: 500.1GB
           2: id: /dev/sdb model: ST1000DM003 size: 1000.2GB 3: USB id: /dev/sdc model: 0AS size: 500.1GB
Partition: ID: / size: 185G used: 6.8G (4%) fs: ext4 ID: swap-1 size: 17.44GB used: 0.00GB (0%) fs: swap
Sensors:   System Temperatures: cpu: 19.6C mobo: N/A gpu: 31C
           Fan Speeds (in rpm): cpu: N/A
Info:      Processes: 179 Uptime: 3:43

Great review, and "behind the scenes" view.

Even though I like to use the Siduction repos, VSIDO is remaining my Debian-base-distro of choice.

Keep up the great work, Vastone. Even though I am not "social" I'm trying to spread the word on this wonderful, best OOTB Debian distro.

-- Jeff

Many of the Xfce4-goodies have been deprecated, i.e. not built for 4.10. As the march continues towards Xfce 4.12, the best bet is to download and install them separately.

Personally, I like to pick and choose the ones I use and need.

-- Jeff

I just posted the nvidia install problems to the other post of losing tty1.

I managed to get the siduction-experimental repo 313.26 drivers to install, but it took a while.

I used synaptic, and used the force install, bringing all of the dependencies and tracking them down. Debian has cut the driver installer into so many myriad parts, it takes a good hour to track them all, force to siduction-experimental, then hit fix broken packages a few times.

one of the hard ones to track down was this driver: libxvmc1nvidia

But I managed to to do this twice now, and tty doesn't break either.

-- Jeff

Quote from: VastOne on March 23, 2013, 03:49:51 AM
I'll take care of the WICD in Xfce.. one I overlooked, thanks

What do you mean by the TODO in the FB Config folder?

The tint2 files in /usr/local/bin are basically the same, the differences being what one is being used for OB or Xfce/Fluxbox.  I am not sure what you are asking here.. 

I included a mass collection of tint2 configs that I had played with for several months for people to use as a guide on what can be done with tint2

Thanks for the feedback!  I appreciate it! 

Re: Tint2 config files. It just took me a while to suss out which one was being used. They're all just in the tint2 folder, but there's one in the home directory and one in like etc or usr. Guess I just need to hone up on tint2; just haven't had time.

The TODO file in the fluxbox folder are like notes of what you want done, where there are bugs and how you want to it to look/work. Perhaps it's not yours, but the Fluxbox devs. Oh, it's in the flux menu folder. I'll attach it. It was just something I found, and thought was rather strange.

I couldn't agree more. I have 2 installs, one just Xfce and the other Fluxbox and both are lightning fast and so much fun to play with.

Just a bit of feedback on my part: WICD is still listed under Xfce's Start-up, and there's a nice little TODO list in the Fluxbox config folder. I found it interesting.

Also, could you place in folders the extra tint2 configs, since it's difficult to find which one does what, especially since they're in at least 2 separate directories.

BTW, I really like the Fluxbox menu editor. Very similar to the Openbox root menu editor, and simple to use.

Keep up the great work. Been loving it.

-- Jeff

On a new install, I used the Nvidia 313.26 drivers from Siduction experimental repos. After some time tracking down dependency issues through synaptic (using the force install for the Siduction/Experimental ones, since the default is 304), it installed. One "Nvidia-Xconfig later, and I was back on screen.

And tty1 works 

So it must just be a bug with the 304 series, or pure debian (not certain if Siduction devs tweaked the binaries or not). Anyway, the Siduction experimental Nvidia drivers are a win.

I smxi'd my way into the pure nvidia driver install and all is well.

-- Jeff

You're welcome.

But like I stated in my other post, Playonlinux seems fussy to install on Debian, and if you use Nvidia GPU (like I do), it'll state it can't find glx drivers if you just used SMXI/SGFXI to install the driver, so you need to install first via commandline or synaptic the drivers, which currently seem to break tty1.

Last night, on my second Vsido testing install, I tried to pull in the 313.26 Nvidia drivers from experimental, and broke apt (segmentation fault). Aptlistbugs stated the tty bug was in nvidia-kernel-dkms file, btw.

Guess POL is wasted now until they fix this, but Winetricks should still work, and is similiar, but slightly harder to configure.

I'm not an expert by any means, but I've installed and used them plenty of times for my one program. Feel free to ask, and I'll try to troubleshoot if you have problems.

-- Jeff

make yourself comfy. It's pretty awesome around here.

-- Jeff

Wine works well on Vsido.

I don't play games, but I do use some 3D applications like Carrara and Poser, so I need Wine. Wine on Debian is currently non-maintained. I think the last build was 1.5.5, while Wine itself is up to 1.5.23. Luckily, the Liquorix team has uploaded ubuntu's wine packages to their repos, and it works on Debian. So, if you're going to be using Wine, use that package.

If you grab the 1.5.5 .debs from the WineHQ download pages, you can just install the 64bit packages, but they'll bring in 32libs, I believe.

I use the playonlinux frontend, which sandboxes any version of wine I want to download to use for a specific project. OS's only allow one version, and if that one doesn't work for you, you would have to find another version, which isn't always possible. But with playonlinux I can download any wine version and pick on I want to use.

I don't own a copy of Windows, so I rely on Wine to run the one program I need, since I bought a lot of Poser-related products that aren't supported under Blender, which I still can't get my head wrapped around.

Yeah, 313 is the latest latest, but the 304 series is like "the stable" branch.

It was just a glitch in the install, I think. It never happened before for me. But the "nvidia-installer-cleanup" has been a pain the backside since Debian introduced it (or segregated it), and is probably the cause. I've had issues with it before, when I was sussing out how to get Playonlinux to work correctly.

I was rushing through the post-install setup, since I wanted to also install the new Manajro Openbox-lite version on another partition so it was probably user-error

Will give it a go on my next day off.

-- Jeff