I see the same firmware loading issue. I assumed the problem was in
tuner_xc2028, as I don't see any related messages in dmesg after the
firmware blob fails to load:
Mar 26 22:03:20 localhost kernel: [ 11.567369] xc2028 0-0061: Loading
firmware for type=BASE F8MHZ (3), id 0
000.
Not seeing the issue on linux-image-generic-lts-raring v3.8.0.37.37 .
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1291459
Title:
ioctl FE_GET_INFO hangs with DViCO FusionHDTV DVB-T Dual Digital
$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=10.04
DISTRIB_CODENAME=lucid
DISTRIB_DESCRIPTION=Ubuntu 10.04.3 LTS
$ version 0.99.99-15ubuntu2
$ strace streamtuner
click on 'local' tab and the last part of the strace output is:
read(3,
** Tags added: lucid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/665168
Title:
Rhythmbox fails to connect to DAAP share
To manage notifications about this bug go to:
I see this in 0.12.8-0ubuntu7 (lucid version, i386).
The server is mt-daap (0.9~r1696.dfsg-15build1) running on lucid i386 also.
iTunes on a mac sees it just fine and plays songs fine.
I am able to play files from the server with VLC and the http: access
method.
I don't see the DAAP server
Public bug reported:
The immediate issue I have is:
I have my login shell set to tcsh. However .cshrc is not getting executed on
login via gdm.
However on investigating I could not find the expected system-wide cshrc and
login files.
dpkg claims they are there but I can't see them (I did a
closing. got the paths wrong. nevermind.
** Changed in: tcsh (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/824245
Title:
tcsh: missing /etc/csh files
To
No further problems here, so it seems it is fixed for me. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/690798
Title:
arduino USB serial device breaks on lucid kernel upgrade
--
After watching waiting a bit, I've seen no more errors of the type I
described in #16. I've rebooted and done a replugging test or two and
it's all been solid.
Coincidentally one of my 1-wire sensors died but I got quite different
error messages from that and it seems clear that the ftdi_sio
Unfortunately the fix seems to be incomplete for me.
$ cat /proc/version_signature
Ubuntu 2.6.32-28.55-generic 2.6.32.27+drm33.12
$ uname -a
Linux ubuntu 2.6.32-28-generic #55-Ubuntu SMP Mon Jan 10 21:21:01 UTC 2011 i686
GNU/Linux
Reverting the commit 55b5b5448771f964776a716227afd3ddef2c860e
strace of digitemp to illustrate the behaviour:
* on 2.6.32-26-generic with 55b5b5448771f964776a716227afd3ddef2c860e reverted
** Attachment added: strace.digitemp.works.2.6.32-22-generic
strace on 2.6.32-28-generic with device not working
** Attachment added: digitemp.strace.2.6.32-28
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/690798/+attachment/1814321/+files/digitemp.strace.2.6.32-28
--
You received this bug notification because you are a member of Ubuntu
Bugs,
strace on 2.6.32-28-generic with device working
** Attachment added: digitemp.strace.2.6.32-28.working
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/690798/+attachment/1814331/+files/digitemp.strace.2.6.32-28.working
--
You received this bug notification because you are a member of
oops - re #17 - the trace attached there is for 2.6.32-22-generic, well
before this whole mess started.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/690798
Title:
arduino USB serial device breaks
Hm. The changelog in the package I installed (linux-
image-2.6.32-28-generic 2.6.32-28.55) shows this:
linux (2.6.32-28.50) lucid-proposed; urgency=low
[ Tim Gardner ]
...
[ Upstream Kernel Changes ]
...
* USB: ftdi_sio: revert USB: ftdi_sio: fix DTR/RTS line modes
- LP: #688669
I tested this device:
$ sudo lsusb -d 0846:4260
Bus 001 Device 004: ID 0846:4260 NetGear, Inc. WG111(v3) 54 Mbps Wireless
[RealTek RTL8187B]
Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass0 (Defined at Interface
With the patched kernel iwconfig reports a bit rate of 36Mbit/s. Non-
optimal tests (rsync over ssh within the wireless LAN) showed a real
throughput of at least 2.7Mbit/s, ie well over 1Mbit/s.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I rebuilt tag Ubuntu-2.6.32-25.43 (3db80d04abba8cf8ab670ddd6435de1ad8287c39)
with
55b5b5448771f964776a716227afd3ddef2c860e reverted.
My device now works correctly. Yay.
--
FTDI based USB to serial adapter no longer works
https://bugs.launchpad.net/bugs/655868
You received this bug notification
** Tags added: patch
** Summary changed:
- FTDI based USB to serial adapter no longer works
+ [lucid regression] FTDI based USB to serial adapter no longer works
--
[lucid regression] FTDI based USB to serial adapter no longer works
https://bugs.launchpad.net/bugs/655868
You received this bug
The change I bisected to (55b5b5448771f964776a716227afd3ddef2c860e)
is 6a1a82df91fa0eb1cc76069a9efe5714d087eccd from upstream.
That commit was reverted recently:
See also LP#650731
--
FTDI based USB to serial adapter no longer works
https://bugs.launchpad.net/bugs/655868
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
I am seeing exactly the same issue, on i386. I have the same version of
digitemp, 3.5.0ds1-1.
I found a kernel commit which I think causes this, see LP#655868.
It's unclear if the kernel was wrong before and got fixed (so digitemp needs to
be changed too)
or if the kernel change was wrong
I've bisected this, down to this commit. What now?
git bisect bad b81cce9f4a8ebd3332063d4cda1b87384d5e33fd
Bisecting: 0 revisions left to test after this (roughly 0 steps)
[55b5b5448771f964776a716227afd3ddef2c860e] USB: ftdi_sio: fix DTR/RTS line modes
** Tags added: i386
** Tags removed:
I think the patch is discussed here:
https://patchwork.kernel.org/patch/139191/
and
http://www.spinics.net/lists/linux-wireless/msg58213.html
See also later discussion of a further series of patches for this hardware
http://www.spinics.net/lists/linux-wireless/msg58361.html
--
rtl8187
Public bug reported:
Binary package hint: ubuntu-docs
This is a report about help.ubuntu.com/community/Kernel/Compile.
I didn't just dive in and change it because I wanted to check I wasn't making
things worse.
If you think I'm right let me know I'll go fix the page.
I think the information
Further checking. Below is the output of
cat /proc/version_signature' and whether the device works:
Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5 OK
Ubuntu 2.6.32-24.43-generic 2.6.32.15+drm33.5 OK
Ubuntu 2.6.32-25.45-generic 2.6.32.21+drm33.7 BAD
These are all i386 kernels.
--
FTDI based
A bit of eyeball comparison of the repository for the two kernels
suggests two commits that might be at fault - just because the changes
occur in the right time frame, it's hard to see why they could cause the
problem.
http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-
I'm still seeing occasional unsupported jumbo messages, but the card does
appear to work fairly reliably,
I have not seen it fall over in days. Thanks Maxim. I haven't made speed tests
but it's not irritatingly slow.
Not seeing any noise floor messages.
$ uptime
21:17:49 up 2 days, 11:48, 7
PS. this host is running 'lucid'.
--
ath5k : disconnection / slow network - unsupported jumbo error
https://bugs.launchpad.net/bugs/369005
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I have one of these devices too:
$ lsusb
Bus 005 Device 002: ID 0403:6001 Future Technology Devices International, Ltd
FT232 USB-Serial (UART) IC
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID
** Attachment added: strace.digitemp.2.6.32-25-generic
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/655868/+attachment/1681322/+files/strace.digitemp.2.6.32-25-generic
--
FTDI based USB to serial adapter no longer works
https://bugs.launchpad.net/bugs/655868
You received this bug
** Attachment added: strace.digitemp.works.2.6.32-22-generic
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/655868/+attachment/1681323/+files/strace.digitemp.works.2.6.32-22-generic
--
FTDI based USB to serial adapter no longer works
https://bugs.launchpad.net/bugs/655868
You received
I tried the debug test above.
# uname -a
Linux ubuntu 2.6.32-25-generic #44-Ubuntu SMP Fri Sep 17 20:26:08 UTC 2010 i686
GNU/Linux
# modprobe -r firewire-ohci
# modprobe firewire-ohci debug=-1
dmesg shows
[170508.165254] firewire_ohci :04:00.0: PCI INT A - GSI 16 (level, low) -
IRQ 16
Since Stefan mentioned h/w failure, I changed which port I was using on the
firewire card.
Interesting results. It appears one of the ports on the card is faulty, while
the other is ok.
Sorry for the noise. Results appended below in case they are helpful.
$ uname -a
Linux ubuntu
I got some feedback that the quirks entries were only added in 2.6.34.
I tried copying some data to a disk containing an ext3 filesystem, connected
via this firewire card.
Worked fine.
$ uname -a
Linux ubuntu 2.6.32-25-generic #44-Ubuntu SMP Fri Sep 17 20:26:08 UTC 2010 i686
GNU/Linux
$ lsmod
This affects Lucid as well. Since this is a long-term release it would
be nice if we could figure out a way forward for users of firewire
cameras (and Kino).
I have a Sony DSR-PDX10P. In Karmic I was able to use Kino to capture
DV, it worked reasonably well.
I upgraded to Lucid a couple of
Despite the reassurances about bus reset loops in
https://ieee1394.wiki.kernel.org/index.php/Release_Notes#Linux_2.6.35 it
appears there is some work for upstream to do here.
I found http://user.in-berlin.de/~s5r6/linux1394/utils/ and ran the
test_cycle_time_v20100125.c utility.
This reports:
I omitted to remove the needs-upstream-testing tag, I'm not that
familiar with all the LP functions.
I noted in the bug I that tested with linux-image-2.6.35-020635rc1-generic.
That has the same problems.
I tested again, with
This bug affected me on Lucid as well.
$ apt-show-versions |grep ssh
openssh-client/lucid-updates uptodate 1:5.3p1-3ubuntu4
openssh-server/lucid-updates uptodate 1:5.3p1-3ubuntu4
ssh-askpass-gnome/lucid-updates uptodate 1:5.3p1-3ubuntu4
$ grep X11 /etc/ssh/sshd_config
X11Forwarding yes
p.s.
I was able to connect to other servers and tunnel X11 to them, at the same time
as I was experiencing this issue with lucid.
$ grep -i family /etc/ssh/sshd_config
$
$ grep 127 /etc/hosts
127.0.0.1 localhost
127.0.1.1 ubuntu
$ ifconfig lo
loLink encap:Local Loopback
This bug affected me on Lucid as well.
$ apt-show-versions |grep ssh
openssh-client/lucid-updates uptodate 1:5.3p1-3ubuntu4
openssh-server/lucid-updates uptodate 1:5.3p1-3ubuntu4
ssh-askpass-gnome/lucid-updates uptodate 1:5.3p1-3ubuntu4
$ grep X11 /etc/ssh/sshd_config
X11Forwarding yes
p.s.
I was able to connect to other servers and tunnel X11 to them, at the same time
as I was experiencing this issue with lucid.
$ grep -i family /etc/ssh/sshd_config
$
$ grep 127 /etc/hosts
127.0.0.1 localhost
127.0.1.1 ubuntu
$ ifconfig lo
loLink encap:Local Loopback
Went back to 2.6.32-22-generic, since that fixed other issues
(LP:459732).
I installed linux-image-2.6.32-22-generic (version 2.6.32-22.36) and
linux-backports-modules-wireless-2.6.32-33-generic (version 2.6.32-22.13) and
rebooted, then selected
this kernel from the grub list.
The same failure
Public bug reported:
I have a Netgear WG111(v3) USB dongle, lsusb id is 0846:4260.
The device is configured with a static IP address, and connects to an access
point using WEP encryption.
The machine it is connected to is a Dell PC, located under a desk. Normally
nobody is logged in via GDM,
** Attachment added: AlsaDevices.txt
https://bugs.launchpad.net/bugs/625265/+attachment/1522758/+files/AlsaDevices.txt
** Attachment added: AplayDevices.txt
https://bugs.launchpad.net/bugs/625265/+attachment/1522759/+files/AplayDevices.txt
** Attachment added: ArecordDevices.txt
I don't see what more I can say but here goes:
* This machine is a clean install of lucid, I did not dist-upgrade from karmic.
* Before upgrading, to keep the network up some of the time I had a cron job
that did
'ifdown wlan1 sleep 10 ifup wlan1'
every 4 minutes (the disassociation
This appears to be fixed for me, after the following upgrades (excerpted
from /var/log/apt/history.log)
Install:
linux-headers-2.6.32-22 (2.6.32-22.33),
linux-image-2.6.32-22-generic (2.6.32-22.33),
linux-backports-modules-wireless-2.6.32-22-generic (2.6.32-22.13)
The comment about not installing the package at all is odd. I didn't manually
select the package for installation.
As far as I can tell it's part of the default install. I installed the Ubuntu
Studio flavour, so perhaps that's why it is still being installed. I've been
dist-upgrading every few
*** This bug is a duplicate of bug 574067 ***
https://bugs.launchpad.net/bugs/574067
Setting this to duplicate status is wrong.
I reported this bug because the documentation was at odds with what I saw in
the tool.
So with the new information that the tool was changed on purpose (was this
$ apt-show-versions gnome-nettool
gnome-nettool/lucid uptodate 2.30.0-0ubuntu1
--
gnome-nettool: does not show 'connections' tab
https://bugs.launchpad.net/bugs/566811
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I don't understand why you think this is incomplete.
1. I already gave you this.
2. Let me spell it out for you:
I opened the tool and expected to see four tabs, as is documented in the
help pages for the tool.
3. Again, rehashing what I already told you:
Instead, I see three tabs,
Public bug reported:
Binary package hint: gnome-nettool
running ubuntustudio lucid/i386, up to date as at 2010-04-20.
In the desktop I go to System-Administration-Network.
The gnome-nettool opens. It shows 'General', 'DNS' and 'Hosts' info, all
correct.
There is no Connections tab. The help
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/44835510/Dependencies.txt
--
does not show 'connections' tab
https://bugs.launchpad.net/bugs/566811
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I am seeing similar things.
$ lsb_release -rd
Description:Ubuntu lucid (development branch)
Release:10.04
$ uname -a
Linux ubuntu 2.6.32-21-generic #32-Ubuntu SMP Fri Apr 16 08:10:02 UTC 2010 i686
GNU/Linux
$ lsusb
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus
PS. There is nothing wrong with the access point I am using, the other
machines on the network (including one sitting on the desk the affected
machine is located under) don't see this problem.
--
wireless internet problem on WG111v3 (RTL8187b)
https://bugs.launchpad.net/bugs/459732
You received
** Summary changed:
- does not show 'connections' tab
+ gnome-nettool: does not show 'connections' tab
--
gnome-nettool: does not show 'connections' tab
https://bugs.launchpad.net/bugs/566811
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Rob's fix went in to v4l as this commit:
http://git.linuxtv.org/v4l-
dvb.git?a=commit;h=0bc3518019f917a370935055f07698a4e9b3ea20
It was added to the karmic kernel git in January:
Hi Damien
are you using stock ubuntu or did you compile more recent v4l-dvb
drivers yourself?
Could you post dmesg output from booting up the working version?
It would be particularly helpful if you could boot, then try to tune the
receiver with dvbscan or equivalently try to watch live tv in
I was able to get 2.6.31-14-generic to boot. I did not try tuning with this, I
doubt it will make any difference.
I tried building the v4l tree:
$ cd v4l-dvb
$ make update; make ;
The build dies on the FiredTV driver for some reason, so turn it off.
$ sed -ie
** Attachment added: strace of dvbscan, with 2.6.31-14-generic + v4l tip
drivers
http://launchpadlibrarian.net/34749121/log.dvbscan.20091031
--
regression: support for dvico dual digital 4 card
https://bugs.launchpad.net/bugs/459523
You received this bug notification because you are a
Hi Bob
it would probably help people processing this report quite a bit to have the
output of a working Jaunty system.
Could you post 'dmesg' from the following sequence of events:
* disable mythtv if you have it installed (rename the /etc/init.d scripts)
* shut down, pull the power.
* boot
Found a simple workaround:
{{{
$ sudo dpkg-reconfigure linux-image-2.6.31-14-generic
Running depmod.
update-initramfs: Generating /boot/initrd.img-2.6.31-14-generic
Not updating initrd symbolic links since we are being updated/reinstalled
(2.6.31-14.48 was configured last, according to dpkg)
Not
Public bug reported:
Binary package hint: linux-image
Hi
symptom:
I have two dvico cards in this machine, dual digital4 and dual digtial express,
see lspci data.
Both work on 'hardy', with v4l modules from the v4l mercurial repository. I'll
provide more details of that setup
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/34302610/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/34302611/AplayDevices.txt
** Attachment added: ArecordDevices.txt
http://launchpadlibrarian.net/34302612/ArecordDevices.txt
and kept the syslog of what occured then (syslog.dvbscan).
it stops when I typed 'halt'.
** Attachment added: syslog.dvbscan
http://launchpadlibrarian.net/34306522/syslog.dvbscan
--
regression: support for dvico dual digital 4 card
https://bugs.launchpad.net/bugs/459523
You received this
I tried stracing the dvbscan, see attached (log.dvbscan)
** Attachment added: log.dvbscan
http://launchpadlibrarian.net/34306455/log.dvbscan
--
regression: support for dvico dual digital 4 card
https://bugs.launchpad.net/bugs/459523
You received this bug notification because you are a
details of the working system:
it's the same hardware, with an earlier version of ubuntu installed on a
separate hard disk.
$ uname -a
Linux wellington 2.6.24-23-rt #1 SMP PREEMPT RT Wed Apr 1 23:40:34 UTC 2009
i686 GNU/Linux
The kernel I am using is linux-image-2.6.24-23-rt, package version
regarding the rmmod/modprobe experiment I described. The module is of
course dvb_usb_cxusb, not 'cxusb'.
--
regression: support for dvico dual digital 4 card
https://bugs.launchpad.net/bugs/459523
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
/etc/lsb-release for working system:
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=8.04
DISTRIB_CODENAME=hardy
DISTRIB_DESCRIPTION=Ubuntu 8.04.3 LTS
--
regression: support for dvico dual digital 4 card
https://bugs.launchpad.net/bugs/459523
You received this bug notification because you are a member of
{{{
$ sudo blkid -p /dev/sdb1
/dev/sdb1: LABEL=newroot UUID=9ecccb04-4b5b-4017-a49d-80dca283631d
VERSION=1.0 TYPE=ext4 USAGE=filesystem
The system has /, swap and an LVM partition for /usr, /var, /home, etc.
sudo fdisk -l /dev/sdb
Disk /dev/sdb: 1500.3 GB, 1500301910016 bytes
255 heads, 63
system is also able to boot an old setup (hardy) on the other hard disk.
--
grub misconfigured after upgrade to linux-image-2.6.31-14-generic
https://bugs.launchpad.net/bugs/454418
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Managed to get some more detailed info.
grub versions: grub* got upgraded along with the kernel.
{{{
grep grub /var/log/dpkg.log
2009-10-18 12:06:48 upgrade grub-pc 1.97~beta3-1ubuntu8 1.97~beta4-1ubuntu2
2009-10-18 12:06:48 status half-configured grub-pc 1.97~beta3-1ubuntu8
2009-10-18 12:06:48
** Attachment added: version of the working kernel
http://launchpadlibrarian.net/33871490/version.log
--
grub misconfigured after upgrade to linux-image-2.6.31-14-generic
https://bugs.launchpad.net/bugs/454418
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Attachment added: dmesg from a cold boot of the working kernel
http://launchpadlibrarian.net/33871571/dmesg.log.gz
--
grub misconfigured after upgrade to linux-image-2.6.31-14-generic
https://bugs.launchpad.net/bugs/454418
You received this bug notification because you are a member of
Managed to get some more detailed info.
grub versions: grub* got upgraded along with the kernel.
{{{
grep grub /var/log/dpkg.log
2009-10-18 12:06:48 upgrade grub-pc 1.97~beta3-1ubuntu8 1.97~beta4-1ubuntu2
2009-10-18 12:06:48 status half-configured grub-pc 1.97~beta3-1ubuntu8
2009-10-18 12:06:48
** Attachment added: hardware summary from lspci
http://launchpadlibrarian.net/33871581/lspci-vnvn.log
--
grub misconfigured after upgrade to linux-image-2.6.31-14-generic
https://bugs.launchpad.net/bugs/454418
You received this bug notification because you are a member of Ubuntu
Bugs,
I got a crash report on upgrading from 1.21 to 1.24 (along with a heap - about
2weeks of updates).
I started the upgrade at about 2009-10-18T00:30:00 GMT, local time 11:30.
dpkg.log contained this
{{{
2009-10-18 12:06:19 upgrade linux-firmware 1.21 1.24
2009-10-18 12:06:19 status half-configured
Public bug reported:
Binary package hint: grub-pc
What happened:
I was running linux-image-2.6.31-13-generic. I upgraded to
linux-image-2.6.31-14-generic using
sudo aptitude safe-upgrade
There was a minor issue with linux-firmware which might be related, but a
second safe-upgrade fixed the
I should have added to 'what happened'
- from the initramfs shell, I halted the machine
- power off, wait, power on.
- boot 2.6.31-13-generic - it booted fine.
I did not gather a lot more detail as I was looking at other issues when
this cropped up.
--
grub misconfigured after upgrade to
The boot line in syslog (from the working kernel) is
Linux version 2.6.31-13-generic (bui...@rothera) (gcc version 4.4.1 (Ubuntu
4.4.1-4ubuntu7) ) #43-Ubuntu SMP Fri Oct 9 17:42:36 UTC 2009 (Ubuntu
2.6.31-13.43-generic)
--
grub misconfigured after upgrade to linux-image-2.6.31-14-generic
Public bug reported:
Binary package hint: cups
This is probably the same underlying issue as
https://bugs.launchpad.net/bugs/304039, but I see different symptoms.
My system is currently working ok but the upgrade process was not as smooth as
it should be.
I did a 'sudo aptitude update; sudo
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/20587133/Dependencies.txt
** Attachment added: DpkgTerminalLog.gz
http://launchpadlibrarian.net/20587134/DpkgTerminalLog.gz
--
cupsd fails to restart on upgrade
https://bugs.launchpad.net/bugs/309877
You received this
The system was under heavy CPU load at the time (numerical simulations).
Not sure if that's relevant, hopefully not.
--
cupsd fails to restart on upgrade
https://bugs.launchpad.net/bugs/309877
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
version is 2.0.6-2 on i386.
System is running the Intrepid release, all packages up to date.
I was connected to an HTTPS site. After a few form submissions, the browser
crashes and burns,
On the terminal I launched the program from was this message:
pure virtual method
As I was attempting (in galeon) to add an 'Also affects project' link, I got
_another_ crash.
This time the error from galeon as 'Segmentation fault'.
I haven't seen this behaviour before, the machine has been quite
stable since the release in October, even though I have been updating
regularly
The 'Also affects project' link was new to me, I thought it was a way to
flag the same bug affects other packages.
I can't see any need to link this to upstream projects at this time.
The other packages I noticed this affecting were
epiphany-browser2.24.1-0ubuntu1
firefox
ugh - i hate launchpad. it just lost my entire post.
I went back through my notes. They leave a little to be desired...
At the time I installed the mythtv metapackage, I did not have support for my
DVB-T card working.
It is a Dvico model that is not yet supported by the mainline v4l tree. (I
I tried a complete purge/reinstall cycle.
$ sudo aptitide --purge remove mythtv
$ sudo aptitude --purge remove mythtv-backend
$ sudo aptitude --purge remove mythtv-frontend
$ sudo aptitude --purge remove mythtv-common
$ sudo aptitude update
$ sudo aptitude upgrade
$ sudo aptitude install mythtv
$
Public bug reported:
Binary package hint: mythtv-backend
$ dpkg -l mythtv-backend
ii mythtv-backend 0.21.0+fixes16838-0 A personal video recorder
application (server)
$ lsb_release -rd
Description:Ubuntu 8.04
Release:8.04
what happens - I cannot complete the configuration of
$ sudo aptitude --purge remove mythtv-database
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
Building tag database... Done
The following packages are BROKEN:
Public bug reported:
Summary:
On install I get an error message about an invalid group, which seems incorrect.
The actual problem is the /dev device is not created.
Possibly because there is a missing 'modprobe' call?
Here's what actually happened:
$ sudo apt-get upgrade
(nothing to do)
$ sudo
I had the same error as the initial report.
However when trying to install the .deb by force, I get further errors, see
below.
So that method won't work for all cases.
$ sudo dpkg -i --force-overwrite
/var/cache/apt/archives/cupsys_1.3.2-1ubuntu4_i386.deb
(Reading database ... 162129 files and
Public bug reported:
Binary package hint: python2.5-dbg
Version: 2.5-2ubuntu2
Severity: normal
Hi,
this was a problem with TeTex for a while too, but they worked around it.
The /usr/local partition is an NFS mount and is not writeable by all hosts,
including the one showing this issue.
I can
Public bug reported:
This occurred on a machine that has been dist-upgraded from
breezy to etch and all the points in between, with official sources.
If apport is installed, the /etc/cron.daily/apport script tries to run
a find over /var/crash and that directory may not actually be there.
This
94 matches
Mail list logo
