r uses uses a seccomp sandbox for its extractors nowadays.
> The error you get is most likely a result of that.
Thanks Michael. I just checked upstream and this issue is reported and fixed
already (Probably in version 1.12).
https://bugzilla.gnome.org/show_bug.cgi?id=779342
--
Ritesh Raj Sa
Package: libpam-systemd
Version: 232-23
Followup-For: Bug #732209
I see the same problem show up on my GNOME box. In my case, it is
tracker that is complaining, which could be a reason why I haven't
directly witnessed any loss of functionality in my laptop usage.
May 18 11:44:52 learner dbus-da
port. :-(
I rebooted the machine, which may have happened after a week of uptime, and now
I cannot reproduce the problem.
I need to improve my bug filing skills.
Do you see anything useful in this bug report? Otherwise, lets close this and
sorry about the noise.
- --
Ritesh Raj Sarraf |
=== AUTHENTICATING FOR org.freedesktop.policykit.exec ===
Authentication is needed to run `/bin/true' as the super user
Authenticating as: Ritesh Raj Sarraf,,, (rrs)
Password:
polkit-agent-helper-1: error response to PolicyKit daemon:
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
prompt where exactly?
> On hostA, hostB?
The action (machinectl) is run on hostB over SSH.
> Does userC have a running X session on hostB besides the SSH session?
>
Yes. hostB also runs Debian Unstable + Xorg + GNOME.
> Still not getting the full picture here yet.
- --
G FOR org.freedesktop.machine1.login ===
Authentication is required to log into a local container.
Authenticating as: Ritesh Raj Sarraf,,, (rrs)
Password:
AUTHENTICATION COMPLETE ===
Connected to machine fitbit. Press ^] three times within 1s to exit session.
Debian GNU/Linux 9 fitbit pts/0
fi
Package: systemd
Version: 232-17
Severity: important
Hello,
***
rrs@chutzpah:~$ echo $DISPLAY
localhost:10.0
14:22 __ _
rrs@chutzpah:~$ export DISPLAY=""
14:22 __ _
rrs@chutzpah:~$ machinectl login debTemplate
networkd[923]:
> [/etc/systemd/network/tap.netdev:5] Unknown section 'TAP'. Ignoring.
>
> Would be great if you can file a bug report upstream. This doesn't look
> like a Debian specific issue.
Thanks. Bug filed and linked with this one.
- --
Ritesh Raj Sarraf | http://people
ing?action=show&redirect=systemd%2FPackaging#Using_debhelper_with_dh_systemd
- --
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEQCVDstmIVAB/Yn02pjpYo/LhdWkFAliI2UoACgkQpjpYo/Lh
dWnfGQ//Zbjrxxw6
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Wed, 2017-01-25 at 20:05 +0530, Ritesh Raj Sarraf wrote:
> > I just purged iio-sensor-proxy, but:
> >
> > $ ps 574
> > PID TTY STAT TIME COMMAND
> > 574 ? Ssl 4:10 /usr/sbin/iio-sensor-proxy
&g
etty.
In my opinion, for now, euid != 0 with an exit is fine. But you want want to
exit 1, which would justify the actual error cause.
- --
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEQCVDstmIVAB/Yn02pj
com/systemd/systemd/issues/1559
I think this Debian bug could be marked as done.
- --
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEQCVDstmIVAB/Yn02pjpYo/LhdWkFAlhU68wACgkQpjpYo/Lh
dWl4CBAApoO5WR+M0w
Package: systemd-coredump
Version: 231-10
Severity: wishlist
I just started using systemd-coredump and was wondering if it has
capability to generate a full stack trace ?
A standard installation wouldn't really have all the debug symbol
packages installed. On Ubuntu (and also an outdated version
ause of missing Reload), and Restart's effect are
not desirable in all scenarios.
The bug is only happening in one of the case, i.e. only during resume.
THe same code works fine after resumption.
Any advise where I should look ?
--
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - T
Control: reassign -1 virutalbox
On Wed, 2016-02-10 at 17:40 +0530, Ritesh Raj Sarraf wrote:
> On Wed, 2016-02-10 at 17:28 +0530, Ritesh Raj Sarraf wrote:
> > I hope I have been able to explain the problem. Or in other words,
> > how
> > do I achieve a bridge interface stat
On Wed, 2016-02-10 at 17:28 +0530, Ritesh Raj Sarraf wrote:
> I hope I have been able to explain the problem. Or in other words,
> how
> do I achieve a bridge interface status like the following under
> systemd-networkd ?
>
> 4: sysbr0: mtu 1500 qdisc noqueue
> state UP gr
Thanks Martin.
For the issue in itself, it now looks like something specific to
systemd.
I'll see if I can take it up with upstream devs.
Thanks,
Ritesh
On Tue, 2015-11-17 at 17:44 +0100, Martin Pitt wrote:
> Ritesh Raj Sarraf [2015-11-14 15:18 +0530]:
> > > > IPForwar
On Sat, 2015-11-14 at 15:27 +0530, Ritesh Raj Sarraf wrote:
>
> I am not sure how it determines the "routable" status. The default
> gateway is 172.16.20.1, which is not pingable.
The same setup, now bound to the traditional bridge, is working.
root@deb-template:~
159/16 via 172.16.20.1
Nov 14 15:28:35 deb-template systemd-networkd[281]: host0: Configured
The "cannot configure IPv4." is now a warning message.
https://github.com/systemd/systemd/pull/495/files
--
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Necessity is
On Sat, 2015-11-14 at 15:18 +0530, Ritesh Raj Sarraf wrote:
> That said, it still does not work. And the odd part is, networking is
> only broken for IPv4.
From within the container, this reporting from networkctl is
interesting.
It states:
root@deb-template:~# networkctl status
●
s is obsolete, is not going to happen any time
soon.
I think upstream had a similar view about /var/lib/machines/, where in
they chose btrfs only. Which led to users with ext4, with almost no
functionality. Please see: https://github.com/systemd/systemd/issues/13
08 for details. It is confirmed as
rt of next upload.
--
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Necessity is the mother of invention."
signature.asc
Description: This is a digitally signed message part
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintain
age for core dump handlers and have
> each
> of them provide that and conflict with it.
>
> I propose core-dump-handler as the virtual package.
Should work for apport. Once the final name is finalized, I'll add the
the relation into the package.
--
Ritesh Raj Sarraf
RESEARCHUT -
On Thu, 2015-10-15 at 03:16 +0200, Michael Biebl wrote:
> I've uploaded 0.20150901t074837.245fe93-1, would be great if you can
> retry with that version.
Thanks Michael. This version works perfect on my setup.
--
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universa
On Fri, 2015-10-02 at 23:32 +0300, Sebastian Dröge wrote:
> I get the same here, so it's not just your system being weird.
> journalctl also shows this for various other services, but a gnome
> -shell session starts up without problems... so it doesn't seem to
> affect everything.
I'm glad that yo
on
> logic,
> and you can't rely on that in your multipath udeb.
Hmmm... I'll look into it later. But when you say "No systemd in d-i",
does it mean that is how it is going to remain ?
--
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating Sys
because upstream added systemd dependency
some time ago. For Jessie, I had disabled systemd support, but now, it
makes sense to have it, and align with upstream and other
distributions.
So, I think the real question is about why libsystemd0 does not have a
udeb ?
systemd maintainers should pro
urnal access (I don't recollect if I tried that then), an
experienced systemd user should be able to dive into the logs.
--
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System
signature.asc
Description: This is a digitally signed message part
__
Nope. Did not work for me. Based on your feedback, I tried on a 2nd
box, but still the same problem.
Gpaste Shell Extension, Iceweasel etc all complain.
Even evolution complains if I look into the journal logs.
I guess I'll just wait for some time :-)
--
Ritesh Raj Sarraf | http://peopl
in the journal?
Nope. No additional error messages.
BTW, are you guys using kdbus ?
I ask because I'm wondering of such a basic issue having gone
unnoticed.
--
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System
signature.asc
Description
On Tue, 2015-09-22 at 00:53 +0200, Michael Biebl wrote:
> Do you have dbus-user-session installed?
> If not, please install it an re-test.
Hello Michael,
Installing dbus-user-session did not help. I still get the same error
messages.
--
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Package: kdbus-dkms
Version: 0.20150824t110616.0c05fbd-1
Severity: normal
Thanks for packaging kdbus. I'm assuming that you are willing to take
bug reports. If not so, please let me know.
>From what I've read so far, my understanding was that kdbus was a
drop-in replacement over dbus.
When boot
ooted it proper. And provided with the getty login
on the shell.
> At least this works for me.
THanks. With this method, machinectl is able to login into the
container. It still cannot login, if the container was started through
machinectl.
--
Ritesh Raj Sarraf | http://people.debian.org
.
--
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System
signature.asc
Description: This is a digitally signed message part
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.d
or now, I'm going to wait for the new release to land in Debian,
and then explore again.
PS: I booted the same with LXC, and have not run into the issues.
Sometimes, choice is really good. :-)
--
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System
sign
Package: systemd-container
Version: 225-1
Followup-For: Bug #792882
Hello Michael / Martin,
I'm following up on this bug report with the new issue, after the new
systemd package, which includes the new systemd-container package.
So, the initial problem in this bug report was about dependency o
Package: systemd-container
Version: 225-1
Severity: normal
File: /bin/machinectl
This one is an odd behavior. I export my container image, and the same
is not allowed to be imported.
rrs@chutzpah:/var/lib/lxc$ sudo machinectl export-tar fed-test
/var/tmp/fedora-container.tar.gz
Enqueued transf
Package: systemd
Version: 223-2
Followup-For: Bug #719695
Hello,
I am hit by the same problem.
So far, we've shipped a SysV init script /etc/init.d/multipath-tools, whereas
upstream ships the service file as multipathd.service
I haven't read through all the details on this bug report, but I'd
> Not quite sure if [1] is related, but I suggest you look at that
> existing bug report as well. Maybe it contains some hints.
>
>
> Michael
>
> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771675
>
>
> --
> Why is it that all of the instruments seeking intellige
On Monday 06 July 2015 04:33 PM, Michael Biebl wrote:
> Sorry for the typo here, I meant "/run/systemd/system" here, without the
> 'd' suffix.
Oh! Thanks. That did not hit me. But another one did.
"systemctl --non-block"
:-)
--
Ritesh Raj Sarraf | http:/
ctive
Jul 06 16:41:07 learner systemd[1]: Reloaded Laptop Mode Tools.
Jul 06 16:44:41 learner systemd[1]: Reloaded Laptop Mode Tools.
16:48 ♒♒♒ ☺
So now, I'm going to add similar check conditions for the pm-utils hook
and the acpid hook.
--
ut the repetitive invocation, that initially
looked like systemd calling.
Turns out the kernel/udev has changed (or I'd rather say improved) the
way it measures the power_supply subsystem. Now, it is capable on
emitting events, when the charge of the battery changes.
That is what was causing multi
s invoked. Reverting to 220, and the processing/invocation works
back.
Both LMT and systemd upgraded around the same time, and I took it as a
bug in LMT. :-)
Luckily I had another machine with older systemd, and was able to narrow
it down.
For now, I'm downgrading back to 220, and spend
LMT, we background another script, lm-polling-daemon. This
script is backgrounded after we acquire a lock in the main program i.e.
/usr/sbin/laptop_mode, and not released until the polling daemon is killed.
How is systemd/cgroup supposed to handle scripts that background other
scrip
houldn't be done in udev. That would just be a workaround.
And not all device combinations are causing the problem you've mentioned.
--
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System
signature.asc
Description: OpenPGP digital signature
___
; The relevant "trigger on resume" mechanism from udev seems to be:
>> ACTION=="add|remove", SUBSYSTEM=="machinecheck", RUN+="lmt-udev auto
>> force"
>>
>
>
--
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Necessity
remote storage for a reason,
when they want to consolidate everything at a central location.
--
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System
signature.asc
Description: OpenPGP digital signature
___
Pkg-syst
Hence the daemon handling is separated from the iSCSI sessions
that are handled in-kernel.
--
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System
signature.asc
Description: OpenPGP digital signature
___
Control: clone -1 -2
Control: retitle -2 multipath not automounting iscsi devices listed in fstab
On 01/25/2015 08:13 PM, Ritesh Raj Sarraf wrote:
>> Is this on LVM (because of /dev/mapper in the output)? If so, did you
>> configure the VGs in /etc/default/open-iscsi? What does journ
s with higher number of LUNs mapped.
I've still kept the systemd folks in the loop, hopefully they may be
able to shed some light.
--
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Necessity is the mother of invention."
signature.asc
Description: OpenPGP digit
Can you please verify
the same ?
http://youtu.be/q4pOQn3C4q0
Ritesh
--
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Necessity is the mother of invention."
signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintai
On 01/21/2015 02:39 PM, Ritesh Raj Sarraf wrote:
> Thanks Christian. I'm building a setup to verify the same.
I was able to reproduce the problem on my local setup. I've put up a
video just to be sure we are both referring to the same problem.
http://youtu.be/cwcnk00Hwk0
Next, I&#
systemd package, to make it work (better) in lxc, please let us know.
Actually I think this should be reassigned to the lxc package.
Containers are supposed to provide Namespace and Process Isolation. And
in this case, it looks like something is broken.
--
Ritesh Raj Sarraf | http://people.debian.o
Had missed the attachment.
systemd-lxc.bug
Description: Binary data
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Package: systemd
Version: 215-5+b1
Severity: important
In my host, I have systemd-shim installed. systemd is not the init used
to boot, but rather is installed because of the dependencies. The
default init is openrc.
When booting LXC Containers, with systemd as the init (i.e. systemd-sysv
instal
On Wednesday 03 September 2014 06:51 PM, Henrique de Moraes Holschuh wrote:
On Wed, 03 Sep 2014, Ritesh Raj Sarraf wrote:
> >My inclination is to ship both, the systemd service files and the
> >init scripts, in their current form along with whatever
> >limitations each may
On Tuesday 02 September 2014 01:33 PM, Ritesh Raj Sarraf wrote:
Could you elaborate a bit more, why those are needed?
What is upstream doing about this?
The block storage has many components that work closely with one another.
Take an example, root fs on LVM on Multipath on iSCSI.
The flow
o you, in the next upload, I'll apply the
systemd service matching to the init script name.
--
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-m
ings. But not all got covered by udev.
Please see my other email for the problem.
--
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.aliot
someone please shed some more light on Debian bug:
760182
Per the bug report, there is no systemd support in d-i. Which then means
that I need to disable systemd support ?
--
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System
questions, please don't hesitate to ask the
pkg-systemd-maintainers mailing list.
In native init scripts, we did a lot of check before starting and
shutting down the daemon. Things like checking the root device, or
tiggering LVM Volume Group activitation. They were easily done in shel
61 matches
Mail list logo
