[Bug 2068860] [NEW] exception: Popper__namespace.createPopper is not a function

2024-06-09 Thread H Buus 
Public bug reported:

Source Package: phpmyadmin (4:5.2.1+dfsg-3) [universe]

# lsb_release -rd
No LSB modules are available.
Description:Ubuntu 24.04 LTS
Release:24.04

# apt-cache policy phpmyadmin
phpmyadmin:
  Installed: 4:5.2.1+dfsg-3
  Candidate: 4:5.2.1+dfsg-3
  Version table:
 *** 4:5.2.1+dfsg-3 500
500 http://us.archive.ubuntu.com/ubuntu noble/universe amd64 Packages
500 http://us.archive.ubuntu.com/ubuntu noble/universe i386 Packages
100 /var/lib/dpkg/status

What I expected to happen: Click on Structure tab for a table, then hover over 
More for a given column in the table. I expected to get a popup menu with 
choices like:
Primary
Unique
Index
Spatial
Fulltext
Distinct values

What happens is nothing. If I click on More, nothing still seems to
happen, but when I scroll to the bottom of the page, I see a line with a
pink background saying: "A fatal JavaScript error has occurred. Would
you like to send an error report?" followed by a button saying "Show
report details". When I click on that button, I get an error report
containing the text in the attached file
"phpmyadmin.createPopper.error.txt"

Someone else has also reported this on github for phpmyadmin here:
https://github.com/phpmyadmin/phpmyadmin/issues/19166

It looks like it's a bug in bootstrap 5.3.1 which is provided by phpmyadmin:
Bootstrap v5.3.1 (https://getbootstrap.com/

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

** Attachment added: "Error report from phpmyadmin"
   
https://bugs.launchpad.net/bugs/2068860/+attachment/5787807/+files/phpmyadmin.createPopper.error.txt

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

Title:
  exception: Popper__namespace.createPopper is not a function

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


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

[Bug 1876157] Re: Memtest86+ in Ubuntu 20.04 doesn't work, switch to Coreboot branch or package new release v5.31b is available since 12/04/2020

2021-07-14 Thread H Buus 
I wasted a lot of time and angst on this issue. The 20.04 version works
as long as I only test with 4GB installed, it hangs if there is more
memory. Same memory works fine with PassMark's memtest86 v4.3.7 and with
memtest86+ v5.31b. I haven't tried v5.01 directly downloaded from
memtest86.org.

I can't help but wonder how may people think they've got bad memory
because this tool is broken.

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

Title:
  Memtest86+ in Ubuntu 20.04 doesn't work, switch to Coreboot branch or
  package new release v5.31b is available since 12/04/2020

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


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

[Bug 1790688] Re: x86/pti: 32-bit x86 systems support already available.

2019-06-17 Thread H Buus 
PTI makes my 2 32 bit laptops unstable. I have lubuntu 18.04 installed on both 
and they both started having trouble after the linux-image upgrade from 
4.15.0-46/47 to 4.15.0-50/51. They either fail to boot without locking up or 
fail to shut down cleanly. I rarely get any useful logs or messages on the 
screen, although if the machines do boot without locking up, I have seen 
messages like this when they fail to shut down:
watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd:1]

I did manage to recover some BUGs with call traces from kern.log when I tried 
the ubuntu mainline kernel build, 4.19.31-041931-generic #201903231635. Here 
are typical BUG stmts:
Apr 22 10:16:04 mikedell kernel: [   43.339955] BUG: unable to handle kernel 
NULL pointer dereference at 0008
Apr 22 10:16:04 mikedell kernel: [   43.484957] BUG: unable to handle kernel 
paging request at eef4817c
Unfortunately, I think it's the only kernel that's given me this much info. I'd 
be happy to share the full call traces I have captured if anyone is interested.

Neither laptop has a serial port and I'm not a kernel developer, so I don't 
feel I've got the means to properly diagnose the problem. Howver, I have since 
found that when I compile the kernel from:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/
and change only one config parameter, CONFIG_PAGE_TABLE_ISOLATION, the kernel 
with the param enabled is unstable, but the kernel with the param disabled is 
stable. I have found this to be the case with kernels 4.19.50 and 5.1.9.

