Public bug reported:
Binary package hint: sox
The version of sox shipped with lucid enables multi-threaded processing
by default, but this results in a *dramatic* slowdown rather than an
improvement. This is what I get trying to resample a 90-second stereo
file:
% time sox --single-threaded -r
If you look at my original comment, you'll see that the reason I
commented here is because someone made my earlier bug report a duplicate
of this bug. So if you're not happy, find that person and tell him/her
to stop doing that.
--
Dialogs of background applications pop up in the foreground
I'm currently running Intrepid and the problem is *not* fixed. I was
wondering why my system was still using a lot of memory despite the fact
I didn't have that many apps running. So I closed all by one of the
evince documents and checked memory use:
% free
total used
Please add kdiff3, it's one of the must-have utils on any Linux distro.
--
kdiff3 is no longer packaged in intrepid
https://bugs.launchpad.net/bugs/292233
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
OK, question to Ubuntu devs. Is there someone actually interested in
investigating this? If so, please list anything that would be useful to
check when the bug occurs (about once a month for me with 8.10).
Some additional info. The last time this bug (or something very similar
-- hard to say)
Considering that this Fiesty regression is marked as WONT_FIX, please
just close this bug like all the others I reported.
--
[regression]Cannot modprobe snd-hda-intel following upgrade to Feisty
https://bugs.launchpad.net/bugs/120305
You received this bug notification because you are a member of
This has to be a joke. Nobody has ever done anything about that bug in
two years and now I should do more testing so it continues to be
ignored? Just close this as WONT_BOTHER like the rest of the bugs.
--
USB fails after suspend to RAM on Dapper
https://bugs.launchpad.net/bugs/48603
You
How about adding a A_DEVELOPER_IS_INTERESTED_IN_THIS_BUG flag to
Launchpad? That way, you could report a bug and only put effort in
finding the bug if a developer is actually interested in fixing it. This
would greatly reduce wasted effort and perhaps improve the odds of
fixing bugs that
I also believe it's related to copy-paste, because it always triggers a
bit after a paste.
--
Runaway leak in composer
https://bugs.launchpad.net/bugs/51662
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Sebastien, I *did* try valgrind. The problem was that evolution
generates so many warnings that valgrind's useless. It's also incredibly
slow (evo+valgrind) that you can't run that all the time. Some people
also gave stack traces, so don't say there was no info provided. Also,
in my case, I wasn't
I think the main reason you're getting no more information is that:
1) No information has been provided by the developers
2) Most people really affected by this bug have probably switched to another
client just like I've done.
You need to understand that the bug's been around for years now and
It is probably related. It happens to me with other apps than rdesktop.
I think the title should be changed.
--
No more mouse events after using rdesktop
https://bugs.launchpad.net/bugs/55739
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
OK, it happened again to me (on Gusty), while I was using Thunderbird and I was
able to get more info. First interesting thing was that trying to run xkill
gave me:
xkill: unable to grab cursor
That was interesting, because it occurred to me that the cursor was indeed
grabbed by something
Just a minor correction: the openoffice.org do you want to save your
changes? dialog is actually created as full-screen, which is really
annoying to say the least. I've also found the behaviour to be
intermittent.
--
Evince presentations start in a window if evince is fullscreen and compiz is
I'm having similar problems with evince when I enable compiz. Basically,
evince will open with the wrong geometry (slightly higher than the
screen) and more than half its window would be outside the screen (top-
left corner almost at the centre of the screen). But evince is not the
only
When I get hit by that bug, I generally can't type anything because the
keyboard focus isn't on any window. However, typing Alt-F2 (or whatever
brings up the run dialog) actually works. From there, I can start a
terminal that will actually get the focus. This is of course of limited
use because
Just upgraded my machine to Gusty 64-bit, which I can confirm doesn't
have the bug in that hda driver (yet!). It also means I will not be able
to test this anymore. Yet another bug heading for a DONTCARE resolution,
which is sad considering it's a regression introduced *after* the Feisty
release.
Rob,
I had a quick look and I believe it's a different bug. The bug here is:
1) About the snd-hda-intel module
2) The module does not load at all (even when using modprobe explicitly) due to
missing symbols
3) As far as I understand, it's specific to x86-64
--
[regression]Cannot modprobe
Just a note, the card with which the problem happens is a Radeon
Mobility X600, so you'd have to blacklist that as well. Let's put it the
other way. Has anyone had any success with any Radeon Mobility card?
** Summary changed:
- random system freeze when desktop-effects activated with X300 (X700
I just installed Gusty and I'm also experiencing exactly the same
problem as MichaelElkins described above, but on a Dell D810 (with
radeon card too). Ctrl-Alt-BackSpace doesn't work for me either, but
Alt-SysRq-b does work. It happens so often that there's no way to do
any work with that enabled
Until that gets fixed, is it at least possible to stop kernel upgrades
from overwriting the drivers I install? This is really annoying. Not
only do I need to work around the problem by compiling alsa drivers
myself, but on top of that, every kernel upgrade breaks everything
again.
--
phaserman: This is not the same problem as your link. The link is about
disabling the soundcard if it hangs on boot. In the case of this bug,
the machine doesn't hang, we're just trying to get the card to actually
work (and disabling it in the BIOS isn't exactly a good way to do that).
--
I'm hit by exactly the same bug on my Dell D820 with the 64-bit version
of Edgy. It's really annoying because it really mean I have no way to
use that CF card in my laptop at all. Bug occurs 100% of the time, so
it's quite serious. I can attach the dmesg, but it's fairly similar to
the one above.
I've experienced exactly the same problem on my Dell D820 laptop
(x86-64) and a Dell Precision 390 desktop (x86-64), which also use the
snd-hda-intel driver. The same driver loads find on another Dell laptop
(i386), although that one doesn't actually have that card. From this
sampling, I would
Same problem here when upgrading from 2.6.20-15 to 2.6.20-16. I've got a
Dell D820 with a Core 2 Duo and a ipw3945 card. On top of that, I also
lose sound (intel-hda soundcard). Don't know what happened to this
kernel, but it's definitely pretty bad.
--
Wireless gone at upgrade to kernel
Yes. See my above comment. It's not as bad, but it definitely has
happened to me with Feisty.
--
No more mouse events
https://bugs.launchpad.net/bugs/55739
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
You've got to be kidding! During the time it took to just have this bug
acknowledged (11 months), I've had time to upgrade Ubuntu twice (now
running Feisty) and replace my laptop with a newer model. So no, this
bug isn't causing me problems anymore, but I couldn't say whether it's
fixed or not.
Upgraded Ubuntu twice (to Feisty) and changed machine (to a 64-bit one)
in the mean time, so I'm no longer affected by this Dapper/i386 bug.
--
Weird X bug with 686 build
https://bugs.launchpad.net/bugs/53857
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Feisty boots fine on a Core2 machine. It's only Edgy and Dapper (and
probably earlier) that are completely broken.
--
Bug on amd64 makes X server unusable in Edgy (CRITICAL)
https://bugs.launchpad.net/bugs/66500
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Although it happens less often, it has happened to me with Feisty on my
new (x86-64) machine. I was in the middle of an IRC meeting so I
couldn't logout. It took maybe 30 minutes to the X server to release the
mouse from it's weird state. This behaviour is very annoying. I get the
choice between
I didn't observe the problem again because I'm no longer using evolution
(mainly because of this bug). All I can remember is that the bug was
often triggered by pasting some text into the compose window. Also, if I
saved the message before killing evolution (it was sometimes possible),
then trying
How about applying the fix to Dapper? Looks like bug #92143, which I
filed.
--
Big memory leak
https://launchpad.net/bugs/66188
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
*** This bug is a duplicate of bug 66188 ***
Seems to fit the pattern. I had set up a script to check the memory
every minute and it turns out that it leaked exactly 6752 KB every time
I brought up the logout dialog today (and did an xlock, but I don't
think the xlock is the problem here).
--
I'm seeing exactly the same behaviour. Any saved password with no login
name makes firefox segfault. The problem appeared in the security
update, as reported by others. Starting firefox with -safe-mode doesn't
change anything. However, if I use the official mozilla.org build,
firefox doesn't crash
% uname -a
Linux theorix 2.6.15-27-386 #1 PREEMPT Fri Dec 8 17:51:56 UTC 2006 i686
GNU/Linux
% lspci -vv
http://people.xiph.org/~jm/d800_lspci_vv.txt
% lspci -vvn
http://people.xiph.org/~jm/d800_lspci_vvn.txt
% dmidecode
http://people.xiph.org/~jm/d800_dmidecode.txt
--
USB fails after
Yet another user affected by this bug. See blog post
http://www.advogato.org/person/berend/diary.html?start=286
Considering there's no way to get out of this except doing a
ctrl-alt-backspace, this is *really* annoying.
--
No more mouse events
https://launchpad.net/bugs/55739
--
ubuntu-bugs
I've got focus-follows-pointer as well. I'll try Alt-tab next time I get
the bug. I also found this page
http://www.jwz.org/xscreensaver/changelog.html and started thinking it
it could actually be screensaver-related because it usually happens
after a bit of idle time. Have you seen the same
Actually, I originally filed this bug against Dapper... In any case,
installing thunderbird solved the problem permanently for me and I'm not
looking back (took about an hour to copy mail around and configure).
It's not perfect, but it's much more stable and has never crashed my
machine.
--
Considering that the patch has been in the main Speex tree for over a
year without complaints and the previous behaviour was totally broken
anyway, I say go for it now.
--
speexenc segfaults on amd64
https://launchpad.net/bugs/19482
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
ACPI problem can be worked around by also using no_timer_check. I have checked
newer kernels (2.6.18 and 2.6.19-rc6) and none of those seems to be affected.
I'd recommend either back-porting the relevant patch or adding notsc
no_timer_check to the default boot options (is that possible?). From
I don't have a Dapper64 machine, but if anyone has, the test is really
simple:
% speexenc /dev/zero /dev/null
If it doesn't crash after a millisecond or so, then the bug is fixed.
--
speexenc segfaults on amd64
https://launchpad.net/bugs/19482
--
ubuntu-bugs mailing list
Turns out the notsc kernel option solves the strange X problems. Machine
still crashes on any ACPI event though.
--
Bug on amd64 makes X server unusable in Edgy (CRITICAL)
https://launchpad.net/bugs/66500
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
It doesn't seem like it's an X server bug, please stop assigning it that
way.
** Changed in: xorg-server (Ubuntu)
Sourcepackagename: xorg-server = None
--
Bug on amd64 makes X server unusable in Edgy (CRITICAL)
https://launchpad.net/bugs/66500
--
ubuntu-bugs mailing list
Some additional info:
Dapper still crashes after a while. The difference with Edgy is that Dapper is
actually behaving normally before it crashes. I tried the Dapper kernel on
Edgy, and it works better -- about the same as normal Dapper -- so it's
probably a kernel bug. I also tried FC6 (2.6.18
I confirm that the final release of Edgy for AMD64 is still totally
unusable on my machine. On the other hand, the 32-bit version doesn't
have any of these problems (have been running it for one week).
--
Bug on amd64 makes X server unusable in Edgy (CRITICAL)
https://launchpad.net/bugs/66500
I confirm that the bug is *still* present in Edgy. And it's *really*
annoying!
--
gnome-panel doesn't show all menu items
https://launchpad.net/bugs/30146
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Considering the refusal to fix the speex encoder 6 months after a patch
was posted, I request (as the Speex maintainer) that package speex
(not libspeex1) be removed from the amd64 version of Dapper. The package
is broken beyond any use on that system, so all it does is give people a
bad
I don't know why the bugs I filed *earlier* are being marked as
duplicates of this bug -- especially considering that what I reported is
much more general than this. The problem is not restricted to dialogs.
New windows -- in general -- should not steal the focus. Not only can
this be a security
Public bug reported:
I'm resubmitting #66500 because I no longer think it's an X.Org bug. It *looks*
like a kernel problem now because it affects too many things. The result is
that Edgy (beta and RC) is totally unusable on my machine, crashing/hanging
after a few minutes. Other than the
Unsure which package
** Changed in: xorg (Ubuntu)
Sourcepackagename: xorg = None
--
Bug on amd64 makes X server unusable in Edgy (CRITICAL)
https://launchpad.net/bugs/66500
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Just summarising the info I have so far. I no longer think it's an X.Org bug.
It *looks* like it could be a kernel problem because it affects many things.
The result is that Edgy (beta and RC) is totally unusable on my machine,
crashing/hanging after a few minutes. Other than the crashes,
*** This bug is a duplicate of bug 66500 ***
More tests:
- Booting amd64 Edgy with Dapper's amd64 kernel results in about the same
behaviour as Dapper itself (not counting the stuff that requires a newer
kernel), so it's probably kernel related.
- With amd64 Dapper, I'm still getting some
I have done some experiments with BIOS settings. Basically, the problem
seems to disappear when I disable the second core. If any Ubuntu
developer is interested in investigating the bug, please let me know as
soon as possible because I'll otherwise be reformatting the partition as
soon as FC6 is
Sorry, the problem doesn't disappear when I disable the second core, it
just takes 20 minutes for the machine to crash instead of 1-2 minutes.
Oh, and BTW the strange info in /proc/cpuinfo was simply due to cpufreq
changing the CPU frequency.
--
Bug on amd64 makes X server unusable in Edgy
Public bug reported:
I've recently attempted to install and64 Edgy on my laptop and I find it
to be totally unusable in X (gnome or KDE). The X server will hang,
crash, etc within minutes (if not seconds) of using it, usually forcing
a reboot. The 32-bit version seems to work fine (haven't tested
Based on what I see at http://packages.ubuntulinux.org/edgy/source/speex
it seems like Edgy is not affected by the bug (which was fixed in
1.1.12). Now will someone finally apply the 4-line fix (above) to
Dapper... or does LTS just stand for Long Time to get Support?
--
speexenc segfaults on
Well, Firefox (and rdesktop in my case) may (or may not) be buggy, but
in any case the X server should contain the bug to these applications
instead of causing the whole system to be unusable.
--
No more mouse events
https://launchpad.net/bugs/55739
--
ubuntu-bugs mailing list
Yes, that would make sense because if it's a modal dialog, you can't
type in the main application window anyway. That's the only case I see
where stealing the focus is OK, and it's not really stealing because
that's what a modal dialog does *by definition*.
The only question remaining is what
Well, the fact remains that the password protection behaviour is
inconsistent. The choices are either to accept that Bug #54741 is real
(and not a feature) or to conclude that the blanking feature of gksu
should be removed. I'd personally prefer the former solutions, but it
seems like some people
Public bug reported:
Binary package hint: update-notifier
As reported in Bug #54741, the focus-stealing behaviour of metacity
makes it *very* easy to type an ssh (or other) password in the wrong
window if there's a new window opening. Since I have been told that this
behaviour should be
The consisteny issue is about having consistent *security* behaviour. I
can't see why some passwords are deemed more important than others.
I didn't they that was not a bug, I just wrote that is was not the same
issue than the focus issue initially described so it could use a
different bug,
Just saw this today. I'm the maintainer of Speex (for some reason the
Speex project no longer appears on launchpad). I'll fix the problem in
Speex for the next release. In the mean time, I suggest simply doing the
following change instead:
- op.packet = (unsigned char
Bit off-topic, but I just noticed that Speex is listed as an Ubuntu
package instead of an individual project. In any case, how can I get
automatically notified of bugs filed against Speex?
--
speexenc segfaults on amd64
https://launchpad.net/bugs/19482
--
ubuntu-bugs mailing list
I talked too soon. The patch I was proposing was actually applied on
01/01/06 19:21:21 (see http://trac.xiph.org/changeset/10684) and
actually made it into 1.1.12. You probably want to apply the same patch
in Dapper.
--
speexenc segfaults on amd64
https://launchpad.net/bugs/19482
--
I totally agree. What I don't get is that there's simply no logical
justification to the current behaviour (at least when focus follows mouse is
selected), yet they still don't want to change it. Sure, maybe Windows does it
like that, but Windows doesn't have focus follows mouse either. Two
I have not seen this error recently. It went away after I logged out.
IIRC I did an Ubuntu update before, so maybe the updated packages added
themselves to the menus again?
--
Multiple entries in gnome menu
https://launchpad.net/bugs/49262
--
ubuntu-bugs mailing list
Because your admin password can be immediately used to compromize
your computer, whereas your ssh or gpg passwords may or may not
be used that way.
I would argue the opposite. The sudo password is *by default* useless
because ubuntu doesn't install a local ssh server by default. Your
when you open a new folder with nautilus spatial or an application
from the panel menu you probably want them taking the focus
instead of having the previous nautilus window of the panel keeping it
This may (or may not) be handled as an exception to the don't steal
focus rule. Even then, it
Public bug reported:
Binary package hint: xorg
I'm running Ubuntu Dapper and sometimes X just stops sending any mouse
events (or so it seems). This usually seems to be triggered by using
rdesktop. At some point, my desktop becomes unusable. I can see the
mouse pointer move, but I can't click on
One thing I would like to point out. A new feature in Dapper is that
when starting up an config tool that requires the admin password (e.g.
update manager), then the screen goes dark to prevent other windows from
opening (and steeling focus) at the same time. Why is it considered that
the admin
Funny, doing the 'sleep 5; nautilus' *and* typing in another window is
the first case of things (sort of) behaving correctly. Any process other
than nautilus steals the focus. If I try the same with xterm, gnome-
terminal, konsole, gimp, ... the new window steals the focus. Clearly,
it should be
The first and third issues are indeed covered in the bugs you linked. The
second, however isn't:
2) When clicking on the main menu button, sometimes the panel hides itself and
the menu pops up too low -- the bottom of the menu is aligned with the bottom
of the screen instead of the top of the
Public bug reported:
Binary package hint: metacity
I'm resubmitting bug #51242 because I'm now convinced it has potential
to be successfully exploited remotely to steal user passwords. It
basically comes down to the fact that metacity gives by default (which
is impossible to change for me) the
So your argument is that if a vulnerability has been there for long
enough (or affects another OS), it's OK to leave it there? If a user
want to be affected by that, it's his/her choice, but the sane behaviour
should be the default. Or, in the minimal case, applications that can be
controlled
Have you ever typed your password in clear in another window that just
opened? I have -- several times. Usually, it just goes into a local
window and only the people around me could see it (which is bad
already), but I don't see why it couldn't happen accidently or
deliberately through IM or a web
that this doesn't seem to be a general nautilus issue
I assume you meant metacity issue here. I think there must be some
soft of confusion in here. On all three Dapper machines I have, I have
yet to see a *single* case of a window opening *without* getting focus.
Click on the panel to open a
Having a key in gconf is nice, but it doesn't change the fact that
automatically giving focus to a new window (by default!) constitutes not
only a security issue (typing a passwd in the wrong window), but a
potential for data loss (typing rm -rf * in the wrong terminal). Maybe
I should file it
Not sure what's going on with metacity/gconf, but I tried:
gconftool-2 --set /apps/metacity/general/focus_new_windows --type string strict
and though the setting was changed (checked with gconf-editor), there's no
change in metacity's behaviour.
--
New windows shouldn't steal focus
Please mark this as a dupe of bug #52600 (which I also filed).
--
rtlimits far too aggressive with SCHED_FIFO on Dapper
https://launchpad.net/bugs/52224
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Public bug reported:
Binary package hint: linux-image-2.6.15-26-686
I just discovered a very strange bug in the 686 kernel build. If I boot
that kernel, the X server ends up eating about 50% CPU, even when idle.
This slows down the machine dramatically. What's even stranger is that,
while top
I'm attaching the IEEEtran.cls file. Not sure what scrartcl is or how to
use it. About tetex-base, how do I check where it's from? I'm using
Dapper, but beyond that, I'm not sure what to check.
Last thing, I don't think bug 36145 is related, or at least it's not the
same bug.
--
Package babel
I've seen the same problem on a panel with default size and with a panel
of size 52. I've been trying a bit with the panel at the top. I've tried
with the panel up and I haven't been able to reproduce the jumping panel
bug. Maybe the bug is only with panel at the bottom or maybe it's
because of
Anything else needed to confirm this bug? I would think the
screenshots should be enough to see what's going on.
--
Autohide bugs
https://launchpad.net/bugs/48226
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
OK, this bug is still marked as Needs Info. What other info is needed?
--
New windows shouldn't steal focus
https://launchpad.net/bugs/51242
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Bug still says Needs Info. Have you been able to reproduce the
problem? Otherwise, what other info is needed?
--
Package babel Error
https://launchpad.net/bugs/48786
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Why is this still marked as Needs Info. What other info do you need?
--
USB fails after suspend to RAM on Dapper
https://launchpad.net/bugs/48603
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Public bug reported:
Not sure what's going on exactly, but it seems like on Dapper a user can
use SCHED_FIFO. The problem is that all priorities are allowed and there
seems to be no limit to the amount of CPU used. What this means is that
I can easily lockup my system by not being careful. As far
Until the problem is fixed, I think Ubuntu should include an option to
just disable gamin without having to remove the binary. Considering the
little benefit it provides (haven't really noticed a difference after
removing it), gamin causes far more harm than it helps. Actually
disabling it by
How do I do that? Sorry, not familiar with that bug tracking system.
--
Runaway leak in composer
https://launchpad.net/bugs/51662
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I'm running Dapper, but I remember seeing the problem on Breezy (and IIRC
earlier) as well. AFAIK, I don't use any special plugin and I don't use the
exchange connector. I tried running valgrind but not only is that incredibly
slow, but there are hundreds of errors and leaks reported. The
Well, any suggestion as to how to obtain debug info? It's not like using
valgrind+evolution as my main mail client for weeks is a realistic
option. Not to mention the fact that even if that was possible, valgrind
would have reported so many errors already that the real one would be
buried in
Public bug reported:
Binary package hint: evolution
Every once in a while, the evolution composer becomes out of control
while leaking memory. This usually makes my system completely
unresponsive within about 10-30 seconds. Evolution's memory footprints
grows at a very fast rate until it gets
Public bug reported:
Binary package hint: gnome-power-manager
I still haven't quite found the exact pattern, but I often have to
restart the gnome-power-manager applet because it either just died or
just failed to re-appear after a logout/reboot.
Setup is:
Dapper with default kernel
Dell D600
Bug #43760 was more about the fact that evolution shouldn't make
warnings pop all the time. I think this bug is more fundamental in the
sense that even if popping up a window is justified, it is *never* (I
still haven't found a counter-example) justified to make the new window
steal focus. It's a
Public bug reported:
Binary package hint: metacity
Whenever a new window pops up on Dapper, metacity assigns the focus to
it. This is bad behaviour. While Dapper solved the problem for some
password entries, it remains that whenever typing in a terminal or text
editor, one never knows if/when a
** Attachment added: Screenshot
http://librarian.launchpad.net/3153315/panel_bug.png
** Attachment added: screenshot (no bug)
http://librarian.launchpad.net/3153327/panel_nobug.png
--
Autohide bugs
https://launchpad.net/bugs/48226
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
OK, since it seemed like this bug was going to be ignored until I
upgraded the BIOS, I just upgraded to A05 (latest). Didn't change
anything. I also noticed that the bug only happens when I suspend when
my laptop is docked.
--
USB fails after suspend to RAM on Dapper
Then, wouldn't it make sense for postfix to make at least a reasonnable
attempt at ensuring it has an FQDN when being setup/installed -- or at
least warn if it doesn't?
--
Installer makes it easy to mess up the hostname
https://launchpad.net/bugs/49530
--
ubuntu-bugs mailing list
Public bug reported:
Binary package hint: debian-installer
When the Dapper installer asks for a host name, it does not specify it
needs to have the domain name. Worse, it even suggests a name with no
domain. So I entered that wrong and after installing postfix (as local
MTA because my ISP
99 matches
Mail list logo
