[Bug 1928118] Re: cannot enter foreign arch schroot since qemu 1:5.2+dfsg-4

[Roger Leigh]

Looking at the attached schroot.debdiff, I'm not sure why this change is
also containing a number of changes related to "dchroot" and "dchroot-
dsa", two obsolete tools which are unrelated to the qemu issue.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928118

Title:
  cannot enter foreign arch schroot since qemu 1:5.2+dfsg-4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/schroot/+bug/1928118/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1899414] [NEW] schroot fails for source chroots with 'std:bad_alloc' on groovy

[Roger Leigh]

Hi Alex,


Looking any 
https://gitlab.com/codelibre/schroot/-/blame/schroot-1.6/sbuild/sbuild-util.cc#L757
 


and this commit:

https://gitlab.com/codelibre/schroot/-/commit/83bc6d3f99b1aa04a4864faeeb867ed09bae8e55


It looks like if this hasn’t been picked up, it should be.  Maybe a new schroot 
point release is in order; schroot isn’t currently a high priority, I’m afraid.


Kind regards,
Roger

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899414

Title:
  schroot fails for source chroots with 'std:bad_alloc' on groovy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/schroot/+bug/1899414/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1899414] Re: schroot fails for source chroots with 'std:bad_alloc' on groovy

[Roger Leigh]

** Bug watch added: Debian Bug tracker #763896
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763896

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899414

Title:
  schroot fails for source chroots with 'std:bad_alloc' on groovy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/schroot/+bug/1899414/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

RE: [Bug 1899414] [NEW] schroot fails for source chroots with 'std:bad_alloc' on groovy

[Roger Leigh]

Hi Alex,This is failing 
here:https://gitlab.com/codelibre/schroot/-/blob/schroot-1.6/sbuild/sbuild-util.cc#L757Is
 there something unusual about the group being checked?  getgrnam_r has 
returned ERANGE and schroot increased the buffer size to accommodate this until 
it ran out of memory.  The cause of failure is clear but the reason is not.Are 
you using LDAP, AD or is this all local users and groups?Kind regards,Roger 
Leigh
 Original message From: Alex Murray 
<1899...@bugs.launchpad.net> Date: 12/10/2020  06:20  (GMT+00:00) To: 
rle...@codelibre.net Subject: [Bug 1899414] [NEW] schroot fails for source 
chroots with
  'std:bad_alloc' on groovy Public bug reported:After upgrading to groovy or 
installing fresh from the beta, schrootfails to enter a source: chroot with 
std:bad_alloc:$ schroot -c source:bionic-amd64E: std::bad_allocRunning this 
with debugging symbols under gdb we get the followingbacktrace:amurray@slate:~$ 
gdb --ex='break std::bad_alloc::bad_alloc()' --ex=run --args schroot -c 
source:bionic-amd64GNU gdb (Ubuntu 9.2-0ubuntu2) 9.2Copyright (C) 2020 Free 
Software Foundation, Inc.License GPLv3+: GNU GPL version 3 or later 
<http://gnu.org/licenses/gpl.html>This is free software: you are free to change 
and redistribute it.There is NO WARRANTY, to the extent permitted by law.Type 
"show copying" and "show warranty" for details.This GDB was configured as 
"x86_64-linux-gnu".Type "show configuration" for configuration details.For bug 
reporting instructions, please see:<http://www.gnu.org/software/gdb/bugs/>.Find 
the GDB manual and other documentation resources online at:    
<http://www.gnu.org/software/gdb/documentation/>.For help, type "help".Type 
"apropos word" to search for commands related to "word"...Reading symbols from 
schroot...Reading symbols from 
/usr/lib/debug/.build-id/70/4469864df39ed3af1f8a23bd8d27adffeb8315.debug...Catchpoint
 1 (throw)Function "std::bad_alloc::bad_alloc()" not defined.Make breakpoint 
pending on future shared library load? (y or [n]) yBreakpoint 2 
(std::bad_alloc::bad_alloc()) pending.Starting program: /usr/bin/schroot -c 
source:bionic-amd64[Thread debugging using libthread_db enabled]Using host 
libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".Catchpoint 1 
(exception thrown), 0x7fd231965762 in __cxa_throw () from 
/lib/x86_64-linux-gnu/libstdc++.so.6(gdb) bt full#0  0x7fd231965762 in 
__cxa_throw () from /lib/x86_64-linux-gnu/libstdc++.so.6No symbol table info 
available.#1  0x7fd231959562 in ?? () from 
/lib/x86_64-linux-gnu/libstdc++.so.6No symbol table info available.#2  
0x5596c26b8a2f in __gnu_cxx::new_allocator::allocate 
(this=0x7ffd3b189dd0, __n=34359738368) at 
/usr/include/c++/9/ext/new_allocator.h:102No locals.#3  
std::allocator_traits >::allocate (__a=..., 
__n=34359738368) at /usr/include/c++/9/bits/alloc_traits.h:444No locals.#4  
std::_Vector_base >::_M_allocate 
(this=0x7ffd3b189dd0, __n=34359738368) at 
/usr/include/c++/9/bits/stl_vector.h:343No locals.#5  std::vector >::reserve (this=this@entry=0x7ffd3b189dd0, 
__n=__n@entry=34359738368) at /usr/include/c++/9/bits/vector.tcc:78    
__old_size = 0    __tmp = #6  0x5596c26b5996 in 
sbuild::group::query_name (this=0x7ffd3b189db0, name=0x5596c2c558c0 "admin") at 
./sbuild/sbuild-util.cc:770    size = 34359738368    error =     grp_result = 0x0#7  0x5596c26b5abf in sbuild::group::query_name 
(name=..., this=0x7ffd3b189db0) at 
/usr/include/c++/9/bits/basic_string.h:2300No locals.#8  sbuild::group::group 
(this=0x7ffd3b189db0, name=...) at ./sbuild/sbuild-util.cc:717No locals.#9  
0x5596c26a463f in sbuild::session::is_group_member (this=, 
groupname="admin") at ./sbuild/sbuild-session.cc:390    grp = { = 
{gr_name = 0x7fd1b0416010 , gr_passwd = 0x7fd1b041601e , gr_gid = 138,     gr_mem = 0x7fd1b0416028}, 
buffer = std::vector of length 0, capacity 17179869184, valid = false}    
group_member =     __PRETTY_FUNCTION__ = #10 
0x5596c26a49eb in sbuild::session::get_chroot_membership 
(this=0x5596c2c329f0, chroot=..., in_users=@0x7ffd3b189e94: false, 
in_root_users=@0x7ffd3b189e95: false, in_groups=@0x7ffd3b189e96: false,     
in_root_groups=@0x7ffd3b189e97: true) at ./sbuild/sbuild-session.cc:475    
gp = "admin"    users = std::vector of length 0, capacity 0    
root_users =     groups =     root_groups 
= std::vector of length 3, capacity 3 = {"root", "sbuild", "admin"}    upos 
=     rupos = #11 0x5596c26a4cd1 in 
sbuild::session::get_chroot_auth_status (this=0x5596c2c329f0, 
status=sbuild::auth::STATUS_NONE, chroot=...) at ./sbuild/sbuild-session.cc:496 
   in_users = false    in_root_users = false    in_groups = false   
 in_root_groups = true#12 0x000

