Bug#758619: requested additional info

2014-08-20 Thread VALETTE Eric OLNC/OLPS

  
  
reportbug --template libgtk2.0-0
  *** Welcome to reportbug.  Use ? for help at prompts. ***
  Note: bug reports are publicly archived (including the email
  address of the submitter).
  Detected character set: UTF-8
  Please change your locale if this is incorrect.
  
  Using 'Eric Valette eric2.vale...@orange.com' as your from
  address.
  Getting status for libgtk2.0-0...
  Will send report to Debian (per lsb_release).
  Maintainer for libgtk2.0-0 is 'Debian GNOME Maintainers
  pkg-gnome-maintain...@lists.alioth.debian.org'.
  Looking up dependencies of libgtk2.0-0...
  
  Rewriting subject to 'libgtk2.0-0: none'
  Content-Type: text/plain; charset="us-ascii"
  MIME-Version: 1.0
  Content-Transfer-Encoding: 7bit
  From: Eric Valette eric2.vale...@orange.com
  To: Debian Bug Tracking System sub...@bugs.debian.org
  Subject: libgtk2.0-0: none
  Reply-To: eric2.vale...@orange.com
  
  Package: libgtk2.0-0
  Version: 2.24.24-1
  Severity: wishlist
  
  Dear Maintainer,
  
  *** Reporter, please consider answering these questions, where
  appropriate ***
  
     * What led up to the situation?
     * What exactly did you do (or not do) that was effective (or
   ineffective)?
     * What was the outcome of this action?
     * What outcome did you expect instead?
  
  *** End of the template - remove these template lines ***
  
  
  -- System Information:
  Debian Release: jessie/sid
    APT prefers unstable
    APT policy: (500, 'unstable'), (1, 'experimental')
  Architecture: amd64 (x86_64)
  
  Kernel: Linux 3.15.10 (SMP w/4 CPU cores; PREEMPT)
  Locale: LANG=en_US.UTF8, LC_CTYPE=en_US.UTF8 (charmap=UTF-8)
  (ignored: LC_ALL set to en_US.UTF8)
  Shell: /bin/sh linked to /bin/bash
  
  Versions of packages libgtk2.0-0 depends on:
  ii  libatk1.0-0  2.12.0-1
  ii  libc6    2.19-9
  ii  libcairo2    1.12.16-2
  ii  libcups2 1.7.5-1
  ii  libfontconfig1   2.11.0-6
  ii  libfreetype6 2.5.2-1.1
  ii  libgdk-pixbuf2.0-0   2.30.7-1
  ii  libglib2.0-0 2.41.2-1
  ii  libgtk2.0-common 2.24.24-1
  ii  libpango-1.0-0   1.36.6-1
  ii  libpangocairo-1.0-0  1.36.6-1
  ii  libpangoft2-1.0-0    1.36.6-1
  ii  libx11-6 2:1.6.2-3
  ii  libxcomposite1   1:0.4.4-1
  ii  libxcursor1  1:1.1.14-1
  ii  libxdamage1  1:1.1.4-2
  ii  libxext6 2:1.3.2-1
  ii  libxfixes3   1:5.0.1-2
  ii  libxi6   2:1.7.4-1
  ii  libxinerama1 2:1.1.3-1
  ii  libxrandr2   2:1.4.2-1
  ii  libxrender1  1:0.9.8-1
  ii  multiarch-support    2.19-9
  ii  shared-mime-info 1.3-1
  
  Versions of packages libgtk2.0-0 recommends:
  ii  hicolor-icon-theme  0.13-1
  ii  libgtk2.0-bin   2.24.24-1
  
  Versions of packages libgtk2.0-0 suggests:
  pn  gvfs none
  ii  librsvg2-common  2.40.3-1
  
  -- no debconf information
  
  If you want to provide additional information, please wait to
  receive the bug tracking number via email; you
  may then send any extra information to n...@bugs.debian.org (e.g.
  999...@bugs.debian.org), where n is the bug
  number. Normally you will receive an acknowledgement via email
  including the bug report number within an hour;
  if you haven't received a confirmation, then the bug reporting
  process failed at some point (reportbug or MTA
  failure, BTS maintenance, etc.).
  toto:~-reportbug --template reportbug
  *** Welcome to reportbug.  Use ? for help at prompts. ***
  Note: bug reports are publicly archived (including the email
  address of the submitter).
  Detected character set: UTF-8
  Please change your locale if this is incorrect.
  
  Using 'Eric Valette eric2.vale...@orange.com' as your from
  address.
  Getting status for reportbug...
  Will send report to Debian (per lsb_release).
  Maintainer for reportbug is 'Reportbug Maintainers
  reportbug-ma...@lists.alioth.debian.org'.
  Looking up dependencies of reportbug...
  Getting status for related package python-reportbug...
  Looking up 'depends' of related package python-reportbug...
  Looking up 'suggests' of related package python-reportbug...
  Getting changed configuration files...
  
  Rewriting subject to 'reportbug: none'
  Gathering additional data, this may take a while...
  Content-Type: text/plain; charset="us-ascii"
  MIME-Version: 1.0
  Content-Transfer-Encoding: 7bit
  From: Eric Valette eric2.vale...@orange.com
  To: Debian Bug Tracking System sub...@bugs.debian.org
  Subject: 

