[SOLVED] pacman -Syu update strikes again!

tasty_minerals · 2011-06-10 10:04:39

Several minutes back updated arch as usual. And apart from xterm and dillo I can't run anything.
chromium

[5734:5734:280761273:ERROR:browser_main.cc(910)] GLib-GObject: specified class size for type `GtkIMContextUIM' is smaller than the parent type's `GtkIMContext' 
class size
[5734:5734:280761665:ERROR:browser_main.cc(910)] GLib-GObject: specified instance size for type `UIMCandWinGtk' is smaller than the parent type's `GtkWindow' 
instance size
Segmentation fault

sakura

(sakura:10437): GLib-GObject-WARNING **: specified class size for type `GtkIMContextUIM' is smaller than the parent type's `GtkIMContext' class size
*** glibc detected *** sakura: malloc(): memory corruption: 0x0000000000978a40 ***

======= Backtrace: =========
/lib/libc.so.6(+0x7342a)[0x7f57dfb5d42a]
/lib/libc.so.6(+0x74e1a)[0x7f57dfb5ee1a]
/lib/libc.so.6(+0x75891)[0x7f57dfb5f891]
/lib/libc.so.6(__libc_memalign+0x93)[0x7f57dfb617a3]
/lib/libc.so.6(posix_memalign+0x59)[0x7f57dfb62909]
/usr/lib/libglib-2.0.so.0(+0x16e96)[0x7f57e00fce96]
/usr/lib/libglib-2.0.so.0(g_slice_alloc+0x5fa)[0x7f57e014404a]
/usr/lib/libglib-2.0.so.0(g_slice_alloc0+0x16)[0x7f57e01441a6]
/usr/lib/libgobject-2.0.so.0(g_type_create_instance+0x99)[0x7f57e0402539]
/usr/lib/libgobject-2.0.so.0(+0x1015c)[0x7f57e03e115c]
/usr/lib/libgobject-2.0.so.0(g_object_newv+0x892)[0x7f57e03e4102]
/usr/lib/libgobject-2.0.so.0(g_object_new+0xec)[0x7f57e03e4ccc]
/usr/lib/gtk-3.0/3.0.0/immodules/im-uim.so(im_module_create+0x46)[0x7f57d9d69686]
/usr/lib/libgtk-x11-2.0.so.0(+0x11e606)[0x7f57e0e5a606]
/usr/lib/libgtk-x11-2.0.so.0(+0x11eee9)[0x7f57e0e5aee9]
/usr/lib/libgtk-x11-2.0.so.0(+0x11ef28)[0x7f57e0e5af28]
/usr/lib/libvte.so.9(+0x26916)[0x7f57dfe6e916]
/usr/lib/libgobject-2.0.so.0(g_closure_invoke+0x15e)[0x7f57e03df1fe]
/usr/lib/libgobject-2.0.so.0(+0x1e815)[0x7f57e03ef815]
/usr/lib/libgobject-2.0.so.0(g_signal_emit_valist+0x88a)[0x7f57e03f97aa]
/usr/lib/libgobject-2.0.so.0(g_signal_emit+0x82)[0x7f57e03f9952]
/usr/lib/libgtk-x11-2.0.so.0(gtk_widget_realize+0x9e)[0x7f57e0f9277e]
/usr/lib/libgtk-x11-2.0.so.0(gtk_widget_map+0xf8)[0x7f57e0f92e68]
/usr/lib/libgtk-x11-2.0.so.0(+0x8432b)[0x7f57e0dc032b]
/usr/lib/libgtk-x11-2.0.so.0(+0xb8abf)[0x7f57e0df4abf]
/usr/lib/libgobject-2.0.so.0(g_closure_invoke+0xa9)[0x7f57e03df149]
/usr/lib/libgobject-2.0.so.0(+0x1e815)[0x7f57e03ef815]
/usr/lib/libgobject-2.0.so.0(g_signal_emit_valist+0x88a)[0x7f57e03f97aa]
/usr/lib/libgobject-2.0.so.0(g_signal_emit+0x82)[0x7f57e03f9952]
/usr/lib/libgtk-x11-2.0.so.0(gtk_widget_map+0xce)[0x7f57e0f92e3e]
/usr/lib/libgtk-x11-2.0.so.0(+0x159968)[0x7f57e0e95968]
/usr/lib/libgobject-2.0.so.0(g_closure_invoke+0xa9)[0x7f57e03df149]
/usr/lib/libgobject-2.0.so.0(+0x1e815)[0x7f57e03ef815]
/usr/lib/libgobject-2.0.so.0(g_signal_emit_valist+0x88a)[0x7f57e03f97aa]
/usr/lib/libgobject-2.0.so.0(g_signal_emit+0x82)[0x7f57e03f9952]
/usr/lib/libgtk-x11-2.0.so.0(gtk_widget_map+0xce)[0x7f57e0f92e3e]
/usr/lib/libgtk-x11-2.0.so.0(+0x2676aa)[0x7f57e0fa36aa]
/usr/lib/libgobject-2.0.so.0(g_closure_invoke+0x15e)[0x7f57e03df1fe]
/usr/lib/libgobject-2.0.so.0(+0x1e815)[0x7f57e03ef815]
/usr/lib/libgobject-2.0.so.0(g_signal_emit_valist+0x88a)[0x7f57e03f97aa]
/usr/lib/libgobject-2.0.so.0(g_signal_emit+0x82)[0x7f57e03f9952]
/usr/lib/libgtk-x11-2.0.so.0(gtk_widget_map+0xce)[0x7f57e0f92e3e]
/usr/lib/libgtk-x11-2.0.so.0(+0x261190)[0x7f57e0f9d190]
/usr/lib/libgobject-2.0.so.0(g_closure_invoke+0x15e)[0x7f57e03df1fe]
/usr/lib/libgobject-2.0.so.0(+0x1e815)[0x7f57e03ef815]
/usr/lib/libgobject-2.0.so.0(g_signal_emit_valist+0x88a)[0x7f57e03f97aa]
/usr/lib/libgobject-2.0.so.0(g_signal_emit+0x82)[0x7f57e03f9952]
/usr/lib/libgtk-x11-2.0.so.0(gtk_widget_show+0x86)[0x7f57e0f93736]
sakura[0x40a55c]
sakura(main+0x104a)[0x40be3a]
/lib/libc.so.6(__libc_start_main+0xed)[0x7f57dfb0af6d]
sakura[0x405599]
======= Memory map: ========
00400000-0040f000 r-xp 00000000 08:06 295413                             /usr/bin/sakura
0060f000-00610000 rw-p 0000f000 08:06 295413                             /usr/bin/sakura
007f9000-00a46000 rw-p 00000000 00:00 0                                  [heap]
7f57d4000000-7f57d4021000 rw-p 00000000 00:00 0 
7f57d4021000-7f57d8000000 ---p 00000000 00:00 0 
7f57d8997000-7f57d89ac000 r-xp 00000000 08:06 280618                     /usr/lib/libgcc_s.so.1
7f57d89ac000-7f57d8bac000 ---p 00015000 08:06 280618                     /usr/lib/libgcc_s.so.1
7f57d8bac000-7f57d8bad000 rw-p 00015000 08:06 280618                     /usr/lib/libgcc_s.so.1
7f57d8bad000-7f57d8c70000 rw-p 00000000 00:00 0 
7f57d8c70000-7f57d8c72000 r-xp 00000000 08:06 272636                     /usr/lib/libgcroots.so.0.1.0
7f57d8c72000-7f57d8e71000 ---p 00002000 08:06 272636                     /usr/lib/libgcroots.so.0.1.0
7f57d8e71000-7f57d8e72000 rw-p 00001000 08:06 272636                     /usr/lib/libgcroots.so.0.1.0
7f57d8e72000-7f57d8e95000 r-xp 00000000 08:06 272638                     /usr/lib/libuim-scm.so.0.1.0
7f57d8e95000-7f57d9095000 ---p 00023000 08:06 272638                     /usr/lib/libuim-scm.so.0.1.0
7f57d9095000-7f57d9098000 rw-p 00023000 08:06 272638                     /usr/lib/libuim-scm.so.0.1.0
7f57d9098000-7f57d90ac000 r-xp 00000000 08:06 272639                     /usr/lib/libuim.so.7.1.0
7f57d90ac000-7f57d92ac000 ---p 00014000 08:06 272639                     /usr/lib/libuim.so.7.1.0
7f57d92ac000-7f57d92af000 rw-p 00014000 08:06 272639                     /usr/lib/libuim.so.7.1.0
7f57d92af000-7f57d92b5000 r-xp 00000000 08:06 278314                     /usr/lib/libcairo-gobject.so.2.11000.2
7f57d92b5000-7f57d94b5000 ---p 00006000 08:06 278314                     /usr/lib/libcairo-gobject.so.2.11000.2
7f57d94b5000-7f57d94b7000 rw-p 00006000 08:06 278314                     /usr/lib/libcairo-gobject.so.2.11000.2
7f57d94b7000-7f57d952c000 r-xp 00000000 08:06 280932                     /usr/lib/libgdk-3.so.0.0.11
7f57d952c000-7f57d972b000 ---p 00075000 08:06 280932                     /usr/lib/libgdk-3.so.0.0.11
7f57d972b000-7f57d972f000 rw-p 00074000 08:06 280932                     /usr/lib/libgdk-3.so.0.0.11
7f57d972f000-7f57d9730000 rw-p 00000000 00:00 0 
7f57d9730000-7f57d9b2c000 r-xp 00000000 08:06 280933                     /usr/lib/libgtk-3.so.0.0.11
7f57d9b2c000-7f57d9d2c000 ---p 003fc000 08:06 280933                     /usr/lib/libgtk-3.so.0.0.11
7f57d9d2c000-7f57d9d36000 rw-p 003fc000 08:06 280933                     /usr/lib/libgtk-3.so.0.0.11
7f57d9d36000-7f57d9d38000 rw-p 00000000 00:00 0 
7f57d9d5f000-7f57d9d74000 r-xp 00000000 08:06 394371                     /usr/lib/gtk-3.0/3.0.0/immodules/im-uim.so
7f57d9d74000-7f57d9f73000 ---p 00015000 08:06 394371                     /usr/lib/gtk-3.0/3.0.0/immodules/im-uim.so
7f57d9f73000-7f57d9f75000 rw-p 00014000 08:06 394371                     /usr/lib/gtk-3.0/3.0.0/immodules/im-uim.so
7f57d9f75000-7f57da0be000 r-xp 00000000 08:06 279142                     /usr/lib/libxml2.so.2.7.8
7f57da0be000-7f57da2bd000 ---p 00149000 08:06 279142                     /usr/lib/libxml2.so.2.7.8
7f57da2bd000-7f57da2c7000 rw-p 00148000 08:06 279142                     /usr/lib/libxml2.so.2.7.8
7f57da2c7000-7f57da2c8000 rw-p 00000000 00:00 0 
7f57da2c8000-7f57da300000 r-xp 00000000 08:06 290166                     /usr/lib/libcroco-0.6.so.3.0.1
7f57da300000-7f57da500000 ---p 00038000 08:06 290166                     /usr/lib/libcroco-0.6.so.3.0.1
7f57da500000-7f57da504000 rw-p 00038000 08:06 290166                     /usr/lib/libcroco-0.6.so.3.0.1
7f57da504000-7f57da538000 r-xp 00000000 08:06 283316                     /usr/lib/librsvg-2.so.2.34.0
7f57da538000-7f57da737000 ---p 00034000 08:06 283316                     /usr/lib/librsvg-2.so.2.34.0
7f57da737000-7f57da739000 rw-p 00033000 08:06 283316                     /usr/lib/librsvg-2.so.2.34.0
7f57da739000-7f57da73b000 r-xp 00000000 08:06 283317                     /usr/lib/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-svg.so
7f57da73b000-7f57da93a000 ---p 00002000 08:06 283317                     /usr/lib/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-svg.so
7f57da93a000-7f57da93b000 rw-p 00001000 08:06 283317                     /usr/lib/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-svg.so
7f57da93b000-7f57da947000 r-xp 00000000 08:06 287497                     /usr/lib/gtk-2.0/2.10.0/engines/libmist.so
7f57da947000-7f57dab47000 ---p 0000c000 08:06 287497                     /usr/lib/gtk-2.0/2.10.0/engines/libmist.so
7f57dab47000-7f57dab48000 rw-p 0000c000 08:06 287497                     /usr/lib/gtk-2.0/2.10.0/engines/libmist.so
7f57dab48000-7f57dab53000 r-xp 00000000 08:06 524524                     /lib/libnss_files-2.13.so
7f57dab53000-7f57dad52000 ---p 0000b000 08:06 524524                     /lib/libnss_files-2.13.so
7f57dad52000-7f57dad53000 r--p 0000a000 08:06 524524                     /lib/libnss_files-2.13.so
7f57dad53000-7f57dad54000 rw-p 0000b000 08:06 524524                     /lib/libnss_files-2.13.so
7f57dad54000-7f57db20a000 r--p 00000000 08:06 278153                     /usr/lib/locale/locale-archive
7f57db20a000-7f57db20f000 r-xp 00000000 08:06 274395                     /usr/lib/libXdmcp.so.6.0.0
7f57db20f000-7f57db40e000 ---p 00005000 08:06 274395                     /usr/lib/libXdmcp.so.6.0.0
7f57db40e000-7f57db40f000 rw-p 00004000 08:06 274395                     /usr/lib/libXdmcp.so.6.0.0
7f57db40f000-7f57db411000 r-xp 00000000 08:06 274409                     /usr/lib/libXau.so.6.0.0
7f57db411000-7f57db610000 ---p 00002000 08:06 274409                     /usr/lib/libXau.so.6.0.0
7f57db610000-7f57db611000 rw-p 00001000 08:06 274409                     /usr/lib/libXau.so.6.0.0
7f57db611000-7f57db638000 r-xp 00000000 08:06 265954                     /usr/lib/libexpat.so.1.5.2
7f57db638000-7f57db837000 ---p 00027000 08:06 265954                     /usr/lib/libexpat.so.1.5.2
7f57db837000-7f57db83a000 rw-p 00026000 08:06 265954                     /usr/lib/libexpat.so.1.5.2
7f57db83a000-7f57db84d000 r-xp 00000000 08:06 524341                     /lib/libresolv-2.13.so
7f57db84d000-7f57dba4d000 ---p 00013000 08:06 524341                     /lib/libresolv-2.13.so
7f57dba4d000-7f57dba4e000 r--p 00013000 08:06 524341                     /lib/libresolv-2.13.so
7f57dba4e000-7f57dba4f000 rw-p 00014000 08:06 524341                     /lib/libresolv-2.13.so
7f57dba4f000-7f57dba51000 rw-p 00000000 00:00 0 
7f57dba51000-7f57dba69000 r-xp 00000000 08:06 263672                     /usr/lib/libz.so.1.2.5
7f57dba69000-7f57dbc68000 ---p 00018000 08:06 263672                     /usr/lib/libz.so.1.2.5
7f57dbc68000-7f57dbc69000 rw-p 00017000 08:06 263672                     /usr/lib/libz.so.1.2.5
7f57dbc69000-7f57dbcd8000 r-xp 00000000 08:06 276147                     /usr/lib/libpixman-1.so.0.22.0
7f57dbcd8000-7f57dbed8000 ---p 0006f000 08:06 276147                     /usr/lib/libpixman-1.so.0.22.0
7f57dbed8000-7f57dbedd000 rw-p 0006f000 08:06 276147                     /usr/lib/libpixman-1.so.0.22.0
7f57dbedd000-7f57dbedf000 r-xp 00000000 08:06 524301                     /lib/libdl-2.13.so
7f57dbedf000-7f57dc0df000 ---p 00002000 08:06 524301                     /lib/libdl-2.13.so
7f57dc0df000-7f57dc0e0000 r--p 00002000 08:06 524301                     /lib/libdl-2.13.so
7f57dc0e0000-7f57dc0e1000 rw-p 00003000 08:06 524301                     /lib/libdl-2.13.so
7f57dc0e1000-7f57dc0fc000 r-xp 00000000 08:06 274458                     /usr/lib/libxcb.so.1.1.0
7f57dc0fc000-7f57dc2fb000 ---p 0001b000 08:06 274458                     /usr/lib/libxcb.so.1.1.0
7f57dc2fb000-7f57dc2fc000 rw-p 0001a000 08:06 274458                     /usr/lib/libxcb.so.1.1.0
7f57dc2fc000-7f57dc353000 r-xp 00000000 08:06 525007                     /lib/libncursesw.so.5.9
7f57dc353000-7f57dc552000 ---p 00057000 08:06 525007                     /lib/libncursesw.so.5.9
7f57dc552000-7f57dc557000 rw-p 00056000 08:06 525007                     /lib/libncursesw.so.5.9
7f57dc557000-7f57dc592000 r-xp 00000000 08:06 524588                     /lib/libpcre.so.0.0.1
7f57dc592000-7f57dc791000 ---p 0003b000 08:06 524588                     /lib/libpcre.so.0.0.1
7f57dc791000-7f57dc792000 rw-p 0003a000 08:06 524588                     /lib/libpcre.so.0.0.1
7f57dc792000-7f57dc7a9000 r-xp 00000000 08:06 524314                     /lib/libpthread-2.13.so
7f57dc7a9000-7f57dc9a9000 ---p 00017000 08:06 524314                     /lib/libpthread-2.13.so
7f57dc9a9000-7f57dc9aa000 r--p 00017000 08:06 524314                     /lib/libpthread-2.13.so
7f57dc9aa000-7f57dc9ab000 rw-p 00018000 08:06 524314                     /lib/libpthread-2.13.so
7f57dc9ab000-7f57dc9af000 rw-p 00000000 00:00 0 
7f57dc9af000-7f57dc9b6000 r-xp 00000000 08:06 539739                     /lib/librt-2.13.so
7f57dc9b6000-7f57dcbb5000 ---p 00007000 08:06 539739                     /lib/librt-2.13.so
7f57dcbb5000-7f57dcbb6000 r--p 00006000 08:06 539739                     /lib/librt-2.13.so
7f57dcbb6000-7f57dcbb7000 rw-p 00007000 08:06 539739                     /lib/librt-2.13.so
7f57dcbb7000-7f57dcbbb000 r-xp 00000000 08:06 265747                     /usr/lib/libgthread-2.0.so.0.2800.8Aborted