[Bug 1824721] Re: g++-8 in disco is broken with libstdc++6 from gcc9 and libstdc++fs

[Roger Leigh]

The link order does seem to be significant as you suggested.  However,
both the linker and run-time linker succeed without error.  The failure
is inside the path dtor.  While --as-needed may well be at fault, it
looks like there may be problems with either not reporting errors, or
doing the wrong thing, when the link order isn't right.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824721

Title:
  g++-8 in disco is broken with libstdc++6 from gcc9 and libstdc++fs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-8/+bug/1824721/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1824721] Re: g++-8 in disco is broken with libstdc++6 from gcc9 and libstdc++fs

[Roger Leigh]

Note that the strategy for GCC packaging in Ubuntu (maybe also in
Debian) is the exact opposite of how RedHat handle GCC packaging for
RHEL with the Devtoolset stuff.

Ubuntu is always providing the latest version of libstdc++6 from the
newest GCC.  This is problematic when the older headers are subtly (or
not-so-subtly) incompatible with the shared library.

RedHat always uses the copy of libstdc++ provided by the default
compiler for the base system.  Newer GCC versions link against this
library, with newer functionality provided by static linking of the
newer libstdc++ for that GCC version.

Both strategies make compromises.  But right now, the default GCC
version in Ubuntu is actually broken as a result of the former strategy.
Perhaps the default libstdc++6 should be provided by the default GCC
version, with later versions adding supplementary functionality via a
static library?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824721

Title:
  g++-8 in disco is broken with libstdc++6 from gcc9 and libstdc++fs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-8/+bug/1824721/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1824721] [NEW] g++-8 in disco is broken with libstdc++6 from gcc9 and libstdc++fs

[Roger Leigh]

Public bug reported:

There is a significant incompatibility here which leaves the default C++
compiler broken with C++17 std::filesystem usage.  Unfortunately, there
isn't an obvious workaround since there's only one libstdc++6 package,
and it's using the non-default and unreleased GCC9 version of libstdc++,
making it impossible to use the compatible GCC8 version of the library.

% cat testpath.cpp
#include 

int main()
{
  std::filesystem::path p("test");
}

g++-9 -std=c++17 -lstdc++fs -g3 -o testpath testpath.cpp 
% ./testpath

% g++-8 -std=c++17 -lstdc++fs -g3 -o testpath testpath.cpp
% ./testpath  
zsh: segmentation fault (core dumped)  ./testpath

% gdb testpath
GNU gdb (Ubuntu 8.2.91.20190405-0ubuntu3) 8.2.91.20190405-git
Copyright (C) 2019 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from testpath...
(gdb) run
Starting program: /tmp/testpath 

Program received signal SIGSEGV, Segmentation fault.
0x649b in std::vector >::~vector (this=0x23, 
__in_chrg=) at /usr/include/c++/8/bits/stl_vector.h:567
567 std::_Destroy(this->_M_impl._M_start, this->_M_impl._M_finish,
(gdb) bt
#0  0x649b in std::vector >::~vector (this=0x23, 
__in_chrg=) at /usr/include/c++/8/bits/stl_vector.h:567
#1  0x6314 in std::filesystem::__cxx11::path::~path (this=0x3, 
__in_chrg=)
at /usr/include/c++/8/bits/fs_path.h:208
#2  0x6f5c in std::filesystem::__cxx11::path::_Cmpt::~_Cmpt 
(this=0x3, __in_chrg=)
at /usr/include/c++/8/bits/fs_path.h:643
#3  0x6f77 in std::_Destroy 
(__pointer=0x3)
at /usr/include/c++/8/bits/stl_construct.h:98
#4  0x6e27 in 
std::_Destroy_aux::__destroy (
__first=0x3, __last=0x0) at /usr/include/c++/8/bits/stl_construct.h:108
#5  0x6a98 in std::_Destroy 
(__first=0x3, __last=0x0)
at /usr/include/c++/8/bits/stl_construct.h:137
#6  0x67a9 in std::_Destroy (__first=0x3, __last=0x0) at 
/usr/include/c++/8/bits/stl_construct.h:206
#7  0x64b1 in std::vector >::~vector 
(this=0x7fffe310, __in_chrg=)
at /usr/include/c++/8/bits/stl_vector.h:567
#8  0x6314 in std::filesystem::__cxx11::path::~path 
(this=0x7fffe2f0, __in_chrg=)
at /usr/include/c++/8/bits/fs_path.h:208
#9  0x6230 in main () at testpath.cpp:5
(gdb) quit
A debugging session is active.

Inferior 1 [process 2414] will be killed.

Quit anyway? (y or n) y

** Affects: gcc-8 (Ubuntu)
 Importance: Undecided
 Status: New

** Package changed: gcc-7 (Ubuntu) => gcc-8 (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824721

Title:
  g++-8 in disco is broken with libstdc++6 from gcc9 and libstdc++fs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-8/+bug/1824721/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1721215] Re: Fails to start with Ubuntu 17.10: undefined symbol tgetent

[Roger Leigh]

Note that I also see the issue with OpenJDK8 as well. But it works with
Oracle JDK9.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1721215

Title:
  Fails to start with Ubuntu 17.10: undefined symbol tgetent

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gradle/+bug/1721215/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1721215] [NEW] Fails to start with Ubuntu 17.10: undefined symbol tgetent

[Roger Leigh]

Public bug reported:

% java -version
openjdk version "9-Ubuntu"
OpenJDK Runtime Environment (build 9-Ubuntu+0-9b181-4)
OpenJDK 64-Bit Server VM (build 9-Ubuntu+0-9b181-4, mixed mode)

% gradle
java: symbol lookup error: /usr/lib/jni/libnative-platform-curses.so: undefined 
symbol: tgetent
% gradle -help
java: symbol lookup error: /usr/lib/jni/libnative-platform-curses.so: undefined 
symbol: tgetent

Maybe it's similar to the previous occurence in
https://bugs.launchpad.net/ubuntu/+source/gradle/+bug/1238322 ?

** Affects: gradle (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1721215

Title:
  Fails to start with Ubuntu 17.10: undefined symbol tgetent

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gradle/+bug/1721215/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1632954] Re: Error building schroot with Clang 3.8

[Roger Leigh]

Thanks, I'll take a look into this.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1632954

Title:
  Error building schroot with Clang 3.8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/schroot/+bug/1632954/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1398569] Re: schroot overlay v2 support

[Roger Leigh]

If any of these changes require merging upstream, please could you
forward a patch to the Debian BTS or open a PR against
https://github.com/codelibre-net/schroot

Thanks,
Roger

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1398569

Title:
  schroot overlay v2 support

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/schroot/+bug/1398569/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1320534] Re: sbuild fails under systemd-boot

[Roger Leigh]

There is no solution at present; these are generated at buildtime for
the host OS, so don't vary at runtime.  That said, it would help to know
what's different between upstart and systemd here.  What's failing
exactly, and why?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1320534

Title:
  sbuild fails under systemd-boot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/schroot/+bug/1320534/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1259153] Re: [MIR] schroot (and lockdev)

[Roger Leigh]

All the above is on the schroot-1.6 git branch; 1.7 is on the master
branch.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1259153

Title:
  [MIR] schroot (and lockdev)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lockdev/+bug/1259153/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1259153] Re: [MIR] schroot (and lockdev)

[Roger Leigh]

Regarding the timescale, schroot development isn't really done in mind
for Ubuntu freezes.  The 1.7.x series is being (roughly) aimed at jessie
for a stable 1.8 release.  However, we can certainly try to accomodate
them.

Note that I have backported the lockdev removal to schroot 1.6.  cmake
building was already backported, and this included dh9 and parallel and
verbose build support in addition, as well as using hardening defaults.
Note hardening was already enabled in Debian TTBOMK; maybe worth
checking you weren't getting a false positive there, since I did see
incorrect warnings previously, or maybe it's just not in the version
you're using.

I will make a schroot 1.6.6 upload to Debian unstable after some further
testing, which should give you all the above features.  There are a few
minor niggles to sort out, so hopefully later this week.

Regarding the missing symbols file, I have looked at adding one, but
doing this for C++ looks quite intimidating.  I'll be happy to add one,
but might need a little assistance to do so.  This will certanly become
more important for 1.7/1.8 which switches to using a shared library from
the existing static library.

Regards,
Roger

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1259153

Title:
  [MIR] schroot (and lockdev)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lockdev/+bug/1259153/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1259153] Re: [MIR] schroot (and lockdev)

[Roger Leigh]

Please see http://people.debian.org/~rleigh/schroot/schroot_1.6.6-1.dsc
(distribution of git commit fe9f3fa on schroot-1.6).  It should cover
most of the points raised above (with the exception of symbols files).

Is there anything additional you'd like in this release (either missing
stuff, stuff you would like changing or improving)?  If not, this will
be released as 1.6.6-1 after further testing.


Thanks,
Roger

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1259153

Title:
  [MIR] schroot (and lockdev)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lockdev/+bug/1259153/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1259153] Re: [MIR] schroot (and lockdev)

[Roger Leigh]

Note that current development (1.7.x releases, in experimental) have
dropped the lockdev dependency.  And we're actively removing the lockdev
rdeps to allow lockdev removal for jessie.  We also updated to dh9 and
cmake for building.

Regards,
Roger

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1259153

Title:
  [MIR] schroot (and lockdev)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lockdev/+bug/1259153/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 917339] Re: 10mount: umount: /CHROOT/dev: device is busy

[Roger Leigh]

Brian Murray:
 I wonder if this is related to bug 1223576 at all.

I would highly suspect so; schroot has been plagued with lvremove
failures for some time, and this looks like a likely candidate for why
lvremove was failing--all the symptoms are suspiciously similar.  If so,
I'll be very happy--not being able to do anthing to fix it myself was
quite frustrating.


