Hide the kittens and the babies, a message from your friendly KDE-SIG
For those brave souls still running or trying to run rawhide just wanted to let you know that KDE is broken. As we speak most Qt based apps will just crash with a message about a missing symbol. To top that we are also preparing for KDE 4.4 beta 1; so don't expect a quick resolution, in fact things will get worse before they get better. Look on the bright side, F12 is rock solid, and with your patience F13 will be even better. We are shooting to have everything fixed by Monday the 30th, so please bear with us as we work to bring you another great KDE release. Steven -- = Steven M. Parrish - gpg fingerprint: 4B6C 8357 059E B7ED 8095 0FD6 1F4B EDA0 A9A6 13C0 http://tuxbrewr.fedorapeople.org/ irc.freenode.net: SMParrish @ #fedora-kde, #fedora-olpc, #sugar, #fedora- devel ___ Fedora-devel-announce mailing list fedora-devel-annou...@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-announce -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Bug Triage workflow for F13 and beyond
Today we celebrate another successful Fedora release (F12), congratulations to everyone. Never one to sit still development has already begun on F13, and with it comes a new bug triage work flow. For bugs filed against F13(rawhide) and beyond the keyword Triaged will now be used to indicate that a bug report has been triaged. BugZappers will no longer change the bug state to ASSIGNED, that will now be left in the hands of the package maintainers. BugZappers will still be using the NEEDINFO flag and closing reports as duplicates. The wiki will soon be updated to reflect these changes. Steven = Steven M. Parrish - gpg fingerprint: 4B6C 8357 059E B7ED 8095 0FD6 1F4B EDA0 A9A6 13C0 http://tuxbrewr.fedorapeople.org/ IRC nick: SMParrish on irc.freenode.net Channels: #fedora-kde, #fedora-olpc, #sugar, #fedora-devel, and many more ___ Fedora-devel-announce mailing list fedora-devel-annou...@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-announce -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: bug in fedora 11
(0x7fd261c5e000) libXi.so.6 = /usr/lib64/libXi.so.6 (0x7fd261a54000) libXcursor.so.1 = /usr/lib64/libXcursor.so.1 (0x7fd261849000) libXcomposite.so.1 = /usr/lib64/libXcomposite.so.1 (0x7fd261647000) libXdamage.so.1 = /usr/lib64/libXdamage.so.1 (0x7fd261445000) libselinux.so.1 = /lib64/libselinux.so.1 (0x7fd261226000) libpng12.so.0 = /usr/lib64/libpng12.so.0 (0x7fd261001000) libpixman-1.so.0 = /usr/lib64/libpixman-1.so.0 (0x7fd260dbb000) libz.so.1 = /lib64/libz.so.1 (0x7fd260ba6000) libexpat.so.1 = /lib64/libexpat.so.1 (0x7fd26097e000) /lib64/ld-linux-x86-64.so.2 (0x00362300) libcap.so.2 = /lib64/libcap.so.2 (0x7fd260779000) libi18npaperlx.so = /usr/lib64/ openoffice.org/basis3.1/program/libi18npaperlx.so (0x7fd260573000) libbasegfxlx.so = /usr/lib64/ openoffice.org/basis3.1/program/libbasegfxlx.so (0x7fd2602cd000) libSM.so.6 = /usr/lib64/libSM.so.6 (0x7fd2600c5000) libICE.so.6 = /usr/lib64/libICE.so.6 (0x7fd25fea9000) libi18nisolang1gcc3.so = /usr/lib64/ openoffice.org/basis3.1/program/libi18nisolang1gcc3.so (0x7fd25fca2000) libi18nutilgcc3.so = /usr/lib64/ openoffice.org/basis3.1/program/libi18nutilgcc3.so (0x7fd25fa8f000) libicuuc.so.40 = /usr/lib64/libicuuc.so.40 (0x7fd25f749000) libicudata.so.40 = /usr/lib64/libicudata.so.40 (0x7fd25e804000) libicule.so.40 = /usr/lib64/libicule.so.40 (0x7fd25e5cf000) libjvmaccessgcc3.so.3 = /usr/lib64/ openoffice.org/basis3.1/program/../ure-link/lib/libjvmaccessgcc3.so.3(0x000 07fd25e3c7000) libuno_salhelpergcc3.so.3 = /usr/lib64/ openoffice.org/basis3.1/program/../ure-link/lib/libuno_salhelpergcc3.so.3(0 x7fd25e1c3000) libcrypt.so.1 = /lib64/libcrypt.so.1 (0x7fd25df8b000) libxcb.so.1 = /usr/lib64/libxcb.so.1 (0x7fd25dd7) libXau.so.6 = /usr/lib64/libXau.so.6 (0x7fd25db6d000) libattr.so.1 = /lib64/libattr.so.1 (0x7fd25d969000) libuuid.so.1 = /lib64/libuuid.so.1 (0x7fd25d764000) libfreebl3.so = /lib64/libfreebl3.so (0x7fd25d506000) ...end sample ldd details ... What is this? I would strongly recommend that you checkout https://bugzilla.redhat.com You may be able to find a bug report that already addresses this, if not you can open one. That is the best way to get your issue to the appropriate people. Steven = Steven M. Parrish - gpg fingerprint: 4B6C 8357 059E B7ED 8095 0FD6 1F4B EDA0 A9A6 13C0 http://tuxbrewr.fedorapeople.org/ irc.freenode.net: SMParrish @ #fedora-kde, #fedora-devel, #fedora-olpc, #sugar -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Looking for people who need guests.
I'm looking to put some load on our new cloud environment. This is a pre-pre-pre type setup. The guests will go up, they'll go down. You know the deal. You'll only have this guest for a month or so but if you think you could use a guest, let me know. Because right now the guests aren't actually doing work. -Mike ___ Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list I'll be glad to give one a spin. FAS Name Tuxbrewr Steven = Steven M. Parrish - gpg fingerprint: 4B6C 8357 059E B7ED 8095 0FD6 1F4B EDA0 A9A6 13C0 http://tuxbrewr.fedorapeople.org/ irc.freenode.net: SMParrish @ #fedora-kde, #fedora-devel, #fedora-olpc, #sugar ___ Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
Re: Whither KDELIBS-4.3?
For the past few days, my system has wanted to update KTorrent, but it can't since a pre-requisite is KDELIBS-4.3 or greater. The only version that appears to be available is 4.2.4-6. Any idea when kdelibs-4.3 will be released? I realize that KTorrent isn't a huge issue, but still... if you've got an updated package available, you need the prerequisites available too... Just wondering when the new kdelibs pacakage will be released??? 4.3 is in updates-testing atm. It should make in into updates later this week. Atleast that is the plan. Steven = Steven M. Parrish - gpg fingerprint: 4B6C 8357 059E B7ED 8095 0FD6 1F4B EDA0 A9A6 13C0 http://tuxbrewr.fedorapeople.org/ irc.freenode.net: SMParrish @ #fedora-kde, #fedora-devel, #fedora-olpc, #sugar -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Seeking comments on my proposal
On 08/18/2009 11:19 AM, Steven M. Parrish wrote: Got the outline of my proposal here https://fedoraproject.org/wiki/SugarZilla I welcome any comments I dislike the idea of anonymous opening of bugs and anonymous commenting in bugzilla. It's not clear from the proposal if that's a proposed feature or not. Can you clarify if it is and if so, how you'll minimize the problem of: 1) SPAM 2) Bug reports with insufficient information to fix the problem with no point of contact to get additional information. -Toshio I haven't had time to fully check out ABRT but are they requiring the user to have a valid bugzilla account? If I remember the original discussion around ABRT at FUDCon Boston was not to require one. SPAM can be handled through a captcha if needed. As far as not being able to contact the reporter, that is why they have the option of being cc'd to the report. They will be advised when filing the bug that without a point of contact if the developer has questions and cannot contact them that the bug could be closed as insufficient info. There are still some finer points which need to be worked out. Steven = Steven M. Parrish - gpg fingerprint: 4B6C 8357 059E B7ED 8095 0FD6 1F4B EDA0 A9A6 13C0 http://tuxbrewr.fedorapeople.org/ irc.freenode.net: SMParrish @ #fedora-kde, #fedora-devel, #fedora-olpc, #sugar ___ Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
Re: Wan't to join and why
Toshio Kuratomi wrote: On 08/17/2009 03:48 PM, Steven M. Parrish wrote: Hi guys and gals, I am looking to join both the sysadmin-test and sysadmin-cvs groups. Why you might ask? Well I'll tell you. I wan't to get more involved in Fedora. Here is my current Fedora resume... - BugZapper for both KDE and Packagekit. - Maintain 20+ packages and am a Sponsor in the packaging group. - Work closely with the OLPC and Sugar folks at getting and maintaining the packages in Fedora - Responsible for creating builds of F11 with Sugar specifically for the OLPC XO-1 (Hope to get an XO-1.5 soon) see http://wiki.laptop.org/go/F11_for_XO-1 for info on this. What I am looking to do now is create a very simplified bugzilla interface that can be used by OLPC users, mostly children, to report issues with Sugar Activities in Fedora. Will develop in PHP and would like to develop and test it on one of the publictest servers. Also would like to help maintain the cvs servers and projects contained there. Any questions just ask. Is this intended to be deployed onto Fedora Infrastructure boxes eventually or just be developed/demoed on the publictest infrastructure? We haven't had development of known-non-Fedora stuff done previously but this might be a valid first case. If it's intended to run on Fedora Infrastructure, we very much prefer developing them in python. In fact, I don't think we have any non-python developed stuff. -Toshio It is intended to run on Fedora infrastructure. It is going to be an alternate front end to our current bugzilla instance. It could be built upon to create different front ends for other user groups as well. Developing it in Python will not be a problem. I am just in the beginning design stage atm. Steven = Steven M. Parrish - gpg fingerprint: 4B6C 8357 059E B7ED 8095 0FD6 1F4B EDA0 A9A6 13C0 http://tuxbrewr.fedorapeople.org/ irc.freenode.net: SMParrish @ #fedora-kde, #fedora-devel, #fedora-olpc, #sugar ___ Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
Re: Wan't to join and why
Rahul Sundaram wrote: On 08/18/2009 05:51 PM, Steven M. Parrish wrote: What I am looking to do now is create a very simplified bugzilla interface that can be used by OLPC users, mostly children, to report issues with Sugar Activities in Fedora. Will develop in PHP and would like to develop and test it on one of the publictest servers. Also would like to help maintain the cvs servers and projects contained there. Any questions just ask. Is this intended to be deployed onto Fedora Infrastructure boxes eventually or just be developed/demoed on the publictest infrastructure? We haven't had development of known-non-Fedora stuff done previously but this might be a valid first case. If it's intended to run on Fedora Infrastructure, we very much prefer developing them in python. In fact, I don't think we have any non-python developed stuff. -Toshio It is intended to run on Fedora infrastructure. It is going to be an alternate front end to our current bugzilla instance. It could be built upon to create different front ends for other user groups as well. Developing it in Python will not be a problem. I am just in the beginning design stage atm. Very interesting. A related project https://fedoraproject.org/wiki/Bugzilla_Desktop_Client Rahul Sounds like we both have similar goals here. I think having both a OS based app and a simple web interface for our bugreporting is a great idea. Anything that makes it easier for normal users to report issues and give feedback will only lead to making Fedora a more user friendly distro. Steven -- = Steven M. Parrish - gpg fingerprint: 4B6C 8357 059E B7ED 8095 0FD6 1F4B EDA0 A9A6 13C0 http://tuxbrewr.fedorapeople.org/ irc.freenode.net: SMParrish @ #fedora-kde, #fedora-devel, #fedora-olpc, #sugar ___ Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
Re: Wan't to join and why
Paul W. Frields wrote: On Tue, Aug 18, 2009 at 09:15:48AM -0400, Steven M. Parrish wrote: Rahul Sundaram wrote: On 08/18/2009 05:51 PM, Steven M. Parrish wrote: What I am looking to do now is create a very simplified bugzilla interface that can be used by OLPC users, mostly children, to report issues with Sugar Activities in Fedora. Will develop in PHP and would like to develop and test it on one of the publictest servers. Also would like to help maintain the cvs servers and projects contained there. Any questions just ask. Is this intended to be deployed onto Fedora Infrastructure boxes eventually or just be developed/demoed on the publictest infrastructure? We haven't had development of known-non-Fedora stuff done previously but this might be a valid first case. If it's intended to run on Fedora Infrastructure, we very much prefer developing them in python. In fact, I don't think we have any non-python developed stuff. -Toshio It is intended to run on Fedora infrastructure. It is going to be an alternate front end to our current bugzilla instance. It could be built upon to create different front ends for other user groups as well. Developing it in Python will not be a problem. I am just in the beginning design stage atm. Very interesting. A related project https://fedoraproject.org/wiki/Bugzilla_Desktop_Client Rahul Sounds like we both have similar goals here. I think having both a OS based app and a simple web interface for our bugreporting is a great idea. Anything that makes it easier for normal users to report issues and give feedback will only lead to making Fedora a more user friendly distro. I know that there were folks in the Desktop SIG who were interested in a more friendly bug filing Web interface, as well as other possibilities for lowering the fright factor of Bugzilla. Yes its something that was discussed at FudCon in January, but now that Sugar/OLPC is basing itself on Fedora I feel its important to get something going. -- = Steven M. Parrish - gpg fingerprint: 4B6C 8357 059E B7ED 8095 0FD6 1F4B EDA0 A9A6 13C0 http://tuxbrewr.fedorapeople.org/ irc.freenode.net: SMParrish @ #fedora-kde, #fedora-devel, #fedora-olpc, #sugar ___ Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
Seeking comments on my proposal
Got the outline of my proposal here https://fedoraproject.org/wiki/SugarZilla I welcome any comments Steven -- = Steven M. Parrish - gpg fingerprint: 4B6C 8357 059E B7ED 8095 0FD6 1F4B EDA0 A9A6 13C0 http://tuxbrewr.fedorapeople.org/ irc.freenode.net: SMParrish @ #fedora-kde, #fedora-devel, #fedora-olpc, #sugar ___ Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
Re: Seeking comments on my proposal
Mel Chua wrote: Got the outline of my proposal here https://fedoraproject.org/wiki/SugarZilla Nifty. My only comment: How can we make sure that the workflow/interface for SugarZilla is what its intended userbase needs? (It's easy for us to sit here and say yes, that will be better for 8-year-olds, but how do we know that?) Might be a good thing to get a Design team consultation on. --Mel I had planned to get some design folks involved, in fact I will need help in that area. I am shooting for the simplest interface possible that is able to gather the needed info. Steven -- = Steven M. Parrish - gpg fingerprint: 4B6C 8357 059E B7ED 8095 0FD6 1F4B EDA0 A9A6 13C0 http://tuxbrewr.fedorapeople.org/ irc.freenode.net: SMParrish @ #fedora-kde, #fedora-devel, #fedora-olpc, #sugar ___ Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
Wan't to join and why
Hi guys and gals, I am looking to join both the sysadmin-test and sysadmin-cvs groups. Why you might ask? Well I'll tell you. I wan't to get more involved in Fedora. Here is my current Fedora resume... - BugZapper for both KDE and Packagekit. - Maintain 20+ packages and am a Sponsor in the packaging group. - Work closely with the OLPC and Sugar folks at getting and maintaining the packages in Fedora - Responsible for creating builds of F11 with Sugar specifically for the OLPC XO-1 (Hope to get an XO-1.5 soon) see http://wiki.laptop.org/go/F11_for_XO-1 for info on this. What I am looking to do now is create a very simplified bugzilla interface that can be used by OLPC users, mostly children, to report issues with Sugar Activities in Fedora. Will develop in PHP and would like to develop and test it on one of the publictest servers. Also would like to help maintain the cvs servers and projects contained there. Any questions just ask. = Steven M. Parrish - gpg fingerprint: 4B6C 8357 059E B7ED 8095 0FD6 1F4B EDA0 A9A6 13C0 http://tuxbrewr.fedorapeople.org/ irc.freenode.net: SMParrish @ #fedora-kde, #fedora-devel, #fedora-olpc, #sugar ___ Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
Re: [Fedora-livecd-list] No space left on device during image creation
I'm getting this error on my spins for x86_64 KDE live images (not for the i686 ones). Which device is meant here? On my local harddisks should be enough free space. Could this explain why the x86_64 images are ~40 megs bigger than the i686 ones? error: /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora: import read failed(-1). e2fsck 1.41.8 (11-July-2009) Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information F12-KDE-016-x86_: 88827/196608 files (0.1% non-contiguous), 533419/786432 blocks e2image 1.41.8 (11-July-2009) resize2fs 1.41.8 (11-July-2009) /sbin/resize2fs: No space left on device while trying to resize /daten/LIVECD/tmp/imgcreate-Z0Z6zr/tmp-hVegM7/ext3fs.img Please run 'e2fsck -fy /daten/LIVECD/tmp/imgcreate-Z0Z6zr/tmp-hVegM7/ext3fs.img' to fix the filesystem after the aborted resize operation. Resizing the filesystem on /daten/LIVECD/tmp/imgcreate-Z0Z6zr/tmp-hVegM7/ext3fs.img to 532899 (4k) blocks. e2fsck 1.41.8 (11-July-2009) Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information F12-KDE-016-x86_: 88827/196608 files (0.1% non-contiguous), 533419/786432 blocks e2image 1.41.8 (11-July-2009) resize2fs 1.41.8 (11-July-2009) The filesystem is already 786432 blocks long. Nothing to do! Sebastian I was getting this error when building the OLPC releases. Turned out I was running out of space in /var/tmp where it builds the images. I have a small / with all the space in my /home. created at temporary build dir in my $HOME and used the --tmpdir=dirname option when creating the image. Steven = Steven M. Parrish - gpg fingerprint: 4B6C 8357 059E B7ED 8095 0FD6 1F4B EDA0 A9A6 13C0 http://tuxbrewr.fedorapeople.org/ irc.freenode.net: SMParrish @ #fedora-kde, #fedora-devel, #fedora-olpc, #sugar -- Fedora-livecd-list mailing list Fedora-livecd-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-livecd-list
Re: Changing the default 32-bit x86 arch for Fedora 12
On Tuesday 16 June 2009, Steven M. Parrish wrote: The OLPC folks have made a commitment use Fedora as the base for future releases for not only the XO-1.0 but for the new XO-1.5 which is still in development. Does use Fedora as the base mean they'll be using binary packages as is from Fedora, without rebuilding them? Yes with the exception of the kernel OLPC uses stock fedora packages. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Changing the default 32-bit x86 arch for Fedora 12
Way back when in February [1], FESCo decided that for Fedora 11, i586 would be the default architecture, and for Fedora 12, it would be some variant of i686. It's time to follow through on that action item. I've submitted https://fedoraproject.org/wiki/Features/F12X86Support. It defines the default arch as i686 + SSE2. Why? - Faster and more consistent FP math by using SSE2 registers - Allows for autovectorization by GCC where necessary - More clearly delineates our support set of targets, sticking true to forwards innovation, not necessarily legacy support What CPUs do we lose that F11 supports? - Intel i586 (all) - Intel Pentium Pro - Intel Pentium II - Intel Pentium III - 32-bit AMD Athlon - AMD Geode - VIA C3 - Transmeta Crusoe Does this lose the PAE/non-PAE kernel split? - Alas, no. Will a Fedora rebuilt in this manner work on ... - OLPC 1.0? No. - OLPC 1.5? Yes. - Atom? Yes. A seconday arch could be done for these older CPUs, if someone is interested enough. Comments? Flames? Predictions of doom? Bill [1] http://bpepple.fedorapeople.org/fesco/FESCo-2009-02-05.html The OLPC folks have made a commitment use Fedora as the base for future releases for not only the XO-1.0 but for the new XO-1.5 which is still in development. No we go and pull the rug out from under them by saying F12+ will not support the processor on the more than one million already deployed XOs. Also over the past few months much of work has gone into packaging the Sugar Desktop and related activity packages for Fedora. I would instead propose that instead of killing off i586 that instead we make i686+SSE2 a new primary arch. This will allow us to not only optimize Fedora for i686+SSE2 but still maintain a viable arch i586 for not only the XO-1.0 but also for the many older but still usable machines that would otherwise be excluded from using Fedora. Steven -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: KPackageKit fail
We are aware of the kpackagekit issue and are awaiting a release from the upstream developers. It should be released later today and after a bit of testing I will get it into the repo asap. SMP I'm testing Rawhide with latest updates and KPackageKit fails to do updates, I get this error log: http://fpaste.org/paste/13851 It is works for you haven't tested it please do, if it works for you then ignore this message, if not then reply if you need some more feedback from me and I will open a new bug report then. Cheers -- http://kernelreloaded.blog385.com/ linux, blog, anime, spirituality, windsurf, wireless registered as user #367004 with the Linux Counter, http://counter.li.org. ICQ: 2125241, Skype: valent.turkovic -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Maintainer Responsibilities
Hello, I don't want to start a long thread, but just to ask a couple questions for my own clarification. Does a maintainer's responsibilities end with packaging bugs? IOW, if there is a problem in the package that is _broken code_ do they need to do something about it or is it acceptable for them to close the bug and say talk to upstream? Do we want those bugs open to track when the bug is fixed in the distro? I'll accept whatever the answer is, I'm just curious. Thanks, -Steve This is from the official Bugzappers page https://fedoraproject.org/wiki/BugZappers/StockBugzillaResponses#Upstreaming The bug is not a packaging bug, the package maintainer has no plans to work on this in the near future, and there is an upstream bug tracking system other than the Red Hat Bugzilla. Thank you for the bug report. At the moment, the Fedora developers are busy fixing other issues and may not have time to work on this one. The best way to make sure your problem will get looked on is to report it to the authors of the program. Most upstream authors use a bug tracking system like Bugzilla, and more people who know the code will be looking at the bug report there. The upstream bug tracking system to use is: You are requested to add the bugzilla link here for tracking purposes. Please make sure the bug isn't already in the upstream bug tracker before filing it. Maintainers should be free to either fix it locally (time permitting) and upstream the patch or request that the bug be filed at the upstream projects tracker for the upstream developers to resolve it. If it is sent upstream the bug is closed as UPSTREAM and our local report is cross-referenced to the upstream one. That way the maintainer and all interested parties can follow its progress. SMP -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Dumbass KDE 4.2 Compilation Question
On Thursday 05 February 2009 15:58:10 homb...@tips-q.com wrote: I thought that I would compile kde 4.2 in developer mode. That is, the files are installed in the developer directory. Thus I can test KDE 4.2 in advance of installing it to the system. The question is, if I move the installation to the system directories, am I going to break anything? Will an ldconfig repair any damage? I guess that I should have queried before I was more than halfway done; Fire - ready - aim. Thanks -- Neither Lifestyle nor Agenda http://www.tips-Q.com You should follow the instructions here: http://techbase.kde.org/Getting_Started/Build/KDE4 This will install a local copy to can log into from your user account and will leave the system version alone. Steven -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Eclipse not working on F10
I am having an issue with Eclipse failing to start on F10. Here is what I am getting when running from konsole... CompilerOracle: exclude org/eclipse/core/internal/dtree/DataTreeNode.forwardDeltaWith CompilerOracle: exclude org/eclipse/jdt/internal/compiler/lookup/ParameterizedMethodBinding.init CompilerOracle: exclude org/eclipse/cdt/internal/core/dom/parser/cpp/semantics/CPPTemplates.instantiateTemplate CompilerOracle: exclude org/eclipse/cdt/internal/core/pdom/dom/cpp/PDOMCPPLinkage.addBinding CompilerOracle: exclude org/python/pydev/editor/codecompletion/revisited/PythonPathHelper.isValidSourceFile CompilerOracle: exclude org/python/pydev/ui/filetypes/FileTypesPreferencesPage.getDottedValidSourceFiles then it just fails. Any ideas? -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Eclipse not working on F10
On Tuesday 23 December 2008 09:10:48 Andrew Overholt wrote:
* Steven M. Parrish smparr...@shallowcreek.net [2008-12-23 09:06]:
I am having an issue with Eclipse failing to start on F10.
Try running with the -clean option. If that doesn't work, try moving
~/.eclipse out of the way: mv ~/.eclipse{,.bak20081223}; eclipse . If
*that* doesn't work, run with -consolelog -debug and paste the output
into a bug at bugzilla.redhat.com.
Thanks,
Andrew
Thanks Andrew,
Turns out I there was a conflict between me running Eclipse x86_64 and the
default JRE I had installed was 32bit. Removed the 32bit JRE and set the
default to the 64bit one using alternatives --config java.
Now Eclipse is running great!
Steven
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Eclipse not working on F10
On Tuesday 23 December 2008 09:10:48 Andrew Overholt wrote:
* Steven M. Parrish smparr...@shallowcreek.net [2008-12-23 09:06]:
I am having an issue with Eclipse failing to start on F10.
Try running with the -clean option. If that doesn't work, try moving
~/.eclipse out of the way: mv ~/.eclipse{,.bak20081223}; eclipse . If
*that* doesn't work, run with -consolelog -debug and paste the output
into a bug at bugzilla.redhat.com.
Thanks,
Andrew
Thanks for the suggestions. Nothing seemed to work so I created the bug
report.
https://bugzilla.redhat.com/show_bug.cgi?id=477766
Steven
--
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: KDE 4.1 task bar.
On Tuesday 19 August 2008 07:45:57 am Mark Haney wrote: Well I've asked on a couple of other lists, but no luck so I'm hoping someone here knows the answer. I just moved to KDE4 and I want to get the default KDE3.5 task bar behaviour back. In other words I don't want listed on my taskbar every item that's open unless it's open on the desktop I'm currently on. If I move an item to another desktop I want that task bar item to only display on that desktop when I click to it. Anyone know how? -- Libenter homines id quod volunt credunt -- Caius Julius Caesar Mark Haney Sr. Systems Administrator ERC Broadband (828) 350-2415 Call (866) ERC-7110 for after hours support Right click on taskbar -- task manager settings -- then check show only tasks from current desktop. Steven signature.asc Description: This is a digitally signed message part. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
