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,
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
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
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
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.
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
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
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
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
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 .
--
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
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
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
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]
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
** 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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
** 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
** 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
** 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
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
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?)
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
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
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?)
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
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
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
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
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
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
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
46 matches
Mail list logo
