I have done the same testing like Jérôme Guelfucci and everything works fine
except that I can still reproduce the bug...
I have read comment #6 very thorough and I can conclude, after tweaking my
screen settings (there seamed to be some pixels off my screen :s), there is
indeed a small line. Th
Never mind my post above. Forgot to reboot... Can't reproduce the bug
anymore :) Thanks Lionel, Jérôme and Jim.
** Changed in: xfce4-panel (Ubuntu)
Status: In Progress => Fix Committed
--
[Hardy A3] [Xubuntu] Panel disappears when dragging files
https://bugs.launchpad.net/bugs/185448
You
*** After Burning an .iso to a CD ***
xfce4-systemload-plugin: 594 MB
gnome-system-monitor: 216.3 MB
** Attachment added: "FreeBurnIso.txt"
http://launchpadlibrarian.net/12515877/FreeBurnIso.txt
--
[Hardy A3][Xubuntu] Incorrect Memory Value
https://bugs.launchpad.net/bugs/187164
You received
*** With only firefox running ***
xfce4-systemload-plugin: 241 MB
gnome-system-monitor: 186.6 MB
** Attachment added: "FreeFireFox.txt"
http://launchpadlibrarian.net/12515865/FreeFireFox.txt
--
[Hardy A3][Xubuntu] Incorrect Memory Value
https://bugs.launchpad.net/bugs/187164
You received this
*** After copying an .iso from an external HDD ***
xfce4-systemload-plugin: 645 MB
gnome-system-monitor: 213.3 MB
** Attachment added: "FreeCopyIso.txt"
http://launchpadlibrarian.net/12515874/FreeCopyIso.txt
--
[Hardy A3][Xubuntu] Incorrect Memory Value
https://bugs.launchpad.net/bugs/187164
I have done some more testing. I have started my system, opened FireFox
and took a look at my memory values. After that I copies an .iso from my
external HDD to my local HDD, and took a look at my memory values. After
that I burned the .iso and took a look at my memory values.
These are the result
Due to circumstances, probably the soonest I can rerun the tests will be
11 march. Just to let you know.
--
[Hardy A3][Xubuntu] Incorrect Memory Value
https://bugs.launchpad.net/bugs/187164
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The Release Candidate (20100419) has broken the nomodeset-workaround.
Laptop is crashing again with flickering diagnostic leds. This bug won't
be solved before the release of Lucid, will it?
** Description changed:
Binary package hint: plymouth
*** System ***
Dell Vostro 1500
Intel T75
Just finished testing the latest ISO QA (20100427) and this bug is still
standing.
Since Lucid will be released in a few hours, here is my workaround to get it
booting:
Update your boot-options to the following (F6 in the menu of your live-CD or
"e" in your grub2 installation or add it in /etc/d
Public bug reported:
Binary package hint: bootchart
*** System-info ***
HW: Dell Vostro 1500
OS: Ubuntu 10.04 LTS
DE: Xfce 4.6
*** Package-info ***
bootchart: 0.90.2-7
pybootchartgui: 0+r139-2
*** Expected Behavior ***
Step. 0: bootchart is installed
Step. 1: bootchart is removed by using a pac
Boot output after removing the bootchart-package.
** Tags added: ubuntu-boot-experience
** Attachment added: "boot.log"
http://launchpadlibrarian.net/48055159/boot.log
--
Bootchart doesn't get properly removed from init
https://bugs.launchpad.net/bugs/577416
You received this bug notificatio
Apparently it does:
$ ls -l /etc/init/bootchart.conf
-rw-r--r-- 1 root root 2018 2010-03-22 19:13 /etc/init/bootchart.conf
--
Bootchart doesn't get properly removed from init
https://bugs.launchpad.net/bugs/577416
You received this bug notification because you are a member of Ubuntu
Bugs, which
I tried your proposed workarounds in order to reproduce your case, with a
liveCD that was already burned, Lubuntu Lucid Beta 2:
Booting with "nomodeset" -> usable screen (This wasn't the case during beta1,
so \o/ )
Booting with "nouveau.modeset=0" -> usable screen (same as above)
Booting with "n
Public bug reported:
Binary package hint: plymouth
*** System ***
Dell Vostro 1500
Intel T7500
Nvidia 8400M GS
*** Affected ISO's ***
Ubuntu Desktop 20100316 - i386
Ubuntu Desktop 20100316 - amd64
Xubuntu Desktop 20100316.1 - i386
Xubuntu Desktop 20100316.1 - amd64
*** Actual behavior 1 ***
1.
** Attachment added: "Picture of the fuzzy Xubuntu screen"
http://launchpadlibrarian.net/41056828/Xubuntu-Fuzzy.jpg
** Description changed:
Binary package hint: plymouth
*** System ***
Dell Vostro 1500
Intel T7500
Nvidia 8400M GS
*** Affected ISO's ***
Ubuntu Desktop 20100
** Attachment added: "Picture of the fuzzy Ubuntu screen"
http://launchpadlibrarian.net/41056753/Ubuntu-Fuzzy.jpg
--
Fuzzy screen without text
https://bugs.launchpad.net/bugs/539878
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Tags added: lucid
** Tags removed: kernel-series-unknown
** Description changed:
Binary package hint: plymouth
*** System ***
Dell Vostro 1500
Intel T7500
Nvidia 8400M GS
*** Affected ISO's ***
Ubuntu Desktop 20100316 - i386
Ubuntu Desktop 20100316 - amd64
Xubuntu Deskt
\o/ Somebody how actually knows what's going wrong, great. I'm willing
to provide you all the information you need, but since I don't have much
experience in these kind of things (I know that if I install jockey-gtk,
I can play movies on my screen) I will need some advice on what I need
to do...
I
** Description changed:
Binary package hint: plymouth
*** System ***
Dell Vostro 1500
Intel T7500
Nvidia 8400M GS
*** Affected ISO's ***
- Ubuntu Desktop 20100316 - i386
- Ubuntu Desktop 20100316 - amd64
- Xubuntu Desktop 20100316.1 - i386
- Xubuntu Desktop 20100316.1 - amd64
+ U
It should remain included in the base install, since aptitude has the
value when things go wrong. If your system gets broken beyond just
fixing a configuration file, when you loose your comfy graphical
X-server, ... then aptitude's value is needed. And you (as a user for
who fixing a broken system
The error you mention isn't really an error...That's a normal exit state
for ureadahead-other, but it's init / upstart fault you're seeing that
"error".
See following bugs:
Bug #484677 (where there is explained that it's normal behavior)
Bug #522197 (where there is a bug running against upstart fo
I was able to get a bit further by supplying the following boot-option:
"vga=normal nomodeset". But my system crashes completely within the 2
minutes and a bunch of diagnostics leds are flickering indicating
something went wrong.
--
nouveau out of sync LVDS (basically card not supported)
https://
>From the Ubuntu Documenatation:
>https://help.ubuntu.com/community/Installation/SystemRequirements#Desktop%20installation
[quote]Recommended minimum requirements
Ubuntu should run reasonably well on a computer with the following
minimum hardware specification. However, features such as visual ef
*** This bug is a duplicate of bug 522197 ***
https://bugs.launchpad.net/bugs/522197
** This bug has been marked a duplicate of bug 522197
init: shouldn't log a warning/error when a job fails with a status in
"normal exit"
--
init: ureadahead-other main process terminated with status 4
h
Ehm, booting with only "nomodeset" results in the same crash as I
mentioned in Comment 6 (when booting with "vga=normal nomodeset), system
crashes during loading and the diagnostics leds are flickering as if the
are saying "Please don't do that again" :) So I can't get to console nor
desktop to ins
@GerryFerdinandus: Since we suspect that this bug-report is about an
issue with nouveau (an open-source driver for Nvidia cards) and your
system has an ATI-card, I think it's better to report a new bug about
the issue you're experiencing . Feel free to link this bug in your new
bug-report-descripti
Done some more testing on the latest liveCD, didn't really solve the
problem though:
The breakpoint: "break=top" produced a type-able terminal to put
commands in. If I only would know which command I need to type to
continue the execution...
All the other breakpoints, like modules,premount,mount,
This is still present in Jaunty_Jackalope 9.04.
Added the GST-project (gnome-system-tools) since this bug occurs when
invoking the "shares-admin"-command. So maybe there's an issue with the
front-end (shares-admin, part of gnome-system-tools) instead of a
problem with the back-end (system-tools-ba
I don't think I completely understand you. Forgive me, English is not my
native language...
You say that due to package installation there is an increase of 90MB in memory
usage. But
1) I decline the request to install any packages upon request, by clicking on
the close button. (see Step 2)
2) I
Ah, now I see. By "first time", I meant, indeed, as long as you didn't
install any packages as requested, since the install of the OS, and
close the application. Basically doing nothing from the point of view of
the shares-admin command.
You can be right about counting memory usage. I don't now ve
And why do I get the same error when trying to install the old
173-version?
** Attachment added: "jockey.log"
http://launchpadlibrarian.net/37893327/jockey.log
--
Jockey failed to install nvidia current drivers
https://bugs.launchpad.net/bugs/506618
You received this bug notification because
I also disagree to the statement of useless. I use it almost every day, and it
never crashed or disappeared from my panel... From switching it from on-demand
when being mobile to performance when I'm flash-gaming and I don't want any
stutters or when I'm running simulations for my studies and ne
I can also confirm this during live-session of Xubuntu Lucid Alpha 2 -
2010-01-12.2
Dmesg output:
[ 98.535728] CPUFREQ: Per core ondemand sysfs interface is deprecated -
up_threshold
--
Deprecate use of HAL
https://bugs.launchpad.net/bugs/503555
You received this bug notification because you
*** System ***
Hardware: Dell Vostro 1500.
Xubuntu Lucid Alpha 2 - 2010-1-12.2
I don't get the "Opening pipe..."-message and it seems that the disk
does get checked, there is only no interaction with the user.
If I run the checker with default boot options, I get a black-screen,
and it starts to
Public bug reported:
Binary package hint: xfce4-systemload-plugin
Ubuntu has set the goal for mobile devices to last longer on a single
battery charge. This can be done by several things, of which keeping the
amount of wakening the processor to a minimum. Tickless-kernels was a
great move forward
Public bug reported:
Binary package hint: gigolo
System: Xubuntu 9.04
Package: gigolo-0.3.0
Preliminary steps:
0.1) The ssh-agent gets started upon boot.
0.2) User adds his private keys to ssh-agent with ssh-add
Expected behavior:
1) User starts gigolo and chooses to connect with sftp
2) The co
Hi Leann,
That's some very good news you are bringing to us.
Just as a note to everyone who wants to use these modules. The usbip
package has still to be upgraded though, in order to get the client side
working as well. The current usbip package still expects the old
modules. But that would be on
The system with the relevant hardware in currently used in as a production
machine. I will be able to test the upstream kernel, but I need some time to
prepare another machine to take over the production role during the testing.
Also I need to find some time to do the actual testing since it's a
The issue seems to be resolved. Unable to reproduce the issue with the
following configuration:
OS: Ubundu 11.04
DE: Xfce 4.8
bootchart: 0.90.2-8
pybootchartgui: 0+r141-0ubuntu3
I'm considering this as fixed.
** Changed in: bootchart (Ubuntu)
Status: New => Fix Released
--
You received
The issue seems to be resolved. Unable to reproduce the issue with the
following configuration:
OS: Ubundu 11.04 - Natty Narwhal
DE: Xfce 4.8
gnibbles: 1:2.32.1-0ubuntu5
I'm considering this as fixed.
** Changed in: gnome-games (Ubuntu)
Status: Triaged => Fix Released
--
You received th
Tested iso: Ubuntu 11.04 (Natty Narwhal) Alpha 2
Still exactly the same issue. Although the "fuzzy" screen is a bit more gray
then purple now, but still totally screwed up...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
** Description changed:
- Binary package hint: plymouth
-
*** System ***
Dell Vostro 1500
Intel T7500
Nvidia 8400M GS
*** Affected ISO's *** (not limited to)
Ubuntu & Xubuntu - i386 & amd64
* Lucid Pre Beta & Beta 1 (201003xx)
* Lucid Beta 2 (20100406)
* Lucid RC (20100419)
I can not reproduce the bug anymore in an fully updated Lucid
installation. Neither could I find something in the source code of the
plug-in that would explain the described behavior of this bug. So bug
closed, also from my point of view.
** Tags removed: iso-testing
--
You received this bug not
It seems that the culprit was on the hardware of the wireless card
itself, a Intel Corporation PRO/Wireless 3945ABG. After replacing the
card the described behavior didn't occur anymore. So I'm closing this
since I can't reproduce the described behavior with the replaced card.
** Changed in: linux
Sure, no problem.
I'm running a complete up to date 10.04 with kernel "2.6.32-23-generic". I
re-installed the required nouveau-packages (libdrm-nouveau1 and
xserver-xorg-video-nouveau), removed my X.org-config file so it would load the
closed-nvidia driver and rebooted.
I'm now capable of booti
Just ignore the previous comment, it was a configuration-issue (Nvidia
and nouveau were both battling for the same card...)
I made a separate partition and installed a fresh 10.04 on it.
First I booted with the blacklist option (see comment #19) and did a complete
update to "2.6.32-23". Upon rebo
On a "Xubuntu 10.04 LTS" using "gigolo-0.4.0-1" I get still prompted.
I have changed status back since the info implied by the Incomplete is
delivered.
** Changed in: gvfs (Ubuntu)
Status: Incomplete => New
--
SSH-agent not used when using sftp
https://bugs.launchpad.net/bugs/501095
You
Public bug reported:
*** System ***
Hardware: Dell Vostro 1500
OS: Ubuntu 10.04 - Lucid Lynx - Linux kernel 2.6.32
DE: Xfce 4.6
*** Expected behavior ***
Wireless doesn't fail (seemingly) at random
*** Actual behavior ***
Wireless does fail (seemingly) at random with seemingly different causes
** Attachment added: "dmesg.log"
http://launchpadlibrarian.net/50428734/dmesg.log
--
kernel trace of wireless core failure
https://bugs.launchpad.net/bugs/595063
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Attachment added: "uname-a.log"
http://launchpadlibrarian.net/50428741/uname-a.log
--
kernel trace of wireless core failure
https://bugs.launchpad.net/bugs/595063
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mai
** Attachment added: "version.log"
http://launchpadlibrarian.net/50428742/version.log
--
kernel trace of wireless core failure
https://bugs.launchpad.net/bugs/595063
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mai
** Attachment added: "lspci-vnvn.log"
http://launchpadlibrarian.net/50428763/lspci-vnvn.log
--
kernel trace of wireless core failure
https://bugs.launchpad.net/bugs/595063
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bu
** Description changed:
Binary package hint: plymouth
*** System ***
Dell Vostro 1500
Intel T7500
Nvidia 8400M GS
- *** Affected ISO's ***
- Ubuntu & Xubuntu - i386 & amd64 - Lucid Pre Beta & Beta 1 (201003xx)
- Ubuntu & Xubuntu - i386 & amd64 - Lucid Beta 2 (20100406)
- Ubuntu & X
** Bug watch added: GNOME Bug Tracker #622972
https://bugzilla.gnome.org/show_bug.cgi?id=622972
** Also affects: network-manager-applet via
https://bugzilla.gnome.org/show_bug.cgi?id=622972
Importance: Unknown
Status: Unknown
--
nm-applet notifications show multiple "Don't show t
Confirming Robert Wall's observations, reproduction is more general then
only suspend&resume, even a plain connect-disconnect cycle introduces a
new button every time.
Found an upstream bug which describes the same problem and added it here
so it can be tracked.
If someone is capable of updating
101 - 155 of 155 matches
Mail list logo
