Deluge seems to be correct in refusing to parse magnet URIs with slashes
after the colon. Transmission also does not accept them either.
gvfs-open (called by xdg-open, called by chrome) is adding the slashes,
which I believe is a bug.
--
You received this bug notification because you are a
Here is an upstream report of the issue:
https://bugzilla.gnome.org/show_bug.cgi?id=748600
Here is the original patch which caused it:
https://bugzilla.gnome.org/show_bug.cgi?id=738690
** Bug watch added: GNOME Bug Tracker #748600
https://bugzilla.gnome.org/show_bug.cgi?id=748600
** Bug
Looks like it is fixed in Gnome 3.16.
** Changed in: deluge (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1480295
Title:
deluge doesn't take magnet:
Correction: fixed in 3.16 branch, so will be in the next 3.16 series
release (3.16.3 presumably)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1480295
Title:
deluge doesn't take magnet: links with
See also https://bugs.launchpad.net/ubuntu/+source/gnome-
keyring/+bug/645561
** Changed in: gnome-keyring (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/987167
I am experiencing the keeps unlocked for entire session behavior and
still can't find a way to change the setting, in Precise. This is a
_horrible_ security flaw!! I am using GPG because I want to protect my
assets and communications, and here my OS is silently subverting my
efforts.
--
You
To be clear, I support the idea of changing the default to a 10 minute
idle timeout.
See also https://bugs.launchpad.net/ubuntu/+source/gnome-
keyring/+bug/987167
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have the same behavior on Ubuntu 11.04 with a MBP 2,2
Additionally:
gstreamer-properties test reports:
gstreamer-properties-Message: Error running pipeline 'Video for Linux 2
(v4l2)': Error reading 614400 bytes on device '/dev/video0'.
[gstv4l2src.c(932): gst_v4l2src_get_mmap ():
Thanks for the detailed report, RNZ. I have been experiencing the
replication issue between CouchDB 1.1.0 and Ubuntu's CouchDB (1.0.1) and
was wondering if anyone else had the same problem. According to your
report replication is even broken between instances of Ubuntu's CouchDB.
Suck!
Packaging
Public bug reported:
CouchDB 1.1.0 [1] has persistent continuous replication and SSL support,
and is quickly becoming the default for CouchDB development. Debian Sid
has a source package [2].
[1]
http://wiki.apache.org/couchdb/Breaking_changes#Changes_Between_1.0.0_and_1.1.0
[2]
This bug is giving my friend a very bad impression of Linux on her new
Thinkpad. Can we have a hotfix plzzz? I guess I will try to build it
myself...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ya, pommed uses too much cpu (Maverick, MBP (2,2))
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/551438
Title:
Eats CPU time
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I've now upgraded to Maverick and the bug is still present. This seems
fairly critical, if only for people with this hardware config. Can
anyone on ubuntu's kernel team provide some context regarding the
addition of kslowd, links to upstream threads, etc?
Here are other reports of usage spikes
*** This bug is a duplicate of bug 653815 ***
https://bugs.launchpad.net/bugs/653815
** This bug has been marked a duplicate of bug 653815
X freezes momentarily every 10 seconds
* You can subscribe to bug 653815 by following this link:
I marked this bug as primary and the #613762 as duplicate since this has
more relevant information. The original reporter of #613762 has an intel
945GM chipset, which is similar to intel 855GM
** This bug is no longer a duplicate of bug 613762
kslow wakes up every 10 seconds making the mouse
*** This bug is a duplicate of bug 613762 ***
https://bugs.launchpad.net/bugs/613762
This bug affects me, using lucid with a backported karmic kernel from
ppa:kernel-ppa/ppa (workaround for dreaded intel video lockups with
lucid kernel)
Other than that, I have the same configuration and
I think this is hardware specific, since I have the same chipset as
Jonathan ( intel 855 GM). .36 kernel works for me too.
--
kslow wakes up every 10 seconds making the mouse cursor
https://bugs.launchpad.net/bugs/613762
You received this bug notification because you are a member of Ubuntu
Bugs,
Hmm, I just turned off pulseaudio and switched to alsa (Lucid) and the
calls are clear now. So this seems to be the fault of pulseaudio
(pending further testing)
--
sip calls garbled (PCMu/a)
https://bugs.launchpad.net/bugs/578009
You received this bug notification because you are a member of
see http://wiki.pdxhub.org/guides/linux_on_laptops for instructions to
switch gstreamer to use ALSA
--
sip calls garbled (PCMu/a)
https://bugs.launchpad.net/bugs/578009
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I'm having the same issue with my ubuntu one account
I first synced using Lucid. I started to see the error after syncing to
Tomboy on OSX (my Ubuntu machine is on the fritz). I've tried deleting
my local notes, and using 1.3.1 of tomboy. I suspect that some data
stored on the server is
i'm experiencing this too, though intermittently (X doesn't die every
time I go to a VT)
--
[gm45] VT switch causes X session to be lost
https://bugs.launchpad.net/bugs/576336
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Jakob, the error on switch to VT with bad file descriptor is reported
in #576336, and seems distinct from your first report (with invalid
argument)
--
[arrandale] Xserver occasionally crashes with Intel mobile graphics (i5-430M
CPU)
https://bugs.launchpad.net/bugs/588027
You received this bug
Fixed in Lucid, by my testing (also confirmed upstream)
** Changed in: telepathy-sofiasip (Ubuntu)
Status: Triaged = Fix Released
** Bug watch added: freedesktop.org Bugzilla #24260
http://bugs.freedesktop.org/show_bug.cgi?id=24260
** Changed in: telepathy-sofiasip
Remote watch:
upstream bug watch: https://bugs.freedesktop.org/show_bug.cgi?id=28269
** Changed in: telepathy-sofiasip (Ubuntu)
Status: Incomplete = New
** Bug watch added: freedesktop.org Bugzilla #28269
http://bugs.freedesktop.org/show_bug.cgi?id=28269
** Also affects: telepathy-sofiasip via
Public bug reported:
Binary package hint: empathy
I use Gizmo (sipphone.com) with Google Voice and a SIP client on my
laptop to place/receive voice calls on the cheap.
Twinkle is my benchmark SIP client, since I've found it to be very
reliable compared to other clients available in the Ubuntu
** Attachment added: sofiasip.log
http://launchpadlibrarian.net/48171378/sofiasip.log
--
sip calls garbled (PCMu/a)
https://bugs.launchpad.net/bugs/578009
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Attachment added: empathy.log
http://launchpadlibrarian.net/48171408/empathy.log
--
sip calls garbled (PCMu/a)
https://bugs.launchpad.net/bugs/578009
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
these logs show a session where I start empathy, place a call to echo
(Gizmo's test service), listen to garbled/dropping audio for a few
seconds, and hang up.
--
sip calls garbled (PCMu/a)
https://bugs.launchpad.net/bugs/578009
You received this bug notification because you are a member of
i have been using evdev for a few releases now, on a variety of fujitsu
and panasonic notebooks. it seems to do everything evtouch does, so I'd
vote to close this.
--
udev rules should be installed by default
https://bugs.launchpad.net/bugs/242590
You received this bug notification because you
The correct calibration program I think is xinput_calibrator [1]
[1] http://www.freedesktop.org/wiki/Software/xinput_calibrator
It is simple and usable, actively maintained, works with a number of
drivers, and has both an X11 and GTK version.
If you'd like to try it out, clone and compile the
upstream bug: http://github.com/tias/xinput_calibrator/issues#issue/7
--
calibration utility is missing for touchscreen
https://bugs.launchpad.net/bugs/557923
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
great job Soren! It's nice to have a unified driver, much easier to
support etc.
i was just looking through the evdev and evtouch code and trying to
understand if evtouch has some sort of right-click emulation via
LONG_TOUCH, which is the only other thing I would miss in evdev
(although it might
still present in Lucid beta. this issue is easily reproducible on any
system with suspend (just mount a share with sshfs and suspend). I
searched for an upstream issue, and found this:
http://sourceforge.net/mailarchive/forum.php?thread_name=E1Nz5rE-0006Yj-
Just a follow-up on Soren's comment, I have been testing
xinput_calibrator [1], it is excellect, with a goal of supporting
calibration of all drivers, and export to udev, xorg, xinput command,
hal. This should be integrated in Ubuntu.
[1] http://github.com/tias/xinput_calibrator
--
udev rules
This report isn't incomplete. It's also not hardware-specific.
Brightness controls are S-L-O-W. This is because g-p-m waits for the
notification to display before making the adjustment (synchronous). To
make is responsive g-p-m should display the notifications asynchronously
and then go ahead and
** Changed in: xf86-input-evtouch (Ubuntu)
Status: New = Confirmed
--
evtoch calibration does not consistently work
https://bugs.launchpad.net/bugs/442553
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Actually, the issue is that the init.d script is being run *after* gdm
starts (restarting gdm makes the touchscreen work). This is tricky
since:
1. gdm and hal have been moved to upstart (/etc/init/)
2. script must be run after hal but before gdm
I think that the calibration wrapper
Confirmed, Panasonic CF-T2. Calibration works after restarting X, but
isn't used on the next boot. Running
sudo service xserver-xorg-input-evtouch start
sudo service gdm restart
applies the calibration. This service should be started at boot but
isn't?
--
evtoch calibration does not
agreed, brightness, volume keys work out of box in karmic (Let's Note
CF-T2)
--
Support for panasonic hotkeys missing
https://bugs.launchpad.net/bugs/222324
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Jonathan: wh
Vistaus: we need to transition to webkit so that the web will unbreak.
want kde to become beos?
7penselen: it is already possible to change the default browser. ubuntu
has a fundamental rule for its derivatives: one default app per
function, so new users aren't overwhelmed.
** Changed in: linux
Status: Fix Released = In Progress
--
kernel 2.6.28 doesn't boot on a dell inspiron 2650
https://bugs.launchpad.net/bugs/327499
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
perhaps someone could create a patched kernel package to test, since the
conditions seem slightly different in each report. In the case I'm
seeing, only acpi=off works.
--
kernel 2.6.28 doesn't boot on a dell inspiron 2650
https://bugs.launchpad.net/bugs/327499
You received this bug notification
** This bug is no longer a duplicate of bug 294994
NAT traversal for SIP using Empathy
--
SIP calls no longer work (Incompatibility with telepathy-sofiasip)
https://bugs.launchpad.net/bugs/409103
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Actually bug #294994 is about REGISTER failing with certain providers
and network configurations, but this bug is about telepathy-sofiasip
being out of sync with the telepathy APIs so that calls hang (but
register works). Note that this is with the Jaunty packages in
Confirming that panasonic_laptop module in Jaunty fails to support
brightness keys, since it does not create the /proc/acpi/pcc/*
interfaces which the panasonic brightness scripts in acpi-support
expect.
I've been using the pcc_acpi module with the suse patches
not fixed
** Changed in: linux (Ubuntu)
Status: Fix Released = Confirmed
--
Support for panasonic hotkeys missing
https://bugs.launchpad.net/bugs/222324
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
not fixed
--
Support for panasonic hotkeys missing
https://bugs.launchpad.net/bugs/222324
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
oops, bad whitespace in patch
** Attachment added: fix build on 2.6.28
http://launchpadlibrarian.net/30291219/pcc-acpi-0.9-2.6.28-nolvalue.diff
--
Support for panasonic hotkeys missing
https://bugs.launchpad.net/bugs/222324
You received this bug notification because you are a member of
Confirming that panasonic_laptop module in Jaunty fails to support
brightness keys, since it does not create the /proc/acpi/pcc/*
interfaces which the panasonic brightness scripts in acpi-support
expect.
I've been using the pcc_acpi module with the suse patches
Confirming that panasonic_laptop module in Jaunty fails to support
brightness keys, since it does not create the /proc/acpi/pcc/*
interfaces which the panasonic brightness scripts in acpi-support
expect.
I've been using the pcc_acpi module with the suse patches
for those like me who just need working brightness control for now, here
is a quick script to patch and build the old module.
insmod /tmp/pcc_acpi_build/pcc-acpi-0.9/pcc_acpi.ko or make install from
there and modprobe pcc_acpi (making sure panasonic_laptop module isn't
loaded)
** Attachment
I think http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=524838 is the
relevant upstream bug for getting brightness key events working with the
new driver. rebooting to test
(note: not sure why my comment shows up multiple times, maybe wanky
browser, sorry)
** Bug watch added: Debian Bug tracker
Success! Installing acpi-support and acpi-support-base 0.123-1 from
Debian Sid enables brightness up/down keys to work with the in-kernel
driver. NOTE: acpi-support 0.125 from Karmic DOES NOT support the
brightness keys. gnome-power-manager still can't send or receive
brightness events.
--
I'm experiencing the same behavior (each event registered twice) with a
panasonic laptop, due to the new panasonic_laptop kernel module. Issue
is resolved similarly for panasonic laptops by removing
/etc/acpi/events/panasonic-[mute,volume-down,volume-up]
Note that the kernel module isn't
Found the same issue reported in the upstream tracker:
https://bugs.freedesktop.org/show_bug.cgi?id=21973
Also attached the output of TPORT_LOG=true SOFIASIP_DEBUG=all
SOFIASIP_PERSIST=true \
/usr/lib/telepathy/telepathy-sofiasip. I think the relevant line is:
**
Public bug reported:
Binary package hint: empathy
I've tested behind several NAT connections, although not with a public
IP. I'm unable to call out or receive calls using gizmo (sipphone.com)
and ekiga.net although incoming calls ring. I've tested using the Jaunty
packages and am currently
related: https://bugs.launchpad.net/ubuntu/+source/telepathy-
sofiasip/+bug/337716
--
gizmo/sofia-sip calls fail to connect behind NAT
https://bugs.launchpad.net/bugs/409103
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
upstream:
http://sourceforge.net/tracker/index.php?func=detailaid=2412241group_id=143636atid=756076
** Bug watch added: SourceForge.net Tracker #2412241
http://sourceforge.net/support/tracker.php?aid=2412241
--
gizmo/sofia-sip calls fail to connect behind NAT
The upstream issue in #2 and https://bugs.launchpad.net/telepathy-
sofiasip/+bug/294994 indicate failure to register, whereas I am
experiencing failure to initialize in/out calls, with registration
working fine behind NAT with both services. Separate issues?
--
gizmo/sofia-sip calls fail to
This is the exact issue, same debug logs I get: http://bugs.debian.org
/cgi-bin/bugreport.cgi?bug=535796
** Bug watch added: Debian Bug tracker #535796
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=535796
--
gizmo/sofia-sip calls fail to connect behind NAT
** Attachment added: lspci -vvnn output
http://launchpadlibrarian.net/26157284/lspcivvnn.txt
--
S3 ProSavageDDR K4M266 hard locks on X init when DRI is enabled
https://bugs.launchpad.net/bugs/336311
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Confirming with S3 Inc. 86C380 [ProSavageDDR K4M266] (rev 02) in generic
VIA laptop.
Setting Option DRI false avoids the lockup. Thanks for the sleuthing
Toni.
Setting Option BusType PCI causes a slightly different lockup, with
vertical black and white bars (without this option, the screen
oops, that log is with the workaround enabled
--
S3 ProSavageDDR K4M266 hard locks on X init when DRI is enabled
https://bugs.launchpad.net/bugs/336311
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Attachment added: Xorg.log for pristine xorg.conf
http://launchpadlibrarian.net/26157366/Xorg.0.log
--
S3 ProSavageDDR K4M266 hard locks on X init when DRI is enabled
https://bugs.launchpad.net/bugs/336311
You received this bug notification because you are a member of Ubuntu
Bugs, which
Peter: Please file a separate report for the Fujitsu.
Confirming, with Toshiba Satellite M45 and up-to-date Intrepid.
No brightness control either via fn-keys or gnome-power-manager dim
display option.
Any suggestions for testing?
** Changed in: gnome-power-manager (Ubuntu)
Status:
I revisited this issue tonight and after an unnecessary excursion into
the land of bleeding xorg, discovered that other user accounts on the
same machine don't have the problem. deleted all kwin related conf files
in ~/.kde/share/config/ fixes and now no crash.
Tried to comment same on upstream
Public bug reported:
Binary package hint: knetworkmanager
opensuse 11.1 has a knetworkmanager package built for kde 4.2, which
seems more or less feature complete, if a bit rough.
Not sure if this is built from
svn://anonsvn.kde.org/home/kde/branches/work/knetworkmanager/
I may try to build a
I made a mistake: OpenSuse 11.1 ships with a KDE-4.1 compiled KNetworkManager
[1] (for instance it links to libplasma2)
There is also a KDE-4.2 compiled package [2] , which may or may not actually
be functional (as of yesterday it wouldn't install due to a dependency issue
with its -lang
Jonathon: I'm confused. I thought this opensuse package was different
from the new plasma applet, but looking inside the src.rpm I see that
you are right about the SVN path.
--
package kde 4.2 knetworkmanager
https://bugs.launchpad.net/bugs/306184
You received this bug notification because you
Kenan just made a new release of evtouch (0.8.8) including gborzi's
patch see http://www.conan.de/touchscreen/CHANGELOG.evtouch
--
evtouch works incorrectly when the screen is left or right rotated
https://bugs.launchpad.net/bugs/222164
You received this bug notification because you are a member
Nicolas: perhaps the calibration values aren't getting transformed? I
will build and test the patch, and try to understand what's going on
with the calibration values (I will need this I think because I have
fairly large corrections in my toughbook T2 config). Thanks for jumping
on this issue
touchscreen issue duplicates
https://bugs.launchpad.net/ubuntu/+source/xf86-input-evtouch/+bug/222164
For me, stick mouse coordinates aren't transformed on screen rotation,
which is correct behavior since the stick rotates (physically) with
the rest of the device. I could see wanting an external
this has been bugging me for months, but I just found this report. After
reading through all the comments and dups, I found that I just needed to
aptitude update aptitude upgrade
Thanks everyone involved in this fix!
--
Xorg crashed with SIGSEGV in i830_emit_state
Great news, James, thanks!
Did you apply the patch to Hardy's kernel source to build? I'm not used
to working with kernel tree patches since I stopped building my own
kernels many years ago. Should I just install linux-source, patch, build
the module, copy into place, depmod -a ?
--
Support for
I'm still experiencing the crash with kwin in opengl composite mode
after installing the update (tried Chris' ppa Mesa too). I have the same
chipset several others have mentioned, intel 855GM. Trying to generate a
backtrace with gdb.
--
Xorg crashed with SIGSEGV in i830_emit_state
there is no core dump in /etc/X11/core, perhaps I misunderstood. Should
I build mesa from scratch as tschenser did to get a useful backtrace?
--
Xorg crashed with SIGSEGV in i830_emit_state
https://bugs.launchpad.net/bugs/277709
You received this bug notification because you are a member of
** Attachment added: gdb-Xorg.log
http://launchpadlibrarian.net/18794694/gdb-Xorg.log
--
SIGSEGV in X with kwin composite, intel 855GM
https://bugs.launchpad.net/bugs/287485
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Public bug reported:
Binary package hint: xorg
Thought it was
https://bugs.launchpad.net/gentoo/+source/mesa/+bug/277709 , but no joy.
To reproduce I start a failsafe console session, run kwin (kwin has
compositing enabled, with opengl backend - no crash with xrender
backend).
Xorg backtrace
** Attachment added: gdb-Xorg.log
http://launchpadlibrarian.net/18794544/gdb-Xorg.log
--
Xorg crashed with SIGSEGV in i830_emit_state
https://bugs.launchpad.net/bugs/277709
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Here are the backtraces from X and gdm with UnTrap Signals. I'm running
latest offical mesa packages.
** Attachment added: xorg.log
http://launchpadlibrarian.net/18794538/xorg.log
--
Xorg crashed with SIGSEGV in i830_emit_state
https://bugs.launchpad.net/bugs/277709
You received this bug
Ok Chris, sorry it just seems so similar since it only effects kwin, same
chipset. Reported as
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/285250
--
Xorg crashed with SIGSEGV in i830_emit_state
https://bugs.launchpad.net/bugs/277709
You received this bug
oops, bad link
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/287485
--
Xorg crashed with SIGSEGV in i830_emit_state
https://bugs.launchpad.net/bugs/277709
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
it's installed. same difficulty Salze had in
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/277709 ?
i didn't install from deb http://ddebs.ubuntu.com intrepid main universe. Is
there any reason to use that instead of the main repo packages?
--
Xorg crashed with SIGSEGV in
ok, built mesa with debug symbols and generated a backtrace. Looks just like
yours from 277709. Did I fail to apply the patches to mesa? I did:
apt-get source mesa
dpkg-source -x mesa*.dsc # this command applies all patches via quilt yes?
** Attachment added: gdb-Xorg.txt
ok, here's a proper backtrace
** Attachment added: gdb-Xorg.txt
http://launchpadlibrarian.net/18796492/gdb-Xorg.txt
--
Xorg crashed with SIGSEGV in _swrast_copy_teximage2d [i855GM]
https://bugs.launchpad.net/bugs/287485
You received this bug notification because you are a member of Ubuntu
** Attachment added: xorg.conf
http://launchpadlibrarian.net/18805639/xorg.conf
--
Xorg crashed with SIGSEGV in _swrast_copy_teximage2d [i855GM]
https://bugs.launchpad.net/bugs/287485
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: lspci.txt
http://launchpadlibrarian.net/18805672/lspci.txt
--
Xorg crashed with SIGSEGV in _swrast_copy_teximage2d [i855GM]
https://bugs.launchpad.net/bugs/287485
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: Xorg.0.log.old
http://launchpadlibrarian.net/18805691/Xorg.0.log.old
--
Xorg crashed with SIGSEGV in _swrast_copy_teximage2d [i855GM]
https://bugs.launchpad.net/bugs/287485
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
glxinfo says:
Mesa warning: couldn't open libtxc_dxtn.so, software DXTn
compression/decompression unavailable
--
Xorg crashed with SIGSEGV in _swrast_copy_teximage2d [i855GM]
https://bugs.launchpad.net/bugs/287485
You received this bug notification because you are a member of Ubuntu
Bugs,
here is an excellent calibration for my Panasonic CF-T2.
** Attachment added: config
http://launchpadlibrarian.net/18809637/config
--
make evtouch devices work with hal-input in intrepid
https://bugs.launchpad.net/bugs/261873
You received this bug notification because you are a member of
lshal output in case the .fdi above needs to be made more selective. can
this make it into intrepid?
udi =
'/org/freedesktop/Hal/devices/usb_device_430_501_noserial_if0_logicaldev_input'
info.capabilities = {'input', 'input.mouse'} (string list)
info.category = 'input' (string)
most (all?) evtouch devices require a lower value for Option MoveLimit
as in https://bugs.launchpad.net/ubuntu/+source/xf86-input-
evtouch/+bug/204633
Can a value for this option be included in .FDI files? Not clear from
linked issue whether one generic value works for all devices.
--
make
It seems that this can be resolved with .FDI files like in
https://bugs.launchpad.net/ubuntu/+source/xf86-input-evtouch/+bug/261873
--
touchscreen only outputs right angles
https://bugs.launchpad.net/bugs/204633
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Setting movelimit to 2 in 10-Panasonic.fdi above makes drawing smooth in
karbon14 etc. Should be the same for Fujitsu since they are really the
same device. Can match contain an OR or regex in .FDI files? If so these
could be merged (they just have a slightly different manufacturer
string)
**
I'm still having the frequent load cycle problem with an up to date
Intrepid, so no. Hernando, will this fix be included in Intrepid?
--
High frequency of load/unload cycles on some hard disks may shorten lifetime
https://bugs.launchpad.net/bugs/59695
You received this bug notification because
Enabling laptop mode as in https://wiki.ubuntu.com/PowerManagement fixes
this for me in Intrepid, so I guess it's working!
I guess laptop mode should be enabled by default?
--
High frequency of load/unload cycles on some hard disks may shorten lifetime
https://bugs.launchpad.net/bugs/59695
You
I have a Panasonic Let's Note (Toughbook) T2. This FDI works for me.
Great work with the new xinput integration guys, much better than the
old calibration by algebra method I'd been using. I'm so excited I
want to swear in text. No swearing on Launchpad right?
PS for those following along at
I may have a better calibration after testing, but here's a first draft
in case I drop the ball.
** Attachment added: /etc/evtouch/config
http://launchpadlibrarian.net/18455448/config
--
make evtouch devices work with hal-input in intrepid
https://bugs.launchpad.net/bugs/261873
You received
Public bug reported:
Binary package hint: kdepim
should kmail perhaps recommend kdepim-doc? For someone looking for a
small install without extra bells and whistles (ie kalarm [sic])
installing the whole kdepim package is overkill, but it is a bit
shocking when going to the help menu and getting
backlink:
http://lists.kde.org/?l=kopete-develm=121976872131592w=2
Penguins are a good animal for Linux: everyone standing on the iceburg,
waiting for someone else to do it :)
--
[KDE4-Kopete]no IRC mode
https://bugs.launchpad.net/bugs/201732
You received this bug notification because you are a
1 - 100 of 118 matches
Mail list logo
