[Touch-packages] [Bug 1784499] Re: AppArmor treats regular NFS file access as network op

2020-06-23 Thread clickwir
FWIW, I still see this on a fresh Ubuntu 20.04 install. My NFS server is
also Ubuntu 20.04.

Linux server01 5.4.0-37-generic #41-Ubuntu SMP Wed Jun 3 18:57:02 UTC
2020 x86_64 x86_64 x86_64 GNU/Linux

[1129462.984558] audit: type=1400 audit(1592950067.469:72821): 
apparmor="DENIED" operation="sendmsg" profile="/usr/bin/man" pid=2490588 
comm="man" laddr=10.x.x.x lport=846 faddr=10.x.x.x fport=2049 family="inet" 
sock_type="stream" protocol=6 requested_mask="send" denied_mask="send"
[1129462.984563] nfs: RPC call returned error 13

My server /etc/exports looks like this:
/path *(rw,async,insecure,mp=/path,all_squash,no_subtree_check)

My client's fstab just uses 'defaults', nothing else. But here's what 'mount' 
shows:
10.x.x.x:/path on /path type nfs4 
(rw,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=10.x.x.x,local_lock=none,addr=10.x.x.x)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1784499

Title:
  AppArmor treats regular NFS file access as network op

Status in AppArmor:
  Confirmed
Status in snapd:
  Invalid
Status in apparmor package in Ubuntu:
  Confirmed

Bug description:
  I am using AppArmor 2.12-4ubuntu5 on Ubuntu 18.04/bionic.

  I have the usr.bin.man profile enforced, and home directories in NFS.

  The log excerpt copied below is the result of a single invocation of
  "man ls" by an unprivileged user. (The program did display the man
  page correctly to the user.)

  It does not seem appropriate for AppArmor to report the man(1) program
  as having attempted to contact the NFS server directly, when it only
  tried to access an NFS-served file in the normal way. "man" is not a
  network-aware program and the log below misleadingly implies
  otherwise.

  

  Jul 30 17:38:35 darkstar kernel: [69963.052243] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.052274] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.052297] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.052314] kauditd_printk_skb: 34 
callbacks suppressed
  Jul 30 17:38:35 darkstar kernel: [69963.052316] audit: type=1400 
audit(1532986715.854:214): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 
faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 
requested_mask="send" denied_mask="send"
  Jul 30 17:38:35 darkstar kernel: [69963.052323] audit: type=1400 
audit(1532986715.854:215): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=802 
faddr=10.24.115.84 fport=2049 family="inet" sock_type="stream" protocol=6 
requested_mask="send" denied_mask="send"
  Jul 30 17:38:35 darkstar kernel: [69963.052327] audit: type=1400 
audit(1532986715.854:216): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 
faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 
requested_mask="send" denied_mask="send"
  Jul 30 17:38:35 darkstar kernel: [69963.052339] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.052363] audit: type=1400 
audit(1532986715.854:217): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 
faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 
requested_mask="send" denied_mask="send"
  Jul 30 17:38:35 darkstar kernel: [69963.052364] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.052369] audit: type=1400 
audit(1532986715.854:218): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=802 
faddr=10.24.115.84 fport=2049 family="inet" sock_type="stream" protocol=6 
requested_mask="send" denied_mask="send"
  Jul 30 17:38:35 darkstar kernel: [69963.052386] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.052450] audit: type=1400 
audit(1532986715.854:219): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 
faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 
requested_mask="send" denied_mask="send"
  Jul 30 17:38:35 darkstar kernel: [69963.059570] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.059640] audit: type=1400 
audit(1532986715.862:220): apparmor="DENIED" operation="sendmsg" 
profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 
faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 
requested_mask="send" denied_mask="send"
  Jul 30 17:38:35 darkstar kernel: [69963.061907] nfs: RPC call returned error 
13
  Jul 30 17:38:35 darkstar kernel: [69963.061925] audit: type=1400 
audit(1532986715.862:221): apparmor="DENIED" 

[Touch-packages] [Bug 1788321] Re: swapon failed: invalid argument

2020-04-27 Thread clickwir
Fixed my problem.

While looking through /var/log/syslog, I noticed this line around the
same time swap mount failed.

BTRFS warning (device sda3): swapfile must not be copy-on-write

Then a few lines later...

systemd[1]: swap.img.swap: Failed with result 'exit-code'.
systemd[1]: Failed to activate swap /swap.img.
systemd[1]: Dependency failed for Swap.
systemd[1]: swap.target: Job swap.target/start failed with result 'dependency'.

Yes my root is on btrfs and I did not see this error before. So I
deleted /swap.img and started over.

$ sudo rm -rf /swap.img
$ sudo touch /swap.img
$ sudo chattr +C /swap.img
$ sudo fallocate -l 2G /swap.img
$ sudo chmod 600 /swap.img
$ sudo mkswap /swap.img
$ sudo swapon /swap.img

No error and "swapon --show" gives this:

NAME  TYPE SIZE USED PRIO
/swap.img file   2G   0B   -2

Just what I was expecting. So problem solved for me, maybe a check can
be put in to see if it's on btrfs and apply the 'chattr +C' option.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1788321

Title:
  swapon failed: invalid argument

Status in linux package in Ubuntu:
  Confirmed
Status in util-linux package in Ubuntu:
  Invalid

Bug description:
  Environment:
   - Ubuntu 18.04.1 LTS
   - Linux 4.15.0-32-generic i686

  Description:
  When I try to mount my swap partition or my swap file, I get "swapon failed: 
invalid argument" .

  Steps to reproduce:
  1) sudo bash
  2) dd if=/dev/zero of=/swapfile bs=1024 count=524288
  3) mkswap /swapfile
  4) chown root:root /swapfile
  5) chmod 0600 /swapfile
  6) swapon /swapfile
  Last execution returns "swapon failed: invalid argument" .

  I'm almost sure it's a bug because I have no problems using Linux
  4.15.0-29-generic instead of Linux 4.15.0-32-generic. Also, no
  problems using Ubuntu 18.04.1 LTS Live CD.

  Regards.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1788321] Re: swapon failed: invalid argument

2020-04-23 Thread clickwir
Just did a fresh install of 20.04 as a Proxmox VM and see this "invalid
argument" in the start up messages and syslog. Trying to start it
manually also fails. Tried recreating it, also failed.

root@changeme:/# fallocate -l 2G /swap.img 
root@changeme:/# chmod 600 /swap.img 
root@changeme:/# ls -lah /swap.img 
-rw--- 1 root root 2.0G Apr 24 04:07 /swap.img
root@changeme:/# mkswap /swap.img 
mkswap: /swap.img: warning: wiping old swap signature.
Setting up swapspace version 1, size = 2 GiB (2147479552 bytes)
no label, UUID=bd9bdc4f-4c53-4b0b-ad92-687ed5f669e6
root@changeme:/# swapon /swap.img
swapon: /swap.img: swapon failed: Invalid argument
root@changeme:/# swapon -v /swap.img
swapon: /swap.img: found signature [pagesize=4096, signature=swap]
swapon: /swap.img: pagesize=4096, swapsize=2147483648, devsize=2147483648
swapon /swap.img
swapon: /swap.img: swapon failed: Invalid argument

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1788321

