When starting with a new .config, if I try to start up "xfcalendar", it seems to hang. Reproducible: Always Steps to Reproduce: 1. erase .config 2. login 3. run xfcalendar from command line Actual Results: xfcalendar hung and did not display the calendar window Expected Results: should have shown the calendar, of course. see attachment of strace.
Created attachment 184 start up xfcalendar - it hangs on a poll and after a while, I kill it.
Actually it may not hand, it just may be invisible. Could you show what you have in your home directory .config/xfce4/xfcalendar If you have there hide tru changing it to show Do yo use clock panel plugin or systray ?
It seems to work most if not all of the time when I call it up by clicking on the clock. I don't think there has been a time when that has not worked. I'm talking about erasing the entire ".config" structure, and then just running "xfcalendar" from an xterm window after restarting xfce and it just hangs. It doesn't do it all the time, but it seems much more likely to happen if I start with a fresh configuration. Maybe you can try from a fresh configuration as well, and see if you get the same result.
Can't get it hang. Tried again. Just to be sure, could you show what: $ xfwm4 --version This is xfwm4 version 4.2.0 for Xfce 4.2.0 built with GTK+-2.4.13, linked with GTK+-2.4.13. shows.
show also the contents of cat .config/xfce4/xfcalendar/xfcalendarrc I would like to be sure it is not just hiding (instead of hanging). clicking the clock a few times does not help ?
xfwm4 --version shows: This is xfwm4 version 4.2.0 for Xfce 4.2.0 built with GTK+-2.6.2, linked with GTK+-2.6.2. cat .config/xfce4/xfcalendar/xfcalendarrc shows: [Session Visibility] hide You are absolutely correct. Changing this to "show" shows the calendar. Why would the default configuration be to "hide"? This makes it so that when you start xfcalendar from the command prompt that it seems to "hang". I'm sure there must be a reason, but why would anyone "hide" it? Thanks, jas.
Idea was that xfcalendar usually just runs in the background and does it alarms. It can quickly be activated by clikcing the clock or the systray. That was the idea. But in 4.2.1 this default has been changed. In the new version all these paramaters are visible in the genaral parameter screen and default is alwasy visible in all places. Anyway, It now works as planned.
Hi. Is it not a bug that if I place in SYSDIR/etc/xdg/xfce4/xfcalendar/xfcalendarrc a file that contains: [Session Visibility] show ... that when I start xfcalendar for the first time (where .config/xfce4/xfcalendar does not exist) that it does not import the global default of having a "show"? (And I instead get the same file with a "hide"). thanks..
New parameters released in 4.2.1
Moving all bugs to new Orage product.