gmane.linux.debian.devel.gtk-gnome

Re: Environment variables when using the email launcher

Jean-Christophe Dubacq — 2012-05-23T06:28:11

On the other hand, another custom shortcut (to launch Chrome) is not
functional any more since the upgrade to 3.4.2-2. So it's possible that
something is missing and updating gnome-settings-daemon is not enough.
Should I switch to the full gnome-in-experimental suite?

Re: Environment variables when using the email launcher

Jean-Christophe Dubacq — 2012-05-22T18:12:40

Nope. Same symptoms. It still works fine from the launcher and from the
application menu (I didn't test with alt+f2 ; maybe I should).

gnome-settings-daemon:
  Installed: 3.4.2-2
  Candidate: 3.4.2-2
  Version table:
 *** 3.4.2-2 0
         50 http://ftp.fr.debian.org/debian/ experimental/main amd64
Packages
        100 /var/lib/dpkg/status
     3.2.2-3 0
        500 http://ftp.fr.debian.org/debian/ testing/main amd64 Packages
        100 http://ftp.fr.debian.org/debian/ unstable/main amd64 Packages
     2.30.2-2+squeeze1 0
        500 http://ftp.fr.debian.org/debian/ stable/main amd64 Packages

Sincerly,

Re: Environment variables when using the email launcher

Michael Biebl — 2012-05-19T23:28:04

I wouldn't have thought about searching in bugs for

Should be available in experimental now.

Let us know if that solves your problem.

Re: Environment variables when using the email launcher

Jean-Christophe Dubacq — 2012-05-19T21:00:28

I wouldn't have thought about searching in bugs for
gnome-settings-daemon for such a bug. I will test the upload as soon as
I see it.

Thanks,

Re: Environment variables when using the email launcher

Michael Biebl — 2012-05-19T17:16:16

This is probably
https://bugzilla.gnome.org/show_bug.cgi?id=662528

An upload of gnome-settings-daemon-3.4.2 containing this patch will be
coming soon.

Michael

Environment variables when using the email launcher

Jean-Christophe Dubacq — 2012-05-19T11:25:45

Hello,

I am in the process of testing seahorse integration with my usual
environment (wheezy/testing gnome3, without any special tweaks;
gnupg-agent installed but disabled at session start editing
/etc/X11/Xsession.d/90gpg-agent).

I find that if I launch icedove either from the terminal
(gnome-terminal, $GPG_AGENT_INFO is set) or from the launcher (left-hand
side of the window), I get gpg working ok (using seahorse as a
gpg-agent, I suppose).

However, if I launch it from the "shortcut" key set in the Keyboard
parameters, gpg is not working correctly (cannot contact gpg-agent: no
gpg-agent available in this session). My guess is that GPG_AGENT_INFO is
not set when using this special session.

I would like to investigate this further, but I do not have many ideas
about where to start. Do you have any ideas ?

Sincerly,

Re: Debian Installation Alpha 1 AMD64 netinst ISO installationreport

Josselin Mouette — 2012-05-17T10:30:25

Le mardi 15 mai 2012 à 00:46 +0200, Cyril Brulebois a écrit : 

A wild guess: when installing gstreamer0.10-pulseaudio some other
backends were removed, and no dependency remained on alsa-base.

Since alsa-base is essential to having working sound, I’d suggest moving
it to priority important, and/or adding a dependency somewhere in the
stack (pulseaudio/linux-any would be a good choice).

E' arrivato

dr.Alfieri — 2012-05-08T18:40:03

Nuovo kit Sbiancante per denti rapido.
Nuova formula ,ancora piu' efficace!

http://naturalmente.visit-page.com

Provalo;e' garantito!

Sono disponibili anche le ricariche.


Dr.Claudio Alfieri

Re: Disabling tracker-miner for some directory globally

Jean-Christophe Dubacq — 2012-04-29T18:14:11

Please note that the home directories are not on NFS, but subdirs of
home(s) are NFS-mounted.

Re: Disabling tracker-miner for some directory globally

Xavier Bestel — 2012-04-29T11:25:34

Le dimanche 29 avril 2012 à 10:23 +0200, Jean-Christophe Dubacq a
écrit :

I don't know if it's really related, but I continually have 2 (ou more)
tracker-store processes banging my harddrive an making everything slow.
If someone has a hint how to avoid that ...

Thanks,
Xav

Disabling tracker-miner for some directory globally

Jean-Christophe Dubacq — 2012-04-29T08:23:41

Hello,

Is there any way I can disable tracker for some directories (we have
some NFS directories and we really do not want any kind of tracker
activity duplicated 100 times on these directories). I have been looking
in the source code, but it's a bit too arcane for me to find if a global
configuration file exists. Is there?

Sincerly,

Bug#604934: Info received (Update on libproxy)

Debian Bug Tracking System — 2012-04-16T15:33:05

Thank you for the additional information you have supplied regarding
this Bug report.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
 Emilio Pozuelo Monfort <pochu< at >debian.org>

If you wish to submit further information on this problem, please
send it to 604934< at >bugs.debian.org.

Please do not send mail to owner< at >bugs.debian.org unless you wish
to report a problem with the Bug-tracking system.

Re: getting rid of the gnome-shell network-manager dependency

Miles Bader — 2012-04-05T10:10:33

I see.

Ok, I tried today, and removed NM, and everything does indeed seem to
work properly now.

Thanks for you help!

-miles

Re: getting rid of the gnome-shell network-manager dependency

Michael Biebl — 2012-04-05T05:25:40


This fix was in libnm-glib4, and libnm-glib4 needs to be installed as
gnome-shell links against it.

Re: getting rid of the gnome-shell network-manager dependency

Antti-Juhani Kaijanaho — 2012-04-05T04:35:55

You do not need to have network-manager installed.  But the source package
creates libnm-glib4, which you do need for gnome-shell.  The bug that led to
the crashes was in recent changes made to that library.

Re: getting rid of the gnome-shell network-manager dependency

Miles Bader — 2012-04-05T03:40:45


I'm a little confused by this ... since this fix seems to be in NM,
does this mean that network-manager still needs to be installed, but
can not be running?  [Before I didn't have NM installed at all, and
gnome-shell worked fine.]

If so, how does one put NM into this non-running state, and still
retain a working network (including automatic NFS moutns at boot,
etc)?  My impression was that NM hooked itself into the boot process
and disabled the other network handling ... e.g. it did this to
/etc/network/interfaces at install time:

   #NetworkManager#iface eth0 inet dhcp

Thanks,

-miles

Re: getting rid of the gnome-shell network-manager dependency

Michael Biebl — 2012-04-04T15:25:43

network-manager (0.9.4.0-3) unstable; urgency=low

  * debian/patches/12-initialize-gerror.patch: Initialize GError, else invalid
    free() crash can occur. Fixes the crash in gnome-shell if NetworkManager
    is not running. Patch cherry-picked from upstream. (Closes: #665791)
    Thank a lot to Antti-Juhani Kaijanaho for tracking down this problem!
  * Remove explicit Build-Depends on gir1.2-glib-2.0 and gir1.2-freedesktop,
    let libgirepository1.0-dev pull those dependencies.

 -- Michael Biebl <biebl< at >debian.org>  Tue, 03 Apr 2012 20:20:13 +0200

You still might have the old version of the library loaded.
So after upgrading to 0.9.4.0-3, you need to restart
gnome-shell.

Re: getting rid of the gnome-shell network-manager dependency

Miles Bader — 2012-04-04T14:07:54

Hmm, it still wasn't fixed in my update today ... maybe it hasn't
percolated through to the mirror I use?


 I did check the BTS, though a few days ago (which is where I found out
 about the install-NM workaround).

Thanks,

-miles

Re: getting rid of the gnome-shell network-manager dependency

Michael Biebl — 2012-04-04T12:25:22

yesterday


Instead of whining, you could have checked the BTS

getting rid of the gnome-shell network-manager dependency

Miles Bader — 2012-04-04T08:40:38

Any idea when gnome-shell will be fixed to not depend on
network-manager being installed?

[gnome-shell dies at startup unless network-manager is installed, but
network-manager interacts very badly with NFS, so installing NM is at
best a painful workaround...]

Thanks,

-Miles

Re: Default groups

Jean-Christophe Dubacq — 2012-04-02T09:05:51

Le 02/04/2012 03:51, Paul Wise a écrit :
I tried it, and apparently fuse is still required (for example, to sync
tomboy notes by ssh). I just wait for somebody with a USB key to test
whether plugdev is still necessary.

I am still pondering if I add these groups through adduser or to
/etc/security/group.conf. I did not find a way to mix fuse permissions
and policykit or consolekit.