devel November 2004

devel@lists.fedoraproject.org

287 participants
252 discussions

Some bugs, where to file them?
by Kyrre Ness Sjobak 01 Dec '04

01 Dec '04

I have had some difficulties with installing a box with a "RIVA128" gfx card. The install process itself goes all well. Problems turns up when it has finished installing packages (which took a couple of hours, using NFS... Dead-slow machine...), and reboots. When it has rebooted, it comes to a point where it says "configuring kernel parametres". And there it stops (i had it hanging there for a weekend, just to be shure. It was still hung when i got back on monday ;) Rigth before this happens, it tries to bring up RHGB, which fails miserably. But it fails, it don't chrash the box. Only way (i) have found to solve it, is to boot into single user (it does then get past the "configuring kernel parameters" without problems), and changing the driver from "nv" to "vesa". reboot gets up rhgb, but it still hangs there (or at least when it comes to firstboot). I i then kill power, boot it into single user mode, and *then* using "init 5" to get it up (twice - firstboot chrashes in the first atempt, taking the rest of the thing with it, but it don't happen again...), it works up to GDM. I can then shutdown and reboot and everything else (after fixing monitor resolution and refresh...) without problems. As far as i can see, this is more than one bug, and i don't know where to file'em. xorg? kudzu? firstboot? rhgb? kernel? Kyrre

3 4

Bug Related.
by Jeffrin Thalakkottoor 01 Dec '04

01 Dec '04

Hello All, Iam Will Start My Fisrt Message To This List With A Possible Bug File. It is Like This , The Keyboard Does Not Work On Somedays atleast for some time. This happens in our lab. All the Fedora core 2 Machine Shows The Same Problem. It Shows this Problem On Different Kernels. So It May Not be A kernel bug. It May not Be A Hardware Bug. Because This Problem Is Occuring with Machines in Different Hardware. Please help me to help my friends. ________________________________________________________________________ Yahoo! India Matrimony: Find your life partner online Go to: http://yahoo.shaadi.com/india-matrimony

4 3

rawhide report: 20041130 changes
by Build System 30 Nov '04

30 Nov '04

Updated Packages: MAKEDEV-3.16-1 -------------- * Mon Nov 29 2004 Nalin Dahyabhai <nalin(a)redhat.com> 3.16-1 - allow devices to be specified either as "device" or "devdir"[/]"device" - update to 22 November 2004 devices.txt: - add fuse - add ttyCPM,cucpm - add ttyIOC4,cuioc4 - rename user-mode block devices to avoid conflict with ub block device authconfig-4.6.6-1 ------------------ * Thu Nov 18 2004 Tomas Mraz <tmraz(a)redhat.com> - 4.6.6-1 - merged patches from dist - fix versioning bind-22:9.3.0-1 --------------- * Mon Nov 29 2004 Jason Vas Dias <jvdias(a)redhat.com> - 9.3.0-1 - Upgrade BIND to 9.3.0 in Rawhide / FC4 (bugs 134529, 133654...) * Mon Nov 29 2004 Jason Vas Dias <jvdias(a)redhat.com> - 20:9.2.4-4 - Fix bugs 140528 and 141113: - 2 second timeouts when IPv6 not configured and root nameserver's - AAAA addresses are queried boost-1.32.0-1 -------------- * Mon Nov 29 2004 Benjamin Kosnik <bkoz(a)redhat.com> 1.32.0-1 - Update to 1.32.0 - (#122817: libboost_*.so symlinks missing) coreutils-5.2.1-33 ------------------ * Thu Nov 25 2004 Tim Waugh <twaugh(a)redhat.com> 5.2.1-33 - Fixed colorls.csh (bug #139988). Patch from Miloslav Trmac. * Mon Nov 08 2004 Tim Waugh <twaugh(a)redhat.com> - Updated URL (bug #138279). emacs-21.3-19 ------------- * Mon Nov 29 2004 Jens Petersen <petersen(a)redhat.com> - 21.3-19 - put XIM status under the window for now to stop httx from dying (125413): add emacs-xim-status-under-window-125413.patch - default diff to unified format in .emacs fonts-xorg-6.8.1.1-1 -------------------- * Mon Nov 29 2004 Mike A. Harris <mharris(a)redhat.com> 6.8.1.1-1 - Updated main tarball to include lucidatypewriter fonts that were missing from X.Org X11 6.8.1, and renamed it to 6.8.1.1 to avoid multiple tarballs with same version but different contents, since it was updated with the new fonts. (#139108, 139121, fdo#1560) gamin-0.0.18-1 -------------- * Fri Nov 26 2004 Daniel Veillard <veillard(a)redhat.com> 0.0.18-1 - still chasing the loop bug, checked and cleaned up all GList use - patch from markmc to minimize load on busy apps * Wed Oct 20 2004 Daniel Veillard <veillard(a)redhat.com> 0.0.16-1 - chasing #132354, lot of debugging, checking and testing and a bit of refactoring * Sat Oct 16 2004 Daniel Veillard <veillard(a)redhat.com> 0.0.15-1 - workaround to detect loops and avoid the nasty effects, see RedHat bug #132354 gcc-3.4.3-7 ----------- * Fri Nov 26 2004 Jakub Jelinek <jakub(a)redhat.com> 3.4.3-7 - update from gcc-3_4-branch - PRs rtl-optimization/18614, rtl-optimization/14838, target/18263 - don't optimize printf/fprintf/__printf_chk/__fprintf_chk in any way if return value is not ignored - fix folding of abs (#140890) - fix ppc #pragma longcall (Alan Modra, PR target/18686) gcc4-4.0.0-0.13 --------------- * Sat Nov 27 2004 Jakub Jelinek <jakub(a)redhat.com> 4.0.0-0.13 - update from trunk - change s390{,x} stack layout to work-around GCC 2.95.3 bug: former -mno-backchain (the default), -mbackchain and -mkernel-backchain options were transformed into (in order) -mno-backchain -mpacked-stack, -mbackchain -mno-packed-stack and -mbackchain -mpacked-stack. A new combination -mno-backchain -mno-packed-stack is now the new default (Andreas Krebbel, #139678) - don't optimize printf/fprintf/__printf_chk/__fprintf_chk in any way if return value is not ignored - some more libgcc_s.so.1 tweaks on ia64 * Fri Nov 12 2004 Jakub Jelinek <jakub(a)redhat.com> 4.0.0-0.12 - update from trunk - make _Unwind_* symbols in libgcc_s.so.1 unversioned to match the "IA-64 Linux ABI" gnome-panel-2.8.1-6 ------------------- * Fri Nov 26 2004 Mark McLoughlin <markmc(a)redhat.com> - 2.8.1-6 - Add patch to fix launcher animation artifact (bug #136938) gnome-vfs2-2.8.2-9 ------------------ * Thu Nov 25 2004 Jeremy Katz <katzj(a)redhat.com> - 2.8.2-9 - rebuild to fix broken dep on x86_64 (#140679) initscripts-8.00-1 ------------------ * Mon Nov 29 2004 Bill Nottingham <notting(a)redhat.com> 8.00-1 - fix previous fix (#139656) kdebase-6:3.3.1-12 ------------------ * Thu Nov 25 2004 Than Ngo <than(a)redhat.com> 6:3.3.1-12 - add patch for kmenu large icons #140842 * Tue Nov 23 2004 Than Ngo <than(a)redhat.com> 6:3.3.1-11 - the existing icon is lost, add patch to fix this problem #140196 kernel-2.6.9-1.1006_FC4 ----------------------- * Fri Nov 26 2004 Rik van Riel <riel(a)redhat.com> - add Xen kernels for i686, plus various bits and pieces to make them work openmotif-2.2.3-8.1 ------------------- * Mon Nov 29 2004 Thomas Woerner <twoerner(a)redhat.com> 2.2.3-8.1 - allow to write XPM files with absolute path names again (#140815) * Wed Nov 24 2004 Miloslav Trmac <mitr(a)redhat.com> - 2.2.3-8 - Convert man pages to UTF-8 * Mon Nov 22 2004 Thomas Woerner <twoerner(a)redhat.com> 2.2.3-7 - latest Xpm patches: CAN-2004-0914 (#134631) - new patch for tmpnam in imake (only used for build) openssh-3.9p1-8.1 ----------------- * Mon Nov 29 2004 Thomas Woerner <twoerner(a)redhat.com> 3.9p1-8.1 - fixed PIE build for all architectures * Mon Oct 04 2004 Nalin Dahyabhai <nalin(a)redhat.com> 3.9p1-8 - add a --enable-vendor-patchlevel option which allows a ShowPatchLevel option to enable display of a vendor patch level during version exchange (#120285) - configure with --disable-strip to build useful debuginfo subpackages pam-0.78-2 ---------- * Thu Nov 25 2004 Tomas Mraz <tmraz(a)redhat.com> 0.78-2 - add argument to pam_console_apply to restrict its work to specified files parted-1.6.19-1 --------------- * Sun Nov 28 2004 Jeremy Katz <katzj(a)redhat.com> - 1.6.19-1 - update to 1.6.19 qt-1:3.3.3-15 ------------- * Mon Nov 29 2004 Than Ngo <than(a)redhat.com> 1:3.3.3-15 - convert qdial.3qt to UTF-8 bug #140946 * Tue Nov 23 2004 Than Ngo <than(a)redhat.com> 1:3.3.3-14 - add missing lupdate and lrelease #140230 * Fri Nov 19 2004 Than Ngo <than(a)redhat.com> 1:3.3.3-13 - apply patch to fix qinputcontext rpmdb-fedora-1:4-0.20041130 --------------------------- selinux-policy-strict-1.19.6-1 ------------------------------ * Wed Nov 24 2004 Dan Walsh <dwalsh(a)redhat.com> 1.19-6-1 - Update to Upstream * Wed Nov 24 2004 Dan Walsh <dwalsh(a)redhat.com> 1.19-5-1 - Update to Upstream - Convert to new network_macros.te selinux-policy-targeted-1.19.6-1 -------------------------------- * Wed Nov 24 2004 Dan Walsh <dwalsh(a)redhat.com> 1.19-6-1 - Update to Upstream * Wed Nov 24 2004 Dan Walsh <dwalsh(a)redhat.com> 1.19-5-1 - Update to Upstream - Convert to new network_macros.te slrn-0.9.8.1-2 -------------- * Fri Nov 26 2004 Jindrich Novy <jnovy(a)redhat.com> 0.9.8.1-2 - include translations to srln package (#140870) - remove upstreamed patches system-config-date-1.7.14-1 --------------------------- * Mon Nov 29 2004 Nils Philippsen <nphilipp(a)redhat.com> 1.7.14-1 - bump version * Fri Nov 26 2004 Nils Philippsen <nphilipp(a)redhat.com> - don't use duplicate accelerators (#134172, #140241) tzdata-2004g-1 -------------- * Mon Nov 29 2004 Jakub Jelinek <jakub(a)redhat.com> 2004g-1 - 2004g (#141107) - updates for Cuba util-linux-2.12a-18 ------------------- * Mon Nov 29 2004 Steve Dickson <SteveD(a)RedHat.com> - Made NFS mounts adhere to the IP protocol if specified on command line as well as made NFS umounts adhere to the current IP protocol. Fix #140016 xorg-x11-6.8.1-20 ----------------- * Mon Nov 29 2004 Mike A. Harris <mharris(a)redhat.com> 6.8.1-20 - Disabled with_fonts again - Added xorg-x11-6.8.1-xpm-security-fixes-CAN-2004-0914-sec8-ammendment.patch to fix bugs introduced into libXpm in the previous security patch for CAN-2004-0914 which cause gimp to fail to save Xpm files (#140815, 141047, fdo#1924) * Mon Nov 29 2004 Kristian Høgsberg <krh(a)redhat.com> - Update xorg-x11-6.8.1-ati-radeon-7000-smp-lockup.patch to the new patch from Alex Deucher <agd5f(a)yahoo.com>, provided in https://bugs.freedesktop.org/show_bug.cgi?id=1912. * Tue Nov 23 2004 Mike A. Harris <mharris(a)redhat.com> 6.8.1-19.with_fonts.0 - Enabled with_fonts for a single build, to update fonts-xorg package xpdf-1:3.00-13 -------------- * Mon Nov 29 2004 Than Ngo <than(a)redhat.com> 1:3.00-13 - set match as default psPaperSize #141131 xscreensaver-1:4.18-13 ---------------------- * Fri Nov 26 2004 Than Ngo <than(a)redhat.com> 1:4.18-13 - add patch to fix vroot bug and make xscreensaver working in KDE again. - get rid of webcollage, which often download porn images yum-2.1.12-1 ------------ * Mon Nov 29 2004 Jeremy Katz <katzj(a)redhat.com> - 2.1.12-1 - update to 2.1.12 - add hack from jbj to workaround python 2.4 urllib breakage (#138535)

2 1

Re: Elektrified X.org released (was: X configuration paradigm, and a proposal)
by Avi Alkalay 30 Nov '04

30 Nov '04

Elektra provides the infrastructure for a unified configuration backend. It was actually designed for this purpose. But to have a unified configuration ecosystem, software must use it. Regards, Avi On Tue, 30 Nov 2004 13:48:29 +0000, Jono Bacon <jono(a)jonobacon.org> wrote: > Avi Alkalay wrote: > ...... > > > > > > Does this provide a unified configuration backend? If not, is there any > work going into a unified configuration backend? It seems so many > potential projects would depend on it. > > Jono > > -- > Jono Bacon - http://www.jonobacon.org/ > Writer / Journalist / Consultant / Developer > >

1 0

wrong buildrequires in pango-1.6.0-7
by Luciano Miguel Ferreira Rocha 30 Nov '04

30 Nov '04

Hello, pango-1.6.0-7.src.rpm, in rawhide (I assume it's the same in FC3) has a BuildRequires: xorg-x11-devel >= 4.2.99 OTOH, the -devel package has a Requires: XFree86-devel >= 4.2.99 FC3 ships with xorg-x11-devel 6.8.1, so, obviously, it satisfies the BuildRequires. YDL 4 still uses 0.0.6.6-0.0.2004_03_11.9, that does provide "XFree86-devel = 4.4.0", but not xorg-x11-devel >= 4.2.99. As there never was a xorg-x11 4.2.99, and the devel package specifies XFree86, I guess the BuildRequires line should be changed to "XFree86-devel >= 4.2.99", no? Regards, Luciano Rocha -- Consciousness: that annoying time between naps.

2 1

Gnome desktop and mime stuff help
by Michael A. Peters 30 Nov '04

30 Nov '04

I'm searching for docs on the "right way" of doing Gnome desktop/mime etc. entries. I know that the "old way" (before update-desktop-database) still seems to work, either by accident or by design apps that don't use that command in %post still seem to function as intended. I'm trying to package something that has (at least one) a broken Makefile, as part of make install it want to cat stuff onto /etc/magic, / etc/gnome-vfs-mime-magic, amongst other things that cause to fail when built from a non root user - that I *think* are actually handled by update-desktop-database in the %post script. I do have a problem though - man update-desktop-database No manual entry for update-desktop-database :( Since it looks like I have to fix Makefiles anyway to build the package as an rpm, I'd like to try to do things the right way - I don't think even under gnome-2.4 that cat >> /etc/gnome-vfs-mime-magic was correct (which is what the Msakefile wants to do). http://www.freedesktop.org/Software/desktop-file-utils Not very helpful. Is there a helpful guide somewhere? -- Cheap Linux CD's http://mpeters.us/linux/

3 4

Pentium 4 and Athlon architecture optimizations in kernel
by William M. Quarles 30 Nov '04

30 Nov '04

I dropped my message into this old thread instead: Recent Fedora Core kernels (plus my SPEC file for 2.6.8-1.541 with Athlon support) Have fun. William

2 2

Boot poster challenge
by Owen Taylor 30 Nov '04

30 Nov '04

Problem description =================== Currently, the time to boot the Linux desktop from the point where the power switch is turned on, to the point where the user can start doing work is roughly two minutes. During that time, there are basically three resources being used: the hard disk, the CPU, and the natural latency of external systems - the time it takes a monitor to respond to a DDC probe, the time it takes for the system to get an IP via DCHP, and so forth. Ideally, system boot would involve a 3-4 second sequential read of around 100 megabytes of data from the hard disk, CPU utilization would be parallelized with that, and all queries on external systems would be asynchronous ... startup continues and once the external system responds, the system state is updated. Plausibly the user could start work under 10 seconds on this ideal system. The challenge is to create a single poster showing graphically what is going on during the boot, what is the utilization of resources, how the current boot differs from the ideal world of 100% disk and CPU utilization, and thus, where are the opportunities for optimization. Graphical Ideas =============== Presumably, the main display would be a timeline with wall clock time on the horizontal (or vertical) axis. Then, you'd have a tree with lines representing the processes running at a particular time. The processes lines would have attributes indicating state - perhaps red when waiting for disk, green when running, dotted when sleeping or blocking on IO. Extra lines might be added to the graph to indicate dependencies between processes. If a process calls waitpid() on another process, a dotted line could be added connecting the end of the other process back to the first process. Similar lines could be added when a write from one process causes another process that was waiting in a read() or select() to wake up. While many thousands of processes are run during system boot, this doesn't mean the graph has to have vertical space for all of them ... vertical space is basically determined by the number of processes that are running at once. Parallel to the display of processes would be a display of overall CPU and disk utilization. CPU utilization on a single processor system is pretty straightforward... either the CPU is running at a point in time or it isn't. Considerations like memory bandwidth, processor stalls, and so forth matter when optimizing particular algorithms but an initial guess (that the poster would confirm or deny) is that CPU is not a significant bottleneck for system start. Disk utilization is more complex, because of the huge cost of seeks; while modern drives can easily read 30-40 megabytes/second a seek still takes 5-10ms. Whether or not the drive is active tells little about how well we are doing using it. In addition, there is a significantly long pipeline of requests to the disk, and seeks aren't even completely predictable because the drive may reorder read requests. But a simple display that might be sufficient is graph of instantaneous bandwidth (averaged over a small period of time) being achieved from the disk drive. If processes are red (waiting on the drive) and the bandwidth is low, then there is a problem with too much seeking that needs to be addressed. You'd also want text in the poster; process names are one obvious textual annotation that should be easy to obtain. It might also be interested for processes to be able to provide extra annotations; for the X server to advertise that it is waiting for a DDC probe, and so forth. Implementation thoughts ======================= It should be possible to start with a limited set of easily collected data and already get a useful picture. Useful data collection could be as simple as taking a snapshot of the data that the "top" program displays a few times a second during boot. That already gives you a list of the running processes, their states, and some statistics about global system load. Moving beyond that would probably involve instrumenting the kernel to give notification of process start and termination (possibly providing times(2) style information on termination) to provide visibility for processes that run for too short a time to be picked up by polling. Better kernel reporting of disk utilization might also be needed. It might be possible to employ existing tools like oprofile, however, the level of detail oprofile provides is really overkill... compressing 2 minutes of runtime involving 1000 processes onto a single poster doesn't really allow worrying about what code is getting run by a process at a particular point. Obviously, one challenge of any profiling tool is to avoid affecting the collected data. Since CPU and memory don't seem to be bottlenecks, while disk definitely is a bottleneck, a low impact implementation might be a profiling daemon that started early in the boot process and accumulated information to be queried and analyzed after the boot finishes. While producing a single poster would already be enormously useful, the ability to recreate the poster on any system at any point would be multiply times more so. So, changes to system components that can be gotten into the upstream projects and that can be activated at runtime rather than needing to be conditionally compiled in are best. Motivation ========== I think this project would be a lot of fun to work on; you'd learn a lot about how system boot up works and about performance measurement. And beyond that there is a significant design and visualization element in figuring out how to display the collected data. It would also make a good small-scale academic project. But to provide a little extra motivation beyond that, if people pick this up and come up with interesting results, I'll (personally) pay for up to 3 posters of up to 4' x 6' to be professionally printed and laminated. I'll be flexible about how that works ... if multiple people collaborate on one design, they can get a copy each of that single design. - Owen Taylor

48 159

Fedora Extras for FC3?
by Shahms King 30 Nov '04

30 Nov '04

Is there any timeline/status update for when the Fedora Extras packages on fedora.us will be updated for FC3? Or have most of these been rolled into Fedora Core? There aren't any specific packages I've noticed missing, but it seems a little odd that the only semi-official Extras repository is so far behind in updating packages for FC3. -- Shahms E. King <shahms(a)shahms.com>

6 9

Does anyone else experience occasionnal xfs crashes?
by Matthias Saou 30 Nov '04

30 Nov '04

Hi, For a few months now, I've been experiencing random xfs (the font server, not the filesystem ;-)) crashes on my laptop running FC Dev. As it was a system installed with FC back in January, which had run a binary distribution of XFree86 4.4RC (because the Radeon Mobility 9600 is not supported by 4.3), then upgraded to FC2, FC Dev and had plenty of custom fonts here and there, I didn't bother much to look for the problem. But I reinstalled FC3RC5 cleanly (complete format) Monday, and saw xfs crash on the same day, even before having installed a single 3rd party package or font! The symptoms are quite nasty : If it happens when xscreensaver is running and locks the display, then the login dialog simply never shows up and it gives the impression that the computer is frozen, since even Alt+Ctrl+F1 takes a long time before actually switching to the console! If it's during "normal" operation, then firefox often disappears, focus between windows doesn't work anymore (actually, it almost does, but keyboard/mouse input stops working sometimes, it can come back after "Alt+Tab"... weird), and new applications _all_ fail to start. Seth, could this be what you're seeing? Computer is still reachable by the network, though, so probably not. Even restarting xfs doesn't cure the running X... X needs to be completely restarted before things start working normally again. Right now, I'm running with "ulimit -c unlimited; xfs -nodaemon" on my first console... but xfs still hasn't crashed again, so I'm still waiting before I can expect being able to make a useful bug report. Still, I was wondering, does anyone else suffer from the symptoms above? I found zarroo bugs about xfs crashing in FC, so I'm a bit puzzled. If you think you have this problem, just "service xfs status" and you'll know for sure. Matthias -- Clean custom Red Hat Linux rpm packages : http://freshrpms.net/ Fedora Core release 3 (Heidelberg) - Linux kernel 2.6.9-1.649.radeon Load : 1.14 0.78 0.80

4 5

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

devel November 2004