You are not logged in.
Reded wrote:Possibly related to the above - When I run indicator-datetime-service, it terminates with this error when ran in a terminal:
terminate called after throwing an instance of 'std::logic_error' what(): basic_string::_S_construct null not valid zsh: abort /usr/lib/indicator-datetime/indicator-datetime-service
It runs for maybe 30 seconds before doing this, and doesn't appear when I login.
Same here:
$ time /usr/lib/indicator-datetime/indicator-datetime-service (process:5814): Indicator-Datetime-WARNING **: Getting timezone from systemd's timedate1 interface (process:5814): Indicator-Datetime-WARNING **: indicator-datetime cannot connect to EDS source: Unable to connect to 'Calendar': Cannot open calendar: Timeout was reached terminate called after throwing an instance of 'std::logic_error' what(): basic_string::_S_construct null not valid Aborted real 0m30.093s user 0m0.093s sys 0m0.010s
30 seconds was a very good estimate..
Edit:
Unfortunately, enabling systemd-timesyncd.service didn't help:
# systemctl enable systemd-timesyncd.service # systemctl start systemd-timesyncd.service
It's a new bug due to the recent update of other archlinux pakcages.
I haven't tested it, but I guess a clean rebuild of unity-for-arch would fix it.
Offline
And my other question: how to set things to run when Unity starts? In Ubuntu there is a startup items option in the power/gear menu.
Offline
It's a new bug due to the recent update of other archlinux pakcages.
I haven't tested it, but I guess a clean rebuild of unity-for-arch would fix it.
Thanks, qiuwei. I did a full rebuild, same problem.
Offline
Reded wrote:Possibly related to the above - When I run indicator-datetime-service, it terminates with this error when ran in a terminal:
terminate called after throwing an instance of 'std::logic_error' what(): basic_string::_S_construct null not valid zsh: abort /usr/lib/indicator-datetime/indicator-datetime-service
It runs for maybe 30 seconds before doing this, and doesn't appear when I login.
Same here:
$ time /usr/lib/indicator-datetime/indicator-datetime-service (process:5814): Indicator-Datetime-WARNING **: Getting timezone from systemd's timedate1 interface (process:5814): Indicator-Datetime-WARNING **: indicator-datetime cannot connect to EDS source: Unable to connect to 'Calendar': Cannot open calendar: Timeout was reached terminate called after throwing an instance of 'std::logic_error' what(): basic_string::_S_construct null not valid Aborted real 0m30.093s user 0m0.093s sys 0m0.010s
30 seconds was a very good estimate..
Edit:
Unfortunately, enabling systemd-timesyncd.service didn't help:
# systemctl enable systemd-timesyncd.service # systemctl start systemd-timesyncd.service
It turns out there's a patch called 0001-Get-timezone-from-systemd-s-timedate1-interface.patch in the PKGBUILD. Disabling it before building brings the clock back, but with the wrong timezone.
Non serviam
Offline
It turns out there's a patch called 0001-Get-timezone-from-systemd-s-timedate1-interface.patch in the PKGBUILD. Disabling it before building brings the clock back, but with the wrong timezone.
Yes. I debugged this yesterday but didn't have time to post it. You can use this patch to fix it with the correct timezone, too. I haven't found any issues with this fix yet. Download the patch, add
patch -p1 -i "${srcdir}/0003-Timezone-systemd-nullptr-check.patch"
in the pkgbuild after the first two patches, update the sha512sums and rebuild.
Alternatively, here's a package for x86_64 that you can use.
Edit: Changed patch
Last edited by aabmass (2014-07-02 15:15:31)
Offline
Yes. I debugged this yesterday but didn't have time to post it. You can use this patch to fix it with the correct timezone, too. I haven't found any issues with this fix yet. Download the patch, add
patch -p1 -i "${srcdir}/0003-Timezone-systemd-nullptr-check.patch"
in the pkgbuild after the first two patches, update the sha512sums and rebuild.
Alternatively, here's a package for x86_64 that you can use.
I couldn't apply the patch. The file being patched doesn't seem to exist.
can't find file to patch at input line 3
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- indicator-datetime-13.10.0+14.04.20140415.3/src/timezone-systemd.cpp 2014-06-30 15:38:53.397571301 -0400
|+++ indicator-datetime-13.10.0+14.04.20140415.3/src/timezone-systemd-nullcheck.cpp 2014-06-30 15:40:35.128794407 -0400
--------------------------
File to patch:
But I can confirm that the built package works. Thanks!
Non serviam
Offline
aabmass wrote:Yes. I debugged this yesterday but didn't have time to post it. You can use this patch to fix it with the correct timezone, too. I haven't found any issues with this fix yet. Download the patch, add
patch -p1 -i "${srcdir}/0003-Timezone-systemd-nullptr-check.patch"
in the pkgbuild after the first two patches, update the sha512sums and rebuild.
Alternatively, here's a package for x86_64 that you can use.
I couldn't apply the patch. The file being patched doesn't seem to exist.
can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- indicator-datetime-13.10.0+14.04.20140415.3/src/timezone-systemd.cpp 2014-06-30 15:38:53.397571301 -0400 |+++ indicator-datetime-13.10.0+14.04.20140415.3/src/timezone-systemd-nullcheck.cpp 2014-06-30 15:40:35.128794407 -0400 -------------------------- File to patch:
But I can confirm that the built package works. Thanks!
Same and same, thanks for the build!
"Some humans would do anything to see if it was possible to do it. If you put a large switch in some cave somewhere, with a sign on it saying "End-of-the-World Switch. PLEASE DO NOT TOUCH", the paint wouldn't even have time to dry."
Offline
I couldn't apply the patch. The file being patched doesn't seem to exist.
can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |--- indicator-datetime-13.10.0+14.04.20140415.3/src/timezone-systemd.cpp 2014-06-30 15:38:53.397571301 -0400 |+++ indicator-datetime-13.10.0+14.04.20140415.3/src/timezone-systemd-nullcheck.cpp 2014-06-30 15:40:35.128794407 -0400 -------------------------- File to patch:
But I can confirm that the built package works. Thanks!
Same and same, thanks for the build!
No problem! I updated the patch, but I don't think that was the problem. The patch patches a file created by 0001-Get-timezone-from-systemd-s-timedate1-interface.patch, so if they aren't in the right order in the pkgbuild, it won't work. Anyway, if you want to build it, here's a makepkg source tarball: https://dl.dropboxusercontent.com/s/upu … src.tar.gz
Offline
No problem! I updated the patch, but I don't think that was the problem. The patch patches a file created by 0001-Get-timezone-from-systemd-s-timedate1-interface.patch, so if they aren't in the right order in the pkgbuild, it won't work. Anyway, if you want to build it, here's a makepkg source tarball: https://dl.dropboxusercontent.com/s/upu … src.tar.gz
Oh, my mistake. I hadn't enabled back the 0001 patch. After doing that the package built fine. Thanks again!
Non serviam
Offline
Still wondering how to launch things when Unity starts. Anyone have a solution?
Offline
Still wondering how to launch things when Unity starts. Anyone have a solution?
I just use the systemd user session https://wiki.archlinux.org/index.php/Systemd/User There is a gnome-tweak-tool section for it but the add button doesn't seem to work for me Maybe it's hidden in dconf-editor somewhere?
"Some humans would do anything to see if it was possible to do it. If you put a large switch in some cave somewhere, with a sign on it saying "End-of-the-World Switch. PLEASE DO NOT TOUCH", the paint wouldn't even have time to dry."
Offline
I also would like to know how to add startup applications.
I have one bug at the moment that is driving me crazy. The Clock applet keeps crashing at login. I see it for a few seconds, then it is gone.
Is this a known bug? And I have no screen brightness control either.
Last edited by ryanvade (2014-07-13 04:12:18)
Offline
Another bug: Applets/menu does not appear after sleep.
Offline
I have one bug at the moment that is driving me crazy. The Clock applet keeps crashing at login. I see it for a few seconds, then it is gone.
That is a known bug. Apparently upstream indicator-datetime calls for the timezone in away that doesn't work on Arch (probably trying to ask Upstart or some such nonsense), and it has to be patched to get that data from systemd. Recompiling indicator-datetime from the AUR fixed it for me.
Last edited by okto (2014-07-13 19:51:34)
Offline
Thanks aabmass for the patch! I don't know if I posted this here earlier, but there's a Unity-for-Arch-Utopic repo based on my utopic branch at Github that includes packages from Ubuntu 14.10. These packages contain many fixes (like the indicator-datetime issue and the external monitor issue), but of course, they're basec on unstable packages. If you'd like to try the out, add the following repo above the Unity-for-Arch repo in pacman.conf:
[Unity-for-Arch-Utopic]
SigLevel = Optional TrustAll
Server = http://dl.dropbox.com/u/486665/Repos/$repo/$arch
Offline
Offline
Indicators don't work, I've installed from the unofficial repositorys.
Maybe someone can help me to make it work.
https://www.dropbox.com/s/70fmofqgxq0l7 … 0%3A20.png
Last edited by someone123 (2014-07-14 08:42:31)
Offline
Try my gnome-session-properties package on the AUR. It's the same thing Ubuntu uses (although it's not integrated into the menu).
Thanks! Exactly what I needed. I'm trying to decide whether or not to upgrade to the Utopic packages from your repo. Have they broken anything for you?
Offline
Indicators are now working for me. Even the calendar. Just need to get the screen brightness working (will just create a keyboard shortcut) . Thanks chenxiaolong and Okto
Last edited by ryanvade (2014-07-19 05:07:46)
Offline
I'm testing qt5 applications and I see it doesn't have a globalmenu. I have appmenu-qt5 and libdbusmenu-qt5 installed. Doesn't unity have qt5 globalmenu support yet?
Non serviam
Offline
I'm testing qt5 applications and I see it doesn't have a globalmenu. I have appmenu-qt5 and libdbusmenu-qt5 installed. Doesn't unity have qt5 globalmenu support yet?
Never mind, I got it working. I just needed to set the environment variable QT_QPA_PLATFORMTHEME=appmenu-qt5. Now I have globalmenu for QT5
Non serviam
Offline
Calendar is missing again.
Also, the logout button does not work.
Offline
Logged in today and neither the Unity panel nor the dock launched. A manual start of Unity reports "unity-panel-service not found".
Issued a pacman -Syu, reports conflicts between metacity and metacity-ubuntu, bamf and bamf-ubuntu, says compiz-ubuntu depends metacity (how is that even possible). Pacman -Syudd and -Syu --force did nothing to fix this. Removed bamf-ubuntu and metacity-ubuntu with -Rdd, currently running pacman -Syu.
Realize this is sort of a mishmash, will report back after system upgrade completes and I do a reboot, but does anyone know why this is suddenly happening?
I'm using the unofficial Utopic repo linked earlier in this thread.
Offline
dconf reset -f /org/compiz/ fixed it. Still curious what caused this in the first place.
Unrelatedly, this seems to have fixed the problem I was having with mount actions for removable disks double-launching.
Maybe a Unity reset is regular maintenance like a PRAM zap used to be on pre-Intel Macintoshes? I still get the urge to hold Cmd-Opt-P-R on boot when things don't work right.
Offline
I'm trying to install Unity on my new SSD drive, and it's saying that libgee06 isn't available. When I look up libgee06, it's available as an AUR package, but that doesn't help me install Unity from scratch. Will libgee06 be added to the Unity-for-Arch repo?
Offline