I'm pretty sure you can bind mount /proc, /sys, /dev, /run, chroot and
then update-initramfs to regen.
Thanks Tim. You make it sound so simple.
I searched for "chroot to mounted disk to update initramfs" and found
several detailed descriptions of the process.
https://forums.debian.net/viewtop
I'm pretty sure you can bind mount /proc, /sys, /dev, /run, chroot and
then update-initramfs to regen.
Thanks Tim. You make it sound so simple.
I searched for "chroot to mounted disk to update initramfs" and found
several detailed descriptions of the process.
https://forums.debian.net/viewto
On Thu, 23 Nov 2023, Andy Dorman wrote:
I have not yet figured out how to fix our two broken servers since we can't
boot them to update them. Since we have several identical running servers
and can mount and manipulate the file system of the dead servers, is it
possible to just copy a good in
On Thu, Nov 23, 2023 at 4:09 PM Andy Dorman wrote:
>
> I have continued to research this and I think I found the problem.
>
> I also think the dbus update timing mentioned in the subject is entirely
> coincidental. I hope I haven't caused any unnecessary excitement or work
I have continued to research this and I think I found the problem.
I also think the dbus update timing mentioned in the subject is entirely
coincidental. I hope I haven't caused any unnecessary excitement or work
for anyone in the dbus package team. My apologies if I did.
A few months
This may actually be a usrmerge problem, both usrmerge and usr-is-merged
(>= 38~) are installed). But I do not know enough about how firmware
controllers are loaded during boot to determine which package, dbus or
usrmerge, I should submit a bug report to.
We have multiple old (14+ years) T
opens Thunar, but I want it to open Caja
>which I use as default file browser.
>
>I have already set it where I have found it in settings, as in
>the "default programs" dialog, and other places, but it seems like
>Firefox uses dbus to get which file browser to use.
>
>Wher
ing "open containing folder" in
>> the "downloaded files" list, opens Thunar, but I want it to open Caja
>> which I use as default file browser.
>>
>> I have already set it where I have found it in settings, as in
>> the "default programs&q
opens Thunar, but I want it to open Caja
> which I use as default file browser.
>
> I have already set it where I have found it in settings, as in
> the "default programs" dialog, and other places, but it seems like
> Firefox uses dbus to get which file browser to use.
&
ve already set it where I have found it in settings, as in
the "default programs" dialog, and other places, but it seems like
Firefox uses dbus to get which file browser to use.
Where do I set dbus and Firefox to use Caja instead of Thunar?
-- Andreas Rönnquist
mailingli...@gusnan.se
andr
gt; When I log out then and restart LXDE or LXQT, everything is working fine.
Please specify if this is buster or bullseye.
> So I believe, this may just be a timing problem with dbus.
Why do you believe this?
> This behaviour appears on my EEEPC (which is slow), but also on my
> Acer
believe, this may just be a timing problem with dbus. This behaviour
appears on my
EEEPC (which is slow), but also on my Acer Notebook (which is fast).
I checked the logs, and I can see in the logs, that there is a difference
between both
starts. You can see, there is a timeout. Here is an
Hi my Debian server will not boot, in recover mode I get :-
Jun 12 15:21:11 dhcpsrv systemd[1]: Condition check resulted in getty on
tty2-tty6 if dbus and logind are not available being skipped.
dhcpsrv dbus-daemon[4427]: Failed to start message bus: No socket received.
ls: cannot access '
On 2019-10-21, Jean-Philippe MENGUAL wrote:
> Hi,
>
> I realize I reproduce the bahivior described here. I dont know if
> debian-accessibility was Cc but I do it. Let's what they say, but I
> guess we should report a bug against at-spi itself.
>
> The problem here is, indeed: at shutdown of Mate,
Hi,
I realize I reproduce the bahivior described here. I dont know if
debian-accessibility was Cc but I do it. Let's what they say, but I
guess we should report a bug against at-spi itself.
The problem here is, indeed: at shutdown of Mate, "at-spi-bus-launcher
does not respond" and I can override
give that a try.
> I am not running Orca, but I have the same issue.
I poked around a little more and noticed that at-spi-dbus-launcher gets
started for both MATE and Xfce. But there's no delay logging out from
Xfce.
So maybe this is worth filing a bug against mate-session-manager?
mike
On 10/19/2019 5:54 PM, Cindy Sue Causey wrote:
On 10/19/19, Mike Kupfer wrote:
I have a system running bullseye. When I try to log out, or shut down,
from MATE, I invariably get a popup that tells me that
at-spi-dbus-launcher is not responding. I click on "logout anyway", and
On 10/19/19, Mike Kupfer wrote:
> I have a system running bullseye. When I try to log out, or shut down,
> from MATE, I invariably get a popup that tells me that
> at-spi-dbus-launcher is not responding. I click on "logout anyway", and
> the system does eventually log
I have a system running bullseye. When I try to log out, or shut down,
from MATE, I invariably get a popup that tells me that
at-spi-dbus-launcher is not responding. I click on "logout anyway", and
the system does eventually log me out, but there's a delay.
I tried disabling th
gt;>
> > >> Here is the requested output from a test server:
> > >>
> > >> $ apt purge dbus -s
> > > <...>
> > >> dbus* libpam-systemd*
> > >
> > > So, dbus is not needed there.
> > >
> >
>
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:
> >>
> >> $
found matching pattern /usr/bin/systemd-nspawn
>
> Are you saying that you installed systemd-nspawn from something other
> than a Debian package, *and* you put it in the /usr/bin directory?
> That's a really poor decision -- local add-ons should be in
> /usr/local
> or in /opt.
>
ackage, *and* you put it in the /usr/bin directory?
That's a really poor decision -- local add-ons should be in /usr/local
or in /opt.
Also, it appears you were relying on various dependenent packages, like
dbus, without knowing it, since the thing that was actually using them
wasn'
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 :
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
> > > <...>
> > > >dbu
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.
>
> Hel
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: Connecti
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.
> >>
> >&g
: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:
>>>>>>>>
>>
e:
> >>>
> >>>> On 8/17/2019 8:15 PM, Brian wrote:
> >>>>> On Tue 13 Aug 2019 at 20:07:49 +0200, john doe wrote:
> >>>>>>
> >>>>>> While upgrading the dbus deamon, I get the following:
> >
; 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
> >>>
> >>>> 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
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
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:
> >>
> >&
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 syst
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 rebo
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.
Anyth
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 queue
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 "jumping
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 y
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
> &
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 db
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
ed us that CUPS
> > > doesn't require avahi-daemon?
> >
> > I don't think so; not in this thread anyway.
>
> I'm getting old, so this piqued somewhat my vanity. I double-checked:
>
> In Message-ID: <15082019194357.c7ba6d840...@desktop.copernicus.
; not in this thread anyway.
I'm getting old, so this piqued somewhat my vanity. I double-checked:
In Message-ID: <15082019194357.c7ba6d840...@desktop.copernicus.org.uk>
[me]
>> CUPS depends on avahi depends somehow on dbus. Try some day lprng,
>> works a charm :-)
[you]
&
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
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 dependen
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:/
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
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 c
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
to
> implement lots of feature that is not always necessery.
That very much depends on the application: some (mis?) use dbus as a
dynamic linking facility which could be as well served by shared objects.
Kind of a Rube Goldberg way of doing dynamic linking -- but that's my
opinion, you
's representation (be
> it PCL or something else), and feeds it to the printer. By utilizing
> unicasts of course.
> A user can discover a print server via mDNS multicasts (*not*
> broadcasts). Or a user can be told a location of such print server.
>
> avahi is useful for discovery of CUPS, and that's about it.
Printer discovery is an important aspect of a modern printing system.
If a user or institution can get by without it, fine. If not, dbus is
required.
--
Brian.
gt; 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,
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?
>>>
&g
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?
aven't changed a bit for last 15 years - a print server
takes user's PS or PDF, mangles it to fit printer's representation (be
it PCL or something else), and feeds it to the printer. By utilizing
unicasts of course.
A user can discover a print server via mDNS multicasts (*not*
bro
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
&g
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 [.
er/print queue Bonjour broadcasts. Not only that, but printers have
changed considerable since lprng was conceived and it is completely
unable to handle them. Tex, on the other hand, is still able to handle
document processing.
dbus "...is redundant for typical server software" appears
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. Works
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 da
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 da
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
s 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 and is redundant for typical server software.
> &
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 on
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 pr
sibly buggy, version for dbus running.
>
>> or how can I avoid rebooting altogether?
>
> 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, .
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
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 cons of not
doing that or how can I avoid rebooting altogether
Hello,
I'm running on Buster installed from testing.
I try to flush my DNS cash but I have this message.
systemd-resolve --status
Failed to get global data: Unit dbus-org.freedesktop.resolve1.service
not found.
Thanks,
Thierry
d: Failed
to execute program /usr/lib/dbus-1.0/debus-daemon-launch-helper: Success
That directory exists and the script file (if that is what it is) is
also exists. Is there something that script file should do but cannot
do for some reason?
Ken Heard
-BEGIN PGP SIGNATURE-
Version: GnuP
I also experienced this issue, and the instructions from Mikael Flood, seem
to have solved it.
Thank you.
"
Hello,
Try removing user file under ~/.config/dconf
rm ~/.config/dconf/user
This will revert your desktop to a "factory default" state (all shortcuts
and desktop changes will be reverted)
76264 37924 621124
>> -/+ buffers/cache: 831456 15513400
>> Swap:0 0 0
>>
>>
>> [image: Description: Inline image 1]
>>
>> Thanks
>>
>> M
>>
>>
>>
>>
>>
>> *From:* claude j
0 0
>
>
> [image: Description: Inline image 1]
>
> Thanks
>
> M
>
>
>
>
>
> *From:* claude juif [mailto:claude.j...@gmail.com]
> *Sent:* 08 April 2015 11:17
> *To:* Magdi Mahmoud
> *Cc:* debian-user@lists.debian.org
> *Subject:* Re
5-04-08 11:33 GMT+02:00 Magdi Mahmoud :
>
>
> Hi All,
>
>
>
> I have a problem with rel. 8.0 testing since installed sometimes
> randomly getting about %80 of CPU busy and X-Win doesn’t responding
>
> gnome-settings-daemon, dbus daemon utilise about %70
Hi All,
I have a problem with rel. 8.0 testing since installed sometimes randomly
getting about %80 of CPU busy and X-Win doesn't responding
gnome-settings-daemon, dbus daemon utilise about %70-%80.
Can someone advise please
Thank you
Mag
This email and any attachments m
Hi All,
I have a problem with rel. 8.0 testing since installed sometimes randomly
getting about %80 of CPU busy and X-Win doesn't responding
gnome-settings-daemon, dbus daemon utilise about %70-%80.
Can someone advise please
Thank you
Mag
Hi All,
I have a problem with rel. 8.0 testing since installed sometimes randomly
getting about %80 of CPU busy and X-Win doesn't responding
gnome-settings-daemon, dbus daemon utilise about %70-%80.
Can someone advise please
Thank you
Mag
This email and any attachments m
hello debian users,
I just tried to update my unstable VM, but I get this:
dpkg: error processing package dbus (--configure):
dependency problems - leaving triggers unprocessed
dpkg: dependency problems prevent processing triggers for dbus:
dbus depends on libdbus-1-3 (>= 1.7.6); howe
On Wed, 3 Sep 2014 21:38:47 +0100
Jonathan Dowland wrote:
> On Wed, Sep 03, 2014 at 03:54:06AM +0200, B wrote:
> > Hehe, because it sinks his claws deep and everywhere (it also
> > plans to implant dbus _into_ the kernel (WTF? A kernel is
> > here to kernelling a
stable to testing but I face the same problems still.
I don't understand this dbus thing.
Sorry to hear it didn't work.
My only options (if nobody can come with some) are to strip out
everything but the bare packages and then reinstall and if this fails,
to do a clean install...
Anyo
x27;t understand this dbus thing.
My only options (if nobody can come with some) are to strip out everything
but the bare packages and then reinstall and if this fails, to do a clean
install...
Anyone has any ideas?
To repeate, after a distupgrade from old-stable to stable I can't login at
the kdm
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?
everal wm, it is the same. I
commented out most of the things in .xsession, everything is executed
before the wm call.
I can't find errors in .xsession-errors and also not in Xorg.0.log. In
kdm.log I found this:
| klauncher(16137) kdemain: No DBUS session-bus found. Check if you have
start
in Xorg.0.log. In
kdm.log I found this:
| klauncher(16137) kdemain: No DBUS session-bus found. Check if you have
started the DBUS server.
| kdeinit4: Communication error with launcher. Exiting!
| kdmgreet(16130)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned
initialize() D-Bus call failed: &
On Sat, Apr 13, 2013 at 5:02 PM, Kevin Chadwick 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?
>> &g
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 fi
On Sat, Apr 13, 2013 at 10:39 AM, Kevin Chadwick 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 m
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 m
> 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 li
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.
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 k
atter is what dbus tackles)
The problem with dbus isn't dbus, it is that developers are becoming a
big problem because they are using it way too much as a first choice.
You should only use dbus when you need to. Some software is
unfortunately encouraging this and in turn other bad practices.
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
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 tha
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.
http://packages.
1 - 100 of 198 matches
Mail list logo