Regards,
Roger

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/917339

Title:
  10mount: umount: /CHROOT/dev: device is busy

To manage notifications about this bug go to:
https://bugs.launchpad.net/schroot/+bug/917339/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1093973] Re: schroot overwrites files in guest system without announcement or backup

[Roger Leigh]

This issue is already being tracked in the following bug reports:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=565613
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=557730

Note that this has been the default behaviour since schroot was written.
What has changed which might have affected you is that older versions
had the option to disable the setup scripts for all chroot types; they
are now always run for all types except plain (which is identical to
directory except that no setup scripts are run).  Note that this is
only the /default/ behaviour--what's copied is entirely configurable if
this does not meet your needs.

This is definitely a problem, but it's not entirely clear what the best
solution (or set of solutions) we need.  Most chroot environments need
the NSS databases syncing from the host, or else the entries for the
current user etc. won't be present.  The purpose of schroot is to
automate this, rather than requiring manual updates by the admin.  This
works fine until you want something different in the chroot, or you add
things inside the chroot which are then subsequently lost; however,
synchronising this data one (or two) ways between the host and guest is
decidedly non-trivial.

For the time being, it's simple enough to disable the behaviour: just
edit /etc/schroot/$profile/nssdatabases (and/or copyfiles) and comment
out the databases/files you don't want to be copied.  Or you could
create your own custom profile rather than modifiying one of the pre-
canned profiles.

I'll look at making your suggested changes to the documentation.

If you could follow up to the original Debian reports rather than here,
that would be appreciated.  Thanks.


Regards,
Roger

** Bug watch added: Debian Bug tracker #565613
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=565613

** Bug watch added: Debian Bug tracker #557730
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=557730

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1093973

Title:
  schroot overwrites files in guest system without announcement or
  backup

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/schroot/+bug/1093973/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1070008] Re: schroot session recovery mounts $device, not $mount-device, for LVM snapshots

[Roger Leigh]

You can now get 1.6.4-2 from Debian unstable or from git

http://anonscm.debian.org/gitweb/?p=buildd-tools/schroot-
dist.git;a=commit;h=8088a3b7e003546e3315957f6091553f4d2136ad

http://anonscm.debian.org/gitweb/?p=buildd-
tools/schroot.git;a=commit;h=5fbab5b020922a454a1a8824ee6920e0ea26e088

(release tarball is distribution/schroot-1.6.4; delta for the -2 release
is debian/schroot-1.6.4-1..debian/schroot-1.6.4-2)


Regards,
Roger

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1070008

Title:
  schroot session recovery mounts $device, not $mount-device, for LVM
  snapshots

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/schroot/+bug/1070008/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1070008] Re: schroot session recovery mounts $device, not $mount-device, for LVM snapshots

[Roger Leigh]

Thanks.

I can reproduce this with 1.6.3.  Still working out where this is
happening though.

- it's set correctly in the session file (as you've shown)
- it's also set correctly on loading (again with --config/--info, so no 
serialisation errors)

So something subtle is happening after that, but prior to running the
setup scripts.  I'll investigate this more to find out where this
occurs.  Possibly some odd interaction between the chroot facets, or
something triggering a call to
sbuild::chroot_facet_mountable::set_mount_device() which is ultimately
where this problem lies.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1070008

Title:
  schroot session recovery mounts $device, not $mount-device, for LVM
  snapshots

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/schroot/+bug/1070008/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1070008] Re: schroot session recovery mounts $device, not $mount-device, for LVM snapshots

[Roger Leigh]

Unwanted side effect of cloning; triggered by the copy constructor
chaining up to the block_device_base ctor, which calls set_device, which
then calls chroot_facet_mountable::set_mount_device.

(gdb) run --recover-session -c snaptest
Starting program: /home/rleigh/schroot/bin/schroot/schroot --recover-session -c 
snaptest
[Thread debugging using libthread_db enabled]
Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1.

Breakpoint 1, sbuild::session::set_user_options (this=0x54b830, 
user_options=...) at sbuild-session.cc:330
330   this-user_options = user_options;
(gdb) break sbuild::chroot_facet_mountable::set_mount_device
Breakpoint 2 at 0x4ad960: file sbuild-chroot-facet-mountable.cc, line 74.
(gdb) c
Continuing.

Breakpoint 2, sbuild::chroot_facet_mountable::set_mount_device (this=0x595e20, 
mount_device=...) at sbuild-chroot-facet-mountable.cc:74
74this-mount_device = mount_device;
(gdb) bt
#0  sbuild::chroot_facet_mountable::set_mount_device (this=0x595e20, 
mount_device=...) at sbuild-chroot-facet-mountable.cc:74
#1  0x004a58a5 in sbuild::chroot_block_device_base::set_device (
this=this@entry=0x595b20, device=...)
at sbuild-chroot-block-device-base.cc:83
#2  0x004a595f in 
sbuild::chroot_block_device_base::chroot_block_device_base (this=0x595b20, 
rhs=...) at sbuild-chroot-block-device-base.cc:54
#3  0x004a7d35 in sbuild::chroot_lvm_snapshot::chroot_lvm_snapshot (
this=0x595b20, rhs=...) at sbuild-chroot-lvm-snapshot.cc:50
#4  0x004a7f31 in sbuild::chroot_lvm_snapshot::clone (this=0x586550)
at sbuild-chroot-lvm-snapshot.cc:61
#5  0x004634f3 in sbuild::session::run_impl (this=0x54b830)
at sbuild-session.cc:660
#6  0x0045e7d4 in sbuild::session::run (this=0x54b830)
at sbuild-session.cc:585
#7  0x0042b77f in schroot::main_base::run_impl (this=0x7fffe9e0)
at schroot-main-base.cc:360
#8  0x0041988a in schroot_base::main::run (this=0x7fffe9e0, 
argc=optimized out, argv=0x7fffeb78) at schroot-base-main.cc:107
#9  0x00414bef in runschroot::options, schroot::main (
argv=0x7fffeb78, argc=4)
at ../../bin/schroot-base/schroot-base-run.h:69
#10 main (argc=4, argv=0x7fffeb78) at schroot.cc:43

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1070008

Title:
  schroot session recovery mounts $device, not $mount-device, for LVM
  snapshots

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/schroot/+bug/1070008/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1070008] Re: schroot session recovery mounts $device, not $mount-device, for LVM snapshots

[Roger Leigh]

We do in fact already take steps to ensure we don't call this when using
LVM snapshots to avoid the exact issue that you've reported.  However,
it looks like in your case this is not working.  As you can see,
set_mount_device should be called for all chroot types /except/ lvm-
snapshot (where the dynamic_cast will fail)...

sbuild::chroot_block_device_base::set_device():

  /// @todo: This may not be appropriate for derived classes such as
  /// lvm_snapshot, since re-setting the device could overwrite the
  /// mount device.
  chroot_facet_mountable::ptr pmnt
(get_facetchroot_facet_mountable());
#ifdef SBUILD_FEATURE_LVMSNAP
  if (!dynamic_castchroot_lvm_snapshot *(this))
#endif
pmnt-set_mount_device(this-device);

and preprocessed:

void
chroot_block_device_base::set_device (std::string const device)
{
  if (!is_absname(device))
throw error(device, DEVICE_ABS);

  this-device = device;



  chroot_facet_mountable::ptr pmnt
(get_facetchroot_facet_mountable());

  if (!dynamic_castchroot_lvm_snapshot *(this))

pmnt-set_mount_device(this-device);
}

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1070008

Title:
  schroot session recovery mounts $device, not $mount-device, for LVM
  snapshots

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/schroot/+bug/1070008/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1070008] Re: schroot session recovery mounts $device, not $mount-device, for LVM snapshots

[Roger Leigh]

OK, so this check is failing.  dynamic_cast() is returning null
because this is being called from the constructor, and the vptr during
this stage of construction does not contain the information about the
derived class.  So we end up setting the mount device inappropriately.

This was working previously.  I can only assume that this is a change
due to a GCC upgrade, though it appears to affect both 4.6 and 4.7.

The code is definitely not following the letter of the C++ standard, so
it will require refactoring to remove this logic entirely.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1070008

Title:
  schroot session recovery mounts $device, not $mount-device, for LVM
  snapshots

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/schroot/+bug/1070008/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1070008] Re: schroot session recovery mounts $device, not $mount-device, for LVM snapshots

[Roger Leigh]

This is now being tracked in Debian bug #691376.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1070008

Title:
  schroot session recovery mounts $device, not $mount-device, for LVM
  snapshots

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/schroot/+bug/1070008/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1070008] Re: schroot session recovery mounts $device, not $mount-device, for LVM snapshots

[Roger Leigh]

http://anonscm.debian.org/gitweb/?p=buildd-
tools/schroot.git;a=commitdiff;h=02fa2aefc24e95852aa991f720b3c9dc53583d1c

Note that this patch needs backporting to the schroot-1.6 branch and
testing with all block-device-using chroot types before I would
recommend applying it.  **Please do not apply this until it is fully
tested.**

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1070008

Title:
  schroot session recovery mounts $device, not $mount-device, for LVM
  snapshots

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/schroot/+bug/1070008/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1070008] Re: schroot session recovery mounts $device, not $mount-device, for LVM snapshots

[Roger Leigh]

I'm not sure this is of low severity.  I've marked this as serious in
the Debian bug since it could allow a user to gain unauthorised root
access to the source volume (if they were a root user for the snapshot),
and potentially result in dataloss if the user didn't realise they were
not using the snapshot.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1070008

Title:
  schroot session recovery mounts $device, not $mount-device, for LVM
  snapshots

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/schroot/+bug/1070008/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1070008] Re: schroot session recovery mounts $device, not $mount-device, for LVM snapshots

[Roger Leigh]

Could you please provide the session file, from
/var/lib/schroot/session?  The original config from /etc/schroot would
also be useful.

schroot --config -c chroot:$origchroot -c session:$session

will provide both of these.  If it's not Ubuntu-specific, the Debian BTS
would also be more appropriate.


Thanks,
Roger

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1070008

Title:
  schroot session recovery mounts $device, not $mount-device, for LVM
  snapshots

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/schroot/+bug/1070008/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 753541] Re: lvm schroots 'not created with udev' error messages

[Roger Leigh]

I've not yet seen any evidence that the underlying LVM issues have been
fixed, so I am not fully convinced that this is yet resolved.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/753541

Title:
  lvm schroots 'not created with udev' error messages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/schroot/+bug/753541/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 932478] Re: schroot recreates stale bind mounts upon system start

[Roger Leigh]

Note that schroot = 1.5.2 (1.6.0 stable release forthcoming in the next
week or so) also have an option in /etc/default/schroot to end sessions
on system shutdown.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/932478

Title:
  schroot recreates stale bind mounts upon system start

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/schroot/+bug/932478/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 791908] Re: Schroot doesn't mount /home submounts in the chroot

[Roger Leigh]

We can't use rbind due to it interacting very badly with autofs
(rbinding autofs mountpoints results in umountable mounts, which
eventually kill your system).  We used to use rbind, but removed it as a
result.

Once the kernel is fixed to allow rbind to work safely, we can re-enable
this.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/791908

Title:
  Schroot doesn't mount /home submounts in the chroot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/schroot/+bug/791908/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 917339] Re: 10mount: umount: /CHROOT/dev: device is busy

