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:
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
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
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
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
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
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.
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
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
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
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
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"
** 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:
** 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:
** 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
** 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
** 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
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
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
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.
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
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
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
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
*** 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
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:
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
27 matches
Mail list logo
