As a workaround I created a file /etc/initramfs-tools/hooks/libgcc:
. /usr/share/initramfs-tools/hook-functions
copy_file library /lib/x86_64-linux-gnu/libgcc_s.so.1
/lib/x86_64-linux-gnu/libgcc_s.so.1
With this hook the lib is copied an I am able to provide a password at
login.
Package: cryptsetup
Version: 2:2.6.1-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: kai.weber+deb...@glorybox.de
Dear Maintainer,
Today's upgrade triggered a rebuild of the initramfs. After a reboot I
can no longer login to my system. Using an older kernel worked. This
* Sebastian Ramacher :
> That could be another case of the driver expecting to have a kernel
> available which in fact is disabled in the open source build. If
> 22.3.1+dfsg1-1 doesn't fix the issue for you, please let my know your
> CPU/GPU so that the issue can be reported upstream.
Package: intel-media-va-driver
Version: 22.3.0+dfsg1-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: kai.weber+deb...@glorybox.de
Dear Maintainer,
since a recent update (can not excalty determine the date) gstreamer based
applications like totem or gst-play-1.0 itself
> They are in a separate archive:
> https://wiki.debian.org/AutomaticDebugPackages
totem works again.
I ran totem again in gdb, and the backtrace mentioned libavcodec.so.57.
libavcodec57 was upgraded on my machine last week
2016-07-12 19:59:08 upgrade libavcodec57:amd64 7:3.0.2-4 7:3.1.1-1
❦ Michael Biebl :
> Can you install the totem-dbgsym and related packages to get a more
> useful backtrace.
It seems, totem-dbgsym is not available for amd64. I double checked
https://packages.debian.org/sid/totem-dbgsym
Do I have to build it by myself? How?
> Since we didn't
Package: totem
Version: 3.20.1-3
Severity: grave
Justification: renders package unusable
When starting totem the program does not start but exits directly with
"Aborted". I can provide more information if required.
$ totem
Aborted
Running with gdb:
$ gdb totem
GNU gdb (Debian 7.11.1-2) 7.11.1
Package: cryptsetup
Version: 2:1.4.1-1
Severity: critical
Justification: breaks the whole system
Since the upgrade from 1.3 to 1.4 my system no longer boots. Seems to be
a problem when trying to detect my root filesystem:
$ update-initramfs -u -v
Calling hook cryptroot
cryptsetup: WARNING:
Source: mutter
Followup-For: Bug #649363
In fallback mode the dialogs appear correctly.
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.1.0-1-amd64 (SMP w/2 CPU cores)
Package: chromium
Version: 15.0.874.106~r107270-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
after upgrade to the new chromium after start I always get the Chromium crash
page: Aw, Snap!
No URL can be opened, even internal ones like chrome://settings/
I am low on
Package: gpointing-device-settings
Version: 1.5.0-1
Severity: normal
I can confirm this bug and behaviour. The touchpad does not work
anymore.
Output of synclient -l attached but seems to be ok.
Regards, Kai
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT
Package: xserver-xorg-input-synaptics
Version: 1.2.0-1
Severity: critical
The fix for #524130 causes to not load the synaptics module for X
anymore. So I can not use the touchpad anymore. I removed the offending
lines from the .fdi file and the driver is loaded again.
As far as I understand from
Package: bash-completion
Version: 1:1.1-2
Severity: grave
Following bug with the new version renders the package unuseable:
bash: /etc/bash_completion: line 967: syntax error near unexpected token
`{'
bash: /etc/bash_completion: line 967: `else if ($1 !~ /:/ $1
~ /^'$cur'/) { print $1
Sebastian Dröge wrote:
could you get a backtrace with
GST_REGISTRY_FORK=no gdb --args gst-inspect-0.10 ladspa
run
bt full
For this please also install the debug packages of libc, glib,
gstreamer, gst-plugins-base and gst-plugins-bad.
This is what I did:
$ rm
$ totem
ERROR: Caught a segmentation fault while loading plugin file:
/usr/lib/gstreamer-0.10/libgstladspa.so
BTW, moving /usr/lib/gstreamer-0.10/libgstladspa.so out of the way
solves the problem.
Regards, Kai
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a
Package: gstreamer0.10-plugins-bad
Version: 0.10.11-2
Severity: normal
The error affects totem-gstreamer as well.
$ totem
ERROR: Caught a segmentation fault while loading plugin file:
/usr/lib/gstreamer-0.10/libgstladspa.so
Please either:
- remove it and restart.
- run with
Package: xserver-xorg-video-intel
Followup-For: Bug #451791
xserver-xorg-video-intel (2:2.3.2-2+lenny3) unstable; urgency=low
[ Brice Goglin ]
* Add 02_xaa_by_default_on_i965.diff to switch back to XAA on
i965 by default to avoid many rendering problems, closes: #451791.
With this
Just wanted to add that I can confirm the bug on amd64. A downgrade to
libglib 2.16.1-1 fixes the problem, too.
Regards
Kai
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Package: cpufrequtils
Version: 002-6
Severity: grave
Justification: renders package unusable
The script init.d/loadcpufreq is disabled by default, so no modules for
cpu frequency scaling are loaded. This makes init.d/cpufrequtils fail
as well.
If I read REDAME.Debian correctly this is not the
19 matches
Mail list logo