Same problem, solution in #9 helped me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766020
Title:
package python3 3.6.5-3 failed to install/upgrade: installed python3
package post-installation
I can confirm this on a fresh install of Ubuntu 12.04 64-bit: this
happened to me two times within the last week already. Just before the
fox goes nuts, memory usage is about 2-3G (entire system, not firefox
only). And then within few seconds all RAM (8GB here) is gone, the
system starts swapping,
** Tags added: amd64
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1014234
Title:
Firefox hogs all memory and swap
To manage notifications about this bug go to:
Public bug reported:
during install
ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: xbmc-live 2:11.0~git20120423.cd20772-1
ProcVersionSignature: Ubuntu 3.2.0-24.39-generic-pae 3.2.16
Uname: Linux 3.2.0-24-generic-pae i686
ApportVersion: 2.0.1-0ubuntu8
Architecture: i386
Date: Wed Jun
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1012608
Title:
package xbmc-live 2:11.0~git20120423.cd20772-1 failed to
install/upgrade: subprocess installed post-installation script
returned
Public bug reported:
It seems that when update-apt-xapian-index runs while Muon Package
Manager is in use, search is disabled until Muon is restarted. Ideally,
I'd expect the old index to remain available until the update is
complete and user notification if there is a need to restart an open
This appears to be the same issue as bug 831768. Short version:
multiarch support, enabled by default in Ubuntu 11.10, causes each
architecture of a package to have an entry in the package database.
Aptitude is not multiarch aware and displays one at random. It appears
that at least a decent
Public bug reported:
I was trying to open up the terminal and received this error. Computer
graphics are much slower compared to 11.04. Using 11.10 development
branch (I think beta 2?).
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: libnux-1.0-0 1.14.0-0ubuntu1
ProcVersionSignature:
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/868824
Title:
compiz assert failure: *** glibc detected *** compiz: double free or
corruption (!prev): 0xad673960 ***
To manage notifications about
I too am having this issue. Running 10.04 x64
lfconfig
wlan0 Link encap:Ethernet HWaddr 00:16:44:1e:66:a9
inet addr:192.168.0.198 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::216:44ff:fe1e:66a9/64 Scope:Link
UP BROADCAST RUNNING MULTICAST
** Changed in: ubuntu
Status: Incomplete = Invalid
--
apt no internet
https://bugs.launchpad.net/bugs/476126
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
Public bug reported:
I installed Ubuntu 9.10, all my hardware works fine. I can install .deb
packages, but apt fails to download anything from the internet. My
internet connection works fine.
** Affects: ubuntu
Importance: Undecided
Status: New
--
apt no internet
Update: I found a new work-around. While KDE has problems with fstab
entries starting with UUID= (results in permission denied when
trying to mount that drive via the desktop icon), the following worked
like a charm:
/dev/disk/by-uuid/FD71-883A /media/diskautorw,user,noauto
0 0
Bad news: No my work-around of restarting the HAL daemon is no longer
working - all that's left is to mount new devices manually at a shell
prompt. Some updates have been applied since my last comment:
Kernel 2.6.24-24-generic
Hal: 0.5.11~rc2-1ubuntu7
DBus: 1.1.20-1ubuntu3.3
After a reboot,
Correction: Due to a too small terminal window, dpkg -l was cutting of
the version numbers. Using apt-cache show I missed that it listed
multiple sources. So versions above should correctly read:
Kernel: 2.6.24-24.61 (generic - just updated now)
Hal: 0.5.11~rc2-1ubuntu8.3
DBus: 1.1.20-1ubuntu3.3
Now that FF3.5 is out for a while, and even available in Jaunty as I
read here: Are there any plans to make it available for the current LTS
(Hardy Heron) via hardy-backports? Since the package is called
firefox-3.5, there would be no danger of accidental updates - but
people who want/need it
I've got the same problem for a couple of months now. I can confirm it
is a hal problem: My usual work-around is to restart the hal daemon
(/etc/init.d/hal restart). After that it is possible again to mount
those USB devices - but you always have to put in your password then.
After a complete
@Ivlo: 200Mb you can almost count as normal behavior (though I agree
this is already far to much, and to me indicates some memory leak).
Guess you don't have any WebCal resource in use for (one of) your
calendar(s)? If you want a zero more at the end, try that :(
I'm quite disappointed it takes
Suffering from the same bug here on one machine (office), while not on
the other (home). Both machines are running Hardy, both use the same
repositories - so it's the same versions. The office machine has one
more large IMAP account configured, plus a couple of CalDav calendars.
Looking back, to
[EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED], Ana Verissimo
[EMAIL PROTECTED], Angela [EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED], Izzy Kiefer [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED],
MARCIA MADZELLE [EMAIL
As I wrote above, I closed all BT apps and even removed the Bluetooth
stick to check whether Bluetooth may be the cause. Now, 7 days later, it
looks like I can approve this: Since I've done so, no more Oops
appeared, and the keyboard is still working fine - so the bug must have
to do with
Public bug reported:
Binary package hint: linux-image-generic
The following problem started with kernel 2.6.26-20 and still persists
with 2.6.26-21 on (K)Ubuntu Hardy 8.04.1, both installed via apt from
the official proposed repository (currently linux-image-generic
2.6.24.21.23).
Returning to
** Attachment added: latest entries from dmesg including Oops and Call Trace
http://launchpadlibrarian.net/17551989/crash.log
--
Daily kernel Oops kills keyboard
https://bugs.launchpad.net/bugs/269322
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: Modules loaded at time of Ooops (lsmod output, sorted)
http://launchpadlibrarian.net/17552041/mods.log
--
Daily kernel Oops kills keyboard
https://bugs.launchpad.net/bugs/269322
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Glad to read this - you are very welcome!
--
Gutsy-Hardy upgrade hangs in localedef
https://bugs.launchpad.net/bugs/249340
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
@joe: Why? Once the upgrade is finished, you can use the latest kernel
again. But if you insist on the -14 kernel to be used, check your
/boot/grub/menu.lst - with the keyword default n (where n is a
number) you can define which option should be automatically used (if
user doesn't decide otherwise
@Gregory: The problem probably does not come up with the direct upgrade
from Dapper, since as it reads it is introduced by the latest kernel
from Gutsy. I just upgraded my server from Dapper last weekend (and to
make sure to not hit the problem, I removed the execute bit from
/usr/bin/localedef as
@Tony Maro: To get at least your broken dependencies fixed without a
hang, you could try the following:
chmod 644 /usr/bin/localedef
# fix your dependencies here:
# apt-get install -f (or whatever)
chmod 755 /usr/bin/localedef
# here you may try to repair your locales (optionally)
#
@jbg7474: Maybe bug #250891 does match your description better? Other
than with this bug here, it has a different error message displayed in
the logs, and you even can use ALT-Fn to switch to an alternate console
(which is impossible here). You may want to check your
/var/log/Xorg.?.log (replace
@Jason: Don't get me wrong - I wasn't telling you you are wrong here
(besides, I'm even not the one who should do so - I'm just another user
affected by a similar bug - namely the other one mentioned). It was just
a suggestion to check, since you seemed to be able to act with your
keyboard which
Ooops - confirmed: With modifiers it still doesn't work neither in xterm
nor in gnome-terminal. In konsole, however, everything is still fine...
--
[feisty] function keys don't work in gnome-terminal
https://bugs.launchpad.net/bugs/96676
You received this bug notification because you are a
I cannot check anymore - CPU changed meanwhile.
--
No powernow support on Athlon 64 (amd64)
https://bugs.launchpad.net/bugs/111375
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
Just wanted to report that the problem disappeared for me after a dist-
upgrade to Hardy (via Gutsy, of course). So maybe the bug is silently
solved?
--
[feisty] function keys don't work in gnome-terminal
https://bugs.launchpad.net/bugs/96676
You received this bug notification because you are a
Must be a fix in some underlying libraries - for me it's not only solved
in gnome-terminal, but in xterm as well (I only tested with the Midnight
Commander). So if some more people can confirm it's gone, the maintainer
maybe can close the bug as solved.
--
[feisty] function keys don't work in
Anybody here reading this?
** Tags added: nvidia
--
X crashes on logout - takes long to come up on boot
https://bugs.launchpad.net/bugs/250891
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Attaching the Xorg log file in the hope it helps on the issue.
Missing technical details:
* 32bit Ubuntu (on an AMD64) - kernel 2.6.24-19-generic
* nvidia-glx 1:96.43.05+2.6.24.14-20.46
* xorg 1:7.3+10ubuntu10.2
If I missed something else, please let me know.
** Attachment added: Xorg.log
Also attaching the Xorg.0.log of the last boot - just in case
** Attachment added: xorg logfile of the last boot
http://launchpadlibrarian.net/16284097/Xorg.0.log
--
X crashes on logout - takes long to come up on boot
https://bugs.launchpad.net/bugs/250891
You received this bug notification
Alberto,
thank you for your reply. Did what you suggested - problem stays the
same. But now I can state more clearly it *must* have to do with X: It
runs through the init scripts normally, and right after the battery
check (which is told to be [OK]) it stalls for about 20..30 seconds.
Next
I checked all the log files now to get some indicators. All I could find
out is a gap of 34 seconds between the last pre-KDM entry and the first
KDM-entry - so it seems that KDE takes more than 30 seconds to come up.
I also attach the latest piece from the KDM log, which may provide some
I had exactly the same with nvidia-glx 1:96.43.05+2.6.24.14-20.46 here -
so the problem seems to have remained. However: I removed nvidia-glx
switching back to nv, and then asked jockey to install the restricted
drivers again - it chose to install nvidia-glx-new. Not sure if the
problem remained
@mash and @Ryan: You might want to have a look at bug #224085 (this bug
here in fact may be considered a duplicate of that). Probably the things
suggested there will help you as well. For me (and some others) on KDE,
it helped to just add
!-- modification in order to KDE users can mount --
Some more details on the PC with the heavy problems: The card is a
GeForce 6100 nForce 430 (according to nvidia-settings). I removed the
above mentioned GDM links, nothing changed. Even more: If I do a warm
boot after logging out from KDE (and having no other choice, since I
have only the black
I was just browsing with synaptic and found some interesting maybe-hint:
There have been changes with the package locales, which is replaced
now by belocs-locales-bin (which is marked installed). However, the
package belocs-locales-data is NOT installed. Is it possible that this
causes the problem
Public bug reported:
Binary package hint: xorg
Not sure whether it applies to xorg or rather some installation
scripts...
After upgrade from Feisty to Hardy, X takes very long to startup after
boot (user just sees the black screen with the last boot messages, ended
with No resume image, doing
Ooops... Just checked the log files of the second machine, and found the
same crash there - so I just didn't notice. So it may be I also did not
notice the slow startup since I haven't rebooted that machine ever after
the dist-upgrade...
On the second machine, the gdm startup scripts are also
It has. I just upgraded yesterday and ran into the same problem with
8.04.1 (so even the first fix pack does have this problem).
If I look closer on that file, it seems that somebody could not decide
what policy to take - both times it is context=default, and the only
difference is that one block
@mash:
Did you check your /etc/fstab if it has corresponding entries? These should
*not* have noauto in if you want the drives to mount automatically. I never
tested this, but probably with proper fstab entries they should be handled as
on boot when connected.
Well: That was much easier on
I just ran into the same problem a few hours ago. Google brought me to
the same sources as quoted above. Compiling the collected information,
here is a work-around that did it for me (step-by-step - so everybody
can solve it until the bug is fixed):
run the dist-upgrade as recommended. If the
ALright no problem .. thanx anyway .. it not a big deal anyway .. you can
chaneg it to the way you want just clicking on the wiew menu .. just trying
to help you guys improve the os .. anyway i can help .. lol thanx
On Nov 13, 2007 7:32 AM, Pedro Villavicencio [EMAIL PROTECTED] wrote:
Thank you
Public bug reported:
Binary package hint: nautilus
When you choose View as Icons or view as List it works perfect , but when you
click on preferences and choose view as icons or or view as list and hit close
nothing changes ..
THank you
** Affects: nautilus (Ubuntu)
Importance: Undecided
-r /media/cdrom0
/media/cdrom1 /media/dumper/Music/Mp3
ProcCwd: /home/izzy
ProcEnviron:
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
LANG=en_US.UTF-8
SHELL=/bin/bash
Signal: 11
SourcePackage: amarok
StacktraceTop:
QPixmap::convertFromImage ()
QPixmap
** Attachment added: CoreDump.gz
http://launchpadlibrarian.net/10002694/CoreDump.gz
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/10002695/Dependencies.txt
** Attachment added: Disassembly.txt
http://launchpadlibrarian.net/10002696/Disassembly.txt
** Attachment
times out. None of the workarounds described here helps. In
the other direction (initiating the session from the VMWare to the
Ubuntu host), it already hangs a couple of lines earlier (debug1:
identity file /home/izzy/.ssh/id_dsa type -1. Any hints where else to
look or what to toggle?
Btw: @Lars
I just found out that the problem does *NOT* appear with konsole.
Checking a bit deeper, it uses TERM=linux - setting TERM=xterm here
breaks a few things again. The other way round (setting TERM=linux in a
xterm session) is not helpful at all. Side-effect of TERM=linux is that
you lose mouse
First it is very funny: Half a year just pointing at each other saying
There's the problem, not here!. :-(
@Thomas Dickey goes Second:
===[ cut here ]===
[EMAIL PROTECTED]:~$ echo $TERM
gnome
[EMAIL PROTECTED]:~$ mc
Unknown terminal: gnome
Check the TERM environment variable.
Also make
Instead of fighting for who's fault it is: Is it somehow likely that this will
be fixed in the near future? I guess the standard user is not interested in
the fact whether the bug is because of ncurses, xterm or whatever. To me it is
completely irrelevant whether xterm follows the rules
Just to push it again: Same problem for me. Any chance to see a fix in
the near future? I just updated my mainboards BIOS (the update contained
a patch for this processors support), but still Ubuntu (Feisty)
recognizes only one core and powernow_k8 does not load (Processor cpuid
70ff1 not
OK - sounds like progress, we were just clearing up things and now the
*issue* is clear. Agree with you we need to check which package needs
the corrections: Whether xterm behaves correctly (and terminfo needs to
be fixed), or xterm is broken (which means xterm, gnome-terminal etc.
need to be
Micah,
I'm afraid I must disappoint you. The entire problem started (for me)
with Feisty and only appears when working locally. When I log in via ssh
(i.e. not Ubuntu xterm, but e.g. RHEL4), everything works as expected:
Shift-F4 opens a new file to edit. If it was mc causing problems, I
would
This also affects xterm - same behavior as described for gnome-terminal
** Also affects: xterm (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
[feisty] function keys don't work in gnome-terminal
https://bugs.launchpad.net/bugs/96676
You received this bug notification because you
60 matches
Mail list logo
