January 2007 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 232942] New: cups -opage-set={odd,even} prints every page
by bugzilla_noreply＠novell.com 10 Jan '07

10 Jan '07

https://bugzilla.novell.com/show_bug.cgi?id=232942 Summary: cups -opage-set={odd,even} prints every page Product: openSUSE 10.2 Version: RC 5 Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Printing AssignedTo: jsmeix(a)novell.com ReportedBy: jeffm(a)novell.com QAContact: jsmeix(a)novell.com My printer doesn't support duplex mode internally, so I end up having to print the odd pages, flipping the pages, and printing the even pages. lpr -opage-set=odd and lpr -opage-set=even are supposed to facilitate this, but both of them end up printing all the pages. -- Configure bugmail: https://bugzilla.novell.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 1

[Bug 232941] New: Clicking on new K-Menu start Kmail
by bugzilla_noreply＠novell.com 10 Jan '07

10 Jan '07

https://bugzilla.novell.com/show_bug.cgi?id=232941 Summary: Clicking on new K-Menu start Kmail Product: openSUSE 10.2 Version: Final Platform: i686 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE AssignedTo: kde-maintainers(a)suse.de ReportedBy: uli.2001(a)gmx.de QAContact: qa(a)suse.de The new K-Menu of Suse 10.2 has the following strange behaviour: When I open it, Kmail is started. I can see no reason why. Maybe it is relevant that I am using an IMAP address book. (Apparently this causes Kopete to start Kmail automatically.) -- Configure bugmail: https://bugzilla.novell.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 185042] YAST System Backup Tool To Tape Device
by bugzilla_noreply＠novell.com 10 Jan '07

10 Jan '07

https://bugzilla.novell.com/show_bug.cgi?id=185042 locilka(a)novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |harbrink(a)bluewin.ch -- Configure bugmail: https://bugzilla.novell.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 0

[Bug 185042] YAST System Backup Tool To Tape Device
by bugzilla_noreply＠novell.com 10 Jan '07

10 Jan '07

https://bugzilla.novell.com/show_bug.cgi?id=185042 locilka(a)novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |locilka(a)novell.com |screening(a)forge.provo.novell| |.com | Status|NEW |ASSIGNED ------- Comment #8 from locilka(a)novell.com 2007-01-10 01:55 MST ------- I see (even if there is nothing in the log file, I'm afraid), backup is saved to /dev/nst0 but the autoprofile (system-configuration export) tries to save the current configuration into /dev/nst0.xml (or something similar). 1.) Unfortunately, it is not possible to include that XML file into a regular archive (because, for instance, that XML file contains names of archives) 2.) This file can be appended to the tape only if it is not rewindable (/dev/nst0 vs. /dev/st0) To be honest, I'm not sure about the correct solution of this issue right now. It would be possible to create and save the autoprofile (append) to a non-rewindable tape and to, let say, ~/.yast-backup/ directory if the tape is rewindable. Or just save it there always when backup destination is under the /dev/ directory... Also maybe the autoprofile (but without names of archives) could be created before the real backup starts and included in the first backup but this would cost a lot of development effort. What do you think of that? Do you have any better idea? -- Configure bugmail: https://bugzilla.novell.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 0

[Bug 227873] New: ata_piix tries to access non-existent ports
by bugzilla_noreply＠novell.com 10 Jan '07

10 Jan '07