The two laptops are:
Dell Inspiron B130 with an Intel Celeron M 1.50GHz (family: 0x6, model: 0xd, 
stepping: 0x8)
IBM Thinkpad R51 1836HAU with Intel Pentium M processor 725 (1.6 GHz)

The Thinkpad's Pentium M 725 is a Dothan processor that supports PAE,
but lies about it, so it requires the forcepae kernel parameter. The
Dell's Celeron M does not requre the forcepae parameter.

I've been trying to figure out if this is a known problem. THere's so
little love for 32 bt hardware these days. Then I saw this bug report
and thought it might be a good place to start.

Should I post this info on the linux-kernel mailing list?

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

Title:
  x86/pti: 32-bit x86 systems support already available.

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

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

[Bug 1616569] Re: Mythbuntu Installer crashes while collecting username info

2016-08-24 Thread H Buus 
It was definitely a bad usb stick. Sorry for the noise.

** Changed in: ubiquity (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/1616569

Title:
  Mythbuntu Installer crashes while collecting username info

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

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

[Bug 1616569] Re: Mythbuntu Installer crashes while collecting username info

2016-08-24 Thread H Buus 
OK this may be a bad stick. I got the following error when doing a checksum:
./casper/filesystem.squashfs: FAILED
I used the same stick to install mythbuntu to another machine at the end of 
July. Seems strange it went bad in a month's time. I will try another stick and 
report back.

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

Title:
  Mythbuntu Installer crashes while collecting username info

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

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

[Bug 1616569] [NEW] Mythbuntu Installer crashes while collecting username info

2016-08-24 Thread H Buus 
Public bug reported:

While installing from USB stick, mythbuntu installer crashes while
collecting primary user login and machine name details.

FWIW, I think was able to successfully install mythbuntu on a previous
iteration. But the boot loader was written to the wrong disk. So I tried
to reinstall to get the boot loader properly installed.  This is the
third reboot using a port on the motherboard instead of a front usb
port, in case that matters. I will now double check the check sums on
the usb stick and report back.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubiquity 2.21.63.2
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CasperVersion: 1.376
Date: Wed Aug 24 13:38:39 2016
InstallCmdLine: file=/cdrom/preseed/mythbuntu.seed boot=casper 
initrd=/casper/initrd.lz ---
LiveMediaBuild: Mythbuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug mythbuntu ubiquity-2.21.63.2 xenial

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

Title:
  Mythbuntu Installer crashes while collecting username info

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

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

[Bug 1311908] Re: Installer on mythbuntu is too wide and cannot be resized

2016-08-01 Thread H Buus 
Typos in previous comment:
change 1800p to 1080p
change 1980x1080 1920x1080

Why can I edit a 4 year old description but not a comment I created a
minute ago?

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

Title:
  Installer on mythbuntu is too wide and cannot be resized

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

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

[Bug 1311908] Re: Installer on mythbuntu is too wide and cannot be resized

2016-08-01 Thread H Buus 
This is still a problem with mythbuntu 16.04.1. It seems to be related
to display size.

On one computer connected to a 720p HDTV, with native resolution
1280x720, the installer window was as wide as the display and the sizes
were cut off due to overscan. This computer has an nVidia ION GPU with
Intel Atom CPU.

However, on another computer connected to a 1800p HDTV, with native
resolution 1980x1080, the installer window was less than 1000 pixels
wide. This computer has an Intel HD 2500 IGP with Intel core i3-3220.

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

Title:
  Installer on mythbuntu is too wide and cannot be resized

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

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

[Bug 1603230] Re: acpi regression first bad commit 02b771b64b73226052d6e731a0987db3b47281e9

2016-07-23 Thread H Buus 
Here's link to upstream bug report, including a fix that works for me:
https://bugzilla.kernel.org/show_bug.cgi?id=135691

** Bug watch added: Linux Kernel Bug Tracker #135691
   http://bugzilla.kernel.org/show_bug.cgi?id=135691

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

Title:
  acpi regression first bad commit
  02b771b64b73226052d6e731a0987db3b47281e9

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

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

[Bug 1603230] Re: acpi regression first bad commit 02b771b64b73226052d6e731a0987db3b47281e9

2016-07-17 Thread H Buus 
Reported to upstream here:
http://www.spinics.net/lists/linux-acpi/msg67711.html

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

Title:
  acpi regression first bad commit
  02b771b64b73226052d6e731a0987db3b47281e9

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

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

[Bug 1603230] Re: acpi regression first bad commit 02b771b64b73226052d6e731a0987db3b47281e9

2016-07-16 Thread H Buus 
I tested v4.7-rc7, specifically this deb:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7-rc7/linux-image-4.7.0-040700rc7-generic_4.7.0-040700rc7.201607110032_amd64.deb

It does not fix the problem, so I will be adding the kernel-bug-exists-upstream 
tags as you requested. The ACPI error messages have changed to reflect a newer 
version:
ACPI Error: Method reached maximum reentrancy limit (255) 
(20160422/dsmethod-340)

FWIW, I haven't found it necessary to install linux-header debs since
the generic kernels support all the hardware on this machine and I don't
need to compile any third party modules.

I have also found that if the machine is idle, there's a pause in the
"ACPI Error" messages. I think it depends on how much writing to disk is
going on, but that's just a gut feeling. I'm not quite sure how to
verify that assumption, or if it would help diagnose the problem.

** Tags added: kernel-bug-exists-upstream kernel-bug-exists-
upstream-4.7-rc7

** 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/1603230

Title:
  acpi regression first bad commit
  02b771b64b73226052d6e731a0987db3b47281e9

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

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

[Bug 1603230] Re: acpi regression first bad commit 02b771b64b73226052d6e731a0987db3b47281e9

2016-07-14 Thread H Buus 
The attachment, kernels.txt, are notes I took while manually bisecting ubuntu 
kernels listed here:
https://launchpad.net/ubuntu/xenial/+source/linux
and mainline kernels from here:
http://kernel.ubuntu.com/~kernel-ppa/mainline/

The attachment, bisect.txt, is an annotated "git bisect log" associating
commits from the linux-stable tree with the deb packages I built,
installed, and tested.

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

Title:
  acpi regression first bad commit
  02b771b64b73226052d6e731a0987db3b47281e9

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

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

[Bug 1603230] Re: acpi regression first bad commit 02b771b64b73226052d6e731a0987db3b47281e9

2016-07-14 Thread H Buus 
** Attachment added: "kernels.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1603230/+attachment/4701218/+files/kernels.txt

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

Title:
  acpi regression first bad commit
  02b771b64b73226052d6e731a0987db3b47281e9

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

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

[Bug 1603230] Re: acpi regression first bad commit 02b771b64b73226052d6e731a0987db3b47281e9

2016-07-14 Thread H Buus 
** Attachment added: "bisect.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1603230/+attachment/4701219/+files/bisect.txt

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

Title:
  acpi regression first bad commit
  02b771b64b73226052d6e731a0987db3b47281e9

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

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

[Bug 1603230] Re: acpi regression first bad commit 02b771b64b73226052d6e731a0987db3b47281e9

2016-07-14 Thread H Buus 
** Tags removed: acpi
** Tags added: kernel-acpi

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

Title:
  acpi regression first bad commit
  02b771b64b73226052d6e731a0987db3b47281e9

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

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

[Bug 1603230] Re: acpi regression first bad commit 02b771b64b73226052d6e731a0987db3b47281e9

2016-07-14 Thread H Buus 
** Description changed:

  I found what I believe is a regression on my Gateway ne570 laptop. It was 
running mythbuntu 14.04 LTS and ubuntu 15.04 releases quite well. But when I 
installed ubuntu 16.04 LTS, I found dmesg and kern.log were filling with 
messages like this:
  Jul 10 17:01:10 buus-ne570 kernel: [   57.741630] ACPI Error: Method reached 
maximum reentrancy limit (255) (20150818/dsmethod-341)
  Jul 10 17:01:10 buus-ne570 kernel: [   57.803775] ACPI Error: Method reached 
maximum reentrancy limit (255) (20150818/dsmethod-341)
  Jul 10 17:01:10 buus-ne570 kernel: [   57.866294] ACPI Error: Method reached 
maximum reentrancy limit (255) (20150818/dsmethod-341)
  Jul 10 17:01:10 buus-ne570 kernel: [   57.928403] ACPI Error: Method reached 
maximum reentrancy limit (255) (20150818/dsmethod-341)
  
  These messages would be repeated several times a second, and then pause
  for several seconds, then start again. I believe they are the cause of
  more sluggish behavior than with the older *Buntu releases.
  
  I followed the instructions here:
  https://wiki.ubuntu.com/Kernel/KernelBisection
- which lead me to doing "git bisect" on the linux-stable tree. The result lead 
me to this commit:
+ which lead me to doing "git bisect" on the linux-stable kernel. The result 
lead me to this commit:
  
  # first bad commit: [02b771b64b73226052d6e731a0987db3b47281e9] ACPI /
  EC: Fix an issue caused by the serialized _Qxx evaluations
  
  commit 02b771b64b73226052d6e731a0987db3b47281e9
  Author: Lv Zheng 
  Date:   Wed Aug 12 11:12:02 2015 +0800
  
  ACPI / EC: Fix an issue caused by the serialized _Qxx evaluations
  
  It is proven that Windows evaluates _Qxx handlers in a parallel way. This
  patch follows this fact, splits _Qxx evaluations from the NOTIFY queue to
  form a separate queue, so that _Qxx evaluations can be queued up on
  different CPUs rather than being queued up on a CPU0 bound queue.
  Event handling related callbacks are also renamed and sorted in this 
patch.
  
  Link: https://bugzilla.kernel.org/show_bug.cgi?id=94411
  Reported-and-tested-by: Gabriele Mazzotta 
  Signed-off-by: Lv Zheng 
  Signed-off-by: Rafael J. Wysocki 
  
  The laptop was purchased from tigerdirect. Here's link to specs:
  
http://www.tigerdirect.com/applications/searchtools/item-details.asp?EdpNo=8556911
  
  The laptop appears to be a re-branded Acer Aspire E1-570:
  http://www.acer.com/ac/en/SI/content/model/NX.MGUEX.001
  
  Both have Insyde UEFI firmware. The latest version for both is v2.06 and
  have same release date, 11/11/2013, according to the Acer & Gateway
  support web sites, although the firmware reports an Oct date.
  
  I realize it's quite likely that the laptop's firmware is the root cause
  of the problem. However, since the problem did not exist on older
  kernels, I hope a patch or workaround can be identified that will allow
  me to make good use of this laptop.
  
- I assume this should also be reported to bugzilla.kernel.org. It is
- convenient to have the ubuntu-bug command do initial data collection.
+ Since I can reproduce the problem with a kernel built from the linux-
+ stable git tree, should this problem also be reported to
+ bugzilla.kernel.org? Or, should I try to contact the author of the
+ "first bad commit", Lv Zheng  with the info in this
+ bug report?
+ 
+ Is there more testing I should do? Starting with enabling
+ CONFIG_ACPI_DEBUG?
+ 
+ Would there be value in me reverting the "first bad commit" to the
+ latest Linux-4.4 kernel or to the latest xenial kernel to see if that
+ helps or hurts?
+ 
+ Is there more info I should collect, like output from acpidump?
+ (Something I've seen mentioned on bugzilla.kernel.org)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-31-generic 4.4.0-31.50
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  buus   1830 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jul 14 18:11:02 2016
  HibernationDevice: RESUME=UUID=aa093ba8-768a-4c3f-a993-de6331fe2190
  InstallationDate: Installed on 2016-07-01 (12 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Gateway NE570
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=b3005ae3-98ce-446f-a4d9-8af24cf4c3ae ro vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/08/2013

[Bug 1603230] Re: acpi regression first bad commit 02b771b64b73226052d6e731a0987db3b47281e9

2016-07-14 Thread H Buus 
** Description changed:

  I found what I believe is a regression on my Gateway ne570 laptop. It was 
running mythbuntu 14.04 LTS and ubuntu 15.04 releases quite well. But when I 
installed ubuntu 16.04 LTS, I found dmesg and kern.log were filling with 
messages like this:
  Jul 10 17:01:10 buus-ne570 kernel: [   57.741630] ACPI Error: Method reached 
maximum reentrancy limit (255) (20150818/dsmethod-341)
  Jul 10 17:01:10 buus-ne570 kernel: [   57.803775] ACPI Error: Method reached 
maximum reentrancy limit (255) (20150818/dsmethod-341)
  Jul 10 17:01:10 buus-ne570 kernel: [   57.866294] ACPI Error: Method reached 
maximum reentrancy limit (255) (20150818/dsmethod-341)
  Jul 10 17:01:10 buus-ne570 kernel: [   57.928403] ACPI Error: Method reached 
maximum reentrancy limit (255) (20150818/dsmethod-341)
  
  These messages would be repeated several times a second, and then pause
  for several seconds, then start again. I believe they are the cause of
  more sluggish behavior than with the older *Buntu releases.
  
  I followed the instructions here:
  https://wiki.ubuntu.com/Kernel/KernelBisection
- which lead me to doing "git bisect" on the linux-stable kernel. The result 
lead me to this commit:
+ which lead me to doing "git bisect" on the linux-stable tree. The result lead 
me to this commit:
  
  # first bad commit: [02b771b64b73226052d6e731a0987db3b47281e9] ACPI /
  EC: Fix an issue caused by the serialized _Qxx evaluations
  
  commit 02b771b64b73226052d6e731a0987db3b47281e9
  Author: Lv Zheng 
  Date:   Wed Aug 12 11:12:02 2015 +0800
  
  ACPI / EC: Fix an issue caused by the serialized _Qxx evaluations
  
  It is proven that Windows evaluates _Qxx handlers in a parallel way. This
  patch follows this fact, splits _Qxx evaluations from the NOTIFY queue to
  form a separate queue, so that _Qxx evaluations can be queued up on
  different CPUs rather than being queued up on a CPU0 bound queue.
  Event handling related callbacks are also renamed and sorted in this 
patch.
  
  Link: https://bugzilla.kernel.org/show_bug.cgi?id=94411
  Reported-and-tested-by: Gabriele Mazzotta 
  Signed-off-by: Lv Zheng 
  Signed-off-by: Rafael J. Wysocki 
  
  The laptop was purchased from tigerdirect. Here's link to specs:
  
http://www.tigerdirect.com/applications/searchtools/item-details.asp?EdpNo=8556911
  
  The laptop appears to be a re-branded Acer Aspire E1-570:
  http://www.acer.com/ac/en/SI/content/model/NX.MGUEX.001
  
  Both have Insyde UEFI firmware. The latest version for both is v2.06 and
  have same release date, 11/11/2013, according to the Acer & Gateway
  support web sites, although the firmware reports an Oct date.
  
  I realize it's quite likely that the laptop's firmware is the root cause
  of the problem. However, since the problem did not exist on older
  kernels, I hope a patch or workaround can be identified that will allow
  me to make good use of this laptop.
  
  I assume this should also be reported to bugzilla.kernel.org. It is
  convenient to have the ubuntu-bug command do initial data collection.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-31-generic 4.4.0-31.50
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  buus   1830 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jul 14 18:11:02 2016
  HibernationDevice: RESUME=UUID=aa093ba8-768a-4c3f-a993-de6331fe2190
  InstallationDate: Installed on 2016-07-01 (12 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Gateway NE570
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=b3005ae3-98ce-446f-a4d9-8af24cf4c3ae ro vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-31-generic N/A
   linux-backports-modules-4.4.0-31-generic  N/A
   linux-firmware1.157.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/08/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V2.06
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: EA50_CX
  dmi.board.vendor: Gateway
  dmi.board.version: V2.06
  dmi.chassis.asset.tag: Acer Asset Tag String
  dmi.chassis.type: 10
  dmi.chassis.vendor: Insyde Corp.
  dmi.chassis.version: V2.06
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.06:bd10/08/2013:svnGateway:pnNE570:pvrV2.06:rvnGateway:rnEA50_CX:rvrV2.06:cvnInsydeCorp.:ct10:cvrV2.06:
  dmi.product.name: NE570
  dmi.product.version: V2.06
  dmi.sys.vendor: Gateway

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

[Bug 1603230] [NEW] acpi regression first bad commit 02b771b64b73226052d6e731a0987db3b47281e9

2016-07-14 Thread H Buus 
Public bug reported:

I found what I believe is a regression on my Gateway ne570 laptop. It was 
running mythbuntu 14.04 LTS and ubuntu 15.04 releases quite well. But when I 
installed ubuntu 16.04 LTS, I found dmesg and kern.log were filling with 
messages like this:
Jul 10 17:01:10 buus-ne570 kernel: [   57.741630] ACPI Error: Method reached 
maximum reentrancy limit (255) (20150818/dsmethod-341)
Jul 10 17:01:10 buus-ne570 kernel: [   57.803775] ACPI Error: Method reached 
maximum reentrancy limit (255) (20150818/dsmethod-341)
Jul 10 17:01:10 buus-ne570 kernel: [   57.866294] ACPI Error: Method reached 
maximum reentrancy limit (255) (20150818/dsmethod-341)
Jul 10 17:01:10 buus-ne570 kernel: [   57.928403] ACPI Error: Method reached 
maximum reentrancy limit (255) (20150818/dsmethod-341)

These messages would be repeated several times a second, and then pause
for several seconds, then start again. I believe they are the cause of
more sluggish behavior than with the older *Buntu releases.

I followed the instructions here:
https://wiki.ubuntu.com/Kernel/KernelBisection
which lead me to doing "git bisect" on the linux-stable kernel. The result lead 
me to this commit:

# first bad commit: [02b771b64b73226052d6e731a0987db3b47281e9] ACPI /
EC: Fix an issue caused by the serialized _Qxx evaluations

commit 02b771b64b73226052d6e731a0987db3b47281e9
Author: Lv Zheng 
Date:   Wed Aug 12 11:12:02 2015 +0800

ACPI / EC: Fix an issue caused by the serialized _Qxx evaluations

It is proven that Windows evaluates _Qxx handlers in a parallel way. This
patch follows this fact, splits _Qxx evaluations from the NOTIFY queue to
form a separate queue, so that _Qxx evaluations can be queued up on
different CPUs rather than being queued up on a CPU0 bound queue.
Event handling related callbacks are also renamed and sorted in this patch.

Link: https://bugzilla.kernel.org/show_bug.cgi?id=94411
Reported-and-tested-by: Gabriele Mazzotta 
Signed-off-by: Lv Zheng 
Signed-off-by: Rafael J. Wysocki 

The laptop was purchased from tigerdirect. Here's link to specs:
http://www.tigerdirect.com/applications/searchtools/item-details.asp?EdpNo=8556911

The laptop appears to be a re-branded Acer Aspire E1-570:
http://www.acer.com/ac/en/SI/content/model/NX.MGUEX.001

Both have Insyde UEFI firmware. The latest version for both is v2.06 and
have same release date, 11/11/2013, according to the Acer & Gateway
support web sites, although the firmware reports an Oct date.

I realize it's quite likely that the laptop's firmware is the root cause
of the problem. However, since the problem did not exist on older
kernels, I hope a patch or workaround can be identified that will allow
me to make good use of this laptop.

I assume this should also be reported to bugzilla.kernel.org. It is
convenient to have the ubuntu-bug command do initial data collection.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-31-generic 4.4.0-31.50
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  buus   1830 F pulseaudio
CurrentDesktop: Unity
Date: Thu Jul 14 18:11:02 2016
HibernationDevice: RESUME=UUID=aa093ba8-768a-4c3f-a993-de6331fe2190
InstallationDate: Installed on 2016-07-01 (12 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Gateway NE570
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic.efi.signed 
root=UUID=b3005ae3-98ce-446f-a4d9-8af24cf4c3ae ro vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-31-generic N/A
 linux-backports-modules-4.4.0-31-generic  N/A
 linux-firmware1.157.2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/08/2013
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V2.06
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: EA50_CX
dmi.board.vendor: Gateway
dmi.board.version: V2.06
dmi.chassis.asset.tag: Acer Asset Tag String
dmi.chassis.type: 10
dmi.chassis.vendor: Insyde Corp.
dmi.chassis.version: V2.06
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV2.06:bd10/08/2013:svnGateway:pnNE570:pvrV2.06:rvnGateway:rnEA50_CX:rvrV2.06:cvnInsydeCorp.:ct10:cvrV2.06:
dmi.product.name: NE570
dmi.product.version: V2.06
dmi.sys.vendor: Gateway

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-bug xenial

** Description changed:

- I found what I believe is a regression on my Gateway ne570 laptop. It was 
running
- mythbuntu 14.04 LTS and ubuntu 15.04 releases quite well. But when I installed
- ubuntu 16.04 LTS, I found dmesg and kern.log were filling with messages like 
this:
- Jul 10 17:01:10

[Bug 1290460] Re: Mythbuntu Installer Crashes: File /usr/lib/python3/dist-packages/mythbuntu_common/vnc.py, line 58, in create_password ValueError: Password should be passed as bytes

2014-05-20 Thread H Buus 
Booted from USB stick  with Mythbuntu 14.04 *i386* into live environment:
- enable trusty-proposed
- update 2 packages:
  - mythbuntu-common from 0.73 to 0.74
  - mythbuntu-live-autostart from 0.69 to 0.70
- disable trusty-proposed
- Use desktop icon to install Mythbuntu, including ticking VNC
This installation succeeds, and VNC works on first boot.

I did not try updating ONLY mythbuntu-live-autostart based on Regen's
experience.

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

Title:
  Mythbuntu Installer Crashes: File /usr/lib/python3/dist-
  packages/mythbuntu_common/vnc.py, line 58, in create_password
  ValueError: Password should be passed as bytes

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

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

[Bug 1290460] Re: Mythbuntu Installer Crashes: File /usr/lib/python3/dist-packages/mythbuntu_common/vnc.py, line 58, in create_password ValueError: Password should be passed as bytes

2014-05-19 Thread H Buus 
I can confirm when booting from hard disk with Mythbuntu 14.04 *i386* installed:
- enable trusty-proposed
- update mythbuntu-common from 0.73 to 0.74
- use Mythbuntu Control Centre to install VNC, including setting the password
VNC is installed successfully and the password works after a reboot.

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

Title:
  Mythbuntu Installer Crashes: File /usr/lib/python3/dist-
  packages/mythbuntu_common/vnc.py, line 58, in create_password
  ValueError: Password should be passed as bytes

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

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

[Bug 1290460] Re: Mythbuntu Installer Crashes: File /usr/lib/python3/dist-packages/mythbuntu_common/vnc.py, line 58, in create_password ValueError: Password should be passed as bytes

2014-05-15 Thread H Buus 
I'm confused. I don't see how enabling a proposed repo on a precise
install would allow one to test a problem seen using a mythbuntu trusty
iso.  Wouldn't I need an updated iso with this package? However, I can
see it would be relatively easy to test the fix on a computer that
already has trusty installed if there were a proposed package for
mythbuntu-common. Then I could install that package and test by using
MCC to change the x11vnc password, right?

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

Title:
  Mythbuntu Installer Crashes: File /usr/lib/python3/dist-
  packages/mythbuntu_common/vnc.py, line 58, in create_password
  ValueError: Password should be passed as bytes

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

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

[Bug 1311864] [NEW] Installer crashed near end

2014-04-23 Thread H Buus 
Public bug reported:

Some of the option I used:
- Try Mythbuntu without installing, then launched the desktop shortcut.
- Chose Primary backend/frontend.
- Did not enable/disable any services.
- Used the something else option to install to a partition I had already set 
up.

I had answered all questions, e.g. user name, time zone, and it looked
like the install was going OK. Then I got the Installer crashed pop-
up, and here I am.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: ubiquity 2.18.7
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic i686
ApportVersion: 2.14.1-0ubuntu3
Architecture: i386
CasperVersion: 1.340
Date: Wed Apr 23 16:15:06 2014
InstallCmdLine: noprompt cdrom-detect/try-usb=true 
file=/cdrom/preseed/mythbuntu.seed boot=casper initrd=/casper/initrd.lz quiet 
splash --
LiveMediaBuild: Mythbuntu 14.04 LTS Trusty Tahr - Release i386 (20140417)
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug i386 mythbuntu trusty ubiquity-2.18.7

** Attachment added: syslog
   https://bugs.launchpad.net/bugs/1311864/+attachment/4094679/+files/syslog

** Attachment removed: syslog
   
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1311864/+attachment/4094679/+files/syslog

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

Title:
  Installer crashed near end

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

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

[Bug 1310359] Re: MythBuntu Control Center Plugins Tab Issue

2014-04-23 Thread H Buus 
I also see this error when I do anything in MCC that involves package 
management. like enabling/disabling services. The symptoms seen on the display 
are an Error dialog containing the message:
Exception in compareState of plugin MySQL
Disabling Plugin
I am launching MCC from the Applications-System menu and the terminal output 
described by the OP goes into my .xsessions-errors file.
This occurred on a fresh install of mythbuntu-14.04-desktop-i386.iso dated 
4/17/2014 before and after apt-get update; apt-get upgrade and before and 
after enabling the mythtv and mythbuntu updates repos.

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

Title:
  MythBuntu Control Center Plugins Tab Issue

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mythbuntu-control-centre/+bug/1310359/+subscriptions

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

[Bug 1311908] [NEW] Installer on mythbuntu is too wide and cannot be resized

2014-04-23 Thread H Buus 
Public bug reported:

My computer is connected to a TV via HDMI. There is some overscan that
cuts off the edges of the display, so being able to resize windows that
fill the screen in either/both vertical horizontal directions is
important. That is not possible with the installer, in both Try
mythbuntu  and Install mythbuntu modes. If I want to see all parts of
the window, my only choice is to move it left and right.

Because of this, I think I filed a duplicate of
https://bugs.launchpad.net/ubuntu/+source/mythbuntu-common/+bug/1309752
because I didn't realize I had checked the Install VNC option. The
check box was off screen. My duplicate is:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1311864

Possibly related is the fact that the mythbuntu-control-centre window is
also too wide and cannot be resized. Perhaps they share a common buggy
library?

** Affects: ubiquity (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/1311908

Title:
  Installer on mythbuntu is too wide and cannot be resized

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

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

[Bug 1311864] Re: Installer crashed near end

2014-04-23 Thread H Buus 
*** This bug is a duplicate of bug 1290460 ***
https://bugs.launchpad.net/bugs/1290460

** This bug has been marked a duplicate of bug 1290460
   Mythbuntu Installer Crashes: File 
/usr/lib/python3/dist-packages/mythbuntu_common/vnc.py, line 58, in 
create_password ValueError: Password should be passed as bytes

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

Title:
  Installer crashed near end

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

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

[Bug 1101395] Re: mythlogserver crashed with SIGSEGV in QObject::disconnect()

2013-02-04 Thread H Buus 
See http://code.mythtv.org/trac/ticket/10924 for a patch (mythlogserver-
segv.patch​) that I believe will fix this problem.

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

Title:
  mythlogserver crashed with SIGSEGV in QObject::disconnect()

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

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

[Bug 1101395] Re: mythlogserver crashed with SIGSEGV in QObject::disconnect()

2013-01-30 Thread H Buus 
I believe this is caused by a bug in nzmqt. It has been reported here:
https://github.com/jonnydee/nzmqt/issues/8
Several tickets have been filed against mythtv that appear to have this same 
root cause:
http://code.mythtv.org/trac/ticket/10924
http://code.mythtv.org/trac/ticket/11043
http://code.mythtv.org/trac/ticket/11360
as well as the mythtv ticket that links to this launchpad bug:
http://code.mythtv.org/trac/ticket/11378

** Bug watch added: code.mythtv.org/trac/ #10924
   http://code.mythtv.org/trac/ticket/10924

** Bug watch added: code.mythtv.org/trac/ #11043
   http://code.mythtv.org/trac/ticket/11043

** Bug watch added: code.mythtv.org/trac/ #11378
   http://code.mythtv.org/trac/ticket/11378

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

Title:
  mythlogserver crashed with SIGSEGV in QObject::disconnect()

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

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