from:"Pascal"

Bug#443626: tinyerp-server: After install the server couldn't connect to the Postgres Database server.

2007-09-22 Thread pascal

Package: tinyerp-server
Version: 4.0.3-2
Severity: grave
Tags: patch
Justification: renders package unusable

Set The DATABASE_PORT to "5433" in the /etc/default/tinyerp-server file.

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.18-3-amd64 (SMP w/2 CPU cores)
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash

Versions of packages tinyerp-server depends on:
ii  adduser3.105 add and remove users and groups
ii  python 2.4.4-6   An interactive high-level object-o
ii  python-libxml2 2.6.30.dfsg-2 Python bindings for the GNOME XML 
ii  python-libxslt11.1.22-1  Python bindings for libxslt1
ii  python-psycopg 1.1.21-15 Python module for PostgreSQL
ii  python-reportlab   2.0dfsg-1 ReportLab library to create PDF do
ii  python-support 0.6.4 automated rebuilding support for p
ii  python-xml 0.8.4-8   XML tools for Python

Versions of packages tinyerp-server recommends:
ii  graphviz  2.8-2.6rich set of graph drawing tools
ii  postgresql8.2.4-2object-relational SQL database (la
ii  postgresql-client 8.2.4-2front-end programs for PostgreSQL 
ii  postgresql-client-8.2 [postgr 8.2.4-2front-end programs for PostgreSQL 
ii  python-imaging1.1.6-1Python Imaging Library
ii  python-pyparsing  1.4.2-1.1  Python parsing module

-- no debconf information




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

Bug#416201: libapache-mod-php4 was causing the problem

2007-03-25 Thread pascal

This package provides:
/etc/php4/apache

from which php-sqlite postinst deduced apache was installed

# apt-get --purge remove libapache-mod-php4

solved my problem but people replacing apache by apache2 will still have 
it. Postinst should rather look in the package database since obsolete 
configuration files are misleading.



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

Bug#393606: mail-notification-evolution: Fails to contact evolution

2006-10-17 Thread Pascal


tags 393606 moreinfo unreproducible
quit
---

Hi Sam,
 I'm unable to reproduce your problem on my amd64 running m-n
3.0.dfsg.1-7 and evolution 2.6.3-2. Therefore, I must ask the
obvious...

1) Is Evolution running when you try to add the mailbox?
2) In "Edit > Plugins", is "Mail Notification" activated?

thanks,

-Pascal

On 10/16/06, Sam Morris <[EMAIL PROTECTED]> wrote:

Package: mail-notification-evolution
Version: 3.0.dfsg.1-7+b1
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

I am unable to add Evolution to the list of mailboxes that m-n monitors.

"Mail Notification can not contact Evolution. Make sure that Evolution
is running and that the Evolution Mail Notification plugin is loaded."


[...]

--
Homepage (http://organact.mine.nu)
Debian GNU/Linux (http://www.debian.org)
École de technologie supérieure (http://www.etsmtl.ca)

Bug#393606: mail-notification-evolution: Fails to contact evolution

2006-10-17 Thread Pascal

tags 393606 - moreinfo unreproducible
tags 393606 + confirmed experimental
quit
---
Oh! I just noticed that you're running evolution 2.8 from the
experimental branch!

Well then, this is a known issue and i can confirm that i need to
modify debian/rules to accomodate evo 2.8 .

I've two choices here, either:
- I fix it as soon as evo 2.8 enters unstable or
- I release a modified version in experimental

Which one would you prefer?

Regards,

-Pascal

On 10/17/06, Sam Morris <[EMAIL PROTECTED]> wrote:

On Tue, 2006-10-17 at 08:16 -0400, Pascal wrote:
>   I'm unable to reproduce your problem on my amd64 running m-n
> 3.0.dfsg.1-7 and evolution 2.6.3-2. Therefore, I must ask the
> obvious...

:)

> 1) Is Evolution running when you try to add the mailbox?

Yes

> 2) In "Edit > Plugins", is "Mail Notification" activated?

There is no "Mail Notification" plugin, however there is "New Mail
Notification" and it is activated.

Perhaps mail-notification cannot see Evolution because of changes in
version 2.8 (available from experimental if you want to test it).

> thanks,
>
> -Pascal

--
Sam Morris
http://robots.org.uk/

PGP key id 1024D/5EA01078
3412 EA18 1277 354B 991B  C869 B219 7FDB 5EA0 1078

