Bug#425742: gnome-session: deleting liferea from the session manually solved hanging for me

2007-06-07 Thread Balazs Ree
Package: gnome-session
Version: 2.18.2-1
Followup-For: Bug #425742


I am suffering from a similar case after a recent upgrade: session
freezes after the splash screen pops up. Recently I realized that in my
case the liferea application caused the problem. If I manually deleted
liferea from my session file, the problem went away. I am not sure if
this really helps investigating the general problem, but maybe it is
interesting information. I would suspect liferea interacts badly with
session loading and it may also be related with its usage of the 
notification tray.

My full session file (before deleting the entry) was:


[Default]
0,id=11c0a8011700011801832090076630002
0,RestartStyleHint=0
0,Program=gaim
0,CurrentDirectory=/home/ree
0,DiscardCommand=/bin/true 
0,CloneCommand=gaim 
0,RestartCommand=gaim --session 11c0a8011700011801832090076630002 
1,id=11c0a8011700011801832520076630003
1,RestartStyleHint=0
1,Program=gecko
1,CurrentDirectory=/home/ree
1,DiscardCommand=/bin/true 
1,CloneCommand=/usr/bin/liferea --mainwindow-state=hidden 
1,RestartCommand=/usr/bin/liferea --session 
11c0a8011700011801832520076630003 --mainwindow-state=hidden 
2,id=11c0a8011700011801829950073390002
2,RestartStyleHint=2
2,Priority=40
2,Program=nautilus
2,CurrentDirectory=/home/ree
2,CloneCommand=nautilus --sm-config-prefix /nautilus-ctwZbt/ 
2,RestartCommand=nautilus --sm-config-prefix /nautilus-ctwZbt/ --sm-client-id 
11c0a8011700011801829950073390002 --screen 0 --load-session 
/home/ree/.nautilus/saved-session-ZFMNST 
3,id=11c0a8011700011801829960073390006
3,Program=gnome-power-manager
3,CurrentDirectory=/home/ree
3,CloneCommand=gnome-power-manager --sm-config-prefix 
/gnome-power-manager-3BMumt/ 
3,RestartCommand=gnome-power-manager --sm-config-prefix 
/gnome-power-manager-3BMumt/ --sm-client-id 
11c0a8011700011801829960073390006 --screen 0 
4,id=11c0a8011700011801829960073390005
4,RestartStyleHint=1
4,Program=update-notifier
4,CurrentDirectory=/home/ree
4,CloneCommand=update-notifier --sm-config-prefix /update-notifier-UQqmlt/ 
4,RestartCommand=update-notifier --sm-config-prefix /update-notifier-UQqmlt/ 
--sm-client-id 11c0a8011700011801829960073390005 --screen 0 
5,id=11c0a801170001180182995007339
5,RestartStyleHint=1
5,Priority=40
5,Program=gnome-volume-manager
5,CurrentDirectory=/home/ree
5,CloneCommand=gnome-volume-manager --sm-config-prefix 
/gnome-volume-manager-o98mJt/ 
5,RestartCommand=gnome-volume-manager --sm-config-prefix 
/gnome-volume-manager-o98mJt/ --sm-client-id 
11c0a801170001180182995007339 --screen 0 
6,id=11c0a8011700011801832730076630004
6,Program=rhythmbox
6,CurrentDirectory=/home/ree
6,CloneCommand=rhythmbox --sm-config-prefix /rhythmbox-hk42Ht/ 
6,RestartCommand=rhythmbox --sm-config-prefix /rhythmbox-hk42Ht/ --sm-client-id 
11c0a8011700011801832730076630004 --screen 0 
7,id=11c0a8011700011801832060076630001
7,RestartStyleHint=0
7,Program=xchat-gnome
7,CurrentDirectory=/home/ree
7,CloneCommand=/usr/bin/xchat-gnome --sm-config-prefix /xchat-gnome-mi0Oax/ 
7,RestartCommand=/usr/bin/xchat-gnome --sm-config-prefix /xchat-gnome-mi0Oax/ 
--sm-client-id 11c0a8011700011801832060076630001 --screen 0 
8,id=11c0a8011700011801829960073390007
8,RestartStyleHint=2
8,Priority=50
8,Program=gnome-cups-icon
8,CurrentDirectory=/home/ree
8,CloneCommand=gnome-cups-icon --sm-config-prefix /gnome-cups-icon-Uxyltx/ 
8,RestartCommand=gnome-cups-icon --sm-config-prefix /gnome-cups-icon-Uxyltx/ 
--sm-client-id 11c0a8011700011801829960073390007 --screen 0 
9,id=11c0a8011700011801829950073390004
9,RestartStyleHint=2
9,Priority=5
9,Program=vino-session
9,CurrentDirectory=/home/ree
9,CloneCommand=vino-session --sm-config-prefix /vino-session-xCGPAx/ 
9,RestartCommand=vino-session --sm-config-prefix /vino-session-xCGPAx/ 
--sm-client-id 11c0a8011700011801829950073390004 --screen 0 
10,id=11c0a8011700011801829950073390001
10,RestartStyleHint=2
10,Priority=40
10,Program=gnome-panel
10,CurrentDirectory=/home/ree
10,CloneCommand=gnome-panel --sm-config-prefix /gnome-panel-CFZNFv/ 
10,RestartCommand=gnome-panel --sm-config-prefix /gnome-panel-CFZNFv/ 
--sm-client-id 11c0a8011700011801829950073390001 --screen 0 
11,id=11c0a801170001180183173390008
11,Program=gnome-terminal
11,CurrentDirectory=/home/ree
11,CloneCommand=gnome-terminal --sm-config-prefix /gnome-terminal-7UjPUw/ 
11,RestartCommand=gnome-terminal --sm-config-prefix /gnome-terminal-7UjPUw/ 
--sm-client-id 11c0a801170001180183173390008 --screen 0 
--window-with-profile-internal-id=Default --show-menubar 
--role=gnome-terminal-7609-279931778-1180183100 --working-directory /home/ree 
--zoom 1 --tab-with-profile-internal-id=Default --working-directory /home/ree 
--zoom 1 --tab-with-profile-internal-id=Default --working-directory /home/ree 
--zoom 1 --tab-with-profile-internal-id=Default --active --geometry 
80x24+714+462 --working-directory /home/ree --zoom 1 

