Bug#993391: [pkg-lxc-devel] Bug#993391: lxc: Unprivileged lxc example from README.Debian.gz gives AppArmor error "Failed to mount proc"

[pk]

> Creation is necessary as you need a valid rootfs to work, and a valid
> rootfs for an unprivileged container has to fit the usernamespace which
> will be created upon startup of the container. "/" is not a valid rootfs
> for an unprivileged container as the uid mappings are totally out of
> line. You therefore need to at least create one container using
> lxc-create or manually create a rootfs using mmdebstrap or whatever fits
> best.

Thank you. How do I close this report?

Bug#993391: [pkg-lxc-devel] Bug#993391: lxc: Unprivileged lxc example from README.Debian.gz gives AppArmor error "Failed to mount proc"

[pk]

Can you post your complete config for autopkgtest-lxc-xwkkud,
autopkgtest-unstable or other working unpriv container? Your output
reads "unprivileged true".

Thanks

Bug#993391: lxc: Unprivileged lxc example from README.Debian.gz gives AppArmor error "Failed to mount proc"

[pk]

Hello,

I copy-pasted configuration and commands from
/usr/share/doc/lxc/README.Debian.gz under "Unprivileged containers".
Are you talking about another file?
https://salsa.debian.org/lxc-team/lxc/-/blob/7d692c266c63fced9417042ae904cc2a280b96d8/debian/README.Debian

lxc.rootfs defaults to the system root / per lxc.container.conf(5).

Creation is unnecessary, it is just a convenience to avoid -f and does
not affect the container runtime. My (still privileged) lxc setup
works perfectly with -f without ever creating any containers.

I pasted full logs above. Please try to be respectful and helpful, do
not reproduce on a configured machine, and leave bug triaging to the
lxc experts.

Thanks,

Bug#993391: lxc: Unprivileged lxc example from README.Debian.gz gives AppArmor error "Failed to mount proc"

[pk]

Thank you for answering. kernel.unprivileged_userns_clone = 1 on my
machine and on the Live DVD. All instructions of the README.Debian.gz
were followed.

To rule out machine-specific misconfiguration, this log is from the
Live DVD, Debian 11.0 AMD64 Standard:



Warning: Permanently added '[localhost]:12346' (ECDSA) to the list of
known hosts.
user@localhost's password:
Linux debian 5.10.0-8-amd64 #1 SMP Debian 5.10.46-4 (2021-08-03) x86_64

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
user@debian:~$ sudo su -l
root@debian:~# apt-get update ; apt-get install lxc
[snip]
root@debian:~# sysctl kernel.unprivileged_userns_clone
kernel.unprivileged_userns_clone = 1
root@debian:~# grep user /etc/subuid /etc/subgid
/etc/subuid:user:10:65536
/etc/subgid:user:10:65536
root@debian:~#
logout
user@debian:~$ mkdir -p .local/share/lxc
user@debian:~$ chmod +x . .local .local/share
user@debian:~$
user@debian:~$ cat > test_config
  lxc.idmap = u 0 10 65536
  lxc.idmap = g 0 10 65536
  lxc.mount.auto = proc:mixed sys:ro cgroup:mixed
  lxc.apparmor.profile = unconfined