Bug#758619: more complete backtrace

2014-08-20 Thread VALETTE Eric OLNC/OLPS
gdb --args python /usr/bin/reportbug -b --no-check-available libpulse0
GNU gdb (Debian 7.7.1+dfsg-3) 7.7.1
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type show copying
and show warranty for details.
This GDB was configured as x86_64-linux-gnu.
Type show configuration for configuration details.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/.
Find the GDB manual and other documentation resources online at:
http://www.gnu.org/software/gdb/documentation/.
For help, type help.
Type apropos word to search for commands related to word...
Reading symbols from python...Reading symbols from
/usr/lib/debug//usr/bin/python2.7...done.
done.
(gdb) run
Starting program: /usr/bin/python /usr/bin/reportbug -b
--no-check-available libpulse0
[Thread debugging using libthread_db enabled]
Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1.
*** Welcome to reportbug.  Use ? for help at prompts. ***
Note: bug reports are publicly archived (including the email address of
the submitter).
Detected character set: UTF-8
Please change your locale if this is incorrect.

Using 'Eric Valette eric2.vale...@orange.com' as your from address.
Getting status for libpulse0...
Will send report to Debian (per lsb_release).
Maintainer for libpulse0 is 'Pulseaudio maintenance team
pkg-pulseaudio-de...@lists.alioth.debian.org'.
Looking up dependencies of libpulse0...
Getting changed configuration files...

Briefly describe the problem (max. 100 characters allowed). This will be
the bug email subject, so keep the
summary as concise as possible, for example: fails to send email or
does not start with -q option specified
(enter Ctrl+c to exit reportbug without reporting a bug).
 Attempt to unlock mutex that was not locked

Program received signal SIGABRT, Aborted.
0x76f28407 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56
56  ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or
directory.
(gdb) thread apply all
bt  



   

Thread 1 (Thread 0x77fc0700 (LWP
17124)):  
#0  0x76f28407 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56   
#1  0x76f297e8 in __GI_abort () at
abort.c:89  
#2  0x72cdc85d in g_mutex_unlock_slowpath (mutex=optimized
out, prev=optimized out)
at
/build/glib2.0-MHsCdQ/glib2.0-2.41.2/./glib/gthread-posix.c:1327


#3  0x719f4bbf in IA__gtk_main () at
/build/gtk+2.0-zztKf7/gtk+2.0-2.24.24/gtk/gtkmain.c:1256  
#4  0x720a7d54 in _loop
() 

at
/build/buildd-pygtk_2.24.0-3+b1-amd64-HH_0XF/pygtk-2.24.0/gtk/gtk.override:126  


