March 2009 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 385376] New: Package 'python' does not build correctly on PPC64
by bugzilla_noreply＠novell.com 30 Mar '09

30 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=385376 Summary: Package 'python' does not build correctly on PPC64 Product: openSUSE 10.2 Version: Final Platform: PowerPC-64 OS/Version: Linux Status: NEW Severity: Major Priority: P5 - None Component: Development AssignedTo: pth(a)novell.com ReportedBy: sergiodj(a)linux.vnet.ibm.com QAContact: qa(a)suse.de Found By: --- Hi, I'm currently trying to build the last version of Python's src.rpm (namely python-2.5-19.6.src.rpm) on a biarch machine (i.e., 64-bit kernel and mostly 32-bit userspace apps). The 32-bit build works properly: #> rpmbuild --target ppc -bb SPECS/python.spec << OK >> What happens is that, when I try to build it for PPC64, some errors occurs: #> rpmbuild --target ppc64 -bb SPECS/python.spec .. Requires(rpmlib): rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(CompressedFileNames) <= 3.0.4-1 Requires: python = 2.5 libc.so.6()(64bit) libc.so.6(GLIBC_2.3)(64bit) libc.so.6(GLIBC_2.4)(64bit) libpthread.so.0()(64bit) libpython2.5.so.1.0()(64bit) RPM build errors: File not found: /var/tmp/python-2.5-build/usr/lib64/python2.5/lib-dynload/_sqlite3.so Note that Python got compiled successfuly, and all the tests were done without errors. Only after that this error came up. I'd like to know what can be done to fix this. Actually, what's happening is that I don't have (and haven't found) the package sqlite3 for PPC64. I've also tried to build it from its src.rpm, but fell in another dependency case and gave up. Obs.: I've made a tiny modification on Python's spec file in order to be able to compile it for PPC64: --- SPECS/python.spec 2008-01-10 09:59:23.000000000 -0800 +++ SPECS/python.spec.new 2008-04-30 11:11:49.000000000 -0700 @@ -217,6 +217,9 @@ # use rpm_opt_flags ######################################## export OPT="$RPM_OPT_FLAGS" +%ifarch ppc64 ia64 +export CC="gcc -m64" +%endif ######################################## # regenerate ######################################## -- 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.

1 10

[Bug 477595] New: easy_install does not work out-of-the-box
by bugzilla_noreply＠novell.com 30 Mar '09

30 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=477595 Summary: easy_install does not work out-of-the-box Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86 OS/Version: openSUSE 11.1 Status: NEW Severity: Minor Priority: P5 - None Component: Development AssignedTo: pth(a)novell.com ReportedBy: novell(a)wayoverthere.com QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (compatible; Konqueror/4.2; Linux; X11; en-US, en) KHTML/4.2.0 (like Gecko) SUSE Trying to use easy_install (from python-setuptools) to install Python eggs doesn't work. It is trying to use /usr/local/lib/python2.6/site-packages, which doesn't exist. I was able to fix it with "mkdir -p /usr/local/lib/python2.6/site-packages/", but I'm sure either the python-devel or python-setuptools packages should have created that directory. Reproducible: Always Steps to Reproduce: 1. easy_install psyco (as root) 2. 3. Actual Results: /usr/lib/python2.6/site-packages/setuptools/package_index.py:7: DeprecationWarning: the md5 module is deprecated; use hashlib instead from md5 import md5 error: can't create or remove files in install directory The following error occurred while trying to add or remove files in the installation directory: [Errno 2] No such file or directory: '/usr/local/lib/python2.6/site-packages/test-easy-install-1643.pth' The installation directory you specified (via --install-dir, --prefix, or the distutils default setting) was: /usr/local/lib/python2.6/site-packages/ This directory does not currently exist. Please create it and try again, or choose a different installation directory (using the -d or --install-dir option). Expected Results: /usr/lib/python2.6/site-packages/setuptools/package_index.py:7: DeprecationWarning: the md5 module is deprecated; use hashlib instead from md5 import md5 Searching for psyco Reading http://pypi.python.org/simple/psyco/ Reading http://psyco.sourceforge.net/ Best match: psyco snapshot Downloading http://wyvern.cs.uni-duesseldorf.de/psyco/psyco-snapshot.tar.gz Processing psyco-snapshot.tar.gz Running psyco-dist/setup.py -q bdist_egg --dist-dir /tmp/easy_install-BvjvwO/psyco-dist/egg-dist-tmp-39unO9 PROCESSOR = 'i386' c/codegen.c:128: warning: ‘psyco_source_condition’ defined but not used c/codegen.c:748: warning: ‘integer_lshift’ defined but not used c/Objects/plistobject.c:116: warning: ‘PsycoList_SingletonNew’ defined but not used zip_safe flag not set; analyzing archive contents... psyco.__init__: module references __path__ Adding psyco 1.6 to easy-install.pth file Installed /usr/local/lib/python2.6/site-packages/psyco-1.6-py2.6-linux-i686egg Processing dependencies for psyco Finished processing dependencies for psyco I think (not 100% sure) that this problem existed in 11.0 also. -- 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.

