Bug#1004003: Acknowledgement (chromium: After upgrade to latest version, chromium cannot open anymore.)

2022-01-19 Thread johnw 

Duplicated with https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003689 .

On 1/19/22 15:33, Debian Bug Tracking System wrote:

Thank you for filing a new Bug report with Debian.

You can follow progress on this Bug here: 1004003: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004003.

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.

As you requested using X-Debbugs-CC, your message was also forwarded to
   johnw.m...@gmail.com
(after having been given a Bug report number, if it did not have one).

Your message has been sent to the package maintainer(s):
  Debian Chromium Team 

If you wish to submit further information on this problem, please
send it to 1004...@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.




--
Key fingerprint: CDB3 6C62 254B C088 1E5D DD32 182C 97DB CF2C 80AC

Bug#1003258: php-redis: Support php8.1

2022-01-06 Thread Johnw 
Package: php-redis
Severity: wishlist
X-Debbugs-Cc: johnw.m...@gmail.com

Dear Maintainer,

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

Since debian sid updated the php to version 8.1.
Please update php-redis to support it, thanks.

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

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


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

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

Versions of packages php-redis depends on:
ii  libc62.33-1
pn  php-common   
pn  php-igbinary 
pn  phpapi-20190902  

php-redis recommends no packages.

Versions of packages php-redis suggests:
pn  redis-server

Bug#995035: Acknowledgement (lxc: Operation not permitted - Failed to mount "proc" onto "/usr/lib/x86_64-linux-gnu/lxc/rootfs/proc")

2021-09-24 Thread johnw 

Attached log file, thanks.



On 9/25/21 1:33 PM, Debian Bug Tracking System wrote:

Thank you for filing a new Bug report with Debian.

You can follow progress on this Bug here: 995035: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995035.

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):
  pkg-lxc 

If you wish to submit further information on this problem, please
send it to 995...@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.




--
Key fingerprint: CDB3 6C62 254B C088 1E5D DD32 182C 97DB CF2C 80AC
lxc-start dmz011 20210925051927.102 INFO confile - 
confile.c:set_config_idmaps:2115 - Read uid map: type u nsid 0 hostid 110 
range 65536
lxc-start dmz011 20210925051927.102 INFO confile - 
confile.c:set_config_idmaps:2115 - Read uid map: type g nsid 0 hostid 110 
range 65536
lxc-start dmz011 20210925051927.102 TRACEcommands - commands.c:lxc_cmd:511 
- Connection refused - Command "get_init_pid" failed to connect command socket
lxc-start dmz011 20210925051927.102 TRACEcommands - commands.c:lxc_cmd:511 
- Connection refused - Command "get_state" failed to connect command socket
lxc-start dmz011 20210925051927.102 TRACEstart - 
start.c:lxc_init_handler:744 - Created anonymous pair {4,5} of unix sockets
lxc-start dmz011 20210925051927.102 TRACEcommands - 
commands.c:lxc_server_init:2063 - Created abstract unix socket 
"/var/lib/lxc/dmz011/command"
lxc-start dmz011 20210925051927.102 TRACEstart - 
start.c:lxc_init_handler:760 - Unix domain socket 6 for command server is ready
lxc-start dmz011 20210925051927.102 INFO lxccontainer - 
lxccontainer.c:do_lxcapi_start:988 - Set process title to [lxc monitor] 
/var/lib/lxc dmz011
lxc-start dmz011 20210925051927.102 DEBUGlxccontainer - 
lxccontainer.c:wait_on_daemonized_start:849 - First child 30914 exited
lxc-start dmz011 20210925051927.103 TRACEstart - start.c:lxc_start:2166 - 
Doing lxc_start
lxc-start dmz011 20210925051927.103 INFO lsm - lsm/lsm.c:lsm_init_static:40 
- Initialized LSM security driver AppArmor
lxc-start dmz011 20210925051927.103 TRACEstart - start.c:lxc_init:784 - 
Initialized LSM
lxc-start dmz011 20210925051927.103 TRACEstart - 
start.c:lxc_serve_state_clients:482 - Set container state to STARTING
lxc-start dmz011 20210925051927.103 TRACEstart - 
start.c:lxc_serve_state_clients:485 - No state clients registered
lxc-start dmz011 20210925051927.103 TRACEstart - start.c:lxc_init:790 - Set 
container state to "STARTING"
lxc-start dmz011 20210925051927.103 TRACEstart - start.c:lxc_init:846 - Set 
environment variables
lxc-start dmz011 20210925051927.103 TRACEstart - start.c:lxc_init:851 - Ran 
pre-start hooks
lxc-start dmz011 20210925051927.103 TRACEstart - 
start.c:setup_signal_fd:375 - Created signal file descriptor 8
lxc-start dmz011 20210925051927.103 TRACEstart - start.c:lxc_init:860 - Set 
up signal fd
lxc-start dmz011 20210925051927.103 TRACEconf - 
conf.c:userns_exec_mapped_root:5281 - Chowned 10((null)) to uid 110 and 
110
lxc-start dmz011 20210925051927.103 TRACEterminal - 
terminal.c:lxc_terminal_map_ids:859 - Chowned terminal 10((null))
lxc-start dmz011 20210925051927.103 DEBUGterminal - 
terminal.c:lxc_terminal_peer_default:665 - No such device - The process does 
not have a controlling terminal
lxc-start dmz011 20210925051927.103 TRACEstart - start.c:lxc_init:868 - 
Created console
lxc-start dmz011 20210925051927.103 TRACEcgfsng - 
cgroups/cgfsng.c:cgroup_hierarchy_add:446 - Adding cgroup hierarchy mounted at  
and base cgroup (null)
lxc-start dmz011 20210925051927.103 TRACEcgfsng - 
cgroups/cgfsng.c:cgroup_hierarchy_add:449 - The hierarchy contains the cpuset 
controller
lxc-start dmz011 20210925051927.103 TRACEcgfsng - 
cgroups/cgfsng.c:cgroup_hierarchy_add:449 - The hierarchy contains the cpu 
controller
lxc-start dmz011 20210925051927.103 TRACEcgfsng - 
cgroups/cgfsng.c:cgroup_hierarchy_add:449 - The hierarchy contains the io 
controller
lxc-start dmz011 20210925051927.103 TRACEcgfsng - 
cgroups/cgfsng.c:cgroup_hierarchy_add:449 - The hierarchy contains the memory 
controller
lxc-start dmz011 20210925051927.103 TRACEcgfsng - 
cgroups/cgfsng.c:cgroup_hierarchy_add:449 - The hierarchy contains the hugetlb 
controller
lxc-start dmz011 20210925051927.103 TRACEcgfsng - 
cgroups/cgfsng.c:cgroup_hierarchy_add:449 - The hierarchy contains the pids 
controller
lxc-start dmz011 20210925051927.103 TRACEcgfsng - 
cgroups/cgfsng.c:cgroup_hierarchy_add:449 - The hierarchy contains the rdma 
controller
lxc-start dmz011 20210925051927.103 TRACEcgfsng -

Bug#964236: php-redis: After upgrade to php-redis (5.3.0+4.3.0-1), php-fpm crash

2020-07-07 Thread johnw 
Still crash.

ii  php-redis   5.3.0+4.3.0-2  amd64
   PHP extension for interfacing with Redis

php-fpm7.4[128121]: segfault at 10001 ip 563936cd83b6 sp
7fffac26b658 error 4 in php-fpm7.4[563936b35000+268000]
[72499.538048] Code: 85 8b 7a e7 ff 48 8b 47 10 48 83 c0 38 48 39 47 18
48 89 c2 48 89 47 10 48 0f 43 57 18 48 8b 47 50 48 89 57 18 48 85 c0 74
0a <48> 8b 10 48 89 57 50 c3 66 90 be 06 00 00 00 e9 96 e5 ff ff 66 0f
[72506.900324] traps: php-fpm7.4[128120] general protection fault
ip:563936cd9634 sp:7fffac26b6a8 error:0 in php-fpm7.4[563936b35000+268000]
[72506.970571] traps: php-fpm7.4[128118] general protection fault
ip:563936cd9634 sp:7fffac26b6a8 error:0 in php-fpm7.4[563936b35000+268000]
[72508.372771] traps: php-fpm7.4[128122] general protection fault
ip:563936cd9634 sp:7fffac26b6a8 error:0 in php-fpm7.4[563936b35000+268000]
[72508.404409] traps: php-fpm7.4[128125] general protection fault
ip:563936cd9634 sp:7fffac26b6a8 error:0 in php-fpm7.4[563936b35000+268000]

Thanks.

On 7/7/20 3:04 PM, Ondřej Surý wrote:
> Version: 5.3.0+4.3.0-2
> 
> I have pulled 5.3.1 prerelease branch into the latest package, so the -2
> should no longer crash on you.
> 
> Ondrej
> 
> On Sat, 4 Jul 2020 at 03:45, John Wong  > wrote:
> 
> Package: php-redis
> Version: After upgrade to php-redis (5.3.0+4.3.0-1), php-fpm crash
> Severity: normal
> 
> Dear Maintainer,
>      After upgrade to php-redis (5.3.0+4.3.0-1), php-fpm crash.
> 
>      traps: php-fpm7.4[198823] general protection fault
> ip:55da0ea4c634 sp:7ffc14657008 error:0 in
> php-fpm7.4[55da0e8a8000+268000]
>      php-fpm7.4[198824]: segfault at 10001 ip 55da0ea4b3b6
> sp 7ffc14656fb8 error 4 in php-fpm7.4[55da0e8a8000+268000]
>      Code: 85 8b 7a e7 ff 48 8b 47 10 48 83 c0 38 48 39 47 18 48 89 c2
>      48 89 47 10 48 0f 43 57 18 48 8b 47 50 48 89 57 18 48 85 c0 74 0a
>      <48> 8b 10 48 89 57 50 c3 66 90 be 06 00 00 00 e9 96 e5 ff f
>      f 66 0f
> 
>      Please help, thank you.
> 
> *** Reporter, please consider answering these questions, where
> appropriate ***
> 
>    * What led up to the situation?
>    * What exactly did you do (or not do) that was effective (or
>      ineffective)?
>    * What was the outcome of this action?
>    * What outcome did you expect instead?
> 
> *** End of the template - remove these template lines ***
> 
> 
> -- System Information:
> Debian Release: bullseye/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 5.7.0-1-amd64 (SMP w/8 CPU cores)
> Kernel taint flags: TAINT_WARN
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
> LANGUAGE=en_US:en (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 


-- 
Key fingerprint: CDB3 6C62 254B C088 1E5D DD32 182C 97DB CF2C 80AC

Bug#963601: Acknowledgement (chromium: Can not upgrade chromium)

2020-06-26 Thread johnw 
Hi All,

Any workaround to solve it?  we cannot run https://web.whatsapp.com with
chromium a week now.
Please help, thank you.

Bug#898025: lxc: apparmor="DENIED" operation="mount" info="failed flags match" error=-13

2018-10-26 Thread johnw 
Hi, sorry for late reply,
I think it's not bug.
Because I removed systemd, either if I reinstall systemd, or I add some mount 
rules to apparmor , then the denied messages gone.
Thank you for help, thanks.

On 2018年10月26日 下午5:55:02 [GMT+08:00], intrigeri  wrote:
>Control: tag -1 - upstream
>Control: tag -1 + moreinfo
>
>Hi,
>
>kaka:
>> Over the year, if I enable apparmor for lxc (lxc.aa_profile =
>lxc-container-default),
>
>First, I don't think you need to turn this on manually and I doubt
>this is the best AppArmor profile to use. According to
>lxc.container.conf(5):
>
>   APPARMOR PROFILE
>If lxc was compiled and installed with apparmor support, and the host 
>sys‐
>tem  has  apparmor  enabled, then the apparmor profile under which the
>con‐
>tainer should be run can be specified in the container  configuration. 
>The
>default  is  lxc-container-default-cgns if the host kernel is cgroup
>names‐
>   pace aware, or lxc-container-default othewise.
>
>So not setting lxc.aa_profile at all should automatically select the
>lxc-container-default-cgns profile. Not that it would make
>a difference for this bug though.
>
>> I see a lot of "apparmor denied" messages like below,
>> But the lxc itself is can running and functional without a problem,
>> Why apparmor always complain lxc? (is this normal)?
>
>> apparmor="DENIED" operation="mount" info="failed type match"
>error=-13 profile="lxc-container-default" name="/sys/fs/pstore/"
>pid=2676 comm="mount" fstype="pstore" srcname="pstore"
>> apparmor="DENIED" operation="mount" info="failed type match"
>error=-13 profile="lxc-container-default" name="/sys/fs/pstore/"
>pid=2676 comm="mount" fstype="pstore" srcname="pstore" flags="ro"
>> apparmor="DENIED" operation="mount" info="failed flags match"
>error=-13 profile="lxc-container-default" name="/" pid=2763
>comm="mount" flags="rw, remount"
>
>On current sid:
>
> - I cannot reproduce this with the lxc-debian template, which is
>   expected since it has no lxc.mount.entry for /sys/fs/pstore
>
> - I cannot reproduce this with the lxc-ubuntu template (which _has_
>   a lxc.mount.entry for /sys/fs/pstore) either:
>
> # lxc-create -n ubuntu -t /usr/share/lxc/templates/lxc-ubuntu
> […]
> # lxc-start -F -n ubuntu
> […]
> Ubuntu 16.04.5 LTS ubuntu console
>
> ubuntu login: ubuntu
> Password: 
> […]
> $ ubuntu@ubuntu:~$ mount | grep pstore
> pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
>
>   And there's no single AppArmor denial in the host system's logs.
>   aa-status confirms that this container is running under the
>   lxc-container-default-cgns profile.
>
>So, can you still reproduce this on current testing/sid?
>If yes, can you please share a simple reproducer similar to the one
>I've tried to provide above?
>
>Cheers,
>-- 
>intrigeri


Key fingerprint: CDB3 6C62 254B C088 1E5D DD32 182C 97DB CF2C 80AC

Bug#908192: Acknowledgement (linux-image-4.18.0-1-amd64: After upgrade kernel to linux-image-4.18.0-1-amd64, LXC can not start)

2018-09-20 Thread johnw 


Is it also reverted/back port to Debian?
Because I still have this problem.
Thanks.

On 2018年9月9日 上午3:35:54 [GMT+08:00], Salvatore Bonaccorso <
>TTBOMK, the change is beeing discussed to be reverted,
>https://lore.kernel.org/lkml/20180705155120.22102-1-christ...@brauner.io/
>
>Regards,
>Salvatore


Key fingerprint: CDB3 6C62 254B C088 1E5D DD32 182C 97DB CF2C 80AC

Bug#908192: Acknowledgement (linux-image-4.18.0-1-amd64: After upgrade kernel to linux-image-4.18.0-1-amd64, LXC can not start)

2018-09-07 Thread johnw 

I can start privileged LXC containers with 4.18 kernel,
Only can not start unprivileged LXC containers with 4.18 kernel.

Maybe the problem is lxc, not the kernel,

https://lists.linuxfoundation.org/pipermail/containers/2018-June/039174.html

--
Key fingerprint: CDB3 6C62 254B C088 1E5D DD32 182C 97DB CF2C 80AC

Bug#908192: Acknowledgement (linux-image-4.18.0-1-amd64: After upgrade kernel to linux-image-4.18.0-1-amd64, LXC can not start)

2018-09-07 Thread johnw 

Attached config and log file for lxc-start -n name -l debug


--
Key fingerprint: CDB3 6C62 254B C088 1E5D DD32 182C 97DB CF2C 80AC
lxc.start.auto = 1
lxc.start.delay = 0

# Distribution configuration
lxc.include = /usr/share/lxc/config/debian.common.conf
lxc.include = /usr/share/lxc/config/debian.userns.conf
lxc.arch = x86_64

# Container specific configuration
lxc.kmsg = 0
lxc.id_map = u 0 1210 65536
lxc.id_map = g 0 1210 65536
#lxc.cap.drop = sys_module mac_admin mac_override sys_time mknod net_raw 
sys_rawio sys_nice sys_pacct setfcap setpcap sys_ptrace syslog sys_resource 
sys_tty_config wake_alarm sys_admin
#lxc.aa_profile = lxc-container-default-local
#lxc.aa_allow_incomplete = 0
lxc.aa_profile = unconfined
lxc.rootfs = /var/lib/lxc/lxc121/rootfs
lxc.rootfs.backend = dir
lxc.utsname = lxc121

# Network configuration
lxc.network.type = veth
lxc.network.flags = up
lxc.network.link = lxcbr0
lxc.network.hwaddr = AA:BB:CC:DD:01:21
lxc.network.ipv4 = 192.168.168.121/32
lxc.network.ipv4.gateway = 192.168.168.1


# manual mount for drop sys_admin
lxc.mount.entry = tmpfs run tmpfs 
rw,nosuid,noexec,relatime,mode=0755,create=dir 0 0
lxc.mount.entry = tmpfs run/lock tmpfs 
rw,nosuid,nodev,noexec,relatime,mode=1777,size=5M,create=dir 0 0
lxc.mount.entry = tmpfs run/shm tmpfs 
rw,nosuid,nodev,noexec,relatime,mode=1777,create=dir 0 0

lxc.mount.entry = tmpfs root tmpfs nosuid,nodev,noatime,mode=0700,uid=0,gid=0 0 0
lxc.mount.entry = tmpfs home/lxc121 tmpfs 
nosuid,nodev,noatime,mode=0700,uid=1121,gid=1121 0 0

# mount tmp first then GUI
lxc.mount.entry = tmpfs tmp tmpfs nosuid,nodev,noatime,mode=1777,create=dir 0 0

lxc.mount.entry = /ramdisk ramdisk none bind,optional,create=dir,nodev,nosuid 0 0
lxc.mount.entry = tmpfs var/cache/apt/archives tmpfs 
nosuid,nodev,noatime,mode=0755,create=dir 0 0

  lxc-start 20180907081437.752 INFO lxc_start_ui - 
tools/lxc_start.c:main:277 - using rcfile /var/lib/lxc/lxc121/config
  lxc-start 20180907081437.752 WARN lxc_confile - 
confile.c:set_config_pivotdir:2262 - lxc.pivotdir is ignored.  It will soon 
become an error.
  lxc-start 20180907081437.752 INFO lxc_confile - 
confile.c:set_config_idmaps:1861 - read uid map: type u nsid 0 hostid 1210 
range 65536
  lxc-start 20180907081437.752 INFO lxc_confile - 
confile.c:set_config_idmaps:1861 - read uid map: type g nsid 0 hostid 1210 
range 65536
  lxc-start 20180907081437.752 INFO lxc_container - 
lxccontainer.c:do_lxcapi_start:877 - Attempting to set proc title to [lxc 
monitor] /var/lib/lxc lxc121
  lxc-start 20180907081437.752 INFO lxc_lsm - lsm/lsm.c:lsm_init:48 - 
LSM security driver AppArmor
  lxc-start 20180907081437.753 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:435 - processing: .reject_force_umount  # comment 
this to allow umount -f;  not recommended.
  lxc-start 20180907081437.753 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:610 - Adding native rule for reject_force_umount 
action 0(kill).
  lxc-start 20180907081437.753 INFO lxc_seccomp - 
seccomp.c:do_resolve_add_rule:276 - Setting Seccomp rule to reject force 
umounts.
  lxc-start 20180907081437.753 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:614 - Adding compat rule for reject_force_umount 
action 0(kill).
  lxc-start 20180907081437.753 INFO lxc_seccomp - 
seccomp.c:do_resolve_add_rule:276 - Setting Seccomp rule to reject force 
umounts.
  lxc-start 20180907081437.753 INFO lxc_seccomp - 
seccomp.c:do_resolve_add_rule:276 - Setting Seccomp rule to reject force 
umounts.
  lxc-start 20180907081437.753 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:435 - processing: .[all].
  lxc-start 20180907081437.753 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:435 - processing: .kexec_load errno 1.
  lxc-start 20180907081437.753 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:610 - Adding native rule for kexec_load action 
327681(errno).
  lxc-start 20180907081437.753 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:614 - Adding compat rule for kexec_load action 
327681(errno).
  lxc-start 20180907081437.753 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:435 - processing: .open_by_handle_at errno 1.
  lxc-start 20180907081437.753 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:610 - Adding native rule for open_by_handle_at action 
327681(errno).
  lxc-start 20180907081437.753 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:614 - Adding compat rule for open_by_handle_at action 
327681(errno).
  lxc-start 20180907081437.753 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:435 - processing: .init_module errno 1.
  lxc-start 20180907081437.753 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:610 - Adding native rule for init_module action 
327681(errno).
  lxc-start 20180907081437.753 INFO lxc_seccomp - 
seccomp.c:parse_config_v2:614 - Adding compat rule for init_module action 
327681(errno).

Bug#900533: chromium 67.0.3396.62-1: youtube video, gif's, html5, and movies no longer work

2018-06-01 Thread johnw 
Yes, same problem here.




signature.asc
Description: OpenPGP digital signature

Bug#898824: btrfs-progs: missing libbtrfs.so.0

2018-05-16 Thread johnw 
Hi John,

On 05/16/2018 07:57 PM, Dimitri John Ledkov wrote:
>
> The library was moved into a standalone package. I guess I need to
> declare breaks, to force correct upgrade sequency and recompile
> snapper against the new btrfs-progs.
>
Yes, I think "force correct upgrade sequency and recompile snapper
against the new btrfs-progs",

is not bad idea.


I solved the problem after install libbtrfs0,

so I will close this bug report,

Thank you.




signature.asc
Description: OpenPGP digital signature

Bug#898025: lxc: apparmor="DENIED" operation="mount" info="failed flags match" error=-13

2018-05-05 Thread johnw 




-- Configuration Files:
/etc/apparmor.d/abstractions/lxc/container-base [Errno 13] Permission
denied: '/etc/apparmor.d/abstractions/lxc/container-base'
/etc/apparmor.d/abstractions/lxc/start-container [Errno 13] Permission
denied: '/etc/apparmor.d/abstractions/lxc/start-container'
/etc/apparmor.d/lxc-containers [Errno 13] Permission denied:
'/etc/apparmor.d/lxc-containers'
/etc/apparmor.d/lxc/lxc-default [Errno 13] Permission denied:
'/etc/apparmor.d/lxc/lxc-default'
/etc/apparmor.d/lxc/lxc-default-cgns [Errno 13] Permission denied:
'/etc/apparmor.d/lxc/lxc-default-cgns'
/etc/apparmor.d/lxc/lxc-default-with-mounting [Errno 13] Permission
denied: '/etc/apparmor.d/lxc/lxc-default-with-mounting'
/etc/apparmor.d/lxc/lxc-default-with-nesting [Errno 13] Permission
denied: '/etc/apparmor.d/lxc/lxc-default-with-nesting'
/etc/apparmor.d/usr.bin.lxc-start [Errno 13] Permission denied:
'/etc/apparmor.d/usr.bin.lxc-start'

-- no debconf information


Attached apparmor.d rules(default from lxc.deb without modify) and lxc 
config here



--
Key fingerprint: CDB3 6C62 254B C088 1E5D DD32 182C 97DB CF2C 80AC


lxc-apparmor.tar
Description: Unix tar archive

Bug#892585: systemd: can not create user.slice/user session, after upgrade systemd from 237-4 to 238-1/2

2018-04-05 Thread johnw 
Hi Michael,

I found out, what cause the problem,
I have this line in fstab
"proc /proc proc rw,nosuid,nodev,noexec,relatime,hidepid=2,gid=4   
0   0"

I changed it to
"proc /proc proc rw,nosuid,nodev,noexec,relatime,hidepid=2    0   0"
(without gid=4), then the problem is gone.

Thank you.

-- 
Key fingerprint: CDB3 6C62 254B C088 1E5D DD32 182C 97DB CF2C 80AC




signature.asc
Description: OpenPGP digital signature

Bug#892585: systemd: can not create user.slice/user session, after upgrade systemd from 237-4 to 238-1/2

2018-03-24 Thread johnw 

Hi Michael,

Michael Biebl 於 2018-03-23 23:31 寫到:


Does it work if you switch to a different display manager, like say
lightdm (which IIRC is the preferred one of xfce). Might be a problem
specific to slim, since I don't see any such issues myself here (using
GNOME/gdm).


No, I tried lightdm lxdm, they have same problem,
I tried gdm3, but can not login, do not why, the screen just become to 
blank/black.


Any idea, how to debug?

Thanks.

--
Key fingerprint: CDB3 6C62 254B C088 1E5D DD32 182C 97DB CF2C 80AC



signature.asc
Description: OpenPGP digital signature

Bug#892585: systemd: can not create user.slice/user session, after upgrade systemd from 237-4 to 238-1/2