#5  0x74148b21 in readline_until_enter_or_signal
(signal=synthetic pointer, prompt=optimized out)  
at
/build/python2.7-WkYSEh/python2.7-2.7.8/Modules/readline.c:996  


#6  call_readline (sys_stdin=optimized out, sys_stdout=optimized
out, prompt=optimized out)  
at
/build/python2.7-WkYSEh/python2.7-2.7.8/Modules/readline.c:1088 


#7  0x0044a06f in PyOS_Readline (sys_stdin=0x772974e0
_IO_2_1_stdin_,
sys_stdout=sys_stdout@entry=0x772972a0 _IO_2_1_stdout_,
prompt=prompt@entry=0x7434f84c  )
at ../Parser/myreadline.c:207
#8  0x004453e2 in builtin_raw_input.lto_priv.1351
(self=optimized out, args=optimized out)
at ../Python/bltinmodule.c:2060
#9  0x004c8265 in call_function (oparg=optimized out,
pp_stack=optimized out)
at ../Python/ceval.c:4021
#10 PyEval_EvalFrameEx () at ../Python/ceval.c:2667
#11 0x004c6ab9 in PyEval_EvalCodeEx () at ../Python/ceval.c:3253
#12 0x004c877c in fast_function (nk=optimized out,
na=optimized out, n=optimized out,
pp_stack=optimized out, func=optimized out) at
../Python/ceval.c:4117
#13 call_function (oparg=optimized out, pp_stack=optimized out) at
../Python/ceval.c:4042
#14 PyEval_EvalFrameEx () at ../Python/ceval.c:2667
#15 0x004c6ab9 in PyEval_EvalCodeEx () at ../Python/ceval.c:3253
#16 0x004c877c in fast_function (nk=optimized out,
na=optimized out, n=optimized out,
pp_stack=optimized out, func=optimized out) at
../Python/ceval.c:4117
#17 call_function (oparg=optimized out, 

Bug#728802: calendar-exchange-provider: Impossible to connect to exchange calendar after 24.0 upgrade (it connect but calendar is RO)

2013-11-06 Thread VALETTE Eric OLNC/OLPS

On 11/05/2013 08:08 PM, Jakub Adam wrote:

Hi,

On 5.11.2013 18:13, Eric Valette wrote:

Running tb 24.1, lightning 2.6.2 and calendar-exchange-provider
3.2.0-beta57 on a windows VM on the same machine works with same 
settings.


Where did you come to beta57? The latest tarball I see available for 
download

is beta52 and in git is beta53.

I goofed (probably mixing the old beta47 on linux and beta52 on windows).


Could you update icedove, iceowl-extension and 
calendar-exchange-provider

to the same version.


I've packaged ~beta53 that declares it's compatible with TB 24.0 [1] and
contacted my sponsor. He is quite fast with reviewing so hopefully 
this time it

won't be an exception. The upload will be into experimental (that's where
Icedove 24.0 is).

I confirm the bug is fixed here. Thanks for your responsiveness.


Is icedove 24.0 really TB 24.0 or 24.0.1 because  24.0.1 requires 
lightning

2.6.1 and 24.1 requires lightning 2.6.2...


AFAIK icedove and iceowl-extension are built from the very same source 
tarball,

so there shouldn't arise any version incompatibilities between these two.

Right. Just the beta3 is confusing but I assume 2.6beta3  = 2.6.

Thanks for your support.


-- eric


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



Bug#723846: mail-notification: Does not find previously confiured account + strange error messages

2013-09-30 Thread VALETTE Eric OLNC/OLPS

  
  
On 09/29/2013 02:41 PM, Stephen Kitt
  wrote:


  Hi Eric,

On Fri, 20 Sep 2013 14:39:29 +0200, Eric Valette eric2.vale...@orange.com
wrote:

  
mail-notification 
error: XDG_RUNTIME_DIR not set in the environment.

  
  
Is this an error message you get, or are you stating that XDG_RUNTIME_DIR is
not set in the environment?