other apps output the same amount of trash.
I tried to reinstall gcc with deps (as it may stand for segmentation fault), reinstalled gtk, all to no avail.
Can somebody help me bring my system into condition after a typical arch-way update)?

Last edited by tasty_minerals (2011-06-12 09:36:50)

Ramses de Norre · 2011-06-10 10:20:39

Using testing?

Varg · 2011-06-10 10:22:23

What did you update ?
Might look at your pacman.log.

tasty_minerals · 2011-06-10 10:29:44

pacman.log

[2011-06-10 11:30] Running 'pacman -Syu'
[2011-06-10 11:30] synchronizing package lists
[2011-06-10 11:30] starting full system upgrade
[2011-06-10 11:37] upgraded glib2 (2.28.7-1 -> 2.28.8-1)
[2011-06-10 11:37] upgraded avahi (0.6.30-2 -> 0.6.30-3)
[2011-06-10 11:37] upgraded gcc-libs (4.6.0-5 -> 4.6.0-6)
[2011-06-10 11:37] upgraded boost-libs (1.46.1-2 -> 1.46.1-3)
[2011-06-10 11:38] upgraded chromium (11.0.696.77-1 -> 12.0.742.91-1)
[2011-06-10 11:38] upgraded coreutils (8.12-1 -> 8.12-2)
[2011-06-10 11:38] upgraded gcc (4.6.0-5 -> 4.6.0-6)
[2011-06-10 11:38] upgraded gcc-ada (4.6.0-5 -> 4.6.0-6)
[2011-06-10 11:38] upgraded gcc-fortran (4.6.0-5 -> 4.6.0-6)
[2011-06-10 11:38] upgraded gcc-objc (4.6.0-5 -> 4.6.0-6)
[2011-06-10 11:38] upgraded gtk3 (3.0.10-2 -> 3.0.11-1)
[2011-06-10 11:38] upgraded openjdk6 (6.b22_1.10.1-2 -> 6.b22_1.10.2-1)
[2011-06-10 11:38] upgraded icedtea-web (1.0.2-1 -> 1.1-2)
[2011-06-10 11:38] ATTENTION UDEV:
[2011-06-10 11:38] ---------------
[2011-06-10 11:38] Arch's custom blacklisting logic has been removed. MOD_AUTOLOAD and
[2011-06-10 11:38] blacklisting in MODULES no longer works.
[2011-06-10 11:38] See 'man modprobe.conf' for a replacement to blacklisting.
[2011-06-10 11:38] To disable a module mod1 on the kernel command line, use
[2011-06-10 11:38] mod1.disable=1
[2011-06-10 11:38] or
[2011-06-10 11:38] modprobe.blacklist=mod1
[2011-06-10 11:38]   --
[2011-06-10 11:38] The following modules are no longer unconditionally loaded:
[2011-06-10 11:38]   pcspkr irtty-sir analog lp ppdev ide-generic
[2011-06-10 11:38] Add them to MODULES in rc.conf if you need them.
[2011-06-10 11:38] ---------------
[2011-06-10 11:38] upgraded udev (171-1 -> 171-2)
[2011-06-10 11:38] upgraded iproute2 (2.6.37-1 -> 2.6.38-3)
[2011-06-10 11:38] warning: /etc/inittab installed as /etc/inittab.pacnew
[2011-06-10 11:38] warning: /etc/rc.conf installed as /etc/rc.conf.pacnew
[2011-06-10 11:38] Blacklisting of modules is no longer supported in rc.conf,
[2011-06-10 11:38] please add blacklist entries to /etc/modprobe.d/ instead.
[2011-06-10 11:38] upgraded initscripts (2011.05.2-1 -> 2011.06.3-1)
[2011-06-10 11:38] upgraded inputproto (2.0.1-1 -> 2.0.2-1)
[2011-06-10 11:38] upgraded inxi (1.5.11-1 -> 1.6.5-1)
[2011-06-10 11:38] upgraded jfsutils (1.1.14-2 -> 1.1.15-2)
[2011-06-10 11:38] >>> Updating module dependencies. Please wait ...
[2011-06-10 11:38] >>> MKINITCPIO SETUP
[2011-06-10 11:38] >>> ----------------
[2011-06-10 11:38] >>> If you use LVM2, Encrypted root or software RAID,
[2011-06-10 11:38] >>> Ensure you enable support in /etc/mkinitcpio.conf .
[2011-06-10 11:38] >>> More information about mkinitcpio setup can be found here:
[2011-06-10 11:38] >>> http://wiki.archlinux.org/index.php/Mkinitcpio
[2011-06-10 11:38] 
[2011-06-10 11:38] >>> Generating initial ramdisk, using mkinitcpio.  Please wait...
[2011-06-10 11:38] ==> Building image "default"
[2011-06-10 11:38] ==> Running command: /sbin/mkinitcpio -k 2.6.38-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26.img
[2011-06-10 11:38] :: Begin build
[2011-06-10 11:38] :: Parsing hook [base]
[2011-06-10 11:39] :: Parsing hook [udev]
[2011-06-10 11:39] :: Parsing hook [autodetect]
[2011-06-10 11:39] :: Parsing hook [pata]
[2011-06-10 11:39] :: Parsing hook [scsi]
[2011-06-10 11:39] :: Parsing hook [sata]
[2011-06-10 11:39] :: Parsing hook [filesystems]
[2011-06-10 11:39] :: Generating module dependencies
[2011-06-10 11:39] :: Generating image '/boot/kernel26.img'...SUCCESS
[2011-06-10 11:39] ==> SUCCESS
[2011-06-10 11:39] ==> Building image "fallback"
[2011-06-10 11:39] ==> Running command: /sbin/mkinitcpio -k 2.6.38-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26-fallback.img -S autodetect
[2011-06-10 11:39] :: Begin build
[2011-06-10 11:39] :: Parsing hook [base]
[2011-06-10 11:39] :: Parsing hook [udev]
[2011-06-10 11:39] :: Parsing hook [pata]
[2011-06-10 11:39] :: Parsing hook [scsi]
[2011-06-10 11:39] :: Parsing hook [sata]
[2011-06-10 11:39] :: Parsing hook [filesystems]
[2011-06-10 11:40] :: Generating module dependencies
[2011-06-10 11:40] :: Generating image '/boot/kernel26-fallback.img'...SUCCESS
[2011-06-10 11:40] ==> SUCCESS
[2011-06-10 11:40] upgraded kernel26 (2.6.38.7-1 -> 2.6.38.8-1)
[2011-06-10 11:40] upgraded kernel26-headers (2.6.38.7-1 -> 2.6.38.8-1)
[2011-06-10 11:40] upgraded lib32-gcc-libs (4.6.0-5 -> 4.6.0-6)
[2011-06-10 11:40] upgraded libpurple (2.7.11-5 -> 2.8.0-1)
[2011-06-10 11:40] upgraded libwebkit (1.4.0-2 -> 1.4.1-1)
[2011-06-10 11:40] upgraded net-tools (1.60-14 -> 1.60-16)
[2011-06-10 11:40] installed lxmenu-data (0.1.1-1)
[2011-06-10 11:40] upgraded pcmanfm (0.9.8-5 -> 0.9.8-6)
[2011-06-10 11:40] upgraded pidgin (2.7.11-5 -> 2.8.0-1)
[2011-06-10 11:40] upgraded python2-sqlalchemy (0.7.0-1 -> 0.7.1-1)
[2011-06-10 11:40] upgraded qt (4.7.3-1 -> 4.7.3-3)
[2011-06-10 11:40] upgraded xfe (1.32.3-1 -> 1.32.4-1)

