1 Reply by 9812713

(43 replies, posted in CrunchBang Talk)

Hi bluejeans ...

Here is yet another (odd) bug..

I added some repos, and did some apt-get upgrade & dist-upgrade 's a like. I decided not to use the tux:tux user as reported earlier.. so i deleted the account ( userdel tux ), However when debian was trying to update wicd, it reported the following error... 

Reading package lists...
Building dependency tree...
Reading state information...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
5 not fully installed or removed.
After this operation, 0B of additional disk space will be used.
Setting up wicd-daemon (1.7.0-3) ...
adduser: The user `tux' does not exist.
dpkg: error processing wicd-daemon (--configure):
 subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of wicd-gtk:
 wicd-gtk depends on wicd-daemon (= 1.7.0-3); however:
  Package wicd-daemon is not configured yet.
dpkg: error processing wicd-gtk (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of wicd-curses:
 wicd-curses depends on wicd-daemon (= 1.7.0-3); however:
  Package wicd-daemon is not configured yet.
dpkg: error processing wicd-curses (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of wicd-cli:
 wicd-cli depends on wicd-daemon (= 1.7.0-3); however:
  Package wicd-daemon is not configured yet.
dpkg: error processing wicd-cli (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of wicd:
 wicd depends on wicd-daemon (= 1.7.0-3); however:
  Package wicd-daemon is not configured yet.
 wicd depends on wicd-gtk (= 1.7.0-3) | wicd-curses (= 1.7.0-3) | wicd-cli (= 1.7.0-3) | wicd-client; however:
  Package wicd-gtk is not configured yet.
  Package wicd-curses is not configured yet.
  Package wicd-cli is not configured yet.
  Package wicd-client is not installed.
  Package wicd-cli which provides wicd-client is not configured yet.
  Package wicd-gtk which provides wicd-client is not configured yet.
  Package wicd-curses which provides wicd-client is not configured yet.
dpkg: error processing wicd (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 wicd-daemon
 wicd-gtk
 wicd-curses
 wicd-cli
 wicd

On line 8 " adduser: The user `tux' does not exist. "

After recreating the "tux" account, everything processed 100%....

Not sure the long term fix .. Maybe tux is tied to the startup process wicd ?

Cheers.

Go to forum: CrunchBang Talk

2 Reply by 9812713

(43 replies, posted in CrunchBang Talk)

Torrent is upp'ed by mromblad ...

Details: http://thepiratebay.org/torrent/5329110 … nux_Distro

Cheers.

Go to forum: CrunchBang Talk

3 Reply by 9812713

(43 replies, posted in CrunchBang Talk)

[Bug Report - Minor] When creating a new user after installation the operator must delete the .moc folder from /etc/skel otherwise the operator will not be able to create a new user.

rm -rf /etc/skel/.moc

Go to forum: CrunchBang Talk

4 Reply by 9812713

(43 replies, posted in CrunchBang Talk)

hi bluejeans.

Here is some feedback on Squeezebang 1.01

During  the install of Squeezebang, by running command " sudo remastersys-installer intl " everything works accordingly. However, after first boot, the user tux:tux does not have a home directory. I guess remastersys fails to create a user home directory for the user.

Since the install fails to install the home directory, all you ' default ' settings are wiped sad . Has anyone else encounter this ?

I have to say this version of debian looks promising, and want to thank you for taking the time to compile this.

Is there ever going to be a amd64 version ?  :crosses fingers:

Cheers.

Go to forum: CrunchBang Talk

5 Reply by 9812713

(225 replies, posted in Feedback & Suggestions)

Hi All..

First time poster in the forums, and a 2 week user of Crunchbang. I believe that the crunchbang devs should consider a build-script for each of the versions of ubuntu that is released, this should generally take a bit of strain off the server (as far as bandwidth) and would allow any intermediate user to move to the next ubuntu release without incurring the upgrade woes. I'm not sure what the time requirement might be for something like this. I for one tried to upgrade from 9.04 (fully patched) to 9.10 ... Well as many know that doesn't work seamless. Okay, get rid of GDM for SLiM ... still did not work .. Anyways, then I tried Omns script.... I have to say, I like it, but it's not crunchbang. I am a user who likes lean, I install only what I need. I generally removed 3/4 of the packages from the lite version just to customize.

I think at this point, crunchbang should hang tight until the next LTS.. Whether to move towards a debian core is generally moot and could be up for it's own discussion. Faster booting is one +1 for moving forward, as well as package support. Maybe debian testing is AKA'ed as as the next, continuous rolling OS .. Sadly, my knowledge of customizing the GUI or config files still relies on someone else.. This is why I like crunchbang .... Install, quick conky, tint2 and app customizing, and a had full of PPA's in the source list, and tada, under 2 hours, and I'm back from scratch ...

I also think a +1 for moving forward is bluetooth support. I have to say I'm not a big fan of Pulse Audio, and the fact that debian, and Ubuntu are a bit "fat" but what can you do..


So to sum up ..

+1 debian or ubuntu next version
-1 No build scripts for each version of ubuntu
-1 Bluetooth support
-1 Upgrade options
-1 Updated software support
-/+ faster booting
-/+ Pulse Audio

Cheers.

Go to forum: Feedback & Suggestions