2018-03-21 Thread johnw 

After upgrade systemd to 238-3, I still have this problem :(
Any one?
Help, please.

--
Key fingerprint: CDB3 6C62 254B C088 1E5D DD32 182C 97DB CF2C 80AC



signature.asc
Description: OpenPGP digital signature

Bug#885155: closed by Michael Gilbert <mgilb...@debian.org> (re: chromium: rejects access to microphone without prompt)

2018-03-17 Thread johnw 

Debian Bug Tracking System 於 2018-01-28 10:45 寫到:

This is an automatic notification regarding your Bug report
which was filed against the chromium package:

#885155: chromium: Enable audio/microphone support (Again)

It has been closed by Michael Gilbert .

Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Michael Gilbert
 by
replying to this email.


Hi Michael,

Is it possible use policy json to override this (intended)default 
setting?

(https://www.chromium.org/administrators/configuring-other-preferences)

if yes, do you know where is the policy json path?

thanks.


--
Key fingerprint: CDB3 6C62 254B C088 1E5D DD32 182C 97DB CF2C 80AC



signature.asc
Description: OpenPGP digital signature

Bug#892585: systemd: can not create user.slice/user session, after upgrade systemd from 237-4 to 238-1/2

2018-03-15 Thread johnw 

Hi, only me have this problem?
Any idea, why new version(238-x) systemd, can not create user-slice?
and can not start "/usr/bin/start-pulseaudio-x11" ??
--
Key fingerprint: CDB3 6C62 254B C088 1E5D DD32 182C 97DB CF2C 80AC



signature.asc
Description: OpenPGP digital signature

Bug#892585: Fwd: Bug#892585: Acknowledgement (systemd: can not create user.slice/user session, after upgrade systemd from 237-4 to 238-1/2)

2018-03-11 Thread johnw 
If I replace (version 238-2) /lib/systemd/systemd-logind to old 
version(237-4) /lib/systemd/systemd-logind,
and ln -s /lib/systemd/libsystemd-shared-238.so 
/lib/systemd/libsystemd-shared-237.so


All the problem gone, everything work again,

Please help, thanks.


--
Key fingerprint: CDB3 6C62 254B C088 1E5D DD32 182C 97DB CF2C 80AC

Bug#885325: systemd: Daemon start with systemctl start daemon can not find mount point not mounted by boot

2017-12-28 Thread johnw 

Forget to CC bug(#885325) tracker  :)


Michael Biebl 於 2017-12-29 04:33 寫到:


Can you please break that down into a minimal test case which would
allow to reproduce the problem.


OK, create mount point /disk, in my case is encrypted by luks,
and not mount on boot.

After the system boot up, ssh login the system, and mount /disk,

Use systemctl to start service/daemon need to access /disk,
(eg: systemctl (re)start smbd.service)
the service/daemon (smbd) will NOT access/stat /disk,

But if I NOT use systemctl to start service/daemon,
(eg: /usr/sbin/smbd -D)
smbd can access/stat /disk normally

And this problem only appear, after upgrade systemd* to 236-1,
It work well before upgrade.

Please help, and thank you.

--
Key fingerprint: CDB3 6C62 254B C088 1E5D DD32 182C 97DB CF2C 80AC

Bug#885155: chromium: Enable audio/microphone support (Again)

2017-12-24 Thread johnw 

https://www.chromium.org/administrators/policy-list-3#AudioCaptureAllowed

--
Key fingerprint: CDB3 6C62 254B C088 1E5D DD32 182C 97DB CF2C 80AC

Bug#861134: slim: Reloads automatically and queries login-prompt after running window manager for some (a short) time

2017-05-06 Thread johnw 
On 04/30/2017 05:30 PM, johnw wrote:
> Hello all, any update?  how to solve it?
>
> Please help, thanks.
>
>>
>> Hi all,
>>
>> I need more informations about this bug, I can't confirm that on my
>> configuration.
>>
>> Have you something specific on start splash or plymouth?
>>
>> I will try to reproduce this bug for fix.
>
After upgrade slim to version 1.3.6-5.1, solved the problem,

Thank all.





signature.asc
Description: OpenPGP digital signature

Bug#861134: slim: Reloads automatically and queries login-prompt after running window manager for some (a short) time

2017-04-30 Thread johnw 

Hello all, any update?  how to solve it?

Please help, thanks.



Hi all,

I need more informations about this bug, I can't confirm that on my
configuration.

Have you something specific on start splash or plymouth?

I will try to reproduce this bug for fix.


--
Key fingerprint: CDB3 6C62 254B C088 1E5D DD32 182C 97DB CF2C 80AC

Bug#861134: Follow 1+

2017-04-26 Thread johnw 
Same problem here

Key fingerprint: CDB3 6C62 254B C088 1E5D DD32 182C 97DB CF2C 80AC

Bug#813658: Please enable virgl support

2016-12-29 Thread johnw 
On 12/29/2016 02:04 PM, Michael Tokarev wrote:
> When I launch qemu-system-x86 with -display gtk,gl=on and -seccomp on,
>> it just freeze and "ps aux" show me.
>> [qemu-system-x86] 
> $ qemu-system-x86_64 -display gtk,gl=on
> Couldn't open libGL.so.1: dlopen: cannot load any more object with
> static TLS
> $ echo $?
> 1
> $ _
>
> So it fails to load libGL.so
>
> http://stackoverflow.com/questions/19268293/matlab-error-cannot-open-with-static-tls
>
> hmm...
>
> /mjt

Hi Michael,

Sorry, I mean "qemu-system-x86_64 -display gtk,gl=on -sandbox on",
(not -seccomp on)

when I launch -display gtk with -sandbox on, qemu-system-x86_64 will freeze,
and "ps aux" will show me [qemu-system-x86] 

I dont have problem, if launch "-display gtk" without "-sandbox on".

Thanks.





signature.asc
Description: OpenPGP digital signature

Bug#813658: Please enable virgl support

2016-12-29 Thread johnw 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

OK, understand now, thank you, Michael

On 2016年12月29日 GMT+08:00下午4時43分53秒, Michael Tokarev <m...@tls.msk.ru> wrote:
>29.12.2016 11:15, johnw wrote:
>> Hi Michael,
>>
>> Sorry, I mean "qemu-system-x86_64 -display gtk,gl=on -sandbox on",
>> (not -seccomp on)
>>
>> when I launch -display gtk with -sandbox on, qemu-system-x86_64 will
>freeze,
>> and "ps aux" will show me [qemu-system-x86] 
>
>I see, and still only with gl=on. It looks like some system call
>is filtered which should not be filtered.
>
>For quite some time, looking at the contents of syscall table which
>is allowed in -sandbox mode, I see less and less reason to enable it
>in the first place, because effectively all interesting system calls
>are allowed anyway.  So I don't see this issue as an issue to start
>with, just don't use -sandbox.
>
>Thanks,
>
>/mjt
>
>> I dont have problem, if launch "-display gtk" without "-sandbox on".
>>
>> Thanks.


Key fingerprint: CDB3 6C62 254B C088 1E5D DD32 182C 97DB CF2C 80AC
-BEGIN PGP SIGNATURE-

iQI+BAEBCgAoIRxKb2huIFdvbmcgPGpvaG53Lm1haWxAZ21haWwuY29tPgUCWGTa
qgAKCRB0uKLLoKPihjMuEADI6RKf935kTNRnZbBO/ZavcGPu8/kkvcwURsTbPJ5i
t9+RUFzADRbqddC3eGDWM2WKelplsxPSVunCnuKfpQN/RxrHnfNYAWcApRrgMbjp
+7QasR0cJqDNVm7KJotEHmWnx+fEpCER0zskzQ0oyyX++63BcwIWwPvcHhLDiFk6
ixPTCLm3oWxup1KsYOzJZjZ9f5m4Rp3NNXxwxXdyhZCTm/FCvBuIo5/c8SzyXdQh
7UwCvXJWipdam9Ols6vmMn6APAcKEufmFN32xy0XbvUW/QDp49Q9r3+GHdIEPiRP
CLl95qroONEGi9XZf3XiHbUzrQWMerGD1S5SsDcjyllw5jldQPogWVpY4Zlv1z8h
cOSBaVjlXxe1lxzp6VQ3WUDo0Ph/MGkr7gVTL+BFcyGqBSq21aqJUM1r87BAqPlP
F9SaywZv0cFCnGlok99oaDQedXPDLt9VzYqX51PzcR4qLKMcsbqMT6kofUFj+kvw
4KzEQ07+DItV90hdYIh9r9MO4X3ju5RRsgTa7quIc7CBjtMZjDhLxjybSwsw0Vfx
YxXe06WXlbY7211iwdG/e5ZXPKjavUC3PBuNzlxNm9Pc7NYGNu8Pu4dAtGG0ENU6
RC4h8uYhnqVoOwVCGSIDy1bFUDQdlAaA1S6+BUdaWUcn92tn8JDqwm4YkLlzZEuk
MA==
=pyw5
-END PGP SIGNATURE-

Bug#813658: Please enable virgl support

2016-12-28 Thread johnw 
Hi, I still have some problem after upgrade qemu-system-x86 to 2.8+dfsg-1.

When I launch qemu-system-x86 with spice and gl=on, it show me error and
can not start.
 qemu-system-x86_64: -spice
unix,addr=/tmp/spice-02.sock,disable-ticketing,gl=on: Invalid parameter 'gl'

When I launch qemu-system-x86 with -display gtk,gl=on and -seccomp on,
it just freeze and "ps aux" show me.
[qemu-system-x86] 

Thanks.



signature.asc
Description: OpenPGP digital signature

Bug#813658: Please enable virgl support

2016-12-16 Thread johnw 
On 12/16/2016 08:05 PM, Michael Tokarev wrote:
> 16.12.2016 04:41, john wrote:
>> Package: qemu-system-x86
>> Version: 1:2.7+dfsg-3+b1
>> Followup-For: Bug #813658
>>
>> Dear Maintainer,
>>
>> *** Reporter, please consider answering these questions, where appropriate 
>> ***
>>
>>  Hi, Is it possible use virgl/opengl with debian's package?
>>  (No recompile or hand make binary)
>>
>>  When I launch qemu-system-x86_64 -args  -display,gl=on
>>  (which is "man qemu-system-x86_64" say),
>>  It complain "SDL1 display code has no opengl support" issus.
>>
>>  Please make debian's qemu package support virgl/opengl, thanks.
>>
>> *** End of the template - remove these template lines ***
> John, out of curiocity, what is the reason of this your
> follow-up, why you sent it? Do you happen to know how to
> deal with the concerns outlined in this bugreport already?
>
> Thanks,
>
> /mjt
>
Hi Michael,

No, unfortunately I do not have any idea, how to deal with. :(

I send this mail, because I have this problem and want to know people
how to solve it,

So, I want to follow the bugreport, maybe someday developer will solve it.

Thanks.




signature.asc
Description: OpenPGP digital signature

Bug#840820: linux-image-grsec-amd64 kernel break CLONE_NEWUSER / newuidmap / unprivileged lxc containers

2016-11-17 Thread johnw 
On 11/15/2016 12:53 AM, Alex Mestiashvili wrote:
> Just stumbled upon the same problem, it seems that CLONE_NEWUSER  (
> and as the consequence unprivileged containers ) simply doesn't work
> with grecurity patched kernel, see:
>
>  https://forums.grsecurity.net/viewtopic.php?f=3=3929
>
> You can see if  "user namespaces" works with this code:
> https://lwn.net/Articles/539941/
>
I find out the problem is new[ug]idmap, patch new[ug]idmap.c (uidmap
package) solved it,

I attached patches for your reference.

Thanks.



--- newgidmap.c.orig	2016-11-17 17:29:16.164529187 +0800
+++ newgidmap.c	2016-11-17 17:28:22.904741277 +0800
@@ -159,7 +159,11 @@
 	if ((getuid() != pw->pw_uid) ||
 	(getgid() != pw->pw_gid) ||
 	(pw->pw_uid != st.st_uid) ||
-	(pw->pw_gid != st.st_gid)) {
+	(pw->pw_gid != st.st_gid && st.st_gid != 64044)) {
+		fprintf(stderr, _( "getuid(%lu) != pw->pw_uid(%lu)\n" ), getuid(), pw->pw_uid);
+fprintf(stderr, _( "getgid(%lu) != pw->pw_gid(%lu)\n" ), getgid(), pw->pw_gid);
+fprintf(stderr, _( "pw->pw_uid(%lu) != st.st_uid(%lu)\n" ), pw->pw_uid, st.st_uid);
+fprintf(stderr, _( "pw->pw_gid(%lu) != st.st_gid(%lu)\n" ), pw->pw_gid, st.st_gid);
 		fprintf(stderr, _( "%s: Target %u is owned by a different user\n" ),
 			Prog, target);
 		return EXIT_FAILURE;
--- newuidmap.c.orig	2016-11-17 17:28:53.124620939 +0800
+++ newuidmap.c	2016-11-17 17:28:22.908741260 +0800
@@ -159,7 +159,12 @@
 	if ((getuid() != pw->pw_uid) ||
 	(getgid() != pw->pw_gid) ||
 	(pw->pw_uid != st.st_uid) ||
-	(pw->pw_gid != st.st_gid)) {
+	(pw->pw_gid != st.st_gid && st.st_gid != 64044)) {
+		fprintf(stderr, _( "getuid(%lu) != pw->pw_uid(%lu)\n" ), getuid(), pw->pw_uid);
+		fprintf(stderr, _( "getgid(%lu) != pw->pw_gid(%lu)\n" ), getgid(), pw->pw_gid);
+		fprintf(stderr, _( "pw->pw_uid(%lu) != st.st_uid(%lu)\n" ), pw->pw_uid, st.st_uid);
+		fprintf(stderr, _( "pw->pw_gid(%lu) != st.st_gid(%lu)\n" ), pw->pw_gid, st.st_gid);
+
 		fprintf(stderr, _( "%s: Target %u is owned by a different user\n" ),
 			Prog, target);
 		return EXIT_FAILURE;


0xCF2C80AC.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature

Bug#840592: vim: Setting in /etc/vim/vimrc no effect / not working

2016-10-13 Thread johnw 
On 10/14/2016 09:11 AM, James McCoy wrote:
> On Thu, Oct 13, 2016 at 10:12:32AM +0800, john wrote:
>>Setting in /etc/vim/vimrc or /etc/vim/vimrc.local no
>>effect.
>>
>>Only setting in $HOME/.vimrc work.
> As already discussed in other bug reports and in the NEWS file, Vim now
> ships with a defaults.vim that is loaded when the user has no vimrc.
>
> See ":help defaults.vim" for more information.
>
> You can either disable it in your system vimrc or load it then and
> override the options you don't like.
>
> Cheers,

Yes, you are right, thank your help and close the bug, thanks.


-- 
Key fingerprint: CDB3 6C62 254B C088 1E5D DD32 182C 97DB CF2C 80AC




signature.asc
Description: OpenPGP digital signature

Bug#840592: vim: Setting in /etc/vim/vimrc no effect / not working

2016-10-12 Thread johnw 
On 10/13/2016 10:12 AM, john wrote:
> Package: vim
> Version: 2:8.0.0022-1
> Severity: normal
>
> Dear Maintainer,
>
> *** Reporter, please consider answering these questions, where appropriate ***
>
>* What led up to the situation?
>
>Setting in /etc/vim/vimrc or /etc/vim/vimrc.local no
>effect.
>
>Only setting in $HOME/.vimrc work.
>
>ls -l /usr/share/vimrc -> /etc/vim/vimrc
>ls -l /usr/share/vimfiles -> /etc/vim
>
>Please help, thank you.
>
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
>* What was the outcome of this action?
>* What outcome did you expect instead?
>
> *** End of the template - remove these template lines ***
>
>
> -- Package-specific info:
>
> --- real paths of main Vim binaries ---
> /usr/bin/vi is /usr/bin/vim.gtk3
> /usr/bin/vim is /usr/bin/vim.gtk3
> /usr/bin/gvim is /usr/bin/vim.gtk3
>
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 4.7.0-1-grsec-amd64 (SMP w/8 CPU cores)
> Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages vim depends on:
> ii  libacl1  2.2.52-3
> ii  libc62.24-3
> ii  libgpm2  1.20.4-6.2
> ii  libselinux1  2.5-3
> ii  libtinfo56.0+20160917-1
> ii  vim-common   2:8.0.0022-1
> ii  vim-runtime  2:8.0.0022-1
>
> vim recommends no packages.
>
> Versions of packages vim suggests:
> pn  ctags
> pn  vim-doc  
> pn  vim-scripts  
>
> -- no debconf information

Sorry, forget to mention, I want set "syntax off" by default.

Thanks.




signature.asc
Description: OpenPGP digital signature

Bug#838546: closed by Ximin Luo <infini...@debian.org> (Bug#838546: fixed in mozilla-gnome-keyring 0.11+git4-2)

2016-09-24 Thread johnw 
On 09/22/2016 07:51 PM, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the xul-ext-gnome-keyring package:
>
> #838546: firefox 49.0-1 (amd64) break xul-ext-gnome-keyring
>
> It has been closed by Ximin Luo .
>
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Ximin Luo 
>  by
> replying to this email.
>
>
Hi, After upgrade to "xul-ext-gnome-keyring 0.11+git4-3", I still have
this problem.

Please help, thank you.



0xCF2C80AC.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature

Bug#838546: closed by Ximin Luo <infini...@debian.org> (Bug#838546: fixed in mozilla-gnome-keyring 0.11+git4-2)

2016-09-23 Thread johnw 
On 09/22/2016 07:51 PM, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the xul-ext-gnome-keyring package:
>
> #838546: firefox 49.0-1 (amd64) break xul-ext-gnome-keyring
>
> It has been closed by Ximin Luo .
>
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Ximin Luo 
>  by
> replying to this email.
>
>
Hi, where can I download it (new verison of xul-ext-gnome-keyring) ?

Thanks.



0xCF2C80AC.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature

Bug#800120: pulseaudio: No sound after upgrade to pulseaudio 7.0-1

2015-09-29 Thread johnw 

On Monday, September 28, 2015 07:13 PM, Felipe Sateler wrote:

Control: forwarded -1 https://bugs.freedesktop.org/show_bug.cgi?id=92141

On 28 September 2015 at 07:03, Felipe Sateler  wrote:

Control: tags -1 moreinfo

Hi,

On 26 September 2015 at 23:50, john  wrote:

Package: pulseaudio
Version: 7.0-1
Severity: normal

Dear Maintainer,

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

No sound after upgrade pulseaudio 7.0-1,
when I run alsamixer:

ALSA lib pulse.c:243:(pulse_connect) PulseAudio: Unable to connect:
Protocol error

cannot open mixer: Connection refused

Could you please attach a verbose log of pulseaudio[1] and then reproduce this?

Also, does pavucontrol work or only alsamixer fails?

Here are better instructions provided by upstream[1], if you could
post the information it would be great.

First, install libpulse0-dbg, pulseaudio-utils-dbg and gdb. Then
follow the steps described by upstream:


% PULSE_LOG=99 gdb --args pactl stat

That will print something like this:

GNU gdb (Debian 7.10-1) 7.10
Copyright (C) 2015 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 pactl...done.
(gdb)

You're now in the gdb prompt. Enter "break pa_memimport_get". That
symbol hasn't yet been loaded, so gdb asks you whether to add the
breakpoint when the symbol becomes available. Answer "y". Then enter
"run". The execution should soon stop at the breakpoint. From now on
enter "n" ("n" is short for "next") repeatedly until the program exits
(that will take quite some time). When the program exits, you can quit
gdb with command "quit", and then save all the terminal output and
attach it here. That should show the exact place that fails.



[1] https://bugs.freedesktop.org/show_bug.cgi?id=92141#c6



Hi, attached log file for your reference, and below is the gdb log, thanks.

GNU gdb (Debian 7.10-1) 7.10
Copyright (C) 2015 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 "i586-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 pactl...(no debugging symbols found)...done.
(gdb) break pa_memimport_get
Make breakpoint pending on future shared library load? (y or [n]) y
Breakpoint 1 (pa_memimport_get) pending.
(gdb) run
Starting program: /usr/bin/pactl stat
[Thread debugging using libthread_db enabled]
Using host libthread_db library 
"/lib/i386-linux-gnu/i686/cmov/libthread_db.so.1".


Breakpoint 1, pa_memimport_get (i=0x805a048, block_id=896, 
shm_id=1861523114, offset=40, size=65496, writable=true) at 
pulsecore/memblock.c:1009

(gdb) n
1013in pulsecore/memblock.c
(gdb) n
1015in pulsecore/memblock.c
(gdb) n
1017in pulsecore/memblock.c
(gdb) n
1022in pulsecore/memblock.c
(gdb) n
1025in pulsecore/memblock.c
(gdb) n
1026in pulsecore/memblock.c
(gdb) n
1029in pulsecore/memblock.c
(gdb) n
1034in pulsecore/memblock.c
(gdb) n
1037in pulsecore/memblock.c
(gdb) n
1038in pulsecore/memblock.c
(gdb) n
1040in pulsecore/memblock.c
(gdb) n
1043in pulsecore/memblock.c
(gdb) n
1052in pulsecore/memblock.c
(gdb) n
1040in pulsecore/memblock.c
(gdb) n
1041in pulsecore/memblock.c
(gdb) n
1043in pulsecore/memblock.c
(gdb) n
1042in pulsecore/memblock.c
(gdb) n
1041in pulsecore/memblock.c
(gdb) n
1043in pulsecore/memblock.c
(gdb) n
1044in pulsecore/memblock.c
(gdb) n
1045in pulsecore/memblock.c
(gdb) n
1046in pulsecore/memblock.c
(gdb) n
1047in pulsecore/memblock.c
(gdb) n
1046in pulsecore/memblock.c
(gdb) n
1047in pulsecore/memblock.c
(gdb) n
1048in pulsecore/memblock.c
(gdb) n
1049in pulsecore/memblock.c
(gdb) n
1050in pulsecore/memblock.c
(gdb) n
1049in pulsecore/memblock.c
(gdb) n
1052in pulsecore/memblock.c
(gdb) n

Bug#800120: pulseaudio: No sound after upgrade to pulseaudio 7.0-1

2015-09-29 Thread johnw 

On Monday, September 28, 2015 07:13 PM, Felipe Sateler wrote:

Control: forwarded -1 https://bugs.freedesktop.org/show_bug.cgi?id=92141

On 28 September 2015 at 07:03, Felipe Sateler  wrote:

Control: tags -1 moreinfo

Hi,

On 26 September 2015 at 23:50, john  wrote:

Package: pulseaudio
Version: 7.0-1
Severity: normal

Dear Maintainer,

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

No sound after upgrade pulseaudio 7.0-1,
when I run alsamixer:

ALSA lib pulse.c:243:(pulse_connect) PulseAudio: Unable to connect:
Protocol error

cannot open mixer: Connection refused

Could you please attach a verbose log of pulseaudio[1] and then reproduce this?

Also, does pavucontrol work or only alsamixer fails?

Here are better instructions provided by upstream[1], if you could
post the information it would be great.

First, install libpulse0-dbg, pulseaudio-utils-dbg and gdb. Then
follow the steps described by upstream:


% PULSE_LOG=99 gdb --args pactl stat

That will print something like this:

GNU gdb (Debian 7.10-1) 7.10
Copyright (C) 2015 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 pactl...done.
(gdb)

You're now in the gdb prompt. Enter "break pa_memimport_get". That
symbol hasn't yet been loaded, so gdb asks you whether to add the
breakpoint when the symbol becomes available. Answer "y". Then enter
"run". The execution should soon stop at the breakpoint. From now on
enter "n" ("n" is short for "next") repeatedly until the program exits
(that will take quite some time). When the program exits, you can quit
gdb with command "quit", and then save all the terminal output and
attach it here. That should show the exact place that fails.



[1] https://bugs.freedesktop.org/show_bug.cgi?id=92141#c6



Hi, attached log file for your reference, and below is the gdb log, thanks.

GNU gdb (Debian 7.10-1) 7.10
Copyright (C) 2015 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 "i586-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 pactl...(no debugging symbols found)...done.
(gdb) break pa_memimport_get
Make breakpoint pending on future shared library load? (y or [n]) y
Breakpoint 1 (pa_memimport_get) pending.
(gdb) run
Starting program: /usr/bin/pactl stat
[Thread debugging using libthread_db enabled]
Using host libthread_db library 
"/lib/i386-linux-gnu/i686/cmov/libthread_db.so.1".


Breakpoint 1, pa_memimport_get (i=0x805a048, block_id=896, 
shm_id=1861523114, offset=40, size=65496, writable=true) at 
pulsecore/memblock.c:1009

(gdb) n
1013in pulsecore/memblock.c
(gdb) n
1015in pulsecore/memblock.c
(gdb) n
1017in pulsecore/memblock.c
(gdb) n
1022in pulsecore/memblock.c
(gdb) n
1025in pulsecore/memblock.c
(gdb) n
1026in pulsecore/memblock.c
(gdb) n
1029in pulsecore/memblock.c
(gdb) n
1034in pulsecore/memblock.c
(gdb) n
1037in pulsecore/memblock.c
(gdb) n
1038in pulsecore/memblock.c
(gdb) n
1040in pulsecore/memblock.c
(gdb) n
1043in pulsecore/memblock.c
(gdb) n
1052in pulsecore/memblock.c
(gdb) n
1040in pulsecore/memblock.c
(gdb) n
1041in pulsecore/memblock.c
(gdb) n
1043in pulsecore/memblock.c
(gdb) n
1042in pulsecore/memblock.c
(gdb) n
1041in pulsecore/memblock.c
(gdb) n
1043in pulsecore/memblock.c
(gdb) n
1044in pulsecore/memblock.c
(gdb) n
1045in pulsecore/memblock.c
(gdb) n
1046in pulsecore/memblock.c
(gdb) n
1047in pulsecore/memblock.c
(gdb) n
1046in pulsecore/memblock.c
(gdb) n
1047in pulsecore/memblock.c
(gdb) n
1048in pulsecore/memblock.c
(gdb) n
1049in pulsecore/memblock.c
(gdb) n
1050in pulsecore/memblock.c
(gdb) n
1049in pulsecore/memblock.c
(gdb) n
1052in pulsecore/memblock.c
(gdb) n

Bug#800120: pulseaudio: No sound after upgrade to pulseaudio 7.0-1

2015-09-29 Thread johnw 

On Tuesday, September 29, 2015 10:39 PM, Felipe Sateler wrote:

On 29 September 2015 at 11:35, johnw <johnw.m...@gmail.com> wrote:

On Tuesday, September 29, 2015 10:11 PM, Felipe Sateler wrote:

On 29 September 2015 at 10:12, johnw <johnw.m...@gmail.com> wrote:

On Monday, September 28, 2015 07:13 PM, Felipe Sateler wrote:

Control: forwarded -1 https://bugs.freedesktop.org/show_bug.cgi?id=92141

On 28 September 2015 at 07:03, Felipe Sateler <fsate...@debian.org>
wrote:

Control: tags -1 moreinfo

Hi,

On 26 September 2015 at 23:50, john <johnw.m...@gmail.com> wrote:

Package: pulseaudio
Version: 7.0-1
Severity: normal

Dear Maintainer,

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

  No sound after upgrade pulseaudio 7.0-1,
  when I run alsamixer:

  ALSA lib pulse.c:243:(pulse_connect) PulseAudio: Unable to
connect:
  Protocol error

  cannot open mixer: Connection refused

Could you please attach a verbose log of pulseaudio[1] and then
reproduce
this?

Also, does pavucontrol work or only alsamixer fails?

Here are better instructions provided by upstream[1], if you could
post the information it would be great.

First, install libpulse0-dbg, pulseaudio-utils-dbg and gdb. Then
follow the steps described by upstream:


% PULSE_LOG=99 gdb --args pactl stat

That will print something like this:

GNU gdb (Debian 7.10-1) 7.10
Copyright (C) 2015 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 pactl...done.
(gdb)

You're now in the gdb prompt. Enter "break pa_memimport_get". That
symbol hasn't yet been loaded, so gdb asks you whether to add the
breakpoint when the symbol becomes available. Answer "y". Then enter
"run". The execution should soon stop at the breakpoint. From now on
enter "n" ("n" is short for "next") repeatedly until the program exits
(that will take quite some time). When the program exits, you can quit
gdb with command "quit", and then save all the terminal output and
attach it here. That should show the exact place that fails.



[1] https://bugs.freedesktop.org/show_bug.cgi?id=92141#c6



Hi, attached log file for your reference, and below is the gdb log,
thanks.

Hm, strange, I don't see any program output there.  What does `pactl
stat` say (without the gdb part) ? Also, please also answer the other
questions I sent, to determine if it is the same bug or not.


pactl stat
Currently in use: 1 blocks containing 64.0 KiB bytes total.
Allocated during whole lifetime: 443 blocks containing 1.8 MiB bytes total.
Sample cache size: 0 B
kaka@kvm102:~$ echo $?
0

This looks like pulseaudio is working normally. Does pavucontrol work?

Or perhaps it is only some applications that do not work?

Yes, pavucontrol work now, I do not know why, but it can not work 
before, it just load the screen and hang.


because pavucontrol not work before, then I think it is not firejail 
problem, but actually, the problem is smplayer with firejail.


I am really sorry for waste your time.

If I run smplayer/mplayer without firejail, the sound work as normal.

Thank for you help, thanks.

I will CC this mail to 800120-cl...@bugs.debian.org

Bug#800120: pulseaudio: No sound after upgrade to pulseaudio 7.0-1

2015-09-29 Thread johnw 

On Tuesday, September 29, 2015 10:11 PM, Felipe Sateler wrote:

On 29 September 2015 at 10:12, johnw <johnw.m...@gmail.com> wrote:

On Monday, September 28, 2015 07:13 PM, Felipe Sateler wrote:

Control: forwarded -1 https://bugs.freedesktop.org/show_bug.cgi?id=92141

On 28 September 2015 at 07:03, Felipe Sateler <fsate...@debian.org> wrote:

Control: tags -1 moreinfo

Hi,

On 26 September 2015 at 23:50, john <johnw.m...@gmail.com> wrote:

Package: pulseaudio
Version: 7.0-1
Severity: normal

Dear Maintainer,

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

 No sound after upgrade pulseaudio 7.0-1,
 when I run alsamixer:

 ALSA lib pulse.c:243:(pulse_connect) PulseAudio: Unable to connect:
 Protocol error

 cannot open mixer: Connection refused

Could you please attach a verbose log of pulseaudio[1] and then reproduce
this?

Also, does pavucontrol work or only alsamixer fails?

Here are better instructions provided by upstream[1], if you could
post the information it would be great.

First, install libpulse0-dbg, pulseaudio-utils-dbg and gdb. Then
follow the steps described by upstream:


% PULSE_LOG=99 gdb --args pactl stat

That will print something like this:

GNU gdb (Debian 7.10-1) 7.10
Copyright (C) 2015 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 pactl...done.
(gdb)

You're now in the gdb prompt. Enter "break pa_memimport_get". That
symbol hasn't yet been loaded, so gdb asks you whether to add the
breakpoint when the symbol becomes available. Answer "y". Then enter
"run". The execution should soon stop at the breakpoint. From now on
enter "n" ("n" is short for "next") repeatedly until the program exits
(that will take quite some time). When the program exits, you can quit
gdb with command "quit", and then save all the terminal output and
attach it here. That should show the exact place that fails.



[1] https://bugs.freedesktop.org/show_bug.cgi?id=92141#c6



Hi, attached log file for your reference, and below is the gdb log, thanks.

Hm, strange, I don't see any program output there.  What does `pactl
stat` say (without the gdb part) ? Also, please also answer the other
questions I sent, to determine if it is the same bug or not.


pactl stat
Currently in use: 1 blocks containing 64.0 KiB bytes total.
Allocated during whole lifetime: 443 blocks containing 1.8 MiB bytes total.
Sample cache size: 0 B
kaka@kvm102:~$ echo $?
0
kaka@kvm102:~$ ps auxZ |grep pulse
unconfined  kaka  4842  0.0  0.1 166912 9216 
?Sl   22:31   0:00 /usr/bin/pulseaudio --start --log-target=syslog


No, I do not use firejail / any sandbox with pulse-*-thing

Bug#800120: pulseaudio: No sound after upgrade to pulseaudio 7.0-1

2015-09-27 Thread johnw 
Hi all, It work again, after downgrade libpulse0 and pulseaudio to 
6.0.5, thanks.

Bug#766581: [Pkg-ime-devel] Bug#766581: ibus: After upgrade to 1.5.9-1, can not input chinese (class quick)

2014-10-26 Thread johnw 

Hi Osamu, sorry to say that, but I do not why, it work right now. :)

What I did is choice use different font in ibus, and different setting,
then it work, I choice the original font and setting again, it still work.

I wild guess the problem is after dist-upgrade, some setting/config 
file(s) change the format or something like this,
so when I change the setting, the new format setting/config is saved, 
then ibus work again.
the config/setting file maybe is for ibus-* or xfce4-*, maybe, I do not 
know.


Anyway, thank you.


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

Bug#766581: ibus: After upgrade to 1.5.9-1, can not input chinese (class quick)

2014-10-25 Thread johnw 

On 2014年10月25日 星期六 09:12 下午, Osamu Aoki wrote:


This is caused since ibus-table-foo packages are not updated with the
newest version yet (they are already uploaded).  If you dist-update again,
this should be fixed.

The proper fix to the root cause is add versioned Breaks: with long list
of packages ibus-table-*.

List all packlages from ibus-table-chinese with ( 1.4.6-Source-2~)
List all packlages from ibus-table-others with ( 1.3.0.20100528-3~)



After dist-upgrade still have a problem.

dpkg -l |grep ibus:

ii  gir1.2-ibus-1.0:amd64 1.5.9-1   
amd64Intelligent Input Bus - introspection data
ii  ibus 1.5.9-1   amd64Intelligent 
Input Bus - core
ii  ibus-clutter:amd64 0.0+git20090728.a936bacf-5.1+b1   
amd64ibus input method framework for clutter
ii  ibus-gtk:amd64 1.5.9-1   amd64
Intelligent Input Bus - GTK+2 support
ii  ibus-gtk3:amd64 1.5.9-1   amd64
Intelligent Input Bus - GTK+3 support
ii  ibus-qt4 1.3.2-2   amd64
qt-immodule for ibus (QT4) (plugin)
ii  ibus-table 1.9.1-1   all  table 
engine for IBus
ii  ibus-table-quick 1.4.6-Source-2all  
ibus-table input method: Quick (dummy package)
ii  ibus-table-quick-classic 1.4.6-Source-2
all  ibus-table input method: Quick Classic
ii  ibus-table-quick3 1.4.6-Source-2all  
ibus-table input method: Quick3
ii  ibus-table-quick5 1.4.6-Source-2all  
ibus-table input method: Quick5
ii  libgusb2:amd64 0.1.6-5   amd64
GLib wrapper around libusb1
ii  libibus-1.0-5:amd64 1.5.9-1   
amd64Intelligent Input Bus - shared library
ii  libibus-qt1 1.3.2-2   amd64
qt-immodule for ibus (QT4) (library)
ii  libusageenvironment1 2014.01.13-1  
amd64multimedia RTSP streaming library (UsageEnvironment classes)
ii  libusb-0.1-4:amd64 2:0.1.12-25   
amd64userspace USB programming library
ii  libusb-1.0-0:amd64 2:1.0.19-1
amd64userspace USB programming library
ii  libusbmuxd2:amd64 1.0.9-1   amd64
USB multiplexor daemon for iPhone and iPod Touch devices - library
ii  libusbredirhost1:amd64 0.7-1 
amd64Implementing the usb-host (*) side of a usbredir connection 
(runtime)
ii  libusbredirparser1:amd64 0.7-1 
amd64Parser for the usbredir protocol (runtime)
ii  libustr-1.0-1:amd64 1.0.4-3   
amd64Micro string library: shared library


Thank you.


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

Bug#766581: ibus: After upgrade to 1.5.9-1, can not input chinese (class quick)

2014-10-25 Thread johnw 

On 2014年10月26日 星期日 01:01 上午, Osamu Aoki wrote:

Hi,

On Sat, Oct 25, 2014 at 10:00:22PM +0800, johnw wrote:

After dist-upgrade still have a problem.

Did you restarted PC (or at least started new X session.) after upgrade?

Regards,

Osamu

Yes, I did restart, but still not work
(notice: now dist-upgrade ibus-table to 1.9.1-3, 
ibus-table-quick-classic to 1.8.2-1).


dpkg -l |grep ibus

ii  gir1.2-ibus-1.0:amd64 1.5.9-1   
amd64Intelligent Input Bus - introspection data
ii  ibus-clutter:amd64 0.0+git20090728.a936bacf-5.1+b1   
amd64ibus input method framework for clutter
ii  ibus-gtk:amd64 1.5.9-1   amd64
Intelligent Input Bus - GTK+2 support
ii  ibus-gtk3:amd64 1.5.9-1   amd64
Intelligent Input Bus - GTK+3 support
ii  ibus-qt4 1.3.2-2   amd64
qt-immodule for ibus (QT4) (plugin)
ii  ibus-table 1.9.1-3   all  table 
engine for IBus
ii  ibus-table-quick 1.8.2-1   all  
ibus-table input method: Quick (dummy package)
ii  ibus-table-quick-classic 1.8.2-1   
all  ibus-table input method: Quick Classic
ii  ibus-table-quick3 1.8.2-1   all  
ibus-table input method: Quick3
ii  ibus-table-quick5 1.8.2-1   all  
ibus-table input method: Quick5
ii  libibus-1.0-5:amd64 1.5.9-1   
amd64Intelligent Input Bus - shared library
ii  libibus-qt1 1.3.2-2   amd64
qt-immodule for ibus (QT4) (library)


Thank you.


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

Bug#750844: apparmor-notify: aa-notify started but no notification

2014-08-31 Thread johnw 

On 08/29/2014 05:44 AM, intrigeri wrote:

Hi John,

what do these command output:

   $ sudo grep apparmor /var/log/kern.log
   $ aa-notify -p -s 1 -w 60

?

Cheers,
--
intrigeri

Hello Intrigeri,
sudo grep apparmor /var/log/kern.log
Aug 31 22:06:06 redcat kernel: [0.00] Command line: 
BOOT_IMAGE=/boot/vmlinuz-3.14-2-amd64 
root=UUID=cc5cf21d-ec9f-4bbc-87b0-e1fbd1bc5351 ro apparmor=1 
security=apparmor quiet
Aug 31 22:06:06 redcat kernel: [0.00] Kernel command line: 
BOOT_IMAGE=/boot/vmlinuz-3.14-2-amd64 
root=UUID=cc5cf21d-ec9f-4bbc-87b0-e1fbd1bc5351 ro apparmor=1 
security=apparmor quiet


aa-notify -p -s 1 -w 60 is already start at boot automatically,

john@redcat:~$ ps aux |grep aa-notify
john  3435  0.0  0.0  39876  5216 ?Ss   14:05   0:01 
/usr/bin/perl /usr/bin/aa-notify -p -s 1 -w 60
john 27567  0.0  0.0  12624   936 pts/4S+   17:39   0:00 grep 
--color=auto aa-notify


If I kill it(3435), then run /usr/bin/aa-notify -p -s 1 -w 60
john@redcat:~$ /usr/bin/aa-notify -p -s 1 -w 60
Starting aa-notify

It start and run without warning/error message.

Thank you.


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

Bug#756375: After upgrade systemd-* to 208-7, I still have this problem

2014-08-07 Thread johnw 

After upgrade systemd-* to 208-7, I still have this problem.
Please help, thank you.


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

Bug#756375: After upgrade systemd-* to 208-7, I still have this problem

2014-08-07 Thread johnw 

On 08/07/2014 05:07 PM, Michael Biebl wrote:

Am 07.08.2014 11:00, schrieb johnw:

After upgrade systemd-* to 208-7, I still have this problem.
Please help, thank you.

Have you tried uninstalling/purging the ulatencyd package?

Yes, I already tried dpkg --purge ulatency ulatencyd, then rm -rf 
/etc/ulatencyd/

then install ulatencyd again.
but unfortunately, it did not help.

(I also tried add 3 lines to /etc/systemd/system.conf)
DefaultControllers=
JoinControllers=
Controllers=

Thank you.


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

Bug#756375: After upgrade systemd-* to 208-7, I still have this problem

2014-08-07 Thread johnw 

On 08/07/2014 05:21 PM, Michael Biebl wrote:

Uninstalling and re-installing obviously has no effect.

Oh, you mean is uninstall/remove ulatencyd (not reinstall),
Yes, I did it, and can solve the problem.
But I want ulatencyd.


The instructions I linked also mention that you need to disable the
pam_systemd PAM module. Have you done that?
Keep in mind that this will break a lot of stuff under systemd, though.

The FAQ say add those line OR disable PAM.
https://github.com/poelzi/ulatencyd/wiki/Faq#id4
I also tried diable pam_system PAM module, but did not help.
and it will break the shutdown behavior.
(when I click the shutdown button, it just logout, not try to shutdown)



Btw, why do you need ulatencyd at all?



Because I feel it can make more smooth on my desktop.
(Yes, I really can feel it)

Anyway, I would remove ulatenyd, If this is know issues and can not be 
solve.


I would close this bug report, if you agree.
(Because this is know issues and can not be solve)

Thank you.


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

Bug#750844: apparmor-notify: aa-notify started but no notification

2014-06-08 Thread johnw 

On 2014年06月08日 星期日 12:29 上午, intrigeri wrote:
What do you have in /etc/apparmor/notify.conf ? How does please run 
aa-notify in the Perl debugger sound to your ear? Cheers, 

Hi, what is Perl debugger?

# --
#
#Copyright (C) 2010 Canonical Ltd.
#
#This program is free software; you can redistribute it and/or
#modify it under the terms of version 2 of the GNU General Public
#License published by the Free Software Foundation.
#
# --

# Set to 'no' to disable AppArmor notifications globally
show_notifications=yes

# Only people in use_group can use aa-notify
use_group=adm

Sorry to say that, I don't know why,
but now, aa-notify will startup automatically on system bootup.

Now, my only problem is, aa-notity do not send the notify messages,
when some program denied by apparmor.

Thanks.


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

Bug#750844: apparmor-notify: aa-notify started but no notification

2014-06-07 Thread johnw 

On 2014年06月07日 星期六 10:17 下午, intrigeri wrote:

Hi

I'm slightly confused: the bug title says that aa-notify is started,
and now you're telling us that it is not. May you please clarify?

Sorry, confused you and other, I mean aa-notify is started manually by hand,
not started by init script or systemd or any thing automatic on system 
bootup

(on my old computer, aa-notify will started on system boot automatically)

FTR, aa-notify starts just fine on my own sid (running GNOME Shell),
but I can't easily reproduce the no notification part, as I'm only
using the systemd journal (that's not supported by aa-notify yet), and
have disabled syslog, so my kern.log is empty.
Umm. I will search what is systemd journal, Yes my system also installed 
systemd

-
dpkg -l |grep systemd
ii  libpam-systemd:amd64 204-10 amd64
system and service manager - PAM module
ii  libsystemd-daemon0:amd64 204-10 
amd64systemd utility library
ii  libsystemd-id128-0:amd64 204-10 
amd64systemd 128 bit ID utility library
ii  libsystemd-journal0:amd64 204-10 
amd64systemd journal utility library
ii  libsystemd-login0:amd64 204-10 
amd64systemd login utility library
ii  systemd 204-10 amd64system and 
service manager
ii  systemd-sysv 204-10 amd64system 
and service manager - SysV links

-

A simple check, just in case: did you logout and log in again after
doing this change?


Yes, I already did it. (login/shutdown/reboot)

If you started aa-notify by hand, what options did you pass it?
The default (as set in /etc/X11/Xsession.d/90apparmor-notify) is to
call:

   /usr/bin/aa-notify -p -s 1 -w 60

Yes, I tried /usr/bin/aa-notify -p -s 1 -w 60
/usr/bin/aa-notify -p --display $DISPLAY -s 7 -w 60
/usr/bin/aa-notify -p --display $DISPLAY -s 7 -w 60 -f /var/log/kern.log

all started by manually/hand,
and if I type echo $DISPLAY, it will show :0.0


Another thing worth checking is whether you have a libnotify
compatible daemon running: what desktop environment are you running?

My system is running sid/64bit/xfce4/gdm3/systemd .
Yes, I already installed libnotify.

dpkg -l |grep notify
ii  apparmor-notify 2.8.0-5.1  all  
AppArmor notification system
ii  gir1.2-notify-0.7 0.7.6-2amd64
sends desktop notifications to a notification daemon (Introspection files)
ii  libnotify-bin 0.7.6-2amd64sends 
desktop notifications to a notification daemon (Utilities)
ii  libnotify4:amd64 0.7.6-2amd64
sends desktop notifications to a notification daemon
ii  python-notify 0.1.1-3amd64Python 
bindings for libnotify
ii  vlc-plugin-notify 2.1.4-1+b2 amd64
LibNotify plugin for VLC
ii  xfce4-notifyd 0.2.4-3amd64
simple, visually-appealing notification daemon for Xfce


I know aa-notify is written by perl, I tried force it send notify 
messages for debug/testing.

--- /usr/bin/aa-notify2014-06-05 19:13:09.0 +0800
+++ /tmp/aa-notify2014-06-07 23:00:07.586682497 +0800
@@ -376,6 +376,7 @@
 $SIG{INT} = $SIG{TERM} = $SIG{HUP} = \signal_handler;
 $SIG{'PIPE'} = 'IGNORE';

+send_message(testing);
 if ($opt_w) {
 sleep($opt_w);
 }
It can send the notify message.

How can I find out what problem?
why it can not send the apparmor's notify message.

Thank you.


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

Bug#749963: Should be software problem

2014-05-31 Thread johnw 

I think this issue is software problem (not hardware),
because, when I use chromium with flash (download from google-chrome),
watching youtue movie (flash version), the movie is very smooth,
and the sound is also good.

Anyone have idea?
Thanks.


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

Bug#728342: [Pkg-xfce-devel] Bug#728342: 1.8.5-1 still have this problem

2013-11-08 Thread johnw 

On 11/08/2013 02:52 PM, Yves-Alexis Perez wrote:

On Fri, 2013-11-08 at 10:55 +0800, johnw wrote:

Hi, after upgrade lightdm to 1.8.5-1, I still have this problem.
(lightdm greeter hangs and no restart/shutdown ... buttom)

downgrade lightdm to 1.6.3-1 without those problem.
my debian is sid/amd64.


Yeah, there's no ConsoleKit-related changes in this update, so it looks
normal that it doesn't change anything.

I'm honestly lost on this, I can't reproduce your issue and I'm out of
ideas, so you (and other people experiencing it) will have to
investigate yourself.

Regards,
Hi, After edited /etc/X11/Xsession.d/90consolekit, then the 
reboot/shutdown button work again.

(but the hang/delay problem is still here)

change $GDMSESSION to $GDMSESSION_IS_NOT_Z
and$XDG_SESSION to $XDG_SESSION_IS_NOT_Z

Thanks.


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

Bug#728342: [Pkg-xfce-devel] Bug#728342: 1.8.5-1 still have this problem

2013-11-08 Thread johnw 

On 11/08/2013 10:55 PM, Yves-Alexis Perez wrote:

On Fri, 2013-11-08 at 21:04 +0800, johnw wrote:

Hi, After edited /etc/X11/Xsession.d/90consolekit, then the
reboot/shutdown button work again.
(but the hang/delay problem is still here)

change $GDMSESSION to $GDMSESSION_IS_NOT_Z
and$XDG_SESSION to $XDG_SESSION_IS_NOT_Z

Remind me the consolekit version you have?

shell:~$ dpkg -l |grep -i consolekit
ii  consolekit 0.4.6-3+b1amd64framework 
for defining and tracking users, sessions and seats
ii  libck-connector0:amd64 0.4.6-3+b1
amd64ConsoleKit libraries
ii  libpam-ck-connector:amd64 0.4.6-3+b1
amd64ConsoleKit PAM module



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

Bug#728342: [Pkg-xfce-devel] Bug#728342: 1.8.5-1 still have this problem

2013-11-08 Thread johnw 

On 11/08/2013 11:02 PM, Yves-Alexis Perez wrote:

On Fri, 2013-11-08 at 22:58 +0800, johnw wrote:

On 11/08/2013 10:55 PM, Yves-Alexis Perez wrote:

On Fri, 2013-11-08 at 21:04 +0800, johnw wrote:

Hi, After edited /etc/X11/Xsession.d/90consolekit, then the
reboot/shutdown button work again.
(but the hang/delay problem is still here)

change $GDMSESSION to $GDMSESSION_IS_NOT_Z
and$XDG_SESSION to $XDG_SESSION_IS_NOT_Z

Remind me the consolekit version you have?

shell:~$ dpkg -l |grep -i consolekit
ii  consolekit 0.4.6-3+b1amd64framework
for defining and tracking users, sessions and seats
ii  libck-connector0:amd64 0.4.6-3+b1
amd64ConsoleKit libraries
ii  libpam-ck-connector:amd64 0.4.6-3+b1
amd64ConsoleKit PAM module


Ok, same version as me, and it /does/ work fine with the original
$GDMSESSION/$XDG_SESSION (as expected, lightdm is supposed to create the
ck session).

Regards,

My lightdm* version and those config files (attachment)

shell:~$ dpkg -l |grep lightdm
ii  liblightdm-gobject-1-0 1.8.5-1   
amd64simple display manager (gobject library)
ii  liblightdm-gobject-dev 1.8.5-1   
amd64simple display manager (gobject development files)
ii  lightdm 1.8.5-1   amd64simple 
display manager
ii  lightdm-gtk-greeter 1.6.1-3   amd64
simple display manager (GTK+ greeter)


Do you use autologin feature?
I don't use autologin and my wm is xfce4
thank you.
[keyring]
#a=0x0123456789ABCD
#b=secret
#
# General configuration
#
# start-default-seat = True to always start one seat if none are defined in the 
configuration
# greeter-user = User to run greeter as
# minimum-display-number = Minimum display number to use for X servers
# minimum-vt = First VT to run displays on
# lock-memory = True to prevent memory from being paged to disk
# user-authority-in-system-dir = True if session authority should be in the 
system location
# guest-account-script = Script to be run to setup guest account
# log-directory = Directory to log information to
# run-directory = Directory to put running state in
# cache-directory = Directory to cache to
# sessions-directory = Directory to find sessions
# remote-sessions-directory = Directory to find remote sessions
# greeters-directory = Directory to find greeters
#
[LightDM]
#start-default-seat=true
#greeter-user=lightdm
#minimum-display-number=0
#minimum-vt=7
#lock-memory=true
#user-authority-in-system-dir=false
#guest-account-script=guest-account
#log-directory=/var/log/lightdm
#run-directory=/var/run/lightdm
#cache-directory=/var/cache/lightdm
#sessions-directory=/usr/share/lightdm/sessions:/usr/share/xsessions
sessions-directory=/usr/share/xsessions
#remote-sessions-directory=/usr/share/lightdm/remote-sessions
#greeters-directory=/usr/share/lightdm/greeters:/usr/share/xgreeters

#
# Seat defaults
#
# type = Seat type (xlocal, xremote)
# xdg-seat = Seat name to set pam_systemd XDG_SEAT variable and name to pass to 
X server
# xserver-command = X server command to run (can also contain arguments e.g. X 
-special-option)
# xserver-layout = Layout to pass to X server
# xserver-config = Config file to pass to X server
# xserver-allow-tcp = True if TCP/IP connections are allowed to this X server
# xserver-share = True if the X server is shared for both greeter and session
# xserver-hostname = Hostname of X server (only for type=xremote)
# xserver-display-number = Display number of X server (only for type=xremote)
# xdmcp-manager = XDMCP manager to connect to (implies xserver-allow-tcp=true)
# xdmcp-port = XDMCP UDP/IP port to communicate on
# xdmcp-key = Authentication key to use for XDM-AUTHENTICATION-1 (stored in 
keys.conf)
# unity-compositor-command = Unity compositor command to run (can also contain 
arguments e.g. unity-system-compositor -special-option)
# unity-compositor-timeout = Number of seconds to wait for compositor to start
# greeter-session = Session to load for greeter
# greeter-hide-users = True to hide the user list
# greeter-allow-guest = True if the greeter should show a guest login option
# greeter-show-manual-login = True if the greeter should offer a manual login 
option
# greeter-show-remote-login = True if the greeter should offer a remote login 
option
# user-session = Session to load for users
# allow-guest = True if guest login is allowed
# guest-session = Session to load for guests (overrides user-session)
# session-wrapper = Wrapper script to run session with
# greeter-wrapper = Wrapper script to run greeter with
# guest-wrapper = Wrapper script to run guest sessions with
# display-setup-script = Script to run when starting a greeter session (runs as 
root)
# greeter-setup-script = Script to run when starting a greeter (runs as root)
# session-setup-script = Script to run when starting a user session (runs as 
root)
# session-cleanup-script = Script to run when quitting a user session

Bug#728342: 1.8.5-1 still have this problem

2013-11-07 Thread johnw 

Hi, after upgrade lightdm to 1.8.5-1, I still have this problem.
(lightdm greeter hangs and no restart/shutdown ... buttom)

downgrade lightdm to 1.6.3-1 without those problem.
my debian is sid/amd64.

Thanks.


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

Bug#717617: ibus: Some characters cannot be typed when in different locale

2013-09-14 Thread johnw 

On 09/14/2013 01:25 PM, Osamu Aoki wrote:

control: found 717617 1.5.1.is.1.4.2-3
control: notfound 717617 1.5.3-7

On Sat, Sep 14, 2013 at 11:18:37AM +0800, johnw wrote:

After upgrade (ibus) to 1.5.3-7, the problem solved.
Thank you.

___
Pkg-ime-devel mailing list
pkg-ime-de...@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-ime-devel
Sorry, it should be solved, after upgrade ibus-table-quick to 
1.4.0.20121008-1,

not ibus to 1.5.3-7.
Thank you.


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

Bug#717617: ibus: Some characters cannot be typed when in different locale

2013-09-13 Thread johnw 
Package: ibus-table-quick
Version: 1.3.5-2
Followup-For: Bug #717617

Dear Maintainer,
*** Please consider answering these questions, where appropriate ***

I also have this problem, I can not type some words but not all.
(eg: china 中X) -- when I type wm, the table list does not show the
'X' word.
Please help, thank you.

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


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

Kernel: Linux 3.10-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages ibus-table-quick depends on:
ii  ibus-table-quick-classic  1.3.5-2
ii  ibus-table-quick3 1.3.5-2
ii  ibus-table-quick5 1.3.5-2

ibus-table-quick recommends no packages.

ibus-table-quick suggests no packages.

-- no debconf information


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

Bug#722749: slim: numlock on does not work

2013-09-13 Thread johnw 
Package: slim
Version: 1.3.4-2
Severity: normal

Dear Maintainer,
*** Please consider answering these questions, where appropriate ***

I enable numlock on in /etc/slim.conf, but the numlock still off.
I also tried numlockx on, but still not work.
(I installed numlockx)

How to enable numlock on slim login screen?
Thank you.

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


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

Kernel: Linux 3.10-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages slim depends on:
ii  consolekit 0.4.6-3+b1
ii  dbus   1.6.14-1
ii  debconf [debconf-2.0]  1.5.51
ii  libc6  2.17-92+b1
ii  libck-connector0   0.4.6-3+b1
ii  libdbus-1-31.6.14-1
ii  libfontconfig1 2.10.2-2
ii  libfreetype6   2.4.9-1.1
ii  libgcc11:4.8.1-10
ii  libjpeg8   8d-1
ii  libpam0g   1.1.3-9
ii  libpng12-0 1.2.49-4
ii  libstdc++6 4.8.1-10
ii  libx11-6   2:1.6.1-1
ii  libxft22.3.1-1
ii  libxmu62:1.1.1-1
ii  libxrender11:0.9.8-1
ii  zlib1g 1:1.2.8.dfsg-1

Versions of packages slim recommends:
ii  xterm  295-1

Versions of packages slim suggests:
pn  scrot  none
ii  xauth  1:1.0.7-1

-- Configuration Files:
/etc/slim.conf changed:
default_path/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
default_xserver /usr/bin/X11/X
xserver_arguments   -nolisten tcp
halt_cmd/sbin/shutdown -h now
reboot_cmd  /sbin/shutdown -r now
console_cmd /usr/bin/xterm -C -fg white -bg black +sb -T Console 
login -e /bin/sh -c /bin/cat /etc/issue.net; exec /bin/login
xauth_path /usr/bin/X11/xauth
authfile   /var/run/slim.auth
 numlock on
login_cmd   exec /bin/bash -login /etc/X11/Xsession %session
sessions
default,startxfce4,openbox,ion3,icewm,wmaker,blackbox,awesome
screenshot_cmd  scrot /root/slim.png
welcome_msg Welcome to %host
shutdown_msg   The system is halting...
reboot_msg The system is rebooting...
current_theme   debian-joy
lockfile/var/run/slim.lock
logfile /var/log/slim.log


-- debconf information:
* shared/default-x-display-manager: slim
  slim/daemon_name: /usr/bin/slim


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

Bug#717617: ibus: Some characters cannot be typed when in different locale

2013-09-13 Thread johnw 

After upgrade (ibus) to 1.5.3-7, the problem solved.
Thank you.


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

Bug#718476: minitube: Minitube can not play any video

2013-08-01 Thread johnw 
Package: minitube
Version: 2.0-1
Severity: normal

Dear Maintainer,
*** Please consider answering these questions, where appropriate ***

Minitube can not play any video, no matter which.
I noticed some messages, when I run it on terminal/console.
Request finished but never started saving ...

I tried remove ${HOME}/.config/Flavio Tordini, but did not help,
minitube still can not play any video, no sound and video.
(but I see minitube make some network connection).

Thank you.

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


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

Kernel: Linux 3.10-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=zh_HK.UTF-8, LC_CTYPE=zh_HK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages minitube depends on:
ii  dbus-x11   1.6.12-1
ii  libc6  2.17-7
ii  libgcc11:4.8.1-8
ii  libphonon4 4:4.6.0.0-3
ii  libqt4-dbus4:4.8.5+dfsg-2
ii  libqt4-network 4:4.8.5+dfsg-2
ii  libqt4-xml 4:4.8.5+dfsg-2
ii  libqtcore4 4:4.8.5+dfsg-2
ii  libqtgui4  4:4.8.5+dfsg-2
ii  libstdc++6 4.8.1-8
ii  phonon 4:4.6.0.0-3
ii  phonon-backend-gstreamer [phonon-backend]  4:4.6.3-1

minitube recommends no packages.

minitube suggests no packages.

-- no debconf information


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

Bug#717150:

2013-07-21 Thread Johnw Qxi 
No one have this problem? only me?
Please help, thanks.

Bug#717150: chromium crash/gone when I click Tools-Extensions

2013-07-17 Thread johnw 
Package: chromium
Version: 28.0.1500.71-2
Severity: normal

Dear Maintainer,
*** Please consider answering these questions, where appropriate ***

   After upgrade chromium to 28.0.1500.71-2, I have this problem.
   When I click Menu-Tools-Extensions, then chromium
   gone/Segmentation fault.
   It never happen before.
   (remove ~/.config/chromium, and use new one do not help.)
   Thank you.

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


-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 3.9-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages chromium depends on:
ii  chromium-inspector   28.0.1500.71-2
ii  gconf-service3.2.6-1
ii  libasound2   1.0.27.2-1
ii  libatk1.0-0  2.8.0-2
ii  libc62.17-7
ii  libcairo21.12.14-5
ii  libcups2 1.6.2-10
ii  libdbus-1-3  1.6.12-1
ii  libexpat12.1.0-4
ii  libfontconfig1   2.10.2-2
ii  libfreetype6 2.4.9-1.1
ii  libgcc1  1:4.8.1-6
ii  libgconf-2-4 3.2.6-1
ii  libgcrypt11  1.5.2-3
ii  libgdk-pixbuf2.0-0   2.28.2-1
ii  libglib2.0-0 2.36.3-3
ii  libgnome-keyring03.8.0-2
ii  libgtk2.0-0  2.24.20-1
ii  libjpeg8 8d-1
ii  libnspr4 2:4.10-1
ii  libnss3  2:3.15-1
ii  libnss3-1d   2:3.15-1
ii  libpango-1.0-0   1.32.5-5+b1
ii  libpangocairo-1.0-0  1.32.5-5+b1
ii  libspeechd2  0.7.1-6.2
ii  libstdc++6   4.8.1-6
ii  libudev0 175-7.2
ii  libx11-6 2:1.6.0-1
ii  libxcomposite1   1:0.4.4-1
ii  libxdamage1  1:1.1.4-1
ii  libxext6 2:1.3.2-1
ii  libxfixes3   1:5.0.1-1
ii  libxml2  2.9.1+dfsg1-2
ii  libxrandr2   2:1.4.1-1
ii  libxrender1  1:0.9.8-1
ii  libxslt1.1   1.1.26-14.1
ii  libxss1  1:1.2.2-1
ii  xdg-utils1.1.0~rc1+git20111210-7

chromium recommends no packages.

Versions of packages chromium suggests:
pn  chromium-l10n  none

-- Configuration Files:
/etc/chromium/default changed [not included]

-- no debconf information


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

Bug#717150:

2013-07-17 Thread Johnw Qxi 
I find out the problem now, when I use --disable-sync and click the
Tools-Extensions, chromium will gone/crash.
If I remove --disable-sync, I can click the Extensions page without
problem.

Bug#712451: apparmor not support network rule

2013-06-16 Thread johnw 
Package: apparmor
Version: 2.7.103-4
Severity: normal

Dear Maintainer,
*** Please consider answering these questions, where appropriate ***

   * What led up to the situation?
   reload apparmor rule.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   apparmor_parser -r rule

   * What was the outcome of this action?
   it show the waring message: network rules not enforced

   * What outcome did you expect instead?
   enforced network rules, without warning/error message.

   I think it is because debian kernel (my: linux-image-3.9-1-amd64/3.9.6-1) 
does not fully support apparmor, is it?
   is it ture, can you point me, where can I download the patches set,
   make the kernel support apparmor (at least support network rule).
   
   Do you use apparmor on debian with network rule? if yes,
   any suggestion, how to make the kernel support apparmor network rule
   on debian?

   If it is not the kernel problem, can you tell me how to make apparmor
   support network rule?

   Thank you.
   

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


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

Kernel: Linux 3.9-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=zh_HK.utf8, LC_CTYPE=zh_HK.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages apparmor depends on:
ii  debconf [debconf-2.0]  1.5.50
ii  dpkg   1.16.10
ii  initramfs-tools0.112
ii  libc6  2.17-5
ii  lsb-base   4.1+Debian12
ii  python 2.7.5-2

apparmor recommends no packages.

Versions of packages apparmor suggests:
ii  apparmor-docs  2.7.103-4
ii  apparmor-profiles  2.7.103-4
ii  apparmor-utils 2.7.103-4

-- Configuration Files:
/etc/apparmor.d/abstractions/base changed [not included]
/etc/apparmor.d/abstractions/ibus changed [not included]
/etc/apparmor.d/abstractions/private-files-strict changed [not included]
/etc/apparmor.d/abstractions/ubuntu-browsers changed [not included]
/etc/apparmor.d/abstractions/ubuntu-browsers.d/plugins-common changed [not 
included]
/etc/apparmor.d/abstractions/ubuntu-browsers.d/ubuntu-integration changed [not 
included]
/etc/apparmor.d/tunables/home changed [not included]

-- debconf information excluded


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

Bug#712451: apparmor not support network rule

2013-06-16 Thread johnw 
On 2013年06月16日 星期日 04:30 下午, intrigeri wrote:
 You may want to nag AppArmor upstream so that they have the network
 mediation code merged into mainline Linux :) Cheers, 
Ok, I am not complain, but did you talk to debian kernel team/developer
this issue?
again, I am not complain, I just want know, what (apparmor/kernel)
developer think.
If you never did it, I will open the new bug report to
linux-image(should I do it?)
thank you.


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

Bug#676456: libscim8c2a: fails to use scim-setup and scim (can't typing)

2012-06-06 Thread johnw 
Package: libscim8c2a
Version: 1.4.13-4
Severity: normal

Dear Maintainer,
*** Please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

   I can not typing (non-english), can not open scim, can not open scim-setup.
   I found my /var/log/syslog had error message like this:
   
   Jun  7 12:25:12 redcat scim-bridge: There is no socket frontend of
   IMEngines for SCIM...
   Jun  7 12:25:12 redcat scim-bridge: Failed to initialize scim
   Jun  7 12:25:12 redcat kernel: [   66.704749] scim-bridge[4375]
   general protection ip:7fa9b6b845ef sp:7fffa8577cf0 error:0 in
   libscim-1.0.so.8.2.6[7fa9b6a8d000+17f000]

   and dpkg -l |grep scim
   ii  libscim8c2a:amd64 1.4.13-4
   library for SCIM platform
   ii  scim  1.4.13-4
   smart common input method platform
   ii  scim-bridge-agent 0.4.16-3
   IME server of scim-bridge communicate with SCIM
   ii  scim-bridge-client-gtk0.4.16-3
   IME server of scim-bridge communicate with SCIM
   ii  scim-bridge-client-qt 0.4.16-3
   IME server of scim-bridge communicate with SCIM
   ii  scim-bridge-client-qt40.4.16-3
   IME server of scim-bridge communicate with SCIM
   rc  scim-chewing  0.3.4-1.1
   Chewing IM engine module for SCIM
   ii  scim-gtk-immodule:amd64   1.4.13-4
   GTK+ input method module with SCIM as backend
   ii  scim-modules-socket:amd64 1.4.13-4
   socket modules for SCIM platform
   ii  scim-modules-table0.5.9-1
   generic tables IM engine module for SCIM platform
   ii  scim-tables-additional0.5.9-1
   miscellaneous input method data tables for SCIM platform
   ii  scim-tables-zh0.5.9-1
   Chinese input method data tables for SCIM platform

   Please help, and thank you.

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


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

Kernel: Linux 3.4.1-core2-amd64 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=zh_TW.UTF-8, LC_CTYPE=zh_TW.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages libscim8c2a depends on:
ii  libatk1.0-0 2.4.0-2
ii  libc6   2.13-33
ii  libcairo-gobject2   1.12.2-2
ii  libcairo2   1.12.2-2
ii  libgcc1 1:4.7.0-11
ii  libgdk-pixbuf2.0-0  2.26.1-1
ii  libglib2.0-02.32.3-1
ii  libgtk-3-0  3.4.2-1
ii  libltdl72.4.2-1
ii  libpango1.0-0   1.30.0-1
ii  libstdc++6  4.7.0-11
ii  libx11-62:1.4.99.901-2
ii  multiarch-support   2.13-33

libscim8c2a recommends no packages.

libscim8c2a suggests no packages.

-- no debconf information



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

Bug#671596: ulatencyd change kernel.sched_autogroup_enabled to 0

2012-05-05 Thread johnw 
Package: ulatencyd
Version: 0.5.0-5
Severity: normal

Dear Maintainer,
*** Please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   sudo /etc/init.d/ulatencyd restart
   * What was the outcome of this action?
   sysctl kernel.sched_autogroup_enabled will change to 0
   * What outcome did you expect instead?
   sysctl kernel.sched_autogroup_enabled will not change.

   when i restart ulatencyd(/etc/init.d/ulatencyd restart),
   sysctl kernel.sched_autogroup_enabled will change to 0.

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


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

Kernel: Linux 3.3.4-core2-amd64 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=zh_TW.UTF-8, LC_CTYPE=zh_TW.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages ulatencyd depends on:
ii  dbus   1.5.12-1
ii  dpkg   1.16.3
ii  libc6  2.13-32
ii  libdbus-1-31.5.12-1
ii  libdbus-glib-1-2   0.98-1
ii  libglib2.0-0   2.32.2-1
ii  liblua5.1-05.1.5-1
ii  libpolkit-gobject-1-0  0.105-1
ii  libxau61:1.0.7-1
ii  libxcb11.8.1-1
ii  lua-posix  5.1.19-1
ii  lua5.1 [lua]   5.1.5-1

ulatencyd recommends no packages.

ulatencyd suggests no packages.

-- Configuration Files:
/etc/ulatencyd/cgroups.conf changed:
-- this is a lua file
CGROUP_ROOT = /sys/fs/cgroup
-- /sys/fs/cgroup is not available on older kernels, we need to change that
-- in those cases
fp = io.open(CGROUP_ROOT, r)
if not fp then
  CGROUP_ROOT = /dev/cgroup
else
  fp:close()
end
-- edit the below only when you know what you are doing
-- describes which subsystems are mounted under
-- which toplevel path
CGROUP_MOUNTPOINTS = {
  cpu={cpu},
-- please have a look at README.Debian to see why the memory resource
-- controller was disabled, and how to re-enable it.
  memory={memory},
  blkio={blkio},
  cpuset={cpuset}
}
-- FIXME we need some better solution for that :-/
-- cpuset, very powerfull, but can't create a group with unset cpus or mems
CGROUP_DEFAULT = {
  cpu={[notify_on_release] = 1,},
  memory={[notify_on_release] = 1,},
  io={[notify_on_release] = 1,},
  cpuset={[notify_on_release] = 1,},
}

/etc/ulatencyd/rules/gnome.lua changed:
--[[
Copyright 2010,2011 ulatencyd developers
This file is part of ulatencyd.
License: GNU General Public License 3 or later
]]--
GnomeUI = {
  name = GnomeUI,
  re_basename = 
metacity|compiz|gnome-panel|gtk-window-decorator|nautilus|Thunar,
  --re_basename = metacity,
  check = function(self, proc)
local flag = ulatency.new_flag(user.ui)
proc:add_flag(flag)
proc:set_oom_score(-300)
rv = ulatency.filter_rv(ulatency.FILTER_STOP)
return rv
  end
}
GnomeCore = {
  name = GnomeCore,
  re_basename = x-session-manager,
-- adjust the oom score adjust so x server will more likely survive
  check = function(self, proc)
proc:set_oom_score(-300)
return ulatency.filter_rv(ulatency.FILTER_STOP)
  end
}
-- gnome does a very bad job in setting grpid's, causing the complete
-- desktop to be run under one group. we fix this problem here, ugly
-- but working
-- filter that instantly sets a fake group on newly spawned processes from
-- gnome-panel or x-session-manager
GnomeFix = RunnerFix.new(GnomeFix, {gnome-panel, x-session-manager, 
gnome-session})
-- on start we have to fix all processes that have descented from kde
local function cleanup_gnome_mess()
  cleanup_desktop_mess({x-session-manager, gnome-session, gnome-panel})
  return false
end
ulatency.add_timeout(cleanup_gnome_mess, 1000)
ulatency.register_filter(GnomeCore)
ulatency.register_filter(GnomeUI)
ulatency.register_filter(GnomeFix)

/etc/ulatencyd/scheduler/20-desktop.lua changed:
--[[
Copyright 2010,2011 ulatencyd developers
This file is part of ulatencyd.
License: GNU General Public License 3 or later
]]--
SCHEDULER_MAPPING_DESKTOP = {
  info = {
description = a good default desktop configuration
  }
}
-- cpu  memory configuration
SCHEDULER_MAPPING_DESKTOP[cpu] =
{
  {
name = rt_tasks,
cgroups_name = rt_tasks,
param = { [cpu.shares]=3048, [?cpu.rt_runtime_us] = 949500 },
check = function(proc)
  local rv = proc.received_rt or check_label({sched.rt}, proc) or 
proc.vm_size == 0
  return rv
end,
  },
  {
name = system_essential,
cgroups_name = sys_essential,
param = { [cpu.shares]=3048 },
label = { system.essential }
  },
  {
name = user,
cgroups_name = usr_${euid},
check = function(proc)
  return ( proc.euid  999 )
end,
param = { [cpu.shares]=3048,  [?cpu.rt_runtime_us] = 100 },
children = {
  { 
name = poison,
param = {

Bug#671596: ulatencyd change kernel.sched_autogroup_enabled to 0

2012-05-05 Thread johnw 

On 2012年05月05日 20:09, Alessandro Ghedini wrote

I don't see how this is a bug. sched_autogroup is what ulatencyd replaces and
they basically do the same thing (with ulatencyd being higher level, more
configurable, etc...). AFAICT they may interfere with each other if enabled at
the same time and, in any case, I don't see what benefit comes from enabling
both at the same time.

Cheers



Yes, i understand now, this is NOT a bug.
how to close the bug report?
thank you.



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

Bug#668127: Acknowledgement (linux-image-3.2.0-2-rt-amd64 (3.2.14-1) can not boot)

2012-04-08 Thread johnw 
I think the bug(s) is related to some video modules,
because when the screen become to high resolution (the font become to
small and beautify),
then the system freeze, the keyboard no response, until hard
poweroff/reboot.

and when the system freeze, the system still in console mode,
not started Xorg/gdm.

john@redcat:~$ ls /etc/modprobe.d/
alsa-base-blacklist.conf fbdev-blacklist.conf nbd-client.conf
alsa-base.conf i915-kms.conf oss-compat.conf
blacklist.conf.dpkg-bak linux-sound-base_noOSS.conf radeon-kms.conf

john@redcat:~$ cat /etc/modprobe.d/i915-kms.conf
options i915 modeset=1

my video card is: Intel G45/G43 Chipset

Thank you.



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