tasty_minerals · 2011-06-10 12:08:53

Ramses de Norre wrote:

Using testing?

I remember uncommenting some reps for skype and maybe something else.
if this is the case, how can I roll back the changes?

Ramses de Norre · 2011-06-10 14:40:26

tasty_minerals wrote:

Ramses de Norre wrote:
Using testing?
I remember uncommenting some reps for skype and maybe something else.
if this is the case, how can I roll back the changes?

Comment testing in /etc/pacman.conf and run

pacman -Suu

to downgrade all packages that are more current than their repo versions.

The Unabeefer · 2011-06-12 00:52:15

So, I have to downgrade 21 packages because 1 effed it up...

While I really DON'T MIND doing this, is there any way to know when this problem is fixed so people can resume using the testing repo? There are unrelated packages I prefer using.... it would be neat if there was a way besides upgrading, trying the one glibc-related issue to see if things bork still, and then downgrading again when they do.

BUT if that's the only way to find out when this issue is resolved, then I'm more than willing to do so.

Ramses de Norre · 2011-06-12 01:17:56

The Unabeefer wrote:

So, I have to downgrade 21 packages because 1 effed it up...
While I really DON'T MIND doing this, is there any way to know when this problem is fixed so people can resume using the testing repo? There are unrelated packages I prefer using.... it would be neat if there was a way besides upgrading, trying the one glibc-related issue to see if things bork still, and then downgrading again when they do.
BUT if that's the only way to find out when this issue is resolved, then I'm more than willing to do so.

