Bug#754314: systemd support for kdm

2014-08-14 Thread Moritz Mühlenhoff
On Tue, Aug 12, 2014 at 10:43:11AM +0200, Michael Biebl wrote:
> Hi,
> 
> On Thu, Jul 17, 2014 at 05:17:23PM +0200, Moritz Muehlenhoff wrote:
> > On Mon, Jul 14, 2014 at 06:34:40PM +0200, Moritz Mühlenhoff wrote:
> > > On Wed, Jul 09, 2014 at 10:16:07PM +0200, Moritz Muehlenhoff wrote:
> > > > Source: kde-workspace
> > > > Severity: wishlist
> > > > Tags: patch
> > > > 
> > > > activation of the service
> > > > -
> > > > 
> > > > After installation of the updated package the service isn't enabled
> > > > by default. You'll need to run "systemctl enable kdm.service" for
> > > > that. I'm not sure how the default display manager is handled if
> > > > several systemd units are installed, so it's probably for the best 
> > > > right now.
> > > 
> > > Michael Stapelberg explained to me that the unit file needs an additional
> > > WantedBy=multi-user.target which would resolve this.
> > 
> > This doesn't seem to be sufficient, I still need to enable the service 
> > manually
> > ATM.
> > 
> 
> This issue was discussed during the systemd/GNOME sprint this spring.
> I.e. how the display-manager.service symlink is supposed to be managed
> when multiple display managers are installed.
> 
> lightdm and gdm3 are already updated to support this scheme, so I'm bringing
> their maintainers into the loop here.
> Please coordinate with them when adding systemd support to kdm.

We should really wrap this into some common code, which is included from
the respective display managers! I've looked into lightdm amd gdm3 and 
they already diverge (lightdm misses the removal code present for gdm3). 
After all, this affects wdm and xdm as well.

Cheers,
Moritz


-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140814202916.GA6931@pisco.westfalen.local



Re: Bug#757841: [kmail] Cannot update localhost mbox

2014-08-14 Thread Kevin Krammer
On Wednesday, 2014-08-13, 22:46:40, Antonio Marcos López Alonso wrote:
> El Martes, 12 de agosto de 2014 15:29:58 Kevin Krammer escribió:
> > Do you have file monitoring enabled?
> > 
> > Cheers,
> > Kevin
> 
> I had it at the beginning, then I re-created the account, disabled file
> monitoring and still it worked right once only after creating the account.
> Also tried to use a procmail lock (after using none) to no avail.

You have two options for getting updated data:
1) file monitoring: the program uses the operating system's file change 
notification mechanism to know when the file has been changed by another 
program

2) interval checking: the program reloads the file regularily in a 
configurable time interval.

I personally use (1) for my /var/spool/$user mail file because it doesn't get 
updated very often so regular reloads would just be a waste of resources.

Cheers,
Kevin

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


Bug#758109: obsolete okular patch

2014-08-14 Thread Jonathan Riddell
Package: okular

no_xrandr_support_on_xvfb.patch is unneeded with libkscreen 1.0.5


-- 
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20140814095320.gx26...@starsky.19inch.net