apport information
** Attachment added: "Package.txt"
https://bugs.launchpad.net/bugs/1954596/+attachment/5547212/+files/Package.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1954596
Title:
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1954596/+attachment/5547213/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
apport information
** Tags added: apport-collected focal third-party-packages
** Description changed:
Table "groups" in otrs is now a reserved word for mysql 8, so upgrading from
ubuntu 18.04 to 20.04 "dies" in the middle of the process because otrs package
cannot update its tables.
This b
Public bug reported:
Table "groups" in otrs is now a reserved word for mysql 8, so upgrading from
ubuntu 18.04 to 20.04 "dies" in the middle of the process because otrs package
cannot update its tables.
This bug is related to bug 1953033
There is a workaround though that has been filed here:
ht
** Description changed:
- Table "groups" in otrs is now a reserved word for mysql 8, so upgrading
- from ubuntu 18.04 to 20.04 "dies" in the middle of the process because
- otrs package cannot update its tables.
+ Table "groups" in otrs is now a reserved word for mysql 8, so upgrading from
ubuntu
Public bug reported:
While advancing from 18.04 LTS to 20.04 LTS things got somewhat
corrupted because of huge databases in mysql, myISAM tables.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: otrs2 6.0.26-1
ProcVersionSignature: Ubuntu 4.15.0-163.171-generic 4.15.18
Uname: Linux 4.15.
@Robie Basak
The main problem is that all the packages that rely on an active mysql-server
to upgrade themselves will stop and ask what to do, thus you anyway need to
babysit them :)
At this point, having the upgrade of Mysql-Server stopping if it was on
and could not restart will only stop the
I understand your concern.
My installation had a separate cnf file in the conf.d directory with a
couple of personal settings affecting the mysqld, among them the old
slow-query variables.
This was done in order to have the my.cnf upgrade smoothly among time.
What happened is that mysql-server d
Why couldn't mysql-server just throw a warning on an unknown variable and start
with a default?
Especially during a release update, mysql is critical when many packages rely
on a DB-based content to upgrade themselves (Mediawiki, otrs, etc)
--
You received this bug notification because you are
*** This bug is a duplicate of bug 1571865 ***
https://bugs.launchpad.net/bugs/1571865
I suggest to simply ignore the unknown variables and throw a warning instead of
blocking mysql server to start... This "feature" broke beyond repair my OTRS
installation that was happening during the same
Public bug reported:
...ERROR: hook /usr/share/apport/general-hooks/ubuntu.py crashed:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 197, in _run_hook
symb['add_info'](report, ui)
File "/usr/share/apport/general-hooks/ubuntu.py", line 6
Public bug reported:
When I close the lid of my laptop everything seems to be fine on the
suspend procedures. BUT the laptop eats all the battery in few hours.
This is an exerpt of the syslog in which you can see that the suspend
procedures are interrupted before the complete suspend, then go on
Public bug reported:
dbcheck is part of the bacula project. It is broken as the version packaged in
Ubuntu 14.04 is still the 5.2.6, while the fixed program is in 5.2.10, released
back in June 2012 but still not in Ubuntu.
This is extremely annoying as it breaks even a vanilla install of a mysql
13 matches
Mail list logo