It's called testing because those packages are intended to be tested. People usually test stuff of which they're not sure it works...
In other words, if you want to use testing, you'll have to deal with these breakages.

Edit: also, what's up with the all caps? That's generally interpreted as yelling and thus not very appropriate.

Last edited by Ramses de Norre (2011-06-12 01:19:17)

The Unabeefer · 2011-06-12 02:18:02

Ramses de Norre wrote:

The Unabeefer wrote:
So, I have to downgrade 21 packages because 1 effed it up...
While I really DON'T MIND doing this, is there any way to know when this problem is fixed so people can resume using the testing repo? There are unrelated packages I prefer using.... it would be neat if there was a way besides upgrading, trying the one glibc-related issue to see if things bork still, and then downgrading again when they do.
BUT if that's the only way to find out when this issue is resolved, then I'm more than willing to do so.
It's called testing because those packages are intended to be tested. People usually test stuff of which they're not sure it works...
In other words, if you want to use testing, you'll have to deal with these breakages.
Edit: also, what's up with the all caps? That's generally interpreted as yelling and thus not very appropriate.

Sorry, not intended as yelling. Just emphasis.

And yes, I like testing things, which is why I like using the testing repo. I just mean if there's some way to keep track of the packages specifically in the testing repo (RSS feed, or likewise) so I (and maybe others) can know when those specific screwy packages get an update, I'd very much like to know so I can test them to see if the bug gets fixed.

