** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/21810464/Dependencies.txt
** Attachment added: "DpkgTerminalLog.gz"
http://launchpadlibrarian.net/21810465/DpkgTerminalLog.gz
--
package mysql-server-5.1 5.1.30-2ubuntu5 failed to install/upgrade: subprocess
post-insta
PeterNSteinmetz wrote on 2009-01-31:
> there a large number of complaints that
>
> ieee1394: The root node is not cycle master capable; selecting a new
> root node and resetting...
>
> Eventually this stops repeating.
Could be flaky hardware or an issue between driver and firmware. Try
unloadi
Is this problem perhaps limited to certain FireWire controllers?
You can check with "lspci" for the controller type.
Did the same hardware work with older kernels?
--
jackd crashed using freebob cannot complete execution of processing graph ...
zombified
https://bugs.launchpad.net/bugs/264201
Y
The problem is that the ohci1394 driver gets only garbage when it
performs MMIO accesses. The core kernel is unable to set up the memory-
mapped IO correctly, I suppose due to an issue with the BIOS.
Neither "pci=noacpi" nor suppressing to leave some of the applicable drivers
off (by blacklistin
I'm not sure, did you already post at kino-dev about this? It's perhaps
fixed by libiec61883 1.2.0 (released 2009-01-15) or dvgrab 3.2
(2008-08-04) or dvgrab 3.3 (2009-01-15).
--
dvgrab -showstatus = segfault
https://bugs.launchpad.net/bugs/298549
You received this bug notification because you
lhz: Yours is a different bug. Please open a new one and include the
output from "dmesg", including the portions where ohci1394 and ieee1394
initialize the controller and from when the camcorder was plugged in/
switched on.
Back to Carl's bug:
Discussion without definite result went on at
http:/
> lhz: Yours is a different bug. Please open a new one and include the
output from "dmesg"
Also make a short not here about the new bug number.
--
dvgrab, Error: no camera exists
https://bugs.launchpad.net/bugs/298579
You received this bug notification because you are a member of Ubuntu
Bugs,
> How do we suggest this to the upstream devs through Launchpad?
Not at all. You go to the upstream developer contacts.
The OpenCV project has its forum, perhaps there you can find somebody
who would be interested in a port from the libdc1394 v1 API to the v2
API.
If specific advice is needed i
This seems to be a packaging mistake.
The /dev/raw1394 file should neither be created nor deleted by a package script.
It should be automatically created and deleted by udev whenever the raw1394
kernel module is loaded and unloaded.
--
rm: cannot remove `raw1394-': Read-only file system
https://
The Western Digital FireWire disks have some non-standard power savings
features which WD apparently tested only with some Windows PCs without
care for compliance to the SCSI specs or IEEE 1394 specs.
Are there any messages in the system log from when the system tries to
unmount the disk, e.g. SCS
Are there also no relevant messages left in the system log?
What is the brand and exact model of the FireWire disk?
--
Ubuntu becomes unrepsonsive on resume with external firewire disk attached
https://bugs.launchpad.net/bugs/320099
You received this bug notification because you are a member of U
Please post the output of dmesg, at least everything from when the
ohci1394 and ieee1394 driver initialize the controller and when the
camcorder is plugged in/ switched on.
--
Cant use firewire for DV capture
https://bugs.launchpad.net/bugs/320898
You received this bug notification because you ar
(I am maintainer of the upstream kernel's IEEE 1394 driver subsystem. I
don't have Ubuntu myself.)
> 8. Realize you need to modprobe raw1394 module into your running
kernel.
This could be a problem with Ubuntu's udev setup, or it could be a
problem at the kernel level or hardware level.
Wheneve
dvgrab v3 uses only raw1394, not the dv1394 kernel module.
The dv1394 special-purpose driver will actually stay in the kernel as
log as the whole ieee1394 driver stack. But the new alternative
firewire stack, which is meant to replace the ieee1394 stack eventually,
won't provide an interface with
For the record: The capture stalls which Carl mentioned are tracked in
bug 298579.
--
dv1394 driver is unsupported
https://bugs.launchpad.net/bugs/298533
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubunt
Oliver:
I could not reproduce the problem with a brand-new LaCie Little Disk 500 GB on
a few different controllers. But I found a little oddness of that disk in the
process: http://marc.info/?l=linux1394-devel&t=12334064382
However, at least I have got an older CD-RW which shows the same
s
[raw1394 not loaded automatically]
Could you post the output of "modinfo raw1394"? I'd like to check
whether all device identifiers are in there as they should be. May be
necessary to run it as root or to run it as "/sbin/modinfo raw1394".
Also, if you have the camcorder around, please plug it
Ok, pulled the proposed kernel and lrm for Jaunty and ran a loop of git
clone for the kernel tree over wireless using the wl driver. So far it
has done 42 iterations and is still running. I would say at least this
seems not to have become worse.
HW: BCM 4328 802.11a/b/g/n (rev 03) on a Dell Inspir
** Changed in: blogtk (Ubuntu)
Status: Incomplete => In Progress
** Changed in: blogtk (Ubuntu)
Assignee: Stefan Lesicnik (stefanlsd) => Ralph Taylor (djnrrd)
** Also affects: blogtk (Ubuntu Jaunty)
Importance: Undecided
Status: New
--
blogtk crashes on start
I updated to xUbuntu 9.04, kernel 2.6.28-11, and the situation is
slightly better. Still a lot of disconnections, but not a complete
disaster - sometimes nearly, but sometimes quiete stable.
--
ipw2100 - "Fatal interrupt. Scheduling firmware restart."
https://bugs.launchpad.net/bugs/24776
You rec
Waiting for test results.
** Changed in: linux (Ubuntu Jaunty)
Status: In Progress => Incomplete
--
modprobe -r iwl3945 causes total system freeze
https://bugs.launchpad.net/bugs/345710
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubun
Setting this back to triaged as the following is still failing on
2.6.30-999-generic:
#> ls -l
total 4
-rw-r--r-- 1 stefan stefan 6 2009-06-19 10:18 a
-rw-r--r-- 1 stefan stefan 0 2009-06-19 10:18 b
#> sudo mount -tcifs -ocredentials=../ ///public /mnt
#> mkdir /mnt/Test
#> cp -a * /
To decide whether this is rather a server or client side problem, the
same test done on a current Hardy client (the server is Jaunty in both
cases):
#> ls -la
total 12
drwxr-xr-x 2 stefan stefan 4096 2009-06-19 10:37 .
drwxr-xr-x 99 stefan stefan 4096 2009-06-19 10:37 ..
-rw-r--r-- 1 ste
Based on the previous comments I mark this as fixed now.
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
** Changed in: linux (Ubuntu)
Assignee: Stefan Bader (stefan-bader-canonical) => (unassigned)
--
Wacom tablet doesn't work in Gutsy, freezes OS in
Yes I am. When using the debug options in conjunction with the skip
argument, the dmesg will contain some information about the system
trying figure out the right routing for the timer interrupt. That might
be interesting to look at.
--
Hardy, Intrepid, Jaunty 64 "hiccup" on Sager notebook.
https
To be more precise here: in order to get any Jaunty SRU:
1. Check against current Jaunty
2. Compare against a recent https://wiki.ubuntu.com/KernelMainlineBuilds
(2.6.30)
3. Report whether it works in 1. and/or 2. and supply "lsusb -v" output for the
device
--
USB Hard Drive Not Accessible, vo
** Also affects: linux (Ubuntu Jaunty)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
** Changed in: linux (Ubuntu)
Assignee: Brad Figg (brad-figg) => (unassigned)
** Changed in: linux (Ubuntu Jaunty)
Importance: Undec
** Description changed:
+ SRU Justification:
+
+ Impact: removed directories in cifs mounted share can still appear
+ within application calls. This could potentially be a security issue?
+
+ Fix: A patch from Steve French fixes the problem, [CIFS] revalidate
+ parent inode when rmdir done with
** Changed in: linux (Ubuntu Jaunty)
Status: Triaged => Fix Committed
--
removed directories in cifs mounted share can still appear within application
calls
https://bugs.launchpad.net/bugs/317274
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
I guess he means that one...
http://git.kernel.org/?p=linux/kernel/git/tytso/ext4.git;a=commitdiff;h=16cb5dd9f53e569130584696909d423b6fe38c1e
--
[PATCH] ext4 filesystem corruption
https://bugs.launchpad.net/bugs/389555
You received this bug notification because you are a member of Ubuntu
Bugs, w
opped into the F11 kernel.)"
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Status: Fix Released => Fix Committed
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Stefan Bader (stefan-bader-canonical)
** Change
nlinux: Could you try the fix described here and let us know...
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495459
Thanks!
--
Wrong device-names in udev - Unable to open master device '/dev/zap/ctl'
https://bugs.launchpad.net/bugs/64059
You received this bug notification because you are a
fta: In your merge diff you mention - - Set BIARCH_LIB_DIR to /usr/lib32
on amd64.
I dont see this in your diff... is this in error?
--
Please sponsor fakeroot 1.12.4ubuntu1
https://bugs.launchpad.net/bugs/389591
You received this bug notification because you are a member of Ubuntu
Bugs, which i
Public bug reported:
Evolution crashed when I entered the google calendar password.
** Affects: evolution (Ubuntu)
Importance: Undecided
Status: New
--
Title: evolution crashed with SIGSEGV in g_closure_invoke()
https://bugs.launchpad.net/bugs/389842
You received this bug notifica
** Attachment added: "_usr_bin_evolution.1000.crash"
http://launchpadlibrarian.net/28138269/_usr_bin_evolution.1000.crash
--
Title: evolution crashed with SIGSEGV in g_closure_invoke()
https://bugs.launchpad.net/bugs/389842
You received this bug notification because you are a member of Ubuntu
** Attachment added: "CoreDump.gz"
http://launchpadlibrarian.net/28148407/CoreDump.gz
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/28148408/Dependencies.txt
** Attachment added: "Disassembly.txt"
http://launchpadlibrarian.net/28148409/Disassembly.txt
** Attachm
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/28164049/BootDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/28164050/Dependencies.txt
** Attachment added: "HalComputerInfo.txt"
http://launchpadlibrarian.net/28164051/HalComputerInfo.txt
Public bug reported:
escription: Ubuntu 9.04
Release:9.04
linux:
Installiert: (keine)
Kandidat: 2.6.28.13.17
Versions-Tabelle:
2.6.28.13.17 0
500 http://de.archive.ubuntu.com jaunty-updates/restricted Packages
2.6.28.11.15 0
500 http://de.archive.ubuntu.
Thanks Ralph
I built with your patch and installed, but I still get a crash with the
following...
Traceback (most recent call last):
File "/usr/bin/blogtk", line 1245, in
blogtk = BloGTK()
File "/usr/bin/blogtk", line 138, in __init__
self.grabConfig()
File "/usr/bin/blogtk", line
Is the "attention"-block at top new? Or do I just mention it by now?
However, my router was in mixed-mode-state, and I set it to 802.11b, but
the problem is still present.
--
ipw2100 - "Fatal interrupt. Scheduling firmware restart."
https://bugs.launchpad.net/bugs/24776
You received this bug noti
Hey Ralph,
Thanks. Deleted the ~/.BloGTK folder and it works fine. Will look at
uploading the karmic fix in a bit.
Thanks!
--
blogtk crashes on start
https://bugs.launchpad.net/bugs/364745
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ralph, thanks for your contribution!
The only change i made was to wrap the changelog slightly. (we wrap at
80 chars).
For the Jaunty SRU, can you follow the procedure outlined here:
https://wiki.ubuntu.com/StableReleaseUpdates
For the Jaunty debdiff, note the following:
1. Version will be some
It looks useful. At least to understand better. It looks like the timer
interrupt is actually connected to pin 0 of the apic, not pin 2 as the override
tells the system. Sadly I messed up with the debug options, so the apic table
was not dumped (the right one is apic=debug). But even with what i
As these locking issues often are sensitive to timing, it could well be
that other changes had some influence. The problem with the stable
kernels is that, after the experience with 2.6.27.y which received a
huge amount of updates and sometimes caused regressions, we now went
back to cherry-pick pa
As far as my understanding goes, this is related to Python 2.6.
Intrepid has 2.5 so it should not be affected?
--
blogtk crashes on start
https://bugs.launchpad.net/bugs/364745
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-b
Just to double check that "no results seen" is meant as: after
repeatedly loading and unloading the iwl3945 module with the test
kernel, there was no system freeze. Is this correct?
--
modprobe -r iwl3945 causes total system freeze
https://bugs.launchpad.net/bugs/345710
You received this bug noti
be that http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.30/)
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Stefan Bader (stefan-bader-canonical)
--
Unable to use STV680 based webcam with Jaunty (REGRESSION)
https://bugs.launchpad.net/bugs/387559
You received this
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => John Johansen (jjohansen)
** Changed in: linux (Ubuntu Jaunty)
Assignee: (unassigned) => John Johansen (jjohansen)
--
AppArmor Debug: Hook being called from interrupt context
https://bugs.launchpad.net/bugs/350789
You received thi
There seem to be multiple issues mixed into one report. The initial report
shows problems on generic write commands without any NCQ. The ICH6 controller
used seems to use the same PCI ID for both piix and ahci modes (according to
the Jaunty code).
The second one fails on DMA read/writes with NCQ
This bug report is being closed because we received no response to the
previous inquiry for information. Please reopen if this is still an
issue in the current Ubuntu release, Jaunty Jackalope 9.04 -
http://www.ubuntu.com/getubuntu/download. If the issue remains in
Jaunty, please test the latest u
@Timo, as you say it works with Jaunty. Can you provide dmesg and 'sudo
lsusb -vvv'? Thanks.
--
[karmic] No sierra 3G with 2.6.30, works with 2.6.28
https://bugs.launchpad.net/bugs/386528
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
-
Can we get this tested and compared against Jaunty. The sony acpi driver
got reworked by then to make use of the input framework to supply a
proper input device for the hotkeys. This stopped working in Hardy as
that still uses acpi_fakekey but the keyboard driver was modified in
upstream to ignore
Setting to incomplete while waiting for feedback.
** Changed in: linux (Ubuntu)
Status: Triaged => Incomplete
--
non-functioning hotkeys on Vaio TX2
https://bugs.launchpad.net/bugs/76924
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
@Marc, could you try the SD card with a 2.6.30 kernel
https://wiki.ubuntu.com/KernelMainlineBuilds?
That way we could get a second data point. In the mean time I would prepare a
Jaunty kernel with mmc debugging enabled.
--
[Regression] Thinkpad T61 card reader no longer works
https://bugs.launc
As there seems to be no one having the inverted values problem any more
I will close the Intrepid task. Won't fix because it is unclear whether
it was fixed in Intrepid but won't qualify for an SRU after Jaunty is
now released.
** Changed in: linux (Ubuntu Intrepid)
Status: Confirmed => Won
** Changed in: linux (Ubuntu Jaunty)
Status: Incomplete => Fix Committed
** Changed in: linux (Ubuntu Jaunty)
Assignee: (unassigned) => Manoj Iyer (manjo)
** Description changed:
- The Jaunty server ISO, installer fails to recognize netxen nic. This is
- caused because netxen_nic mis
> closest to 2.6.27-14 and 2.6.28-11. I have not tested any version
> after 2.6.28-11. In all this cases, using the ahci module produces the
A mainline kernel farther away (2.6.30) would be of interest as it could show
whether this is an issue upstream.
> timeouts, but ata_piix works fine. If o
Ralph - Thanks for the Jaunty diff and SRU report. The only change you
need to make is jaunty needs to be jaunty-proposed. MOTU-SRU can also
do that though. So im subscribing them to this bug for the SRU.
--
blogtk crashes on start
https://bugs.launchpad.net/bugs/364745
You received this bug no
Debdiff for Karmic attached.
nlinux: are you able to apply this diff and build to test it functions
as it should before I upload. (should apply against Jaunty also)
Thanks
** Attachment added: "karmic-debdiff"
http://launchpadlibrarian.net/28256470/karmic-debdiff
--
Wrong device-names in ud
Karmic contains 0.61.09-2 which has the included fix.
** Also affects: synfigstudio (Ubuntu Jaunty)
Importance: Undecided
Status: New
** Also affects: synfigstudio (Ubuntu Intrepid)
Importance: Undecided
Status: New
** Changed in: synfigstudio (Ubuntu Jaunty)
Status: N
Jaunty debdiff - slightly modified to go to jaunty-proposed and version
number.
** Attachment added: "synfigstudio-jaunty.debdiff"
http://launchpadlibrarian.net/28257934/synfigstudio-jaunty.debdiff
--
synfigstudio crashed with SIGSEGV in Gtk::Tooltips::set_tip()
https://bugs.launchpad.net/bug
I built the Jaunty package on my system with the debdiff but I still get
the synfig crash... I deleted ~/.synfig and still the same issue.
Is there something else thats needs to be updated? I see some people
have reported it working with just this small change? Can anyone check
this for me and co
Intrepid debdiff
** Attachment added: "synfigstudio-intrepid.debdiff"
http://launchpadlibrarian.net/28257936/synfigstudio-intrepid.debdiff
--
synfigstudio crashed with SIGSEGV in Gtk::Tooltips::set_tip()
https://bugs.launchpad.net/bugs/277926
You received this bug notification because you are
Marc, sure it will. In the meantime I finished the build of debug Jaunty kernel
(the same as the updates kernel but with mmc debug enabled). Those can be found
at: http://people.ubuntu.com/~smb/bug329424/
So installing one of this will get more debugging info on Jaunty.
--
[Regression] Thinkpad
Right, this rather sounds like something specific to a certain card and
not like a regression for Thinkpads as it seemed before. For the moment
I would close this now (as invalid as we do not have a unreproducible).
Should the problem come back, feel free to reopen it.
** Changed in: linux (Ubuntu
Thanks a lot for the references Andres. Huaxu sent a patch on our mailing list
which also moved the statement which remove the work queue to a later point.
Given your references this would sound like even the current upstream code will
run into this. So we definitely need someone with that hardwa
@gidantribal, no, that would require to know what to change. So far I know the
in the working kernels, there was a GFX0 object in /proc/acpi/video (and likely
that hat the brightness control). The acpidump shows that there should be the
required methods to detect the brightness control (although
The problem here is that the message just tells you there is something
wrong operating the disk. And reading through the report this has been
resolved for some by replacing cables, bios settings or even memory. And
this is really hard, if not impossible to get solved. Ok, enough
whining.
Those wit
I had a look at the drivers code for firmware loading. This seems to be
the same since Intrepid. And the firmware size (which would be relevant
here) also is roughly the same. While an order-6 allocation (64 pages in
one block) is somewhat large, it did not seem to be a problem in the
past. So may
Closing fixed as indicated by last comment.
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
--
after restart (reboot) console (ctrl-alt-f1) not available
https://bugs.launchpad.net/bugs/185152
You received this bug notification because you are a member of Ubuntu
Bugs, whi
This bug report is being closed because we received no response to the
previous inquiry for information. Please reopen if this is still an
issue in the current Ubuntu release, Jaunty Jackalope 9.04 -
http://www.ubuntu.com/getubuntu/download. If the issue remains in
Jaunty, please test the latest u
This bug is being closed as it does not seem to be an issue any more,
Please reopen if this is still an issue in the current Ubuntu release,
Jaunty Jackalope 9.04 - http://www.ubuntu.com/getubuntu/download. If
the issue remains in Jaunty, please test the latest upstream kernel
build - https://wiki
This bug report is being closed because we received no response to the
previous inquiry for information. Please reopen if this is still an
issue in the current Ubuntu release, Jaunty Jackalope 9.04 -
http://www.ubuntu.com/getubuntu/download. If the issue remains in
Jaunty, please test the latest u
This bug report is being closed because we received no response to the
previous inquiry for information. Please reopen if this is still an
issue in the current Ubuntu release, Jaunty Jackalope 9.04 -
http://www.ubuntu.com/getubuntu/download. If the issue remains in
Jaunty, please test the latest u
This bug report is being closed because we received no response to the
previous inquiry for information. Please reopen if this is still an
issue in the current Ubuntu release, Jaunty Jackalope 9.04 -
http://www.ubuntu.com/getubuntu/download. If the issue remains in
Jaunty, please test the latest u
clearer.
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Stefan Bader (stefan-bader-canonical)
--
package linux-image-2.6.27-7-generic 2.6.27-7.14 failed to install/upgrade:
impossibile creare il link per la copia di sicurezza di
`./boot/vmlinuz-2.6.27-7-generic' prima di i
I strongly believe this has been fixed by now. Please reopen if this is
still an issue in the current Ubuntu release, Jaunty Jackalope 9.04 -
http://www.ubuntu.com/getubuntu/download. If the issue remains in
Jaunty, please test the latest upstream kernel build -
https://wiki.ubuntu.com/KernelMainl
This bug report is being closed because we received no response to the
previous inquiry for information. Please reopen if this is still an
issue in the current Ubuntu release, Jaunty Jackalope 9.04 -
http://www.ubuntu.com/getubuntu/download. If the issue remains in
Jaunty, please test the latest u
This bug report is being closed because we received no response to the
previous inquiry for information. Please reopen if this is still an
issue in the current Ubuntu release, Jaunty Jackalope 9.04 -
http://www.ubuntu.com/getubuntu/download. If the issue remains in
Jaunty, please test the latest u
.
2. If no, run the following two commands and attach the resulting text files:
- 'sudo acpidump -o acpidump.txt'
- 'sudo dmidecode >dmidecode.txt'
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Stefan Bader (stefan-bader-canonical)
--
powernow-k8:
** Also affects: linux (Ubuntu Hardy)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Hardy)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Hardy)
Status: New => Fix Committed
** Changed in: linux (Ubuntu Hardy)
Assignee: (unassigned) => Brya
Setting back to committed. This seems to be in the portion of changes I
am about to upload.
** Changed in: linux (Ubuntu Hardy)
Status: Fix Released => Fix Committed
--
kernel bug rpc nfs client
https://bugs.launchpad.net/bugs/212485
You received this bug notification because you are a me
** Also affects: linux (Ubuntu Hardy)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Hardy)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Hardy)
Status: New => In Progress
** Changed in: linux (Ubuntu Hardy)
Assignee: (unassigned) => Brad F
** Also affects: linux (Ubuntu Hardy)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Hardy)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Hardy)
Status: New => Fix Committed
** Changed in: linux (Ubuntu Hardy)
Assignee: (unassigned) => Brad
** Changed in: linux (Ubuntu Hardy)
Status: In Progress => Fix Committed
** Description changed:
+ SRU justification:
+
+ Impact: Oops in sunrpc:rpc_shutdown_client
+
+ Fix: likely related to: #212485 kernel bug rpc nfs client. Backported
+ patch to Hardy.
+
+ Test: Test kernel in http:
** Description changed:
+ SRU Justification:
+
+ Impact: This bug causes keyboard to spew garbage on resume and might
+ cause it to go into an unknown state as reported by the bug reporter
+
+ Fix: This patch that is upstream since 2.6.26 (and is contained in
+ Intrepid and Jaunty)
+
+ ---
+
No, I did not reverse the changes "with no effect". All three changes were in
at the same time. In other words the UseEvents option of xorg.conf was enabled
at the same time as Use OpenGL vsync was disabled in mythtv.
But for now I will reverse the changes, especially the playback profile,
becau
** Changed in: linux (Ubuntu Intrepid)
Status: Triaged => Won't Fix
** Changed in: linux (Ubuntu Jaunty)
Assignee: Stefan Bader (stefan-bader-canonical) => (unassigned)
--
Genesys Logic Webcam 05e3:0503 Not Working
https://bugs.launchpad.net/bugs/215604
You receiv
Hi Quentin, sorry for not getting back for that long. If you have some time it
would be great if you could verify tat hangs against the latest daily kernel
from https://wiki.ubuntu.com/KernelMainlineBuilds
We want to make sure this problem still exists upstream. That kernel can be
installed in p
Hi Frank, the driver in use can be found looking at 'sudo lspci -vvvnn'
but drivers should be loaded automatically. With libata the hdparm
command cannot be used for setting the DMA mode. Can you add "debug" to
the kernel command line in grub (escape on the countdown then 'e' on the
kernel to boot,
This shows the problem well. What I found though is that i8k alone does
not control the fan. It only offers an interface to it. It is i8kutils
that allows to do that. Otherwise it seems to me the BIOS is in charge
of controlling the fan. Testing the here with an 1535 it looks like it
normally stays
: High
Assignee: Stefan Bader (stefan-bader-canonical)
Status: In Progress
--
Suspending with mounted ext3 formatted SD card erases partition table (karmic
regression)
https://bugs.launchpad.net/bugs/383668
You received this bug notification because you are a member of Ubuntu
Bugs
nux (Ubuntu)
Status: New => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Stefan Bader (stefan-bader-canonical)
** Attachment added: "Debugging log before patch"
http://launchpadlibrarian.net/27500271/mmc-suspend-test-3.txt
--
Suspendin
With the patch the forced unmount of ext3 still wants to write out some
data before closing the block device but this time the requests get
rejected.
Probably this is not the behavior intended but it seems to be the safe
approach.
** Attachment added: "Debugging log after patch"
http://launchp
** Attachment added: "Proposed patch"
http://launchpadlibrarian.net/27500463/0001-UBUNTU-Upstream-mmc-prevent-dangling-block-device-fr.patch
--
Suspending with mounted ext3 formatted SD card erases partition table (karmic
regression)
https://bugs.launchpad.net/bugs/383668
You received this
OK, I want to try disabling VSync. But how can I see that it is
activated? And how can I deactivate it?
--
livetv freezes randomly
https://bugs.launchpad.net/bugs/310178
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mai
OK, this is what I did:
1.) I disabled the following three settings of nvidia-settings and wrote the
result into a new xorg.conf.
X Server XVideo Settings -> Video Texture Adaptor -> Sync to VBlank
X Server XVideo Settings -> Video Blitter Adaptor -> Sync to VBlank
OpenGL Settings -> Performance
In my understanding, using udevadm settle would be the right thing to
do. This makes sure udev has done all the processing and device nodes
have been created for the existing devices. I have not looked at the
current installer code but I think it should go there if it isn't
already. I have not run
Sorry, but disabling OpenGL vsync had no effect. LiveTV freezes
randomly.
--
livetv freezes randomly
https://bugs.launchpad.net/bugs/310178
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.ub
Hey Stani.
Can you check a few things.
1. The debdiff for karmic (possibly the other also) has ctrl-m
characters (^M). Removing them causes the patch to fail. Could you
have a look at that and re-upload the diff.
2. (Closes LP: #370839) is a mix of Debian and Ubuntu. Just use (LP: #)
3. The
801 - 900 of 18987 matches
Mail list logo
