You are not logged in.
Since icu package upgrade unity is not working for me. I can open terminal and run applications but launcher, dash, top panel etc. are not displaying.
Also .xsession-errors is blank for me so don't know what is causing an issue.
Can anyone please guide me where to look for issue ?
Thanks.
Offline
Sounds like a Compiz issue to me.
Offline
Since icu package upgrade unity is not working for me. I can open terminal and run applications but launcher, dash, top panel etc. are not displaying.
Also .xsession-errors is blank for me so don't know what is causing an issue.
Can anyone please guide me where to look for issue ?
Thanks.
Same problem to me. I fixed it by open ccsm and re-enable "Ubuntu Unity Plugin"
Offline
I have this problem with System Monitor. The background is made transparent instead of white. It's like the problem with gnome-control-center before
http://i.imgur.com/B17RWHQs.png
This is a very common problem unfortunately. It is caused by using the overlay scrollbars with GNOME 3.12 (and possibly the Ubuntu themes). As I'm not very familiar with theming, there's not much I can do to fix it. If you don't care about losing the overlay scrollbars, you can just remove the package and everything will be fine:
pacman -Rc overlay-scrollbar
Offline
chenxiaolong wrote:Please do not "pacman -Syu" yet. I need to rebuild some packages for the new icu package.
EDIT: Building now
dee-ubuntu: https://jenkins.cxl.epac.to/job/ArchLin … 67/console
libcolumbus: https://jenkins.cxl.epac.to/job/ArchLin … 68/consoleEDIT2: It's safe to upgrade now
Hey brother, is it possible to install unity along side gnome without problems ?
Yes, gnome-shell should continue to work just fine
Offline
gauravpadia wrote:Since icu package upgrade unity is not working for me. I can open terminal and run applications but launcher, dash, top panel etc. are not displaying.
Also .xsession-errors is blank for me so don't know what is causing an issue.
Can anyone please guide me where to look for issue ?
Thanks.
Same problem to me. I fixed it by open ccsm and re-enable "Ubuntu Unity Plugin"
Thanks, that solved the issue for me too
Offline
You're doing a great job chenxiaolong, however I don't think I can life with Unity on Arch as a main DE, because it's really badly integrated with most Gnome core applications (Canonicals fault)
Have you considered making a nautilus-ubuntu package?
Offline
You're doing a great job chenxiaolong, however I don't think I can life with Unity on Arch as a main DE, because it's really badly integrated with most Gnome core applications (Canonicals fault)
Have you considered making a nautilus-ubuntu package?
There already is one (At least, I have one installed) It doesn't seem any different to the regular version though, so I dunno what it does...
"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
Thank you for your great work @chenxiaolong I installed today from your git repo. Unity for Arch repos are giving 404 error. I want to ask you sth. I am updating now some of Unity packages from Aur. Is this wrong? If I should not do these updates how can I update packages?
Offline
Thank you for your great work @chenxiaolong I installed today from your git repo. Unity for Arch repos are giving 404 error. I want to ask you sth. I am updating now some of Unity packages from Aur. Is this wrong? If I should not do these updates how can I update packages?
Speaking as the current maintainer of the majority of the Unity packages in the AUR I would recommend not mixing the two. Many of the packages there are based directly on chenxiaolong's packages (a big thanks to chenxiaolong btw) but I haven't used the same versioning. Some of the version strings for chenxiaolong's packages were too long for the AUR so I've simply used the actual version and the date of the source used. I've also reset the pkgrels to 1 because it doesn't make sense for a package to enter the AUR at pkgrel 102 or whatever. These aren't major issues but the differences in versioning could cause headaches. The other issue is that I didn't want to flood the AUR with duplicate packages so where possible I updated the existing bazaar packages instead of submitting new ones based on chenxiaolong's sources. This means the AUR packages have different dependency chains e.g. libindicator-bzr ido-bzr libunity-misc-bzr etc. Sorry for the inconvenience. I'll add a note to the wiki for future reference.
Last edited by Chazza (2014-04-23 13:07:30)
Offline
I have been searching the internet all day today trying to find a solution to my theme problem, and through my research, I have found that this has been a problem in Ubuntu since 11.10, if my memory serves me correctly. Everything seems to point me towards gnome-settings-daemon, which oi_wtf pointed out to me in an earlier reply. I was unable to solve the problem back then, but I seem to be making some progress on it now. I found a thread on Ubuntu forums that talked about this problem, and it seemed to be a consensus that gnome-settings-daemon was crashing. Restarting gnome-settings-daemon was one of the popular replies, but I have tried that via terminal, and I get command not found. I found another post that said there are two gnome-settings-daemons running at the same time, and offered a script to fix the problem. I have put the script in place, and it DOES make a difference- my theme stays much longer than it did before. Using gnome-system-monitor, I can replicate the problem by killing the gnome-settings-daemon process. Here are screenshots that show the degradation in my themes:
Normal settings, prior to killing gnome-settings-daemon:
http://s532.photobucket.com/user/horsem … 5.png.htmlAfter killing the first gnome-settings-daemon process:
http://s532.photobucket.com/user/horsem … 5.png.htmlAfter killing the second gnome-settings-daemon process:
http://s532.photobucket.com/user/horsem … 4.png.htmlI'm still at a loss for what's causing the crash, but it seems to me that once I kill the process the first time, another one immediately starts (checking the 2nd process shows it starts RIGHT after the initial change in my themes) and holds the downgraded theme for a short while, then that one crashes as well. With the script I mentioned earlier in place, I haven't stayed on my desktop long enough to see if there is a second crash. I will do some further testing and try to find out what's going on. Is there a log file somewhere that will show me what's happening when gnome-settings-daemon crashes? That would be particularly helpful.
Moderator edit [ewaller] Large images were being displayed. I see you tried to create click through images, but the target of the img tags should be thumbnails, not the full size images. I broke the img tags so they won't display. Feel free to replace the target of the img tags with links to thumbnails, and take the spaces I placed in the img tags back out. The links to the full size images should still work.
I kept my desktop open and yes, even with the script, the second gnome-settings-daemon crashes. Am I the only one having this issue? Anyone?
Last edited by horsemanoffaith (2014-04-24 05:12:24)
Offline
Never seen anything like that before. Does gsd crash for any theme you apply or just for the particular theme you were using in your first screenshot?
Offline
horsemanoffaith wrote:I have been searching the internet all day today trying to find a solution to my theme problem, and through my research, I have found that this has been a problem in Ubuntu since 11.10, if my memory serves me correctly. Everything seems to point me towards gnome-settings-daemon, which oi_wtf pointed out to me in an earlier reply. I was unable to solve the problem back then, but I seem to be making some progress on it now. I found a thread on Ubuntu forums that talked about this problem, and it seemed to be a consensus that gnome-settings-daemon was crashing. Restarting gnome-settings-daemon was one of the popular replies, but I have tried that via terminal, and I get command not found. I found another post that said there are two gnome-settings-daemons running at the same time, and offered a script to fix the problem. I have put the script in place, and it DOES make a difference- my theme stays much longer than it did before. Using gnome-system-monitor, I can replicate the problem by killing the gnome-settings-daemon process. Here are screenshots that show the degradation in my themes:
Normal settings, prior to killing gnome-settings-daemon:
http://s532.photobucket.com/user/horsem … 5.png.htmlAfter killing the first gnome-settings-daemon process:
http://s532.photobucket.com/user/horsem … 5.png.htmlAfter killing the second gnome-settings-daemon process:
http://s532.photobucket.com/user/horsem … 4.png.htmlI'm still at a loss for what's causing the crash, but it seems to me that once I kill the process the first time, another one immediately starts (checking the 2nd process shows it starts RIGHT after the initial change in my themes) and holds the downgraded theme for a short while, then that one crashes as well. With the script I mentioned earlier in place, I haven't stayed on my desktop long enough to see if there is a second crash. I will do some further testing and try to find out what's going on. Is there a log file somewhere that will show me what's happening when gnome-settings-daemon crashes? That would be particularly helpful.
Moderator edit [ewaller] Large images were being displayed. I see you tried to create click through images, but the target of the img tags should be thumbnails, not the full size images. I broke the img tags so they won't display. Feel free to replace the target of the img tags with links to thumbnails, and take the spaces I placed in the img tags back out. The links to the full size images should still work.
I kept my desktop open and yes, even with the script, the second gnome-settings-daemon crashes. Am I the only one having this issue? Anyone?
I've never run into this issue on Arch or Ubuntu (though I do use a very standard setup with the default themes). Do you know how gnome-settings-daemon is crashing, like what error message it generates?
Could you try running the following command? It'll kill all running gnome-settings-daemon processes and start it again with debug messages enabled.
killall gnome-settings-daemon; G_MESSAGES_DEBUG=all /usr/lib/gnome-settings-daemon/gnome-settings-daemon
Offline
Thank you for your great work @chenxiaolong I installed today from your git repo. Unity for Arch repos are giving 404 error. I want to ask you sth. I am updating now some of Unity packages from Aur. Is this wrong? If I should not do these updates how can I update packages?
Glad you're enjoying Unity The repos probably 404'd because you updated while a package was being uploaded.
Like @Chazza mentioned, updating to the AUR packages is not a good idea. If any packages are doing that, please let me know and so I can update the version number.
Offline
I've never run into this issue on Arch or Ubuntu (though I do use a very standard setup with the default themes). Do you know how gnome-settings-daemon is crashing, like what error message it generates?
Could you try running the following command? It'll kill all running gnome-settings-daemon processes and start it again with debug messages enabled.
killall gnome-settings-daemon; G_MESSAGES_DEBUG=all /usr/lib/gnome-settings-daemon/gnome-settings-daemon
I ran your code immediately upon log-in, and it kills the default theme and goes to the theme in my second screenshot. Eventually, it crashes again, with the error below and changes the theme in line with the third screenshot.
GnomeDesktop:ERROR:gnome-rr.c:527:screen_update: assertion failed: (screen != NULL)
Aborted (core dumped)
Any idea what could be causing this? I tried changing to the Catalyst drivers, but that didn't do any good. It looks to have something to do with either the video drivers or X. I also saw some people on Ubuntu forums say it had something to do with xRandR. Any help you can give me with this would be greatly appreciated. I really do want to use Unity for Arch, but this theme changing nonsense is driving me CRAZY!!!
Offline
Well done,
Offline
I've never run into this issue on Arch or Ubuntu (though I do use a very standard setup with the default themes). Do you know how gnome-settings-daemon is crashing, like what error message it generates?
Could you try running the following command? It'll kill all running gnome-settings-daemon processes and start it again with debug messages enabled.
killall gnome-settings-daemon; G_MESSAGES_DEBUG=all /usr/lib/gnome-settings-daemon/gnome-settings-daemon
Hey, Chen, I installed Unity on my desktop (and that made me REALLY nervous with the issues I'm having with it on my laptop), and I have had zero issues with it so far, and I've been on Unity for at least 30 minutes. That makes me think that the problem is specific to my laptop, which brings me back to my video drivers. I did a fresh install of Arch and Unity last night, and the exact same thing happened. What I'm wondering, at this point, is if it has something to do with Intel's video driver. I run an nVidia card on my desktop, and an ATI video card on my laptop. I know that I've had issues with the Intel video driver in the past, because I've had to downgrade the Intel driver to get X to start on the previous version of Catalyst (14.3 beta, I believe). Not too long ago I was having issues with the video drivers, and it ended up that the scanner driver installation was screwing up my video drivers. While I was looking at the X log file, I noticed that the Intel section always came up with null on the screens section, so X looked to the ATI driver. I'm not sure why that is, but I'm going to do a little more research and see if I can find out what the exact cause of GSD crashing on me is. My laptop is a Hybrid Graphics machine, so I'm going to try switching to the Intel chip and see if there's any difference.
UPDATE: Switching to the Intel chip made no difference. I looked to see if there is a generic video driver, and I found the vesa driver. I deleted catalyst-test-pxp, which also deletes the Intel driver, and installed the vesa drivers. So far, I have had no issues with GSD crashing on me. Being the type that I have to know what the root of the problem is, I have removed and re-installed the Intel drivers to see if GSD crashes on me.
UPDATE 2: I have reinstalled the Intel driver, and I have not had a crash in about 15 minutes. I'm not sure made the difference, because I installed the Intel driver when I installed Arch. I looked in my xorg file, and the Intel module is showing up, where before when I looked in the log, it was not. Now that I know this is working, I think I will try re-installing Catalyst and see if the crashes come back.
UPDATE 3: I have reinstalled catalyst-test-pxp, and so far no crash. Looking in my Xorg log, everything seems to be on the up and up. I'm not sure why it's crashing upon a new install, but so far everything is working properly. I will do another update if I have any more crashes.
Last edited by horsemanoffaith (2014-04-25 22:54:13)
Offline
chenxiaolong wrote:I've never run into this issue on Arch or Ubuntu (though I do use a very standard setup with the default themes). Do you know how gnome-settings-daemon is crashing, like what error message it generates?
Could you try running the following command? It'll kill all running gnome-settings-daemon processes and start it again with debug messages enabled.
killall gnome-settings-daemon; G_MESSAGES_DEBUG=all /usr/lib/gnome-settings-daemon/gnome-settings-daemon
Hey, Chen, I installed Unity on my desktop (and that made me REALLY nervous with the issues I'm having with it on my laptop), and I have had zero issues with it so far, and I've been on Unity for at least 30 minutes. That makes me think that the problem is specific to my laptop, which brings me back to my video drivers. I did a fresh install of Arch and Unity last night, and the exact same thing happened. What I'm wondering, at this point, is if it has something to do with Intel's video driver. I run an nVidia card on my desktop, and an ATI video card on my laptop. I know that I've had issues with the Intel video driver in the past, because I've had to downgrade the Intel driver to get X to start on the previous version of Catalyst (14.3 beta, I believe). Not too long ago I was having issues with the video drivers, and it ended up that the scanner driver installation was screwing up my video drivers. While I was looking at the X log file, I noticed that the Intel section always came up with null on the screens section, so X looked to the ATI driver. I'm not sure why that is, but I'm going to do a little more research and see if I can find out what the exact cause of GSD crashing on me is. My laptop is a Hybrid Graphics machine, so I'm going to try switching to the Intel chip and see if there's any difference.
UPDATE: Switching to the Intel chip made no difference. I looked to see if there is a generic video driver, and I found the vesa driver. I deleted catalyst-test-pxp, which also deletes the Intel driver, and installed the vesa drivers. So far, I have had no issues with GSD crashing on me. Being the type that I have to know what the root of the problem is, I have removed and re-installed the Intel drivers to see if GSD crashes on me.
UPDATE 2: I have reinstalled the Intel driver, and I have not had a crash in about 15 minutes. I'm not sure made the difference, because I installed the Intel driver when I installed Arch. I looked in my xorg file, and the Intel module is showing up, where before when I looked in the log, it was not. Now that I know this is working, I think I will try re-installing Catalyst and see if the crashes come back.
UPDATE 3: I have reinstalled catalyst-test-pxp, and so far no crash. Looking in my Xorg log, everything seems to be on the up and up. I'm not sure why it's crashing upon a new install, but so far everything is working properly. I will do another update if I have any more crashes.
Thanks for the detailed information! If the video drivers are really the cause of the issue, I can make another gnome-settings-daemon package that strips out all the multiple monitors, etc. code since that doesn't work in Unity anyway.
I'm curious to know why the order you installed the video drivers matters. With Xorg autodetecting nowadays, I wouldn't think that this would be an issue (although you did mention that the log doesn't show the intel module).
Offline
Thanks for the detailed information! If the video drivers are really the cause of the issue, I can make another gnome-settings-daemon package that strips out all the multiple monitors, etc. code since that doesn't work in Unity anyway.
I'm curious to know why the order you installed the video drivers matters. With Xorg autodetecting nowadays, I wouldn't think that this would be an issue (although you did mention that the log doesn't show the intel module).
I spoke too soon on the Catalyst driver. GSD did crash on me. I am currently running the vesa drivers. I downloaded half-life, played the hazard course, made a Skype call, and I'm just letting it sit. So far, it hasn't crashed with vesa. If it holds, I'll try it with JUST the Intel drivers and see if it works. My desktop has been solid as a rock... no change.
UPDATE: Nope, it's not totally video drivers. It crashed on vesa, too. I was playing Portal 2 native Linux (very graphically intensive program!!!) when the crash occurred, but still, my theme lasted for a LONG time- way longer than any other so far. Now it's back to the drawing board to figure out what's causing the crash.
Last edited by horsemanoffaith (2014-04-26 02:00:27)
Offline
Hi chenxiaolong, the latest updates are looking really good! Thanks for all the hard work.
There's just a few issues:
1. Zeitgeist isn't being very intelligent. It appears that it lists search results in reverse alphabetical order. If I have two files, "blah1.odt" and "blah2.odt", it always shows "blah2.odt" first, even if I open "blah1.odt" more frequently. Likewise, if I copy a file with the file manager, it keep remembering the default name [like "blah2(copy).odt"] and keeps showing it in the search results even if I later rename it. I'm not sure if this is a bug specific to Arch Unity or maybe it's present on Ubuntu too.
2. I can't make the keyboard shortcuts work to change keyboard languages. I can set the shortcut (Ctl-ShiftLeft), but it doesn't actually work to change the language. Again, not sure if this is specific to Arch Unity or not.
Thanks again for working on this!
Last edited by sb56637 (2014-04-28 14:36:26)
Offline
What to do after installing??
I've tried to put "exec unity" in my .xinitrc, but when I execute X, it only shows a blank black wallpaper and a black cursor
Offline
What to do after installing??
I've tried to put "exec unity" in my .xinitrc, but when I execute X, it only shows a blank black wallpaper and a black cursor
You have to put:
exec gnome-session --session=ubuntu
Offline
I can never reach the repo: it always gives 404. Is there a particular reason?
Offline
when I try to run unity-control-center or gnome-control-center I get:
error while loading shared libraries: libcolord.so.1: cannot open shared object file: No such file or directory
I have extra/colord installed, and I tried with systemctl start colord but nothing change
Offline
when I try to run unity-control-center or gnome-control-center I get:
error while loading shared libraries: libcolord.so.1: cannot open shared object file: No such file or directory
I have extra/colord installed, and I tried with systemctl start colord but nothing change
Make sure libcolord.so.1 is in your /usr/lib directory, also keep your git clone and your system up to date. I don't think it's a PKGBUILD problem because for me it built ok. But you can always install the binary from the unity repository and be from building problems, if you wish.
Non serviam
Offline