I got this error after an upgrade to hardy-backports and hardy-proposed
and found this ticket while troubleshooting.
My solution was to remove the display device, start the VM headless, and
then re-add the display device. This seemed to cleanup the virt-manager
configuration file. I didn't have
This is the change in Jaunty that seems to have broken sl-modem:
https://launchpad.net/ubuntu/+source/sl-modem/2.9.11~20080817-3ubuntu2
--
no more /dev/ttySL0 device node
https://bugs.launchpad.net/bugs/375148
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
If sl-modem was working for you properly in Hardy or Intrepid, then the
easy solution for Jaunty is to restore the modprobe file. (Look for the
file attached to this comment.)
The proper fix is likely a new udev rule.
** Attachment added: "/etc/modprobe.d/sl-modem.conf"
http://launchpadlibrar
I've tried the patch, confirmed that it works on Jaunty i386 and Jaunty
amd64 with Asterisk, and uploaded a fixed package to my PPA at:
https://launchpad.net/~dajhorn/+archive/ppa
--
build zaptel against kernel 2.6.28
https://bugs.launchpad.net/bugs/353024
You received this bug notification becau
This bug persists on the Lenovo ThinkPad T61 even with the 64-bit linux-
backports-modules-jaunty package.
However, I've got two T61 computers, and the hang only happens for me on
the computer with the offboard Nvidia 140M video card. The hang seems
much more frequent with the closed Nvidia drive
This bug got fixed in the Intrepid beta. I'm getting desirable behavior
from the latest Evolution 2.24.0 packages.
--
warnings about bad SSL certificate when viewing mail
https://bugs.launchpad.net/bugs/19065
You received this bug notification because you are a member of Ubuntu
Bugs, which is a
The Evolution 2.24.0-0ubuntu2 package still has this bug. I did an
upgrade from Hardy to the Intrepid beta today and all of my IMAP
accounts got the double message glitch. (My IMAP server is Courier.)
--
Evolution doesn't refresh the INBOX folder
https://bugs.launchpad.net/bugs/265043
You recei
Per the duplicate ticket, this was the fix for me:
1. Click "Folder" -> "Subscriptions".
2. Choose the IMAP account from the "Server" pulldown menu.
3. Uncheck the "Inbox" folder.
4. Click the "Close" button.
5. Restart Evolution.
The Inbox folder will be automatically resubscribed and correctly
I tried the PPA package on the first Ubuntu Intrepid beta, but sl-modem
fails to start with this error message:
$ sudo /etc/init.d/sl-modem-daemon start
Only access through ALSA is available on amd64 but slamr driver was chosen!
Make sure that an ALSA driver for your chipset is available and is lo
I can confirm this bug with a Treo 650 and the first Intrepid 64-bit
beta on amd64.
Rebooting into a 32-bit i386 environment on the same computer results in
proper behavior.
--
[intrepid] impossible to sync palm pilot device
https://bugs.launchpad.net/bugs/282491
You received this bug notificati
** Attachment added: "reportbug-gnome-pilot_amd64.txt"
http://launchpadlibrarian.net/18514222/reportbug-gnome-pilot_amd64.txt
--
[intrepid] impossible to sync palm pilot device
https://bugs.launchpad.net/bugs/282491
You received this bug notification because you are a member of Ubuntu
Bugs, w
** Attachment added: "reportbug-gnome-pilot_i386.txt"
http://launchpadlibrarian.net/18514236/reportbug-gnome-pilot_i386.txt
--
[intrepid] impossible to sync palm pilot device
https://bugs.launchpad.net/bugs/282491
You received this bug notification because you are a member of Ubuntu
Bugs, whi
Calling this a VMware bug is unfair because:
* The kernel KConfig for the new driver (at line 93) recommends
linking /dev/rtc to the new character device for backwards
compatibility, which Intrepid does not do.
* The legacy /dev/rtc device has not been deprecated in either the Intrepid
man p
Ubuntu Intrepid removes a traditional interface that breaks popular
software, so the pertinent issue is backwards compatibility.
Whether /dev/rtc0 and /dev/rtc1 are identical or different is irrelevant
to the person using the computer because either would be adequate for
software that expects the
> We would want to make sure that /dev/rtc pointed to the same real time
clock after each reboot
The /dev/rtc0 node is stable because the 2.6.27-7 kernel has
CONFIG_RTC_DRV_CMOS=y and all others set =m. Thus, rtc-cmos.c is always
initialized before any other rtc-*.c module, and it creates only on
This bug persists in Hardy with Evolution 2.22.3.1, and it looks like
Intrepid could have it too.
I've attached a screenshot to complement the text attachment.
** Attachment added: "Screenshot Evolution Warning Signature Bad.png"
http://launchpadlibrarian.net/18165168/Screenshot%20Evolution%2
I can confirm this bug with 2.6.24-18-xen and 2.6.24-19-xen on a late
Pentium D. It usually happens within two days of runtime when the
system is loaded. My cpuinfo is attached.
This glitch on my computer usually trashes I/O and results in several
"faulty removed" components in MD arrays.
** A
I can confirm the bug. I am trying the patch now.
--
lshw -xml reporting invalid xml
https://bugs.launchpad.net/bugs/241675
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
https:
All of my affected computers are stable with Karmic. It looks like
Jaunty got a dud update sometime in mid-June that is causing instability
on this kind of computer.
--
Lenovo X61 hangs with flashing caps lock LED.
https://bugs.launchpad.net/bugs/303276
You received this bug notification because
This hook patch is needed to run backported kernels on Hardy systems
with root-in-lvm and partitionless PVs because Ubuntu kernels after
2.6.24 need "sysfs_scan = 0" set in the lvm.conf file. Without it, a
Hardy system can hang at the "waiting for root file system" boot
message.
The change that w
This bug persists in the latest 2.6.24-24-xen kernel package that was
recently released for Hardy running in a domU on an Intel Xeon CPU
L5335.
I can provoke the crash by downloading something with wget that pins the
ethernet interface.
--
xen dom0 crashes with "BUG: soft lockup - CPU#0 stuck fo
The 2.6.17-7 kernel in Edgy has a similar glitch with the sl-modem-
source 2.9.10+2.9.9d+e-pre2-5build1 package.
--
kernel module not working with kernel 2.6.15
https://launchpad.net/bugs/31640
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ub
Public bug reported:
The Smart Link modem kernel module fails to build for 2.6.17-8-generic
and 2.6.17-8-386 in Ubuntu Edgy. A module-assistant log file is
attached.
The last error is:
/usr/src/modules/sl-modem/drivers/amrmo_init.c:704: error: expected ‘)’
before string constant
** Affects: sl
** Attachment added: "sl-modem-source.buildlog.2.6.17-8-generic.1158872716"
http://librarian.launchpad.net/4391184/sl-modem-source.buildlog.2.6.17-8-generic.1158872716
--
sl-modem-source fails to build through module-assistant in Edgy 6.10
https://launchpad.net/bugs/61749
--
ubuntu-bugs ma
Yes, as 61749.
https://launchpad.net/distros/ubuntu/+source/sl-modem/+bug/61749
--
kernel module not working with kernel 2.6.15
https://launchpad.net/bugs/31640
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
This bug is in Edgy, and this patch also fixes it. (Thanks.)
--
Encoding progress always zeros
https://launchpad.net/bugs/39076
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
The sl-modem-source is still broken and fails to build against the
current 2.6.17-10 kernel.
The kludges suggested in this ticket (and other related tickets) do not
work for me on Ubuntu Edgy.
--
sl-modem-source fails to build through module-assistant in Edgy 6.10
https://launchpad.net/bugs/6174
Note that Canonical partner repo for Gutsy does not contain the VMware
Server packages.
However, the upstream VMware Server 1.0.4 tarball installs properly on
Ubuntu Gutsy, but it is not managed by the packaging system, so you'll
need to run the vmware-config.pl script manually after each kernel
u
I can confirm that this bug happens during the upgrade to Feisty for
i386 and amd64 computers, and that the given patch fixes both.
The upgrade from Edgy to Feisty will break any computer that has an EVMS
root. The severity of the bug should be increased because it makes
affected computers unboot
The nvidia-glx package is also broken on Dell Latitude laptops with the
Nvidia GeForce 440 Go video card. The open "nv" driver successfully
probes the EDID, whereas the closed "nvidia" driver says:
(WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
The result is a black screen.
Sitsofe: You are correct, this is a duplicate of Bug #82312.
The solution was to add this line to the Screen section of the
/etc/X11/xorg.conf file:
Option "UseDisplayDevice" "DFP"
--
using nvidia-glx drivers on toshiba satellite 1410 freezes
https://bugs.launchpad.net/bugs/35251
You received
This patch against the unpacked lshw_02.12.01-2.dsc source package
restores user privacy to the lshw program.
** Attachment added: "lshw 02.12.01 privacy patch"
http://launchpadlibrarian.net/12088009/lshw-02.12.01-privacy.patch
--
lshw 02.12.01 phones home
https://bugs.launchpad.net/bugs/1933
Public bug reported:
Binary package hint: lshw
The lshw 02.12.01 program that was recenty added to Ubuntu Hardy phones
home to when you ask for its version number.
Running `lshw -version` results in a query to the ezix.org domain.
The first problem with this behavior is that silent network acti
Does this patch fix the lshw hang?
The lshw program can loop forever if it does not recognize a PCI
capability, or if it gets garbage from sysfs.
** Attachment added: "lshw bogus capability handler"
http://launchpadlibrarian.net/13543177/lshw-02.11.01-bogus_capability.patch
--
lshw hangs on
> Was this a regression from Gutsy, or what's going on?
No, this bug exists in Gutsy too, but it may not express on your
hardware.
> It still waits for a while (perhaps approx 30 seconds) on PCI
This is normal.
> Thanks... Can we get this into Hardy?
Hardy could be released next week, so pro
> Perhaps we could get it into a backport for hardy considering it's a
LTS release?
Ensure that it gets fixed early in the hardy+1 development so that it
can be a backport candidate.
Upstream may already have a fix for this bug here:
http://www.ezix.org/project/ticket/340
> does this indicat
*** This bug is a duplicate of bug 202460 ***
https://bugs.launchpad.net/bugs/202460
** This bug has been marked a duplicate of bug 202460
Hardware Testing app hangs
--
lshw hangs on "PCI (sysfs)"
https://bugs.launchpad.net/bugs/218864
You received this bug notification because you are a
** Also affects: lshw via
http://www.ezix.org/project/ticket/340
Importance: Unknown
Status: Unknown
--
Hardware Testing app hangs
https://bugs.launchpad.net/bugs/202460
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ub
I'm getting the same glxinfo crash on a Dell D600 running the latest
Hardy beta release. My hardware line is:
(--) PCI:*(1:0:0) ATI Technologies Inc Radeon RV250 [Mobility FireGL
9000] rev 1, Mem @ 0xe800/27, 0xfcff/16, I/O @ 0xc000/8
--
[via] glxinfo crashed with SIGSEGV in viaXMesaWin
My fix for the Firefox 3 slow scrolling glitch on Ubuntu 8.04 Hardy was
to re-add this section to my /etc/X11/xorg.conf file after running in
safe mode:
Section "Module"
Load "dbe"
Load "extmod"
Load "fbdevhw"
Load "glx"
Load "record"
Load "fre
I had this bug on several laptop computers upgraded to Gutsy. Looking
at the output of `trackerd -v 2`, it seems that any home directory with
more than a few hundred files will cause the tracker process to pin
system utilization to 100% and make the computer unusable longer than
most people will w
The latest `update-manager -d` from Feisty is now prompting to remove
the evms packages, but they are not completely removed, so the user must
still manually remove the evms packages.
--
Device-mapper errors: dm-linear, lookup failed
https://bugs.launchpad.net/bugs/115616
You received this bug no
I found this closed bug on Google while trying to troubleshoot the same
issue. I can confirm that it happens randomly.
Switching to a virtual console and back with CTRL+ALT+F2 and CTRL+ALT+F7
causes metacity to resume normal behavior.
--
maximize/minimize unresponsive
https://bugs.launchpad.net
This also happens while trying to install Ubuntu Feisty on a stock Dell
PowerEdge 2650.
--
[feisty] installer reports I/O error dev fd0
https://bugs.launchpad.net/bugs/97306
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubunt
I've got a computer that always expresses this bug, perhaps because the
filesystem is XFS. Let me know if I can help test a fix.
--
snapshot creation failure race "in use: not deactivating"
https://bugs.launchpad.net/bugs/105936
You received this bug notification because you are a member of Ubun
My comment about XFS was mistaken. The glitch can be reliably
reproduced only because I am trying to create very large snapshots. I'm
getting the same race condition with small snapshots.
--
snapshot creation failure race "in use: not deactivating"
https://bugs.launchpad.net/bugs/105936
You rec
*** This bug is a duplicate of bug 132320 ***
https://bugs.launchpad.net/bugs/132320
** This bug has been marked a duplicate of bug 132320
Tracker consumes more then 90% of CPU even when indexing is disabled
--
trackerd eating CPU and memory
https://bugs.launchpad.net/bugs/130817
You rece
*** This bug is a duplicate of bug 132320 ***
https://bugs.launchpad.net/bugs/132320
Why was this bug hidden from the public? -- I'm relating it to #132320
so that it doesn't fall out of the Launchpad database so early.
The behavior of trackerd makes the Gutsy slow and unresponsive on many
co
Public bug reported:
Binary package hint: drip
The drip-0.9.0 package fails to build from source on Gutsy as of Friday
September 14th 2007.
The error is:
checking for Avifile version 0.7.34... found (not)
configure: error:
You need Avifile 0.7.34 or higher, but less than 9.9.9, to build D
Invoking dpkg-buildpackage directly results in fewer libtool and
autoconf warnings.
** Attachment added: "apt-get source --compile drip"
http://launchpadlibrarian.net/9283933/out.txt
--
Drip ftbs in Gutsy with libavi version error
https://bugs.launchpad.net/bugs/139670
You received this bug n
The drip-0.9.0 package now compiles cleanly against the
avifile-0.7.47-20070718-1ubuntu2 package.
--
Drip ftbs in Gutsy with libavi version error
https://bugs.launchpad.net/bugs/139670
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
> I'm closing this bug report, since this is a development version of
Ubuntu, and it's likely to eat your dog or fire your house at some point
;)
Gutsy beta freeze is happening in two days and general release is less
than a month away. The system should be stable and working properly for
most peo
I've got one computer that still expresses this bug with the latest
Feisty updates. On this computer, there is a 25% chance that the
snapshot creation will fail.
Package revisions on the affected computer are:
dmsetup 2:1.02.08-1ubuntu10
libdevmapper1.02 2:1.02.08-1ubuntu10
lvm-common 1
** Attachment added: "dmesg (Pentium-D 930 cpu on an E7230 motherboard)"
http://launchpadlibrarian.net/9123542/dmesg-moxo.txt
--
[feisty] failures when creating snapshots "in use: not deactivating"
https://bugs.launchpad.net/bugs/84672
You received this bug notification because you are a memb
** Attachment added: "lvcreate verbose output"
http://launchpadlibrarian.net/9123543/lvcreate-bug84672.txt
--
[feisty] failures when creating snapshots "in use: not deactivating"
https://bugs.launchpad.net/bugs/84672
You received this bug notification because you are a member of Ubuntu
Bugs,
** Attachment added: "fstab for the affected computer"
http://launchpadlibrarian.net/9123548/fstab
--
[feisty] failures when creating snapshots "in use: not deactivating"
https://bugs.launchpad.net/bugs/84672
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I had this bug happen to me when I did some Feisty to Gutsy upgrades
this weekend. The MD UUIDs are correct in the
initrd.img-2.6.22-14-generic files, but the scripts are not assembling
the arrays.
The computers with the bug are panic'ing into "VFS: Cannot mount root
filesystem" without providing
The patch never made it into Ubuntu 7.10, so this problem persists with
VMware Player, VMware Workstation, and VMware Server running on Gutsy.
--
vmware and hibernation don't play nicely together
https://bugs.launchpad.net/bugs/18180
You received this bug notification because you are a member of
How is the given patch inadequate? The patch removes the code that
causes lshw to get linked, unnecessarily, to network libraries.
What information is missing? You pasted a form letter and closed the
ticket without actually asking for anything.
--
lshw 02.12.01 phones home
https://bugs.launchp
Public bug reported:
Binary package hint: lshw
Running `lshw -version` results in a query to the ezix.org domain. This
behavior was noticed during a security audit. Please engage me in
discussion on this ticket before closing it or marking it invalid.
The attached `tcpdump` transcript is a con
** Attachment added: "tcpdump transcript of lshw phoning home"
http://launchpadlibrarian.net/12951527/tcpdump-lshw.txt
--
lshw 02.12.01-2 phones home (with tcpdump example)
https://bugs.launchpad.net/bugs/208399
You received this bug notification because you are a member of Ubuntu
Bugs, which
This issue was first opened as Bug #193373.
--
lshw 02.12.01-2 phones home (with tcpdump example)
https://bugs.launchpad.net/bugs/208399
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.ubunt
This dpatch removes the code from lshw that contacts the upstream
developer.
There is no reason for the lshw program to make network calls to a hard-
coded name.
** Attachment added: "lshw-02.12.01/debian/patches/09-lshw-privacy.dpatch"
http://launchpadlibrarian.net/12951816/09-lshw-privacy.dp
You got NMU'd.
Please review and comment on patches in the future.
--
lshw 02.12.01 phones home
https://bugs.launchpad.net/bugs/193373
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
Fixed and released in Bug #208399.
--
lshw 02.12.01 phones home
https://bugs.launchpad.net/bugs/193373
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
https://lists.ubuntu.com/mai
I will not have time to verify the fix until next week.
Please close this bug. I will reopen it if the glitch persists.
--
Horde_Block_kronolith_tree_alarms not found
https://bugs.launchpad.net/bugs/51023
You received this bug notification because you are a member of Ubuntu
Bugs, which is the b
** Attachment added: "Reportbug output for dh-make-php."
http://librarian.launchpad.net/7031055/reportbug.txt
--
dh-make-php_0.1.3: dh-make-pecl fails to build all packages
https://launchpad.net/bugs/97240
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mai
Public bug reported:
Binary package hint: dh-make-php
The dh-make-pecl script in dh-make-php_0.1.3_all.deb fails to build any
PECL modules on my Ubuntu Edgy computer. The errors are all of the
form:
$ dh-make-pecl dbx
downloading dbx-1.1.0.tgz ... Starting to download dbx-1.1.0.tgz (30,872 byte
SpeedStep in a similar Dell C800 cannot be enabled in Edgy. Most of the
CPUs that were shipped with the C800 do not have SpeedStep built-in, so
the 1 GHz Coppermine CPU is a corner case in this laptop model.
Given that SpeedStep is not properly supported on the Dell C800 even in
Microsoft Windows
Public bug reported:
Binary package hint: evms
The stripe unit and stripe width in the XFS superblock is a multiple of
the volume block size, but the EVMS XFS plugin assumes that the volume
block size is the same as the volume sector size.
The bug can be reproduced like this:
# mdadm --create
** Attachment added: "XFS stripe reporting patch for EVMS 2.5.5"
http://librarian.launchpad.net/6342380/evms-2.5.5-xfs_stripe.patch
** Summary changed:
- EVMS reports incorrect stripe unit and stripe width reported for XFS.
+ EVMS reports incorrect XFS stripe unit and width sizes.
--
EVMS r
The is kludge also works with VMware Server Console 1.0.1 for Linux.
You can apply the same change to the /usr/bin/vmware-server-console
file.
--
libhal1 0.5.7.1-0ubuntu8 with new dbus breaks vmware
https://launchpad.net/bugs/59232
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https:
Public bug reported:
Binary package hint: upstart
This upstart configuration file worked in Karmic:
# hvc0.conf
start on stopped rc RUNLEVEL=[2345]
stop on runlevel [!2345]
respawn
exec /sbin/getty -8 38400 hvc0
After the upgrade to Lucid, something is silently moving this file to
/et
** Attachment added: "messages"
http://launchpadlibrarian.net/46777488/messages
--
upstart disables hvc0 getty in Lucid 10.04
https://bugs.launchpad.net/bugs/572708
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mail
** Attachment added: "syslog"
http://launchpadlibrarian.net/46781104/syslog
--
upstart disables hvc0 getty in Lucid 10.04
https://bugs.launchpad.net/bugs/572708
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Attachment added: "initctl-list"
http://launchpadlibrarian.net/46781115/initctl-list
--
upstart disables hvc0 getty in Lucid 10.04
https://bugs.launchpad.net/bugs/572708
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-b
While troubleshooting, I downgraded to linux-image-2.6.31-20-virtual and
upstart-0.6.3-10 from Karmic on both of i386 and amd64, but the problem
persisted.
This makes me think that the glitch is my upstart configuration or udev.
I haven't yet been able to downgrade udev to check because most of th
I've discovered the glitch. This seemingly good file name is actually
bad:
/etc/init/hvc0.conf
Renaming this specific file to any of these names results in the desired
behavior:
/etc/init/hvc1.conf
/etc/init/hvc00.conf
/etc/init/hvc01.conf
/etc/init/bork0.conf
/etc/init/bork00.conf
This is not an Ubuntu bug.
I'm running this domU at Linode. By default, the Linode manager
modifies the Ubuntu system for better Xen compatibility and moves the
hvc0.conf file.
The fix is:
1. Click the Dashboard.
2. Click the Profile.
3. Set "Xenify Distro: No" in the Helper Options.
4.
I got this bug with tftpd-hpa after an upgrade to Lucid. The solution
for me was to add `sleep 10s` to the script stanza in the /etc/init
/tftpd-hpa file.
Running `initctl restart tftpd-hpa` properly starts in.tftpd if it fails
during system startup, so it follows that there could be a race.
Up
BTW, I'm running tftp-hpa 5.0-11ubuntu2, which is current for Lucid.
This bug seems to depend on the order of network interface plumbing, and
probably expresses more frequently if one interface is configured by
DHCP or is otherwise slow. My guess is that this bug does not express
on computers wit
Public bug reported:
Binary package hint: dahdi-linux
An ubuntu-minimal system cannot install the DAHDI module for Asterisk.
The DKMS build fails with this error message:
make[1]: Entering directory `/usr/src/linux-headers-2.6.31-302-ec2'
awk: line 2: function gensub never defined
scripts/
** Attachment added: "dahdi build transcript"
http://launchpadlibrarian.net/35589406/make.log
--
dahdi-dkms should depend on gawk: "Your awk program does not define gensub"
https://bugs.launchpad.net/bugs/481566
You received this bug notification because you are a member of Ubuntu
Bugs, whic
** Attachment added: "dahdi-linux: Add gawk dependency to dahdi-dkms package."
http://launchpadlibrarian.net/35589475/dahdi-linux-bug481566.patch
--
dahdi-dkms should depend on gawk: "Your awk program does not define gensub"
https://bugs.launchpad.net/bugs/481566
You received this bug notifi
This seems like a regression in Karmic because the -server kernel in
Jaunty had the necessary _XEN kernel configuration for pvops booting. I
was using the linux-server-image package and the upgrade to Karmic broke
all of my 32-bit virtual machines.
The 64-bit kernels in Karmic can still run in a
This bug persists into Ubuntu 10.04 Lucid, but it seems to have changed
slightly.
When the slusb module is loaded on my computer, I get these lines in my
dmesg:
-- ST7554 USB Modem.
-- usbcore: registered new interface driver ST7554 USB Modem
The /dev/slusb0 device node is created, but it is
Note that there are two maildrop providers in Karmic:
* http://packages.ubuntu.com/karmic/maildrop
* http://packages.ubuntu.com/karmic/courier-maildrop
This glitch happens only with the non-courier maildrop package. Any easy fix
for me was:
$ apt-get remove maildrop
$ apt-get install
@rlaager, zed first shipped in the zfsutils package, and the `Replaces`
line was required for a smooth upgrade between releases. It can/should
be dropped now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
Public bug reported:
All `s3cmd` commands fail with a Segmentation Fault on Ubuntu 12.04
Precise Pangolin if `use_https = True` is set in the `$HOME/.s3cfg`
file.
$ apt-cache policy s3cmd
s3cmd:
Installed: 1.0.0-1
Candidate: 1.0.0-1
Version table:
*** 1.0.0-1 0
500 http://us.archi
Public bug reported:
Binary package hint: totem
I have a Panasonic Network camera that provides an authenticated RTSP
video stream.
Totem can play the stream if the username and password are passed in the
URL like this:
$ totem rtsp://me:passw...@netcam/nphMpeg4/g726-640x480
Totem cannot pla
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/693644
Title:
totem doesn't pass RTSP credentials to gstreamer
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mail
Kudos to Aaron at Nvidia for providing excellent ongoing Linux support.
--
ABI change in xorg 1.9 breaks legacy nvidia-96 and nvidia-173 drivers in
Maverick
https://bugs.launchpad.net/bugs/626974
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
I don't see the new 173.14.28 driver in the Ubuntu x-swat queue, so I
updated the nvidia-173 package and put it here:
https://launchpad.net/~dajhorn/+archive/x-updates/
This updated Nvidia driver is compatible with my 32-bit Ubuntu 10.10
Maverick RC computer where I have older hardware. The 64
Paulo: libssl0.9.7 is incompatible with libssl0.9.8, and the kernel
modules for a gutsy-era VMware Player won't compile for the Maverick
kernel regardless.
The vmware-player package is not currently published in the Ubuntu
partner repository. You'll get a better result installing from
upstream:
*** This bug is a duplicate of bug 674190 ***
https://bugs.launchpad.net/bugs/674190
** This bug has been marked a duplicate of bug 674190
Stuck in Upgrade Loop
* You can subscribe to bug 674190 by following this link:
https://bugs.launchpad.net/ubuntu/+source/adobeair/+bug/674190/+subscr
This problem resolved for me on several computers when I installed the
stable xorg stack from the x-updates ppa:
https://launchpad.net/~ubuntu-x-swat/+archive/x-updates
--
xorg is jerky, uses too much cpu, small display bugs
https://bugs.launchpad.net/bugs/653851
You received this bug notifica
The vmwgfx driver was disabled in Maverick per Bug #606139, and
CONFIG_DRM_VMWGFX is currently disabled in the Natty kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/603599
Title:
Please build
This bug is resolved on my hardware since at least the Maverick release.
Last activity has been more than a year ago, so perhaps this bug should
be closed.
--
Lenovo ideapad S10 internal microphone doesn't work
https://bugs.launchpad.net/bugs/312403
You received this bug notification because you
This non-conformance bug works in both directions, so an easy kludge is
to hard link all file names like this:
$ ln foobar-1.2+baz3_all.deb 'foobar-1.2 baz3_all.deb'
And sync to the s3 bucket normally. Afterwards, the key can be called
through http with a literal "+" character or the "%2B" esca
Public bug reported:
Running `bzr branch lp:ubuntu/precise/mountall` currently returns the
old mountall-2.36 source code, but mountall-2.36.3 is expected because
it is currently published to precise-updates.
LP #714622 suggests a reason for this glitch and a solution for it.
** Affects: mountall
1 - 100 of 172 matches
Mail list logo
