Public bug reported:
Here is the result in gdb :
$ LC_ALL=C gdb empathy
(gdb) run
[Thread debugging using libthread_db enabled]
[New Thread 0xb6771b70 (LWP 19262)]
(empathy:19256): libebook-WARNING **: Can't find installed BookFactories
(empathy:19256): GLib-CRITICAL **: g_propagate_error:
Same problem with my other computer :
lspci | grep VGA
01:00.0 VGA compatible controller: nVidia Corporation G86 [GeForce 8300 GS]
(rev a1)
Seems not to depend on the graphical card.
--
kdeinit4: plasma-desktop takes 60-90% of CPU
https://bugs.launchpad.net/bugs/419054
You received this bug
Public bug reported:
The process plasma-desktop uses most of time between 60 and 90% of my
CPU when KDE is started.
In order to fix the situation (and make plasma-desktop use ~ 10% of CPU), the
following works most of time
1. right click on the desktop
2. unblock widgets
3. re-block widgets
Public bug reported:
Binary package hint: ubiquity
There should be a verification for critical hardware regression before
performing an upgrade.
That should be implemented at two levels.
1. The live-CD should check when launching the Ubiquity
2. The upgrade manager should also check it when it
I created a new bug (that has to be understood as a wishlist). I propose
a solution to avoid new cases of critical regressions that could impact
poor end-users who end up with an useless computer.
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/384039
--
[i965] X freezes starting on
I think that this one is the one we are speaking about :
http://brainstorm.ubuntu.com/idea/17218/
So it is already in the brainstorm. I don't know if there is something
more to do. I don't think that we should open a new idea in the
brainstorm in order to say that one should not only check for
In fact, there is already an idea in the Brainstorm database :
http://brainstorm.ubuntu.com/idea/17218/
I think that implementing it could prevent, for the future, problems
like the one we are facing now.
--
[i965] X freezes starting on April 3rd
https://bugs.launchpad.net/bugs/359392
You
At present, with a 6 months release
cycle, users should probably be considering moving to a release around
the time its successor is released. Or staying with an LTS, and
upgrading when the successor's .1 comes out.
By the way, this is what most of people do with Windows. Even more :
I still have freezes.
K-Jaunty with Compiz effects enable.
I added the following to my sources.list
deb http://archive.ubuntu.com/ubuntu/ jaunty-proposed main
deb http://ppa.launchpad.net/ubuntu-x-swat/x-updates/ubuntu jaunty main
My graphical card is (from lspci)
00:00.0 Host bridge: Intel
vervelover a écrit :
Well, I totally understand who is seeking for a new distro, maybe one
that really is for human beings. Because you favor the geeks, giving
them the latest and greatest, 'cause they know what a ppa is and
whatever. But you know if you were serious about a distro for human
Can someone indicate me how to apply the workaround, from a liveCD ?
I added it in my source.list :
deb http://be.archive.ubuntu.com/ubuntu/ jaunty-proposed main
I got some upgrades, but no ameliorations for the freeze. I guess that I have
something else to do. There are more than 400 comments;
I'm also impacted by freezes since (more or less) the same datum.
My hardware is :
00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960
Integrated Graphics Controller (rev 03)
By the way, the workaround proposed here (for other reasons) seems to fix the
situation about
Reported to KDE.
https://bugs.kde.org/show_bug.cgi?id=189623
** Bug watch added: KDE Bug Tracking System #189623
http://bugs.kde.org/show_bug.cgi?id=189623
--
okular crashes when refresh compiling DVI files
https://bugs.launchpad.net/bugs/360647
You received this bug notification because you
Public bug reported:
Binary package hint: kdegraphics
1. Open a large DVI file with Okular (see an example of LaTeX source file
bellow)
2. Compile the tex file
3. Okular crashes when refresh under certain conditions.
At a certain point during the compilation, Okular remarks that the DVI is
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/25352967/Dependencies.txt
--
okular crashes when refresh compiling DVI files
https://bugs.launchpad.net/bugs/360647
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Bug opened there :
http://bugzilla.gnome.org/show_bug.cgi?id=576630
I answer the question about dbus at that place.
--
Keyring should launch itself when needed
https://bugs.launchpad.net/bugs/34
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
Binary package hint: gnome-keyring
gnome-keyring-daemon should launch itself when needed.
I have a fresh install of K-jaunty, and I installed Empathy. Now, when I launch
empathy, it refuses to connect my accounts because keyring-daemon is not
working.
If I type
I confirm the bug for Ubuntu and Kubuntu RC-1 : download the live-CD, burn,
reboot on the live-CD --- Busy box.
I attach my lspci.
If it can help you to improve the product, my computer is *the* Dell
that was sold with pre-installed Feisty (Inspiron 530). Feisty and Gutsy
work perfectly.
**
I confirm the bug on live-CD Ubuntu and Kubuntu RC-1.
By changing IDE - RAID,it works well.
(Dell Inspiron 530, lspci in attachement)
** Attachment added: lspci.txt
http://launchpadlibrarian.net/13745752/lspci.txt
--
Dell Inspiron 530 SATA drive not detected in IDE mode
I have the same problem with alpha6 (Ubuntu and kubuntu). After
launching the liveCD, I enter the busybox.
In qemu, I notice the following unusual (for me) message before boot:
[0.00] ACPI: no DMI BIOS year, acpi=force is required to enable ACPI
[ 14.464065] PCI : PIIX3: Enabling
uname -a
Linux moky-laptop 2.6.20-16-generic #2 SMP Sun Sep 23 19:50:39 UTC 2007 i686
GNU/Linux
** Attachment added: dmesg when suspend to swap
http://launchpadlibrarian.net/10862883/dmesg-swap.log
--
keybboard problem after sleep
https://bugs.launchpad.net/bugs/110762
You received
The same probmec occures when suspend to ram or when suspend to swap.
** Attachment added: dmesg when suspend to ram
http://launchpadlibrarian.net/10862960/dmesg-ram.log
--
keybboard problem after sleep
https://bugs.launchpad.net/bugs/110762
You received this bug notification because you
** Attachment added: lspci when no problems
http://launchpadlibrarian.net/10862951/lspci-vvnn-correct.log
--
keybboard problem after sleep
https://bugs.launchpad.net/bugs/110762
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
** Attachment added: lspci when suspend to ram
http://launchpadlibrarian.net/10862956/lspci-vvnn-ram.log
--
keybboard problem after sleep
https://bugs.launchpad.net/bugs/110762
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
** Attachment added: dmesg when no problems
http://launchpadlibrarian.net/10862949/dmesg-correct.log
--
keybboard problem after sleep
https://bugs.launchpad.net/bugs/110762
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
** Attachment added: lspci when supspend to swap
http://launchpadlibrarian.net/10862904/lspci-vvnn-swap.log
--
keybboard problem after sleep
https://bugs.launchpad.net/bugs/110762
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
Yes, it is still an issue. But only under a fully upgraded K-Feisty, on
one laptop. For some (hardware) reasons, I cannot upgrade it to newer
Ubuntu versions. Thus I cannot confirm the bug for Gutsy or Hardy,
sorry.
Laurent
--
keybboard problem after sleep
Public bug reported:
When I recover from a sleep, the keyboard has problem: it sometimes
produces 10 times the same character. I obtain this kind of text :
abcdeffghijklmnopqrsttuvwxyz
I am using Feisty fawn (from beta, but updated) but I has not this problem
three mouth
It am able to precise the problem. In fact, I was using a feisty which was just
a dist-upgrade from Edgy.
Now I installed Feisty from Herd4. No more problems.
So the problem is not a true Feisty Vs Edgy problem, but rather a problem in
the way to upgrade from Edgy to Feisty.
--
Well. The iwconfig of Edgy and Feisty are pretty different :
-- EDGY ---
22:35:37 ~$ iwconfig
lono wireless extensions.
wlan0 IEEE 802.11b+/g+ ESSID: Nickname:acx v0.3.21
Mode:Managed Frequency:2.412 GHz
Yes it is installed.
07:45:09 ~$ LC_ALL=C dpkg -l linux-restricted-modules-`uname -r`
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name
Public bug reported:
Binary package hint: wlassistant
wlassistant does not detect my Wifi network under Feisty while it works
perfectly under Edgy. :'(
Here are some output of lspci and dmesg :
FEISTY
lscpi
FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 80)
If the installation of ffmpeg is accepted, then SoundJuicer should be hacked in
such a way that the correct mp3 pipeline is automatically added.
...
and maybe amarok too... :)
--
Should install gstreamer0.10-ffmpeg
https://launchpad.net/bugs/77707
--
ubuntu-bugs mailing list
Public bug reported:
Binary package hint: gstreamer0.10-fluendo-mp3
Hello
Untill now, after installing gstreamer0.10-fluendo-mp3,we have to add
manually a new profile in Sound-Juicer to extract CD into mp3. I think that the
package should add the new pipeline itself, so that once
Public bug reported:
Binary package hint: sound-juicer
Dear developpers
In order to extract CD in mp3 format, I add a new profile. This profile
does not appears immediatly in the list of ourput formats : one needs to
restart sound-juicer to be able to extract in mp3 format.
That's
I confirm the fact that I have two DHCP computers on the same router. The one
has the bug while the orther has not.
However the proposed solution works.
Thanks you. Without your help, I would still be on Dapper ;)
Laurent
--
Network unreachable with Edgy
https://launchpad.net/bugs/58927
I think it is not a router problem. On the same router at home, Edgy works on
my computer while it doesn't works on my laptop.
But the same laptop that has the bug at home has no problem at university.
It should be a combination of the router and the internal network card.
--
Network
Public bug reported:
Hello
As other latest bugs in ubiquity, I report a crash with the daily 11.09.2006.
As far as I remember this problem did not appears with knot2.
Have a nice day
I tryed twice and it crashes twice.
Traceback (most recent call last):
File /usr/bin/ubiquity, line
** Attachment added: my syslog file as asked
http://librarian.launchpad.net/4227855/syslog
--
Installer crashed for Kubutu, daily 11.09.2006
https://launchpad.net/bugs/60045
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
That's all.
Thanks
** Attachment added: my partman file as asked
http://librarian.launchpad.net/4227857/partman
--
Installer crashed for Kubutu, daily 11.09.2006
https://launchpad.net/bugs/60045
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Public bug reported:
Binary package hint: ubiquity
When you creates partitions at hand (qtparted), there is a message :
« Assure vous d'allouer ... »
the correct spelling is
«AssureZ vous d'allouer ...»
I found this error on the Dapper live install; it is still in the daily
11.09.2006 (which
Public bug reported:
Binary package hint: ubiquity
Hello
this is a feature request.
When you install kubuntu with the live-cd, you have to choose a city on a
world map. I think it should be possible to zoom on the map as with Ubuntu (for
example : Bruxelles, Luxembourg,Paris and
Public bug reported:
Binary package hint: ubiquity
Feature request
When you install Kubuntu from live CD, I says that I am living in
Brussel (Belgium). Then when the installer ask me my keybord, I think
that Belgian should be preselected.
thank for all the work
Laurent
** Affects: ubiquity
Public bug reported:
Hi everyone
I am in a trouble with my internet connection on Edgy knot2 (the same was
already buggy with knot1). The default DHCP does not work at all : host
unreachable.
When I configure a fix IP and when I give my rooter as DNS, I am able to
solve ip (host
Some propositions about Synaptic menu
Apply marked changes Edit --- packages (logically with the Mark for
installations, for uninstallation, ...)
Unmark all Edit --- Packages (just bellow Unmark)
Preferences Setting Edit
Rename Setting --
45 matches
Mail list logo