user@debian:~$
user@debian:~$   systemd-run --scope --quiet --user
--property=Delegate=yeslxc-start --logfile /dev/stderr -f
test_config -n machine
lxc-start machine 20210901150740.103 ERRORutils -
utils.c:safe_mount:1204 - Permission denied - Failed to mount "proc"
onto "/proc"
lxc-start machine 20210901150740.104 ERRORconf -
conf.c:lxc_mount_auto_mounts:681 - Permission denied - Failed to mount
"proc" on "/proc" with flags 14
lxc-start machine 20210901150740.104 ERRORconf -
conf.c:lxc_setup:3330 - Failed to setup first automatic mounts
lxc-start machine 20210901150740.105 ERRORstart -
start.c:do_start:1218 - Failed to setup container "machine"
lxc-start machine 20210901150740.106 ERRORsync -
sync.c:__sync_wait:36 - An error occurred in another process (expected
sequence number 5)
lxc-start machine 20210901150740.106 ERRORstart -
start.c:__lxc_start:1999 - Failed to spawn container "machine"
lxc-start machine 20210901150740.107 ERRORlxccontainer -
lxccontainer.c:wait_on_daemonized_start:859 - Received container state
"ABORTING" instead of "RUNNING"
lxc-start: machine: lxccontainer.c: wait_on_daemonized_start: 859
Received container state "ABORTING" instead of "RUNNING"
lxc-start machine 20210901150740.108 ERRORlxc_start -
tools/lxc_start.c:main:308 - The container failed to start
lxc-start: machine: tools/lxc_start.c: main: 308 The container failed to start
lxc-start machine 20210901150740.108 ERRORlxc_start -
tools/lxc_start.c:main:311 - To get more details, run the container in
foreground mode
lxc-start: machine: tools/lxc_start.c: main: 311 To get more details,
run the container in foreground mode
lxc-start machine 20210901150740.108 ERRORlxc_start -
tools/lxc_start.c:main:313 - Additional information can be obtained by
setting the --logfile and --logpriority options
lxc-start: machine: tools/lxc_start.c: main: 313 Additional
information can be obtained by setting the --logfile and --logpriority
options
user@debian:~$  sudo su -l
root@debian:~# dmesg | tail
[  294.416862] audit: type=1400 audit(1630508543.972:7):
apparmor="STATUS" operation="profile_replace" info="same as current
profile, skipping" profile="unconfined" name="lsb_release" pid=2444
comm="apparmor_parser"
[  294.526095] audit: type=1400 audit(1630508544.084:8):
apparmor="STATUS" operation="profile_load" profile="unconfined"
name="/usr/bin/man" pid=2442 comm="apparmor_parser"
[  294.527098] audit: type=1400 audit(1630508544.084:9):
apparmor="STATUS" operation="profile_load" profile="unconfined"
name="man_filter" pid=2442 comm="apparmor_parser"
[  294.528359] audit: type=1400 audit(1630508544.084:10):
apparmor="STATUS" operation="profile_load" profile="unconfined"
name="man_groff" pid=2442 comm="apparmor_parser"
[  297.864908] audit: type=1400 audit(1630508547.412:11):
apparmor="STATUS" operation="profile_load" profile="unconfined"
name="lxc-container-default" pid=2618 comm="apparmor_parser"
[  297.867516] audit: type=1400 audit(1630508547.416:12):
apparmor="STATUS" operation="profile_load" profile="unconfined"
name="lxc-container-default-cgns" pid=2618 comm="apparmor_parser"
[  297.869845] audit: type=1400 audit(1630508547.420:13):
apparmor="STATUS" operation="profile_load" profile="unconfined"
name="lxc-container-default-with-mounting" pid=2618
comm="apparmor_parser"
[  297.872902] audit: type=1400 audit(1630508547.420:14):
apparmor="STATUS" operation="profile_load" profile="unconfined"
name="lxc-container-default-with-nesting" pid=2618
comm="apparmor_parser"
[  297.933031] audit: type=1400 audit(1630508547.480:15):
apparmor="STATUS" operation="profile_load" profile="unconfined"
name="/usr/bin/lxc-s

Bug#976174: Made an itp

[Devops PK Carlisle LLC]

Thanks for responding. This is the first software I have ever submitted
for Debian, so please forgive any amateur misunderstandings regarding
the process.

- The email (below) which retitles the software notes "stopping
processing here". Should I attempt to repackage papershaper as a .deb or
is the .git sufficient? I have never compiled a .deb before.

- The entire install "process" is to
* place the contents into a folder called ~/com.pkcarlisle/papershaper
in the user home directory. There are no additions to or changes to
system level files
* check for and/or resolve dependencies for Python 3 and lynx
* (optionally) add a start up command as
python3 ~/com.pkcarlisle/papershaper/papershaper.py

