RE: [opensuse] slow desktop action and hangs after upgrade to 42.1
-----Ursprüngliche Nachricht----- Von: George Olson (SUSE list) Gesendet: Sa. 02.01.2016 01:02 An: suse , Betreff: [opensuse] slow desktop action and hangs after upgrade to 42.1
Hi everyone,
I just finished the installation of 42.1 in my laptop (#2 below). I am now tweaking it to make it work. My installation was a clean install of 42.1 into a separate root partition from my root partition of 13.2. I installed by means of the install dvd which I downloaded.
My home partition I am using is the same as the home partition I used for 13.2.
First problem - the graphics driver - fixed (I think). It is an intel i915 card with a discrete nVidia GM107M graphics card. I installed bumblebee with the proprietary nvidia driver according to this: https://en.opensuse.org/SDB:NVIDIA_Bumblebee
After that my system was able to boot into opensuse and kde. The hwinfo --gfxcard indicates that both the i915 driver and the nvidia driver are the ones installed.
Second problem - KDE had a significant delay whenever I tried to do anything. When I clicked on any icon, I had to wait between 10 and 30 seconds for the application to give any indication that it is opening up. It didn't matter if it was kwrite, konsole, the kicker button, yast, or firefox or chrome. Also if I hit alt-tab to switch between applications, sometimes I would have to wait for that to switch also, and watch the desktop hang.
I tried disabling desktop effects and switching the display backend driver to openGL something, and that seemed to help for about 1 minute, but then the delays and hangs would come back at random.
Your system is running baloo file indexing on the whole disk. The delays will be in the same moment as heavy disk activity I suppose. Once the indexing process has finished, the system will turn to be normally responsive. Log in your user and just let it run. Go to bed and when you wake up it should be O.K. This has normally nothing to do with conflicts. Try "top" from the command line to see that balloo indexer is running requiring a lot of CPU load. --- Alle Postfächer an einem Ort. Jetzt wechseln und E-Mail-Adresse mitnehmen! http://email.freenet.de/basic/Informationen -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/02/2016 08:49 AM, stakanov@freenet.de wrote:
Your system is running baloo file indexing on the whole disk. The delays will be in the same moment as heavy disk activity I suppose. Once the indexing process has finished, the system will turn to be normally responsive. Log in your user and just let it run. Go to bed and when you wake up it should be O.K. This has normally nothing to do with conflicts. Try "top" from the command line to see that balloo indexer is running requiring a lot of CPU load.
--- Alle Postfächer an einem Ort. Jetzt wechseln und E-Mail-Adresse mitnehmen! http://email.freenet.de/basic/Informationen
Ah, thank you! I was pretty concerned. I will wait until the baloo indexer finishes and then start working on it again. -- George Box #1: 13.2 | KDE 4.14 | AMD Phenom IIX4 | 64 | 16GB Box #2: 13.1 | KDE 4.12 | AMD Athlon X3 | 64 | 4GB Laptop #1: 13.1 | KDE 4.12 | Core i7-2620M | 64 | 8GB Laptop #2: 42.1 | KDE Plasma 5 | Core i7-4710HQ | 64 | 16GB -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 01/02/2016 08:49 AM, stakanov@freenet.de wrote:
Your system is running baloo file indexing on the whole disk. The delays will be in the same moment as heavy disk activity I suppose. Once the indexing process has finished, the system will turn to be normally responsive. Log in your user and just let it run. Go to bed and when you wake up it should be O.K. This has normally nothing to do with conflicts. Try "top" from the command line to see that balloo indexer is running requiring a lot of CPU load.
Is there a way to tell when baloo file indexing is complete, besides top? Is there a command line tool or something that you can type in that will say it is 90% or 100% or anything like that? -- George Box #1: 13.2 | KDE 4.14 | AMD Phenom IIX4 | 64 | 16GB Box #2: 13.1 | KDE 4.12 | AMD Athlon X3 | 64 | 4GB Laptop #1: 13.1 | KDE 4.12 | Core i7-2620M | 64 | 8GB Laptop #2: 42.1 | KDE Plasma 5 | Core i7-4710HQ | 64 | 16GB -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On January 2, 2016 12:07:21 AM PST, "George Olson (SUSE list)" <grglsn765@gmail.com> wrote:
On 01/02/2016 08:49 AM, stakanov@freenet.de wrote:
Your system is running baloo file indexing on the whole disk. The
delays will be
in the same moment as heavy disk activity I suppose. Once the indexing process has finished, the system will turn to be normally responsive. Log in your user and just let it run. Go to bed and when you wake up it should be O.K. This has normally nothing to do with conflicts. Try "top" from the command line to see that balloo indexer is running requiring a lot of CPU load.
Is there a way to tell when baloo file indexing is complete, besides top? Is there a command line tool or something that you can type in that will say it is 90% or 100% or anything like that?
No, but you may be on the track anyway. Baloo does not actually use that much resources anyway. Furthermore it doesn't index the whole disk in the default setup. If you have terabytes of disks to index it might take till morning but I doubt it. It can index just about as fast as it can read all the data. -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am Samstag, 02. Januar 2016 09:07 CET, "George Olson (SUSE list)" <grglsn765@gmail.com> schrieb:
Is there a way to tell when baloo file indexing is complete, besides top? Is there a command line tool or something that you can type in that will say it is 90% or 100% or anything like that?
Try balooctl status Sometimes, the tool gets stuck or something. Try to restart it. Regards, -- Aaron "Optimizer" Digulla a.k.a. Philmann Dark "It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits." http://blog.pdark.de/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
stakanov@freenet.de schreef op 02-01-2016 1:49:
Your system is running baloo file indexing on the whole disk. The delays will be in the same moment as heavy disk activity I suppose. Once the indexing process has finished, the system will turn to be normally responsive. Log in your user and just let it run. Go to bed and when you wake up it should be O.K. This has normally nothing to do with conflicts. Try "top" from the command line to see that balloo indexer is running requiring a lot of CPU load.
Just saying... if an indexing service can cause up to 8 second delays in system responsiveness, something is really really wrong. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (5)
-
Aaron Digulla -
George Olson (SUSE list) -
John Andersen -
stakanov＠freenet.de -
Xen