LinuxQuestions.org
Register a domain and help support LQ
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 11-04-2008, 05:56 AM   #1
heimdal
LQ Newbie
 
Registered: Nov 2007
Posts: 4

Rep: Reputation: 0
Problem with Slackware current KDE4 and HAL I guess


Dear all,

Another thread about hal/automount, but I didn't find any solutions in other threads.

What's the matter:
I installed my brand new Slack 12.1 upgrade to current then installed KDE4.1.
Until then no problem neither some KDE4 features are really slow, but that's not the subject.

The problem is that it is impossible to get automount works neither in KDE4 or XFCE.

All seems OK, hal is running well, my user is declared in all needed groups (cdrom, plugdev,video, audio and so on), but impossible to get an USBkey or a CDROM automount...

groups output:
users floppy audio video cdrom plugdev power scanner

ps aux| grep hal gives:
82 2952 0.0 0.1 5748 3608 ? Ss 11:01 0:01 /usr/sbin/hald --daemon=yes
root 2953 0.0 0.0 3164 1044 ? S 11:01 0:00 hald-runner
root 2957 0.0 0.0 3260 1052 ? S 11:01 0:00 hald-addon-input: Listening on /dev/input/event1 /dev/input/event7 /dev/input/event3 /dev/input/event4 /dev/input/event5
82 2965 0.0 0.0 2220 984 ? S 11:01 0:00 hald-addon-acpi: listening on acpid socket /var/run/acpid.socket
root 8225 0.0 0.0 2244 796 pts/0 S+ 11:57 0:00 grep hal

dmesg gives concerning inserting usbkey:
scsi 7:0:0:0: Direct-Access USB BAR 2.00 PQ: 0 ANSI: 2
ready
sd 7:0:0:0: [sdb] 256000 512-byte hardware sectors (131 MB)
sd 7:0:0:0: [sdb] Write Protect is off
sd 7:0:0:0: [sdb] Mode Sense: 03 00 00 00
sd 7:0:0:0: [sdb] Assuming drive cache: write through
sd 7:0:0:0: [sdb] 256000 512-byte hardware sectors (131 MB)
sd 7:0:0:0: [sdb] Write Protect is off
sd 7:0:0:0: [sdb] Mode Sense: 03 00 00 00
sd 7:0:0:0: [sdb] Assuming drive cache: write through
sdb: sdb1
sd 7:0:0:0: [sdb] Attached SCSI removable disk
sd 7:0:0:0: Attached scsi generic sg1 type 0
usb-storage: device scan complete

If you have any idea...

thanks

Last edited by heimdal; 11-04-2008 at 06:43 AM. Reason: adding groups command outputs
 
Old 11-04-2008, 03:56 PM   #2
heimdal
LQ Newbie
 
Registered: Nov 2007
Posts: 4

Original Poster
Rep: Reputation: 0
Solved by a downgrade of the system in 12.1 state and not current anymore. And it works perfectly (even if KDE4 still slow)
 
Old 11-04-2008, 04:15 PM   #3
tomtomjkw
Member
 
Registered: Jan 2008
Distribution: Slackware64-current
Posts: 127

Rep: Reputation: 31
It was enough to downgrade hal - the package from current has well known bug.
 
Old 11-04-2008, 04:38 PM   #4
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 5,223

Rep: Reputation: Disabled
Quote:
Originally Posted by tomtomjkw View Post
It was enough to downgrade hal - the package from current has well known bug.
What well-known bug?
I run slackware-current with KDE 4.1.2 and automounting removable devices works without problem.

Eric
 
Old 11-04-2008, 08:29 PM   #5
T3slider
Senior Member
 
Registered: Jul 2007
Distribution: Slackware64-14.1
Posts: 2,247

Rep: Reputation: 625Reputation: 625Reputation: 625Reputation: 625Reputation: 625Reputation: 625
The 'problem' is likely that you didn't install the now-essential parted package if you want to use HAL from -current. From the ChangeLog:
Code:
l/parted-1.8.8-i486-1.tgz:  Moved from /extra (this is now a HAL dependency).
 
Old 11-05-2008, 01:14 AM   #6
heimdal
LQ Newbie
 
Registered: Nov 2007
Posts: 4

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by T3slider View Post
The 'problem' is likely that you didn't install the now-essential parted package if you want to use HAL from -current. From the ChangeLog:
Code:
l/parted-1.8.8-i486-1.tgz:  Moved from /extra (this is now a HAL dependency).
Damn, error. You're not far from the truth, I do not read the changelog when I perform the upgrade.
I read it for major release but not for an upgrade with current (since my first slack installation with the 10.0, it's the first time I have problem with the chnagelog ...)

Thanks for the information!
 
Old 11-05-2008, 02:03 AM   #7
tomtomjkw
Member
 
Registered: Jan 2008
Distribution: Slackware64-current
Posts: 127

Rep: Reputation: 31
It seems i shall write "I will read the changelog carefully" hundred times on the blackboard Thanks guys.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
KDE4.1 on current - problems running bgeddy Slackware 14 03-29-2009 12:57 PM
kde4.1.2 in current --- AmaroK crashes kded4 grissiom Slackware 5 10-15-2008 04:56 PM
Problem running HAL on fresh Slackware 12.1 installation on P1510 olefiver Slackware 3 08-19-2008 04:04 PM
Request for Testing - hal-0.5.11rc1 in -current rworkman Slackware 11 03-18-2008 01:23 PM
Aug 28 current : no HAL, no mouse, no good ! EvilBill Slackware 32 09-02-2006 08:19 PM


All times are GMT -5. The time now is 07:49 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration