Version: svn (using Devel) Installed from: Compiled sources OS: Linux Several times using SVN version (until last week), I could click in the clock in system tray, and I could get a calendar, and controls for navigating though dates (like prev-next day arrows, a date input, and so on), but now, I can't see any calendar, only that controls. Is this intented or is really a bug?
I'm sorry, I am not sure if it's a plasma bug or a pim one..
this is part of plasma, and it works just fine here using trunk/. can provide a screenshot? thanks.
Created attachment 23716 [details] screenshot showing the problem This is the screenshot shown the problem that does not show the calendar, only date controls.
I'm using also trunk. kdelibs Revision: 779409 kdebase Revision: 779409
Sorry for posting so fast, but I want to point out that the "first" time I click on clock, this window appears close to system's tray, and after that first time, window appears as shown in screenshot, which is a bit weird too..
evidently the calendar's KDateTable isn't getting painted/shown. dunno what that's about; the code looks fine and i honestly can't reproduce this. p.s. it's not the system tray; it's the panel. the system tray are those little icons from other apps that get embedded into the panel.
Maybe it is related to the repainting problem that are affecting kwin+qt4 this days.
FiNeX, now that you say that, I could say that I am having this issue SINCE I changed to qt-copy from kde's SVN, along with other repainting problems (close icon in window sometimes is not in the position it should be, and so on). I think I didn't have this with Qt 4.3. Does changing to official Qt 4.4 and not the qt-copy from SVN suppose any improvement, or at least a test to see if the kde's patches has something to do with it?
Qt4.4 is not relased yet, actually we are on the first beta. Maybe the next version will be improved even on this side. Keep looking on. I'll recompile whole qt-copy/kde on the next days.
Works here with a recent svn checkout and qt-copy.
Confirmed. It is working on revision 783974. I close this bug.
I need to reopen this, because I still can't see the calendar, but it happens a curious thing: I cannot get the calendar working in the clock plasmoid which is in my bottom bar (right side of systray), but if I add a new 'Digital CLock' plasmoid to Desktop, I CAN see that calendar. Is it casuality? I tested with SVN: 784601 of KDE libs, and I have SVN Revision 784563 of qt-copy. I tested with a new user without anything in ~/newuser folder, to create a 100% default config, and I can reproduce exactly this message within.
It is solved I don't know how. I just formatted to try amd64 arch, and the problem is away now.
I just had this happen in KDE 4.0.2. Removing my plasma config files (ie resetting desktop) didn't fix it either. I've tried also restarting X.
Also I am using Qt 4.3.4-r1 (r1 refers to gentoo revision, and they have applied this patch http://bugs.gentoo.org/213411 ) originally from fedora
So you are still having this issues? I couldn't fix that either, but in my case, after a format and a reinstall of gentoo, it gots fixed. It is a bit strange. Kalidam, I'll reopen that for you in that case, but could you try what I said in comment #12 (adding a new "digital clock plasmoid") and see if in that new you can see the calendar? For devs: it seems is related to some config issue, or maybe any installed file, because it makes no sense for me that it gets fixed only by formatting and reinstalling everything from scratch
Yeah i don't want to format and re-install and yes i've tried adding new digital clock plasmoids as well as rebooting X and then the entire machine as well as remerging plasma. Also tried creating a new user, and that didn't help either. I'm using gentoo too actually. Fixed the problem, downgrading QT version fixed it.
So it is definitely a QT bug, any other hint?
As I when downgrading to qt-4.3.4 the problem went away, well to be sure I upgraded to qt-4.3.4-r1 and then the problem returned. The only difference is that: # Anti-aliasing rules are broken in qt-4.3*, causing random runtime failures # in Qt programs. bug 213411. append-flags -fno-strict-aliasing
Then, try posting a bug in gentoo bugzilla telling that, and reference this bug in case they can do something against it. I had this problem with Qt-copy 4.4.0 from kde's svn too!
Then, try posting a bug in gentoo bugzilla telling that, and reference this bug in case they can do something against it. I had this problem with Qt-copy 4.4.0 from kde's svn too! 21 Mar 2008 01:13:05 -0000, Kalidarn <dcecchin@gmail.com>: [bugs.kde.org quoted mail] Then, try posting a bug in gentoo bugzilla telling that, and reference this bug in case they can do something against it. I had this problem with Qt-copy 4.4.0 from kde's svn too! <br><br><div><span class="gmail_quote">21 Mar 2008 01:13:05 -0000, Kalidarn <<a href="mailto:dcecchin@gmail.com">dcecchin@gmail.com</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> ------- You are receiving this mail because: -------<br> You reported the bug, or are watching the reporter.<br> <br> <a href="http://bugs.kde.org/show_bug.cgi?id=158409">http://bugs.kde.org/show_bug.cgi?id=158409</a><br> <br> <br> <br> <br> <br>------- Additional Comments From dcecchin gmail com 2008-03-21 02:13 -------<br> As I when downgrading to qt-4.3.4 the problem went away, well to be sure I upgraded to qt-4.3.4-r1 and then the problem returned.<br> <br> The only difference is that:<br> <br> # Anti-aliasing rules are broken in qt-4.3*, causing random runtime failures<br> # in Qt programs. bug 213411.<br> append-flags -fno-strict-aliasing<br> </blockquote></div><br><br clear="all"> <br>-- <br>影分身の術！
Sorry for my last report, I replied to the mail I received from bugzilla instead of posting bug directly. I've got a hint about this issue. Since removing this applet, and readding solves this issue, I think the problem is in some initialization issues between Clock and ~Clock, maybe when system loads, something can't be initializated well, and when destroyed and recreated object, is OK. I've been looking at the code, but since my level of C++ is not much I couldn't discover the real source. I've seen that is calls m_calendar.show() and I've been looking too at Qt documentation. I found: Calling setVisible(true) or show() sets the widget to visible status if all its parent widgets up to the window are visible. If an ancestor is not visible, the widget won't become visible until all its ancestors are shown. If its size or position has changed, Qt guarantees that a widget gets move and resize events just before it is shown. If the widget has not been resized yet, Qt will adjust the widget's size to a useful default using adjustSize(). As I said before, this problem can be solved by removing widget and recreating so maybe some "ancestor" is not visible (maybe because when loading all KDE stuff this widget loads before something...). Is this possible?
More info: When killing plasma, and started plasma in a konsole manually, I get this when clicking in clock to see calendar: QWidget::setLayout: Attempting to set QLayout "" on Plasma::Dialog "calendar", which already has a layout.
removing the applet and re-adding doesn't fix it for me, neither does killing plasma and restarting it. I do however see that error: "QWidget::setLayout: Attempting to add QLayout "" to Plasma::Dialog "calendar", which already has a layout"
WFM with Opensuse 10.3 and KDE 4.0.3. QT 4.3.4 installed. Is it necessary to let this bug open, if the problem seems to be in Qt 4.4?
Created attachment 24291 [details] another screenshot showing the problem Hi, I also have this problem for quite some time now ( a few months or so?). I just updated to latest qt-copy, kdelibs and kdebase, but the problem is still there.
*** Bug 160758 has been marked as a duplicate of this bug. ***
After a fresh install of kde4.1 beta 1 on ubuntu hardy i can't reproduce the bug. If the problem still exists please reopen it.