[Dapper] After last update, I have no documents in yelp

Bug #38588 reported by Ricardo Pérez López
8
Affects Status Importance Assigned to Milestone
yelp (Ubuntu)
Fix Released
Medium
Ubuntu Desktop Bugs

Bug Description

After the last update (april, 7th), when I open yelp I get an almost blank document, that's all. Screenshot following.

Revision history for this message
Ricardo Pérez López (ricardo) wrote : Screenshot

The yelp documentation is empty :/

Revision history for this message
Daniel Holbach (dholbach) wrote :

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs which you find.

Please run "sudo scrollkeeper-rebuilddb" to resolve the issue.

Changed in yelp:
assignee: nobody → desktop-bugs
status: Unconfirmed → Fix Released
Revision history for this message
Sebastien Bacher (seb128) wrote :

Do you do daily updates? Can you run "dpkg -S /var/lib/scrollkeeper/C/scrollkeeper_cl.xml"?

Revision history for this message
Ricardo Pérez López (ricardo) wrote :

I do «sudo scrollkeeper-rebuilddb» as Daniel pointed me above, and now the problem is solved.

Thanks a lot.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Could you reply to my comment anyway? You should not have to run that by hand after update, it would be useful to figure what broken it for you

Revision history for this message
Ricardo Pérez López (ricardo) wrote :

Of course:

ricardo@yuggoth $ dpkg -S /var/lib/scrollkeeper/C/scrollkeeper_cl.xml
dpkg: /var/lib/scrollkeeper/C/scrollkeeper_cl.xml not found.

And this is my locale:

ricardo@yuggoth:~ $ locale
LANG=es_ES.UTF-8
LANGUAGE=es_ES:es:en_GB:en
LC_CTYPE="es_ES.UTF-8"
LC_NUMERIC="es_ES.UTF-8"
LC_TIME="es_ES.UTF-8"
LC_COLLATE="es_ES.UTF-8"
LC_MONETARY="es_ES.UTF-8"
LC_MESSAGES="es_ES.UTF-8"
LC_PAPER="es_ES.UTF-8"
LC_NAME="es_ES.UTF-8"
LC_ADDRESS="es_ES.UTF-8"
LC_TELEPHONE="es_ES.UTF-8"
LC_MEASUREMENT="es_ES.UTF-8"
LC_IDENTIFICATION="es_ES.UTF-8"
LC_ALL=

I don't know if this could help.

Revision history for this message
Mario Vukelic (kreuzsakra) wrote :

Sebastien, just FYI, I have the same result for dpkg -S, the file is not found.

I am the guy who first added a comment in #35670 (scrollkeeper-rebuilddb exiting without doing anything), and then opened #37577 after you told me that this was a different issue.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Do you do daily updates? Or is that likely you updated from a bug ekiga package not update for some weeks when that happened?

Revision history for this message
Mario Vukelic (kreuzsakra) wrote :

I've done more or less daily updates for the last 3 months or so, in Dec/Jan I made none for 2 or 3 weeks due to vacation.

Revision history for this message
Mario Vukelic (kreuzsakra) wrote :

I have aptitude logs back to October 05. I find those ekiga updates:

Jan 31: [INSTALL, DEPENDENCIES] ekiga
Feb 1: ekiga 1.99.0-0ubuntu2 -> 1.99.0-0ubuntu3
Feb 3: ekiga 1.99.0-0ubuntu3 -> 1.99.0-0ubuntu4
Feb 16: ekiga 1.99.0-0ubuntu4 -> 1.99.1-0ubuntu2
Feb 27: ekiga 1.99.1-0ubuntu2 -> 1.99.1-0ubuntu3
March 2: ekiga 1.99.1-0ubuntu3 -> 1.99.1-0ubuntu4
March 15: ekiga 1.99.1-0ubuntu4 -> 2.0.1-0ubuntu1
March 18: ekiga 2.0.1-0ubuntu1 -> 2.0.1-0ubuntu2
March 28: ekiga 2.0.1-0ubuntu2 -> 2.0.1-0ubuntu3

Revision history for this message
Sebastien Bacher (seb128) wrote :

Do you use yelp daily? Or is that possible you had the issue for a week and didn't notice before?

Revision history for this message
Mario Vukelic (kreuzsakra) wrote :

Sebastien, if the question was for me, I have had the issue for a very long time, it might be even since I upgraded to Dapper. I use yelp very rarely (see #36478, which is a duplicate of #35670).

The OP, Ricardo, said it happened recently, but not how often he uses yelp.

Revision history for this message
Ricardo Pérez López (ricardo) wrote :

> The OP, Ricardo, said it happened recently, but not how often he uses yelp.

Very rarely. I had never used yelp in Dapper until some days ago.

Hope this help.

Revision history for this message
Sebastien Bacher (seb128) wrote :

That's probably a duplicate of the other issue that you just noticed, that's fixed now

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.