[Bug 1627474] Re: ath10k_pci 0000:03:00.0: firmware crashed! (uuid n/a)
On Tue, Oct 4, 2016 at 6:25 AM Joseph Salisbury < joseph.salisb...@canonical.com> wrote: Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? No - it's a new machine on which I've installed Yakkety. Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.8 kernel[0]. Yes, though I did already try the upstream firmwares directly, which didn't fix it. I've updated and tested with the latest 4.8 in yakkety first: michael@hpmor2:~$ dmesg | grep ath10k.*crashed [ 274.052266] ath10k_pci :03:00.0: firmware crashed! (uuid 80f6a701-8aa3-4f34-8d20-49e478f9020a) [ 276.900284] ath10k_pci :03:00.0: firmware crashed! (uuid 55e52555-0bfb-42b8-b612-579a9188b642) [ 1247.381606] ath10k_pci :03:00.0: firmware crashed! (uuid 6f45c6af-33a0-4c5d-a65c-785a97c2ea3a) michael@hpmor2:~$ uname -a Linux hpmor2 4.8.0-21-generic #23-Ubuntu SMP Tue Oct 4 18:27:25 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux Then, given that you wrote your comment before the mainline/4.8.1 was created, I've also tested with that: michael@hpmor2:~$ dmesg | grep ath10k.*crashed [ 652.277650] ath10k_pci :03:00.0: firmware crashed! (uuid n/a) [ 655.127699] ath10k_pci :03:00.0: firmware crashed! (uuid n/a) michael@hpmor2:~$ uname -a Linux hpmor2 4.8.1-040801-generic #201610071031 SMP Fri Oct 7 14:34:10 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux Updating ... thanks Joseph. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1627474 Title: ath10k_pci :03:00.0: firmware crashed! (uuid n/a) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1627474/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1627474] [NEW] ath10k_pci 0000:03:00.0: firmware crashed! (uuid n/a)
Public bug reported: The wireless card in my Acer V3-372-587T suffers from firmware crashes regularly (every 5-10mins approx). $ lsb_release -rd Description:Ubuntu Yakkety Yak (development branch) Release:16.10 Checking dmesg I see: $ dmesg | grep ath10k [91/214] [7.773800] ath10k_pci :03:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 [8.123875] request_firmware: ath10k/pre-cal-pci-:03:00.0.bin [8.126477] ath10k_pci :03:00.0: Direct firmware load for ath10k/pre-cal-pci-:03:00.0.bin fa$ led with error -2 [8.126481] request_firmware: ath10k/cal-pci-:03:00.0.bin [8.126492] ath10k_pci :03:00.0: Direct firmware load for ath10k/cal-pci-:03:00.0.bin failed with error -2 [8.126493] request_firmware: ath10k/QCA6174/hw3.0/firmware-5.bin [8.127095] ath10k_pci :03:00.0: Direct firmware load for ath10k/QCA6174/hw3.0/firmware-5.bin fa$ led with error -2 [8.127098] ath10k_pci :03:00.0: could not fetch firmware file 'ath10k/QCA6174/hw3.0/firmware-5.$ in': -2 [8.127101] request_firmware: ath10k/QCA6174/hw3.0/firmware-4.bin [8.129458] ath10k_pci :03:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 105b:e09$ [8.129460] ath10k_pci :03:00.0: kconfig debug 0 debugfs 0 tracing 0 dfs 0 testmode 0 [8.129954] ath10k_pci :03:00.0: firmware ver WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 features wowla$ ,ignore-otp,no-4addr-pad crc32 75dee6c5 [8.195123] request_firmware: ath10k/QCA6174/hw3.0/board-2.bin [8.198141] ath10k_pci :03:00.0: board_file api 2 bmi_id N/A crc32 6fc88fe7 [ 10.338326] ath10k_pci :03:00.0: htt-ver 3.26 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypt$ 1 [ 10.436186] ath10k_pci :03:00.0 wlp3s0: renamed from wlan0 [ 319.064117] ath10k_pci :03:00.0: firmware crashed! (uuid n/a) [ 319.064164] ath10k_pci :03:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 105b:e09$ [ 319.064174] ath10k_pci :03:00.0: kconfig debug 0 debugfs 0 tracing 0 dfs 0 testmode 0 [ 319.066828] ath10k_pci :03:00.0: firmware ver WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 features wowla$ ,ignore-otp,no-4addr-pad crc32 75dee6c5 [ 319.068042] ath10k_pci :03:00.0: board_file api 2 bmi_id N/A crc32 6fc88fe7 [ 319.068055] ath10k_pci :03:00.0: htt-ver 3.26 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypt$ 1 [ 319.070104] ath10k_pci :03:00.0: firmware register dump: [ 319.070127] ath10k_pci :03:00.0: [00]: 0x0503 0x15B3 0x009860FA 0x00955B31 [ 319.070139] ath10k_pci :03:00.0: [04]: 0x009860FA 0x00060730 0x0004 0x0040E8A0 [ 319.070148] ath10k_pci :03:00.0: [08]: 0x00498110 0x00955A00 0x000B 0x0040 [ 319.070158] ath10k_pci :03:00.0: [12]: 0x0009 0x 0x00952CD0 0x00952CE6 [ 319.070167] ath10k_pci :03:00.0: [16]: 0x00952CC4 0x0091080D 0x 0x0091080D [ 319.070176] ath10k_pci :03:00.0: [20]: 0x409860FA 0x0040E7E8 0x 0x0041E0DC [ 319.070195] ath10k_pci :03:00.0: [24]: 0x800B5A1D 0x0040E848 0x000F 0xC09860FA [ 319.070214] ath10k_pci :03:00.0: [28]: 0x809B3230 0x0040E948 0x0018 0x004313DC [ 319.070231] ath10k_pci :03:00.0: [32]: 0x809B2992 0x0040E998 0x0040E9BC 0x00429548 [ 319.070246] ath10k_pci :03:00.0: [36]: 0x8091D252 0x0040E9B8 0x 0x0001 [ 319.070255] ath10k_pci :03:00.0: [40]: 0x809FF05D 0x0040EA68 0x0043A380 0x00429C10 [ 319.070264] ath10k_pci :03:00.0: [44]: 0x809FCFDB 0x0040EA88 0x0043A380 0x0001 [ 319.070272] ath10k_pci :03:00.0: [48]: 0x80911210 0x0040EAD8 0x0010 0x004041D0 [ 319.070281] ath10k_pci :03:00.0: [52]: 0x80911154 0x0040EB28 0x0040 0x [ 319.070290] ath10k_pci :03:00.0: [56]: 0x8091122D 0x0040EB48 0x 0x00400600 [ 321.584066] ath10k_pci :03:00.0: device successfully recovered [ 2409.664284] ath10k_pci :03:00.0: firmware crashed! (uuid n/a) [ 2409.664332] ath10k_pci :03:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 105b:e09d [ 2409.664342] ath10k_pci :03:00.0: kconfig debug 0 debugfs 0 tracing 0 dfs 0 testmode 0 [ 2409.667010] ath10k_pci :03:00.0: firmware ver WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 features wowlan ,ignore-otp,no-4addr-pad crc32 75dee6c5 [ 2409.668230] ath10k_pci :03:00.0: board_file api 2 bmi_id N/A crc32 6fc88fe7 [ 2409.668243] ath10k_pci :03:00.0: htt-ver 3.26 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1 [ 2409.670262] ath10k_pci :03:00.0: firmware register dump: [ 2409.670279] ath10k_pci :03:00.0: [00]: 0x0503 0x15B3 0x009860FA 0x00955B31 [ 2409.670289] ath10k_pci :03:00.0: [04]: 0x009860FA 0x00060730 0x0004 0x0040E8A0 [ 2409.670298] ath10k_pci :03:00.0: [08]: 0x00498110 0x00955A00 0x000B 0x0040 [ 2409.670307] ath10k_pci :03:00.0: [12]: 0x0009 0x 0x00952CD0 0x00952CE6
[Bug 1603018] Re: snap create-user gets bad username
** Also affects: snappy Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1603018 Title: snap create-user gets bad username To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1603018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1603018] Re: snap create-user gets bad username
Assuming we don't want people to have to change usernames on SSO/LP (sometimes not even possible, if people have packages published in PPAs - from memory?), I don't (yet) see any other option than to use the username with a period from SSO/LP (which is posix compliant [1]). But can we be sure usernames with dots will be safe on other distros? (hopefully given it's within the standard). Or what other options are there? I'd be happy to provide a fix if there's a decided direction. [1] See points in http://askubuntu.com/questions/405638/what-are-the- disadvantages-of-having-a-dot-in-a-user-name#405668 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1603018 Title: snap create-user gets bad username To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1603018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1603018] [NEW] snap create-user gets bad username
Public bug reported: ubuntu@dev-xenial3:~⟫ sudo snap create-user michael.nel...@canonical.com error: bad user result: cannot create user michael.nelson: adduser failed with exit status 1: adduser: Please enter a username matching the regular expression configured via the NAME_REGEX[_SYSTEM] configuration variable. Use the `--force-badname' option to relax this check or reconfigure NAME_REGEX. ubuntu@dev-xenial3:~⟫ curl -s https://login.ubuntu.com/api/v2/keys/michael.nel...@canonical.com | jq .username "michael.nelson" ubuntu@dev-xenial3:~⟫ grep NAME_REGEX /etc/adduser.conf #NAME_REGEX="^[a-z][-a-z0-9_]*\$" Assuming the above commented out NAME_REGEX is the default, then create- user will fail for some usernames which launchpad/SSO allow. ** Affects: snapd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1603018 Title: snap create-user gets bad username To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1603018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1581310] Re: ubuntu-core doesn't allow sed -i (fchown syscall)
Interestingly, sed is happy to ignore failures on fchown itself: $ grep chown sed/execute.c -B4 -A2 output_fd = fileno (output_file.fp); #ifdef HAVE_FCHOWN /* Try to set both UID and GID, but if that fails, try to set only the GID. Ignore failure. */ if (fchown (output_fd, input->st.st_uid, input->st.st_gid) == -1) ignore_value (fchown (output_fd, -1, input->st.st_gid)); #endif copy_acl (input->in_file_name, input_fd, -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1581310 Title: ubuntu-core doesn't allow sed -i (fchown syscall) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1581310/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1581310] [NEW] ubuntu-core doesn't allow sed -i (fchown syscall)
Public bug reported: Similar to bug 1580018, I'm not sure if the default apparmor profile is not correct, or possibly this bug is invalid and `sed -i.bak` should be denied. AFAICT, the issue is that sed -i.bak tries a chown syscall on the backup file in the $SNAP_USER_DATA directory, and the apparmor profile does not allow that (perhaps for good reason). michael@dev-xenial2:~/dev/todo.txt⟫ cat /snap/todo-txt/11/test-sed.sh #! /bin/bash echo "The quick brown fox jumped over the lazy dog" > $SNAP_USER_DATA/sed-test.txt sed 's/quick/fast/' $SNAP_USER_DATA/sed-test.txt | tee $SNAP_USER_DATA/sed-output.txt sed -i.bak 's/quick/fast/' $SNAP_USER_DATA/sed-test.txt chown michael@dev-xenial2:~/dev/todo.txt⟫ todo-txt.test-sed The fast brown fox jumped over the lazy dog /snap/todo-txt/11/test-sed.sh: line 5: 11763 Bad system call sed -i.bak 's/quick/fast/' $SNAP_USER_DATA/sed-test.txt /snap/todo-txt/11/test-sed.sh: line 6: /bin/chown: Permission denied 126 michael@dev-xenial2:~/dev/todo.txt⟫ ls -l ~/snap/todo-txt/11/ total 12 -rw-rw-r-- 1 michael michael 44 May 13 04:30 sed-output.txt -rw-rw-r-- 1 michael michael 45 May 13 04:30 sed-test.txt -- 1 michael michael 44 May 13 04:30 sedwCnCDY michael@dev-xenial2:~/dev/todo.txt⟫ dmesg -H | tail -n3 [ +39.843825] audit: type=1326 audit(1463113859.687:232): auid=1001 uid=1001 gid=1001 ses=4 pid=11763 comm="sed" exe="/bin/sed" sig=31 arch=c03e syscall=93 compat=0 ip=0x7f8428874a77 code=0x0 [ +0.001342] audit: type=1400 audit(1463113859.691:233): apparmor="DENIED" operation="exec" profile="snap.todo-txt.test-sed" name="/bin/chown" pid=11764 comm="test-sed.sh" requested_mask="x" denied_mask="x" fsuid=1001 ouid=0 [ +0.000100] audit: type=1400 audit(1463113859.691:234): apparmor="DENIED" operation="open" profile="snap.todo-txt.test-sed" name="/bin/chown" pid=11764 comm="test-sed.sh" requested_mask="r" denied_mask="r" fsuid=1001 ouid=0 michael@dev-xenial2:~/dev/todo.txt⟫ scmp_sys_resolver 93 fchown ** Affects: snapd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1581310 Title: ubuntu-core doesn't allow sed -i (fchown syscall) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1581310/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1580018] Re: ubuntu-core image missing awk
Thanks Jamie. My ubuntu-core was out of date, but updating doesn't
change the symlinks which my snap'd app sees:
michael@dev-xenial2:~/dev/todo.txt⟫ snap list
Name Version Developer
hello-world 6.0 canonical
todo 2.1
ubuntu-core 16.04.0-24 canonical
michael@dev-xenial2:~/dev/todo.txt⟫ sudo snap refresh ubuntu-core
64.64 MB / 64.64 MB
[]
100.00 % 26.19 MB/s
michael@dev-xenial2:~/dev/todo.txt⟫ snap list
Name Version Developer
hello-world 6.0 canonical
todo 2.1
ubuntu-core 16.04+20160419.20-55 canonical
michael@dev-xenial2:~/dev/todo.txt⟫ rm -rf parts/testawk && sudo snap remove
todo && snapcraft && sudo snap install todo_2.1_amd64.
snap
[-] Remove snap "todo" from the system
...
Snapped todo_2.1_amd64.snap
[/] Setup snap "todo" security profiles
michael@dev-xenial2:~/dev/todo.txt⟫ todo.testawk
ls: cannot access '/usr/bin/gawk': No such file or directory
lrwxrwxrwx 1 root root 21 Apr 19 20:52 /usr/bin/awk -> /etc/alternatives/awk
-rwxr-xr-x 1 root root 117768 Mar 24 2014 /usr/bin/mawk
lrwxrwxrwx 1 root root 13 Apr 12 14:18 /etc/alternatives/awk -> /usr/bin/gawk
/snap/todo/11/testawk.sh: line 5: /usr/bin/awk: No such file or directory
/snap/todo/11/testawk.sh: line 6: /etc/alternatives/awk: No such file or
directory
michael@dev-xenial2:~/dev/todo.txt⟫ cat /snap/todo/11/testawk.sh
#! /bin/bash
ls -l /usr/bin/{,g,m}awk
ls -l /etc/alternatives/awk
/usr/bin/awk -h
/etc/alternatives/awk -h
michael@dev-xenial2:~/dev/todo.txt⟫ uname -a
Linux dev-xenial2 4.4.0-18-generic #34-Ubuntu SMP Wed Apr 6 14:01:02 UTC 2016
x86_64 x86_64 x86_64 GNU/Linux
This is running on a (canonistack) xenial instance .
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1580018
Title:
ubuntu-core image missing awk
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1580018/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1580018] Re: ubuntu-core image missing awk
** Description changed:
- I'm trying to snap a tool which uses awk. I checked the default apparmor
- profile for any snap, and it seems to indicate that awk is installed and
- enabled by the profile, but when checking (via a test snap),
- /usr/bin/awk symlinks to /etc/alternatives/awk symlinks to /usr/bin/gawk
- which doesn't exist (in ubuntu-core 16.04.0-24):
+ I'm trying to snap a tool which uses awk. Now I can try including awk in
+ my snap directly, but I checked the default apparmor profile for any
+ snap, and it seems to indicate that awk is installed and enabled by the
+ profile, but when checking (via a test snap), /usr/bin/awk symlinks to
+ /etc/alternatives/awk symlinks to /usr/bin/gawk which doesn't exist (in
+ ubuntu-core 16.04.0-24):
- michael@dev-xenial2:~/dev/todo.txt⟫ cat /snap/todo/11/testawk.sh
+ michael@dev-xenial2:~/dev/todo.txt⟫ cat /snap/todo/11/testawk.sh
#! /bin/bash
ls -l /usr/bin/{,g,m}awk
ls -l /etc/alternatives/awk
/usr/bin/awk -h
/etc/alternatives/awk -h
- michael@dev-xenial2:~/dev/todo.txt⟫ todo.testawk
+ michael@dev-xenial2:~/dev/todo.txt⟫ todo.testawk
ls: cannot access '/usr/bin/gawk': No such file or directory
lrwxrwxrwx 1 root root 21 Mar 8 11:29 /usr/bin/awk ->
/etc/alternatives/awk
-rwxr-xr-x 1 root root 117768 Mar 24 2014 /usr/bin/mawk
lrwxrwxrwx 1 root root 13 Apr 12 14:18 /etc/alternatives/awk -> /usr/bin/gawk
/snap/todo/11/testawk.sh: line 5: /usr/bin/awk: No such file or directory
/snap/todo/11/testawk.sh: line 6: /etc/alternatives/awk: No such file or
directory
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1580018
Title:
ubuntu-core image missing awk
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1580018/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1580018] [NEW] ubuntu-core image missing awk
Public bug reported:
I'm trying to snap a tool which uses awk. I checked the default apparmor
profile for any snap, and it seems to indicate that awk is installed and
enabled by the profile, but when checking (via a test snap),
/usr/bin/awk symlinks to /etc/alternatives/awk symlinks to /usr/bin/gawk
which doesn't exist (in ubuntu-core 16.04.0-24):
michael@dev-xenial2:~/dev/todo.txt⟫ cat /snap/todo/11/testawk.sh
#! /bin/bash
ls -l /usr/bin/{,g,m}awk
ls -l /etc/alternatives/awk
/usr/bin/awk -h
/etc/alternatives/awk -h
michael@dev-xenial2:~/dev/todo.txt⟫ todo.testawk
ls: cannot access '/usr/bin/gawk': No such file or directory
lrwxrwxrwx 1 root root 21 Mar 8 11:29 /usr/bin/awk -> /etc/alternatives/awk
-rwxr-xr-x 1 root root 117768 Mar 24 2014 /usr/bin/mawk
lrwxrwxrwx 1 root root 13 Apr 12 14:18 /etc/alternatives/awk -> /usr/bin/gawk
/snap/todo/11/testawk.sh: line 5: /usr/bin/awk: No such file or directory
/snap/todo/11/testawk.sh: line 6: /etc/alternatives/awk: No such file or
directory
** Affects: snapd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1580018
Title:
ubuntu-core image missing awk
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1580018/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1564209] Re: Doesn't recognise own reviews
** Changed in: rnr-server Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1564209 Title: Doesn't recognise own reviews To manage notifications about this bug go to: https://bugs.launchpad.net/rnr-server/+bug/1564209/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1564209] Re: Doesn't recognise own reviews
@fgallina or @kelvin: Can you check the background for these decisions. I'm not 100% but from memory RnR used to use the SSO (well, LP) username when it has one for the user (as SSO users don't always have a username, it depends whether they have an LP account), so I don't know that we can provide a username consistently. But in Robert's case I'd imagine it's for a user who certainly does have a username (his own account?) The only consistent options I can imagine are: 1) always return the consumer key - @Robert - can you use that instead to identify (sorry, I don't know the background), and will this break anything (doubt it, if they're not broken already - if it does currently return either) 2) add a separate consumer_key which always has the consumer key. Rodney is keen for (1) so that it's consistent with the click rnr api: 21:47 < noodles> dobey: could you use a different key from the result, I mean if consumer_key was added separately? 21:48 < dobey> noodles: well i think we should match what we're doing for click; and i think software-center might be doing this comparison already anyway 21:57 < dobey> noodles: so, imo, always returning the consumer_key value for everyone in reviewer_username there, would be best 21:59 < noodles> dobey: Right, but that's exactly what Robert *doesn't* want, unless he could also identify with the consumer key? 21:59 < dobey> noodles: he can identify with the consumer key -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1564209 Title: Doesn't recognise own reviews To manage notifications about this bug go to: https://bugs.launchpad.net/rnr-server/+bug/1564209/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1451632] Re: drm:intel_cpu_fifo_underrun_irq_handler [i915] - complete lockups
@francis-regan: I'm still getting issues with Chromium on 16.04, but I don't see the same (fifo_underrun) error. So it's likely that it was solved. What I see now (only just checked the logs) are messages like: Mar 23 08:27:11 hpmor kernel: [20182.144009] [drm] stuck on render ring Mar 23 08:27:11 hpmor kernel: [20182.145137] [drm] GPU HANG: ecode 7:0:0x7ecffd67, in chromium-browse [2306], reason: Ring hung, action: reset Mar 23 08:27:11 hpmor kernel: [20182.147336] drm/i915: Resetting chip after gpu hang but that's likely a separate bug. Other similar messages mention that it could be a userspace issue too: Mar 23 10:11:18 hpmor kernel: [ 4448.875191] [drm] stuck on render ring Mar 23 10:11:18 hpmor kernel: [ 4448.876441] [drm] GPU HANG: ecode 7:0:0x85dfbff8, in chromium-browse [2320], reason: Ring hung, action : reset Mar 23 10:11:18 hpmor kernel: [ 4448.876444] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. Mar 23 10:11:18 hpmor kernel: [ 4448.876445] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1451632 Title: drm:intel_cpu_fifo_underrun_irq_handler [i915] - complete lockups To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1451632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1451632] Re: drm:intel_cpu_fifo_underrun_irq_handler [i915] - complete lockups
FWIW, I've switched back to Chromium after installing 16.04 on the same machine, to see if I can reproduce it with the Xenial kernel, and it's been 4 days without any such lockups. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1451632 Title: drm:intel_cpu_fifo_underrun_irq_handler [i915] - complete lockups To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1451632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1336742] Re: Caching responses with Vary header
On Wed, Jul 8, 2015 at 11:45 PM Chris J Arges 1336...@bugs.launchpad.net wrote: Hello Michael, or anyone else affected, Hi Chris, Unfortunately I'm not able to reproduce the original problem with the existing 3.3.8-1ubuntu6.2 (which is different to what I originally used) . As I mentioned in the description, I'd not tested with a pristine trusty environment, nor can I setup the same env with which I tested in the original description. In case I'm missing something obvious, and it helps someone else reproduce the original issue and/or confirm the fix, here is how I tried to reproduce the original problem just now on a freshly booted trusty instance: http://paste.ubuntu.com/11853981/ Of course, if we're unable to reproduce the original issue, it may have been specific to something in the environment I had (or have others seen the same?). One possibility is that the app server I was using was sending an incorrect Content-Length when Vary was present (as I noticed that an incorrect Content-Length header causes squid to not cache, which is understandable). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1336742 Title: Caching responses with Vary header To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/1336742/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1336742] Re: Caching responses with Vary header
On Wed, Jul 8, 2015 at 11:45 PM Chris J Arges 1336...@bugs.launchpad.net wrote: Hello Michael, or anyone else affected, Hi Chris, Unfortunately I'm not able to reproduce the original problem with the existing 3.3.8-1ubuntu6.2 (which is different to what I originally used) . As I mentioned in the description, I'd not tested with a pristine trusty environment, nor can I setup the same env with which I tested in the original description. In case I'm missing something obvious, and it helps someone else reproduce the original issue and/or confirm the fix, here is how I tried to reproduce the original problem just now on a freshly booted trusty instance: http://paste.ubuntu.com/11853981/ Of course, if we're unable to reproduce the original issue, it may have been specific to something in the environment I had (or have others seen the same?). One possibility is that the app server I was using was sending an incorrect Content-Length when Vary was present (as I noticed that an incorrect Content-Length header causes squid to not cache, which is understandable). -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1336742 Title: Caching responses with Vary header To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/1336742/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1451632] [NEW] drm:intel_cpu_fifo_underrun_irq_handler [i915] - complete lockups
Public bug reported: After updating to vivid, I'm experiencing lockups when visiting certain pages (not sure if it's flash-enabled) with chromium-browser. I see the following in the syslog matching the corresponding time (but don't know whether it's the cause): May 5 11:11:42 michael-acer kernel: [16951.714263] [drm:intel_set_cpu_fifo_underrun_reporting [i915]] *ERROR* uncleared fifo underrun on pipe A May 5 11:11:42 michael-acer kernel: [16951.714344] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun May 5 11:11:49 michael-acer org.freedesktop.Notifications[1833]: ** (notify-osd:2671): WARNING **: dnd_is_screensaver_active(): Got error Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, th e reply timeout expired, or the network connection was broken. May 5 11:11:52 michael-acer dbus[759]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop .nm-dispatcher.service' Let me know if I can provide more info. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue May 5 11:35:03 2015 DistUpgraded: 2015-05-02 09:55:23,389 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a06] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0a11] InstallationDate: Installed on 2014-09-03 (243 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Acer Peppy ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash tpm_tis.force=1 vt.handoff=7 SourcePackage: xserver-xorg-video-intel UpgradeStatus: Upgraded to vivid on 2015-05-01 (3 days ago) dmi.bios.date: 10/18/2013 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvncoreboot:bvr:bd10/18/2013:svnAcer:pnPeppy:pvr1.0:cvnAcer:ct3:cvr: dmi.product.name: Peppy dmi.product.version: 1.0 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Tue May 5 11:18:54 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4402 vendor CMN xserver.version: 2:1.17.1-0ubuntu3 ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu vivid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1451632 Title: drm:intel_cpu_fifo_underrun_irq_handler [i915] - complete lockups To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1451632/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1336742] Re: Caching responses with Vary header
On Fri, Feb 27, 2015 at 1:27 AM, Robie Basak 1336...@bugs.launchpad.net wrote: We're past feature freeze for Vivid now, so I can't just update to the latest any more, unless only bugfixes are involved or the release team grant an exception. If you can give me backported patches though, I can apply those. I backported the fix to trusty as per the attached branch. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1336742 Title: Caching responses with Vary header To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/1336742/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1336742] Re: Caching responses with Vary header
On Fri, Feb 27, 2015 at 1:27 AM, Robie Basak 1336...@bugs.launchpad.net wrote: We're past feature freeze for Vivid now, so I can't just update to the latest any more, unless only bugfixes are involved or the release team grant an exception. If you can give me backported patches though, I can apply those. I backported the fix to trusty as per the attached branch. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1336742 Title: Caching responses with Vary header To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/1336742/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1336742] [NEW] Caching responses with Vary header
Public bug reported: See the upstream bug report for more details [1], but it seems as though squid in trusty isn't caching any response which includes a vary header [2]. The upstream bug was fixed in 3.3.12 [3]. Steps to reproduce: * Setup an application returning responses with Vary: User-Agent * Add squid in front of an application server * Make multiple requests to squid Expected result: * Second request is a Hit Actual result: * Second (and subsequent) requests are all misses. Repeat without a Vary header and things are cached as expected. Note, I've only reproduced this with a specific setup (as in [2]), I've not yet reproduced with a simplified setup to be certain I'm seeing the upstream bug. [1] http://bugs.squid-cache.org/show_bug.cgi?id=3806 [2] http://paste.ubuntu.com/7736175/ [3] http://www.squid-cache.org/Versions/v3/3.3/changesets/SQUID_3_3_12.html ** Affects: squid3 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1336742 Title: Caching responses with Vary header To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1336742/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1336742] [NEW] Caching responses with Vary header
Public bug reported: See the upstream bug report for more details [1], but it seems as though squid in trusty isn't caching any response which includes a vary header [2]. The upstream bug was fixed in 3.3.12 [3]. Steps to reproduce: * Setup an application returning responses with Vary: User-Agent * Add squid in front of an application server * Make multiple requests to squid Expected result: * Second request is a Hit Actual result: * Second (and subsequent) requests are all misses. Repeat without a Vary header and things are cached as expected. Note, I've only reproduced this with a specific setup (as in [2]), I've not yet reproduced with a simplified setup to be certain I'm seeing the upstream bug. [1] http://bugs.squid-cache.org/show_bug.cgi?id=3806 [2] http://paste.ubuntu.com/7736175/ [3] http://www.squid-cache.org/Versions/v3/3.3/changesets/SQUID_3_3_12.html ** Affects: squid3 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1336742 Title: Caching responses with Vary header To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1336742/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1318144] Re: Can't edit reviews
** Project changed: software-center-agent = rnr-server -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1318144 Title: Can't edit reviews To manage notifications about this bug go to: https://bugs.launchpad.net/rnr-server/+bug/1318144/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1318144] Re: Can't edit reviews
The reviews server doesn't (didn't last time I checked [1]) allow a second review for the same user, returning a 400 not allowed [2]. The other aspect is exactly right - the click reviews server only allows creating reviews right now. It's trivial to move the other functionality across from the older deb-reviews app, but we'd like to do that as it's needed. So checking what's there, I assume the things we'll want right now are: * edit review (PUT to the review resource) * delete review (DELETE to the review resource, but doesn't delete from the db, just filters out) Things that we may need soon (and which are easy enough to do at the same time on the server): * flag a review * mark a review as useful * include review 'usefulness' on the review resource uri * Add a hal+json format for appropriate accept header (for consistency with other apis) [1] See the example at the bottom returning a 400 with the error A user cannot create multiple reviews for an app. https://wiki.ubuntu.com/AppStore/Interfaces/RatingsAndReviews ** Changed in: rnr-server Status: New = Triaged ** Changed in: rnr-server Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1318144 Title: Can't edit reviews To manage notifications about this bug go to: https://bugs.launchpad.net/rnr-server/+bug/1318144/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1302947] Re: [FFe] ansible 1.5.4
+1 Thanks mvo. One small but incredible useful feature that 1.5 brings is the ability to loop over hashes in your playbook. In juju-world, this enables you to loop over all your relations for a specific interface very neatly. [1] http://docs.ansible.com/playbooks_loops.html#looping-over-hashes Thanks mvo! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1302947 Title: [FFe] ansible 1.5.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ansible/+bug/1302947/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1263128] Re: Skype is hidden under technical items in USC when installed from deb downloaded from skype
On Thu, Feb 6, 2014 at 8:28 PM, John Pugh john.p...@canonical.com wrote: From #3 above, issue #2 is not present in 13.04 and is present in 13.10+. This would lead one to believe the problem is either in the SCA or in the software-center client (in one of the USC components). Hi John. Yes, the issue that once it is installed it only appears in the technical items must be something that USC can fix. I'll ask Rodney if he can take a look. All I see is that it should appear as it has a desktop file: michael-X201EP# ~/tmp/skype $ dpkg --contents skype-ubuntu-precise_4.2.0.13-1_i386.deb | grep desktop -rw-r--r-- root/root 249 2013-12-18 19:52 ./usr/share/applications/skype.desktop Issue #1 on the other hand is likely due to the multiarch packaging issue mentioned below in paragraph #3. Yes, this is unrelated to USC, as you say. On an amd64 system, there is no 'skype' package installed after installing the downloaded deb, only 'skype:i386', so the partner version is still ready to be installed (http://paste.ubuntu.com/6908092/). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1263128 Title: Skype is hidden under technical items in USC when installed from deb downloaded from skype To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1263128/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1263128] Re: Skype is hidden under technical items in USC when installed from deb downloaded from skype
On Fri, Feb 7, 2014 at 9:07 PM, Marco Cimmino cimmino.ma...@gmail.com wrote: Hi, yes I think John is right, the problem is: Skype is not interested in splitting the package into two different packages, this will make the user confused at our web site download page and we would like to still provide Ubuntu package on our website. So what else could be done? Is there anything in our package (32-bit) that could be done to prevent this? I don't know - but I'll ask Steve who packaged the partner version if he knows. Ultimately, I think you'd need two packages - one skype package that is arch-independent so that you always end up with a 'skype' package installed, and a skype-bin which installs the i386 binaries, and I think you can only hide the two packages from the user by either using a repository (where one pkg depends on the other), or doing something ugly like the first package downloading and installing the second. Steve? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1263128 Title: Skype is hidden under technical items in USC when installed from deb downloaded from skype To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1263128/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1263128] Re: Skype is hidden under technical items in USC when installed from deb downloaded from skype
On Mon, Feb 10, 2014 at 7:03 PM, Marco Cimmino cimmino.ma...@gmail.com wrote: Ultimately, I think you'd need two packages - one skype package that is arch-independent so that you always end up with a 'skype' package installed, and a skype-bin which installs the i386 binaries I guess I haven't been clear enough, but Skype is NOT interested in creating TWO packages only to workaround this problem. Sorry Marco - I do understand that you're not interested in creating two packages, I was only commenting that we need to ask someone who may know other solutions, as I can't see how it could work without that. I've already contacted Steve, and am waiting to hear back from him. Plus this mean on skype.com we would need to make a i386 and an amd64 packages, both will pull a THIRD package i386, 3 packages to fix a simple usability problem on USC? I think is too much. If there is something in the deb file we can add to avoid this I am more than happy to do so, but releasing 3 packages only for Ubuntu doesn't seem something we want to do. Yes, I totally understand that. Let's see what Steve says. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1263128 Title: Skype is hidden under technical items in USC when installed from deb downloaded from skype.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1263128/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1263128] Re: Skype is hidden under technical items in USC when installed from deb downloaded from skype
Hi Marco, I think you've already stated this, but this is specifically about the skype deb package from the skype website correct? That is, the skype debian package that is in the Ubuntu partner archive [1] seems to behave as expected (see screenshot). Perhaps it'd be best if whoever packaged the version in the canonical partner archive could work with Skype so that we use the same package in both places? [1] http://paste.ubuntu.com/6885532/ ** Attachment added: installing-skype-from-partner-on-trusty.png https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1263128/+attachment/3971337/+files/installing-skype-from-partner-on-trusty.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1263128 Title: Skype is hidden under technical items in USC when installed from deb downloaded from skype To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1263128/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1246624] Re: Reminders from Google are displayed as “This is an event reminder”
This issue is fixed on Ubuntu 13.10, evoluion version 3.10.3-0ubuntu3~saucy1. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1246624 Title: Reminders from Google are displayed as “This is an event reminder” To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1246624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1268250] Re: No reviews displayed (ValueError: time data ... does not match format)
Fixed released and verified. Thanks everyone for all the info, sorry for the disruption to reviews. Before deploy: http://paste.ubuntu.com/6745216/ After deploy: http://paste.ubuntu.com/6749235/ Verified with USC on saucy that searching for skype and viewing details displays the reviews. ** Changed in: rnr-server Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1268250 Title: No reviews displayed (ValueError: time data ... does not match format) To manage notifications about this bug go to: https://bugs.launchpad.net/rnr-server/+bug/1268250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1268250] Re: No reviews displayed (ValueError: time data ... does not match format)
** Changed in: rnr-server Status: New = In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1268250 Title: No reviews displayed (ValueError: time data ... does not match format) To manage notifications about this bug go to: https://bugs.launchpad.net/rnr-server/+bug/1268250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1268250] Re: No reviews displayed (ValueError: time data ... does not match format)
Confirmed - it was a result of the upgrade to Django 1.5, the work for which was done over 6 months ago, but it was only deployed last Friday. Fixing now and will get deployed asap. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1268250 Title: No reviews displayed (ValueError: time data ... does not match format) To manage notifications about this bug go to: https://bugs.launchpad.net/rnr-server/+bug/1268250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1246624] Re: Reminders from Google are displayed as “This is an event reminder”
Confirmed here too. Interesting thing I noticed is that when you click Edit, the event name is in the Summary field. Perhaps Google's Calendar API changed and has become misaligned with what Evolution expects. Would love a fix or workaround! ** Attachment added: Screenshot from 2014-01-12 22:39:07.png https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1246624/+attachment/3947396/+files/Screenshot%20from%202014-01-12%2022%3A39%3A07.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1246624 Title: Reminders from Google are displayed as “This is an event reminder” To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1246624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1213917] Re: kworker thread 99.8 - 100% CPU after 1st suspend - no second suspend
Surprise :/, here are the steps that I took (perhaps it'll give you some information showing my mistake): 1) I downloaded and installed all the debs - note missing linux-tools: https://pastebin.canonical.com/99199/ 2) Tested: $ uname -a Linux michael-X201EP 3.11.0-12-generic #19~lp1213917v1 SMP Wed Oct 16 16:05:23 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Good (suspend/resume without kworker issues), BUT, I didn't get a wifi connection at all (even before suspend):. 3) So I apt-get -f to add linux-tools, and then ensured the lp1213917 versions were all still valid: https://pastebin.canonical.com/99211/ 4) The network issue was still there and seemed to be apparmor related: https://pastebin.canonical.com/99208/ Figuring that the network issue may be related to an apparmor update I was missing or similar, I installed the archive versions of 3.11.0-12 to verify that I'd have the same issue there (which I did - no network at all): https://pastebin.canonical.com/99210/. What I didn't do at that point, but should have in retrospect, was confirmed that suspend/resume still triggered the kworker issue. 5) I did a dist-upgrade which was huge - as I'd stopped updating after a few rounds of the bisect (I can put it on chinstrap if it's useful - note-to-self, starts at 2013-10-17 10:56:46), and sure enough, the network issue is fixed, but to my surprise, so is the kworker issue: $ uname -a Linux michael-X201EP 3.11.0-12-generic #19-Ubuntu SMP Wed Oct 9 16:20:46 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Good. If there's something obvious that I did incorrectly, or it's obvious to you where an update may have fixed the issue, please let me know. Sorry for apparently wasting time here :/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1213917 Title: kworker thread 99.8 - 100% CPU after 1st suspend - no second suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1213917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1213917] Re: kworker thread 99.8 - 100% CPU after 1st suspend - no second suspend
$ uname -a Linux michael-X201EP 3.10.0-031000-generic #201310151549 SMP Tue Oct 15 19:50:32 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Good. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1213917 Title: kworker thread 99.8 - 100% CPU after 1st suspend - no second suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1213917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1213917] Re: kworker thread 99.8 - 100% CPU after 1st suspend - no second suspend
$ uname -a Linux michael-X201EP 3.10.0-031000rc6-generic #201310091534 SMP Wed Oct 9 19:36:30 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Good. $ uname -a Linux michael-X201EP 3.10.0-031000rc6-generic #201310101545 SMP Thu Oct 10 19:47:16 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Also good (I'd half expected this second one - 201310101545 to be bad and that we'd found the issue :/). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1213917 Title: kworker thread 99.8 - 100% CPU after 1st suspend - no second suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1213917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1213917] Re: kworker thread 99.8 - 100% CPU after 1st suspend - no second suspend
$ uname -a Linux michael-X201EP 3.10.0-031000-generic #201310011456 SMP Tue Oct 1 18:58:54 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Also bad. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1213917 Title: kworker thread 99.8 - 100% CPU after 1st suspend - no second suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1213917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1213917] Re: kworker thread 99.8 - 100% CPU after 1st suspend - no second suspend
$ uname -a Linux michael-X201EP 3.10.0-031000-generic #201309181425 SMP Wed Sep 18 18:27:23 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Also bad. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1213917 Title: kworker thread 99.8 - 100% CPU after 1st suspend - no second suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1213917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1213917] Re: kworker thread 99.8 - 100% CPU after 1st suspend - no second suspend
$ uname -a Linux michael-X201EP 3.10.0-031000-generic #201309171602 SMP Tue Sep 17 20:03:44 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Also bad. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1213917 Title: kworker thread 99.8 - 100% CPU after 1st suspend - no second suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1213917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1213917] Re: kworker thread 99.8 - 100% CPU after 1st suspend - no second suspend
Also, just in case it's relevant in confirming the eventual commit, I've already mentioned above that after the first suspend and kworker going to 100%, I can't suspend a second time (I get a complete freeze requiring a hard power-off), but if I instead try a soft power off rather than the second suspend, it will finally power off after a minute of scrolling this message over the console (which I grabbed from syslog): Sep 17 21:39:40 michael-X201EP kernel: [ 100.139891] alx :03:00.0: invalid PHY speed/duplex: 0x Sep 17 21:39:40 michael-X201EP kernel: [ 100.141169] alx :03:00.0: invalid PHY speed/duplex: 0x Sep 17 21:39:40 michael-X201EP kernel: [ 100.142847] alx :03:00.0: invalid PHY speed/duplex: 0x Sep 17 21:39:40 michael-X201EP kernel: [ 100.144159] alx :03:00.0: invalid PHY speed/duplex: 0x Sep 17 21:39:40 michael-X201EP kernel: [ 100.145398] alx :03:00.0: invalid PHY speed/duplex: 0x -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1213917 Title: kworker thread 99.8 - 100% CPU after 1st suspend - no second suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1213917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1213917] Re: kworker thread 99.8 - 100% CPU after 1st suspend - no second suspend
$ uname -a Linux michael-X201EP 3.10.0-031000-generic #201309171218 SMP Tue Sep 17 16:20:31 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Bad. Thanks Joseph -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1213917 Title: kworker thread 99.8 - 100% CPU after 1st suspend - no second suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1213917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1213917] Re: kworker thread 99.8 - 100% CPU after 1st suspend - no second suspend
$ uname -a Linux michael-X201EP 3.10.0-031000rc5-generic #201309121250 SMP Thu Sep 12 16:51:50 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Also good. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1213917 Title: kworker thread 99.8 - 100% CPU after 1st suspend - no second suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1213917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1213917] Re: kworker thread 99.8 - 100% CPU after 1st suspend - no second suspend
$ uname -a Linux michael-X201EP 3.10.0-031000rc6-generic #20130954 SMP Wed Sep 11 15:55:58 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Good - multiple suspend/resume without kworker thread going crazy. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1213917 Title: kworker thread 99.8 - 100% CPU after 1st suspend - no second suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1213917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1213917] Re: kworker thread 99.8 - 100% CPU after 1st suspend - no second suspend
$ uname -a Linux michael-X201EP 3.10.0-031000rc6-generic #201309101033 SMP Tue Sep 10 14:35:30 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Good - multiple suspend/resume without kworker thread going above 5% -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1213917 Title: kworker thread 99.8 - 100% CPU after 1st suspend - no second suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1213917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1213917] Re: kworker thread 99.8 - 100% CPU after 1st suspend - no second suspend
Good - unable to reproduce the issue with: $ uname -a Linux michael-X201EP 3.10.0-031000rc6-generic #201309091524 SMP Mon Sep 9 19:25:40 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux (Note: I was confused at first by the change in package name and re- tested the previous (non-rc6) version). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1213917 Title: kworker thread 99.8 - 100% CPU after 1st suspend - no second suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1213917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1213917] Re: kworker thread 99.8 - 100% CPU after 1st suspend - no second suspend
Thanks Joseph. I hit the issue straight after a suspend with the 3.10.0-031000.201309061430 build. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1213917 Title: kworker thread 99.8 - 100% CPU after 1st suspend - no second suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1213917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1213917] Re: kworker thread 99.8 - 100% CPU after 1st suspend - no second suspend
On Thu, Aug 29, 2013 at 3:07 PM, Joseph Salisbury joseph.salisb...@canonical.com wrote: I built the next test kernel, up to the following commit: 1b375dc30710180c4b88cc59caba6e3481ec5c8b The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1213917 Running $ uname -a Linux michael-X201EP 3.10.0-031000-generic #201308281157 SMP Wed Aug 28 15:59:22 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Also good. Suspended multiple times without kworker issues. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1213917 Title: kworker thread 99.8 - 100% CPU after 1st suspend - no second suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1213917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Blueprint servercloud-s-juju-charmhelper2] Charm Development Tooling
Blueprint changed by Michael Nelson:
Whiteboard changed:
+ Note: schedule updated to 2013-08-29 14:00..15:00 in Server Cloud 2
+
[USER STORIES]
Rodrigo is a new charm writer and needs tools to solve problems other
authors have already solved in their charms.
Dora is a seasoned charmer that has common functions she wants to
publish and share with other authors
Ricardo has written charms before and wants to know what shared
functions are available for charms
Lucy is rewriting several hooks to another language and needs to know
what helpers exist in that language
Bruce wants to review what parameters a helper function accepts and what
the expected output is
[ASSUMPTIONS]
[RISKS]
- It'll be difficult for some functions to create a comperable cross-
language function
[IN SCOPE]
[OUT OF SCOPE]
[USER ACCEPTANCE]
[RELEASE NOTE/BLOG]
[NOTES]
vUDS 1304 Notes:
http://pad.ubuntu.com/uds-1305-servercloud-s-juju-charmhelper2
--- UDS Discussion ---
We've learned a lot since the creation of charm helper. Debian packagers
took 7 iterations before boiling all of debhelper's goodness into a
declarative system. We can learn from them, and get there in our second
iteration.
Discussion:
Charm-helper is not easily discoverable, poorly documented, and not as
awesome as it could be.
dannf likes to write makefiles
sources list
config settings with meaning
want common things to go in a declarative charm
get rid of copied lib files/folder
Maintain charm-helper seperately from juju, calling it at the top of the hook
vs included in juju trunk
What happens during upgrade-charm or if a pakcage gets removed?
Juju can't help with leader election across units of a service, but
charm-helper could)
Work:
- describe how to handle lifecycle changes for packages in
charm-helper/packages (also thinkof: upgrade-charm)
- install packages
- debconf preseeding too
- templating and/or building config files with dotd/concat partials
(erb_template _and_ cheetah_template helpers)?
- remote_files
- deploy from {distro,ppa,upstream?} ?
- Manage config files (dynamic, static, etc)
- Sanitize relation settings (potential risk of SQL Ejection, highjacking,
terror)
- Plugin based for easy extension of charm-helper
- leader election (perhaps somewhere other than charmhelper)
- private files (SSL certs) ... no clue...
- Collaborate on files that no charm owns
---
[notes from cloudsprint 2013-05]
- Wedgewood has “Charm Support” which is used in IS and online services charms
- Python based library
- Covers debian packaging
-
- Command line interface
- Bash support via argparse
- Has hook env for handling various hook specific items (nrpe, relation
data, etc)
- Exec.d allows you to pre-seed stuff in to charm prior to deployment to
perform “pre-install” tasks
- Handles items as exec.d/charm-pre-install in various hooks by invoking
the matching command
- “Rudimentary” persistent storage support
- Charm helpers doesn’t do what they wanted it to. Charm-helpers wasn’t a
known until after using charm support.
- OpenStack has “openstack-charm-helpers” which is used by the OpenStack
charms for deployment
- Configuration/relation abstracting for easier python support
- “Storage” management like charm-support
- Conditional restart of services, mapping dicts to services to manage
restart of services
- Caching of juju environment data, to speed up hook execution
- Local file syncs between peers
- Bi-directional file xfer between peers
- Didn’t use it because: Primitive, moving too fast, and didn’t achieve
anything they needed at the time.
- Current work: lp:~openstack-charmers/openstack-charm-helpers/ha-helpers
Gary’s Ideas:
- Python helpers of charm-helpers
- Three levels of stuff
- Shelltoolbox
- Current charm helpers
- some random lib stuff?
- utils.py branch/release management
- backend.py specify repos that a config wants, packages. Does really cool
python stuff
TIME TO GET DOWN TO BUSINESS
- Salt/chef/puppet for potential dropins to research. Configuration
management tools and how they solve this
- Look at openstack for management of shared libraries
- Python package
- Sub packages and modules
- Merge proposals for charms, make libs not txt?
Marco scratch
machine.py for machine level functionality
--
Charm Development Tooling
https://blueprints.launchpad.net/ubuntu/+spec/servercloud-s-juju-charmhelper2
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1213917] Re: kworker thread 99.8 - 100% CPU after 1st suspend - no second suspend
On Tue, Aug 27, 2013 at 9:29 PM, Joseph Salisbury joseph.salisb...@canonical.com wrote: The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1213917 Can you test that kernel and report back if it has the bug or not. I will build the next test kernel based on your test results. Thanks in advance Wow - thanks Joseph. 3.10.0-031000 does not have the bug. Out of interest (for my own learning), what specific tags are you bisecting on? I tried the following: $ git log --oneline Ubuntu-3.10.0-6.17..Ubuntu-3.11.0-0.1 | wc -l 11198 but assumed I was doing something wrong because of the 11k commits. Ah - whereas you're doing the bisect on the upstream kernel? Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1213917 Title: kworker thread 99.8 - 100% CPU after 1st suspend - no second suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1213917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1214071] Re: [ASUSTeK COMPUTER INC. X201EP] suspend/resume failure
*** This bug is a duplicate of bug 1213917 *** https://bugs.launchpad.net/bugs/1213917 ** This bug has been marked a duplicate of bug 1213917 kworker thread 99.8 - 100% CPU after 1st suspend - no second suspend -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1214071 Title: [ASUSTeK COMPUTER INC. X201EP] suspend/resume failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1214071/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1213917] Re: kworker thread 99.8 - 100% CPU after 1st suspend - no second suspend
** Summary changed: - kworker thread consuming 99.8 - 100% CPU after update + kworker thread 99.8 - 100% CPU after 1st suspend - no second suspend -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1213917 Title: kworker thread 99.8 - 100% CPU after 1st suspend - no second suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1213917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1213917] Re: kworker thread 99.8 - 100% CPU after 1st suspend - no second suspend
@jsalisbury I looked at reporting upstream, and have the email ready, but I think they expect the bisect to be done also. I checked the mainline builds and it seems to be when my machine was updated from 3.10 to 3.11. That is, I can confirm that running v3.10.9-saucy installed [1] I cannot reproduce the bug (suspend works perfectly multiple times without crazy kworker threads), while v3.11-rc1 [2] breaks exactly as per the description. I'm not sure (a) if that makes sense, and (b) how I can bisect between those. I assume I'll need to go further back in the 3.11 branch upstream to where it was branched? Let me know if there are specific instructions. Thanks! [1] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.10.9-saucy/ [2] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc1-saucy/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1213917 Title: kworker thread 99.8 - 100% CPU after 1st suspend - no second suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1213917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1214071] Re: [ASUSTeK COMPUTER INC. X201EP] suspend/resume failure
On Thu, Aug 22, 2013 at 3:21 AM, Christopher M. Penalver christopher.m.penal...@gmail.com wrote: Michael Nelson, the next step would be to bisect from Precise to Quantal, in order to identify the commit that caused this regression. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ? Hi Christopher. Sorry, I don't see why that would be relevant. It worked in Precise I assume because I bought it with Ubuntu pre-installed (with custom drivers? I'm not sure). Anyway, the issue that I experienced in Quantal/Raring was fixed in Saucy - I had working suspend/resume up until this week - and is not the same issue that I started experiencing just this week. So, when I get time, I'll follow the kernel bisection wiki page for the saucy kernel releases and get the specific last known working version. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1214071 Title: [ASUSTeK COMPUTER INC. X201EP] suspend/resume failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1214071/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1214071] Re: [ASUSTeK COMPUTER INC. X201EP] suspend/resume failure
On Tue, Aug 20, 2013 at 1:41 PM, Christopher M. Penalver christopher.m.penal...@gmail.com wrote: Michael Nelson, did this problem not occur in a release prior to Saucy? Yes - I was not able to suspend/resume with Raring at all (it would wake immediately). But after updating to Saucy (and updating the bios, as you suggested), it was working perfectly in Saucy [1]. So I had a few weeks of bliss with perfect suspend/resume, and then this issue (it suspends first time, but then kworker goes to 100% after resume, and subsequent suspends fail). [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1206625/comments/4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1214071 Title: [ASUSTeK COMPUTER INC. X201EP] suspend/resume failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1214071/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1214071] Re: [ASUSTeK COMPUTER INC. X201EP] suspend/resume failure
On Wed, Aug 21, 2013 at 10:03 AM, Christopher M. Penalver christopher.m.penal...@gmail.com wrote: Michael Nelson, did this problem not occur in a release prior to Raring? I bought the machine with Ubuntu installed (12.04 I think) and suspend/resume worked fine. I updated to Quantal and it no longer worked. I updated to Raring and it also didn't work (as per the bug I mentioned above). I updated to Saucy, upgraded the bios, and it worked perfectly for a few weeks, until I updated a few days ago and created this bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1214071 Title: [ASUSTeK COMPUTER INC. X201EP] suspend/resume failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1214071/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1213917] [NEW] kworker thread consuming 99.8 - 100% CPU after update
Public bug reported: After updating today (hadn't updated for a while), my fan won't stop and top is showing: PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 4 root 20 0 000 R 100,2 0,0 36:42.35 kworker/0:0 Let me know if I can provide more details. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-2-generic 3.11.0-2.5 ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5 Uname: Linux 3.11.0-2-generic x86_64 ApportVersion: 2.12-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael2372 F pulseaudio Date: Mon Aug 19 14:39:57 2013 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=1efd421f-ac68-455b-b4d4-8912fa02494d MachineType: ASUSTeK COMPUTER INC. X201EP MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-2-generic.efi.signed root=UUID=05643352-201b-43e8-976a-c1d40d591e80 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-2-generic N/A linux-backports-modules-3.11.0-2-generic N/A linux-firmware1.113 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/04/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X201EP.209 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X201EP dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX201EP.209:bd02/04/2013:svnASUSTeKCOMPUTERINC.:pnX201EP:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX201EP:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X201EP dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1213917 Title: kworker thread consuming 99.8 - 100% CPU after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1213917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1214071] [NEW] [ASUSTeK COMPUTER INC. X201EP] suspend/resume failure
Public bug reported: Suspend was working after upgrading to saucy, but failed after updating today (I hadn't updated for a week or two). Screen goes blank, but fan and disk keep spinning. ProblemType: KernelOops DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-2-generic 3.11.0-2.5 ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5 Uname: Linux 3.11.0-2-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.12-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: michael3214 F pulseaudio /dev/snd/controlC0: michael3214 F pulseaudio Date: Mon Aug 19 17:39:55 2013 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=1efd421f-ac68-455b-b4d4-8912fa02494d InterpreterPath: /usr/bin/python3.3 MachineType: ASUSTeK COMPUTER INC. X201EP MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-2-generic.efi.signed root=UUID=05643352-201b-43e8-976a-c1d40d591e80 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. RelatedPackageVersions: linux-restricted-modules-3.11.0-2-generic N/A linux-backports-modules-3.11.0-2-generic N/A linux-firmware1.113 SourcePackage: linux Title: [ASUSTeK COMPUTER INC. X201EP] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 02/04/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X201EP.209 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X201EP dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX201EP.209:bd02/04/2013:svnASUSTeKCOMPUTERINC.:pnX201EP:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX201EP:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X201EP dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Tags: amd64 apport-kerneloops resume saucy suspend -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1214071 Title: [ASUSTeK COMPUTER INC. X201EP] suspend/resume failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1214071/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1214071] Re: [ASUSTeK COMPUTER INC. X201EP] suspend/resume failure
But works fine after a second reboot. ** Changed in: linux (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1214071 Title: [ASUSTeK COMPUTER INC. X201EP] suspend/resume failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1214071/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1213917] Re: kworker thread consuming 99.8 - 100% CPU after update
On Mon, Aug 19, 2013 at 7:27 PM, Joseph Salisbury joseph.salisb...@canonical.com wrote: Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.11 kernel[0]. Yes - although since rebooting it's not happening. If I can trigger it consistently I'll update and test 3.11. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1213917 Title: kworker thread consuming 99.8 - 100% CPU after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1213917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1214071] Re: [ASUSTeK COMPUTER INC. X201EP] suspend/resume failure
...and fails again the third time. ** Changed in: linux (Ubuntu) Status: Invalid = New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1214071 Title: [ASUSTeK COMPUTER INC. X201EP] suspend/resume failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1214071/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1214071] Re: [ASUSTeK COMPUTER INC. X201EP] suspend/resume failure
I have no way currently of knowing, but just ftr, suspend is failing whenever I try to suspend while kworker thread is near 100% cpu usage (another bug I reported earlier - bug 1213917). Actually, I just tested and suspend/resume works fine the first time, but after the resume bug 1213917 starts happening and the machine no longer suspends either. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1214071 Title: [ASUSTeK COMPUTER INC. X201EP] suspend/resume failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1214071/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1213917] Re: kworker thread consuming 99.8 - 100% CPU after update
OK, I've just tested 3 times, and this issue seems to be triggered by suspend/resume, which works fine the first time, but after the first resume, the kworker CPU consumption starts and the next suspend fails (bug 1214071). I'll update to 3.11 and check if I can reproduce it there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1213917 Title: kworker thread consuming 99.8 - 100% CPU after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1213917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1214071] Re: [ASUSTeK COMPUTER INC. X201EP] suspend/resume failure
Updated to 3.11 (note, see circular dependency for linux-headers - is that normal or am I miss-reading? [1]). It did not fix the problem. [1] http://paste.ubuntu.com/6004055/ ** Tags added: kernel-bug-exists-upstream ** Description changed: Suspend was working after upgrading to saucy, but failed after updating today (I hadn't updated for a week or two). Screen goes blank, but fan and disk keep spinning. + + Steps to reproduce: + 1) Fresh reboot, + 2) Suspend and resume + + ER: everything works as usual. + AR: kworker thread starts using 100% cpu (bug 1213917), and next suspend fails. ProblemType: KernelOops DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-2-generic 3.11.0-2.5 ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5 Uname: Linux 3.11.0-2-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.12-0ubuntu3 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: michael3214 F pulseaudio - /dev/snd/controlC0: michael3214 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC1: michael3214 F pulseaudio + /dev/snd/controlC0: michael3214 F pulseaudio Date: Mon Aug 19 17:39:55 2013 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=1efd421f-ac68-455b-b4d4-8912fa02494d InterpreterPath: /usr/bin/python3.3 MachineType: ASUSTeK COMPUTER INC. X201EP MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: - TERM=linux - PATH=(custom, no user) + TERM=linux + PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-2-generic.efi.signed root=UUID=05643352-201b-43e8-976a-c1d40d591e80 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. RelatedPackageVersions: - linux-restricted-modules-3.11.0-2-generic N/A - linux-backports-modules-3.11.0-2-generic N/A - linux-firmware1.113 + linux-restricted-modules-3.11.0-2-generic N/A + linux-backports-modules-3.11.0-2-generic N/A + linux-firmware1.113 SourcePackage: linux Title: [ASUSTeK COMPUTER INC. X201EP] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: - + dmi.bios.date: 02/04/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X201EP.209 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X201EP dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX201EP.209:bd02/04/2013:svnASUSTeKCOMPUTERINC.:pnX201EP:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX201EP:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X201EP dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1214071 Title: [ASUSTeK COMPUTER INC. X201EP] suspend/resume failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1214071/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1213917] Re: kworker thread consuming 99.8 - 100% CPU after update
** Description changed: After updating today (hadn't updated for a while), my fan won't stop and top is showing: - PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND - 4 root 20 0 000 R 100,2 0,0 36:42.35 kworker/0:0 + PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND + 4 root 20 0 000 R 100,2 0,0 36:42.35 kworker/0:0 - Let me know if I can provide more details. + Edit: seems related to bug 1214071. I can reproduce with: + + 1) Start with a fresh reboot + 2) suspend and resume + + At this point after the successful resume, kworker thread starts + consuming 100% cpu and I can no longer suspend (bug 1214071). ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-2-generic 3.11.0-2.5 ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5 Uname: Linux 3.11.0-2-generic x86_64 ApportVersion: 2.12-0ubuntu3 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: michael2372 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: michael2372 F pulseaudio Date: Mon Aug 19 14:39:57 2013 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=1efd421f-ac68-455b-b4d4-8912fa02494d MachineType: ASUSTeK COMPUTER INC. X201EP MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-2-generic.efi.signed root=UUID=05643352-201b-43e8-976a-c1d40d591e80 ro quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-3.11.0-2-generic N/A - linux-backports-modules-3.11.0-2-generic N/A - linux-firmware1.113 + linux-restricted-modules-3.11.0-2-generic N/A + linux-backports-modules-3.11.0-2-generic N/A + linux-firmware1.113 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/04/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X201EP.209 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X201EP dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX201EP.209:bd02/04/2013:svnASUSTeKCOMPUTERINC.:pnX201EP:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX201EP:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X201EP dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Tags added: kernel-bug-exists-upstream ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1213917 Title: kworker thread consuming 99.8 - 100% CPU after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1213917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1183116] Re: 'juju status' output when no env is non-intuitive
*** This bug is a duplicate of bug 1028053 *** https://bugs.launchpad.net/bugs/1028053 ** This bug has been marked a duplicate of bug 1028053 running juju status on a non bootstrapped environment gives confusing results -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1183116 Title: 'juju status' output when no env is non-intuitive To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1183116/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1183116] Re: 'juju status' output when no env is non-intuitive
*** This bug is a duplicate of bug 1028053 *** https://bugs.launchpad.net/bugs/1028053 ** This bug has been marked a duplicate of bug 1028053 running juju status on a non bootstrapped environment gives confusing results -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1183116 Title: 'juju status' output when no env is non-intuitive To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1183116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1206625] Re: [ASUSTeK COMPUTER INC. X201EP] suspend/resume failure
Thanks Christopher. I updated to the latest bios, and tried again - resumed perfectly. ** Changed in: linux (Ubuntu) Status: Incomplete = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1206625 Title: [ASUSTeK COMPUTER INC. X201EP] suspend/resume failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1206625/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1157435] Re: Unable to enter suspend/hibernation in Ubuntu 13.04 on an Asus X201E a.k.a. F201E
@jsalisbury Sorry - update: After updating the bios to the latest version from Asus, retrying with the v3.10 kernel resumed fine :) Thanks for your help! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1157435 Title: Unable to enter suspend/hibernation in Ubuntu 13.04 on an Asus X201E a.k.a. F201E To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1157435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1206383] [NEW] Error! Bad return status for module build on kernel
Public bug reported: After an upgrade to 13.10, I rebooted to find a bunch of error reports (see screenshot). Hoping they might go away with another update, I tried that - which resulted in the same errors [1] [1] http://paste.ubuntu.com/5927929/ ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.10.0-5-generic 3.10.0-5.15 ProcVersionSignature: Ubuntu 3.10.0-5.15-generic 3.10.2 Uname: Linux 3.10.0-5-generic x86_64 ApportVersion: 2.11-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: michael2231 F pulseaudio michael3657 F pulseaudio /dev/snd/controlC0: michael2231 F pulseaudio michael3657 F pulseaudio Date: Tue Jul 30 08:15:43 2013 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-annan-standard-precise-amd64-20121106-1 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=bb448ef7-de71-4b93-8343-74c1c165c1ad InstallationDate: Installed on 2012-11-09 (262 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20121106-09:07 MachineType: ASUSTeK COMPUTER INC. X201EP MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-5-generic root=UUID=05643352-201b-43e8-976a-c1d40d591e80 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.10.0-5-generic N/A linux-backports-modules-3.10.0-5-generic N/A linux-firmware1.112 SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-07-30 (0 days ago) dmi.bios.date: 11/30/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X201EP.205 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X201EP dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX201EP.205:bd11/30/2012:svnASUSTeKCOMPUTERINC.:pnX201EP:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX201EP:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X201EP dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug saucy ** Attachment added: install-errors-after-reboot.png https://bugs.launchpad.net/bugs/1206383/+attachment/3754079/+files/install-errors-after-reboot.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1206383 Title: Error! Bad return status for module build on kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1206383/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1206625] [NEW] [ASUSTeK COMPUTER INC. X201EP] suspend/resume failure
Public bug reported: This might be considered a dupe of bug 1157435. I upgrade to saucy for other reasons, but saw a chance to check if suspend was working with v3.10 kernal. The machine suspended, but when I tried to resume, the fan span but the screen never changed from a blank one :) [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1157435/comments/19 ProblemType: KernelOops DistroRelease: Ubuntu 13.10 Package: linux-image-3.10.0-6-generic 3.10.0-6.17 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 Uname: Linux 3.10.0-6-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.11-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael1728 F pulseaudio Date: Tue Jul 30 19:59:06 2013 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=1efd421f-ac68-455b-b4d4-8912fa02494d InterpreterPath: /usr/bin/python3.3 MachineType: ASUSTeK COMPUTER INC. X201EP MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-6-generic.efi.signed root=UUID=05643352-201b-43e8-976a-c1d40d591e80 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. RelatedPackageVersions: linux-restricted-modules-3.10.0-6-generic N/A linux-backports-modules-3.10.0-6-generic N/A linux-firmware1.112 SourcePackage: linux Title: [ASUSTeK COMPUTER INC. X201EP] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 11/30/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X201EP.205 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X201EP dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX201EP.205:bd11/30/2012:svnASUSTeKCOMPUTERINC.:pnX201EP:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX201EP:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X201EP dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-kerneloops resume saucy suspend -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1206625 Title: [ASUSTeK COMPUTER INC. X201EP] suspend/resume failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1206625/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1157435] Re: Unable to enter suspend/hibernation in Ubuntu 13.04 on an Asus X201E a.k.a. F201E
@jsalisbury I updated to saucy (for other reasons), and tried suspend with the v3.10 kernal. It suspended, but didn't resume. Details on bug 1206625. Thanks to the team for looking at these! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1157435 Title: Unable to enter suspend/hibernation in Ubuntu 13.04 on an Asus X201E a.k.a. F201E To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1157435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1206640] [NEW] Encrypted home inaccessible after iso upgrade
Public bug reported: Steps to reproduce: 1) Start with an existing ubuntu installation [1] with an encrypted home directory for 'username' 2) Create a bootable USB of 13.10, reboot to installer and choose the upgrade your existing ubuntu installation (ie. keep the home directory) 3) When prompted for a user name/passphrase, enter the same username and passphrase (I assumed it'd either realise it was the same or tell me to choose a different username) 4) After completion/reboot, login to the (only) 'username' account Expected result: * Login works with encrypted home being unencrypted with the (same) passphrase Actual result * Login flicks away from login screen, but then immediately returns without explanation, leaving the user unable to login. After initial panic, it turns out it was pretty simple to rectify. Doing `ls -al` for /home/username (in a rescue console) showed that all the encrypted file data was owned by uid/gid 1001 (the old username I assume). The new 'username' user had uid/gid of 1000. To fix I did the following: 1) Reboot and choose the Ubuntu advanced options grub menu item, then root shell. 2) Ensure / is writable with `mount -o remount,rw /` 3) `usermod --uid 1001 username` 4) `groupmod --gid 1001 username` Reboot and login as normal. I'm assuming there's nothing that needs to change in ecryptfs-utils but I'll add it just in case so Dustin et al can verify. [1] Note: as I'd previously upgraded to 13.10 via apt but experienced issues, I was really overriding the existing 13.10 ubuntu. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 Uname: Linux 3.10.0-6-generic x86_64 ApportVersion: 2.11-0ubuntu1 Architecture: amd64 Date: Tue Jul 30 20:14:41 2013 EcryptfsInUse: Yes InstallCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.10.0-6-generic.efi.signed root=UUID=05643352-201b-43e8-976a-c1d40d591e80 ro quiet splash MarkForUpload: True SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ecryptfs-utils (Ubuntu) Importance: Undecided Status: New ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy ** Also affects: ecryptfs-utils (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1206640 Title: Encrypted home inaccessible after iso upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1206640/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1192666] [NEW] salt-call returns incorrect exit status (ie. succeeds and returns 2)
Public bug reported: Originally reported at http://bugs.debian.org/cgi- bin/bugreport.cgi?bug=712819 I was using salt-minion from the salt PPA which is version 0.15.3, and everything was fine. I then tried instead to use the 0.15.1 version from the debian archive (well, a copy of the debian package) - it worked but the command I was using (salt-call) returns an incorrect exit status. http://paste.ubuntu.com/5781258/ This bug is known and fixed upstream [1] in 0.15.3, the patch is a 3 liner [2] [1] https://github.com/saltstack/salt/issues/4904 [2] See the salt/cli/caller.py patch at https://github.com/saltstack/salt/commit/4b5c3e61062f0b9ed047afe51ea783bd6486155a#L1L174 ** Affects: salt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1192666 Title: salt-call returns incorrect exit status (ie. succeeds and returns 2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/salt/+bug/1192666/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1157435] Re: Unable to enter suspend/hibernation in Ubuntu 13.04 on an Asus X201E [F201E]
I'm tagging this with regression-release, but the only last-working version I can give is the precise version. Info that I have: * suspend was working fine with Precise (the OS the machine was purchased with) and there are no updates at http://asus.archive.canonical.com/updates/dists/precise-annan/public/binary-amd64/, * suspend would work mostly with Quantal (seemed to stop suspending after 4-5 suspends - it was for this reason I tried upgrading to raring) * suspend doesn't work at all (for me) in raring as per above. This is on a machine purchased with Precise pre-installed. ** Tags added: regression-release ** Description changed: - Ubuntu 13.04 works great on my Asus X201E [F201E in Germany], the only - thing that doesn't work is suspend, as it bounces directly back into the - OS. Strangely enough, the first suspend-operation works, but thereafter, - it waked up immediately. Activating hibernation via terminal leads to - the same phenomenon. + Ubuntu 13.04 works great on my Asus X201E [F201E in Germany, pre- + installed with Precise], the only thing that doesn't work is suspend, as + it bounces directly back into the OS. Strangely enough, the first + suspend-operation works, but thereafter, it waked up immediately. + Activating hibernation via terminal leads to the same phenomenon. pm-suspend.log in /var/log tells me: s2ram_do: Input/output error KMS graphics driver is in use, skipping quirks. Tue Mar 19 21:26:01 CET 2013: Awake. Tue Mar 19 21:26:01 CET 2013: Running hooks for resume Tue Mar 19 21:26:01 CET 2013: Finished. I also deleted everything via terminal in /usr/lib/pm-utils/sleep.d/ and /etc/pm/sleep.d/ without any success [nor effect]. It would be great if this bug could be fixed before 13.04 comes officially out, as the Asus X201E is preinstalled with Ubuntu 12.04 LTS and I guess a lot of users will want to upgrade their OS. Best, Alex -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1157435 Title: Unable to enter suspend/hibernation in Ubuntu 13.04 on an Asus X201E [F201E] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1157435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1157435] Re: Unable to enter suspend/hibernation in Ubuntu 13.04 on an Asus X201E [F201E]
FWIW, I had also seen this behaviour on 12.10 on my Asus F201E, but not as often (usually after a day or two it would stop suspending). I upgraded to 13.04 and so far it's happened every time (only just rebooted into 13.04), as Alex described. My log is a bit different, attaching in full. ** Attachment added: pm-suspend.log https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1157435/+attachment/3591514/+files/pm-suspend.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1157435 Title: Unable to enter suspend/hibernation in Ubuntu 13.04 on an Asus X201E [F201E] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1157435/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1052721] Re: Some packages say not available for your current Ubuntu version when viewed from purchase list
Another point (thanks Anthony): although the sca fix above ensures that buyers will no longer see a Not available for your version for multiarch apps, when they click on the Install button: * for i386 users, everything should work fine * for amd64 users, they will currently see a Not found response in USC, as the apt url provided does not include the :i386 suffix (and that isn't a problem sca can solve - as we can't know definitively the arch of the user... we do know this for chromium users, and may be able to help them). USC would ultimately need to recognise an apt://foopackage as a possible multi-arch when searching. ** Also affects: software-center (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1052721 Title: Some packages say not available for your current Ubuntu version when viewed from purchase list To manage notifications about this bug go to: https://bugs.launchpad.net/software-center-agent/+bug/1052721/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1052721] Re: Some packages say not available for your current Ubuntu version when viewed from purchase list
On Wed, Sep 19, 2012 at 2:40 PM, James Westby jw+deb...@jameswestby.net wrote: On Wed, 19 Sep 2012 08:31:45 -, Michael Nelson 1052...@bugs.launchpad.net wrote: We also discussed on irc [1] whether sca could potentially provide a work-around for USC's Reinstall previous purchases by appending :i386 to all multi-arch apps, but in the end it seems this isn't possible, because at that point (the /subscriptions/ api handler), sca does not currently know the client distroseries (and whether it will understand :i386 suffixes) [2]. Will an old distroseries that doesn't understand that syntax be able to install that package if it can find it? It will have it's own native package which I assume would install :) I'm not sure I've understood the question, but if you look at the available precise apps for any arch [1], the package 'irukandji' is multiarch for precise and oneiric, but has i386 and amd64 builds for natty and maverick. Does that make more sense? [1] http://software- center.ubuntu.com/api/2.0/applications/en/ubuntu/precise/any/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1052721 Title: Some packages say not available for your current Ubuntu version when viewed from purchase list To manage notifications about this bug go to: https://bugs.launchpad.net/software-center-agent/+bug/1052721/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 920542] Re: Exhibits: One image isn't enough for nice exhibits
** Also affects: software-center (Ubuntu) Importance: Undecided Status: New ** Changed in: software-center-agent Assignee: Danny Tamez (zematynnad) = Łukasz Czyżykowski (lukasz-czyzykowski) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/920542 Title: Exhibits: One image isn't enough for nice exhibits To manage notifications about this bug go to: https://bugs.launchpad.net/software-center-agent/+bug/920542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1022074] Re: Blank page when attempting to purchase software
Thanks Alexander, I'll update the bug and see if we can get some of the pay.ubuntu.com folk to investigate. ** Project changed: software-center-agent = canonical-payment-service -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1022074 Title: Blank page when attempting to purchase software To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-payment-service/+bug/1022074/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1022074] Re: Blank page when attempting to purchase software
@achuni: To save a bit of back-n-forth-ing, I took a look at the pay logs and see this: 2012-08-07 19:42:26,642 INFO NEW payment created with id '36682a0f9f5d9e03da0a651bf832d4fb' for user with openid '' as requested by consumer 'SCA'. 2012-08-07 19:42:26,870 WARNING Payment '36682a0f9f5d9e03da0a651bf832d4fb' has no openid associated. which results in a 404 on pay, but it looks like the openid could be being sent as '' from SCA. I need someone with access to our production data to confirm - but I'm guessing the value of subscription.open_id is not what we expect for Alexander's subscriptions above (ie. it would be returned as '' if there are no associated useropenid's for his user). ** Project changed: canonical-payment-service = software-center-agent -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1022074 Title: Blank page when attempting to purchase software To manage notifications about this bug go to: https://bugs.launchpad.net/software-center-agent/+bug/1022074/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1022074] Re: Blank page when attempting to purchase software
@mvo: I can't see any 404s on softwarecenteragent requesting volleybrawl :/. Here are the ones I do see: https://pastebin.canonical.com/71628/ Nick's image (thanks Nick!) is showing that, at least when he got that error, he'd already been redirected through to pay.ubuntu.com (but I think the error shown is due to a pay issue bug 1032739 (private - sorry)). Nick or Alexander, if you open the URL mvo provided above in your browser, after logging in, when you've been redirected to the blank page, can you copy and paste the browsers url here? Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1022074 Title: Blank page when attempting to purchase software To manage notifications about this bug go to: https://bugs.launchpad.net/software-center-agent/+bug/1022074/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1022074] Re: Blank page when attempting to purchase software
In fact, the blank screen *may* have been due to the same pay bug (bug 1033140). It may be best to check with ricardo if that is now resolved (as the comment implies it would have been fixed yesterday). Either way, if Nick or Alexander report back with either the URL displaying the blank page, or the info that it no longer happens, we can move forward :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1022074 Title: Blank page when attempting to purchase software To manage notifications about this bug go to: https://bugs.launchpad.net/software-center-agent/+bug/1022074/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1020205] Re: add support for a click_url in a exhibit banner
** Changed in: software-center-agent Assignee: (unassigned) = Michael Nelson (michael.nelson) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1020205 Title: add support for a click_url in a exhibit banner To manage notifications about this bug go to: https://bugs.launchpad.net/software-center-agent/+bug/1020205/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 872701] Re: Keyboard layout doesn't change
Confirming that upgrading to libgtk-3-0 from proposed also allows me to unlock using the selected layout. Thank-you to all involved! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/872701 Title: Keyboard layout doesn't change To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/872701/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1011504] [NEW] Rhythm box freezes consistently
Public bug reported: I seem to get about 1.5 songs out of Rhythm box until it freezes. I haven't worked out the cause, only that it's consistent, and isn't related to which music I play (although all my music is ogg). I didn't watch to see if the following message appeared right when it freezes, but nonetheless, the terminal shows: ~$ rhythmbox (rhythmbox:18803): GStreamer-WARNING **: Trying to join task 0x7f6a0402a0c0 from its thread would deadlock. You cannot change the state of an element from its streaming thread. Use g_idle_add() or post a GstMessage on the bus to schedule the state change from the main thread. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: rhythmbox 2.96-0ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16 Uname: Linux 3.2.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 CheckboxSubmission: f26299558349e6bfa9a64225e1770925 CheckboxSystem: 669b662da410063cc918e0f60cf6cddf Date: Mon Jun 11 10:51:55 2012 InstallationMedia: Ubuntu 10.04 Lucid Lynx - Alpha amd64 (20100224.1) ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rhythmbox UpgradeStatus: Upgraded to precise on 2012-01-16 (146 days ago) ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1011504 Title: Rhythm box freezes consistently To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1011504/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1011504] Re: Rhythm box freezes consistently
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1011504 Title: Rhythm box freezes consistently To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1011504/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1008289] Re: Failed to download repository information for purchased application
** Changed in: software-center-agent Assignee: (unassigned) = Michael Nelson (michael.nelson) ** Changed in: software-center-agent Status: Confirmed = In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1008289 Title: Failed to download repository information for purchased application To manage notifications about this bug go to: https://bugs.launchpad.net/software-center-agent/+bug/1008289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 901336] Re: Software center doesn't work after LP accounts merge
Another possible (?) solution mentioned by lukasz, was if Launchpad keeps a record of merged accounts (and previous usernames), it could include the auth details in the htpasswd for the old username as well. This would mean no changes needed for the client at all. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/901336 Title: Software center doesn't work after LP accounts merge To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-identity-provider/+bug/901336/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 901336] Re: Software center doesn't work after LP accounts merge
@ricardo: that would be ideal if sca could subscribe to such events. In the mean-time, sca already (attempts to [1]) update to the current LP username the next time the user initiates a purchase (which will update the exported deblines for all purchases). We could use this same call (check_or_create_lp_user) to verify / update the username when USC requests the list of subscriptions for a user (ie. so the exported deb- lines include the correct username). This would mean that users could simply Reinstall previous purchases to sort the issue out? [2] [1] We currently have a related issue that the new username may already be present in sca and we blindly try to save a second user record with the same username, rather than (possibly) moving the subscription/openid over to the existing django user or vice-versa. [2] Although I assume USC would need to handle remove the old entries if they are found while trying to add the new ones? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/901336 Title: Software center doesn't work after LP accounts merge To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-identity-provider/+bug/901336/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 709125] Re: User agent doesn't include Ubuntu in it so apt.ubuntu.com doesn't work
@chris: I've just checked for the change you landed with r255, and see it must have been removed at some point. Is there a way we can have this included for apps.ubuntu.com and software-center.ubuntu.com (or *.ubuntu.com so we can test the functionality on our staging servers too)? Currently we can only provide useful info to Chromium users. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/709125 Title: User agent doesn't include Ubuntu in it so apt.ubuntu.com doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/apturlredirector/+bug/709125/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 912509] Re: Lots of requests to the checkout complete URL
On Fri, May 18, 2012 at 4:35 AM, Natalia Bidart 912...@bugs.launchpad.net wrote: Re opening in SCA since while brainstorming about this with my office roommate I realized the template that checkout_complete rendes does reload the page every a given amount of seconds. Will propose a branch tomorrow for sca. Excellent - as james mentioned on irc, once the title-change event has been delivered, there's no reason to keep the refresh there (assuming USC is guaranteed to receive the first title-change event rendered by the server). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/912509 Title: Lots of requests to the checkout complete URL To manage notifications about this bug go to: https://bugs.launchpad.net/software-center-agent/+bug/912509/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 912509] Re: Lots of requests to the checkout complete URL
Hi Natalia - yes, the browser refresh was one of those temporary options that stuck. The plan was to have the client handle the UI straight after the purchase was initiated - bug 622732 - initially with the client polling sca via an API, but ultimately removing the need to poll at all (plenty of ways to do that these days). If you've got other ideas, please add them to the bug. Thanks for the fix here! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/912509 Title: Lots of requests to the checkout complete URL To manage notifications about this bug go to: https://bugs.launchpad.net/software-center-agent/+bug/912509/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 997402] Re: Buying software is impossible
Hi Jimmy and Gary. This seems to be a repeat of an issue that we also experienced on Monday - in short, our database server is getting stuck for period of time, in which the purchases can't be processed. The bug for the original issue on Monday is bug 996686 - but I'll not yet mark this as a duplicate as the other bug is private and there may be more info to collect and share here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/997402 Title: Buying software is impossible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/997402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 933300] Re: nm-applet needs restart after resume
@mathieu-tl - Since my comment above (comment 2 on 2012-02-23) I have not seen the original issue that I reported. There have been a few times where I thought my machine wasn't going to connect after a resume, but it always began animating before I'd been able to pkill nm-applet. Is there info you can request hazmat or others to attach when they see it again (related to the initial nm-applet instance)? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/933300 Title: nm-applet needs restart after resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/933300/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 993233] Re: Purchased software not installed
Hi Fabio! Is it possible that you purchased Irukandji when you were
running Ubuntu Natty or Maverick. It seems it was available for amd64 on
those series, but is only available for i386 for Oneiric and Precise
[1].
There's a comment on the changelog that mentions this decision [2],
which was an unfortunate one for people like yourself who had purchased
it to run on amd64. I'll notify both the person in charge of the
packaging, to see if it really is not possible to publish this for amd64
as well, as well as a support person. Thank you for taking the time to
report the details of the bug!
[1] From
http://software-center.ubuntu.com/api/2.0/applications/en/ubuntu/precise/i386/
(which is what Software Center uses):
{{{
series: {
precise: [
i386
],
maverick: [
i386,
amd64
],
natty: [
i386,
amd64
],
oneiric: [
i386
]
},
}}}
[2] * Building for i386 only due to multiarch changes
-- Brian Thomason brian.thoma...@canonical.com Fri, 23 Sep 2011 21:49:40
+
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/993233
Title:
Purchased software not installed
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/993233/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 872701] Re: Keyboard layout doesn't change
Apparently this has been fixed upstream in gtkplug: https://bugzilla.gnome.org/show_bug.cgi?id=675167 ** Bug watch added: GNOME Bug Tracker #675167 https://bugzilla.gnome.org/show_bug.cgi?id=675167 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/872701 Title: Keyboard layout doesn't change To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/872701/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 993233] Re: Purchased software not installed
On Thu, May 3, 2012 at 11:00 AM, Fabio Marconi fabiomarc...@ubuntu.com wrote: Hello Michael I've purchased Irukandji yesterday and it was regularry proposed as a normal software in software center. I've never purchased this software before, and is the first time that I see it. Wow, so somehow your Ubuntu Software Center on amd64 presented an application for purchase which is only available for i386. Only last night the title was updated adding that the software isn't available for this version of Ubuntu, but was too late. Oh, that's possible, but I would be surprised if it's the case - but JohnP will know for sure. Either way, we'll find out why you were presented with an uninstallable app for purchase. Thanks again Fabio. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/993233 Title: Purchased software not installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/993233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 986021] Re: Cannot make purchase in Ubuntu Software Center
I haven't yet found the above oops (rangpur and satsuma only have pay oopses until 2012-04-19 currently), but the behaviour sounds as if SCA initiate the payment via the pay API, then redirected to the payments checkout URL (ie. HttpResponseRedirect(payment.checkout_url) ), but pay didn't recognise the payment id and 404'd. I've pinged some pay folk, so once we have the oops we'll be able to stop guessing :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/986021 Title: Cannot make purchase in Ubuntu Software Center To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/986021/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 980241] Re: Purchasing software took almost 5 minutes
So this is the delay from:
2012-04-12 16:36:11,789 - softwarecenter.backend - INFO -
add_repo_add_key_and_install_app()
'private-ppa.launchpad.net/commercial-ppa-uploaders/bobby/ubuntu precise main'
'1024R/75254D99' 'Bobby,bobby'
... (apparently 4 failed attempts before)...
2012-04-12 16:40:07,105 - softwarecenter.backend - INFO -
_on_reload_for_add_repo_and_install_app_finished() AptTransaction object at
0x587b370 (aptdaemon+client+AptTransaction at 0x66b5c80) True Bobby,bobby
during which time USC is unable to see /var/lib/apt/lists/private-
ppa.launchpad.net_commercial-ppa-
uploaders_bobby_ubuntu_dists_precise_Release.gpg
This would indeed indicate that USC wasn't able to access the private
PPA until then, but is strange as the only LP script that I can imagine
causing this delay is the one updating the ht-access for the private PPA
- that's currently scheduled to happen every minute (cronscripts
/generate-ppa-htaccess.py has a crontab with * * * * *).
Indeed, checking the logs for generate-ppa-htaccess.py and assuming that
the above logs are all -0300 (Natalia's tz) shows it happily chugging
along nearly once-per minute until
{{{
2012-04-12 19:36:33 INFOLogging INFO and higher messages to
/srv/launchpad.net/production-logs/lp_publish/generate-ppa-htaccess.log
2012-04-12 19:36:33 INFOCreating lockfile:
/var/lock/launchpad-generate-ppa-htaccess.lock
2012-04-12 19:37:14 INFOLogging INFO and higher messages to
/srv/launchpad.net/production-logs/lp_publish/generate-ppa-htaccess.log
2012-04-12 19:37:14 INFOCreating lockfile:
/var/lock/launchpad-generate-ppa-htaccess.lock
2012-04-12 19:37:35 INFOStarting the PPA .htaccess generation
2012-04-12 19:38:10 INFOLogging INFO and higher messages to
/srv/launchpad.net/production-logs/lp_publish/generate-ppa-htaccess.log
2012-04-12 19:38:10 INFOCreating lockfile:
/var/lock/launchpad-generate-ppa-htaccess.lock
2012-04-12 19:39:10 INFOLogging INFO and higher messages to
/srv/launchpad.net/production-logs/lp_publish/generate-ppa-htaccess.log
2012-04-12 19:39:10 INFOCreating lockfile:
/var/lock/launchpad-generate-ppa-htaccess.lock
2012-04-12 19:39:50 INFOCommitting transaction...
2012-04-12 19:39:56 INFOFinished PPA .htaccess generation
}}}
(more context for log https://pastebin.canonical.com/64326/)
which seems to indicate that:
1) Started at 19:36:33 but didn't even start PPA.htaccess generation (perhaps
lockfile existed? Need to check the lp code)
2) Restarted at 19:37:14 but didn't commit the transaction or finish the
htaccess generation.
3) Restarted at 19:38:10 but didn't even start PPA .htaccess generation, before
finally
4) Restarted at 19:39:10 and finished 46 seconds later.
I've put that in an LP bug 982938 so we can track it (we may have to
investigate/fix ourselves, just let me know).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/980241
Title:
Purchasing software took almost 5 minutes
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/980241/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 979696] Re: apt-get check apparently consuming CPU leaving instance unusable
This happened again today, and it seems it's not related to apt-cache itself (sorry). It runs slowly and consumes heaps of CPU, but so does everything else. This time I even saw vim take over 60% cpu while starting, as well as multiple postgres processes etc., so it seems related to the system itself - just wish I knew how to find out what. If there's anything I can do to give more info, pls let me know. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/979696 Title: apt-get check apparently consuming CPU leaving instance unusable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/979696/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