Well I now have it on most gnome related packages... I recently
openend a bug on gupnp-tools that fails to launch due to missing
icons. Was working before and I need it...

  


  
(mail-notification:7001): GLib-WARNING **:
(/build/glib2.0-I6u57X/glib2.0-2.37.93/./glib/gerror.c:390):g_error_new_valist:
runtime check failed: (domain != 0)

  
  
This is odd...


  
Fontconfig warning: "/etc/fonts/conf.d/50-user.conf", line 9: reading
configurations from ~/.fonts.conf is deprecated.

  
  
This is #714148 but it shouldn't have any impact.

Yes .

  


  
This lead to two popup  :
  1) one saying An error kas occured while loading the mailboxes
configuration (on line 3: unknown mailbox type "imap") which I find quite
strange!!!

  
  
Could you send a screen capture of this dialog? The message means that it did
find your configuration but it couldn't determine how to handle IMAP
mailboxes, which is very strange indeed.

That's the idea. I though that it was due to incompatibilities in
xml file and was ready to recreate the mailbox, but even when
creating it, IMAP is not an option = which points also to the
fact that imap support is broken

  

If you don't mind, I'd like to see the contents of your
~/.gnome2/mail-notification/mailboxes.xml file too, with the usernames
obscured (and anything else you don't feel comfortable sharing).

?xml version="1.0"?
mailboxes
  mailbox type="imap" username="DOMAIN\name"
connection-type="ssl" authmech="+LOGIN" hostname="exchange-
server-name"/
/mailboxes


  


  
  2) Opens the mailbox configuration dialog

  
  
That's the normal behaviour when the configuration can't be determined.




-- 
Eric Valette
Orange Lab Product and Services
Homebox Etudes Architecture et Développement 
Architecte Livebox et Set Top Box
tél : (+33) 2 99 12 45 71
mél : mailto:eric2.vale...@orange.com

  

attachment: mail-notif-error.png

Bug#723846: when clicking on the icon in the tray I get a segmentation fault in addition.

2013-09-20 Thread VALETTE Eric OLNC/OLPS

  
  
(mail-notification:7114): Gtk-WARNING **: Error
  loading theme icon 'stock_mail-compose' for stock: Icon
  'stock_mail-compose' not present in theme
  
  (mail-notification:7114): Gtk-WARNING **: Error loading theme icon
  'stock_mail-open' for stock: Icon 'stock_mail-open' not present in
  theme
  
  (mail-notification:7114): Gtk-WARNING **: Error loading theme icon
  'mail-mark-read' for stock: Icon 'mail-mark-read' not present in
  theme
  Segmentation fault   ==

-- eric


  



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



Bug#707092: Confirmed: the auto keyword parsing seems broken

2013-05-07 Thread VALETTE Eric OLNC/OLPS

ifup eth0
/etc/network/interfaces:5: interface lo declared allow-auto twice
ifup: couldn't read interfaces file /etc/network/interfaces

If I remove the auto lo line I get network but no lo!

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
#auto lo===
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
iface eth0 inet dhcp
  hostname r-x-ceva6380

iface wlan0 inet dhcp
  pre-up  /etc/network/WirelessLanStartLiveBox.sh wlan0
  hostname r-x-ceva6380
  post-down /etc/network/WirelessLanStopLiveBox.sh wlan0


--
Eric Valette
Orange Lab Product and Services
Homebox Etudes Architecture et Développement
Architecte Livebox et Set Top Box
tél : (+33) 2 99 12 45 71
mél : mailto:eric2.vale...@orange.com


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



Bug#701024: Bug is upstream and related to opening file on CIFS mounted share

2013-02-21 Thread VALETTE Eric OLNC/OLPS

  
  
Hi Rene,

Yesterday I took time to browse openoffice bug reports and found one
related to opening file on CIFS share and I was typically using
that. So I tried copying the same file on my local system and bingo
I can open the file. The message is really strange: File is
corrupted...
-- eric
  



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



Bug#701024: Bug is upstream and related to opening file on CIFS mounted share and fixed in 4.0.1-rc1

