You are not logged in.
Hey,
i recently switched back to Archlinux with KDE and most of my problems i was able to fix with, but one error keeps occuring and i have no idea where even to begin looking: If my arch boots up, everything works fine. After a while of normal using (Browsing, Texteditor, Emails) the system kind of slows down. All running programs work fine, but for example it takes about 2 minutes to open the right-click-context-menu in dolphin or the terminal. Telepathy takes forever to show up a new Chat-Window (or any window other than the default contact-list, which is already open). Even shutdown/reboot takes forever to show up and then won't do much (At least i have never waited that long to see if it actually restarts). The laptop also runs an ubuntu and a windows 7, which are working fine. top and iotop show no processes, which are consuming lots of harddrive or cpu.
My problem is, i have no idea where to start looking.
I have an Acer Timeline X laptop. I had the problem before installing laptop-mode-utils and afterwards, currently i have it disabled. I would be happy about any input. If i should post more infos, please say so, as written, i'm currently a bit clueless as to where i should look ![]()
My current /etc/fstab:
/dev/sda10 / ext4 rw,relatime,data=ordered 0 1
/dev/sda5 none swap defaults 0 0
/dev/sda9 /home ext4 defaults,noatime 0 2Offline
This sound like problem that was torturing me for a long time on my Acer 5735 laptop.
When system slows down, go to Ksystemlog, and if you find error like this
[ 7300.537036] ACPI Exception: AE_TIME, Returned by Handler for
[EmbeddedControl] (20121018/evregion-501)
[ 7300.537056] ACPI Error: Method parse/execution failed.
you have problem described here
Patch is in 3.9.3 kernel, try to update system.
Offline
Thanks, i will try that.
Currently i have removed my entire home-folder and tried starting arch/kde with blank settings. Currently it is running, but i haven't done much yet instead of browsing and editing python-files....maybee there just was a problem with a kde setting i made ![]()
I'll report back here, if the problem occurs once more ![]()
Offline
I'll report back here, if the problem occurs once more
When that occurs, please include the output of free -l
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
total used free shared buffers cached
Mem: 3719540 3237636 481904 0 4700 1355704
Low: 3719540 3237636 481904
High: 0 0 0
-/+ buffers/cache: 1877232 1842308
Swap: 4095996 76308 4019688This is the current output, and that is roughly the same as the infos i got from running `top`, while the laptop was slow the last time.
Offline
That does not look too bad. You are using some swap space, but it is not hideous.
When unresponsive, is the disk access light on? This would indicate either the machine is thrashing servicing page faults, or, you have bad sectors on your disk.
Are there any I/O errors being reported in the journal or reported by dmesg ?
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
You can install and run iotop to check for heavy IO activity and who causes it. Also post the output of dmesg once the computer has entered the bad state somewhere and link it here so we can take a look.
Last edited by hachre (2013-05-22 18:52:21)
Offline
Thanks, i will try that.
Currently i have removed my entire home-folder and tried starting arch/kde with blank settings. Currently it is running, but i haven't done much yet instead of browsing and editing python-files....maybee there just was a problem with a kde setting i made
I'll report back here, if the problem occurs once more
The way you answered that leads one to think you haven't updated your system in awhile. You should update it before you try anything else out.
Offline
The Arch is a fresh install (Running ~3 Weeks), all packages are up-to-date and were updated once or twice a week.
i checked iotop one time while it was very slow, but it showed no processes that were heavily using the disk (nor did the harddrive-led flicker more often than usual). I will check for bad sectors, but neither of the other two systems have problems (Which doesnt say that much if the usage doesn't overlap, i know ... but i can hope...bad sectors are never good
)
Currently (After deleting my ~) i'm running mostly the default settings and it is working so far. I had changed the Colour-Theme and used some designs, maybe there was a problem with one of those Oo
Last edited by daishy (2013-05-22 21:15:48)
Offline
Hey,
i just encountered the error once again in a somewhat smaller version: I cant use dolphin right now (Its unbearably slow), kde-tools like amarok or ktorrent take ages to load and then dont respond, the rest of the system is a little bit slower, but still usable.
The slowdown occured after i plugged in a usb-stick. Even after unplugging it, the `error` occures. I pasted the current dmesg-output to pastebin:
Last edited by daishy (2013-05-26 16:23:46)
Offline
FWIW, those are normal messages that occur when you plug in a USB storage device. From what you posted there is no indication of why your system would be acting this way. Sorry ![]()
Offline
hey again,
i resurected this thread, because the error still occurs and so far none of the updates so far have changed anything. I'm up-to-date with my packages. Any time i plug in any kind of usb-stick/usb-drive kde becomes unusable. (Right-click-context-menu, KDE-Apps, ...). Any none KDE-App (Chromium for example) have no problems and work without problems. If i restart the laptop (via. reboot-command, the normal kde-reboot-button wont show up in this condition) the shutdown-process always takes a long time to kill kde4d.
Still no idea in which files to look for indicators as to what is wrong, so any request for files to post here are very welcome ![]()
Offline
Test this with a new user
bitcoin: 1G62YGRFkMDwhGr5T5YGovfsxLx44eZo7U
Offline
I just tested with a new user and unfortunatly it didn't make much of a difference. I will just reinstall the whole system and see if that brings any difference, once i find the time to do so ![]()
Offline
Me again. After having some time on my hand a few days ago I tried formatting&reinstalling the entire arch, which didnt' do much good. Shortly after the new installation the problem occured again and i wasnt able to reproduce it consequently yet. The first time i was using chromium, thunderbird, dolphin and gimp, maybee the system-settings, but not much more. This time around, on top to the normal KDE reacting very slow/not reacting at all, the laptop is not able to shut down properly (Not a single time so far. It always hangs at some point and stops reacting, i have to press the power-button).
But i noticed, if i do `kdesu dolphin` from a console, dolphin starts immediatly and i can use the root-instance without any problems (Starting, right-clicking), even if the bug occured and the dolphin startet with my normal user wont react. So it seems to be some kind of problem with the kde-instances associated with my user.
Does anyone have any clue where i could look any further? So far I still have no clue as to where to look or what do try
. I really dont want to look for another distro to use, i like my arch ![]()
Desperate Greetings,
Daishy
Offline
have you set up /etc/hosts and /etc/hostname properly?
also whats the output of groups as your user?
Offline
try rule out some things, perhaps ditch all desktop environments and dependencies, and try using i3 with dmenu.
https://wiki.archlinux.org/index.php/I3
its very easy to use
bitcoin: 1G62YGRFkMDwhGr5T5YGovfsxLx44eZo7U
Offline
Hey,
output of groups is
usersSo far i haven't added the user to any other groups (On the fresh install). On the old installation (With the same problem) the user was in a few more groups (storage, vboxusrs ...
Content of /etc/hostname is:
littlezombieCOntent of /etc/hosts is:
#
# /etc/hosts: static lookup table for host names
#
#<ip-address> <hostname.domain.org> <hostname>
127.0.0.1 localhost.localdomain localhost
::1 localhost.localdomain localhost
# End of fileI will try another environment, but I would bet the error will disappear, because only the kde-tools behave very slow, when the bug occurs. Firefox for example starts without any problems, while konquerer takes ages to even show.
Offline
Would you mind trying temporarily with some other distro (live-CD)? Ubuntu and/or Fedora if possible to see if you get the same results? (There's a live Fedora KDE spin available).
Offline
The same output or the same bug? On a second partition i had a kubuntu 13.04 running (Fresh install at the same time the first arch was installed), which didnt have this bug, and prior to this i had an ubuntu 13.04 which also didnt show any signs of the bug. Everytime a dualboot with a windows 7. I will add the fdisk -l output once i get back to my laptop.
Offline
I don't know how much you've googled already but found a couple things you could try,
In regards to the 60 second start time - this sounds suspiciously like a D-Bus timeout. Can you try running "qdbus" and see if that returns instantly (it should, with a long list of names).
Please check the permissions of /var/tmp/kdecache-$USER and optionally remove it (outside KDE)
also there seems to be some kde-stuff in /tmp/ you may try to remove (according to forum posts, I don't use KDE myself)
Last edited by ooo (2013-09-26 19:11:16)
Offline
For the first:
i only have qdbus-qt4 on my machine which produces the following output, returning instantly without the bug occuring (Since i dont know how to reproduce the bug exactly, i will wait a bit until the bug occures and append the output of the message later
)
littlezombie% qdbus-qt4
:1.1
org.kde.klauncher
:1.12
org.freedesktop.ScreenSaver
org.kde.ksmserver
org.kde.ksmserver-603
org.kde.screensaver
:1.13
org.kde.KWin
org.kde.kwin
org.kde.kwin-611
org.kde.kwin.Compositing
org.kde.kwin.Scripting
:1.15
org.freedesktop.Notifications
org.kde.DeviceNotifications
org.kde.StatusNotifierHost-617
org.kde.Telepathy.PresenceAppletActive
org.kde.plasma-desktop
:1.17
org.kde.JobViewServer
org.kde.kuiserver
:1.19
org.kde.knotify
:1.2
org.freedesktop.PowerManagement
org.freedesktop.PowerManagement.Inhibit
org.freedesktop.Telepathy.Client.KTp.Approver
org.kde.Solid.PowerManagement
org.kde.Solid.PowerManagement.PolicyAgent
org.kde.StatusNotifierWatcher
org.kde.kded
org.kde.keyboard
org.kde.networkmanagement
:1.21
org.freedesktop.Telepathy.AccountManager
org.freedesktop.Telepathy.ChannelDispatcher
org.freedesktop.Telepathy.MissionControl5
:1.22
org.kde.kwalletmanager
:1.24
org.kde.StatusNotifierItem-637-1
:1.25
:1.29
org.freedesktop.Akonadi.Control
org.freedesktop.Akonadi.Control.lock
:1.30
org.freedesktop.Akonadi
:1.34
org.kde.KResourcesManager
org.kde.krunner
:1.36
org.kde.yakuake
:1.38
org.kde.korgac
:1.40
org.kde.Polkit1AuthAgent
:1.42
org.kde.kmix
:1.44
org.kde.klipper
:1.46
org.kde.StatusNotifierItem-698-1
:1.47
org.kde.StatusNotifierItem-689-1
:1.48
org.kde.StatusNotifierItem-694-1
:1.49
org.freedesktop.Akonadi.Janitor
:1.5
org.kde.kglobalaccel
:1.50
:1.51
org.freedesktop.Akonadi.Agent.akonadi_akonotes_resource_0
org.freedesktop.Akonadi.Resource.akonadi_akonotes_resource_0
:1.52
org.freedesktop.Akonadi.Agent.akonadi_akonotes_resource_1
org.freedesktop.Akonadi.Resource.akonadi_akonotes_resource_1
:1.53
org.freedesktop.Akonadi.Agent.akonadi_maildispatcher_agent
org.freedesktop.Akonadi.MailDispatcherAgent
org.kde.akonadi_maildispatcher_agent-724
:1.54
org.freedesktop.Akonadi.Agent.akonadi_ical_resource_0
org.freedesktop.Akonadi.Resource.akonadi_ical_resource_0
:1.55
org.freedesktop.Akonadi.Agent.akonadi_maildir_resource_0
org.freedesktop.Akonadi.Resource.akonadi_maildir_resource_0
:1.56
org.freedesktop.Akonadi.Agent.akonadi_contacts_resource_0
org.freedesktop.Akonadi.Resource.akonadi_contacts_resource_0
:1.57
org.freedesktop.Akonadi.Agent.akonadi_nepomuk_feeder
org.kde.akonadi_nepomuk_feeder-730
:1.58
org.freedesktop.Akonadi.Agent.akonadi_newmailnotifier_agent
org.freedesktop.Akonadi.NewMailNotifierAgent
org.kde.akonadi_newmailnotifier_agent-740
:1.59
org.freedesktop.Akonadi.Agent.akonadi_sendlater_agent
org.freedesktop.Akonadi.SendLaterAgent
org.kde.akonadi_sendlater_agent-741
:1.60
org.freedesktop.Akonadi.Agent.akonadi_archivemail_agent
org.freedesktop.Akonadi.ArchiveMailAgent
org.kde.akonadi_archivemail_agent-720
:1.61
org.freedesktop.Akonadi.Agent.akonadi_mailfilter_agent
org.freedesktop.Akonadi.MailFilterAgent
org.kde.akonadi_mailfilter_agent-729
:1.64
:1.7
org.kde.kwalletd
:1.70
org.kde.dolphin-1158
:1.72
:1.9
org.kde.ActivityManager
org.kde.kactivitymanagerd
org.freedesktop.DBusPermissions are as follows:
drwx------ 10 daishy users 4096 26. Sep 23:33 kdecache-daishy
drwx------ 2 kdm kdm 4096 24. Sep 12:26 kdecache-kdm
drwx------ 3 root root 4096 26. Sep 13:48 kdecache-root
drwx------ 5 testuser users 4096 25. Sep 12:28 kdecache-testuserOffline
For the first:
i only have qdbus-qt4 on my machine which produces the following output, returning instantly without the bug occuring (Since i dont know how to reproduce the bug exactly, i will wait a bit until the bug occures and append the output of the message later)
the bug would have been if it had taken a very long time ![]()
did you try removing all that kde-stuff from /var/tmp and /tmp?
that seemed to have helped some people with similar issues
Offline
The same output or the same bug?
The same bug.
Please try the latest Fedora 20 KDE spin live-CD. It runs the same recent kernel as Arch does. This will help us rule out installation and/or kernel configuration problems. Kubuntu 13.04 seemed to work fine, so that's a start.
Also, please perform what hachre suggested: run iotop and take note of which processes make most of the IO when the problem occurs.
Offline
I'm currently waiting for the bug to happen (as i said, i havent figured out how to exactly reproduce the bug, most of the times it happens while plugin in an usb-drive, sometimes, like now, it has no problem with usb-drives)
Also, please perform what hachre suggested: run iotop and take note of which processes make most of the IO when the problem occurs.
From memory from earlier occurances of the bug, iotop/top showed no processes which took a lot of cpu / disk. Which is coherent with the other behaviour. For example, if my harddisc is under heavy load, I cant open a mediafile via konsole (vlc /link/to/my/file). While the bug is happening this is not even a slight problem. The system is responsive, just not the kde-applications/desktop
Please try the latest Fedora 20 KDE spin live-CD. It runs the same recent kernel as Arch does. This will help us rule out installation and/or kernel configuration problems. Kubuntu 13.04 seemed to work fine, so that's a start.
I will try that tomorrow.
the bug would have been if it had taken a very long time smile did you try removing all that kde-stuff from /var/tmp and /tmp?
that seemed to have helped some people with similar issues
I will once the bug occures, see above ![]()
And really, really thanks a lot for the help so far. I would think i'm not that new to arch/linux, but that bug still baffles me.
Edit:
Sooo, while writing this post i open jDownloader, Gimp, thunderbird, settings, ..., copied some files to get the bug to occur and it has.
qdbus-qt4: returned immediatly with the list from above
iotop: Shows no thread which is above 5% and no longer than a second
top:
617 daishy 20 0 3895172 162720 49236 S 5,0 4,4 1:21.46 plasma-desktop
512 root 20 0 326140 65296 50964 S 4,3 1,8 0:47.04 X
686 daishy 20 0 438148 29420 20388 S 3,7 0,8 0:08.22 yakuake
844 daishy 20 0 3552968 190116 55548 S 0,7 5,1 0:36.22 chromium
1041 daishy 20 0 1266784 78768 30380 S 0,7 2,1 0:26.04 chromium
4290 root 20 0 15688 1524 1100 R 0,7 0,0 0:00.06 top I did `killall -u daishy` (Because i couldnt log out of kde, because the logout button would freeze the system, same as the shutdown-button when the bug occures. Had to switch to a second console via strg+alt+f6 to do the killall) and removed everything in /tmp and /var/tmp. Logged in again, but that didn't change much.
Could it be, that the bug only occures, if I have reached a specific amount of disk-read/write or ram-limit? Or maybee some problems with the swap-space (i will try and disable it tomorrow).
Last edited by daishy (2013-09-26 20:59:09)
Offline