Results 1 to 5 of 5

Thread: Trouble with KDE4 Permission

  1. #1
    Join Date
    Apr 2014
    Location
    Kampala, Uganda
    Posts
    95

    Default Trouble with KDE4 Permission

    Hi,

    So I'm having trouble with permissions with applications, this seems to be following me around as I had the same problem while running openSUSE 13.2 until I upgraded to LEAP 42.2 3 days ago and I have never quite gotten a permanent solution.
    I managed to boot up my laptop but got the errors below;

    Configuration file "/home/username/.kde4/share/config/knotifyrc" not writable.Please contact your system administrator.

    I tried to start one of the applications - VirtualBox but got this instead

    Configuration file "/home/username/.config/VirtualBoxrc" not writable.

    Please contact your system administrator.

    Please help. Thanks.

  2. #2
    Join Date
    Apr 2014
    Location
    Kampala, Uganda
    Posts
    95

    Default Re: Trouble with KDE4 Permission

    Below is an extract from dmesg

    Code:
    651.612100] blk_update_request: I/O error, dev sda, sector 1077190712
    [  651.612109] sd 0:0:0:0: [sda] tag#5 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
    [  651.612110] sd 0:0:0:0: [sda] tag#5 Sense Key : Medium Error [current] 
    [  651.612112] sd 0:0:0:0: [sda] tag#5 Add. Sense: Unrecovered read error - auto reallocate failed
    [  651.612113] sd 0:0:0:0: [sda] tag#5 CDB: Write(10) 2a 00 0c 30 08 00 00 00 08 00
    [ 651.612115] Buffer I/O error on dev sda4, logical block 0, lost async page write
    [  651.612120] ata1: EH complete
    [  655.152339] ata1.00: exception Emask 0x0 SAct 0x2 SErr 0x0 action 0x0
    [  655.152341] ata1.00: irq_stat 0x40000008
    [  655.152343] ata1.00: failed command: READ FPDMA QUEUED
    [  655.152347] ata1.00: cmd 60/08:08:18:d4:4f/00:00:0d:00:00/40 tag 1 ncq 4096 in
                            res 41/40:08:18:d4:4f/00:00:0d:00:00/40 Emask 0x409 (media error) <F>
    [  655.152348] ata1.00: status: { DRDY ERR }
    [  655.152349] ata1.00: error: { UNC }
    [  655.155873] ata1.00: configured for UDMA/100
    [  655.155883] sd 0:0:0:0: [sda] tag#1 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
    [  655.155885] sd 0:0:0:0: [sda] tag#1 Sense Key : Medium Error [current] 
    [  655.155886] sd 0:0:0:0: [sda] tag#1 Add. Sense: Unrecovered read error - auto reallocate failed
    [  655.155888] sd 0:0:0:0: [sda] tag#1 CDB: Read(10) 28 00 0d 4f d4 18 00 00 08 00
    [  655.155890] blk_update_request: I/O error, dev sda, sector 223335448
    [  655.155904] ata1: EH complete
    [  655.388627] Aborting journal on device sda4-8.
    [  655.551561] EXT4-fs (sda4): Delayed block allocation failed for inode 29624863 at logical offset 0 with max blocks 2 with error 30
    [  655.551563] EXT4-fs (sda4): This should not happen!! Data will be lost
    
    [  655.551568] EXT4-fs error (device sda4) in ext4_writepages:2777: Journal has aborted
    [  655.551570] EXT4-fs (sda4): previous I/O error to superblock detected
    [  655.560783] EXT4-fs error (device sda4): ext4_journal_check_start:56: Detected aborted journal
    [  655.560784] EXT4-fs (sda4): Remounting filesystem read-only
    /etc/fstab

    Code:
    UUID=6a20db41-e7a0-40d0-ac66-6623b459103d swap swap defaults 0 0
    UUID=4798ec44-537f-45c7-90b1-b6d4c0632595 / btrfs defaults 0 0
    UUID=4798ec44-537f-45c7-90b1-b6d4c0632595 /boot/grub2/i386-pc btrfs subvol=@/boot/grub2/i386-pc 0 0
    UUID=4798ec44-537f-45c7-90b1-b6d4c0632595 /boot/grub2/x86_64-efi btrfs subvol=@/boot/grub2/x86_64-efi 0 0
    UUID=4798ec44-537f-45c7-90b1-b6d4c0632595 /tmp btrfs subvol=@/tmp 0 0
    UUID=4798ec44-537f-45c7-90b1-b6d4c0632595 /usr/local btrfs subvol=@/usr/local 0 0
    UUID=4798ec44-537f-45c7-90b1-b6d4c0632595 /.snapshots btrfs subvol=@/.snapshots 0 0
    UUID=e1f5da8d-34d3-41f1-adbf-b3124860b518 /home                ext4       acl,user_xattr        1 2
    UUID=eee24072-d26a-442c-ac9b-e25583ccc43e /opt                 xfs        nofail                1 2
    UUID=4540f81b-cc18-411c-9ad8-5020f579a04b /srv                 btrfs      nofail                0 0
    UUID=bc158f39-4260-4cae-8003-23630a7e0f1d /var                 ext4       acl,user_xattr        1 2

  3. #3
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    24,894

    Default Re: Trouble with KDE4 Permission

    As you see for yourself, there seem to be problems with sda4. As we can not see from the fstab what sda4 is (because it uses UUIDs), we have to find that:
    Code:
    ls -l /dev/disk/by-uuid/ | grep sda4
    Henk van Velden

  4. #4
    Join Date
    Apr 2014
    Location
    Kampala, Uganda
    Posts
    95

    Default Re: Trouble with KDE4 Permission

    Good point.

    Code:
    ls -l /dev/disk/by-uuid/ | grep sda4
    lrwxrwxrwx 1 root root 10 Apr 12 17:26 e1f5da8d-34d3-41f1-adbf-b3124860b518 -> ../../sda4
    Code:
    fdisk -l
    Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes                                                                                                                                          
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes                                                                                                                                             
    Disklabel type: dos                                                                                                                                                                             
    Disk identifier: 0x3d92cd28                                                                                                                                                                     
                                                                                                                                                                                                    
    Device     Boot     Start        End    Sectors  Size Id Type                                                                                                                                   
    /dev/sda1  *         2048   83892223   83890176   40G 83 Linux                                                                                                                                  
    /dev/sda2       154142720  162529279    8386560    4G 82 Linux swap / Solaris                                                                                                                   
    /dev/sda3       162529280  193984511   31455232   15G 83 Linux                                                                                                                                  
    /dev/sda4       204474368 1953523711 1749049344  834G 83 Linux

  5. #5
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    24,894

    Default Re: Trouble with KDE4 Permission

    Well, did you not come to any conclusion?

    Looking for the UUID e1f5da8d-34d3-41f1-adbf-b3124860b518 in your fstab, it shows that /home should be on there. It seems to be ext4. Checking it might be an important thing to do (and having a good backup also of course).

    And your dmesg lines also say it is now mounted read-only. Thus you can not write to it (which you blame on KDE only, but no other program can also).

    So, when you have no recent backup, you can still make one from the read only file system.

    Better check the disk. When there are no failures on disk, you could create the file system anew and restore the data.

    BTW, your CODE sections look a bit strange here and there. Please copy complete (prompt, command, output, next prompt) and paste between the CODE tags.
    Henk van Velden

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •