search

Thor77 / Blueproximity

Run a command once a bluetooth device is in/out of a range
GNU General Public License v2.0
66 stars 15 forks source link

status changes to "gone", but no screensaver #19

Closed Thor77 closed 8 years ago

Thor77 commented 8 years ago

I have Ubuntu 7.04 and OpenSUSE 10.2 and a Nokia 6230. Using either Ubuntu or SUSE, blueproximity does not work. When I leave the computer with my mobile phone, blueproximity changes to status "gone", but does not switch on the screensaver. If I manually execute the "Locking command", the screensaver does start.

Thor77 commented 8 years ago

Logged In: YES user_id=1312539 Originator: NO

This Tracker item was closed automatically by the system. It was previously set to a Pending status, and the original submitter did not respond within 14 days (the time period specified by the administrator of this Tracker). (By sf-robot)

Thor77 commented 8 years ago

Logged In: YES user_id=114903 Originator: NO

Hi again,

if it tells you it is in simulation mode that means the preferences dialog is still open. While that is open no locking will be done (and is therefore called "simulation mode"). You should see that by a single left click on the icon the prefs do appear and close again at the next click. Please check that the prefs dialog is not shown. (By highno)

Thor77 commented 8 years ago

Logged In: YES user_id=1692926 Originator: YES

I ran into that error again, moved my mouse to the tooltip and got a message about a simulation mode. I moved the mouse away and again on the tooltip, and now, there is no longer this message.

You are using GNOME screensaver? yes Are blueproximity and the screensaver run as the same user? yes Are both started from the same GNOME and X session? yes Is BlueProximity started with a different environment/path set? no Do you see error messages if you quit blueproximity and restart it from a console window? no Does it work if it is started from a console? no Do you use prepackaged versions or the source tarball? The source tarball. (By thstaerk)

Thor77 commented 8 years ago

Logged In: YES user_id=114903 Originator: NO

I have some questions regarding this bug: You are using GNOME screensaver? Are blueproximity and the screensaver run as the same user? Are both started from the same GNOME and X session? Is BlueProximity started with a different environment/path set? Do you see error messages if you quit blueproximity and restart it from a console window? Does it work if it is started from a console? Do you use prepackaged versions or the source tarball? (By highno)