Re: k3b doesn't remember the settings for my burner anymore

From: Mariano Kamp (mkamp_at_gmx.de)
Date: 08/31/03

  • Next message: Arnt Karlsen: "Re: Newbie Hardware/Partitioning" 
    To: Henning Moll <newsScott@gmx.de>, debian-user@lists.debian.org
Date: Sun, 31 Aug 2003 17:53:38 +0200

    Hallo Henning,

      I am not sure if I got you right.

    1) I added cdrom to my groups:
    mkamp@black:~$ groups
    mkamp cdrom audio cdrecording
    2) Restarted KDE. (What was that good for?)
    3) Launched K3B
    4) Ran Setup
    5) Ran Configure
    ... and configure just shows me readers not writers ;-( So it is still the
    same problem.

    Here are my access settings:

    mkamp@black:~$ ls -l /usr/bin/cdrecord*
    -rws--x--- 1 root cdrecording 142 2003-07-08 19:08
    /usr/bin/cdrecord
    -rwsr-xr-- 1 root cdrom 310060 2003-07-08 19:08
    /usr/bin/cdrecord.mmap
    -rwsr-xr-- 1 root cdrom 310476 2003-07-08 19:08
    /usr/bin/cdrecord.shm

    I then executed:
    mkamp@black:~$ sudo chgrp cdrecording /usr/bin/cdrecord*
    Password:
    mkamp@black:~$ ls -l /usr/bin/cdrecord*
    -rws--x--- 1 root cdrecording 142 2003-07-08 19:08
    /usr/bin/cdrecord
    -rwxr-xr-- 1 root cdrecording 310060 2003-07-08 19:08
    /usr/bin/cdrecord.mmap
    -rwxr-xr-- 1 root cdrecording 310476 2003-07-08 19:08
    /usr/bin/cdrecord.shm
    mkamp@black:~$ k3b

    Didn't work too. Didn't restart KDE. Neccessary?

    I then tried that:
    mkamp@black:~$ sudo chmod g+xw /usr/bin/cdrecord*
    mkamp@black:~$ ls -l /usr/bin/cdrecord*
    -rws-wx--- 1 root cdrecording 142 2003-07-08 19:08
    /usr/bin/cdrecord
    -rwxrwxr-- 1 root cdrecording 310060 2003-07-08 19:08
    /usr/bin/cdrecord.mmap
    -rwxrwxr-- 1 root cdrecording 310476 2003-07-08 19:08
    /usr/bin/cdrecord.shm

    With the same effect ;-(
      
    Anything else I can look for? The log files don't seem helpful to *me*.

    black:/home/mkamp# ls -ltr /var/log/
    total 1624
    [..]
    -rw-rw-r-- 1 root utmp 292584 2003-08-31 17:34 lastlog
    -rw-r----- 1 root adm 1138 2003-08-31 17:47 messages
    -rw-r----- 1 root adm 11721 2003-08-31 17:49 syslog
    -rw-r----- 1 root adm 4162 2003-08-31 17:49 daemon.log
    -rw-r----- 1 root adm 10173 2003-08-31 17:50 auth.log
    black:/home/mkamp# tail -f /var/log/auth.log /var/log/daemon.log
    /var/log/syslog
    ==> /var/log/auth.log <==
    Aug 31 17:45:24 black su[23723]: + pts/4 mkamp-root
    Aug 31 17:45:24 black su(pam_unix)[23723]: session opened for user root by
    (uid=1000)
    Aug 31 17:47:54 black sudo: mkamp : TTY=pts/0 ; PWD=/home/mkamp ; USER=root
    ; COMMAND=/bin/chmod g+xw /usr/bin/cdrecord /usr/bin/cdrecord.mmap
    /usr/bin/cdrecord.shm
    Aug 31 17:49:07 black su[23853]: + pts/4 mkamp-root
    Aug 31 17:49:07 black su(pam_unix)[23853]: session opened for user root by
    (uid=1000)
    Aug 31 17:49:07 black su[23856]: + pts/2 mkamp-root
    Aug 31 17:49:07 black su(pam_unix)[23856]: session opened for user root by
    (uid=1000)
    Aug 31 17:50:24 black su[23940]: + pts/0 mkamp-root
    Aug 31 17:50:24 black su(pam_unix)[23940]: session opened for user root by
    (uid=1000)

    ==> /var/log/daemon.log <==
    Aug 31 17:41:32 black modprobe: modprobe: Can't locate module block-major-34
    Aug 31 17:41:32 black modprobe: modprobe: Can't locate module block-major-34
    Aug 31 17:45:25 black modprobe: modprobe: Can't locate module block-major-33
    Aug 31 17:45:25 black modprobe: modprobe: Can't locate module block-major-33
    Aug 31 17:45:25 black modprobe: modprobe: Can't locate module block-major-34
    Aug 31 17:45:25 black modprobe: modprobe: Can't locate module block-major-34
    Aug 31 17:49:08 black modprobe: modprobe: Can't locate module block-major-33
    Aug 31 17:49:08 black modprobe: modprobe: Can't locate module block-major-33
    Aug 31 17:49:08 black modprobe: modprobe: Can't locate module block-major-34
    Aug 31 17:49:08 black modprobe: modprobe: Can't locate module block-major-34

    ==> /var/log/syslog <==
    [..]
    (same as in daemon.log)

    Mariano

    On Saturday 30 August 2003 23:07, Henning Moll wrote:
    > On Saturday 30 August 2003 19:11, Mariano Kamp wrote:
    > > I ran kb3 setup and it detects my devices properly, but when
    > > relaunching k3b it still doesn't remeber them anymore.
    >
    > Maybe, this is your problem:
    >
    > after a fresh install of package cdrecord, its main files have these
    > permissions:
    >
    > # ls -la /usr/bin/cdrecord*
    > -rwxr-xr-x 1 root root 142 2003-07-08 19:08 cdrecord
    > -rwsr-xr-- 1 root cdrom 310060 2003-07-08 19:08 cdrecord.mmap
    > -rwsr-xr-- 1 root cdrom 310476 2003-07-08 19:08 cdrecord.shm
    >
    > running k3bsetup changes this to
    >
    > # ls -la /usr/bin/cdrecord*
    > -rwsr-x--- 1 root cdrecording 142 2003-07-08 19:08 cdrecord
    > -rwsr-xr-- 1 root cdrom 310060 2003-07-08 19:08 cdrecord.mmap
    > -rwsr-xr-- 1 root cdrom 310476 2003-07-08 19:08 cdrecord.shm
    >
    > which is fine for most distributions (including debian/woody) but not
    > debian/sid, because /usr/bin/cdrecord is not a binary anymore but a shell
    > script wrapper to cdrecord.mmap resp. cdrecord.shm. The real binary files
    > (mmap/shm) also need to be in group cdrecording:
    >
    > # chgrp cdrecording cdrecord.mmap cdrecord.shm
    >
    > or, as an alternative to the last command, you can add yourself to group
    > cdrom. (Don't forget to restart KDE before testing k3b...)
    >
    > Henning 

    -- 
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
  • Next message: Arnt Karlsen: "Re: Newbie Hardware/Partitioning"