Public bug reported:
Syncthing (1.1.4~ds1-4) in Eaon results in *other* clients (eg, one
running 1.0.1) reporting the error "Not sending symlinks to old client
{EAON CLIENT} - please upgrade to v0.14.14 or newer". It appears that
it reports its version as "unknown-dev". From the log of the 1.0.1
Public bug reported:
On a clean install of Maverick Alpha 3, installing the hdfview package
will not result in a usable hdfview. The only java dependency hdfview
has appears to be from the libjgraph-java package, which in turn depends
on default-jre-headless or java-runtime-headless. Both of these
** Changed in: usplash (Ubuntu)
Status: Fix Committed => Fix Released
--
framebuffer setup should not be done in usplash.
https://bugs.launchpad.net/bugs/40257
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing
Is there some reason for the change from Fix Released to Fix Committed,
or was it a mistake? As far as I can tell, this bug was fixed four years
ago.
--
framebuffer setup should not be done in usplash.
https://bugs.launchpad.net/bugs/40257
You received this bug notification because you are a memb
dmuir, that isn't this bug, and it isn't actually a bug at all. All vim
documentation, if I recall correctly, points out that "vi" is meant to
run a traditional form of vi, which means compatible is set. The fact
that "vi" runs vim with nocompatible set when anything other than vim-
tiny is install
I'm afraid I didn't notice this bug closure, and I hope I won't be
offending anyone by reopening it. The documentation explanation doesn't
make sense to me, because not only is the repetition terribly confusing
and unnecessary (having both lines uncommented makes it seem as though
they are both doi
It looks to me as though this is a video driver bug, possibly in the
proprietary nvidia drivers. Nik, what drivers are you using?
--
[nvidia-new] a visit to http://www.themareks.com/xf/ in firefox hardy causes X
to restart
https://bugs.launchpad.net/bugs/212648
You received this bug notification
A patch to simply stop the automatic timezone selection would be quite
easy. I can do this if it is needed.
Alternatively, I can improve my original patch to allow for timezones to
be specified for entire countries/states. This would probably also be
rather easy, though it would require that someo
It's certainly an unfortunate default, and I had hoped it would be
brought up elsewhere, as, at least at one time, I seem to recall that
these sorts of issues weren't handled in bugs, especially for issues
involving confusing behaviour and vi.
One option would be to undo the changes made for the D
Sorry, that bug number appears to be a Debian bug. See
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=388659 .
--
"visudo" is completely unusable (/etc/sudoers can only be editted with an
external text editor)
https://bugs.launchpad.net/bugs/207369
You received this bug notification because yo
(I'm assuming this isn't a prank about vi)
I'm afraid this is the direct result of bug #388659, which means that
visudo will now use vi by default. Vi is an editor with a rather
different model of editing.
If you want to use nano, set your $EDITOR variable (eg, export
EDITOR=nano), and then eithe
Public bug reported:
Binary package hint: system-config-printer
If a network printer is inaccessible in a way such that dns doesn't fail
and the connection isn't refused, system-config-printer hangs for
several minutes while starting up or modifying that printer.
For example, if a laptop user ha
While there is a similar bug that I am probably going to file soon, this
one appears to be fixed.
--
Cannot configure printers when not connected to the network.
https://bugs.launchpad.net/bugs/179847
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
It seems that the backup-writing code has been rewritten (to begin with,
it's now in gedit-local-...). This error no longer occurs in hardy, with
2.22, and was probably fixed in even earlier versions.
** Changed in: gedit (Ubuntu)
Status: Triaged => Fix Released
--
gedit error "Could not
I agree that the solution is rather wanting, and believe that the
timezone-guessing code is something that does not belong in any release.
The idea of it not selecting a timezone at all is interesting: it would
be very easy to do - I can make the patch if necessary - and wouldn't
require any extra
Of course, it is almost impossible to write code that works perfectly
without any testing. The patches here should now work.
I'm not happy with this solution, however. It seems as though it
requires a huge amount of work in updating Locations.xml, in a rather
unfortunate way. It could certainly be
These two patches (for gnome-panel and libgweather trunks) may or may
not lay the groundwork for solving this problem. As I proposed in my
recent comment, the code allows for tags in Locations.xml;
I've added an example for San Diego.
Unfortunately, I can't figure out how to test this, due to the
** Attachment added: "Patch for libgweather"
http://launchpadlibrarian.net/12714304/libgweather-tzfix.diff
--
Clock applet chooses wrong timezone for many cities (eg Pittsburgh, Beijing)
https://bugs.launchpad.net/bugs/185190
You received this bug notification because you are a member of Ubun
The obvious way to fix this would be to add a entry to each
city in Locations.xml. Unfortunately, that would be a very tedious task.
It may be better to add timezone information to locations where the
distance code gives the incorrect result, and use the distance code as a
default.
--
Clock app
This was reported over a year ago! I can't remember what I did at the
time, especially for little bugs. It might be a good idea to report it
upstream again if it hasn't been fixed yet.
--
XHTML file recognition
https://bugs.launchpad.net/bugs/65941
You received this bug notification because you a
Using the Alpha 4 livecd with an updated libgtk-vnc connecting to
tightvnc 3.3.tight1.2.9, I can confirm this bug. The problem appears to
be one of gtk keyboard focus: while clicking on elements generally
focuses them, clicking on the remote screen doesn't.
As a workaround, try clicking on the tab
I actually did bring this up quite a while ago on ubuntu-devel (before
the split), and the consensus seemed to be for the traditional mode.
--
Vim variants other than vim-tiny source /etc/vim/vimrc instead of
/etc/vim/vimrc.tiny when invoked as vi (ie, Arrow keys not broken when running
vi)
htt
As I believe I noted earlier, these lines *do not* enable support for
tablets by default. They only add support for a few tablet PCs.
Tablets aren't supported by Ubuntu by default, and getting them working
is actually rather annoying.
--
wacom input devices enabled by default, why?
https://launc
Sorry for the spam, but I should point all of you to bug 70569 as well,
which pertains to the issue, and explains why there is some confusion
over what vi does.
--
Arrow keys are incorrectly mapped in vim
https://launchpad.net/bugs/62980
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
The 'vim' command is already there by default (vim-tiny is installed).
If you want vim, use the 'vim' command. Vi isn't vim.
In response to Reuben, there is nothing to revert. The 'vi' command has
always been this way.
In response to Liegerm, isn't the 'vim' command already there after
installing
Freddy, just go to any site that uses mathml - search for mathml, for
example - and make sure that pango rendering in firefox is enabled. If I
recall correctly, pango is only used for firefox rendering now if there
are certain language support packages installed which need the enhanced
language sup
Denis, Jonh just said that two comments ago, and the status is Fix
Released. Also, I think it is safe to assume that people here know how
to use apt.
As for the patch, I agree with Christof here - even if the problem isn't
occurring any more, the patch should still be applied, since it would
preve
For some reason, my comment I thought I had made a few days ago didn't
show up here.
The issue wasn't in speedstep-centrino, it was in the ppc code of acpi,
acpi_processor_ppc_notifier. My hack of commenting out code in the
speedstep-centrino code was to keep the acpi code from being used to
limit
Messed up subtle aspects of this, due on distinction of upstream/package
status.
** Changed in: abiword (Ubuntu)
Status: Fix Committed => Confirmed
--
Abiword ignores DPI setting for zooming, assumes 72 dpi (1440 dpi / 20)
https://launchpad.net/bugs/76396
--
ubuntu-bugs mailing list
ubu
A fix for this was committed upstream.
** Changed in: abiword (Ubuntu)
Status: Confirmed => Fix Committed
--
Abiword ignores DPI setting for zooming, assumes 72 dpi (1440 dpi / 20)
https://launchpad.net/bugs/76396
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ub
This should be very easy to fix.
** Summary changed:
- Edgy: Users not in games group.
+ Powermanga not
** Description changed:
- Found this bug while playing powermanga.
-
- [EMAIL PROTECTED]:~$ powermanga --window --easy
- /var/games/powermanga/powermanga.hi-easy: Permission denied
- [EMAIL
Public bug reported:
Binary package hint: bash
The current .bashrc in feisty has export HISTCONTROL=ignoredups, then
has a one line comment, and then has export HISTCONTROL=ignoreboth. This
is terribly confusing and unnecessary. The correct way to set this, I
believe, would be to just have HISTCO
en an instance of GR_UnixGraphics is created (destroyed),
instead of being done in the function as it is now, which causes a
significant performance problem.
** Changed in: abiword (Ubuntu)
Assignee: Constantine Evans => (unassigned)
Status: In Progress => Confirmed
--
Abiword
** Changed in: abiword (Ubuntu)
Status: Unconfirmed => In Progress
--
Abiword ignores DPI setting for zooming, assumes 72 dpi (1440 dpi / 20)
https://launchpad.net/bugs/76396
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
.
** Changed in: abiword (Ubuntu)
Assignee: (unassigned) => Constantine Evans
--
Abiword ignores DPI setting for zooming, assumes 72 dpi (1440 dpi / 20)
https://launchpad.net/bugs/76396
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Public bug reported:
Binary package hint: abiword
Akin to bug #44672 in Evince, Abiword also ignores the system's and
user's DPI settings (Xft.dpi and xorg.conf) for purposes of zooming.
This was also discussed in bug #62347 in abiword, but was beyond the
scope of that bug.
It appears that Abiwo
Thank you, Mirco - that confirms some suspicions I had. I think I might
be able to reproduce the problem now.
--
kernel can't scale cpu frequency
https://launchpad.net/bugs/36014
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
** Bug watch added: GNOME Bug Tracker #382093
http://bugzilla.gnome.org/show_bug.cgi?id=382093
** Also affects: gnome-utils (upstream) via
http://bugzilla.gnome.org/show_bug.cgi?id=382093
Importance: Unknown
Status: Unknown
--
Baobab uses incorrect units
https://launchpad.net/bug
Public bug reported:
Baobab displays directory content sizes in binary prefix based units,
but uses SI prefixes. We need to either display sizes with the correct
units (KiB, MiB, etc), or have the calculation scheme changed so that
the numbers are in SI units. I will report this upstream and write
Mirco - unfortunately, the bug is in an obscure part of the cpufreq
code, and dmesg and lsmod don't show anything abnormal. The bug _does_
have a tendency to randomly appear and disappear. You might want to try
resetting the BIOS, perhaps that will help.
I suppose if you blacklisted all of the cpu
Arthur, it appears that this bug shows up somewhat randomly, and is not
necessarily reproducible even with the same hardware and software
configurations. I had the bug for months, and then it went away without
explanation. Others have it even with newer kernels.
Mirco, you should look at scaling_m
I must say, this bug is the worst I have worked with. I had thought that
the patches that were included in 2.6.17 fixed the issue, but the PPC
commenting method still works to solve the issue, it is apparent that
the bug still exists.
I have a few thoughts about how the bug might be solved, but no
Dan, please *don't* file another bug. I'm not sure what Paul is trying
to say, but the D600 is one of the machines that has this problem, and
is the machine I used to examine the bug. It has also rather been seen
that the patch doesn't fix it, but unfortunately it is very difficult to
work on becau
This is fixed in Edgy, as you mention, so it should be closed here. If
you would like to request that this be backported, please see the
appropriate section in https://wiki.ubuntu.com/UbuntuBackports.
** Changed in: vim (Ubuntu)
Status: Unconfirmed => Fix Released
--
Syntax highlighting v
The new version is now in Feisty (and also makes itself the default font
as a side effect...).
** Changed in: ttf-arphic-uming (Ubuntu)
Status: Unconfirmed => Fix Released
--
updae available: 0.1.20060903
https://launchpad.net/bugs/58993
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubu
This is the patch that changes all tags to tags, and
is probably the better and more conservative of the two patches.
** Attachment added: "Changes all tags to "
http://librarian.launchpad.net/5035368/uming-accept.patch
--
0.1.20060928-2 makes default gnome fonts ugly
https://launchpad.net
I'm attaching two patches here, one which changes all of the to
, and one which removes all of the sections in ttf-
arphic-uming altogether.
I'm assuming that there is some reason why uming is declaring aliases in
its configuration file, which not a single other font in fontconfig
appears to do,
This is a problem with the fontconfig configuration. It appears that it
is being caused by /etc/fonts/conf.d/70-ttf-arphic-uming.conf declaring
uming to be the strongest preference for every alias. Why was that done?
--
0.1.20060928-2 makes default gnome fonts ugly
https://launchpad.net/bugs/7112
Nicolò, the arrow keys aren't mapped because compatibility mode acts
exactly like the original vi, down to bugs if I recall correctly.
For this bug, I can understand the desire to have vi start vim. However,
if someone wants to start vim, they need to run vim. One wouldn't use
the command emacs an
** Summary changed:
- jump to last position when reopening file
+ jump to last position when reopening file does not work when g is remapped.
--
jump to last position when reopening file does not work when g is remapped.
https://launchpad.net/bugs/69611
--
ubuntu-bugs mailing list
ubuntu-bugs@
Confirming this. This is still happening in Edgy.
** Changed in: vim (Ubuntu)
Status: Unconfirmed => Confirmed
--
Nautilus Passes Relative Path to vim for Remote Files
https://launchpad.net/bugs/46209
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mail
This is most likely caused by an incorrect alternatives configuration.
If you are still having this problem, it would be most helpful if you
could tell me what the output of "update-alternatives --display gvim"
is? If it doesn't point to vim.gnome, then that is the problem, and this
isn't a bug. In
The intended behaviour is to have vi use set compatible, as noted in the
vim manpage, /etc/vim/vimrc.tiny, and a variety of other places. The
behaviour in Dapper was a bug. In fact, I've even filed a bug report
about this (bug 70569).
--
Arrow keys are incorrectly mapped in vim
https://launchpad.
I can confirm this. The problem is trivially easy to fix, and I will
forward it upstream tomorrow.
** Changed in: vim (Ubuntu)
Status: Unconfirmed => Confirmed
--
XHTML file recognition
https://launchpad.net/bugs/65941
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lis
Since the reporter was the only one to see this, and is no longer seeing
it, and I am also unable to see it in Edgy, I am closing it as Fix
Released.
** Changed in: vim (Ubuntu)
Status: Needs Info => Fix Released
--
Dapper: hitting q: in (g)vim causes a long cpu hang when syntax highlight
Since this is from when Dapper was not yet released, and I am unable to
reproduce it in Edgy, I am going to close this as Fix Released, since
the bug would be rather apparent if it were still there and I would
expect that others would have commented or filed duplicates.
If you are still having the
After testing this in Edgy with Simon Morgan's .vimrc, I've found that
this has been fixed, probably because gvimrc no longer contains the
commands noted in the description.
** Changed in: vim (Ubuntu)
Status: Unconfirmed => Fix Released
--
colorscheme get's sourced twice resulting in los
It is possible that the configuration could be changed to use wget
instead of ftp. I will look into the issue.
--
Spellchecking impossible for most languages
https://launchpad.net/bugs/66878
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubunt
- LC_TIME=POSIX
- LC_COLLATE="ru_RU.UTF-8"
- LC_MONETARY="ru_RU.UTF-8"
- LC_MESSAGES=POSIX
- LC_PAPER="ru_RU.UTF-8"
- LC_NAME="ru_RU.UTF-8"
- LC_ADDRESS="ru_RU.UTF-8"
- LC_TELEPHONE="ru_RU.UTF-8"
- LC_MEASUREMENT="ru_RU.UTF-8"
- LC_
*** This bug is a duplicate of bug 69267 ***
** This bug has been marked a duplicate of bug 69267
vim-gnome doesn't open non-ascii filenames by double click
--
gVim doesn't handle german umlauts correctly
https://launchpad.net/bugs/46907
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.
*** This bug is a duplicate of bug 69267 ***
** This bug has been marked a duplicate of bug 69267
vim-gnome doesn't open non-ascii filenames by double click
--
gvim will not use the same filename for writing
https://launchpad.net/bugs/65947
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubun
I've confirmed this in Edgy. I will look into this upstream tomorrow.
** Changed in: vim (Ubuntu)
Status: Unconfirmed => Confirmed
--
Vim locks up while editing a specific file (file attached)
https://launchpad.net/bugs/68960
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
http
Public bug reported:
When invoked as vi, vim.tiny sources /etc/vim/vimrc.tiny, which sets
compatible so that the vi command runs like the original vi. According
to several people on -devel, this is the desired behaviour for vim when
invoked as vi, and the behaviour makes sense.
However, when anot
Thank you for your report, but this is actually the intended behaviour
of the vi command. When invoking vim-tiny, the variant of vim installed
by default, using the vi command, it reads /etc/vim/vimrc.tiny, which
sets the compatible mode, so that vi acts like the original vi. The
broken arrow keys
Thank you for reporting this. The problem has already been fixed in
Feisty because it has a newer patch (7.0.122), which fixes the problem,
as you mentioned.
It is unlikely that this will be fixed in Edgy Backports unless there is
some other reason for a newer version of Vim to be backported.
**
Confirming this. This is trivial to fix, as the fix is already
explained. I will add a bug about this to the debian package tomorrow.
** Changed in: vim (Ubuntu)
Status: Unconfirmed => Confirmed
--
jump to last position when reopening file
https://launchpad.net/bugs/69611
--
ubuntu-bugs
As mentioned, this has been fixed in Firefox 2.0 in Edgy, which will
most likely be in Ubuntu Backports for Dapper.
** Changed in: firefox (Ubuntu)
Status: Confirmed => Fix Released
--
firefox - tab switching causes unintended tab drag&drop
https://launchpad.net/bugs/40733
--
ubuntu-bug
This was indirectly fixed in 7.0, which is now in Edgy. Ctrl-C now exits
insert mode instead of printing the message.
As this is not a very important bug, I would suggest against requesting
a backport because of it, but it will be fixed in Ubuntu Backports if
vim 7 is backported. Please see https:
*** This bug is a duplicate of bug 59981 ***
Rejecting hal part as well.
** Changed in: hal (Ubuntu)
Status: Unconfirmed => Rejected
--
HAL changes wireless interface (net.80211) to wired (net.80203) in
info.category after suspend
https://launchpad.net/bugs/55809
--
ubuntu-bugs mailin
Assigning to self per what sflaw told me on #ubuntu-bugs.
** Changed in: firefox (Ubuntu)
Assignee: (unassigned) => Constantine Evans
--
firefox has bee ncrashing often in edgy
https://launchpad.net/bugs/69181
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
ht
I am going to be a bit brave here and reject this, since it seems to be
an intentional decision by the Xorg team. If the inclusion is causing a
specific problem, then you should file a bug about the problem. Feel
free to reopen this if I am incorrect in my reasoning.
Unfortunately, the underlying
Thanks for your comment. The changes you are requesting require more
discussion and should rather be done on an appropriate mailing list or
forum.
http://www.ubuntu.com/community/forums/ might be a good start.
** Changed in: gedit (Ubuntu)
Status: Unconfirmed => Rejected
--
Using F5 as H
Thank you for your comments. I believe that you do make good points, but
bug reports are not the proper venue for discussing such changes. Your
ideas would be better received as a specification
(https://features.launchpad.net/distros/ubuntu/+specs, and
https://wiki.ubuntu.com/FeatureSpecifications)
My apologies - I meant uid, not umask.
Ari wrote:
> Hi Constantine, first thanks a lot for your quick response!
>
> On umask: It doesn't look like that option will accept a user number...
> it seems to be a permission mask for filesystems that don't support
> builtin unix permissions
>
>
> umask:
Recommends are for situations where the program does not require the
package to run, but needs it for major functions to work. Anjuta still
works as an editor without autogen installed.
In the future, installation of recommends will probably be easier.
** Changed in: anjuta (Ubuntu)
Status
Please read the comments here before adding your comments, and *don't
add your experience if you are having an unrelated bug*. Dragonmirov,
your bug has nothing to do with this problem.
John, I might take a look at the problem again, but because of its
intermittent nature I am not experiencing it
I've figured out the problem, and added a description of it to the
upstream bug. For now, you can get around the issue by mounting with the
option umask=(YOUR_USER_NUMBER) instead of umask=000 (probably
umask=1000).
--
gedit error "Could not create a backup file" when trying to save a file in a
** Bug watch added: GNOME Bug Tracker #343559
http://bugzilla.gnome.org/show_bug.cgi?id=343559
** Also affects: gedit (upstream) via
http://bugzilla.gnome.org/show_bug.cgi?id=343559
Importance: Unknown
Status: Unknown
--
gedit error "Could not create a backup file" when trying to
I'm confirming this after reproducing it with a clean loop mounted image
- vim works without an error, but gedit gives this error.
** Changed in: gedit (Ubuntu)
Status: Unconfirmed => Confirmed
--
gedit error "Could not create a backup file" when trying to save a file in a
VFAT partition
Unfortunately, your report doesn't give us enough information to
understand what is going wrong with Firefox on your system. If you have
the nonfree Flash plugin installed, do the sites you go to when Firefox
crashes normally have Flash components or advertisements?
If not, it would be very helpfu
Fjodor, throttling and scaling *are not the same*, as I noted before.
Throttling has nothing to do with this bug. Please don't discuss it
here.
John, I'm rather certain that the max_freq cannot be set manually. If
max == min, then you probably have the race condition problem that this
bug is discu
The configuration in xorg.conf specifically breaks tablet support for
tablet users by having ForceDevice ISDV4. These lines are to support
tablet *PCs* that use wacom's interface.
--
wacom entries appear even when not having a tablet
https://launchpad.net/bugs/63862
--
ubuntu-bugs mailing list
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Fjodor, the issue that you are having is not related to this bug. Please
file a new bug report about it if you can't find a relevant one.
That said, I think you need to ask on the forums or the mailing list,
since it doesn't appear you are experiencin
BBCUrdu seems to be rendering without any obvious (eg, boxes) problems
for me with Pango disabled (though I know nothing about the language),
but we probably should err on the side of safety here. Ian, could you
consider adding Urdu to the list of locales requiring Pango?
--
Pango-enabled firefo
Hmm... that seems reasonable, but we also don't seem to say that this
option shouldn't be used. In fact, the help file for Evolution says the
exact same thing for IMAP and IMAP4rev1. Is there some documentation
that I am missing that says this, and if so, why is it so obscure?
--
IMAP4rev1 should
I can't confirm this in a mostly clean 6.06.1 installation. Evolution
does appear to be using the gconf setting instead of x-www-browser or
$BROWSER, so I can't see where the problem would be unless the gconf key
is set incorrectly.
--
evolution ignoring preferred browser setting
https://launchpa
Just to clarify here, I'm listing this as a bug because I believe this
is something that could be done without significant discussion. We could
just patch evolution to remove the IMAP4rev1 option when creating new
accounts, without causing the compatibility issues entailed with
removing the code en
Public bug reported:
The IMAP4rev1 option for receiving mail is broken, unsupported,
unnecessary, outdated and confusing. Evolution developers seem to agree
at http://bugzilla.gnome.org/show_bug.cgi?id=324118 that it should never
have been included in a stable release. We really shouldn't have it
This occurs with my test, on edgy as well.
** Changed in: nautilus (Ubuntu)
Status: Needs Info => Confirmed
--
Nautilus duplicates thumbnails for files with special characters when searching
https://launchpad.net/bugs/55814
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https:
This is a rather obscure bug, but more info is not needed. I've
confirmed it with nautilus on edgy.
This is entirely in nautilus. To reproduce it, do the following:
1) Remove ~/.thumbnails
2) Create a directory with one thumbnailable file in it, that has a space in
the name.
3) Go to that directo
I'm attaching a log of hald's verbose output when this happens, but it
doesn't appear to have any obviously useful information on the problem.
Search for "event is 'button/sleep" to get to what I believe is the
relevant portion.
--
HAL changes wireless interface (net.80211) to wired (net.80203)
rejecting - this is a hal bug. oops.
** Also affects: hal (Ubuntu)
Importance: Untriaged
Status: Unconfirmed
** Summary changed:
- NetworkManager detects wireless interface as wired interface after coming out
of suspend.
+ HAL changes wireless interface (net.80211) to wired (net.80203
This actually appears to be a bug in hal - I'll move it as soon as I get
more information on it. Hal seems to be changing the information it
publishes after a suspend. Restarting hal fixes the problem.
I'm attaching the NM log. Search for "Going to sleep" to find point
where suspend occurs.
--
N
Confirming, as others have reported this as well.
** Changed in: network-manager (Ubuntu)
Status: Unconfirmed => Confirmed
--
NetworkManager detects wireless interface as wired interface after coming out
of suspend.
https://launchpad.net/bugs/55809
--
ubuntu-bugs mailing list
ubuntu-bu
Public bug reported:
On a Dell D600 running Edgy with an Intel 2200BG, Network Manager
detects the card as a wired interface instead of a wireless interface
after suspending (everything is fine before suspending). It then goes on
to claim that it is connected to a wired connection, but it does not
baszoetekouw, that is a different bug. Please don't post about it here -
make another bug, or wait for me to do so - I'm having the same problem.
--
Doesn't bring the network back online when resuming from suspend / hibernate
https://launchpad.net/bugs/40125
--
ubuntu-bugs mailing list
ubuntu-b
Ken, could you check to see if this happens with the 2.6.17 kernel in
Edgy? I no longer have the problem now that I am using Edgy, and there
is reason to believe that the issue was resolved by some changes
upstream.
--
kernel can't scale cpu frequency
https://launchpad.net/bugs/36014
--
ubuntu-
My problem was that this was happening with all kernels that I tried
(386, 686, etc), and fixing it required hackish modification of the _PPC
frequency limiting code, to stop it from incorrectly limiting. It
appears that this bug is now gone as of 2.6.17-2 in Edgy, but I can't
say for sure. The des
Unfortunately, it seems that the patch does not fix the problem. I
compiled 2.6.15-25.43 with the patch added, but with the same
configuration, and it did not resolve the problem. I also tried the
using the 2.6.17-2 from Edgy, and that also did not resolve the problem,
so I am guessing that the pat
The patch applies cleanly with the changes, but won't compile, since
mutex_lock and mutex_unlock aren't defined. After some cursory research,
it appears that the functions are called down and up in 2.6.15. Is this
correct? I am trying to compile the kernel with the names changed to up
and down now.
1 - 100 of 104 matches
Mail list logo
