[Solved] bluedevil + bluez freeze my machine

Labello · 2013-12-30 08:25:05

Hello everyone,

I am having an issue with the current bluetooth tool chain. First of my currently installed packages are from testing:

[seb@seb-desktop ~]$ pacman -Qs blue
local/bluedevil 1:2.0rc1-1
KDE bluetooth framework
local/bluez 5.13-1
Daemons for the bluetooth protocol stack
local/bluez-libs 5.13-1
Deprecated libraries for the bluetooth protocol stack
local/libbluedevil 1:2.0rc1-2
A Qt4 wrapper for bluez used in the new KDE bluetooth stack

But whenever I connect to my Apple Magic Trackpad my whole machine immediately freezes. Then only a hard reboot is possible. It used to work just fine some time ago. This is really annoying and I don't have a single clue what to do

Last edited by Labello (2014-03-31 20:11:23)

Harey · 2013-12-30 10:22:35

Did you try to connect on a shell with bluetoothctl without using bluedevil as I told you on the other thread?

Harvey

Labello · 2013-12-30 11:56:08

Yes I followed these instructions here:
https://wiki.archlinux.org/index.php/Bl … uetoothctl

And this resulted in the following output:

[seb@seb-desktop ~]$ bluetoothctl
[NEW] Controller 00:15:83:3F:C0:F6 seb-desktop-0 [default]
[NEW] Device 28:37:37:2E:D2:09 gotschmarcels Trackpad
[bluetooth]# select 00:15:83:3F:C0:F6
[bluetooth]# power on
[CHG] Controller 00:15:83:3F:C0:F6 Class: 0x0c0104
Changing power on succeeded
[CHG] Controller 00:15:83:3F:C0:F6 Powered: yes
[bluetooth]# scan on
Discovery started
[CHG] Controller 00:15:83:3F:C0:F6 Discovering: yes
[CHG] Device 28:37:37:2E:D2:09 LegacyPairing: yes
[CHG] Device 28:37:37:2E:D2:09 RSSI: -49
[CHG] Device 28:37:37:2E:D2:09 RSSI: -59
[CHG] Device 28:37:37:2E:D2:09 Connected: yes
[CHG] Device 28:37:37:2E:D2:09 Connected: no
[CHG] Device 28:37:37:2E:D2:09 RSSI: -49
[bluetooth]# devices
Device 28:37:37:2E:D2:09 gotschmarcels Trackpad
[bluetooth]# trust 28:37:37:2E:D2:09
Changing 28:37:37:2E:D2:09 trust succeeded
[CHG] Device 28:37:37:2E:D2:09 Connected: yes
[CHG] Device 28:37:37:2E:D2:09 Connected: no
[CHG] Device 28:37:37:2E:D2:09 Connected: yes
[CHG] Device 28:37:37:2E:D2:09 Connected: no
[bluetooth]# pairable on
Changing pairable on succeeded
[bluetooth]# pair 28:37:37:2E:D2:09
Attempting to pair with 28:37:37:2E:D2:09
Failed to pair: org.bluez.Error.ConnectionAttemptFailed
[CHG] Device 28:37:37:2E:D2:09 RSSI: -67
[CHG] Device 28:37:37:2E:D2:09 RSSI: -85
[CHG] Device 28:37:37:2E:D2:09 RSSI: -50
[bluetooth]# pair 28:37:37:2E:D2:09
Attempting to pair with 28:37:37:2E:D2:09
[CHG] Device 28:37:37:2E:D2:09 Paired: yes
Pairing successful
[CHG] Device 28:37:37:2E:D2:09 Connected: yes
[CHG] Device 28:37:37:2E:D2:09 Paired: no
[CHG] Device 28:37:37:2E:D2:09 Connected: no
[bluetooth]# connect 28:37:37:2E:D2:09
Attempting to connect to 28:37:37:2E:D2:09
[CHG] Device 28:37:37:2E:D2:09 Connected: yes
Failed to connect: org.bluez.Error.Failed
[CHG] Device 28:37:37:2E:D2:09 Connected: no
[bluetooth]# connect 28:37:37:2E:D2:09
Attempting to connect to 28:37:37:2E:D2:09
[CHG] Device 28:37:37:2E:D2:09 Connected: yes
Failed to connect: org.bluez.Error.Failed
[CHG] Device 28:37:37:2E:D2:09 Connected: no
[CHG] Device 28:37:37:2E:D2:09 RSSI: -62
[CHG] Device 28:37:37:2E:D2:09 RSSI: -54
[CHG] Device 28:37:37:2E:D2:09 RSSI: -65
[CHG] Device 28:37:37:2E:D2:09 RSSI: -54
[CHG] Device 28:37:37:2E:D2:09 RSSI: -63
[CHG] Device 28:37:37:2E:D2:09 RSSI: -55
[CHG] Device 28:37:37:2E:D2:09 RSSI: -64
[bluetooth]# connect 28:37:37:2E:D2:09
Attempting to connect to 28:37:37:2E:D2:09
[CHG] Device 28:37:37:2E:D2:09 Connected: yes
Failed to connect: org.bluez.Error.Failed
[CHG] Device 28:37:37:2E:D2:09 Connected: no
[CHG] Device 28:37:37:2E:D2:09 RSSI: -51
[CHG] Device 28:37:37:2E:D2:09 RSSI: -60
[CHG] Device 28:37:37:2E:D2:09 RSSI: -51

