I have two cdwriters, one is as address sr0 ( a scsi device) the other sr1 (hdc) I have ide-scsi loaded as a module. Both devices have rwxrwxrwx permissions and I can read from both devices. Using cdbakeoven I can write to both devices but I can't use k3b or xcdroast on either device (even if I logon as root). Anybody any clues? Phil
On Sunday, 24 October 2004 16.48, Phil Burness wrote:
I have two cdwriters, one is as address sr0 ( a scsi device) the other sr1 (hdc) I have ide-scsi loaded as a module. Both devices have rwxrwxrwx permissions and I can read from both devices. Using cdbakeoven I can write to both devices but I can't use k3b or xcdroast on either device (even if I logon as root).
That's probably because those programs use resmgr, not unix permissions to gain access, while cdbakeoven presumably doesn't.
Anybody any clues?
I'm guessing suse 9.0, right? Please always mention that. Some of these things do vary between versions You need to add session required pam_resmgr.so to either /etc/pam.d/xdm or /etc/pam.d/kdm (I forget which, try both). Then log out, log back in and try again
On Sunday 24 October 2004 16:09, Anders Johansson wrote:
On Sunday, 24 October 2004 16.48, Phil Burness wrote:
I have two cdwriters, one is as address sr0 ( a scsi device) the other sr1 (hdc) I have ide-scsi loaded as a module. Both devices have rwxrwxrwx permissions and I can read from both devices. Using cdbakeoven I can write to both devices but I can't use k3b or xcdroast on either device (even if I logon as root).
That's probably because those programs use resmgr, not unix permissions to gain access, while cdbakeoven presumably doesn't.
Anybody any clues?
I'm guessing suse 9.0, right? Please always mention that. Some of these things do vary between versions
You need to add
session required pam_resmgr.so
to either /etc/pam.d/xdm or /etc/pam.d/kdm (I forget which, try both). Then log out, log back in and try again Anders, Thanks, it is v9.0. I looked in /etc/pam.d and I only had a xdm file no kdm. The xdm file already had the pam_resmgr.so in it so I created a kdm file and added that line but it didn't work.
Also, on a recent KDE upgrade to 3.3.0 the kdm stopped working so I switched to gdm but used a kde session. Using your clue above I upgraded to 3.3.1, switched back to kdm, restarted the X-Server logged in via KDM and hey-presto k3b and xcdroast work. Now I have a seperate problem.... When I reboot (with kdm) the booting hangs just at the starting SMB section. My workaround is to boot into init 3, then switch to init 5. I have no idea why this happens. Phil
On Monday, 25 October 2004 10.07, Phil Burness wrote:
On Sunday 24 October 2004 16:09, Anders Johansson wrote:
You need to add
session required pam_resmgr.so
to either /etc/pam.d/xdm or /etc/pam.d/kdm (I forget which, try both). Then log out, log back in and try again
Anders, Thanks, it is v9.0. I looked in /etc/pam.d and I only had a xdm file no kdm. The xdm file already had the pam_resmgr.so in it so I created a kdm file and added that line but it didn't work.
Also, on a recent KDE upgrade to 3.3.0 the kdm stopped working so I switched to gdm but used a kde session.
ok, then it should have been in /etc/pam.d/gdm, but never mind, you got it to work so all is well
Using your clue above I upgraded to 3.3.1, switched back to kdm, restarted the X-Server logged in via KDM and hey-presto k3b and xcdroast work.
Now I have a seperate problem.... When I reboot (with kdm) the booting hangs just at the starting SMB section. My workaround is to boot into init 3, then switch to init 5. I have no idea why this happens.
It is extremely unlikely that this has anything to do with kdm or the kde upgrade, since as far as I know, nothing related to kde is used that early in the boot process. Did you upgrade anything else? Anything interesting in the boot logs?
On Monday, 25 October 2004 10.07, Phil Burness wrote:
On Sunday 24 October 2004 16:09, Anders Johansson wrote:
You need to add
session required pam_resmgr.so
to either /etc/pam.d/xdm or /etc/pam.d/kdm (I forget which, try both). Then log out, log back in and try again
Anders, Thanks, it is v9.0. I looked in /etc/pam.d and I only had a xdm file no kdm. The xdm file already had the pam_resmgr.so in it so I created a kdm file and added that line but it didn't work.
Also, on a recent KDE upgrade to 3.3.0 the kdm stopped working so I switched to gdm but used a kde session.
ok, then it should have been in /etc/pam.d/gdm, but never mind, you got it to work so all is well
Using your clue above I upgraded to 3.3.1, switched back to kdm, restarted the X-Server logged in via KDM and hey-presto k3b and xcdroast work.
Now I have a seperate problem.... When I reboot (with kdm) the booting hangs just at the starting SMB section. My workaround is to boot into init 3, then switch to init 5. I have no idea why this happens.
It is extremely unlikely that this has anything to do with kdm or the kde upgrade, since as far as I know, nothing related to kde is used that early in the boot process. Did you upgrade anything else? Anything interesting in the boot logs? K3b has stopped writing to disks again. It see's the drives, but only shows
On Monday 25 October 2004 09:04, Anders Johansson wrote: them as readers even if I log in as root. I don't know why, but it worked for a while after I reloaded kdm as above. I've manually set the permissions on the drives to rwxrwxrwx but still no joy. Phil
On Wednesday, 27 October 2004 00.27, Phil Burness wrote:
K3b has stopped writing to disks again. It see's the drives, but only shows them as readers even if I log in as root. I don't know why, but it worked for a while after I reloaded kdm as above.
Did you change anything at all about the system?
I've manually set the permissions on the drives to rwxrwxrwx but still no joy.
No, as I said, those programs are set to use resmgr, not the regular unix permissions
On Wednesday 27 October 2004 00:20, Anders Johansson wrote:
On Wednesday, 27 October 2004 00.27, Phil Burness wrote:
K3b has stopped writing to disks again. It see's the drives, but only shows them as readers even if I log in as root. I don't know why, but it worked for a while after I reloaded kdm as above.
Did you change anything at all about the system?
I've manually set the permissions on the drives to rwxrwxrwx but still no joy.
No, as I said, those programs are set to use resmgr, not the regular unix permissions
I upgraded aaa_base via apt-get upgrade Phil
On Wednesday, 27 October 2004 01.48, Phil Burness wrote:
On Wednesday 27 October 2004 00:20, Anders Johansson wrote:
On Wednesday, 27 October 2004 00.27, Phil Burness wrote:
K3b has stopped writing to disks again. It see's the drives, but only shows them as readers even if I log in as root. I don't know why, but it worked for a while after I reloaded kdm as above.
Did you change anything at all about the system? <snip> I upgraded aaa_base via apt-get upgrade
only? OK, well, that *shouldn't* have changed anything relevant, but just the same check the contents of the files in /etc/pam.d Also look and see what's happening in /var/log/messages when you start k3b, perhaps resmgr is giving some error message (while you're at it, check and see if resmgrd is running at all)
On Wednesday 27 October 2004 00:41, Anders Johansson wrote:
On Wednesday, 27 October 2004 01.48, Phil Burness wrote:
On Wednesday 27 October 2004 00:20, Anders Johansson wrote:
On Wednesday, 27 October 2004 00.27, Phil Burness wrote:
K3b has stopped writing to disks again. It see's the drives, but only shows them as readers even if I log in as root. I don't know why, but it worked for a while after I reloaded kdm as above.
Did you change anything at all about the system?
<snip>
I upgraded aaa_base via apt-get upgrade
only?
OK, well, that *shouldn't* have changed anything relevant, but just the same check the contents of the files in /etc/pam.d
Also look and see what's happening in /var/log/messages when you start k3b, perhaps resmgr is giving some error message (while you're at it, check and see if resmgrd is running at all) resmgrd is running when I tail /var/log/messages I get
Oct 27 01:00:34 desktop resmgr[1307]: accepted connection from user pburness Oct 27 01:00:34 desktop resmgr[1307]: disconnect from pburness Oct 27 01:00:34 desktop resmgr[1307]: accepted connection from user pburness Oct 27 01:00:34 desktop resmgr[1307]: disconnect from pburness Oct 27 01:00:34 desktop resmgr[1307]: accepted connection from user pburness Oct 27 01:00:34 desktop k3b: resmgr: server response code 500 then more of above followed by Oct 27 01:00:34 desktop k3b: resmgr: server response code 502 Oct 27 01:00:34 desktop resmgr[1307]: disconnect from pburness Oct 27 01:00:34 desktop resmgr[1307]: accepted connection from user pburness Oct 27 01:00:34 desktop resmgr[1307]: disconnect from pburness Oct 27 01:00:34 desktop kernel: Device not ready. Make sure there is a disc in the drive. then more of the accept - disconnect stuff with server response code 502 & 501 and more of the Device not ready messages Can't see anything suspect in the pam.d directory but not sure what I should be looking for in there. Phil
On Wednesday, 27 October 2004 02.07, Phil Burness wrote:
pburness Oct 27 01:00:34 desktop k3b: resmgr: server response code 500 then more of above followed by Oct 27 01:00:34 desktop k3b: resmgr: server response code 502 Oct 27 01:00:34 desktop resmgr[1307]: disconnect from pburness Oct 27 01:00:34 desktop resmgr[1307]: accepted connection from user pburness Oct 27 01:00:34 desktop resmgr[1307]: disconnect from pburness Oct 27 01:00:34 desktop kernel: Device not ready. Make sure there is a disc in the drive. then more of the accept - disconnect stuff with server response code 502 & 501 and more of the Device not ready messages
This all looks perfect to me, just as it should be (I'm assuming there really isn't a disc in the drive). But you still can't see the device as a writer in k3b? That is weird. Are you sure you haven't changed anything else about the system?
On Wed, 27 Oct 2004 12:45, Anders Johansson wrote:
On Wednesday, 27 October 2004 02.07, Phil Burness wrote:
pburness Oct 27 01:00:34 desktop k3b: resmgr: server response code 500 then more of above followed by Oct 27 01:00:34 desktop k3b: resmgr: server response code 502 Oct 27 01:00:34 desktop resmgr[1307]: disconnect from pburness Oct 27 01:00:34 desktop resmgr[1307]: accepted connection from user pburness Oct 27 01:00:34 desktop resmgr[1307]: disconnect from pburness Oct 27 01:00:34 desktop kernel: Device not ready. Make sure there is a disc in the drive. then more of the accept - disconnect stuff with server response code 502 & 501 and more of the Device not ready messages
This all looks perfect to me, just as it should be (I'm assuming there really isn't a disc in the drive). But you still can't see the device as a writer in k3b? That is weird. Are you sure you haven't changed anything else about the system?
If you are using SuSE 9.1 and haven't rebooted your computer since Oct 20th 2004, I suggest you do so, as there was a new kernel update. SUSE Security Announcement Package: kernel Announcement-ID: SUSE-SA:2004:037 Date: Wednesday, Oct 20th 2004 18:00 MEST Affected products: 9.1 Additionaly the following non-security bugs were fixed: - Two CD burning problems. - USB 2.0 stability problems under high load on SMP systems. - Several SUSE Linux Enterprise Server issues. -- Regards, Graham Smith ---------------------------------------------------------
On Wednesday 27 October 2004 03:45, Anders Johansson wrote:
On Wednesday, 27 October 2004 02.07, Phil Burness wrote:
pburness Oct 27 01:00:34 desktop k3b: resmgr: server response code 500 then more of above followed by Oct 27 01:00:34 desktop k3b: resmgr: server response code 502 Oct 27 01:00:34 desktop resmgr[1307]: disconnect from pburness Oct 27 01:00:34 desktop resmgr[1307]: accepted connection from user pburness Oct 27 01:00:34 desktop resmgr[1307]: disconnect from pburness Oct 27 01:00:34 desktop kernel: Device not ready. Make sure there is a disc in the drive. then more of the accept - disconnect stuff with server response code 502 & 501 and more of the Device not ready messages
This all looks perfect to me, just as it should be (I'm assuming there really isn't a disc in the drive). But you still can't see the device as a writer in k3b? That is weird. Are you sure you haven't changed anything else about the system? I only use apt to upgrade / update and here are the last entries from the apt.log
Sat 23 Oct 2004 16:33:56 BST;upgrade;xpdf;2.02pl1-89 => 2.02pl1-141 Sat 23 Oct 2004 16:33:56 BST;upgrade;libtiff;3.5.7-307 => 3.5.7-376 Sun 24 Oct 2004 09:06:12 BST;install;xcdroast;0.98alpha14-44 Tue 26 Oct 2004 12:36:42 BST;upgrade;tetex;2.0.2-76 => 2.0.2-199 Tue 26 Oct 2004 12:36:42 BST;upgrade;aaa_base;9.0-7 => 9.0-10 As can be seen the only packages loaded since 25th when things where working are aaa_base and tetex. The only other thing that happened is that I rebooted into vmlinux-2.4.21-243 but that breaks my wireless connection so I rebooted back into vmlinux-2.4.21-99 could this have an effect? Phil
participants (3)
-
Anders Johansson -
Graham Smith -
Phil Burness