You are not logged in.
Updated Waldorf images are available now.
These new images were built to address an issue with the live session, whereby under certain conditions the live session would spawn two X sessions. Whilst this bug only affected live sessions and was not present once an installation had been performed, I still figured it was worth addressing to ensure any live users can more accurately evaluate the system, before performing an installation.
Other changes have been kept to an absolute minimum and any existing Waldorf users should not need to perform a new installation, unless they wish to help with testing the install process.
Other minor changes of note are:
Iceweasel updated to version 16.0.1
To improve the out-of-the-box networking experience, users are now automatically added to the 'fuse' group. This should make mounting of remote filesystems somewhat easier for novice users.
Thunar should now startup without delay. This addresses a long standing issue with Thunar whereby under certain conditions it would pause whilst waiting to automount network filesystems.
Other minor usability fixes which have been documented on the forums over the past few weeks.
A massive thank you to everybody who has helped test and provide feedback on the previous Waldorf images -- I have received numerous messages from people who have said that Waldorf is developing into something quite special and this would not have been possible without you!
As always, your feedback is greatly appreciated, so please do not hesitate to post below!
Ex-developer of #! CrunchBang. Follow me on Twitter
Offline
There were two "fixes" suggested for the slow Thunar startup - one involved removing the package that auto-mounts the network shares, the other involved modifying a preferences file so it just doesn't try to auto-mount them. Which fix did you apply?
Offline
Congrats,
Keep digging.
Linux beginner.
Offline
@pvsage, no. 2.
I also rebuilt Thunar with a suggested patch, which delayed the action until after Thunar was open and running, but then read that the patch had been deprecated due to it causing other issues, so I removed it. Anyhow, I modified '/usr/share/gvfs/mounts/network.mount' from:
[Mount]
Type=network
Exec=/usr/lib/gvfs/gvfsd-network
AutoMount=true
to:
[Mount]
Type=network
Exec=/usr/lib/gvfs/gvfsd-network
AutoMount=false
This is currently done via a hook in the build process, but depending on feedback, I may look at patching the 'gvfs-backends' package.
Ex-developer of #! CrunchBang. Follow me on Twitter
Offline
yay. the crescendo cometh
Offline
Just ran the 32bit PAE version on a Compaq SR2010NX w/ 1G RAM, everything worked OOTB, including keyboard volume multimedia keys, though volume was muted on login. Graphics were fine on an Nivida 6150LE integrated card, system RAM usage was ~100M at login. Great work, I have a spare partition I can install this to shortly.
No install option available from the LIVE session?
One tiny, miniscule fraction of a niggle, the download site says the ISO is ~765M but both Transmission and Nautilus told me it was ~802M.
Any things you'd like specific feedback on, either running live or from the installed OS?
bunsenlabs 8) forum mod squad
Offline
No install option available from the LIVE session?
Not at the moment. While it is possible to launch the d-i from within an X session, it is prone to errors with mismatched kernels etc. If I get time, I will look into it some more and see if I can troubleshoot the problems. That said, it is not super-high on my list of priorities at the moment.
One tiny, miniscule fraction of a niggle, the download site says the ISO is ~765M but both Transmission and Nautilus told me it was ~802M.
I used Thunar to grab the approximate size. I am not sure why it reported differently
Any things you'd like specific feedback on, either running live or from the installed OS?
Not really, any feedback is helpful, especially about any issues you might find
Ex-developer of #! CrunchBang. Follow me on Twitter
Offline
Volume's been mute on first login with every CrunchBang I've used on my netbook and desktop since the first Statler release. What's up with that?
Offline
Volume's been mute on first login with every CrunchBang I've used on my netbook and desktop since the first Statler release. What's up with that?
Hmm, not too sure. Across numerous systems, my volume is set to about mid level on first boot, so my initial thoughts are that it could be hardware related. I will look into it.
Ex-developer of #! CrunchBang. Follow me on Twitter
Offline
^ I remember this happening to me once at first boot. Read somewhere that alsa runs lsmod to check if the snd modules have loaded. If not alsa won't execute the code to unmute sound...
ahh here it is.. http://bkhome.org/blog/?viewDetailed=01960
Offline
^ I remember this happening to me once at first boot. Read somewhere that alsa runs lsmod to check if the snd modules have loaded. If not alsa won't execute the code to unmute sound...
ahh here it is.. http://bkhome.org/blog/?viewDetailed=01960
Interesting, thank you for sharing the link.
Ex-developer of #! CrunchBang. Follow me on Twitter
Offline
Well, not exactly muted on my hardware (Radeon sound chip on the desktop, Intel "HD Audio" on the netbook); volume sliders just run all the way down, and mixer channel list completely unpopulated. Not really a big deal for me to add all the channels that first boot, but still...
...Of course, in Waldorf under Pulseaudio, things are...somewhat stranger.
Offline
Thanks for the UpDate!
@hhh says
No install option available from the LIVE session?
@Corenominal says
Not at the moment. While it is possible to launch the d-i from within an X session, it is prone to errors with mismatched kernels etc.
I continue use my Statler install almost Daily. I have downloaded and installed the 1st Waldorf some months ago. I used the Desktop install and had and Have no problems...
So, My Waldorf install is not the Norm?
OHCG #!, Jessie,, Siduction-13.1, Slackware 14, Bridge,, Sabayon 13.4,
Offline
Thanks Philip once again...I was expecting this update due to the frequent updates of the last few days
Other minor usability fixes which have been documented on the forums over the past few weeks.
Any relevant fix that we, existing Waldorf users, should apply?
Thank you very much.
Offline
Any relevant fix that we, existing Waldorf users, should apply?
Not that I can think of. The fixes were applied to packages, so you should have them already
Ex-developer of #! CrunchBang. Follow me on Twitter
Offline
Milozzy wrote:Any relevant fix that we, existing Waldorf users, should apply?
Not that I can think of. The fixes were applied to packages, so you should have them already
Cool, thanks!Are there fixes in the config files too, so that should be wise to update my config files or create a new user?
Offline
Are there fixes in the config files too, so that should be wise to update my config files or create a new user?
No, your configs should be all good
Ex-developer of #! CrunchBang. Follow me on Twitter
Offline
Milozzy wrote:Are there fixes in the config files too, so that should be wise to update my config files or create a new user?
No, your configs should be all good
Excellent, thanks again!!
Offline
The live install works flawlessly. With Thunar, I am able to access network shares as well as the other partitions on my hard drive, even without any root authorization.
After installing to my hard drive though, I am unable to access the other partitions on my hard drive.
Trying to mount them in Thunar tells me that I need to have authorization to mount them but fails to give me the opportunity to do so.
I support the candidate that will steal the least from me....
Offline
@afab4, thanks for the feedback, I will investigate.
Ex-developer of #! CrunchBang. Follow me on Twitter
Offline
Sorry for the delay, I was just able to install Waldorf and mess around a bit (life gets in the way and all)...
I can confirm afab4's bug. When Waldorf is installed, Thunar shows my internal partitions as mounted, but clicking on the drive's icon gives me a "Not Authorized" message. If I run gksu thunar, Thunar does not show those partitions, nor are they visible in either /media or /mnt.
The installer has a quirk that I've never seen with the Debian installer, and as a result it was pretty confusing. The installer labeled my install media (a USB stick) as sda and my hard drive as sdb, every other Debian install I've done it's been the opposite, sdb for the stick and sda for the hard drive. So, install GRUB (and format swap) to sdb was, as I said, confusing.
HTH, I can mess around more with it later and see what I can see.
@sqlpython, maybe we're just not using the same terminology? Yes, I can install Waldorf from the GRUB menu option (Live; Install; Memory Check, or something like that). I meant that once logged in to the Live desktop session, there is no menu item or desktop icon for "Install Waldorf to your hard drive", as there often is with Live CDs. A very minor observation on my part.
bunsenlabs 8) forum mod squad
Offline
I've taken the new installed and ran it in live mode on a Dell 1525 and a Dell mini 10.
The live system worked flawlessly on both units having tested wireless, browser, usb devices like my headset.
I installed Waldorf using the new iso on a 32 gig usbdrive using the Dell 1525 and the install came off fine.
The install also worked just fine on the Dell Mini 10 which has a dual monitor installed which came up just
fine during 1st boot of Waldorf.
I tried simple, LVM, LVM encrypted installs and the only confusion I had was during the usbdisk install when
I tried to install the boot loader to (HD2) and noticed the non-default grub installer had changed. It was a bit confusing to me to use /dev devices and had to look. I figured /dev/sdc would do this usbstick but found out that was rejected. finally /dev/sdc1 worked and it booted. Anyway, I wonder why they did away with say (hd2,0) specs??? Anyway, minor thing... Just have to get used to the new Debian way of doing things.
Also, if your going to install to a usbdisk, best not plug the target usbdrive in until you've got to the
install section, about keyboard settings, otherwise the install get's hung trying to figure out who's who...
Again, this was cheating and I don't consider it an error or bug... I had an old OS on that key and it would have confused my boot loader F12 on the dell as Waldorf was on another usbkey disk. So, there you go...
FYI,,
If there is something wrong with this one, I couldn't find it. Must be on the live side and I ran what I could.
Offline
This october release works again with my nForce2 desktop (the september releases did not)
Offline
The live install works flawlessly. With Thunar, I am able to access network shares as well as the other partitions on my hard drive, even without any root authorization.
After installing to my hard drive though, I am unable to access the other partitions on my hard drive.
Trying to mount them in Thunar tells me that I need to have authorization to mount them but fails to give me the opportunity to do so.
Seems that the only partitions being written to fstab are the ones selected to be used during install.
You can add the others manually and all is good.
A person who has a cat by the tail knows a whole lot more about cats than someone who has just read about them.
Mark Twain
Offline
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