Linux Archive

Linux Archive (http://www.linux-archive.org/)
-   Debian User (http://www.linux-archive.org/debian-user/)
-   -   Using GTK+ 2.x and GTK+ 3 in the same process is not supported (http://www.linux-archive.org/debian-user/545261-using-gtk-2-x-gtk-3-same-process-not-supported.html)

"John A. Sullivan III" 06-28-2011 01:05 AM

Using GTK+ 2.x and GTK+ 3 in the same process is not supported
 
Hello, all. Today, I upgraded my wireshark as you can see from the
below excerpt from the apt log. Since doing so, I cannot run any GTK
based applications. They all fail with:

Using GTK+ 2.x and GTK+ 3 in the same process is not supported

Here is the log:

Commandline: apt-get install wireshark wireshark.doc
Install: libwsutil1:i386 (1.6.0-1, automatic), libwireshark-data:i386
(1.6.0-1, automatic), wireshark-doc:i386 (1.6.0-1),
libgdk-pixbuf2.0-0:i386 (2.23.3-3, automatic), libwireshark1:i386
(1.6.0-1, automatic), libwiretap1:i386 (1.6.0-1, automatic)
Upgrade: libgail18:i386 (2.20.1-2, 2.24.4-3), libwmf0.2-7:i386
(0.2.8.4-6.1+b1, 0.2.8.4-8), libgtk2.0-bin:i386 (2.20.1-2, 2.24.4-3),
libgeoip1:i386 (1.4.7~beta12+dfsg-1, 1.4.7+dfsg-2), wireshark:i386
(1.2.11-6+squeeze1, 1.6.0-1), librsvg2-2:i386 (2.26.3-1, 2.34.0-1),
librsvg2-common:i386 (2.26.3-1, 2.34.0-1), libgtk2.0-0:i386 (2.20.1-2,
2.24.4-3), wireshark-common:i386 (1.2.11-6+squeeze1, 1.6.0-1)

Here are my preferences:
Package: *
Pin: release a=squeeze
Pin: release o=LP-PPA-trinity-trinity-builddeps
Pin-Priority: 902

Package: *
Pin: release a=squeeze
Pin: release o=LP-PPA-trinity-trinity
Pin-Priority: 901

Package: *
Pin: release a=squeeze
Pin-Priority: 900

Package: *
Pin: release a=wheezy
Pin-Priority: 800


What happened and how do I fix it? This is a bit of a disaster. Thanks
- John


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 1309223156.28063.40.camel@denise.theartistscloset. com">http://lists.debian.org/1309223156.28063.40.camel@denise.theartistscloset. com

Camaleón 06-28-2011 01:16 PM

Using GTK+ 2.x and GTK+ 3 in the same process is not supported
 
On Mon, 27 Jun 2011 21:05:56 -0400, John A. Sullivan III wrote:

> Hello, all. Today, I upgraded my wireshark as you can see from the
> below excerpt from the apt log. Since doing so, I cannot run any GTK
> based applications. They all fail with:
>
> Using GTK+ 2.x and GTK+ 3 in the same process is not supported
>
> Here is the log:

(...)

> Package: *
> Pin: release a=wheezy
> Pin-Priority: 800
>
>
> What happened and how do I fix it? This is a bit of a disaster. Thanks

Google seems to point at GTK+ 2/3 conflicts.

Is it possible that some GTK+ libraries have been updated to newer
versions because of the above wheezy pinning? :-?

Greetings,

--
Camaleón


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: pan.2011.06.28.13.16.14@gmail.com">http://lists.debian.org/pan.2011.06.28.13.16.14@gmail.com

"John A. Sullivan III" 06-28-2011 01:31 PM

Using GTK+ 2.x and GTK+ 3 in the same process is not supported
 
On Tue, 2011-06-28 at 13:16 +0000, Camaleón wrote:
> On Mon, 27 Jun 2011 21:05:56 -0400, John A. Sullivan III wrote:
>
> > Hello, all. Today, I upgraded my wireshark as you can see from the
> > below excerpt from the apt log. Since doing so, I cannot run any GTK
> > based applications. They all fail with:
> >
> > Using GTK+ 2.x and GTK+ 3 in the same process is not supported
> >
> > Here is the log:
>
> (...)
>
> > Package: *
> > Pin: release a=wheezy
> > Pin-Priority: 800
> >
> >
> > What happened and how do I fix it? This is a bit of a disaster. Thanks
>
> Google seems to point at GTK+ 2/3 conflicts.
>
> Is it possible that some GTK+ libraries have been updated to newer
> versions because of the above wheezy pinning? :-?
>
> Greetings,
>
> --
> Camaleón
>
>
That's what I'm guessing but I don't see it:

ii libgtk2.0-0 2.24.4-3 The GTK+ graphical user interface library
ii libgtk2.0-bin 2.24.4-3 The programs for the GTK+ graphical user interface library
ii libgtk2.0-common 2.20.1-2 Common files for the GTK+ graphical user interface library

Everything is 2.x although I wonder why common is a different version.
I'll try updating that next. I also don't know why libraries would have
been brought in from Wheezy since it is pinned lower than Squeeze.
Wireshark should have been in Squeeze so it should not have pulled it
from Wheezy and the same for any libraries. Thanks - John



--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 1309267904.5956.3.camel@denise.theartistscloset.co m">http://lists.debian.org/1309267904.5956.3.camel@denise.theartistscloset.co m

Camaleón 06-28-2011 02:36 PM

Using GTK+ 2.x and GTK+ 3 in the same process is not supported
 
On Tue, 28 Jun 2011 09:31:44 -0400, John A. Sullivan III wrote:

> On Tue, 2011-06-28 at 13:16 +0000, Camaleón wrote:

>> > What happened and how do I fix it? This is a bit of a disaster.
>> > Thanks
>>
>> Google seems to point at GTK+ 2/3 conflicts.
>>
>> Is it possible that some GTK+ libraries have been updated to newer
>> versions because of the above wheezy pinning? :-?
>>
>>
>>
> That's what I'm guessing but I don't see it:
>
> ii libgtk2.0-0 2.24.4-3 The GTK+ graphical user interface library
> ii libgtk2.0-bin 2.24.4-3 The programs for the GTK+ graphical user interface library
> ii libgtk2.0-common 2.20.1-2 Common files for the GTK+ graphical user interface library

I would put the focus into the "upgraded" packages:

libgail18:i386 (2.20.1-2, 2.24.4-3)
libwmf0.2-7:i386 (0.2.8.4-6.1+b1, 0.2.8.4-8)
libgtk2.0-bin:i386 (2.20.1-2, 2.24.4-3)
libgeoip1:i386 (1.4.7~beta12+dfsg-1, 1.4.7+dfsg-2)
wireshark:i386 (1.2.11-6+squeeze1, 1.6.0-1)
librsvg2-2:i386 (2.26.3-1, 2.34.0-1)
librsvg2-common:i386 (2.26.3-1, 2.34.0-1)
libgtk2.0-0:i386 (2.20.1-2,2.24.4-3)
wireshark-common:i386 (1.2.11-6+squeeze1, 1.6.0-1)

> Everything is 2.x although I wonder why common is a different version.

Updated versions are from wheezy, as you say below.

> I'll try updating that next. I also don't know why libraries would have
> been brought in from Wheezy since it is pinned lower than Squeeze.
> Wireshark should have been in Squeeze so it should not have pulled it
> from Wheezy and the same for any libraries. Thanks - John

I can't help for the pinning issue, that thingy looks like a sort of "black
magic" to me :-). But yes, it seems they're now from wheezy and that pulled
the updated GKT+ libraries so I would try to return back the packages to the
old version and see how it goes.

Greetings,

--
Camaleón


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: pan.2011.06.28.14.35.58@gmail.com">http://lists.debian.org/pan.2011.06.28.14.35.58@gmail.com

"John A. Sullivan III" 06-28-2011 02:56 PM

Using GTK+ 2.x and GTK+ 3 in the same process is not supported
 
On Tue, 2011-06-28 at 14:36 +0000, Camaleón wrote:
> On Tue, 28 Jun 2011 09:31:44 -0400, John A. Sullivan III wrote:
>
> > On Tue, 2011-06-28 at 13:16 +0000, Camaleón wrote:
>
> >> > What happened and how do I fix it? This is a bit of a disaster.
> >> > Thanks
> >>
> >> Google seems to point at GTK+ 2/3 conflicts.
> >>
> >> Is it possible that some GTK+ libraries have been updated to newer
> >> versions because of the above wheezy pinning? :-?
> >>
> >>
> >>
> > That's what I'm guessing but I don't see it:
> >
> > ii libgtk2.0-0 2.24.4-3 The GTK+ graphical user interface library
> > ii libgtk2.0-bin 2.24.4-3 The programs for the GTK+ graphical user interface library
> > ii libgtk2.0-common 2.20.1-2 Common files for the GTK+ graphical user interface library
>
> I would put the focus into the "upgraded" packages:
>
> libgail18:i386 (2.20.1-2, 2.24.4-3)
> libwmf0.2-7:i386 (0.2.8.4-6.1+b1, 0.2.8.4-8)
> libgtk2.0-bin:i386 (2.20.1-2, 2.24.4-3)
> libgeoip1:i386 (1.4.7~beta12+dfsg-1, 1.4.7+dfsg-2)
> wireshark:i386 (1.2.11-6+squeeze1, 1.6.0-1)
> librsvg2-2:i386 (2.26.3-1, 2.34.0-1)
> librsvg2-common:i386 (2.26.3-1, 2.34.0-1)
> libgtk2.0-0:i386 (2.20.1-2,2.24.4-3)
> wireshark-common:i386 (1.2.11-6+squeeze1, 1.6.0-1)
>
> > Everything is 2.x although I wonder why common is a different version.
>
> Updated versions are from wheezy, as you say below.
>
> > I'll try updating that next. I also don't know why libraries would have
> > been brought in from Wheezy since it is pinned lower than Squeeze.
> > Wireshark should have been in Squeeze so it should not have pulled it
> > from Wheezy and the same for any libraries. Thanks - John
>
> I can't help for the pinning issue, that thingy looks like a sort of "black
> magic" to me :-). But yes, it seems they're now from wheezy and that pulled
> the updated GKT+ libraries so I would try to return back the packages to the
> old version and see how it goes.
>
> Greetings,
>
> --
> Camaleón
>
>
Grrr . . . upgrading common did not help but it made it clear it was
from Wheezy. Downgrading all libgtk to 2.20 wanted to uninstall half my
system. So, I did an apt-get update/upgrade and it has upgrade 500+
packages to wheezy :( We'll see if it works after a reboot but I really
didn't want to run Wheezy. That's why I pinned it below Squeeze.
Thanks - John


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 1309273005.5956.6.camel@denise.theartistscloset.co m">http://lists.debian.org/1309273005.5956.6.camel@denise.theartistscloset.co m

"John A. Sullivan III" 06-28-2011 03:37 PM

Using GTK+ 2.x and GTK+ 3 in the same process is not supported
 
On Tue, 2011-06-28 at 10:56 -0400, John A. Sullivan III wrote:
> On Tue, 2011-06-28 at 14:36 +0000, Camaleón wrote:
> > On Tue, 28 Jun 2011 09:31:44 -0400, John A. Sullivan III wrote:
> >
> > > On Tue, 2011-06-28 at 13:16 +0000, Camaleón wrote:
> >
> > >> > What happened and how do I fix it? This is a bit of a disaster.
> > >> > Thanks
> > >>
> > >> Google seems to point at GTK+ 2/3 conflicts.
> > >>
> > >> Is it possible that some GTK+ libraries have been updated to newer
> > >> versions because of the above wheezy pinning? :-?
> > >>
> > >>
> > >>
> > > That's what I'm guessing but I don't see it:
> > >
> > > ii libgtk2.0-0 2.24.4-3 The GTK+ graphical user interface library
> > > ii libgtk2.0-bin 2.24.4-3 The programs for the GTK+ graphical user interface library
> > > ii libgtk2.0-common 2.20.1-2 Common files for the GTK+ graphical user interface library
> >
> > I would put the focus into the "upgraded" packages:
> >
> > libgail18:i386 (2.20.1-2, 2.24.4-3)
> > libwmf0.2-7:i386 (0.2.8.4-6.1+b1, 0.2.8.4-8)
> > libgtk2.0-bin:i386 (2.20.1-2, 2.24.4-3)
> > libgeoip1:i386 (1.4.7~beta12+dfsg-1, 1.4.7+dfsg-2)
> > wireshark:i386 (1.2.11-6+squeeze1, 1.6.0-1)
> > librsvg2-2:i386 (2.26.3-1, 2.34.0-1)
> > librsvg2-common:i386 (2.26.3-1, 2.34.0-1)
> > libgtk2.0-0:i386 (2.20.1-2,2.24.4-3)
> > wireshark-common:i386 (1.2.11-6+squeeze1, 1.6.0-1)
> >
> > > Everything is 2.x although I wonder why common is a different version.
> >
> > Updated versions are from wheezy, as you say below.
> >
> > > I'll try updating that next. I also don't know why libraries would have
> > > been brought in from Wheezy since it is pinned lower than Squeeze.
> > > Wireshark should have been in Squeeze so it should not have pulled it
> > > from Wheezy and the same for any libraries. Thanks - John
> >
> > I can't help for the pinning issue, that thingy looks like a sort of "black
> > magic" to me :-). But yes, it seems they're now from wheezy and that pulled
> > the updated GKT+ libraries so I would try to return back the packages to the
> > old version and see how it goes.
> >
> > Greetings,
> >
> > --
> > Camaleón
> >
> >
> Grrr . . . upgrading common did not help but it made it clear it was
> from Wheezy. Downgrading all libgtk to 2.20 wanted to uninstall half my
> system. So, I did an apt-get update/upgrade and it has upgrade 500+
> packages to wheezy :( We'll see if it works after a reboot but I really
> didn't want to run Wheezy. That's why I pinned it below Squeeze.
> Thanks - John
>
>
Argh! This isn't getting any better. After reluctantly upgrading half
my system to Wheezy, and after several apt-get -f install, I still get
the same error message! Hmm . . . . now, after an apt-get clean, the
update, an apt-get upgrade gives me:
The following packages will be upgraded:
libglib2.0-data
1 upgraded, 0 newly installed, 0 to remove and 366 not upgraded.
Need to get 1,994 kB of archives.
After this operation, 2,187 kB of additional disk space will be used.
Do you want to continue [Y/n]? y
Get:1 http://debian.lcs.mit.edu/debian/ wheezy/main libglib2.0-data all
2.28.6-1 [1,994 kB]
Fetched 1,994 kB in 2s (846 kB/s)
Reading changelogs... Done
(Reading database ... 199996 files and directories currently installed.)
Preparing to replace libglib2.0-data 2.24.2-1
(using .../libglib2.0-data_2.28.6-1_all.deb) ...
rm: cannot remove `/usr/share/doc/libglib2.0-data': Is a directory
dpkg: error
processing /var/cache/apt/archives/libglib2.0-data_2.28.6-1_all.deb
(--unpack):
subprocess new pre-installation script returned error exit status 1
configured to not write apport reports
Errors were encountered while
processing:
/var/cache/apt/archives/libglib2.0-data_2.28.6-1_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

I'll try renaming that directory and see what happens. I'm shocked that
a simple apt-get install wireshark would cause such grief and leave a
broken system. Thanks - John


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 1309275425.5956.13.camel@denise.theartistscloset.c om">http://lists.debian.org/1309275425.5956.13.camel@denise.theartistscloset.c om

"John A. Sullivan III" 06-28-2011 03:54 PM

Using GTK+ 2.x and GTK+ 3 in the same process is not supported
 
On Tue, 2011-06-28 at 11:37 -0400, John A. Sullivan III wrote:
> On Tue, 2011-06-28 at 10:56 -0400, John A. Sullivan III wrote:
> > On Tue, 2011-06-28 at 14:36 +0000, Camaleón wrote:
> > > On Tue, 28 Jun 2011 09:31:44 -0400, John A. Sullivan III wrote:
> > >
> > > > On Tue, 2011-06-28 at 13:16 +0000, Camaleón wrote:
> > >
> > > >> > What happened and how do I fix it? This is a bit of a disaster.
> > > >> > Thanks
> > > >>
> > > >> Google seems to point at GTK+ 2/3 conflicts.
> > > >>
> > > >> Is it possible that some GTK+ libraries have been updated to newer
> > > >> versions because of the above wheezy pinning? :-?
> > > >>
> > > >>
> > > >>
> > > > That's what I'm guessing but I don't see it:
> > > >
> > > > ii libgtk2.0-0 2.24.4-3 The GTK+ graphical user interface library
> > > > ii libgtk2.0-bin 2.24.4-3 The programs for the GTK+ graphical user interface library
> > > > ii libgtk2.0-common 2.20.1-2 Common files for the GTK+ graphical user interface library
> > >
> > > I would put the focus into the "upgraded" packages:
> > >
> > > libgail18:i386 (2.20.1-2, 2.24.4-3)
> > > libwmf0.2-7:i386 (0.2.8.4-6.1+b1, 0.2.8.4-8)
> > > libgtk2.0-bin:i386 (2.20.1-2, 2.24.4-3)
> > > libgeoip1:i386 (1.4.7~beta12+dfsg-1, 1.4.7+dfsg-2)
> > > wireshark:i386 (1.2.11-6+squeeze1, 1.6.0-1)
> > > librsvg2-2:i386 (2.26.3-1, 2.34.0-1)
> > > librsvg2-common:i386 (2.26.3-1, 2.34.0-1)
> > > libgtk2.0-0:i386 (2.20.1-2,2.24.4-3)
> > > wireshark-common:i386 (1.2.11-6+squeeze1, 1.6.0-1)
> > >
> > > > Everything is 2.x although I wonder why common is a different version.
> > >
> > > Updated versions are from wheezy, as you say below.
> > >
> > > > I'll try updating that next. I also don't know why libraries would have
> > > > been brought in from Wheezy since it is pinned lower than Squeeze.
> > > > Wireshark should have been in Squeeze so it should not have pulled it
> > > > from Wheezy and the same for any libraries. Thanks - John
> > >
> > > I can't help for the pinning issue, that thingy looks like a sort of "black
> > > magic" to me :-). But yes, it seems they're now from wheezy and that pulled
> > > the updated GKT+ libraries so I would try to return back the packages to the
> > > old version and see how it goes.
> > >
> > > Greetings,
> > >
> > > --
> > > Camaleón
> > >
> > >
> > Grrr . . . upgrading common did not help but it made it clear it was
> > from Wheezy. Downgrading all libgtk to 2.20 wanted to uninstall half my
> > system. So, I did an apt-get update/upgrade and it has upgrade 500+
> > packages to wheezy :( We'll see if it works after a reboot but I really
> > didn't want to run Wheezy. That's why I pinned it below Squeeze.
> > Thanks - John
> >
> >
> Argh! This isn't getting any better. After reluctantly upgrading half
> my system to Wheezy, and after several apt-get -f install, I still get
> the same error message! Hmm . . . . now, after an apt-get clean, the
> update, an apt-get upgrade gives me:
> The following packages will be upgraded:
> libglib2.0-data
> 1 upgraded, 0 newly installed, 0 to remove and 366 not upgraded.
> Need to get 1,994 kB of archives.
> After this operation, 2,187 kB of additional disk space will be used.
> Do you want to continue [Y/n]? y
> Get:1 http://debian.lcs.mit.edu/debian/ wheezy/main libglib2.0-data all
> 2.28.6-1 [1,994 kB]
> Fetched 1,994 kB in 2s (846 kB/s)
> Reading changelogs... Done
> (Reading database ... 199996 files and directories currently installed.)
> Preparing to replace libglib2.0-data 2.24.2-1
> (using .../libglib2.0-data_2.28.6-1_all.deb) ...
> rm: cannot remove `/usr/share/doc/libglib2.0-data': Is a directory
> dpkg: error
> processing /var/cache/apt/archives/libglib2.0-data_2.28.6-1_all.deb
> (--unpack):
> subprocess new pre-installation script returned error exit status 1
> configured to not write apport reports
> Errors were encountered while
> processing:
> /var/cache/apt/archives/libglib2.0-data_2.28.6-1_all.deb
> E: Sub-process /usr/bin/dpkg returned an error code (1)
>
> I'll try renaming that directory and see what happens. I'm shocked that
> a simple apt-get install wireshark would cause such grief and leave a
> broken system. Thanks - John
<snip>
Double Argh!! renaming the directory allowed the upgrade to
libglib2.0-data but I still have the problem, e.g.,

jsullivan@jaseee:~$ xsane

Gtk-ERROR **: GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in
the same process is not supported
aborting...
Aborted

So I'm still left with a broken system after a simple apt-get install
wireshark. It is almost certainly the libgtk2.0-bin:i386 (2.20.1-2,
2.24.4-3) that was pulled in but I can't seem to back it out without
uninstalling half my system and rolling everything forward hasn't fixed
the problem. What next? Thanks - John


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 1309276473.5956.18.camel@denise.theartistscloset.c om">http://lists.debian.org/1309276473.5956.18.camel@denise.theartistscloset.c om

Camaleón 06-28-2011 04:18 PM

Using GTK+ 2.x and GTK+ 3 in the same process is not supported
 
On Tue, 28 Jun 2011 11:54:33 -0400, John A. Sullivan III wrote:

> On Tue, 2011-06-28 at 11:37 -0400, John A. Sullivan III wrote:
>> On Tue, 2011-06-28 at 10:56 -0400, John A. Sullivan III wrote:
>> > On Tue, 2011-06-28 at 14:36 +0000, Camaleón wrote:

(...)

>> > > > I'll try updating that next. I also don't know why libraries
>> > > > would have been brought in from Wheezy since it is pinned lower
>> > > > than Squeeze. Wireshark should have been in Squeeze so it should
>> > > > not have pulled it from Wheezy and the same for any libraries.
>> > > > Thanks - John
>> > >
>> > > I can't help for the pinning issue, that thingy looks like a sort
>> > > of "black magic" to me :-). But yes, it seems they're now from
>> > > wheezy and that pulled the updated GKT+ libraries so I would try to
>> > > return back the packages to the old version and see how it goes.
>> > >
>> > Grrr . . . upgrading common did not help but it made it clear it was
>> > from Wheezy. Downgrading all libgtk to 2.20 wanted to uninstall half
>> > my system. So, I did an apt-get update/upgrade and it has upgrade
>> > 500+ packages to wheezy :( We'll see if it works after a reboot but
>> > I really didn't want to run Wheezy. That's why I pinned it below
>> > Squeeze. Thanks - John
>> >
>> >

(...)

> Double Argh!! renaming the directory allowed the upgrade to
> libglib2.0-data but I still have the problem, e.g.,
>
> jsullivan@jaseee:~$ xsane
>
> Gtk-ERROR **: GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in
> the same process is not supported
> aborting...
> Aborted
>
> So I'm still left with a broken system after a simple apt-get install
> wireshark. It is almost certainly the libgtk2.0-bin:i386 (2.20.1-2,
> 2.24.4-3) that was pulled in but I can't seem to back it out without
> uninstalling half my system and rolling everything forward hasn't fixed
> the problem. What next? Thanks - John

Ouch! ;-(

That's why I don't like to play with black magic stuff that goes beyond
my control...

Are you still using any pinning in your "sources.list" file? How does the
file look like by now?

Take it easy, maybe all is not lost, afterall. Let's see is someone here
can give you a hand for restoring the system functionalities.

Greetings,

--
Camaleón


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: pan.2011.06.28.16.18.36@gmail.com">http://lists.debian.org/pan.2011.06.28.16.18.36@gmail.com


All times are GMT. The time now is 07:53 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.