http://bugzilla.novell.com/show_bug.cgi?id=493152 User mzugec@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=493152#c2 Michal Zugec changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mzugec@novell.com AssignedTo|mzugec@novell.com |snwint@novell.com --- Comment #2 from Michal Zugec 2009-04-09 02:22:22 MDT --- It works fine for me (VirtualBox-2.2.0), so it's probably some kvm/hwinfo issue. Reassigned to hwinfo maintainer (I can only close as WORKSFORME) -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=493152 User coolo@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=493152#c4 Stephan Kulow changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|coolo@novell.com | AssignedTo|snwint@novell.com |yast2-maintainers@suse.de --- Comment #4 from Stephan Kulow 2009-04-09 04:59:39 MDT --- this has nothing to do with hwinfo and very likely not even with network. The UI stalls _completely_ - I can reproduce in just repeating the second stage. And looking at the processes, the main y2base is stuck in an endless loop shown by strace. Here is the screenshot of the backtrace -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=493152 User coolo@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=493152#c6 --- Comment #6 from Stephan Kulow 2009-04-09 05:04:28 MDT --- Created an attachment (id=284992) --> (http://bugzilla.novell.com/attachment.cgi?id=284992) Y2DEBUG=1 logfile -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=493152 User coolo@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=493152#c8 --- Comment #8 from Stephan Kulow 2009-04-09 05:53:13 MDT --- *** Bug 493246 has been marked as a duplicate of this bug. *** http://bugzilla.novell.com/show_bug.cgi?id=493246 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=493152 User varkoly@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=493152#c10 Peter Varkoly changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |mzugec@novell.com --- Comment #10 from Peter Varkoly 2009-04-14 04:34:44 MDT --- Why du you think it is my bug? I could not open the attachement #284991. The attachement #284992 does not contains any problems which concern one of my packages unless I've missed anything. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=493152 Michal Zugec changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|mzugec@novell.com | -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=493152 Stephan Kulow changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |yast2-maintainers@suse.de |ovo.novell.com | -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=493152 Martin Vidner changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #284991|image/png |image/pnm mime type| | Attachment #284991|file.png |file.pnm filename| | -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=493152 User mvidner@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=493152#c14 Martin Vidner changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mvidner@novell.com AssignedTo|mvidner@novell.com |pbaudis@novell.com --- Comment #14 from Martin Vidner 2009-04-17 09:23:45 MDT --- Workaround: when yast hangs, the main y2base process has 2 y2base children. Kill -9 both of them, then it will go on. I can reproduce it in the running system by: ( while true; do echo '`Execute(.target.bash_output, "date >&2")' | /usr/lib/YaST2/bin/y2base stdio scr ) # the parens enable ^Z + fg And then letting it run and sending it ^C randomly. The processes hang in futex(2), yet they have only a single thread (says gdb and /proc/PID/status). FWIW, to my knowledge the only part of YaST dealing with threads is these 3 files: http://svn.opensuse.org/svn/yast/trunk/libyui/src/YUI.h http://svn.opensuse.org/svn/yast/trunk/libyui/src/YUI.cc http://svn.opensuse.org/svn/yast/trunk/libyui/src/YUILog.cc -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=493152 User pbaudis@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=493152#c16 Petr Baudis changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |mvidner@novell.com --- Comment #16 from Petr Baudis 2009-04-17 09:49:46 MDT --- I'm not sure I understood your instructions correctly; am I supposed to be able to reproduce this on 11.1 too? If not, can you give me some host I can ssh to in order to reproduce this? Nothing relevant has changed in glibc recently either, so I don't think this is a bug in glibc; one never knows, though. :) -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=493152 User coolo@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=493152#c18 Stephan Kulow changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|mvidner@novell.com | --- Comment #18 from Stephan Kulow 2009-04-20 09:57:05 MDT --- Hi, I tried your test case on my own machine and I receive a backtrace that shows signal handler using malloc (indirectly): #0 __lll_lock_wait_private () at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:91 #1 0x00007f4cb3753927 in _L_lock_8582 () from /lib64/libc.so.6 #2 0x00007f4cb3752233 in realloc_check (oldmem=0x7f4cb3a2ea00, bytes=77, caller=0x7f4cb37c1fd8) at hooks.c:322 #3 0x00007f4cb37c1fd8 in *__GI___vasprintf_chk (result_ptr=0x7fffbea24e88, flags=1, format=0x7f4cb55bc1f8 "%s %s%s:%d %s%s", args=0x7fffbea24d70) at vasprintf_chk.c:90 #4 0x00007f4cb37c1ec3 in __asprintf_chk (result_ptr=0x7f4cb3a2ea00, flags=128, format=0x7f4cb37c1fd8 "I\211\aH\205�017\204\224") at asprintf_chk.c:34 #5 0x00007f4cb55b747e in y2_logfmt_common(bool, char const*, char const*, int, char const*, char const*, __va_list_tag*) () from /usr/lib64/liby2util.so.4 #6 0x00007f4cb55b9e13 in y2_vlogger_function(loglevel_t, char const*, char const*, int, char const*, char const*, __va_list_tag*) () from /usr/lib64/liby2util.so.4 #7 0x00007f4cb55ba0fe in y2_logger_function(loglevel_t, char const*, char const*, int, char const*, char const*, ...) () from /usr/lib64/liby2util.so4 #8 0x00007f4cb5c79fba in signal_handler(int) () from /usr/lib64/liby2.so.2 #9 <signal handler called> #10 0x00007f4cb377bddd in __libc_fork () at ../nptl/sysdeps/unix/sysv/linux/fork.c:130 #11 0x00007f4cb1b427cd in shellcommand(std::string const&, std::string const&) ---Type <return> to continue, or q <return> to quit--- () from /usr/lib64/YaST2/plugin/libpy2ag_system.so.2 This should not happen. I'm not sure if it's the bug at hand or just another problem, but it has to be fixed. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=493152 User mvidner@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=493152#c20 --- Comment #20 from Martin Vidner 2009-04-21 02:23:54 MDT --- Now I can reproduce it also on 11.1 :-/ taskset 1 sh -c "while true; do echo '\`Execute(.target.bash_output, \"date