Title:
  swapon failed: invalid argument

Status in linux package in Ubuntu:
  Confirmed
Status in util-linux package in Ubuntu:
  Invalid

Bug description:
  Environment:
   - Ubuntu 18.04.1 LTS
   - Linux 4.15.0-32-generic i686

  Description:
  When I try to mount my swap partition or my swap file, I get "swapon failed: 
invalid argument" .

  Steps to reproduce:
  1) sudo bash
  2) dd if=/dev/zero of=/swapfile bs=1024 count=524288
  3) mkswap /swapfile
  4) chown root:root /swapfile
  5) chmod 0600 /swapfile
  6) swapon /swapfile
  Last execution returns "swapon failed: invalid argument" .

  I'm almost sure it's a bug because I have no problems using Linux
  4.15.0-29-generic instead of Linux 4.15.0-32-generic. Also, no
  problems using Ubuntu 18.04.1 LTS Live CD.

  Regards.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1742867] Re: Screen blank, audio choppy, system locked

2018-01-16 Thread clickwir
xorg was chosen by the bug utility, I did not select xorg. Problem
appears to be with latest kernel, did not happen prior.

** Package changed: xorg (Ubuntu) => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1742867

Title:
  Screen blank, audio choppy, system locked

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  While watching a YouTube video, screen went blank. Audio cut out,
  after a few seconds the audio started playing normally for a few more
  seconds then kept repeating the last half a second of audio for a few
  more seconds. Then it stopped and nothing responded.

  It did this a few times over the course of an hour. Had to power off
  the PC to get a reboot. Last time it did this I ssh'd from another PC
  to get dmesg and syslog info as it happened. Attaching those captures.

  clickwir@mach:~$ uname -a
  Linux mach 4.13.0-25-generic #29-Ubuntu SMP Mon Jan 8 21:14:41 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  clickwir@mach:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 17.10
  Release:17.10
  Codename:   artful

  
   dmesg 

  [   10.136445] bond0: Enslaving enp7s0f1 as an active interface with an up 
link
  [   10.136497] IPv6: ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
  [   10.144317] e1000e :07:00.0 enp7s0f0: changing MTU from 1500 to 9000
  [   10.310070] e1000e :07:00.1 enp7s0f1: changing MTU from 1500 to 9000
  [   10.625965] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
  [   10.730200] r8169 :02:00.0 eth0: link down
  [   10.730246] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
  [   12.573052] e1000e: enp7s0f0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   12.633055] e1000e: enp7s0f1 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   16.875586] FS-Cache: Loaded
  [   16.896010] FS-Cache: Netfs 'nfs' registered for caching
  [   16.914353] NFS: Registering the id_resolver key type
  [   16.914364] Key type id_resolver registered
  [   16.914364] Key type id_legacy registered
  [   17.485539] ip6_tables: (C) 2000-2006 Netfilter Core Team
  [   17.513074] Ebtables v2.0 registered
  [   17.564084] radeon_dp_aux_transfer_native: 74 callbacks suppressed
  [   17.863232] bridge: filtering via arp/ip/ip6tables is no longer available 
by default. Update your scripts to load br_netfilter if you need this.
  [   17.864899] virbr0: port 1(virbr0-nic) entered blocking state
  [   17.864903] virbr0: port 1(virbr0-nic) entered disabled state
  [   17.864995] device virbr0-nic entered promiscuous mode
  [   17.960322] nf_conntrack version 0.5.0 (65536 buckets, 262144 max)
  [   18.038385] virbr0: port 1(virbr0-nic) entered blocking state
  [   18.038388] virbr0: port 1(virbr0-nic) entered listening state
  [   18.095412] virbr0: port 1(virbr0-nic) entered disabled state
  [   89.815180] radeon_dp_aux_transfer_native: 74 callbacks suppressed
  [   92.062606] show_signal_msg: 27 callbacks suppressed
  [   92.062608] xembedsniproxy[2507]: segfault at 2 ip 55ea4a6890d7 sp 
7fff6c7a7c30 error 4 in xembedsniproxy[55ea4a67d000+13000]
  [   95.955166] radeon_dp_aux_transfer_native: 74 callbacks suppressed

  ### abnormal begins here ###

  [ 1429.496584] sched: RT throttling activated
  [ 1429.706303] clocksource: timekeeping watchdog on CPU3: Marking clocksource 
'tsc' as unstable because the skew is too large:
  [ 1429.706305] clocksource:   'hpet' wd_now: c4741f2e 
wd_last: c3bcdb60 mask: 
  [ 1429.706306] clocksource:   'tsc' cs_now: 4acf553cc2d 
cs_last: 4ac71a54967 mask: 
  [ 1429.706309] tsc: Marking TSC unstable due to clocksource watchdog
  [ 1434.739539] nfs: server 10.1.0.4 not responding, still trying
  [ 1437.469449] nfs: server 10.1.0.4 OK
  [ 1439.143494] TSC found unstable after boot, most likely due to broken BIOS. 
Use 'tsc=unstable'.
  [ 1439.143498] sched_clock: Marking unstable (1439092126811, 
50992985)<-(1439477690212, -334199655)
  [ 1440.403916] clocksource: Switched to clocksource hpet
  [ 1443.553969] hrtimer: interrupt took 629117003 ns
  [ 1454.039245] INFO: NMI handler (nmi_cpu_backtrace_handler) took too long to 
run: 209.684 msecs
  [ 1454.454671] INFO: NMI handler (perf_event_nmi_handler) took too long to 
run: 44.646 msecs
  [ 1454.454673] perf: interrupt took too long (349007 > 2500), lowering 
kernel.perf_event_max_sample_rate to 500
  [ 1455.293492] INFO: NMI handler (perf_event_nmi_handler) took too long to 
run: 61.329 msecs
  [ 1455.293494] perf: interrupt took too long (479410 > 436258), lowering 
kernel.perf_event_max_sample_rate to 250
  [ 1463.284343] INFO: NMI handler (perf_event_nmi_handler) took too long to 