1 3

[Bug 471280] New: OpenOffice 3.0.1 don't start
by bugzilla_noreply＠novell.com 30 Mar '09

30 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=471280 Summary: OpenOffice 3.0.1 don't start Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: openSUSE 11.1 Status: NEW Severity: Critical Priority: P5 - None Component: OpenOffice.org AssignedTo: bnc-team-ooo(a)forge.provo.novell.com ReportedBy: weigelt.bernd(a)web.de QAContact: kyu(a)novell.com Found By: --- User-Agent: Mozilla/5.0 (compatible; Konqueror/4.2; Linux) KHTML/4.2.0 (like Gecko) SUSE I have made an update to 00 3.0.1 today. OpenOffice show only 'Die Anwendung kann nicht gestartet werden' There is _no_ message by start at console, but i take strace -o oo.txt ooffice to follow the startproc Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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.

1 45

[Bug 490149] New: screen+emacs "pos1"/"end" keys don't work
by bugzilla_noreply＠novell.com 30 Mar '09

30 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=490149 Summary: screen+emacs "pos1"/"end" keys don't work Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: andi-nbz(a)firstfloor.org QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.7) Gecko/2009022800 SUSE/3.0.7-1.1.6 Firefox/3.0.7 screen emacs -nw -q and then go to a buffer and try to just to the end or the first line using the "pos1" or "end" keys This used to work in a pretty old distribution (10.2), but not anymore with 11.0 or 11.1 Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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.

1 0

[Bug 490145] New: pam_mount annoying/misleading default
by bugzilla_noreply＠novell.com 30 Mar '09

30 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=490145 Summary: pam_mount annoying/misleading default Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: andi-nbz(a)firstfloor.org QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.7) Gecko/2009022800 SUSE/3.0.7-1.1.6 Firefox/3.0.7 I use pam_mount to encrypt home directories. Since I updated from an older version which didn't have this crazy XML format for configuration I recreated the configuration based on the example pam_mount.conf.xml Then my desktop was always logged out when idle, killing my applications After a lot of debugging I found this line in the example configuration (without any comments!!!): <logout wait="2000" hup="0" term="1" kill="1" /> I fixed this now but: - Please add a comment clearly explaining what bad side effects such automatic logout has and that it's usually a bad idea. - Please disable this line in the example so that others do not fall into the same deathtrap Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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.

1 0

[Bug 490142] New: kernel: netfilter-ipv4options
by bugzilla_noreply＠novell.com 30 Mar '09

30 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=490142 Summary: kernel: netfilter-ipv4options Classification: openSUSE Product: openSUSE 11.2 Version: Alpha 0 Platform: All OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: jeffm(a)novell.com ReportedBy: jengelh(a)medozas.de QAContact: qa(a)suse.de CC: okir(a)novell.com, perex(a)novell.com Found By: Beta-Customer I noticed you added a ipv4options patch to Kernel:/HEAD. quoting series.conf: # anyone want to refresh this one? patches.suse/netfilter-ipv4options This was recently reworked and is available in Xtables-addons 1.13. So please remove it from series.conf. (Also if you think code needs a revamp, contact netfilter-devel.) Last but not least, it does not make sense to add it to the kernel if iptables.src.rpm does not have the corresponding parts. -- 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.

1 0

[Bug 465127] New: Logwatch does not run from cron
by bugzilla_noreply＠novell.com 30 Mar '09

