Thanks, hotchili! Sounds horrible.

BTW, What's the reason to haste to udev-182 instead of staying with udev-175, while still using Linux-3.2 to let so many people suffer from the long delay on start-up?

... and to go so fast to the RC2 stage?

(I know there must be a reason I saw it somewhere but I just forgot it. So I'm asking. Thanks!)

I have an inherent distrust of new udev versions. However, 175 wasn't going to do it... that version had some firmware loading bugs that were breaking wireless drivers, and 182 fixed them. 182 has some problems as well, but overall they aren't nearly as bad.

Concerning RC2, if there's a big batch of updates, it's going to be called a new RC. Don't take those version numbers to indicate haste.

3 members found this post helpful.

Yes. You are right.
And if those who have problems with udev-182 have their problems solved with Linux-3.5 (at least one of them said so), could slackware-14 include a Linux-3.5 kernel config in the "testing" directory?

Thanks! I thought RC2 meant "much more close to a release". My mistake.

on the last minute... please update cdrtools to 3.01a8, 3.01a5 introduce a bug that prevent 7-zip open an iso image
the discuss is here
http://sourceforge.net/projects/seve.../topic/4944122

Here's a minor bug: XFCE does not show up in the KDM session chooser dialog

This should fix it:
The xfce4-session package should include this link since it is the package that includes the original xfce.desktop file.

Just for fun, run "slackpkg new-config" and find out what *.new files you have forgotten to take care of.

Eric

Remember THAT bug? Well, it's nearly 3 years later and the bug remains. I'm unsure if the bug is specifically related to Slackware or GNU/Linux in general since my solitary distribution of GNU/Linux is Slackware. I suspect a combination of problems.

For those members who aren't familiar with this bug, the main symptom is read or mount failure of a newly inserted disc. If the disc is inserted in the drive at boot, the disc can generally be read, mounted, and written without error. If the disc is inserted into the drive AFTER the operating system is booted, then the failures to read and mount begin. If a user manually reloads udev's rules and ejects the disc and then reinserts the disc, then it's generally possible to read and mount the disc without error ... but not always. In my experience the only method of ensuring an accurate read, mount, or write to an optical disc REQUIRES the disc to be inserted into the drive BEFORE the operating system is booted. The motherboard is a 5 year old M2N68-LA (Ivy) with nForce 430 chipset.

Sorry I don't remember that bug. Could you give us a pointer, as for instance a link to a thread about it?

Furthermore if you don't give more precise information, like error messages found in the logs, I really don't know what we can do to help you.

And IMHO this should be posted elsewhere, as the goal of this thread is to help iron out upcoming Slackware 14.

None, but I did not move over the /etc/kde/kdm/kdmrc. I wanted to keep my old one, so I removed that file. I don't think that is the issue, though.

I had previously grep'd /var/log/{packages,scripts} from 13.37 and 14.0 to see what package the file was apart of:

From 14.0
From 13.37
The file is not there in 14.0_RC2.

That is where you are wrong in your assumptions. There were some changes between Slackware 13.37 and 14.0 which require you to pay heed to the .new files (do not discard them so easily!).

... showing you that KDM will look in other directories too, now. And guess what's in one of them:
You're not the first one to fall for that trap, though.

Eric

OK. I turned on the light at the end of the tunnel. Do you see that? It’s white. Caution: don’t follow the red one – it leads to the bad womb.

(The explanation for the laymen: following the red light will result in reincarnation as a smart chimp in a zoo watching dumb people all day long or as a dumb politician watched by the smart people all day long. Misfortune.)

1 members found this post helpful.

Thanks for pointing this out! I should have known some obscure change was buried in that kdmrc file. This might be a good candidate for the CHANGES_AND_HINTS.TXT.

other problem on rc2...

install in virtualbox, connect via vnc, run xfce in it.
open a terminal with multi-tab, after some work, on the terminal can not input any char, CRTL+D doesn't work also. but ALT+# still working.
after drag the window with mouse, or do some switch between tabs, the keyboard is ok

do a check with the system, the difference is upgrade scim to 1.4.14. after I disable the scim program, the issue never happen again.

my locale is zh_CN.utf8, the scim is started in xinitrc with command: "scim -d"

I know the changelog says versions are frozen, but I was wondering if it'd be worth updating Perl, since there was a bug fix release recently.

1 members found this post helpful.