I meant to say that last year an update killed my middle mouse pasting,
which had worked before. This install is a completely clean install of
Lubuntu 16.10 after reformatting the hard drive.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
I followed John's instructions and am attaching the terminal output (from the
script command) because it does show emulation set to zero as well as my type
of mouse.
My scrolling has always worked, just not the middle mouse paste. Performing
the steps john suggested did not make the pasting wor
Kill -9 does the trick. I had been using xkill and I guess it does not
do that. Destroying or closing the window, or using xkill, results in a
respawn, but kill -9 from the terminal gets rid of it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I stand corrected. It seems that I can't get rid of yelp by killing the
terminal after all. If I could figure out what is respawing it I would
kill that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/9
Also note that there is an upstream bug for this in Debian.:
http://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg1088861.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/914889
Title:
This problem exists in 12.04 "Precise" as well. And no matter how much you kill
it, it keeps coming back. The process shows init as its parent:
rifter5626 1 14 15:05 ?00:00:48 yelp
ghelp:///usr/share/gnome/help/gnome-terminal/C/gnome-terminal.xml
The only way to stop i
Oh and just in case ?I was not clear this affects the latest Ubuntu and
the latest drivers. I don't see a way to indicate that but I believe
we're still where we were before on this.
** Changed in: nvidia-graphics-drivers (Ubuntu)
Status: Expired => Incomplete
--
You received this bug not
The issue exists for *all* cards, including the newest, and in the
newest drivers from nvidia. It doesn't remember the setting between
reboots, either, which is very frustrating. And the only reason we did
not report it to nvidia as I recall is we could find no means to do so.
--
You received thi
** Attachment added: "gpointing-device-settings.bug.apport"
https://bugs.launchpad.net/ubuntu/+source/gpointing-device-settings/+bug/562414/+attachment/3329913/+files/gpointing-device-settings.bug.apport
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
I am on Ubuntu 12.04 LTS (AMD64) and this is still a problem. The command just
flat does not work.
If I use gksudo I get the above result, like the OP.
If I try as a normal user I get:
... a different error. (apport would not let me copy and paste, and would not
come up again so I could even se
@#25 Maximum performance is not an overclocked setting. I would expect
overheating when overclocking. Not to say that Nvidia cards don't do that
under normal speed, because the ones that don't do powermizer have for me in
the past. However that only happens if you have insufficient cooling.
The people who claim only some people are affected by this bug are completely
off base. This is a bug that affects everyone. It is ridiculous that the
setting for the nvidia powermizer is not saved when you change it unless you do
so by manually editing xorg.conf. It's also pretty annoying th
This problem continues in Maverick Meerkat (10.10) it was not an issue in
Karmic. I needed to install the all package to support esd .. I guess i can't
now.
I say the option that -all satisfies all dependencies for the others makes more
sense. I am pretty sure that is how it is handled before;
Okay it says the fix is released, but in what version? I have the
latest package and this still continuously happens. Further, the bug
continues to exist in Lucid
https://bugs.launchpad.net/ubuntu/+source/xfstt/+bug/575026
I see the patch in here, but is it going to get included in a package?
I
This was in Karmic
--
package ecm 1.00-0ubuntu2 failed to install/upgrade: trying to overwrite
'/usr/bin/ecm', which is also in package gmp-ecm 0:6.2-1
https://bugs.launchpad.net/bugs/648436
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/648436/+attachment/1641161/+files/Dependencies.txt
** Attachment added: "Dmesg.txt"
https://bugs.launchpad.net/bugs/648436/+attachment/1641162/+files/Dmesg.txt
** Attachment added: "DpkgTerminalLog.gz"
https://bug
Public bug reported:
Binary package hint: ecm
gmp-ecm and ecm are both packages in Universe. The first is a math
program and the second one deals with a format for cdrom images.
Apparently they both call their command ecm. These are the involved
versions:
$ apt-cache policy gmp-ecm
gmp-ecm:
it seems silly that such a simple patch could not be applied to karmic
packages, especially since it looks like it is Ubuntu's fault and it
would only require adding ONE CHARACTER (an x) to the package
instructions.
--
package xscreensaver-data-extra (not installed) failed to install/upgrade:
tr
except that it hasn't been fixed. or at least it hasn't been fixed for
karmic. I haven't made the jump to lucid yet.
--
package xscreensaver-data-extra (not installed) failed to install/upgrade:
trying to overwrite '/usr/share/man/man6/pacman.6.gz', which is also in package
pacman 0:10-17ubun
OK, it looks like I had indi on my system. Getting rid of it was pretty
ugly. apt-get remove wouldn't work because the kstars package and
others were broken, fix didn't work because libindi0 gave the error
"trying to overwrite '/usr/bin/indiserver'" as above. In the end I was
able to do dpkg -r
I'm on karmic, and the kstars package still causes this error. So is it
really fixed?
--
kstars does not support indi
https://bugs.launchpad.net/bugs/359517
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdeedu in ubuntu.
--
kubuntu-bugs mai
Uninstalling also fixed a problem where the following programs crashed when
trying to open or save files (which had started after pango-graphite was
installed): gnumeric, openoffice (calc), gimp, kspread
All of those started working again when I uninstalled pango-graphite.
--
gnome-appearance-p
pango-graphite broke my gnome-volume-control as well as gnome-
appearance-properties by causing segfaults. It also caused xchat to
break as far as how it renders fonts (the end of the line would get cut
off and some words would be mashed together ... highlighting the line
revealed the beginning an
This turns out to be a duplicate of the following bug because it was
caused by pango-graphite
https://bugs.launchpad.net/ubuntu/+source/pango-graphite/+bug/404681
pango-graphite broke my gnome-volume-control as well as
gnome-appearance-properties by causing segfaults. It also caused xchat to
One other thing ... I know that I have installed several updates from
update manager since the font problem. It could just as well be that
one of these broke gnome-volume-control.
--
9.10 (Karmic): gnome-volume-control segmentation fault on startup (crashed with
SIGSEGV in _int_free())
https://
** Attachment added: "trace-bugreport.tar.gz"
http://launchpadlibrarian.net/44206093/trace-bugreport.tar.gz
** Attachment added: "CoreDump.gz"
http://launchpadlibrarian.net/44204934/CoreDump.gz
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/44204938/Dependencies.t
I am running Ubuntu 9.10 on AMD 64-bit and I have this bug. I disagree with
those who say the resource waste from this bug is negligible because at least
in my case I have 64 instances of this process, each of which are using over
122MB of RAM, 117MB of which is virtual. That's a total of over
I have no sounds, either (in Karmic). I installed the freedesktop theme
as above but that did not make the sounds work. Is there some
workaround to get sounds in Empathy?
--
Empathy sounds not in default ubuntu theme
https://bugs.launchpad.net/bugs/400485
You received this bug notification beca
Thank you thank you thank you Grondr and Robert for giving some respite
to people who are suffering from this horrible bug.
This problem is highly annoying to me. The initial reason for neutering
the pc speaker was that besides it being "outdated" you had to grovel
through 8 miles of innards to ge
29 matches
Mail list logo
