Bug#947833: Emergency shell unusable with root login disabled

2019-12-31 Thread Glenn McGrath
Package: debian-installer
Version: Bullseye Alpha 1

Did an 'advanced graphical install' of Bullseye using alpha1 installer;

I selected to disable root login for security reasons, so just had the one
account (and because i was too lazy to type in another password again).
I tried to do some advanced partitioning (crypt+lvm) during setup on disk
2+3.

Upon reboot there was something wrong with the disk setup, it tried to dump
me into the "Emergency shell", but i couldn't actually get a shell,
something about root login disabled (forget the exact wording).

I think it should be possible to have a working login to an emergency shell
via sudo (sudo did configure itself properly).
Or perhaps there could be a warning that the emergency shell wont work when
logins are being configured in the installer.

I bypassed the LVM problem and will manually do it, i believe there are
other bug reports about that.


Bug#701779: Fails to install due to missing library (in dependency?)

2013-02-26 Thread Glenn McGrath
Package: lttng-tools
Version: 2.1.0~rc9-1
Severity: grave
Justification: renders package unusable

The package or one of its dependencies appears to be missing a symlink for
a required library.

Setting up lttng-tools (2.1.0~rc9-1) ...
/usr/sbin/addgroup
[] Starting lttng-sessiond : lttng-sessiond/usr/bin/lttng-sessiond:
error
while loading shared libraries: liblttng-ust-ctl.so.0: cannot open shared
object file: No such file or directory
 failed!
invoke-rc.d: initscript lttng-sessiond, action start failed.

As shown in bold, liblttng-ust-ctl isnt found.
$ ldd /usr/bin/lttng-sessiond
linux-vdso.so.1 =  (0x7fff551a5000)
librt.so.1 = /lib/x86_64-linux-gnu/librt.so.1 (0x7fa93cce8000)
liblttng-ctl.so.0 = /usr/lib/x86_64-linux-gnu/liblttng-ctl.so.0
(0x7fa93cac6000)
liburcu-common.so.1 = /usr/lib/liburcu-common.so.1
(0x7fa93c8c2000)
liburcu.so.1 = /usr/lib/liburcu.so.1 (0x7fa93c6bc000)
libdl.so.2 = /lib/x86_64-linux-gnu/libdl.so.2 (0x7fa93c4b8000)
*liblttng-ust-ctl.so.0 = not found*
libpopt.so.0 = /lib/x86_64-linux-gnu/libpopt.so.0
(0x7fa93c2aa000)
libpthread.so.0 = /lib/x86_64-linux-gnu/libpthread.so.0
(0x7fa93c08e000)
libc.so.6 = /lib/x86_64-linux-gnu/libc.so.6 (0x7fa93bd03000)
/lib64/ld-linux-x86-64.so.2 (0x7fa93d15c000)

Looking for it in the filesystem i find an unresolved symlink,
liblttng-ust-ctl.so.1.0.0

$ ls -al /usr/lib/x86_64-linux-gnu/liblttng-ust-ctl*
-rw-r--r-- 1 root root 217596 Jan 21 09:01
/usr/lib/x86_64-linux-gnu/liblttng-ust-ctl.a
lrwxrwxrwx 1 root root 25 Jan 21 09:01
/usr/lib/x86_64-linux-gnu/liblttng-ust-ctl.so - liblttng-ust-ctl.so.1.0.0

$ dpkg -S /usr/lib/x86_64-linux-gnu/liblttng-ust-ctl.so
liblttng-ust-dev:amd64: /usr/lib/x86_64-linux-gnu/liblttng-ust-ctl.so
$ dpkg -S liblttng-ust-ctl.so.1.0.0
dpkg-query: no path found matching pattern *liblttng-ust-ctl.so.1.0.0*

Im not sure which package should be installing liblttng-ust-ctl.so.0 and
liblttng-ust-ctl.so.1.0.0, but it didnt happen on my install.

I guess i can just do the symlink myself.



-- System Information:
Debian Release: 7.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages lttng-tools depends on:
ii  libc6   2.13-38
ii  liblttng-ctl0   2.1.0~rc9-1
ii  liblttng-ust0   2.1.1-1
ii  libpopt01.16-7
ii  liburcu10.7.6-1
ii  lttng-modules-dkms  2.1.0-1

Versions of packages lttng-tools recommends:
ii  babeltrace  1.0.3-1

lttng-tools suggests no packages.

-- debconf-show failed


Bug#701779: Clarification

2013-02-26 Thread Glenn McGrath
The previous fix was fro the debian files in ust-2.1.1 source package, then
you can rebuild ltt-control (unchanged) and all the debs install.


Bug#667751: Current status

2012-08-03 Thread Glenn McGrath
I just upgraded to Sid from testing, uninstalled libsqlite3-dev and
anjuta still seems to be working fine, it can open my project.

I had not manually changed anything.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#668244: New uriparser source release, 0.7.7

2012-04-09 Thread Glenn McGrath
Source: uriparser
Version: 0.7.5

There is a new version of uriparser available from its homepage, version 0.7.7.

0.7.6 looks to be fix mainly build errors, 0.7.7 has a couple of bug fixes.


Thanks



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#667751: Anjuta problem starting

2012-04-07 Thread Glenn McGrath
I think i have the same bug, since updating some packages (had done an
update for a while), im using testing with everything upto date, cant
see where libsqlite dependency is coming from, i think the bug might
be in a different package, this my output;

$ anjuta

** (anjuta:16054): WARNING **: Can't find libsqlite3.so file.

(anjuta:16054): GLib-GObject-CRITICAL **: g_object_new: assertion
`G_TYPE_IS_OBJECT (object_type)' failed

(anjuta:16054): GLib-GObject-CRITICAL **: g_object_set_data: assertion
`G_IS_OBJECT (object)' failed

** (anjuta:16054): WARNING **: Can't find libsqlite3.so file.

(anjuta:16054): GLib-GObject-CRITICAL **: g_object_new: assertion
`G_TYPE_IS_OBJECT (object_type)' failed

** (anjuta:16054): WARNING **: Can't find libsqlite3.so file.

(anjuta:16054): GLib-GObject-CRITICAL **: g_object_new: assertion
`G_TYPE_IS_OBJECT (object_type)' failed

(anjuta:16054): GLib-GObject-CRITICAL **: g_object_set_data: assertion
`G_IS_OBJECT (object)' failed

** (anjuta:16054): CRITICAL **: gda_server_provider_supports_feature:
assertion `GDA_IS_SERVER_PROVIDER (provider)' failed

** (anjuta:16054): WARNING **: Can't find libsqlite3.so file.

(anjuta:16054): GLib-GObject-CRITICAL **: g_object_new: assertion
`G_TYPE_IS_OBJECT (object_type)' failed

(anjuta:16054): GLib-GObject-CRITICAL **: g_object_set_data: assertion
`G_IS_OBJECT (object)' failed

(anjuta:16054): libanjuta-symbol-db-WARNING **: Could not open
connection to DB_DIR=/home/glenn/.cache/anjuta;DB_NAME=.anjuta_sym_db


libanjuta-symbol-db-ERROR **: Opening global project under
/home/glenn/.cache/anjuta
Trace/breakpoint trap

$ rm -Rf  /home/glenn/.cache/anjuta/session
$ anjuta
$

Anjuta started once i deleted that cache directory, but it crashes
once you open or import a project.