[Roger Leigh]

This bug report does not mention exactly what the device is which
couldn't be umounted.  Note that if we can't umount, we don't end the
session, or else we could end up leaking resources e.g. LVM snapshots,
which would also be quite annoying.

Please could you provide: the result of 'cat /proc/mounts' when you
reproduce the problem.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/917339

Title:
  10mount: umount: /CHROOT/dev: device is busy

To manage notifications about this bug go to:
https://bugs.launchpad.net/schroot/+bug/917339/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 917339] Re: 10mount: umount: /CHROOT/dev: device is busy

[Roger Leigh]

Also, as the message stated, the output of 'lsof' would also be helpful.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/917339

Title:
  10mount: umount: /CHROOT/dev: device is busy

To manage notifications about this bug go to:
https://bugs.launchpad.net/schroot/+bug/917339/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 840061] Re: schroot cant mount large file

[Roger Leigh]

schroot has had large file support since 1.4.22-1.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/840061

Title:
  schroot cant mount large file

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/schroot/+bug/840061/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 753541] Re: lvm schroots 'not created with udev' error messages

[Roger Leigh]

While schroot uses lvcreate/lvremove, it is not itself responsible for
any lvm issues.  This is not a schroot bug, and should be reassigned to
lvm2/dmsetup/udev as appropriate.

Also, is this still reproducible, or is it fixed with new upstream
versions of the above?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/753541

Title:
  lvm schroots 'not created with udev' error messages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/schroot/+bug/753541/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 744451] Re: Needs automount support

[Roger Leigh]

Note that we will happily include additional setup scripts in schroot.
However, since I look at the Ubuntu bug tracker about once every 2
years, it's much better to just send them to us directly, or file a bug
in the Debian BTS!

Note that the 1.5.x (and shortly forthcoming 1.6.0) releases add the
ability to run regular /etc/init.d services in the script, by starting
and stopping them when you create and end a session.  So it's possible
to use the regular packaged services.  It also adds support for user-
defined configuration keys, so the automount configuration could be put
directly into your schroot.conf chroot definition.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/744451

Title:
  Needs automount support

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/schroot/+bug/744451/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 744265] Re: schroot does not read files in /etc/schroot/chroot.d/

[Roger Leigh]

This was fixed (read: documented) in 1.4.1-1 over 2 years ago.  Should
this be closed?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/744265

Title:
  schroot does not read files in /etc/schroot/chroot.d/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/schroot/+bug/744265/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 744264] Re: schroot can't handle unionfs

[Roger Leigh]

This should really be added as a separate union type, since unionfs and
unionfs-fuse require different logic.

I'll be happy to include such a feature.  Please mail the patch to the
upstream mailing list or file a bug in the Debian BTS.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/744264

Title:
  schroot can't handle unionfs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/schroot/+bug/744264/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 769595] Re: Encrypted home not mountable under chroot

[Roger Leigh]

Note that we don't currently enable rbind by default due to it
interacting badly with autofs.  See the other bugs about this.
https://bugs.launchpad.net/ubuntu/+source/schroot/+bug/791908

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/769595

Title:
  Encrypted home not mountable under chroot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dchroot/+bug/769595/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 723054] Re: Intermittently fails to recognize file system

[Roger Leigh]

Are you using lvm-snapshot chroots with schroot?

If this is the case, is the snapshot device mounted in your filesystem?
If so, and the filesystem is dirty, i.e. you are making changes to it
while you are snapshotting, or there are pending changes not yet written
to disc, then the filesystem will be in an inconsistent state in the
snapshot, and it may fail to mount.

If this is the case, the solution is to not mount the device being
snapshotted.  This way, the filesystem will always be mountable.  Note
that there is a contrib schroot setup script, 09fsck, to fsck the
snapshot before mount.  It's a workaround, but I wouldn't recommend it
unless you had no other choice.


Regards,
Roger
(Debian maintainer of sbuild and schroot)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/723054

Title:
  Intermittently fails to recognize file system

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 605581] Re: schroot fails to use files in /etc/schroot/chroot.d/

[Roger Leigh]

Update: the naming rules have been relaxed in current stable releases
(1.4.16+) so the filenames above will now work correctly again.

Regards,
Roger

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/605581

Title:
  schroot fails to use files in /etc/schroot/chroot.d/

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 605581] Re: schroot fails to use files in /etc/schroot/chroot.d/

[Roger Leigh]

** Changed in: schroot (Ubuntu)
   Status: New = Fix Released

** Changed in: schroot (Ubuntu)
 Assignee: (unassigned) = Roger Leigh (rleigh)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/605581

Title:
  schroot fails to use files in /etc/schroot/chroot.d/

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 486944] Re: Different permission denied errors

[Roger Leigh]

** Changed in: schroot (Ubuntu)
   Status: New = Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/486944

Title:
  Different permission denied errors

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 637597] Re: schroot will not allow multiple user login to chroot

[Roger Leigh]

The chroot definition contains these lines for access control:

root-users=scott,lwhitney
users=lwhitney,scott,coboluser
groups=cobolusers

These control who is permitted to /start/ a session.  So, if user scott 
starts a new session,
then they will become the owner of that session.  In the session file, you'll 
just get something like

root-users=scott
users=
groups=
root-groups=

This is intended to give a measure of privacy between session users, and 
prevent users from deleting each other's sessions.
In the future, I'd like to give session owners the ability to grant others 
access to their sessions (effectively, to modify the above lines in the session 
file).  However, I'm not yet sure of the best interface for doing that, be it 
new command-line options or some other mechanism.  Any suggestions would be 
helpful.


Regards,
Roger

-- 
schroot will not allow multiple user login to chroot
https://bugs.launchpad.net/bugs/637597
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 605581] Re: schroot fails to use files in /etc/schroot/chroot.d/

