Bug#916247: upgrade 239.1+20181115-1 -> 239.3-1+patch still has problems with mplayer in currently running session

2018-12-14 Thread Arthur Marsh
OK, I rebuilt with pbuilder, then downgraded to version 239.1+20181115-1 then upgraded again to 239.3-1+patches and did not have problems with the logged in desktop session thanks. Arthur. On 14 December 2018 8:19:34 pm ACDT, Mark Hindley wrote: >On Fri, Dec 14, 2018 at 06:57:59PM +1030,

Bug#916247: upgrade 239.1+20181115-1 -> 239.3-1+patch still has problems with mplayer in currently running session

2018-12-14 Thread Mark Hindley
On Fri, Dec 14, 2018 at 06:57:59PM +1030, Arthur Marsh wrote: >Hi, I ran debuild -b after applying your second patch on top of your >first patch, and received the following result: Can you try building it in a pbuilder or sbuilder chroot. Mark

Bug#916247: upgrade 239.1+20181115-1 -> 239.3-1+patch still has problems with mplayer in currently running session

2018-12-14 Thread Arthur Marsh
uild subprocess returned exit status 2 debuild: fatal error at line 1182: dpkg-buildpackage -us -uc -ui -b failed   - Original Message - From: "Mark Hindley" To:"Arthur Marsh" , Cc: Sent:Fri, 14 Dec 2018 00:57:51 +0000 Subject:Re: Bug#916247: upgrade 239.1+201

Bug#916247: upgrade 239.1+20181115-1 -> 239.3-1+patch still has problems with mplayer in currently running session

2018-12-13 Thread Mark Hindley
On Thu, Dec 13, 2018 at 02:20:01PM +, Mark Hindley wrote: > This is a different issue. I am discussing solutions with upstream. > > See https://github.com/elogind/elogind/issues/104 Arthur, Could you try this patch please? It works for me. commit db6a15aa2b3a575a63bf567915e96575db938c84

Bug#916247: upgrade 239.1+20181115-1 -> 239.3-1+patch still has problems with mplayer in currently running session

2018-12-13 Thread Mark Hindley
On Thu, Dec 13, 2018 at 10:47:41PM +1030, Arthur Marsh wrote: > After applying the patch suggested for Debian bug 916212 for elogind, >I could restart elogind (239.3-1+patch) without experiencing problems >in the currently running user session. > >However, the upgrade

Bug#916247: upgrade 239.1+20181115-1 -> 239.3-1+patch still has problems with mplayer in currently running session

2018-12-13 Thread Arthur Marsh
After applying the patch suggested for Debian bug 916212 for elogind, I could restart elogind (239.3-1+patch) without experiencing problems in the currently running user session. However, the upgrade 239.1+20181115-1 -> 239.3-1+patch still resulted in mplayer not being able to play a new track