Bug#373710: change back /lib/python2.4/site-packages to /lib/python

2006-06-18 Thread Balazs Ree
Hi Fabio,

2006. 06. 15, csütörtök keltezéssel 10.52-kor Fabio Tranchitella ezt
írta:
 ... Debian didn't changed the distribution path. Taken from
 debian/rules:

Confirmed that it should, indeed, be /lib/python.

 ./configure \
   --prefix=/usr/lib/$(ZOPE) \
   --with-python=$(PYTHONBIN) \
   --force
 $(PYTHONBIN) install.py build
 
 AFAIK, there is no Debian modification and the upstream build system,
 when called as above, will install under
 $PREFIX/lib/python2.4/site-packages.
 
 Do you have any suggestion/patch to workaround this behaviour, instead
 of exporting ZOPE_HOME inside the skeletons?

Yes. Please change --prefix to --home. I can not identify how the
difference is triggered exactly, but note that the original Makefile
also uses --home.

About my original proposal, the ZOPE_HOME export: it is not necessary
then, it seems however to be an upstream inconsistency, because if
ZOPE_HOME is not exported, what is the point of defining it at all. (Not
a Debian issue, just wanted to note it.)

Attached patch that resolves the correct /lib/python path in rules.
(Also please don't forget in addition to change the SOFTWARE_HOME paths
in all the skeletons too.) 

-- 
Balazs Ree
--- debian/rules	2006-06-18 13:45:43.0 +0200
+++ /tmp/rules	2006-06-18 13:30:37.0 +0200
@@ -84,7 +84,7 @@
 
 	# Install Zope and remove *.pyc
 	cd z  $(PYTHONBIN) install.py install \
-		--skip-build --prefix $(DEBIAN)/usr/lib/zope$(ZVER)
+		--skip-build --home $(DEBIAN)/usr/lib/zope$(ZVER)
 	find $(DEBIAN) -name '*.pyc' | xargs -r rm -r
 
 	# FHS enforcement
@@ -113,15 +113,15 @@
 	  fi; else  rm -f $$i~ ; fi ; \
 	done
 
