On Thu, Nov 14, 2019 at 11:48:14PM +0100, Michael Biebl wrote:
> Is this a system that has been restored from a backup?
It never was.
> Maybe some usr-merge related oddity.
> Michael
This system was originally installed as jessie long time ago and according
to versions of orphaned libraries it
Am 14.11.19 um 20:26 schrieb Sorin Manolache:
> I had the same problem. The cause were some old libs in
> /lib/x86_64-linux-gnu, especially a libseccomp. They are not
> package-managed (i.e. they don't belong to any package). I have copied
> them manually from /usr/lib/x86_64-linux-gnu to
Am 14.11.19 um 23:27 schrieb Jan Sindelar:
> Actually I have found a bunch of libraries not owned by any package
> (according to dpkg) in this directory and I am pretty sure I never manually
> copied them. Clearly this bug is not related to systemd, but I am not sure
> where should I report it.
On Thu, Nov 14, 2019 at 10:52:50PM +0100, Michael Biebl wrote:
> Hi,
> I suppose
> dpkg -S /lib/x86_64-linux-gnu/libseccomp.so.2
> yields nothing.
Hello,
preciselly right, there was stalled version of libseccomp.so.2 in
/lib/x86_64-linux-gnu and
Your message dated Thu, 14 Nov 2019 22:52:50 +0100
with message-id <03c5b4b7-077c-a8bf-9f65-651aca4cf...@debian.org>
and subject line Re: Bug#944726: systemd undefined symbol
has caused the Debian Bug report #944726,
regarding systemd undefined symbol
to be marked as done.
This means that you
Hello,
On Thu, Nov 14, 2019 at 05:19:32PM +0100, Michael Biebl wrote:
> Am 14.11.19 um 17:16 schrieb Michael Biebl:
> > For the failing binary, please run
> > ldd /path/to/binary
> > and attach the output to this bug report.
> I see from your systemd-delta.txt output:
> systemd-delta: symbol
Am 14.11.19 um 20:26 schrieb Sorin Manolache:
I copy the new binaries from
> /usr/lib/x86_64-linux-gnu to /lib/x86_64-linux-gnu.
Please don't do that. The only reasonable solution is to remove any
stale libraries you have copied/installed manually.
You might have to run ldconfig afterwards.
--
On Thu, 14 Nov 2019 17:19:32 +0100 Michael Biebl wrote:
Am 14.11.19 um 17:16 schrieb Michael Biebl:
> For the failing binary, please run
> ldd /path/to/binary
>
> and attach the output to this bug report.
I see from your systemd-delta.txt output:
systemd-delta: symbol lookup error:
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package systemd
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
#
# bts-link upstream status pull for source package systemd
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
# https://bts-link-team.pages.debian.net/bts-link/
#
user debian-bts-l...@lists.debian.org
# remote status report for #902416 (http://bugs.debian.org/902416)
Control: severity -1 normal
Am 14.11.19 um 13:22 schrieb Jan Sindelar:
> Package: systemd
> Version: 243-5
> Severity: critical
> Justification: breaks the whole system
>
> Dear Maintainer,
>
>* What led up to the situation?
> Installing latest systemd package using apt full-upgrade in
Am 14.11.19 um 17:16 schrieb Michael Biebl:
> For the failing binary, please run
> ldd /path/to/binary
>
> and attach the output to this bug report.
I see from your systemd-delta.txt output:
systemd-delta: symbol lookup error:
/lib/systemd/libsystemd-shared-243.so: undefined symbol:
Processing control commands:
> severity -1 normal
Bug #944726 [systemd] systemd undefined symbol
Severity set to 'normal' from 'critical'
--
944726: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944726
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Your message dated Thu, 14 Nov 2019 14:52:16 +
with message-id
and subject line Bug#944586: fixed in systemd 243-6
has caused the Debian Bug report #944586,
regarding udev: after upgrading to version 243-5, udev blocks the removal of
lvm2 snapshots
to be marked as done.
This means that you
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 14 Nov 2019 14:09:49 +0100
Source: systemd
Architecture: source
Version: 243-6
Distribution: unstable
Urgency: medium
Maintainer: Debian systemd Maintainers
Changed-By: Michael Biebl
Closes: 944586
Changes:
systemd_243-6_source.changes uploaded successfully to localhost
along with the files:
systemd_243-6.dsc
systemd_243-6.debian.tar.xz
systemd_243-6_source.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
Processing control commands:
> tag -1 pending
Bug #944586 [udev] udev: after upgrading to version 243-5, udev blocks the
removal of lvm2 snapshots
Added tag(s) pending.
--
944586: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944586
Debian Bug Tracking System
Contact ow...@bugs.debian.org
Processing control commands:
> forwarded -1 https://github.com/systemd/systemd/issues/14027
Bug #944675 [udev] udev: Keyboard and mouse not working in X.org with udev 243-5
Set Bug forwarded-to-address to
'https://github.com/systemd/systemd/issues/14027'.
--
944675:
Control: forwarded -1 https://github.com/systemd/systemd/issues/14027
Am 14.11.19 um 14:23 schrieb Gunther Furtado:
> Keyboard and mouse not working in X.org with udev 243-5 #14027
Thanks, marking accordingly.
--
Why is it that all of the instruments seeking intelligent life in the
universe
Dear Maintainer,
I've done it. Hope it helps.
Keyboard and mouse not working in X.org with udev 243-5 #14027
Cheers,
Em 14/11/2019 10:35, Michael Biebl escreveu:
Am 14.11.19 um 13:25 schrieb Gunther Furtado:
Package: udev
Version: 243-5
Followup-For: Bug #944675
Dear Maintainer,
Same
Processing commands for cont...@bugs.debian.org:
> severity 944675 important
Bug #944675 [udev] udev: Keyboard and mouse not working in X.org with udev 243-5
Severity set to 'important' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
944675:
Am 14.11.19 um 11:50 schrieb Klaumi Klingsporn:
> So: As this bug makes desktop-systems where systemd generally uses the
> graphical.target
> as default.target totally unusable, I think thebug should be set to grave!
So far this seems to be an isolated issue, possibly hardware related or
Processing control commands:
> tags -1 + moreinfo
Bug #944726 [systemd] systemd undefined symbol
Added tag(s) moreinfo.
--
944726: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944726
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 + moreinfo
Am 14.11.19 um 13:22 schrieb Jan Sindelar:
> Package: systemd
> Version: 243-5
> Severity: critical
> Justification: breaks the whole system
>
> Dear Maintainer,
>
>* What led up to the situation?
> Installing latest systemd package using apt full-upgrade in
Package: systemd
Version: 243-5
Severity: critical
Justification: breaks the whole system
Dear Maintainer,
* What led up to the situation?
Installing latest systemd package using apt full-upgrade in testing
* What exactly did you do (or not do) that was effective (or
ineffective)?
Processing commands for cont...@bugs.debian.org:
> retitle 944645 systemd: daemon-reload triggers an assert in
> manager_unref_uid_internal()
Bug #944645 [systemd] systemd: upgrade breaks dbus
Changed Bug title to 'systemd: daemon-reload triggers an assert in
manager_unref_uid_internal()' from
Package: systemd
Followup-For: Bug #944675
It's the same here, no input devices in X with udev 243-5.
All worked fine after yesterdays upgrade until the reboot today. My desktop
computer which starts lightdm as login-service was unusable because there
was no input device.
Rebooting in recovery
27 matches
Mail list logo