&2\")' | /usr/lib/YaST2/bin/y2base stdio scr; done" .. and hitting ^C

-- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=493152 User coolo@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=493152#c22 --- Comment #22 from Stephan Kulow 2009-04-21 03:42:16 MDT --- OK, I think the signal handler bug is independent of this one - as I get the same problem with my hotfix removing the logging from signal handler. Now there are 3 y2base processes. One has two threads: the UI and the YCP thread. The UI thread waits for the YCP thread to finish a statement and the YCP thread waits for a fgets on a pipe opened. I think the one it waits for has this backtrace - hangs in futex_wait: PID: 3810 #0 0xffffe422 in __kernel_vsyscall () #1 0xb790ee63 in __lll_lock_wait_private () at ./nptl/sysdeps/unix/sysv/linux/i386/i486/lowlevellock.S:89 #2 0xb78bc41b in _L_lock_1671 () at tzset.c:138 #3 0xb78bc211 in __tz_convert (timer=0xbff75d10, use_localtime=1, tp=0xb798c360) at tzset.c:604 #4 0xb78ba8ef in *__GI_localtime (t=0xbff75d10) at localtime.c:43 #5 0xb7cdca98 in y2_logfmt_prefix (level=LOG_DEBUG) at y2log.cc:247 #6 0xb7cddd98 in y2_vlogger_blanik (level=LOG_DEBUG, component=0xb7073c82 "bash", file=0xb7073c9a "ShellCommand.cc", line=157, function=0xb7073d84 "shellcommand", format=0xb7073d04 "Exit status is %d", ap=0xbff76218 "\001") at y2log.cc:314 #7 0xb7cddfd7 in y2_logger_blanik (level=LOG_DEBUG, component=0xb7073c82 "bash", file=0xb7073c9a "ShellCommand.cc", line=157, func=0xb7073d84 "shellcommand", format=0xb7073d04 "Exit status is %d") at y2log.cc:173 #8 0xb7062d73 in shellcommand (command=@0xbff76a94, tempdir=@0xbff76a90) at ShellCommand.cc:157 #9 0xb706c064 in SystemAgent::Execute (this=0x8c60bf0, path=@0xbff76c60, value=@0xbff76c5c, arg=@0xbff76c58) at SystemAgent.cc:977 PID: 3809 #0 0xffffe422 in __kernel_vsyscall () #1 0xb78f2b2b in read () from /lib/libc.so.6 #2 0xb789939c in _IO_new_file_underflow (fp=0x979ef88) at fileops.c:598 #3 0xb789ad6b in _IO_default_uflow (fp=0x979ef88) at genops.c:440 #4 0xb789c1d8 in *__GI___uflow (fp=0x979ef88) at genops.c:394 #5 0xb788ec26 in _IO_getline_info (fp=0x979ef88, buf=0xbff762d8 "�b��,�\211�@�\230���\211�(yu\t�\217\230��\217\230�d", n=1023, delim=10, extract_delim=1, eof=0x0) at iogetline.c:74 #6 0xb788eb71 in _IO_getline (fp=0x979ef88, buf=0xbff762d8 "�b��,�\211�@�\230���\211�(yu\t�\217\230��\217\230�d", n=1023, delim=10, extract_delim=1) at iogetline.c:42 #7 0xb788d9ad in _IO_fgets (buf=0xbff762d8 "�b��,�\211�@�\230���\211�(yu\t�\217\230��\217\230�d", n=1024, fp=0x979ef88) at iofgets.c:58 #8 0xb7062700 in fgets (__stream=<value optimized out>, __n=<value optimized out>, __s=<value optimized out>) at /usr/include/bits/stdio2.h:255 #9 shellcommand (command=@0xbff76a94, tempdir=@0xbff76a90) at ShellCommand.cc:125 #10 0xb706c064 in SystemAgent::Execute (this=0x8c60bf0, path=@0xbff76c60, value=@0xbff76c5c, arg=@0xbff76c58) at SystemAgent.cc:977 PID: 3329, YCP thread #0 0xffffe422 in __kernel_vsyscall () #1 0xb78f2b2b in read () from /lib/libc.so.6 #2 0xb789939c in _IO_new_file_underflow (fp=0x979ef88) at fileops.c:598 #3 0xb789ad6b in _IO_default_uflow (fp=0x979ef88) at genops.c:440 #4 0xb789c1d8 in *__GI___uflow (fp=0x979ef88) at genops.c:394 #5 0xb788ec26 in _IO_getline_info (fp=0x979ef88, buf=0xbff762d8 "�b��,�\211�@�\230���\211�(yu\t�\217\230��\217\230�d", n=1023, delim=10, extract_delim=1, eof=0x0) at iogetline.c:74 #6 0xb788eb71 in _IO_getline (fp=0x979ef88, buf=0xbff762d8 "�b��,�\211�@�\230���\211�(yu\t�\217\230��\217\230�d", n=1023, delim=10, extract_delim=1) at iogetline.c:42 #7 0xb788d9ad in _IO_fgets (buf=0xbff762d8 "�b��,�\211�@�\230���\211�(yu\t�\217\230��\217\230�d", n=1024, fp=0x979ef88) at iofgets.c:58 #8 0xb70620a8 in fgets (__stream=<value optimized out>, __n=<value optimized out>, __s=<value optimized out>) at /usr/include/bits/stdio2.h:255 #9 shellcommand (command=@0xbff76a94, tempdir=@0xbff76a90) at ShellCommand.cc:67 PID: 3329, UI thread #0 0xffffe422 in __kernel_vsyscall () #1 0xb78fb3e1 in select () from /lib/libc.so.6 #2 0xb6e73140 in QEventDispatcherUNIX::select(int, fd_set*, fd_set*, fd_set*, timeval*) () from /usr/lib/libQtCore.so.4 #3 0xb651093b in ?? () from /usr/lib/libQtGui.so.4 #4 0xb6e7398f in QEventDispatcherUNIXPrivate::doSelect(QFlagsQEventLoop::ProcessEventsFlag, timeval*) () from /usr/lib/libQtCore.so.4 #5 0xb6e756b1 in QEventDispatcherUNIX::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib/libQtCore.so.4 #6 0xb6510cd2 in ?? () from /usr/lib/libQtGui.so.4 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=493152 User pbaudis@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=493152#c24 --- Comment #24 from Petr Baudis 2009-04-21 03:48:50 MDT --- This is again Yast bug - as POSIX writes: # A process shall be created with a single thread. If a multi-threaded process calls fork(), the new process shall contain a replica of the calling thread and its entire address space, possibly including the states of mutexes and other resources. Consequently, to avoid errors, the child process may only execute async-signal-safe operations until such time as one of the exec functions is called. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=493152 User coolo@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=493152#c26 --- Comment #26 from Stephan Kulow 2009-04-21 05:10:37 MDT --- That still wouldn't explain the deadlock of 3810. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=493152 User mvidner@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=493152#c28 --- Comment #28 from Martin Vidner 2009-04-21 06:04:25 MDT --- Created an attachment (id=287092) --> (http://bugzilla.novell.com/attachment.cgi?id=287092) nofancyfork.diff comment 24: this radical simplification of shellcommand() could help, at the expense of losing the early logging of stderr (we may log it after the child finishes. not in this patch yet) -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=493152 User coolo@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=493152#c30 --- Comment #30 from Stephan Kulow 2009-04-21 06:44:45 MDT --- Created an attachment (id=287104) --> (http://bugzilla.novell.com/attachment.cgi?id=287104) my patch -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=493152 User coolo@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=493152#c32 Stephan Kulow changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P1 - Urgent |P2 - High Severity|Blocker |Critical --- Comment #32 from Stephan Kulow 2009-04-22 02:54:22 MDT --- no longer blocking testing. It only blocks submission of new yast2-core packages from SVN. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=493152 User mvidner@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=493152#c34 Martin Vidner changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #34 from Martin Vidner 2009-04-27 08:11:58 MDT ---