https://bugzilla.novell.com/show_bug.cgi?id=227873 Summary: ata_piix tries to access non-existent ports Product: openSUSE 10.2 Version: Final Platform: i586 OS/Version: Linux Status: NEW Severity: Minor Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: grok(a)tnt.pl QAContact: qa(a)suse.de This seems like a hardware bug, not a kernel bug really, but here it goes: On Dell Optiplex 745 machines (Dec2006) there are two SATA controlers 00:1f.2 IDE interface: Intel Corporation 82801H (ICH8 Family) 4 port SATA IDE Controller (rev 02) 00:1f.5 IDE interface: Intel Corporation 82801H (ICH8 Family) 2 port SATA IDE Controller (rev 02) visible via lspci. The first one works like expected and is visible in the BIOS (can be disabled etc.). Unfortunately, the BIOS does not allow disabling ata3 and ata4 (there are simply no SATA-2 and SATA-3 options in the bios). In effect the following happends on boot: PCI: Setting latency timer of device 0000:00:1f.5 to 64 ata3: SATA max UDMA/133 cmd 0xFE40 ctl 0xFE52 bmdma 0xFED0 irq 201 ata4: SATA max UDMA/133 cmd 0xFE60 ctl 0xFE72 bmdma 0xFED8 irq 201 scsi2 : ata_piix ata3: port is slow to respond, please be patient (Status 0xff) ata3: port failed to respond (30 secs, Status 0xff) ata3: SRST failed (status 0xFF) ata3: SRST failed (err_mask=0x100) ata3: softreset failed, retrying in 5 secs ata3: SRST failed (status 0xFF) ata3: SRST failed (err_mask=0x100) ata3: softreset failed, retrying in 5 secs ata3: SRST failed (status 0xFF) ata3: SRST failed (err_mask=0x100) ata3: reset failed, giving up scsi3 : ata_piix ata4: port is slow to respond, please be patient (Status 0xff) ata4: port failed to respond (30 secs, Status 0xff) ata4: SRST failed (status 0xFF) ata4: SRST failed (err_mask=0x100) ata4: softreset failed, retrying in 5 secs ata4: SRST failed (status 0xFF) ata4: SRST failed (err_mask=0x100) ata4: softreset failed, retrying in 5 secs ata4: SRST failed (status 0xFF) ata4: SRST failed (err_mask=0x100) ata4: reset failed, giving up The hardware vendor has been notified about the problem. Still awaiting bios update. Proposed solution: Add bootoption to skip detection when status of the port is 0xff or don't try to detect ports with status 0xff (not sure if this is legit :). -- Configure bugmail: https://bugzilla.novell.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 6

[Bug 215300] New: nForce4 based motherboard unstable in SMP configuration
by bugzilla_noreply＠novell.com 10 Jan '07

10 Jan '07

https://bugzilla.novell.com/show_bug.cgi?id=215300 Summary: nForce4 based motherboard unstable in SMP configuration Product: SUSE Linux 10.1 Version: Final Platform: x86-64 OS/Version: SuSE Linux 10.1 Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: grok(a)tnt.pl QAContact: qa(a)suse.de Running an AMD Athlon 64 X2 Dual core with PCI-E based motherboard under -smp kernel causes the machine to be unstable. Suggested fix "pci=nommconf" does not help in the long term. The following configurations were tested: Motherboards: - ASUS A8N-SLI Premium - ASUS A8N-SLI Deluxe Graphic cards: - 2x nVidia Corporation GeForce 7800 GTX (both SLI and separate) - 1x nVidia Corporation GeForce 7950 GX2 Memory: - 2x 1GB (dual channel configuration) -- Configure bugmail: https://bugzilla.novell.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 28

[Bug 225699] New: Switch "Start menu style", click Apply -> dialog disappears
by bugzilla_noreply＠novell.com 10 Jan '07

10 Jan '07

https://bugzilla.novell.com/show_bug.cgi?id=225699 Summary: Switch "Start menu style", click Apply -> dialog disappears Product: openSUSE 10.3 Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: KDE AssignedTo: kde-maintainers(a)suse.de ReportedBy: mmarek(a)novell.com QAContact: qa(a)suse.de 1) Right click the KDE panel, select "Configure Panel..." 2) In "Menus", switch between KDE/SUSE "Start menu style" 3) Click "Apply" - this restarts the panel (?), but doesn't bring the dialog back, so "Apply" behaves like "OK" in this case. -- Configure bugmail: https://bugzilla.novell.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 223751] New: Konqueror crashes after deleting files
by bugzilla_noreply＠novell.com 10 Jan '07

10 Jan '07