[Roger Leigh]

Ryan,

This is exactly the cause of the problem.  From schroot(1):

   /etc/schroot/chroot.d
  Additional  chroot definitions may be placed in files under this
  directory.  They are treated in  exactly  that  same  manner  as
  /etc/schroot/schroot.conf.   Each  file  may contain one or more
  chroot definitions.  Note that the files in this directory  fol‐
  low  the  same  naming  rules  as run-parts(8) when run with the
  --lsbsysinit option.

This means the file can't contain '.'s, or appear as though it's an
editor backup file or backup dpkg conffile.

The Ubuntu version is outdated WRT Debian, but this documentation was
added for 1.4.0.


Regards,
Roger
(upstream author)

-- 
schroot fails to use files in /etc/schroot/chroot.d/
https://bugs.launchpad.net/bugs/605581
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 486944] Re: Different permission denied errors

[Roger Leigh]

Just for the record, Brian brought this up on debian-devel back in March in 
this thread:
  http://lists.debian.org/debian-devel/2010/03/msg00298.html

This is a serious bug in gcrypt/gnutls.  These libraries are modifying
global process state in a very intrusive and unjustified way, in this
case dropping root privs when you do a simple NSS passwd/group database
lookup(!)  This isn't something that can be fixed in schroot; please
could you reassign it to libgcrypt.

I hope that in the future, pam_ldap can use a library other than
gcrypt/gnutls given its severe brokenness and upstream cluelessness.


Regards,
Roger

** Branch linked: lp:ubuntu/libgcrypt11

-- 
Different permission denied errors
https://bugs.launchpad.net/bugs/486944
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 486944] Re: Different permission denied errors

[Roger Leigh]

Hmm, I didn't appear to be notified of your replies, so didn't notice
them until now.

It's looking very much like schroot is not being run with full effective
root permissions, despite being correctly setuid-root as intended.  Are
you using anything which could override this?  For example, mandatory
access controls as provided by SELinux or AppArmor.  TTBOMK we aren't in
the SELinux policy, so this could be a source of privilege restriction.
If this is the case, then this needs sorting out with the SELinux people
(I haven't got the knowledge to help here, sorry).


Regards,
Roger

-- 
Different permission denied errors
https://bugs.launchpad.net/bugs/486944
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 486944] Re: Different permission denied errors

[Roger Leigh]

Hi,

(I'm the upstream author and Debian maintainer.)

 Failed to lock chroot: /var/lib/schroot/session/sid-9a6aa3bc-6afc-
4eda-9924-ec90cfee2a8a: Failed to write session file: Permission denied

This is independent from any of your LVM setup, I think, being a
filesystem ownership/permissions failure.  Note that schroot is setuid
root (or else it won't be able to chroot(2)), so root must be able to
write to every directory under /var/lib/schroot.  It must also be able
to lock the files with fcntl(2), so your filesystem must support this
(most do unless you use something very exotic).

 drwx-- 2 root root 220 2009-11-23 14:42 /dev/sys11
This looks wrong.  I have 0755 perms on mine.  However, since all the mounting 
of the filesystems is done as root, this shouldn't in an of itself cause a 
failure.

 sudo schroot -c sid
   Volume group mapper not found
  /etc/schroot/setup.d/90passwd: 2: cannot create  
  /var/lib/schroot/mount/sid-7d92b549-39ec-4668-8d04-742e6428eb62/etc/passwd: 
  Directory nonexistent
  E: sid-7d92b549-39ec-4668-8d04-742e6428eb62: Chroot setup failed: 
 stage=setup-start
This looks like one or more of the parent directories are nonexistent.  Does 
/etc exist in the chroot.  Did anything get mounted on 
/var/lib/schroot/mount/sid-7d92b549-39ec-4668-8d04-742e6428eb62/ ?

 getent passwd brian  ${CHROOT_PATH}/etc/passwd
Note that the default 20nssdatabases script sets the passwd database using 
getent, so this is unnecessary.  If you want to restrict it to a subset of 
users, that's something we could add to the script as a customisable option 
(patch welcome).

So far, it's looking like it's probably an ownership or permissions
problem on /var/lib/schroot and/or its main subdirectories.  They should
all be 0755 and files should be 0644 in the session dir.

Note that if you run schroot with -v as well as --debug=info, you'll get
diagnostics from the setup scripts which you haven't got in your case.
Re-testing with -v as well would be useful.


BTW, there was a new release of schroot, 1.4.0 a couple of days back.  In 
Debian unstable, no idea about Ubuntu.  Possibly worth trying if you haven't 
had any success to date.


Regards,
Roger

-- 
Different permission denied errors
https://bugs.launchpad.net/bugs/486944
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 54867] Re: Fails when /etc/resolv.conf is set for dynamic updates

[Roger Leigh]

I would be interested to know if this still affects the current stable
1.2.3 release, and additionally the new stable 1.4.0 release.

I'm using resolvconf (and hence a symlinked /etc/resolv.conf) on my
*host* system, and resolv.conf is successfully copied into the chroot.

If /etc/resolv.conf is a symlink *inside* the chroot, then cp will copy
to the file pointed to by the symlink.  This is the default behaviour of
cp, and I see nothing in the manpage to tell it to not dereference the
destination (you can for the source).  Hence if the symlink is invalid,
the copy will fail.  It's not clear this is a bug in schroot, or rather
a broken symlink in the chroot causing problems.

If there's a way to make cp snap links for the destination, this is
something we can add.  However, if the admin deliberately symlinked
/etc/resolv.conf to somewhere else for their own reasons, this behaviour
would be equally wrong.  It's not clear that the current behaviour is
actually wrong /per se/ except for the special case that the symlink is
invalid (points to nowhere).


Regards,
Roger

-- 
Fails when /etc/resolv.conf is set for dynamic updates
https://bugs.launchpad.net/bugs/54867
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 54867] Re: Fails when /etc/resolv.conf is set for dynamic updates

