Many times after the boot of the PC the application lens doesn't return any result

Bug #1038221 reported by Nicola Jelmorini
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
unity-lens-applications
Incomplete
Undecided
Unassigned

Bug Description

I use Ubuntu 12.04 64bit, and I have found that frequently, when I boot my PC, the Applications Lens doesn't return any result.
To make the lens working again, I have to use the command "unity --replace" to restart unity.

So, to find out what's going wrong, I have stopped the process "unity-applications-daemon", and restarted it in a terminal. These are the error messages displayed:

#################################################################################
close: Descrittore di file errato <== (Bad file descriptor)
unable to join the environment

(process:4912): unity-applications-daemon-WARNING **: daemon.vala:121: Unable to open ratings database environment '/home/nicola/.cache/software-center/reviews.ubuntu.com_reviews_api_1.0_review-stats-pkgnames.p__5.1.db.dbenv': Risorsa temporaneamente non disponibile <== (Resource temporarily unavailable)
#################################################################################

I haven't found a mean to restart this lens without restarting all Unity, and I don't know why sometimes this issue happens and sometimes not.

summary: - Many times after reboot the PC the application lens doesn't return any
- result
+ Many times after the boot of the PC the application lens doesn't return
+ any result
Revision history for this message
Omer Akram (om26er) wrote :

on logi, open and close the dash. check open a terminal and check if unity-applications-daemon is actually running, paste the output the below command in this bug report. I am not sure if restarting unity does actually starts the application daemon, so it may as well be another issue.

Changed in unity-lens-applications:
status: New → Incomplete
Revision history for this message
Nicola Jelmorini (jelmorini) wrote :

Hi Omer,

I can confirm you that the "unity-applications-daemon" is already running after the boot of the PC. I don't need to open the Dash. In fact if I execute in a terminal the command "/usr/lib/unity-lens-applications/unity-applications-daemon" the response is:

"Another instance of the Unity Applications Daemon already appears to be running. Bailing out"

Then I open and close the Dash, but, as always, the Applications Lens has no result.

You ask me to paste the output of the "below command" in this bug report, but, I'm sorry, I don't see any command to run.

Revision history for this message
Omer Akram (om26er) wrote :

sorry about that really :/

$ ps aux | grep "unity-applications-daemon"

Revision history for this message
Omer Akram (om26er) wrote :

could you "pkill unity-applications-daemon" and start the dash. This will make sure all instances of the daemon are killed.

Revision history for this message
Nicola Jelmorini (jelmorini) wrote :

I have used the command you suggested before the pkill and this is the output:

########################################################################
nicola@nicola-Pangolino:~$ ps aux | grep "unity-applications-daemon"
nicola 2687 0.0 0.3 495412 15528 ? Sl 08:41 0:01 /usr/lib/unity-lens-applications/unity-applications-daemon
nicola 8463 0.0 0.0 13616 928 pts/0 S+ 12:42 0:00 grep --color=auto unity-applications-daemon
nicola@nicola-Pangolino:~$
########################################################################

Then I have tried the command pkill, but the daemon doesn't close. It remains running. So I have run the system monitor and killed the daemon from there. After, I have opened the Dash and finally executed again your command. Here the output:

########################################################################
nicola@nicola-Pangolino:~$ ps aux | grep "unity-applications-daemon"
nicola 8470 0.0 0.0 13612 928 pts/0 S+ 12:46 0:00 grep --color=auto unity-applications-daemon
nicola@nicola-Pangolino:~$
########################################################################

Until I restarts it, there is no more applications daemon running on my system. And if I restarts the daemon, there is the message I have pasted in the bug description.

Revision history for this message
Omer Akram (om26er) wrote :

Its seems this bug has already been reported by someone else as bug 987689. marking this as duplicate. There is a workaround there which seems to have worked for two people

Revision history for this message
Nicola Jelmorini (jelmorini) wrote :

Thank you Omer, I will follow the other bug and try the workaround.

Revision history for this message
Michal Hruby (mhr3) wrote :

When you run the daemon from the terminal and try searching for something then, does anything else get output on the console? (try waiting up to 30seconds after the search)

Revision history for this message
Nicola Jelmorini (jelmorini) wrote :

Hello Michal,

no, the message is the same as above, and is the only one displayed in the console.

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

Other bug subscribers

Remote bug watches

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