-	rm $(DEBIAN)/usr/lib/zope2.9/lib/python2.4/site-packages/zope/formlib/LICENSE.txt \
-	   $(DEBIAN)/usr/lib/zope2.9/lib/python2.4/site-packages/Products/Five/COPYING.txt \
-	   $(DEBIAN)/usr/lib/zope2.9/lib/python2.4/site-packages/Products/Five/doc/ZopePublicLicense.txt \
-	   $(DEBIAN)/usr/lib/zope2.9/lib/python2.4/site-packages/docutils/COPYING.txt \
-	   $(DEBIAN)/usr/lib/zope2.9/lib/python2.4/site-packages/pytz/LICENSE.txt
-
-	chmod 755 $(DEBIAN)/usr/lib/zope2.9/lib/python2.4/site-packages/DocumentTemplate/release.sh \
-	  $(DEBIAN)/usr/lib/zope2.9/lib/python2.4/site-packages/ZPublisher/Client.py \
-	  $(DEBIAN)/usr/lib/zope2.9/lib/python2.4/site-packages/ZPublisher/Test.py
+	rm $(DEBIAN)/usr/lib/zope2.9/lib/python/zope/formlib/LICENSE.txt \
+	   $(DEBIAN)/usr/lib/zope2.9/lib/python/Products/Five/COPYING.txt \
+	   $(DEBIAN)/usr/lib/zope2.9/lib/python/Products/Five/doc/ZopePublicLicense.txt \
+	   $(DEBIAN)/usr/lib/zope2.9/lib/python/docutils/COPYING.txt \
+	   $(DEBIAN)/usr/lib/zope2.9/lib/python/pytz/LICENSE.txt
+
+	chmod 755 $(DEBIAN)/usr/lib/zope2.9/lib/python/DocumentTemplate/release.sh \
+	  $(DEBIAN)/usr/lib/zope2.9/lib/python/ZPublisher/Client.py \
+	  $(DEBIAN)/usr/lib/zope2.9/lib/python/ZPublisher/Test.py
 
 	chmod 644 $(DEBIAN)/usr/lib/zope2.9/bin/stats.py \
 	  $(DEBIAN)/usr/lib/zope2.9/bin/reindex_catalog.py \


signature.asc
Description: Ez az üzenetrész	 digitális aláírással van	ellátva


Bug#373710: zope2.9: zopectl test broken due to: ZOPE_HOME is not exported from zopectl, runzope skeletons

2006-06-15 Thread Balazs Ree
Package: zope2.9
Version: 2.9.3-2
Severity: normal


... and this, combined with the fact that Debian changed the
distribution path /lib/python to /lib/python2.4/site-packages, makes it
impossible to run tests from zopectl with instances created with these
skeletons.

This is because Zope startup scripts suppose that ZOPE_HOME is 2 levels down
from SOFTWARE_HOME, which would fail in Debian where it is in fact 3
levels down.

Since the ZOPE_HOME is forgotted from the export in the zopectl.in and
runzope.in skeletons, it is as if it were not defined when Zope is run.
The scripts will try to deduct ZOPE_HOME from SOFTWARE_HOME but it will
get one extra /lib path segment on the end.

Please put ZOPE_HOME in the export statement in the above mentioned
skeletons.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (600, 'unstable'), (50, 'experimental')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-1-amd64-k8
Locale: LANG=hu, LC_CTYPE=hu (charmap=UTF-8) (ignored: LC_ALL set to 
hu_HU.UTF-8)

Versions of packages zope2.9 depends on:
ii  debconf [debconf-2.0] 1.5.2  Debian configuration management sy
ii  libc6 2.3.6-15   GNU C Library: Shared libraries
ii  lsb-base  3.1-10 Linux Standard Base 3.1 init scrip
ii  python2.4 2.4.3-5An interactive high-level object-o
ii  zope-common   0.5.24 common settings and scripts for zo

zope2.9 recommends no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#342894: zope-cmfmember: Not the same package version + please upgrade

2005-12-11 Thread Balazs Ree
Package: zope-cmfmember
Severity: important


The version of CMFMember in this package is not really 1.1b5
as the debian package information states but 1.0b5 (1.0 beta5).

Also, this version does not work with Plone 2.1 so please
upgrade the package to upstream version 1.1b2 (1.1-beta2).
This is the newest version at the moment and prior versions
have known bugs when used with Plone 2.1.

