Apparently this bug is present in 13.10 (Saucy) as well.
Setting up mumble-django (2.9-2) ...
dpkg: error processing mumble-django (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
mumble-django
E: Sub-process
I feel like a bit of an idiot atm, I left firefox open last night and
this morning my laptop was overheating. After I gave it a reboot and
checked my email someone had messaged me stating that sometime in Karmic
the custom DSDT option was removed, I checked my logs and found that it
seems to be
It's actually hard to say at this point. The freezing has disappeared
quite a while ago, but there is another problem which I still
experience, which seems directly related to what caused the freezes in
the first place. This seems to be an issue on certain chipsets not
handling IRQ's properly. I
I can also confirm the newest lucid release as being bugged:
$ apt-cache policy k3b
k3b:
Installed: 1.70.0~beta1+svn1087124-0ubuntu2
Candidate: 1.70.0~beta1+svn1087124-0ubuntu2
Version table:
*** 1.70.0~beta1+svn1087124-0ubuntu2 0
500 http://us.archive.ubuntu.com lucid/main
I suppose I should have waited a bit longer before I posted that update,
I guess my repos` took a while longer to update than some people... i
was using 4.6.1 at my previous post, but I just ran update check again
and 4.6.2 came up. After updating I can confirm that this is indeed
fixed! Thanks to
Public bug reported:
Binary package hint: k3b
Release: Kubuntu 9.10 (KDE 4.4rc2)
$ apt-cache policy k3b
k3b:
Installed: 1.68.0~alpha3-0ubuntu1
Candidate: 1.68.0~alpha3-0ubuntu1
Version table:
*** 1.68.0~alpha3-0ubuntu1 0
500 http://us.archive.ubuntu.com karmic/main Packages
IMO, when using a alpha-state release, one should be glad they are only
seeing warnings instead of errors. I've had the same warnings as
everyone else and so long as my system is operating properly, I don't
care about the warnings so long as I know they will be fixed. As for the
off-topic usplash
I am currently in the same situation. I ran an update yesterday (Sept.
15th), and then switched to windows to do a few things. This morning
when I woke up, I tried to reboot back into linux to find that the
minute I got to the login screen, my mouse and keyboard were frozen. I
am going to connect
Well, at this point, it seems as tho X isn't getting the mouse/keyboard
info from udev. I'd love to post some logs, but since I can't seem to
get into kde to do so, there is not much I can provide. On a more
amusing note, everytime I go from recovery mode to normal boot, fsck
throws a fit over
Alright... got my linux working just a moment ago. Not sure if it was
one of the few updates (one of which being hal), or if it was upstart
not being updated, but I do have full kb/mouse again. Apparently upstart
and some init-scripts packages were being kept back. Doing an apt-get -f
install
Confirmed fixed here on my end as well, prior to that I had the package
versions locked in synaptic.
On Tue, Sep 15, 2009 at 10:42 AM, Eric Casteleijn
eric.castele...@canonical.com wrote:
Brian:
No icons, no taskbars, desktop background is there. When I click
somewhere the taskbars seem to
I've been playing with Karmic for a while now, and so far for me it's boot
on and off battery without requiring a key to be pressed down. However, I
have noticed it occasionally overheats.. but so far it only seems to
overheat if I leave firefox open and close the lid. When I come back after a
few
Conn, I could not find your full Xorg log, you seem to have only posted
your grep via mouse. Could you run the following commands that Andreas
had suggested to me previously?
grep -c Synaptics /var/log/Xorg.0.log
lshal | grep -c input.touchpad
If the 2 commands produce a number higher than 1,
@Conn,
If this is the case.. grab my custom fdi file from the previous post and follow
the instructions, if everything works as it should you should have tap-clicking
and vertical scrolling re-enabled, I also left the 2 finger scrolling active in
case anyone wanted both but you can easily
This may be a duplicate to: https://bugs.launchpad.net/bugs/339313
--
wi-fi not work in kubuntu 9.10
https://bugs.launchpad.net/bugs/384493
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Turns out, here in Karmic I've had the same problem in both the plasmoid
and knetworkmanager. It continually attempts to connect over and over to
no avail. I rather liked the plasmoid, but to fix the problem (as
someone else suggested) I did sudo apt-get install wicd, then gave it
a reboot.
For
Unless/Until someone marks this as a duplicate, I added this post this
morning to the other bug thread on how to gain wifi back. Unfortunately
you lose knetworkmanager and the plasmoid applet but you should atleast
have wifi (which I personally can't live without on my laptop).
To: Andreas Henriksson
Unfortunately in my case (and probably others), the synaptics driver
doesn't actually seem to be loading. Typing the options listed in that
news file doesn't seem to effect the mouse at all.
--
[Karmic] Touchpad not recognised correctly, synaptics driver not in use
$ grep -c Synaptics /var/log/Xorg.0.log
15
$ lshal | grep -c input.touchpad
1
This is rather odd.. it seems to actually find my touchpad (which is
good in some respects)..
$ cat /var/log/Xorg.0.log | grep Synaptics
(II) config/hal: Adding input device SynPS/2 Synaptics TouchPad
(II) Synaptics
Can confirm this is still not fixed as of: 2.6.30-8-generic
--
apparmor fails to load at startup
https://bugs.launchpad.net/bugs/375422
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
knetworkmanager and the plasma widget both seem to be using the same
back-end system which doesn't work properly at current. Like I said,
follow that link and try using wicd, if it doesn't work for you, your
problem might be completely different. I tried both the plasma applet
and knetworkmanager.
On a secondary note: the plasma widget and knetwork manager worked for
me on intrepid, and jaunty.. as well as karmic until i added pre-
released and unsupported repositories in order to play with KDE
4.3beta. So it seems to me that the back-end for knetworkmanager and the
plasmoid broke in 4.3
There is no reason to be rude here. I was not vague at all, i merely
made the assumption that you read the file you suggested other people
read in regards to re-enabling tap-clicking, which I stated did not work
for me.
No, I was not aware that it defaults to mac touchpad behavior, but
If I have time later I may pop in my Jaunty live CD, I am unsure of what
changed between then and now as far as default configurations are
concerned.. however.. after poking around in /etc/hal/fdi/policy/ as
well as /usr/share/hal/fdi/policy/20thirdpolicy (some sites suggest the
default file is in
Did you have pre-release repositories enabled in Jaunty before dist-
upgrading? I had this same issue when I tried to do a dist-upgrade. I
then decided (since my linux install was minimal), to do a full CD
install of karmic. My wifi worked absolutely fine, until I enabled pre-
release to get KDE
Can confirm same issue on the HP Pavilion dv9610us. No tap-click, no
scroll:
~$ cat /var/log/Xorg.0.log | grep -i mouse
(==) NVIDIA(0): Silken mouse enabled
(II) config/hal: Adding input device Macintosh mouse button emulation
(**) Macintosh mouse button emulation: always reports core events
(**)
I seem to be having the same general issue, though I cannot get
knetworkmanager to function either. It detects my network, and attempts
to connect for what seems like.. ever. Ocassionally it will ask for the
wpa-personal passkey again, but again fail.
I get these few msg's cycling repeatedly in
To 67GTA:
I noticed on your post in the ubuntu forums you mentioned acpi_osi=Linux.
Has this been known to work without the custom DSDT or is that required? The
custom DSDT file seems a bit beyond my range of knowledge. :/ This problem
is actually really upsetting, I've noticed my laptop being
I just noticed something I haven't before.. I may have previously stated
that the new kernels being used in Jaunty fix the issue, but for the
first time in a very long time I booted my laptop via battery instead of
the power cord and it went back to it's same old shenanigans. I was
forced to use
strangely enough, i didnt notice my bluetooth icon was missing until I
reinstalled dbus. I was originally trying to fix the update notifier
problem, and on reboot... my bluetooth icon showed up. Hah, I still
haven't seen the update notifier icon come up with anything new though..
usually (on 8.10)
I just updated my jaunty release to ensure i got all of alpha 6, and the new
drivers were in there.. I have proposed and backports enabled though.
On Fri, Mar 13, 2009 at 3:51 PM, Schmirrwurst schmirrwu...@free.fr
wrote:
when the update is going to be available in the repositories ?
- Mail
I can both confirm the problem and confirm the fix via reinstalling
python-qt4-dbus. update-notifier-kde is now showing up in processes
list like it should. Not sure what exactly caused the original problem
but since this system was a pure Jaunty alpha 5 install (non-upgrade
from any previous
Maybe someone should change the importance of this to something more than
wishlist. While we all wish this would be fixed, I think it's a bit more
important than that since it effects pretty much everyone with an nvidia
card.
On Mon, Mar 9, 2009 at 6:18 AM, Michael Marley
I added the tag needs-packaging in the hopes it will bring this
particular problem to attention.
Jaunty really should have this driver updated, while we have a location
to retrieve older driver packages and the means to lock them I don't
believe that should be considered a triage or fix. To
Thanks michael, I've been been using the drivers from your repos for about
an hour now, and so far they seem to fix the problem .35 produced. Hopefully
these will make it into the jaunty repos soon. Until then I think I will be
keeping your repos` in my sources list. :)
On Sun, Mar 8, 2009 at
I agree, Jaunty is still in alpha anyway... they should pop them in untested
or something so we can have a crack at them. I doubt they could be any worse
than 180.35 anyway.
On Sat, Mar 7, 2009 at 12:20 PM, Mark Greenwood
fatger...@ntlworld.comwrote:
Why not create some packages just for
As soon as the packages pop up I'd be more than happy to test. I don't like
manually installing drivers because I don't think they work with dkms, and
with all the kernel upgrades kubuntu likes to push out, it's much easier for
me to let it do the work itself. My laptop's video is very
I also added this one since it was in the collection of packages provided
here, didn't want anything to get screwed up with mismatched versions:
Package: nvidia-180-libvdpau
Pin: release
Pin-Priority: 999
On Thu, Mar 5, 2009 at 8:41 AM, 3vi1 launchpad@eternaldusk.com
wrote:
As mentioned
first, I'd like to thank getaceres for providing the 180.29 packages,
they fixed all the bugs I currently have with jaunty. Second, I agree
with 3vil, they should put .29 back until nvidia fixes the problem
because the current drivers break numerous parts of kde4.
--
nvidia driver 180.35 breaks
This bug is caused by the nvidia drivers as found in this bug:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-180/+bug/335879
going to mark it as invalid.
** Changed in: kdeartwork (Ubuntu)
Status: New = Invalid
--
screensaver refuses to exit
Funny you should mention that, I was just about to mark these as invalid
(this bug + one with the screensaver's not functioning as intended)
because they were both fixed via backing off my nvidia drivers to pre
.35 as mentioned in this bug:
Public bug reported:
Binary package hint: ksmserver
Distributor ID: Ubuntu
Description:Ubuntu jaunty (development branch)
Release:9.04
Codename: jaunty
Linux 2.6.28-8-generic #26-Ubuntu SMP Wed Feb 25 04:28:54 UTC 2009 i686
GNU/Linux
I've recently updated to Jaunty alpha 5,
Public bug reported:
Binary package hint: kscreensaver
Distributor ID: Ubuntu
Description:Ubuntu jaunty (development branch)
Release:9.04
Codename: jaunty
Linux 2.6.28-8-generic #26-Ubuntu SMP Wed Feb 25 04:28:54 UTC 2009 i686
GNU/Linux
I've been having sketchy behavior with
Tell-tale signs are the apci issues, and the nvidia MCP67 chipset, and it's
HP :/ all the Pavilion laptops with the AMD solution instead of Intel seem
to be effected. But I believe that but report is geared towards mandriva's
kernel, while this one is for ubuntu. I may be wrong tho, but they are
If i am not mistaken, the Jaunty alpha series boots from the 2.6.27 kernel
series with the problem on install. What actually fixes the problem is the
2.6.28 kernel you can update to. If it doesn't show up in the normal
updates, try checking pre-release or unsupported. If people are getting this
to
In regards to the GIT question, I have not tried it.. but I came across this
which might be something for you to look at... it's a zen kernel for
2.6.28.
https://wiki.kubuntu.org/ZenKernel
On Sun, Feb 1, 2009 at 2:55 PM, Morten Minke
mor...@earthrevealed.comwrote:
** Description changed:
I actually don't believe this problem is fixed at all. I messed with
jaunty when I had heard that this problem was fixed in the 2.6.28 kernel but
experienced erratic keyboard/mouse behavior. Might just be me but I never
had the problem in intrepid. Now, I am not sure exactly what your problem is
I am guessing these won't make it into kde 4.2 until the official
release?
On Thu, Jan 22, 2009 at 7:54 AM, Scott Kitterman
ubu...@kitterman.comwrote:
It's automatically built. The amd64 buildds are just running a bit
behind.
--
solid-bluetooth needs update for bluez 4.x
I just updated my packaged for intrepid w/ kde 4.2rc1 and got the app
upgrade, seems to be working, I will try to pair it with something later to
see if it's fully functional.
On Thu, Jan 22, 2009 at 10:48 AM, Scott Kitterman
ubu...@kitterman.comwrote:
The ones you want are version
I've apparently managed to break it already. I was attempting to pair it
with my cellphone when the kbluetooth4-devicemanager crashed. It now
refuses to open with the following output:
kbluetooth4-devicemanager(8445)
Solid::Control::ManagerBasePrivate::loadBackend: Backend loaded: BlueZ
This glitch is hard to reproduce. My laptop functions fine for whatever
reason, it's aware of the existance of
./usr/share/services/fileshare.desktop ; I can even use it in dolphin.
System Settings - Advanced - Samba also works perfectly.
Here on my desktop neither work, I even tried copying the
some more wierdness, i installed locate to see where the file exists. It
didn't show up in /usr/share/services/ it showed up in
/usr/share/kde4/services/
On my desktop:
/usr$ find | grep fileshare
./lib/kde4/fileshare_propsdlgplugin.so
./lib/kde4/kcm_fileshare.so
Tried compiling it this morning for intrepid + kde 4.2rc1 and came up with
this:
[ 3%] Building CXX object src/CMakeFiles/kbluetooth4.dir/agent/agent.o
/home/srelysian/kbluetooth4/src/agent/agent.cpp: In member function 'void
Agent::Authorize(QDBusObjectPath, const QString)':
/home/srelysian
The triage will be broken this month. So far as I've read, kbluetooth4
is the cuplrit, which is why the 3.x drivers work with it. It was only
ported and not set up to function on the bluez4 system. Downgrading
bluez puts it into a version series it can get along with, but so far as
I have been
The more I think on this, the more it aggravates me. I was scrolling through
the posts earlier to see if any of the dev's have even spoken up about it,
and I came across something to the effect of not having time to fix it.
This isn't some obscure mouse that for some reason doesn't work, it's an
Tom
references the repository experimental code can be found in that has
already partially been ported.
It would also help if every one of us voted an the KDE bug so that it
gets fixed in the 4.2 release.
SRELysian: I guess this bug doesn't really move forward simply because
no (K)Ubuntu
You have my (20) vote(s). Hopefully this will change the priority a
little.
On Fri, Jan 16, 2009 at 8:40 AM, frapell frap...@gmail.com wrote:
@Niels Ganser:
Yes, that was the answer i was referring to... forgot to add a link there,
heh...
The mail i sent him was asking how to start, if i
I haven't seen the 2.6.28 kernel either, really hoping it makes it in, since
it's a ways off before they release Jaunty. I have enough beta'd software on
this laptop as it is, I prefer not to make it worse.
On Thu, Jan 15, 2009 at 8:58 AM, Perpetual lando...@yahoo.com wrote:
Jordan Dunn, which
No offense to you sir, but I really wouldn't consider it fixed when the
problem is still present in the current official release. The only ways to
fix it are to either A) compile the kernel yourself, or B) dist-upgrade to
an Alpha testing release. As well, the distro listed when the bug-report was
.
On Thu, Jan 15, 2009 at 11:44 AM, Andy Whitcroft a...@canonical.com
wrote:
@SRElysian, @Joschi Holaubek -- I think you have missunderstood. What
has happened is the Linux task has been closed. This task _always_
represents the bugs state in the development release, in this case
Jaunty. Which as I
That's hard to say, from what I read the .28 kernel has some
brand-spanking-new stuff in it. Supposedly, it works in Intrepid as is. I've
been poking around on random forums and blogs and found that there are quite
a few people now who are temporarily adding the Jaunty repos` just long
enough to
I think my post can be ignored and this can be disabled again, I found
out later, that while KDE doesn't recognize my mp3 player as a storage
device, Amarok (atleast 2.x) detects and allows me to manage it. So long
as I use it through Amarok I can put music on it, though I'd prefer to
be able to
** Description changed:
Once the Ubuntu splash screen loads with the progress bar that moves back and
forth, it freezes. Holding down any key unfreezes the system, and it continues
loading normally, until I release the key, at which point it freezes again.
Holding a key down again
Still not fixed as of kernel 2.6.27-9
** Changed in: linux (Ubuntu)
Status: Invalid = New
--
Mass Storage USB device error
https://bugs.launchpad.net/bugs/179250
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Info:
I have a GoGear SA6145/37, and it is experiencing the same problem. I am
currently running Kubuntu 8.10 (Intrepid Ibex). I will post any relevant
information.
** Linux 2.6.27-9-generic #1 SMP Thu Nov 20 21:57:00 UTC 2008 i686
GNU/Linux
** I pulled the following from lsusb -v
Bus 003
** Also from hwinfo --disk
31: USB 00.0: 10600 Disk
[Created at usb.122]
UDI:
/org/freedesktop/Hal/devices/usb_device_471_2002_3730053B95E208051315010209CB_if0
Unique ID: KRJj.mU6_6JUAdE3
Parent ID: uIhY.OqydEZZ981A
SysFS ID: /devices/pci:00/:00:02.1/usb3/3-1/3-1:1.0
Sorry you feel that way gizmoguy, but I am sorry to say the threats of one
person aren't going to change anything. I've been using intrepid since beta,
and have been dealing with the problem since then. I've been using a boot
variable to get around it and the problem itself doesn't really bother
Just wanted to say I have this same problem with Toshiba Satellite
A35-S139 I tried hpet=disable to no avail. Note I also booted with
Fedora 10 live cd and it has the same problem.
Try acpi=noirq and see if that helps you.That's the one I've been
using on my Pavilion dv9610.
--
System freezes
Can confirm that
http://launchpadlibrarian.net/18798999/zsnes_1.510-0ubuntu1_i386.deb
works perfectly fine, however, it is considered a downgrade.
$ sudo dpkg --install zsnes_1.510-0ubuntu1_i386.deb
dpkg - warning: downgrading zsnes from 1.510-2.1ubuntu1 to 1.510-0ubuntu1.
(Reading database ...
I am going to ask a dumb question here, I've done a bit of research but
can't seem to find a good explanation as to what the consequences are so
I figured I'd ask here just to get the record straight for myself as
well as anyone else with this issue trying to get the same information.
So far I've
rafaeljcg: thanks for the link, it was full of all sorts of useful
information and I have bookmarked it accordingly.
I found another issue which I suspect may possibly be a result of this
on-going bug, however, since I am not sure I was hoping I could get some
insight from a few guys frequenting
It had just dawned on me to test my remote last night to find it
worked... litterally... once. I have no idea what the deal is there but
judging by the last few messages here n there, it seems that this might
be tied in to this same on-going issue. I have the dv9610us (Turion64x2,
nVidia, etc),
I too can confirm this, no Wine menu. All Wine apps show in Lost
Found, including itself :/
--
Wine related applications are in Lost Found in K menu.
https://bugs.launchpad.net/bugs/263041
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I found a way to fix it... it turns out that while kde-applications.menu
contains the mergedir option, kde4-applications does not, so, I fixed it
like so:
sudo nano /etc/xdg/menus/kde4-applications.menu
or if you are not a console jockey:
alt-f2
kdesudo kate
I can confirm this problem, I started working on tweaking out my kde
desktop this morning. I was changing color schemes, icons, etc and
decided to switch my login screen to match. Found a couple I wanted to
try out but when I tried to install some behavior became erratic.
Sometimes there would be
I can confirm that acpi=noirq fixes the problem on the HP Pavilion
dv9610us. I am starting to notice a trend, heh. I am actually curious
to know how many of these plagued pavilion laptops originally had
vista on them :P I know mine did, and I was proud to be rid of it.
--
System freezes during
I noticed this seems to be a plague on HP Pavilion laptops. I've been
experiencing the same problem on my dv9610us since the install of 8.10
beta (now official). I tested it with acpi=off to find that it booted
just fine but no power management with that option (which is no good for
a laptop you
77 matches
Mail list logo