$ ldd /usr/bin/anjuta
linux-vdso.so.1 =  (0x7fff9b56d000)
libgtksourceview-3.0.so.0 = /usr/lib/libgtksourceview-3.0.so.0
(0x7f3e8d5c1000)
libanjuta-3.so.0 = /usr/lib/libanjuta-3.so.0 (0x7f3e8d31c000)
libgdl-3.so.1 = /usr/lib/libgdl-3.so.1 (0x7f3e8d0ea000)
libgtk-3.so.0 = /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 
(0x7f3e8ca97000)
libgdk-3.so.0 = /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 
(0x7f3e8c819000)
libgio-2.0.so.0 = /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
(0x7f3e8c4d3000)
libgdk_pixbuf-2.0.so.0 =
/usr/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0 (0x7f3e8c2b4000)
libgobject-2.0.so.0 = /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
(0x7f3e8c063000)
libgthread-2.0.so.0 = /usr/lib/x86_64-linux-gnu/libgthread-2.0.so.0
(0x7f3e8be5d000)
libglib-2.0.so.0 = /lib/x86_64-linux-gnu/libglib-2.0.so.0 
(0x7f3e8bb66000)
libxml2.so.2 = /usr/lib/libxml2.so.2 (0x7f3e8b808000)
libpthread.so.0 = /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f3e8b5eb000)
libc.so.6 = /lib/x86_64-linux-gnu/libc.so.6 (0x7f3e8b264000)
libpangocairo-1.0.so.0 =
/usr/lib/x86_64-linux-gnu/libpangocairo-1.0.so.0 (0x7f3e8b057000)
libcairo.so.2 = /usr/lib/x86_64-linux-gnu/libcairo.so.2 
(0x7f3e8ad63000)
libpango-1.0.so.0 = /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0
(0x7f3e8ab16000)
libgmodule-2.0.so.0 = /usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0
(0x7f3e8a913000)
libutil.so.1 = /lib/x86_64-linux-gnu/libutil.so.1 (0x7f3e8a70f000)
libatk-1.0.so.0 = /usr/lib/x86_64-linux-gnu/libatk-1.0.so.0
(0x7f3e8a4ec000)
libpangoft2-1.0.so.0 =
/usr/lib/x86_64-linux-gnu/libpangoft2-1.0.so.0 (0x7f3e8a2c)
libcairo-gobject.so.2 =
/usr/lib/x86_64-linux-gnu/libcairo-gobject.so.2 (0x7f3e8a0b7000)
libfreetype.so.6 = /usr/lib/x86_64-linux-gnu/libfreetype.so.6
(0x7f3e89e18000)
libfontconfig.so.1 = /usr/lib/x86_64-linux-gnu/libfontconfig.so.1
(0x7f3e89be3000)
librt.so.1 = /lib/x86_64-linux-gnu/librt.so.1 (0x7f3e899da000)
libX11.so.6 = /usr/lib/x86_64-linux-gnu/libX11.so.6 
(0x7f3e8969b000)
libXcomposite.so.1 = /usr/lib/x86_64-linux-gnu/libXcomposite.so.1
(0x7f3e89499000)
libXdamage.so.1 = /usr/lib/x86_64-linux-gnu/libXdamage.so.1
(0x7f3e89296000)
libXfixes.so.3 = /usr/lib/x86_64-linux-gnu/libXfixes.so.3 
(0x7f3e8909)
libm.so.6 = /lib/x86_64-linux-gnu/libm.so.6 (0x7f3e88e0e000)
libXext.so.6 = /usr/lib/x86_64-linux-gnu/libXext.so.6 
(0x7f3e88bfa000)
libXinerama.so.1 = /usr/lib/x86_64-linux-gnu/libXinerama.so.1
(0x7f3e889f8000)
libXi.so.6 = /usr/lib/x86_64-linux-gnu/libXi.so.6 (0x7f3e887e8000)
libXrandr.so.2 = /usr/lib/x86_64-linux-gnu/libXrandr.so.2 
(0x7f3e885e)
libXcursor.so.1 = /usr/lib/x86_64-linux-gnu/libXcursor.so.1
(0x7f3e883d6000)
libz.so.1 = /usr/lib/x86_64-linux-gnu/libz.so.1 (0x7f3e881bf000)
libselinux.so.1 = /lib/x86_64-linux-gnu/libselinux.so.1 
(0x7f3e87f9f000)

Bug#667751:

2012-04-07 Thread Glenn McGrath
Upgrading anjuta from testing to sid doesnt change the bug.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#667751: Workaround for the this bug

2012-04-07 Thread Glenn McGrath
A workaround for this bug is;

apt-get install libsqlite3-dev

No idea why it fixes it.. (btw didnt see the workaround in first post,
should have tried that first)



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#667751:

2012-04-07 Thread Glenn McGrath
Specifically, its the symlink from libsqlite-dev that is needed fro
anjuta to start

/usr/lib/x86_64-linux-gnu/libsqlite3.so - libsqlite3.so.0.8.6

Maybe this bug is really from libgda



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org