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?
@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
[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.
yay. the crescendo cometh
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?
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?
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.
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....
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.
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...
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.
This october release works again with my nForce2 desktop (the september releases did not)