run: 172.103 msecs
  [ 1463.284345] perf: interrupt took too long (1344829 > 59

[Touch-packages] [Bug 1742867] Re: Screen blank, audio choppy, system locked

2018-01-12 Thread clickwir
Happened again after just a few minutes of watching. Tried not watching
YouTube for a while and it was fine for about 20 mins.


 dmesg 

[ 2441.656816] clocksource: timekeeping watchdog on CPU2: Marking clocksource 
'tsc' as unstable because the skew is too large:
[ 2441.656819] clocksource:   'hpet' wd_now: 23e5cdb2 
wd_last: 2300b853 mask: 
[ 2441.656820] clocksource:   'tsc' cs_now: 7e4398e6b37 
cs_last: 7e389faed6b mask: 
[ 2441.656822] tsc: Marking TSC unstable due to clocksource watchdog
[ 2446.689848] hrtimer: interrupt took 1048512639 ns
[ 2450.464784] nfs: server 10.1.0.4 not responding, still trying
[ 2461.579468] sched: RT throttling activated
[ 2462.627985] INFO: NMI handler (perf_ibs_nmi_handler) took too long to run: 
419.422 msecs
[ 2462.627988] INFO: NMI handler (perf_event_nmi_handler) took too long to run: 
838.852 msecs
[ 2462.627990] perf: interrupt took too long (6553849 > 4096258), lowering 
kernel.perf_event_max_sample_rate to 250
[ 2464.305681] watchdog: BUG: soft lockup - CPU#2 stuck for 23s! 
[kworker/u16:1:4770]
[ 2464.305684] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 
nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 
xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables 
iptable_filter nfsv3 nfs_acl cfg80211 rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs 
lockd grace fscache zram binfmt_misc nls_iso8859_1 snd_hda_codec_hdmi 
edac_mce_amd kvm_amd kvm irqbypass crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel pcbc input_leds aesni_intel aes_x86_64 crypto_simd 
glue_helper cryptd eeepc_wmi asus_wmi sparse_keymap video snd_hda_intel 
snd_ctxfi snd_hda_codec k10temp snd_hda_core wmi_bmof snd_hwdep fam15h_power 
snd_pcm snd_seq_midi snd_seq_midi_event i2c_piix4 snd_rawmidi snd_seq 
snd_seq_device
[ 2464.305717]  snd_timer snd soundcore shpchp mac_hid bonding parport_pc ppdev 
sunrpc lp parport ip_tables x_tables autofs4 btrfs xor raid6_pq hid_generic 
usbhid hid amdkfd amd_iommu_v2 radeon i2c_algo_bit ttm drm_kms_helper e1000e 
syscopyarea sysfillrect firewire_ohci sysimgblt ptp fb_sys_fops pps_core 
firewire_core crc_itu_t drm ahci r8169 libahci mii wmi
[ 2464.305738] CPU: 2 PID: 4770 Comm: kworker/u16:1 Not tainted 
4.13.0-25-generic #29-Ubuntu
[ 2464.305739] Hardware name: To be filled by O.E.M. To be filled by 
O.E.M./M5A97 EVO, BIOS 1604 10/16/2012
[ 2464.305765] Workqueue: events_power_efficient radeon_fence_check_lockup 
[radeon]
[ 2464.305766] task: 9a5eeb535d00 task.stack: b3d203218000
[ 2464.305788] RIP: 0010:evergreen_is_display_hung+0x125/0x1b0 [radeon]
[ 2464.305789] RSP: 0018:b3d20321bd80 EFLAGS: 0286 ORIG_RAX: 
ff10
[ 2464.305791] RAX:  RBX: 0001 RCX: 
[ 2464.305792] RDX:  RSI: 6ea0 RDI: 000550ba
[ 2464.305792] RBP: b3d20321bdd8 R08: 0001 R09: 
[ 2464.305793] R10: 9a5f18678000 R11:  R12: 9a5f18678000
[ 2464.305794] R13: 0004 R14: 003f R15: 0001
[ 2464.305795] FS:  () GS:9a5f3ec8() 
knlGS:
[ 2464.305796] CS:  0010 DS:  ES:  CR0: 80050033
[ 2464.305797] CR2: 7faff1182000 CR3: 00061a4ca000 CR4: 000406e0
[ 2464.305798] Call Trace:
[ 2464.305822]  evergreen_gpu_check_soft_reset+0xc5/0x120 [radeon]
[ 2464.305843]  evergreen_gfx_is_lockup+0x17/0x40 [radeon]
[ 2464.305859]  radeon_fence_check_lockup+0x93/0x180 [radeon]
[ 2464.305862]  process_one_work+0x1e7/0x410
[ 2464.305864]  worker_thread+0x4b/0x420
[ 2464.305866]  kthread+0x125/0x140
[ 2464.305868]  ? process_one_work+0x410/0x410
[ 2464.305869]  ? kthread_create_on_node+0x70/0x70
[ 2464.305872]  ret_from_fork+0x1f/0x30
[ 2464.305873] Code: ca 8b 04 95 40 50 6d c0 05 a0 6e 00 00 49 3b 84 24 b0 01 
00 00 48 89 c6 72 07 3d ff ff 00 00 77 41 49 03 84 24 e8 01 00 00 8b 00 <39> 44 
95 b8 74 05 f7 d3 41 21 de 83 c1 01 41 39 8c 24 98 26 00 
[ 2466.612565] watchdog: BUG: soft lockup - CPU#7 stuck for 25s! 
[kworker/7:1:79]
[ 2466.612569] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 
nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 
xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables 
iptable_filter nfsv3 nfs_acl cfg80211 rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs 
lockd grace fscache zram binfmt_misc nls_iso8859_1 snd_hda_codec_hdmi 
edac_mce_amd kvm_amd kvm irqbypass crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel pcbc input_leds aesni_intel aes_x86_64 crypto_simd 
glue_helper cryptd eeepc_wmi asus_wmi sparse_keymap video snd_hda_intel 
snd_ctxfi snd_hda_codec k10temp snd_hda_core wmi_bmof snd_hwdep fam15h_power 

[Touch-packages] [Bug 1742867] Re: Screen blank, audio choppy, system locked

2018-01-12 Thread clickwir
10
Jan 12 21:39:43 mach kernel: [  604.118215] RAX:  RBX: 
0286 RCX: 
Jan 12 21:39:43 mach kernel: [  604.118216] RDX: 90bda252e698 RSI: 
0286 RDI: 0286
Jan 12 21:39:43 mach kernel: [  604.118216] RBP: a067c3303d40 R08: 
 R09: 
Jan 12 21:39:43 mach kernel: [  604.118217] R10: a067c3303de0 R11: 
90bdbedd7870 R12: 0001
Jan 12 21:39:43 mach kernel: [  604.118218] R13: 90bda252e568 R14: 
90bda252e238 R15: 90bda252e5a8
Jan 12 21:39:43 mach kernel: [  604.118219] FS:  () 
GS:90bdbedc() knlGS:
Jan 12 21:39:43 mach kernel: [  604.118220] CS:  0010 DS:  ES:  CR0: 
80050033
Jan 12 21:39:43 mach kernel: [  604.118221] CR2: 7f4ee88c5ff0 CR3: 
00061d9aa000 CR4: 000406e0
Jan 12 21:39:43 mach kernel: [  604.118222] Call Trace:
Jan 12 21:39:43 mach kernel: [  604.118227]  io_watchdog_func+0x12a/0x3a0
Jan 12 21:39:43 mach kernel: [  604.118229]  ? ohci_dump+0x90/0x90
Jan 12 21:39:43 mach kernel: [  604.118231]  call_timer_fn+0x33/0x130
Jan 12 21:39:43 mach kernel: [  604.118233]  run_timer_softirq+0x40f/0x470
Jan 12 21:39:43 mach kernel: [  604.118236]  ? __switch_to+0x182/0x540
Jan 12 21:39:43 mach kernel: [  604.118238]  __do_softirq+0xde/0x2a5
Jan 12 21:39:43 mach kernel: [  604.118241]  run_ksoftirqd+0x29/0x60
Jan 12 21:39:43 mach kernel: [  604.118243]  smpboot_thread_fn+0xec/0x160
Jan 12 21:39:43 mach kernel: [  604.118245]  kthread+0x125/0x140
Jan 12 21:39:43 mach kernel: [  604.118247]  ? sort_range+0x30/0x30
Jan 12 21:39:43 mach kernel: [  604.118249]  ? kthread_create_on_node+0x70/0x70
Jan 12 21:39:43 mach kernel: [  604.118251]  ret_from_fork+0x1f/0x30
Jan 12 21:39:43 mach kernel: [  604.118252] Code: 25 dd 35 f0 65 ff ff ff 7f 89 
d0 5d c3 90 90 90 90 90 90 90 90 90 0f 1f 44 00 00 55 48 89 e5 c6 07 00 0f 1f 
40 00 48 89

 end syslog 

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1742867

Title:
  Screen blank, audio choppy, system locked

Status in xorg package in Ubuntu:
  New

Bug description:
  While watching a YouTube video, screen went blank. Audio cut out,
  after a few seconds the audio started playing normally for a few more
  seconds then kept repeating the last half a second of audio for a few
  more seconds. Then it stopped and nothing responded.

  It did this a few times over the course of an hour. Had to power off
  the PC to get a reboot. Last time it did this I ssh'd from another PC
  to get dmesg and syslog info as it happened. Attaching those captures.

  clickwir@mach:~$ uname -a
  Linux mach 4.13.0-25-generic #29-Ubuntu SMP Mon Jan 8 21:14:41 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  clickwir@mach:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 17.10
  Release:17.10
  Codename:   artful

  
   dmesg 

  [   10.136445] bond0: Enslaving enp7s0f1 as an active interface with an up 
link
  [   10.136497] IPv6: ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
  [   10.144317] e1000e :07:00.0 enp7s0f0: changing MTU from 1500 to 9000
  [   10.310070] e1000e :07:00.1 enp7s0f1: changing MTU from 1500 to 9000
  [   10.625965] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
  [   10.730200] r8169 :02:00.0 eth0: link down
  [   10.730246] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
  [   12.573052] e1000e: enp7s0f0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   12.633055] e1000e: enp7s0f1 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   16.875586] FS-Cache: Loaded
  [   16.896010] FS-Cache: Netfs 'nfs' registered for caching
  [   16.914353] NFS: Registering the id_resolver key type
  [   16.914364] Key type id_resolver registered
  [   16.914364] Key type id_legacy registered
  [   17.485539] ip6_tables: (C) 2000-2006 Netfilter Core Team
  [   17.513074] Ebtables v2.0 registered
  [   17.564084] radeon_dp_aux_transfer_native: 74 callbacks suppressed
  [   17.863232] bridge: filtering via arp/ip/ip6tables is no longer available 
