I always need to run some ximput commands when my bluetooth
mouse connects, I'm wondering if I can automagically detect
the mouse connecting and run the commands so I never have
to remember to do it manually.
The only thing I've found so far that notices a new mouse connection
is messag
On Wed, Aug 28, 2019 at 10:55:29AM -0400, Chris Bredesen wrote:
>Hi list,
>I reported this issue on the UPower GitLab issue tracker but I don't
>hold much hope it'll get the required visibility.
>[1]https://gitlab.freedesktop.org/upower/upower/issues/100
>I just had my Satechi M
Hi list,
I reported this issue on the UPower GitLab issue tracker but I don't hold
much hope it'll get the required visibility.
https://gitlab.freedesktop.org/upower/upower/issues/100
I just had my Satechi M1 mouse quit working unceremoniously ... due to a
dead battery. All along, GNOME's power
ations widget used to show the battery
> > level in my Bluetooth mouse. Now it just says there are no batteries.
> > It's a desktop, so there are indeed no batteries in the system, but
> > there are in the mouse.
> >
> > One responder suggested trying "
On Sun, Oct 9, 2016 at 8:19 AM, Patrick O'Callaghan
wrote:
> (Originally posted to the KDE list but now I don't think it's a KDE
> issue).
>
> Using the Status and Notifications widget used to show the battery
> level in my Bluetooth mouse. Now it just says th
(Originally posted to the KDE list but now I don't think it's a KDE
issue).
Using the Status and Notifications widget used to show the battery
level in my Bluetooth mouse. Now it just says there are no batteries.
It's a desktop, so there are indeed no batteries in the system, but
t
On Fri, Jul 29, 2016 at 03:18:52PM +0100, Patrick O'Callaghan wrote:
> On Wed, 2016-07-27 at 18:47 -0400, Jon LaBadie wrote:
> > Sounds like there is a problem with blueman-manager!
>
> I assume you've reported this to Bugzilla. If so, best quote the BZ
> report number here so others can chip in.
On Wed, 2016-07-27 at 18:47 -0400, Jon LaBadie wrote:
> Sounds like there is a problem with blueman-manager!
I assume you've reported this to Bugzilla. If so, best quote the BZ
report number here so others can chip in.
poc
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or chan
On Fri, Jul 08, 2016 at 12:43:07AM -0400, Jon LaBadie wrote:
> I have an old Dell Vostro 1500 laptop. It was running
> Fedora 17 with no problems with the bluetooth mouse I use.
>
> After a fresh install of Fedora 24 Workstation I can't
> get the mouse to reconnect afte
On Sat, 2016-07-09 at 00:11 -0400, Jon LaBadie wrote:
> On Fri, Jul 08, 2016 at 10:50:15PM +0100, Patrick O'Callaghan wrote:
> > On Fri, 2016-07-08 at 16:31 -0400, Jon LaBadie wrote:
> > > BTW the Broadcom BT adapter in my laptop seems to present as
> > > a USB device:
> > >
> > > $ lsusb
> > > ..
On Fri, Jul 08, 2016 at 10:50:15PM +0100, Patrick O'Callaghan wrote:
> On Fri, 2016-07-08 at 16:31 -0400, Jon LaBadie wrote:
> > BTW the Broadcom BT adapter in my laptop seems to present as
> > a USB device:
> >
> > $ lsusb
> > ...
> > Bus 004 Device 001: ID 1d6b:0001 Linux Foundation
> > Bus 003
On Fri, 2016-07-08 at 16:31 -0400, Jon LaBadie wrote:
> BTW the Broadcom BT adapter in my laptop seems to present as
> a USB device:
>
> $ lsusb
> ...
> Bus 004 Device 001: ID 1d6b:0001 Linux Foundation
> Bus 003 Device 009: ID 0a5c:4503 Broadcom Corp. Mouse (Boot Interface
> Subclass)
> Bus 003
On 07/07/2016 09:43 PM, Jon LaBadie wrote:
> I have an old Dell Vostro 1500 laptop. It was running
> Fedora 17 with no problems with the bluetooth mouse I use.
>
> After a fresh install of Fedora 24 Workstation I can't
> get the mouse to reconnect after a boot. Systemctl
On Fri, Jul 08, 2016 at 05:02:57PM +0100, Patrick O'Callaghan wrote:
> On Fri, 2016-07-08 at 09:53 -0300, George N. White III wrote:
> > > I also find the dongle sometimes doesn't power on after returning
> > from
> > > hibernation. Haven't found a fix for that other than keeping an
> > extra
> > >
On Fri, 2016-07-08 at 09:53 -0300, George N. White III wrote:
> > I also find the dongle sometimes doesn't power on after returning
> from
> > hibernation. Haven't found a fix for that other than keeping an
> extra
> > mouse so I can enable it manually.
> >
> >
> If is any consolation, my new iMac
Fedora 17 with no problems with the bluetooth mouse I use.
> > >
> > > After a fresh install of Fedora 24 Workstation I can't
> > > get the mouse to reconnect after a boot. Systemctl
> > > reports bluetoothd 'Failed to obtain handles for
> > > &qu
On Fri, Jul 08, 2016 at 09:43:35AM +0100, Patrick O'Callaghan wrote:
> On Fri, 2016-07-08 at 00:43 -0400, Jon LaBadie wrote:
> > I have an old Dell Vostro 1500 laptop. It was running
> > Fedora 17 with no problems with the bluetooth mouse I use.
> >
> > Af
On Fri, Jul 8, 2016 at 5:43 AM, Patrick O'Callaghan
wrote:
> On Fri, 2016-07-08 at 00:43 -0400, Jon LaBadie wrote:
> > I have an old Dell Vostro 1500 laptop. It was running
> > Fedora 17 with no problems with the bluetooth mouse I use.
> >
> > After a fresh in
On Fri, 2016-07-08 at 00:43 -0400, Jon LaBadie wrote:
> I have an old Dell Vostro 1500 laptop. It was running
> Fedora 17 with no problems with the bluetooth mouse I use.
>
> After a fresh install of Fedora 24 Workstation I can't
> get the mouse to reconnect after a boot.
I have an old Dell Vostro 1500 laptop. It was running
Fedora 17 with no problems with the bluetooth mouse I use.
After a fresh install of Fedora 24 Workstation I can't
get the mouse to reconnect after a boot. Systemctl
reports bluetoothd 'Failed to obtain handles for
"S
connection info
> May 26 13:03:12 ope46 bluetoothd[789]: connect error: Host is down (112)
>
> Tried also from mate and from kde sessio s with same results.
>
> Device added successfully, but failed to connect
>
> Connection Failed: blueman.bluez.errors.DBusFailedError: Input/output error
>
> I also f
On Thu, May 26, 2016 at 1:08 PM, Gianluca Cecchi
wrote:
> hello,
> I have a Samsung S Action Mouse ET-MP900D that I'm trying to connect from
> my laptop: Asus U36SD with Fedora 23.
>
> I can pair and connect to the mouse both from a Samsung S2 phone and from
> a Samsung Pro 12.2 tablet.
>
> I rem
hello,
I have a Samsung S Action Mouse ET-MP900D that I'm trying to connect from
my laptop: Asus U36SD with Fedora 23.
I can pair and connect to the mouse both from a Samsung S2 phone and from a
Samsung Pro 12.2 tablet.
I remember in the past on the same PC with Fedora 21 I was able to connect
to
On Tue, 2015-12-22 at 04:06 +0100, Andrej Podzimek wrote:
> Hello,
>
> In Fedora 23, my Bluetooth mouse works fine in KDE. However, it
> doesn't work in sddm before the first user logs in. It works
> afterwards and keeps working even after the first (or second or
> whicheve
Hello,
In Fedora 23, my Bluetooth mouse works fine in KDE. However, it doesn't work in
sddm before the first user logs in. It works afterwards and keeps working even
after the first (or second or whichever) user logs out.
The very first login without a mouse is quite an inconvenience
On Sat, 2015-03-14 at 17:45 -0600, jd1008 wrote:
>
> On 03/14/2015 05:40 PM, Patrick O'Callaghan wrote:
> > On Sat, 2015-03-14 at 13:39 -0400, Neal Becker wrote:
> >> Just got a logitech bt m557 mouse. Using it on F21 (kde).
> >>
> >> One annoyance, it does not automatically connect when the mach
On 03/14/2015 05:40 PM, Patrick O'Callaghan wrote:
On Sat, 2015-03-14 at 13:39 -0400, Neal Becker wrote:
Just got a logitech bt m557 mouse. Using it on F21 (kde).
One annoyance, it does not automatically connect when the machine wakes. To
connect, I have to go to the bluetooth icon on my pa
On Sat, 2015-03-14 at 13:39 -0400, Neal Becker wrote:
> Just got a logitech bt m557 mouse. Using it on F21 (kde).
>
> One annoyance, it does not automatically connect when the machine wakes. To
> connect, I have to go to the bluetooth icon on my panel (without a mouse)
> and select the mouse,
Just got a logitech bt m557 mouse. Using it on F21 (kde).
One annoyance, it does not automatically connect when the machine wakes. To
connect, I have to go to the bluetooth icon on my panel (without a mouse)
and select the mouse, and click 'connect'. Any ideas?
--
Those who fail to understa
On Tue, 27 Jan 2015 13:50:11 -0500
Digimer wrote:
> Any tips/pointers to docs to help with a udev-triggered script would be
> much appreciated!
These scripts are for something completely different, but the web
page here documents the nonsense I discovered and how I worked
around it to trigger so
Hi all,
I've got a bluetooth mouse that is rediculously sensitive. I have a
script I can run that drops the sensitivity to a reasonable level, but I
would like to have the script triggered automatically.
I can see in /var/log/messages these messages on connect:
Powering on the
On Sat, 2014-03-08 at 22:21 +, Patrick O'Callaghan wrote:
> On Sun, 2014-03-09 at 04:52 +0800, Ed Greshko wrote:
> > On 03/08/14 22:01, Patrick O'Callaghan wrote:
> > > Various things about mice, such as:
> > >
> > >> > [ 3.188] (II) config/udev: Adding input device 2.4G Receiver
> > >> >
a Bluetooth USB dongle.
>> >
>> > Running the default Nouveau video driver, I was able to connect my
>> > Sondstrom Bluetooth mouse with no trouble. I then installed the Nvidia
>> > proprietary drivers using akmod, rebooted, and now can't connect to
>> >
On Sun, 2014-03-09 at 04:52 +0800, Ed Greshko wrote:
> On 03/08/14 22:01, Patrick O'Callaghan wrote:
> > Various things about mice, such as:
> >
> >> > [ 3.188] (II) config/udev: Adding input device 2.4G Receiver
> >> > (/dev/input/mouse1)
> >> > [ 3.188] (II) No input driver specified, ig
On 03/08/14 22:01, Patrick O'Callaghan wrote:
> Various things about mice, such as:
>
>> > [ 3.188] (II) config/udev: Adding input device 2.4G Receiver
>> > (/dev/input/mouse1)
>> > [ 3.188] (II) No input driver specified, ignoring this device.
No driver seems suspicious
>> > [ 3
e default Nouveau video driver, I was able to connect my
> > Sondstrom Bluetooth mouse with no trouble. I then installed the Nvidia
> > proprietary drivers using akmod, rebooted, and now can't connect to
> > the mouse. I get the KDE connection dialogue, the mouse appears as
the default Nouveau video driver, I was able to connect my
> > Sondstrom Bluetooth mouse with no trouble. I then installed the Nvidia
> > proprietary drivers using akmod, rebooted, and now can't connect to
> > the mouse. I get the KDE connection dialogue, the mouse appears
"Patrick O'Callaghan" writes:
> This is a new install of F20, with all updates applied, using KDE. The
> machine has an Nvidia G630 graphics card and a Bluetooth USB dongle.
>
> Running the default Nouveau video driver, I was able to connect my
> Sondstrom Bluetooth
On 03/08/14 18:39, Patrick O'Callaghan wrote:
> This is a new install of F20, with all updates applied, using KDE. The
> machine has an Nvidia G630 graphics card and a Bluetooth USB dongle.
>
> Running the default Nouveau video driver, I was able to connect my
> Sondstrom Blu
This is a new install of F20, with all updates applied, using KDE. The
machine has an Nvidia G630 graphics card and a Bluetooth USB dongle.
Running the default Nouveau video driver, I was able to connect my
Sondstrom Bluetooth mouse with no trouble. I then installed the Nvidia
proprietary drivers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Le 26/12/2010 02:24, Darr a écrit :
> On Saturday, 25 December, 2010 @10:28 zulu, François Patte scribed:
>
>> Bonjour,
>>
>> I have a logitech V470 bluetooth mouse which did work fine up to
>> day
>>
>>
On Saturday, 25 December, 2010 @10:28 zulu, François Patte scribed:
> Bonjour,
>
> I have a logitech V470 bluetooth mouse which did work fine up to
> day
>
> This morning, it no more works! Cells are OK.
>
> I tried hctool scan and it does not see the mouse, except if
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bonjour,
I have a logitech V470 bluetooth mouse which did work fine up to day
This morning, it no more works! Cells are OK.
I tried hctool scan and it does not see the mouse, except if I press a
small button under the mouse on wich "connec
43 matches
Mail list logo
