Hi.
On Mon, Aug 19, 2019 at 10:08:10PM +0300, Andrei POPESCU wrote:
> On Lu, 19 aug 19, 09:54:08, john doe wrote:
> > Hi Rico, thanks for your answer.
> > On 8/19/2019 9:37 AM, Reco wrote:
> > > On Mon, Aug 19, 2019 at 09:25:56AM +0200, john doe wrote:
> > >>
> > >> Here is the requested
On Lu, 19 aug 19, 09:54:08, john doe wrote:
> Hi Rico, thanks for your answer.
> On 8/19/2019 9:37 AM, Reco wrote:
> > On Mon, Aug 19, 2019 at 09:25:56AM +0200, john doe wrote:
> >>
> >> Here is the requested output from a test server:
> >>
> >> $ apt purge dbus -s
> > <...>
> >> dbus*
Le lundi 19 août 2019 à 10:15 -0400, Greg Wooledge a écrit :
> On Mon, Aug 19, 2019 at 11:41:33AM +0200, Bastien Durel wrote:
> > Ok, there muste have been an error somewhere ...
> >
> > root@corrin-2:~# apt-cache policy systemd-container
> > systemd-container:
> > Installed: (none)
> >
On Mon, Aug 19, 2019 at 11:41:33AM +0200, Bastien Durel wrote:
> Ok, there muste have been an error somewhere ...
>
> root@corrin-2:~# apt-cache policy systemd-container
> systemd-container:
> Installed: (none)
> Candidate: 241-5
> Version table:
> 241-5 500
> 500
On Mon, Aug 19, 2019 at 11:41:33AM +0200, Bastien Durel wrote:
> Le lundi 19 août 2019 à 11:54 +0300, Reco a écrit :
> > Hi.
> >
> > On Mon, Aug 19, 2019 at 10:23:54AM +0200, Bastien Durel wrote:
> > > Le lundi 19 août 2019 à 10:37 +0300, Reco a écrit :
> > > > > $ apt purge dbus -s
> > > >
Le lundi 19 août 2019 à 11:54 +0300, Reco a écrit :
> Hi.
>
> On Mon, Aug 19, 2019 at 10:23:54AM +0200, Bastien Durel wrote:
> > Le lundi 19 août 2019 à 10:37 +0300, Reco a écrit :
> > > > $ apt purge dbus -s
> > > <...>
> > > >dbus* libpam-systemd*
> > >
> > > So, dbus is not needed
Hi.
On Mon, Aug 19, 2019 at 10:23:54AM +0200, Bastien Durel wrote:
> Le lundi 19 août 2019 à 10:37 +0300, Reco a écrit :
> > > $ apt purge dbus -s
> > <...>
> > >dbus* libpam-systemd*
> >
> > So, dbus is not needed there.
>
> Hello. Same here, but with dbus removed, my jobs using
Le lundi 19 août 2019 à 10:37 +0300, Reco a écrit :
> > $ apt purge dbus -s
> <...>
> >dbus* libpam-systemd*
>
> So, dbus is not needed there.
Hello. Same here, but with dbus removed, my jobs using systemd-nspawn
fails with:
Failed to open system bus: Connection refused
So testing your
On Mon, Aug 19, 2019 at 09:54:08AM +0200, john doe wrote:
> >> If things goes well on this server, which is a test server, I'll
> >> consider purging dbus from my production server(s) on which a reboot is
> >> to be avoided.
> >>
> >> Here is the requested output from a test server:
> >>
> >> $
Hi Rico, thanks for your answer.
On 8/19/2019 9:37 AM, Reco wrote:
> Hi.
>
> On Mon, Aug 19, 2019 at 09:25:56AM +0200, john doe wrote:
>> On 8/18/2019 4:59 PM, Reco wrote:
>>> On Sun, Aug 18, 2019 at 04:56:34PM +0200, john doe wrote:
On 8/18/2019 3:19 PM, Brian wrote:
> On Sun 18
Hi.
On Mon, Aug 19, 2019 at 09:25:56AM +0200, john doe wrote:
> On 8/18/2019 4:59 PM, Reco wrote:
> > On Sun, Aug 18, 2019 at 04:56:34PM +0200, john doe wrote:
> >> On 8/18/2019 3:19 PM, Brian wrote:
> >>> On Sun 18 Aug 2019 at 12:17:59 +0200, john doe wrote:
> >>>
> On 8/17/2019
On 8/18/2019 4:59 PM, Reco wrote:
> On Sun, Aug 18, 2019 at 04:56:34PM +0200, john doe wrote:
>> On 8/18/2019 3:19 PM, Brian wrote:
>>> On Sun 18 Aug 2019 at 12:17:59 +0200, john doe wrote:
>>>
On 8/17/2019 8:15 PM, Brian wrote:
> On Tue 13 Aug 2019 at 20:07:49 +0200, john doe wrote:
On Sun, Aug 18, 2019 at 04:56:34PM +0200, john doe wrote:
> On 8/18/2019 3:19 PM, Brian wrote:
> > On Sun 18 Aug 2019 at 12:17:59 +0200, john doe wrote:
> >
> >> On 8/17/2019 8:15 PM, Brian wrote:
> >>> On Tue 13 Aug 2019 at 20:07:49 +0200, john doe wrote:
> >>>
> Hi,
>
> While
On 8/18/2019 3:19 PM, Brian wrote:
> On Sun 18 Aug 2019 at 12:17:59 +0200, john doe wrote:
>
>> On 8/17/2019 8:15 PM, Brian wrote:
>>> On Tue 13 Aug 2019 at 20:07:49 +0200, john doe wrote:
>>>
Hi,
While upgrading the dbus deamon, I get the following:
"A reboot is required
On Sun 18 Aug 2019 at 12:17:59 +0200, john doe wrote:
> On 8/17/2019 8:15 PM, Brian wrote:
> > On Tue 13 Aug 2019 at 20:07:49 +0200, john doe wrote:
> >
> >> Hi,
> >>
> >> While upgrading the dbus deamon, I get the following:
> >>
> >> "A reboot is required to replace the running dbus-daemon.
>
On 8/17/2019 8:15 PM, Brian wrote:
> On Tue 13 Aug 2019 at 20:07:49 +0200, john doe wrote:
>
>> Hi,
>>
>> While upgrading the dbus deamon, I get the following:
>>
>> "A reboot is required to replace the running dbus-daemon.
>> Please reboot the system when convenient."
>>
>>
>> I have no plan to
On Tue 13 Aug 2019 at 20:07:49 +0200, john doe wrote:
> Hi,
>
> While upgrading the dbus deamon, I get the following:
>
> "A reboot is required to replace the running dbus-daemon.
> Please reboot the system when convenient."
>
>
> I have no plan to reboot that server, what are the pros and
On Sat 17 Aug 2019 at 12:59:16 +0300, Reco wrote:
> On Fri, Aug 16, 2019 at 11:23:48PM +0100, Brian wrote:
> >
> > ipptool depends on libcups2.
>
> Which does not make it require CUPS on the other side - [2].
> And note - a conventional RFC1918 IP is used there. No "discovery"
> involved.
On Fri, Aug 16, 2019 at 11:23:48PM +0100, Brian wrote:
> On Fri 16 Aug 2019 at 22:39:09 +0300, Reco wrote:
>
> > On Fri, Aug 16, 2019 at 07:14:58PM +0100, Brian wrote:
> > > On Fri 16 Aug 2019 at 09:51:15 +0300, Reco wrote:
> > >
> > > > On Thu, Aug 15, 2019 at 08:47:34PM +0100, Brian wrote:
> >
On Fri 16 Aug 2019 at 22:39:09 +0300, Reco wrote:
> On Fri, Aug 16, 2019 at 07:14:58PM +0100, Brian wrote:
> > On Fri 16 Aug 2019 at 09:51:15 +0300, Reco wrote:
> >
> > > On Thu, Aug 15, 2019 at 08:47:34PM +0100, Brian wrote:
> > >
> > > > Nowadays that system often relies on printer/print
On Fri, Aug 16, 2019 at 07:14:58PM +0100, Brian wrote:
> On Fri 16 Aug 2019 at 09:51:15 +0300, Reco wrote:
>
> > On Thu, Aug 15, 2019 at 08:47:34PM +0100, Brian wrote:
> >
> > > Nowadays that system often relies on printer/print queue Bonjour
> > > broadcasts.
> >
> > And that is called
On Fri 16 Aug 2019 at 09:51:15 +0300, Reco wrote:
> On Thu, Aug 15, 2019 at 08:47:34PM +0100, Brian wrote:
>
> > Nowadays that system often relies on printer/print queue Bonjour
> > broadcasts.
>
> And that is called "jumping to conclusions".
> Printing itself haven't changed a bit for last 15
On Fri 16 Aug 2019 at 08:39:43 -0400, Greg Wooledge wrote:
> On Fri, Aug 16, 2019 at 09:53:20AM +0300, Reco wrote:
> > On Thu, Aug 15, 2019 at 10:36:57PM +0100, Brian wrote:
> > > On Thu 15 Aug 2019 at 22:15:59 +0100, Tixy wrote:
> > >
> > > > On Thu, 2019-08-15 at 19:41 +0100, Brian wrote:
> >
On Fri, Aug 16, 2019 at 09:53:20AM +0300, Reco wrote:
> On Thu, Aug 15, 2019 at 10:36:57PM +0100, Brian wrote:
> > On Thu 15 Aug 2019 at 22:15:59 +0100, Tixy wrote:
> >
> > > On Thu, 2019-08-15 at 19:41 +0100, Brian wrote:
> > > > The fact remains that dbus is not a DE only package. How did
On Fri, Aug 16, 2019 at 12:46:17PM +0100, Brian wrote:
> On Fri 16 Aug 2019 at 13:21:11 +0200, to...@tuxteam.de wrote:
> > I'm getting old, so this piqued somewhat my vanity. I double-checked:
[...]
> It's a fair cop!
:-)
Cheers
-- t
signature.asc
Description: Digital signature
On Fri 16 Aug 2019 at 13:21:11 +0200, to...@tuxteam.de wrote:
> On Fri, Aug 16, 2019 at 12:15:18PM +0100, Brian wrote:
> > On Fri 16 Aug 2019 at 13:01:10 +0200, to...@tuxteam.de wrote:
>
> [...]
>
> > > No, I didn't get that idea -- wasn't it you who reminded us that CUPS
> > > doesn't require
On Fri, Aug 16, 2019 at 12:15:18PM +0100, Brian wrote:
> On Fri 16 Aug 2019 at 13:01:10 +0200, to...@tuxteam.de wrote:
[...]
> > No, I didn't get that idea -- wasn't it you who reminded us that CUPS
> > doesn't require avahi-daemon?
>
> I don't think so; not in this thread anyway.
I'm getting
On Fri 16 Aug 2019 at 13:01:10 +0200, to...@tuxteam.de wrote:
> On Fri, Aug 16, 2019 at 11:54:50AM +0100, Brian wrote:
> > On Fri 16 Aug 2019 at 11:48:30 +0100, Brian wrote:
> >
> > > On my print server with buster:
> > >
> > > root@futro:~# apt purge dbus
> > > Reading package lists...
On Fri, Aug 16, 2019 at 11:54:50AM +0100, Brian wrote:
> On Fri 16 Aug 2019 at 11:48:30 +0100, Brian wrote:
>
> > On my print server with buster:
> >
> > root@futro:~# apt purge dbus
> > Reading package lists... Done
> > Building dependency tree
> > Reading state
On Fri, Aug 16, 2019 at 11:48:30AM +0100, Brian wrote:
> On Fri 16 Aug 2019 at 12:24:14 +0200, to...@tuxteam.de wrote:
>
> > On Fri, Aug 16, 2019 at 11:03:41AM +0100, Brian wrote:
> >
> > [...]
> >
> > > https://www.freedesktop.org/wiki/Software/dbus/
> > ^^^
> >
> > ;-)
On Fri 16 Aug 2019 at 11:48:30 +0100, Brian wrote:
> On my print server with buster:
>
> root@futro:~# apt purge dbus
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> The following packages will be REMOVED:
> dbus*
On Fri 16 Aug 2019 at 12:24:14 +0200, to...@tuxteam.de wrote:
> On Fri, Aug 16, 2019 at 11:03:41AM +0100, Brian wrote:
>
> [...]
>
> > https://www.freedesktop.org/wiki/Software/dbus/
> ^^^
>
> ;-)
DE - Desktop *Environment*. A case of selective censorship? :)
> [...]
>
On Fri, Aug 16, 2019 at 11:03:41AM +0100, Brian wrote:
[...]
> https://www.freedesktop.org/wiki/Software/dbus/
^^^
;-)
[...]
> As Reco said:
>
> > If you don't need it - just uninstall it.
>
> What do you get for 'apt purge dbus'?
Not the OP, but here's mine:
On Fri, Aug 16, 2019 at 11:06:43AM +0200, john doe wrote:
[...]
> Okay, as far as I understand it, depends means that it will be pulled as
> an dependency but not that it is required for it to work properly.
> What I'm starting to realise is that to much dependencies are pulled to
> implement
On Fri 16 Aug 2019 at 09:51:15 +0300, Reco wrote:
> On Thu, Aug 15, 2019 at 08:47:34PM +0100, Brian wrote:
> > On Thu 15 Aug 2019 at 21:05:10 +0200, to...@tuxteam.de wrote:
> >
> > > On Thu, Aug 15, 2019 at 07:41:06PM +0100, Brian wrote:
> > >
> > > > I wouldn't try to dissuade anyone from using
On Fri 16 Aug 2019 at 11:06:43 +0200, john doe wrote:
> On 8/15/2019 6:52 PM, Brian wrote:
> > On Wed 14 Aug 2019 at 07:36:21 +0200, john doe wrote:
> >
> >> Hi Rico, and thanks for your answer.
> >>
> >> On 8/13/2019 9:25 PM, Reco wrote:
> >>> On Tue, Aug 13, 2019 at 08:07:49PM +0200, john doe
On 8/15/2019 6:52 PM, Brian wrote:
> On Wed 14 Aug 2019 at 07:36:21 +0200, john doe wrote:
>
>> Hi Rico, and thanks for your answer.
>>
>> On 8/13/2019 9:25 PM, Reco wrote:
>>> On Tue, Aug 13, 2019 at 08:07:49PM +0200, john doe wrote:
I have no plan to reboot that server, what are the pros
On Thu, Aug 15, 2019 at 10:36:57PM +0100, Brian wrote:
> On Thu 15 Aug 2019 at 22:15:59 +0100, Tixy wrote:
>
> > On Thu, 2019-08-15 at 19:41 +0100, Brian wrote:
> > > The fact remains that dbus is not a DE only package. How did anyone
> > > get the idea it was?
> >
> > Perhaps because D-Bus
On Thu, Aug 15, 2019 at 08:47:34PM +0100, Brian wrote:
> On Thu 15 Aug 2019 at 21:05:10 +0200, to...@tuxteam.de wrote:
>
> > On Thu, Aug 15, 2019 at 07:41:06PM +0100, Brian wrote:
> >
> > > I wouldn't try to dissuade anyone from using last century's
> > > technology
> > > if they have their heart
On Thu 15 Aug 2019 at 22:15:59 +0100, Tixy wrote:
> On Thu, 2019-08-15 at 19:41 +0100, Brian wrote:
> > The fact remains that dbus is not a DE only package. How did anyone
> > get the idea it was?
>
> Perhaps because D-Bus stands for Desktop Bus and according to Wikipedia
> [1]
>
>D-Bus was
On Thu, 2019-08-15 at 19:41 +0100, Brian wrote:
> The fact remains that dbus is not a DE only package. How did anyone
> get the idea it was?
Perhaps because D-Bus stands for Desktop Bus and according to Wikipedia
[1]
D-Bus was developed as part of the freedesktop.org project [...] to
On Thu 15 Aug 2019 at 21:05:10 +0200, to...@tuxteam.de wrote:
> On Thu, Aug 15, 2019 at 07:41:06PM +0100, Brian wrote:
>
> > I wouldn't try to dissuade anyone from using last century's technology
> > if they have their heart set on it [...]
>
> C'mon. You /know/ you're talking nonsense. Old is
On Thu, Aug 15, 2019 at 07:41:06PM +0100, Brian wrote:
> I wouldn't try to dissuade anyone from using last century's technology
> if they have their heart set on it [...]
C'mon. You /know/ you're talking nonsense. Old is old, and new is new.
Beyond that...
BTW I still use TeX, so... 1980s.
On Thu 15 Aug 2019 at 19:14:19 +0200, to...@tuxteam.de wrote:
> On Thu, Aug 15, 2019 at 05:52:39PM +0100, Brian wrote:
>
> [...]
>
> > Those setting up a print server would likely not see a corner case here.
>
> CUPS depends on avahi depends somehow on dbus. Try some day lprng,
> works a charm
On Thu 15 Aug 2019 at 19:14:19 +0200, to...@tuxteam.de wrote:
> On Thu, Aug 15, 2019 at 05:52:39PM +0100, Brian wrote:
>
> [...]
>
> > Those setting up a print server would likely not see a corner case here.
>
> CUPS depends on avahi depends somehow on dbus. Try some day lprng,
> works a charm
On Thu, Aug 15, 2019 at 05:52:39PM +0100, Brian wrote:
[...]
> Those setting up a print server would likely not see a corner case here.
CUPS depends on avahi depends somehow on dbus. Try some day lprng,
works a charm :-)
Cheers
-- t
signature.asc
Description: Digital signature
On Wed 14 Aug 2019 at 07:36:21 +0200, john doe wrote:
> Hi Rico, and thanks for your answer.
>
> On 8/13/2019 9:25 PM, Reco wrote:
> > On Tue, Aug 13, 2019 at 08:07:49PM +0200, john doe wrote:
> >> I have no plan to reboot that server, what are the pros and cons of not
> >> doing that
> >
> >
On 2019-08-14, Reco wrote:
> Hi.
>
> On Wed, Aug 14, 2019 at 08:58:56AM +0200, Sven Hartge wrote:
>> Reco wrote:
>>
>> > 1) libpam-systemd, loginctl and friends.
>> > Useful for a workstation, useless for a server.
>>
>> I wouldn't go this far. libpam-systemd and loginctl can be useful
Hi.
On Wed, Aug 14, 2019 at 08:58:56AM +0200, Sven Hartge wrote:
> Reco wrote:
>
> > 1) libpam-systemd, loginctl and friends.
> > Useful for a workstation, useless for a server.
>
> I wouldn't go this far. libpam-systemd and loginctl can be useful on a
> server, depening on its job and
Reco wrote:
> 1) libpam-systemd, loginctl and friends.
> Useful for a workstation, useless for a server.
I wouldn't go this far. libpam-systemd and loginctl can be useful on a
server, depening on its job and role.
Grüße,
Sven.
--
Sigmentation fault. Core dumped.
Hi.
On Wed, Aug 14, 2019 at 07:36:21AM +0200, john doe wrote:
> > dbus is not mandatory and is redundant for typical server software.
> > If you don't need it - just uninstall it. Simple as that.
>
> okay, dbus is only required when a DE (Gnome,Mate, ...) is present.
> If I'm correct,
Hi Rico, and thanks for your answer.
On 8/13/2019 9:25 PM, Reco wrote:
> On Tue, Aug 13, 2019 at 08:07:49PM +0200, john doe wrote:
>> I have no plan to reboot that server, what are the pros and cons of not
>> doing that
>
> Pro: keeping uptime
> Con: keeping previous, possibly buggy, version for
On Tue, Aug 13, 2019 at 08:07:49PM +0200, john doe wrote:
> I have no plan to reboot that server, what are the pros and cons of not
> doing that
Pro: keeping uptime
Con: keeping previous, possibly buggy, version for dbus running.
> or how can I avoid rebooting altogether?
dbus is not mandatory
I still have this problem...
Renaming all dot-files in $HOME I can only login if I use icewm as window
manager. All the other will fail. With icewm I can run some programs, while
attempting to open others will log me out. Again, this is for all users.
Programs that will crash the window manager
On 09/10/2013 02:27 PM, Ionel Mugurel Ciobîcă wrote:
I still have this problem...
Renaming all dot-files in $HOME I can only login if I use icewm as
window manager. All the other will fail. With icewm I can run some
programs, while attempting to open others will log me out. Again, this
is
Hi
I had this issue on time if I'm remember well, I had to remove the
.config directory
I think.
Regards
Diog.
On 08/28/2013 06:52 PM, Ionel Mugurel Ciobîcă wrote:
Hi,
After squeeze = wheezy upgrade I can't login at kdm. After I type
the password I am logged out. I try several wm, it is
Thank you, renaming .config doesn't change anything. The folder is not
even re-created. I was not aware of the existance of this .config
folder. There are not new files in there...
Ionel
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble?
DBus isn't a problem per se, it just can cause issues, when implemented
without thinking about the needs of all users?
Right but it's actually much worse than that. Take mozilla firefox even
which may or may not have been changed due to me bringing it up on the
dev-security list. Without dbus
Le 13/04/2013 19:39, Kevin Chadwick a écrit :
DBus isn't a problem per se, it just can cause issues, when implemented
without thinking about the needs of all users?
Right but it's actually much worse than that. Take mozilla firefox even
which may or may not have been changed due to me bringing
On Sat, Apr 13, 2013 at 10:39 AM, Kevin Chadwick ma1l1i...@yahoo.co.uk wrote:
DBus isn't a problem per se, it just can cause issues, when implemented
without thinking about the needs of all users?
Right but it's actually much worse than that. Take mozilla firefox even
which may or may not
On Sat, 13 Apr 2013 10:34:36 -0700
Kelly Clowers wrote:
DBus isn't a problem per se, it just can cause issues, when implemented
without thinking about the needs of all users?
Right but it's actually much worse than that. Take mozilla firefox even
which may or may not have been changed
On Sat, Apr 13, 2013 at 5:02 PM, Kevin Chadwick ma1l1i...@yahoo.co.uk wrote:
On Sat, 13 Apr 2013 10:34:36 -0700
Kelly Clowers wrote:
DBus isn't a problem per se, it just can cause issues, when implemented
without thinking about the needs of all users?
Right but it's actually much worse
On Tue, 2013-04-09 at 19:29 +0200, Ralf Mardorf wrote:
On Tue, 2013-04-09 at 07:21 -1000, Joel Roth wrote:
Ralf Mardorf wrote:
dbus often is a PITA!
Do you have experience with dbus's predecessors, such as
CORBA?
No. I guess a predecessor won't help, if applications depend on dbus,
Le 09/04/2013 19:29, Ralf Mardorf a écrit :
On Tue, 2013-04-09 at 07:21 -1000, Joel Roth wrote:
Ralf Mardorf wrote:
dbus often is a PITA!
Do you have experience with dbus's predecessors, such as
CORBA?
No. I guess a predecessor won't help, if applications depend on dbus,
such as
On Tue, 2013-04-09 at 19:33 +0200, Erwan David wrote:
WHen reporting erreor messages when emacs-gtk from a ssh -X session, I
was told that it's normal that it won't work since it uses dbus. Since
then I have a bad feeling with dbus dependencies which seem to reduce
the capabilities of
Ralf Mardorf wrote:
On Tue, 2013-04-09 at 19:29 +0200, Ralf Mardorf wrote:
On Tue, 2013-04-09 at 07:21 -1000, Joel Roth wrote:
Ralf Mardorf wrote:
dbus often is a PITA!
Do you have experience with dbus's predecessors, such as
CORBA?
No. I guess a predecessor won't help, if
On Tue, Apr 9, 2013 at 11:04 AM, Joel Roth jo...@pobox.com wrote:
Ralf Mardorf wrote:
On Tue, 2013-04-09 at 19:29 +0200, Ralf Mardorf wrote:
On Tue, 2013-04-09 at 07:21 -1000, Joel Roth wrote:
Ralf Mardorf wrote:
dbus often is a PITA!
Do you have experience with dbus's
On Tue, 2013-04-09 at 11:47 -0700, Kelly Clowers wrote:
D-Bus is good overall... There could definitely be improvements in
remote connections though. I think there are workarounds... [snip]
DBus isn't an issue for applications you'll use with a desktop
environment, when those apps should
OT regarding to dbus:
I wrote:
For other
stuff package maintainers have to do a hard job, somebody seemingly does
extract udev from systemd for Debian. I'm on a distro that follows
upstream and there were many issues when they switched to systemd.
Ralf Mardorf wrote:
DBus isn't an issue for applications you'll use with a desktop
environment, when those apps should communicate with each other, but it
could become an issue, if apps should run on other setups (too) and it's
an issue if simple commands that worked before, then won't work
On Tue, Apr 09, 2013 at 09:20:15PM +0200, Ralf Mardorf wrote:
OT regarding to dbus:
I wrote:
For other
stuff package maintainers have to do a hard job, somebody seemingly does
extract udev from systemd for Debian. I'm on a distro that follows
upstream and there were many issues when
D-Bus is good overall...
The good thing about standard IPC was that you would have to develop
the protocol etc.. which means if your app used it.
1./ You needed to use it otherwise you wouldn't.
2./ You made an app specific mechanism (very good if your good but
could be bad, the latter is what
Too funny, under the jokes is one, asking to merge it with dbus.
Udev and systemd to merge
Posted Apr 3, 2012 22:31 UTC
Next step is of course to integrate D-Bus in systemd, no?
On Tue, 2013-04-09 at 09:32 -1000, Joel Roth wrote:
https://lwn.net/Articles/490413/
I don't know if systemd and
On Tue, 2013-04-09 at 22:59 +0100, Kevin Chadwick wrote:
What I really don't get though is why there are so many
easily avoidable hard dependencies.
+1
We can see what projects come with the most hilarious dependencies and
that's why we should avoid EMONG, or similar, have forgotten the name.
On 2012-11-20, at 9:37 AM, Michael Biebl bi...@debian.org wrote:
org.freedesktop.UPower provided by upower
http://upower.freedesktop.org/
http://upower.freedesktop.org/docs/
Thanks, this works now.
http://www.but-i-digress.ca/suspend-on-lid-close-debian-squeeze.html
--
To UNSUBSCRIBE,
On 20.11.2012 14:59, Michael P. Soulier wrote:
Hi,
I had an old python script for monitoring my laptop lid with dbus, and then
suspending when it was closed. It doesn't work now because the dbus namespace
on debian seems to have changed.
dbus.exceptions.DBusException:
On Fri, 13 Apr 2012 10:49:28 +0200
admini adm...@freeatome.com wrote:
la question est: le DBUS est-il vraiment nécessaire sur un serveur
(VM) qui ne démarre que des bases et des applis java?
Désinstalle les packages D-Bus, tu verras bien s'il-y-a des
dépendances gênantes ou non.
--
--
On Fri, 13 Apr 2012 13:35:44 +0200, Bzzz lazyvi...@gmx.com wrote:
On Fri, 13 Apr 2012 10:49:28 +0200
admini adm...@freeatome.com wrote:
la question est: le DBUS est-il vraiment nécessaire sur un serveur
(VM) qui ne démarre que des bases et des applis java?
Désinstalle les packages D-Bus,
On Fri, 13 Apr 2012 14:05:56 +0200
admini adm...@freeatome.com wrote:
je vais le rebasculer sur l'autre vlan pour faire un test. je ne crois
pas que ce soit très très genant de ne pas avoir dbus et avahi.
Pas vraiment, dbus est un bus messager avahi == bonjour =
découverte auto des services
Le vendredi 13 avril 2012 à 14:05:56, admini a écrit :
[…]
d'ailleurs, on pourrait m'expliquer un peu à
quoi sert dbus? d'après wikipédia, ce serait un service
permeettant la communication entre services, avec un système
de cannaux.
mais concrètement, qui s'en servent?
`apt-cache rdepends
On Fri, 13 Apr 2012 14:25:15 +0200, Sylvain L. Sauvage
sylvain.l.sauv...@free.fr wrote:
Le vendredi 13 avril 2012 à 14:05:56, admini a écrit :
[…]
d'ailleurs, on pourrait m'expliquer un peu à
quoi sert dbus? d'après wikipédia, ce serait un service
permeettant la communication entre services,
First of all, it is helpful to know if you are running (an up-to-date)
squeeze, wheezy or sid system.
On 01.12.2011 15:49, lina wrote:
(it's related to former thread, but also different)
Here the problem,
gdm3 restart
showed me Could not connect to system bus: failed to connect to
On Fri, Dec 2, 2011 at 2:33 AM, Michael Biebl bi...@debian.org wrote:
First of all, it is helpful to know if you are running (an up-to-date)
squeeze, wheezy or sid system.
On 01.12.2011 15:49, lina wrote:
(it's related to former thread, but also different)
Here the problem,
gdm3 restart
Sáb, 11062011, Gunther Furtado disse:
Olá lista,
Esta versão(1.5.2-2) do dbus fez o wicd parar de funcionar por aqui.
Estou avisando por que ainda não deu tempo de reportar o bug. Reverter
para a versão sid (1.4.10-2) resolveu o problema.
Na versão experimental mais recente (1.5.4-2) o
On Sat, Jul 26, 2008 at 22:11:34 +0200, Marko Randjelovic wrote:
I setup i386 etch chroot on amd64 etch using debootstrap and installed
build-essential with no problem. I need dbus to satisfy buld-dep for pidgin.
But
threre is problem in configure step.
[...]
Setting up dbus
David Baron:
Dbus is running in the 111 crontab group!
Hal is running in the 127 boinc group!
Are these number reserved for these?
Debian uses the UID range from (I think) 500-999 for system users (users
which don't belong to a person, but are used by daemons provided by
specific packages).
David Baron [EMAIL PROTECTED] writes:
Dbus is running in the 111 crontab group!
Hal is running in the 127 boinc Are!
Note that ps, by default, displays process *users*, not groups. For
dbus and hal, the correct users are messagebus and haldaemon.
Since these names are unusually long, ps will
On Sat, 28 Apr 2007 01:07:20 +0100
somethin2cool [EMAIL PROTECTED] wrote:
debian:/home/dave# thunar
Thunar: Failed to connect to the D-BUS session bus: Did not receive a
reply. Possible causes include: the remote application did not send a
reply, the message bus security policy blocked the
On 4/28/07, somethin2cool [EMAIL PROTECTED] wrote:
debian:/home/dave# thunar
Thunar: Failed to connect to the D-BUS session bus: Did not receive a
reply. Possible causes include: the remote application did not send a
reply, the message bus security policy blocked the reply, the reply
timeout
Werner Zacherl wrote:
Am Mittwoch, 8. November 2006 17:59 schrieb Andre Massing:
Werner Zacherl wrote:
Läuft den hald?
Ja, schon, oder fehlt evt. ein Unterdämon?
Wie sieht dies bei dir denn aus?
ps -e |grep hal
32: 2942 ?00:00:05 hald
33: 2943 ?00:00:00 hald-runner
34:
B_Kloss wrote:
Viele Grüße,
Andre
Hallo,
Hi,
bei mir läuft ETCH mit KDE 3.5.5 und mein Problem war folgendes:
USB-Stick eingesteckt und der Automounter meldet sich in KDE.
Das Problem bei mir besteht schon darin, dass sich dieser bei mir nicht
meldet. Irgendwie bekommt KDE das
Am Mittwoch, 8. November 2006 11:03 schrieb Andre Massing:
B_Kloss wrote:
Viele Grüße,
Andre
Ich denke, dass wird bei mir leider das Problem nicht lösen.
Gruppenrechtlich ist soweit ich das sehe alles okay:
uid=1000(andre) gid=1000(andre)
Werner Zacherl wrote:
kenne mich leider selber nicht intensive aus, aber bei mir geht es mit
den gleichen Versionen, die du installiert hast.
Sprich, es wird zwar kein Icon angelegt, aber KDE frägt brav wie es
reagieren soll Fenster oder sonstwas.
Das wünschte ich mir auch... :-)
Läuft
Am Mittwoch, 8. November 2006 17:59 schrieb Andre Massing:
Werner Zacherl wrote:
Läuft den hald?
Ja, schon, oder fehlt evt. ein Unterdämon?
Wie sieht dies bei dir denn aus?
ps -e |grep hal
32: 2942 ?00:00:05 hald
33: 2943 ?00:00:00 hald-runner
34: 2949 ?
Am Dienstag, 7. November 2006 10:31 schrieb Andre Massing:
Liebe Debianer,
seit einiger Zeit plagt mich (mal wieder) die Erkennung von USB-Sticks.
Sowohl unter Gnome 2.14 als auch unter KDE 3.5.5 wird das Einpluggen eines
USB-Sticks im *laufenden* Betrieb nicht mehr mit dem Anlegen eines
Kelly Clowers [EMAIL PROTECTED] wrote:
| I have something like this in my ~/.bash_profile
| (because I start X manually, and I want dbus on before X starts ):
|
| if test -z $DBUS_SESSION_BUS_ADDRESS ; then
| ## if not found, launch a new one
| eval $(dbus-launch --sh-syntax)
|
Kelly Clowers [EMAIL PROTECTED] wrote:
| I have something like this in my ~/.bash_profile
| (because I start X manually, and I want dbus on before X starts ):
|
| if test -z $DBUS_SESSION_BUS_ADDRESS ; then
| ## if not found, launch a new one
| eval $(dbus-launch --sh-syntax)
|
On 11/5/06, Jim McCloskey [EMAIL PROTECTED] wrote:
Kelly Clowers [EMAIL PROTECTED] wrote:
| I have something like this in my ~/.bash_profile
| (because I start X manually, and I want dbus on before X starts ):
|
| if test -z $DBUS_SESSION_BUS_ADDRESS ; then
| ## if not found, launch a new
On 11/4/06, Jim McCloskey [EMAIL PROTECTED] wrote:
Following a recent upgrade (sorry, I can't be more precise), I'm
getting the dbus error:
Unable to determine the address of the message bus
from a number of applications at start-up, including at least:
f-spot (which fails to start as a
Le 26.01.2006 14:01:12, Nicolas Roudninski a écrit :
Bonjour à tous,
Tout est dans le titre...
Quelqu'un peut-il me dire quelles différences il y a entre dbus et
dbus-1 ? Chez moi dbus-1 est installé. Y'a-t-il un avantage à passer à
dbus ?
Il n'y a pas d'avantage particulier à passer de l'un
1 - 100 of 105 matches
Mail list logo