by default. Update your scripts to load br_netfilter if you need this.
  [   17.864899] virbr0: port 1(virbr0-nic) entered blocking state
  [   17.864903] virbr0: port 1(virbr0-nic) entered disabled state
  [   17.864995] device virbr0-nic entered promiscuous mode
  [   17.960322] nf_conntrack version 0.5.0 (65536 buckets, 262144 max)
  [   18.038385] virbr0: port 1(virbr0-nic) entered blocking state
  [   18.038388] virbr0: port 1(virbr0-nic) entered listening state
  [   18.095412] virbr0: port 1(virbr0-nic) entered disabled state
  [   89.815180] radeon_dp_aux_transfer_native: 74 callbacks suppressed
  [   92.062606] show_signal_msg: 27 callbacks suppressed
  [   92.062608] xembedsniproxy[2507]: se

[Touch-packages] [Bug 1742867] Re: Screen blank, audio choppy, system locked

2018-01-11 Thread clickwir
I used "ubuntu-bug" to gather this info. I see it set
"ExtraDebuggingInterest: I just need to know a workaround" but that's
not what I selected when it asked. I chose the option that was something
like "Yes, but not if too technical".

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1742867

Title:
  Screen blank, audio choppy, system locked

Status in xorg package in Ubuntu:
  New

Bug description:
  While watching a YouTube video, screen went blank. Audio cut out,
  after a few seconds the audio started playing normally for a few more
  seconds then kept repeating the last half a second of audio for a few
  more seconds. Then it stopped and nothing responded.

  It did this a few times over the course of an hour. Had to power off
  the PC to get a reboot. Last time it did this I ssh'd from another PC
  to get dmesg and syslog info as it happened. Attaching those captures.

  clickwir@mach:~$ uname -a
  Linux mach 4.13.0-25-generic #29-Ubuntu SMP Mon Jan 8 21:14:41 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  clickwir@mach:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 17.10
  Release:17.10
  Codename:   artful

  
   dmesg 

  [   10.136445] bond0: Enslaving enp7s0f1 as an active interface with an up 
link
  [   10.136497] IPv6: ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
  [   10.144317] e1000e :07:00.0 enp7s0f0: changing MTU from 1500 to 9000
  [   10.310070] e1000e :07:00.1 enp7s0f1: changing MTU from 1500 to 9000
  [   10.625965] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
  [   10.730200] r8169 :02:00.0 eth0: link down
  [   10.730246] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
  [   12.573052] e1000e: enp7s0f0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   12.633055] e1000e: enp7s0f1 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   16.875586] FS-Cache: Loaded
  [   16.896010] FS-Cache: Netfs 'nfs' registered for caching
  [   16.914353] NFS: Registering the id_resolver key type
  [   16.914364] Key type id_resolver registered
  [   16.914364] Key type id_legacy registered
  [   17.485539] ip6_tables: (C) 2000-2006 Netfilter Core Team
  [   17.513074] Ebtables v2.0 registered
  [   17.564084] radeon_dp_aux_transfer_native: 74 callbacks suppressed
  [   17.863232] bridge: filtering via arp/ip/ip6tables is no longer available 
by default. Update your scripts to load br_netfilter if you need this.
  [   17.864899] virbr0: port 1(virbr0-nic) entered blocking state
  [   17.864903] virbr0: port 1(virbr0-nic) entered disabled state
  [   17.864995] device virbr0-nic entered promiscuous mode
  [   17.960322] nf_conntrack version 0.5.0 (65536 buckets, 262144 max)
  [   18.038385] virbr0: port 1(virbr0-nic) entered blocking state
  [   18.038388] virbr0: port 1(virbr0-nic) entered listening state
  [   18.095412] virbr0: port 1(virbr0-nic) entered disabled state
  [   89.815180] radeon_dp_aux_transfer_native: 74 callbacks suppressed
  [   92.062606] show_signal_msg: 27 callbacks suppressed
  [   92.062608] xembedsniproxy[2507]: segfault at 2 ip 55ea4a6890d7 sp 
