Re: JBoss in Fedora
Le Jeu 26 novembre 2009 01:21, Ricardo Argüello a écrit : Is there anybody interested in helping port JPackage's JBoss to Fedora 13: https://fedoraproject.org/wiki/JBoss I understand there is an ongoing work to include JBoss AS 5.1 in JPackage.org. Where can we get this SRPMS to begin porting? The bits constituting JBoss are landing one after another in the jpackage cvs. You can go there to check them. It is no easy integration work because JBoss upstream insists on using old versions of several components, when other java apps already depend on newer ones, and because java dependency handling is in the stone age. When this is finished Jpackage-side, I'm sure many people will be interested in importing the result in Fedora. (however if it's done again in fork-and-forget mode with incompatibilities gratuituously introduced Fedora-side and the Fedora maintainer completely absent when users start complaining at the jpp packager that did most of the work Fedora benefited from, I'm sure it won't improve the relationship between the projects) -- Nicolas Mailhot -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: memset bugs.
On Wed, 2009-11-25 at 23:39 -0500, Tom Lane wrote: John Reiser jrei...@bitwagon.com writes: On 11/25/2009 02:03 PM, Dave Jones wrote: A zero sized memset is always a bug. No, memset(,,0) is not always a bug. I think it's reasonably safe to assume that a *literal constant* zero in the third argument is a bug. Whether the header macros can distinguish that from compile-time-constant expressions is an interesting question, but if they can, +1 for throwing an error. I logged some time ago a trivial patch of https://bugzilla.redhat.com/show_bug.cgi?id=532492 which is apparently in rawhide now to generally avoid a warning on memset(foo, 0, 0) C. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: abrt + X Error = zillions of duplicate bug reports?
On 11/25/2009 06:54 PM, Adam Williamson wrote: What do you think of the idea of running the improved duplicate detection logic over existing abrt bug reports in Bugzilla? Would that be feasible, perhaps with some help from the Bugzilla maintainer? Thanks! Many backtraces currently stored in bugzilla are damaged (truncated) by a bug (in Linux kernel?). That bug has been fixed, but the backtraces already uploaded with that bug are not parsable by current backtrace parser. I haven't figured out how to tweak the parser to handle the damaged backtraces yet. However, I'd like to focus on the new duplication detection mechanism for now, because it is more important from my point of view. Karel -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
dracut hanging in F12 under Xen 3.4.2
dracut: Mounted root filesystem /dev/xvda1 dracut: Switching root The machine has 1 vpcu and 512mb ram, disks are 8*500 gb sata drives so shouldn't be any performance issues in the dom0 Endre -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
rawhide report: 20091126 changes
Compose started at Thu Nov 26 08:15:08 UTC 2009 Broken deps for i386 -- anjal-0.1.0-1.fc13.i686 requires libevolution-mail-shared.so.0 anjal-0.1.0-1.fc13.i686 requires libefilterbar.so.0 bind-dyndb-ldap-0.1.0-0.3.a1.fc12.i686 requires libdns.so.50 blacs-mpich2-1.1-33.fc12.i686 requires libmpich.so.1.1 blam-1.8.5-20.fc13.i686 requires gecko-libs = 0:1.9.1.5 cluster-snmp-0.16.1-2.fc12.i686 requires libnetsnmp.so.15 collectd-snmp-4.6.5-1.fc12.i686 requires libnetsnmp.so.15 dnsperf-1.0.1.0-12.fc12.i686 requires libdns.so.50 dnsperf-1.0.1.0-12.fc12.i686 requires libisc.so.50 dnsperf-1.0.1.0-12.fc12.i686 requires libbind9.so.50 dnsperf-1.0.1.0-12.fc12.i686 requires libisccfg.so.50 evolution-exchange-2.28.0-1.fc12.i686 requires libexchange-storage-1.2.so.3 galeon-2.0.7-19.fc13.i686 requires gecko-libs = 0:1.9.1.5 gnome-python2-gtkmozembed-2.25.3-13.fc13.i686 requires gecko-libs = 0:1.9.1.5 gnome-web-photo-0.9-3.fc13.i686 requires gecko-libs = 0:1.9.1.5 grads-1.9b4-28.fc12.i686 requires libnetcdf.so.4 gtranslator-1.9.6-2.fc13.i686 requires libsvn_fs_base-1.so.0 hulahop-0.6.0-2.fc12.i686 requires xulrunner-python hulahop-0.6.0-2.fc12.i686 requires libpyxpcom.so ifstat-1.1-12.fc12.i686 requires libnetsnmp.so.15 inksmoto-0.7.0-1.rc1.fc13.noarch requires /bin/python jaxodraw-latex-2.0.1-3.fc13.noarch requires tex(texmf) kdebase-workspace-python-applet-4.3.75-0.2.svn1048496.fc13.i686 requires PyKDE4 = 0:4.3.75 2:koffice-langpack-wa-2.1.0-2.fc13.noarch requires koffice-langpack = 0:2.1.0-2.fc13 kst-fits-1.8.0-3.fc12.i686 requires cfitsio = 0:3.140 kst-netcdf-1.8.0-3.fc12.i686 requires libnetcdf.so.4 kst-netcdf-1.8.0-3.fc12.i686 requires libnetcdf_c++.so.4 maniadrive-1.2-18.fc12.i686 requires libphp5-5.3.0.so maniadrive-track-editor-1.2-18.fc12.i686 requires libphp5-5.3.0.so monodevelop-debugger-mdb-2.1.0-1.fc12.i686 requires mono(MonoDevelop.Debugger) = 0:2.1.0.0 monodevelop-debugger-mdb-2.1.0-1.fc12.i686 requires mono(MonoDevelop.Core) = 0:2.1.0.0 monodevelop-debugger-mdb-2.1.0-1.fc12.i686 requires mono(MonoDevelop.AspNet) = 0:2.1.0.0 nagios-plugins-snmp-disk-proc-1.2-6.fc12.i686 requires libnetsnmp.so.15 ncview-1.93c-6.fc12.i686 requires libnetcdf.so.4 orsa-lam-0.7.0-11.fc12.i686 requires libmpich.so.1.1 orsa-lam-0.7.0-11.fc12.i686 requires libmpichcxx.so.1.1 orsa-mpich2-0.7.0-11.fc12.i686 requires libmpich.so.1.1 orsa-mpich2-0.7.0-11.fc12.i686 requires libmpichcxx.so.1.1 php-pecl-gmagick-1.0.2b1-3.fc11.i586 requires php(zend-abi) = 0:20060613 php-pecl-gmagick-1.0.2b1-3.fc11.i586 requires php(api) = 0:20041225 rapidsvn-0.10.0-2.fc12.i686 requires libsvn_fs_base-1.so.0 raydium-1.2-18.fc12.i686 requires libphp5-5.3.0.so rubygem-activeldap-1.2.0-3.fc12.noarch requires rubygem(gettext_activerecord) = 0:2.0.4 rubygem-activeldap-1.2.0-3.fc12.noarch requires rubygem(gettext) = 0:2.0.4 rubygem-activeldap-1.2.0-3.fc12.noarch requires rubygem(locale) = 0:2.0.4 scalapack-mpich2-1.7.5-7.fc12.i686 requires libmpich.so.1.1 thunar-vcs-plugin-0.1.2-2.fc13.i686 requires libsvn_fs_base-1.so.0 Broken deps for x86_64 -- anjal-0.1.0-1.fc13.x86_64 requires libevolution-mail-shared.so.0()(64bit) anjal-0.1.0-1.fc13.x86_64 requires libefilterbar.so.0()(64bit) bind-dyndb-ldap-0.1.0-0.3.a1.fc12.x86_64 requires libdns.so.50()(64bit) blacs-mpich2-1.1-33.fc12.x86_64 requires libmpich.so.1.1()(64bit) blam-1.8.5-20.fc13.x86_64 requires gecko-libs = 0:1.9.1.5 cluster-snmp-0.16.1-2.fc12.x86_64 requires libnetsnmp.so.15()(64bit) collectd-snmp-4.6.5-1.fc12.x86_64 requires libnetsnmp.so.15()(64bit) dnsperf-1.0.1.0-12.fc12.x86_64 requires libisc.so.50()(64bit) dnsperf-1.0.1.0-12.fc12.x86_64 requires libisccfg.so.50()(64bit) dnsperf-1.0.1.0-12.fc12.x86_64 requires libbind9.so.50()(64bit) dnsperf-1.0.1.0-12.fc12.x86_64 requires libdns.so.50()(64bit) evolution-exchange-2.28.0-1.fc12.x86_64 requires libexchange-storage-1.2.so.3()(64bit) galeon-2.0.7-19.fc13.x86_64 requires gecko-libs = 0:1.9.1.5 gnome-python2-gtkmozembed-2.25.3-13.fc13.x86_64 requires gecko-libs = 0:1.9.1.5 gnome-web-photo-0.9-3.fc13.x86_64 requires gecko-libs = 0:1.9.1.5 grads-1.9b4-28.fc12.x86_64 requires libnetcdf.so.4()(64bit) gtranslator-1.9.6-2.fc13.x86_64 requires libsvn_fs_base-1.so.0()(64bit) hulahop-0.6.0-2.fc12.x86_64 requires xulrunner-python hulahop-0.6.0-2.fc12.x86_64 requires libpyxpcom.so()(64bit) ifstat-1.1-12.fc12.x86_64
Fedora 12 Graphics Issues: Cancel F13 and concentrate on fixing F12 ?
Ok, controversial title. I have just tried to test install F12 on some of my systems, (5 different ones). All of these bar 1 has problems with the graphics (X11 lockups, system lockups and other problems) mainly in 3D but also in 2D. I still am using F8 on most of my systems as the Graphics systems have not been stable enough for 3D in Fedora since around those times. I know there is a lot of work going on in the graphics front, I myself have worked on and fed back issues as time and ability allow. During F11 I helped with some issues, but unfortunately none of these made it back into updates for F11 and now F12 is out with yet more issues. The Linux kernel is generally relatively stable, as is the main system libraries etc in Fedora. The core issues most people seem to be facing is Graphics and Sound issues. Obviously a major issue with Graphics is the sheer number of different graphics chip sets in use and the lack of documentation for quite a few of them. Due to this it requires a lot of user testing and feedback to get these issues sorted out. Unfortunately the very fast Fedora new release schedule gets in the way of getting this testing done and things do not get fixed prior to a new release which introduces yet another set of problems. The new release speed also uses a lot of developer and user time in just managing to create a new release and updating systems to use it. I know the quick release cycle is one of Fedora's features in its aim to be close to the leading edge, but this has to be balanced with usability otherwise there will be few people actually using it in anger and thus actually testing the software. This could lead to the demise of Fedora. As an idea, at this stage, how about canceling the F13 release and just fixing and updating the F12 release ? This will concentrate developers and users into one system release. Similar to the pre-release test days we could have post-release test days. For example a Graphics test day for F12 where a certain set of tests with a test suite and a set of well known applications could be run. As F12 would be out longer, more people could participate in this. If a commitment, all round, to producing updates fixing the issues in F12 were made, I think more people would be willing to participate as users could expect to see a stable system for their efforts. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Fedora 12 Graphics Issues: Cancel F13 and concentrate on fixing F12 ?
On Thu, Nov 26, 2009 at 02:01:00PM +, Terry Barnaby wrote: another set of problems. The new release speed also uses a lot of developer and user time in just managing to create a new release and updating systems to use it. This is the key flaw in your suggestion. Fedora developer effort isn't as malleable as you seem to think -- managing a new release is very different from fixing graphics bugs, and even if everyone involved in a different aspect of the project _wanted_ to switch to graphics driver programming _and_ was qualified to do so _and_ was able to get up to speed in a reasonable time, you can't necessarily solve programming problems faster by multiplying the number of developers. On the other hand, having a release which emphasizes stability over new features is an idea that's been around for a while. It may be a good idea occasionally, but one of the problems you get is that new development in general doesn't stop and wait for stabilization, so the _next_ release, where you open things up again, ends up extra-unstable as all that new stuff hits at once. -- Matthew Miller mat...@mattdm.org Senior Systems Architect Cyberinfrastructure Labs / Instructional Research Computing Computing Information Technology Harvard School of Engineering Applied Sciences -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Fedora 12 Graphics Issues: Cancel F13 and concentrate on fixing F12 ?
2009/11/26 Terry Barnaby ter...@beam.ltd.uk: Ok, controversial title. I have just tried to test install F12 on some of my systems, (5 different ones). All of these bar 1 has problems with the graphics (X11 lockups, system lockups and other problems) mainly in 3D but also in 2D. I still am using F8 on most of my systems as the Graphics systems have not been stable enough for 3D in Fedora since around those times. which cards exactly did you try? which drivers do you use... and what are the bugzilla bug numbers? As an idea, at this stage, how about canceling the F13 release and just fixing and updating the F12 release ? This will concentrate developers and users into one system release. Similar to the pre-release test days we could have post-release test days. For example a Graphics test day for F12 where a certain set of tests with a test suite and a set of well known applications could be run. As F12 would be out longer, more people could participate in this. i dont see the point because that will definitely lead to new regressions in f12 and annoy other people. interested partys can at any time of the development cycle test the current state of development (aka rawhide) and report and fix bugs in it. my personal experience is: intel (i965) works fine... there are some problems with shaders i have to investigate and there is a problem with interlaced resolutions. even displayport output works (hooked up to a fullhd tv via displayport - hdmi adapter) radeon 4650 works fine... even 3d works to some extent with the experimental dri drivers testing a new mesa build from koji even fixed various issues with 3d games i had left... also some effects/shaders seem to be not properly implemented yet... but hey... it is experimental) nvidia: nouveau kernel mode setting works and 2d experience is alot better already. 2d works in all setups i have personally tested. 3d still requires some progress but i dont see how it helps to stay on one release to get them resolved. kind regards, Rudolf Kastl If a commitment, all round, to producing updates fixing the issues in F12 were made, I think more people would be willing to participate as users could expect to see a stable system for their efforts. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Eddie So is out of the office.
I will be out of the office starting 11/26/2009 and will not return until 12/01/2009.I will check emails in the evening and respond to your message. Please contact Teresia Lai if you need immediate assistance.This message contains information from Equifax Inc. which may be confidential and privileged. If you are not an intended recipient, please refrain from any disclosure, copying, distribution or use of this information and note that such actions are prohibited. If you have received this transmission in error, please notify by e-mail postmas...@equifax.com. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Fedora 12 Graphics Issues: Cancel F13 and concentrate on fixing F12 ?
On 11/26/2009 02:12 PM, Matthew Miller wrote: On Thu, Nov 26, 2009 at 02:01:00PM +, Terry Barnaby wrote: another set of problems. The new release speed also uses a lot of developer and user time in just managing to create a new release and updating systems to use it. This is the key flaw in your suggestion. Fedora developer effort isn't as malleable as you seem to think -- managing a new release is very different from fixing graphics bugs, and even if everyone involved in a different aspect of the project _wanted_ to switch to graphics driver programming _and_ was qualified to do so _and_ was able to get up to speed in a reasonable time, you can't necessarily solve programming problems faster by multiplying the number of developers. That is true, but a major amount of work in getting a release out must be testing it. Those Fedora people involved in the testing, which are also user-testers, have their own systems with there own hardware and are fully conversant with delving into bugs and reporting them in the correct way. On the other hand, having a release which emphasizes stability over new features is an idea that's been around for a while. It may be a good idea occasionally, but one of the problems you get is that new development in general doesn't stop and wait for stabilization, so the _next_ release, where you open things up again, ends up extra-unstable as all that new stuff hits at once. No things don't stop and they shouldn't. But at least it gives a reference platform to assist with future developments and bug fixing and also a stable release that people can recommend. I am unable to recommend F9, F10, F11, or F12 ... -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Fedora 12 Graphics Issues: Cancel F13 and concentrate on fixing F12 ?
On 11/26/2009 07:54 PM, Terry Barnaby wrote: That is true, but a major amount of work in getting a release out must be testing it. Those Fedora people involved in the testing, which are also user-testers, have their own systems with there own hardware and are fully conversant with delving into bugs and reporting them in the correct way. Yes. So let them go ahead and do it. Development can continue in parallel for the next release and that integration testing in the development branch often helps the older branches get more stable when fixes are pushed as updates. Your proposal if it was indeed a serious one doesn't help with anything. Rahul -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: rawhide report: 20091126 changes
Am Donnerstag, den 26.11.2009, 13:13 + schrieb Rawhide Report: Compose started at Thu Nov 26 08:15:08 UTC 2009 Broken deps for i386 -- gtranslator-1.9.6-2.fc13.i686 requires libsvn_fs_base-1.so.0 ... rapidsvn-0.10.0-2.fc12.i686 requires libsvn_fs_base-1.so.0 ... thunar-vcs-plugin-0.1.2-2.fc13.i686 requires libsvn_fs_base-1.so.0 I contacted the subversion maintainer yesterday and Joe replied: The library has disappeared because Berkeley DB support was no longer detected by configure due to a new version being built in dist-f13. I'll get this fixed. So I think it's not necessary to rebuild these packages and wait for a fixed subversion instead. Regards, Christoph -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Fedora 12 Graphics Issues: Cancel F13 and concentrate on fixing F12 ?
On 11/26/2009 02:14 PM, Rudolf Kastl wrote: 2009/11/26 Terry Barnabyter...@beam.ltd.uk: Ok, controversial title. I have just tried to test install F12 on some of my systems, (5 different ones). All of these bar 1 has problems with the graphics (X11 lockups, system lockups and other problems) mainly in 3D but also in 2D. I still am using F8 on most of my systems as the Graphics systems have not been stable enough for 3D in Fedora since around those times. which cards exactly did you try? which drivers do you use... and what are the bugzilla bug numbers? The cards I have tried include: Intel Corporation 82945G/GZ Integrated Graphics Controller ATI Technologies Inc RV535 [Radeon X1650 Series] ATI Technologies Inc M22 [Mobility Radeon X300] ATI Technologies Inc RV280 [Radeon 9200 PRO] (rev 01) VGA compatible controller: Intel Corporation 82G33/G31 Express Integrated Graphics Controller (rev 02) I have not entered any bugzilla numbers as yet. I spent days with F11 and previous releases diagnosing reporting and attempting to fix bugs. No graphics updates were ever made available for F11 and still Fedora cannot run even Blender on most of my machines. At the moment I am not convinced that it is worth spending this time on F12. It seems likely no updates will appear and in F13 the whole ball game may have changed anyway. As an idea, at this stage, how about canceling the F13 release and just fixing and updating the F12 release ? This will concentrate developers and users into one system release. Similar to the pre-release test days we could have post-release test days. For example a Graphics test day for F12 where a certain set of tests with a test suite and a set of well known applications could be run. As F12 would be out longer, more people could participate in this. i dont see the point because that will definitely lead to new regressions in f12 and annoy other people. interested partys can at any time of the development cycle test the current state of development (aka rawhide) and report and fix bugs in it. For testing Graphics you need a lot of testers. I would not have thought that the number of people testing rawhide is enough. I would have thought that real users actually using Fedora are required here. Certainly the F12 release seems to reflect the lack of 3D graphics testing ... my personal experience is: intel (i965) works fine... there are some problems with shaders i have to investigate and there is a problem with interlaced resolutions. even displayport output works (hooked up to a fullhd tv via displayport - hdmi adapter) radeon 4650 works fine... even 3d works to some extent with the experimental dri drivers testing a new mesa build from koji even fixed various issues with 3d games i had left... also some effects/shaders seem to be not properly implemented yet... but hey... it is experimental) nvidia: nouveau kernel mode setting works and 2d experience is alot better already. 2d works in all setups i have personally tested. 3d still requires some progress but i dont see how it helps to stay on one release to get them resolved. Yes, some graphics boards I am sure work well, although 3D should really be working on all cards in 2009 ... But this is the point, there are a lot of different graphics boards, and so a much wider scope for the testing is required here which requires more users over more time with many different applications using basically the same software. kind regards, Rudolf Kastl If a commitment, all round, to producing updates fixing the issues in F12 were made, I think more people would be willing to participate as users could expect to see a stable system for their efforts. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Fedora 12 Graphics Issues: Cancel F13 and concentrate on fixing F12 ?
On 11/26/2009 08:09 PM, Terry Barnaby wrote: I have not entered any bugzilla numbers as yet. I spent days with F11 and previous releases diagnosing reporting and attempting to fix bugs. No graphics updates were ever made available for F11 and still Fedora cannot run even Blender on most of my machines. At the moment I am not convinced that it is worth spending this time on F12. It seems likely no updates will appear and in F13 the whole ball game may have changed anyway. Seems a bunch of incorrect assumptions considering that Fedora 11 did get many updates and I already see updates for Fedora 12 in updates-testing repository. Specific bug reports are definitely going to help. Rahul -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Fedora 12 Graphics Issues: Cancel F13 and concentrate on fixing F12 ?
On Thu, 2009-11-26 at 14:01 +, Terry Barnaby wrote: Ok, controversial title. I have just tried to test install F12 on some of my systems, (5 different ones). All of these bar 1 has problems with the graphics (X11 lockups, system lockups and other problems) mainly in 3D but also in 2D. I still am using F8 on most of my systems as the Graphics systems have not been stable enough for 3D in Fedora since around those times. I know there is a lot of work going on in the graphics front, I myself have worked on and fed back issues as time and ability allow. During F11 I helped with some issues, but unfortunately none of these made it back into updates for F11 and now F12 is out with yet more issues. The Linux kernel is generally relatively stable, as is the main system libraries etc in Fedora. The core issues most people seem to be facing is Graphics and Sound issues. Obviously a major issue with Graphics is the sheer number of different graphics chip sets in use and the lack of documentation for quite a few of them. Due to this it requires a lot of user testing and feedback to get these issues sorted out. Unfortunately the very fast Fedora new release schedule gets in the way of getting this testing done and things do not get fixed prior to a new release which introduces yet another set of problems. The new release speed also uses a lot of developer and user time in just managing to create a new release and updating systems to use it. I know the quick release cycle is one of Fedora's features in its aim to be close to the leading edge, but this has to be balanced with usability otherwise there will be few people actually using it in anger and thus actually testing the software. This could lead to the demise of Fedora. As an idea, at this stage, how about canceling the F13 release and just fixing and updating the F12 release ? This will concentrate developers and users into one system release. Similar to the pre-release test days we could have post-release test days. For example a Graphics test day for F12 where a certain set of tests with a test suite and a set of well known applications could be run. As F12 would be out longer, more people could participate in this. If a commitment, all round, to producing updates fixing the issues in F12 were made, I think more people would be willing to participate as users could expect to see a stable system for their efforts. +1 on this. I have 4 bugs entered into bugzilla related to display problems and none of them get any attention. I even posted a warning to the group about this matter. (See November 16, Warning about possible display issues with F12 upgrade.) For KDE users, this situation has been building for a while. Back in F9 the Folderview widget didn't work correctly with some nvidia cards, supposedly because of issues in the proprietary nvidia driver. The developer's response to this: tough luck for using a proprietary driver. Now that the open source nvidia driver is out they say to use it. The problem with nouveau is that it has just as many or more problems than the proprietary driver, albeit in different areas. I am not buying that all of the display problems are caused by the proprietary driver. And if they are, why do these bugs get closed ? They should be forwarded to nvidia for work. Aside: I know, the bug reporter should forward them to nvidia. But then why even report a bug to the Redhat bugzilla ? EVERYTHING is upstream to them ! And the problem with reporting the bug (non proprietary nvidia) upstream is that they say that we aren't running the general release of the component, we are running the Fedora version and thus Fedora should fix it. I am VERY frustrated with the state of the display components right now. I am quite frustrated with how display component bugs are handled by the Fedora developers. I think some things need to change. I'm holding back from upgrading to F12 until I hear that some of these issues are resolved. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Fedora 12 Graphics Issues: Cancel F13 and concentrate on fixing F12 ?
On 2009/11/26 14:39 (GMT) Terry Barnaby composed: ... The cards I have tried include: Intel Corporation 82945G/GZ Integrated Graphics Controller ATI Technologies Inc RV535 [Radeon X1650 Series] ATI Technologies Inc M22 [Mobility Radeon X300] ATI Technologies Inc RV280 [Radeon 9200 PRO] (rev 01) VGA compatible controller: Intel Corporation 82G33/G31 Express Integrated Graphics Controller (rev 02) ... For testing Graphics you need a lot of testers. I would not have thought that the number of people testing rawhide is enough. I would have thought that real users actually using Fedora are required here. Certainly the F12 release seems to reflect the lack of 3D graphics testing ... ... Yes, some graphics boards I am sure work well, although 3D should really be working on all cards in 2009 ... But this is the point, there are a lot of different graphics boards, and so a much wider scope for the testing is required here which requires more users over more time with many different applications using basically the same software. Surely fewer testers find 3D to be relevant to getting their work done. I for one always disable that bling as soon as I see it sneak in past a change in configuration methodology. I tried an F12 install on rv200 Radeon 36 hours ago, and Anaconda refused to even come up in GUI mode. -- The husband should fulfill his marital duty to his wife, and likewise the wife to her husband. 1 Corinthians 7:3 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://fm.no-ip.com/ -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Fedora 12 Graphics Issues: Cancel F13 and concentrate on fixing F12 ?
On 11/26/2009 02:43 PM, Rahul Sundaram wrote: On 11/26/2009 08:09 PM, Terry Barnaby wrote: I have not entered any bugzilla numbers as yet. I spent days with F11 and previous releases diagnosing reporting and attempting to fix bugs. No graphics updates were ever made available for F11 and still Fedora cannot run even Blender on most of my machines. At the moment I am not convinced that it is worth spending this time on F12. It seems likely no updates will appear and in F13 the whole ball game may have changed anyway. Seems a bunch of incorrect assumptions considering that Fedora 11 did get many updates and I already see updates for Fedora 12 in updates-testing repository. Specific bug reports are definitely going to help. Rahul Sorry, should have been more specific. On the graphics package front, there have been no ATI or Intel X11 driver updates in F11 so far. Mesa was last updated 14th of June. Not sure about DRM as that is in the kernel and may have been updated with kernel updates. Yes, clear bug reports are needed but they also need the follow through to a fix and updated packages. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Fedora 12 Graphics Issues: Cancel F13 and concentrate on fixing F12 ?
On Thu, 2009-11-26 at 20:13 +0530, Rahul Sundaram wrote: Specific bug reports are definitely going to help. Here are 4 to start with: 1) Cronometer crashes KDE session. https://bugzilla.redhat.com/show_bug.cgi?id=504173 2) Display not operating properly https://bugzilla.redhat.com/show_bug.cgi?id=528188 Notice that this uses nouveau and it was reported back in rawhide. 3) Blank screen on login https://bugzilla.redhat.com/show_bug.cgi?id=525767 4) KDE session display gets messed up on Gateway LT3108u https://bugzilla.redhat.com/show_bug.cgi?id=525767 -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Fedora 12 Graphics Issues: Cancel F13 and concentrate on fixing F12 ?
On 11/26/2009 08:34 PM, Terry Barnaby wrote: Yes, clear bug reports are needed but they also need the follow through to a fix and updated packages. Agreed. File specific bug reports and post the links here. Rahul -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Fedora 12 Graphics Issues: Cancel F13 and concentrate on fixing F12 ?
On Thu, Nov 26, 2009 at 03:04:43PM +, Terry Barnaby wrote: On 11/26/2009 02:43 PM, Rahul Sundaram wrote: On 11/26/2009 08:09 PM, Terry Barnaby wrote: I have not entered any bugzilla numbers as yet. I spent days with F11 and previous releases diagnosing reporting and attempting to fix bugs. No graphics updates were ever made available for F11 and still Fedora cannot run even Blender on most of my machines. At the moment I am not convinced that it is worth spending this time on F12. It seems likely no updates will appear and in F13 the whole ball game may have changed anyway. Seems a bunch of incorrect assumptions considering that Fedora 11 did get many updates and I already see updates for Fedora 12 in updates-testing repository. Specific bug reports are definitely going to help. Rahul Sorry, should have been more specific. On the graphics package front, there have been no ATI or Intel X11 driver updates in F11 so far. Mesa was last updated 14th of June. Not sure about DRM as that is in the kernel and may have been updated with kernel updates. xorg-x11-drv-intel-2.7.0-9.fc11 ajax2009-11-20 20:35:24 xorg-x11-drv-intel-2.7.0-8.fc11 mjg59 2009-09-24 20:58:55 xorg-x11-drv-intel-2.7.0-7.fc11 krh 2009-05-28 19:32:16 xorg-x11-drv-ati-6.12.2-18.fc11 airlied 2009-06-29 02:40:01 And from kernel changelogs: * Fri Sep 25 2009 Chuck Ebbert cebb...@redhat.com 2.6.30.8-63 - Disable the GEM graphics manager on i686 PAE kernels (fixes modesetting on Intel graphics.) * Fri Aug 14 2009 Chuck Ebbert cebb...@redhat.com 2.6.30.5-28.rc2 - Linux 2.6.30.5-rc2 - Dropped drm-intel-tv-fix.patch, merged in -stable now. Wed Aug 12 2009 Kyle McMartin k...@redhat.com - DRM patch sync-up with F-11-2.6.29.y, ABI probably isn't right yet though... - drm-modesetting-radeon.patch - drm-nouveau.patch - drm-no-gem-on-i8xx.patch - drm-i915-resume-force-mode.patch - drm-intel-big-hammer.patch - drm-intel-gen3-fb-hack.patch - drm-intel-hdmi-edid-fix.patch - drm-modesetting-radeon-fixes.patch - drm-radeon-new-pciids.patch - drm-dont-frob-i2c.patch - drm-intel-tv-fix.patch - drm-radeon-cs-oops-fix.patch - drm-pnp-add-resource-range-checker.patch - drm-i915-enable-mchbar.patch - The rest were merged upstream. Anyway, I understand you sentiment. I was bitten by Intel graphics bug (EQ overflowing) which wasn't fixed for all F11 life. Things are much better in F12 now. But still, without any bug number we have nothing to talk about. -- Tomasz TorczThere exists no separation between gods and men: xmpp: zdzich...@chrome.pl one blends softly casual into the other. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Fedora 12 Graphics Issues: Cancel F13 and concentrate on fixing F12 ?
On 11/26/2009 08:38 PM, Linuxguy123 wrote: On Thu, 2009-11-26 at 20:13 +0530, Rahul Sundaram wrote: Specific bug reports are definitely going to help. Here are 4 to start with: 1) Cronometer crashes KDE session. https://bugzilla.redhat.com/show_bug.cgi?id=504173 Filed against wrong component. How is Fedora marketing related to a KDE issue? Please reassign. 2) Display not operating properly https://bugzilla.redhat.com/show_bug.cgi?id=528188 Waiting on information from you. Notice that this uses nouveau and it was reported back in rawhide. 3) Blank screen on login https://bugzilla.redhat.com/show_bug.cgi?id=525767 Likewise. 4) KDE session display gets messed up on Gateway LT3108u https://bugzilla.redhat.com/show_bug.cgi?id=525767 Likewise. Rahul -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Fedora 12 Graphics Issues: Cancel F13 and concentrate on fixing F12 ?
On 11/26/2009 03:11 PM, Tomasz Torcz wrote: On Thu, Nov 26, 2009 at 03:04:43PM +, Terry Barnaby wrote: On 11/26/2009 02:43 PM, Rahul Sundaram wrote: On 11/26/2009 08:09 PM, Terry Barnaby wrote: I have not entered any bugzilla numbers as yet. I spent days with F11 and previous releases diagnosing reporting and attempting to fix bugs. No graphics updates were ever made available for F11 and still Fedora cannot run even Blender on most of my machines. At the moment I am not convinced that it is worth spending this time on F12. It seems likely no updates will appear and in F13 the whole ball game may have changed anyway. Seems a bunch of incorrect assumptions considering that Fedora 11 did get many updates and I already see updates for Fedora 12 in updates-testing repository. Specific bug reports are definitely going to help. Rahul Sorry, should have been more specific. On the graphics package front, there have been no ATI or Intel X11 driver updates in F11 so far. Mesa was last updated 14th of June. Not sure about DRM as that is in the kernel and may have been updated with kernel updates. xorg-x11-drv-intel-2.7.0-9.fc11 ajax2009-11-20 20:35:24 xorg-x11-drv-intel-2.7.0-8.fc11 mjg59 2009-09-24 20:58:55 xorg-x11-drv-intel-2.7.0-7.fc11 krh 2009-05-28 19:32:16 xorg-x11-drv-ati-6.12.2-18.fc11 airlied 2009-06-29 02:40:01 And from kernel changelogs: * Fri Sep 25 2009 Chuck Ebbertcebb...@redhat.com 2.6.30.8-63 - Disable the GEM graphics manager on i686 PAE kernels (fixes modesetting on Intel graphics.) * Fri Aug 14 2009 Chuck Ebbertcebb...@redhat.com 2.6.30.5-28.rc2 - Linux 2.6.30.5-rc2 - Dropped drm-intel-tv-fix.patch, merged in -stable now. Wed Aug 12 2009 Kyle McMartink...@redhat.com - DRM patch sync-up with F-11-2.6.29.y, ABI probably isn't right yet though... - drm-modesetting-radeon.patch - drm-nouveau.patch - drm-no-gem-on-i8xx.patch - drm-i915-resume-force-mode.patch - drm-intel-big-hammer.patch - drm-intel-gen3-fb-hack.patch - drm-intel-hdmi-edid-fix.patch - drm-modesetting-radeon-fixes.patch - drm-radeon-new-pciids.patch - drm-dont-frob-i2c.patch - drm-intel-tv-fix.patch - drm-radeon-cs-oops-fix.patch - drm-pnp-add-resource-range-checker.patch - drm-i915-enable-mchbar.patch - The rest were merged upstream. Anyway, I understand you sentiment. I was bitten by Intel graphics bug (EQ overflowing) which wasn't fixed for all F11 life. Things are much better in F12 now. But still, without any bug number we have nothing to talk about. Mind you the above xorg packages are not in F11 updates ... I note that there is a package in fedora-testing for xorg-x11-drv-intel but I can't see anything for xorg-x11-drv-ati is this somewhere else ? For me F12 seems worse than F11, so far on this aspect. I'm sure others mileage will vary in the same manner as the number of different graphics boards :) As you obviously know tracking down and reporting bugs like these do take a lot of time and effort, quite often more than actually fixing them. At the moment with the frequency of Fedora releases and the lack of a push to testing and stability on this front I am not enthused, at the moment, with doing this and I suspect many others feel the same. Cheers Terry -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Fedora 12 Graphics Issues: Cancel F13 and concentrate on fixing F12 ?
On Thu, Nov 26, 2009 at 04:08:27PM +, Terry Barnaby wrote: As you obviously know tracking down and reporting bugs like these do take a lot of time and effort, quite often more than actually fixing them. At the moment with the frequency of Fedora releases and the lack of a push to testing and stability on this front I am not enthused, at the moment, with doing this and I suspect many others feel the same. I'm confused. You want Fedora to skip a release to focus on testing and fixing, and you have no plans to help and aren't enthusiastic about actually participating in the testing and fixing? josh -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Fedora 12 Graphics Issues: Cancel F13 and concentrate on fixing F12 ?
On Nov 26, 2009, at 6:01, Terry Barnaby ter...@beam.ltd.uk wrote: Ok, controversial title. I have just tried to test install F12 on some of my systems, (5 different ones). All of these bar 1 has problems with the graphics (X11 lockups, system lockups and other problems) mainly in 3D but also in 2D. I still am using F8 on most of my systems as the Graphics systems have not been stable enough for 3D in Fedora since around those times. I know there is a lot of work going on in the graphics front, I myself have worked on and fed back issues as time and ability allow. During F11 I helped with some issues, but unfortunately none of these made it back into updates for F11 and now F12 is out with yet more issues. The Linux kernel is generally relatively stable, as is the main system libraries etc in Fedora. The core issues most people seem to be facing is Graphics and Sound issues. Obviously a major issue with Graphics is the sheer number of different graphics chip sets in use and the lack of documentation for quite a few of them. Due to this it requires a lot of user testing and feedback to get these issues sorted out. Unfortunately the very fast Fedora new release schedule gets in the way of getting this testing done and things do not get fixed prior to a new release which introduces yet another set of problems. The new release speed also uses a lot of developer and user time in just managing to create a new release and updating systems to use it. I know the quick release cycle is one of Fedora's features in its aim to be close to the leading edge, but this has to be balanced with usability otherwise there will be few people actually using it in anger and thus actually testing the software. This could lead to the demise of Fedora. As an idea, at this stage, how about canceling the F13 release and just fixing and updating the F12 release ? This will concentrate developers and users into one system release. Similar to the pre- release test days we could have post-release test days. For example a Graphics test day for F12 where a certain set of tests with a test suite and a set of well known applications could be run. As F12 would be out longer, more people could participate in this. If a commitment, all round, to producing updates fixing the issues in F12 were made, I think more people would be willing to participate as users could expect to see a stable system for their efforts. You make the assumption that if fedora stopped, s -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Fedora 12 Graphics Issues: Cancel F13 and concentrate on fixing F12 ?
On Nov 26, 2009, at 6:01, Terry Barnaby ter...@beam.ltd.uk wrote: Ok, controversial title. I have just tried to test install F12 on some of my systems, (5 different ones). All of these bar 1 has problems with the graphics (X11 lockups, system lockups and other problems) mainly in 3D but also in 2D. I still am using F8 on most of my systems as the Graphics systems have not been stable enough for 3D in Fedora since around those times. I know there is a lot of work going on in the graphics front, I myself have worked on and fed back issues as time and ability allow. During F11 I helped with some issues, but unfortunately none of these made it back into updates for F11 and now F12 is out with yet more issues. The Linux kernel is generally relatively stable, as is the main system libraries etc in Fedora. The core issues most people seem to be facing is Graphics and Sound issues. Obviously a major issue with Graphics is the sheer number of different graphics chip sets in use and the lack of documentation for quite a few of them. Due to this it requires a lot of user testing and feedback to get these issues sorted out. Unfortunately the very fast Fedora new release schedule gets in the way of getting this testing done and things do not get fixed prior to a new release which introduces yet another set of problems. The new release speed also uses a lot of developer and user time in just managing to create a new release and updating systems to use it. I know the quick release cycle is one of Fedora's features in its aim to be close to the leading edge, but this has to be balanced with usability otherwise there will be few people actually using it in anger and thus actually testing the software. This could lead to the demise of Fedora. As an idea, at this stage, how about canceling the F13 release and just fixing and updating the F12 release ? This will concentrate developers and users into one system release. Similar to the pre- release test days we could have post-release test days. For example a Graphics test day for F12 where a certain set of tests with a test suite and a set of well known applications could be run. As F12 would be out longer, more people could participate in this. If a commitment, all round, to producing updates fixing the issues in F12 were made, I think more people would be willing to participate as users could expect to see a stable system for their efforts. You make the assumption that if fedora stopped, so would upstream. You also state that the kernel is stable, yet most of the graphics work is going on at the kernel level so we have to continue to bring in new kernels to pick up these changes. Graphics work is not a fedora issue alone. It is an upstream issue first and formost. By abandoning upstream and trying to stagnate will ultimatly damage upstreams ability to gennew changes tested and released. -- Jes -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Fedora 12 Graphics Issues: Cancel F13 and concentrate on fixing F12 ?
On 11/26/2009 04:34 PM, Josh Boyer wrote: On Thu, Nov 26, 2009 at 04:08:27PM +, Terry Barnaby wrote: As you obviously know tracking down and reporting bugs like these do take a lot of time and effort, quite often more than actually fixing them. At the moment with the frequency of Fedora releases and the lack of a push to testing and stability on this front I am not enthused, at the moment, with doing this and I suspect many others feel the same. I'm confused. You want Fedora to skip a release to focus on testing and fixing, and you have no plans to help and aren't enthusiastic about actually participating in the testing and fixing? josh I really want to help and get a stable release and present bug reports and even fix them if I can. But, the current short term release schedule, and no focus on testing and fixing graphics issues, does not inspire me with confidence that a stable usable release will emerge. This makes it difficult for me to justify the effort. Convince me :) -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: abrt + X Error = zillions of duplicate bug reports?
On Thu, 2009-11-26 at 11:32 +0100, Karel Klic wrote: On 11/25/2009 06:54 PM, Adam Williamson wrote: What do you think of the idea of running the improved duplicate detection logic over existing abrt bug reports in Bugzilla? Would that be feasible, perhaps with some help from the Bugzilla maintainer? Thanks! Many backtraces currently stored in bugzilla are damaged (truncated) by a bug (in Linux kernel?). That bug has been fixed, but the backtraces already uploaded with that bug are not parsable by current backtrace parser. I haven't figured out how to tweak the parser to handle the damaged backtraces yet. However, I'd like to focus on the new duplication detection mechanism for now, because it is more important from my point of view. Sure, I agree that would take priority for now. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org http://www.happyassassin.net -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Fedora 12 Graphics Issues: Cancel F13 and concentrate on fixing F12 ?
On 11/26/2009 05:05 PM, Jesse Keating wrote: On Nov 26, 2009, at 6:01, Terry Barnaby ter...@beam.ltd.uk wrote: Ok, controversial title. I have just tried to test install F12 on some of my systems, (5 different ones). All of these bar 1 has problems with the graphics (X11 lockups, system lockups and other problems) mainly in 3D but also in 2D. I still am using F8 on most of my systems as the Graphics systems have not been stable enough for 3D in Fedora since around those times. I know there is a lot of work going on in the graphics front, I myself have worked on and fed back issues as time and ability allow. During F11 I helped with some issues, but unfortunately none of these made it back into updates for F11 and now F12 is out with yet more issues. The Linux kernel is generally relatively stable, as is the main system libraries etc in Fedora. The core issues most people seem to be facing is Graphics and Sound issues. Obviously a major issue with Graphics is the sheer number of different graphics chip sets in use and the lack of documentation for quite a few of them. Due to this it requires a lot of user testing and feedback to get these issues sorted out. Unfortunately the very fast Fedora new release schedule gets in the way of getting this testing done and things do not get fixed prior to a new release which introduces yet another set of problems. The new release speed also uses a lot of developer and user time in just managing to create a new release and updating systems to use it. I know the quick release cycle is one of Fedora's features in its aim to be close to the leading edge, but this has to be balanced with usability otherwise there will be few people actually using it in anger and thus actually testing the software. This could lead to the demise of Fedora. As an idea, at this stage, how about canceling the F13 release and just fixing and updating the F12 release ? This will concentrate developers and users into one system release. Similar to the pre-release test days we could have post-release test days. For example a Graphics test day for F12 where a certain set of tests with a test suite and a set of well known applications could be run. As F12 would be out longer, more people could participate in this. If a commitment, all round, to producing updates fixing the issues in F12 were made, I think more people would be willing to participate as users could expect to see a stable system for their efforts. You make the assumption that if fedora stopped, so would upstream. You also state that the kernel is stable, yet most of the graphics work is going on at the kernel level so we have to continue to bring in new kernels to pick up these changes. Graphics work is not a fedora issue alone. It is an upstream issue first and formost. By abandoning upstream and trying to stagnate will ultimatly damage upstreams ability to gennew changes tested and released. -- Jes I'm not suggesting F12 should not be updated, in fact the opposite. As you state most of the Graphics work is being done up-stream, but it is the distributions role to package, release and allow users to test this and feed back bugs. I am saying that a focus on Graphics with a quick update cycle will help upstream get the testing they need and the users to get fixes. Actually a question on the Mesa packages, these are packaged as version 7.6-0.13 in F12. It seems however, that this is packaged from Mesa's 7.7-devel tree. I think the mesa developers have branched 7.6 as a stable branch and moved new development to 7.7. Shouldn't F12's Mesa packages have a 7.7 version number ?? -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Fedora 12 Graphics Issues: Cancel F13 and concentrate on fixing F12 ?
On Nov 26, 2009, at 9:27, Terry Barnaby ter...@beam.ltd.uk wrote: On 11/26/2009 05:05 PM, Jesse Keating wrote: On Nov 26, 2009, at 6:01, Terry Barnaby ter...@beam.ltd.uk wrote: Ok, controversial title. I have just tried to test install F12 on some of my systems, (5 different ones). All of these bar 1 has problems with the graphics (X11 lockups, system lockups and other problems) mainly in 3D but also in 2D. I still am using F8 on most of my systems as the Graphics systems have not been stable enough for 3D in Fedora since around those times. I know there is a lot of work going on in the graphics front, I myself have worked on and fed back issues as time and ability allow. During F11 I helped with some issues, but unfortunately none of these made it back into updates for F11 and now F12 is out with yet more issues. The Linux kernel is generally relatively stable, as is the main system libraries etc in Fedora. The core issues most people seem to be facing is Graphics and Sound issues. Obviously a major issue with Graphics is the sheer number of different graphics chip sets in use and the lack of documentation for quite a few of them. Due to this it requires a lot of user testing and feedback to get these issues sorted out. Unfortunately the very fast Fedora new release schedule gets in the way of getting this testing done and things do not get fixed prior to a new release which introduces yet another set of problems. The new release speed also uses a lot of developer and user time in just managing to create a new release and updating systems to use it. I know the quick release cycle is one of Fedora's features in its aim to be close to the leading edge, but this has to be balanced with usability otherwise there will be few people actually using it in anger and thus actually testing the software. This could lead to the demise of Fedora. As an idea, at this stage, how about canceling the F13 release and just fixing and updating the F12 release ? This will concentrate developers and users into one system release. Similar to the pre-release test days we could have post-release test days. For example a Graphics test day for F12 where a certain set of tests with a test suite and a set of well known applications could be run. As F12 would be out longer, more people could participate in this. If a commitment, all round, to producing updates fixing the issues in F12 were made, I think more people would be willing to participate as users could expect to see a stable system for their efforts. You make the assumption that if fedora stopped, so would upstream. You also state that the kernel is stable, yet most of the graphics work is going on at the kernel level so we have to continue to bring in new kernels to pick up these changes. Graphics work is not a fedora issue alone. It is an upstream issue first and formost. By abandoning upstream and trying to stagnate will ultimatly damage upstreams ability to gennew changes tested and released. -- Jes I'm not suggesting F12 should not be updated, in fact the opposite. As you state most of the Graphics work is being done up-stream, but it is the distributions role to package, release and allow users to test this and feed back bugs. I am saying that a focus on Graphics with a quick update cycle will help upstream get the testing they need and the users to get fixes. This is what rawhide is for. Rapid updates with fast feedback and upstream snapshots. It is not the role of a stable release to be grabbing upstream new stuff and throwing it at users without abandon. -- Jes -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Fedora 12 Graphics Issues: Cancel F13 and concentrate on fixing F12 ?
Linuxguy123 wrote: I have 4 bugs entered into bugzilla related to display problems and none of them get any attention. I even posted a warning to the group about this matter. (See November 16, Warning about possible display issues with F12 upgrade.) If these are the ones you linked to earlier, from Rahul's reply, they're waiting on you for these. Haven't checked myself, so maybe the status has changed or these aren't your bugs. For KDE users, this situation has been building for a while. Back in F9 the Folderview widget didn't work correctly with some nvidia cards, supposedly because of issues in the proprietary nvidia driver. The developer's response to this: tough luck for using a proprietary driver. Now that the open source nvidia driver is out they say to use it. The problem with nouveau is that it has just as many or more problems than the proprietary driver, albeit in different areas. Nouveau is the nicest driver I've used when it comes to stability. The only places I've encountered issues are with 3d because it's not supported fully so that's more of a missing feature than a bug and coming back from sleep with some artifacts that disappear when the screen is unlocked. The blob driver gets many more issues than nouveau and I can't imagine going back on any install I use day to day. I am not buying that all of the display problems are caused by the proprietary driver. And if they are, why do these bugs get closed ? They should be forwarded to nvidia for work. A lot are. And *you* should forward them. All we can do is say there's a problem with your driver that X had, go talk to this guy for details. Since I don't run the driver, I can't even attempt to reproduce any issues that you have other than well, works with nouveau. We'd be wasting time shuttling messages back and forth. Aside: I know, the bug reporter should forward them to nvidia. But then why even report a bug to the Redhat bugzilla ? EVERYTHING is upstream to them ! Well, we can at least track it and know when it's fixed to get any related fixes included sooner. Also, we can see if it's truly our problem or not. And the problem with reporting the bug (non proprietary nvidia) upstream is that they say that we aren't running the general release of the component, we are running the Fedora version and thus Fedora should fix it. If they give us some source code to work on, we could. As it stands, we can't do *anything* if it doesn't work with their driver and it works with others. As for forwarding bugs upstream, you know what went wrong better than we do. makes no sense for us to play a middleman in communication. I am VERY frustrated with the state of the display components right now. I am quite frustrated with how display component bugs are handled by the Fedora developers. I think some things need to change. For nvidia stuff, what are we to do? I don't (as do many other developers) know much about X and the driver inner workings and if I do get started with it, poking the black box that nvidia ships is surely the last thing I ever want to do with it. --Ben -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Fedora 12 Graphics Issues: Cancel F13 and concentrate on fixing F12 ?
On Thu, Nov 26, 2009 at 17:09:14 +, Terry Barnaby ter...@beam.ltd.uk wrote: I really want to help and get a stable release and present bug reports and even fix them if I can. But, the current short term release schedule, and no focus on testing and fixing graphics issues, does not inspire me with confidence that a stable usable release will emerge. This makes it difficult for me to justify the effort. Convince me :) I follow the radeon updates pretty closely and my 9200 finally starting working with 3d again a few weeks before the release. Airlie has continued development in the f12 branch and there have been several updates over the last couple of weeks. If you have just tried F11 and not F12 you should consider doing so. For r5xx and below, grab a live image and install one of the smaller 3d apps and try it out. For r6xx and above you'll want to install mesa-experimental-drivers and update xorg-x11-drv-ati. This won't get you the kernel updates related to graphics since the release, but should give you a good look at where things are at so that you can decide if you want install F12 on the machine. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Fedora 12 Graphics Issues: Cancel F13 and concentrate on fixing F12 ?
On Thu, Nov 26, 2009 at 13:46:54 -0600, Bruno Wolff III br...@wolff.to wrote: mesa-experimental-drivers and update xorg-x11-drv-ati. This won't get you That should be: mesa-dri-drivers-experimental -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Fedora 12 Graphics Issues: Cancel F13 and concentrate on fixing F12 ?
On 11/26/2009 07:46 PM, Bruno Wolff III wrote: On Thu, Nov 26, 2009 at 17:09:14 +, Terry Barnabyter...@beam.ltd.uk wrote: I really want to help and get a stable release and present bug reports and even fix them if I can. But, the current short term release schedule, and no focus on testing and fixing graphics issues, does not inspire me with confidence that a stable usable release will emerge. This makes it difficult for me to justify the effort. Convince me :) I follow the radeon updates pretty closely and my 9200 finally starting working with 3d again a few weeks before the release. Airlie has continued development in the f12 branch and there have been several updates over the last couple of weeks. If you have just tried F11 and not F12 you should consider doing so. For r5xx and below, grab a live image and install one of the smaller 3d apps and try it out. For r6xx and above you'll want to install mesa-experimental-drivers and update xorg-x11-drv-ati. This won't get you the kernel updates related to graphics since the release, but should give you a good look at where things are at so that you can decide if you want install F12 on the machine. Hi, I have tried out F12 on 4 different systems, 2 with different ATI graphics and two with different Intel based boards. Only the last one appears to be able to run Blender. You mention Airlie has continued development in the f12 branch. If that means there are people working on the bugs and producing new driver updates for F12 (DRM,MESA,X11), especially for ATI then I certainly will give it some time. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Fedora 12 Graphics Issues: Cancel F13 and concentrate on fixing F12 ?
Dne Thu, 26 Nov 2009 13:46:54 -0600 Bruno Wolff III napsal(a): On Thu, Nov 26, 2009 at 17:09:14 +, Terry Barnaby ter...@beam.ltd.uk wrote: I really want to help and get a stable release and present bug reports and even fix them if I can. But, the current short term release schedule, and no focus on testing and fixing graphics issues, does not inspire me with confidence that a stable usable release will emerge. This makes it difficult for me to justify the effort. Convince me :) I follow the radeon updates pretty closely and my 9200 finally starting working with 3d again a few weeks before the release. Airlie has continued development in the f12 branch and there have been several updates over the last couple of weeks. +1 The ATI graphics in my laptop works in F12 better than ever before. Thanks to Dave Airlie and other developers. The activity of the QA team has also been more visible recently. So I disagree with Terry about the lack of focus on testing and fixing graphics issues. Michal -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Fedora 12 Graphics Issues: Cancel F13 and concentrate on fixing F12 ?
On Thu, Nov 26, 2009 at 20:16:54 +, Terry Barnaby ter...@beam.ltd.uk wrote: I have tried out F12 on 4 different systems, 2 with different ATI graphics and two with different Intel based boards. Only the last one appears to be able to run Blender. You mention Airlie has continued development in the f12 branch. If that means there are people working on the bugs and producing new driver updates for F12 (DRM,MESA,X11), especially for ATI then I certainly will give it some time. Yes there have been updates to all of those (and the X server and the kernel) since the F12 release, though I am not sure that all have made it to the updates repository. I typically pull that stuff right from koji when I see it show up. I don't usually mess with blender, though I am starting to learn about Ogre. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Fedora 12 Graphics Issues: Cancel F13 and concentrate on fixing F12 ?
On Thu, 2009-11-26 at 20:16 +, Terry Barnaby wrote: On 11/26/2009 07:46 PM, Bruno Wolff III wrote: On Thu, Nov 26, 2009 at 17:09:14 +, Terry Barnabyter...@beam.ltd.uk wrote: I really want to help and get a stable release and present bug reports and even fix them if I can. But, the current short term release schedule, and no focus on testing and fixing graphics issues, does not inspire me with confidence that a stable usable release will emerge. This makes it difficult for me to justify the effort. Convince me :) I follow the radeon updates pretty closely and my 9200 finally starting working with 3d again a few weeks before the release. Airlie has continued development in the f12 branch and there have been several updates over the last couple of weeks. If you have just tried F11 and not F12 you should consider doing so. For r5xx and below, grab a live image and install one of the smaller 3d apps and try it out. For r6xx and above you'll want to install mesa-experimental-drivers and update xorg-x11-drv-ati. This won't get you the kernel updates related to graphics since the release, but should give you a good look at where things are at so that you can decide if you want install F12 on the machine. Hi, I have tried out F12 on 4 different systems, 2 with different ATI graphics and two with different Intel based boards. Only the last one appears to be able to run Blender. You mention Airlie has continued development in the f12 branch. If that means there are people working on the bugs and producing new driver updates for F12 (DRM,MESA,X11), especially for ATI then I certainly will give it some time. So is blender working the only thing you consider as working? The current focus is on making graphics work for as many ppl as possible first, then 3D is always further down the list, this is just common sense. Current priorities are: 0) you aren't running a binary driver - if so no priority for you. a) Can you see stuff on the screen at install/boot? b) can you run GNOME desktop in reasonably useful manner? i.e. firefox runs okay, no glitches, major slowdowns etc. c) can you suspend/resume? d) can you run compiz/gnome-shell? e) can you run non-Gnome desktops at reasonable speed? (yes we have to prioritise gnome over KDE, it sucks but thats life) f) does misc 3D application run? So yes I'm sorry 3D generally does end up at the end of the list, but if everything else on your desktops work except that, then I suggest you try and lead some sort of 3D testing group and maybe feedback upstream when your favourite apps breaks. The big mesa problem for F11 was we pushed one mesa update to fix some r300 bugs, and it broke some Intel, we just cannot get the regression testing necessary with the current Fedora updates/updates-testing system, we are hoping per-user repos stuff will solve some of that. Dave. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: [RFC] unified i386/x86_64 install media.
On a not entirely unrelated topic, I noticed the other day that Ubuntu ships generic kernels which work on i386 and x86-64 (or that's what it appeared to do for me). Anyone know how that works? Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming blog: http://rwmj.wordpress.com Fedora now supports 80 OCaml packages (the OPEN alternative to F#) http://cocan.org/getting_started_with_ocaml_on_red_hat_and_fedora -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Fedora 12 Graphics Issues: Cancel F13 and concentrate on fixing F12 ?
Yes, some graphics boards I am sure work well, although 3D should really be working on all cards in 2009 ... But this is the point, there are a lot of different graphics boards, and so a much wider scope for the testing is required here which requires more users over more time with many different applications using basically the same software. Why do you think 3D should be working in 2009 as opposed to any previous years btw? I'm interested in the logic that leads to this point. GPUs have gotten more and more complex every 6 months for about 8 years now. A current radeonhd 4000 series bears little resemblence to the radeon r100 that was out then. The newer GPUs require a full complier to be written for an instruction set more complex than x86 in some places. The newer GPUs get more and more varied modesetting combos that all require supporting. Now I'd would guess (educated slightly) that the amount of code required to write a full driver stack for a modern GPU has probably gone up 40-50x what used to be required, whereas the number of open source community developers has probably doubled since 2001. Also newer GPU designs have forced us to redesign the Linux GPU architecture, this had to happen in parallel with all the other stuff, again with similiar number of developers. So yes it sucks but it should point out why there is no reason why 3D should really be working on all cards. Dave. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Fedora 12 Graphics Issues: Cancel F13 and concentrate on fixing F12 ?
On Fri, 2009-11-27 at 07:23 +1000, Dave Airlie wrote: On Thu, 2009-11-26 at 20:16 +, Terry Barnaby wrote: On 11/26/2009 07:46 PM, Bruno Wolff III wrote: On Thu, Nov 26, 2009 at 17:09:14 +, Terry Barnabyter...@beam.ltd.uk wrote: I really want to help and get a stable release and present bug reports and even fix them if I can. But, the current short term release schedule, and no focus on testing and fixing graphics issues, does not inspire me with confidence that a stable usable release will emerge. This makes it difficult for me to justify the effort. Convince me :) I follow the radeon updates pretty closely and my 9200 finally starting working with 3d again a few weeks before the release. Airlie has continued development in the f12 branch and there have been several updates over the last couple of weeks. If you have just tried F11 and not F12 you should consider doing so. For r5xx and below, grab a live image and install one of the smaller 3d apps and try it out. For r6xx and above you'll want to install mesa-experimental-drivers and update xorg-x11-drv-ati. This won't get you the kernel updates related to graphics since the release, but should give you a good look at where things are at so that you can decide if you want install F12 on the machine. Hi, I have tried out F12 on 4 different systems, 2 with different ATI graphics and two with different Intel based boards. Only the last one appears to be able to run Blender. You mention Airlie has continued development in the f12 branch. If that means there are people working on the bugs and producing new driver updates for F12 (DRM,MESA,X11), especially for ATI then I certainly will give it some time. So is blender working the only thing you consider as working? The current focus is on making graphics work for as many ppl as possible first, then 3D is always further down the list, this is just common sense. Current priorities are: 0) you aren't running a binary driver - if so no priority for you. a) Can you see stuff on the screen at install/boot? b) can you run GNOME desktop in reasonably useful manner? i.e. firefox runs okay, no glitches, major slowdowns etc. c) can you suspend/resume? d) can you run compiz/gnome-shell? e) can you run non-Gnome desktops at reasonable speed? (yes we have to prioritise gnome over KDE, it sucks but thats life) f) does misc 3D application run? I should follow up just as far as the Red Hat X team goes a-d are what we are paid to do, e/f and nice to haves, so really if some community effort was to be brought up around this, e/f are where it would make sense to focus it. Having some sort of repos where we can publish a new kernel/libdrm/mesa/intel/ati/nouveau package in one block for people to test and find regression that isn't rawhide and isn't updates-testing (since it would be abusing that) would be an excellent place to start. Dave. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Fedora 12 Graphics Issues: Cancel F13 and concentrate on fixing F12 ?
On Thu, Nov 26, 2009 at 05:09:14PM +, Terry Barnaby wrote: On 11/26/2009 04:34 PM, Josh Boyer wrote: On Thu, Nov 26, 2009 at 04:08:27PM +, Terry Barnaby wrote: As you obviously know tracking down and reporting bugs like these do take a lot of time and effort, quite often more than actually fixing them. At the moment with the frequency of Fedora releases and the lack of a push to testing and stability on this front I am not enthused, at the moment, with doing this and I suspect many others feel the same. I'm confused. You want Fedora to skip a release to focus on testing and fixing, and you have no plans to help and aren't enthusiastic about actually participating in the testing and fixing? josh I really want to help and get a stable release and present bug reports and even fix them if I can. But, the current short term release schedule, and no focus on testing and fixing graphics issues, does not inspire me with confidence that a stable usable release will emerge. This makes it difficult for me to justify the effort. Convince me :) You're making some pretty bold accusations that there is no focus on testing and fixing graphics issues. Perhaps you could classify what you see as needing more testing and fixing instead of claiming there is none. I think that would be more accurate. As for convincing you, I think I'll refrain. I'd rather try and find someone that actually wants to help then spend time trying to talk to someone that has the nerve to propose canceling a release to do testing and fixing and then needs convincing to actually help with their own idea. Fedora needs less arm-chair quarterbacking. We have shit-tons of that already. josh -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Fedora 12 Graphics Issues: Cancel F13 and concentrate on fixing F12 ?
On 11/26/09, Terry Barnaby ter...@beam.ltd.uk wrote: On 11/26/2009 04:34 PM, Josh Boyer wrote: On Thu, Nov 26, 2009 at 04:08:27PM +, Terry Barnaby wrote: As you obviously know tracking down and reporting bugs like these do take a lot of time and effort, quite often more than actually fixing them. At the moment with the frequency of Fedora releases and the lack of a push to testing and stability on this front I am not enthused, at the moment, with doing this and I suspect many others feel the same. I'm confused. You want Fedora to skip a release to focus on testing and fixing, and you have no plans to help and aren't enthusiastic about actually participating in the testing and fixing? josh I really want to help and get a stable release and present bug reports and even fix them if I can. But, the current short term release schedule, and no focus on testing and fixing graphics issues, does not inspire me with confidence that a stable usable release will emerge. This makes it difficult for me to justify the effort. Convince me :) Convince you? Not sure we need to do that. I've had some issues with graphics on my Dell laptop with nvidia graphics and I reported a couple of bugs and ones been fixed, one was not a bug and the other one I've had lots of help to get fixed, and while not there yet its well and truly on its way. My Intel based systems are spectacularly stable. The thing is with open source communities is that its a two way street. You need to contribute time to get help fixing stuff... if you can't justify the effort to assist in debugging stuff so it can be fixed and help the community as a whole why should the maintainer spend time dealing with your moaning when he's got dozens of other bugs with proper debugs attached that can help with the fixing of the issues and have people appreciate the effort. Its too easy to moan and harder to contribute. Peter -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Fedora 12 Graphics Issues: Cancel F13 and concentrate on fixing F12 ?
Matthew Miller wrote: On the other hand, having a release which emphasizes stability over new features is an idea that's been around for a while. That's actually mostly what F12 has been, partly due to RHEL scheduling, partly due to the shortened release schedule to realign with our target dates and partly due to accidents of scheduling. For example, KDE hasn't received any major changes (e.g. KOffice 2 was punted to F13), only new minor versions (like KDE 4.3) which have also been pushed to F11 updates. You won't get much more conservative in Fedora land. but one of the problems you get is that new development in general doesn't stop and wait for stabilization, so the _next_ release, where you open things up again, ends up extra-unstable as all that new stuff hits at once. In fact that has already happened to some extent: F8 was a release with a shortened release schedule which had a reputation of being very stable, F9 was a lot more groundbreaking with brand new stuff like KDE 4, a new release of X11, Upstart, a rewritten GDM etc. The cool new stuff also came with some funkiness, which thankfully mostly got sorted out by updates. Kevin Kofler -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Fedora 12 Graphics Issues: Cancel F13 and concentrate on fixing F12?
Terry Barnaby wrote: I have just tried to test install F12 on some of my systems, (5 different ones). All of these bar 1 has problems with the graphics (X11 lockups, system lockups and other problems) mainly in 3D but also in 2D. That's surprising as I've read mostly positive feedback about graphics in F12 so far, at least compared to F11. Maybe you are just really unlucky? Kevin Kofler -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Fedora 12 Graphics Issues: Cancel F13 and concentrate on fixing F12 ?
On Thu, 26 Nov 2009, Rahul Sundaram wrote: I have not entered any bugzilla numbers as yet. I spent days with F11 and previous releases diagnosing reporting and attempting to fix bugs. No graphics updates were ever made available for F11 and still Fedora cannot run even Blender on most of my machines. At the moment I am not convinced that it is worth spending this time on F12. It seems likely no updates will appear and in F13 the whole ball game may have changed anyway. Seems a bunch of incorrect assumptions considering that Fedora 11 did get many updates and I already see updates for Fedora 12 in updates-testing repository. Specific bug reports are definitely going to help. Well, here's one graphics regression: https://bugzilla.redhat.com/show_bug.cgi?id=540476 radeon.modeset=0 worked around the problem. (I'm not sure if it's filed against the right component.) -- Pekka Savola You each name yourselves king, yet the Netcore Oykingdom bleeds. Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Fedora 12 Graphics Issues: Cancel F13 and concentrate on fixing F12 ?
On Fri, 2009-11-27 at 08:07 +0200, Pekka Savola wrote: On Thu, 26 Nov 2009, Rahul Sundaram wrote: I have not entered any bugzilla numbers as yet. I spent days with F11 and previous releases diagnosing reporting and attempting to fix bugs. No graphics updates were ever made available for F11 and still Fedora cannot run even Blender on most of my machines. At the moment I am not convinced that it is worth spending this time on F12. It seems likely no updates will appear and in F13 the whole ball game may have changed anyway. Seems a bunch of incorrect assumptions considering that Fedora 11 did get many updates and I already see updates for Fedora 12 in updates-testing repository. Specific bug reports are definitely going to help. Well, here's one graphics regression: https://bugzilla.redhat.com/show_bug.cgi?id=540476 radeon.modeset=0 worked around the problem. (I'm not sure if it's filed against the right component.) Don't use radeonhd, the Fedora X team don't support it and never have. I'm thinking it should reallyt be removed from the distro at this point as it makes things worse rather than better. remove your xorg.conf and turn modesetting on and if its still horrible, then we can talk. So you've proven you can break your own machine that is all. Dave. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: memset bugs.
Hi All, Iam new to this fedora world.. a small question on the below discussion: It is mentioned that having, zero in the third argument is legitimate use cases. Can somebody direct me to such a use case, as i feel, giving memset a zero, is asking it, not to do anything [ might have side effects, not sure from my end, though ]. Regards Roopesh M. On Thu, Nov 26, 2009 at 2:24 PM, Caolán McNamara caol...@redhat.com wrote: On Wed, 2009-11-25 at 23:39 -0500, Tom Lane wrote: John Reiser jrei...@bitwagon.com writes: On 11/25/2009 02:03 PM, Dave Jones wrote: A zero sized memset is always a bug. No, memset(,,0) is not always a bug. I think it's reasonably safe to assume that a *literal constant* zero in the third argument is a bug. Whether the header macros can distinguish that from compile-time-constant expressions is an interesting question, but if they can, +1 for throwing an error. I logged some time ago a trivial patch of https://bugzilla.redhat.com/show_bug.cgi?id=532492 which is apparently in rawhide now to generally avoid a warning on memset(foo, 0, 0) C. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Fedora 12 Graphics Issues: Cancel F13 and concentrate on fixing F12 ?
On 27/11/09 06:08, Dave Airlie wrote: Don't use radeonhd, the Fedora X team don't support it and never have. I'm thinking it should reallyt be removed from the distro at this point as it makes things worse rather than better. If you do this, please consider having a radeonhd-radeon testing day for people like myself - radeonhd works for me where radeon doesn't: https://bugzilla.redhat.com/show_bug.cgi?id=492723 (I haven't yet tested with F12 final, it's on my to-do list - but the various alphas/betas didn't improve matters) I would have thought that the radeon driver capabilities should be very close to radeonhd, some of these bugs should be easy to squash (he says ;). Cheers Alex. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
File hanazono-20091003.zip uploaded to lookaside cache by tagoh
File hanazono-20091003.zip for package hanazono-fonts has been uploaded to the lookaside cache with md5sum e680769573b481a3ae8365fec3b4d463 by tagoh ___ Fedora-fonts-bugs-list mailing list Fedora-fonts-bugs-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-fonts-bugs-list
rpms/hanazono-fonts/devel .cvsignore, 1.2, 1.3 hanazono-fonts.spec, 1.4, 1.5 sources, 1.2, 1.3
Author: tagoh
Update of /cvs/pkgs/rpms/hanazono-fonts/devel
In directory cvs1.fedora.phx.redhat.com:/tmp/cvs-serv32425
Modified Files:
.cvsignore hanazono-fonts.spec sources
Log Message:
* Fri Nov 27 2009 Akira TAGOH ta...@redhat.com - 20091003-1
- Update to 20091003.
Index: .cvsignore
===
RCS file: /cvs/pkgs/rpms/hanazono-fonts/devel/.cvsignore,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -p -r1.2 -r1.3
--- .cvsignore 17 Nov 2008 02:23:06 - 1.2
+++ .cvsignore 27 Nov 2009 02:42:43 - 1.3
@@ -1 +1,2 @@
hanazono-20081012.zip
+hanazono-20091003.zip
Index: hanazono-fonts.spec
===
RCS file: /cvs/pkgs/rpms/hanazono-fonts/devel/hanazono-fonts.spec,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -p -r1.4 -r1.5
--- hanazono-fonts.spec 25 Jul 2009 02:01:14 - 1.4
+++ hanazono-fonts.spec 27 Nov 2009 02:42:43 - 1.5
@@ -4,8 +4,8 @@
%define fontconf %{priority}-%{fontname}.conf
Name: %{fontname}-fonts
-Version: 20081012
-Release: 8%{?dist}
+Version: 20091003
+Release: 1%{?dist}
Summary: Japanese Mincho-typeface TrueType font
Group: User Interface/X
@@ -26,14 +26,16 @@ Japan Society for the Promotion of Scien
Institute for Zen Buddhism (IRIZ), Hanazono University. also with volunteers
who work together on glyphwiki.org.
-This font supports:
- - 6359 characters in JIS X 0208:1997
+This font contains 49161 characters in ISO/IEC 10646 and Unicode Standard,
+also supports character sets:
+ - 6355 characters in JIS X 0208:1997
+ - 5801 characters in JIS X 0212:1990
- 3695 characters in JIS X 0213:2004
- - 22 characters in ISO/IEC 10646:2003/Amd.1:2005 (U+9FA6~U+9FBB)
- - 8 characters in Unicode 5.1 (U+9FBC~U+9FC3)
- - 16 characters in ISO/IEC 10646:2003/Amd.1:2005 (U+31C0~U+31CF)
- - 20 characters in ISO/IEC 10646:2003/Amd.3:2008 (U+31D0~U+31E3)
- - 84 characters in IBM extensions
+ - 6763 characters in GB 2312-80
+ - 13053 characters in Big-5
+ - 4888 characters in KS X 1001:1992
+ - 360 characters in IBM extensions
+ - 9810 characters in IICORE
%prep
%setup -q -T -c -a 0
@@ -64,6 +66,9 @@ rm -rf $RPM_BUILD_ROOT
%changelog
+* Fri Nov 27 2009 Akira TAGOH ta...@redhat.com - 20091003-1
+- Update to 20091003.
+
* Fri Jul 24 2009 Fedora Release Engineering rel-...@lists.fedoraproject.org
- 20081012-8
- Rebuilt for https://fedoraproject.org/wiki/Fedora_12_Mass_Rebuild
Index: sources
===
RCS file: /cvs/pkgs/rpms/hanazono-fonts/devel/sources,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -p -r1.2 -r1.3
--- sources 17 Nov 2008 02:23:06 - 1.2
+++ sources 27 Nov 2009 02:42:43 - 1.3
@@ -1 +1 @@
-eed4ae19b1fbee96ac334bf7af4c564a hanazono-20081012.zip
+e680769573b481a3ae8365fec3b4d463 hanazono-20091003.zip
___
Fedora-fonts-bugs-list mailing list
Fedora-fonts-bugs-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-fonts-bugs-list
rpms/hanazono-fonts/devel hanazono-fonts.spec,1.5,1.6
Author: tagoh
Update of /cvs/pkgs/rpms/hanazono-fonts/devel
In directory cvs1.fedora.phx.redhat.com:/tmp/cvs-serv1393
Modified Files:
hanazono-fonts.spec
Log Message:
Index: hanazono-fonts.spec
===
RCS file: /cvs/pkgs/rpms/hanazono-fonts/devel/hanazono-fonts.spec,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -p -r1.5 -r1.6
--- hanazono-fonts.spec 27 Nov 2009 02:42:43 - 1.5
+++ hanazono-fonts.spec 27 Nov 2009 02:52:06 - 1.6
@@ -61,7 +61,7 @@ rm -rf $RPM_BUILD_ROOT
%_font_pkg -f %{fontconf} hanazono.ttf
-%doc LISENCE.txt README.txt THANKS.txt
+%doc LISENSE.txt README.txt THANKS.txt
%dir %{_fontdir}
___
Fedora-fonts-bugs-list mailing list
Fedora-fonts-bugs-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-fonts-bugs-list
rpms/hanazono-fonts/devel hanazono-fonts.spec,1.6,1.7
Author: tagoh
Update of /cvs/pkgs/rpms/hanazono-fonts/devel
In directory cvs1.fedora.phx.redhat.com:/tmp/cvs-serv10555
Modified Files:
hanazono-fonts.spec
Log Message:
correct a typo
Index: hanazono-fonts.spec
===
RCS file: /cvs/pkgs/rpms/hanazono-fonts/devel/hanazono-fonts.spec,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -p -r1.6 -r1.7
--- hanazono-fonts.spec 27 Nov 2009 02:52:06 - 1.6
+++ hanazono-fonts.spec 27 Nov 2009 04:55:38 - 1.7
@@ -61,8 +61,7 @@ rm -rf $RPM_BUILD_ROOT
%_font_pkg -f %{fontconf} hanazono.ttf
-%doc LISENSE.txt README.txt THANKS.txt
-%dir %{_fontdir}
+%doc LICENSE.txt README.txt THANKS.txt
%changelog
___
Fedora-fonts-bugs-list mailing list
Fedora-fonts-bugs-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-fonts-bugs-list
Meeting today
Just a note about our weekly meeting this week. I know I won't be there and it seems likely several people won't be around as it's holiday in the US. Having said that, I certainly wouldn't want to stop anyone from having a meeting, there's always lots to discuss so if people show up and have a meeting, just make sure you send the meeting notes to the list. If no one shows up, happy holidays :) -Mike ___ Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
introduction
Hi everyone, My name is Mike Maravillo and I'd like to join the Fedora community, particularly the Infrastructure group. I started using Linux way back with Slackware 3.0 as a system administrator for a local ISP in the Philippines. Since then, I've been connected with companies doing consulting, training, and technical support using Linux and Open Source. I've also done software development projects using C, PHP, Perl, and Python/PyGTK. Joining the Infrastructure group would be a good chance for me to contribute and bring back to the community, and hopefully would quench that thirst to learn more of what's current since I've been mostly involved with programming lately. :) Cheers, Mike ___ Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
[Fedora-legal-list] Trademark License Agreement
Greetings, I'm planning to open a website about fedora.I think I have to sign TLA to legalize this but I have no idea about how to do this... I tried to connect with le...@fedor* they didn't replied to me Can anybody give me some directions? Thanks! ___ Fedora-legal-list mailing list Fedora-legal-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-legal-list
Re: [Fedora-legal-list] Trademark License Agreement
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, Nov 26, 2009 at 12:03 PM, B.S. wrote: Greetings, I'm planning to open a website about fedora.I think I have to sign TLA to legalize this but I have no idea about how to do this... I tried to connect with le...@fedor* they didn't replied to me Can anybody give me some directions? Thanks! Per this page: https://fedoraproject.org/wiki/Legal/Trademark_guidelines#Domain_names You should contact the Board, and I would mail the fedora-advisory-board mailing list. The fedora-legal list is generally, but not always, concerned with software licensing issues. Seems that this set of guidelines would come into play, and likely you would need a TLA. https://fedoraproject.org/wiki/Local_community_domains However, today (and in most cases) tomorrow is a public holiday in the US where a significant chunk of the Board resides. Cheers, David Nalley -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Use GnuPG with Firefox : http://getfiregpg.org (Version: 0.7.10) iEYEARECAAYFAksOuVYACgkQkZOYj+cNI1ei7wCgnnk+PIsZ3kFqcxtqzt+sVlf3 +2UAoJAl+AHMSfG7anim+jSCuhlDWxVQ =TYlc -END PGP SIGNATURE- ___ Fedora-legal-list mailing list Fedora-legal-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-legal-list
Re: Can't control flash player (32 bits)
Il 25/11/2009 22:15, Wolfgang S. Rupprecht ha scritto: Andre Robatinoan...@bwh.harvard.edu writes: I think but am not absolutely sure that the problem started after installing Nvidia's video driver I see this problem Radeon-based frame buffers too. It isn't just an nvidea problem. Definitely is not a driver problem: I'm using an Intel GPU. Looking this evening for the compiz solution, but I need compiz for maximize vertically/horizontally windows! :( -- 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: httpd with symbolic links and selinux enabled
On Thu, 2009-11-26 at 15:16 +0800, Justin Jereza wrote: I'm having trouble accessing symbolic links in userdirs through httpd with selinux enabled on Fedora 12. Have you configured Apache to follow symlinks? http://localhost/manual/mod/core.html#options You also need appropriate file and directory permissions (world readable files and directories, and directories need to be world executable, too). -- [...@localhost ~]$ uname -r 2.6.27.25-78.2.56.fc9.i686 Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists. -- 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: F11 Thunderbird 3 beta 4
On 26/11/09 07:09, Joachim Backes wrote: On 11/25/2009 06:12 PM, Paul Erickson wrote: Does anyone know when there will be an upgrade beyond Thunderbird 3 beta 4? My main problem with it is that the ability to run filter now button is no longer functioning. A Bugzilla report has been filed some time ago, but I see no indication of when a new version of Thunderbird will be available for F11 which will fix the problem. Have I missed something somewhere? Having similar problems: Bug 527729 - thunderbird-3.0 Beta 4 message filters do not run correctly Get yourself cc to the relevant upstream bugs. Will give you some idea of what is happening. -- Regards, Frank Murphy UTF_8 Encoded. -- 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: httpd with symbolic links and selinux enabled
Have you configured Apache to follow symlinks?
http://localhost/manual/mod/core.html#options
Yes, Apache follows symlinks. That's why http://localhost/~user/foo/
is accessible.
You also need appropriate file and directory permissions (world readable
files and directories, and directories need to be world executable,
too).
All necessary permissions are set. Only directories inside ~/foo that
contain symlinks are inaccessible. Remove the symlinks, and they
become accessible. Also, http://localhost/~user/foo/bar/baz.html is
accessible even though http://localhost/~user/foo/bar/ isn't. Finally,
symlinks within ~/public_html itself work fine. So it seems that
symlinks within symlinks are the only ones that give me trouble.
Should have attached the following log messages earlier:
Nov 26 16:49:26 adnix kernel: type=1400 audit(1259225366.816:11484):
avc: denied { read } for pid=21208 comm=httpd name=index.html
dev=dm-2 ino=5144788 scontext=unconfined_u:system_r:httpd_t:s0
tcontext=unconfined_u:object_r:user_home_t:s0 tclass=lnk_file
Nov 26 16:49:26 adnix kernel: type=1400 audit(1259225366.816:11485):
avc: denied { getattr } for pid=21208 comm=httpd
path=/home/justin/foo/bar/index.html dev=dm-2 ino=5144788
scontext=unconfined_u:system_r:httpd_t:s0
tcontext=unconfined_u:object_r:user_home_t:s0 tclass=lnk_file
--
Justin Jereza
LPIC-1
--
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
Problem with maximum size of group and getent when using LDAP backend
I am seeing a problem with retrieving group information from an LDAP backend where the number of members of the groups can be large. The data I have contains duplicate gidNumbers which may be causing other problems. But I think this is a buffer size problem in the interface between the glibc library and the nss_ldap backend. The behaviour is as follows. I am using getent to enuerate the group map e.g. getent group I get all of the entries from the local group files back, and then the first entry from the LDAP store is returned, the next entry is retrieved from the LDAP backend by NSS_LDAP but this layer returns NSS_TRYAGAIN/ERANGE and getent just terminates. Does anybody know if this is a correct diagnosis of the problem I am seeing, i.e. getent calls into getgrent in the library and it calls the nss layer which gives up on the LDAP service as soon as the buffer overflows. Note I am testing this on a rehat RHEL 5.3 box running glibc-2.5-34 with nss_ldap-265 plus my patches (which do not touch this area of the code yet). Thoughts or suggestions as to where I can go to check this out further solicited. Regards, Howard. Coherent Technology Limited, 23 Northampton Square, Finsbury, London EC1V 0HL, United Kingdom Telephone: +44 20 7690 7075 Mobile: +44 7980 639379 Company Email: coher...@cohtech.com Website: http://www.cohtech.com http://www.cohtech.com/ -- 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
Kaffeine
I am using Fedora 12. After I first install Fedora 12 Kaffeine would play my music cd's. Once I disconnect my computer to clean up cables (just tight up cables) I could no longer get kaffeine to work. I always gets error *Cannot find input plugin for MRL [cdda:/]*. What I am wondering - does anyone else see this problem and has anyone solved this problem. I have two sata cdroms. I just got on this list so I am not aware if had been previously discussed. Thanks Jim Bennett -- 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: Is F12 ready to upgrade ? Is it worth it ?
Tim wrote: I'm perplexed by the posts I am seeing regarding F12 upgrades. Lots of upgrade issues and darn faint praise as far as I can tell ? On a support list you, typically, see more problems than all is well postings. It surprises me that there is not a greater attempt to get feed-back on the frequency of problems, or equally, the lack of problems. I would have thought it would be relatively easy to design an online form that Fedora users could be asked to complete. -- Timothy Murphy e-mail: gayleard /at/ eircom.net tel: +353-86-2336090, +353-1-2842366 s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland -- 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: Is F12 ready to upgrade ? Is it worth it ?
On 11/26/2009 12:53 PM, Timothy Murphy wrote: Tim wrote: I'm perplexed by the posts I am seeing regarding F12 upgrades. Lots of upgrade issues and darn faint praise as far as I can tell ? On a support list you, typically, see more problems than all is well postings. It surprises me that there is not a greater attempt to get feed-back on the frequency of problems, or equally, the lack of problems. I would have thought it would be relatively easy to design an online form that Fedora users could be asked to complete. There are certainly issues with X11 graphics in F12. On 4 different systems I have installed it on 3 do not work in 3D (System hangs, etc). 2 of the systems have hangs (X11 and/or system) in 2D. The problems I have experienced and I believe a number of others are experiencing are due to graphics driver problems (DRM,DRI,MESA,X11) with certain graphics chip sets (At least 4 different ones in my case). I know there are a lot of changes happening on the Graphics front, but I do feel its time to focus on fixing these issues rather than spending valuable developer and user time on a new release ... -- 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: Prius Gas Mileage
Jon, What list was your question for? I have a Prius and experiencing similar problem too. thanks, -pete On Wed, 25 Nov 2009 19:36:40 -0800 Jonathan Ryshpan jonr...@pacbell.net wrote: On Wed, 2009-11-25 at 19:33 -0800, Jonathan Ryshpan wrote: The gas mileage on my Prius has slowly declined from about 40 mpg when I bought it in 2005... Please accept my apologies for posting this message, which was intended for another list (8-(. jon -- 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: Is F12 ready to upgrade ? Is it worth it ?
Terry Barnaby wrote: It surprises me that there is not a greater attempt to get feed-back on the frequency of problems, or equally, the lack of problems. I would have thought it would be relatively easy to design an online form that Fedora users could be asked to complete. There are certainly issues with X11 graphics in F12. On 4 different systems I have installed it on 3 do not work in 3D (System hangs, etc). 2 of the systems have hangs (X11 and/or system) in 2D. If you don't mind my using your problem as a hook to hang an opinion on: You have had graphics problems with 3 out of 4 machines. Personally, I have had no graphics problems with Fedora-12/KDE on 5 machines, though I have had other minor (and unimportant) problems. But how rare or common is your experience? Have only 5% of Fedora users had graphics problems with F-12? Or is it 50%? Or 75%? I don't see how it is possible to plan development rationally without some idea of the statistics. -- Timothy Murphy e-mail: gayleard /at/ eircom.net tel: +353-86-2336090, +353-1-2842366 s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland -- 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: Prius Gas Mileage
Am Mittwoch, den 25.11.2009, 22:44 -0500 schrieb Marcus D. Leech: On 11/25/2009 10:38 PM, Sam Varshavchik wrote: Jonathan Ryshpan writes: The gas mileage on my Prius has slowly declined from about 40 mpg when I bought it in 2005 (2d hand, it's a 2004 model year) to about 35 mpg today. Has anyone else noticed this? Any ideas why? It could, of course, be just that I'm paying less attention to driving for good gas mileage, or have let the pressure in the tires go down, but I don't think so. Try upgrading your Prius' kernel to the latest version in updates. Perhaps one of the kernel performance measurement tools would be in order? Might have to translate from context-switches/sec to MPG, but that's what 'units' is for, right? Sounds like a perfect job for powertop to me. Did somebody port it over to this prius architecture (some kind of RISC?). signature.asc Description: Dies ist ein digital signierter Nachrichtenteil -- 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: Prius Gas Mileage
2009/11/26 Marcus D. Leech mle...@ripnet.com: On 11/25/2009 10:38 PM, Sam Varshavchik wrote: Jonathan Ryshpan writes: The gas mileage on my Prius has slowly declined from about 40 mpg when I bought it in 2005 (2d hand, it's a 2004 model year) to about 35 mpg today. Has anyone else noticed this? Any ideas why? It could, of course, be just that I'm paying less attention to driving for good gas mileage, or have let the pressure in the tires go down, but I don't think so. Try upgrading your Prius' kernel to the latest version in updates. Perhaps one of the kernel performance measurement tools would be in order? Might have to translate from context-switches/sec to MPG, but that's what 'units' is for, right? I think this might be the problem, try using thusnelda rather than mpg. -- imalone -- 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
Sirius Player
Anyone know of a media player that supports Sirius with a slightly better interface than Sipie? Thanks! jlc -- 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
fedora 12, attempt to install dual boot with OS X 10.4 (Tiger) on MacBook Pro
I was running Fedora 10 under bootcamp, dual booting with OS X 10.4.11 (Tiger) on a MacBook Pro. I began (using the live boot CD) an install of Fedora 12. When I got to the point where you reboot to continue, the Fedora partition (an LVM, I just let the installer do what it wanted) was not a bootable drive. That is, bootcamp didn't see it anymore. I booted up into OS X and tried the bootcamp assistant, which no longer runs. Apparently there is no version of bootcamp that still runs on the version of OS X that I have. So I have a few questions: 1) Has anyone solved this? 2) If not, if I ditch OS X for good (I'm not going to pay for a new OS on this 4 yr old computer), should I expect any particular problems with Fedora 12 on this older MacBook Pro? It's an Intel Core Duo (not core 2 duo) model with ATI Radeon X1600. The only reasons I keep OS X now are 1) can't get bluetooth to work under Fedora 10; 2) Can't get my java-based VPN portal to load up under Fedora 10 on this computer. The ATI doesn't do everything it should, but that doesn't bother me (I've never tried to fix it). Thanks, Matt -- 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
F11 - F12 from DVD: error; unable to read package metadata
Hi all, I would like to upgrade an existing F11 system to F12. However, the installer throws up an error message: Unable to read package metadata. This may be due to a missing repodata directory. Please ensure that your install tree has been properly generated. Cannot retrieve repository data (respond.xml) for respository anaconda-InstallationRepo-200911081904-x86_64. Please verify its path and try again. I've seen this the last few Fedora upgrades. As a result, I usually end up doing the upgrade with yum. However this time I am changing architecture (686-86_64) and would prefer to do it from the DVD, as I don't believe that using yum to do this is supported. Thanks. - Colin Brace Amsterdam http://lim.nl -- View this message in context: http://old.nabble.com/F11--%3E-F12-from-DVD%3A-error--unable-to-read-package-metadata-tp26530686p26530686.html Sent from the Fedora List mailing list archive at Nabble.com. -- 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: Prius Gas Mileage
On Thu, 2009-11-26 at 15:40 +0100, Christoph Höger wrote: Am Mittwoch, den 25.11.2009, 22:44 -0500 schrieb Marcus D. Leech: On 11/25/2009 10:38 PM, Sam Varshavchik wrote: Jonathan Ryshpan writes: The gas mileage on my Prius has slowly declined from about 40 mpg when I bought it in 2005 (2d hand, it's a 2004 model year) to about 35 mpg today. Has anyone else noticed this? Any ideas why? It could, of course, be just that I'm paying less attention to driving for good gas mileage, or have let the pressure in the tires go down, but I don't think so. Try upgrading your Prius' kernel to the latest version in updates. Perhaps one of the kernel performance measurement tools would be in order? Might have to translate from context-switches/sec to MPG, but that's what 'units' is for, right? Sounds like a perfect job for powertop to me. Did somebody port it over to this prius architecture (some kind of RISC?). I think someone needs to give it a hummer Craig -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- 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: F11 - F12 from DVD: error; unable to read package metadata
On Thu, 2009-11-26 at 07:05 -0800, Colin Brace wrote: Hi all, I would like to upgrade an existing F11 system to F12. However, the installer throws up an error message: Unable to read package metadata. This may be due to a missing repodata directory. Please ensure that your install tree has been properly generated. Cannot retrieve repository data (respond.xml) for respository anaconda-InstallationRepo-200911081904-x86_64. Please verify its path and try again. I've seen this the last few Fedora upgrades. As a result, I usually end up doing the upgrade with yum. However this time I am changing architecture (686-86_64) and would prefer to do it from the DVD, as I don't believe that using yum to do this is supported. did you verify the DVD so that it properly matches the sha256sum? Generally I burn these things at the slowest rate possible so I have least likelihood of problems in whatever cd/dvd reader I put it into. Craig -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- 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: F11 Thunderbird 3 beta 4
On 11/26/2009 03:24 AM, Frank Murphy (Frankly3D) wrote: On 26/11/09 07:09, Joachim Backes wrote: On 11/25/2009 06:12 PM, Paul Erickson wrote: Does anyone know when there will be an upgrade beyond Thunderbird 3 beta 4? My main problem with it is that the I am running nightly upstream from here (insyalled in /usr/local): http://ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/latest-comm-1.9.1/ and many of the problems are fixed - the printing bug is there (no printers show up but with 2 simple work arounds) and of course GLODA is crap and cannot be completely turned off - but that is in beta 4 too ... Also, remember that mozilla team is not convinced code is 64 bit clean which is why firefox only provides 64 bit testing version with no plans for supported till 4.0. TB may follow suit. So you may want to use 32 bit version on x86_64 fedora anyway if you run into those problems. good luck. -- 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: F11 - F12 from DVD: error; unable to read package metadata
Craig White-6 wrote: did you verify the DVD so that it properly matches the sha256sum? If you are asking whether I chose the verify disk first option in the DVD menu, yes, I always do this. - Colin Brace Amsterdam http://lim.nl -- View this message in context: http://old.nabble.com/F11--%3E-F12-from-DVD%3A-error--unable-to-read-package-metadata-tp26530686p26530803.html Sent from the Fedora List mailing list archive at Nabble.com. -- 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
reinstalling grub MBR on first drive
Hi all, Several weeks ago, I installed a new motherboard in my Fedora system. During the switchover, the SATA drives (I have five) were reconnected in a slightly different order. As a result, the grub menu wasn't displayed; rather I was dumped into the grub prompt and had to boot manually (root..., kernel... initrd... boot). Just now, I tried to fix it by reconnecting the SATA drives in the order I think they should, but I have succeeded only in making things worse. Now I don't even get a the grub prompt; just an empty screen. Yes, I've googled this, yes, there lots of hits, but I can't seem to figure out what I need to do. From what I understand, the MBR of the first drive needs to point to the drive with the OS. In my case, the OS is on /dev/sdb. So, there needs to be something in the MBR on /dev/sda pointing to /dev/sdb1, which is /boot, no? Still, I seem to be missing part of the picture. Simply put, what do I need to do to be able to boot my system again? Thanks. - Colin Brace Amsterdam http://lim.nl -- View this message in context: http://old.nabble.com/reinstalling-grub-MBR-on-first-drive-tp26530961p26530961.html Sent from the Fedora List mailing list archive at Nabble.com. -- 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: Prius Gas Mileage
The gas mileage on my Prius has slowly declined from about 40 mpg when I bought it in 2005 (2d hand, it's a 2004 model year) to about 35 mpg today. Has anyone else noticed this? Any ideas why? It could, of course, be just that I'm paying less attention to driving for good gas mileage, or have let the pressure in the tires go down, but I don't think so. Thanks - jon Hello Everyone I hope this doesn't seem off topic... But my wife told me about this: http://www.thestar.com/wheels/article/730933--toyota-launches-massive-u-s-recall Well, the recall does relate to the proper/improper functioning of the gas pedal... Steven P. Ulrick -- 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: Prius Gas Mileage
The gas mileage on my Prius has slowly declined from about 40 mpg when I bought it in 2005 (2d hand, it's a 2004 model year) to about 35 mpg today. Has anyone else noticed this? Any ideas why? It could, of course, be just that I'm paying less attention to driving for good gas mileage, or have let the pressure in the tires go down, but I don't think so. Thanks - jon Hello Everyone I hope this doesn't seem off topic... But my wife told me about this: http://www.thestar.com/wheels/article/730933--toyota-launches-massive-u-s- recall Well, the recall does relate to the proper/improper functioning of the gas pedal... Steven P. Ulrick And this is from Toyota themselves: http://pressroom.toyota.com/pr/tms/toyota/toyota-consumer-safety- advisory-102572.aspx Steven P. Ulrick -- 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
Your experience of Firefox + HTML5
Hi, recently Firefox has become capable of playing video directly without plugins. It's the big HTML5 + video saga. I'm running Fedora 11 super up to date and I have to say that this things works a bit but not very well. Take for instance the home page of firefox and click bottom left http://www.mozilla-europe.org/en/firefox/video/ It's a good example of what does not work. If I pause the video there is no way of starting again. And the same for all other HTML5 videos I've seen. Has anybody tried http://www.youtube.com/html5, this is even worse as it does not work even without pressing pause. -- 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: Prius Gas Mileage
On Wed, 2009-11-25 at 19:33 -0800, Jonathan Ryshpan wrote: The gas mileage on my Prius has slowly declined from about 40 mpg when I bought it in 2005 (2d hand, it's a 2004 model year) to about 35 mpg today. Has anyone else noticed this? Any ideas why? It could, of course, be just that I'm paying less attention to driving for good gas mileage, or have let the pressure in the tires go down, but I don't think so. Thanks - jon The same thing is happen to us. I thought it might be possible to replace the module that decides whether the motor or engine runs the car. But the Toyota people tell it can't be done. It pursue this further contact PriusChat a group of Prius owners that field questions -- 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: Your experience of Firefox + HTML5
2009/11/26 Andrea mariofut...@googlemail.com: Hi, recently Firefox has become capable of playing video directly without plugins. It's the big HTML5 + video saga. I'm running Fedora 11 super up to date and I have to say that this things works a bit but not very well. Take for instance the home page of firefox and click bottom left http://www.mozilla-europe.org/en/firefox/video/ It's a good example of what does not work. If I pause the video there is no way of starting again. And the same for all other HTML5 videos I've seen. Has anybody tried http://www.youtube.com/html5, this is even worse as it does not work even without pressing pause. Not on a Fedora system right now, but the http://www.mozilla-europe.org/en/firefox/video/ example is working for me on Firefox 3.5.5 on Slackware (pausing, backwards and forwards, etc.), so that might be a Fedora-specific problem. The http://www.youtube.com/html5 example does not work, right clicking on it to 'save as' shows it is an mp4 file, which is probably not supported without extra plugins. The failure to specify a basic codec support for HTML5 was its major failing. -- imalone -- 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: Pulseaudio error message -
On 25/11/09 20:09, stan wrote: On Wed, 25 Nov 2009 15:10:04 -0500 Bob Goodwinbobgood...@wildblue.net wrote: I don't have much need for sound but it usually works. This is a new F-12 install from the livecd and it acts like the audio level is turned down somewhere although I haven't been able to find it. I think I can hear some very faint sounds at times?. One symptom is:[b...@box6 ~]$ aplay /usr/share/sounds/purple/alert.wav Home directory /home/bobg not ours. ALSA lib pulse.c:229:(pulse_connect) PulseAudio: Unable to connect: Connection refused aplay: main:608: audio open error: Connection refused When I try pavucontrol I get an error message: Connection failed: Connection refused I don't know what this is telling me, I know that I have changed anything related to sound. It worked with no problem in F-11 Any suggestions appreciated. Bob Sure sounds like a permission problem. It is acting like you are a different user than pulse was started with. What happens if you set up a new user and try from there? I created a new user bob and he was able to get sound after changing some of the sound config's via the GUI for Sound Preferences. It was set to Analog Mono Output/Amplifier. Changing that to Analog Output/Amplifier got sound working for bob but not for me bobg! I've been checking permissions but obviously not the right ones or not recognizing the error? Pavucontrol still comes up with the same error message. Bob -- 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: Is F12 ready to upgrade ? Is it worth it ?
On 11/26/2009 02:08 PM, Timothy Murphy wrote: Terry Barnaby wrote: It surprises me that there is not a greater attempt to get feed-back on the frequency of problems, or equally, the lack of problems. I would have thought it would be relatively easy to design an online form that Fedora users could be asked to complete. There are certainly issues with X11 graphics in F12. On 4 different systems I have installed it on 3 do not work in 3D (System hangs, etc). 2 of the systems have hangs (X11 and/or system) in 2D. If you don't mind my using your problem as a hook to hang an opinion on: You have had graphics problems with 3 out of 4 machines. Personally, I have had no graphics problems with Fedora-12/KDE on 5 machines, though I have had other minor (and unimportant) problems. But how rare or common is your experience? Have only 5% of Fedora users had graphics problems with F-12? Or is it 50%? Or 75%? I don't see how it is possible to plan development rationally without some idea of the statistics. I agree. I could be unlucky with my particular systems. Although from the forum there apear to be many people having install problems that sound like Graphics driver issues. I am also mainly talking about 3D apps that, I guess, a lot of people do not use. Are there any statistics of actual F12 users, not just those who downloaded the systems and installed them ? (I have test installed 5 F12 systems but use none of them). -- 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
Thunderbird + Gmail: double notification of every mail
Hi, I am running Thunderbird 3 beta 4 and with a IMAP gmail account I am notified twice for every email, one in the inbox and one in the Gmail/Allmail folder. Any setting could change that? -- 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: Thunderbird + Gmail: double notification of every mail
On 11/26/2009 10:15 AM, Andrea wrote: Hi, I am running Thunderbird 3 beta 4 and with a IMAP gmail account I am notified twice for every email, one in the inbox and one in the Gmail/Allmail folder. Any setting could change that? Right click on All Mail, select Properties, and uncheck Check this folder for new messages. -- Steve -- 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: Your experience of Firefox + HTML5
On 11/26/2009 10:37 AM, Andrea wrote: Hi, recently Firefox has become capable of playing video directly without plugins. It's the big HTML5 +video saga. I'm running Fedora 11 super up to date and I have to say that this things works a bit but not very well. Take for instance the home page of firefox and click bottom left http://www.mozilla-europe.org/en/firefox/video/ It's a good example of what does not work. If I pause the video there is no way of starting again. Works fine for me. Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.5) Gecko/20091105 Fedora/3.5.5-1.fc11 Firefox/3.5.5 And the same for all other HTML5 videos I've seen. Has anybody tried http://www.youtube.com/html5, this is even worse as it does not work even without pressing pause. Ditto. Does not start. -- 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: Thunderbird + Gmail: double notification of every mail
On 26/11/09 16:57, Steven Stern wrote: On 11/26/2009 10:15 AM, Andrea wrote: Hi, I am running Thunderbird 3 beta 4 and with a IMAP gmail account I am notified twice for every email, one in the inbox and one in the Gmail/Allmail folder. Any setting could change that? Right click on All Mail, select Properties, and uncheck Check this folder for new messages. It is already unchecked. -- 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: Your experience of Firefox + HTML5
On 26/11/09 16:53, brian wrote: On 11/26/2009 10:37 AM, Andrea wrote: Hi, recently Firefox has become capable of playing video directly without plugins. It's the big HTML5 +video saga. I'm running Fedora 11 super up to date and I have to say that this things works a bit but not very well. Take for instance the home page of firefox and click bottom left http://www.mozilla-europe.org/en/firefox/video/ It's a good example of what does not work. If I pause the video there is no way of starting again. Works fine for me. Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.5) Gecko/20091105 Fedora/3.5.5-1.fc11 Firefox/3.5.5 I've got the same exact version, but as soon as I press pause, nothing works anymore... And the same for all other HTML5 videos I've seen. Has anybody tried http://www.youtube.com/html5, this is even worse as it does not work even without pressing pause. Ditto. Does not start. -- 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
TRIUMPH! Re: Upgrading : give me strength ...
On Wed, 25 Nov 2009 20:19:49 +, I Beartooth wrote: [] Meanwhile, there is a new development. I had burned the install DVD on the first disk that came handy, which happened to be double-sided. I thought to try a well-used DVD-RW instead, and put that into #4 machine. It seems to be working. Stay tuned. PC #4, my oldest and slowest, is now running F12! Gnat in ointment: I could swear I told it to upgrade existing (and got suspicious when it let me customize now), but it didn't. However, that machine and all it had were expendable. What's more, that same DVD-RW, now in my Thinkpad T42, is installing F12 again. It also just offered me the customization choice -- and wouldn't let me go back, except by terminating the install; but again, its data was expendable. Meanwhile, preupgrade still fails on PC #2 and #3 (and I have yet to try on #1 or the T30 Thinkpad), and on the EeePC running Omega. I'll try again, probably tomorrow (It's Thanksgiving here, and I'm the cook.), and report further. -- Beartooth Staffwright, Neo-Redneck Not Quite Clueless Power User I have precious (very precious!) little idea where up is. -- 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
Fedora12 on Acer Aspire 6930
Hi people, i have just installed fedora 12 on my acer Aspire 6930, and everything go fine... (overwriting a perfectly running Fedora11 :) ) but when i reboot the machine it taken very long times to complete the boot procedure... so i have installed bootchart, to look where it takes so long... you could look at it here http://dl.dropbox.com/u/313729/bootchart_tegamino.png; so it seems that my kernel losses for mor than 70 seconds looking for someting... (more if bootchart is not installed...) so i wached dmesg... in seach for tips... there seem to be an HPET timer problem... could somone help??? (dmesg attachment) Initializing cgroup subsys cpuset Initializing cgroup subsys cpu Linux version 2.6.31.5-127.fc12.i686.PAE (mockbu...@x86-3.fedora.phx.redhat.com) (gcc version 4.4.2 20091027 (Red Hat 4.4.2-7) (GCC) ) #1 SMP Sat Nov 7 21:25:57 EST 2009 KERNEL supported cpus: Intel GenuineIntel AMD AuthenticAMD NSC Geode by NSC Cyrix CyrixInstead Centaur CentaurHauls Transmeta GenuineTMx86 Transmeta TransmetaCPU UMC UMC UMC UMC BIOS-provided physical RAM map: BIOS-e820: - 0009f400 (usable) BIOS-e820: 0009f400 - 000a (reserved) BIOS-e820: 000e - 0010 (reserved) BIOS-e820: 0010 - bdaa1000 (usable) BIOS-e820: bdaa1000 - bdaa7000 (reserved) BIOS-e820: bdaa7000 - bdbba000 (usable) BIOS-e820: bdbba000 - bdc0f000 (reserved) BIOS-e820: bdc0f000 - bdd08000 (usable) BIOS-e820: bdd08000 - bdf0f000 (reserved) BIOS-e820: bdf0f000 - bdf19000 (usable) BIOS-e820: bdf19000 - bdf1f000 (reserved) BIOS-e820: bdf1f000 - bdf64000 (usable) BIOS-e820: bdf64000 - bdf9f000 (ACPI NVS) BIOS-e820: bdf9f000 - bdfe2000 (usable) BIOS-e820: bdfe2000 - bdfff000 (ACPI data) BIOS-e820: bdfff000 - be00 (usable) BIOS-e820: 0001 - 00014000 (usable) DMI present. last_pfn = 0x14 max_arch_pfn = 0x100 MTRR default type: uncachable MTRR fixed ranges enabled: 0-9 write-back A-B uncachable C-F write-protect MTRR variable ranges enabled: 0 base 0 mask F8000 write-back 1 base 08000 mask FC000 write-back 2 base 1 mask FC000 write-back 3 disabled 4 disabled 5 disabled 6 disabled x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106 e820 update range: c000 - 0001 (usable) == (reserved) initial memory mapped : 0 - 0100 init_memory_mapping: -375fe000 NX (Execute Disable) protection: active 00 - 20 page 4k 20 - 003740 page 2M 003740 - 00375fe000 page 4k kernel direct mapping tables up to 375fe000 @ 7000-f000 RAMDISK: 37533000 - 37fefb5a Allocated new RAMDISK: 00afb000 - 015b7b5a Move RAMDISK from 37533000 - 37fefb59 to 00afb000 - 015b7b59 ACPI: RSDP 000f74b0 00024 (v02 PTLTD ) ACPI: XSDT bdff63d2 0007C (v01 ACRSYS ACRPRDCT 0604 LTP ) ACPI: FACP bdfe6000 000F4 (v03 INTEL CRESTLNE 0604 ALAN 0001) ACPI: DSDT bdfe7000 08597 (v02 Intel CANTIGA 0604 INTL 20061109) ACPI: FACS bdf9efc0 00040 ACPI: HPET bdffed1b 00038 (v01 INTEL CRESTLNE 0604 LOHR 005A) ACPI: MCFG bdffed53 0003C (v01 INTEL CRESTLNE 0604 LOHR 005A) ACPI: APIC bdffed8f 00068 (v01 PTLTD APIC 0604 LTP ) ACPI: BOOT bdffedf7 00028 (v01 PTLTD $SBFTBL$ 0604 LTP 0001) ACPI: SLIC bdffee1f 00176 (v01 ACRSYS ACRPRDCT 0604 acer ) ACPI: ASF! bdffef95 0006B (v32 OEMID OEMTBL 0604 PTL 0001) ACPI: SSDT bdff6476 001A6 (v01 SataRe SataAhci 1000 INTL 20061109) ACPI: SSDT bdfe5000 00655 (v01 PmRefCpuPm 3000 INTL 20061109) ACPI: SSDT bdfe4000 00259 (v01 PmRef Cpu0Tst 3000 INTL 20061109) ACPI: SSDT bdfe3000 0020F (v01 PmRefApTst 3000 INTL 20061109) ACPI: Local APIC address 0xfee0 4234MB HIGHMEM available. 885MB LOWMEM available. mapped low ram: 0 - 375fe000 low ram: 0 - 375fe000 node 0 low ram: - 375fe000 node 0 bootmap b000 - 00011ec0 (9 early reservations) == bootmem [00 - 00375fe000] #0 [00 - 001000] BIOS data page == [00 - 001000] #1 [001000 - 002000]EX TRAMPOLINE == [001000 - 002000] #2 [006000 - 007000] TRAMPOLINE == [006000 - 007000] #3 [40 - af1210]TEXT DATA BSS == [40 - af1210] #4 [09f400 - 10]BIOS reserved == [09f400 - 10] #5 [af2000 - afa154] BRK == [af2000 - afa154] #6 [007000 - 00b000] PGTABLE == [007000 - 00b000] #7 [afb000 - 00015b7b5a] NEW RAMDISK == [afb000 - 00015b7b5a] #8 [00b000 - 012000] BOOTMAP ==
Reorganising F11 partitions - how to?
Hi all, Again, thanks to all for the support, systems, ideas ( laughs - The Prius Upgrade -- sounded a bit like my old Landrover!) Ok... tried the F12-KDE Live cd am very impressed, especially as it decided orl on its own to treat my laptop screen plugged in monitor as a dual head where I spent 5 minutes looking for my cursor before I realised it was on the other screen.. so now I wwant to use preupgrade to zap 11 to 12. When I first installed F11 on the laptop, I setup several partitions (suggestions from O'Reilly's running Linux...), which now doesn't seem such a good idea or necessary idea. What I'd like to do is to move the contents of /usr /local /tmp from their individual partitions into the / partition delete the individual (now empty) partitions, sharing the space out amongs / and /Home. Q1. Is this possible? if yes, Q2. Do I a) do the mv (or cp + rm) of the contents then b) use KDE4 Partitionmanager to unmount the partitions modify the space and c) remove the unneeded entries from fstab, restart all is OK? or Q3. Is there a way with one of the CLI partitioners to merge the individual partitions with the existing / partition? As ever, many thanks for taking the time to help me out! Dave in freezing cold Rauris. PS is therre a way of searching 'man' pages to look for a command that does 'x' ? -- 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
F12 yum install wireshark - not added to menus
Hi, I have just installed Wireshark on F12 on the console using 'yum install wireshark' as root. And Wireshark has not appearing on the menus, and it is does not envoke from the command line either. Where does it live and is there anyway to add it to the menus ? Many thanks in advance, Aaron -- 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: Your experience of Firefox + HTML5
On 11/26/2009 12:05 PM, Andrea wrote: On 26/11/09 16:53, brian wrote: On 11/26/2009 10:37 AM, Andrea wrote: If I pause the video there is no way of starting again. Works fine for me. Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.5) Gecko/20091105 Fedora/3.5.5-1.fc11 Firefox/3.5.5 I've got the same exact version, but as soon as I press pause, nothing works anymore... Maybe you have an extension loaded that's causing a conflict. -- 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: F12 yum install wireshark - not added to menus
Le jeudi 26 novembre 2009 à 18:20 +, Aaron Gray a écrit : Hi, I have just installed Wireshark on F12 on the console using 'yum install wireshark' as root. And Wireshark has not appearing on the menus, and it is does not envoke from the command line either. Where does it live and is there anyway to add it to the menus ? Many thanks in advance, Aaron -- 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 Hi, the GUI is in the wireshark-gnome package. -- 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: F12 yum install wireshark - not added to menus
On Thu, Nov 26, 2009 at 20:20, Aaron Gray aaronngray.li...@googlemail.comwrote: Hi, I have just installed Wireshark on F12 on the console using 'yum install wireshark' as root. And Wireshark has not appearing on the menus, and it is does not envoke from the command line either. Where does it live and is there anyway to add it to the menus ? Many thanks in advance, Aaron -- 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 This is the package you want : wireshark-gnome-1.2.2-1.fc12.i686 Do yum install wireshark-gnome -- When you have eliminated the impossible, whatever remains, however improbable, must be the truth - Sherlock Holmes -- 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
installation through Fedora
Hi all, This is almost like a riddle to me... I want to install Windows XP on a computer that currently has only fedora installed. It does not have a CD-ROM (not working) and I cannot boot from disk on key, though I can access a disk on key on fedora. I have no internet connection on that computer, but I can still copy files from another computer through the disk on key. How can I install windows XP on it? One of my thoughts is to use fedora to create a FAT32 partition for Windows and make it bootable, and then copy the Windows installation there. But I am not sure about: (1) how to create a partition while on Fedora, without being able to boot to some program like gparted? I don't think I can repartition the disk while running fedora from it. (2) how to make the new partition XP bootable so I can install XP on it in Linux? I know of a few Windows utilities to do that, not sure about Linux any ideas on this bootstrapping process will be greatly appreciated. happy thanksgiving to those who celebrate it. -- 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: F12 yum install wireshark - not added to menus
2009/11/26 ELMORABITY Mohamed pikachu.2...@gmail.com Le jeudi 26 novembre 2009 à 18:20 +, Aaron Gray a écrit : Hi, I have just installed Wireshark on F12 on the console using 'yum install wireshark' as root. And Wireshark has not appearing on the menus, and it is does not envoke from the command line either. Where does it live and is there anyway to add it to the menus ? Hi, the GUI is in the wireshark-gnome package. Thanks, Aaron -- 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: installation through Fedora
Hi all,
This is almost like a riddle to me...
I want to install Windows XP on a computer that currently
has only fedora installed. It does not have a CD-ROM (not
working) and I cannot boot from disk on key, though I can
access a disk on key on fedora. I have no internet
connection on that computer, but I can still copy files from
another computer through the disk on key.
How can I install windows XP on it?
Put the drive into another computer - install - swap it back.
Mick M
Standard guarantee applies - 30 feet or 30 seconds, whichever comes first.
# find / -name *your base* -exec chown us:us {} \;
--
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: Reorganising F11 partitions - how to?
2009/11/26 DB freddog...@yahoo.co.uk: PS is therre a way of searching 'man' pages to look for a command that does 'x' ? You can try `apropos x' or `man -k x' -- Suvayu Open source is the future. It sets us free. -- 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
Problem Module Kernel
I have problem compile module kernel in fedora 11 Kernel: 2.6.30.5-43.fc11.i686.PAE No having module modprobe ip_masq_ftp FATAL: Module ip_masq_ftp not found. -- 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
Cifs with no writing permissions
Dear All, I have just upgraded from F11 to F12, and now when I mount a samba partition with command mount -t cifs -o iocharset=iso8859-1,user=xxx,rw //xxx /mnt/mydir I do not have writing permissions on the mounted directory. Any ideas? Thanks in advance, Paul -- 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
