Small correction for comment "#18": the command to selectively restore a
configuration option is "dconf write" (not "dconf set").
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1756585
Title:
unity s
The problem was caused by an old (created under Ubuntu 12.04) DCONF
configuration (attached).
Apparently, there is code to reset such outdated configuration. In my
case, however, "/usr/lib/i386-linux-gnu/unity/compiz-config-profile-
setter" (usually) crashed (sometimes a SIGSEGV; sometimes the ina
"unity" starts again successfully. Unfortunately, I do not why.
What I did:
I noticed that in "~/.cache.upstart.unity7.log" I saw
compizconfig - Info: Backend : gsettings
compizconfig - Info: Integration : true
compizconfig - Info: Profile : unity-lowgfx
The "unity-lowgfx" surprized me. T
** Attachment added: "fail.activity"
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1756585/+attachment/5084784/+files/fail.activity
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1756585
Tit
** Attachment added: "ok.activity"
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1756585/+attachment/5084786/+files/ok.activity
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1756585
Title:
** Attachment added: "diff.activity"
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1756585/+attachment/5084787/+files/diff.activity
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1756585
Tit
I have compared the "syslog" messages for a failing ("unity" startup
fails) and a successful ("unity" startup correct) login. There are some
differences. But for me, they do not seem critical: in the failing case,
apparently, someone tries to start a "bamfdaemon" which is already
running; in the su
I can get back my compiz config with 'setsid compiz --replace' BUT
everything is lost again after reboot...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1756585
Title:
unity session without window
If I create a new user, "unity" starts fine (for this user).
This implies that the problem depends on the configuration of an old user
(created under Ubuntu 12.04).
"https://askubuntu.com/questions/17381/unity-doesnt-load-no-launcher-no-dash-appears/";
suggested to fix the problem by "dconf rese
I'm not sure if it's related, but when I log in with another account (regular
or administrator type), the problem doesn't appear.
Same thing if I create another account.
In my case, this bug concerns only the primary account.
--
You received this bug notification because you are a member of Ubun
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: unity (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1756585
Title:
unit
Bug may be related to https://bugs.launchpad.net/ubuntu/+source/at-
spi2-core/+bug/1285444
There the content of ".xsession.errors" was requested:
** Attachment added: "xsession-errors"
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1756585/+attachment/5083418/+files/xsession-errors
--
** Attachment added: "dbus.log"
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1756585/+attachment/5082963/+files/dbus.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1756585
Title:
unit
** Attachment added: "upstart-event-bridge.log"
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1756585/+attachment/5082968/+files/upstart-event-bridge.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
** Attachment added: "unity-panel-service.log"
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1756585/+attachment/5082964/+files/unity-panel-service.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
** Attachment added: "window-stack-bridge.log"
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1756585/+attachment/5082967/+files/window-stack-bridge.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
** Attachment added: "unity-settings-daemon.log"
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1756585/+attachment/5082966/+files/unity-settings-daemon.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
Downgrading of the above packages from "xenial-updates" to "xenial" has
not solved the problem. Further analysis is for the "xenial-updates"
versions.
At the beginning of the "unity session", "top" reveals a very high CPU
(and disk) usage by "dconf-service". Apparently, it is used by "compiz-
conf
18 matches
Mail list logo