Please also introduce in the new package some mechanism 
like epoch that allows updating (because otherwise 1.1b5 - 1.1b2
would appear as a downgrade to the package handling system).

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (50, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12-kt7
Locale: LANG=hu, LC_CTYPE=hu (charmap=ISO-8859-2) (ignored: LC_ALL set to 
hu_HU.ISO-8859-2)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#341529: zope3: init.d bug: zeo instances not started

2005-12-01 Thread Balazs Ree
Package: zope3
Version: 3.1.0-3
Severity: normal


Please consider the following patch.

--- debian/zopeZVER.init.in 2005-12-01 08:25:58.495475902 +0100
+++ /tmp/zopeZVER.init.in   2005-12-01 08:29:08.234884902 +0100
@@ -26,7 +26,7 @@
 
 if [ -n $ZEOSERVERS ]; then
 cd /var/lib/zope$ZVER/zeo
-for i in $INSTANCES ; do
+for i in $ZEOSERVERS ; do
 if [ $i = * ]; then
 # log_success_msg Zope$ZVER: no ZEO servers found.
 break

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (50, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12-kt7
Locale: LANG=hu, LC_CTYPE=hu (charmap=ISO-8859-2) (ignored: LC_ALL set to 
hu_HU.ISO-8859-2)

Versions of packages zope3 depends on:
ii  libc6 2.3.5-7GNU C Library: Shared libraries an
ii  lsb-base  3.0-11 Linux Standard Base 3.0 init scrip
ii  python-docutils   0.3.9-0.1  Utilities for the documentation of
ii  python2.4 2.4.2-1An interactive high-level object-o
ii  python2.4-tz  2005m-1Python version of the Olson timezo
ii  zope-common   0.5.13 common settings and scripts for zo

zope3 recommends no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#341526: zope2.7: init.d bug: zeo instances not started

2005-11-30 Thread Balazs Ree
Package: zope2.7
Version: 2.7.8-1
Severity: normal


Please consider the following patch.

--- debian/zopeZVER.init.in 2005-12-01 08:25:58.495475902 +0100
+++ /tmp/zopeZVER.init.in   2005-12-01 08:29:08.234884902 +0100
@@ -26,7 +26,7 @@
 
 if [ -n $ZEOSERVERS ]; then
 cd /var/lib/zope$ZVER/zeo
-for i in $INSTANCES ; do
+for i in $ZEOSERVERS ; do
 if [ $i = * ]; then
 # log_success_msg Zope$ZVER: no ZEO servers found.
 break

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (50, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12-kt7
Locale: LANG=hu, LC_CTYPE=hu (charmap=ISO-8859-2) (ignored: LC_ALL set to 
hu_HU.ISO-8859-2)

Versions of packages zope2.7 depends on:
ii  debconf  1.4.58  Debian configuration management sy
ii  dpkg 1.13.11.0.1 package maintenance system for Deb
ii  libc62.3.5-7 GNU C Library: Shared libraries an
ii  lsb-base 3.0-11  Linux Standard Base 3.0 init scrip
ii  python2.32.3.5-8 An interactive high-level object-o
ii  python2.3-xml0.8.4-1 XML tools for Python (2.3.x)
ii  zope-common  0.5.13  common settings and scripts for zo

zope2.7 recommends no packages.

-- debconf information:
* zope/tips/standalone_install:
* zope/instance_home/move: true
  zope/upgrade/2.7:
* zope/tips/2.7:
* shared/zope/restart: configuring


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#341527: zope2.8: init.d bug: zeo instances not started

2005-11-30 Thread Balazs Ree
Package: zope2.8
Version: 2.8.3-1
Severity: normal


Please consider the following patch.

--- debian/zopeZVER.init.in 2005-12-01 08:25:58.495475902 +0100
+++ /tmp/zopeZVER.init.in   2005-12-01 08:29:08.234884902 +0100
@@ -26,7 +26,7 @@
 
 if [ -n $ZEOSERVERS ]; then
 cd /var/lib/zope$ZVER/zeo
-for i in $INSTANCES ; do
+for i in $ZEOSERVERS ; do
 if [ $i = * ]; then
 # log_success_msg Zope$ZVER: no ZEO servers found.
 break

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (50, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12-kt7
Locale: LANG=hu, LC_CTYPE=hu (charmap=ISO-8859-2) (ignored: LC_ALL set to 
hu_HU.ISO-8859-2)

Versions of packages zope2.8 depends on:
ii  debconf [debconf-2.0] 1.4.58 Debian configuration management sy
ii  libc6 2.3.5-7GNU C Library: Shared libraries an
ii  lsb-base  3.0-11 Linux Standard Base 3.0 init scrip
ii  python2.3 2.3.5-8An interactive high-level object-o
ii  python2.3-xml 0.8.4-1XML tools for Python (2.3.x)
ii  zope-common   0.5.13 common settings and scripts for zo

zope2.8 recommends no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#325315: zsh-beta: broken symlinks after last update, zsh cannot start

2005-08-27 Thread Balazs Ree
Package: zsh-beta
Version: 4.3.0-dev-1+20050823-1
Severity: important


After the last update zsh did not start up and as a consequence
I was even unable to log in as root (as I use zsh for root as well)
when trying to fix the problem.

After the update, I realized that /etc/alternatives/zsh and
/etc/alternatives/zsh-userbin were pointing to /usr/bin/zsh-beta instead
of /bin/zsh-beta. I don't know if the update left them in this state:
more probably I have set them there manually years ago. You might argue
that this was a bad thing to do. However, even in this case I suggest
that upon the update the script should check for this possibility
and correct the symlinks. Otherwise this can put a previously
well-working system into a rather annoying state.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (50, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12-kt7
Locale: LANG=hu, LC_CTYPE=hu (charmap=ISO-8859-2) (ignored: LC_ALL set to 
hu_HU.ISO-8859-2)

Versions of packages zsh-beta depends on:
ii  libc6 2.3.5-4GNU C Library: Shared libraries an
ii  libcap1   1:1.10-14  support for getting/setting POSIX.
ii  libncurses5   5.4-9  Shared libraries for terminal hand
ii  libpcre3  5.0-1.1Perl 5 Compatible Regular Expressi
ii  passwd1:4.0.3-39 change and administer password and

zsh-beta recommends no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#305854: zope2.7: 2.7.5-2 confirmed

2005-05-02 Thread Balazs Ree
Package: zope2.7
Version: 2.7.5-2
Followup-For: Bug #305854


Andrea,

the 2.7.5-2 solves the current problem

I have run the tests this way: changed dir to my instance dir,
(/var/lib/zope2.7/instance/default) and did a bin/zopectl test.
All works right for me.

I think you received 0 tests run because the directory where
it looks for tests to run must be given by the --libdir parameter,
or by default it is under the current directory. If you do not
give --libdir and you are in the wrong place, this is what happens.

And thanks for solving this. (BTW, I don't think this change 
could break anything, unless someone would want to manually 
symlink test.py out to some other location and run it from there,
but as the designated way is now to run test.py via zopectl,
this should not be a big worry. IMO.)

Balazs Ree


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#304458: zope-testcase: cannot import ZopeTestCase with zope2.7 multi-product-dir setup

2005-04-13 Thread Balazs Ree
Package: zope-testcase
Version: 0.9.0-1
Severity: normal


I use zope2.7 with a multi-product dir setup, i.e. both the product
paths (and libs) in /usr/lib/zope2.7 and /usr/lib/zope are searched 
and this is properly configured in zope.conf and working correctly 
in zope.

But when it comes to running tests, the test runner fails since it
cannot import ZopeTestCase.

This is because
- zope-testcase installs ZopeTestCase into /usr/lib/zope under the
  Testing library
- but there is also a Testing library in /usr/lib/zope2.7. This does not
  include ZopeTestCase but it is found (correctly) earlier than the
  Testing product in /usr/lib/zope. So, as a result, ZopeTestCase cannot
  be found.

As a workaround, I symlink /usr/lib/zope/lib/python/Testing/ZopeTestCase
to /usr/lib/zope2.7/lib/python/Testing/ZopeTestCase. But I think it
would be good to resolve this from the install scripts, for example
attept to do this symlink from postinst?

--

(ps. There is an other independent (path) problem with running tests 
through test.py in zope2.7 but this does not concern this product and 
I'll try to clear that one with the mainstream developers.)

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable'), (50, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.9-kt7
Locale: LANG=hu, LC_CTYPE=hu (charmap=ISO-8859-2) (ignored: LC_ALL set to 
hu_HU.ISO-8859-2)

Versions of packages zope-testcase depends on:
ii  zope 3:2.6.2-6rb Open Source Web Application Server
ii  zope2.7 [zope]   2.7.5-1 Open Source Web Application Server

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]