triage November 2008

triage@lists.stg.fedoraproject.org

1 participants
327 discussions

[Bug 440580] New: no gpm mouse support in mc
by Red Hat Bugzilla 15 Dec '09

15 Dec '09

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.

1 8

[Bug 456393] New: RFE: version of pgf in texlive is old
by Red Hat Bugzilla 21 Oct '09

21 Oct '09

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.

1 7

[Bug 448758] New: Grub sometimes does not detect entire memory map
by Red Hat Bugzilla 12 Jan '09

12 Jan '09

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.

1 8

[Bug 453036] New: Build php-pecl-apc for EPEL 4
by Red Hat Bugzilla 04 Jan '09

04 Jan '09

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.

1 5

[Bug 208723] volume labels missing for Option boot via OpenFirmware
by Red Hat Bugzilla 30 Nov '08

30 Nov '08

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=208723 John Reiser <jreiser(a)bitwagon.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|8 |10 --- Comment #7 from John Reiser <jreiser(a)bitwagon.com> 2008-11-30 17:49:54 EDT --- Using the CD image Fedora-10-ppc-netinst.iso from torrent Fedora-10-ppc-CDs: On Fedora 10 and Fedora 9, the label under the Desktop icon is "PBOOT". On MacOS 10.4 and MacOS 10.5, the label under the Desktop icon is "10". Holding down the Option key while booting a PowerPC Apple Macintosh with Fedora-10-ppc-netinst.iso in the optical drive, then the boot choices show no text label under the icon of an optical drive (with Tux "inset".) For booting, I was expecting to see the text label "Fedora 10" displayed under the icon. "od -Ax -c" of Fedora-10-ppc-netinst.iso shows these interesting lines: ----- 008000 001 C D 0 0 1 001 \0 P P C 008010 008020 P B O O T 008030 008040 \0 \0 \0 \0 \0 \0 \0 \0 008230 F e 008240 d o r a 1 0 008250 * 008320 2 0 0 008a30 \0 \0 \0 \0 \0 \0 \0 \0 F 008a40 \0 e \0 d \0 o \0 r \0 a \0 \0 1 \0 0 008a50 \0 \0 \0 \0 \0 \0 \0 \0 * 008ae0 \0 \0 \0 \0 \0 \0 \0 \0 \0 ----- So: In this case, Gnome desktop takes the icon name from (32K+32+8), while MacOS 10 takes the icon name from either (32K+512+64+5) [as 8-bit chars] or from (32K+2560+64+13) [as 16-bit chars]. I am changing this Bugzilla report to be against Fedora 10. -- 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.

1 0

[Bug 189676] Synaptics driver not functioning when the h/w is a Synaptics-cPad
by Red Hat Bugzilla 30 Nov '08

