I can reproduce something similar with 8.10 by means of creating a
table, putting the cursor into the table and typing at least one letter
into the table. When moving away from the table to a different page with
the mouse scroll wheel, openoffice goes back to the cursor when pressing
the "save file
I have the same problem that the 3g modem is not detected. See attached
the syslog output when the modem is not detected by network-manager.
Since I cannot post more than one file using the web-gui I will post a
second syslog file in the next message...
** Attachment added: "syslog when 3g fails
It is not always the case that the 3g modem is not detected. See
attached a case when it is successfully detected. As mentioned before
the order of the messages (actions) in the syslog is different. Maybe
this helps to pinpoint the problem.
Other observations:
1) the 3g modem detection appears to
Public bug reported:
I own a N900 and have it attached to my PC in order to charge it and in order
to use it as a UMTS modem.
http://maemo.nokia.com/n900/
Steps to reproduce the bug
1) Start ubuntu without the N900 attached
2) Plug the N900 using the USB cable and put it in "PC Suite Mode"
3) Re
$ lsb_release -rd
Description:Ubuntu 9.10
Release:9.10
Package Name: linux-image-2.6.31-19-generic
** Attachment added: "uname-a.log"
http://launchpadlibrarian.net/39758764/uname-a.log
--
n900 in PC Suite Mode causes karmic to crash at startup
https://bugs.launchpad.net/bugs/5276
** Attachment added: "version.log"
http://launchpadlibrarian.net/39758778/version.log
--
n900 in PC Suite Mode causes karmic to crash at startup
https://bugs.launchpad.net/bugs/527624
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
-
** Attachment added: "dmesg.log"
http://launchpadlibrarian.net/39758790/dmesg.log
--
n900 in PC Suite Mode causes karmic to crash at startup
https://bugs.launchpad.net/bugs/527624
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
u
The dmesg.log and the lspci-vnvn.log were performed without the N900
attached.
** Attachment added: "lspci-vnvn.log"
http://launchpadlibrarian.net/39758840/lspci-vnvn.log
--
n900 in PC Suite Mode causes karmic to crash at startup
https://bugs.launchpad.net/bugs/527624
You received this bug no
I have the same problem. This error appears after reconnecting a few
times. The error is more frequent if the connection fails once due to
GSM network problems. After the error appears the modem does not work
again until I kill the "modem-manager".
IMHO following log message is the most important
I tested the restart behavior of lucid also with my n900 in pc-suite
mode. As far as I can see the result is the same as for karmic, the
kernel crashes.
** Changed in: linux (Ubuntu)
Status: Expired => New
--
n900 in PC Suite Mode causes karmic to crash at startup
https://bugs.launchpad.n
I managed to get a kernel backtrace since the ddeb for the current lucid
kernel is currently available at ddebs.ubuntu.com.
** Attachment added: "kernel backtrace"
http://launchpadlibrarian.net/49651397/crash.txt
--
n900 in PC Suite Mode causes karmic to crash at startup
https://bugs.launchpa
Unix-like operating system don't delete a file on a disk until the last
filehandle to the file is closed. Therefore, for log-files you also have
to restart the respective daemon (e.g. apache) to have the disk space
actually freed.
Rebooting the system has the same effect for obvious reasons.
--
I have to second the posting of sothis. I have an Saitek X52pro joystick
and cannot use it on jaunty with kernel 2.6.28-15-generic because no
/dev/input/js0 device is created! The same joystick works with
2.6.28-14-generic.
--
tablet devices show up as non-functional joysticks
https://bugs.launch
I don't know if this is the right place to report following bug:
On karmic my X52 pro is not detected again. It appears that the
regression is still active in karmic.
linux-source-2.6.31/drivers/input/joydev.c:854
static const struct input_device_id joydev_blacklist[] = {
/* ... snip */
When I try netstat -W on karmic I actually get "wide" output. Should it
be called "fixed" then?
--
netstat lacks -W wide columns option
https://bugs.launchpad.net/bugs/175988
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bug
My ASUS M3A32 Board has an it87 sensor on it worked fine on intrepid.
With karmic it does not work anymore. Bug#418246 appears to have a
solution (adding a kernel option acpi_enforce_resources=lax) but this
can be very dangerous according to http://marc.info/?l=linux-
kernel&m=125043293401414.
Th
Public bug reported:
The wacom Intuos 4 tablets (S, M, L and XL) have 6-8 buttons and a so-
called "touch ring". On my tablet they show up as "Wacom Intuos4 8x13
pad". Due to a bug in xf86-input-wacom, all events of these buttons and
"touch ring" end up with the coordinates x=0,y=0 on the screen.
Public bug reported:
Binary package hint: xorg
The xf86ScaleAxis function is used to scale x and y axis values of input
devices between different resolutions. Due to internal integer overflow,
the acceptable value range for its arguments are limited below their
type (signed 32bit integer). This i
** Patch added: "Patch from the xorg repository"
https://bugs.launchpad.net/bugs/730488/+attachment/1891113/+files/xf86-scale-high-resolution.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/7304
I've read some SRU related documentation and decided to supply a
debdiff. I did not yet test it. I'm quite new to this stuff, so is this
the way to go?
** Patch added: "debdiff from applied patch"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/730488/+attachment/1892854/+files/xorg
I tested the new xserver-common 2:1.7.6-2ubuntu7.6 and it works
perfectly.
Steps
1) Compiled and (make-) installed xf86-input-wacom-0.10.10.
2) Restarted x-server: Stylus cursor wraps to zero
3) Activated lucid-proposed in update-manager and performed update
4) Restarted computer: Stylus cursor us
I have the same problem with my ASUS setup.
mainboard: M3A32-MVP DELUXE
cpu: AMD Phenom(tm) II X4 940 Processor
ram: 8GB
gpu: GeForce 8800 GTS 512
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/765230
Public bug reported:
I have both a Western Digital MyPassport Essential 500GB harddisk and a
Seagate FreeAgent GoFlex Desk 2TB working ok on my ASUS U3S6 XHCI
controller in USB 3.0 mode. Currently I'm using ubuntu 10.04 (Lucid).
When I disconnect the devices, and connect a USB 3.0 hub (DeLock USB
Hi Yvon
The patch makes no change to the ABI nor API. Reading your description I
get the impression, the most likely reason for the failure is that the
AMD driver overwrites some packaged file of the xorg-server. If there is
any update of the xorg-server, it gets re-set to the "clean" state, and
i
I had the same problem at upgrading to maverick. Please find attached my
log files.
** Attachment added: "apt.log"
https://bugs.launchpad.net/ubuntu/+bug/643154/+attachment/1690116/+files/apt.log
--
upgrade to maverick interrupted due to overlapping dialog box
https://bugs.launchpad.net/bugs
** Attachment added: "history.log"
https://bugs.launchpad.net/ubuntu/+bug/643154/+attachment/1690117/+files/history.log
--
upgrade to maverick interrupted due to overlapping dialog box
https://bugs.launchpad.net/bugs/643154
You received this bug notification because you are a member of Ubunt
** Attachment added: "term.log"
https://bugs.launchpad.net/ubuntu/+bug/643154/+attachment/1690118/+files/term.log
--
upgrade to maverick interrupted due to overlapping dialog box
https://bugs.launchpad.net/bugs/643154
You received this bug notification because you are a member of Ubuntu
Bugs
One additional note: Some time before the system upgrade I did a minor
modification to the grub configuration. Apparently, the update process
wants to ask which version of the configuration to install. But due to
some unknown reason, the window manager is not useable at that time.
** Attachment ad
Public bug reported:
I have a mini USB Bluetooth V2.1+EDR dongle from DeLock which appears to
have the AR3011 chip on it. It is not supported by ubuntu yet (kernel
2.6.32-22).
Atheros has provided a driver for this chip:
http://lwn.net/Articles/363557/
Since Lucid is a LTS release it should prov
As I wrote, this "Bug" affects Lucid. I guess the Chip will work with
Maverick since it works since 2.6.33. I have compiled a vanilla 2.6.33.5
kernel and can confirm that it works.
It is just that Lucid is a LTS release and should IMHO therefore support
this Bluetooth dongle.
--
No support for A
30 matches
Mail list logo
