[Bug 1130897] [NEW] MythBuntu update-manager comes up in the foreground even when configured to display under MythTV

2013-02-20 Thread tji
Public bug reported: Running Mythbuntu 12.04.2, and I have configured update-manager to display behind the mythfrontend GUI, but it still displays in the foreground. Since MythTV is primarily controlled via infrared remote and does not have keyboard and mouse connected, it is problematic to dismi

[Bug 343781] Re: nvidia-based Mac Mini (Macmini3, 1) won't reboot (but will halt)

2009-10-03 Thread tji
Just confirming the same behavior.. Mac Mini (nvidia chipset) running 9.04. When I reboot it appears to work, closes down everything, kills ssh sessions, etc. But, hangs at a black screen never actually rebooting. -- nvidia-based Mac Mini (Macmini3,1) won't reboot (but will halt) https://bugs

[Bug 145382] Re: [Gutsy] broken 70-persistent-net.rules

2008-02-27 Thread tji
I realized after my previous message that this bug relates to Gutsy in general, and not just the JeOS version.. My comment was specific to the JeOS build, which operates in a fundamentally different environment as a Virtual Machine, which leads to issues with the virtual NIC devices being a lot mo

[Bug 145382] Re: [Gutsy] broken 70-persistent-net.rules

2008-02-27 Thread tji
Aside from the busybox issue..Isn't the udev net persistence feature going to cause a lot more problems than it solves? As I understand it, it is recording the MAC address of the NIC, and associating that with an ethernet interface. So, that if the order the NICs are initialized in changes,

[Bug 113710] Re: HAL fails to initialize on startup. hald takes all CPU.

2007-05-10 Thread tji
Resolved issue by swapping out 3Com 3CR990 NIC (Typhoon Driver) for Intel e100. 3cr990 seemed to work fine from a network perspective, the pause/hald issue was the only problem. -- HAL fails to initialize on startup. hald takes all CPU. https://bugs.launchpad.net/bugs/113710 You received thi

[Bug 113710] Re: HAL fails to initialize on startup. hald takes all CPU.

2007-05-10 Thread tji
Based on www searches, turning up similar errors, I have tried several other debugging steps, all of which failed: - Removed all USB devices (Griffin Radio Shark), for reboot. No Effect. - Changed from ATI X driver to fbdev. No Effect. - Changed from auto-login to delayed login. No Effect. - D

[Bug 113710] HAL fails to initialize on startup. hald takes all CPU.

2007-05-09 Thread tji
Public bug reported: Clean install of Feisty x86-64, on a box previously running dapper (completely clean, OS disk formatted in install). Boots normally, until it gets to "starting HAL" item, at which point it stops for 5 minutes. Eventually, it resumes the boot process, and completes. On the