the disabled logging affects these items: [...] Keeping open (downgraded) to resurrect that. Hopefully it can be done using signal-safe calls.

Reimplemented in yast2-core-2.18.9, r56997, submitreq 9427. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=493152 Stephan Kulow changed: What |Removed |Added ---------------------------------------------------------------------------- CC|mzugec@novell.com | Component|Installation |libzypp AssignedTo|mvidner@novell.com |zypp-maintainers@forge.prov | |o.novell.com QAContact|jsrain@novell.com |qa@suse.de -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=493152 User coolo@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=493152#c37 Stephan Kulow changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P1 - Urgent |P3 - Medium --- Comment #37 from Stephan Kulow 2009-05-27 06:21:32 MDT --- I tried to reproduce the issue but can't. I wait for gdb to return to working state and hope I catch it then. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=493152 User coolo@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=493152#c39 Stephan Kulow changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P3 - Medium |P1 - Urgent --- Comment #39 from Stephan Kulow 2009-07-28 06:02:54 MDT --- That's the backtrace I was able to retrieve: #0 0x00007f472445d999 in read () from /lib64/libc.so.6 #1 0x00007f4724408e58 in _IO_file_underflow () from /lib64/libc.so.6 #2 0x00007f47243fea77 in getdelim () from /lib64/libc.so.6 #3 0x00007f471c415027 in getline (__stream=<value optimized out>, __n=<value optimized out>, __lineptr=<value optimized out>) at /usr/include/bits/stdio.h:118 #4 zypp::externalprogram::ExternalDataSource::receiveLine (__stream=<value optimized out>, __n=<value optimized out>, __lineptr=<value optimized out>) at /usr/src/debug/libzypp-6.10.5/zypp/base/ExternalDataSource.cc:147 #5 0x00007f471c256ec5 in zypp::media::MediaAria2c::existsAria2cmd () at /usr/src/debug/libzypp-6.10.5/zypp/media/MediaAria2c.cc:79 #6 0x00007f471c21c505 in zypp::media::MediaAccess::open (this=0x41e95a0, url=@0x7fff3bf1a120, preferred_attach_point=@0x7fff3bf1ba60) at /usr/src/debug/libzypp-6.10.5/zypp/media/MediaAccess.cc:143 #7 0x00007f471c264777 in zypp::media::MediaManager::open (this=<value optimized out>, url=@0x7fff3bf1a120, preferred_attach_point=@0x7fff3bf1ba60) at /usr/src/debug/libzypp-6.10.5/zypp/media/MediaManager.cc:273 #8 0x00007f471c35beea in zypp::MediaSetAccess::getMediaAccessId (this=0x7fff3bf1ba40, medianr=1) at /usr/src/debug/libzypp-6.10.5/zypp/MediaSetAccess.cc:351 #9 0x00007f471c35c5dd in zypp::MediaSetAccess::provide(boost::function, zypp::OnMediaLocation const&, zypp::base::Flagszypp::MediaSetAccess::ProvideFileOption) (this=0x7fff3bf1ba40, op=<value optimized out>, resource=@0x4203cd0, options=<value optimized out>) at /usr/src/debug/libzypp-6.10.5/zypp/MediaSetAccess.cc:197 #10 0x00007f471c35dc7d in zypp::MediaSetAccess::provideFile (this=0x7fff3bf1ba40, resource=@0x4203cd0, options=<value optimized out>) at /usr/src/debug/libzypp-6.10.5/zypp/MediaSetAccess.cc:160 #11 0x00007f471c33bb14 in zypp::Fetcher::Impl::provideToDest (this=<value optimized out>, media=@0x7fff3bf1ba40, resource=@0x4203cd0, dest_dir=@0x7fff3bf1be20) at /usr/src/debug/libzypp-6.10.5/zypp/Fetcher.cc:558 #12 0x00007f471c33e27a in zypp::Fetcher::Impl::start(zypp::filesystem::Pathname const&, zypp::MediaSetAccess&, boost::function const&) (this=0x4244a50, dest_dir=<value optimized out>, media=<value optimized out>, progress_receiver=@0x7fff3bf1ad40) at /usr/src/debug/libzypp-6.10.5/zypp/Fetcher.cc:798 #13 0x00007f471c29dab1 in zypp::repo::yum::Downloader::download(zypp::MediaSetAccess&, zypp::filesystem::Pathname const&, boost::function const&) (this=0x4218340, media=<value optimized out>, dest_dir=@0x7fff3bf1be20, progressrcv=<value optimized out>) at /usr/src/debug/libzypp-6.10.5/zypp/repo/yum/Downloader.cc:129 #14 0x00007f471c39cd54 in zypp::RepoManager::refreshMetadata(zypp::RepoInfo const&, zypp::RepoManager::RawMetadataRefreshPolicy, boost::function const&) (this=0x7fff3bf1c230, info=@0x7fff3bf1c300, policy=<value optimized out>, progress=<value optimized out>) at /usr/src/debug/libzypp-6.10.5/zypp/RepoManager.cc:952 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=493152 User ma@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=493152#c41 Michael Andres changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |CLOSED Resolution| |FIXED --- Comment #41 from Michael Andres 2009-07-29 05:41:16 MDT --- Fixed in libzypp-6.11.4 Also removed the superfluous 'which aria2c' calls. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=493152 User coolo@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=493152#c43 Stephan Kulow changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |CLOSED Resolution| |FIXED --- Comment #43 from Stephan Kulow 2009-08-12 02:10:24 MDT --- this has nothing to do with this bug being fixed for 11.2! -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=493152 Stephan Binner changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |530260 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=493152 http://bugzilla.novell.com/show_bug.cgi?id=493152#c46 Swamp Workflow Management changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard|maint:released:11.1:27695 |maint:released:11.1:27695 | |maint:released:sle11-moblin | |20:31703 --- Comment #46 from Swamp Workflow Management 2010-03-23 14:11:54 UTC --- Update released for: yast2-core, yast2-core-debuginfo, yast2-core-debugsource, yast2-core-devel Products: SUSE-MOBLIN 2.0 (i386) SUSE-MOBLIN 2.0-DEBUG (i386) -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=493152 http://bugzilla.novell.com/show_bug.cgi?id=493152#c48 Swamp Workflow Management changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard|maint:released:11.1:27695 |maint:released:11.1:27695 |maint:released:sle11-moblin |maint:released:sle11-moblin |20:31703 |20:31703 |maint:released:sle11:31702 |maint:released:sle11:31702 | |maint:released:sle11-moblin | |21:31704 --- Comment #48 from Swamp Workflow Management 2010-08-16 11:27:40 UTC --- Update released for: yast2-core, yast2-core-debuginfo, yast2-core-debugsource, yast2-core-devel Products: SUSE-MOBLIN 2.1 (i386) SUSE-MOBLIN 2.1-DEBUG (i386) -- Configure bugmail: http://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=493152 https://bugzilla.novell.com/show_bug.cgi?id=493152#c50 Swamp Workflow Management changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard|maint:released:11.1:27695 |maint:released:11.1:27695 |maint:released:sle11-moblin |maint:released:sle11-moblin |20:31703 |20:31703 |maint:released:sle11:31702 |maint:released:sle11:31702 |maint:released:sle11-moblin |maint:released:sle11-moblin |21:31704 |21:31704 | |maint:released:sle10-sp4:42 | |976 --- Comment #50 from Swamp Workflow Management 2011-09-29 12:50:43 UTC --- Update released for: yast2-core, yast2-core-debuginfo, yast2-core-devel Products: SLE-DEBUGINFO 10-SP4 (i386, ia64, ppc, s390x, x86_64) SLE-DESKTOP 10-SP4 (i386, x86_64) SLE-SDK 10-SP4 (i386, ia64, ppc, s390x, x86_64) SLE-SERVER 10-SP4 (i386, ia64, ppc, s390x, x86_64) -- 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.