7fff6c7a7c30 error 4 in xembedsniproxy[55ea4a67d000+13000]
  [   95.955166] radeon_dp_aux_transfer_native: 74 callbacks suppressed

  ### abnormal begins here ###

  [ 1429.496584] sched: RT throttling activated
  [ 1429.706303] clocksource: timekeeping watchdog on CPU3: Marking clocksource 
'tsc' as unstable because the skew is too large:
  [ 1429.706305] clocksource:   'hpet' wd_now: c4741f2e 
wd_last: c3bcdb60 mask: 
  [ 1429.706306] clocksource:   'tsc' cs_now: 4acf553cc2d 
cs_last: 4ac71a54967 mask: 
  [ 1429.706309] tsc: Marking TSC unstable due to clocksource watchdog
  [ 1434.739539] nfs: server 10.1.0.4 not responding, still trying
  [ 1437.469449] nfs: server 10.1.0.4 OK
  [ 1439.143494] TSC found unstable after boot, most likely due to broken BIOS. 
Use 'tsc=unstable'.
  [ 1439.143498] sched_clock: Marking unstable (1439092126811, 
50992985)<-(1439477690212, -334199655)
  [ 1440.403916] clocksource: Switched to clocksource hpet
  [ 1443.553969] hrtimer: interrupt took 629117003 ns
  [ 1454.039245] INFO: NMI handler (nmi_cpu_backtrace_handler) took too long to 
run: 209.684 msecs
  [ 1454.454671] INFO: NMI handler (perf_event_nmi_handler) took too long to 
run: 44.646 msecs
  [ 1454.454673] perf: interrupt took too long (349007 > 2500), lowering 
kernel.perf_event_max_sample_rate to 500
  [ 1455.293492] INFO: NMI handler (perf_event_nmi_handler) took too long to 
run: 61.329 msecs
  [ 1455.293494] perf: interrupt took too long (479410 > 436258), lowering 
kernel.perf_event_max_sample_rate to 250
  [ 1463.284343] INFO: NMI handler (perf_event_nmi_handler) took too long to 
r

[Touch-packages] [Bug 1742867] Re: Screen blank, audio choppy, system locked

2018-01-11 Thread clickwir
Quick comment, before today I've never seen this happen on this PC. Now
it's happened 4 times in the past couple hours.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1742867

Title:
  Screen blank, audio choppy, system locked

Status in xorg package in Ubuntu:
  New

Bug description:
  While watching a YouTube video, screen went blank. Audio cut out,
  after a few seconds the audio started playing normally for a few more
  seconds then kept repeating the last half a second of audio for a few
  more seconds. Then it stopped and nothing responded.

  It did this a few times over the course of an hour. Had to power off
  the PC to get a reboot. Last time it did this I ssh'd from another PC
  to get dmesg and syslog info as it happened. Attaching those captures.

  clickwir@mach:~$ uname -a
  Linux mach 4.13.0-25-generic #29-Ubuntu SMP Mon Jan 8 21:14:41 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  clickwir@mach:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 17.10
  Release:17.10
  Codename:   artful

  
   dmesg 

  [   10.136445] bond0: Enslaving enp7s0f1 as an active interface with an up 
link
  [   10.136497] IPv6: ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
  [   10.144317] e1000e :07:00.0 enp7s0f0: changing MTU from 1500 to 9000
  [   10.310070] e1000e :07:00.1 enp7s0f1: changing MTU from 1500 to 9000
  [   10.625965] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
  [   10.730200] r8169 :02:00.0 eth0: link down
  [   10.730246] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
  [   12.573052] e1000e: enp7s0f0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   12.633055] e1000e: enp7s0f1 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   16.875586] FS-Cache: Loaded
  [   16.896010] FS-Cache: Netfs 'nfs' registered for caching
  [   16.914353] NFS: Registering the id_resolver key type
  [   16.914364] Key type id_resolver registered
  [   16.914364] Key type id_legacy registered
  [   17.485539] ip6_tables: (C) 2000-2006 Netfilter Core Team
  [   17.513074] Ebtables v2.0 registered
  [   17.564084] radeon_dp_aux_transfer_native: 74 callbacks suppressed
  [   17.863232] bridge: filtering via arp/ip/ip6tables is no longer available 
by default. Update your scripts to load br_netfilter if you need this.
  [   17.864899] virbr0: port 1(virbr0-nic) entered blocking state
  [   17.864903] virbr0: port 1(virbr0-nic) entered disabled state
  [   17.864995] device virbr0-nic entered promiscuous mode
  [   17.960322] nf_conntrack version 0.5.0 (65536 buckets, 262144 max)
  [   18.038385] virbr0: port 1(virbr0-nic) entered blocking state
  [   18.038388] virbr0: port 1(virbr0-nic) entered listening state
  [   18.095412] virbr0: port 1(virbr0-nic) entered disabled state
  [   89.815180] radeon_dp_aux_transfer_native: 74 callbacks suppressed
  [   92.062606] show_signal_msg: 27 callbacks suppressed
  [   92.062608] xembedsniproxy[2507]: segfault at 2 ip 55ea4a6890d7 sp 
7fff6c7a7c30 error 4 in xembedsniproxy[55ea4a67d000+13000]
  [   95.955166] radeon_dp_aux_transfer_native: 74 callbacks suppressed

  ### abnormal begins here ###

  [ 1429.496584] sched: RT throttling activated
  [ 1429.706303] clocksource: timekeeping watchdog on CPU3: Marking clocksource 
'tsc' as unstable because the skew is too large:
  [ 1429.706305] clocksource:   'hpet' wd_now: c4741f2e 
wd_last: c3bcdb60 mask: 
  [ 1429.706306] clocksource:   'tsc' cs_now: 4acf553cc2d 
cs_last: 4ac71a54967 mask: 
  [ 1429.706309] tsc: Marking TSC unstable due to clocksource watchdog
  [ 1434.739539] nfs: server 10.1.0.4 not responding, still trying
  [ 1437.469449] nfs: server 10.1.0.4 OK
  [ 1439.143494] TSC found unstable after boot, most likely due to broken BIOS. 
Use 'tsc=unstable'.
  [ 1439.143498] sched_clock: Marking unstable (1439092126811, 
50992985)<-(1439477690212, -334199655)
  [ 1440.403916] clocksource: Switched to clocksource hpet
  [ 1443.553969] hrtimer: interrupt took 629117003 ns
  [ 1454.039245] INFO: NMI handler (nmi_cpu_backtrace_handler) took too long to 
run: 209.684 msecs
  [ 1454.454671] INFO: NMI handler (perf_event_nmi_handler) took too long to 
run: 44.646 msecs
  [ 1454.454673] perf: interrupt took too long (349007 > 2500), lowering 
kernel.perf_event_max_sample_rate to 500
  [ 1455.293492] INFO: NMI handler (perf_event_nmi_handler) took too long to 