30 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=465127 Summary: Logwatch does not run from cron Product: openSUSE 11.0 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: pth(a)novell.com ReportedBy: puzel(a)novell.com QAContact: qa(a)suse.de Found By: Development Running logwatch as root works OK. However, when ran from cron, it fails with the error: -- Can't exec "sendmail": No such file or directory at /usr/sbin/logwatch line 1017, <TESTFILE> line 2. Can't execute sendmail -t: No such file or directory -- Changing 'mailer' configuration option in '/usr/share/logwatch/default.conf/logwatch.conf' to contain full path to sendmail fixes the problem for me. Looking into factory version shows that it might suffer from this issue too, but I haven't tested it. -- 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.

1 7

[Bug 458593] New: system doesn't boot with root on md raid1
by bugzilla_noreply＠novell.com 30 Mar '09

30 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=458593 User cthiel(a)novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=458593#c435778 Summary: system doesn't boot with root on md raid1 Product: openSUSE 11.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: mmarek(a)novell.com ReportedBy: cthiel(a)novell.com QAContact: qa(a)suse.de Found By: --- Pasting from E-Mail: > Last night I installed 11.1 on a servr of mine (located in a remote > datacenter), where I usually use md raid1 on /dev/sda and /dev/sdb as /. > Unfortuantely, the server didn't boot after the first stage installation. > (I had booted it with kexec from the running 11.0.) > > Now, Hetzner (the datacenter folks) have a nice rescue system and a way to > reset your server, so I was able to log in and look around. By looking at > bugzilla, I figured, that mdadm wasn't working the way it should have been > working. A quick diff of mdadm in STABLE vs. the 11.1 version of mdadm > showed this diff: > > +Fri Dec 5 10:21:10 CET 2008 - hare(a)suse.de > + > +- Wait for udev to settle before continuing (bnc#435778) > + > +------------------------------------------------------------------- > +Fri Dec 5 06:18:44 CET 2008 - nfbrown(a)suse.de > + > +- boot.md : an exit status of '2' from "mdadm --assemble" > + should not be seen as failure by boot.md. > + It happens if one or more arrays is already > + assembled. > + (bnc#456028) > + > +------------------------------------------------------------------- > > I updated mdadm, rebuilt the initrd and rebootet the server -- now it boots > just fine! > > So, the question come down to: Shouldn't we make sure to release an update > of mdadm to 11.1? -- 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.

1 9

[Bug 461673] New: xen/kernel-xen on OpenSuse 11.1 not starting; OK on OpenSuse 11.0
by bugzilla_noreply＠novell.com 30 Mar '09