EDIT by scarpino
please use the code tag

Last edited by ilpianista (2013-12-31 12:20:48)

Harey · 2013-12-30 12:31:30

I would try to uninstall libbluedevil and bluedevil before or at least end kde and do this from a root shell. Just to make sure nothing interferes with bluetoothctl. Then rather use this guide. Make sure you have not to provide any PIN codes and that your device really is in discoverable/pairing mode. Searching the forums I get the idea that you are not alone.

Hope that helps

Harvey

Labello · 2013-12-30 15:47:32

Harey wrote:

[...] Make sure you have not to provide any PIN codes and that your device really is in discoverable/pairing mode. [...]

Does that mean, that I am in bad luck, when my Trackpad needs "0000" as a pin?

Edit: Astonishingly the command "agent on" in bluetoothctl let me input "0000" as a PIN and now I was able to connect to my Trackpad in a wink of an eye. But unfortunately afterwards my whole KDE began choking up i.e. clementine not reacting, chrome not starting, kwin not showing any decorations of new windows and finally a complete lock up.

I am currently completely out of options. In my about 7 years of daily linux usage something liek this never occured.

Last edited by Labello (2013-12-30 16:07:05)

Harey · 2013-12-30 15:53:08

Labello wrote:

Harey wrote:
[...] Make sure you have not to provide any PIN codes and that your device really is in discoverable/pairing mode. [...]
Does that mean, that I am in bad luck, when my Trackpad needs "0000" as a pin?

No, it means read the guide and provide a PIN when default agent asks you for it...

Labello · 2013-12-30 16:36:31

Labello wrote:

Edit: Astonishingly the command "agent on" in bluetoothctl let me input "0000" as a PIN and now I was able to connect to my Trackpad in a wink of an eye. But unfortunately afterwards my whole KDE began choking up i.e. clementine not reacting, chrome not starting, kwin not showing any decorations of new windows and finally a complete lock up.
I am currently completely out of options. In my about 7 years of daily linux usage something liek this never occured.

Harey · 2013-12-30 17:04:37

So bluez seems to work and it's a kde problem. Not uncommon as we only have rcs by now and bluez 5 support in kde is very unstable. Uninstall bluedevil and libbluedevil and try again. When I had my headphone connected with bluetoothctl I did not need them at all. xf86-input-synaptics is installed?

Labello · 2013-12-30 19:40:21

Bluedevil is now completely deinstalled along with lib-bluedevil - same thing happens. maybe there is something I need to deactivate in KDE except the obvious things? could it also be pulseaudio, since it also has some strange connection with bluetooth? I am just guessing into the blue here...

Last edited by Labello (2013-12-30 19:52:42)

Harey · 2013-12-30 23:16:35