run: 61.329 msecs
  [ 1455.293494] perf: interrupt took too long (479410 > 436258), lowering 
kernel.perf_event_max_sample_rate to 250
  [ 1463.284343] INFO: NMI handler (perf_event_nmi_handler) took too long to 
run: 172.103 msecs
  [ 1463.284345] perf: interrupt took too long (1344829 > 599262), lowering 
kernel.perf_event_max_sample_rate to 250
  [ 1465.

[Touch-packages] [Bug 1742867] [NEW] Screen blank, audio choppy, system locked

2018-01-11 Thread clickwir
Public bug reported:

While watching a YouTube video, screen went blank. Audio cut out, after
a few seconds the audio started playing normally for a few more seconds
then kept repeating the last half a second of audio for a few more
seconds. Then it stopped and nothing responded.

It did this a few times over the course of an hour. Had to power off the
PC to get a reboot. Last time it did this I ssh'd from another PC to get
dmesg and syslog info as it happened. Attaching those captures.

clickwir@mach:~$ uname -a
Linux mach 4.13.0-25-generic #29-Ubuntu SMP Mon Jan 8 21:14:41 UTC 2018 x86_64 
x86_64 x86_64 GNU/Linux

clickwir@mach:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 17.10
Release:17.10
Codename:   artful


 dmesg 

[   10.136445] bond0: Enslaving enp7s0f1 as an active interface with an up link
[   10.136497] IPv6: ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
[   10.144317] e1000e :07:00.0 enp7s0f0: changing MTU from 1500 to 9000
[   10.310070] e1000e :07:00.1 enp7s0f1: changing MTU from 1500 to 9000
[   10.625965] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   10.730200] r8169 :02:00.0 eth0: link down
[   10.730246] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   12.573052] e1000e: enp7s0f0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
[   12.633055] e1000e: enp7s0f1 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
[   16.875586] FS-Cache: Loaded
[   16.896010] FS-Cache: Netfs 'nfs' registered for caching
[   16.914353] NFS: Registering the id_resolver key type
[   16.914364] Key type id_resolver registered
[   16.914364] Key type id_legacy registered
[   17.485539] ip6_tables: (C) 2000-2006 Netfilter Core Team
[   17.513074] Ebtables v2.0 registered
[   17.564084] radeon_dp_aux_transfer_native: 74 callbacks suppressed
[   17.863232] bridge: filtering via arp/ip/ip6tables is no longer available by 
default. Update your scripts to load br_netfilter if you need this.
[   17.864899] virbr0: port 1(virbr0-nic) entered blocking state
[   17.864903] virbr0: port 1(virbr0-nic) entered disabled state
[   17.864995] device virbr0-nic entered promiscuous mode
[   17.960322] nf_conntrack version 0.5.0 (65536 buckets, 262144 max)
[   18.038385] virbr0: port 1(virbr0-nic) entered blocking state
[   18.038388] virbr0: port 1(virbr0-nic) entered listening state
[   18.095412] virbr0: port 1(virbr0-nic) entered disabled state
[   89.815180] radeon_dp_aux_transfer_native: 74 callbacks suppressed
[   92.062606] show_signal_msg: 27 callbacks suppressed
[   92.062608] xembedsniproxy[2507]: segfault at 2 ip 55ea4a6890d7 sp 
7fff6c7a7c30 error 4 in xembedsniproxy[55ea4a67d000+13000]
[   95.955166] radeon_dp_aux_transfer_native: 74 callbacks suppressed

### abnormal begins here ###

[ 1429.496584] sched: RT throttling activated
[ 1429.706303] clocksource: timekeeping watchdog on CPU3: Marking clocksource 
'tsc' as unstable because the skew is too large:
[ 1429.706305] clocksource:   'hpet' wd_now: c4741f2e 
wd_last: c3bcdb60 mask: 
[ 1429.706306] clocksource:   'tsc' cs_now: 4acf553cc2d 
cs_last: 4ac71a54967 mask: 
[ 1429.706309] tsc: Marking TSC unstable due to clocksource watchdog
[ 1434.739539] nfs: server 10.1.0.4 not responding, still trying
[ 1437.469449] nfs: server 10.1.0.4 OK
[ 1439.143494] TSC found unstable after boot, most likely due to broken BIOS. 
Use 'tsc=unstable'.
[ 1439.143498] sched_clock: Marking unstable (1439092126811, 
50992985)<-(1439477690212, -334199655)
[ 1440.403916] clocksource: Switched to clocksource hpet
[ 1443.553969] hrtimer: interrupt took 629117003 ns
[ 1454.039245] INFO: NMI handler (nmi_cpu_backtrace_handler) took too long to 
run: 209.684 msecs
[ 1454.454671] INFO: NMI handler (perf_event_nmi_handler) took too long to run: 
44.646 msecs
[ 1454.454673] perf: interrupt took too long (349007 > 2500), lowering 
kernel.perf_event_max_sample_rate to 500
[ 1455.293492] INFO: NMI handler (perf_event_nmi_handler) took too long to run: 
61.329 msecs
[ 1455.293494] perf: interrupt took too long (479410 > 436258), lowering 
kernel.perf_event_max_sample_rate to 250
[ 1463.284343] INFO: NMI handler (perf_event_nmi_handler) took too long to run: 
172.103 msecs
[ 1463.284345] perf: interrupt took too long (1344829 > 599262), lowering 
kernel.perf_event_max_sample_rate to 250
[ 1465.175694] INFO: NMI handler (perf_event_nmi_handler) took too long to run: 
209.709 msecs
[ 1479.788229] perf: interrupt took too long (1849954 > 1681036), lowering 
kernel.perf_event_max_sample_rate to 250
[ 1481.889284] INFO: NMI handler (perf_event_nmi_handler) took too long to run: 
209.761 msecs
[ 1481.889284] perf: interrupt took too long (3252104 > 2312442), lowering 
kernel.perf_event_max_sample_rate to 250
[ 1491.745472] INFO: NMI handler (perf_event_nmi_handler) took too long to run: 
401.897 msecs
[

[Touch-packages] [Bug 1630946] Re: ubuntu-server depends on open-iscsi and runs iscsid

2017-09-26 Thread clickwir
Would like to have the ability to cleanly remove iscsi related processes
from systems that don't need it.

Sitting there, it's not hard on resources, but I'm trying to shave off
anything I can.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1630946

Title:
  ubuntu-server depends on open-iscsi and runs iscsid

Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  ubuntu-server has a hard dependency on open-iscsi, which means there
  is a daemon running (iscsid), and the package cannot be removed. All
  unnecessary daemons are a cause of concern when auditing a system.

  Propose moving this to "Recommends" instead, which currently has:

  Recommends: lxd, snapd

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-server 1.361
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  Uname: Linux 4.4.0-38-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Oct  6 10:43:04 2016
  Ec2AMI: ami-c06b1eb3
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: eu-west-1a
  Ec2InstanceType: t2.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  ProcEnviron:
   TERM=xterm-256color
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=en_US.UTF-8
   XDG_RUNTIME_DIR=
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1464990] Re: Job for dnsmasq.service failed because the control process exited with error code