30 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=461673 User pgnet.trash+F(a)gmail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=461673#c1 Summary: xen/kernel-xen on OpenSuse 11.1 not starting; OK on OpenSuse 11.0 Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: openSUSE 11.1 Status: NEW Severity: Blocker Priority: P5 - None Component: Xen AssignedTo: cgriffin(a)novell.com ReportedBy: pgnet.trash+F(a)gmail.com QAContact: qa(a)suse.de Found By: Customer i've been successfully running a headless install of OpenSuse 11.0 + Xen 321 as a Xen Dom0 w/ multiple DomUs for quite awhile ... i just built up a new OpenSuse 11.1 + Xen 331 box. short story -- Xen Dom0 on 11.1 w/ RAID-1 is not working; not clear as to why not. drop back to same setup on v11.0 -- all's ok. i've now reproduced this on another box, so posting it as a bug (?). i'm happy to provide any info -- just need some guidance as to where to look .. here are the 'gory details': i've partitioned, as always, as RAID-1 across two disks, sda + sdb, each part1 150 MB, LinuxRaid part2 10 GB, LinuxRaid part3 *, LinuxRaid RAID-1 /dev/md0 = sda1 + sdb1, mount_pt = '/boot', ext3 /dev/md1 = sda2 + sdb2 Volume Group "System" Logical Volume "Swap", mount_pt = 'swap', 512 MB, Logical Volume "Root", mount_pt = '/', * /dev/md2 = sda3 + sdb3 with this setup, boot to non-xen kernel works perfectly, as it did on OpenSuse 11.0, uname -a Linux server 2.6.27.7-9-default #1 SMP 2008-12-04 18:10:04 +0100 x86_64 x86_64 x86_64 GNU/Linux lsb_release -r Release: 11.1 cat /etc/fstab /dev/md0 /boot ext3 acl,user_xattr 1 2 /dev/System/Root / ext3 acl,user_xattr 1 1 /dev/System/Swap swap swap defaults 0 0 proc /proc proc defaults 0 0 sysfs /sys sysfs noauto 0 0 debugfs /sys/kernel/debug debugfs noauto 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 dmesg | egrep -i "fs|mount" Mount-cache hash table entries: 256 ACPI: Checking initramfs for custom DSDT Unpacking initramfs... done VFS: Disk quotas dquot_6.5.1 usbcore: registered new interface driver usbfs EXT3 FS on dm-0, internal journal EXT3-fs: mounted filesystem with ordered data mode. EXT3 FS on md0, internal journal EXT3-fs: mounted filesystem with ordered data mode. EXT3 FS on dm-2, internal journal EXT3-fs: mounted filesystem with ordered data mode. EXT3 FS on dm-3, internal journal EXT3-fs: mounted filesystem with ordered data mode. df -H Filesystem Size Used Avail Use% Mounted on /dev/mapper/System-Root 13G 2.1G 9.8G 18% / udev 4.2G 160k 4.2G 1% /dev /dev/md0 152M 52M 92M 37% /boot next, i've installed zypper in -t pattern xen-server rpm -qa | grep -i xen kernel-xen-base-2.6.27.7-9.1 xen-libs-3.3.1_18494_03-1.8 xen-tools-3.3.1_18494_03-1.8 kernel-xen-2.6.27.7-9.1 kernel-xen-extra-2.6.27.7-9.1 xen-3.3.1_18494_03-1.8 on attempt to boot to xen kernel, it fails. @ boot console I see mention of '/var' not available scroll quickly by, and something about fsck.ext3 failing ... then i'm dumped @ a console prompt: "fsck failed for at lease one filesystem (not /). Please repair manually and reboot. The root file system is is already mounted read-write. Attention: Only CONTROL-D will reboot the system in this maintenance mode. Shutdown or reboot will not work. Give root passwod for login:" I enter the password ... "if: Expression Syntax. (none) /root # (none) /root # ls -ald /var /boot drwxr-xr-x 15 root root 4096 Dec 19 18:20 /var drwxr-xr-x 2 root root 4096 Dec 19 18:12 /boot (none) /root # ls /boot (none) /root # > Is it that boot is not mounted? > try mount /boot (none) /root # (none) /root # mount /boot "EXT3-fs: unable to read superblock mount: wrong fs type, bad option, bad superblock on /dev/md0" (none) /root # (none) /root # reboot ... which, despite the admonition above, DOES work ... checking, nothing is written to /var/log/xen/xend.log or /var/log/messages. rebooting to non-xen kernel, all is ok again. at the non-xen kernel system's prompt, checking, service xend start returns simply xend unused and, > xend ERROR Internal error: Could not obtain handle on privileged command interface (2 = No such file or directory) Traceback (most recent call last): File "/usr/sbin/xend", line 44, in <module> from xen.xend.server import SrvDaemon File "/usr/lib64/python2.6/site-packages/xen/xend/server/SrvDaemon.py", line 26, in <module> import relocate File "/usr/lib64/python2.6/site-packages/xen/xend/server/relocate.py", line 28, in <module> from xen.xend import XendDomain File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomain.py", line 35, in <module> from xen.xend import XendOptions, XendCheckpoint, XendDomainInfo File "/usr/lib64/python2.6/site-packages/xen/xend/XendCheckpoint.py", line 20, in <module> from xen.xend import balloon, sxp, image File "/usr/lib64/python2.6/site-packages/xen/xend/image.py", line 44, in <module> xc = xen.lowlevel.xc.xc() xen.lowlevel.xc.Error: (1, 'Internal error', 'Could not obtain handle on privileged command interface (2 = No such file or directory)') It was pointed out to me elsewhere that, > xend can't start on a non-xen kernel, it doesn't have /proc/xen/* etc. If true, then, I've clearly misread this @ http://en.opensuse.org/Installing_Xen3: "... Next you can activate the Xen daemon: /etc/init.d/xend start insserv –d xend Finally you have to reboot your system: reboot ..." which seems to me to imply that 'xend' can be started before rebooting into the xen kernel ... for debugging, I'm in the process of trying to communicate with the box via serial port to capture the Xen startup process output. no luck with serial comms -- yet ... -- 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.

1 23

[Bug 445874] New: Empathy can not connect to Google Talk
by bugzilla_noreply＠novell.com 30 Mar '09