If you want to debug further you have to check the logs in /var/log/*, ~/.xsession-errors, maybe journalctl, dmesg and so on.

Harvey

Labello · 2013-12-31 10:23:34

Thank you for your patience, Harvey! I tried to collect some logs. This is what I could come up with:

[root@seb-desktop 71ca0da2c4d44be0a52550bdb09dfc61]# journalctl --unit=bluetooth -r
-- Logs begin at So 2013-09-29 22:36:07 CEST, end at Di 2013-12-31 11:15:10 CET. --
Dez 31 11:14:37 seb-desktop bluetoothd[1943]: Bluetooth management interface 1.3 initialized
Dez 31 11:14:37 seb-desktop bluetoothd[1943]: Starting SDP server
Dez 31 11:14:37 seb-desktop systemd[1]: Started Bluetooth service.
Dez 31 11:14:37 seb-desktop bluetoothd[1943]: Bluetooth daemon 5.13
Dez 31 11:14:37 seb-desktop systemd[1]: Starting Bluetooth service...
-- Reboot --
Dez 31 09:39:47 seb-desktop bluetoothd[900]: Bluetooth management interface 1.3 initialized
Dez 31 09:39:47 seb-desktop bluetoothd[900]: Starting SDP server
Dez 31 09:39:47 seb-desktop systemd[1]: Started Bluetooth service.
Dez 31 09:39:47 seb-desktop bluetoothd[900]: Bluetooth daemon 5.13
Dez 31 09:39:47 seb-desktop systemd[1]: Starting Bluetooth service...
-- Reboot --
Dez 30 22:32:41 seb-desktop systemd[1]: Stopped Bluetooth service.
Dez 30 22:32:41 seb-desktop systemd[1]: Stopping Bluetooth service...
Dez 30 20:59:04 seb-desktop bluetoothd[888]: Bluetooth management interface 1.3 initialized
Dez 30 20:59:04 seb-desktop bluetoothd[888]: Starting SDP server
Dez 30 20:59:04 seb-desktop systemd[1]: Started Bluetooth service.
Dez 30 20:59:04 seb-desktop bluetoothd[888]: Bluetooth daemon 5.13
Dez 30 20:59:04 seb-desktop systemd[1]: Starting Bluetooth service...
-- Reboot --
Dez 30 20:58:31 seb-desktop systemd[1]: Stopped Bluetooth service.
Dez 30 20:58:31 seb-desktop systemd[1]: Stopping Bluetooth service...
Dez 30 18:09:38 seb-desktop bluetoothd[895]: Bluetooth management interface 1.3 initialized
Dez 30 18:09:38 seb-desktop bluetoothd[895]: Starting SDP server
Dez 30 18:09:38 seb-desktop systemd[1]: Started Bluetooth service.
Dez 30 18:09:38 seb-desktop bluetoothd[895]: Bluetooth daemon 5.13
Dez 30 18:09:38 seb-desktop systemd[1]: Starting Bluetooth service...

Everything seems fine so far...

[root@seb-desktop 71ca0da2c4d44be0a52550bdb09dfc61]# journalctl --unit=kdm -r
-- Logs begin at So 2013-09-29 22:36:07 CEST, end at Di 2013-12-31 11:15:10 CET. --
Dez 31 11:14:31 seb-desktop kdm[588]: :0[588]: pam_unix(kde-np:session): session opened for user seb by (uid=0)
Dez 31 11:14:29 seb-desktop systemd[1]: Started K Display Manager.
Dez 31 11:14:29 seb-desktop systemd[1]: Starting K Display Manager...
-- Reboot --
Dez 31 09:39:44 seb-desktop systemd[1]: Started K Display Manager.
Dez 31 09:39:44 seb-desktop systemd[1]: Starting K Display Manager...
-- Reboot --
Dez 30 22:32:41 seb-desktop systemd[1]: Stopped K Display Manager.
Dez 30 22:32:41 seb-desktop systemd[1]: Stopping K Display Manager...
Dez 30 20:59:03 seb-desktop kdm[470]: :0[470]: pam_unix(kde-np:session): session opened for user seb by (uid=0)
Dez 30 20:59:01 seb-desktop systemd[1]: Started K Display Manager.
Dez 30 20:59:01 seb-desktop systemd[1]: Starting K Display Manager...
-- Reboot --

The end of my Xorg.0.log.old which I believe is the log of my last X-session?

[    17.174] (II) NVIDIA(GPU-0):     Vision stereo.
[    24.793] (II) NVIDIA(GPU-0): Display (DELL U2713HM (DFP-0)) does not support NVIDIA 3D
[    24.793] (II) NVIDIA(GPU-0):     Vision stereo.
[   158.912] (II) config/udev: Adding input device Microsoft Microsoft 5-Button Mouse with IntelliEye(TM) (/dev/input/event6)
[   158.912] (**) Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): Applying InputClass "evdev pointer catchall"
[   158.912] (II) Using input driver 'evdev' for 'Microsoft Microsoft 5-Button Mouse with IntelliEye(TM)'
[   158.912] (**) Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): always reports core events
[   158.912] (**) evdev: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): Device: "/dev/input/event6"
[   158.912] (--) evdev: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): Vendor 0x45e Product 0x39
[   158.912] (--) evdev: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): Found 9 mouse buttons
[   158.912] (--) evdev: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): Found scroll wheel(s)
[   158.912] (--) evdev: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): Found relative axes
[   158.912] (--) evdev: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): Found x and y relative axes
[   158.912] (II) evdev: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): Configuring as mouse
[   158.912] (II) evdev: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): Adding scrollwheel support
[   158.912] (**) evdev: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): YAxisMapping: buttons 4 and 5
[   158.912] (**) evdev: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[   158.912] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:12.2/usb8/8-5/8-5.4/8-5.4:1.0/input/input9/event6"
[   158.912] (II) XINPUT: Adding extended input device "Microsoft Microsoft 5-Button Mouse with IntelliEye(TM)" (type: MOUSE, id 11)
[   158.912] (II) evdev: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): initialized for relative axes.
[   158.913] (**) Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): (accel) keeping acceleration scheme 1
[   158.913] (**) Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): (accel) acceleration profile 0
[   158.913] (**) Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): (accel) acceleration factor: 2.000
[   158.913] (**) Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): (accel) acceleration threshold: 4
[   158.913] (II) config/udev: Adding input device Microsoft Microsoft 5-Button Mouse with IntelliEye(TM) (/dev/input/mouse0)
[   158.913] (II) No input driver specified, ignoring this device.
[   158.913] (II) This device may have been added with another device file.
[  1941.151] (II) config/udev: removing device Microsoft Microsoft 5-Button Mouse with IntelliEye(TM)
[  1941.164] (II) evdev: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): Close
[  1941.164] (II) UnloadModule: "evdev"
[  5378.698] (II) config/udev: Adding input device Microsoft Microsoft 5-Button Mouse with IntelliEye(TM) (/dev/input/event6)
[  5378.698] (**) Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): Applying InputClass "evdev pointer catchall"
[  5378.698] (II) Using input driver 'evdev' for 'Microsoft Microsoft 5-Button Mouse with IntelliEye(TM)'
[  5378.698] (**) Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): always reports core events
[  5378.698] (**) evdev: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): Device: "/dev/input/event6"
[  5378.698] (--) evdev: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): Vendor 0x45e Product 0x39
[  5378.698] (--) evdev: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): Found 9 mouse buttons
[  5378.698] (--) evdev: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): Found scroll wheel(s)
[  5378.698] (--) evdev: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): Found relative axes
[  5378.698] (--) evdev: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): Found x and y relative axes
[  5378.698] (II) evdev: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): Configuring as mouse
[  5378.698] (II) evdev: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): Adding scrollwheel support
[  5378.698] (**) evdev: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): YAxisMapping: buttons 4 and 5
[  5378.698] (**) evdev: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[  5378.698] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:12.2/usb8/8-5/8-5.4/8-5.4:1.0/input/input10/event6"
[  5378.698] (II) XINPUT: Adding extended input device "Microsoft Microsoft 5-Button Mouse with IntelliEye(TM)" (type: MOUSE, id 11)
[  5378.698] (II) evdev: Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): initialized for relative axes.
[  5378.699] (**) Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): (accel) keeping acceleration scheme 1
[  5378.699] (**) Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): (accel) acceleration profile 0
[  5378.699] (**) Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): (accel) acceleration factor: 2.000
[  5378.699] (**) Microsoft Microsoft 5-Button Mouse with IntelliEye(TM): (accel) acceleration threshold: 4
[  5378.699] (II) config/udev: Adding input device Microsoft Microsoft 5-Button Mouse with IntelliEye(TM) (/dev/input/mouse0)
[  5378.699] (II) No input driver specified, ignoring this device.
[  5378.699] (II) This device may have been added with another device file.

And finally my ~/.xsession-errors which also yields nothing strange I presume

[seb@seb-desktop ~]$ cat .xsession-errors 
cat: /proc/1144/comm: Datei oder Verzeichnis nicht gefunden
Agent pid 2024
startkde: Starting up...
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
kbuildsycoca4 running...
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath)
Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath)
kded(2042)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: name 'org.kde.kglobalaccel' had owner '' but we thought it was ':1.9'
QDBusConnection: name 'org.freedesktop.UDisks2' had owner '' but we thought it was ':1.16'
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
kded(2042) PowerDevil::Core::loadProfile: The profile  "AC" tried to activate "DimDisplay" a non existent action. This is usually due to an installation problem or to a configuration problem. or simlpy the action is not supported 
QCoreApplication::sendPostedEvents: Cannot send posted events for objects in another thread
QCoreApplication::sendPostedEvents: Cannot send posted events for objects in another thread
QCoreApplication::sendPostedEvents: Cannot send posted events for objects in another thread
QCoreApplication::sendPostedEvents: Cannot send posted events for objects in another thread
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusObjectPath: invalid path ""
QDBusObjectPath: invalid path ""
plasma-desktop(2122)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability 
plasma-desktop(2122)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability 
plasma-desktop(2122)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability 
plasma-desktop(2122)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability 
Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath)
Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath)
========================>  7 0
plasma-desktop(2122)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
static bool QDeclarativeMetaType::isModule(const QByteArray&, int, int) Qt 4.7 import detected; please note that Qt 4.7 is directly reusable as QtQuick 1.x with no code changes. Continuing, but startup time will be slower. 
plasma-desktop(2122)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
file:///usr/lib/kde4/imports/org/kde/plasma/components/SectionScroller.qml:103: TypeError: Result of expression 'listView' [null] is not an object.
file:///usr/lib/kde4/imports/org/kde/plasma/components/SectionScroller.qml:175: ReferenceError: Can't find variable: sectionsRepeater                        
file:///usr/lib/kde4/imports/org/kde/plasma/components/SectionScroller.qml:103: Error: Cannot assign [undefined] to QString                                  
file:///usr/share/apps/plasma/plasmoids/notifier/contents/ui/devicenotifier.qml:224:13: QML QDeclarativeListView_QML_80: Bei der FÃÂ¼lloperation wurde eine potentielle Endlosschleife der Anker festgestellt.
file:///usr/share/apps/plasma/plasmoids/notifier/contents/ui/devicenotifier.qml:224:13: QML QDeclarativeListView_QML_80: Bei der FÃÂ¼lloperation wurde eine potentielle Endlosschleife der Anker festgestellt.
file:///usr/share/apps/plasma/plasmoids/notifier/contents/ui/devicenotifier.qml:224:13: QML QDeclarativeListView_QML_80: Bei der FÃÂ¼lloperation wurde eine potentielle Endlosschleife der Anker festgestellt.
file:///usr/share/apps/plasma/plasmoids/notifier/contents/ui/devicenotifier.qml:224:13: QML QDeclarativeListView_QML_80: Bei der FÃÂ¼lloperation wurde eine potentielle Endlosschleife der Anker festgestellt.
file:///usr/share/apps/plasma/plasmoids/notifier/contents/ui/devicenotifier.qml:224:13: QML QDeclarativeListView_QML_80: Bei der FÃÂ¼lloperation wurde eine potentielle Endlosschleife der Anker festgestellt.
file:///usr/share/apps/plasma/plasmoids/notifier/contents/ui/devicenotifier.qml:224:13: QML QDeclarativeListView_QML_80: Bei der FÃÂ¼lloperation wurde eine potentielle Endlosschleife der Anker festgestellt.
file:///usr/share/apps/plasma/plasmoids/notifier/contents/ui/devicenotifier.qml:224:13: QML QDeclarativeListView_QML_80: Bei der FÃÂ¼lloperation wurde eine potentielle Endlosschleife der Anker festgestellt.
plasma-desktop(2122)/libakonadi Akonadi::AgentManagerPrivate::createDBusInterface: AgentManager failed to get a valid AgentManager DBus interface. Error is: 1 "org.freedesktop.DBus.Error.NameHasNoOwner" "Could not get owner of name 'org.freedesktop.Akonadi.Control': no such name" 
plasma-desktop(2122)/libakonadi Akonadi::SessionPrivate::socketError: Socket error occurred: "QLocalSocket::connectToServer: Invalid name" 
plasma-desktop(2122)/libakonadi Akonadi::SessionPrivate::socketError: Socket error occurred: "QLocalSocket::connectToServer: Invalid name" 
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
search paths:  ("/home/seb/.rbenv/shims", "/home/seb/.rbenv/bin", "/usr/local/sbin", "/usr/local/bin", "/usr/bin", "/opt/cuda/bin", "/usr/bin/vendor_perl", "/usr/bin/core_perl", "/usr/sbin", "/usr/local/sbin", "/usr/local/libexec", "/usr/libexec", "/opt/mysql/libexec", "/opt/local/lib/mysql5/bin", "/opt/mysql/sbin") 
Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath)
Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath)
plasma-desktop(2122)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
plasma-desktop(2122)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
akonadi.collectionattributetable                   OK
akonadi.collectionmimetyperelation                 OK
akonadi.collectionpimitemrelation                  OK
akonadi.collectiontable                            OK
akonadi.flagtable                                  OK
akonadi.mimetypetable                              OK
akonadi.parttable                                  OK
akonadi.pimitemflagrelation                        OK
akonadi.pimitemtable                               OK
akonadi.resourcetable                              OK
akonadi.schemaversiontable                         OK
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
Nepomuk Query Server not available
search paths:  ("/home/seb/.rbenv/shims", "/home/seb/.rbenv/bin", "/usr/local/sbin", "/usr/local/bin", "/usr/bin", "/opt/cuda/bin", "/usr/bin/vendor_perl", "/usr/bin/core_perl") 
search paths:  ("/home/seb/.kde4/lib/kde4/plugins/", "/usr/lib/kde4/plugins/", "/usr/lib/qt4/plugins", "/usr/bin", "/usr/lib/kde4/plugins", "/home/seb/.kde4/lib/kde4/", "/usr/lib/kde4/") 
search paths:  ("/home/seb/.kde4/lib/kde4/plugins/", "/usr/lib/kde4/plugins/", "/usr/lib/qt4/plugins", "/usr/bin", "/usr/lib/kde4/plugins", "/home/seb/.kde4/lib/kde4/", "/usr/lib/kde4/") 
search paths:  ("/home/seb/.kde4/lib/kde4/plugins/", "/usr/lib/kde4/plugins/", "/usr/lib/qt4/plugins", "/usr/bin", "/usr/lib/kde4/plugins", "/home/seb/.kde4/lib/kde4/", "/usr/lib/kde4/") 
search paths:  ("/home/seb/.kde4/lib/kde4/plugins/", "/usr/lib/kde4/plugins/", "/usr/lib/qt4/plugins", "/usr/bin", "/usr/lib/kde4/plugins", "/home/seb/.kde4/lib/kde4/", "/usr/lib/kde4/") 
search paths:  ("/home/seb/.kde4/lib/kde4/plugins/", "/usr/lib/kde4/plugins/", "/usr/lib/qt4/plugins", "/usr/bin", "/usr/lib/kde4/plugins", "/home/seb/.kde4/lib/kde4/", "/usr/lib/kde4/") 
search paths:  ("/home/seb/.kde4/lib/kde4/plugins/", "/usr/lib/kde4/plugins/", "/usr/lib/qt4/plugins", "/usr/bin", "/usr/lib/kde4/plugins", "/home/seb/.kde4/lib/kde4/", "/usr/lib/kde4/") 
Object::connect: No such signal QDBusAbstractInterface::StateChanged(uint)
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: name 'org.kde.kwalletd' had owner '' but we thought it was ':1.42'
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
 list is empty 
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
usage: synaptikscfg [-h] [--version] {init,load,save} ...
synaptikscfg: error: no touchpad found
N: [pulseaudio] main.c: User-configured server at {71ca0da2c4d44be0a52550bdb09dfc61}unix:/run/user/1000/pulse/native, which appears to be local. Probing deeper.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
N: [pulseaudio] main.c: User-configured server at {71ca0da2c4d44be0a52550bdb09dfc61}unix:/run/user/1000/pulse/native, which appears to be local. Probing deeper.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
Fehlgeschlagen: Modulinitialisierung fehlgeschlagen
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath)
Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath)
Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath)
Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath)
New PolkitAgentListener  0x24cc220 
Adding new listener  PolkitQt1::Agent::Listener(0x26c61a0) for  0x24cc220 
plasma-desktop(2122)/plasma StatusNotifierItemSource::refreshCallback: DBusMenu disabled for this application 
plasma-desktop(2122)/plasma StatusNotifierItemSource::refreshCallback: DBusMenu disabled for this application 
Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath)
Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath)
I/O warning : failed to load external entity "/home/seb/.qalculate/eurofxref-daily.xml"
I/O warning : failed to load external entity "/home/seb/.qalculate/eurofxref-daily.xml"
kded(2042) ContactRequestHandler::onNewAccountAdded: 
kded(2042) ContactRequestHandler::onNewAccountAdded: 
kded(2042) ContactRequestHandler::onNewAccountAdded: 
Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath)
Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath)
11:14:50.213 WARN  unknown                          libpng warning: iCCP: known incorrect sRGB profile 
11:14:50.377 WARN  unknown                          libpng warning: iCCP: known incorrect sRGB profile 
11:14:50.770 WARN  unknown                          QDBusConnection: name 'org.freedesktop.UDisks' had owner '' but we thought it was ':1.27' 
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
akonadi_googlecalendar_resource_2(2181)/LibKGAPI KGAPI2::Job::Private::_k_replyReceived: Unauthorized. Access token has expired or is invalid. 
 list is empty 
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
[10:10:1231/111932:ERROR:base_feature_provider.cc(122)] manifestTypes: Allowing web_page contexts requires supplying a value for matches.
[13:13:1231/111932:ERROR:base_feature_provider.cc(122)] manifestTypes: Allowing web_page contexts requires supplying a value for matches.
[17:17:1231/111932:ERROR:base_feature_provider.cc(122)] manifestTypes: Allowing web_page contexts requires supplying a value for matches.
[16716:16716:1231/111932:ERROR:base_feature_provider.cc(122)] manifestTypes: Allowing web_page contexts requires supplying a value for matches.
[16716:16716:1231/111933:ERROR:profile_sync_service.cc(1222)] History Delete Directives datatype error was encountered: Delete directives not supported with encryption.
[30:30:1231/111934:ERROR:base_feature_provider.cc(122)] manifestTypes: Allowing web_page contexts requires supplying a value for matches.
[25:25:1231/111934:ERROR:base_feature_provider.cc(122)] manifestTypes: Allowing web_page contexts requires supplying a value for matches.
[33:33:1231/111934:ERROR:base_feature_provider.cc(122)] manifestTypes: Allowing web_page contexts requires supplying a value for matches.
[37:37:1231/111934:ERROR:base_feature_provider.cc(122)] manifestTypes: Allowing web_page contexts requires supplying a value for matches.
[41:41:1231/111934:ERROR:base_feature_provider.cc(122)] manifestTypes: Allowing web_page contexts requires supplying a value for matches.
[47:47:1231/111936:ERROR:base_feature_provider.cc(122)] manifestTypes: Allowing web_page contexts requires supplying a value for matches.
[51:51:1231/111937:ERROR:base_feature_provider.cc(122)] manifestTypes: Allowing web_page contexts requires supplying a value for matches.
plasma-desktop(2122)/plasma StatusNotifierItemSource::refreshCallback: DBusMenu disabled for this application 
plasma-desktop(2122)/plasma StatusNotifierItemSource::refreshCallback: DBusMenu disabled for this application 
plasma-desktop(2122)/plasma StatusNotifierItemSource::refreshCallback: DBusMenu disabled for this application 
plasma-desktop(2122)/plasma StatusNotifierItemSource::refreshCallback: DBusMenu disabled for this application 
plasma-desktop(2122)/plasma StatusNotifierItemSource::refreshCallback: DBusMenu disabled for this application 
[55:55:1231/112224:ERROR:base_feature_provider.cc(122)] manifestTypes: Allowing web_page contexts requires supplying a value for matches.
plasma-desktop(2122)/plasma StatusNotifierItemSource::refreshCallback: DBusMenu disabled for this application 
plasma-desktop(2122)/plasma StatusNotifierItemSource::refreshCallback: DBusMenu disabled for this application 
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
plasma-desktop(2122)/plasma StatusNotifierItemSource::refreshCallback: DBusMenu disabled for this application 
[59:59:1231/112704:ERROR:base_feature_provider.cc(122)] manifestTypes: Allowing web_page contexts requires supplying a value for matches.
plasma-desktop(2122)/plasma StatusNotifierItemSource::refreshCallback: DBusMenu disabled for this application 
plasma-desktop(2122)/plasma StatusNotifierItemSource::refreshCallback: DBusMenu disabled for this application 
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QPixmap: It is not safe to use pixmaps outside the GUI thread
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.

I am wondering if there actually is any fix at all? I am getting more and more frustrated because I love my Trackpad so much

EDIT by scarpino
please use the code tag

Last edited by ilpianista (2013-12-31 12:20:01)

Harey · 2013-12-31 11:19:24

Pfeeew! Use code tags please! This is your problem:

usage: synaptikscfg [-h] [--version] {init,load,save} ...
synaptikscfg: error: no touchpad found

You could try

cat /proc/bus/input/devices

to detect if your touchpad is recognized at all when paired. I suggest to try this from a pure shell. Maybe the device name has changed and you need to reflect this in your synaptics.conf?

For better understanding of the Synaptics driver there are several wiki pages (again...)

What happens when using the kde desktop without the trackpad paired? There are a lot more errors in ~/.xsession-errors...

Happy new year (nevertheless)
Harvey

Labello · 2013-12-31 13:54:11

I officially give up. I just tested the Trackpad first with my usb-dongle on another pc (thinkpad running openbox and a very minimal setup) which resultet into a drop out to a tty and a kernel panic message. After that I tried the built-in bluetooth of the laptop. Same result. So what the hell. It seems to be a synaptics/xorg/whatever kind of problem. I don't give a s**t anymore.

frumble · 2014-01-14 20:20:00

Just found this and I can TOTALLY confirm this bug! Connect the Magic Trackpad to my machine and it crashes reproducible, sometimes faster, even on login, sometimes a hour later. Thought it must be a Kernel issue and stayed for months on Linux 3.10 but the same problem with 3.12. BIG SHOWSTOPPER!

frumble · 2014-01-22 20:01:29

Hey @Labello, I want to make this work again, any progress? I tried to roll back these packages to versions from September 02:

bluedevil-1.3.1-1-x86_64.pkg.tar.xz
bluez-libs-5.7-1-x86_64.pkg.tar.xz
bluez-utils-5.7-1-x86_64.pkg.tar.xz
bluez4-4.101-3-x86_64.pkg.tar.xz
libbluedevil-1.9.3-2-x86_64.pkg.tar.xz
obexd-client-1:0.46-2-x86_64.pkg.tar.xz
openobex-1.7-6-x86_64.pkg.tar.xz

Still the same crashing! Is this problem so deep into KDE libs? Anyone, have you any idea what packages I could try to downgrade too?
I'm hoping some KDE devs will stumble upon this bug themselves but I have the feeling there are not so many fans of Apple products in their community despite the world's best trackpad... And I can't really write a bug report since we don't even know which part of the stack is responsible for the fatal freeze.

EDIT: There are hints that this is a Kernel bug.

Last edited by frumble (2014-01-23 21:28:09)

Labello · 2014-01-23 15:51:48

@frumble: well I more or less gave up. today a new bluez update to 5.14 arrived. I will try with that one.

EDIT: still the same issue with all packages updated. I am completely out of motivation to investigate any further. but if anyone could toss a hint I still would be infinitly grateful.

Last edited by Labello (2014-01-23 16:09:15)

frumble · 2014-01-23 21:27:03

After reading of the Kernel bug I have made a downgrade of Linux to 3.10 – AND IT WORKS!
Just install 3.10.10-1 from September and set

IgnorePkg = linux linux-headers

in /etc/pacman.conf. Sucks a bit to use an old Kernel, especially as a btrfs user, but I'm using this Magic Trackpad as my primary input device before my 3 mice. Yes, 3 mice and I love the Magic Trackpad. BTW, are you using Touchegg? Adds some nice OS X multitouch gestures, try my config (with regular Synaptics driver because evdev doesn't really work.). So we just have to wait for Linux 3.14 or 3.15.

Last edited by frumble (2014-01-23 21:27:50)

Labello · 2014-01-24 22:53:55

This seems like a rathe brutal fix to me. but thanks for the headsup! furthermore I realized that my binary nvidia blob need at least 3.12 so no downgrade for me. but I just got touchegg from the aur and now simply have to wait for the kernel bug to be fixed. maybe i just build it myself after the first RC that linus puts out

Labello · 2014-02-11 17:46:04

Are there any news regarding this issue? Is anyone testing 3.14rc1 already?

frumble · 2014-02-11 22:38:16

"The patch that fixes the crash has finally received some positive feedback and barring surprises should hit 3.14 (might be CCed to stable as well)" https://bugzilla.redhat.com/show_bug.cgi?id=1027465#c29
But unclear if only in the Fedora tree or in the official tree for 3.14.

Last edited by frumble (2014-02-11 22:39:46)

holovati · 2014-03-04 12:52:51

frumble wrote:

"The patch that fixes the crash has finally received some positive feedback and barring surprises should hit 3.14 (might be CCed to stable as well)" https://bugzilla.redhat.com/show_bug.cgi?id=1027465#c29
But unclear if only in the Fedora tree or in the official tree for 3.14.

I just patched 3.13.5 with that patch and i can confirm that it works like a charm thanks

Labello · 2014-03-10 17:13:27

holovati wrote:

I just patched 3.13.5 with that patch and i can confirm that it works like a charm thanks

could you provide any more specific info on how to do that? what are the news on this patches inclusion upstream?

Labello · 2014-03-28 14:46:05

From the link posted above... Do I suppose correctly that the afformentioned patch is included in >=3.13.6?

EDIT: Tried it again with bluez-5.16 and 3.13.6. Same s**t happens...

Last edited by Labello (2014-03-28 22:16:21)

holovati · 2014-03-29 09:11:37

Labello wrote:

could you provide any more specific info on how to do that? what are the news on this patches inclusion upstream?

Well I used https://wiki.archlinux.org/index.php/Ke … ild_System as a guide to build a custom kernel package and I just added the patch before compiling.

If you are to lazy to compile it yourself i can send you my custom package and you can use it till 3.14 becomes stable

holovati · 2014-03-29 09:24:02

Labello wrote:

From the link posted above... Do I suppose correctly that the afformentioned patch is included in >=3.13.6?
EDIT: Tried it again with bluez-5.16 and 3.13.6. Same s**t happens...

http://www.spinics.net/lists/linux-blue … 41904.html

https://git.kernel.org/cgit/linux/kerne … gs/v3.13.7

The patch is not included in 3.13.7

Arch Linux

#1 2013-12-30 08:25:05

[Solved] bluedevil + bluez freeze my machine

#2 2013-12-30 10:22:35

Re: [Solved] bluedevil + bluez freeze my machine

#3 2013-12-30 11:56:08

Re: [Solved] bluedevil + bluez freeze my machine

#4 2013-12-30 12:31:30

Re: [Solved] bluedevil + bluez freeze my machine

#5 2013-12-30 15:47:32

Re: [Solved] bluedevil + bluez freeze my machine

#6 2013-12-30 15:53:08

Re: [Solved] bluedevil + bluez freeze my machine

#7 2013-12-30 16:36:31

Re: [Solved] bluedevil + bluez freeze my machine

#8 2013-12-30 17:04:37

Re: [Solved] bluedevil + bluez freeze my machine

#9 2013-12-30 19:40:21

Re: [Solved] bluedevil + bluez freeze my machine

#10 2013-12-30 23:16:35

Re: [Solved] bluedevil + bluez freeze my machine

#11 2013-12-31 10:23:34

Re: [Solved] bluedevil + bluez freeze my machine

#12 2013-12-31 11:19:24

Re: [Solved] bluedevil + bluez freeze my machine

#13 2013-12-31 13:54:11

Re: [Solved] bluedevil + bluez freeze my machine

#14 2014-01-14 20:20:00

Re: [Solved] bluedevil + bluez freeze my machine

#15 2014-01-22 20:01:29

Re: [Solved] bluedevil + bluez freeze my machine

#16 2014-01-23 15:51:48

Re: [Solved] bluedevil + bluez freeze my machine

#17 2014-01-23 21:27:03

Re: [Solved] bluedevil + bluez freeze my machine

#18 2014-01-24 22:53:55

Re: [Solved] bluedevil + bluez freeze my machine

#19 2014-02-11 17:46:04

Re: [Solved] bluedevil + bluez freeze my machine

#20 2014-02-11 22:38:16

Re: [Solved] bluedevil + bluez freeze my machine

#21 2014-03-04 12:52:51

Re: [Solved] bluedevil + bluez freeze my machine

#22 2014-03-10 17:13:27

Re: [Solved] bluedevil + bluez freeze my machine

#23 2014-03-28 14:46:05

Re: [Solved] bluedevil + bluez freeze my machine

#24 2014-03-29 09:11:37

Re: [Solved] bluedevil + bluez freeze my machine

#25 2014-03-29 09:24:02

Re: [Solved] bluedevil + bluez freeze my machine

Board footer