Otherwise, I will be commenting and un-commenting my pacman.conf every single day just to see if there's a version difference... and that can get obsessively time-consuming.

heleos · 2011-06-12 03:23:44

I know arch recommends you join a mailing list if you plan on using the testing repo, that may have all the packages

anonymous_user · 2011-06-12 04:36:42

Specifically, I think its the arch-dev-public mailing list that you should look into.

ANOKNUSA · 2011-06-12 06:20:09

The Unabeefer wrote:

Otherwise, I will be commenting and un-commenting my pacman.conf every single day just to see if there's a version difference... and that can get obsessively time-consuming.

So, uh... don't do that? Perhaps you should be grateful that you're using a rolling-release, bleeding-edge, binary-based distro that lets you easily downgrade in such situations. This lets you test things while filing and following bug reports to help make the distro stronger, so people less daring than you won't have to deal with the same issues when the packages get pushed to the mainstream repos. Gentoo, Slackware and the like let you use the same "pre-release" grade software that Arch does, yet our package manager and community (ARM) allow you to revert changes that cause breaks more quickly and easily than that of those distros. To be frank: if you're unhappy with the fact that using potentially unstable software gives you an unstable system, you're barking up the wrong tree. And believe me, this is coming from someone who learns all his "hacking" skills from regularly breaking his system hours before he has a school paper due.