30 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=445874 Summary: Empathy can not connect to Google Talk Product: openSUSE 11.1 Version: Beta 5 Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: mgonnelly(a)novell.com QAContact: qa(a)suse.de Found By: --- Created a Google Talk Account in empathy using all default settings. Fails to connect. mark@triona:~/Desktop> export EMPATHY_DEBUG=all mark@triona:~/Desktop> empathy (empathy:11705): tp-glib-DEBUG: tp_proxy_borrow_interface_by_id: 0x65f440: org.freedesktop.DBus DBusGProxy is 0x65f4b0 ** (empathy:11705): DEBUG: mission_control_get_presence_actual: MC not running. ** (empathy:11705): DEBUG: mission_control_get_presence_message_actual: MC not running. ** (empathy:11705): DEBUG: idle_nm_state_change_cb: New network state 3 ** (empathy:11705): DEBUG: empathy_idle_set_presence: Changing presence to (null) (2) ** (empathy:11705): DEBUG: create_salut_account: Try to add a salut account... ** (empathy:11705): DEBUG: create_salut_account: Failed to get self econtact: e_book_get_self: there was no self contact UID stored in gconf ** (empathy:11705): DEBUG: get_glade_file: Loading glade file /usr/share/empathy/empathy-main-window.glade ** (empathy:11705): DEBUG: mission_control_get_online_connections: MC not running. ** (empathy:11705): DEBUG: empathy_geometry_load: Loading window geometry: x:1431, y:0, w:243, h:325 ** (empathy:11705): DEBUG: empathy_main_window_show: Configuring window default size w:243, h:325 ** (empathy:11705): DEBUG: empathy_main_window_show: Configuring window default position x:1431, y:0 ** (empathy:11705): DEBUG: mission_control_get_tpconnection: MC not running. ** (empathy:11705): DEBUG: mission_control_get_connection_status: MC not running. ** (empathy:11705): DEBUG: get_glade_file: Loading glade file /usr/share/empathy/empathy-status-icon.glade (empathy:11705): tp-glib-DEBUG: tp_connection_init: 0x6b8580 (empathy:11705): tp-glib-DEBUG: tp_connection_constructor: Connecting to StatusChanged (empathy:11705): tp-glib-DEBUG: tp_proxy_borrow_interface_by_id: 0x6b8580: org.freedesktop.Telepathy.Connection DBusGProxy is 0x784a00 (empathy:11705): tp-glib-DEBUG: tp_connection_constructor: Calling GetStatus (empathy:11705): tp-glib-DEBUG: tp_connection_constructor: Returning 0x6b8580 (empathy:11705): tp-glib-DEBUG: tp_connection_call_when_ready: arranging callback later (empathy:11705): tp-glib-DEBUG: tp_proxy_invalidate: 0x6b8580: Disconnected: reason 2 (empathy:11705): tp-glib-DEBUG: tp_proxy_signal_connection_proxy_invalidated: 0x784a70: TpProxy 0x6b8580 invalidated (I have 0x6b8580): Disconnected: reason 2 (empathy:11705): tp-glib-DEBUG: _tp_connection_clean_up_handle_refs: 0x6b8580 (empathy:11705): tp-glib-DEBUG: cwr_invalidated: enter ** (empathy:11705): DEBUG: dispatcher_connection_invalidated_cb: Error: Disconnected: reason 2 (empathy:11705): tp-glib-DEBUG: tp_connection_got_status_cb: 0x6b8580 (empathy:11705): tp-glib-DEBUG: tp_connection_got_status_cb: 0x6b8580: GetStatus() failed with dbus-glib-error-quark 19 "Method "GetStatus" with signature "" on interface "org.freedesktop.Telepathy.Connection" doesn't exist " (empathy:11705): tp-glib-DEBUG: tp_connection_dispose: 0x6b8580 (empathy:11705): tp-glib-DEBUG: tp_proxy_dispose: 0x6b8580 (empathy:11705): tp-glib-DEBUG: tp_connection_finalize: 0x6b8580 (empathy:11705): tp-glib-DEBUG: tp_proxy_finalize: 0x6b8580 ** (empathy:11705): DEBUG: empathy_geometry_save: Saving window geometry: x:1431, y:0, w:243, h:325 ** (empathy:11705): DEBUG: empathy_geometry_save: Saving window geometry: x:1431, y:0, w:243, h:325 ** (empathy:11705): DEBUG: empathy_geometry_save: Saving window geometry: x:1431, y:0, w:243, h:325 -- 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.

1 30