https://bugzilla.novell.com/show_bug.cgi?id=330615#c1 JP Rosevear changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |joe_morris@ntm.org --- Comment #1 from JP Rosevear 2007-10-17 11:47:02 MST --- *** Bug 334546 has been marked as a duplicate of this bug. *** https://bugzilla.novell.com/show_bug.cgi?id=334546 -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=330615 Jarl Friis changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |184798 -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=330615#c4 --- Comment #4 from Cristian Rodriguez 2007-11-07 19:36:47 MST --- found an ugly workaround rpm -e cups-autoconfig and configure the printer manually with yast. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=330615#c6 --- Comment #6 from Jarl Friis 2007-11-21 13:14:41 MST --- When I run /usr/lib64/cups-autoconfig/cups-autoconfig --debug --add --migrate-hal-printers I see CUPS printer 'hp:/usb/OfficeJet_G85?serial=SGG15E2RV8VL' - 'officejetg85' Segmentation fault (core dumped) Then I run strace /usr/lib64/cups-autoconfig/cups-autoconfig --debug --add --migrate-hal-printers 1> /tmp/cups-autoconfig_out.txt 2> /tmp/cups-autoconfig_err.txt cups-autoconfig_out.txt is empty I will attach cups-autoconfig_err.txt When I run gdb /usr/lib64/cups-autoconfig/cups-autoconfig core I get GNU gdb 6.6.50.20070726-cvs Copyright (C) 2007 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "x86_64-suse-linux"... (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". Reading symbols from /usr/lib64/libglib-2.0.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/lib64/libglib-2.0.so.0 Reading symbols from /usr/lib64/libhal.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib64/libhal.so.1 Reading symbols from /usr/lib64/libusb-0.1.so.4... (no debugging symbols found)...done. Loaded symbols for /usr/lib64/libusb-0.1.so.4 Reading symbols from /lib64/libdl.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/libdl.so.2 Reading symbols from /lib64/libuuid.so.1... (no debugging symbols found)...done. Loaded symbols for /lib64/libuuid.so.1 Reading symbols from /lib64/libdbus-1.so.3...(no debugging symbols found)...done. Loaded symbols for /lib64/libdbus-1.so.3 Reading symbols from /usr/lib64/libcups.so.2... (no debugging symbols found)...done. Loaded symbols for /usr/lib64/libcups.so.2 Reading symbols from /lib64/libc.so.6...(no debugging symbols found)...done. Loaded symbols for /lib64/libc.so.6 Reading symbols from /lib64/ld-linux-x86-64.so.2... (no debugging symbols found)...done. Loaded symbols for /lib64/ld-linux-x86-64.so.2 Reading symbols from /lib64/libpthread.so.0...(no debugging symbols found)...done. Loaded symbols for /lib64/libpthread.so.0 Reading symbols from /usr/lib64/libssl.so.0.9.8... (no debugging symbols found)...done. Loaded symbols for /usr/lib64/libssl.so.0.9.8 Reading symbols from /usr/lib64/libcrypto.so.0.9.8...(no debugging symbols found)...done. Loaded symbols for /usr/lib64/libcrypto.so.0.9.8 Reading symbols from /lib64/libm.so.6... (no debugging symbols found)...done. Loaded symbols for /lib64/libm.so.6 Reading symbols from /lib64/libcrypt.so.1...(no debugging symbols found)...done. Loaded symbols for /lib64/libcrypt.so.1 Reading symbols from /lib64/libz.so.1... (no debugging symbols found)...done. Loaded symbols for /lib64/libz.so.1 Core was generated by `/usr/lib64/cups-autoconfig/cups-autoconfig --debug --add --migrate-hal-printers'. Program terminated with signal 11, Segmentation fault. #0 0x00002afc56400bd0 in strlen () from /lib64/libc.so.6 (gdb) where #0 0x00002afc56400bd0 in strlen () from /lib64/libc.so.6 #1 0x00002afc563d084d in vfprintf () from /lib64/libc.so.6 #2 0x00002afc56461680 in __vfprintf_chk () from /lib64/libc.so.6 #3 0x0000000000402864 in g_str_equal () #4 0x0000000000402e5f in g_str_equal () #5 0x0000000000404639 in g_str_equal () #6 0x00002afc563a8b54 in __libc_start_main () from /lib64/libc.so.6 #7 0x0000000000402229 in g_str_equal () #8 0x00007fff55894c18 in ?? () #9 0x0000000000000000 in ?? () I would love to install some debug rpms, but bug #335789 prevents me from doing so. Do you want the core file? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=330615#c8 --- Comment #8 from Jarl Friis 2007-11-21 13:22:53 MST --- The info needed is requested from Chris Rivera , however I comment #4 he has said he is now using a workaround. As a reporter of a duplicate of this bug (bug #335901), I have provided the needed info. Jarl -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=330615#c9 Chris Rivera changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |crrodriguez@novell.com --- Comment #9 from Chris Rivera 2007-12-03 08:23:06 MST --- I would like to actually fix the problem. Can you reattach he strace output? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=330615 User crrodriguez@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=330615#c11 --- Comment #11 from Cristian Rodriguez 2007-12-03 21:14:49 MST --- (In reply to comment #9 from Chris Rivera)

I would like to actually fix the problem. Can you reattach he strace output?

Chris: I dont have access to the affected system right now, however I will provide you the needed info as soon as I can, next week. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=330615 User crivera@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=330615#c13 --- Comment #13 from Chris Rivera 2007-12-04 12:15:46 MST --- (In reply to comment #12 from Jarl Friis)