--
Homepage (http://organact.mine.nu)
Debian GNU/Linux (http://www.debian.org)
École de technologie supérieure (http://www.etsmtl.ca)

Bug#903514: Gimp issues

2018-07-18 Thread Pascal Giard

Dear maintainer,

In case that may shed some light...

Before having gimp-python installed, gimp would start.
I could modify images and save them in the native gimp format.
Attempting to export to png or jpg would freeze though.
(With the exportation processes visible with `ps` but not doing anything,
it appears).

After installing gimp-python, attempting to start gimp, I get stuck on the
splash screen with status message "Interrogation des nouveaux greffons"
(python-eval.py).
Sorry, attempting to start with LC_ALL=C doesn't work; this loosely
translates to "Querying new plugins". Killing gimp, either of the following
process remains active
/usr/bin/python2 /usr/lib/gimp/2.0/plug-ins/py-slice.py -gimp 12 11 -query 0
/usr/bin/python2 /usr/lib/gimp/2.0/plug-ins/python-eval.py -gimp 12 11
-query 0

Best regards,

-Pascal
--
Homepage (http://giard.info)
Debian GNU/Linux (http://www.debian.org)
TCL: École polytechnique fédérale de Lausanne (http://tcl.epfl.ch)

Bug#903514: Gimp issues

2018-07-25 Thread Pascal Giard

Hi,

Exact same results as Benedict Geihe, i.e., removing libopenblas-base
solves the issue.
Thanks A LOT for pointing this out Benedict!

Best regards,

-Pascal
--
Homepage (http://giard.info)
Debian GNU/Linux (http://www.debian.org)
TCL: École polytechnique fédérale de Lausanne (http://tcl.epfl.ch)

Bug#789407: unable to send openpgp messages

2017-01-08 Thread Pascal Winkelmann

On Sat, 20 Jun 2015 21:10:56 +0530 Pirate Praveen 
wrote:
> package: pidgin-openpgp
> version: 0.1-2
> severity: grave
> 
> I can only receive openpgp messages, sending does not work.
> 

Hi. 
I've just tried to reproduce the behavior with two seperate XMPP
accounts on two different servers. I've added both JIDs with the same
OpenPGP-ID in the settings of the plugin. 
After sending "ENABLEPGP" in the chat with my second account the
message from that point on were indeed encrypted. Receiving the
encrypted messages wasn't a problem either.

pgpKMyoj452ng.pgp
Description: Digitale Signatur von OpenPGP

Bug#1033913: partman-auto-lvm: Broken "Guided - use entire disk and set up LVM" in UEFI mode

2023-04-03 Thread Pascal Hambourg


Hello,

On 03/04/2023 at 21:50, Cyril Brulebois wrote:


  - It very much looks like the intermediary states are slightly
different when setting up LVM and when setting up encrypted LVM, and
the LVM case case leads to some confusion in partman-efi's
/lib/partman/init.d/50efi (which logs to /var/log/partman rather than
to /var/log/syslog): “Found 0 ESPs, 3 non-ESPs”.


Not sure if it is relevant, but the non-EFI partition calculation is 
wrong. Patch attached.diff --git a/init.d/efi b/init.d/efi
index 7eb8d2e..092ba80 100755
--- a/init.d/efi
+++ b/init.d/efi
@@ -71,23 +71,22 @@ for dev in /var/lib/partman/devices/*; do
 	close_dialog
 
 	for id in $partitions; do
-	efi=no
-	open_dialog GET_FLAGS $id
-	while { read_line flag; [ "$flag" ]; }; do
-		if [ "$flag" = boot ]; then
-			efi=yes
+		efi=no
+		open_dialog GET_FLAGS $id
+		while { read_line flag; [ "$flag" ]; }; do
+			if [ "$flag" = boot ]; then
+efi=yes
+			fi
+		done
+		close_dialog
+		if [ "$efi" = yes ]; then
+			mkdir -p $id
+			echo efi >$id/method
 			NUM_ESP=$(($NUM_ESP + 1))
-			# cannot break here
 		else
 			NUM_NO=$(($NUM_NO + 1))
 		fi
 	done
-	close_dialog
-	if [ "$efi" = yes ]; then
-		mkdir -p $id
-		echo efi >$id/method
-	fi
-	done
 done
 
 log "Found $NUM_ESP ESPs, $NUM_NO non-ESPs"

Bug#1033913: partman-auto-lvm: Broken "Guided - use entire disk and set up LVM" in UEFI mode

2023-04-10 Thread Pascal Hambourg

partman-efi "Fix detection of BIOS-bootable systems" provides a 
significant improvement over previous behaviour. However I have a few 
comments.


1a) The patch assumes that a GPT disk may be BIOS-bootable only if it 
has a BIOS boot partition. But a GPT disk can be BIOS-bootable even 
without a BIOS boot partition:
- GRUB may be installed without a BIOS boot partition if /boot is a 
plain partition (using blocklists), even though it is less reliable so a 
BIOS boot partition is strongly recommended.
- Other BIOS boot loaders such as syslinux/extlinux do not need or use a 
BIOS boot partition.


1b) IIUC the patch fixes #1033913 because the disk selected for 
installation has received a new GPT disklabel without a BIOS boot 
partition, so further checking is skipped. But IMO the root cause of 
#1033913 is that changes are not committed to disk after setting the 
'boot' and 'esp' flags to the newly created ESP partition before 
stopping parted_server.

This can be seen in /var/log/partman:

/bin/autopartition-lvm
NEW_LABEL sda gpt
NEW_PARTITION 1 sda ext2 538MB (future ESP)
NEW_PARTITION 2 sda ext2 512MB (future /boot)
NEW_PARTITION 3 sda ext3 159GB (future LVM)
SET_FLAGS sda3 lvm
(user prompt to write changes to the disk)
COMMIT sda
...
/lib/partman/update.d/21efi_sync_flag
SET_FLAGS sda1 boot esp
...
/bin/perform_recipe_by_lvm
QUIT <- esp and boot flags have not been committed yet so are lost
...
/lib/partman/init.d/50efi
GET_FLAGS sda1 -> none

2) The patch considers the 'esp' and 'boot' flags to be equal. But this 
is true only with GPT. With MSDOS, they have totally different meanings:

- 'esp' means that the partition has the ESP type identifier.
- 'boot' means that the partition has the active/boot indicator set. The 
UEFI specification says that this indicator is ignored by EFI boot.


3) The patch considers LVM and RAID partitions not bootable. But both 
LVM and RAID superblocks can have a boot loader reserved area. Also, 
GRUB may boot them directly without a /boot partition.


4) It appears that partman fails to detect the specially crafted 
partition table on the installation media created with a debian image. 
Is it intended or fortunately unintentional ? If partman could see the 
EFI partition on the installation media, the detection of BIOS-bootable 
systems would fail.

Bug#1033913: partman-auto-lvm: Broken "Guided - use entire disk and set up LVM" in UEFI mode

2023-04-10 Thread Pascal Hambourg


On 10/04/2023 at 15:13, Steve McIntyre wrote:


Overall comment: I'm not trying to make the heuristics 100% reliable
here, as I don't think that's actually possible. Instead, I'm trying
to tread the fine line of:

  * minimising false negatives - let's try to pick up on the most
common cases where people are dual-booting with other systems and
might not understand the issues here. That's 99%+ going to be
people with Windows installed

  * minimising false positives - the issue that angered Cyril in
particular, with an incomplete LVM setup triggering the "bios
bootable OS" warning


IMO it is more important to avoid false positives, because switching to 
a BIOS installation on systems which are not BIOS-boot capable would 
create a non bootable system. In case oft is easier to install GRUB for 
BIOS boot on an running EFI system than the other way around.



- Other BIOS boot loaders such as syslinux/extlinux do not need or use a BIOS
boot partition.


Also not a use case I'm particularly caring about, I'll be
honest. They're also *really* not likely to work well without another
filesystem in use, which I expect we'll detect anyway.


Indeed other partitions are needed and will be detected, but they will 
not increment $NUM_NOT_ESP if the disk is GPT and has no BIOS boot 
partition (so $DISK_BIOS_BOOT=no), so it might cause a false negative. 
So why not just treat MSDOS and GPT disk labels equally and treat BIOS 
boot partitions like any other non-ESP ?



1b) IIUC the patch fixes #1033913 because the disk selected for installation
has received a new GPT disklabel without a BIOS boot partition, so further
checking is skipped. But IMO the root cause of #1033913 is that changes are
not committed to disk after setting the 'boot' and 'esp' flags to the newly
created ESP partition before stopping parted_server.


I originally thought about fixing partman-auto-lvm but it appears that 
other transient states can also trigger the "force UEFI installation" 
dialog during partitioning, for example after setting up LVM in manual 
partitioning if there is no ESP partition yet. As discussed in 
#debian-boot, a more general fix might be to run the check only once 
because only existing partitions before partitioning are relevant. Are 
there any use cases for which this might cause a false negative ?



4) It appears that partman fails to detect the specially crafted partition
table on the installation media created with a debian image. Is it intended
or fortunately unintentional ? If partman could see the EFI partition on the
installation media, the detection of BIOS-bootable systems would fail.


That's not a worry for today... :-)


Sure, but the issue can also happen if another removable media is 
present. For instance the USB drive I use to provide missing firmware 
has an ESP partition (and a regular partition table) thus can cause a 
false negative.

Bug#1029352: netcfg: broken ifupdown support for wireless interfaces

2023-01-22 Thread Pascal Hambourg


Hello,

On 21/01/2023 at 17:14, Cyril Brulebois wrote:


# Second issue

Once that's fixed, if one gets both DHCP+SLAAC, the generated /e/n/i
looks like this (± comments/newlines):

 allow-hotplug wlXXX

 iface wlXXX inet dhcp

 iface wlXXX inet6 auto
   wpa-ssid my-home-network
   wpa-psk  my-very-secret-passphrase

At best, we get SLAAC to work (IPv6 via RAs) but not DHCP: the first
iface stanza is missing wpa-* parameters, and we get a huge delay at
boot-up until dhclient finally times out.

(...)

→ ifupdown & wpa maintainers, comments welcome!


Comment from a simple user: I hate so say, but IMO ifupdown and/or 
/etc/network/interfaces format is broken by design. Stanzas mix link 
layer and network layer parameters and this causes various issues when 
you have several stanzas for the same interface. Link layer parameters 
should be applied once per interface regardless of the address family.



# Third issue

netcfg has some hotplug detection, which was last touched in 2005; it
tries to identify interfaces that are hotpluggable, and lists them under
/etc/network/devhotplug (in the installer's context), which is then used
to determine whether interfaces should be declared “auto” or
“allow-hotplug”. My rtl8192cu-based Wi-Fi USB dongle (shared from the
host via libvirt) ends up as “allow-hotplug”, which is problematic
because the module gets loaded after networking.service has returned,
failing to raise the wireless interface. Using “auto” makes ifupdown
wait a little more, and I'm getting my wireless interface configured.


That should not happen. After reading Alf's reply, I suspect a 
regression introduced in the latest bookwork ifupdown release:


   * networking.service: Add ExecStart=/sbin/ifup -a --allow=hotplug.
 Patch by "Oleg A. Arkhangelsky" 
 (Closes: #1022843)

According to the bug report, the patch also adds '--ignore-errors' so 
that ifup and networking.service return success even if hotplug 
interfaces are missing. I'm afraid it has a side effect: it also marks 
the interface as brought up, and when invoked by udev after the 
interface is created, ifup will not do anything.

Bug#1022843: Bug#1029352: Bug#1022843: ifupdown: network down after systemctl restart

2023-01-22 Thread Pascal Hambourg


Oleg A. Arkhangelsky wrote:

Note that we have to use '--ignore-errors'. Otherwise if we have real
hotplug interface that is not present at the moment of restart, `ifup`
returns non-zero and systemd unit fail.


"--ignore-errors" marks missing interfaces as configured, so ifup will 
not configure them when invoked by udev. In order to not fail the 
systemd unit start on ifup error, you can prefix the command with "-".


On 22/01/2023 at 20:58, Cyril Brulebois wrote:


with an extra ens3 declared as auto, the following seems to work fine
for boot-up, stop and start, and restart:

 [Service]
 Type=oneshot
 EnvironmentFile=-/etc/default/networking
 ExecStart=/sbin/ifup -a --read-environment
 ExecStart=/bin/sh -c 'if [ -f /run/network/restart-hotplug ]; then 
/sbin/ifup -a --read-environment --allow=hotplug; fi'
 ExecStop=/sbin/ifdown -a --read-environment --exclude=lo
 ExecStopPost=/usr/bin/touch /run/network/restart-hotplug
 RemainAfterExit=true
 TimeoutStartSec=5min


That seems needlessly convoluted. What about this:

[Service]
Type=oneshot
EnvironmentFile=-/etc/default/networking
ExecStart=/sbin/ifup -a --read-environment
ExecStart=-/sbin/ifup -a --read-environment --allow=hotplug
ExecStop=/sbin/ifdown -a --read-environment --exclude=lo
RemainAfterExit=true
TimeoutStartSec=5min

"start" and "restart" configure all existing "auto" and "allow-hotplug" 
interfaces.
Missing "allow-hotplug" interfaces do not be marked as configured (so 
that they can be configured by udev) and do not make "start" or 
"restart" fail.

Bug#1022843: Bug#1029352: Bug#1022843: ifupdown: network down after systemctl restart

2023-01-25 Thread Pascal Hambourg


Sorry for the late (and long) answer...

On 23/01/2023 à 19:36, Oleg A. Arkhangelsky wrote:


I tried this *.deb (Pascal approach). It doesn't change behaviour
introduced after this patch [1]. Yes, restart for "allow-hotplug"
interfaces work but I got the same system boot lag in Jeff configuration.


In your reply to Jeff on 21/01/2023, you acknowledged it was correct 
behaviour. You get the same delay with an unplugged interface marked 
"auto". I suspect that using "allow-hotplug" instead may have been used 
as a workaround to hide the delay in the background. Not the best way to 
fix things IMO.



Cyril's latest solution seems to work. I just added "-" to /bin/sh to
deal with cases when we have a device that is really hotplug and absent:

(...)

I got fast boot (as without bad patch) and working restart. One minute
long blocking during `systemctl restart networking` when DHCP is not
respoding (as in Jeff config) is expected.


Right, but you can add --no-block to avoid the delay.

This delay is caused by dhclient which becomes a daemon only after 
acquiring an address or 1-minute time-out. A solution would be to run 
dhclient with the option -nw to become a daemon immediately.
Why should ifup wait until an IP address is acquired ? dhclient and ifup 
return status 0 anyway.


udhcpc causes a shorter delay (10s) than dhclient, but it has no option 
to run in the background from the start.


I also had another idea: interfaces marked "allow-hotplug" are brought 
up by udev events, so why not restart them by replaying events with udevadm:


udevadm trigger --action=add --subsystem-match=net

First, a summary of relevant files in the ifupdown package:

/lib/systemd/system/networking.service:
ExecStart=/sbin/ifup -a --read-environment
ExecStop=/sbin/ifdown -a --read-environment --exclude=lo

/lib/udev/rules.d/80-ifupdown.rules:
SUBSYSTEM=="net", ACTION=="add|remove", RUN+="ifupdown-hotplug"

/lib/udev/ifupdown-hotplug:
TARGET_IFACE=$(/sbin/ifquery --allow hotplug -l "$INTERFACE")
systemctl --no-block start $(systemd-escape --template ifup@.service 
$TARGET_IFACE)


/lib/systemd/system/ifup@.service:
ExecStart=/bin/sh -ec 'ifup --allow=hotplug %I; ifquery --state %I'
ExecStop=/sbin/ifdown %I

On net add events, udev runs ifupdown-hotplug which starts instantiated 
ifup@.service for interfaces marked "allow-hotplug".

ifup@.service configures interfaces marked "allow-hotplug".

Problem: when networking.service stops interfaces, it does not stop the 
instantiated ifup@*.service. The above udevadm command triggers 
ifupdown-hotplug as expected, but starting ifup@*service which are 
already started is a no-op so ifup is not run again and the interfaces 
stay down.


Is this on purpose ?

If no, the obvious fix is to stop all ifup@*.service when 
networking.service is stopped, so that they can be restarted by udev.

So I ended up adding these two lines in networking.service:

 ExecStart=udevadm trigger --action=add --subsystem-match=net
 ExecStop=systemctl --no-block stop ifup@*.service

Maybe there is a more elegant way to stop ifup@*.service, e.g. using 
systemd unit dependencies but I am not familiar enough with this topic.


This setup causes no delay when (re)starting networking.service by hand 
at boot time or by hand. However if an interface marked "allow-hotplug" 
was manually stopped with ifdown without stopping the associated 
ifup@.service, it is not restarted when restarting networking.service.


Any thoughts ?

Additional questions:

networking.service starts only interfaces marked "auto", so shouldn't it 
stop only those interfaces ?


Alternatively, interfaces marked "allow-hotplug" are started by udev 
even if networking.service is not started (not started yet, stopped, 
disabled). This brings a significant difference between interfaces 
marked "auto" and "allow-hotplug": interfaces marked "allow-hotplug" are 
started when booting in recovery mode while interfaces marked "auto" are 
started only when booting in normal mode (multi-user.target). Is it 
desirable ?

Bug#990447: Similar problems

2023-02-01 Thread Pascal Hambourg


On 02/02/2023 at 00:33, Phil Dibowitz wrote:


And I've run `grub-install` with my EFI dir mounted. What's interesting 
is the version in EFI is different than the version staged by the package:


```
# sum /usr/lib/shim/shimx64.efi /boot/EFI/EFI/debian/shimx64.efi
47979   918 /usr/lib/shim/shimx64.efi
36147   913 /boot/EFI/EFI/debian/shimx64.efi
```


You must compare with /usr/lib/shim/shimx64.efi.signed from shim-signed.

Bug#1041497: vmm: fails to run with python3 >= 3.10

2023-07-20 Thread Pascal Volk


On 2023-07-19 20:20, Bernd Zeimetz wrote:

[...]
AttributeError: module 'collections' has no attribute 'Callable'


collections.Callable is collections.abs.Callable since Python 3.10
[...]


Hi there,

this has been fixed in 
https://bitbucket.org/pvo/vmm/commits/29d157a4ee8f019fde92aa74976e9f168386a0fe/raw


Regards,
Pascal

Bug#850291: gdm3: does not work without gnome-session

2019-06-12 Thread Pascal Liehne

Package: gdm3
Version: 3.30.2-3
Followup-For: Bug #850291

Hi,

It looks like the bug is back. After install of gdm3 and gnome-terminal
in one command and login I get only the background image.

HowTo reproduce:
- Install Debian 10 RC1 via Netinstaller without additional software
- run: apt-get install gdm3 gnome-terminal
- reboot, so gdm3 ist started
- login
- you will see only the background image.

Workarounds:
a) Install gdm3 and gnome-terminal in two commands:
- apt-get install gdm3
- apt-get install gnome-terminal
On this way gnome-session{,-common} will be installed automaticaly

b) Install gnome-session manualy

It didn't helped to
- switch to sid and run dist-upgrade
- upgrade gmd3 from experimental

-- System Information:
Debian Release: 10.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-5-amd64 (SMP w/1 CPU core)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gdm3 depends on:
ii  accountsservice   0.6.45-2
ii  adduser   3.118
ii  dconf-cli 0.30.1-2
ii  dconf-gsettings-backend   0.30.1-2
ii  debconf [debconf-2.0] 1.5.71
ii  gir1.2-gdm-1.03.30.2-3
ii  gnome-session-bin 3.30.1-2
ii  gnome-settings-daemon 3.30.2-3
ii  gnome-shell   3.30.2-9
ii  gnome-terminal [x-terminal-emulator]  3.30.2-2
ii  gsettings-desktop-schemas 3.28.1-1
ii  libaccountsservice0   0.6.45-2
ii  libaudit1 1:2.8.4-3
ii  libc6 2.28-10
ii  libcanberra-gtk3-00.30-7
ii  libcanberra0  0.30-7
ii  libgdk-pixbuf2.0-02.38.1+dfsg-1
ii  libgdm1   3.30.2-3
ii  libglib2.0-0  2.58.3-2
ii  libglib2.0-bin2.58.3-2
ii  libgtk-3-03.24.5-1
ii  libkeyutils1  1.6-6
ii  libpam-modules1.3.1-5
ii  libpam-runtime1.3.1-5
ii  libpam-systemd241-5
ii  libpam0g  1.3.1-5
ii  librsvg2-common   2.44.10-2.1
ii  libselinux1   2.8-1+b1
ii  libsystemd0   241-5
ii  libwrap0  7.6.q-28
ii  libx11-6  2:1.6.7-1
ii  libxau6   1:1.0.8-1+b2
ii  libxcb1   1.13.1-2
ii  libxdmcp6 1:1.1.2-3
ii  lsb-base  10.2019051400
ii  mutter [x-window-manager] 3.30.2-7
ii  policykit-1   0.105-25
ii  procps2:3.3.15-2
ii  ucf   3.0038+nmu1
ii  x11-common1:7.7+19
ii  x11-xserver-utils 7.7+8

Versions of packages gdm3 recommends:
ii  at-spi2-core2.30.0-7
ii  desktop-base10.0.2
ii  x11-xkb-utils   7.7+4
ii  xserver-xephyr  2:1.20.4-1
ii  xserver-xorg1:7.7+19
ii  zenity  3.30.0-2

Versions of packages gdm3 suggests:
pn  gnome-orca
pn  libpam-fprintd
ii  libpam-gnome-keyring  3.28.2-5

-- debconf information:
* shared/default-x-display-manager: gdm3
  gdm3/daemon_name: /usr/sbin/gdm3

Bug#847590:

2016-12-10 Thread Pascal Obry


And the new version 24.2.0-5 just released is working fine.

-- 
  Pascal Obry /  Magny Les Hameaux (78)

  The best way to travel is by means of imagination

  http://www.obry.net

  gpg --keyserver keys.gnupg.net --recv-key F949BD3B

Bug#854258: firefox-esr: firefox crashes every few seconds or minutes with a crash handler dialog since last update

2017-02-05 Thread Pascal Legrand


Hello,
same problem here.
What is the way to downgrade 45.7.0esr-1 ?

Bug#994971: OpenCL not working with latest Nvidia driver

2021-09-24 Thread Pascal Obry



Package: nvidia-driver
Version: 470.57.02-3
Severity: grave

I'm currently using GNU/Debian sid. The current NVidia driver is
470.57.02-2 and OpenCL is working fine.

$ clinfo 

Number of platforms   1
  Platform Name   NVIDIA CUDA
  Platform Vendor NVIDIA Corporation
  Platform Version    OpenCL 3.0 CUDA
11.4.94
  ...

There is a new version available 470.57.02-3 and when installed OpenCL
is not supported. clinfo report that there is 0 platform
supported/detected.

I have this issue with kernel 5.10.0-8-amd64 and new 5.14. The only
solution I have found at this point is to revert the NVidia driver to
470.57.02-3 and kernel 5.10.

I cannot tell if this is a kernel issue or an NVidia driver one. Maybe
someone with more knowledge on this area could help finding out.

Thanks,

-- 
  Pascal Obry /  Magny Les Hameaux (78)

  The best way to travel is by means of imagination

  http://www.obry.net

  gpg --keyserver keys.gnupg.net --recv-key F949BD3B

Bug#994971: OpenCL not working with latest Nvidia driver

2021-09-26 Thread Pascal Obry


Hi Klaus,

> Thats caused as the modprobe config was dropped. Without, the needed
> modules are not loaded automatically anymore.
> 
> A simple `modprobe nvidia-current-uvm` fixes the issue temporarily.
> However, the modprobe config needs to come back.

Will test this.

> By the way, I would rate this as a normal bug instead of grave.

I fully agree by re-reading the rating description. Sorry for that.

Thanks,

-- 
  Pascal Obry /  Magny Les Hameaux (78)

  The best way to travel is by means of imagination

  http://www.obry.net

  gpg --keyserver keys.gnupg.net --recv-key F949BD3B


signature.asc
Description: This is a digitally signed message part

Bug#994971: closed by Debian FTP Masters (reply to Andreas Beckmann ) (Bug#994971: fixed in nvidia-graphics-drivers 470.63.01-1)

2021-09-30 Thread Pascal Obry


Hello !

Just installed 470.63.01-1 this morning and I can confirm that the
issue is fixed. I have OpenCL activated without any other action.

Thanks a lot for the quick resolution.

Have a nice day,


-- 
  Pascal Obry /  Magny Les Hameaux (78)

  The best way to travel is by means of imagination

  http://www.obry.net

  gpg --keyserver keys.gnupg.net --recv-key F949BD3B


signature.asc
Description: This is a digitally signed message part

Bug#938794: vmm: Python2 removal in sid/bullseye

2021-11-07 Thread Pascal Volk

On 25/05/2020 20.05, Pascal Volk wrote:
> 
> Hi Martin and Moritz,
> 
> vmm is in a `beauty sleep' - not yet dead.
> There's the v0.7.x¹ branch which requires Python (≥ 3.2).
> 
> I hope I'll find some time for vmm soon

Hi Martin and Moritz,

I finally had the time to release vmm-0.7.0. :-)
The code is available at:
https://bitbucket.org/pvo/vmm/commits/tag/vmm-0.7.0

Regards,
Pascal
-- 
Ubuntu is an ancient African word meaning “I can’t install Debian.”
 -- unknown

Bug#873327: aegisub FTBFS with luajit 2.1

2018-10-26 Thread Pascal Mons

I believe I have successfully build from the latest Debian source 
aegisub_3.2.2+dfsg.orig the application Aegisub.


This build follows the Debian guidelines and use the latest available system 
libraries e.g. luajit_2.1.0~beta3+dfsg-5.1

To achieve the result I did use the patch mentioned here by Paul and coming 
from openSUSE taking care of luajit 2.1.


https://build.opensuse.org/package/view_file/multimedia:apps/aegisub/luabins.patch?expand=1


I did as well add a add-unicode-international-include-unistr.h.patch


I am using this list of patches in order to build properly (from 
debian/patches/series):


fix-pthread.patch
only-add-timestamp-in-build-credit.patch
change-aegisub-command.patch
openal-workaround.patch
change-default-dictionary-search-path.patch
#link-against-system-luajit.patch
escape-sequence-lua-5.2.patch
link-against-system-luajit-and-remove-vendor-luajit-dependency.patch
add-libatomic-dependency.patch
add-unicode-international-include-unistr.h.patch
add-luabins-support-for-lua5.2-luajit-2.1.patch


The aegisub Debian packages are build and available for the last 4 maintained 
Ubuntu releases in my Launchpad PPA Photo Video Applications.


https://launchpad.net/~anton+/+archive/ubuntu/photo-video-apps


Unfortunately the upstream source currently hosted at 
GitHub and previously mentioned here, is 
poorly maintained to say the least since 2014 / 2015, as it looks like there 
isn't any active developer to speak of, taking care of it.


I did just verify in the GitHub git how they did manage to solve the luajit 2.1 
FTBFS as Paul commented earlier:


'The upstream IRC channel mentioned that this bug is fixed in git master

...

I wasn't able to find the patch in upstream, likely fixed another way.'


For sure, they just ditched the system luajit 2.1 libraries and forced use of 
the older luajit bundled in their vendor sources. Here is the commit describing 
the action in their 'master' git:


commit bc157d9bbc00860fb7019b9c869317809a350ef7
Author: Thomas Goyne 
Date:   Sat Mar 3 12:44:31 2018 -0800

Also stub out the `system` lua module that newer versions of busted use


I believe their master git maintained at GitHub is utterly not properly 
maintained at all and unreliable period.


If properly patched, the Debian source aegisub_3.2.2+dfsg can still be build 
properly.

I believe as well that aegisub should be back soon in debian testing.


https://tracker.debian.org/news/874946/aegisub-removed-from-testing/

Bug#914175: lightning is not installable after binNMUs

2018-11-23 Thread Pascal Legrand


Same problem here.
No more lightning after upgrading thunderbird to 1:60.3.0-1+b1

--
Pascal

Bug#1015976: Should vmm be removed?

2022-07-25 Thread Pascal Volk

On 7/24/22 18:05, Moritz Muehlenhoff wrote:
> Source: vmm
> Version: 0.6.2-2
> Severity: serious
> 
> Your package came up as a candidate for removal from Debian:
> - Still depends on Python 2
> - Last upload in 2017, removed from testing since 2019
> 
> If you disagree and want to continue to maintain this package,
> please just close this bug (and fix the open issues).
> 

Hi Moritz,

looks like Bernd Zeimetz has taken over the maintenance for vmm. :-)
https://salsa.debian.org/debian/vmm/-/commit/5f5c7ef13ed33c60fdb0d4eb140370d9593bce56

Bernd, that's why I've added you to CC.


Regards,
Pascal
-- 
Ubuntu is an ancient African word meaning “I can’t install Debian.”
 -- unknown

Bug#883313: OpenCL clCreateContext fails in 384.x

2017-12-02 Thread Pascal Obry


Package: nvidia-driver
Version: 384.98-2
Severity: grave

With the latest update (384.x) OpenCL does not work, it is possible to
reproduce the issue with clinfo:

clCreateContext(NULL, ...) [default]

The same error is reported by other applications like darktable.

This was working with the version 375.x.

Let me know if you need additional information or do some testing on my
side.

Thanks,

-- 
  Pascal Obry /  Magny Les Hameaux (78)

  The best way to travel is by means of imagination

  http://www.obry.net

  gpg --keyserver keys.gnupg.net --recv-key F949BD3B

Bug#883313: OpenCL clCreateContext fails in 384.x

2017-12-02 Thread Pascal Obry


This bug is actually the same as:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883303

And the same fix works for me:

   cd /usr/lib/x86_64-linux-gnu
   sudo ln -s nvidia/current/libnvidia-ptxjitcompiler.so.1 .

So after all that seems a simple packaging issue.

Thanks,

-- 
  Pascal Obry /  Magny Les Hameaux (78)

  The best way to travel is by means of imagination

  http://www.obry.net

  gpg --keyserver keys.gnupg.net --recv-key F949BD3B

Bug#883785: libvirtd 3.10 segfault when starting a VM

2017-12-07 Thread Pascal Obry


Package: libvirt
Version: 3.10
Severity: grave

With libvirt version 3.10 I cannot start a VM. Reverting to 3.0
(Debian/stable) all is fine. This was initially found in GNOME-Boxes
but I have been able to reproduce on the command line using virsh.

Note also that I had the same issue with 3.9.

On one console:

$ LIBVIRT_DEBUG=1 gdb /usr/sbin/libvirtd

On a second console, I tried to start the VM:

$ virsh start boxes-winxp

Then I got this exception from libvirtd:

Thread 5 "libvirtd" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7febad4a5700 (LWP 7867)]
0x7feb94b109c8 in virStorageFileReportBrokenChain ()
   from /usr/lib/libvirt/connection-driver/libvirt_driver_storage.so
(gdb) bt
#0  0x7feb94b109c8 in virStorageFileReportBrokenChain ()
   from /usr/lib/libvirt/connection-driver/libvirt_driver_storage.so
#1  0x7feb7d266da3 in qemuDomainDetermineDiskChain ()
   from /usr/lib/libvirt/connection-driver/libvirt_driver_qemu.so
#2  0x7feb7d28eec2 in qemuProcessPrepareHost ()
   from /usr/lib/libvirt/connection-driver/libvirt_driver_qemu.so
#3  0x7feb7d294b71 in qemuProcessStart ()
   from /usr/lib/libvirt/connection-driver/libvirt_driver_qemu.so
#4  0x7feb7d2f5201 in ?? ()
   from /usr/lib/libvirt/connection-driver/libvirt_driver_qemu.so
#5  0x7feb7d2f58e6 in ?? ()
   from /usr/lib/libvirt/connection-driver/libvirt_driver_qemu.so
#6  0x7febb9e5e077 in virDomainCreate (domain=0x7feb980008c0)
at ../../../src/libvirt-domain.c:6531
#7  0x56190ba2ed9c in ?? ()
#8  0x7febb9ec697c in virNetServerProgramDispatchCall (msg=0x56190d9e7590, 
client=0x56190d9e6fb0, server=0x56190d9d00f0, prog=0x56190d9e4f40)
at ../../../src/rpc/virnetserverprogram.c:437
#9  virNetServerProgramDispatch (prog=0x56190d9e4f40, server=0x56190d9d00f0, 
client=0x56190d9e6fb0, msg=0x56190d9e7590)
at ../../../src/rpc/virnetserverprogram.c:307
#10 0x56190ba3e988 in ?? ()
#11 0x7febb9da1c01 in virThreadPoolWorker (
opaque=opaque@entry=0x56190d9ce9f0)
at ../../../src/util/virthreadpool.c:167
#12 0x7febb9da0f78 in virThreadHelper (data=)
at ../../../src/util/virthread.c:206
#13 0x7febb68b0519 in start_thread (arg=0x7febad4a5700)
at pthread_create.c:456
#14 0x7febb65f2a5f in clone ()
at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97
(gdb) 

I noticed that running with 3.0 I had a message saying that /dev/sr0 is
not accessible. And indeed I do not have a CDROM on this machine. The
.xml were migrated from a machine with a CDROM to this new one.

Removing:


  
  
  
  
  


Seems to fix the issue. Yet, libvirt should not crash on this. And the
backtrace makes sense with this fix BTW.

Please let me know if you need additional information.

Thanks,

-- 
  Pascal Obry /  Magny Les Hameaux (78)

  The best way to travel is by means of imagination

  http://www.obry.net

  gpg --keyserver keys.gnupg.net --recv-key F949BD3B

Bug#895508: closed by Jeremy Bicha (Bug#895504: fixed in evolution 3.28.1-2)

2018-04-12 Thread Pascal Obry


Fixed now indeed.

Thanks for the quick fix.

-- 
  Pascal Obry /  Magny Les Hameaux (78)

  The best way to travel is by means of imagination

  http://www.obry.net

  gpg --keyserver keys.gnupg.net --recv-key F949BD3B

signature.asc
Description: This is a digitally signed message part

Bug#873765: same issue for me

2017-09-25 Thread Pascal Obry

I have the same issue since a month now. Any idea to when the GNOME Shell
3.26 will be part of Debian/unstable.

Thanks,

-- 
  Pascal Obry /  Magny Les Hameaux (78)

  The best way to travel is by means of imagination

  http://photos.obry.net
  http://www.obry.net

  gpg --keyserver keys.gnupg.net --recv-key F949BD3B

Bug#954311: Not just rendering issues...

2020-04-05 Thread Pascal Giard

Thanks A LOT for the /etc/drirc trick, it fixed the problem detailed below
for me.
Took me over an hour to figure out what was wrong and to end up on this bug
report.

I have a Thinkpad T480 (Intel UHD 620).

The new iris driver causes all my video players to crash (e.g., VLC or mpv)
and prevents Zoom from converting my recorded sessions.

Best regards,

-Pascal
--
Homepage (http://pascal.giard.info)
École de technologie supérieure (http://etsmtl.ca)

Bug#954311: Not just rendering issues...

2020-04-08 Thread Pascal Giard

On Mon, Apr 6, 2020 at 12:05 PM Timo Aaltonen  wrote:

> On 6.4.2020 1.55, Pascal Giard wrote:
> > Thanks A LOT for the /etc/drirc trick, it fixed the problem
> > detailed below for me.
> > Took me over an hour to figure out what was wrong and to end up on this
> > bug report.
> >
> > I have a Thinkpad T480 (Intel UHD 620).
> >
> > The new iris driver causes all my video players to crash (e.g., VLC or
> > mpv) and prevents Zoom from converting my recorded sessions.
> Do you use xserver-xorg-video-intel? If yes, get rid of it.
>
>
I do use it, yes. Which driver am I suppose to use instead?

Thanks,

-Pascal

Bug#954311: Not just rendering issues...

2020-04-08 Thread Pascal Giard

Thanks for the information, I appreciate it.

Apparently I missed the transition from intel_drv to modesetting_drv.

After switching to modesetting (instead of intel) and purging
xserver-xorg-video-intel, the workaround in /etc/drirc is no longer needed.

Best regards,

-Pascal
--
Homepage (http://pascal.giard.info)
École de technologie supérieure (http://etsmtl.ca)




On Wed, Apr 8, 2020 at 10:52 AM Timo Aaltonen  wrote:

> On 8.4.2020 17.15, Pascal Giard wrote:
> > On Mon, Apr 6, 2020 at 12:05 PM Timo Aaltonen  > <mailto:tjaal...@debian.org>> wrote:
> >
> > On 6.4.2020 1.55, Pascal Giard wrote:
> > > Thanks A LOT for the /etc/drirc trick, it fixed the problem
> > > detailed below for me.
> > > Took me over an hour to figure out what was wrong and to end up on
> > this
> > > bug report.
> > >
> > > I have a Thinkpad T480 (Intel UHD 620).
> > >
> > > The new iris driver causes all my video players to crash (e.g.,
> VLC or
> > > mpv) and prevents Zoom from converting my recorded sessions.
> > Do you use xserver-xorg-video-intel? If yes, get rid of it.
> >
> >
> > I do use it, yes. Which driver am I suppose to use instead?
>
> The default, which is modesetting_drv.so from the xserver.
>
>
> --
> t
>

Bug#970356: assertion failed in vte_terminal_spawn_with_fds_async

2020-09-28 Thread Pascal Legrand




Hello,
is there a solution about this bug ?
I can't downgrade libvte-2.91-0 0.60.3-1
Then, i'm very interested by a patch or new version.

Thanks a lot for your help

Pascal

Bug#938794: vmm: Python2 removal in sid/bullseye

2020-05-25 Thread Pascal Volk

On 25/05/2020 18.06, Moritz Mühlenhoff wrote:
> 
> Hi,
> vmm seems dead upstream. Are you planning to port it to Python 3
> yourself or should it be removed?
> 
> Cheers,
> Moritz
> 

Hi Martin and Moritz,

vmm is in a `beauty sleep' - not yet dead.
There's the v0.7.x¹ branch which requires Python (≥ 3.2).

I hope I'll find some time for vmm soon


Regards,
Pascal

- - -
[1] = https://bitbucket.org/pvo/vmm/src/v0.7.x/
-- 
Ubuntu is an ancient African word meaning “I can’t install Debian.”
 -- unknown



signature.asc
Description: OpenPGP digital signature

Bug#1059167: installation-reports: installer hangs while recognizing network hardware

2023-12-20 Thread Pascal Hambourg


Hello Janusz,

On 20/12/2023 at 20:52, Janusz Bień wrote:


I understand the installer now includes non-free drivers,


No, only non-free firmware.


but I suspect  it missing one needed for my hardware, which is
Intel Ethernet Connection (7) I219-V
Intel Dual Band Wireless-AC 3168
(on the mainboard ASRock B360M-ITX/AC).


How does the installer hang ? Can you switch to the installer shell in 
tty2 with Ctrl+Alt+F2 ? If yes, can you post the output of


lspci -nnk

and attach (compressed) /var/log/syslog ?

Bug#361085: denyhosts-python2.4: /usr/bin/denyhosts contains incorrect shebang

2006-04-06 Thread Pascal Volk

Package: denyhosts-python2.4
Version: 2.2-1
Severity: grave
Tags: patch
Justification: renders package unusable

After the command `/etc/init.d/denyhosts start` denyhosts-python2.4 raises
an ImportError exception:

Starting DenyHosts: denyhostsTraceback (most recent call last):
  File "/usr/bin/denyhosts", line 5, in ?
import DenyHosts.python_version
ImportError: No module named DenyHosts.python_version

The attached patch will fix this problem.

best regards
Pascal

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)

Versions of packages denyhosts-python2.4 depends on:
ii  denyhosts-common  2.2-1  an utility to help sys admins thwa
ii  python2.4 2.4.2-2An interactive high-level object-o

denyhosts-python2.4 recommends no packages.

-- no debconf information
--- /usr/bin/denyhosts.org	2006-04-06 14:04:24.0 +0200
+++ /usr/bin/denyhosts	2006-04-06 14:14:23.0 +0200
@@ -1,4 +1,4 @@
-#!/usr/bin/env python
+#!/usr/bin/env python2.4
 import os
 import sys

Bug#348119: mail-notification: package depends on non-existant package libgnome-menu0

2006-01-15 Thread Pascal Giard

Thanks for reporting,
 I've uploaded the new package.

-Pascal

On 1/14/06, John McCutchan <[EMAIL PROTECTED]> wrote:
> Package: mail-notification
> Version: 2.0.dfsg.1-1
> Severity: grave
> Justification: renders package unusable
>
> Package should depend on libgnome-menu2 instead of libgnome-menu0.
>
> -- System Information:
> Debian Release: testing/unstable
>   APT prefers unstable
>   APT policy: (500, 'unstable')
> Architecture: i386 (i686)
> Shell:  /bin/sh linked to /bin/bash
> Kernel: Linux 2.6.14.5
> Locale: LANG=en_CA, LC_CTYPE=en_CA (charmap=ISO-8859-1)
>
> Versions of packages mail-notification depends on:
> ii  gconf22.12.1-8   GNOME configuration database 
> syste
> ii  gnome-icon-theme  2.12.1-2   GNOME Desktop icon theme
> ii  libart-2.0-2  2.3.17-1   Library of functions for 2D 
> graphi
> ii  libatk1.0-0   1.10.3-1   The ATK accessibility toolkit
> ii  libaudiofile0 0.2.6-6Open-source version of SGI's 
> audio
> ii  libbonobo2-0  2.10.1-1   Bonobo CORBA interfaces library
> ii  libbonoboui2-02.10.1-1   The Bonobo UI library
> ii  libc6 2.3.5-11   GNU C Library: Shared libraries 
> an
> ii  libeel2-2 2.12.2-2   Eazel Extensions Library (for 
> GNOM
> ii  libesd0   0.2.36-3   Enlightened Sound Daemon - Shared
> ii  libgail-common1.8.8-1GNOME Accessibility 
> Implementation
> ii  libgail17 1.8.8-1GNOME Accessibility 
> Implementation
> ii  libgconf2-4   2.12.1-8   GNOME configuration database 
> syste
> ii  libgcrypt11   1.2.2-1LGPL Crypto library - runtime 
> libr
> ii  libglade2-0   1:2.5.1-2  library to load .glade files at 
> ru
> ii  libglib2.0-0  2.8.5-1The GLib library of C routines
> ii  libgmime2.1   2.1.18-1   MIME library, unstable version
> ii  libgnome-desktop-22.12.2-2   Utility library for loading 
> .deskt
> ii  libgnome-keyring0 0.4.6-2GNOME keyring services library
> ii  libgnome-menu02.10.2-1   an implementation of the 
> freedeskt
> ii  libgnome2-0   2.12.0.1-4 The GNOME 2 library - runtime 
> file
> ii  libgnomecanvas2-0 2.12.0-2   A powerful object-oriented 
> display
> ii  libgnomeui-0  2.12.0-2   The GNOME 2 libraries (User 
> Interf
> ii  libgnomevfs2-02.12.2-3   The GNOME virtual file-system 
> libr
> ii  libgnutls11   1.0.16-14  GNU TLS library - runtime library
> ii  libgpg-error0 1.1-4  library for common error values 
> an
> ii  libgtk2.0-0   2.8.10-1   The GTK+ graphical user interface
> ii  libice6   6.9.0.dfsg.1-3 Inter-Client Exchange library
> ii  libjpeg62 6b-11  The Independent JPEG Group's JPEG
> ii  liborbit2 1:2.12.4-1 libraries for ORBit2 - a CORBA 
> ORB
> ii  libpango1.0-0 1.10.2-1   Layout and rendering of 
> internatio
> ii  libpopt0  1.7-5  lib for parsing cmdline 
> parameters
> ii  libsasl2  2.1.19-1.8 Authentication abstraction 
> library
> ii  libsm66.9.0.dfsg.1-3 X Window System Session 
> Management
> ii  libstartup-notification0  0.8-1  library for program launch 
> feedbac
> ii  libtasn1-20.2.17-1   Manage ASN.1 structures (runtime)
> ii  libx11-6  6.9.0.dfsg.1-3 X Window System protocol client 
> li
> ii  libxext6  6.9.0.dfsg.1-3 X Window System miscellaneous 
> exte
> ii  libxml2   2.6.23-1.1 GNOME XML library
> ii  libxrender1   1:0.9.0.2-1X Rendering Extension client 
> libra
> ii  xlibs 6.9.0.dfsg.1-3 X Window System client libraries 
> m
> ii  zlib1g1:1.2.3-9  compression library - runtime
>
> mail-notification recommends no packages.
>
> -- no debconf information
>
>


--
Homepage (http://organact.mine.nu)
Debian GNU/Linux (http://www.debian.org)

Bug#327896: php4-idn: idn.so is stored in the wrong directory

2005-09-12 Thread Pascal Volk

Package: php4-idn
Version: 1.1-5
Severity: grave
Justification: renders package unusable

The php4-extension idn.so is stored in /usr/lib/php4/20050606, but php4's
(4.3.10-15) API-Extension is 20020429 (/usr/lib/php4/20020429).
When the Apache web server is starting, it prints the following message:

Starting web server: apachePHP Warning:  Unknown(): Unable to load dynamic
library '/usr/lib/php4/20020429/idn.so' - /usr/lib/php4/20020429/idn.so: cannot
open shared object file: No such file or directory in Unknown on line 0

Workaround: Create a symlink
`cd /usr/lib/php4/20020429/`
`ln -s ../20050606/idn.so .

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.13
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)

Versions of packages php4-idn depends on:
ii  libapache-mod-php4 [phpapi-2 4:4.3.10-15 server-side, HTML-embedded scripti
ii  libc62.3.5-6 GNU C Library: Shared libraries an
ii  libidn11 0.5.18-1GNU libidn library, implementation
ii  php4-cli [phpapi-20020918]   4:4.3.10-15 command-line interpreter for the p

php4-idn recommends no packages.

-- no debconf information


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

Bug#298964: Fixed in NMU of atris 1.0.7.dfsg1-0.1

2005-03-13 Thread Pascal Giard

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Micah Anderson wrote:
| No problem, just working with the Bug Squashing Party trying to close
| as many Grave RC bugs as possible this weekend.
:)
| I would suggest that you contact upstream about this font, because
| they probably should not be distributing it as is.
I've already notified the upstream about this ;)
I suggested him to use FreeSans from ttf-freefont, a package under GPLv2.
| Also, you don't
| want them to distribute it in the next release, or you will have to
| pull it out of the .orig.tar.gz again :)
i'll be more carefull and remove it if they don't react.
keep up the good work!
- -Pascal
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCNN+l1Lfd97FsypURAn6aAJ4sM/fdIHtISNFuRx1kU3RSVXKGPwCfQ6xM
wb+e+XK/PS77IEMp1vARdyk=
=ucoE
-END PGP SIGNATURE-
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#292258: libgtksourceview-cil: Will have file clash with upcoming libgtksourceview-common (1.1.2)

2005-03-15 Thread Pascal Giard

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
the fix is as simple as removing that file from the debian/install file...
i might provide an NMU... if i see that this issue doesn't get solved.
- -Pascal
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCNpy71Lfd97FsypURAhZLAJ4lNJpeuMPUU6m1Zo6ZrasZnfeT6wCeJSWL
A0AwDQ/DwOvtLuICT4juL/I=
=Ms2J
-END PGP SIGNATURE-
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#316455: kernel-source-2.6.11: Fails to boot since 2.6.11-4

2005-06-30 Thread Pascal Giard


Package: kernel-source-2.6.11-amd64-generic
Version: 2.6.11-4
Severity: critical
Justification: breaks the whole system

(Sorry if this is a dupe, i had filled it against 
kernel-image-2.6.11-amd64-generic).


Since kernel-image-2.6.11-amd64-generic 2.6.11-4, the kernel-image won't 
boot.


The first error message says something like:
" Can't load shared object file libc.so.6 "
The second error message says it can't find sda1.

My hypothesis is that the necessary modules for my onboard SATA
controller are no longer included in the initrd image.

I HAVEN'T modified /etc/mkinitrd/mkinitrd.conf.

I've a pretty common Asus K8V-X motherboard which SATA ctrler
requires at least scsi_mod, sata_via and libata to work.

Booting with the current kernel-image-2.6.8-amd64-generic image works fine.
I'm happy i kept my very old image before upgrading 2.6.11!!

-Pascal
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.8-11-amd64-generic
Locale: LANG=fr_CA, LC_CTYPE=fr_CA (charmap=ISO-8859-1)


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

Bug#316453: kernel-image-2.6.11-amd64-generic: Fails to boot since 2.6.11-4

2005-06-30 Thread Pascal Giard


Package: kernel-image-2.6.11-amd64-generic
Version: 2.6.11-4
Severity: critical
Justification: breaks the whole system

Since 2.6.11-4, the kernel-image won't boot.

The first error message says something like:
" Can't load shared object file libc.so.6 "
The second error message says it can't find sda1.

My hypothesis is that the necessary modules for my onboard SATA
controller are no longer included in the initrd image.

I HAVEN'T modified /etc/mkinitrd/mkinitrd.conf.

I've a pretty common Asus K8V-X motherboard which SATA ctrler
requires at least scsi_mod, sata_via and libata to work.

Booting with the current kernel-image-2.6.8-amd64-generic image works fine.
I'm happy i kept my very old image before upgrading 2.6.11!!

-Pascal
-- System Information:
Debian Release: testing/unstable
 APT prefers unstable
 APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.8-11-amd64-generic
Locale: LANG=fr_CA, LC_CTYPE=fr_CA (charmap=ISO-8859-1)



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

Bug#316476: kernel-source-2.6.11: Fails to boot since 2.6.11-4

2005-06-30 Thread Pascal Giard

Package: kernel-source-2.6.11
Version: 2.6.11-4
Severity: critical
Justification: breaks the whole system

(Sorry if this is a dupe, i had filled it against
kernel-image-2.6.11-amd64-generic).

Since kernel-image-2.6.11-amd64-generic 2.6.11-4, the kernel-image won't
boot.

The first error message says something like:
" Can't load shared object file libc.so.6 "
The second error message says it can't find sda1.

My hypothesis is that the necessary modules for my onboard SATA
controller are no longer included in the initrd image.

I HAVEN'T modified /etc/mkinitrd/mkinitrd.conf.

I've a pretty common Asus K8V-X motherboard which SATA ctrler
requires at least scsi_mod, sata_via and libata to work.

Booting with the current kernel-image-2.6.8-amd64-generic image works fine.
I'm happy i kept my very old image before upgrading 2.6.11!!

-Pascal
-- System Information:
Debian Release: testing/unstable
 APT prefers unstable
 APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.8-11-amd64-generic
Locale: LANG=fr_CA, LC_CTYPE=fr_CA (charmap=ISO-8859-1)

Bug#316476: kernel-source-2.6.11: Fails to boot since 2.6.11-4

2005-07-01 Thread Pascal Giard

Thanks for fixing my mess.
I wasn't sure if the kernel-image-2.6.11-amd64-generic one was going
to reach anyone since bugs.debian.org was showing "unknown
maintainer".

And kernel-source-2.6.11-amd64-generic was a mistake.

Sorry about that,
won't happen again.

-Pascal

On 7/1/05, Steve Langasek <[EMAIL PROTECTED]> wrote:
> reassign 316476 kernel-image-2.6.11-amd64-generic
> merge 316476 316453
> thanks
> 
> On Fri, Jul 01, 2005 at 02:10:04AM -0400, Pascal Giard wrote:
> > Package: kernel-source-2.6.11
> > Version: 2.6.11-4
> > Severity: critical
> > Justification: breaks the whole system
> 
> > (Sorry if this is a dupe, i had filled it against
> > kernel-image-2.6.11-amd64-generic).
> 
> Well, given that you filed three bugs all about the same issue, yes, two of
> them would seem to be duplicates.
> 
> --
> Steve Langasek
> postmodern programmer
> 
> 
> BodyID:43972286.2.n.logpart (stored separately)
> 
> 


-- 
Projet MoviXMaker (http://sv.gnu.org/projects/movixmaker)
Projet [e]MoviX[2] (http://movix.sf.net)
Debian Project (http://www.debian.org)
TuxKart (Wiki (GOTM): http://netpanzer.berlios.de/tuxkart/index.php)

Bug#316476: kernel-source-2.6.11: Fails to boot since 2.6.11-4

2005-07-01 Thread Pascal Giard

Hi Frederik,

i've just tried kernel-image-2.6.11-amd64-k8 with the exact same result...

> On Fri, Jul 01, 2005 at 02:10:04AM -0400, Pascal Giard wrote:
> > Since kernel-image-2.6.11-amd64-generic 2.6.11-4, the kernel-image won't
> > boot.
> >
> > The first error message says something like:
> > " Can't load shared object file libc.so.6 "
> > The second error message says it can't find sda1.
> 
> Do you have the initrd in place, and is it linked correctly in the
> bootloader?

i'm using grub and my /boot/grub/menu.lst shows that yes, it finds it:

title   Debian GNU/Linux, kernel 2.6.11-9-amd64-k8 Default
root(hd0,0)
kernel  /boot/vmlinuz root=/dev/sda1 ro console=tty0
initrd  /boot/initrd.img
savedefault
boot

[EMAIL PROTECTED]:/home/recover$ ls -l /boot/initrd.img*
lrwxrwxrwx  1 root root  28 2005-06-30 19:39 /boot/initrd.img ->
initrd.img-2.6.11-9-amd64-k8
-rw-r--r--  1 root root 4694016 2005-06-29 23:42
/boot/initrd.img-2.6.11-9-amd64-generic
-rw-r--r--  1 root root 4730880 2005-06-30 19:39
/boot/initrd.img-2.6.11-9-amd64-k8
-rw-r--r--  1 root root 4182016 2005-06-19 03:53
/boot/initrd.img-2.6.8-11-amd64-generic
lrwxrwxrwx  1 root root  33 2005-06-19 14:07 /boot/initrd.img.old
-> initrd.img-2.6.11-9-amd64-generic

> > My hypothesis is that the necessary modules for my onboard SATA
> > controller are no longer included in the initrd image.
> >
> > I HAVEN'T modified /etc/mkinitrd/mkinitrd.conf.
> >
> > I've a pretty common Asus K8V-X motherboard which SATA ctrler
> > requires at least scsi_mod, sata_via and libata to work.
> 
> what do you have listed in your /etc/mkinitrd/modules?

it's empty... (well there are commented-out lines).
so i should use that file to specify my needed modules since mkinitrd
can't auto-detect them anymore?

> > Booting with the current kernel-image-2.6.8-amd64-generic image works fine.
> > I'm happy i kept my very old image before upgrading 2.6.11!!
> 
> the amd64-generic kernel is intended for the installer, you should
> run install 2.6.11-9-amd64-k8 instead, but this is another issue.

thanks for your help,

-Pascal
-- 
XBGM# (http://xbgm.sf.net)
MoviXMaker-2 (http://sv.gnu.org/projects/movixmaker)
[e]MoviX[2] (http://movix.sf.net)
Debian GNU/Linux (http://www.debian.org)

Bug#316476: kernel-source-2.6.11: Fails to boot since 2.6.11-4

2005-07-01 Thread Pascal Giard

Hi Frederik,

> > i've just tried kernel-image-2.6.11-amd64-k8 with the exact same result...
> 
> This is interesting. You have latest initrd-utils installed, and your
> system is up to date?

i've initrd-tools 0.1.81.1 ... the latest according to packages.debian.org.

> can you please send your mkinitrd.conf?

sure! i attached it.
Could my problem be caused by ROOT=probe that fails detecting the
needed modules?
That would be strange as it used to work...

> menu.lst looks good, do the root devices match?

yes... and 2.6.8 working confirms this.
(also, i only have one SATA drive)

i've just tried with a /etc/mkinitrd/modules that contains:
ext3
sata_via
scsi_mod
sd_mod
libata

without success same error as before ("shared object not found libc.so.6").
i regenerated the initrd.img by "dpkg -P  && apt-get install ".

-Pascal
-- 
XBGM# (http://xbgm.sf.net)
MoviXMaker-2 (http://sv.gnu.org/projects/movixmaker)
[e]MoviX[2] (http://movix.sf.net)
Debian GNU/Linux (http://www.debian.org)


mkinitrd.conf
Description: Binary data

Bug#316476: kernel-source-2.6.11: Fails to boot since 2.6.11-4

2005-07-01 Thread Pascal Giard

I was beginning to doubt that this was actually related to a change in
kernel-source so i tried going back to 2.6.11-3.

And it fails just like the others!?

So it seems it's something else that broke it and the kernel-image
package update just trigerred the problem...

Could this be related to libc6¹ ?! I doubt it as the changelog doesn't
show any change since may 10th (just before i actually bought my
current amd64).

When looking at the content of the initrd.img-2.6.11* i noticed that
there wasn't any lib/libc.so.6 but there's a lib64/libc.so.6...
Perhaps it could not find it!

So i looked into initrd.img-2.6.8-amd64-generic and noticed that
lib/libc.so.6 existed and there wasn't any lib64/libc.so.6.
Ah ah, gotcha!

Any idea what's the root cause? How can i fix this cleanly?

-Pascal
-- 
XBGM# (http://xbgm.sf.net)
MoviXMaker-2 (http://sv.gnu.org/projects/movixmaker)
[e]MoviX[2] (http://movix.sf.net)
Debian GNU/Linux (http://www.debian.org)

Bug#316453: found a "not-so-bad" solution

2005-07-09 Thread Pascal Giard

reassign 316476 initrd-tools
reassign 316453 initrd-tools
thx!

First of all, i'm reassigning this to initrd-tools as this is not
related to the kernel-source nor image.

I found a quite good solution to solve the issue.

in my /etc/mkinitrd/mkinitrd.conf, i changed:
INITRD_LD_LIBRARY_PATH=$LD_LIBRARY_PATH
to
INITRD_LD_LIBRARY_PATH=/lib:/lib64:$LD_LIBRARY_PATH

i know /lib64 is theoritically useless, but i didn't tried w/o so i'm
including it here to.

other amd64 users might encounter this problem in the near future so i
hope you guys will look at this.

thanks!

-Pascal
-- 
XBGM# (http://xbgm.sf.net)
MoviXMaker-2 (http://sv.gnu.org/projects/movixmaker)
[e]MoviX[2] (http://movix.sf.net)
Debian GNU/Linux (http://www.debian.org)

Bug#316476: Bug#316453: found a "not-so-bad" solution

2005-07-10 Thread Pascal Giard

> Under Debian /lib64 is a link to /lib.

yes i know, i was also surprised to see that it was working by adding
/lib to LD_LIBRARY_PATH in the mkinitrd.conf.

> /lib64/ld-linux-x86-64.so.2 has
> to exist. Your change should have no effect at all as LD_LIBRARY_PATH
> is usualy unset and /lib is already in the default path.

well, in my case, my /etc/ld.so.conf was:
/lib64
/usr/lib
/usr/lib64
/usr/X11R6/lib
/usr/X11R6/lib64
/usr/local/lib/
# chroot 32bit
/home/chroot-sid-i386/lib
/home/chroot-sid-i386/usr/lib
/home/chroot-sid-i386/usr/X11R6/lib
/home/chroot-sid-i386/usr/local/lib/

i changed it by prepending /lib and now it works w/o modifying the
mkinitrd.conf.
unfortunatly, i can't remember if /lib was ever there or if it was i
who removed it accidently at one point.

> Caoul you add a "set -x" to /usr/sbin/mkinitrd, reinstall the
> kernel-image and send us a log of the output please.

yes, here it is anyway...even if we know the root now...
libc.so.6 is the cornerstone, so look at it's location to compare.

-Pascal
-- 
XBGM# (http://xbgm.sf.net)
MoviXMaker-2 (http://sv.gnu.org/projects/movixmaker)
[e]MoviX[2] (http://movix.sf.net)
Debian GNU/Linux (http://www.debian.org)


with.lib.aka.working.log.gz
Description: GNU Zip compressed data


wo.lib.aka.notworking.log.gz
Description: GNU Zip compressed data

Bug#316453: Fwd: Bug#316453: found a "not-so-bad" solution

2005-07-10 Thread Pascal Giard

-- Forwarded message --
From: Pascal Giard <[EMAIL PROTECTED]>
Date: Jul 10, 2005 10:23 PM
Subject: Re: Bug#316453: found a "not-so-bad" solution
To: Goswin von Brederlow <[EMAIL PROTECTED]>


> Just a though: Ubuntu?

nope, pure Debian.

> > /lib64
> > /usr/lib
> > /usr/lib64
> > /usr/X11R6/lib64
>
> Those four are not suposed to be there and from the logs are harmfull.

alrite, i'll remove them.

-Pascal
--
XBGM# (http://xbgm.sf.net)
MoviXMaker-2 (http://sv.gnu.org/projects/movixmaker)
[e]MoviX[2] (http://movix.sf.net)
Debian GNU/Linux (http://www.debian.org)


-- 
XBGM# (http://xbgm.sf.net)
MoviXMaker-2 (http://sv.gnu.org/projects/movixmaker)
[e]MoviX[2] (http://movix.sf.net)
Debian GNU/Linux (http://www.debian.org)

Bug#389681: apt-listbugs: Reports undefined variable and fails

2006-09-27 Thread Pascal LACROIX

Same for me

Lecture de l'état des paquets... Fait
Récupération des rapports de bogue... 0% ... E: undefined local
variable or meth   od `pkg' for
Factory::BugsFactory:Module E: Le sous-processus if dpkg -s
apt-listbugs | grep -q '^Status: .* ok
installed   '; then /usr/sbin/apt-listbugs
apt || ( test $? -ne 10 || exit 10; echo
'Warning   : apt-listbugs exited
abnormally, hit enter key to continue.' 1>&2 ; read a
< /d   ev/tty ); fi a renvoyé un code
d'erreur (10) E: Failure running script if dpkg -s apt-listbugs | grep
-q '^Status: .* ok inst   alled';
then /usr/sbin/apt-listbugs apt || ( test $? -ne 10 || exit 10; echo
'Wa   rning: apt-listbugs exited
abnormally, hit enter key to continue.' 1>&2 ; read
a< /dev/tty ); fi

Reverting to version 0.0.53, and no trouble.
B. Rgds 
-- 
Pascal LACROIX

 http://kikoucalou.chez-alice.fr

La vie est pleine d'une infinité d'absurdités, qui, impudemment, n'ont
même pas besoin de paraître vraisemblables; car elles sont vraies.

Bug#463800: sox upload

2008-02-13 Thread Pascal Giard

On Feb 9, 2008 3:07 PM, Fathi Boudra <[EMAIL PROTECTED]> wrote:
> Hi,
>
> It seems you have uploaded a new upstream release of sox:
> http://packages.qa.debian.org/s/sox/news/20080209T150203Z.html
>
> and missed to fix my issue:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=463800
>
> My NMU is now useless:
> http://people.debian.org/~djpig/delayed/sox_14.0.0-5.1_amd64.changes
>
> the bug prevents to build mlt -> mlt++ -> kdenlive packages.
>
> could you upload 14.0.1-2 to fix #463800 ASAP ?
>
> TIA.
>
> cheers,
>
> Fathi

Hello Fathi!
 indeed, i've missed your bug and will release 14.0.1-2 ASAP.

I'd also like to fix the segfault on 64bit at the same time but that
requires further investigation as applying the patch AS-IS breaks the
build for me. Hopefully i'll have the time to have a look today or
tomorrow.

Cheers,

-Pascal
-- 
Homepage (http://organact.mine.nu)
Debian GNU/Linux (http://www.debian.org)
LACIME: École de technologie supérieure (http://lacime.etsmtl.ca)

Bug#434329: mail-notification: crashes on startup

2007-07-30 Thread Pascal Giard

Hi Fabiano,
 does it constantly crash or restarting it works?

I've experienced a crash at startup a couple of times, but i'm having
a hard time to reliably reproduce it.

-Pascal

On 7/23/07, Fabiano Manoel de Andrade <[EMAIL PROTECTED]> wrote:
>Hi.
>I have the same problem here. With the following messages:
> ~$ mail-notification
>
> (mail-notification:3727): GLib-GObject-WARNING **: specified instance size
> for type `MNGMimeStreamVFS' is smaller than the parent type's `GMimeStream'
> instance size
>
> (mail-notification:3727): GLib-GObject-WARNING **: cannot retrieve class for
> invalid (unclassed) type `'
>
> (mail-notification:3727): GLib-GObject-WARNING **: specified instance size
> for type `MNGMimeStreamVFS' is smaller than the parent type's `GMimeStream'
> instance size
>
> (mail-notification:3727): GLib-GObject-CRITICAL **: g_object_new: assertion
> `G_TYPE_IS_OBJECT (object_type)' failed
>
>Regards.
>Fabiano.
>


-- 
Homepage (http://organact.mine.nu)
Debian GNU/Linux (http://www.debian.org)
LACIME: École de technologie supérieure (http://lacime.etsmtl.ca)

Bug#434329: mail-notification: crashes on startup

2007-07-30 Thread Pascal Giard

tags 434329 sid help unreproducible
--
Hmm... I'm unable to reproduce this problem with current unstable
section altho i do have libgmime-2.0-2_2.2.10-1 ...

I need help in this one.

-Pascal

On 7/30/07, Fabiano Manoel de Andrade <[EMAIL PROTECTED]> wrote:
> Em Seg, 2007-07-30 às 12:00 -0400, Pascal Giard escreveu:
> > Hi Fabiano,
> >  does it constantly crash or restarting it works?
> >
> > I've experienced a crash at startup a couple of times, but i'm having
> > a hard time to reliably reproduce it.
> >
> > -Pascal
> >
> Constantly. Starting or restarting it crash. I workaround this by
> reversing the the package libgmime-2.0-2 from version (2.2.10-1) to
> version (2.2.9-1).
> Regards.
> Fabiano.
>
>


-- 
Homepage (http://organact.mine.nu)
Debian GNU/Linux (http://www.debian.org)
LACIME: École de technologie supérieure (http://lacime.etsmtl.ca)

Bug#434329: mail-notification crashes

2007-08-11 Thread Pascal Giard

On 8/11/07, Ludovic Rousseau <[EMAIL PROTECTED]> wrote:
> I am not sure the problem is with libgmime-2.0-2.
> mail-notification compiled and executed with version 2.2.9 is fine.
> mail-notification compiled and executed with version 2.2.10 is fine.
> mail-notification compiled with version 2.2.9 and executed with version
> 2.2.10 crashes.
>
> It looks like an ABI incompatibility for libgmime-2.0-2 between 2.2.9
> and 2.2.10. But I may be wrong.
>
> I propose to just rebuild mail-notification using a binNMU or something
> similar.

Hi,
 first, thanks to everyone who contributed to this thread.

Since rebuilding using latest gmime seems to fix the issue, i've just
done that and uploaded 4.1.dfsg.1-2 to Debian.

-Pascal
-- 
Homepage (http://organact.mine.nu)
Debian GNU/Linux (http://www.debian.org)
LACIME: École de technologie supérieure (http://lacime.etsmtl.ca)

Bug#434329: mail-notification crashes

2007-08-16 Thread Pascal Giard

On 8/16/07, Rúben Fonseca <[EMAIL PROTECTED]> wrote:
> Just to report that I had this problem too and the new version fixed the
> bug! Thank you!
>
> Ruben

Glad to know that!
Thanks for reporting Rùben.

-Pascal
-- 
Homepage (http://organact.mine.nu)
Debian GNU/Linux (http://www.debian.org)
LACIME: École de technologie supérieure (http://lacime.etsmtl.ca)

Bug#477643: Patches

2008-06-27 Thread Pascal Giard

Thank you for the workaround + patches, works great.

-Pascal
-- 
Homepage (http://organact.mine.nu)
Debian GNU/Linux (http://www.debian.org)
LACIME: École de technologie supérieure (http://lacime.etsmtl.ca)



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

Bug#393606: mail-notification-evolution: Fails to contact Evolution

2008-07-31 Thread Pascal Giard

Forgotten bug... Does this still apply?

Cheers,

-Pascal
-- 
Homepage (http://organact.mine.nu)
Debian GNU/Linux (http://www.debian.org)
LACIME: École de technologie supérieure (http://lacime.etsmtl.ca)



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

Bug#531461: Fix ed

2009-06-01 Thread Pascal Giard

tag 531461 + patch
thx
--
When executing "debuild -B" the binary target is not called, only binary-arch.
Hence, none of the buildd packages had /bin/ed.

Here's a patch that fixes it.
Tested on my amd64 machine.

Cheers,

-Pascal
-- 
Homepage (http://organact.mine.nu)
Debian GNU/Linux (http://www.debian.org)
LACIME: École de technologie supérieure (http://lacime.etsmtl.ca)
24c24
< binary:
---
> binary-arch: 
34c34,36
< .PHONY: build clean
---
> binary: binary-arch
> 
> .PHONY: build clean binary

Bug#506031: dovecot-common: ManageSieve security hole: virtual users can edit scripts of other virtual users

2008-11-17 Thread Pascal Volk

Package: dovecot-common
Version: 1:1.0.15-2.2
Severity: grave
Tags: security
Justification: user security hole

Stephan Bosch has reported¹ a security hole in ManageSieve implementation for
Dovecot.
"… clever virtual users that know the directory structure of the server can
read and edit script files of other virtual users with the same system uid…"

The security patch for Dovecot 1.0.15 is available at:
http://www.rename-it.nl/dovecot/1.0/dovecot-1.0.15-managesieve-v9.3-security.patch

Regards,
Pascal

1 = http://dovecot.org/list/dovecot/2008-November/035259.html


-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing'), (50, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages dovecot-common depends on:
ii  adduser   3.110  add and remove users and groups
ii  libc6 2.7-15 GNU C Library: Shared libraries
ii  libcomerr21.41.3-1   common error description library
ii  libkrb53  1.6.dfsg.4~beta1-4 MIT Kerberos runtime libraries
ii  libldap-2.4-2 2.4.11-1   OpenLDAP libraries
ii  libmysqlclient15off   5.0.51a-17 MySQL database client library
ii  libpam-runtime1.0.1-4Runtime support for the PAM librar
ii  libpam0g  1.0.1-4+b1 Pluggable Authentication Modules l
ii  libpq58.3.5-1PostgreSQL C client library
ii  libsqlite3-0  3.5.9-5SQLite 3 shared library
ii  libssl0.9.8   0.9.8g-14  SSL shared libraries
ii  openssl   0.9.8g-14  Secure Socket Layer (SSL) binary a
ii  ucf   3.0010 Update Configuration File: preserv
ii  zlib1g1:1.2.3.3.dfsg-12  compression library - runtime

dovecot-common recommends no packages.

dovecot-common suggests no packages.

-- no debconf information



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

Bug#408259: movixmaker-2: missing dep on debconf

2007-01-24 Thread Pascal Giard


Hi Lucas!
 thank you for your bug report.
I've uploaded 0.8.3-3 which fixes this bug.

I was quite surprised to receive a bug report as I was wondering if
movixmaker-2 was still in use by anyone.
Do you use it or just ran across it by testing packages?

-Pascal
--
Homepage (http://organact.mine.nu)
Debian GNU/Linux (http://www.debian.org)
École de technologie supérieure (http://www.etsmtl.ca)

Bug#400051: antigravitaattori: Segfault attempting to start; fail to load texture

2006-11-30 Thread Pascal Giard


tag 400051 + patch
quit
-

Hello Gürkan,
 i've tested 0.0.2-3 (i had to build it). Of course, i still get the
same problem except that there are more informations now that you've
modified the m3dtexture.cpp:

[EMAIL PROTECTED]:~/programmes/experimental$ antigrav
libpng error: Invalid image width
setjmp: Success
Invalid: can't load texture racer.png
Width 9900836, Height 9900840
libpng error: Invalid image width
setjmp: Success
Can't load texture road.png
Width -1508628612, Height -1508628616
Erreur de segmentation

Looking at the code, i quickly spotted the culprit: width and height.
Sometime declared as unsigned int and other times assumed png_uint_32.
That's not good!

I fixed the issue using png_uint_32 all over the place.
I've created a patch that you could include in your debian package.

The patch is attached.

-Pascal
PS: Looking at your diff, i see that you've made changes to main.cpp
and m3dtexture.cpp without using the patch system. I feel like this is
not the proper way of doing things.

I believe that only files from the debian/ directory should appear in your diff.

On 11/30/06, Gürkan Sengün <[EMAIL PROTECTED]> wrote:

dear pascal

please can you try antigravitaattori 0.0.2-3 and tell me what it says?
i don't have debian gnu/linux on a 64bit platform, so i'll need your
help to get this bug sorted out.

if your mirror is slow/doesn't have it yet, try from here:
http://gnu.ethz.ch/debian/antigrav/ (you'll need to build the source
package yourself)

thank you,
guerkan





--
Homepage (http://organact.mine.nu)
Debian GNU/Linux (http://www.debian.org)
École de technologie supérieure (http://www.etsmtl.ca)
--- antigrav-0.0.2/src/m3dtexture.h.old 2006-11-30 17:01:00.0 -0500
+++ antigrav-0.0.2/src/m3dtexture.h 2006-11-30 17:01:20.0 -0500
@@ -9,7 +9,7 @@
 {
std::string filename;
GLuint handle;
-   unsigned int width, height;
+   png_uint_32 width, height;
 };
 
 /// A texture
@@ -34,8 +34,8 @@

m3dTexture &operator=(const m3dTexture &t);
 
-   static int loadPNG(const char *filename, unsigned char **data, unsigned 
int *width, unsigned int *height);
-   static int savePNG(const char *filename, const unsigned char *data, 
unsigned int width, unsigned int height);
+   static int loadPNG(const char *filename, unsigned char **data, 
png_uint_32 *width, png_uint_32 *height);
+   static int savePNG(const char *filename, const unsigned char *data, 
png_uint_32 width, png_uint_32 height);
static int screenshot(const char *filename);

static GLuint loadTexture(const char *filename);
@@ -48,8 +48,8 @@
static void pngWriteCallbackSTDIO(png_structp pngPtr, png_bytep data, 
png_size_t length);
static void pngFlushCallbackSTDIO(png_structp pngPtr);

-   static int loadPNG(unsigned char **data, unsigned int *width, unsigned 
int *height, void *handle, void (*pngReadCallback)(png_structp ctx, png_bytep 
area, png_size_t size));
-   static int savePNG(const unsigned char *data, unsigned int width, 
unsigned int height, void *handle, void (*pngWriteCallback)(png_structp pngPtr, 
png_bytep data, png_size_t length), void (*pngFlushCallback)(png_structp 
pngPtr));
+   static int loadPNG(unsigned char **data, png_uint_32 *width, 
png_uint_32 *height, void *handle, void (*pngReadCallback)(png_structp ctx, 
png_bytep area, png_size_t size));
+   static int savePNG(const unsigned char *data, png_uint_32 width, 
png_uint_32 height, void *handle, void (*pngWriteCallback)(png_structp pngPtr, 
png_bytep data, png_size_t length), void (*pngFlushCallback)(png_structp 
pngPtr));
 };
 
 #endif
--- antigrav-0.0.2/src/m3dtexture.cpp.old   2006-11-30 17:00:56.0 
-0500
+++ antigrav-0.0.2/src/m3dtexture.cpp   2006-11-30 17:19:53.0 -0500
@@ -104,6 +104,7 @@
if(loadPNG(texUnits[n].filename.c_str(), &data, 
&(texUnits[n].width), &(texUnits[n].height)) != 0)
{
fprintf(stderr, "Invalid: can't load texture %s\n", 
texUnits[n].filename.c_str());
+   fprintf(stderr, "Width %d, Height 
%d\n",&(texUnits[n].width), &(texUnits[n].height));
return -1;
}

@@ -148,6 +149,7 @@
if(loadPNG(texUnits[n].filename.c_str(), &data, 
&(texUnits[n].width), &(texUnits[n].height)) != 0)
{
fprintf(stderr, "Invalid: can't load texture %s\n", 
texUnits[n].filename.c_str());
+   fprintf(stderr, "Width %d, Height 
%d\n",&(texUnits[n].width), &(texUnits[n].height));
return -1;
}

@@ -204,7 +206,7 @@
@param height a pointer where to store the image width
@return 0 on success, -1

Bug#400051: antigravitaattori: Segfault attempting to start; fail to load texture

2006-12-01 Thread Pascal Giard


Hi Gürkan,


On 12/1/06, Gürkan Sengün <[EMAIL PROTECTED]> wrote:

I've applied and tried your patch, but failed, see logs at
http://gnu.ethz.ch/debian/antigrav/


It seems that the patch was only applied to  src/m3dtexture.h and not
src/m3dtexture.cpp . Look carefully, both files are modified in that
patch.


If you get it to work, I'll be glad to upload it.


To get it to work, i simply follow those steps:
[EMAIL PROTECTED]:~/programmes/experimental/t$ tar -zxvf
antigrav_0.0.2.orig.tar.gz
[EMAIL PROTECTED]:~/programmes/experimental/t$ patch -p0 < png_amd64_fix.diff
patching file antigrav-0.0.2/src/m3dtexture.h
patching file antigrav-0.0.2/src/m3dtexture.cpp
[EMAIL PROTECTED]:~/programmes/experimental/t$ cd antigrav-0.0.2 && debuild -B

cheers,

-Pascal
--
Homepage (http://organact.mine.nu)
Debian GNU/Linux (http://www.debian.org)
École de technologie supérieure (http://www.etsmtl.ca)

Bug#400051: antigravitaattori: Segfault attempting to start; fail to load texture

2006-12-01 Thread Pascal Giard


Hello Gürkan,

 please see below :-)

On 12/1/06, Pascal Giard <[EMAIL PROTECTED]> wrote:
[...]

To get it to work, i simply follow those steps:
[EMAIL PROTECTED]:~/programmes/experimental/t$ tar -zxvf
antigrav_0.0.2.orig.tar.gz
[EMAIL PROTECTED]:~/programmes/experimental/t$ patch -p0 < png_amd64_fix.diff
patching file antigrav-0.0.2/src/m3dtexture.h
patching file antigrav-0.0.2/src/m3dtexture.cpp
[EMAIL PROTECTED]:~/programmes/experimental/t$ cd antigrav-0.0.2 && debuild -B


Oops, there's a missing info here.
I copied over the debian directory from your 0.0.2-3 diff after
extracting the orig.tar.gz.

I'm attaching another patch which has been created against your
modified versions of m3dtexture.{h,cpp} . So if you prefer, you can
use this one.

cheers,

-Pascal
--
Homepage (http://organact.mine.nu)
Debian GNU/Linux (http://www.debian.org)
École de technologie supérieure (http://www.etsmtl.ca)

Bug#400051: antigravitaattori: Segfault attempting to start; fail to load texture

2006-12-01 Thread Pascal Giard


Sorry, here's the patch...

-Pascal... who's going to bed
--
Homepage (http://organact.mine.nu)
Debian GNU/Linux (http://www.debian.org)
École de technologie supérieure (http://www.etsmtl.ca)
--- antigrav-0.0.2/src/m3dtexture.cpp   2006-12-01 23:12:39.0 -0500
+++ antigrav-0.0.2/src/m3dtexture.cpp.new   2006-12-01 23:14:08.0 
-0500
@@ -206,7 +206,7 @@
@param height a pointer where to store the image width
@return 0 on success, -1 on failure
 */
-int m3dTexture::loadPNG(const char *filename, unsigned char **data, unsigned 
int *width, unsigned int *height)
+int m3dTexture::loadPNG(const char *filename, unsigned char **data, 
png_uint_32 *width, png_uint_32 *height)
 {
FILE *f;
int result;
@@ -223,7 +223,7 @@
return result;
 }
 
-int m3dTexture::loadPNG(unsigned char **data, unsigned int *width, unsigned 
int *height, void *handle, void (*pngReadCallback)(png_structp ctx, png_bytep 
area, png_size_t size))
+int m3dTexture::loadPNG(unsigned char **data, png_uint_32 *width, png_uint_32 
*height, void *handle, void (*pngReadCallback)(png_structp ctx, png_bytep area, 
png_size_t size))
 {
png_structp pngPtr;
png_infop pngInfoPtr;
@@ -260,7 +260,7 @@
png_set_read_fn(pngPtr, handle, pngReadCallback);
 
png_read_info(pngPtr, pngInfoPtr);
-   png_get_IHDR(pngPtr, pngInfoPtr, (png_uint_32*)width, 
(png_uint_32*)height, &bitDepth, &colorType, &interlaceType, NULL, NULL);
+   png_get_IHDR(pngPtr, pngInfoPtr, width, height, &bitDepth, &colorType, 
&interlaceType, NULL, NULL);
 
png_set_strip_16(pngPtr);
 
@@ -281,7 +281,7 @@
}

png_read_update_info(pngPtr, pngInfoPtr);
-   png_get_IHDR(pngPtr, pngInfoPtr, (png_uint_32*)width, 
(png_uint_32*)height, &bitDepth, &colorType, &interlaceType, NULL, NULL);
+   png_get_IHDR(pngPtr, pngInfoPtr, width, height, &bitDepth, &colorType, 
&interlaceType, NULL, NULL);

(*data) = new unsigned char[(*width) * (*height) * 
pngInfoPtr->channels];
if((*data) == NULL)
@@ -314,7 +314,7 @@
return 0;
 }
 
-int m3dTexture::savePNG(const char *filename, const unsigned char *data, 
unsigned int width, unsigned int height)
+int m3dTexture::savePNG(const char *filename, const unsigned char *data, 
png_uint_32 width, png_uint_32 height)
 {
FILE *f;
int result;
@@ -347,7 +347,7 @@
fflush(f);
 }
 
-int m3dTexture::savePNG(const unsigned char *data, unsigned int width, 
unsigned int height, void *handle, void (*pngWriteCallback)(png_structp pngPtr, 
png_bytep data, png_size_t length), void (*pngFlushCallback)(png_structp 
pngPtr))
+int m3dTexture::savePNG(const unsigned char *data, png_uint_32 width, 
png_uint_32 height, void *handle, void (*pngWriteCallback)(png_structp pngPtr, 
png_bytep data, png_size_t length), void (*pngFlushCallback)(png_structp 
pngPtr))
 {
png_structp pngPtr;
png_infop pngInfoPtr;
@@ -437,7 +437,7 @@
 GLuint m3dTexture::loadTexture(const char *filename)
 {
unsigned char *data;
-   unsigned int width, height;
+   png_uint_32 width, height;
GLuint tex;

glGenTextures(1, &tex);
--- antigrav-0.0.2/src/m3dtexture.h 2006-08-04 15:38:31.0 -0400
+++ antigrav-0.0.2/src/m3dtexture.h.new 2006-12-01 23:14:15.0 -0500
@@ -9,7 +9,7 @@
 {
std::string filename;
GLuint handle;
-   unsigned int width, height;
+   png_uint_32 width, height;
 };
 
 /// A texture
@@ -34,8 +34,8 @@

m3dTexture &operator=(const m3dTexture &t);
 
-   static int loadPNG(const char *filename, unsigned char **data, unsigned 
int *width, unsigned int *height);
-   static int savePNG(const char *filename, const unsigned char *data, 
unsigned int width, unsigned int height);
+   static int loadPNG(const char *filename, unsigned char **data, 
png_uint_32 *width, png_uint_32 *height);
+   static int savePNG(const char *filename, const unsigned char *data, 
png_uint_32 width, png_uint_32 height);
static int screenshot(const char *filename);

static GLuint loadTexture(const char *filename);
@@ -48,8 +48,8 @@
static void pngWriteCallbackSTDIO(png_structp pngPtr, png_bytep data, 
png_size_t length);
static void pngFlushCallbackSTDIO(png_structp pngPtr);

-   static int loadPNG(unsigned char **data, unsigned int *width, unsigned 
int *height, void *handle, void (*pngReadCallback)(png_structp ctx, png_bytep 
area, png_size_t size));
-   static int savePNG(const unsigned char *data, unsigned int width, 
unsigned int height, void *handle, void (*pngWriteCallback)(png_structp pngPtr, 
png_bytep data, png_size_t length), void (*pngFlushCallback)(png_structp 
pngPtr));
+   static int loadPNG(unsigned char **data, png_uint_32 *width, 
png_uint_32 *height, void *handle,

Bug#401795: CVE-2006-6301: Remote external manipulation of /etc/hosts.deny

2006-12-09 Thread Pascal Volk

Tags: fixed-upstream

Should be fixed in version 2.6, available at
http://sourceforge.net/project/showfiles.php?group_id=131204

>From denyhosts changelog:

2.6 (Dec 7, 2006)
==

- security fix: malicious users can cause a DoS of ssh.
  for more info: http://nvd.nist.gov/nvd.cfm?cvename=CVE-2006-6301
...

Regards
Pascal


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

Bug#403119: #403119 openssh-(client|server) 4.3p2-7 fail to install

2006-12-14 Thread Pascal Giard


Shouldn't the "ssh" package be also upgraded?
The "ssh" package became a transitionnal package since then...

What happens if you "apt-get install ssh"?

-Pascal
--
Homepage (http://organact.mine.nu)
Debian GNU/Linux (http://www.debian.org)
École de technologie supérieure (http://www.etsmtl.ca)

Bug#403119: #403119 openssh-(client|server) 4.3p2-7 fail to install

2006-12-16 Thread Pascal Giard

Hmm... i doubt that the package maintainer will want to close this bug
as the upgrade path is clearly broken...and that's not good.

I leave it up to him.

-Pascal

On 12/16/06, Donatas Ciuksys <[EMAIL PROTECTED]> wrote:

Hi,

Well after some googling I solved my problem executing:

$ dpkg -i ssh_3.8.1p1-8.sarge.6_sparc.deb && dpkg -i
openssh-client_4.3p2-7_sparc.deb openssh-server_4.3p2-7_sparc.deb

After that:

$ aptitude dist-upgrade
The following packages are unused and will be REMOVED:
  libssl0.9.7 openssh-client openssh-server
...

Well I was left without ssh. Then I did:

$ aptitude install ssh

That did the trick, I'm having the latest ssh version now.

So my problem is solved, the bug can be closed now.

Regards,
Donatas

> -Original Message-
> From: Pascal Giard [mailto:[EMAIL PROTECTED]
> Sent: Thursday, December 14, 2006 10:32 PM
> To: [EMAIL PROTECTED]; Donatas Ciuksys
> Subject: #403119 openssh-(client|server) 4.3p2-7 fail to install
>
> Shouldn't the "ssh" package be also upgraded?
> The "ssh" package became a transitionnal package since then...
>
> What happens if you "apt-get install ssh"?
>
> -Pascal
> --
> Homepage (http://organact.mine.nu)
> Debian GNU/Linux (http://www.debian.org)
> École de technologie supérieure (http://www.etsmtl.ca)
>
>
>

--
Homepage (http://organact.mine.nu)
Debian GNU/Linux (http://www.debian.org)
École de technologie supérieure (http://www.etsmtl.ca)

Bug#393606: mail-notification-evolution broke again

2006-12-29 Thread Pascal Giard


On 12/27/06, Sam Morris <[EMAIL PROTECTED]> wrote:

found 393606 4.0~rc2.dfsg.1-5
thanks

After upgrading to 3.0.dfsg.1-10, mail-notification-evolution was again
unable to contact Evolution (2.8). I just upgraded to the version in
experimental and still can't get it to work.


Unfortunatly, i can't test this in a chroot as Evolution 2.8 will
refuse to start¹ and bonobo-slay doesn't solve this.

Øystein, can you test this please?

-Pascal
¹ i get the following error:

Evolution can not start.
Your system configuration does not match your Evolution configuration.
--
Homepage (http://organact.mine.nu)
Debian GNU/Linux (http://www.debian.org)
École de technologie supérieure (http://www.etsmtl.ca)

Bug#393606: mail-notification: Now detecting evolution-dev version

2006-11-11 Thread Pascal Giard


Hi Øystein,
 the latest version in unstable (3.0.dfsg.1-8) detects evolution-dev's version.

Would you mind making a binNMU for experimental?

thanks,

-Pascal
--
Homepage (http://organact.mine.nu)
Debian GNU/Linux (http://www.debian.org)
École de technologie supérieure (http://www.etsmtl.ca)

Bug#400051: antigravitaattori: Segfault attempting to start; fail to load texture

2006-11-23 Thread Pascal Giard


Package: antigravitaattori
Version: 0.0.2-2
Severity: grave
Justification: renders package unusable

Attempting to start the game, i get:

[EMAIL PROTECTED]:~$ antigrav
libpng error: Invalid image width
setjmp: Success
Invalid: can't load texture racer.png
libpng error: Invalid image width
setjmp: Success
Can't load texture road.png
Erreur de segmentation

"Erreur de segmentation" translates to "Segmentation fault".

-Pascal

-- System Information:
Debian Release: 4.0
 APT prefers unstable
 APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-2-amd64
Locale: LANG=fr_CA, LC_CTYPE=fr_CA (charmap=ISO-8859-1)

Versions of packages antigravitaattori depends on:
ii  libalut0 1.0.1-1 OpenAL Utility Toolkit
ii  libc62.3.6.ds1-8 GNU C Library: Shared libraries
ii  libgcc1  1:4.1.1-20  GCC support library
ii  libgl1-mesa-glx [libgl1] 6.5.1-0.4   A free implementation of the OpenG
ii  libglu1-mesa [libglu1]   6.5.1-0.4   The OpenGL utility library (GLU)
ii  libopenal0a  1:0.0.8-1   OpenAL is a portable library for 3
ii  libpng12-0   1.2.13-4PNG library - runtime
ii  libsdl1.2debian  1.2.11-7Simple DirectMedia Layer
ii  libstdc++6   4.1.1-20The GNU Standard C++ Library v3

antigravitaattori recommends no packages.

-- no debconf information
--
Homepage (http://organact.mine.nu)
Debian GNU/Linux (http://www.debian.org)
École de technologie supérieure (http://www.etsmtl.ca)

Bug#383555: udev broken for initrd kernels

2006-08-18 Thread Pascal LACROIX

Same for me, also xorg-xserver refused starting, reverting to testing
version and works again.

B.Rgds


-- 
God is dead.'  -Nietzsche|'Nietzsche is dead.'  -God  
88' _`88'_  `8   | Pascal LACROIX

 http://kikoucalou.chez-alice.fr

La vie est pleine d'une infinité d'absurdités, qui, impudemment, n'ont
même pas besoin de paraître vraisemblables; car elles sont vraies.

Bug#384361: xserver-xorg-video-ati: Driver reporting ABI version number mismatch - xserver fails to start

2006-08-23 Thread Pascal LACROIX

Like Eric, when upgrading experimental, trouble appear fixed for me.

-- 
God is dead.'  -Nietzsche|'Nietzsche is dead.'  -God  
88' _`88'_  `8   | Pascal LACROIX

 http://kikoucalou.chez-alice.fr

La vie est pleine d'une infinité d'absurdités, qui, impudemment, n'ont
même pas besoin de paraître vraisemblables; car elles sont vraies.

Bug#386500: Problem located

2006-09-08 Thread Pascal LACROIX

For me, this bug was breaking a lot : resolvconf, exim4 ...

-- 
Pascal LACROIX




signature.asc
Description: PGP signature

Bug#388451: mail-notification: does not start, looks for liblinc.so.1

2006-09-20 Thread Pascal Giard


tags 388451 unreproducible moreinfo
thx!
--

Hi Claudio,
 i'm quite surprised by your bugreport.

Executing "ldd /usr/bin/mail-notification" shows no dynamic linking
against that librairy neither on i386 nor amd64.
Can you try this on your side?

-Pascal
PS: obviously, i'm unable to reproduce your problem neither on amd64
nor my i386 chroot.

On 9/20/06, Claudio Belotti <[EMAIL PROTECTED]> wrote:

Package: mail-notification
Version: 3.0.dfsg.1-7
Severity: grave
Justification: renders package unusable

launching 'mail-notification' from a terminal gives the following error:
mail-notification: error while loading shared libraries: liblinc.so.1:
cannot open shared object file: No such file or directory

launching 'Configure Mail Notification' from the menu
Desktop > Preferences
does not open any window

and I cannot find any package in debian testing/unstable with liblinc

[...]

--
Homepage (http://organact.mine.nu)
Debian GNU/Linux (http://www.debian.org)


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

Bug#388451: mail-notification: does not start, looks for liblinc.so.1

2006-09-20 Thread Pascal Giard


Hi again Claudio,
 i see there's no reference to the library you mentionned: liblinc.

Could you run strace on mail-notification and see me over the result
as an attached file please?

thanks,

-Pascal

On 9/20/06, Claudio Belotti <[EMAIL PROTECTED]> wrote:

on 20/09/2006 17:12 Pascal Giard wrote:
>   i'm quite surprised by your bugreport.
> Executing "ldd /usr/bin/mail-notification" shows no dynamic linking
> against that librairy neither on i386 nor amd64.
> Can you try this on your side?
Hi Pascal this is what I get

ldd /usr/bin/mail-notification:

linux-gate.so.1 =>  (0xe000)
libeel-2.so.2 => /usr/lib/libeel-2.so.2 (0xa7eb5000)
libgnomeui-2.so.0 => /usr/lib/libgnomeui-2.so.0 (0xa7e2c000)
libtasn1.so.3 => /usr/lib/libtasn1.so.3 (0xa7e18000)
libjpeg.so.62 => /usr/lib/libjpeg.so.62 (0xa7df8000)
libgailutil.so.17 => /usr/lib/libgailutil.so.17 (0xa7df1000)
libglade-2.0.so.0 => /usr/lib/libglade-2.0.so.0 (0xa7dd9000)
libbonoboui-2.so.0 => /usr/lib/libbonoboui-2.so.0 (0xa7d7c000)
libgnome-keyring.so.0 => /usr/lib/libgnome-keyring.so.0 (0xa7d71000)
libgnome-2.so.0 => /usr/lib/libgnome-2.so.0 (0xa7d5c000)
libesd.so.0 => /usr/lib/libesd.so.0 (0xa7d53000)
libaudiofile.so.0 => /usr/lib/libaudiofile.so.0 (0xa7d2f000)
libgnomevfs-2.so.0 => /usr/lib/libgnomevfs-2.so.0 (0xa7cd)
libgnutls.so.13 => /usr/lib/libgnutls.so.13 (0xa7c62000)
libgcrypt.so.11 => /usr/lib/libgcrypt.so.11 (0xa7c11000)
libgpg-error.so.0 => /usr/lib/libgpg-error.so.0 (0xa7c0c000)
libavahi-glib.so.1 => /usr/lib/libavahi-glib.so.1 (0xa7c09000)
libavahi-client.so.3 => /usr/lib/libavahi-client.so.3 (0xa7bfa000)
libdbus-1.so.2 => /usr/lib/libdbus-1.so.2 (0xa7bcb000)
libavahi-common.so.3 => /usr/lib/libavahi-common.so.3 (0xa7bc)
libutil.so.1 => /lib/tls/i686/cmov/libutil.so.1 (0xa7bbc000)
libbonobo-2.so.0 => /usr/lib/libbonobo-2.so.0 (0xa7b61000)
libgconf-2.so.4 => /usr/lib/libgconf-2.so.4 (0xa7b3)
libgnomecanvas-2.so.0 => /usr/lib/libgnomecanvas-2.so.0 (0xa7b05000)
libart_lgpl_2.so.2 => /usr/lib/libart_lgpl_2.so.2 (0xa7aef000)
libgtk-x11-2.0.so.0 => /usr/lib/libgtk-x11-2.0.so.0 (0xa7805000)
libgdk-x11-2.0.so.0 => /usr/lib/libgdk-x11-2.0.so.0 (0xa7784000)
libatk-1.0.so.0 => /usr/lib/libatk-1.0.so.0 (0xa7769000)
libgdk_pixbuf-2.0.so.0 => /usr/lib/libgdk_pixbuf-2.0.so.0 (0xa7753000)
libpangocairo-1.0.so.0 => /usr/lib/libpangocairo-1.0.so.0 (0xa774b000)
libSM.so.6 => /usr/lib/libSM.so.6 (0xa7742000)
libICE.so.6 => /usr/lib/libICE.so.6 (0xa772a000)
libpangoft2-1.0.so.0 => /usr/lib/libpangoft2-1.0.so.0 (0xa7705000)
libXext.so.6 => /usr/lib/libXext.so.6 (0xa76f6000)
libXinerama.so.1 => /usr/lib/libXinerama.so.1 (0xa76f3000)
libXi.so.6 => /usr/lib/libXi.so.6 (0xa76eb000)
libXrandr.so.2 => /usr/lib/libXrandr.so.2 (0xa76e7000)
libXcursor.so.1 => /usr/lib/libXcursor.so.1 (0xa76de000)
libXfixes.so.3 => /usr/lib/libXfixes.so.3 (0xa76d9000)
libpango-1.0.so.0 => /usr/lib/libpango-1.0.so.0 (0xa769f000)
libcairo.so.2 => /usr/lib/libcairo.so.2 (0xa763d000)
libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0xa75d3000)
libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0xa75a3000)
libpng12.so.0 => /usr/lib/libpng12.so.0 (0xa757f000)
libXrender.so.1 => /usr/lib/libXrender.so.1 (0xa7577000)
libX11.so.6 => /usr/lib/libX11.so.6 (0xa74b)
libbonobo-activation.so.4 => /usr/lib/libbonobo-activation.so.4
(0xa749c000)
libORBitCosNaming-2.so.0 => /usr/lib/libORBitCosNaming-2.so.0 
(0xa7498000)
libORBit-2.so.0 => /usr/lib/libORBit-2.so.0 (0xa7447000)
libpopt.so.0 => /lib/libpopt.so.0 (0xa743f000)
libm.so.6 => /lib/tls/i686/cmov/libm.so.6 (0xa741a000)
libxml2.so.2 => /usr/lib/libxml2.so.2 (0xa730)
libgmime-2.0.so.2 => /usr/lib/libgmime-2.0.so.2 (0xa72b2000)
libgmodule-2.0.so.0 => /usr/lib/libgmodule-2.0.so.0 (0xa72af000)
libgthread-2.0.so.0 => /usr/lib/libgthread-2.0.so.0 (0xa72ab000)
libpthread.so.0 => /lib/tls/i686/cmov/libpthread.so.0 (0xa7299000)
libz.so.1 => /usr/lib/libz.so.1 (0xa7285000)
libnsl.so.1 => /lib/tls/i686/cmov/libnsl.so.1 (0xa726e000)
libgobject-2.0.so.0 => /usr/lib/libgobject-2.0.so.0 (0xa7234000)
libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0xa71a2000)
libsasl2.so.2 => /usr/lib/libsasl2.so.2 (0xa718d000)
libdl.so.2 => /lib/tls/i686/cmov/libdl.so.2 (0xa7189000)
libresolv.so.2 => /lib/tls/i686/cmov/libresolv.so.2

Bug#403247: no automatic refresh also with thunar_0.8.0-1

2007-03-25 Thread Pascal Dormeau


> The good news is that the symptoms I described previously for #403247
> have disappeared with thunar_0.8.0-1 and gamin_0.1.8-1. But the Debian

Sorry, I reported too quickly, I finally encountered problems today with 
gamin_0.1.8-1 and thunar_0.8.0-1 not auto refreshing.


Please note that upgrading to a thunar version built against libfam-dev 
may then not be a reliable solution (as I half suggested in a previous 
message).


Unfortunately, I don't know how to reproduce it. It is strange because I 
have been using it for 10 days without noticing any problem.


Best regards,

Pascal D.



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

Bug#416201: Fail installing php-sqlite3 while apache2 is installed

2007-03-25 Thread Pascal Bernard

Package: php-sqlite3
Version: 0.4-4
Severity: serious
Justification: Policy 3.5

Paramétrage de php-sqlite3 (0.4-4) ...
/usr/sbin/apachectl is not executable, exiting... failed!
invoke-rc.d: initscript apache, action "restart" failed.
dpkg : erreur de traitement de php-sqlite3 (--configure) :

# apt-file search usr/sbin/apachectl
apache: usr/sbin/apachectl

Should php-sqlite3 pre-depend on apache or preinst be updated for apache2 ?

-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.19
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)

Versions of packages php-sqlite3 depends on:
ii  php-db1.7.6-2PHP PEAR Database Abstraction Laye

php-sqlite3 recommends no packages.

-- no debconf information

Bug#403247: no automatic refresh also with thunar_0.8.0-1

2007-03-28 Thread Pascal Dormeau


Michael Banck a écrit :

How exactly are you reproducing this?  Do you have a directory open in
thunar and try "touch foo", "touch bar", "rm foo", "rm bar" etc.?


Yes, $HOME/tmp is opened in Thunar and from xfce4-terminal I run 'touch 
tmp/test0', 'rm tm/test0'.


This is the method I use to check if thunar self-refreshes (or not).



If you do that, does thunar get notified after the second or third
operation at least? 


No, never, the only way to get thunar "notified" is to perform a manual 
refresh (click on refresh button or hit ctrl r). Just like gam_server 
had died (but it seems to have not, according to 'ps').


I could reproduce it again tonight. This how I "triggered" it:

I have the following line in my /etc/fstab:

/dev/hda15 /mnt/archives ext3 noauto,user 0 0

First I mount /mnt/archives (using mount in xfce4-terminal),

then I navigate inside /mnt/archives using thunar.

Starting from that moment, thunar does not self-refresh anymore 
(whatever the directory opened in thunar).


I repeated the operation several times (leaving the Xfce4-session and 
re-entering into between). Each time, I triggered the problem once 
entering into /mnt/archives with thunar. This does not happen with 
gamin_0.1.7-4 (only with gamin_0.1.8-1).


I don't know if that helps.

Best regards.

Pascal D.

Bug#403247: no automatic refresh also with thunar_0.8.0-1

2007-03-29 Thread Pascal Dormeau


Michael Banck a écrit :

Hi,

can you guys maybe try the following gamin_0.1.8-2 package, and see
whether it fixes your problems?

http://people.debian.org/~mbanck/unstable/gamin_0.1.8-2_i386.deb
http://people.debian.org/~mbanck/unstable/libgamin0_0.1.8-2_i386.deb



Hello again Michael,

I tested gamin_0.1.8-2 (I took care to kill everything: stopping 
xfce4-session, killing gam_server to be sure not to use the 0.1.8-1 
version, restarting xfce4-session). But unfortunately the problem is 
still there.


I also noticed:

- if /mnt/archives (/etc/fstab: /dev/hda15 /mnt/archives ext3 
noauto,user 0 0 ) is mounted before thunar and gam_server are started, 
and if I navigate with thunar inside, thunar is no more notified by 
gam_server (the problem is not triggered by the fact the file system is 
mounted, but rather more by the fact thunar is used to navigate inside),


I extended the test to other file systems/media:

- if I mount a usb stick and if I navigate with thunar inside, thunar is 
no more notified by gam_server,


- if I mount a CDROM and navigate with thunar inside, thunar is still 
notified by gam_server (test repeated twice only).


Could it have something to do with the user 's ownership on the 
concerned file systems?


It seems (as far as I can see) that it only occurs when the user has 
write permission on given file system and thunar is used to navigate inside.


No more clue here.

Best regards.

Pascal D.

Bug#403247: no automatic refresh also with thunar_0.8.0-1

2007-03-29 Thread Pascal Dormeau


Michael Banck a écrit :


Can you try to add (or create) either "poll /mnt/archives" or "notify
/mnt/archives" to your ~/.gaminrc and see if any of those help?


I tested both, but none of them helps.

Other interesting thing (maybe not relevant):

- I navigate inside the "faulty" directory (I know it will make thunar 
not being notified by gam_server anymore),


- I open ~/tmp with thunar,

- I check if gam_server is still running: OK

- in xfce4-terminal I run 'touch tmp/test0', thunar is not notified 
(that 's the "bug"),


- I check if gam_server is still running:OK

- I make a manual refresh,

- I check if gam_server is still running: gam_server has been killed.

Note that it may be the expected behavior: maybe thunar kills gam_server 
on purpose since it knows gam_server is no more useful.


Best regards.

Pascal D.

Bug#403247: no automatic refresh also with thunar_0.8.0-1

2007-03-30 Thread Pascal Dormeau


Michael Banck a écrit :

So,

Maximiliano Curia found an upstream patch which fixes things for him.
Could you all please install and test gamin_0.1.8-2 from 


deb http://people.debian.org/~mbanck/unstable/ ./

or

http://people.debian.org/~mbanck/unstable/gamin_0.1.8-2_i386.deb
http://people.debian.org/~mbanck/unstable/libgamin0_0.1.8-2_i386.deb

again? Sorry about the same package name, just use --reinstall for
apt-get or so.

Does this fix thunar and/or pcmanfm for you.


Hi Michael,

Fixed for me also.

Tested with:

thunar_0.4.0rc1-3 + libthunar-vfs-1-2_0.4.0rc1-3 (testing)
thunar_0.5.0rc2-1 + libthunar-vfs-1-2_0.5.0rc2-1 (unstable)
thunar_0.8.0-1 + libthunar-vfs-1-2_0.8.0-1 (experimental)
pcmanfm_0.3.2.2-1 (testing/unstable)

So far, I could not trigger the "bug", and I did not meet any problem.

Note that I did not tested very extensively because I checked the three 
thunar versions this evening (I originally reported the bug against the 
thunar version in testing) and each time I had to make sure that the new 
thunar version was correctly taken into account, that the gam_server was 
correctly started by the corresponding version, that there were not 
other environment side effect (in practice, I killed the gam_server and 
restarted the xfce4-session). I probably did not do it so carefully when 
I too early announced that the problem was solved with thunar_0.8.0-1 
two weeks ago.


I do not have the skills to understand Maximiliano explanations about 
why the patch fixes the bug, but I trust him because it works now.


Thank you, Michael and Maximiliano.

Pascal D.

Bug#540497: sox: diff for NMU version 14.3.0-1.1

2009-10-08 Thread Pascal Giard

Thanks for the NMU Stefano.

-Pascal

On Sun, Oct 4, 2009 at 9:10 AM, Stefano Zacchiroli  wrote:
> tags 540497 + patch pending
> thanks
>
> Dear maintainer,
>
> I've prepared an NMU for sox (versioned as 14.3.0-1.1) and uploaded it
> to DELAYED/2, according to devref §5.11.1. The patch simply adds a
> missing Replaces from libsox-fmt-base to libsox-fmt-sndfile.
>
> A few more comments:
>
> - the fact that a user declared that the bug was not reproducible in his
>  specific upgrade is not very meaningful. I've tried an upgrade from
>  Lenny to Sid and while with the current apt-get sorting algorithm it
>  can work properly (libsox-fmt-sndfile got removed before than
>  libsox-fmt-base got unpacked), I was able to trigger the overwrite
>  errors with dpkg alone
>
> - the NMUed version of the package works properly even in that corner
>  case
>
> Cheers.
>
> --
> Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ Univ. Paris 7
> z...@{upsilon.cc,pps.jussieu.fr,debian.org} -<>- http://upsilon.cc/zack/
> Dietro un grande uomo c'è ..|  .  |. Et ne m'en veux pas si je te tutoie
> sempre uno zaino ...| ..: | Je dis tu à tous ceux que j'aime
>



-- 
Homepage (http://organact.mine.nu)
Debian GNU/Linux (http://www.debian.org)
LACIME: École de technologie supérieure (http://lacime.etsmtl.ca)



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

Bug#546695: dovecot-imapd: dovecot epoll fails with -EPERM for "dovecot --exec-mail imap" at the shell

2009-09-23 Thread Pascal Volk

tags: + patch

hi,

please find attached a dpatch (obtained from Dovecot's hg repo) to
resolve this issue.


Regards,
Pascal
-- 
Ubuntu is an ancient African word meaning “I can’t install Debian.”
 -- unknown
#! /bin/sh /usr/share/dpatch/dpatch-run
##
## DP: Author: Timo Sirainen
## DP: Fix #546695

# Patch obtained from http://hg.dovecot.org/dovecot-1.2/rev/0f04c7da33f1

@DPATCH@
diff -urNad dovecot-1.2.5~/src/master/main.c dovecot-1.2.5/src/master/main.c
--- dovecot-1.2.5~/src/master/main.c2009-09-11 18:25:25.0 +0200
+++ dovecot-1.2.5/src/master/main.c 2009-09-24 02:09:03.0 +0200
@@ -614,8 +614,6 @@
sizeof(ssl_manual_key_password));
} T_END;
 
-   open_std_fds();
-
/* save TZ environment. AIX depends on it to get the timezone
   correctly. */
env_tz = getenv("TZ");
@@ -636,6 +634,9 @@
mail_process_exec(exec_protocol, exec_args);
}
 
+   /* closes stdin/stdout, must be after --exec-mail handling */
+   open_std_fds();
+
/* log all errors to both stderr and log file until we've finished
   startup. */
set_tee_logfile(settings_root->defaults);

Bug#564240: nvidia-graphics-drivers-legacy-96xx: Unable to start X.org -- X.org crashes

2010-01-08 Thread Pascal Giard

Package: nvidia-kernel-legacy-96xx-source
Version: 96.43.14-2
Justification: renders package unusable
Severity: grave

The current version of this driver crashes the latest version of X.org.

/var/log/Xorg.0.log shows:
[...]
(II) LoadModule: "glx"
(II) Loading /usr/lib/xorg/modules/extensions//libglx.so
(II) Module glx: vendor="NVIDIA Corporation"
compiled for 4.0.2, module version = 1.0.0
Module class: X.Org Server Extension
(II) NVIDIA GLX Module  96.43.14  Sun Nov  8 18:24:17 PST 2009
(II) Loading extension GLX
[...]
(II) NVIDIA(0): Initialized GART.

Backtrace:
0: /usr/bin/X(xorg_backtrace+0x3b) [0x81314cb]
1: /usr/bin/X(xf86SigHandler+0x51) [0x80c1df1]
2: [0xb7f89400]

Fatal server error:
Caught signal 11.  Server aborting
[...]

I currently have to use nv in order to have X. Having a dual display
setup, I'm loosing a monitor...


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

Kernel: Linux 2.6.31-1-686 (SMP w/2 CPU cores)
Locale: LANG=fr_CA, LC_CTYPE=fr_CA (charmap=ISO-8859-1) (ignored:
LC_ALL set to fr_CA)
Shell: /bin/sh linked to /bin/bash

Versions of packages nvidia-kernel-legacy-96xx-source depends on:
ii  debhelper 7.4.10 helper programs for debian/rules
ii  dpatch2.0.31 patch maintenance system for Debia
ii  make  3.81-7 An utility for Directing compilati
ii  sed   4.2.1-6The GNU sed stream editor

Versions of packages nvidia-kernel-legacy-96xx-source recommends:
ii  devscripts2.10.59scripts to make the life of a Debi
ii  kernel-package12.031 A utility for building Linux kerne
ii  nvidia-glx-legacy-96xx96.43.14-2 NVIDIA binary Xorg driver (96xx le

nvidia-kernel-legacy-96xx-source suggests no packages.

-- no debconf information

-Pascal
-- 
Homepage (http://organact.mine.nu)
Debian GNU/Linux (http://www.debian.org)
LACIME: École de technologie supérieure (http://lacime.etsmtl.ca)


Xorg.0.log
Description: Binary data

Bug#585524: Proposed workaround

2010-06-28 Thread Pascal Giard

Prosposed workaround in #585524 also fixed my issue with all printers
(HP Laserjet).

Thanks,

-Pascal
-- 
Homepage (http://organact.mine.nu)
Debian GNU/Linux (http://www.debian.org)
COMunité/LACIME: École de technologie supérieure (http://www.comunite.ca)



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

Bug#539224: Severity changed to serious

2010-04-20 Thread Pascal Giard

On Tue, Apr 20, 2010 at 4:07 PM, Christian Marillat  wrote:
> severity 539224 serious
> thanks
>
> Hi,
>
> As you know kfreebsd-i386 is an arch for the squeeze release. This
> package doesn't install on kfreebsd so severity changed to serious.

I shall take care of this very soon.
A new stable release just came out to.

-Pascal
-- 
Homepage (http://organact.mine.nu)
Debian GNU/Linux (http://www.debian.org)
LACIME: École de technologie supérieure (http://lacime.etsmtl.ca)



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

Bug#616011: libreoffice-wiki-publisher: Export filter cannot be found

2011-03-01 Thread Pascal Giard

Package: libreoffice-wiki-publisher
Version: 1.1.1+LibO3.3.1-1
Justification: renders package unusable
Severity: grave

Trying to export a document to a MediaWiki server results in an error:
The MediaWiki export filter cannot be found. Choose 'Tools-XML Filter Settings'
to install the filter, or use the setup to install the component.

Looking into Tools/Tools-XML Filter reveals that, indeed, there is no MediaWiki
export filter to be found.

Cheers,

-Pascal

-- Package-specific info:

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

Kernel: Linux 2.6.37-1-686 (SMP w/1 CPU core)
Locale: LANG=fr_CA, LC_CTYPE=fr_CA (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash

Versions of packages libreoffice-wiki-publisher depends on:
ii  default-jre [java5-runtime] 1:1.6-40 Standard Java or Java compatible R
ii  gcj-4.4-jre [java5-runtime] 4.4.5-9  Java runtime environment using GIJ
ii  gcj-jre [java5-runtime] 4:4.4.5-2Java runtime environment using GIJ
ii  libcommons-codec-java   1.4-2encoder and decoders such as Base6
ii  libcommons-httpclient-java  3.1-9A Java(TM) library for creating HT
ii  libcommons-lang-java2.4-4Extension of the java.lang package
ii  libcommons-logging-java 1.1.1-8  commmon wrapper interface for seve
ii  libreoffice-core1:3.3.1-1office productivity suite -- arch-
ii  openjdk-6-jre [java5-runtim 6b18-1.8.5-1 OpenJDK Java runtime, using Hotspo
ii  sun-java6-jre [java5-runtim 6.24-1   Sun Java(TM) Runtime Environment (

Versions of packages libreoffice-wiki-publisher recommends:
ii  liblucene2-java  2.9.3+ds1-1 Full-text search engine library fo

Versions of packages libreoffice-wiki-publisher suggests:
pn  mediawiki  (no description available)

-- no debconf information

-- 
Homepage (http://organact.mine.nu)
Debian GNU/Linux (http://www.debian.org)
COMunité/LACIME: École de technologie supérieure (http://www.comunite.ca)
Integrated Microsystems Laboratory: McGill (http://www.iml.ece.mcgill.ca)



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

Bug#616011: libreoffice-wiki-publisher: Export filter cannot be found

2011-03-01 Thread Pascal Giard

On Tue, Mar 1, 2011 at 9:08 PM, Rene Engelhard  wrote:
> tag 616011 + moreinfo
> thanks
>
> Hi,
>
> On Tue, Mar 01, 2011 at 07:58:49PM +, Pascal Giard wrote:
>> Trying to export a document to a MediaWiki server results in an error:
>> The MediaWiki export filter cannot be found. Choose 'Tools-XML Filter 
>> Settings'
>> to install the filter, or use the setup to install the component.
>>
>> Looking into Tools/Tools-XML Filter reveals that, indeed, there is no 
>> MediaWiki
>> export filter to be found.
>
> That's new to me, then again I don't have a mediawiki I can publish to
> anyways.
>
> OK, I can imagine two (or maybe both are the cause together) causes of this.
> I guess that there's just a dependency missing.
> 1. libreoffice-java-common (anyone needing Java stuff in OOo needs this 
> anyway)
> 2. libreoffce-filter-mobiledev (Mobile Devices Filters, shouldn't influence
>   Wiki PUblisher, more or it's optional anyway)
>
> I bet you don't have libreoffice-java-common installed. (Which would make
> this bug not "grave" but "serious" anymore for the missing dependency)

Hello Rene,
 thanks for the quick reply!

Unfortunately, both are installed...

FWIW, libreoffice-filter-binfilter is also installed.

Also note that for raising that error, you don't need to connect to
any mediawiki server.
Simply selecting "Send/To MediaWiki..." will raise the error.

And while the filter is indeed not shown in "Tools/XML Filter
Settings", the extension is correctly shown in the Extension Manager.
So it seems it's partially integrated...

On a final note, this does sound as grave to me as I have the
dependencies you mentioned and I'm unable to use this package...
In any case, my objective is to get this to work, not to get into an
argument ;-)

Any other idea is welcome...

Regards,

-Pascal
-- 
Homepage (http://organact.mine.nu)
Debian GNU/Linux (http://www.debian.org)
COMunité/LACIME: École de technologie supérieure (http://www.comunite.ca)
Integrated Microsystems Laboratory: McGill (http://www.iml.ece.mcgill.ca)

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

Bug#616011: libreoffice-wiki-publisher: Export filter cannot be found

2011-03-01 Thread Pascal Giard

On Tue, Mar 1, 2011 at 11:16 PM, Rene Engelhard  wrote:
> tag 616011 + unreproducible
> thanks
>
> Hi,
>
> On Tue, Mar 01, 2011 at 09:25:58PM +, Pascal Giard wrote:
>> Also note that for raising that error, you don't need to connect to
>> any mediawiki server.
>> Simply selecting "Send/To MediaWiki..." will raise the error.
>
> Mmh, OK.
>
> Then it's unreproducible here. When I create a new doc and do
> "Send/To MediaWiki..." I get a dialog box.

It's also unreproducible on my laptop. Hmmm...

> Uptodaate sid? Version mismatch?

Up to date: yes, as of today.
Version mismatch... I highly doubt it, I no longer have any
experimental package installed on that box.

> And:
>
>> ii  openjdk-6-jre [java5-runtim 6b18-1.8.5-1 OpenJDK Java runtime, using 
>> Hotspo
>> ii  sun-java6-jre [java5-runtim 6.24-1       Sun Java(TM) Runtime 
>> Environment (
>
> Just out of curiosity: what of those is set in the options? There already have
> been reports of brokeness with 23 (in an other area) and 24..
>
> I "of course" tried with OpenJDK

I've tried both. I use update-alternatives to switch between the two.

Now I wonder where something fails on my desktop at work.
It must be something minor.

Although my issue is not fixed on my desktop at work, I'd be very
grateful if you could help tracking down the issue.

As the filter is not in the list, the first thing that comes to my
mind is: how does the XML filter get updated?
As soon as I get back to work (on Thursday), I'll try the obvious i.e.
reinstall the package and make sure libreoffice is restarted.
(I doubt the latter is the issue as the command appeared in the menu
(Send/To MediaWiki...) and in the Extension Manager but since I don't
understand the mechanism involved...)

Thanks,

-Pascal
-- 
Homepage (http://organact.mine.nu)
Debian GNU/Linux (http://www.debian.org)
COMunité/LACIME: École de technologie supérieure (http://www.comunite.ca)
Integrated Microsystems Laboratory: McGill (http://www.iml.ece.mcgill.ca)

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

Bug#616011: libreoffice-wiki-publisher: Export filter cannot be found

2011-03-02 Thread Pascal Giard

On Wed, Mar 2, 2011 at 3:10 PM, Rene Engelhard  wrote:
> Hi,
>
> On Wed, Mar 02, 2011 at 02:04:17AM +0000, Pascal Giard wrote:
>> As soon as I get back to work (on Thursday), I'll try the obvious i.e.
>> reinstall the package and make sure libreoffice is restarted.
>> (I doubt the latter is the issue as the command appeared in the menu
>> (Send/To MediaWiki...) and in the Extension Manager but since I don't
>> understand the mechanism involved...)
>
> Please don't tell me you did intrusive changes like a complete LibO package
> upgrade while LibO was running? (Extension registration should be ok if
> done via unopkg, but I don't think it will work with the new "preregistered"
> way)

It's a possibility; I can not rule that out.
If I understand correctly, doing a reinstall on all installed
libreoffice packages should fix things?

Cheers,

-Pascal
-- 
Homepage (http://organact.mine.nu)
Debian GNU/Linux (http://www.debian.org)
COMunité/LACIME: École de technologie supérieure (http://www.comunite.ca)
Integrated Microsystems Laboratory: McGill (http://www.iml.ece.mcgill.ca)



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

Bug#616011: libreoffice-wiki-publisher: Export filter cannot be found

2011-03-03 Thread Pascal Giard

Hello René,

On Wed, Mar 2, 2011 at 3:48 PM, Rene Engelhard  wrote:
> Hi,
>
> On Wed, Mar 02, 2011 at 03:48:48PM +0000, Pascal Giard wrote:
>> It's a possibility; I can not rule that out.
>> If I understand correctly, doing a reinstall on all installed
>> libreoffice packages should fix things?
>
> I don't know. Worth a try, though.

Ok, I've tried different things w/o success, most notably:

1) Deleted ~/.libreoffice, ~/.openoffice.org2 ~/.oppenoffice.org

2) Removing everything related to libreoffice (I don't have any
openoffice.org package) and reinstalling the wanted features:
apt-get remove libreoffice*
apt-get install libreoffice-wiki-publisher libreoffice-writer

Interestingly, libreoffice-common-java and
libreoffice-filter-binfilter are correctly installed so while
libreoffice-wiki-publisher does not depend on it, something else
required does.
However, doing things this way, libreoffice-wiki-publisher got
installed before python-uno and thus I don't see it getting registered
(missing predepend there?).

3) Reinstalling libreoffice-wiki-publisher alone; gets registered.

Unfortunately, while the extension can be found in the manager (unopkg
gui), the filter still is not found. I don't get it...

How do filters get in there? Is it through unopkg?
When I say that it gets registered, I mean that I see the following
(some blank lines removed):

Synchronizing repository for shared extensions
 Synchronizing repository for bundled extensions

  Enabling: Wiki Publisher
   Enabling: help
   Enabling: WikiExtension.xcs
   Enabling: WikiEditor
   Enabling: mediawiki.jar
   Enabling: Addons.xcu
   Enabling: ProtocolHandler.xcu
   Enabling: WikiExtension.xcu
   Enabling: OptionsDialog.xcu
   Enabling: Filter.xcu
   Enabling: Types.xcu
   Enabling: Paths.xcu

unopkg done.

More ideas?

Regards,

-Pascal
-- 
Homepage (http://organact.mine.nu)
Debian GNU/Linux (http://www.debian.org)
COMunité/LACIME: École de technologie supérieure (http://www.comunite.ca)
Integrated Microsystems Laboratory: McGill (http://www.iml.ece.mcgill.ca)

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

Bug#616011: libreoffice-wiki-publisher: Export filter cannot be found

2011-03-03 Thread Pascal Giard

Hi René,

On Thu, Mar 3, 2011 at 3:57 PM, Rene Engelhard  wrote:
[...]
> On Thu, Mar 03, 2011 at 03:26:25PM +0000, Pascal Giard wrote:
[...]
>> More ideas?
>
> No. Except maybe a somewhat broken extension registry..

Hmmm... If you are talking about the registry in ~/.libreoffice, I've
deleted it completely before reinstalling libreoffice.
I've also tried with a different user, w/o success.

And after removal, /usr/lib/libreoffice no longer exist.
There isn't any /usr/lib/openoffice.org either.

I can't find anything else with locate (up to date DB)...
Are there other files hidden somewhere?

In any case, is the registery human readable?

Regards,

-Pascal
-- 
Homepage (http://organact.mine.nu)
Debian GNU/Linux (http://www.debian.org)
COMunité/LACIME: École de technologie supérieure (http://www.comunite.ca)
Integrated Microsystems Laboratory: McGill (http://www.iml.ece.mcgill.ca)

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

Bug#616011: libreoffice-wiki-publisher: Export filter cannot be found

2011-03-07 Thread Pascal Giard

Hi René,

On Mon, Mar 7, 2011 at 12:05 AM, Rene Engelhard  wrote:
> Hi,
>
> On Thu, Mar 03, 2011 at 04:41:45PM +0000, Pascal Giard wrote:
>> On Thu, Mar 3, 2011 at 3:57 PM, Rene Engelhard  wrote:
>> [...]
>> > On Thu, Mar 03, 2011 at 03:26:25PM +, Pascal Giard wrote:
>> [...]
>> >> More ideas?
>> >
>> > No. Except maybe a somewhat broken extension registry..
>>
>> Hmmm... If you are talking about the registry in ~/.libreoffice, I've
>> deleted it completely before reinstalling libreoffice.
>> I've also tried with a different user, w/o success.
>>
>> And after removal, /usr/lib/libreoffice no longer exist.
>> There isn't any /usr/lib/openoffice.org either.
>
> Not everything is in /usr. What I had in mind was:
>
> (sid)root@frodo:/usr/lib/libreoffice/share# ls -l
> insgesamt 24
> drwxr-xr-x  2 root root 4096  3. Mär 00:31 config
> drwxr-xr-x 14 root root 4096  3. Mär 00:31 extensions
> drwxr-xr-x  2 root root 4096 22. Jan 22:33 prereg
> drwxr-xr-x  2 root root 4096  3. Mär 00:31 registry
> drwxr-xr-x  2 root root 4096 22. Jan 22:33 uno_packages
> drwxr-xr-x  2 root root 4096  3. Mär 00:33 xdg
> (sid)root@frodo:/usr/lib/libreoffice/share# cd prereg/
> (sid)root@frodo:/usr/lib/libreoffice/share/prereg# ls
> bundled
> (sid)root@frodo:/usr/lib/libreoffice/share/prereg# ls -l
> insgesamt 0
> lrwxrwxrwx 1 root root 41 22. Jan 22:33 bundled -> 
> /var/lib/libreoffice/share/prereg/bundled
> (sid)root@frodo:/usr/lib/libreoffice/share/prereg# cd bundled
> (sid)root@frodo:/usr/lib/libreoffice/share/prereg/bundled# ls
> extensions.db  lastsynchronized  registry
>
> this. /var/lib/libreoffice/share/prereg/bundled contains the "pre-registerd"
> extensions (what unopkg sync does)
>
>> Are there other files hidden somewhere?
>
> All over the fs, actually. Not everything is in /usr/lib/libreoffice :-)

I expressed myself wrong.
I should have said: "are there files somewhere still hidden after a purge?"

>> In any case, is the registery human readable?
>
> Depends. If you mean the actual db? No. If you mean the registered files and
> their structure? Yes. (Run a tree in /var/lib/libreoffice/share/prereg/bundled
> and you'll see)

After a purge, /var/lib/libreoffice is not there.
Therefore, I would assume that it's not corrupted.

Reinstall it shows that this file contains the expected MediaWiki filter:
/var/lib/libreoffice/share/prereg/bundled/registry/com.sun.star.comp.deployment.configuration.PackageRegistryBackend/ng1sQ6_/Filter.xcu

And that file is listed in
/var/lib/libreoffice/share/prereg/bundled/registry/com.sun.star.comp.deployment.configuration.PackageRegistryBackend/backenddb.xml
However, it's still not shown in "Tools/XML Filter Settings...".

What can go wrong here?

Is there a sort of "verbose" or "debug" mode?
"soffice.bin -help" does not show any... :-(

-Pascal
-- 
Homepage (http://organact.mine.nu)
Debian GNU/Linux (http://www.debian.org)
COMunité/LACIME: École de technologie supérieure (http://www.comunite.ca)
Integrated Microsystems Laboratory: McGill (http://www.iml.ece.mcgill.ca)



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

Bug#612845: NVIDIA 96.43.19

2011-03-24 Thread Pascal Giard

Hi,
 to fix building under kernel 2.6.38, I've modified the
AUTOCONF_INCLUDED.patch to add:

---
+++ b/conftest.h2011-03-24 10:44:17.0 -0400
@@ -303,6 +303,13 @@
  #undef NV_LINUX_SEMAPHORE_H_PRESENT
 #endif

+/* Check for generated/autoconfig.h */
+#if LINUX_VERSION_CODE > KERNEL_VERSION(2,6,37)
+ #define NV_GENERATED_AUTOCONF_H_PRESENT
+#else
+ #undef NV_GENERATED_AUTOCONF_H_PRESENT
+#endif
+
 /* Check for linux/cred.h */
 #if LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,27)
  #define NV_LINUX_CRED_H_PRESENT
---

I've attached my modified file.

Cheers,

-Pascal
-- 
Homepage (http://organact.mine.nu)
Debian GNU/Linux (http://www.debian.org)
COMunité/LACIME: École de technologie supérieure (http://www.comunite.ca)
Integrated Microsystems Laboratory: McGill (http://www.iml.ece.mcgill.ca)
From: Andreas Beckmann 
Subject: Fix build of 173xx with 2.6.33 and newer kernels

Index: b/nv-linux.h
===
--- a/nv-linux.h	2010-06-10 15:24:01.824037317 +
+++ b/nv-linux.h	2010-06-10 15:24:25.120037815 +
@@ -15,11 +15,13 @@
 #include "nv.h"
 #include "conftest.h"
 
+#ifndef AUTOCONF_INCLUDED
 #if defined(NV_GENERATED_AUTOCONF_H_PRESENT)
 #include 
 #else
 #include 
 #endif
+#endif
 
 #ifndef LINUX_VERSION_CODE
 #include 
--- a/conftest.h	2011-02-15 07:33:11.0 -0500
+++ b/conftest.h	2011-03-24 10:44:17.0 -0400
@@ -303,6 +303,13 @@
  #undef NV_LINUX_SEMAPHORE_H_PRESENT
 #endif
 
+/* Check for generated/autoconfig.h */
+#if LINUX_VERSION_CODE > KERNEL_VERSION(2,6,37)
+ #define NV_GENERATED_AUTOCONF_H_PRESENT
+#else
+ #undef NV_GENERATED_AUTOCONF_H_PRESENT
+#endif
+
 /* Check for linux/cred.h */
 #if LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,27)
  #define NV_LINUX_CRED_H_PRESENT

Bug#616011: libreoffice-wiki-publisher: Export filter cannot be found

2011-03-24 Thread Pascal Giard

Hi René,
 FWIW, the issue is still present in 1:3.3.2-1 (only at work).

Cheers,

-Pascal
-- 
Homepage (http://organact.mine.nu)
Debian GNU/Linux (http://www.debian.org)
COMunité/LACIME: École de technologie supérieure (http://www.comunite.ca)
Integrated Microsystems Laboratory: McGill (http://www.iml.ece.mcgill.ca)



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

Bug#593648: Addendum

2011-01-19 Thread Pascal BERNARD

No problem when the system is on a standard partition, even if /home is
on an lvm/raid1.






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

Bug#611918: postgresql-client-8.4: psql segfaults … in libedit.so.2.11

2011-02-03 Thread Pascal Volk

Package: postgresql-client-8.4
Version: 8.4.5-0squeeze2
Severity: grave
Justification: causes non-serious data loss

Hi,

the psql binary segfaults from time to time. Mostly when hitting the arrow
up key. Find down below some (probably not that useful (#551880)) gdb
output. Please contact me, if you need more information from the core file.


Regards,
Pascal

-- GDB output:
user@localhost ~ $ gdb /usr/lib/postgresql/8.4/bin/psql 
core.psql.1296755217-30280 
GNU gdb (GDB) 7.0.1-debian
Copyright (C) 2009 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".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...

warning: The current binary is a PIE (Position Independent Executable), which
GDB does NOT currently support.  Most debugger features will fail if used
in this session.

Reading symbols from /usr/lib/postgresql/8.4/bin/psql...(no debugging symbols 
found)...done.
Core was generated by `/usr/lib/postgresql/8.4/bin/psql vmm06'.
Program terminated with signal 11, Segmentation fault.
#0  0x7f9767e99388 in ?? ()
(gdb) bt full
#0  0x7f9767e99388 in ?? ()
No symbol table info available.
#1  0x7f9767e9b9b0 in ?? ()
No symbol table info available.
#2  0x7fff30387730 in ?? ()
No symbol table info available.
#3  0x7f976a1ab360 in ?? ()
No symbol table info available.
#4  0x7f970018 in ?? ()
No symbol table info available.
#5  0x7fff303877a0 in ?? ()
No symbol table info available.
#6  0x7fff30387730 in ?? ()
No symbol table info available.
#7  0x7f976874e001 in ?? ()
No symbol table info available.
#8  0x0013 in ?? ()
No symbol table info available.
#9  0x in ?? ()
No symbol table info available.
(gdb) quit 
user@localhost ~ $

-- System Information:
Debian Release: 6.0
  APT prefers testing
  APT policy: (500, 'testing'), (50, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages postgresql-client-8.4 depends on:
ii  libc6   2.11.2-10Embedded GNU C Library: Shared lib
ii  libedit22.11-20080614-2  BSD editline and history libraries
ii  libpq5  8.4.5-0squeeze2  PostgreSQL C client library
ii  libssl0.9.8 0.9.8o-4 SSL shared libraries
ii  postgresql-client-commo 113  manager for multiple PostgreSQL cl
ii  zlib1g  1:1.2.3.4.dfsg-3 compression library - runtime

postgresql-client-8.4 recommends no packages.

Versions of packages postgresql-client-8.4 suggests:
ii  postgresql-8.4   8.4.5-0squeeze2 object-relational SQL database, ve
pn  postgresql-doc-8.4 (no description available)

-- no debconf information



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

Bug#611918: postgresql-client-8.4: psql segfaults … in libedit.so.2.11

2011-02-04 Thread Pascal Volk

On 02/04/2011 11:29 PM Petter Reinholdtsen wrote:
> Can you try to reproduce it while running psql using valgrind, to get
> more information about the segfault?
> 
> Happy hacking,


Hi,

here's the Valgrind output, generated right after the segmentation
fault. Please let me know if I should pass any options to Valgrind.


Regards,
Pascal

-- Valgrind output:
==31630== Warning: ignored attempt to set SIGSTOP handler in sigaction();
==31630==  the SIGSTOP signal is uncatchable
vmm06=# ==31630== Invalid write of size 1
==31630==at 0x52AE388: ??? (in /usr/lib/libedit.so.2.11)
==31630==by 0x52B09AF: ??? (in /usr/lib/libedit.so.2.11)
==31630==by 0x52B6EDD: el_gets (in /usr/lib/libedit.so.2.11)
==31630==by 0x52C06E6: readline (in /usr/lib/libedit.so.2.11)
==31630==by 0x11C916: ??? (in /usr/lib/postgresql/8.4/bin/psql)
==31630==by 0x11F9BF: ??? (in /usr/lib/postgresql/8.4/bin/psql)
==31630==by 0x122943: main (in /usr/lib/postgresql/8.4/bin/psql)
==31630==  Address 0x0 is not stack'd, malloc'd or (recently) free'd
==31630== 
==31630== 
==31630== Process terminating with default action of signal 11 (SIGSEGV)
==31630==  Access not within mapped region at address 0x0
==31630==at 0x52AE388: ??? (in /usr/lib/libedit.so.2.11)
==31630==by 0x52B09AF: ??? (in /usr/lib/libedit.so.2.11)
==31630==by 0x52B6EDD: el_gets (in /usr/lib/libedit.so.2.11)
==31630==by 0x52C06E6: readline (in /usr/lib/libedit.so.2.11)
==31630==by 0x11C916: ??? (in /usr/lib/postgresql/8.4/bin/psql)
==31630==by 0x11F9BF: ??? (in /usr/lib/postgresql/8.4/bin/psql)
==31630==by 0x122943: main (in /usr/lib/postgresql/8.4/bin/psql)
==31630==  If you believe this happened as a result of a stack
==31630==  overflow in your program's main thread (unlikely but
==31630==  possible), you can try to increase the size of the
==31630==  main thread stack using the --main-stacksize= flag.
==31630==  The main thread stack size used in this run was 8388608.
==31630== 
==31630== HEAP SUMMARY:
==31630== in use at exit: 90,261 bytes in 311 blocks
==31630==   total heap usage: 668 allocs, 357 frees, 149,661 bytes allocated
==31630== 
==31630== LEAK SUMMARY:
==31630==definitely lost: 186 bytes in 4 blocks
==31630==indirectly lost: 480 bytes in 20 blocks
==31630==  possibly lost: 0 bytes in 0 blocks
==31630==still reachable: 89,595 bytes in 287 blocks
==31630== suppressed: 0 bytes in 0 blocks
==31630== Rerun with --leak-check=full to see details of leaked memory
==31630== 
==31630== For counts of detected and suppressed errors, rerun with: -v
==31630== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 8 from 6)
Segmentation fault
user@localhost ~ $

-- 
Ubuntu is an ancient African word meaning “I can’t install Debian.”
 -- unknown



smime.p7s
Description: S/MIME Cryptographic Signature

1 2 >

1 - 100 of 167 matches

Mail list logo