2017-02-05 Thread clickwir
*** This bug is a duplicate of bug 1531184 ***
https://bugs.launchpad.net/bugs/1531184

Running 16.04.1 and this fix doesn't seem to make a difference.


Feb  5 10:55:56 ubuntu systemd[1]: dnsmasq.service: Start-post operation timed 
out. Stopping.
Feb  5 10:55:56 ubuntu dnsmasq[31933]: exiting on receipt of SIGTERM
Feb  5 10:55:56 ubuntu systemd[1]: Failed to start dnsmasq - A lightweight DHCP 
and caching DNS server.
Feb  5 10:55:56 ubuntu systemd[1]: Dependency failed for Host and Network Name 
Lookups.
Feb  5 10:55:56 ubuntu systemd[1]: nss-lookup.target: Job 
nss-lookup.target/start failed with result 'dependency'.
Feb  5 10:55:56 ubuntu systemd[1]: dnsmasq.service: Unit entered failed state.
Feb  5 10:55:56 ubuntu systemd[1]: dnsmasq.service: Failed with result 
'timeout'.


/lib/systemd/system/dnsmasq.service is where I added the 2 lines so it
looks like this:

[Unit]
Description=dnsmasq - A lightweight DHCP and caching DNS server
Requires=network.target
After=network-online.target
Wants=network-online.target


Yet the error still happens: ubuntu systemd[1]: nss-lookup.target: Job
nss-lookup.target/start failed with result 'dependency'.

I ran a apt --purge and removed dnsmasq completely, then reinstalled it.
Got the same nss-lookup.target error. Based on some other bugs, maybe
dnsmasq didn't have it's interface defined properly. So I added the
interface=enp6s0 line to the dnsmasq.conf file. Restarting the service
still yields the same nss-lookup.target error.

To get back to a working system, either a reboot or run "service dnsmasq
start" instead of restart.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1464990

Title:
  Job for dnsmasq.service failed because the control process exited with
  error code

Status in dnsmasq package in Ubuntu:
  Confirmed

Bug description:
  Got an error while upgrading:

  
  Setting up dnsmasq-base (2.72-3.1build1) ...
  Setting up dnsmasq (2.72-3.1build1) ...
  Job for dnsmasq.service failed because the control process exited with error 
code. See "systemctl status dnsmasq.service" and "journalctl -xe" for details.
  invoke-rc.d: initscript dnsmasq, action "restart" failed.
  ***

  systemctl status dnsmasq.service
  ● dnsmasq.service - dnsmasq - A lightweight DHCP and caching DNS server
     Loaded: loaded (/lib/systemd/system/dnsmasq.service; enabled; vendor 
preset: enabled)
    Drop-In: /run/systemd/generator/dnsmasq.service.d
     └─50-dnsmasq-$named.conf, 50-insserv.conf-$named.conf
     Active: failed (Result: exit-code) since dim. 2015-06-14 12:40:41 CEST; 
1min 11s ago
    Process: 29275 ExecStop=/etc/init.d/dnsmasq systemd-stop-resolvconf 
(code=exited, status=0/SUCCESS)
    Process: 29335 ExecStart=/etc/init.d/dnsmasq systemd-exec (code=exited, 
status=2)
    Process: 29331 ExecStartPre=/usr/sbin/dnsmasq --test (code=exited, 
status=0/SUCCESS)
   Main PID: 915 (code=exited, status=0/SUCCESS)

   systemd[1]: Starting dnsmasq - A lightweight DHCP and .
   dnsmasq[29331]: dnsmasq: syntax check OK.
   dnsmasq[29335]: dnsmasq: failed to create listening so...se
   systemd[1]: dnsmasq.service: Control process exited, c...=2
   systemd[1]: Failed to start dnsmasq - A lightweight DH...r.
   systemd[1]: dnsmasq.service: Unit entered failed state.
   systemd[1]: dnsmasq.service: Failed with result 'exit-...'.
  Hint: Some lines were ellipsized, use -l to show in full.

   journalctl -xe
   dnsmasq[29335]: failed to create listening socket for 192.168.1.2: Address 
already in
   dnsmasq[29335]: FAILED to start up
   systemd[1]: dnsmasq.service: Control process exited, code=exited status=2
   systemd[1]: Failed to start dnsmasq - A lightweight DHCP and caching DNS 
server.
  -- Subject: L'unité (unit) dnsmasq.service a échoué
  -- Defined-By: systemd
  -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
  --
  -- L'unité (unit) dnsmasq.service a échoué, avec le résultat failed.
   systemd[1]: Dependency failed for Host and Network Name Lookups.
  -- Subject: L'unité (unit) nss-lookup.target a échoué
  -- Defined-By: systemd
  -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
  --
  -- L'unité (unit) nss-lookup.target a échoué, avec le résultat dependency.
   systemd[1]: nss-lookup.target: Job nss-lookup.target/start failed with 
result 'depend
   systemd[1]: dnsmasq.service: Unit entered failed state.
   systemd[1]: dnsmasq.service: Failed with result 'exit-code'.
   polkitd(authority=local)[910]: Unregistered Authentication Agent for 
unix-process:292

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: dnsmasq 2.72-3.1build1
  ProcVersionSignature: Ubuntu 4.0.0-1.2-generic 4.0.5
  Uname: Linux 4.0.0-1-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.3-0ubuntu4
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Sun Jun 14 12:45:55 2015
  

[Touch-packages] [Bug 1632415] Re: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2016-10-14 Thread clickwir
Was going through the regular GUI upgrade process from 16.04, message
kept coming up dozens of times. After clicking CLOSE on about the 20th
one, I just held ENTER until they went away. Upgrade continued, gave a
message at the end that something didn't install right and my system
might be unstable.

After the upgrade process was done, I manually ran apt update and dist-
upgrade, it found several more things to do. Those all completed without
issue, rebooted and everything is fine so far.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gconf in Ubuntu.
https://bugs.launchpad.net/bugs/1632415

Title:
  package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  error after updating from 16.04.1 to 16.10

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gconf2 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.8.0-21.23-generic 4.8.0
  Uname: Linux 4.8.0-21-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Tue Oct 11 22:08:46 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-07-25 (78 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.1
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu7 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to yakkety on 2016-10-11 (0 days ago)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1254085] Re: ssh fails to connect to VPN host - hangs at 'expecting SSH2_MSG_KEX_ECDH_REPLY'

2015-11-16 Thread clickwir
Had the same hang. Client is Ubuntu 15.10 and server is 14.04, both up
to date as of today. Fix was to change client MTU from 9000 to 1500.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1254085

Title:
  ssh fails to connect to VPN host - hangs at 'expecting
  SSH2_MSG_KEX_ECDH_REPLY'

Status in openssh package in Ubuntu:
  Confirmed

