Bug#611279: Bug confirmed

2011-02-03 Thread Sebastien Rodriguez
Hello,
I had the same problem , so thanks to this bug report I looked my packages :

# dpkg -l | grep 3.3.0
ii  libreoffice   1:3.3.0-1
  office productivity suite
ii  libreoffice-base  1:3.3.0-1
  office productivity suite -- database
ii  libreoffice-base-core 1:3.3.0-1
  office productivity suite -- shared library
ii  libreoffice-calc  1:3.3.0-1
  office productivity suite -- spreadsheet
ii  libreoffice-common1:3.3.0-1
  office productivity suite -- arch-independent files
ii  libreoffice-core  1:3.3.0-1
  office productivity suite -- arch-dependent files
ii  libreoffice-draw  1:3.3.0-1
  office productivity suite -- drawing
ii  libreoffice-emailmerge1:3.3.0~rc1-1
  office productivity suite -- email mail merge
ii  libreoffice-filter-binfilter  1:3.3.0-1
  office productivity suite -- legacy filters (e.g. StarOffice
5.2)
ii  libreoffice-filter-mobiledev  1:3.3.0~rc1-1
  office productivity suite -- mobile devices filters
ii  libreoffice-gnome 1:3.3.0-1
  office productivity suite -- GNOME integration
ii  libreoffice-gtk   1:3.3.0-1
  office productivity suite -- GTK+ integration
ii  libreoffice-help-fr   1:3.3.0~rc1-1
  office productivity suite -- French help
ii  libreoffice-impress   1:3.3.0-1
  office productivity suite -- presentation
ii  libreoffice-java-common   1:3.3.0~rc1-1
  office productivity suite -- arch-independent Java support
files
ii  libreoffice-l10n-fr   1:3.3.0-1
  office productivity suite -- French language package
ii  libreoffice-math  1:3.3.0-1
  office productivity suite -- equation editor
ii  libreoffice-report-builder-bin1:3.3.0~rc1-1
  LibreOffice extension for building database reports --
libraries
ii  libreoffice-style-andromeda   1:3.3.0~rc1-1
  office productivity suite -- Andromeda (Classic) symbol
style
ii  libreoffice-style-galaxy  1:3.3.0~rc1-1
  office productivity suite -- Galaxy (Default) symbol style
ii  libreoffice-style-tango   1:3.3.0~rc1-1
  office productivity suite -- Tango symbol style
ii  libreoffice-writer1:3.3.0-1
  office productivity suite -- word processor
ii  python-uno1:3.3.0-1
  Python-UNO bridge
ii  ttf-opensymbol
2:2.4.3+LibO3.3.0~rc1-1OpenSymbol TrueType font
ii  uno-libs3 1.7.0+LibO3.3.0-1
  LibreOffice UNO runtime environment -- public shared
libraries
ii  ure   1.7.0+LibO3.3.0-1
  LibreOffice UNO runtime environment

I updated the 3.3.0~rc1 packages with :
# aptitude -t experimental install libreoffice-emailmerge
libreoffice-filter-mobiledev libreoffice-help-fr
libreoffice-java-common libreoffice-report-builder-bin
libreoffice-style-galaxy libreoffice-style-andromeda
libreoffice-style-tango ttf-opensymbol


And everything is ok now :  I can see the options dialog.

I hope it might help someone.

Regards,
Sébastien.



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#611279: Bug confirmed

2011-02-03 Thread Sebastien Rodriguez
2011/2/3 Rene Engelhard :
> Hi,
>
> On Thu, Feb 03, 2011 at 11:10:42AM +0100, Sebastien Rodriguez wrote:
>> I had the same problem , so thanks to this bug report I looked my packages :
>
> No, you have far more problems, You have even more packages not updated.
> Why on earth do people cause such havoc to their systems? If you don't know
> how to use experimental properly, don't.

Hi,
You are right, I had a problem with my "experimental" experiment !

First, I upgraded ure, but it does not work. So I looked all 3.3.0~rc1
versions and upgraded these packages.

>> I hope it might help someone.
>
> No, it doesn't. because it does answer the question which *exact* package
> is at fault.  Your scanrio at least might rule out ure but why
> on earth were you upgrading all those in one go instead of doing what I
> reuquested in the bug? Check fix package install *exactly* fixes it.
>

Ok, I thought It could be libreoffice-style-* because of this Options
Dialog manages the styles.
> The only common package together with the OP is libreoffice-filter-mobiledev,
> though, but I don't see how this should affect it...
>
> (and as said, I can't reproduce this anyway)

Neither do I.

Regards,
Sebastien



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#558772: ifupdown: "ifup lo" does not give ip address to loopback interface

2009-11-30 Thread Sebastien Rodriguez
Package: ifupdown
Version: 0.6.9
Severity: important

In the file /etc/network/interfaces, I have :
auto lo
iface lo inet loopback


But when I launch :
# /etc/init.d/networking restart (or ifup lo)
I have :
# ifconfig lo
loLink encap:Local Loopback
  inet6 addr: ::1/128 Scope:Host
  UP LOOPBACK RUNNING  MTU:16436  Metric:1
  RX packets:1895 errors:0 dropped:0 overruns:0 frame:0
  TX packets:1895 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0
  RX bytes:356898 (348.5 KiB)  TX bytes:356898 (348.5 KiB)

The loopbak interface  has not the adress 127.0.0.1...

In order to put it to work, I have to do
# ifconfig lo 127.0.0.1


-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'squeeze'), (500, 'unstable'),
(1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.30-2-686 (SMP w/1 CPU core)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages ifupdown depends on:
ii  libc6 2.10.1-7   GNU C Library: Shared libraries
ii  lsb-base  3.2-23 Linux Standard Base 3.2 init scrip
ii  net-tools 1.60-23The NET-3 networking toolkit

ifupdown recommends no packages.

Versions of packages ifupdown suggests:
ii  dhcp3-client   3.1.3-1   DHCP client
ii  iproute20090324-1networking and traffic control too
ii  ppp2.4.4rel-10.1 Point-to-Point Protocol (PPP) - da

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#558772: Please close this bug....

2009-12-04 Thread Sebastien Rodriguez
It seems the problem was caused by the exhalt-daemon from emodules-all package.
It was installed with enlightenment.

I desinstalled exhalt-daemon and everything seems fine.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org