2013-02-21 Thread VALETTE Eric OLNC/OLPS

  
  
Hi Rene,

Installed 4.0.1-rc1 from your work in progress repo = bug is
gone as expected because fixed upstream.

Thanks for the pointer and support

-- eric
  



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



Bug#701024: Files are ok with 3.6.5 on a windows VM

2013-02-20 Thread VALETTE Eric OLNC/OLPS
I reinstalled windows libreoffice version 3.6.5 ona vm and all files 
open correctly = not a problem with files themselves.


--eric


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



Bug#699351: UPnP forum communication: UPnP Forum Responds to Recently Identified LibUPnP/MiniUPnP Security Flaw

2013-02-11 Thread VALETTE Eric OLNC/OLPS

Extract from official communication:

For gateway vendors both affected and unaffected by this identified 
flaw, the UPnP Forum continues to advise that vendors implement the 
latest version of the Internet Gateway Device (v2) rather than the V1 
that is deployed today. Along with our Device Protection standard, this 
specification provides numerous enhancements for security as well as 
necessary enhancements like the growing deployment of IPv6.


--
Eric Valette
Orange Lab Product and Services
Homebox Etudes Architecture et Développement
Architecte Livebox et Set Top Box
tél : (+33) 2 99 12 45 71
mél : mailto:eric2.vale...@orange.com


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



Bug#699351: linux-gd obsolete and lubupnp4

2013-02-04 Thread VALETTE Eric OLNC/OLPS

  
  
On 02/02/2013 01:30 AM, Scott Howard
  wrote:


  retitle 699351 linux-igd follows old UPnP IGD V1 spec
thanks


On Thu, Jan 31, 2013 at 3:32 AM, VALETTE Eric OLNC/OLPS
eric2.vale...@orange.com wrote:

  
Look at the CVE that have been filled regarding libupnp6 and the associated
bugs.

  
  
Thanks - they have been fixed in libupnp4 [1]. I've renamed the bug
appropriately. I do not know enough about UPnP IGD V1 versus V2 [2] to
have an opinion about whether this is an RC bug or not, so I'll leave
that for the security team or someone more qualified.

[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699459
[2] http://upnp.org/sdcps-and-certification/standards/sdcps/


Fine for me. Thanks. 

PS : Security wise, UPNP IGD 2 is more strict to prevent a device to
open a  port to a different IP than itself. The bug that make SSDP
available on the WAN side is also problematic in the IGD V1 version.
You shall not rely on the firewall to block incoming WAN packet but
not listen to the WAN interface for SSDP...

-- eric
  



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



Bug#699351: linux-gd obsolete and lubupnp4

2013-01-31 Thread VALETTE Eric OLNC/OLPS

  
  
On 01/30/2013 10:26 PM, Scott Howard
  wrote:


  Hello Eric,

You wrote:
"Linux-igd is dead code, use very old libpunp version that contains
numerous security holes. Besides this version is not compatible with
IPV6 as required by UPnP IGD V2 specification."

I believe you mean libupnp4 contains numerous security holes - have
they been reported in Debian? That could be serious with implications
beyond linux-gd and needs to be addressed immediately. I don't see any
reported [1].

Look at the CVE that have been filled regarding libupnp6 and the
associated bugs.

  

Are there security problems with linux-igd independent of libupnp4?

Yes fixed in UPnP IGD V2because the specification themszelves
addressed the security concerns.

  

It seems that the main bug is the linux-igd is not compatible with
UPnP IGD V2. If that is the case, I don't think this is an RC bug
(severity Grave). A "normal" severity seems more appropriate to me.

Regards,
Scott

[1] http://bugs.debian.org/cgi-bin/pkgreport.cgi?ordering=normal;archive=0;src="">




-- 
Eric Valette
Orange Lab Product and Services
Homebox Etudes Architecture et Développement 
Architecte Livebox et Set Top Box
tél : (+33) 2 99 12 45 71
mél : mailto:eric2.vale...@orange.com

  



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