You are not logged in.
pjbrunet wrote:A hyperlink to the new website/distro (at the top here) would be helpful.
If you click on the #! logo, it should take you straight there
I found http://BunsenLabs.org in Google (ranked #5 for "Bunsen Labs" LOL) but the logo still takes me to http://crunchbang.org/ after I cleared cache.
OK I get it now, http://crunchbang.org/ redirects to http://BunsenLabs.org duh :-)
For "defining features" how about a window tiler?
A hyperlink to the new website/distro (at the top here) would be helpful.
pj at pjbrunet dot com
moderator edit: email address ambiguated to protect poster's inbox from spam
I posted my unadulterated email deliberately, as a matter of (human) convenience.
Remember the days when email harvesting was a problem?
Frankly, I think we're beyond that now that spam filters have sufficiently advanced :-)
Regarding the color change. I think an undertone change would accomplish much the same as an overt change. Philip did it with the switch from black -> gray and I think once again from 1 gray to another.
I have a terrible sense of color so I'm not going to attempt a mockup to illustrate... perhaps someone else was thinking along the same lines though.
This is something I actually think about because I was trained by a color expert who was a student of a student of a student of Picasso. (Not kidding.) Personally, I think if you're going to go gray, stick to even numbers like #111, #222, #333, etc. Why? Because some displays are warm and some are cool. So if you go "even" you're leaving the temperature decision up to the owner of the display. Personally, I prefer my grays warm, but you may like yours cool. It's a matter of preference. So IMO, don't force warm or cool on anybody, let them decide the temperature w/ hardware settings.
Please keep it as close as possible to crunchbang. I am using crunchbang as my daily driver. Please don't stop maintaining this project
![]()
![]()
![]()
![]()
![]()
![]()
Same here. I use CB just about every day. It's beautiful.
Rest assured we are working on restructuring the forums to better suit our new community needs. A new layout is in discussion and we just need Philip to implement it for us. When this has been done, we will do our moderator job to clean up the mess and move topics to where they belong
As far as appearance, the forum here looks good IMO.
Sorry I don't really have time to help but you can put me on the email list for announcements:
pj at pjbrunet dot com
moderator edit: email address ambiguated to protect poster's inbox from spam
I'm thinking, I'll probably keep using Waldorf as long as possible :-/
Basically I like Openbox + a window tiler (I use pytyle) and all the slim, minimal dark-grey themes are awesome. If you guys continue that tradition, I'm behind it.
Encore!
Glad it helped, and I'm actually glad it got resurrected, because I sure like Master P as a nick for pvsage better than Ponymod.
While this solution works, I saw some "warning" messages. So either there's a legit syntax problem or I'm accidentally on the edge of some new frontier. I tend to ignore warnings but maybe somebody will want to get to the bottom of this.
Solved. Jebus that was maddening. This is what I think is happening...
If I enable bitmap fonts, either through dpkg-reconfigure fontconfig-config or by symlinking 70-yes-bitmaps.conf and have the default preferences for Iceweasel, Firefox or Midori, and if Helvetica is specified in the web page's stylesheet, like "Helvetica, Arial, sans-serif", it renders horribly. In chromium, or if I disable bitmap fonts, or if I change Iceweasel's prefs to use a specific font like "sans", no problem.
The solution, from Debian Wiki Fonts/FAQ, was to include the following in my ~/.fonts.conf (before the final </fontconfig> tag)...
<!-- Helvetica is a non true type font, and will look bad. This replaces it with whatever is the default sans-serif font --> <match target="pattern" name="family" > <test name="family" qual="any" > <string>Helvetica</string> </test> <edit mode="assign" name="family" > <string>sans-serif</string> </edit> </match> <dir>/usr/share/fonts</dir>
Screenshot...
http://www.dumpyourphoto.com/files6/154 … zT3CpP.png@Master P, I just meant that I don't have Philip's font configs on my rig. Thanks for the good wishes, they helped!
@el_ko, thanks for checking, my man.
Marking this [RESOLVED], though I'd love to hear opinions on why I was seeing this and others with bitmapped fonts enabled weren't, and why chromium rendered the page fine. Is the font getting cascaded to Arial or sans, and then the bitmap rendering messes them up? Here's another web page where the entire page rendered horribly until editing ~/.fonts.conf...
http://freecode.com/projects/xfsttI'll also drop a line in the Font Task Force thread in case someone else experiences this. Thanks all!
-edit- This also solved another rendering issue I was having, where the text on some of the thumbnails in Iceweasel's New Tab Page was all jumbled.
I realize this is old but I can confirm this code fixed my Helvetica font problem in Iceweasel. Before the fix, Facebook and LinkedIn looked like they reverted back to 1988 fonts.
I know this is very late. But try the following:
pkill nm-applet
Need to kill first
sudo nm-applet
Turns out to be a bug. Gnome no longer maintains this package. WIth root nm-applet works. Seems to happen only when upgrading to testing repos
edit: this allows you to save the connection, but it's not visible if you run it without sudo. Also, my ip address still seems to be my regular IP when checking on a site...
Same error message for me, though in English. I only see the error after I log out and then log back in.
Killing and starting nm-applet as root didn't fix it.
sudo update-alternatives --config x-www-browser
update-alternatives --config x-www-browser
There are 5 choices for the alternative x-www-browser (providing /usr/bin/x-www-browser).Selection Path Priority Status
------------------------------------------------------------
0 /usr/bin/firefox 200 auto mode
1 /usr/bin/chromium 40 manual mode
2 /usr/bin/chromium-browser 40 manual mode
* 3 /usr/bin/firefox 200 manual mode
4 /usr/bin/google-chrome-stable 200 manual mode
5 /usr/bin/iceweasel 70 manual modePress enter to keep the current choice *, or type selection number: 5
update-alternatives: using /usr/bin/iceweasel to provide /usr/bin/x-www-browser (x-www-browser) in manual mode
that would lead me to believe that your x-www-browser pref is set to something other than your iceweasel. What does it list for the browser when you enter the following in a terminal?
sudo update-alternatives --config x-www-browser
I had to edit menu.xml and in there it was executing "firefox" (which was coming up as Iceweasel 13)
I probably changed that several years ago and forgot about it.
Just realized the problem, I had been launching Iceweasel from Openbox instead of the CLI.
Somehow obmenu is launching an older version of Iceweasel (version 13) and I never noticed till now :-/
If I launch "iceweasel" from a terminal I get version 31.
Oops!
Quoting pjbrunet: "hardware beep beep beep every time!"
Right after starting the computer, how many beeps do you hear before the BIOS screen appears?
Adding the Waldorf source stopped the beeps. Straight Debian I would even get a hardware beep if I backspaced too far on the CLI (very loud at 4am)
From what I remember, one beep upon reboot and another upon startup (booting) I think the startup beep was lower frequency.
I just did a fresh Waldorf 64 install last night and tried installing pytyle2 and couldn't get it working. So I tried installing pytyle and pytyle3, which I think was a bad idea because pytyle2 is awesome.
Turns out, maybe I just forgot to press Alt-A and it really was working fine. Alt-A might not be necessary if you edit .config/pytyle2/config.ini which is probably how I forgot about Alt-A.
I followed the xaos52 instructions and I think this is all you need to do with Waldorf:
apt-get install mercurial
hg clone https://code.google.com/p/pytyle/
cd pytyle
apt-get install python-xpyb
python setup.py build
python setup.py install
pytyle2&
( Then press Alt-A to activate it...remeber edit your config.ini )If I left anything out, I will be back to this page whenever I get a new laptop ;-)
This has always worked for me but I upgraded to Debian 8 and now it doesn't...
Traceback (most recent call last):
File "/usr/local/bin/pytyle2", line 27, in <module>
import pt.state as state
File "/usr/local/lib/python2.7/dist-packages/pt/state.py", line 272, in <module>
init()
File "/usr/local/lib/python2.7/dist-packages/pt/state.py", line 20, in init
load_properties()
File "/usr/local/lib/python2.7/dist-packages/pt/state.py", line 109, in load_properties
update_property(pname)
File "/usr/local/lib/python2.7/dist-packages/pt/state.py", line 155, in update_property
m()
File "/usr/local/lib/python2.7/dist-packages/pt/state.py", line 199, in update_NET_CURRENT_DESKTOP
properties['_NET_CURRENT_DESKTOP'] = ptxcb.XROOT.get_current_desktop()
File "/usr/local/lib/python2.7/dist-packages/pt/ptxcb/window.py", line 564, in get_current_desktop
return self._get_property('_NET_CURRENT_DESKTOP')[0]
IndexError: list index out of range
Hi there pjbrunet
I'm running sid, and have done so for about four months. My way of doing an upgrade is pretty simple. I start out with a fresh install of #! and don't run the cb-welcome upgrade script. Then in the sources.list I just keep one line (changed to sid):
deb http://http.debian.net/debian sid main contrib non-free
Delete the /etc/apt/preferences file.
Then:sudo apt-get purge tint2 tint2conf slimconf
Then:
sudo service slim stop
Login and:
sudo su
Then:
apt-get update && apt-get dist-upgrade --no-install-recommends
Then:
apt-get install tint2
Restart your computer:
reboot
Now you are running sid
I did something similar to that. Initially I had no preferences files (as other people said, and no mention of CB in sources.list) but only added it back because after the dist-upgrade (which seemed to go smoothly) I had no GUI just a blue-gray blank screen.
(Speaking of uninstalling Tint2, yes I had to uninstall some things to get the dist-upgrade to work. Like PHP5 for example.)
Now I'm wondering if I can get my openbox/autostart.sh working again...
Wow I fell waaay down the rabbit hole and ended up with a blank blue-gray screen of death.
I thought that was it, toasted machine.
Control-Alt-1 got me to a command prompt LOL. (Learned something new.)
Then I tried dozens of commands, rebooting rebooting rebooting, hardware beep beep beep every time!
This is 4am *crunch* *bang*
What was I thinking? Anyway, nothing was working and I kept hearing about "Sid" so I did this...
## CRUNCHBANG
## Compatible with Debian Wheezy, but use at your own risk.
deb http://packages.crunchbang.org/waldorf waldorf main
#deb-src http://packages.crunchbang.org/janice janice main# DEBIAN
deb http://http.debian.net/debian sid main contrib non-free
#deb-src http://http.debian.net/debian jessie main contrib non-free# DEBIAN SECURITY
#deb http://security.debian.org/ sid/updates main
#deb-src http://security.debian.org/ jessie/updates main
and
Package: *
Pin: release n=waldorf
Pin-Priority: 1001Package: *
Pin: release n=sid
Pin-Priority: 500
Still blue screen of death, no openbox. Everything I tried said "no display".
Then I did "apt-cache search crunchbang" and figured OK I'll just start installing crunchbang stuff till I get some kind of GUI I can work with. Then I did "apt-get upgrade cb-metapackage" which switched me to "slim" and I said Yes Yes Yes please overwrite my broken Debian junk with gray Crunchbang-ness. Rebooted and here I am, woohoo at least Openbox i working.
pj@modeblue:~$ cat /etc/*-release
PRETTY_NAME="Debian GNU/Linux 8 (jessie)"
NAME="Debian GNU/Linux"
VERSION_ID="8"
VERSION="8 (jessie)"
ID=debian
HOME_URL="http://www.debian.org/"
SUPPORT_URL="http://www.debian.org/support/"
BUG_REPORT_URL="https://bugs.debian.org/"
Comment out the janice repo and remove the preference pinning. Backup important data and prepare3 for breakage...
http://crunchbang.org/forums/viewtopic.php?id=29337
http://crunchbang.org/forums/viewtopic.php?id=37931
http://crunchbang.org/forums/viewtopic.php?id=38111
I got stuck on some errors and keyring stuff so decided to be less ambitious...
## CRUNCHBANG
## Compatible with Debian Wheezy, but use at your own risk.
#deb http://packages.crunchbang.org/janice janice main
#deb-src http://packages.crunchbang.org/janice janice main# DEBIAN
deb http://http.debian.net/debian jessie main contrib non-free
#deb-src http://http.debian.net/debian jessie main contrib non-free# DEBIAN SECURITY
deb http://security.debian.org/ jessie/updates main
#deb-src http://security.debian.org/ jessie/updates main
I'll try upgrading Firefox once I get Janice working.
I have this now, but I read a comment here "https://jschueths.wordpress.com/2014/04 … t-release/" saying "Janice repository for CrunchBang is empty, so “deb http://packages.crunchbang.org/janice janice” is completely useless. If you want to use cb- packages you must keep waldorf line here."
## CRUNCHBANG
## Compatible with Debian Wheezy, but use at your own risk.
deb http://packages.crunchbang.org/janice janice main
#deb-src http://packages.crunchbang.org/janice janice main# DEBIAN
deb http://http.debian.net/debian jessie main contrib non-free
#deb-src http://http.debian.net/debian jessie main contrib non-free# DEBIAN SECURITY
deb http://security.debian.org/ jessie/updates main
#deb-src http://security.debian.org/ jessie/updates maindeb http://cdn.debian.net/debian unstable main
deb http://mozilla.debian.net/ experimental iceweasel-aurora
Also I need help with my preferences file.
This is what I have
Package: *
Pin: release a=janice
Pin-Priority: 1001Package: *
Pin: release a=jessie
Pin-Priority: 500
maybe you should mention which browser you speak of...
wheezy should have iceweasel 31 and that is what is in jessie also, so not sure switching to jessie is a fix for your problem
not sure which backports you are using but you can get iceweasel 35 for wheezy from http://mozilla.debian.net/
I always download the browser from the guys that actually make the browser. I don't need a middleman slowing down my browser's security updates.
the middleman in this case works for mozilla so probably about as quick as it gets
That's what they said on Hacker News too... https://news.ycombinator.com/item?id=8988485 LOL.
I had "deb http://mozilla.debian.net/ wheezy-backports iceweasel-release" in my sources.list. My Iceweasel user agent at this moment says "Firefox/13.0"! Maybe I pinned something wrong to be stuck on Firefox 13?
I will try installing Aurora after Jessie installs.
I'm going to try getting Jessie and hope I don't break everything.
Lately I have nag messages everywhere I go: "Your browser is too old." It's irritating, but on the other hand I appreciate the scolding.
Is there any way to get automatic updates? Seems like with Iceweasel I can never keep up. I just upgraded to Wheezy and got the backports and I'm still waaay behind.
I'm still getting nag messages everywhere. Google says anything < 2 latest versions is unsupported.
What can I do? Switch browsers?
Is there any way to get "one click" browser upgrades with Debian?
UPDATE: The problem was obmenu wasn't really executing Iceweasel.
What did work was deleting the files in /var/lib/dpkg/info/adobe-flashplugin*.
That solved it for me...
/var/lib/dpkg/info# rm -rf adobe-flash*
apt-get remove adobe-flashplugin
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
adobe-flashplugin
0 upgraded, 0 newly installed, 1 to remove and 2 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue [Y/n]?
(Reading database ...
dpkg: warning: files list file for package `adobe-flashplugin' missing, assuming package has no files currently installed.
(Reading database ... 191102 files and directories currently installed.)
Removing adobe-flashplugin ...
Copyright © 2012 CrunchBang Linux.
Proudly powered by Debian. Hosted by Linode.
Debian is a registered trademark of Software in the Public Interest, Inc.
Server: acrobat