If the wishlist is waiting for me to compile papershaper into a .deb I
can give it a try, but I do not want the wishlist to be waiting for
something and for me not to know about the next steps.

On 12/22/20 3:27 PM, Debian Bug Tracking System wrote:
> Processing commands for cont...@bugs.debian.org:
>
>> retitle 976174 ITP: papershaper -- automagic wallpaper swapper
> Bug #976174 [wnpp] ITP:papershaper--automagic wallpaper swapper
> Changed Bug title to 'ITP: papershaper -- automagic wallpaper swapper'
from 'ITP:papershaper--automagic wallpaper swapper'.
>> thanks
> Stopping processing here.
>
> Please contact me if you need assistance.

On 12/22/20 2:30 PM, Devops PK Carlisle LLC wrote:
> Thanks for responding.
>
> If I understand the definitions correctly, I should resubmit this as an
> RFP since it has never been included in a Debian (or other Linux) release?
>
> Being kind of careful about the definition of a package here...
>
> The software is here as a git
>
> https://github.com/pkcarlislellc/git-papershaper
>
> here as a tarball:
>
> https://sourceforge.net/projects/papershaper/
>
> It is open source licensed, and does not download anything as part of
> the install process. It has two dependencies: Python and the lynx
> browser. Python 2 and 3 versions are included in the tarball but it is
> presumed that the preferred Python version is now Python 3, so that is
> the default.
>
> It does optionally download images, but only on execution.
>
>
> On 12/22/20 1:54 PM, olivier sallou wrote:
>> You created an itp so an intent to package.
>> If not willing to propose a apckage should be an rfp request for package.
>> Ideally you package your app and propose it for review and upload.
>> Requirements are an open source license and package install should not
>> download anything.
>> Only its execution can download remote stuff.
>>
>> Olivier

Bug#976174: Made an itp

[Devops PK Carlisle LLC]

Thanks for responding.

If I understand the definitions correctly, I should resubmit this as an
RFP since it has never been included in a Debian (or other Linux) release?

Being kind of careful about the definition of a package here...

The software is here as a git

https://github.com/pkcarlislellc/git-papershaper

here as a tarball:

https://sourceforge.net/projects/papershaper/

It is open source licensed, and does not download anything as part of
the install process. It has two dependencies: Python and the lynx
browser. Python 2 and 3 versions are included in the tarball but it is
presumed that the preferred Python version is now Python 3, so that is
the default.

It does optionally download images, but only on execution.


On 12/22/20 1:54 PM, olivier sallou wrote:
> You created an itp so an intent to package.
> If not willing to propose a apckage should be an rfp request for package.
> Ideally you package your app and propose it for review and upload.
> Requirements are an open source license and package install should not
> download anything.
> Only its execution can download remote stuff.
> 
> Olivier

Bug#976174: ITP:papershaper--automagic wallpaper swapper

[Devops PK Carlisle LLC]

Package: wnpp
Severity: wishlist
Owner: Devops PK Carlisle LLC 
X-Debbugs-Cc: debian-de...@lists.debian.org, dev...@pkcarlisle.com

* Package name: papershaper
* URL : https://github.com/pkcarlislellc/git-papershaper
* License : LGPL-3+
  Programming Lang: Python
  Description : automagic wallpaper swapper

Papershaper automatically changes wallpaper from either locally stored
images,from webcams, or both. User chooses how often Papershaper updates
wallpaper.

Originally written in Python 2, now updated to default to Python 3
(Python 2 code is still included for those who want it).

Available for download at https://github.com/pkcarlislellc/git-papershaper

Available as a tar.gz from https://sourceforge.net/projects/papershaper/

Fully documented at both of these sources.

Bug#942230: fromiso on a multi-device btrfs needs btrfs device scan

[pk]

Package: debian-live

Booting lxqt 10.1 live iso, stored on a multi-device btrfs, fails with
an infinite loop.

Workaround: boot with break, then:
modprobe btrfs
btrfs device scan
^D


