|
Bugzilla – Full Text Bug Listing |
| Summary: | yast2 PPD::cleanupLists memory corruption | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Forgotten User kAgYoS08kd <forgotten_kAgYoS08kd> |
| Component: | YaST2 | Assignee: | Michal Zugec <mzugec> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | suse-beta |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | SuSE Linux 10.0 | ||
| Whiteboard: | |||
| Found By: | Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | /var/log/YaST2/* | ||
|
Description
Forgotten User kAgYoS08kd
2006-05-13 20:57:30 UTC
Please don't only attach a backtrace but describe the problem, specially how it can be reproduced. How to reproduce: Open some command line, eg. xterm. Enter the invokation shown on line 8 in the first description by typing in the characters excluding the first >, or copy and paste it. You might need to press Enter. Now (gdb) appears. There enter the invokation shown on line 9 in the first description the same way. If you are not root, you need to enter the root password. Now the memory corruption takes place. Remark: "printer ncurses printer ncurses" is not needed, a single "printer ncurses" also does the memory corruption. Please attach /var/log/YaST2 as tarball. Does YaST only crash when using the ncurses interface? Does it only crash when calling the priniter module? Have you configured any printers? What does `hwinfo --printer' say? That's what I ment by reproducing, I can see that you called the module, however if this would not work in general, you can impress that it would've been fixed a long time ago. For YaST related bugs, we always need the ylogs, a backtrace is normally not required as YaST's logging is quite verbosive. Please reopen this report if you can provide the required information. YaST only crashes when calling the printer module. The printer module cashes in both ncurses and QT interface. It crashed the first time the printer module was invoked after installation of SuSE Linux 10.0, when no printer had been configured. It even crashes when I remove both parallel ports (disabling on-board parallel port and removing PCI parallel port card, and removing the cables to the printer). `hwinfo --printer' says nothing when all printers are removed, and says the following if they are connected: 13: Parallel 00.0: 10900 Printer [Created at parallel.154] Unique ID: ffnC.j2fGfujUQ30 Parent ID: YMnp.ecK7NLYWZ5D Hardware Class: printer Model: "Hewlett-Packard HP LaserJet 5L" Vendor: "Hewlett-Packard" Device: "HP LaserJet 5L" Device File: /dev/lp0 Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #9 (Parallel controller) 15: Parallel 00.0: 10900 Printer [Created at parallel.154] Unique ID: 6r1H.LzKKbu1WGa8 Parent ID: +X1u.ecK7NLYWZ5D Hardware Class: printer Model: "HEWLETT-PACKARD PSC 500" Vendor: "HEWLETT-PACKARD" Device: "PSC 500" Device File: /dev/lp1 Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #14 (Parallel controller) Created attachment 85086 [details]
/var/log/YaST2/*
Attached /var/log/YaST2 as tarball.
Michal, please have a look. I can't see anything bad. No y2error (with code <3>) cat y2log|cut -d' ' -f3|sort -u This is proabably cups problem. Klaus? Michal: Sorry, but no, I don't think it's a cups problem. No cups library call is involved in above trace. It's within in YaST2. It's similar to #214265 remove /var/lib/YaST2/ppd_db.ycp a start yast2 printer will rebuild that database *** This bug has been marked as a duplicate of bug 214265 *** |