orage doesn't start nepbabu@everest:~$ orage ** Message: Orage **: Too small icon size, using static icon ** Message: Orage **: Build alarm list: Processed 0 events. Found 0 alarms of which 0 are active. (Searched 0 recurring alarms.) <program hangs now forever until CTRL-C is pressed>
upon stracing, it hangs with upon poll( ) ............. read(6, "\n", 1) = 1 read(6, "", 1) = 0 read(6, "", 1) = 0 time(NULL) = 1176218931 write(2, "** Message: Orage **: Build alar"..., 130** Message: Orage **: Build alarm list: Processed 0 events. Found 0 alarms of which 0 are active. (Searched 0 recurring alarms.) ) = 130 fcntl64(6, F_SETFD, 0xbfb9a744 /* FD_??? */) = 0 close(6) = 0 ioctl(3, FIONREAD, [0]) = 0 gettimeofday({1176218931, 89435}, NULL) = 0 poll([{fd=3, events=POLLIN}, {fd=4, events=POLLIN|POLLPRI}], 2, 4994) = 0 gettimeofday({1176218936, 83129}, NULL) = 0 time(NULL) = 1176218936 ioctl(3, FIONREAD, [0]) = 0 gettimeofday({1176218936, 83664}, NULL) = 0 poll([{fd=3, events=POLLIN}, {fd=4, events=POLLIN|POLLPRI}], 2, 5000) = 0 gettimeofday({1176218941, 83452}, NULL) = 0 time(NULL) = 1176218941 ioctl(3, FIONREAD, [0]) = 0 gettimeofday({1176218941, 83984}, NULL) = 0 poll( ...............
Probably Orage is running instead of hanging. Do you have orage-clock panel plugin in use? Try to click it with left button. You should see Orage to become visible? Then modify settings so that Orage is visible when started, Do you see Orage icon in systay Eiher click Orage icon so that Orage gets visible or select Preferences from the icon menu and change startup setting. If those did not aork, try starting Orage from another terminal also, that should again cause Orage to become visible. Which version of Orage you are using?
ok found orage plugin which has basic functionality of 1. display date 2. display day of the week 3. display the date in d/m/y format But the calendar is still missiong when ALT+F2 is pressed and then ``orage'' is typed, it still doesn't display properly. Only a tiny window with 1x1 pixel window border is displayed.
nepbabu@everest:~$ sudo apt-cache policy orage orage: Installed: 4.3.99.1svn+r23486-0ubuntu1 Candidate: 4.3.99.1svn+r23486-0ubuntu1 Version table: *** 4.3.99.1svn+r23486-0ubuntu1 0 500 http://au.archive.ubuntu.com edgy/main Packages 100 /var/lib/dpkg/status
Seems like Orage has problems communicating with the xfce-mcs-manager. When you start Xfce settings manager, can you make changes to Orage - Calendar settings? I have seen the same problem you are describing, but that was caused by using Orage version in corrupted install, so that Orage executable was from different version compared to Orage mcs client. But this can't be the case here? If you can find orage_plugin.so in your system (locate might help), you could check that it's size is big enough. It should be something like 50 k.
No, xfce-setting-show doesn't have orage calendar settings in it. nepbabu@everest:/$ sudo dpkg -L orage | grep orage_plugin.so /usr/lib/xfce4/mcs-plugins/orage_plugin.so nepbabu@everest:/$ ls -lh /usr/lib/xfce4/mcs-plugins/orage_plugin.so -rw-r--r-- 1 root root 26K 2006-10-21 13:12 /usr/lib/xfce4/mcs-plugins/orage_plugin.so So, it's only 26k and not 50k or so. what could be done ? Is this problem from Ubuntu devels or a specific problem with orage ?
I guess you have already started the environment so that mcs manager is up to the same level and should see Orage plugin? Installing Orage separately after mcs might cause this also (although I have never seen it). Try logging out and logging and check that xfce-mcs-manager has been restarted. The other issue causing this is version mismatch between two parts of Orage. If you compile from source, the problem is not there, so it is not Orage problem in itself. It is something in the environment. For some reason Orage is not able to communicate with mcs. (And it seems mcs itself can't see/communite with Orage mcs-plugin.). You could also compare the file settings with other plugins in the same plugin directory /usr/lib/xfce4/mcs-plugins/. Perhaps there is something different for Orage?
hey thanks. it's resolved now. Restarted the system and it's working now. ;) Thanks for the patience. It's a while now have to rest for a while. thanks again.
restart did the trick