Only a temp KDE 4.5 beta 1 i686 repo

OK, After I heard that KDE 4.5 beta 1 is out, and kde-unstable is hold it, I remove kdemod as soon as possible to change to the offical kde and finally found that there is no i686 available!
I know a few days later they may set i686 repo up. But I can't wait ..
So I set up an kde-unstable repo for any one who want it.
If you want to use this one, it's your own risk.
It contains all kde package, support libs, and only some of the newer l10n package (many l10n packages don't compile..) and recompiled 4.4.3 kdepim (because new kdepim will not out with kde 4.5).
Backup your ~/.kde4 before updating
I don't promise to keep this repo sync with the offical repo, so if offical kde 4.5 beta is available in kde-unstable, you should switch to it.
If you have any problems like depend is missing, you should try to enable testing or tell me.
It will be fully available in few minutes, I'm uploading the final kdeedu packages.
i686 only!
[kde-unstable]
Server=http://csslayer-aur-repo.googlecode.com/files/

duendetuc wrote:Thanks. Now it works. But why I had to do this? Is the order important?
Yes. If packages with the same names exist in several repos, the order of repos is decisive.

Similar Messages

Kde 3.4 beta 2 transparency in taskbar

kde 3.4 beta 2 rocks...one tiny thing though, and im not sure if its a kde problem or a package problem...when i select the transparency option for the panel, a small section towards the right of the panel doesnt show the underlying wallpaper perfectly...its just a little bit messed up, but only in that one area, which is rectified if i hide/unhide the panel...just a small problem...happens every time i log on..does anyone have a soultion?
Thanks!

I don't use KDE 3.4beta2 yet... but I could suggest the following:
1. post a screenshot
2. http://bugs.kde.org (it might get fixed in the release) - make sure you link the screenshot also

Anyone tried KDE 4.2 Beta?

Anyone tried KDE 4.2 Beta? I'm thinking of testing out KDE 4.2 if it is better than the current KDE(Mod)4 in the repos.

Yep, so it says in your original link I have no gripes whatsoever about 4.1.96-1 apart from aforesaid kppp. Anyway, only three days to go until 4.2 proper comes out. I'll be counting the days 'til it hits the repos!

KDE 3.2 Beta 1

I know there are some KDE-Addicts among the Arch-Linux users!
Did anyone already compile the packages for the new KDE 3.2 Beta 1 and could put them into incoming?

KDE 3.2 sounds promising according to KDE's website:
<i>"With its 25 page feature plan, nearly 10,000 bugs closed and over 2,000 user wishes processed a complete report on what one can expect from Rudi would be so long that by the time you finished reading it, there would probably be a more current KDE release to try out. The only way to truly appreciate this release is to experience it first hand, but here are a few of the highlights anyways..."</i>
http://www.kde.org/announcements/announce-3.2beta1.php

[SOLVED] [no actual solution inside] No sound in KDE 4.1 beta

Installed KDE 4.1 beta as found here
There is no sound and device list in KDE control center shows ESD
I installed pulseaudio and added it and esd in the deamons in rc.conf and added the user in the groups and added the auth file in home
Now the module shows both ESD and the hardware device and still there is no sound
Any clue ?
EDIT
No miracle with the speakers being plugged in the microphone port
Last edited by 11010010110 (2008-07-20 13:26:02)

Try the latest RC and make sure to have phonon installed.

DRDY ERR I/O Errors only occur with KDE. HDD or kernel related?

This isn't too urgent since I'm not having this problem anymore, but I would like to know what caused it in the first place.
A few months ago, I think it was in May, when I was booting into KDE, the desktop wouldnt load. After logging in it goes to a black screen with a cursor. I check my tty consoles and they are all spammed with DRDY and I/O errors.
Today my log files don't go back to that time, but I apparantly wrote them down:
[timestamp] ata1.00: irq_stat 0x40000001
[timestamp] ata1: SError: { CommWake }
[timestamp] ata1.00: failed command: READ FPDMA QUEUED
[timestamp] ata1.00: cmd 60/08:00:79:c5:e9/00:00:38:00:00/40 tag 0 ncq 4096 in
[timestamp] res 41/40:08:7c:c5:e9/00:00:38:00:00/60 Emast 0x409 (media error) <F>
[timestamp] ata1.00: status {DRDY ERR }
[timestamp] error: { UNC }
[timestamp] end_request: I/O error, dev sda, sector 9540445540
It repeats this over and over again on all 7 consoles. I believe the hex numbers and sector # change slightly each time it repeats.
I restart the computer and it does the same thing. Then one day it booted into the desktop after sitting at a black screen with a cursor for 10 minutes.
When I saw Media and I/O error, I immediately thought it was my hard drive failing (which sucks because I had this computer for less than a year). But the weird thing was that once it finally boots into a desktop enviroment, everything works fine. I can access any file without any error, I can boot into my windows partition perfectly, and everything runs as fast as it did before. I ran fschk and chksdk several times, I passed with 0 bad sectors. SMART tests come out perfect.
The strangest thing about this is that the errors only come about when I boot into KDE. If I boot into any other enviroment I do not get these errors. Completely reinstalling KDE did not fix it. I don't remember updating or changing anything before these errors started appearing. I did do a full system update once I was actually able to get into my KDE session, but it didnt do anything. I eventually solved it by using another desktop enviroment, which was xfice at the time but now its cinnamon. I never got those errors ever since.
I posted something similar to this on KDE's forum, and no one could figure it out. One of the admins told me its very unusual that something like this would happen only with KDE, and the READ FPDMA/DRDY ERRs "are sourced from the kernel - and are disk/kernel related according to https://bugs.launchpad.net/ubuntu/+sour ... bug/550559."
As of now I can install KDE perfectly without any sort of issue, but I know several kernel updates occured since then. So could this be a issue with the kernel? Or is my hdd really starting to fail? I backed up the computer already, but I record music constantly and don't "aggresively" run backups (i.e not every day, but every month or so). Should I start doing so?
Thanks

68flag wrote:
@lspci
Those links you sent me were VERY helpful! I used the online SMART test using SpeedFan on windows; I never thought of using smartctl --all /dev/sda.
Heres what it gave me:
smartctl 5.43 2012-06-30 r3573 [x86_64-linux-3.4.9-1-ARCH] (local build)
Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net
=== START OF INFORMATION SECTION ===
Model Family: Toshiba 2.5" HDD MK..76GSX
Device Model: TOSHIBA MK5076GSX
Serial Number: 91OHT43CT
LU WWN Device Id: 5 000039 3818077b6
Firmware Version: GS002D
User Capacity: 500,107,862,016 bytes [500 GB]
Sector Size: 512 bytes logical/physical
Device is: In smartctl database [for details use: -P show]
ATA Version is: 8
ATA Standard is: Exact ATA specification draft version not indicated
Local Time is: Tue Aug 28 00:22:51 2012 EDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 120) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 163) minutes.
SCT capabilities: (0x003d) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 128
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0
3 Spin_Up_Time 0x0027 100 100 001 Pre-fail Always - 1756
5 Reallocated_Sector_Ct 0x0033 100 100 050 Pre-fail Always - 0
9 Power_On_Minutes 0x0032 092 092 000 Old_age Always - 3277h+14m
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 1072
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 2191
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 133
193 Load_Cycle_Count 0x0032 094 094 000 Old_age Always - 61036
194 Temperature_Celsius 0x0022 100 100 000 Old_age Always - 45 (Min/Max 15/53)
199 UDMA_CRC_Error_Count 0x0032 100 100 000 Old_age Always - 25758112
200 Multi_Zone_Error_Rate 0x0032 100 100 000 Old_age Always - 56684070
240 Head_Flying_Hours 0x0032 094 094 000 Old_age Always - 153507
241 Total_LBAs_Written 0x0032 100 100 000 Old_age Always - 5471510246
242 Total_LBAs_Read 0x0032 100 100 000 Old_age Always - 7806093714
254 Free_Fall_Sensor 0x0032 100 100 000 Old_age Always - 0
SMART Error Log Version: 1
ATA Error Count: 558 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 558 occurred at disk power-on lifetime: 2148 hours (89 days + 12 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
40 41 02 7c c5 e9 68 Error: UNC at LBA = 0x08e9c57c = 149538172
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
60 08 00 79 c5 e9 40 00 00:06:08.673 READ FPDMA QUEUED
ef 10 02 00 00 00 a0 00 00:06:08.673 SET FEATURES [Reserved for Serial ATA]
27 00 00 00 00 00 e0 00 00:06:08.673 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 a0 00 00:06:08.672 IDENTIFY DEVICE
ef 03 45 00 00 00 a0 00 00:06:08.672 SET FEATURES [Set transfer mode]
Error 557 occurred at disk power-on lifetime: 2148 hours (89 days + 12 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
40 41 02 7c c5 e9 68 Error: UNC at LBA = 0x08e9c57c = 149538172
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
60 08 00 79 c5 e9 40 00 00:06:04.673 READ FPDMA QUEUED
ef 10 02 00 00 00 a0 00 00:06:04.673 SET FEATURES [Reserved for Serial ATA]
27 00 00 00 00 00 e0 00 00:06:04.673 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 a0 00 00:06:04.672 IDENTIFY DEVICE
ef 03 45 00 00 00 a0 00 00:06:04.672 SET FEATURES [Set transfer mode]
Error 556 occurred at disk power-on lifetime: 2148 hours (89 days + 12 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
40 41 02 7c c5 e9 68 Error: UNC at LBA = 0x08e9c57c = 149538172
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
60 08 00 79 c5 e9 40 00 00:06:00.673 READ FPDMA QUEUED
ef 10 02 00 00 00 a0 00 00:06:00.673 SET FEATURES [Reserved for Serial ATA]
27 00 00 00 00 00 e0 00 00:06:00.673 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 a0 00 00:06:00.672 IDENTIFY DEVICE
ef 03 45 00 00 00 a0 00 00:06:00.672 SET FEATURES [Set transfer mode]
Error 555 occurred at disk power-on lifetime: 2148 hours (89 days + 12 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
40 41 02 7c c5 e9 68 Error: UNC at LBA = 0x08e9c57c = 149538172
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
60 08 00 79 c5 e9 40 00 00:05:56.673 READ FPDMA QUEUED
ef 10 02 00 00 00 a0 00 00:05:56.673 SET FEATURES [Reserved for Serial ATA]
27 00 00 00 00 00 e0 00 00:05:56.672 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 a0 00 00:05:56.672 IDENTIFY DEVICE
ef 03 45 00 00 00 a0 00 00:05:56.672 SET FEATURES [Set transfer mode]
Error 554 occurred at disk power-on lifetime: 2148 hours (89 days + 12 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
40 41 02 7c c5 e9 68 Error: WP at LBA = 0x08e9c57c = 149538172
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
61 08 18 d1 d8 e7 40 00 00:05:52.624 WRITE FPDMA QUEUED
61 08 10 89 d8 e7 40 00 00:05:52.624 WRITE FPDMA QUEUED
61 08 40 51 d8 e7 40 00 00:05:52.624 WRITE FPDMA QUEUED
61 10 38 01 d8 e7 40 00 00:05:52.623 WRITE FPDMA QUEUED
61 08 30 e1 d7 e7 40 00 00:05:52.623 WRITE FPDMA QUEUED
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed without error 00% 2320 -
# 2 Extended offline Aborted by host 90% 2075 -
# 3 Short offline Completed without error 00% 1900 -
# 4 Short offline Completed without error 00% 1574 -
# 5 Short offline Completed without error 00% 1415 -
# 6 Short offline Completed without error 00% 1081 -
# 7 Short offline Completed without error 00% 637 -
# 8 Short offline Completed without error 00% 248 -
# 9 Short offline Completed without error 00% 0 -
#10 Short offline Completed without error 00% 0 -
SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
The READ FPDMA QUEUED errors come up in SMART's log, so those problems I had have to be HDD related, not kernel. Other than that I really don't know what I'm looking at here. I don't like the numbers for UDMA_CRC_Error Count or Multi Zone Error rate, but I don't know what those mean. Until someone explains to me what I'm dealing with here, I'm going to assume it is an HDD problem and start furiously backing stuff up.
bart_b wrote:Some of these issues are related to interference of the Spread Spectrum Clocking (SSC), SSC is a way of eliminating interference. Now some BIOSes let you tweak this setting and some harddisks like WD have a jumper setting to disable/enable the spread spectrum frequency. But since it is more of a RF issue rearranging your sata cables might help or replace them with a better quality cable could do the trick to reduce interference. If you have overclocked your PC, try to re-tweak it to a more sane level.
I forgot to mention that my computer is a Dell Inspiron n5110. Its a piece of garbage, its the only computer I am aware off that has programs that PREVENT you from connecting to the internet when you don't buy their stupid extended warranty. I'm saving up for a thinkpad t420 but thats another story
Woah. Radio signals interfering with data passing through the SATA cables? I've had poorly sheilded guitar cables that pick up odd AM stations, but SATA cables? Thats bizzare. I don't own a PC yet, but I'm going to build one for my brothers once the parts come in, and I'll definitely make a note of that. I didn't even know you could overclock a CPU to the point where it GENERATES RF signals powerful enough to interfere with the HDD. Thats really interesting.
Another note I should mention is that the motherboard on my dell died maybe a month or 2 after the I/O errors. Gotta love dell. Every single dell computer I owned died of mobo failure without any warning. Even their printers. Good god.
Anyway, could the mobo have been a factor? I know the tech that replaced the mobo told me that the LCD cable wasn't seated correctly, so could the SATA cables have been bad as well? I really doubt it though, but who knows
Edited for embarrassing spelling mistakes
I think it's rather interesting that both you and I have Toshiba hard drives. I've heard that they're supposed to be as delicate as glass, but mine's held up all right, until these weird errors and stuff.
As for motherboards. If the motherboard is messed up, everything will seem messed up, but may or may not.

How can you remove old conversations from the iMac. Even when I remove them they return when I start a new conversation with the same person. Only happens on iMac with the Beta iMessage program

How do you remove an old conversation using the Beta iMessage on an iMac. When I open a new conversation with the same person the old conversation comes back

Hi,
Previously iChat had tried a Last Chat/IM option when using Saved Transcripts - which itself was an option.
iChat has also tried "Saving" the Last Chat by leaving a Chat window open and using something similar to the Lion method of showing an app in the state is was closed in.
In Messages the option to Save Transcripts has been removed and Chats or all types are saved as a matter of course.
What this tends to mean for your iChat style Buddy Chats is that it opens all the Transcripts for that buddy as a sort of History you can scroll back through if you want (I have some Buddies with saved chats gong back to 2004)
With the Syncing of iMessages with iPhones and iPads (or Touches) then it seems this works slightly differently.
Although you can delete the chat and the contents of the Chat as separate action it is true that in the Beta as soon as you connect to the same Contact that the contents of the previous chats are shown to you.
I have found that Messages stores a data base of info on iMessages in Your Home Folder/Library/Messages
I have found that deleting this chat-db removes the "History" that keep popping up.
By default the Saved "iChats" are also stored in the Home Folder/Documents/iChats (At least this is the default place iChat used and they go to the same iChats folder where ever you had it)
Some people claim removing iMessages saved here stops the "History" reappearing.
In Lion the only access to the Home Folder/Library is via the Finder's Go Menu and hiding down the ALT key
10:00 PM Sunday; June 10, 2012
Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"
 iMac 2.5Ghz 5i 2011 (Lion 10.7.4)
 G4/1GhzDual MDD (Leopard 10.5.8)
 MacBookPro 2Gb (Snow Leopard 10.6.8)
 Mac OS X (10.7.4),
"Limit the Logs to the Bits above Binary Images."  No, Seriously

KDE Applications look better in Cinammon. Solved

I am trying to get a decent desktop going. have installed KDE, KDE-Base etc.
But the KDE apps have very poor color scheme/fonts/ Thin light grey letters on a light grey tool bar.
I have tried to use KDE to change the themes but no luck.
I have installed Cinnamon, and when I run Konqueror etc under Cinnamon they look MUCH better. Menus and letters are readable.
Is there a way to fix KDE so the apps look right?
pgmer6809
Last edited by pgmer6809 (2014-05-09 20:50:12)

K Thanks for the pointers.
'looks right' means that under cinnamon the desktop does not look like kde (duh!) and the menu structures are all different, and the bar at the bottom is using non KDE icons etc.
Under KDE the fonts were grey on grey and very hard to read. (number one complaint).
However now fixed mostly. Changed the theme from CDE to Oxygen. and just to be safe the appplication appearance ditto.
KDE now seems useable.
Next step is to get X, KDE, and network to start automatically at boot.
Thanks again for the help.
pgmer6809

My phone is only offering upgrade to iOS 6 beta 3???

Tried all the standard stuff short of factory reset (last resort only!!!!) Any ideas?
Paul

The first step to take when any iOS device is acting up is to Reset it. I have seen excess battery drain ocasionally on every iOS device I've owned since my 1G touch. I would not consider it a major bug but something that happens on some devices occasionally. An app or process starts to misbehave pushing the processor to run harder consuming more battery power. The same happens on computers where they start to run slugish when a runaway process pushes the cpu to 100%. Just like restarting a PC Resetting the iOS device can clear out a misbehaving process.
The most reliable steps I found to Restore:
From the Home screen double tap the Home button to view the multitasking bar at the bottom. Tap and hold an app at the bottom till the icons wiggle with the minus button visible. Tap the button to close all apps then tap the Home button to get back to the Home page. Press and hold the Sleep button till you see the Slide to power off message and power it off. Once powered down completely press and hold the sleep button till the Apple icon appears.

KDE 4.2 Beta Crash

I've been using KDE 4 SVN for a while now without problems. But I think ever since I upgraded to Xorg 7.4, my KDE 4 crashes. It crashes a few seconds after the desktop is fully loaded. Does anyone know why this is happening?

You need to be more specific. No we don't know why this happens, because we don't have your log files, we don't have your hardware details, and we don't know what crashing is. Try searching the Wiki for 'Xorg Hotplugging', that might be the answer to your problem.
You can find your log files at /var/log
.log files contain the log of the current session
.old files contain the log of the last session (this is what you want, because this is where the crash would be)
next time please be more informative

How to enable kde 4 theme into libreoffice-fresh ?

Some time ago I installed libreoffice-fresh and the file dialogs and icons are "libreoffice-style" rather than "kde-style", i have installed "kdelibs" for KDE desktop integration .. but no result.
Any ideas?, any advice ?
Regards.

It was an error in PKGBUILD, sorry. Now it's improve. Try now, or....:
PKGBUILD:
# Maintainer: Piotr Gorski <[email protected]>
pkgname=kgtk
pkgver=0.11.0
pkgrel=3.1
pkgdesc="LD_PRELOAD hack with helper scripts to make gtk and qt-only programs use KDE file dialogs."
arch=('i686' 'x86_64')
url="http://www.kde-apps.org/content/show.php?content=36077"
license=('GPL')
depends=('kdelibs')
makedepends=('pkgconfig' 'automoc4' 'cmake' 'gettext' 'gtk2>=2.6' 'gtk3>=3.0')
install=kgtk.install
source=(http://kde-apps.org/CONTENT/content-files/36077-KGtk-${pkgver}.tar.bz2)
md5sums=('e5abf37b9f15b301d213ffb881144ddb')
build() {
cd "${srcdir}/KGtk-${pkgver}"
mkdir -p "${srcdir}/build"
cd "${srcdir}/build"
cmake "../KGtk-${pkgver}" -DCMAKE_INSTALL_PREFIX=/usr -DQT_QMAKE_EXECUTABLE=/usr/bin/qmake-qt4
package() {
cd "${srcdir}/build"
make || return 1
make DESTDIR=$pkgdir install || return 1
and kgtk.install:
post_install() {
echo ""
echo "This converts GTK Filedialogs to KDE4 dialogs."
echo ""
echo "You can run GTK applications in 2 ways:"
echo " A. Call /usr/bin/kgtk-wrapper gimp"
echo " B. Create a symbolic link from the wrapper script to"
echo " your application, e.g."
echo ""
echo " ln -s /usr/bin/kgtk-wrapper /usr/local/bin/gimp"
echo ""
echo " and make sure you run /usr/local/bin/gimp instead of"
echo " /usr/bin/gimp in the future"
echo ""
/bin/true
pre_remove() {
echo ""
echo "If you linked some GTK applications to the wrapper"
echo "script provided by this package, make sure to"
echo "remove those links."
echo ""
/bin/true
Now it builds pkg.tar.xz file:
tar -tvf kgtk-0.11.0-3.1-x86_64.pkg.tar.xz
-rw-r--r-- root/root 714 2014-12-30 22:48 .PKGINFO
-rw-r--r-- root/root 747 2014-12-30 22:48 .INSTALL
-rw-r--r-- root/root 1465 2014-12-30 22:48 .MTREE
drwxr-xr-x root/root 0 2014-12-30 22:48 usr/
drwxr-xr-x root/root 0 2014-12-30 22:48 usr/bin/
drwxr-xr-x root/root 0 2014-12-30 22:48 usr/lib/
drwxr-xr-x root/root 0 2014-12-30 22:48 usr/share/
drwxr-xr-x root/root 0 2014-12-30 22:48 usr/share/locale/
drwxr-xr-x root/root 0 2014-12-30 22:48 usr/share/locale/pt_BR/
drwxr-xr-x root/root 0 2014-12-30 22:48 usr/share/locale/fr/
drwxr-xr-x root/root 0 2014-12-30 22:48 usr/share/locale/en_GB/
drwxr-xr-x root/root 0 2014-12-30 22:48 usr/share/locale/zh_CN/
drwxr-xr-x root/root 0 2014-12-30 22:48 usr/share/locale/de/
drwxr-xr-x root/root 0 2014-12-30 22:48 usr/share/locale/cs/
drwxr-xr-x root/root 0 2014-12-30 22:48 usr/share/locale/es/
drwxr-xr-x root/root 0 2014-12-30 22:48 usr/share/locale/it/
drwxr-xr-x root/root 0 2014-12-30 22:48 usr/share/locale/ru/
drwxr-xr-x root/root 0 2014-12-30 22:48 usr/share/locale/ru/LC_MESSAGES/
-rw-r--r-- root/root 1470 2014-12-30 22:48 usr/share/locale/ru/LC_MESSAGES/kdialogd4.mo
drwxr-xr-x root/root 0 2014-12-30 22:48 usr/share/locale/it/LC_MESSAGES/
-rw-r--r-- root/root 1106 2014-12-30 22:48 usr/share/locale/it/LC_MESSAGES/kdialogd4.mo
drwxr-xr-x root/root 0 2014-12-30 22:48 usr/share/locale/es/LC_MESSAGES/
-rw-r--r-- root/root 1112 2014-12-30 22:48 usr/share/locale/es/LC_MESSAGES/kdialogd4.mo
drwxr-xr-x root/root 0 2014-12-30 22:48 usr/share/locale/cs/LC_MESSAGES/
-rw-r--r-- root/root 1149 2014-12-30 22:48 usr/share/locale/cs/LC_MESSAGES/kdialogd4.mo
drwxr-xr-x root/root 0 2014-12-30 22:48 usr/share/locale/de/LC_MESSAGES/
-rw-r--r-- root/root 1190 2014-12-30 22:48 usr/share/locale/de/LC_MESSAGES/kdialogd4.mo
drwxr-xr-x root/root 0 2014-12-30 22:48 usr/share/locale/zh_CN/LC_MESSAGES/
-rw-r--r-- root/root 1191 2014-12-30 22:48 usr/share/locale/zh_CN/LC_MESSAGES/kdialogd4.mo
drwxr-xr-x root/root 0 2014-12-30 22:48 usr/share/locale/en_GB/LC_MESSAGES/
-rw-r--r-- root/root 1199 2014-12-30 22:48 usr/share/locale/en_GB/LC_MESSAGES/kdialogd4.mo
drwxr-xr-x root/root 0 2014-12-30 22:48 usr/share/locale/fr/LC_MESSAGES/
-rw-r--r-- root/root 1305 2014-12-30 22:48 usr/share/locale/fr/LC_MESSAGES/kdialogd4.mo
drwxr-xr-x root/root 0 2014-12-30 22:48 usr/share/locale/pt_BR/LC_MESSAGES/
-rw-r--r-- root/root 1128 2014-12-30 22:48 usr/share/locale/pt_BR/LC_MESSAGES/kdialogd4.mo
drwxr-xr-x root/root 0 2014-12-30 22:48 usr/lib/kgtk/
drwxr-xr-x root/root 0 2014-12-30 22:48 usr/lib/kde4/
drwxr-xr-x root/root 0 2014-12-30 22:48 usr/lib/kde4/libexec/
-rwxr-xr-x root/root 81944 2014-12-30 22:48 usr/lib/kde4/libexec/kdialogd4
-rwxr-xr-x root/root 48376 2014-12-30 22:48 usr/lib/kgtk/libkgtk2.so
-rwxr-xr-x root/root 48384 2014-12-30 22:48 usr/lib/kgtk/libkgtk3.so
-rwxr-xr-x root/root 2009 2014-12-30 22:39 usr/bin/kgtk-wrapper
Last edited by pb (2014-12-30 21:53:41)

If ONLY the original Dev Beta is installed, will GM Candidate install over this without intervening betas?

I have an odd problem.
I installed the Yosemite dev beta back in August, and have all the intervening beta patches AND the GM Patch. My 7 1/2 year old iMac is failing, so I ordered a new one. It's supposed to be in today, and want to get it up to the Yosemite GM release.
So - is it possible to download and update JUST the original Yosemite beta, and then when I go to App Store, I will download and install ONLY the GM Candidate, and skip betas 2-8? It just takes my internet connection forever to download all the betas (due to size), and I'd basically just like to "cut to the chase" as they say.
Is that possible, or am I doomed to download and install each beta (fighting the debacles of beta 2 all over again)?

this is not possible. Snow leopard Mail will not work with any other version of OS X. you need to install Snow leopard if you want to run it.

New Case brings Better temps

I just got a new case today and I was excited to see my system temps and CPU temps drop quite substantially. When I bought my first case, I didn't notice that the PSU went directly in front of the the CPU cooler. I was worried, but my temps were ok, so I didn't care much.
My Original temps:
50 Idle
58 Load
However, in my new case, the PSU is located higher up in the case and is no where near my CPU cooler. I have no case fans in the new case but the new temps are still much better.
New Temps:
CPU Idle 41
CPU Load 49
To improve my CPU temp even more, I've got a TT Volcano 12 coming in tomorrow (I hope).
So, for all those out there experiencing high CPU temps, make sure your PSU is located high enough in the case that it is not covering your CPU fan intake.
This may seem obvious, but I don't know anyone who has experienced such a drop in CPU temperature just by switching cases (and no change in case fans).
Hope this is of some use to someone.

I agree that the case and case temp helps but you also have to make sure that you have good airflow and a top blowhole with a fan helps vent the case heat. Aluminum cases seem to work pretty good at keeping down the temps, it like having one big aluminum heat sink.

Xcompmgr messing with openbox windows (conky and kde apps only)

here's the involved packages:
openbox 3.4.7.2-1
nvidia 177.82-1
xorg-server 1.5.3-3
xcompmgr 1.1.4-1
kdelibs3 3.5.10-2
conky 1.6.1-2
now the issue is primarily with xcompmgr. when it's running (default options or the whole -cCfF... stuff doesn't make a difference). i have the following:
whenever a kde apps window opens. (i.e. i start amarok or k3b; k3b opens new windows during burn start/stop process) my conky will disappear only to flicker and reappear a few seconds later. (this only happens with kde apps)
when i'm tweaking my conky i will often `pkill conky; sleep 3; conky` to see my changes. when i kill conky, ALL of my active windows on the current desktop disappear and only reappear if a) they are redrawn because of an update to their contents on their own accord, or b) (kinda the same thing) i grab a window and drag it all over the screen resetting whatever i pass over to it's correct visual state. (this only happens when killing conky)
this is annoying me, i love the shadows/fading from xcompmgr but this flickering makes my whole experience feel unstable and i have to turn it off after a few minutes. turn off xcompmgr and it's rock solid just as before... snappier too i think.
this behavior started immediately after the recent xorg update (i saved that for last because i know were all sick of _that_). i changed nothing, but for the -Syu when this happened.
anyways, your thoughts and help is much appreciated.

so i'm resurrecting this thread because i hoped, and prayed, that xorg 1.6 in testing would fix this problem. i've been working my ass off to keep my system back in xorg 1.4. my desktop just looks so oldfashioned w/o shadows and transparency.
ok so to re-outline, i'm running:
pacman -Q stuff
xorg-server 1.6.0-1
nvidia 180.29-3
openbox 3.4.7.2-1
xcompmgr 1.1.4-1
with this gpu:
hwd -s | grep video
Video : GeForce 7150 / nForce 630i server: XFree86 (vesa)
i created a minimal xorg.conf via nvidia-xconfig an added a few suggested options (although they _really_ don't seem to affect this bug...):
cat /etc/X11/xorg.conf
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 1.0 (buildmeister@builder62) Thu Feb 5 00:08:50 PST 2009
Section "ServerLayout"
Identifier "Layout0"
Screen 0 "Screen0" 0 0
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName "Unknown"
HorizSync 28.0 - 33.0
VertRefresh 43.0 - 72.0
Option "DPMS"
EndSection
Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
Option "NoLogo" "True"
Option "RenderAccel" "True"
Option "TripleBuffer" "True"
Option "BackingStore" "False"
Option "DamageEvents" "True"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Depth 24
EndSubSection
EndSection
now, here's what happens:
i startx, .xinitrc or autostart.sh bring up xcompmgr, bmpanel, and conky
if i open amarok or k3b, conky and bmpanel (both using transparency) vanish while the splash screen(s) show.
when i burn something with k3b (and new windows appear) i see similar behavior
sometimes it's just for a sec and then it's back, sometimes conky comes back with part of itself missing
also, if you execute `pkill conky` from an xterm, all windows are 'destroyed' until you [blindly] grab that xterm window and move it about your desktop 'revealing' the desktops contents. please see this screenshot for this in action.
killing xcompmgr fixes all this... but it's so ugly. the problems go away if i downgrade to xorg-server 1.4 (and also adjust any related/dependant packages to match).
please please, tell me i'm not alone! a fix would be nice too .
thanks in advance... again
Last edited by brisbin33 (2009-03-05 01:30:10)

Kde-unstable beta 2 shows blank white screen

installed kde 4.3 beta 2 with pacman -R kde (4.2.4) and pacman -S kde-meta
after logging in the splash screen appears and later disappears leaving white blank screen
there used to be red X button (with title could not load this plasmoid when hovering over it) in the place where i had folder view in 4.2.4. it disppeared after i deleted ~/.kde4
the screen shows no reaction o any keys or clicks except alt F2 and alt ctrl del
in alt F2 commands can be typed but cannot be launched (as if they dont exist). task manager can be opened from there and it shows the normal kde apps (plasma etc) up and running
alt ctrl del logout menu works normal
UPDATE
i installed and installed kde and kde-meta few times more. nowi have kde 4.2.4 that won't open konqueror and few other apps and it has visual artifacts of kde 4.3
Last edited by ash (2009-07-14 11:58:29)

Try:
- iOS: Not responding or does not turn on
- Also try DFU mode after try recovery mode
How to put iPod touch / iPhone into DFU mode « Karthik's scribblings
- If not successful and you can't fully turn the iOS device fully off, let the battery fully drain. After charging for an least an hour try the above again.
- Try on another computer
- If still not successful that usually indicates a hardware problem and an appointment at the Genius Bar of an Apple store is in order.
Apple Retail Store - Genius Bar

Only a temp KDE 4.5 beta 1 i686 repo

Similar Messages

Maybe you are looking for