I have tried upgrading a clean, fully upgraded install of 8.04.3 to
10.04, and have had no issues whatsoever during the process.
Bodhi, as a hunch, can you please post your fstab listing.
Knowing you, you may have some weird security mount settings in place
that is preventing upgrade from taking
Public bug reported:
Binary package hint: gdc-4.3
Description:Ubuntu lucid (development branch)
Release:10.04
gdc-4.3:
Installed: 1:1.046-4.3.4-3ubuntu1
Candidate: 1:1.046-4.3.4-3ubuntu1
Version table:
*** 1:1.046-4.3.4-3ubuntu1 0
500
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/45774744/Dependencies.txt
** Description changed:
Binary package hint: gdc-4.3
Description: Ubuntu lucid (development branch)
Release: 10.04
gdc-4.3:
- Installed: 1:1.046-4.3.4-3ubuntu1
- Candidate:
Attaching output of:
gdc-4.1 -c -g nestedclass.d
objdump -d -M intel nestedclass.o nestedclass41.dump
** Attachment added: nestedclass41.dump
http://launchpadlibrarian.net/45784371/nestedclass41.dump
--
Classes nested in functions are not written to object files
Attaching output of:
gdc-4.3 -c -g nestedclass.d
objdump -d -M intel nestedclass.o nestedclass43.dump
** Attachment added: nestedclass43.dump
http://launchpadlibrarian.net/45784445/nestedclass43.dump
--
Classes nested in functions are not written to object files
Thanks for the canned response, not sure why you added 'needs-kernel-
logs', as is completely irrelevant to the nature of the report, so
removing it.
And no, the 2.6.32 kernel in the development version of Ubuntu (Lucid)
does not exhibit the btrfs bugs stated that are present in the 2.6.31
kernel
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
The problem is that pcmanfm bails out if it can't immediately connect to
HAL (reasons because the service is not already running). What it should
be doing instead is continuing anyway, where it should immediately
problem found to be in pcmanfm itself.
** Summary changed:
- HAL - service init scripts missing from package
+ pcmanfm - does not trigger hal startup
** Package changed: hal (Ubuntu) = pcmanfm (Ubuntu)
** Description changed:
- Binary package hint: hal
+ Since hal service daemon has been
Attaching patch.
** Patch added: pcmanfm-hal.diff
http://launchpadlibrarian.net/44252926/pcmanfm-hal.diff
** Tags added: patch
--
pcmanfm - does not trigger hal startup
https://bugs.launchpad.net/bugs/556080
You received this bug notification because you are a member of Ubuntu
Bugs, which
Alternatively, see no harm in just removing the check altogether, as if
hal is not present, it *should* error out later when calling
libhal_device_property_watch_all().
Regards
** Patch added: pcmanfm-remcheck.diff
http://launchpadlibrarian.net/44253359/pcmanfm-remcheck.diff
--
pcmanfm -
** Patch removed: pcmanfm-remcheck.diff
http://launchpadlibrarian.net/44253359/pcmanfm-remcheck.diff
--
pcmanfm - does not trigger hal startup
https://bugs.launchpad.net/bugs/556080
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Public bug reported:
Binary package hint: gdc-4.3
Build logs:
d/d-lang.glue.o: In function `d_init':
/build/buildd/gdc-4.3-1.046-4.3.4/build/gcc/../../src/gcc/d/d-lang.cc:449:
undefined reference to `rs6000_cpu_cpp_builtins'
collect2: ld returned 1 exit status
make[5]: *** [cc1d] Error 1
This reverts that part of the commit - I knew it was useful for
something, but just couldn't put my finger on what.
Thanks.
Iain
** Patch added: revert-r5.diff
http://launchpadlibrarian.net/43700929/revert-r5.diff
** Tags added: patch
--
gdc-4.3 powerpc ftbfs
** Tags removed: amd64 apport-bug
--
HAL - service init scripts missing from package
https://bugs.launchpad.net/bugs/556080
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:
Binary package hint: hal
[~] dpkg -L hal | grep etc
/etc
/etc/hal
/etc/hal/fdi
/etc/hal/fdi/information
/etc/hal/fdi/policy
/etc/hal/fdi/policy/preferences.fdi
/etc/hal/fdi/preprobe
/etc/dbus-1
/etc/dbus-1/system.d
/etc/dbus-1/system.d/hal.conf
As you can see from above,
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/43198060/Dependencies.txt
--
HAL - service init scripts missing from package
https://bugs.launchpad.net/bugs/556080
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Can someone confirm if this bug is still the case in Lucid? If not, I'll
have a prep machine in a few days.
Also, if anyone has any direction on where this is heading, please let
me know also. Specifically, does this need patching? Or should the wiki
be updated to reflect the new behaviour of
I have given this a second try after some updates, and the original
functionality quirk seems to have resolved itself. However, data keys
are still missing from /apps/panel/global if opened in gconf-editor, or
if I were to dump them via gconftool.
Regards
Iain
--
gnome-panel global keys missing
Yes, see the attached image.
Rest assured, I have done nothing but switch to guest session and opened
those two programs.
I'll give gnome-panel a re-installation, to see if that clears it up.
Regards
Iain
** Attachment added: Screenshot.png
Hmm, reinstalling the package via dpkg seems to have resolved the issue,
which strikes heavy bearing to another bug I'm currently trying to
investigate (have no official report on the issue yet).
This incident actually may shed some light onto what the core problem
is...
Feel free to close this
Public bug reported:
Binary package hint: gnome-panel
If I open gconf-editor, and browse to '/apps/panel/global', all keys
listed there are missing.
If I were to run in a terminal: `gconftool --set
/apps/panel/global/lock_down --type bool true`, gnome-panel does not
adhere to this setting.
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/41438334/Dependencies.txt
--
gnome-panel global keys missing in gconf
https://bugs.launchpad.net/bugs/542883
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Well since everyone seems pretty much fixed on the idea that static
GRUB_DEVICE and GRUB_DEVICE_UUID entries are ok, just have two posing
questions.
How do you suppose we get those entries there in the first place?
What would we do in the event that a UUID changes (if unlikely, I know :) ?
Or
** Changed in: pidgin (Ubuntu)
Status: New = Invalid
--
Saner settings for the max scrollback in open chats?
https://bugs.launchpad.net/bugs/337272
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
The hardware profiling you are referring to I presume is ureadahead.
No, this doesn't profile on every start. It is my understanding that it
periodically updates the cache file once every month, and only forces a
re-profiling when installing/upgrading certain system components.
Is the cycle that
I also notice that this is in your BootMesg attachment.
NVRM: The NVIDIA GeForce FX 5200 GPU installed in this system is
NVRM: supported through the NVIDIA 173.14.xx Legacy drivers. Please
NVRM: visit http://www.nvidia.com/object/unix.html for more
NVRM: information. The 190.53 NVIDIA driver
Have exchanged words with Nico, and he is (as of writing) updating the package
in Debian/
http://packages.debian.org/source/unstable/nitrogen
An eventual sync with upstream then before the release of Lucid would be
preferable.
Regards
Iain
--
nitrogen crashed with SIGSEGV at startup when
** Changed in: nitrogen (Ubuntu)
Status: New = Fix Released
** Changed in: nitrogen (Ubuntu)
Status: Fix Released = Confirmed
--
nitrogen crashed with SIGSEGV at startup when restoring wallpaper
https://bugs.launchpad.net/bugs/520861
You received this bug notification because you
This bug has been fixed upstream as a bugfix-only update.
CHANGELOG
Thu Feb 4 18:43:52 EST 2010Dave Foster d...@minuslab.net
* Releasing 1.5.1.
* Fixes bug with detecting root window type, README updates.
Am attaching the diff.gz of the update, and the link to the upstream source
*** This bug is a duplicate of bug 520861 ***
https://bugs.launchpad.net/bugs/520861
** This bug has been marked a duplicate of bug 520861
nitrogen crashed with SIGSEGV at startup when restoring wallpaper
--
nitrogen segfaults when setting background
Public bug reported:
Binary package hint: nitrogen
This is not restricted to architecture, happens on both amd64 and i386.
Is very reproducible, either by double-clicking on a background, or by
pressing the Apply button.
ProblemType: Bug
Architecture: amd64
Date: Tue Feb 23 20:15:09 2010
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/39653884/Dependencies.txt
--
nitrogen segfaults when setting background
https://bugs.launchpad.net/bugs/526655
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Attached back-trace.
** Attachment added: nitrogen-bt.txt
http://launchpadlibrarian.net/39667117/nitrogen-bt.txt
--
nitrogen segfaults when setting background
https://bugs.launchpad.net/bugs/526655
You received this bug notification because you are a member of Ubuntu
Bugs, which is
And the attached patch fixes it.
** Patch added: nitrogen.patch
http://launchpadlibrarian.net/39667189/nitrogen.patch
--
nitrogen segfaults when setting background
https://bugs.launchpad.net/bugs/526655
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Can anyone test this to see if this works when using Nitrogen whilst
Nautilus is being used to draw the root desktop?
** Description changed:
Binary package hint: nitrogen
+
+ Nitrogen segfaults when trying to set the background image for a window
+ manager that is not being controlled by
Having had a look, this bug has actually been fixed upstream, so can we please
sync?
Thanks.
--
nitrogen segfaults when setting background
https://bugs.launchpad.net/bugs/526655
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Quick question on this bug, if you don't mind.
Regarding this part of the patch:
.callback = init_set_sci_en_on_resume,
.ident = Hewlett-Packard Pavilion dv4,
.matches = {
DMI_MATCH(DMI_SYS_VENDOR, Hewlett-Packard),
Sorry - seemed to have answered my own question.
Had a look at the function dmi_matches() and it uses strstr() to match
strings - which is all OK.
Thanks anyway.
Regards
Iain
--
Battery status unavailable after suspend / resume on some HP laptops
https://bugs.launchpad.net/bugs/453963
You
multiple times
** Affects: pulseaudio (Ubuntu)
Importance: Undecided
Assignee: Iain Bucław (tinivole)
Status: New
** Tags: apport-bug i386
--
pa_threaded_mainloop_signal() deadlocks in while condition
https://bugs.launchpad.net/bugs/502992
You received this bug notification
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/37409843/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/37409844/AplayDevices.txt
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/37409845/BootDmesg.txt
**
This mostly affects games using the libopenal1 library, and is likely to occur
either:
1) When the sound initialises. or -
2) When the sound deinitialises.
But will likely affect any other application that uses Pulse Audio's
threaded mainloop library.
Attached is a strace of running Alien Arena
This mostly affects games using the libopenal1 library, and is likely to occur
either:
1) When the sound initialises. or -
2) When the sound deinitialises.
But will likely affect any other application that uses Pulse Audio's
threaded mainloop library.
Attached is a strace of running Alien Arena
: (unassigned) = Iain Bucław (tinivole)
--
pa_threaded_mainloop_signal() deadlocks in while condition
https://bugs.launchpad.net/bugs/502992
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs
** Changed in: pulseaudio (Ubuntu)
Status: New = Confirmed
--
pa_threaded_mainloop_signal() deadlocks in while condition
https://bugs.launchpad.net/bugs/502992
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Description changed:
Binary package hint: pulseaudio
This bug regards this patch in pulseaudio:
http://git.0pointer.de/?p=pulseaudio.git;a=commitdiff;h=4f5e2b745ea357e2b5c815ff33a556505a7d1f18
- The variable n_waiting_for_accept never gets properly initialised, and
- due to
The current kernel you were running on is Linux 2.6.32-7-generic x86_64
when the drivers were being built, but it seems that the headers weren't
available when dkms went to build them, so skipped and continued onto
the 2.6.32-9-generic x86_64 kernel.
This is as per the following output:
Building
And with regards to bug #459199, updated to match system uid
configuration.
Also, renamed it to disallow_invalid_login to better describe what it
does.
Regards
Iain
** Attachment added: 29_disallow_invalid_login.patch
http://launchpadlibrarian.net/37358835/29_disallow_invalid_login.patch
--
And imported all the relevant translations from gdm-2.20 into gdm-2.28
(using a perl script to grab+insert into files, so there may be error,
although I'm confident there isn't).
If anyone has any comments - greatly appreciated. As I'm learning here
as much as I am contributing.
Regards
Iain
@Kees, I agree.
This patch attached should do just that.
It's a slight modification of another part of the gdm code that
disallows the showing of system users in the selection screen. Copied it
into the do_accredit stage of the user authorisation, tested and it
works as expected.
Just putting
** Attachment added: 26_disallow_rootlogin.patch
http://launchpadlibrarian.net/37226490/26_disallow_rootlogin.patch
--
GDM allows root logins
https://bugs.launchpad.net/bugs/484317
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Is anything happening with this upstream?
I've managed to get grub2 working via backporting the legacy 0.97 shell probe
functions into the grub-mkconfig_lib file. But this doesn't really seem right.
Attached my changes against this post anyway for people to see.
Regards
Iain
** Attachment
Hmm, perhaps I have a different issue, this is what I've found so far in
the behaviour of the netbook-launcher iconview on a Samsung N110.
Res: 640x480
2 Columns
3 Rows per group of icons
All icons showing. (Albeit, with a large gap after every third row)
Res: 800x600
Public bug reported:
Binary package hint: gdm
Steps to reproduce:
1) Create a password for root
2) Logout
3) Login as root
Now, previous versions of Ubuntu prevented a graphical root login in
GDM, and I see no reason why this should differ in the new versions.
There has always been a strict
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/35788719/Dependencies.txt
--
GDM allows root logins
https://bugs.launchpad.net/bugs/484317
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Thankfully, the fix is trivial too:
Add the following to /etc/pam.d/gdm
authrequiredpam_succeed_if.so user != root quiet
Patch for the debian build attached.
Regards
Iain
** Attachment added: disallow_root_login.patch
Just running sudo passwd is enough to set the password.
Actually, after having a sleep on it, would it be useful just to deny
uid's 1000 and the 'nobody' user?
ie:
auth required pam_succeed_if.so uid = 1000 quiet
auth required pam_succeed_if.so user != nobody quiet
This, I think will restore
I can confirm this bug happened to me, but am reporting here because
today, I've noticed the complete reversal of this bug.
Only recent updates I've had relating to netbook-launcher are:
libclutter-gtk (0.10-0 0.10.2-0ubuntu1 = 0.10-0_0.10.2-0ubuntu2)
libgnome-desktop (2.28.1-0ubuntu2 =
Not sure if this helps you philinux, but removing stop on starting-dm
seemed to shorten the inbetween black screen between 1-2 seconds
depending on reboot/startup from cold. At least, on first impressions
(admittedly, it could just be a placebo working here).
File edited: /etc/init/usplash.conf
OK, after several reboots, 1-2 seconds is a bit of an exaggeration (4-5
seconds on my watch, not on my counting skills).
Only notable difference between before and after is that before there
was a blinking _ on the tty which added about 3 seconds, now there is
just a plain black screen. I suppose
@Trulan, how was NViDIA installed before hand?
The first time you tried and failed was probably because you had
residual pieces of a previous NViDIA installation still present (ie:
from manual installation from the nv site), and so it was more likely an
X11 failure rather than a driver failure.
Alberto, that is what I have been using when compiling the drivers
manually for the past 2 months.
As for the debian build, I noticed there was already an nvidia-rt-compat.patch
file in the debian.binary/patches tree.
So I fixed that and added it to the dkms.conf.in file.
Had a try at package
** Changed in: nvidia-graphics-drivers-180 (Ubuntu)
Status: In Progress = Fix Released
--
Nvidia binary driver won't build with 2.6.31-rt kernel
https://bugs.launchpad.net/bugs/413296
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Motin, I will look into it.
I currently use 190.32 drivers... Most current is 190.40, and I *know*
that it doesn't work in the most recent stable (185.36).
Will message back with updates.
--
Nvidia binary driver won't build with 2.6.31-rt kernel
https://bugs.launchpad.net/bugs/413296
You
** Changed in: zenbuntu/zenix-9.10
Status: Confirmed = Fix Committed
--
ubuntu and zenix unable to start X on liveCD
https://bugs.launchpad.net/bugs/448495
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Bryce, sorry, but I was very quick to remove it after it became evident
that it affected something else in the driver when going into
screensaver.
The idea was:
#ifdef CONFIG_PREEMPT_RT
#define spin_lock_init(lock)atomic_spin_lock_init(lock)
/* etc */
#endif
Removing the need for a separate
*** This bug is a duplicate of bug 68464 ***
https://bugs.launchpad.net/bugs/68464
This is harder one to work around than what I original thought it be.
Rather than tweaking debconf, this package is installed via a hard-coded
line in the Ubiquity installer.
That makes the possible
Since it's BugJam, I had a more detailed look at the difference between
2.6.29-2.6.31 with and without RT patches, and came up with this
shorter, sweeter patch that should resolve things, at least, until the
NV-devs fix things up properly.
I don't think backwards compatibility with previous
** Attachment removed: rt_preempt_31-new.patch
http://launchpadlibrarian.net/3307/rt_preempt_31-new.patch
--
Nvidia binary driver won't build with 2.6.31-rt kernel
https://bugs.launchpad.net/bugs/413296
You received this bug notification because you are a member of Ubuntu
Bugs, which is
-graphics-drivers-180 (Ubuntu)
Status: Fix Released = In Progress
** Changed in: nvidia-graphics-drivers-180 (Ubuntu)
Assignee: (unassigned) = Iain Bucław (tinivole)
--
Nvidia binary driver won't build with 2.6.31-rt kernel
https://bugs.launchpad.net/bugs/413296
You received this bug
And attached is the patch that should now work.
Regards
Iain
** Attachment added: rt_preempt_31.patch
http://launchpadlibrarian.net/32679012/rt_preempt_31.patch
--
Nvidia binary driver won't build with 2.6.31-rt kernel
https://bugs.launchpad.net/bugs/413296
You received this bug
This is the patch in the recent upload:
---
nvidia-graphics-drivers-180-185.18.36.orig/debian.binary/patches/rt_preempt_31.patch
+++
nvidia-graphics-drivers-180-185.18.36/debian.binary/patches/rt_preempt_31.patch
@@ -0,0 +1,12 @@
+diff -urN NVIDIA-Linux-x86-185.18.36-pkg1/usr/src/nv/nv-linux.h
Yes, it is in the Hardy Multiverse Backports AND the Hardy Partner
repositories:
Add, or uncomment the following lines from your /etc/apt/sources.list
file:
deb http://archive.canonical.com/ubuntu hardy partner
deb-src http://archive.canonical.com/ubuntu hardy partner
Regards
Iain
--
Hardy:
Oops, forgot to attach.
** Attachment added: nv-2.6.31-rt.patch
http://launchpadlibrarian.net/31986809/nv-2.6.31-rt.patch
--
Nvidia binary driver won't build with 2.6.31-rt kernel
https://bugs.launchpad.net/bugs/413296
You received this bug notification because you are a member of Ubuntu
I ran into this issue, and wrote a patch, and posted here:
http://www.nvnews.net/vbulletin/showthread.php?p=2087519#post2087519
It is based on the patch in the previous post, but rather than a
separate patch for all NV driver versions, this should work across the
board. At least, I hope.
Regards
I was doing this at David Rubin's request Nathan (I presume he already
uses Weechat 0.3 and is exhilarated by it).
I can get back to you once I've updated him of the above.
Thanks
Iain
--
Sync weechat 0.3.0~rc3-1 (universe) from Debian experimental (main)
https://bugs.launchpad.net/bugs/429634
Public bug reported:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
affects ubuntu/weechat
status new
importance wishlist
subscribe ubuntu-universe-sponsors
done
Please sync weechat 0.3.0~rc3-1 (universe) from Debian experimental
(main)
Changelog entries since current karmic version
Thank you for your report.
Could you please attach the following that can help the developers
identify the issue.
sudo lspci -nnvv lspci_nnvv.log
sudo iw event -t iw_event_t.log
And can you try to identify whether or not this is an issue with
NetworkManager, wpa_supplicant, or mac80211 ?
Public bug reported:
When you send a notification in Synchronous with another, the both Title
and Sub-Title doesn't get updated.
As an example:
while true; do
notify-send first title first subtitle -i dialog-info -h
string:x-canonical-private-synchronous:test
sleep 1
notify-send
** Summary changed:
- notification title doesn't change for synchronous messages
+ notification summary doesn't change for synchronous messages
** Description changed:
- When you send a notification in Synchronous with another, the both Title
- and Sub-Title doesn't get updated.
+ When you send
I looked into this a bit when Bender2k14 mentioned it on the forums.
Pausing the timer if the file is reported to be a broken link seems like the
most obvious thing to do.
Patch against the nautilus source directory is attached.
Regards
Iain
** Attachment added: timed_wait.patch
Three days ago, it appears that a patch was supplied on the main Broadcom site.
http://www.broadcom.com/support/802.11/linux_sta.php
I recommend that this gets pushed into the upstream in time for the
Jaunty release.
Regards
Iain
--
Complete system freeze when trying to connect to WPA2 network
I do believe I'm getting something similar to this.
I don't have anything in logs that would suggest a fail, but after a
period of around 4-6 hours network inactivity, my system will freeze
once I start using the network device again (ie: checking for updates).
General Information:
cat
** Attachment added: pidgin.patch
http://launchpadlibrarian.net/23372497/pidgin.patch
--
Saner settings for the max scrollback in open chats?
https://bugs.launchpad.net/bugs/337272
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Public bug reported:
Binary package hint: pidgin
Hi, I am going to enlist this as a wishlist, but in this report, I am
asking that wouldn't it make more sense if the viewable scrollback lines
for open chats in pidgin were removed in sync with the line_count
exceeding max_scrollback_lines?
Thank-you Allisson, my gratitudes to you.
Regards
Iain
--
please sync with upstream version
https://bugs.launchpad.net/bugs/114150
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Well... I decided to have a look at the source, I won't pretend that I'm
a C++ guru, but I know what I'm looking at when I see it.
I have supplied a cheap patch, I tested it in a debootstrap and the
results of it don't seem to have any side effects (not that it would
anyway)...
What it does
Public bug reported:
Binary package hint: flashplugin-nonfree
Hi,
I'm not sure how long flashplayer has been removed from the current location in
the flashplugin-nonfree install script:
http://fpdownload.macromedia.com/get/flashplayer/current/install_flash_player_9_linux.tar.gz
But, that link
Attached:
lsmod
Regards
Iain Bucław
** Attachment added: lsmod
http://launchpadlibrarian.net/19350217/lsmod
--
kernel 2.6.27-7-generic bug BUG: scheduling while atomic: swapper/0/0x0100
https://bugs.launchpad.net/bugs/286285
You received this bug notification because you are a member
Nov 3 07:35:05 intrepid kernel: [35527.615957] Call Trace:
Nov 3 07:35:05 intrepid kernel: [35527.615959] [8023e06d]
dequeue_task_idle+0x2d/0x40
Nov 3 07:35:05 intrepid kernel: [35527.615961] [8023c436]
dequeue_task+0x96/0xe0
Nov 3 07:35:05 intrepid kernel: [35527.615964]
** Description changed:
Binary package hint: bristol
- please version 0.10.2 was released. Debian package have missed many
+ please version 0.20.6 was released. Debian package have missed many
releases.
--
please sync with upstream version
https://bugs.launchpad.net/bugs/114150
You
** Description changed:
Binary package hint: bristol
please version 0.20.6 was released. Debian package have missed many
releases.
+
+ The version in the repositories is 0.9.1-13, which is nearly two years old.
+ An update is needed so the users of Ubuntu can use a fresh version with
As far as I'm concerned, this has been fixed in Intrepid :)
I followed that howto link in car-los's post above, then pinned
hardy/added intrepid to my sources list.
Then upgraded to firefox 3.0 and Flash 10 beta using the /t intrepid
option in apt-get, et Voila!
I've had no crashes since (this
Hi, may I add my findings to this? I think I have the same problem
(firefox crashing when switching between flash videos).
Here is my gdb output.
__
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread
Hi Mika,
Thanks for the reply. That is helpful information.
The point I was getting at, was that it worked a few weeks ago, back when I
posted the post. (Else, why would I have made it in the first place).
But, now, it seems that it is now acting as it should.
Maybe it was a temporary
Public bug reported:
Binary package hint: bash
Hi, this is a knock-on effect bug from here:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/207369
And the reason why I'm posting the bug here is because echo $SHELL
prints out bash, although this happens on sh and dash too.
Basically, ever
You could add these lines:
CODE:
# Set Environment for sudo -E.
#export EDITOR=vim
#export EDITOR=nano
# Make sudo -E the default setting for sudo.
# alias sudo='sudo -E'
:CODE
to the ~/.bashrc file, so that slightly advanced users can set this up right.
Or when given directions to this, all
Putting this in /etc/gdm/Init/Default seems to have the right effect for me:
CODE:
### Fix that bloody apt error! ###
mkdir -p /var/log/apt/
exit 0
Does anyone know what's wrong?
Regards
Iain
--
E: Directory '/var/log/apt/' missing
https://bugs.launchpad.net/bugs/220239
You received
Public bug reported:
Binary package hint: nautilus
Hi, I've noticed that when I double click Up in Nautilus that I go up
two directories in the GUI. But according to the text-based location
I've only gone up one.
Also, I cannot re-enter the directory that I am supposedly in (because I
am
** Attachment added: Ogg Video of the Bug in action.
http://launchpadlibrarian.net/13832791/out.ogg
--
Double-Click Up Bug
https://bugs.launchpad.net/bugs/220864
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Public bug reported:
Binary package hint: apt
The error message that popups up after doing anything with aptitude/apt-
get (download, install, remove, etc, etc)
Creating the folder gets rid of this error message. And a lovely, tiny log file
is stored in the folder. With all of my days history
1 - 100 of 107 matches
Mail list logo
