*** This bug is a duplicate of bug 512096 ***
https://bugs.launchpad.net/bugs/512096
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 512096, so it is being marked as such. Please look at
Feature request submitted:
http://sourceforge.net/tracker/?func=detail&aid=2941314&group_id=119&atid=350119
** Bug watch added: SourceForge.net Tracker #2941314
http://sourceforge.net/support/tracker.php?aid=2941314
--
lcdproc: Futaba dm-140gink VFD device needs driver
https://bugs.launchpad.
Public bug reported:
Mythbuntu 9.10 AMD64 on MSI Media Live, fresh install, default settings,
standalone (frontend + backend installed).
Once Mythbuntu is running, pressing the power button does nothing. The
box does not shut down as it used to on Mythbuntu 8.04.
If Myth is configured to give a
** Changed in: libxfce4util (Ubuntu)
Importance: Undecided => Low
** Changed in: libxfce4util (Ubuntu)
Assignee: (unassigned) => Lionel Le Folgoc (mrpouit)
--
xfconf dbus service doesn't know about XDG user variables
https://bugs.launchpad.net/bugs/327926
You received this bug notificati
** Branch linked: lp:~xubuntu-dev/libxfce4util/lucid
--
xfconf dbus service doesn't know about XDG user variables
https://bugs.launchpad.net/bugs/327926
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to mythbuntu-default-settings in ubuntu.
** Changed in: libxfce4util (Ubuntu)
Status: New => In Progress
--
xfconf dbus service doesn't know about XDG user variables
https://bugs.launchpad.net/bugs/327926
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to mythbuntu-default-se
** Branch linked: lp:~mrpouit/mythbuntu/mythbuntu-default-settings
--
xfconf dbus service doesn't know about XDG user variables
https://bugs.launchpad.net/bugs/327926
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to mythbuntu-default-settin
Steve, I would hardly call changing the description
from:
"in-place corruption of large files *without fsck or reboot* reported with
linux 2.6.31-14.46 on ext4"
to:
"in-place corruption of files *without fsck or reboot* reported with linux
2.6.31-14.46 on ext4"
hardly constitutes hijacking. i
On Wed, Jan 27, 2010 at 08:29:43PM -, TragicWarrior wrote:
> Why not just re-characterize the bug to match the collected data?
Because the data is not related to the bug that was reported, and it's not
appropriate to hijack bug reports for unrelated issues.
--
Steve Langasek
This bug was fixed in the package xubuntu-default-settings - 10.04.0
---
xubuntu-default-settings (10.04.0) lucid; urgency=low
* New versioning scheme, includes the release version.
* Rename etc/xdg/xubuntu to etc/xdg/xdg-xubuntu, to use the new "feature"
added in gdm by Didie
** Changed in: xubuntu-default-settings (Ubuntu)
Status: New => In Progress
** Changed in: xubuntu-default-settings (Ubuntu)
Importance: Undecided => Low
** Changed in: xubuntu-default-settings (Ubuntu)
Assignee: (unassigned) => Lionel Le Folgoc (mrpouit)
--
xfconf dbus service d
Steve,
The original posting mentions files that are 512MB (comment #53). Later
it is assessed at 300MB (comment #89). Then it was whittled down to
120MB (comment #143). Then it went to 45MB (comment #174). I don't
think it would be ideal to open a new bug since so much data has been
captured h
On Wed, Jan 27, 2010 at 07:49:06PM -, TragicWarrior wrote:
> I believe the large file aspect of the bug is an incorrect
> characterization. If you take a look at comment #184, you will see that
> I have reproduced the bug on much smaller files.
No, you have reproduced some *other* corruption
You did not say anything about reproducing the bug on smaller files. To
my knowledge this would be the first report of a file smaller than 100MB
being corrupted by this bug.
--
in-place corruption of large files *without fsck or reboot* reported with linux
2.6.31-14.46 on ext4
https://bugs.laun
Ryan,
I believe the large file aspect of the bug is an incorrect
characterization. If you take a look at comment #184, you will see that
I have reproduced the bug on much smaller files.
--
in-place corruption of large files *without fsck or reboot* reported with linux
2.6.31-14.46 on ext4
http
Why would the kernel update get corrupted unless the archive or any of
the files it contains are several hundred megabytes in size?
--
Ryan C. Underwood,
--
in-place corruption of large files *without fsck or reboot* reported with linux
2.6.31-14.46 on ext4
https://bugs.launchpad.net/bugs/45
** Branch linked: lp:xubuntu-default-settings
--
xfconf dbus service doesn't know about XDG user variables
https://bugs.launchpad.net/bugs/327926
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to mythbuntu-default-settings in ubuntu.
Status
This is an unfortunate chicken-and-egg scenario. Assuming the latest
kernel in karimc-proposed does fix the problem, how does one safely
upgrade their system since there is a likelihood the very update itself
will get corrupted? The only certain solution would be to (gasp) re-
master the Karmic I
This is not incomplete. The issue is documented in the release notes.
** Changed in: ubuntu-release-notes
Status: Incomplete => Fix Released
--
in-place corruption of large files *without fsck or reboot* reported with linux
2.6.31-14.46 on ext4
https://bugs.launchpad.net/bugs/453579
You
** Changed in: ubuntu-release-notes
Status: Fix Released => Incomplete
--
in-place corruption of large files *without fsck or reboot* reported with linux
2.6.31-14.46 on ext4
https://bugs.launchpad.net/bugs/453579
You received this bug notification because you are a member of Mythbuntu
Bu
I have the same problem with "VLC media player 0.9.9a Grishenko" on Kubuntu
9.04.
Neither the screensaver, nor the powermanagement are disbled by vlc.
--
gnome-screensaver-command --poke no longer inhibits screensaver
https://bugs.launchpad.net/bugs/428884
You received this bug notification beca
I have the same problem with "VLC media player 0.9.9a Grishenko" on Kubuntu
9.04.
Neither the screensaver, nor the powermanagement are disbled by vlc.
--
gnome-screensaver-command --poke no longer inhibits screensaver
https://bugs.launchpad.net/bugs/428884
You received this bug notification beca
** Changed in: mythbuntu
Status: Fix Committed => Fix Released
--
Hauppage HVR-2200/2250 support for Ubuntu Lucid
https://bugs.launchpad.net/bugs/490763
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to Mythbuntu.
Status in Mythbuntu
I'm indifferent upon either approach. I'm happy to make either set of
changes as long as it's functional.
On Tue, Jan 26, 2010 at 15:51, Lionel Le Folgoc
wrote:
> To add some problems (found by Didier) about my proposed approach:
> - clutter /etc/X11/Xsession.d with two mores files (maybe not s
** Changed in: mythbuntu
Status: Incomplete => New
--
V9.10 Import of channels.conf not possible
https://bugs.launchpad.net/bugs/483055
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to Mythbuntu.
Status in Mythbuntu, Ubuntu derivati
First I tried another theme with regular V9.10 but without any
difference. (mythbuntu,mythcenter4:3)
Then I changed to auto-builds but with no change in behavior related to
the bug.
$ apt-cache policy mythtv-backend
mythtv-backend:
Installiert: 0.23.0~trunk23319-0ubuntu0~mythbuntu1
Kandidat:
There's a fair amount of ext4-fixes in the latest 2.6.31-18.55-kernel in
karmic-proposed, according to the changelog. I suppose it would be worth
testing with that kernel for the people who experience this bug.
--
in-place corruption of large files *without fsck or reboot* reported with linux
2.
** Changed in: mythplugins (Ubuntu)
Status: Triaged => In Progress
** Changed in: mythbuntu
Status: Triaged => Invalid
--
Jamu exits(1) when multiple instances are executed (such as if tvdb is down and
one doesn't time out)
https://bugs.launchpad.net/bugs/502051
You received this
Updated to mytharchive 0.22.0+fixes23230-0ubuntu0+mythbuntu3 (on a
virtual machine) and the bug seems to have been fixed. I'll try to do
the same on the real thing and let you know.
--
Mytharchive fails to create DVD: IndexError
https://bugs.launchpad.net/bugs/511696
You received this bug notific
> In the mytharchive temp directory you have chosen (usually something in
> /var/lib) you'll find a logs subdirectory.
OK attaching log (still have not upgraded to autobuilds though but just
in case).
Please see the end of the log to check the error.
I will try to reproduce the bug on a virtual
** Changed in: ubuntu-release-notes
Status: Fix Released => Fix Committed
** Changed in: ubuntu-release-notes
Status: Fix Committed => Fix Released
** Description changed:
There are worrying reports of filesystem corruption on ext4 in karmic.
Scott says:
12:36 < Keybuk> th
31 matches
Mail list logo
