Version: 1.6 (using KDE 3.5.0, Arch Linux) Compiler: Target: i686-pc-linux-gnu OS: Linux (i686) release 2.6.13-archck8 on a new konsole window, when i rightclick or press any menu items or open a new tab, it freezes for a few seconds and resumes work as usual. Subsequent opening of tabs or clicking on menus does not produce this freeze. So i ran strace on konsole and performed the operations (new tab or menu) and got this: read(3, "\26\264\202\t\360\0 \2\360\0 \2@\0 \2\0\0\0\0\226\0F\0"..., 32) = 32 read(3, "\1\1\263\t\0\0\0\0\0\0y\10\0\200\0\0\330\263\221\277;\253"..., 32) = 32 mmap2(NULL, 770048, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x41e0d000 open("/etc/mtab", O_RDONLY) = 13 fstat64(13, {st_mode=S_IFREG|0644, st_size=471, ...}) = 0 mmap2(NULL, 131072, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x41dd8000 read(13, "/dev/hdb6 / reiserfs rw 0 0\nnone"..., 131072) = 471 close(13) = 0 munmap(0x41dd8000, 131072) = 0 open("/proc/meminfo", O_RDONLY) = 13 fstat64(13, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0 mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x40aa8000 read(13, "MemTotal: 773928 kB\nMemFre"..., 1024) = 598 close(13) = 0 munmap(0x40aa8000, 4096) = 0 brk(0x86d7000) = 0x86d7000 It freezes at this place for 3 or 4 seconds and proceeds normally from there.. so this makes me wonder why it has to access mtab, and open /proc/meminfo and all when creating a new tab ? and why doesnt this happen when i open another tab? Will produce more info if requested. Thanks
This is known. The "entire" menu structure is not automatically created when Konsole starts up, only when the user firsts uses the menu (top menu or mouse menu). Konsole reads files under $KDEDIR and $KDEHOME; perhaps that is why it reads mtab.
What does reading an environment variable have to do with mtab and pausing for 4 seconds ? besides.. the main issue i face is the new tab.. what does that have anything to do with mtab and meminfo ? it wasnt happening in kde 3.4.X .. I'm sure something has crept in with 3.5..
Not environment variables... all the config files for KDE and Konsole are under $KDEHOME and $KDEDIR.... For example: % echo $KDEDIR /opt/KDEDIRS/branches/3.5 % echo $KDEHOME /home/kvh/.kdehome-3.5 This is nothing new... there are a few more options but the delay should be about the same in KDE 3.4.x
my query is.. why does this happen only for first tab in a konsole window and not on second, third or any other attempts ?
This has to do with when the entire menu structure is loaded. Nothing to do in KDE 3.5. Hopefully will be 'fixed' in KDE4