https://bugzilla.novell.com/show_bug.cgi?id=223751 Summary: Konqueror crashes after deleting files Product: openSUSE 10.2 Version: RC 1 Platform: x86-64 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE AssignedTo: kde-maintainers(a)suse.de ReportedBy: markus.kriewald(a)web.de QAContact: qa(a)suse.de After deleting some files konqueror crashes. Not reproducible. Überprüfung der Systemkonfiguration beim Start deaktiviert. (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 47833704192048 (LWP 3901)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [KCrash handler] #5 0x00002b812103df6e in KFileMetaInfo::deref () from /opt/kde3/lib64/libkio.so.4 #6 0x00002b812103e071 in KFileMetaInfo::operator= () from /opt/kde3/lib64/libkio.so.4 #7 0x00002b8121068dcb in KFileItem::metaInfo () from /opt/kde3/lib64/libkio.so.4 #8 0x00002b812106902d in KFileItem::getToolTipText () from /opt/kde3/lib64/libkio.so.4 #9 0x00002b8126f78d9e in KonqFileTip::showTip () from /opt/kde3/lib64/libkonq.so.4 #10 0x00002b8126f78ef1 in KonqFileTip::qt_invoke () from /opt/kde3/lib64/libkonq.so.4 #11 0x00002b8121be9adc in QObject::activate_signal () from /usr/lib/qt3/lib64/libqt-mt.so.3 #12 0x00002b8121bea7b3 in QObject::activate_signal () from /usr/lib/qt3/lib64/libqt-mt.so.3 #13 0x00002b8121c08e35 in QTimer::event () from /usr/lib/qt3/lib64/libqt-mt.so.3 #14 0x00002b8121b92eb5 in QApplication::internalNotify () from /usr/lib/qt3/lib64/libqt-mt.so.3 #15 0x00002b8121b93c40 in QApplication::notify () from /usr/lib/qt3/lib64/libqt-mt.so.3 #16 0x00002b81215d8e38 in KApplication::notify () from /opt/kde3/lib64/libkdecore.so.4 #17 0x00002b8121b8950f in QEventLoop::activateTimers () from /usr/lib/qt3/lib64/libqt-mt.so.3 #18 0x00002b8121b4969d in QEventLoop::processEvents () from /usr/lib/qt3/lib64/libqt-mt.so.3 #19 0x00002b8121ba7963 in QEventLoop::enterLoop () from /usr/lib/qt3/lib64/libqt-mt.so.3 #20 0x00002b8121ba7812 in QEventLoop::exec () from /usr/lib/qt3/lib64/libqt-mt.so.3 #21 0x00002b8127602bd3 in kdemain () from /opt/kde3/lib64/libkdeinit_konqueror.so #22 0x0000000000407491 in QGList::~QGList () #23 0x0000000000407dc4 in QGList::~QGList () #24 0x0000000000408185 in QGList::~QGList () #25 0x00000000004091da in QGList::~QGList () #26 0x00002b8122b53ae4 in __libc_start_main () from /lib64/libc.so.6 #27 0x0000000000404a89 in QGList::~QGList () #28 0x00007fff8a119f28 in ?? () #29 0x0000000000000000 in ?? () -- Configure bugmail: https://bugzilla.novell.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 13

[Bug 190481] save_video_pci_state support for s2ram
by bugzilla_noreply＠novell.com 10 Jan '07

10 Jan '07

https://bugzilla.novell.com/show_bug.cgi?id=190481 ------- Comment #29 from andreas.hanke(a)gmx-topmail.de 2007-01-10 01:37 MST ------- (In reply to comment #27) > I commited slightly cleaned up version of the patch, it would be nice to test > if it still works. I've just built s2ram myself from sf.net CVS, and it does still work. (Btw. I had to add -lz to the makefile, -lpci seems to require that now.) (In reply to comment #28) > If this machine has an intel chipset, it is most likely an X bug. It's an Intel 855GM using the i810 driver. 2D and 3D acceleration are currently enabled. Is it useful to test with these disabled? > You could try if "-a3" or "-p -m" helps (-a3 would be preferred, > since it happens totally in kernel space). OK, will do that now. > Another note: Are you sure that you have no acpi_sleep boot parameter? > You can check this with "cat /proc/sys/kernel/acpi_video_flags", it must be 0. It is: # cat /proc/sys/kernel/acpi_video_flags 0 -- Configure bugmail: https://bugzilla.novell.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 0

[Bug 190481] save_video_pci_state support for s2ram
by bugzilla_noreply＠novell.com 10 Jan '07

10 Jan '07

https://bugzilla.novell.com/show_bug.cgi?id=190481 ------- Comment #28 from seife(a)novell.com 2007-01-10 01:31 MST ------- If this machine has an intel chipset, it is most likely an X bug. The intel X server is a bit "sensitive" to suspend. On many machines that worked with "-p -s" before, now "-p -m" works better. I have not heard of any thinkpad that has this problem. You could try if "-a3" or "-p -m" helps (-a3 would be preferred, since it happens totally in kernel space). Another note: Are you sure that you have no acpi_sleep boot parameter? You can check this with "cat /proc/sys/kernel/acpi_video_flags", it must be 0. -- Configure bugmail: https://bugzilla.novell.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 0