Opensuse 13.1 - Nvidia - Desktop Search

I made an earlier post relating all the grief I had experienced with installing the nvidia drivers. Although I had followed all the troubleshooting advice I could gather, the screen resolution was absolutely horrendous.
I had settled on the Nouveau driver since with 13.1 I was able to have OpenGL support which was impossible with 12.3.
Right after I heard that the nvidia repo was pulled. It reappeared a few days later. So I surmised some pesky bug was fixed. Being a glutton for punishment I gave it one more try. All went well (I used the one-click method since I could not find any difference between that and the “hard-way”). All went well, the driver installed correctly.

Right after I noticed that desktop search began acting up. I could no longer perform searches, dolphin always returned no results.
These few lines are a summary of the suggested solutions:

                              If Akonadi does not start, delete the config files in ~/.config/akonadi and in ~/.local/share/akonadi
Then run: 
kbuildsycoca4 --noincremental


    Also If Nepomuk is acting up also then delete ~/.kde4/share/apps/nepomuk - this particular suggestion is not really useful.

Reboot

I did another clean install, re-installed the nvidia drivers, keeping an eye on the activities of desktop search the whole time.

It did not take long for things to revert to a broken desktop search.

Another clean install but this time I stayed with nouveau and desktop search is stable and indexing.

Obviously something is broken. Whether it is nvidia, or akonadi or nepomuk, I don’t know.

A listing of lspci is below - should this be deemed interesting.

============= lspci ===============
linux-lmhy:/home/henry # lspci
00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port (rev 09)
00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b4)
00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b4)
00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b4)
00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b4)
00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation HM65 Express Chipset Family LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family 6 port SATA AHCI Controller (rev 04)
00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 04)
01:00.0 VGA compatible controller: NVIDIA Corporation GF119M [GeForce GT 520M] (rev a1)
01:00.1 Audio device: NVIDIA Corporation GF119 HDMI Audio Controller (rev a1)
02:00.0 Network controller: Qualcomm Atheros AR9287 Wireless Network Adapter (PCI-Express) (rev 01)
03:00.0 SD Host controller: Ricoh Co Ltd MMC/SD Host Controller (rev 09)
03:00.1 System peripheral: Ricoh Co Ltd Device e232 (rev 06)
03:00.3 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 PCIe IEEE 1394 Controller (rev 05)
04:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host Controller (rev 04)
05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)

You are not alone. Here (openSUSE 12.3 64but, Nvidia 260GTX) was a downgrade to 319.32 the solution.
https://devtalk.nvidia.com/default/topic/633706/linux/recent-drivers-cause-applications-to-hang-not-start-at-all-or-compilation-failures/

https://devtalk.nvidia.com/default/topic/659230/linux/331-20-on-x86_64-breaks-signal-processing-/

Kieltux wrote:

>
> You are not alone. Here (openSUSE 12.3 64but, Nvidia 260GTX) was a
> downgrade to 319.32 the solution.
> ’
> https://devtalk.nvidia.com/default/topic/633706/linux/recent-drivers-cause-applications-to-hang-not-start-at-all-or-compilation-failures/
> (http://tinyurl.com/onuc8cn)
>
> http://tinyurl.com/qcjqvao
>
>

Thank you for that link! I thought I had a flaky hardware problem, but it
looks like this could be the cause. My symptoms: mysqld not terminating,
causing akonadi failures the NEXT time I logged in. (oS 12.3, nVidia GT640)

Guess it’s time to go back to 319.32(or .49).

Not sue those will work with 13.1. Uninstall the version you have and install again via yast repos. NVIDIA is now available there.

To be honest though I don’t see how a video driver would produce the symptoms you are seeing. Maybe it is time to run smartctrl to check the health of the drive.

gogalthorp wrote:

>
> Not sue those will work with 13.1. Uninstall the version you have and
> install again via yast repos. NVIDIA is now available there.
>

As I said, this system is still on 12.3 - 319.32 was running just fine,
until updated to 331 - both from the openSUSE nVidia repo. To downgrade
though it looks like I’ll have to fall back to the “tedious” way.

> To be honest though I don’t see how a video driver would produce the
> symptoms you are seeing. Maybe it is time to run smartctrl to check the
> health of the drive.
>

You must be psychic - I do have a failing drive, with a new disk ready to
pop in when I get time to do a full backup (/home is on a different drive)
and pull the box apart to get at it.

However, when I look at the at the URL above, I see random stuff where it
shouldn’t be, meaning that same random stuff is not where it should be,
meaning all bets are off about what causes what. GIGO.

On 2013-12-19 22:44, George Baltz wrote:
> gogalthorp wrote:

>> To be honest though I don’t see how a video driver would produce the
>> symptoms you are seeing. Maybe it is time to run smartctrl to check the
>> health of the drive.
>>
>
> You must be psychic - I do have a failing drive, with a new disk ready to
> pop in when I get time to do a full backup (/home is on a different drive)
> and pull the box apart to get at it.
>
> However, when I look at the at the URL above, I see random stuff where it
> shouldn’t be, meaning that same random stuff is not where it should be,
> meaning all bets are off about what causes what. GIGO.

You should stop anything else and replace that disk, ASAP, top priority.


Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)

Every now and again the crystal ball works. :slight_smile:
Yes replace the drive ASAP

Me too. But after the update to 331.20 we got here problems on 2 PCs with Akonadi and d-bus. Both PCs (and the HDDs) are in good condition. Then I started to look around and found user reports from Gentoo, Fedora, Arch Linux and so on with the same symptoms. A downgrade to 319.32 was the solution (for me).
Of course, it is always correct to check other things like drives with smartctl.