I'll also note I'm problem free for a few days on 5.10.24-051024-generic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889342
Title:
Thunderbolt Dock Loses Monitors
To manage notifications about
https://www.dell.com/community/XPS/XPS-13-9300-and-WD19TB-linux-
problem/td-p/7644488/highlight/true/page/13
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889342
Title:
Thunderbolt Dock Loses
5.10.0-1011kgen9tgps3rsm-oem does not help. The system doesn't detect
the TB dock at all on one USB-C port. The other leads to the laptop
screen constantly turning off and on, and no connection to the TB
dock/monitor occuring.
Same results with 5.10.0-1016 in Feisty Fixes.
I see in the Dell
See kernel log with the 5.10.0-4008-oem kernel. Didn't work with either
USB-C port.
** Attachment added: "kern.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889342/+attachment/5451633/+files/kern.log
--
You received this bug notification because you are a member of Ubuntu
Is there a signed version of 5.10 oem available anywhere? I see
5.10.0-1008-oem available in Ubuntu sources, but the version you asked
for testing is 5.10.0-4008-oem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
>From the Dell thread mentioned above, adding this to grub helps:
"mem_sleep_default=deep i915.enable_guc=2 i915.enable_dp_mst=0"
I'll test out the new kernel and get you feedback.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Another thing to note, when I get flickering monitor loss unplugging and
plugging in the dock seems to resolve. Same thing going on in the logs then:
[221027.376079] [drm:intel_fbc_enable [i915]] Enabling FBC on pipe A
[221027.387002] [drm:__intel_fbc_disable [i915]] Disabling FBC on pipe A
It looks like 5.6.0-1037.41 is on the PPA, is it worth trying that?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889342
Title:
Thunderbolt Dock Loses Monitors
To manage notifications about this
I'm already on linux-oem-5.6-headers-5.6.0-1036 with the issue still
present. I recently upgraded to a Dell Ultrasharp 38" instead of my
double configuration, and the same issue occurs with USB-C connection in
this configuration.
--
You received this bug notification because you are a member of
Can you double check that URL? Doesn't seem to be working.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889342
Title:
Thunderbolt Dock Loses Monitors
To manage notifications about this bug go
I have two monitors connected 1080p 60hz. I have tried with either HTMI
or DP, issue is present no matter the combination. I'll also note that
I lose my sound settings quite often and need to switch that back to
HDMI after any hiccups.
--
You received this bug notification because you are a
It definitely occurs with a fresh install (dell image). I received my
laptop and dock together, happened right out of the box.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889342
Title:
Happened out of the box from Dell, switching to 5.6 OEM didn't help. I
think part of the key here is the double monitor in the dock with the
laptop screen closed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
See attachment, everything is up to date according to fwupdmgr.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889342
Title:
Thunderbolt Dock Loses Monitors
To manage notifications about this bug
** Attachment added: "current_firmware.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889342/+attachment/5421352/+files/current_firmware.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "kernel_dump.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889342/+attachment/5420275/+files/kernel_dump.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889342
I'll also note that at one point in this log the dock lost my keyboard,
which needed to be unplugged and plugged back in.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889342
Title:
Thunderbolt
Took me a bit to reproduce again while logging:
1. Hit win+l to lock
2. Let monitors go to sleep (the longer the better, if I did this for a short
amount of time the system recovered)
3. Try to wake up with keyboard/mouse
4. Unlock screen is not prompted
5. Open laptop, find unlock screen there
The issue is still occurring.
Configuration - Laptop docked with screen closed, dual monitor on dock.
Linux unicron 5.6.0-1028-oem #28-Ubuntu SMP Tue Sep 8 13:34:39 UTC 2020 x86_64
x86_64 x86_64 GNU/Linux
I can reproduce it by doing the following:
1. Hit win+l to lock
2. Let monitors go to
** Attachment added: "dmesg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889342/+attachment/5414835/+files/dmesg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889342
Title:
Installed, give me some time to do some tests and see if the issue is
fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889342
Title:
Thunderbolt Dock Loses Monitors
To manage notifications
Back on 5.4.0-42-generic
I get random cut outs with this in dmesg:
[60008.139725] xhci_hcd :03:00.0: xHCI host controller not responding,
assume dead
[60008.158394] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR*
failed to get link status
Eventually the displays come back after
I upgraded my kernel to 5.6.0-1020-oem in order to test. The issue is
better then, but not resolved. When using the lock screen one out of
the two monitors is lost.
This errors are in dmesg:
[257474.965612] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR*
failed to get link status
Some additional details: I'm using a Dell WD19TB dock.
The lock screen seems to be the tipping point, with that disabled I'm
able to continually use external monitors. If I hit win+l to lock then I
have to unplug the dock in order to get external monitors working again.
--
You received this
Public bug reported:
After a suspend or locking the only way to regain external monitors is
to unplug and replug the thunderbolt dock back in.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-42-generic 5.4.0-42.46
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Public bug reported:
System failed to upgrade cleanly, dumping logs.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubuntu-release-upgrader-core 1:16.04.12
ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5
Uname: Linux 4.2.0-35-generic x86_64
NonfreeKernelModules: nvidia_uvm
If you run sudo dpkg-reconfigure mythexport and provide a real path it
should work. It should be defaulting to a good path if junk is
provided, not sure why that doesn't work sometimes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The linked branch seems to have resolved the issue.
** Changed in: squid-deb-proxy (Ubuntu)
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid-deb-proxy in Ubuntu.
The linked branch seems to have resolved the issue.
** Changed in: squid-deb-proxy (Ubuntu)
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1320587
Title:
Thanks, is there a PPA somewhere I could use to test or should I build
on my own?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid-deb-proxy in Ubuntu.
https://bugs.launchpad.net/bugs/1320587
Title:
Intermittent 403 Issues
To
Thanks, is there a PPA somewhere I could use to test or should I build
on my own?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1320587
Title:
Intermittent 403 Issues
To manage notifications about
It almost looks like you entered a space or something when asked what
folder to use?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1079972
Title:
package mythexport 2.2.4-0ubuntu1 failed to
Public bug reported:
I get intermittent 403 errors using squid-deb-proxy. If I keep retrying
eventually it will work, so this isn't a configuration issue. I have
looked into the squid logs and haven't found anything that stuck out as
an issue. I see these occurring on both Ubuntu URLs and 3rd
Public bug reported:
I get intermittent 403 errors using squid-deb-proxy. If I keep retrying
eventually it will work, so this isn't a configuration issue. I have
looked into the squid logs and haven't found anything that stuck out as
an issue. I see these occurring on both Ubuntu URLs and 3rd
I added the following in /etc/mythtv/session-settings to work around this issue:
killall xfsettingsd
This will kill xfsettingsd when mythfrontend starts.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I added the following in /etc/mythtv/session-settings to work around this issue:
sleep 10 DISPLAY=:0 wmctrl -r MythTV Frontend -b add,fullscreen
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1282868
I upgraded two boxes from 12.04 to 13.04. On both boxes xorg.conf was
renamed. This caused a DPI issue on one box, and removed several vdpau
fixes on both boxes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Correction 14.04 not 13.04, sorry.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1307546
Title:
DPI really messed up after upgrade
To manage notifications about this bug go to:
Attaching gpu-manager log that shows xorg.conf being removed.
** Attachment added: gpu-manager.log
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1307546/+attachment/4083855/+files/gpu-manager.log
--
You received this bug notification because you are a member of
This fixed the issue for me. Slade's brightness issue is a different
bug.
** Changed in: linux (Ubuntu)
Status: Incomplete = 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/1175029
I can confirm, using raring-proposed that version 3.8.0-20.31fixes the
issue.
Version 3.8.0-21.32 however does not. This matches with the mainline
kernel reports earlier in this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Any idea when the 3.8.9 kernel is coming, and what is the best way to
test it out raring-proposed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1175029
Title:
Intel HD 4000 Black Screen
To manage
Trevor, what have you done to fix the issues, are you still using an
older kernel or back to 3.8.0-19?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1170232
Title:
won't show login screen
To
I don't understand how you are getting around the blank screen issue,
there haven't been any updates to the kernel so the issue itself still
exists.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm up to date with everything except raring-proposed enabled, and the
issue still affects me. Do you have proposed enabled?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1170232
Title:
won't show
I have this same issue, I have confirmed with the mainline kernels that
both 3.8.9 and 3.8.10 work properly. 3.8.8 and Ubuntu's 3.8.0-19 both
give me a black screen. If I plug something into the display port then
I get a login screen there, but there is no way of getting said login
screen onto my
No new packages for me in raring-proposed, I am at a loss.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1170232
Title:
won't show login screen
To manage notifications about this bug go to:
*** This bug is a duplicate of bug 1175029 ***
https://bugs.launchpad.net/bugs/1175029
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
With the following kernel I only get an empty black screen on my laptop:
3.8.0-19-generic #29-Ubuntu SMP Wed Apr 17 18:16:28 UTC 2013 x86_64 x86_64
x86_64 GNU/Linux
I have tested and the same issue occurs with the 3.8.8 mainline kernel,
the 3.8.9 and 3.8.10 mainline kernels
*** This bug is a duplicate of bug 1175029 ***
https://bugs.launchpad.net/bugs/1175029
** This bug has been marked a duplicate of bug 1175029
Intel HD 4000 Black Screen
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1175029 ***
https://bugs.launchpad.net/bugs/1175029
** This bug has been marked a duplicate of bug 1175029
Intel HD 4000 Black Screen
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I tested with the mainline kernels. Both 3.8.9 and 3.8.10 work
properly. 3.8.8 shows the same results as Ubuntu's 3.8.0-19.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1170232
Title:
won't show
I have this same issue on my Dell XPS 13 ultrabook with Intel HD 4000
graphics. I believe that the 3.8.0-19 kernel is causing the issue, if
I boot to a previously installed kernel everything works fine. Using
the 3.8.0-19 kernel I get nothing on the laptop screen, if I plug
something into the
Public bug reported:
The signed kernel doesn't serve much purpose without a signed grub
bootloader, currently the user will need to install both by hand.
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: linux-signed-image-generic 3.5.0.19.22
ProcVersionSignature: Ubuntu 3.5.0-19.30-generic
Public bug reported:
On my system I needed shim-signed installed along side of grub2-signed
in order to successfully secure boot an UEFI bios.
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: grub-efi-amd64-signed 1.9+2.00-7ubuntu11
ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7
Public bug reported:
I booted a usb live image with secure boot enabled, and performed the
installation while choosing the EFI partition for the bootloader. An
unsigned version of grub and kernel were installed, causing a security
error to be thrown when attempting to boot. Disabling secure
/var/log/installer/syslog
** Attachment added: syslog
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1086989/+attachment/3452512/+files/syslog
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: mythexport
Status: New = Confirmed
** Changed in: mythexport
Assignee: (unassigned) = rhpot1991 (rhpot1991)
** Changed in: mythexport
Importance: Undecided = High
** Project changed: mythexport = mythexport (Ubuntu)
--
You received this bug notification because
** Changed in: mythexport (Ubuntu)
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/1075791
Title:
Fails to create a video with MythTV 0.26
To manage
From your log:
ERROR 2005 (HY000): Unknown MySQL server host 'jancoo' (1)
Looks like either your MySQL server is not running, or that is the
incorrect host name.
** Changed in: mythexport (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of
** Changed in: mythexport (Ubuntu)
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/1010080
Title:
Mythexport file URLs missing part of the file extension
To
** Changed in: mythexport (Ubuntu)
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/982241
Title:
mythexport daemon cannot start - no permission to write to
** Changed in: mythexport (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1010080
Title:
Mythexport file URLs missing part of the file extension
To manage
I haven't been able to reproduce this. Are you using the default
configs or a custom one?
Is there any chance you can post the results of this query:
SELECT rec.title, rec.subtitle, rec.description, pg.syndicatedepisodenumber,
pg.showtype, rec.programid, rec.basename, rec.starttime
FROM
Scratch that, I see now that the issue is in the name stored in the db
and displayed on the web interface.
** Changed in: mythexport (Ubuntu)
Assignee: (unassigned) = rhpot1991 (rhpot1991)
** Changed in: mythexport (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug
Try changing
my $x = 63 - $extension;
to:
my $x = 63 - length($extension);
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1010080
Title:
Mythexport file URLs missing part of the file
Confirmed this issue is fixed.
** Changed in: mythtv (Ubuntu)
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/997367
Title:
mythfilldatabase takes hours
Public bug reported:
Background: 12.04 went to MySQL 5.5, which uses InnoDB by default. So
temp tables created by mythfilldatabase are now innodb instead of
myisam. These temp tables get written to disk at /var/lib/mysql.
Because these temp tables are written to disk the ext4 journaler
Versions:
john@ultramagnus:~$ dpkg -l |grep mythtv
ii libmythtv-perl
2:0.25.0+fixes.20120508.b9e60ff-0ubuntu0mythbuntu4 A PERL library to access
some MythTV features
ii mythtv
2:0.25.0+fixes.20120508.b9e60ff-0ubuntu0mythbuntu4 A
Temporary fix:
Add default-storage-engine=MyISAM
to /etc/mysql/mythtv.cnf
This is not a great fix as it will set the default to MyISAM for the
entire MySQL instance.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: mythtv (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/997367
Title:
mythfilldatabase takes hours to complete
To manage notifications about
** Changed in: mythexport (Ubuntu)
Assignee: (unassigned) = rhpot1991 (rhpot1991)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/982241
Title:
mythexport daemon cannot start - no permission
*** This bug is a duplicate of bug 994238 ***
https://bugs.launchpad.net/bugs/994238
As I asked on the other bug: What did you enter when prompted for a
directory? The only way I know to force that to happen is to enter
something like spaces.
--
You received this bug notification because
What did you enter when prompted for a directory? The only way I know
to force that to happen is to enter something like spaces.
** Changed in: mythexport (Ubuntu)
Status: In Progress = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
From your log: ERROR 2002 (HY000): Can't connect to local MySQL server
through socket '/var/run/mysqld/mysqld.sock' (2)
One of the following issues will cause this:
1. MySQL isn't installed or running
2. Your /etc/mythtv/mysql.txt or /etc/mythtv/config.xml have the wrong MySQL
login information
No response, marking as invalid.
** Changed in: mythexport (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/963789
Title:
package mythexport
** Changed in: mythbuntu
Status: Fix Released = Triaged
** Changed in: mythbuntu
Status: Triaged = Fix Committed
** Changed in: mythbuntu
Assignee: (unassigned) = rhpot1991 (rhpot1991)
** Also affects: mythweb (Ubuntu)
Importance: Undecided
Status: New
** Changed
** Changed in: mythbuntu
Status: Fix Released = Triaged
** Changed in: mythbuntu
Status: Triaged = Fix Committed
** Changed in: mythbuntu
Assignee: (unassigned) = rhpot1991 (rhpot1991)
** Also affects: mythweb (Ubuntu)
Importance: Undecided
Status: New
** Changed
** Changed in: mythexport (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/948671
Title:
package mythexport 2.1.5-0ubuntu1 failed to install/upgrade:
** Changed in: mythexport (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/769494
Title:
package mythexport 2.1.5-0ubuntu1 failed to install/upgrade:
What directory did you choose when prompted? The only way to force this
to happen is to put junk in there.
** Changed in: mythexport (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
From your log: ERROR 2002 (HY000): Can't connect to local MySQL server
through socket '/var/run/mysqld/mysqld.sock' (2)
One of the following issues will cause this:
1. MySQL isn't installed or running
2. Your /etc/mythtv/mysql.txt or /etc/mythtv/config.xml have the wrong MySQL
login information
From your log: ERROR 2002 (HY000): Can't connect to local MySQL server
through socket '/var/run/mysqld/mysqld.sock' (2)
One of the following issues will cause this:
1. MySQL isn't installed or running
2. Your /etc/mythtv/mysql.txt or /etc/mythtv/config.xml have the wrong MySQL
login information
From your log: ERROR 2002 (HY000): Can't connect to local MySQL server
through socket '/var/run/mysqld/mysqld.sock' (2)
One of the following issues will cause this:
1. MySQL isn't installed or running
2. Your /etc/mythtv/mysql.txt or /etc/mythtv/config.xml have the wrong MySQL
login information
Your dpkg terminal log is incomplete.
** Changed in: mythexport (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/948671
Title:
package mythexport
Already depends on it: http://packages.ubuntu.com/oneiric/mythexport
** Changed in: mythexport (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/946317
Title:
Did the issue go away when you upgraded to 11.10?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-dfsg-5.1 in Ubuntu.
https://bugs.launchpad.net/bugs/633725
Title:
mysql thread_stack parameter too low, causing usage problems.
Did the issue go away when you upgraded to 11.10?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/633725
Title:
mysql thread_stack parameter too low, causing usage problems.
To manage notifications
** Changed in: mythexport (Ubuntu)
Status: Incomplete = Opinion
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-dfsg-5.1 in Ubuntu.
https://bugs.launchpad.net/bugs/633725
Title:
mysql thread_stack parameter too low,
** Changed in: mythexport (Ubuntu)
Status: New = Confirmed
** Changed in: mythexport (Ubuntu)
Assignee: (unassigned) = rhpot1991 (rhpot1991)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
From your log: ERROR 2002 (HY000): Can't connect to local MySQL server
through socket '/var/run/mysqld/mysqld.sock' (2)
One of the following issues will cause this:
1. MySQL isn't installed or running
2. Your /etc/mythtv/mysql.txt or /etc/mythtv/config.xml have the wrong MySQL
login information
Missing log files but most likely this is your issue:
ERROR 2002 (HY000): Can't connect to local MySQL server through socket
'/var/run/mysqld/mysqld.sock' (2)
One of the following issues will cause this:
1. MySQL isn't installed or running
2. Your /etc/mythtv/mysql.txt or /etc/mythtv/config.xml
From your log: ERROR 2002 (HY000): Can't connect to local MySQL server
through socket '/var/run/mysqld/mysqld.sock' (2)
One of the following issues will cause this:
1. MySQL isn't installed or running
2. Your /etc/mythtv/mysql.txt or /etc/mythtv/config.xml have the wrong MySQL
login information
From your log: ERROR 2002 (HY000): Can't connect to local MySQL server
through socket '/var/run/mysqld/mysqld.sock' (2)
One of the following issues will cause this:
1. MySQL isn't installed or running
2. Your /etc/mythtv/mysql.txt or /etc/mythtv/config.xml have the wrong MySQL
login information
From your log: ERROR 2002 (HY000): Can't connect to local MySQL server
through socket '/var/run/mysqld/mysqld.sock' (2)
One of the following issues will cause this:
1. MySQL isn't installed or running
2. Your /etc/mythtv/mysql.txt or /etc/mythtv/config.xml have the wrong MySQL
login information
From your log: ERROR 2002 (HY000): Can't connect to local MySQL server
through socket '/var/run/mysqld/mysqld.sock' (2)
One of the following issues will cause this:
1. MySQL isn't installed or running
2. Your /etc/mythtv/mysql.txt or /etc/mythtv/config.xml have the wrong MySQL
login information
ERROR 1045 (28000): Access denied for user 'mythtv'@'localhost' (using
password: YES)
One of the following issues will cause this:
1. MySQL isn't installed or running
2. Your /etc/mythtv/mysql.txt or /etc/mythtv/config.xml have the wrong MySQL
login information
3. You provided the wrong MySQL
** Changed in: mythexport (Ubuntu)
Status: Incomplete = Opinion
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/633725
Title:
mysql thread_stack parameter too low, causing usage problems.
To
ERROR 1045 (28000): Access denied for user 'mythtv'@'localhost' (using
password: YES)
One of the following issues will cause this:
1. MySQL isn't installed or running
2. Your /etc/mythtv/mysql.txt or /etc/mythtv/config.xml have the wrong MySQL
login information
3. You provided the wrong MySQL
From your log: ERROR 2002 (HY000): Can't connect to local MySQL server
through socket '/var/run/mysqld/mysqld.sock' (2)
One of the following issues will cause this:
1. MySQL isn't installed or running
2. Your /etc/mythtv/mysql.txt or /etc/mythtv/config.xml have the wrong MySQL
login information
1 - 100 of 223 matches
Mail list logo