(In reply to comment #11 from Cristian Rodriguez)

...

(In reply to comment #9 from Chris Rivera)

...

I would like to actually fix the problem. Can you reattach he strace output?

Chris: I dont have access to the affected system right now, however I will provide you the needed info as soon as I can, next week.

And again, what's missing in the info I provided in comment #6 and comment #7 ?

Jarl

The strace attachment in comment 7 has been removed. Also, you can grab the source packages and build the rpms with rpmbuild -ba. This will give you a debuginfo package that you can install (forcefully if necessary). -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=330615 User wolfgang@rosenauer.org added comment https://bugzilla.novell.com/show_bug.cgi?id=330615#c15 --- Comment #15 from Wolfgang Rosenauer 2007-12-16 11:55:19 MST --- Created an attachment (id=187780) --> (https://bugzilla.novell.com/attachment.cgi?id=187780) patch #0 0x00002b525fc8fbd0 in strlen () from /lib64/libc.so.6 #1 0x00002b525fc5f84d in vfprintf () from /lib64/libc.so.6 #2 0x00002b525fcf0680 in __vfprintf_chk () from /lib64/libc.so.6 #3 0x0000000000402864 in log_it (debug=1, fmt=0x404ebc "CUPS printer '%s' - '%s'\n") at cups-autoconfig.c:90 #4 0x0000000000402e5f in get_cups_printers (list=0x7fff4bfea238) at cups-autoconfig.c:873 #5 0x0000000000404639 in main (argc=1, argv=0x7fff4bfea388) at cups-autoconfig.c:1139 #6 0x00002b525fc37b54 in __libc_start_main () from /lib64/libc.so.6 #7 0x0000000000402229 in _start () g_vfprintf() modifies the va_list pointer so that the second call fails. Proposed patch attached. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=330615 User wolfgang@rosenauer.org added comment https://bugzilla.novell.com/show_bug.cgi?id=330615#c17 --- Comment #17 from Wolfgang Rosenauer 2007-12-16 12:08:18 MST --- And one more note: http://www.gnu.org/software/libc/manual/html_node/Variable-Arguments-Output.... says " In some other systems, the va_list pointer may become invalid after the call to vprintf, so you must not use va_arg after you call vprintf. Instead, you should call va_end to retire the pointer from service. However, you can safely call va_start on another pointer variable and begin fetching the arguments again through that pointer. Calling vprintf does not destroy the argument list of your function, merely the particular pointer that you passed to it. GNU C does not have such restrictions. You can safely continue to fetch arguments from a va_list pointer after passing it to vprintf, and va_end is a no-op. (Note, however, that subsequent va_arg calls will fetch the same arguments which vprintf previously used.) " That suggests that the crash shouldn't happen with gcc but it still does. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=330615 User crivera@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=330615#c19 Chris Rivera changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #19 from Chris Rivera 2007-12-17 13:34:13 MST --- I've submitted a fix for this to 10.3 and STABLE. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=330615 User jarl@softace.dk added comment https://bugzilla.novell.com/show_bug.cgi?id=330615#c21 --- Comment #21 from Jarl Friis 2008-01-21 14:02:25 MST --- (In reply to comment #20 from Jarl Friis)

I still get a the followin message on my AMD64 installation: hal-cups-autoco[8439] general protection rip:2b03b3021bd0 rsp:7ffff8c556e8 error:0

I see that my version is cups-autoconfig-0.1.0-27 and it has apparently been built sat 22 sep 2007 04:34:32 CEST and installed thu 04 okt 2007 22:28:22 CEST which is before your fix. Could it be that YOU has missed something? or is your fix in another package. Jarl -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=330615 User jarl@softace.dk added comment https://bugzilla.novell.com/show_bug.cgi?id=330615#c23 Jarl Friis changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | --- Comment #23 from Jarl Friis 2008-01-30 11:27:38 MST --- A fix is useless untill it is released. The status "FIXED" is uesless unless it reflects that the fix has been released. I suggest that you mark it fixed, when the fix is released. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=330615 User jarl@softace.dk added comment https://bugzilla.novell.com/show_bug.cgi?id=330615#c25 --- Comment #25 from Jarl Friis 2008-02-14 13:47:36 MST --- (In reply to comment #24 from Chris Rivera)

Sorry buddy, but you don't determine how our big fixing process works. I mark the bugs as fixed when they're fixed.

You are right, I don't determine the bug fixing process flow, I didn't try to do that either. I am sorry if that was what it looked like. By the way: Who do decide the bug process flow for this open community project known as OpenSuSE? Anyway. May I suggest a new state for bugs than has been fixed (development complete) but not yet released (as an online patch)? And in this particular case (this bug): When can expect the fix to be released? And how are we notified so we can test it? Jarl -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=330615 User wolfgang@rosenauer.org added comment https://bugzilla.novell.com/show_bug.cgi?id=330615#c27 --- Comment #27 from Wolfgang Rosenauer 2008-02-15 02:17:14 MST --- Bugzilla provides "keywords" which would fit quite well for that purpose. It would just need to be added to the patch process. Should be simply to automate between SWAMP and Bugzilla I think. (OT but as the other bug is internal...) -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=330615 User jarl@softace.dk added comment https://bugzilla.novell.com/show_bug.cgi?id=330615#c29 --- Comment #29 from Jarl Friis 2008-02-21 13:20:13 MST --- Any news as of when to see this fix in an online-update? Jarl -- 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.