In theory, another approach would be to pass the list of partitions as
a mount option, as done on installed distros that do not run the
device scan:
rootflags=device=/dev/sda2,...
However, this seems unapplicable to the boot parameter fromiso.

Bug#942222: crash at startup, like #734405 (ValueError: numpy.dtype does not appear to be the correct type object)

[pk]

Package: seekwatcher
Version: 0.12+hg20091016-3
Severity: grave

In Debian 10 and current Debian 9:

# seekwatcher
Traceback (most recent call last):
  File "/usr/bin/seekwatcher", line 58, in 
from seekwatcher import rundata
  File "numpy.pxd", line 43, in seekwatcher.rundata (seekwatcher/rundata.c:7885)
ValueError: numpy.dtype does not appear to be the correct type object

Previous report: 

Bug#942221: openbox: padding next to the title

[pk]

Package: openbox
Version: 3.6.1-8
Severity: minor

NLIMC with Artwiz-boxed shows padding at the left. Same for any theme
with a title background different from the titlebar background.


This behavior differs from fedora 30, which has openbox 3.6.1 like
debian 10, and from debian 9.

Bug#885818: alltray: Depends on gconf

[pk]

alltray works on openbox on Buster, as of June 2019.

The original issue was solved ("depends on gconf"). The severity
serious is inappropriate and should be lowered, even if this report
stays open for the unrelated, potential issues mentioned in message
#28 (gnome theme, exit code).

Thanks

Bug#929216: RM: algotutor/0.8.6-2

[pk]

Hi,

I am using algotutor on Buster with my home as working directory and
do not experience the reported issue. algotutor is 0.8.6-2. Here is
the terminal output:

$ algotutor
Use of uninitialized value $opts{"a"} in string eq at
/usr/share/algotutor/algotutor line 34.
Use of uninitialized value $opts{"a"} in string eq at
/usr/share/algotutor/algotutor line 34.
Use of uninitialized value $opts{"a"} in string eq at
/usr/share/algotutor/algotutor line 34.
need exactly one data file. Example:
algotutor -a bst /usr/share/algotutor/data/countries.gr
$ algotutor -a bst /usr/share/algotutor/data/countries.gr
total marks: 184
seeking to step 0...

Bug#920978: audacious: It would be great is the qt5 ui from audacios was also put into the deb package

[PK]

Source: audacious
Severity: wishlist

Dear Maintainer,



For quite a while it is possible to (also) build a qt5-based user interface for 
audacious. I built it by saying: ./configure --prefix=/usr --enable-qt . It 
works great. It would be great for kde-users if they could use this interface. 
It would be a way to show appreciation for the work the audacious-team does.



-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#920357: partitionmanager: When I format a usb-stick to ext4 using partitionmanager the result will be read only for users

[PK]

Package: partitionmanager
Version: 3.3.1-5
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
I used partitionmanager to format a usb drive
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
I followed partitionmanager completely. I formatted some usb drives to ext4
   * What was the outcome of this action?
The outcome whas that the formatted drive was - is always - read only for users
   * What outcome did you expect instead?
I expected to be able to write to the usb-stick as a user

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.18.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages partitionmanager depends on:
ii  kio   5.54.1-1
ii  libc6 2.28-5
ii  libkf5configcore5 5.54.0-1
ii  libkf5configgui5  5.54.0-1
ii  libkf5configwidgets5  5.54.0-1
ii  libkf5coreaddons5 5.54.0-1
ii  libkf5crash5  5.54.0-1
ii  libkf5i18n5   5.54.0-1
ii  libkf5iconthemes5 5.54.0-1
ii  libkf5jobwidgets5 5.54.0-1
ii  libkf5kiocore55.54.1-1
ii  libkf5kiowidgets5 5.54.1-1
ii  libkf5widgetsaddons5  5.54.0-1
ii  libkf5xmlgui5 5.54.0-1
ii  libkpmcore7   3.3.0-4
ii  libqt5core5a  5.11.3+dfsg-2
ii  libqt5gui55.11.3+dfsg-2
ii  libqt5widgets55.11.3+dfsg-2
ii  libstdc++68.2.0-14

