So, something that used to work and now does not -- the boilerplate
definition of a regression, I'd think -- and the "solution" is to update
a distro specific README file, that nobody will read? It is your call
in the end, but I have to say that doesn't improve the end-user
experience any
--
Public bug reported:
As of 16.04, the screen program started using a 256 colour setting. The
problem is that this setting is relatively new and has not had a chance
to propagate to older hosts, including something as new as the previous
15.x release. For example:
---
Tracked down this device and plugged it into an utopic box - seems to
work ; at least it can pass "iwlist wlan0 scan".
[947835.164024] usb 2-6: new high-speed USB device number 2 using ehci-pci
[947835.315382] usb 2-6: New USB device found, idVendor=13b1, idProduct=002f
[947835.315386] usb 2-6: Ne
Confirmed locally that the patch fixes the white-screen-of-death problem
on 12.10/quantal.
Is the upstream approval absolutely required here? The objection
("seems a bit simple...") is rather vague, and Alberts above has
essentially shown that it is in fact one per screen anyway, making the
obje
See bug 1019561, as it adds a device ID for the AE1000.
Note however, even though that claims the bug is solved, I question
whether that applies to _all_ the device IDs added (testing was only one
one specific case, and not the AE1000). In addition, for example, see
here:
http://wikidevi.com/wi
Seems OK now, see below:
-
root@yow-lpgnfs-02:/home/paul# ls -l /sbin/mdadm
-rwxr-xr-x 1 root root 462496 Aug 4 02:54 /sbin/mdadm
root@yow-lpgnfs-02:/home/paul# mdadm --version
mdadm - v3.2.5 - 18th May 2012
root@yow-lpgnfs-02:/home/paul# dpkg-query -l|grep mdadm
ii mdadm
On Wed, Apr 4, 2012 at 12:42 PM, Brian Murray wrote:
> I was unable to recreate this on two separate systems using mdadm in
> precise with raid arrays.
I suspect it is tied to my using raw deice names and not UUIDs. Rather
than focusing on recreating it, did you investigate the various traces a
** Attachment added: "configuration file for md0 layout"
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/969384/+attachment/2968911/+files/mdadm.conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
Public bug reported:
ubuntu precise, Installed version of mdadm is 3.2.3-2ubuntu1
mdadm segfaults on ubuntu precise during update-initramfs step. You can
reproduce it by running the command separately. Stealing an older mdadm
binary from an older ubuntu can be used as a workaround.
-
A quick google search and you will find this is a common problem with
these Toshiba models all over, even in the BSD variants. The threads
are in linux forums and even toshiba forums.
Having one myself -- and having it get hot and shutdown without a
warning is the only reason I happened onto this
I can confirm that the above suggested workaround [from David] of
pruning non-existent entries from the mailbox line(s) worked for me
locally. Server was Exch 2010.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
If you have a crapload of files in your home dir, then rythmbox, in its
infinite wisdom will try and index your complete home dir, and also try
to setup an inotify against every file it finds, which from memory (and
strace) will eventually cause it to get reams and reams of ENOSPC
returns, which it
Also seen on a 2GB machine with the server kernel.
Note that you can do an:
apt-get --purge remove ureadahead
as a workaround, with largely no ill effects, if you aren't relying on
any of its functionality directly.
This will remove the meta-package ubuntu-minimal, so once this bug is
fixed
Aha. Now the whole switch user thing makes sense too. I (and probably
others) didn't have the alsa-sink in .pulse, but there were objects in
/tmp that stopped it from creating a socket:
~$pulseaudio
E: module-protocol-stub.c: Failed to create socket directory
'/tmp/.esd-8023/socket': Permissio
** Attachment added: "strace output from memory eating polkitd"
http://launchpadlibrarian.net/46042521/polkitd.strace.txt
--
High CPU usage in policykit-1
https://bugs.launchpad.net/bugs/570015
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I had polkitd eat through all RAM and swap (approx 6G total) and trigger
oom-killer on firefox overnight.
Seeing the above, and being long overdue for a housecleaning of dot
files/directories, I started with a clean dir and only migrated key
stuff I use daily directly (i.e. .gitconfig, .thunderbir
On Tue, Mar 2, 2010 at 4:55 PM, Sebastien Bacher wrote:
> Thanks for the bug report. This particular bug has already been
> reported, but feel free to report any other bugs you find.
>
> ** Changed in: nautilus (Ubuntu)
> Status: New => Invalid
Is it invalid (i.e. because nvidia drviers are
Public bug reported:
Binary package hint: nautilus
Nautilus fails to launch completely on AMD64, running Nvidia drivers and
dual head. It briefly flashes a white horizontal bar of varying height
(approx 1/3 of screen height) and then dies. Upon a normal startup
sequence, it tries to relaunch ove
*** This bug is a duplicate of bug 290935 ***
https://bugs.launchpad.net/bugs/290935
On Tue, May 12, 2009 at 9:39 AM, Alex F wrote:
> *** This bug is a duplicate of bug 290935 ***
> https://bugs.launchpad.net/bugs/290935
>
> This was first marked as a duplicate of 346964, which sounds like
It appears that the discussion is inadvertently steering towards the
nvidia drivers, however based on what I'm seeing myself (on my own
machine) it really looks like a gnome panel thing -- where it simply
isn't passing the required :0.1 onto the application(s), and so it just
goes with the assumed
On Sat, Apr 11, 2009 at 11:03 AM, Brad wrote:
> Paul,
> Is there anyway to unload this module from the bootloader or something? I
> would love to at least, temporarily disable the driver so the livecd won't
> crash, so I can manage to install a newer version of Ubuntu, like 8.10 or
> 9.04.
I
** Summary changed:
- Kernel panic in gutsy 8.10 on HP 530j
+ acx wireless kernel panic in gutsy 8.10
--
acx wireless kernel panic in gutsy 8.10
https://bugs.launchpad.net/bugs/350436
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Whoops. Minicom file name extensions are misleading. Here is the real
log.
** Attachment added: "boot log of failing wireless card that worked on 8.04"
http://launchpadlibrarian.net/25004068/minicom.cap
--
Kernel panic in gutsy 8.10 on HP 530j
https://bugs.launchpad.net/bugs/350436
You rece
tested on another machine using a similar card, and got same results
(again via serial console). Complete dmesg/bootlog attached.
** Attachment added: "minicom.log"
http://launchpadlibrarian.net/25004037/minicom.log
--
Kernel panic in gutsy 8.10 on HP 530j
https://bugs.launchpad.net/bugs/350
Here is the driver detection data from the serial console, in case it
helps someone...
[ 27.260447] acx: Loaded combined PCI/USB driver, firmware_ver=default
[ 27.266909] acx: compiled to use 32bit I/O access. I/O timing issues might oc
cur, such as non-working firmware upload. Report
Confirmed -- and I can hopefully shed some light on this as well.
Seems that this (acx wireless) is the common thread/culprit:
acx_l_process_authen+0x124/0x380
Background:
I had an RT2500 wireless card on WEP that used to work on 8.04 but
doesn't even link on 8.10 (separate problem) and so I rep
Changing to "Fix Released" -- as it was tested and confirmed fixed on
Intrepid as of the packages released by 09/09/2008.
** Changed in: binutils (Ubuntu)
Status: Fix Committed => Fix Released
--
[intrepid] gas (binutils) fails to compile any recent kernel
https://bugs.launchpad.net/bugs/
I've re-tested today, with the latest pkgs pulled, and with the latest
kernel via git, and the problem appears resolved, so I've changed the
status to "Fix Committed", although I've no idea where along the lines
it was actually fixed, since I've not been doing daily tests.
** Changed in: binutils
On Mon, Sep 8, 2008 at 11:22 AM, Matthias Klose <[EMAIL PROTECTED]> wrote:
> please re-run gcc with -v to show the command line options used for the
> assembler. also please make sure to use an up-to-date intrepid.
>
> current kernels appear to build fine.
OK, I'll pull all new packages, do a git-
On Tue, Jul 8, 2008 at 12:10 AM, Matthias Klose <[EMAIL PROTECTED]> wrote:
> please could you re-run the build with verbose settings, and attach the
> preprocessed source, plus command line options?
The kernel config used to reproduce this problem was from a "make defconfig"
(for i386 arch)
Verbo
Public bug reported:
Binary package hint: binutils
Trying to compile any recent kernel (I tried git-latest, and also
v2.6.16) results in the following failure:
-
AS arch/i386/kernel/vsyscall-int80.o
/home/paul/linux-2.6/arch/i386/kernel/vsyscall-sigreturn.S: Assembler mess
Public bug reported:
Binary package hint: memtest86+
Seems memtest86+ is broken in intrepid. (2.01-1ubuntu1), as it gives
screenfulls of errors instantly, but the old memtest86 image (copied
from a 1.70 on a hardy-heron) works fine. I did an apt-get --reinstall
install memtest86+ -- and the md5
32 matches
Mail list logo