tasty_minerals · 2011-06-12 09:35:44

uncommenting testing reps and running pacman -Syu didn't help, it simply didn't update anything but one unrelated app. So, anyway, thanks. I've reinstalled /dev/sdaX (

Last edited by tasty_minerals (2011-06-12 09:36:24)

schuay · 2011-06-12 09:51:19

tasty_minerals wrote:

uncommenting testing reps and running pacman -Syu didn't help, it simply didn't update anything but one unrelated app. So, anyway, thanks. I've reinstalled /dev/sdaX (

You need to run -Syuu to enable downgrading packages.

tasty_minerals · 2011-06-12 09:52:33

schuay wrote:

tasty_minerals wrote:
uncommenting testing reps and running pacman -Syu didn't help, it simply didn't update anything but one unrelated app. So, anyway, thanks. I've reinstalled /dev/sdaX (
You need to run -Syuu to enable downgrading packages.

ah, thanks, I will remember that.

The Unabeefer · 2011-06-12 18:55:41

ANOKNUSA wrote:

The Unabeefer wrote:
Otherwise, I will be commenting and un-commenting my pacman.conf every single day just to see if there's a version difference... and that can get obsessively time-consuming.
So, uh... don't do that? Perhaps you should be grateful that you're using a rolling-release, bleeding-edge, binary-based distro that lets you easily downgrade in such situations. This lets you test things while filing and following bug reports to help make the distro stronger, so people less daring than you won't have to deal with the same issues when the packages get pushed to the mainstream repos. Gentoo, Slackware and the like let you use the same "pre-release" grade software that Arch does, yet our package manager and community (ARM) allow you to revert changes that cause breaks more quickly and easily than that of those distros. To be frank: if you're unhappy with the fact that using potentially unstable software gives you an unstable system, you're barking up the wrong tree. And believe me, this is coming from someone who learns all his "hacking" skills from regularly breaking his system hours before he has a school paper due.