30 Nov '08

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=189676 Mace Moneta <mmoneta(a)optonline.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mmoneta(a)optonline.net --- Comment #5 from Mace Moneta <mmoneta(a)optonline.net> 2008-11-30 17:13:55 EDT --- The Synaptics cPad is still not functioning in Fedora 10. The version on the bug should be updated. $ ls -l /dev/input/by-id/ total 0 lrwxrwxrwx 1 root root 9 2008-11-30 16:50 usb-Synaptics_Inc._Synaptics_cPad-event-mouse -> ../event4 lrwxrwxrwx 1 root root 9 2008-11-30 16:50 usb-Synaptics_Inc._Synaptics_cPad-mouse -> ../mouse1 $ lsusb -vvv -s 002:002 Bus 002 Device 002: ID 06cb:0003 Synaptics, Inc. HID Device Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass 0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x06cb Synaptics, Inc. idProduct 0x0003 HID Device bcdDevice 0.11 iManufacturer 1 iProduct 2 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 116 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 1 Boot Interface Subclass bInterfaceProtocol 2 Mouse iInterface 3 HID Device Descriptor: bLength 9 bDescriptorType 33 bcdHID 1.00 bCountryCode 0 Not supported bNumDescriptors 1 bDescriptorType 34 Report wDescriptorLength 50 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0003 1x 3 bytes bInterval 10 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 1 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 1 Boot Interface Subclass bInterfaceProtocol 2 Mouse iInterface 4 HID Device Descriptor: bLength 9 bDescriptorType 33 bcdHID 1.00 bCountryCode 0 Not supported bNumDescriptors 1 bDescriptorType 34 Report wDescriptorLength 132 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 10 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 2 bNumEndpoints 3 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 1 Boot Interface Subclass bInterfaceProtocol 2 Mouse iInterface 5 HID Device Descriptor: bLength 9 bDescriptorType 33 bcdHID 1.00 bCountryCode 0 Not supported bNumDescriptors 1 bDescriptorType 34 Report wDescriptorLength 23 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0020 1x 32 bytes bInterval 0 ** UNRECOGNIZED: 09 21 00 01 00 01 22 17 00 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0020 1x 32 bytes bInterval 0 ** UNRECOGNIZED: 09 21 00 01 00 01 22 84 00 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0008 1x 8 bytes bInterval 10 cannot read device status, Operation not permitted (1) -- 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.

1 0

[Bug 202022] slow (780KB/s) USB2.0 + VT82xxxx + yenta (cardbus pcmcia)
by Red Hat Bugzilla 30 Nov '08

30 Nov '08

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=202022 John Reiser <jreiser(a)bitwagon.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|8 |10 --- Comment #28 from John Reiser <jreiser(a)bitwagon.com> 2008-11-30 17:00:32 EDT --- However the VT82xxxx still is slow: kernel-2.6.27.5-117.fc10.i686 # echo 1 >/proc/sys/vm/drop_caches # time dd if=flash bs=32k of=/dev/null 6000+0 records in 6000+0 records out 196608000 bytes (197 MB) copied, 276.482 s, 711 kB/s 06:00.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 61) 06:00.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 61) 06:00.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 63) 06:00.0 0c03: 1106:3038 (rev 61) 06:00.1 0c03: 1106:3038 (rev 61) 06:00.2 0c03: 1106:3104 (rev 63) I am changing this Bugzilla report to be against Fedora 10. -- 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.

1 0

[Bug 202022] slow (780KB/s) USB2.0 + VT82xxxx + yenta (cardbus pcmcia)
by Red Hat Bugzilla 30 Nov '08

30 Nov '08

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=202022 --- Comment #27 from John Reiser <jreiser(a)bitwagon.com> 2008-11-30 16:48:35 EDT --- Works for me today under kernel-2.6.27.5-117.fc10.i686. # echo 1 >/proc/sys/vm/drop_caches # time dd if=flash bs=32k of=/dev/null 6000+0 records in 6000+0 records out 196608000 bytes (197 MB) copied, 16.8209 s, 11.7 MB/s 06:00.0 USB Controller: NEC Corporation USB (rev 44) 06:00.1 USB Controller: NEC Corporation USB 2.0 (rev 05) 06:00.0 0c03: 1033:0035 (rev 44) 06:00.1 0c03: 1033:00e0 (rev 05) 00:03.0 CardBus bridge: Texas Instruments PCI1420 PC card Cardbus Controller 00:03.1 CardBus bridge: Texas Instruments PCI1420 PC card Cardbus Controller 00:03.0 0607: 104c:ac51 00:03.1 0607: 104c:ac51 -- 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.

1 0

[Bug 449200] New: Conflicts between libxslt-devel.x86_64 and libxslt-devel.i386
by Red Hat Bugzilla 30 Nov '08

30 Nov '08

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.

1 2

[Bug 248793] make logout confirmation dialog go away!
by Red Hat Bugzilla 29 Nov '08

29 Nov '08

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=248793 Jonathan Kamens <jik(a)kamens.brookline.ma.us> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|8 |rawhide -- 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.

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

triage November 2008