On Sat 03 Dec 2022 at 08:19:48 (+0100), Loïc Grenié wrote:
> On Sat Dec, 3, 2022 at 04:03, David Wright wrote:
> > Yes, hence my comment on potential interactions between different
> > packages. The OP mentioned udev, but in their OP they talked about
> > manually restarting systemd services. I wa
On Sat Dec, 3, 2022 at 04:03, David Wright wrote:
> On Fri 02 Dec 2022 at 21:33:45 (-0500), The Wanderer wrote:
> >
> > FWIW:
> >
> > $ apt-cache policy udev
> > udev:
> > Installed: 252.1-1
> > Candidate: 252.1-1
> > Version table:
> > *** 252.1-1 900
> > 900 http://ftp.us.debian.o
On Fri 02 Dec 2022 at 21:33:45 (-0500), The Wanderer wrote:
>
> FWIW:
>
> $ apt-cache policy udev
> udev:
> Installed: 252.1-1
> Candidate: 252.1-1
> Version table:
> *** 252.1-1 900
> 900 http://ftp.us.debian.org/debian testing/main amd64 Packages
> 100 /var/lib/dpkg/statu
On 2022-12-02 at 21:04, David Wright wrote:
> On Fri 02 Dec 2022 at 09:04:35 (+0100), Loïc Grenié wrote:
>
>> On Fri Dec 2 2022 at 04:31, David Wright wrote:
>>> AFAICT udev was upgraded from 247.3-7 to 247.3-7+deb11u1 in early
>>> September, so which distribution are /you/ running?
>>
>> % lsb_
On Fri 02 Dec 2022 at 09:04:35 (+0100), Loïc Grenié wrote:
> On Fri Dec 2 2022 at 04:31, David Wright wrote:
> > On Wed 30 Nov 2022 at 14:25:19 (+0100), Loïc Grenié wrote:
> > > Happened once again. This time I think the culprit was udev (but I
> > > cannot
> > > be too sure). Among the upda
On Fri Dec 2 2022 at 04:31, David Wright wrote:
> On Wed 30 Nov 2022 at 14:25:19 (+0100), Loïc Grenié wrote:
> > Happened once again. This time I think the culprit was udev (but I
> > cannot
> > be too sure). Among the updated package nothing should have killed X:
> > beyond udev there wa
On Wed 30 Nov 2022 at 14:25:19 (+0100), Loïc Grenié wrote:
> Happened once again. This time I think the culprit was udev (but I
> cannot
> be too sure). Among the updated package nothing should have killed X:
> beyond udev there was a bunch of libreoffice and related (not using right
> n
On Thu 01 Dec 2022 at 17:45:25 (-0700), Tom Dial wrote:
> On 11/29/22 15:35, Loïc Grenié wrote:
> > Dear Debian users,
> >
> > when I apt upgrade my system, I often (one every three, more
> > or less) find myself brutally logged out of the window system,
> > with systemd services p
Loïc Grenié wrote:
Dear Debian users,
when I apt upgrade my system, I often (one every three, more
or less) find myself brutally logged out of the window system,
with systemd services painfully restarting (or failing to restart).
The only way I can recover is usually to reboot
On 11/29/22 15:35, Loïc Grenié wrote:
Dear Debian users,
when I apt upgrade my system, I often (one every three, more
or less) find myself brutally logged out of the window system,
with systemd services painfully restarting (or failing to restart).
The only way I can recove
On Thu, Dec 01, 2022 at 12:34:35AM -0500, Stefan Monnier wrote:
> >> The one application I do avoid upgrading while it's running is
> >> Firefox, but that's mainly because it occasionally gives a new
> >> startup screen after an upgrade, and I want to read what it says.
> >
> > I take the risk and
>> The one application I do avoid upgrading while it's running is
>> Firefox, but that's mainly because it occasionally gives a new
>> startup screen after an upgrade, and I want to read what it says.
>
> I take the risk and watch the thing going down in flames. I
> admit that it gives me a strange
On Wed, Nov 30, 2022 at 02:36:57PM -0600, David Wright wrote:
[...]
> The only reasons I'd close down X are (a) a dist-upgrade from
> oldstable to stable (and the like),
That I do, too.
> and (b) dpkg-reconfigure
> console-setup and keyboard-configuration after I've been
> t
On Wed 30 Nov 2022 at 08:42:41 (+0100), to...@tuxteam.de wrote:
> On Wed, Nov 30, 2022 at 12:36:43AM -0500, Felix Miata wrote:
>
> > I learned many many moons ago to not trust any update/upgrade process to not
> > interfere with a running X session. I usually close apps I don't want data
> > lost
On 11/30/22, to...@tuxteam.de wrote:
> On Wed, Nov 30, 2022 at 12:36:43AM -0500, Felix Miata wrote:
>
> [...]
>
>> What I have noticed in Debian that I do not at all like, is when I boot
>> to
>> multi-user.target for the specific purpose of apt or apt-get upgrading,
>> even when
>> systemctl get-
Happened once again. This time I think the culprit was udev (but I
cannot
be too sure). Among the updated package nothing should have killed X:
beyond udev there was a bunch of libreoffice and related (not using right
now), zathura (not using), not much more, at the very least, nothing t
On Wed, Nov 30, 2022 at 06:16:04AM +0100, to...@tuxteam.de wrote:
> FWIW it never happened to me. But: I'm on a pretty minimal system by
> today's standards (X, Fvwm). The only application behaving strangely
> after a dist-upgrade is... the browser, Firefix: "Ohmigod, something
> funny happened, I'
On 11/30/22, to...@tuxteam.de wrote:
> On Wed, Nov 30, 2022 at 12:44:49AM +0100, DdB wrote:
>> Am 29.11.2022 um 23:35 schrieb Loïc Grenié:
>> > when I apt upgrade my system, I often (one every three, more
>> > or less) find myself brutally logged out of the window system,
>> > with systemd
Jeffrey Walton writes:
> KDE works as expected.
Yep.
> God bless those who have stuck with GNOME after the change to GNOME3.
> They have the tolerance of saints.
I have to agree. I did get Gnome 3 to somewhere I kinda liked but when
an updated wiped my customizations, it was time to say good b
Thanks Tomas, and thanks to all those responded,
On Wed, Nov 30, 2022 at 06:16, Tomas wrote:
> On Wed, Nov 30, 2022 at 12:44:49AM +0100, DdB wrote:
> > Am 29.11.2022 um 23:35 schrieb Loïc Grenié:
> > > when I apt upgrade my system, I often (one every three, more
> > > or less) find mys
On Wed, Nov 30, 2022 at 12:36:43AM -0500, Felix Miata wrote:
[...]
> What I have noticed in Debian that I do not at all like, is when I boot to
> multi-user.target for the specific purpose of apt or apt-get upgrading, even
> when
> systemctl get-default returns multi-user.target, that if the DM
Loïc Grenié composed on 2022-11-29 23:35 (UTC+0100):
> when I apt upgrade my system, I often (one every three, more
> or less) find myself brutally logged out of the window system,
> with systemd services painfully restarting (or failing to restart).
> The only way I can recover is usual
On Wed, Nov 30, 2022 at 12:16 AM wrote:
>
> On Wed, Nov 30, 2022 at 12:44:49AM +0100, DdB wrote:
> > Am 29.11.2022 um 23:35 schrieb Loïc Grenié:
> > > when I apt upgrade my system, I often (one every three, more
> > > or less) find myself brutally logged out of the window system,
> > > wit
On Wed, Nov 30, 2022 at 12:44:49AM +0100, DdB wrote:
> Am 29.11.2022 um 23:35 schrieb Loïc Grenié:
> > when I apt upgrade my system, I often (one every three, more
> > or less) find myself brutally logged out of the window system,
> > with systemd services painfully restarting (or failing t
Am 29.11.2022 um 23:35 schrieb Loïc Grenié:
> when I apt upgrade my system, I often (one every three, more
> or less) find myself brutally logged out of the window system,
> with systemd services painfully restarting (or failing to restart).
> The only way I can recover is usually to rebo
Dear Debian users,
when I apt upgrade my system, I often (one every three, more
or less) find myself brutally logged out of the window system,
with systemd services painfully restarting (or failing to restart).
The only way I can recover is usually to reboot. I've tried to
manually
26 matches
Mail list logo
