[Bug 1178841] Re: [regression] iwl3945 0000:04:00.0: Radio disabled by HW RF Kill switch
I'm running Linux Mint 17 Qiana, and I have experience the same problem. I have posted about it here: http://forums.linuxmint.com/viewtopic.php?f=49t=181680e=0 I'm new to Linux Mint, I don't know how to log a bug report, but if someone can post instructions I will follow them. Thanks very much, Zelek. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1178841 Title: [regression] iwl3945 :04:00.0: Radio disabled by HW RF Kill switch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1178841/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1388488] Re: iwl3945 0000:10:00.0: Radio disabled by HW RF Kill switch
If a developer require remote access to my laptop to view the issue, 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/1388488 Title: iwl3945 :10:00.0: Radio disabled by HW RF Kill switch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1388488/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1388488] [NEW] iwl3945 0000:10:00.0: Radio disabled by HW RF Kill switch
Public bug reported: See http://forums.linuxmint.com/viewtopic.php?f=49t=181680e=0 (Text from above is copied below) I have just installed Linux Mint 17 on one of my laptops. syslog and kern.log are going crazy. kern.log is filling up with lines like this: [code]Nov 2 09:35:42 mark-HP-Compaq-nc6400-RR980UC-ABG kernel: [ 3081.138890] iwl3945 :10:00.0: Radio disabled by HW RF Kill switch Nov 2 09:35:42 mark-HP-Compaq-nc6400-RR980UC-ABG kernel: [ 3081.139569] iwl3945 :10:00.0: Radio disabled by HW RF Kill switch Nov 2 09:35:42 mark-HP-Compaq-nc6400-RR980UC-ABG kernel: [ 3081.144192] iwl3945 :10:00.0: Radio disabled by HW RF Kill switch Nov 2 09:35:42 mark-HP-Compaq-nc6400-RR980UC-ABG kernel: [ 3081.144563] iwl3945 :10:00.0: Radio disabled by HW RF Kill switch Nov 2 09:35:42 mark-HP-Compaq-nc6400-RR980UC-ABG kernel: [ 3081.146589] iwl3945 :10:00.0: Radio disabled by HW RF Kill switch Nov 2 09:35:42 mark-HP-Compaq-nc6400-RR980UC-ABG kernel: [ 3081.147038] iwl3945 :10:00.0: Radio disabled by HW RF Kill switch Nov 2 09:35:42 mark-HP-Compaq-nc6400-RR980UC-ABG kernel: [ 3081.148757] iwl3945 :10:00.0: Radio disabled by HW RF Kill switch Nov 2 09:35:42 mark-HP-Compaq-nc6400-RR980UC-ABG kernel: [ 3081.149123] iwl3945 :10:00.0: Radio disabled by HW RF Kill switch Nov 2 09:35:42 mark-HP-Compaq-nc6400-RR980UC-ABG kernel: [ 3081.151086] iwl3945 :10:00.0: Radio disabled by HW RF Kill switch Nov 2 09:35:42 mark-HP-Compaq-nc6400-RR980UC-ABG kernel: [ 3081.151381] iwl3945 :10:00.0: Radio disabled by HW RF Kill switch[/code] syslog is filling up with lines like this: [code]Nov 2 09:28:17 mark-HP-Compaq-nc6400-RR980UC-ABG NetworkManager[768]: warn Trying to remove a non-existant call id. Nov 2 09:28:17 mark-HP-Compaq-nc6400-RR980UC-ABG wpa_supplicant[813]: Could not set interface wlan0 flags (UP): No such device Nov 2 09:28:17 mark-HP-Compaq-nc6400-RR980UC-ABG wpa_supplicant[813]: nl80211: Could not set interface 'wlan0' UP Nov 2 09:28:17 mark-HP-Compaq-nc6400-RR980UC-ABG wpa_supplicant[813]: Could not set interface wlan0 flags (UP): No such device Nov 2 09:28:17 mark-HP-Compaq-nc6400-RR980UC-ABG wpa_supplicant[813]: WEXT: Could not set interface 'wlan0' UP Nov 2 09:28:17 mark-HP-Compaq-nc6400-RR980UC-ABG wpa_supplicant[813]: wlan0: Failed to initialize driver interface Nov 2 09:28:17 mark-HP-Compaq-nc6400-RR980UC-ABG NetworkManager[768]: error [1414873697.838472] [nm-supplicant-interface.c:997] interface_add_cb(): (wlan0): error adding interface: wpa_supplicant couldn't grab this interface. [/code] wpa_supplicant and rsyslogd are tanking the CPU (two-core laptop): [code]top - 09:29:44 up 45 min, 3 users, load average: 3.28, 3.36, 3.22 Tasks: 163 total, 4 running, 159 sleeping, 0 stopped, 0 zombie %Cpu(s): 48.9 us, 29.7 sy, 0.0 ni, 20.7 id, 0.2 wa, 0.5 hi, 0.0 si, 0.0 st KiB Mem: 3082052 total, 2998228 used,83824 free, 5168 buffers KiB Swap: 1998844 total,34532 used, 1964312 free. 2062920 cached Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 813 root 20 0 30476 1004856 R 49.7 0.0 22:46.56 wpa_supplicant 551 syslog20 0 255844 1172716 S 26.2 0.0 12:00.12 rsyslogd 768 root 20 0 340840 3976 3336 S 24.2 0.1 11:06.54 NetworkManager 497 message+ 20 0 40008 1744900 R 14.2 0.1 6:24.06 dbus-daemon [/code] I believe it is related to the following bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1178841 Does anyone have a fix for this? Due to the excessive CPU load and filling up the root filesystem with logs the system is under heavy strain and not usable for what I plan for it. I have already had to delete syslog.1 and kern.log.1 once... the root filesystem had 0 bytes free, I waited for the system to automatically create the .1 files then I deleted them. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mark 1917 F pulseaudio CurrentDesktop: X-Cinnamon Date: Sun Nov 2 15:13:14 2014 HibernationDevice: RESUME=UUID=ba7c5f8c-8e81-47fc-b3f5-ca9b24261ee1 InstallationDate: Installed on 2014-11-01 (0 days ago) InstallationMedia: Linux Mint 17 Qiana - Release amd64 20140624 MachineType: Hewlett-Packard HP Compaq nc6400 (RR980UC#ABG)
[Bug 390452] Re: Update to 0.5.3 release
The fix for MythTV has been released so that is no longer a blocker for this. -- Update to 0.5.3 release https://bugs.launchpad.net/bugs/390452 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400018] Re: Automatic reboot for UI-limited machines
That is great. I might play with it myself. I'd like to add the extra options so that it doesn't reboot if I'm watching TV. if /usr/X11R6/bin/xset -display :0 -q | grep -q Monitor is On and for samba something involving: net RAP session -I localhost but I'll have to turn those into Python. Without these checks I'm not sure I'd want to actually turn that on. My other issue is that it isn't very discoverable. So thanks! I might also have a play myself. -- Automatic reboot for UI-limited machines https://bugs.launchpad.net/bugs/400018 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400018] Re: Automatic reboot for UI-limited machines
I just re-read my last comment and realised it sounded sarcastic. It wasn't meant to. I really am grateful for the fast response. -- Automatic reboot for UI-limited machines https://bugs.launchpad.net/bugs/400018 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 400018] [NEW] Automatic reboot for UI-limited machines
Public bug reported: Binary package hint: update-manager Summary: At the moment on my Jaunty box I have automatic security updates selected, and mostly that works fine. Sometimes the machine needs to reboot for these updates to be effective. In this case it brings up a dialog informing me that a reboot is required and giving me the option to do so. I would like an option to reboot automatically. I notice that an option like this is already in the https://wiki.ubuntu.com/auto-update-blueprint , but there are some extra tweaks that would be useful for me. Details: I'm running a mythtv box. This is a home media server that uses the 'lirc' infra-red controller package as its main form of input - I have no keyboard or mouse available for normal use. Auto-update is good, but at the moment when I get the restart required dialog I have to go dig out the keyboard or mouse to make the dialog go away. There are a couple of potential solutions here: - Make the dialog lirc aware, or - Make the system reboot automatically, or - Make the system reboot automatically, but only when the machine is idle. The first two would both work, but I think the third is the best option. Detecting 'idle'ness really depends upon what the machine is used for. For me, there are three indicators: - The X DPMS system has the display dimmed, and - noone is logged in to the samba server on the machine (which happens automatically - the machine is used for Apple Time Machine backups). The first of those is the most relevant. I don't want the system rebooting while I'm watching a movie, even though the mouse, which is not readily accessible, hasn't moved in weeks. I'd be happy if there was a way to script your own idleness detector, with a simple, sensible, default. I don't know if this bug belongs in the update-notifier package instead. ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New -- Automatic reboot for UI-limited machines https://bugs.launchpad.net/bugs/400018 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 392362] [NEW] Upgrade to mythtv fixes 20697 for lcdproc compatibility
Public bug reported: Binary package hint: mythtv LCDProc has recently released a new version with many driver updates, etc. There is a bug in the 0.21 release of mythtv that means mythtv does not work with this new release of LCDProc (Mythtv bugs 6105 and 6625). The bug was fixed in mythtv trunk and then backported to the 0.21 fixes branch in mythtv revision 20697. It would be nice to upgrade to a 0.21-fixes revision that includes this fix before Karmic is released. ** Affects: mythtv (Ubuntu) Importance: Undecided Status: New -- Upgrade to mythtv fixes 20697 for lcdproc compatibility https://bugs.launchpad.net/bugs/392362 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 392362] Re: Upgrade to mythtv fixes 20697 for lcdproc compatibility
The ubuntu LCDProc package hasn't been updated yet, but I'm hoping it will be soon. The launchpad ticket # for that update is 390452. -- Upgrade to mythtv fixes 20697 for lcdproc compatibility https://bugs.launchpad.net/bugs/392362 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 390452] Re: Update to 0.5.3 release
There is a bug in older versions of MythTV that make it not work well with this release of LCDProc. This bug has been fixed in the MythTV repository, but the fix hasn't reached the mythtv Ubuntu package yet. The launchpad ticket asking for an update of the Ubuntu MythTV package is 392362 . -- Update to 0.5.3 release https://bugs.launchpad.net/bugs/390452 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 390452] [NEW] Update to 0.5.3 release
Public bug reported: Binary package hint: lcdproc LCDProc 0.5.3 has just been released. It would be nice to upgrade to this for Karmic. http://sourceforge.net/projects/lcdproc/ I suspect that there might be people encountering configuration issues on upgrade. It might be a good idea to adjust the default config to include ServerScreen=no. The default setting of this option has changed since 0.5.2 (well, a bug in the default was fixed having a similar effect), and this means that people using MythTV to turn off their backlight will see the backlight flash. Turning ServerScreen off fixes the problem. ** Affects: lcdproc (Ubuntu) Importance: Undecided Status: New -- Update to 0.5.3 release https://bugs.launchpad.net/bugs/390452 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 390452] Re: Update to 0.5.3 release
Upgrading to this version will also fix #153185. As noted in the comments on that bug report, a driver for the imon device is included in the new release. -- Update to 0.5.3 release https://bugs.launchpad.net/bugs/390452 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 90228] Re: Impossible to list only user installed packages
This would also be useful for failed dist-upgrades (which I've had happen before). I'd like to be able to easily list the packages I've installed so that if I need to reconstruct the system from scratch, I can. -- Impossible to list only user installed packages https://bugs.launchpad.net/bugs/90228 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 385417] Re: libqt3-mt segfault on closing sql database
Guess at appropriate package. ** Description changed: - I have mythtv packages installed on an Intrepid amd64 system. I've been + I have mythtv packages installed on an Jaunty amd64 system. I've been getting the following in my logs: Jun 9 15:14:07 willvo kernel: [58904.532991] mythfilldatabas[21579]: segfault at 22523b0 ip 022523b0 sp 7fdaea4dada8 error 15 Following up on the mythtv mailing lists lead me here: http://www.gossamer-threads.com/lists/mythtv/users/382116#382116 which notes that this is a qt3-3.3.8 bug. It is being tracked on the QT bug tracker here: http://www.qtsoftware.com/developer/task- tracker/index_html?id=154194method=entry and appears to be fixed in qt 3.3.9. There also appears to be a patch to 3.3.8 floating around the mythtv mailing list (which might allow a faster fix than waiting for 3.3.9 in ubuntu): http://www.gossamer-threads.com/lists/mythtv/dev/259725#259725 I've attached the patch below. ** Package changed: ubuntu = qt-x11-free (Ubuntu) -- libqt3-mt segfault on closing sql database https://bugs.launchpad.net/bugs/385417 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to qt-x11-free in ubuntu. -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 385417] [NEW] libqt3-mt segfault on closing sql database
Public bug reported: I have mythtv packages installed on an Intrepid amd64 system. I've been getting the following in my logs: Jun 9 15:14:07 willvo kernel: [58904.532991] mythfilldatabas[21579]: segfault at 22523b0 ip 022523b0 sp 7fdaea4dada8 error 15 Following up on the mythtv mailing lists lead me here: http://www.gossamer-threads.com/lists/mythtv/users/382116#382116 which notes that this is a qt3-3.3.8 bug. It is being tracked on the QT bug tracker here: http://www.qtsoftware.com/developer/task- tracker/index_html?id=154194method=entry and appears to be fixed in qt 3.3.9. There also appears to be a patch to 3.3.8 floating around the mythtv mailing list (which might allow a faster fix than waiting for 3.3.9 in ubuntu): http://www.gossamer-threads.com/lists/mythtv/dev/259725#259725 I've attached the patch below. ** Affects: ubuntu Importance: Undecided Status: New -- libqt3-mt segfault on closing sql database https://bugs.launchpad.net/bugs/385417 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 385417] Re: libqt3-mt segfault on closing sql database
** Attachment added: qt3-mysql-unload-crash.diff http://launchpadlibrarian.net/27716068/qt3-mysql-unload-crash.diff -- libqt3-mt segfault on closing sql database https://bugs.launchpad.net/bugs/385417 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 383446] [NEW] Update to 0.8.5 release
Public bug reported: Binary package hint: lirc I'm using the lirc_imon driver. The current (0.8.4a) release doesn't work for me, but a newer release (CVS when I first tried it) did work. It would be nice to update to the recent 0.8.5 release for Karmic (so I don't have to maintain a separate kernel module with lirc-modules-source and a backport of the appropriate driver). ** Affects: lirc (Ubuntu) Importance: Undecided Status: New -- Update to 0.8.5 release https://bugs.launchpad.net/bugs/383446 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 326768] Re: mysqld_safe thinks mysqld has crashed when it hasn't
I just tried Marc's signal tracker: Here is the output after boot: Executing (/usr/bin/mysqld_safe_real ) signo: [1], errno: [0], code: [128], pid: [0], uid: [0] It looks like a code of 0x80 corresponds to a code of SI_KERNEL. What does the kernel have against mysqld_safe? -- mysqld_safe thinks mysqld has crashed when it hasn't https://bugs.launchpad.net/bugs/326768 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-dfsg-5.0 in ubuntu. -- 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 326768] Re: mysqld_safe thinks mysqld has crashed when it hasn't
I just tried Marc's signal tracker: Here is the output after boot: Executing (/usr/bin/mysqld_safe_real ) signo: [1], errno: [0], code: [128], pid: [0], uid: [0] It looks like a code of 0x80 corresponds to a code of SI_KERNEL. What does the kernel have against mysqld_safe? -- mysqld_safe thinks mysqld has crashed when it hasn't https://bugs.launchpad.net/bugs/326768 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 326768] Re: mysqld_safe thinks mysqld has crashed when it hasn't
On 12/05/2009, at 2:16 AM, Mathias Gug wrote: Thanks for figuring this out. This is probably the root cause of the issue. I've seen similar behavior with sshd - could you describe your network configuration? Are you using network-manager or /etc/network/intrefaces? Are you using a static configuration or rely on dhcp? I have a static configuration in /etc/network/interfaces. The reload seems to happen just before NetworkManager starts up. Will :-} -- mysqld_safe thinks mysqld has crashed when it hasn't https://bugs.launchpad.net/bugs/326768 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-dfsg-5.0 in ubuntu. -- 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 326768] Re: mysqld_safe thinks mysqld has crashed when it hasn't
On 12/05/2009, at 2:16 AM, Mathias Gug wrote: Thanks for figuring this out. This is probably the root cause of the issue. I've seen similar behavior with sshd - could you describe your network configuration? Are you using network-manager or /etc/network/intrefaces? Are you using a static configuration or rely on dhcp? I have a static configuration in /etc/network/interfaces. The reload seems to happen just before NetworkManager starts up. Will :-} -- mysqld_safe thinks mysqld has crashed when it hasn't https://bugs.launchpad.net/bugs/326768 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 326768] Re: mysqld_safe thinks mysqld has crashed when it hasn't
I just tried manually adding Mathias' latest change. That also seems to solve the problem for me. (This was not a full re-install with that patch - just me with vim reverting the old patch and adding that patch. I hope I haven't made any mistakes :) -- mysqld_safe thinks mysqld has crashed when it hasn't https://bugs.launchpad.net/bugs/326768 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 326768] Re: mysqld_safe thinks mysqld has crashed when it hasn't
I patched mysqld_safe directly based on Mario's diff (and replace the wait that I had removed). This fixes the problem for me. I also looked in the logs to see what was happening on boot with the change and I noticed: May 10 11:02:55 willvo sshd[2981]: Received signal 15; terminating. May 10 11:02:55 willvo ntpd[3721]: ntpd exiting on signal 15 but both seem to be running. Postfix also reloads its configuration. Is someone (upstart?) telling all daemons to reload their configs for some reason? Is there an easy way to track down who sends a signal? It seems there are two problems here - the signal being sent, and mysqld_safe poor response to receiving it. It would be nice to get to the bottom of each of them. ** Description changed: --Impact-- I'm running mythtv on jaunty with mysql-server-5.0 version 5.1.30really5.0.75-0ubuntu5. During boot mysql starts, then mythtv starts, then mysql restarts and mythtv gets confused. This is caused by some portions of a debian patch that is applied on top of MySQL. It has not been accepted yet at upstream MySQL. The MySQL server is receiving a SIGHUP which the behavior is changed because of the debian patch. Here are some relevant syslog sections: Feb 8 12:35:07 willvo mysqld_safe[3668]: started Feb 8 12:35:08 willvo mysqld[3671]: 090208 12:35:08 InnoDB: Started; log sequence number 0 43655 Feb 8 12:35:08 willvo mysqld[3671]: 090208 12:35:08 [Note] /usr/sbin/mysqld: ready for connections. Feb 8 12:35:08 willvo mysqld[3671]: Version: '5.0.75-0ubuntu5' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu) Feb 8 12:35:08 willvo /etc/mysql/debian-start[3710]: Upgrading MySQL tables if necessary. Feb 8 12:35:08 willvo /etc/mysql/debian-start[3713]: Looking for 'mysql' as: /usr/bin/mysql Feb 8 12:35:08 willvo /etc/mysql/debian-start[3713]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck Feb 8 12:35:08 willvo /etc/mysql/debian-start[3713]: This installation of MySQL is already upgraded to 5.0.75, use --force if you still need to run mysql_upgrade Feb 8 12:35:08 willvo /etc/mysql/debian-start[3720]: Checking for insecure root accounts. Feb 8 12:35:08 willvo /etc/mysql/debian-start[3724]: Triggering myisam-recover for all MyISAM tables Feb 8 12:35:13 willvo mythtv-backend[4560]: Started mythtv-backend Feb 8 12:35:16 willvo mysqld_safe[5212]: Number of processes running now: 1 Feb 8 12:35:16 willvo mysqld_safe[5223]: mysqld process hanging, pid 3670 - killed Feb 8 12:35:16 willvo mysqld_safe[5227]: restarted Feb 8 12:35:16 willvo mysqld[5231]: 090208 12:35:16 InnoDB: Started; log sequence number 0 43655 Feb 8 12:35:17 willvo mysqld[5231]: 090208 12:35:17 [Note] /usr/sbin/mysqld: ready for connections. Feb 8 12:35:17 willvo mysqld[5231]: Version: '5.0.75-0ubuntu5' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu) Note that mysqld_safe is finds one mysqld process still running after it is supposed to have crashed. mysqld_safe then kills that process and starts another. This only seems to happen once during boot - it doesn't keep restarting mysqld in normal use. --Addressing-- This has *not* yet been addressed in the karmic branch, but it has been verified that a PPA resolve the problem. MySQL hasn't changed yet in karmic, so this can easily be brought to karmic if viewed to properly solve the problem. - --Test Case-- + --Test Case - Myth To reproduce this, you can boot up off of a fresh install of Mythbuntu 9.04 (which includes MySQL and mythtv-backend preinstalled). Check /var/log/syslog and you will see errors regarding mysql getting restarted because of a hanging process. Depending on the speed of your system, this may or may not cause problems with mythtv-backend because of the race condition inherent in this problem. + + -- Test Case - non-Myth + sudo killall -HUP mysqld_safe # should cause mysql to reload its config, but causes it to restart instead. --Regression Potential-- This type of patch has implications if users were dependent on the behavior of this debian/ubuntu specific patch to issue a mysql refresh via a SIGHUP. -- mysqld_safe thinks mysqld has crashed when it hasn't https://bugs.launchpad.net/bugs/326768 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-dfsg-5.0 in ubuntu. -- 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 326768] Re: mysqld_safe thinks mysqld has crashed when it hasn't
I patched mysqld_safe directly based on Mario's diff (and replace the wait that I had removed). This fixes the problem for me. I also looked in the logs to see what was happening on boot with the change and I noticed: May 10 11:02:55 willvo sshd[2981]: Received signal 15; terminating. May 10 11:02:55 willvo ntpd[3721]: ntpd exiting on signal 15 but both seem to be running. Postfix also reloads its configuration. Is someone (upstart?) telling all daemons to reload their configs for some reason? Is there an easy way to track down who sends a signal? It seems there are two problems here - the signal being sent, and mysqld_safe poor response to receiving it. It would be nice to get to the bottom of each of them. ** Description changed: --Impact-- I'm running mythtv on jaunty with mysql-server-5.0 version 5.1.30really5.0.75-0ubuntu5. During boot mysql starts, then mythtv starts, then mysql restarts and mythtv gets confused. This is caused by some portions of a debian patch that is applied on top of MySQL. It has not been accepted yet at upstream MySQL. The MySQL server is receiving a SIGHUP which the behavior is changed because of the debian patch. Here are some relevant syslog sections: Feb 8 12:35:07 willvo mysqld_safe[3668]: started Feb 8 12:35:08 willvo mysqld[3671]: 090208 12:35:08 InnoDB: Started; log sequence number 0 43655 Feb 8 12:35:08 willvo mysqld[3671]: 090208 12:35:08 [Note] /usr/sbin/mysqld: ready for connections. Feb 8 12:35:08 willvo mysqld[3671]: Version: '5.0.75-0ubuntu5' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu) Feb 8 12:35:08 willvo /etc/mysql/debian-start[3710]: Upgrading MySQL tables if necessary. Feb 8 12:35:08 willvo /etc/mysql/debian-start[3713]: Looking for 'mysql' as: /usr/bin/mysql Feb 8 12:35:08 willvo /etc/mysql/debian-start[3713]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck Feb 8 12:35:08 willvo /etc/mysql/debian-start[3713]: This installation of MySQL is already upgraded to 5.0.75, use --force if you still need to run mysql_upgrade Feb 8 12:35:08 willvo /etc/mysql/debian-start[3720]: Checking for insecure root accounts. Feb 8 12:35:08 willvo /etc/mysql/debian-start[3724]: Triggering myisam-recover for all MyISAM tables Feb 8 12:35:13 willvo mythtv-backend[4560]: Started mythtv-backend Feb 8 12:35:16 willvo mysqld_safe[5212]: Number of processes running now: 1 Feb 8 12:35:16 willvo mysqld_safe[5223]: mysqld process hanging, pid 3670 - killed Feb 8 12:35:16 willvo mysqld_safe[5227]: restarted Feb 8 12:35:16 willvo mysqld[5231]: 090208 12:35:16 InnoDB: Started; log sequence number 0 43655 Feb 8 12:35:17 willvo mysqld[5231]: 090208 12:35:17 [Note] /usr/sbin/mysqld: ready for connections. Feb 8 12:35:17 willvo mysqld[5231]: Version: '5.0.75-0ubuntu5' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu) Note that mysqld_safe is finds one mysqld process still running after it is supposed to have crashed. mysqld_safe then kills that process and starts another. This only seems to happen once during boot - it doesn't keep restarting mysqld in normal use. --Addressing-- This has *not* yet been addressed in the karmic branch, but it has been verified that a PPA resolve the problem. MySQL hasn't changed yet in karmic, so this can easily be brought to karmic if viewed to properly solve the problem. - --Test Case-- + --Test Case - Myth To reproduce this, you can boot up off of a fresh install of Mythbuntu 9.04 (which includes MySQL and mythtv-backend preinstalled). Check /var/log/syslog and you will see errors regarding mysql getting restarted because of a hanging process. Depending on the speed of your system, this may or may not cause problems with mythtv-backend because of the race condition inherent in this problem. + + -- Test Case - non-Myth + sudo killall -HUP mysqld_safe # should cause mysql to reload its config, but causes it to restart instead. --Regression Potential-- This type of patch has implications if users were dependent on the behavior of this debian/ubuntu specific patch to issue a mysql refresh via a SIGHUP. -- mysqld_safe thinks mysqld has crashed when it hasn't https://bugs.launchpad.net/bugs/326768 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 326768] Re: mysql thinks it has crashed when it hasn't
I thought I'd list what I discovered when originally looking at this bug. Much of this is mythtv specific. I'm currently of the opinion that there are issues in both mythtv and mysql, with the mythtv strange behaviour tickling a mysql issue. On a problematic boot, mysql starts normally. This means that the mysqld_safe script is run. It starts the mysql daemon then waits for the daemon to stop. If the daemon stops normally (the pid file has been removed) then mysqld_safe exits. If the daemon didn't stop normally then mysqld_safe kills any remaining instances of mysqld running, before restarting the daemon. mythbackend then starts. During startup, mythbackend does a reschedule of its recordings (i.e. it goes through the list of programs to be recorded and the epg and decides which ones to record with which tuner). At some point around this time, mysqld_safe is detecting that the mysql daemon has stopped. It is then, as noted above, killing all remaining mysql daemon processes, before starting a fresh one. My understanding is that on my default desktop jaunty install I should only ever have one mysql daemon running at once (and a quick ps reveals that is what I currently have). If you look at the logs above, you'll see that mysqld_safe is detecting one mysql daemon running after it has already decided that one has failed. This is what I meant by the bug report title, mysql thinks it has crashed when it hasn't. This seems to be a problem with a false detection of a crash causing the cleanup mechanism to actually kill the mysqld process. When the mysqld process is killed in this way during a mythbackend reschedule, mythbackend fails to schedule any recordings. Once the database restarts, mythbackend can still access the database - e.g. you can see the epg, and you see the list of programs you've ask to be recorded. If you do anything that causes mythbackend to re-schedule recordings (e.g. change anything in the list of programs to be recorded - you can even change it back after the reschedule), then mythbackend will connect to the db, reschedule correctly and everything will be fine. This is a little bit weird in that restarting mythbackend later doesn't cause mysql to restart again. It only seems to restart once. If there was a major problem with mythbackend then I would expect it to show up every time mythbackend is restarted. It also doesn't seem to be a race condition (which was suggested by the fact that it only happens the first time). If I put a `sleep 10` at the start of the mythbackend init script it doesn't help. ** Summary changed: - mysql thinks it has crashed when it hasn't + mysqld_safe thinks mysqld has crashed when it hasn't -- mysqld_safe thinks mysqld has crashed when it hasn't https://bugs.launchpad.net/bugs/326768 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 326768] Re: mysql thinks it has crashed when it hasn't
Barney - could you clarify your comment for me? You say Running mythtv-setup, removing all encoder cards and adding them again fixes this. Is this a permanent fix, or does the problem recur if you reboot? If this is only a fix for that boot, there are easier ones. Anything that causes mythbackend to force a reschedule is a temporary fix (this includes restarting mythbackend, or just marking a new show to be recorded). -- mysql thinks it has crashed when it hasn't https://bugs.launchpad.net/bugs/326768 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-dfsg-5.0 in ubuntu. -- 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 326768] Re: mysql thinks it has crashed when it hasn't
Barney - could you clarify your comment for me? You say Running mythtv-setup, removing all encoder cards and adding them again fixes this. Is this a permanent fix, or does the problem recur if you reboot? If this is only a fix for that boot, there are easier ones. Anything that causes mythbackend to force a reschedule is a temporary fix (this includes restarting mythbackend, or just marking a new show to be recorded). -- mysql thinks it has crashed when it hasn't https://bugs.launchpad.net/bugs/326768 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 326768] Re: mysql thinks it has crashed when it hasn't
Yeah - it looks to me like Bug 358173 is the same bug. I find it very strange that this bug only affects mythbackend (all the possible duplicates seem to reference mythtv). I suspect that it is doing something strange. I reported a mysql bug because I figured that the mysql server shouldn't behave strangely even if the client program does weird things. -- mysql thinks it has crashed when it hasn't https://bugs.launchpad.net/bugs/326768 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-dfsg-5.0 in ubuntu. -- 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 326768] Re: mysql thinks it has crashed when it hasn't
Yeah - it looks to me like Bug 358173 is the same bug. I find it very strange that this bug only affects mythbackend (all the possible duplicates seem to reference mythtv). I suspect that it is doing something strange. I reported a mysql bug because I figured that the mysql server shouldn't behave strangely even if the client program does weird things. -- mysql thinks it has crashed when it hasn't https://bugs.launchpad.net/bugs/326768 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 339233] Re: [iGM45] Video playback suffers from tearing on GMA 4500MHD
Just a quick note... It appears this upstream bug is also relevant: http://bugs.freedesktop.org/show_bug.cgi?id=20664 ** Bug watch added: freedesktop.org Bugzilla #20664 https://bugs.freedesktop.org/show_bug.cgi?id=20664 -- [iGM45] Video playback suffers from tearing on GMA 4500MHD https://bugs.launchpad.net/bugs/339233 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 326768] Re: mysql thinks it has crashed when it hasn't
Without the fix I mentioned in the original report, mysql gets restarted once. Obviously mysqld_safe uses some CPU to do this (it will do one iteration of the loop at the bottom of the script). mysqld_safe is not looping and restarting mysql multiple times, which is, I think, the behaviour you were asking about. No, it does not sit at the top of `top`. It is strange that it only falls through once. -- mysql thinks it has crashed when it hasn't https://bugs.launchpad.net/bugs/326768 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 339781] Re: [g45] xv video tearing
** Attachment added: Output of lspci -vvnn http://launchpadlibrarian.net/24302932/lspci.out -- [g45] xv video tearing https://bugs.launchpad.net/bugs/339781 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 339781] Re: [g45] xv video tearing
** Attachment added: Xorg.0.log http://launchpadlibrarian.net/24302965/Xorg.0.log -- [g45] xv video tearing https://bugs.launchpad.net/bugs/339781 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 339781] Re: [g45] xv video tearing
** Attachment added: Output of xvinfo http://launchpadlibrarian.net/24303042/xvinfo.out -- [g45] xv video tearing https://bugs.launchpad.net/bugs/339781 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 339781] [NEW] [g45] xv video tearing
Public bug reported: Binary package hint: xserver-xorg-video-intel This bug report is similar to bug #278318 . The difference is that that bug was asking people switch from textured video to video overlay. The G45 doesn't have an overlay mode - the switch from textured video simply isn't possible. This bug is being worked on upstream here: http://bugs.freedesktop.org/show_bug.cgi?id=19635 A patch was committed upstream on about the 6th of March which purports to solve this problem. It would be nice to get this into the Jaunty release. ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New -- [g45] xv video tearing https://bugs.launchpad.net/bugs/339781 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 326768] [NEW] mysql thinks it has crashed when it hasn't
Public bug reported: Binary package hint: mysql-server-5.0 I'm running mythtv on jaunty with mysql-server-5.0 version 5.1.30really5.0.75-0ubuntu5. During boot mysql starts, then mythtv starts, then mysql restarts and mythtv gets confused. What seems to be happening is that line 387 (or 389?) of /usr/bin/mysqld_safe is falling through when it shouldn't. mysqld_safe is a script that starts mysqld and restarts it if it crashes. Here are some relevant syslog sections: Feb 8 12:35:07 willvo mysqld_safe[3668]: started Feb 8 12:35:08 willvo mysqld[3671]: 090208 12:35:08 InnoDB: Started; log sequence number 0 43655 Feb 8 12:35:08 willvo mysqld[3671]: 090208 12:35:08 [Note] /usr/sbin/mysqld: ready for connections. Feb 8 12:35:08 willvo mysqld[3671]: Version: '5.0.75-0ubuntu5' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu) Feb 8 12:35:08 willvo /etc/mysql/debian-start[3710]: Upgrading MySQL tables if necessary. Feb 8 12:35:08 willvo /etc/mysql/debian-start[3713]: Looking for 'mysql' as: /usr/bin/mysql Feb 8 12:35:08 willvo /etc/mysql/debian-start[3713]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck Feb 8 12:35:08 willvo /etc/mysql/debian-start[3713]: This installation of MySQL is already upgraded to 5.0.75, use --force if you still need to run mysql_upgrade Feb 8 12:35:08 willvo /etc/mysql/debian-start[3720]: Checking for insecure root accounts. Feb 8 12:35:08 willvo /etc/mysql/debian-start[3724]: Triggering myisam-recover for all MyISAM tables Feb 8 12:35:13 willvo mythtv-backend[4560]: Started mythtv-backend Feb 8 12:35:16 willvo mysqld_safe[5212]: Number of processes running now: 1 Feb 8 12:35:16 willvo mysqld_safe[5223]: mysqld process hanging, pid 3670 - killed Feb 8 12:35:16 willvo mysqld_safe[5227]: restarted Feb 8 12:35:16 willvo mysqld[5231]: 090208 12:35:16 InnoDB: Started; log sequence number 0 43655 Feb 8 12:35:17 willvo mysqld[5231]: 090208 12:35:17 [Note] /usr/sbin/mysqld: ready for connections. Feb 8 12:35:17 willvo mysqld[5231]: Version: '5.0.75-0ubuntu5' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu) Note that mysqld_safe is finds one mysqld process still running after it is supposed to have crashed. mysqld_safe then kills that process and starts another. This only seems to happen once during boot - it doesn't keep restarting mysqld in normal use. The problem is somewhat intermittent. I made it go away once before by mysqlrepairing my tables, but they seem fine now. Debian bug 418648 looks somewhat similar but slightly different (and the fix they used doesn't work for me). My current fix is to replace: $NOHUP_NICENESS $ledir/$MYSQLD $defaults --basedir=$MY_BASEDIR_VERSION --d atadir=$DATADIR $USER_OPTION --pid-file=$pid_file --skip-external-locking 21 | $ERR_LOGGER -t mysqld wait with: $NOHUP_NICENESS $ledir/$MYSQLD $defaults --basedir=$MY_BASEDIR_VERSION --dat adir=$DATADIR $USER_OPTION --pid-file=$pid_file --skip-external-locking 21 | $ ERR_LOGGER -t mysqld in the mysqld_safe script (the second line has wait removed from the end). This seems to fix the problem. I don't understand the difference in semantics between wait and normal process termination. Will ** Affects: mysql-dfsg-5.0 (Ubuntu) Importance: Undecided Status: New -- mysql thinks it has crashed when it hasn't https://bugs.launchpad.net/bugs/326768 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-dfsg-5.0 in ubuntu. -- 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 326702] [NEW] MythTV creates files in /home even if mount /home fails
Public bug reported: Binary package hint: mythtv-backend I've been having some difficulty with the filesystem I'm using for /home. This means that that filesystem has occasionally failed to mount. This is annoying, but it interacts with /etc/init.d/mythtv- backend in a bad way too... If /home doesn't mount, the mythtv-backend startup script runs anyway. And that startup script, on line 51, does this: mkdir -p $USER_HOME/.mythtv which, because of the -p option, creates files in /home even if $USER_HOME doesn't exist (because the mount failed). This causes all future attempts to mount /home to fail! (until the newly created files are removed.) Might I suggest that the '-p' option here be removed. If $USER_HOME exists, this will still create the .mythtv directory, but if /home isn't mounted then nothing bogus will be created. This is on jaunty with mythtv-backend version 0.21.0+fixes19556-0ubuntu6 ** Affects: mythtv (Ubuntu) Importance: Undecided Status: New ** Description changed: Binary package hint: mythtv-backend I've been having some difficulty with the filesystem I'm using for /home. This means that that filesystem has occasionally failed to mount. This is annoying, but it interacts with /etc/init.d/mythtv- backend in a bad way too... If /home doesn't mount, the mythtv-backend startup script runs anyway. And that startup script, on line 51, does this: mkdir -p $USER_HOME/.mythtv which, because of the -p option, creates files in /home even if $USER_HOME doesn't exist (because the mount failed). This causes all future attempts to mount /home to fail! (until the newly created files are removed.) Might I suggest that the '-p' option here be removed. If $USER_HOME exists, this will still create the .mythtv directory, but if /home isn't mounted then nothing bogus will be created. + + This is on jaunty with mythtv-backend version 0.21.0+fixes19556-0ubuntu6 -- MythTV creates files in /home even if mount /home fails https://bugs.launchpad.net/bugs/326702 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 326702] Re: MythTV creates files in /home even if mount /home fails
That sounds reasonable. Something like this: if [ ! -d $USER_HOME ]; then log_failure_msg MythTV home directory, $USER_HOME, does not exist! exit 1 fi #create a symbolic link for mysql.txt so it can't be overwritten if [ ! -e $USER_HOME/.mythtv/mysql.txt ]; then mkdir -p $USER_HOME/.mythtv chown -R $USER $USER_HOME/.mythtv ln -s /etc/mythtv/mysql.txt $USER_HOME/.mythtv/mysql.txt fi -- MythTV creates files in /home even if mount /home fails https://bugs.launchpad.net/bugs/326702 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 326768] [NEW] mysql thinks it has crashed when it hasn't
Public bug reported: Binary package hint: mysql-server-5.0 I'm running mythtv on jaunty with mysql-server-5.0 version 5.1.30really5.0.75-0ubuntu5. During boot mysql starts, then mythtv starts, then mysql restarts and mythtv gets confused. What seems to be happening is that line 387 (or 389?) of /usr/bin/mysqld_safe is falling through when it shouldn't. mysqld_safe is a script that starts mysqld and restarts it if it crashes. Here are some relevant syslog sections: Feb 8 12:35:07 willvo mysqld_safe[3668]: started Feb 8 12:35:08 willvo mysqld[3671]: 090208 12:35:08 InnoDB: Started; log sequence number 0 43655 Feb 8 12:35:08 willvo mysqld[3671]: 090208 12:35:08 [Note] /usr/sbin/mysqld: ready for connections. Feb 8 12:35:08 willvo mysqld[3671]: Version: '5.0.75-0ubuntu5' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu) Feb 8 12:35:08 willvo /etc/mysql/debian-start[3710]: Upgrading MySQL tables if necessary. Feb 8 12:35:08 willvo /etc/mysql/debian-start[3713]: Looking for 'mysql' as: /usr/bin/mysql Feb 8 12:35:08 willvo /etc/mysql/debian-start[3713]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck Feb 8 12:35:08 willvo /etc/mysql/debian-start[3713]: This installation of MySQL is already upgraded to 5.0.75, use --force if you still need to run mysql_upgrade Feb 8 12:35:08 willvo /etc/mysql/debian-start[3720]: Checking for insecure root accounts. Feb 8 12:35:08 willvo /etc/mysql/debian-start[3724]: Triggering myisam-recover for all MyISAM tables Feb 8 12:35:13 willvo mythtv-backend[4560]: Started mythtv-backend Feb 8 12:35:16 willvo mysqld_safe[5212]: Number of processes running now: 1 Feb 8 12:35:16 willvo mysqld_safe[5223]: mysqld process hanging, pid 3670 - killed Feb 8 12:35:16 willvo mysqld_safe[5227]: restarted Feb 8 12:35:16 willvo mysqld[5231]: 090208 12:35:16 InnoDB: Started; log sequence number 0 43655 Feb 8 12:35:17 willvo mysqld[5231]: 090208 12:35:17 [Note] /usr/sbin/mysqld: ready for connections. Feb 8 12:35:17 willvo mysqld[5231]: Version: '5.0.75-0ubuntu5' socket: '/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu) Note that mysqld_safe is finds one mysqld process still running after it is supposed to have crashed. mysqld_safe then kills that process and starts another. This only seems to happen once during boot - it doesn't keep restarting mysqld in normal use. The problem is somewhat intermittent. I made it go away once before by mysqlrepairing my tables, but they seem fine now. Debian bug 418648 looks somewhat similar but slightly different (and the fix they used doesn't work for me). My current fix is to replace: $NOHUP_NICENESS $ledir/$MYSQLD $defaults --basedir=$MY_BASEDIR_VERSION --d atadir=$DATADIR $USER_OPTION --pid-file=$pid_file --skip-external-locking 21 | $ERR_LOGGER -t mysqld wait with: $NOHUP_NICENESS $ledir/$MYSQLD $defaults --basedir=$MY_BASEDIR_VERSION --dat adir=$DATADIR $USER_OPTION --pid-file=$pid_file --skip-external-locking 21 | $ ERR_LOGGER -t mysqld in the mysqld_safe script (the second line has wait removed from the end). This seems to fix the problem. I don't understand the difference in semantics between wait and normal process termination. Will ** Affects: mysql-dfsg-5.0 (Ubuntu) Importance: Undecided Status: New -- mysql thinks it has crashed when it hasn't https://bugs.launchpad.net/bugs/326768 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 326162] [NEW] mythtv-status clobbers other motd update scripts
Public bug reported: Binary package hint: mythtv-status Mythtv status (version 0.7.3-2ubuntu2) has been sending annoying emails to root every 10 minutes on my machine. (Related to, but *not* the same as bug 311532.) Mythtv-status has also been clobbering other motd altering scripts on my machine (such as the one notifying me of available updates). It turns out that these two issues can be fixed with the same fix. mythtv-status is using its own system to update the motd. On the jaunty system I'm running, there is already a nice motd update mechanism in place that has two advantages: a) it doesn't have the bug that causes an error to root when it updates, and b) it doesn't clobber other motd update scripts. The fix then is simple. Remove the mythtv-status init script, and add a script in /etc/update-motd.d/ that calls mythtv-status. Be well, Will ** Affects: mythtv-status (Ubuntu) Importance: Undecided Status: New -- mythtv-status clobbers other motd update scripts https://bugs.launchpad.net/bugs/326162 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 262177] Re: [needs-packaging] FreeSwitch - telephony exchange media gateway
Hi, Just leaving notes here for whoever follows. FreeSwitch 1.0.2 will not compile with libtool 2 (which is used in intrepid and jaunty). There are some patches being worked on here: http://jira.freeswitch.org/browse/FSBUILD-82 to fix that. They apply cleanly to the source of the package I noted above (which is 1.0.2 with some patches). With that patch, the source builds, but the deb package has a few problems on jaunty. -- [needs-packaging] FreeSwitch - telephony exchange media gateway https://bugs.launchpad.net/bugs/262177 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 262177] Re: [needs-packaging] FreeSwitch - telephony exchange media gateway
It seems that some packages are available here: http://ppa.launchpad.net/pbxbuntu-drivers/ubuntu hardy main (which I found here: http://wiki.freeswitch.org/wiki/Quick_Start ) I haven't tried it myself yet, but thought it worth pointing out. -- [needs-packaging] FreeSwitch - telephony exchange media gateway https://bugs.launchpad.net/bugs/262177 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 224665] Re: ntpd starts but does not contact peers
I also had this issue. Rather than just not start ntpd in /etc/network/if-up.d/ntpdate (you'd be better off just removing the script, no?), I made it so that ntpd is restarted only if it was running to begin with: I now have this at the bottom of my script (replacing the few lines where ntpd was stopped, ntpdate run and then ntpd restarted): # Do not start ntpd if it wasn't already running RESTARTNTP=0 if [ -f /var/run/ntpd.pid ]; then RESTARTNTP=1 if [ -x /bin/pidof ]; then pidof /usr/sbin/ntpd | grep -f /var/run/ntpd.pid -q || RESTARTNTP=0 fi fi if [ $RESTARTNTP = 1 ]; then invoke-rc.d --quiet ntp stop || true fi /usr/sbin/ntpdate-debian -s $OPTS 2/dev/null if [ $RESTARTNTP = 1 ]; then invoke-rc.d --quiet ntp start || true fi -- ntpd starts but does not contact peers https://bugs.launchpad.net/bugs/224665 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 217254] Re: open-vm-tools is an alpha quality release
It is a pity that these tools are missing. While perhaps only 'alpha' quality, the official vmware tools are currently broken on hardy, whereas the open tools work. Even the vmware blogs are pointing to them: http://blogs.vmware.com/teamfusion/2008/05/linux-2624-and.html Perhaps adding a warning: unsupported would have been better than removing them entirely. Is there any chance of bringing them back? -- open-vm-tools is an alpha quality release https://bugs.launchpad.net/bugs/217254 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 154000] Re: kubuntu dist upgrade tool crashed
I have recently been re-installing Kubuntu 7.10 on a VMWare virtual machine. I had previously installed 7.10 on a similar VM last year (when 7.10 was new), and it had worked fine. Now I'm getting this crash on dist-upgrade. Directions to get a crash: i) Make a new VM (I'm using VMWare Fusion 1.1.1 on a MacBook running MacOS Leopard 10.5.2). Use the default VM settings for Ubunutu (VMWare has these defaults. It includes an 8Gb drive and 512 Mb of RAM.) ii) Install from MD5 (kubuntu-7.10-desktop-i386.iso) = ae9b209fe4b9caf545fa2011631de797 I downloaded that iso a while ago, so it may not be up-to-date. I have installed with it successfully before though (on both VMs and real machines). iii) Everything installs as normal. You then restart into the new OS. iv) Start Adept. The first time you update the apt package lists, it will tell you there is a dist-upgrade. Select it. v) Adept will download the update manager and then start it. vi) The update manager will crash. I did finally manage to get this to work by increasing the amount of RAM in my VM to 1024Mb, and increasing the drive size to 10Gb. When I did this (and re-installed from scratch) dist-upgrade didn't crash any more. -- kubuntu dist upgrade tool crashed https://bugs.launchpad.net/bugs/154000 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 202052] [NEW] Installer should allow mirror choice
Public bug reported: I've been installing kubuntu 7.10 on some machines in Australia recently. This is annoying at the moment because it seems the Aus mirror is down. This causes the install the freeze for a long time scanning the mirror. It seems that I'm not the first to have a problem like this (see bugs #162865 #95335 and even #103825). There are two problems here: i) the mirror is failing (this is what is reported in the bugs listed above), ii) There is no nice fallback from i) (This is what I'm reporting in this bug). The particular fallback that springs to mind is being able to select the mirror to install from in the installer. At the moment the mirror is selected automatically from your location, and this isn't always the best choice. There are two current work-arounds: i) Unplug the network while installing. This causes the installer to use the CD by itself. You can then plug in the network, switch mirrors, and update on the first boot. This seems messy. ii) I could probably use the Alternate install CD. This works ok for me (although I'd prefer a nice option in the gui installer), but is awful for other people in Aus I'm trying to encourage to use Kubunutu. What I would like to see: The install works as it currently does. However, if the mirror doesn't respond, or responds very slowly, then a dialog is displayed (much like the one in Adept) that allows the user to choose another mirror (hopefully starting with the ones in the user's country). Be well, Will:-} ** Affects: ubuntu Importance: Undecided Status: New -- Installer should allow mirror choice https://bugs.launchpad.net/bugs/202052 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