partitionmanager recommends no packages.

Versions of packages partitionmanager suggests:
pn  btrfs-progs
ii  dosfstools 4.1-2
pn  hfsplus
pn  hfsutils   
pn  jfsutils   
ii  ntfs-3g1:2017.3.23AR.3-2
pn  reiser4progs   
pn  reiserfsprogs  
ii  xfsprogs   4.15.1-1

-- no debconf information

Bug#619504: Probably fixed in 2.6.32-34squeeze1

[pk-alt]

The bug seems to be fixed in current stable. After fast-forward upgrade from 
2.6.32-30 to 2.6.32-34squeeze1, the trip points have remained exactly the same 
(see previous email).

Pavel



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

Bug#584473: Request for bug package change or disposal

[pk-alt]

This bug stopped to occur with switching from KDE to XFCE. It therefore
seems that the X server restart was rather a cause than a consequence
and that the bug is not related to pm-utils but rather kdm or kwin.
Unfortunately I have removed KDE and cannot test it furhter right now.

On Thu, 03 Jun 2010 19:15:04 +
ow...@bugs.debian.org (Debian Bug Tracking System) wrote:

> Thank you for filing a new Bug report with Debian.
> 
> This is an automatically generated reply to let you know your message
> has been received.
> 
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
> 
> Your message has been sent to the package maintainer(s):
>  Tim Dijkstra 
> 
> If you wish to submit further information on this problem, please
> send it to 584...@bugs.debian.org.
> 
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
> 




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

Bug#495257: More info

[dantti85-pk]

Hi,
I'm a packagekit and kpackagekit developer. (www.packagekit.org)
i was going to contact dbus packgers people but i found a bug that
has what i need.

i'll try to explain why not restart Dbus:

* Fist of all dbus should be treated like a kernel? sould stupid?
but you can't (ok i know there are ways to do it) upgrade your kernel
and don't do a restart.

* gdm > 2.22 or greater will kill you login session.

* policykit a program that is getting wide used, creates a session
every time you login on kdm or gdm, if you restart Dbus it will never come back.

* and in our case we use dbus to have a very good design in security and
transparency for the user and a developer application.
how it works? well if you don't know packagekit has a wide range of backends
so you will be able to manage software the same way (in the user poit of view)
on ANY distro. Fedora 9 already uses it. ALL the comunication between 
packagekit and the user interface is made using DBUS.
So if you restart DBUS the ui is not able to respond to the current request
and the user got's confused.
AND in the most common case doing a system update using packagekit ui
will end up with a ui stuck and it never concludes the updates...

If the user kills the updates ui, he will never be able again to 
install/remove ANY packages WHY? because polkit the program that
gives him the right to do admin tasks was killed by a restart.

Please don't think that only m$ should do restart, on m$98
if you hold the shift (not sure if this was the key) the os
did not restart completely.

if restarting is a m$ thing why should you restart a running program??
tell it to re read it's config file (i also think it's unecessary).

So please consider not doing this restart anymore. you will be crashing
too many things, it's like to unplug a pendrive while it's copying...

the application don't know what to do and some of then could do nothing!

Ah i remember more one problem:
IF dbus is not able to start again due this update a kde user will not be able
to use shortcuts, nor see popups messages... it all Depends on DBUS.
and to finish my huge email :)

Dbus was made for desktop users (freedesktop.org), so you can't have
a power user to be able to start dbus by hand cause it failed to start...

please add my email if this is not automatic,
and please don't see this like an angry or ofence email.
It's just that there are a bounch of projects that rely on Dbus
and doing so is breaking everything.

cheers,
Daniel.



  Novos endereços, o Yahoo! que você conhece. Crie um email novo com a sua 
cara @ymail.com ou @rocketmail.com.
http://br.new.mail.yahoo.com/addresses