I made a zope 2.9 package, and would like your comment on it, if you
The SRPM is here
A powerfull GroupWare, CMS, CRM, ECM: CPS (Open Source & GPL).
Opengroupware, SPIP, Plone, PhpBB, JetSpeed... are good: CPS is better.
http://www.cps-project.org for downloads & documentation.
Free hosting of CPS groupware: http://www.objectis.org.
Andy Burns wrote:
> Have you tried with acpi=off?
> Is there a BIOS update available for your motherboard?
After submitting my original message, I found bugzilla report 175731 that suggested booting with acpi=off.
That allowed boot of SMP kernel.
Also, I tried booting with pci=noacpi. That also allowed boot of SMP kernel. There is no output from the "dmidecode output" command.
I had my wife install and run x86info: it reports a number of problems. I'll have to see that for myself. And crack the case to see which motherboard is in there. ISTR that I installed a BIOS upgrade within a year after I got the system.
I have an entry in fstab for the memory bar so in particular I mean mounted
automatically in gnome.
Since the gnome volume manager crashed though when the memory bar was
inserted something must have changed in user space land to cause these
>From: Jeff Spaleta <jspaleta(a)gmail.com>
>Reply-To: For testers of Fedora Core development releases
>To: For testers of Fedora Core development releases
>Subject: Re: Memory Bar
>Date: Mon, 2 Jan 2006 13:07:32 -0500
>On 1/2/06, Don Springall <don_springall(a)hotmail.com> wrote:
> > udev-078-3 seems to have problems mounting my memory bar again. I
> > this was working nicely for a while.
>since udev doesn't actually control "mounting" as i understand the
>verb...let's be clear... when you mean "problems mounting" at which
>point in the mounting process do you see a problem:
>1) no /dev/ entry created for the device on insertion
>this is udev, and you will see messages in /var/log/messages
>associated with the device being created within a few sections on
>inserting the usb device.
>2)no /etc/fstab entry created for the device
>this is hal
>3) no mountpoint created for the device in /media/
>this is hal
>4) no entry in the computer window in gnome
>this is gnome..nautilus or gamin specifically i think
>5) not mounting automatically in gnome
>this is gnome-volume-manager
>fedora-test-list mailing list
udev-078-3 seems to have problems mounting my memory bar again. I thought
this was working nicely for a while. I don't know if it was a coincidence
or not but as soon as I plugged it in the gnome volume manager also crashed.
My /usr/share/doc/HTML/index.html is still the old Core 4 release notes even
though I am running current rawhide release. Is there some package I can
install to update all the documentation to core 5 or does that take a fresh
For about a month I've been greeted by this message every time I log in.
Any suggestions? What's the correct bugzilla component?
Error activating XKB configuration.
It can happen under various circumstances:
- a bug in libxklavier library
- a bug in X server (xkbcomp, xmodmap utilities)
- X server with incompatible libxkbfile implementation
X server version data:
The X.Org Foundation
If you report this situation as a bug, please include:
- The result of xprop -root | grep XKB
- The result of gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
xprop -root |grep XKB:
_XKB_RULES_NAMES_BACKUP(STRING) = "xorg", "pc105", "us", "", ""
_XKB_RULES_NAMES(STRING) = "xorg", "pc105", "us", "", ""
gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd:
layouts = [us,bg phonetic]
model = pc105
overrideSettings = false
options = [grp grp:alts_toggle]
When I install non-Fedora RPMs I get:
error: %post(rpmname-n.n-n) scriptlet failed, exit status 255
Where rpmname is the RPM (e.g. W3C's Amaya, Real Player, etc.).
This seems to break the end of the install: the normal symlinks are
missing in the bin directory.
Is this a bug?