I never said I was ungrateful or unhappy about anything... (in fact, I *think* I said I really *don't mind* doing it if that was the only option) ... I just asked if there was another way to keep up with changes to the testing tree, since I am essentially forced to comment it out. If I don't comment it out, there's no way pacman will even *let* me update anything at all. I normally don't even care if there's a million bugs that crash xorg or my entire system (been crashing for 15 years on Slack and Gentoo), as long as I am able to update somehow when there's updates... but since I am not even able to do that, I have *no choice* but to block the testing repo out and downgrade until the issue is fixed.

And that's why I simply asked if there was a way (aside from up/down/up/down/up/down-grade) to keep an eye out for a fix. Looks like the mailing list was basically what I wanted, and I'm glad someone was able to inform me about that. Never even knew that existed!

Arch Linux

#1 2011-06-10 10:04:39

[SOLVED] pacman -Syu update strikes again!

#2 2011-06-10 10:20:39

Re: [SOLVED] pacman -Syu update strikes again!

#3 2011-06-10 10:22:23

Re: [SOLVED] pacman -Syu update strikes again!

#4 2011-06-10 10:29:44

Re: [SOLVED] pacman -Syu update strikes again!

#5 2011-06-10 12:08:53

Re: [SOLVED] pacman -Syu update strikes again!

#6 2011-06-10 14:40:26

Re: [SOLVED] pacman -Syu update strikes again!

#7 2011-06-12 00:52:15

Re: [SOLVED] pacman -Syu update strikes again!

#8 2011-06-12 01:17:56

Re: [SOLVED] pacman -Syu update strikes again!

#9 2011-06-12 02:18:02

Re: [SOLVED] pacman -Syu update strikes again!

#10 2011-06-12 03:23:44

Re: [SOLVED] pacman -Syu update strikes again!

#11 2011-06-12 04:36:42

Re: [SOLVED] pacman -Syu update strikes again!

#12 2011-06-12 06:20:09

Re: [SOLVED] pacman -Syu update strikes again!

#13 2011-06-12 09:35:44

Re: [SOLVED] pacman -Syu update strikes again!

#14 2011-06-12 09:51:19

Re: [SOLVED] pacman -Syu update strikes again!

#15 2011-06-12 09:52:33

Re: [SOLVED] pacman -Syu update strikes again!

#16 2011-06-12 18:55:41

Re: [SOLVED] pacman -Syu update strikes again!

Board footer