SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm not having that problem on Slackware32-current -- kde433
See my post above you.
For those of us sticking with the release version that comes with 4.2.4, we're all experiencing the problem. Was wondering if a fix would be backported to the stock release. Not all of us want to move to -current, but a backported fix would be nice.
If I scroll through the calender, it doesn't even hit January 2010. I have to manually choose 2010 on January 2011 to get it to change...then when I close and open, it's back to December 2010.
This is exactly the behavior that I observe. No crash, just the bad behavior. There is no way to get to January 2010 by scrolling with the arrows. You can only get there by going to January 2011 and then changing the date to 2010. And if you click on certain days, you go back to December 2010 (back to the future).
This occurs on an upgrade of 12.2 to 13.0, 32-bit version. I have a laptop with a clean install of the 32-bit version, and I've had no problems there. I also have a clean install of 13.0 64-bit, but X won't work at all, so I can't test KDE on that system.
Has anyone had this weird clock / calendar problem on a clean install of 13.0 32-bit version? Or just on the upgrade? Why would it only affect an upgrade?
Yes, I did rename ~/.kde before I started the upgrade.
This is exactly the behavior that I observe. No crash, just the bad behavior. There is no way to get to January 2010 by scrolling with the arrows. You can only get there by going to January 2011 and then changing the date to 2010. And if you click on certain days, you go back to December 2010 (back to the future).
This occurs on an upgrade of 12.2 to 13.0, 32-bit version. I have a laptop with a clean install of the 32-bit version, and I've had no problems there. I also have a clean install of 13.0 64-bit, but X won't work at all, so I can't test KDE on that system.
Has anyone had this weird clock / calendar problem on a clean install of 13.0 32-bit version? Or just on the upgrade? Why would it only affect an upgrade?
Yes, I did rename ~/.kde before I started the upgrade.
Mine was a clean installation of Slackware 13 32-bit and I noticed this problem today. I've only updated via slackpkg and nothing else. Haven't checked on my 64-bit Slackware installation on my work laptop.
What's strange is that while the tooltip shows the correct date, the calendar does not.
Yeah, the tooltip shows the right, time, but it also shows the wrong time simultaneously. Sort of. I'm in US Central time zone, which is the "Chicago" timezone in the date/time settings. The tooltip right now shows "Chicago 23:06 03 January 2010" and right below that "Chicago 05:06 04 January 2010". I've got my system clock set to UTC, with a minus six hour offset to US Central time zone. The first date and time is correct for US Central time zone. The second one shouldn't say "Chicago" since it is really the system-clock UTC time.
I'd prefer to be able to have the clock display CST rather than "Chicago", but that's a different issue.
I also notice this problem in Slackware 13 64 bits stable but only today. When I click on calender and select another months, I have a crash. I have to do a Ctrl+Alt+Delete to login again on KDE.
It happens on two of my machines that have Slackware 13 64 bits stable with KDE 4.2.4.
Last edited by Laodiceans; 01-06-2010 at 01:38 PM.
For those of us sticking with the release version that comes with 4.2.4, we're all experiencing the problem. Was wondering if a fix would be backported to the stock release. Not all of us want to move to -current, but a backported fix would be nice.
This was his post ...
Quote:
If I click on the clock in the system tray, KDE presents me with the calendar December 2010... if I try to change the display by clicking on the month and selecting Jan, KDE crashes!
Lol! what a piece of crap.
__________________
Love
I do not understand your comment ...
My response is in agreement with other responses to your post, at least until the time that my writing was ...
With continued I realized that you are using KDE default, but until then you not made that clear.
Anyway I was curious and I see the calendar with my Slack with KDE default. :-)
On the other hand my English is bad!
regards
ps:cmiranda sorry, I made a big mess. I could erase what I wrote but as is already written ...
Last edited by afreitascs; 01-09-2010 at 10:09 PM.
Checking my calender today, it is showing correct, January 6th.
Not sure what the issue was, but it looks like some kind of problem with the 1st 5 days of the year...and quite frankly, they've sucked, so Slackware can have them.
Clean install of 13-32bit. I just clicked it and my desktop disappeared into the dark abyss but I still have Firefox and a terminal running. That's pretty nice for a crash. ps says kde and all its related stuff is still running, but not plasma.
I'll have to check my Slackware64 13 installation on my work laptop. At first, I thought that maybe the fact that I was using ntpd to sync the clock on the PC, but my laptop isn't using ntpd to sync the time, so that rules out that suspicion.
svn co svn://anonsvn.kde.org/home/kde/branches/KDE/4.3/kdebase/workspace/plasma/applets/digital-clock
than
Code:
cd digital-clock
mkdir build
cd build
cmake -DCMAKE_INSTALL_PREFIX=`kde4-config --prefix` ..
but a receive this error
Code:
CMake Error at CMakeLists.txt:6 (kde4_add_ui_files):
Unknown CMake command "kde4_add_ui_files".
CMake Warning (dev) in CMakeLists.txt:
No cmake_minimum_required command is present. A line of code such as
cmake_minimum_required(VERSION 2.6)
should be added at the top of the file. The version specified may be lower
if you wish to support older CMake versions for this project. For more
information run "cmake --help-policy CMP0000".
This warning is for project developers. Use -Wno-dev to suppress it.
-- Configuring incomplete, errors occurred!
That will not work because it need another libraries too. The solution will be or to upgrade to KDE 4.3.4 or being stuck with this digital clock bug at slackware-stable on KDE 4.2.4.
Any help or advice from Pat Team would be great.
Well, I've checked the calendar today and it's working fine, just as JamesGT mentioned. Maybe it might have had something to do with how December 2009 was displaying some of the January 2010 date for that particular week and vice-versa....who knows? But at least now it's working as it should.
Did you tried open the calender and view the next months to January and then go back to January? When I do that I have crash. Everything disappears. It is like plasma had quit.
When I tried to use gdb to backtrace the crash is this the result:
Code:
gdb plasma
GNU gdb 6.8
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-slackware-linux"...
(no debugging symbols found)
(gdb) run
Starting program: /usr/bin/plasma
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
---Type <return> to continue, or q <return> to quit---
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[New Thread 0x7f8b1042e7a0 (LWP 8779)]
(no debugging symbols found)
(no debugging symbols found)
QLayout: Attempting to add QLayout "" to QWidget "", which already has a layout
Object::connect: Attempt to bind non-signal
TaskManager::TaskGroup::editRequest()
QCoreApplication::postEvent: Unexpected null receiver
plasma(8870)/libplasma Plasma::FrameSvg::resizeFrame: Invalid size QSizeF(-16,
26)
plasma(8870)/libplasma Plasma::FrameSvg::resizeFrame: Invalid size QSizeF(0, 0)
plasma(8870)/libplasma Plasma::FrameSvg::resizeFrame: Invalid size QSizeF(-16,
26)
plasma(8870)/libplasma Plasma::FrameSvg::resizeFrame: Invalid size QSizeF(0, 0)
QCoreApplication::postEvent: Unexpected null receiver
Program exited normally.
(gdb) QCoreApplication::postEvent: Unexpected null receiver
QCoreApplication::postEvent: Unexpected null receiver
QCoreApplication::postEvent: Unexpected null receiver
(gdb)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
