Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.
https://bugzilla.redhat.com/show_bug.cgi?id=440580
Summary: no gpm mouse support in mc
Product: Fedora
Version: 8
Platform: All
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: mc
AssignedTo: jnovy(a)redhat.com
ReportedBy: stsp(a)aknet.ru
QAContact: extras-qa(a)fedoraproject.org
CC: fedora-triage-list(a)redhat.com,leonard-rh-
bugzilla@den.ottolander.nl,stsp@aknet.ru
+++ This bug was initially created as a clone of Bug #194593 +++
Description of problem:
Mouse doesn't work in mc. "ldd /usr/bin/mc" doesn't list libgpm,
so the mouse obviously is not expeced to work. This is quite bad,
unless I am missing something obvious.
Version-Release number of selected component (if applicable):
mc-4.6.1a-13.FC5
How reproducible:
Press the left mouse button and move the mouse. Only the gpm text
selection happens. You can't go to menu or move the mc cursor with
the mouse.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.
https://bugzilla.redhat.com/show_bug.cgi?id=456393
Summary: RFE: version of pgf in texlive is old
Product: Fedora
Version: 9
Platform: All
URL: http://sourceforge.net/projects/pgf/
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: texlive-texmf
AssignedTo: jnovy(a)redhat.com
ReportedBy: uckelman(a)nomic.net
QAContact: extras-qa(a)fedoraproject.org
CC: andreas.bierfert(a)lowlatency.de,fedora-triage-
list@redhat.com,pertusus@free.fr
+++ This bug was initially created as a clone of Bug #219146 +++
Description of problem:
Version 1.10 of pgf is packaged with texlive; the current version of pgf (2.0)
is two years newer and has far more features.
Version-Release number of selected component (if applicable):
texlive-texmf-2007-22.fc9.noarch
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.
https://bugzilla.redhat.com/show_bug.cgi?id=448758
Summary: Grub sometimes does not detect entire memory map
Product: Fedora
Version: 8
Platform: x86_64
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: grub
AssignedTo: pjones(a)redhat.com
ReportedBy: dustin.henning(a)prd-inc.com
QAContact: extras-qa(a)fedoraproject.org
CC: amyagi@gmail.com,dustin.henning@prd-
inc.com,eric.moret(a)gmail.com,fedora-triage-
list@redhat.com,jm@ish.de,mishu@piatafinanciara.ro,natha
n.robertson@gmail.com,rjones@redhat.com,sputhenp@redhat.
com,tru(a)pasteur.fr
+++ This bug was initially created as a clone of Bug #250299 +++
Description of problem:
Sometimes, grub does not recognize the entire e820 memory map, when the map is
not provided by the BIOS in the multiboot information data structure.
Ultimately, this appears to be an over-optimization by the compiler when
building grub, in combination with buggy BIOS.
The result is that some downstream kernels (in my particular case, the Xen
kernel) does not recognize all the memory available on a system.
Version-Release number of selected component (if applicable):
grub-0.97-13
How reproducible:
>From the lack of discussion on the Fedora and Xen mailing lists, I presume this
problem is rare in the real world, and may be hard to reproduce.
The machine this happens on for me is has two Dual-Core AMD Opteron 2210 w/16GB
of memory, using an American Megatrends BIOS. Upon boot on an unpatched grub,
Xen only recognizes slightly less than 4GB. The Multiboot information data
structure has flag for the mem_lower/mem_upper fields set (and Xen memory
detection matches the values in these fields), and does not have the flag for
memory map set.
Patch to fix problem:
--- grub-0.97/stage2/common.c.e820 2007-07-30 11:36:19.000000000 -0800
+++ grub-0.97/stage2/common.c 2007-07-30 11:36:55.000000000 -0800
@@ -142,6 +142,7 @@
init_bios_info (void)
{
#ifndef STAGE1_5
- unsigned long cont, memtmp, addr;
+ unsigned long memtmp, addr;
+ volatile unsigned long cont;
int drive;
#endif
-- Additional comment from peter.peltonen(a)gmail.com on 2007-08-14 08:56 EST --
I encountered the same problem with i386 and x86_64 CentOS5 + xen-enabled
kernels. Only 2,9GB of my 6GB RAM was recognized. Non-xen 64bit and 32bit
PAE-kernels saw the memory correctly. After patching grub with this patch and
reinstalling grub (not just the rpm -- grub has to be reinstalled from grub
prompt) all memory was recognized correctly.
-- Additional comment from dustin.henning(a)prd-inc.com on 2007-10-23 13:14 EST --
I too experienced this issue. The system in question was a Core 2 Quad E6600
with 8GiB on an Intel P965 Express chipset. Like the original reporter, this
system also utilizes an AMIBIOS.
In my case, only 3.2GiB was recognized prior to the patch, and the base (SMP)
kernel did not recognize the ful amount of memory until I added mem=10G to the
kernel arguments. Once the base (SMP) kernel was booted detecting 7.8GiB, the
problem did not reoccur when the kernel argument was removed. Said kernel
argument (and derivatives) had no effect on the xen kernels when placed after
either/both kernel lines (xen.gz and module vmlinuz).
-- Additional comment from nathan.robertson(a)gmail.com on 2008-02-07 09:49 EST --
I too an experiencing this issue on an AMD64 machine with 8GBs of memory. Does
anyone know if there is an updated Grub package with this patch applied?
-- Additional comment from eric.moret(a)gmail.com on 2008-02-14 09:25 EST --
Any progress in applying this patch? I too have this issue.
-- Additional comment from eric.moret(a)gmail.com on 2008-02-15 11:11 EST --
You can grab the fixed package at:
ftp://ftp.zouric.com/public/grub-0.97-14.x86_64.rpm
SRPMS at
ftp://ftp.zouric.com/public/grub-0.97-14.src.rpm
-- Additional comment from amyagi(a)gmail.com on 2008-02-15 11:29 EST --
(In reply to comment #5)
> You can grab the fixed package at:
> ftp://ftp.zouric.com/public/grub-0.97-14.x86_64.rpm
> SRPMS at
> ftp://ftp.zouric.com/public/grub-0.97-14.src.rpm
Thanks for making the patched grub available. According to your note on the
CentOS forum:
http://www.centos.org/modules/newbb/viewtopic.php?topic_id=12491&forum=38
you have fixed the problem on a Hetzner root server DS8000 ?
-- Additional comment from grover66(a)gmail.com on 2008-02-17 00:35 EST --
After installing the above grub rpm, you will have to run "grub-install
/dev/sda" (for example) to make it all work.
-Mike
-- Additional comment from eric.moret(a)gmail.com on 2008-03-20 02:41 EST --
(In reply to comment #6)
> you have fixed the problem on a Hetzner root server DS8000 ?
Yes, that is correct. I now have my 8Gb of RAM recognized on a Hetzner DS8000
-- Additional comment from steve(a)electricmint.com on 2008-05-07 02:18 EST --
(In reply to comment #5)
> You can grab the fixed package at:
> ftp://ftp.zouric.com/public/grub-0.97-14.x86_64.rpm
> SRPMS at
> ftp://ftp.zouric.com/public/grub-0.97-14.src.rpm
Many thank for this patch Eric, it's also allowed me to see the 6GB on
CentOS/Xen install on Core 2 Quad Acer.
Steve
-- Additional comment from drfatalis(a)hotmail.com on 2008-05-13 16:43 EST --
Hi there,
I've got a Dell 1900 with CentOS 5.1 64 bit and 4 GB ram.
Only 3 GB are recognized with kernel-xen-2.6.18-53.1.19.el5.
I've downloaded & installed grub-0.97-14.x86_64.rpm and did grub-
install /dev/sda.
But it did not help and I still got 3 GB recognized.
Can you please help me to fix this.
Thank you in advance.
-- Additional comment from fedora-triage-list(a)redhat.com on 2008-05-14 09:47
EST --
This message is a reminder that Fedora 7 is nearing the end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining and
issuing updates for Fedora 7. It is Fedora's policy to close all bug reports
from releases that are no longer maintained. At that time this bug will be
closed as WONTFIX if it remains open with a Fedora 'version' of '7'.
Package Maintainer: If you wish for this bug to remain open because you plan to
fix it in a currently maintained version, simply change the 'version' to a
later Fedora version prior to Fedora 7's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that we may
not be able to fix it before Fedora 7 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version of
Fedora please change the 'version' of this bug. If you are unable to change the
version, please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a more recent
Fedora release includes newer upstream software that fixes bugs or makes them
obsolete. If possible, it is recommended that you try the newest available
Fedora distribution to see if your bug still exists.
Please read the Release Notes for the newest Fedora distribution to make sure
it will meet your needs:
http://docs.fedoraproject.org/release-notes/
The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.
https://bugzilla.redhat.com/show_bug.cgi?id=453036
Summary: Build php-pecl-apc for EPEL 4
Product: Fedora EPEL
Version: el4
Platform: All
OS/Version: Linux
Status: NEW
Severity: low
Priority: low
Component: php-pecl-apc
AssignedTo: rpm(a)timj.co.uk
ReportedBy: rpm(a)timj.co.uk
QAContact: extras-qa(a)fedoraproject.org
CC: chabotc@xs4all.nl,fedora-triage-list@redhat.com
Build php-pecl-apc for EPEL 4
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.
https://bugzilla.redhat.com/show_bug.cgi?id=449200
Summary: Conflicts between libxslt-devel.x86_64 and libxslt-
devel.i386
Product: Fedora
Version: 9
Platform: x86_64
OS/Version: Linux
Status: NEW
Severity: medium
Priority: low
Component: libxslt
AssignedTo: veillard(a)redhat.com
ReportedBy: harald.berghoff(a)gmx.net
QAContact: extras-qa(a)fedoraproject.org
CC: fedora-triage-list(a)redhat.com
+++ This bug was initially created as a clone of Bug #313001 +++
+++ This bug was initially created as a clone of Bug #312991 +++
Description of problem:
On Fedora 9/x86-64, when libxslt causes conflicts. Any automated update fails
for this reason.
Version-Release number of selected component (if applicable):
libxslt-1.1.23-3.fc9.i386
libxslt-1.1.24-1.fc9.x86_64
How reproducible:
Every time.
Steps to Reproduce:
1. Install Fedora 9/x86-64
2. Have libxslt-1.1.23-3.fc9.i386 and libxslt-1.1.23-3.fc9.x86_64 installed
3. yum update libxslt
Actual results:
Transaction Check Error:
file /usr/bin/xslt-config from install of libxslt-devel-1.1.21-1.fc7
conflicts with file from package libxslt-devel-1.1.21-1.fc7
file /usr/share/man/man1/xsltproc.1.gz from install of
libxslt-1.1.24-1.fc9.i386 conflicts with file from package
libxslt-1.1.23-3.fc9.x86_64
Expected results:
The package should install without conflicts between 64 and 32 bit versions.
Additional info:
I already tried to remove the i386 Package, but i get several dependent package
which i don't wnat to remove.
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.
https://bugzilla.redhat.com/show_bug.cgi?id=451770
Summary: Cannot create bridged network for paravirtualized guest.
Product: Fedora
Version: 8
Platform: ia64
OS/Version: Linux
Status: NEW
Severity: high
Priority: low
Component: xen
AssignedTo: xen-maint(a)redhat.com
ReportedBy: sella(a)digital-genesis.com
QAContact: extras-qa(a)fedoraproject.org
CC: berrange(a)redhat.com,fedora-triage-
list@redhat.com,sella@digital-genesis.com
+++ This bug was initially created as a clone of Bug #386151 +++
Description of problem:
I cannot create a bridged network connection using either virt-manager or
virt-install. Virt-manager does not allow me to specify a shared interface
(paravirtualized guest) - the space contains no choices. When I try to create
the guest using virt-install, I specify --network briege:eth0 and get hotplug
errors of this type:
can't add vif1.0 to bridge eth0: Operation not supported
Version-Release number of selected component (if applicable):
xen-3.1.0-8.fc7.i386
libvirt-0.3.3-1.fc7.i386
How reproducible:
Always happens.
Steps to Reproduce:
1. virt-install -p -n fed8p -r 1000 -f /var/lib/xen/images/fed8p -s 8 -l
http://download.fedora.redhat.com/pub/fedora/linux/releases/8/Fedora/i386/o…
--os-type=linux --os-variant=generic26 --network bridge:eth0
2. Follow the installation sequence until the network setting step. Specify
dhcp and the boot will hang (and then return to the network set up question)
3.
Actual results:
Guest installation cannot get past the network set up question.
Expected results:
Normal installation
Additional info:
-- Additional comment from moose(a)quadruped.com on 2007-11-15 21:40 EST --
Created an attachment (id=260681)
--> (https://bugzilla.redhat.com/attachment.cgi?id=260681&action=view)
xend log of failed installation due to network problem
-- Additional comment from moose(a)quadruped.com on 2007-11-15 21:50 EST --
Created an attachment (id=260701)
--> (https://bugzilla.redhat.com/attachment.cgi?id=260701&action=view)
virt-install log of guest create that fails with network problem.
-- Additional comment from moose(a)quadruped.com on 2007-11-16 07:52 EST --
I should note that this is the i386 version of Fedora 7 running on x86_64
hardware (a Dell Precision 690). I see this problem regardless of SELinux
setting (I'
ve tried enforcing, permissive, and disabled - albeit without any reboots
between attempts).
-- Additional comment from moose(a)quadruped.com on 2007-11-16 22:30 EST --
Created an attachment (id=262081)
--> (https://bugzilla.redhat.com/attachment.cgi?id=262081&action=view)
Xend log from rebooted system reveals network bridge errors
I rebooted my machine and examined the xend log. Please note the errors
indicating failures to create network bridges. What do I have to do to avoid
these? Is this a known problem with Fedora 7, a problem with my platform, or
some obscure configuration error?
-- Additional comment from sella(a)digital-genesis.com on 2008-03-23 18:18 EST --
I've run into this issue on both Fedora 7 and Fedora 8. In both cases, it only
happens after I update the system with yum. It appears to be an issue with dbus
or how virt-manager works with it.
Using virt-manager to create new bridged Xen virtual machines works fine after a
fresh install. After I use yum to update the system I'm no longer able to create
virtual machines with bridged interfaces. Specifically, in virt-manager on the
"Connect to a Host" screen, the "Shared physical device" option has an empty
drop down for "device".
Below is a fix that worked for me with Fedora 8 (didn't try Fedora 7):
On the updated system, as root, mount the install DVD and change to the
directory containing your original set of RPMs ("Packages" with Fedora 8,
"Fedora" with Fedora 7), then reinstall the old RPMs for dbus, dbus-libs and
dbus-x11.
Example:
# cd /media/disk/Packages
# rpm -Uvh --oldpackage dbus-1.1.2-7.fc8.x86_64.rpm
dbus-libs-1.1.2-7.fc8.x86_64.rpm dbus-libs-1.1.2-7.fc8.i386.rpm
dbus-x11-1.1.2-7.fc8.x86_64.rpm
*NOTE: You may need to specify other packages if RPM complains about dependencies.
This fix is very similar to one mentioned for RHES5.1 here:
http://www.linuxquestions.org/questions/linux-enterprise-47/virt-manager-in…
There is also mention of the same issue in CentOS-5, which they resolve by
patching /usr/share/virt-manager/virtManager/connection.py. Description and
patch is here:
http://bugs.centos.org/view.php?id=2516
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.
Summary: enhance kickstart selection dialog to match anaconda
https://bugzilla.redhat.com/show_bug.cgi?id=183445
clumens(a)redhat.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |russell(a)coker.com.au
------- Additional Comments From clumens(a)redhat.com 2008-07-31 17:31 EST -------
*** Bug 445473 has been marked as a duplicate of this bug. ***
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.
Summary: poppler appears to be hit by CVE-2007-0104
https://bugzilla.redhat.com/show_bug.cgi?id=224448
michal(a)harddata.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |NEW
Flag|needinfo?(michal(a)harddata.co|
|m) |
------- Additional Comments From michal(a)harddata.com 2008-07-31 12:31 EST -------
"do you still believe this issue affects current versions of poppler".
It looks to me that notes in comment #8 show that this bug is
indeed fixed and it should be closed. It still not clear from the
above, nor from changelog, to which versions this may apply but I will
leave that to "owners".
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.
Summary: Support for Kolab annotations
https://bugzilla.redhat.com/show_bug.cgi?id=207654
dan(a)danny.cz changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |CLOSED
Resolution| |WONTFIX
Flag|needinfo?(gyurco(a)freemail.hu|
|) |
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.
Summary: Initscript Review
https://bugzilla.redhat.com/show_bug.cgi?id=247010
dan(a)danny.cz changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |CLOSED
Fixed In Version| |2.12.0
Resolution| |CURRENTRELEASE
--
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.