[Roger Leigh]

I would be interested to know if this still affects the current stable
1.2.3 release, and additionally the new stable 1.4.0 release.

I'm using resolvconf (and hence a symlinked /etc/resolv.conf) on my
*host* system, and resolv.conf is successfully copied into the chroot.

If /etc/resolv.conf is a symlink *inside* the chroot, then cp will copy
to the file pointed to by the symlink.  This is the default behaviour of
cp, and I see nothing in the manpage to tell it to not dereference the
destination (you can for the source).  Hence if the symlink is invalid,
the copy will fail.  It's not clear this is a bug in schroot, or rather
a broken symlink in the chroot causing problems.

If there's a way to make cp snap links for the destination, this is
something we can add.  However, if the admin deliberately symlinked
/etc/resolv.conf to somewhere else for their own reasons, this behaviour
would be equally wrong.  It's not clear that the current behaviour is
actually wrong /per se/ except for the special case that the symlink is
invalid (points to nowhere).


Regards,
Roger

-- 
Fails when /etc/resolv.conf is set for dynamic updates
https://bugs.launchpad.net/bugs/54867
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 291312] [NEW] broken dependencies from cupsys-cups transition

[Roger Leigh]

Public bug reported:

Version: 5.2.0~rc1-0ubuntu1

debian/control: cups-driver-gutenprint

Depends: ${shlibs:Depends}, perl (= 5.8.0), cups (= 1.2.5) | cups (= 1.2.5)
Replaces: cupsys-driver-gutenprint (= 5.1.99), cups-driver-gimpprint, 
cups-driver-gimpprint-data
Conflicts: cupsys-driver-gutenprint (= 5.1.99), cups-driver-gimpprint

A global search and replace s/cupsys/cups/g has screwed up at least
these dependencies.  The depends line contains duplicate deps, and cups-
dfriver-gimpprint* never existed and should be cupsys-driver-gimpprint*.


Regards,
Roger

** Affects: gutenprint (Ubuntu)
 Importance: Undecided
 Status: New

-- 
broken dependencies from cupsys-cups transition
https://bugs.launchpad.net/bugs/291312
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 135397] Re: schroot crash at login for dapper

[Roger Leigh]

I'm not entirely sure I am getting the point of this bug.  Is there a
bug at all here?

schroot gets the login shell from the passwd database using
getpwuid/getpwnam.  In the first case, it appears that the shell is set
to /usr/bin/schroot, which unsurprisingly doesn't exist inside the
chroot, so the session fails.  In the second case, it's running a bash
login shell (I'm assuming a different passwd database here, or there is
a nasty bug!), though I'm not sure where the sudo message comes from
unless you added some sudo use to your .bash_profile or something.

Regards,
Roger

-- 
schroot crash at login for dapper
https://bugs.launchpad.net/bugs/135397
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 54867] Re: Fails when /etc/resolv.conf is set for dynamic updates

[Roger Leigh]

Just to clarify, are you running resolvconf inside the chroot, outside
the chroot, or both?

Is /etc/resolv.conf a symlink inside or outside the chroot, or both?

Currently we don't support resolvconf or anything else that is
dynamically updating resolv.conf, like NetworkManager.  Suggestions for
how to handle this properly would be much appreciated.


Thanks,
Roger

-- 
Fails when /etc/resolv.conf is set for dynamic updates
https://bugs.launchpad.net/bugs/54867
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 52465] Re: [libgcc1] segfault on ppc when unwinding stack (c++ exceptions, mono exceptions)

[Roger Leigh]

Matthias,

Also see:
http://librarian.launchpad.net/3303410/buildlog_ubuntu-edgy-powerpc.schroot_0.99.2-2ubuntu1_FAILEDTOBUILD.txt.gz

The testsuite fails for all tests throwing exceptions.  The above test I
wrote is just a minimal testcase for that.  Most package builds don't
throw exceptions, so this will only show up at runtime for them.

-- 
[libgcc1] segfault on ppc when unwinding stack (c++ exceptions, mono exceptions)
https://launchpad.net/bugs/52465

--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 52465] Re: [libgcc1] segfault on ppc when unwinding stack (c++ exceptions, mono exceptions)

[Roger Leigh]

From the build log toolchain package versions: g++-4.1_4.1.1-2ubuntu5

It may just be an outdated buildd chroot, and the bug is already fixed?

-- 
[libgcc1] segfault on ppc when unwinding stack (c++ exceptions, mono exceptions)
https://launchpad.net/bugs/52465

--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 52465] Re: [libgcc1] segfault on ppc when unwinding stack (c++ exceptions, mono exceptions)

[Roger Leigh]

From the build log toolchain package versions: g++-4.1_4.1.1-2ubuntu5

It may just be an outdated buildd chroot, and the bug is already fixed?

-- 
[libgcc1] segfault on ppc when unwinding stack (c++ exceptions, mono exceptions)
https://launchpad.net/bugs/52465

--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 29696] Re: High quality photo printing broken

[Roger Leigh]

Have your tried with the newer Gutenprint driver?  This is the package
cupsys-driver-gutenprint (in dapper and edgy only).  It has much
improved colour quality.

The escputil tool will let you print a test pattern out to check for
blocked nozzles in the printhead.  It will also do head alignment and
cleaning.

Spurious characters printing indicate a bad printer connection, e.g.
intermittent connection in the parallel port contacts or a broken wire.

-- 
High quality photo printing broken
https://launchpad.net/bugs/29696

--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs