Mouse cursor disappearing after running gnome-settings-daemon in OpenBoxCursor disappears after login on...
What is the German word for: "It only works when I try to show you how it does not work"?
How to give a rationality-inducing drug to an entire software company?
Usefulness of Nash embedding theorem
Variable fixing based on a good feasible solution
Paper status "Accept with Shepherd". What does it really mean?
Do you say "good game" after a game in which your opponent played poorly?
Some interesting and elementary topics with connections to the representation theory?
They say I should work on bigger things
What does the British parliament hope to achieve by requesting a third Brexit extension?
What happens if a geocentric model of the world were correct?
Source for "no Yetzer Harah when a Torah Scroll is opened/read"?
How can a "proper" function have a vertical slope?
Sanitize and build data structure from Consul configuration
Can digital computers understand infinity?
Marxist and post modernism contradiction
How can demon technology be prevented from surpassing humans?
What is a recommended strategy on exercises in a mathematical textbook at graduate level?
Can you set fire to beer barrels?
How is Smough's name pronounced?
How to protect my Wi-Fi password from being displayed by Android phones when sharing it with QR code?
A replacement for NextPermutation in Combinatorica
'Pound' meaning in this context
Is the value of a probability density function for a given input a point, a range, or both?
How can AnyDVD destroy a DVD drive?
Mouse cursor disappearing after running gnome-settings-daemon in OpenBox
Cursor disappears after login on xubuntuUbuntu with Gnome and Openboxper-instance application settings in OpenboxNo internet connection after uninstalling gnome [Fedora + Openbox]Options disappeared from the Mouse & Touchpad settingswhat are gnome-session and gnome-settings-daemon?Fix random mouse cursor movement in Fedora GnomeMake GTK/Gnome NOT use the theme's mouse cursor
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{
margin-bottom:0;
}
I'm running Openbox 3.5.2 on Fedora 20. For extra comfort (font rendering, tap-to-click, ...), I used to let gnome-settings-daemon run in the background.
Now since upgrading to the F20 beta, my mouse cursor is disappearing right after executing /usr/libexec/gnome-settings-daemon. That is it visually disappears; I am still able to click on things. But the impact on usability is unbearable nonetheless.
At first I thought compton were at fault, which I installed fresh out of koji. But removing it from my autostart doesn't change things for the better. The mouse is just fine in Gnome itself. There's nothing suspicious in .xsession-errors as far as I can tell. I'm really out of ideas right now.
Relevant system info:
$ rpm -q openbox compton gnome-settings-daemon
openbox-3.5.2-2.fc20.x86_64
compton-0-0.3.20121218g75aec17.fc19.x86_64
gnome-settings-daemon-3.10.2-3.fc20.x86_64
$ uname -sr
Linux 3.11.10-301.fc20.x86_64
The machine itself is a X121e Thinkpad with a E-450 APU, powered by the OSS radeon driver.
fedora gnome openbox
asked Dec 17 '13 at 18:33
DaSourcererDaSourcerer
2213 silver badges13 bronze badges
add a comment
|
I'm running Openbox 3.5.2 on Fedora 20. For extra comfort (font rendering, tap-to-click, ...), I used to let gnome-settings-daemon run in the background.
Now since upgrading to the F20 beta, my mouse cursor is disappearing right after executing /usr/libexec/gnome-settings-daemon. That is it visually disappears; I am still able to click on things. But the impact on usability is unbearable nonetheless.
At first I thought compton were at fault, which I installed fresh out of koji. But removing it from my autostart doesn't change things for the better. The mouse is just fine in Gnome itself. There's nothing suspicious in .xsession-errors as far as I can tell. I'm really out of ideas right now.
Relevant system info:
$ rpm -q openbox compton gnome-settings-daemon
openbox-3.5.2-2.fc20.x86_64
compton-0-0.3.20121218g75aec17.fc19.x86_64
gnome-settings-daemon-3.10.2-3.fc20.x86_64
$ uname -sr
Linux 3.11.10-301.fc20.x86_64
The machine itself is a X121e Thinkpad with a E-450 APU, powered by the OSS radeon driver.
fedora gnome openbox
asked Dec 17 '13 at 18:33
DaSourcererDaSourcerer
2213 silver badges13 bronze badges
I experienced the same problem on Ubuntu 13.10 with Openbox 3.5.2-3 and gnome-settings-daemon 3.8.5-0ubuntu9. Your answer below solved it!
– MDCore
Jan 23 '14 at 8:52
add a comment
|
I'm running Openbox 3.5.2 on Fedora 20. For extra comfort (font rendering, tap-to-click, ...), I used to let gnome-settings-daemon run in the background.
Now since upgrading to the F20 beta, my mouse cursor is disappearing right after executing /usr/libexec/gnome-settings-daemon. That is it visually disappears; I am still able to click on things. But the impact on usability is unbearable nonetheless.
At first I thought compton were at fault, which I installed fresh out of koji. But removing it from my autostart doesn't change things for the better. The mouse is just fine in Gnome itself. There's nothing suspicious in .xsession-errors as far as I can tell. I'm really out of ideas right now.
Relevant system info:
$ rpm -q openbox compton gnome-settings-daemon
openbox-3.5.2-2.fc20.x86_64
compton-0-0.3.20121218g75aec17.fc19.x86_64
gnome-settings-daemon-3.10.2-3.fc20.x86_64
$ uname -sr
Linux 3.11.10-301.fc20.x86_64
The machine itself is a X121e Thinkpad with a E-450 APU, powered by the OSS radeon driver.
fedora gnome openbox
asked Dec 17 '13 at 18:33
DaSourcererDaSourcerer
2213 silver badges13 bronze badges
I'm running Openbox 3.5.2 on Fedora 20. For extra comfort (font rendering, tap-to-click, ...), I used to let gnome-settings-daemon run in the background.
Now since upgrading to the F20 beta, my mouse cursor is disappearing right after executing /usr/libexec/gnome-settings-daemon. That is it visually disappears; I am still able to click on things. But the impact on usability is unbearable nonetheless.
At first I thought compton were at fault, which I installed fresh out of koji. But removing it from my autostart doesn't change things for the better. The mouse is just fine in Gnome itself. There's nothing suspicious in .xsession-errors as far as I can tell. I'm really out of ideas right now.
Relevant system info:
$ rpm -q openbox compton gnome-settings-daemon
openbox-3.5.2-2.fc20.x86_64
compton-0-0.3.20121218g75aec17.fc19.x86_64
gnome-settings-daemon-3.10.2-3.fc20.x86_64
$ uname -sr
Linux 3.11.10-301.fc20.x86_64
The machine itself is a X121e Thinkpad with a E-450 APU, powered by the OSS radeon driver.
fedora gnome openbox
fedora gnome openbox
asked Dec 17 '13 at 18:33
DaSourcererDaSourcerer
2213 silver badges13 bronze badges
asked Dec 17 '13 at 18:33
DaSourcererDaSourcerer
2213 silver badges13 bronze badges
edited Jan 27 '14 at 8:49
DaSourcerer
asked Dec 17 '13 at 18:33
DaSourcererDaSourcerer
2213 silver badges13 bronze badges
asked Dec 17 '13 at 18:33
DaSourcererDaSourcerer
2213 silver badges13 bronze badges
asked Dec 17 '13 at 18:33
DaSourcererDaSourcerer
2213 silver badges13 bronze badges
2213 silver badges13 bronze badges
I experienced the same problem on Ubuntu 13.10 with Openbox 3.5.2-3 and gnome-settings-daemon 3.8.5-0ubuntu9. Your answer below solved it!
– MDCore
Jan 23 '14 at 8:52
add a comment
|
I experienced the same problem on Ubuntu 13.10 with Openbox 3.5.2-3 and gnome-settings-daemon 3.8.5-0ubuntu9. Your answer below solved it!
– MDCore
Jan 23 '14 at 8:52
I experienced the same problem on Ubuntu 13.10 with Openbox 3.5.2-3 and gnome-settings-daemon 3.8.5-0ubuntu9. Your answer below solved it!
– MDCore
Jan 23 '14 at 8:52
I experienced the same problem on Ubuntu 13.10 with Openbox 3.5.2-3 and gnome-settings-daemon 3.8.5-0ubuntu9. Your answer below solved it!
– MDCore
Jan 23 '14 at 8:52
add a comment
|
2 Answers
2
active
oldest
votes
After further investigation, this post in the Arch forums revealed the answer. I used dconf-editor to navigate to org/gnome/settings-daemon/plugins/cursor and unticked the active setting. gnome-settings-daemon is behaving perfectly well now.
answered Jan 4 '14 at 15:49
DaSourcererDaSourcerer
2213 silver badges13 bronze badges
2
thank you for this; you could also use$dconf write /org/gnome/settings-daemon/plugins/cursor falsein case it's not possible to get a GUI (dconf-editor).
– ILMostro_7
Jan 26 '14 at 20:59
add a comment
|
Correction to IlMostro_7: It should be dconf write /org/gnome/settings/daemon/plugins/cursor/active false
answered Dec 20 '14 at 16:03
proyconproycon
2791 silver badge4 bronze badges
add a comment
|
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/4.0/"u003ecc by-sa 4.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f105607%2fmouse-cursor-disappearing-after-running-gnome-settings-daemon-in-openbox%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
After further investigation, this post in the Arch forums revealed the answer. I used dconf-editor to navigate to org/gnome/settings-daemon/plugins/cursor and unticked the active setting. gnome-settings-daemon is behaving perfectly well now.
answered Jan 4 '14 at 15:49
DaSourcererDaSourcerer
2213 silver badges13 bronze badges
2
thank you for this; you could also use$dconf write /org/gnome/settings-daemon/plugins/cursor falsein case it's not possible to get a GUI (dconf-editor).
– ILMostro_7
Jan 26 '14 at 20:59
add a comment
|
After further investigation, this post in the Arch forums revealed the answer. I used dconf-editor to navigate to org/gnome/settings-daemon/plugins/cursor and unticked the active setting. gnome-settings-daemon is behaving perfectly well now.
answered Jan 4 '14 at 15:49
DaSourcererDaSourcerer
2213 silver badges13 bronze badges
2
thank you for this; you could also use$dconf write /org/gnome/settings-daemon/plugins/cursor falsein case it's not possible to get a GUI (dconf-editor).
– ILMostro_7
Jan 26 '14 at 20:59
add a comment
|
After further investigation, this post in the Arch forums revealed the answer. I used dconf-editor to navigate to org/gnome/settings-daemon/plugins/cursor and unticked the active setting. gnome-settings-daemon is behaving perfectly well now.
answered Jan 4 '14 at 15:49
DaSourcererDaSourcerer
2213 silver badges13 bronze badges
After further investigation, this post in the Arch forums revealed the answer. I used dconf-editor to navigate to org/gnome/settings-daemon/plugins/cursor and unticked the active setting. gnome-settings-daemon is behaving perfectly well now.
answered Jan 4 '14 at 15:49
DaSourcererDaSourcerer
2213 silver badges13 bronze badges
answered Jan 4 '14 at 15:49
DaSourcererDaSourcerer
2213 silver badges13 bronze badges
answered Jan 4 '14 at 15:49
DaSourcererDaSourcerer
2213 silver badges13 bronze badges
answered Jan 4 '14 at 15:49
DaSourcererDaSourcerer
2213 silver badges13 bronze badges
2213 silver badges13 bronze badges
2
thank you for this; you could also use$dconf write /org/gnome/settings-daemon/plugins/cursor falsein case it's not possible to get a GUI (dconf-editor).
– ILMostro_7
Jan 26 '14 at 20:59
add a comment
|
2
thank you for this; you could also use$dconf write /org/gnome/settings-daemon/plugins/cursor falsein case it's not possible to get a GUI (dconf-editor).
– ILMostro_7
Jan 26 '14 at 20:59
2
2
thank you for this; you could also use
$dconf write /org/gnome/settings-daemon/plugins/cursor false in case it's not possible to get a GUI (dconf-editor).– ILMostro_7
Jan 26 '14 at 20:59
thank you for this; you could also use
$dconf write /org/gnome/settings-daemon/plugins/cursor false in case it's not possible to get a GUI (dconf-editor).– ILMostro_7
Jan 26 '14 at 20:59
add a comment
|
Correction to IlMostro_7: It should be dconf write /org/gnome/settings/daemon/plugins/cursor/active false
answered Dec 20 '14 at 16:03
proyconproycon
2791 silver badge4 bronze badges
add a comment
|
Correction to IlMostro_7: It should be dconf write /org/gnome/settings/daemon/plugins/cursor/active false
answered Dec 20 '14 at 16:03
proyconproycon
2791 silver badge4 bronze badges
add a comment
|
Correction to IlMostro_7: It should be dconf write /org/gnome/settings/daemon/plugins/cursor/active false
answered Dec 20 '14 at 16:03
proyconproycon
2791 silver badge4 bronze badges
Correction to IlMostro_7: It should be dconf write /org/gnome/settings/daemon/plugins/cursor/active false
answered Dec 20 '14 at 16:03
proyconproycon
2791 silver badge4 bronze badges
answered Dec 20 '14 at 16:03
proyconproycon
2791 silver badge4 bronze badges
answered Dec 20 '14 at 16:03
proyconproycon
2791 silver badge4 bronze badges
answered Dec 20 '14 at 16:03
proyconproycon
2791 silver badge4 bronze badges
2791 silver badge4 bronze badges
add a comment
|
add a comment
|
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f105607%2fmouse-cursor-disappearing-after-running-gnome-settings-daemon-in-openbox%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
I experienced the same problem on Ubuntu 13.10 with Openbox 3.5.2-3 and gnome-settings-daemon 3.8.5-0ubuntu9. Your answer below solved it!
– MDCore
Jan 23 '14 at 8:52