Bug description:
  ssh -vvv  is failing for me where  is a VPN system.

  VPN is configured and connected via network-manager. Last messages
  from ssh (hangs forever):

  debug2: kex_parse_kexinit: none,z...@openssh.com
  debug2: kex_parse_kexinit: none,z...@openssh.com
  debug2: kex_parse_kexinit: 
  debug2: kex_parse_kexinit: 
  debug2: kex_parse_kexinit: first_kex_follows 0 
  debug2: kex_parse_kexinit: reserved 0 
  debug2: mac_setup: found hmac-md5
  debug1: kex: server->client aes128-ctr hmac-md5 none
  debug2: mac_setup: found hmac-md5
  debug1: kex: client->server aes128-ctr hmac-md5 none
  debug1: sending SSH2_MSG_KEX_ECDH_INIT
  debug1: expecting SSH2_MSG_KEX_ECDH_REPLY

  
  = Workaround =

  $ sudo apt-get install putty
  $ putty 

  This works perfectly.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: openssh-client 1:6.4p1-1
  ProcVersionSignature: Ubuntu 3.12.0-3.8-generic 3.12.0
  Uname: Linux 3.12.0-3-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.7-0ubuntu1
  Architecture: i386
  CurrentDesktop: Unity
  Date: Fri Nov 22 15:37:18 2013
  InstallationDate: Installed on 2010-10-21 (1128 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
  RelatedPackageVersions:
   ssh-askpass   1:1.2.4.1-9
   libpam-sshN/A
   keychain  2.7.1-1
   ssh-askpass-gnome 1:6.4p1-1
  SSHClientVersion: OpenSSH_6.4p1 Ubuntu-1, OpenSSL 1.0.1e 11 Feb 2013
  SourcePackage: openssh
  UpgradeStatus: Upgraded to trusty on 2013-11-01 (20 days ago)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1402195] Re: Newer versions available

2015-03-21 Thread clickwir
Running Kubuntu 14.10 and only have adb 1.0.31. Can't update my Nexus 4
to 5.0.1 because it requires at least adb 1.0.32.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to android-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1402195

Title:
  Newer versions available

Status in android-tools package in Ubuntu:
  Triaged
Status in android-tools source package in Vivid:
  Triaged

Bug description:
  When adb sideloading 5.0.0 - 5.0.1, the recovery on a nexus 5
  requires at least adb 1.0.32

  $ adb version
  Android Debug Bridge version 1.0.31

  :(

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: android-tools-adb 4.2.2+git20130218-3ubuntu36
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Dec 13 14:47:38 2014
  InstallationDate: Installed on 2014-02-07 (308 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  SourcePackage: android-tools
  UpgradeStatus: Upgraded to utopic on 2014-11-08 (34 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/android-tools/+bug/1402195/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1003950] Re: launcher does not show minimized update manager while clicked

2015-01-02 Thread clickwir
Me too. :-) Yup, just updated my laptop that's running 14.10. Software
Updater is on the side, I can right click on it and tell it to install
the updates. It even asks for the password, then installs the updates.
But doesn't show a window.

Running it manually works fine.

** Tags added: ui

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1003950

Title:
  launcher does not show minimized update manager while clicked

Status in Unity:
  Fix Released
Status in Unity 5.0 series:
  Fix Released
Status in Unity 6.0 series:
  Fix Released
Status in unity package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Confirmed
Status in unity source package in Precise:
  Fix Released
Status in update-manager source package in Precise:
  Confirmed
Status in unity source package in Quantal:
  Fix Released
Status in update-manager source package in Quantal:
  Won't Fix

Bug description:
  Update manager is showing up in the dock but I can click on the icon
  all day and nothing happens. Similarly if I do Super-S or Super-W it
  doesn't show up anywhere.

  Even if I alt-tab to the application nothing shows up. This happens
  only when update manager runs on its own. If I kill it and then launch
  it myself it comes to the foreground just fine.

  I'm not 100% sure whether this is a unity, compiz, or update-manager
  bug but so far my bet is on unity.

  =Original Report=
  Bug #877444 is showing again in latest updates, please re-open it. This is 
the exact same problem.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 669729] Re: pulseaudio[1641]: ratelimit.c: 22715 events suppressed

2015-01-02 Thread clickwir
 and there. But for the most part, it's acceptable. My
  uneducated guess is ALSA is skipping (rare, and not all the time) and
  pulseaudio doesn't know what to do and pukes.

  If you are interested, I've had some troubleshooting done by a helpful
  forum member here:
  http://kubuntuforums.net/forums/index.php?topic=3114316

  
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: E2E [ESS ES1978 (Maestro 2E)], device 0: ESS Maestro [ESS Maestro]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  clickwir   1768 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'E2E'/'ESS ES1978 (Maestro 2E) at 0x1000, irq 21'
 Mixer name : 'SigmaTel STAC9721,23'
 Components : 'AC97a:83847609'
 Controls  : 31
 Simple ctrls  : 21
  Card1.Amixer.info:
   Card hw:1 'HDMI'/'HDA ATI HDMI at 0xe011 irq 48'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100100'
 Controls  : 4
 Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  DistroRelease: Ubuntu 10.10
  InstallationMedia: Kubuntu 10.10 Maverick Meerkat - Release amd64 (20101007)
  NonfreeKernelModules: fglrx
  Package: alsa-driver (not installed)
  ProcEnviron:
   LANGUAGE=
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.35-23.36-generic 2.6.35.7
  Tags: maverick
  Uname: Linux 2.6.35-23-generic x86_64
  UserGroups:
   
  dmi.bios.date: 11/24/2009
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: JOQ3510J.86A.1126.2009.1124.2311
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: DQ35JO
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAD82085-804
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrJOQ3510J.86A.1126.2009.1124.2311:bd11/24/2009:svn:pn:pvr:rvnIntelCorporation:rnDQ35JO:rvrAAD82085-804:cvn:ct3:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/669729/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1320556] Re: Show copy dialog right click launcher entry doesn't work

2014-10-14 Thread clickwir
Same boat here. Ubuntu 14.04 64bit. FIle 3.10.1.

Was in the middle of copying files from a cd to the server (via SMB),
used Alt+Tab to switch to a Remmina RDP session. Kind of switched back
and forth too quickly and then had to Alt+Tab again till I got my RDP
session to the forefront. When I went back to clicking on the files
(icon on the left panel, still shows the file copy progress bar), I only
get the folder view. No dialog box with the copy. Also, the copy is very
very slow. I was able to copy the next 4 CD's from a Win7 box before
mine finished.

Right clicking on Files and then clicking on Show copy dialog does
nothing. No error, no visiual indication of anything. Double clicking on
the Files icon only presents me with the folder view window that's
already open and working fine.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1320556

Title:
   Show copy dialog right click launcher entry doesn't work

Status in Unity:
  Confirmed
Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  I noticed  that right-clicking on the and clicking show copy dialogue 
doesn't work (again) with 14.04.
  Seems to be a regression bug of #887821 

  my nautilus version is: GNOME nautilus 3.10.1

  unity version: unity 7.2.0

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140423-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Sat May 17 23:48:56 2014
  InstallationDate: Installed on 2014-05-03 (14 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp