[Bug 1847018] [NEW] Syncthing reports bad version, confusing other clients
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
client:
2019-10-07 06:05:13 Device {DEVICE ID} client is "syncthing unknown-dev"
named "{DEVICE NAME}" at {IP ADDRESS}/tcp-server
** Affects: syncthing (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
- Syncthing 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 client:
+ 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
+ client:
2019-10-07 06:05:13 Device {DEVICE ID} client is "syncthing unknown-dev"
named "{DEVICE NAME}" at {IP ADDRESS}/tcp-server
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847018
Title:
Syncthing reports bad version, confusing other clients
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/syncthing/+bug/1847018/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 620779] [NEW] hdfview dependencies are wrong: requires non-headless jre
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 are headless, and thus don't have the required libraries to actually run hdfview. ** Affects: jhdf (Ubuntu) Importance: Undecided Status: New -- hdfview dependencies are wrong: requires non-headless jre https://bugs.launchpad.net/bugs/620779 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 40257] Re: framebuffer setup should not be done in usplash.
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 member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 40257] Re: framebuffer setup should not be done in usplash.
** 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 list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 70569] Re: 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)
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 installed is actually wrong; if you want to run vim with nocompatible set, you are supposed to use vim, not vi. Unfortunately, this has become so confused that any solution to this bug will inevitably upset some people. Personally, I know of very few people who would ever use vim in compatible mode, and that the best solution would probably be to change the documentation and make vi run vim with nocompatible set. However, it is worth pointing out that vim is not the only implementation of vi, and having it as vi could presumably lead to some confusion among a small set of people. -- 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) https://bugs.launchpad.net/bugs/70569 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76807] Re: /etc/skel/.bashrc sets HISTCONTROL twice in succession.
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 doing something, etc), but it also appears that the comments explaining the lines are actually completely wrong. Setting ignoredups *already* ignores same successive entries. Setting ignoreboth adds ignorespace, which causes *lines beginning with spaces* to be ignored. If the intent is documentation, then the implementation is very poor, to the point of being a bug in itself. ** Changed in: bash (Ubuntu) Status: Won't Fix = Confirmed -- /etc/skel/.bashrc sets HISTCONTROL twice in succession. https://bugs.launchpad.net/bugs/76807 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 212648] Re: [nvidia-new] a visit to http://www.themareks.com/xf/ in firefox hardy causes X to restart
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 because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 185190] Re: Clock applet chooses wrong timezone for many cities (eg Pittsburgh, Beijing)
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 someone actually specify those timezones; I don't think I have the time to do that, but it might only require around 300 or fewer entries. However, if a solution is needed for 8.04 - and I am also of the opinion that we do need one by then - then I'd prefer to have some input as to the best quick solution to this. Completely disabling the autoselection would probably be preferable to leaving the code as it is. -- 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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 207369] Re: visudo is completely unusable (/etc/sudoers can only be editted with an external text editor)
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 Debian bug, making
visudo use editor rather than vi once again, and then change the
documentation, which seems mainly to consist of the man page. For
consistency, however, it appears we would need to change vigr and vipw
as well.
Another would be to create a command edit_sudoers (and presumably
edit_passwd and edit_group as well), which would use editor/$EDITOR
instead (the latter is made more difficult, of course, by the env_reset
default of sudo); this would allow Ubuntu to have commands for editing
these files that would be usable by most cli users, while at the same
time not making the behaviour of the vi{sudo,pw,gr} commands unexpected
for those experienced with other systems.
I don't quite understand why visudo is so restrictive about the editor
anyway.
--
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 you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 179847] Re: Cannot configure printers when not connected to the network.
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 to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 207395] [NEW] system-config-printer hangs for several minutes while loading if network is connected but remote printer is unreachable.
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 has a printer ipp://192.168.1.123, but then tries to use the laptop on another network, system-config-printer will hang while starting up. Similarly, using something like ipp://example.com where example.com isn't actually reachable but does resolve can result in the same behaviour. This is not a duplicate of bug #165197. ** Affects: system-config-printer (Ubuntu) Importance: Undecided Status: New ** Summary changed: - system-config-printer hangs for several minutes while loading if network is connected but server is unreachable in particular ways. + system-config-printer hangs for several minutes while loading if network is connected but remote printer is unreachable. ** Description changed: 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 has a printer ipp://192.168.1.123, but then tries to use the laptop on another network, system-config-printer will hang while starting up. Similarly, using something like ipp://example.com where example.com isn't actually reachable but does resolve can result in the same behaviour. + + This is not a duplicate of bug #165197. -- system-config-printer hangs for several minutes while loading if network is connected but remote printer is unreachable. https://bugs.launchpad.net/bugs/207395 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 207369] Re: visudo is completely unusable (/etc/sudoers can only be editted with an external text editor)
(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 either use sudo -E to run visudo, or remove env_reset from sudoers. I'm closing this as invalid, because it seems that it is actually the correct, documented behaviour of visudo (there is, after all, a reason for it to have that name). Discussions about changing this probably need to take place elsewhere. ** Changed in: sudo (Ubuntu) Status: New = Invalid -- 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 you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 207369] Re: visudo is completely unusable (/etc/sudoers can only be editted with an external text editor)
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 you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 185190] Re: Clock applet chooses wrong timezone for many cities (eg Pittsburgh, Beijing)
The obvious way to fix this would be to add a timezone 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 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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 185190] Re: Clock applet chooses wrong timezone for many cities (eg Pittsburgh, Beijing)
** 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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 185190] Re: Clock applet chooses wrong timezone for many cities (eg Pittsburgh, Beijing)
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 timezone 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 convoluted nature of gnome-panel applets; I can't keep the Ubuntu version of the clock applet from loading, and can't figure out how to load the more recent applet manually. ** Attachment added: Patch for gnome-panel http://launchpadlibrarian.net/12714309/gnome-panel-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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 185190] Re: Clock applet chooses wrong timezone for many cities (eg Pittsburgh, Beijing)
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 possible to allow timezone entries for larger areas than just locations; for example, having one under a state or country apply to all cities and locations under that tag. However, I've attempted to change as little as possible with these patches, and so haven't gone about implementing such a system. ** Attachment removed: Patch for gnome-panel http://launchpadlibrarian.net/12714309/gnome-panel-tzfix.diff ** Attachment added: gnome-panel-tzfix.diff http://launchpadlibrarian.net/12718172/gnome-panel-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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 185190] Re: Clock applet chooses wrong timezone for many cities (eg Pittsburgh, Beijing)
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 work. However, I don't think upstream will accept that solution, whereas I think that having timezone data in the Locations.xml would be more likely to be accepted. If someone who has the ability to actually apply any of the patches here would give an opinion on what should be done, I would be happy to implement the code (though I certainly can't enter the timezone data!). -- 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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 69184] Re: gedit error Could not create a backup file when trying to save a file in a VFAT partition
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 create a backup file when trying to save a file in a VFAT partition https://bugs.launchpad.net/bugs/69184 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 65941] Re: XHTML file recognition
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 are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 192051] Re: Vinagre keyboard not working, mouse not always visible
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 for the screen in order to place the focus there, and then press Tab in order to move the focus to the screen. After doing so, everything should work normally, including the Ctrl-Alt to grab the mouse, which doesn't work unless the screen is focused. I'll probably report this upstream rather soon, as it doesn't appear to have been noted there yet. The bug should probably be rather easy to fix. ** Changed in: vinagre (Ubuntu) Status: New = Confirmed -- Vinagre keyboard not working, mouse not always visible https://bugs.launchpad.net/bugs/192051 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 70569] Re: 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)
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) https://bugs.launchpad.net/bugs/70569 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 42553] Re: wacom input devices enabled by default, why?
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://launchpad.net/bugs/42553 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 62980] Re: Arrow keys are incorrectly mapped in vim
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? I know that it isn't the full version, but it is still there and should act like vim rather than vi. Personally, I think the whole thing is rather silly, but the response I received on -devel seemed to indicate that there was considerable support for keeping 'vi' as meaning compatible mode. -- Arrow keys are incorrectly mapped in vim https://launchpad.net/bugs/62980 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 62980] Re: Arrow keys are incorrectly mapped in vim
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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 19066] Re: Pango-enabled firefox breaks MathML support
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 support - in other words, the bug hasn't been fixed, but it won't show up for most users now. -- Pango-enabled firefox breaks MathML support https://launchpad.net/bugs/19066 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 79619] Re: Add/Remove programs crashed on Feisty
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 prevent a whole class of possible bugs where the pickle file was corrupted. Is there some reason for not applying the patch, besides the obvious reason that it would be a change to the code? -- Add/Remove programs crashed on Feisty https://launchpad.net/bugs/79619 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 36014] Re: kernel can't scale cpu frequency
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 the frequency, and it is quite probable that acpi_cpufreq uses this code as well. Nacim Rahal's comments might point to what is happening, however. It could be that the BIOS is frequency-limiting due to overheating, and then something is happening to cause the limiting to stick even after the overheating. I might be able to test this if I have time next week. -- 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 76396] Re: Abiword ignores DPI setting for zooming, assumes 72 dpi (1440 dpi / 20)
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.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76396] Re: Abiword ignores DPI setting for zooming, assumes 72 dpi (1440 dpi / 20)
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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76396] Re: Abiword ignores DPI setting for zooming, assumes 72 dpi (1440 dpi / 20)
I have a patch for this which compiles in the CVS of abiword, but the version not only aborts in feisty, but also locks up the system (probably X) to the point of complete inoperability when run under gdb. I will try with the version in feisty - my guess is that CVS version has some problems. ** 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
[Bug 76396] Re: Abiword ignores DPI setting for zooming, assumes 72 dpi (1440 dpi / 20)
** 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
[Bug 76396] Re: Abiword ignores DPI setting for zooming, assumes 72 dpi (1440 dpi / 20)
A patch is now upstream, and can be easily modified to work with the version in feisty (s_getDeviceResolution already exists there, so the patch fails). However, it needs some work to get it into a reasonable state, as I don't know enough C++ - the display needs to be opened (closed) when 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 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
[Bug 76807] /etc/skel/.bashrc sets HISTCONTROL twice in succession.
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 HISTCONTROL=ignoreboth, which has the effect of combining ignoredups and ignorespace. There is no point in setting one first and then setting ignoreboth. This was probably caused by bug #66539. ** Affects: bash (Ubuntu) Importance: Undecided Status: Unconfirmed -- /etc/skel/.bashrc sets HISTCONTROL twice in succession. https://launchpad.net/bugs/76807 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76803] Re: Powermanga not
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 PROTECTED]:~$ ls -la /var/games/powermanga/powermanga.hi - -rw-rw-r-- 1 root games 0 2006-12-13 16:17 /var/games/powermanga/powermanga.hi - [EMAIL PROTECTED]:~$ ls -la /var/games/powermanga/powermanga.hi* - -rw-rw-r-- 1 root games 0 2006-12-13 16:17 /var/games/powermanga/powermanga.hi - -rw-rw-r-- 1 root games 0 2006-12-13 16:17 /var/games/powermanga/powermanga.hi-easy - -rw-rw-r-- 1 root games 0 2006-12-13 16:17 /var/games/powermanga/powermanga.hi-hard - [EMAIL PROTECTED]:~$ id - uid=1000(lhansen) gid=1000(lhansen) groups=4(adm),20(dialout),24(cdrom),25(floppy),29(audio),30(dip),44(video),46(plugdev),109(lpadmin),111(scanner),114(admin),1000(lhansen) + In edgy and feisty, /usr/games/powermanga is not in the games group and + is not setgid. It needs these two properties to be able to write the + high score files in /var/games/powermanga/. ** Changed in: Ubuntu Sourcepackagename: None = powermanga Status: Unconfirmed = Confirmed ** Summary changed: - Powermanga not + Powermanga binary not setgid games -- Powermanga binary not setgid games https://launchpad.net/bugs/76803 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 76396] Abiword ignores DPI setting for zooming, assumes 72 dpi (1440 dpi / 20)
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 Abiword uses a resolution of 72 dpi for zooming, which would make sense as 72*20=1440. This should be relatively easy to fix in the GNOME and Gtk versions - I should be able to write a patch that will scale the given zoom by screen_dpi/72 to get the zoom that Abiword should use. I will report this upstream and try to fix it later. ** Affects: abiword (Ubuntu) Importance: Undecided Status: Unconfirmed -- 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
[Bug 36014] Re: kernel can't scale cpu frequency
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 36014] Re: kernel can't scale cpu frequency
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 cpufreq code, it might solve the problem, though of course you would have no frequency scaling. You could also use my hackish fix. In addition, I'm thinking about writing the safer fix that I outlined earlier. Unfortunately, I have no way of knowing whether it will work or not (my computer randomly stopped having the bug about 6 months ago), so you would need to test the kernel. Luckily, we are both running Edgy. I'll try to do this in the next few days. -- 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 74325] Baobab uses incorrect units
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 some patches in the next few days. ** Affects: gnome-utils (Ubuntu) Importance: Undecided Status: Unconfirmed ** Description changed: Baobab displays directory content sizes in binary prefix based units, - but uses SI prefixes. The sizes need to either be displayed with the - correct units (KiB, MiB, etc), or the calculation scheme needs to be - changed so that the numbers are in SI units. I will report this upstream - and write some patches in the next few days. + 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 some + patches in the next few days. -- Baobab uses incorrect units https://launchpad.net/bugs/74325 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 74325] Re: Baobab uses incorrect units
** 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/bugs/74325 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 36014] Re: kernel can't scale cpu frequency
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_max_freq, scaling_min_freq, cpufreq_max_freq and cpufreq_min_freq, all in /sys/devices/system/cpu/cpu0/cpufreq. If scaling_max_freq is not the same as scaling_min_freq, then you are not experiencing this bug, and have another issue. If you do have this bug, then you might want to try my suggestion detailed in previous comments about commenting out the PPC frequency limiting code if you are comfortable with doing so. -- 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 36014] Re: kernel can't scale cpu frequency
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 none of my ideas are without disadvantages. It would not be overly difficult to write a patch that, if a Pentium M was detected, and the PPC tried to limit the frequency in this way (min_freq==max_freq), would cause the PPC's advice to be ignored. However, there is a possibility that this would not solve the problem for everyone, and it is also possible that it would cause problems for others. It might prove to be hard to maintain, as well, since I do not believe that such a patch would be considered suitable for inclusion in the vanilla kernel. Unfortunately, I still don't understand *why* the PPC gives this false information. Does anyone have any ideas? -- 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 36014] Re: kernel can't scale cpu frequency
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 because it appears to be an obscure race condition that appears and disappears, and I haven't had it in quite a long time. If you are comfortable with doing so, try my method listed earlier: comment out the verification steps in __cpufreq_set_policy in cpufreq.c. You need to keep the ACPI PPC from being used to limit the maximum frequency. This applied to 2.6.15, so you might need to make some changes to the process for it to work on newer kernels. -- 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 71121] Re: 0.1.20060928-2 makes default gnome fonts ugly
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/71121 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 71121] Re: 0.1.20060928-2 makes default gnome fonts ugly
I'm attaching two patches here, one which changes all of the prefer to accept, and one which removes all of the alias 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, so I suppose that the accept patch should be the least controversial. However, I don't understand why the font configuration for uming does this. Is there some language reason? In addition, why is it declaring itself as preferred for the sans alias, which *doesn't even exist*? But I'll file another bug about those issues. ** Attachment added: Patch removing alias sections from ttf-arphic-uming http://librarian.launchpad.net/5035363/uming-noalias.patch -- 0.1.20060928-2 makes default gnome fonts ugly https://launchpad.net/bugs/71121 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 71121] Re: 0.1.20060928-2 makes default gnome fonts ugly
This is the patch that changes all prefer tags to accept tags, and is probably the better and more conservative of the two patches. ** Attachment added: Changes all prefer tags to accept http://librarian.launchpad.net/5035368/uming-accept.patch -- 0.1.20060928-2 makes default gnome fonts ugly https://launchpad.net/bugs/71121 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 58993] Re: updae available: 0.1.20060903
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.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 35084] Re: Syntax highlighting vor cmake is missing
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 vor cmake is missing https://launchpad.net/bugs/35084 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63862] Re: wacom entries appear even when not having a tablet
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 cause of all of this is that xorg.conf just doesn't work well with hotplugging, and the configuration system of Xorg will eventually need to be redone entirely, which will fix all problems of this sort. ** Changed in: xorg (Ubuntu) Status: Unconfirmed = Rejected -- wacom entries appear even when not having a tablet https://launchpad.net/bugs/63862 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 69181] Re: firefox has bee ncrashing often in edgy
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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 55809] Re: HAL changes wireless interface (net.80211) to wired (net.80203) in info.category after suspend
*** 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 mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 34633] Re: Ctrl-C wrong exit help in insert mode
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://wiki.ubuntu.com/UbuntuBackports for more information. ** Changed in: vim (Ubuntu) Status: Unconfirmed = Fix Released -- Ctrl-C wrong exit help in insert mode https://launchpad.net/bugs/34633 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 40733] Re: firefox - tab switching causes unintended tab dragdrop
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 dragdrop https://launchpad.net/bugs/40733 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 69611] Re: jump to last position when reopening file
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 mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63448] Re: [edgy] command tab-completion broken in vim
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. ** Changed in: vim (Ubuntu) Status: Unconfirmed = Fix Released -- [edgy] command tab-completion broken in vim https://launchpad.net/bugs/63448 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 62980] Re: Arrow keys are incorrectly mapped in vim
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 are part of that compatibility. In reality, the bug is that in Dapper, the arrow keys aren't incorrectly mapped when running vi. To run vim, instead of vi, use the vim command, which reads /etc/vim/vimrc. ** Changed in: vim (Ubuntu) Status: Confirmed = Rejected -- Arrow keys are incorrectly mapped in vim https://launchpad.net/bugs/62980 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 70569] 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)
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 another variant of vim, such as vim-full or vim-gnome is installed, the vi command sources /etc/vim/vimrc, which among other things sets nocompatible, so, for example, arrow keys work in insert mode. This is not the intended behaviour. ** Affects: vim (Ubuntu) Importance: Undecided Status: Unconfirmed -- 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) https://launchpad.net/bugs/70569 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 68960] Re: Vim locks up while editing a specific file (file attached)
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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 65947] Re: gvim will not use the same filename for writing
*** 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.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 46907] Re: gVim doesn't handle german umlauts correctly
*** 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.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 69267] Re: vim-gnome misinterprets non-ascii filenames when opened via nautilus
I'm confirming this, and have updated the description. This only happens when the file is opened via nautilus. It may be that this is actually a bug in nautilus, but I do not have enough understanding of what is going on to tell right now. I will look into this further tomorrow. ** Summary changed: - vim-gnome doesn't open non-ascii filenames by double click + vim-gnome misinterprets non-ascii filenames when opened via nautilus ** Description changed: - After upgrade to Edgy I can't open file with non-ascii symbols in path - or filename in my Gnome desktop with my default GVim Text Editor - - gvim from vim-gnome package. After double click on file - ~/Desktop/тест.txt in vim status line I see - ~/Desktop/Ñ82еÑ81Ñ82.txt [New File]. + After upgrade to Edgy, when a file with non-ascii characters in the path + or filename is opened with vim-gnome via nautilus, the filename is + garbled. For example, when opening ~/Desktop/тест.txt, vim opens + ~/Desktop/Ñ82еÑ81Ñ82.txt instead. This happens across in all + UTF-8 locales tested, most likely all (at least en_US and ru_RU) - Forgot to say: + This does not occur when opening via the command line, only when opening + via nautilus. + version of vim-gnome is 7.0-035+1ubuntu5 - locale settings: - % locale - LANG=ru_RU.UTF-8 - LANGUAGE=ru_RU:ru:en_GB:en - LC_CTYPE=ru_RU.UTF-8 - LC_NUMERIC=ru_RU.UTF-8 - 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_IDENTIFICATION=ru_RU.UTF-8 - LC_ALL= + + (edited by Constantine Evans) ** Changed in: vim (Ubuntu) Status: Unconfirmed = Confirmed -- vim-gnome misinterprets non-ascii filenames when opened via nautilus https://launchpad.net/bugs/69267 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 66878] Re: Spellchecking impossible for most languages
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/ubuntu-bugs
[Bug 17386] Re: colorscheme get's sourced twice resulting in lost custom highlighting
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 lost custom highlighting https://launchpad.net/bugs/17386 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 47385] Re: Gvim doesn't scroll correctly when using arrows
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 problem, please reopen the bug. ** Changed in: vim (Ubuntu) Status: Unconfirmed = Fix Released -- Gvim doesn't scroll correctly when using arrows https://launchpad.net/bugs/47385 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 35925] Re: Dapper: hitting q: in (g)vim causes a long cpu hang when syntax highlighting is enabled
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 highlighting is enabled https://launchpad.net/bugs/35925 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 65941] Re: XHTML file recognition
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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 62980] Re: Arrow keys are incorrectly mapped in vim
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.net/bugs/62980 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 55068] Re: vim-gtk won't work
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 that case, it can be corrected by using update- alternatives --config gvim and selecting vim.gnome. ** Changed in: vim (Ubuntu) Status: Unconfirmed = Needs Info -- vim-gtk won't work https://launchpad.net/bugs/55068 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 46209] Re: Nautilus Passes Relative Path to vim for Remote Files
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/mailman/listinfo/ubuntu-bugs
[Bug 69611] Re: jump to last position when reopening file does not work when g is remapped.
** 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@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 62980] Re: Arrow keys are incorrectly mapped in vim
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 and expect xemacs to start by default, would they? IbeeX, a power user will not know how to fix this, because it is not easy to fix. It breaks the -v option to vim as well as breaking the vi command. The only way to fix it right now means setting compatible in vimrc, which then prevents them from running vim in nocompatible mode without changing the vimrc. Finally, this isn't a bug - all documentation for vim states that vi and vim -v start vim in compatibility mode and read vimrc.tiny. What you are requesting is a change in the behaviour of vim, which, according to https://wiki.ubuntu.com/Bugs/CommonTasks, should go to the appropriate mailing list instead of being discussed on launchpad. But do note that I have discussed this ubuntu-devel before, and was told by several people that vi should start vim in compatibility mode (I wanted vi to start vim at the time). Perhaps with more people, you will have more success. ** Changed in: vim (Ubuntu) Status: Needs Info = Rejected -- Arrow keys are incorrectly mapped in vim https://launchpad.net/bugs/62980 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 62140] Re: Pleave remove Insert (INS) / Overwrite (OVR) modes
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), especially since, if such changes were to be made, it would be best if they were made consistently throughout packages in Ubuntu's main. ** Changed in: gedit (Ubuntu) Status: Unconfirmed = Rejected -- Pleave remove Insert (INS) / Overwrite (OVR) modes https://launchpad.net/bugs/62140 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 70316] Re: Using F5 as Hotkey in the Date/Time Plugin
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 Hotkey in the Date/Time Plugin https://launchpad.net/bugs/70316 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 69557] Re: Anjuta requires autogen in order to create new project
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: Unconfirmed = Rejected -- Anjuta requires autogen in order to create new project https://launchpad.net/bugs/69557 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 69184] Re: gedit error Could not create a backup file when trying to save a file in a VFAT partition
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: octal file permissions You can change permissions using the parameter umask. But be aware that it must be the bitmask of permissions that are not present for the mountpoint. It is an octal number, formed like this: * character '0': Indicates that this is an octal number, not decimal. * first digit: owner user permissions * second digit: owner group permissions * third digit: world permissions (every other user on the system) -- gedit error Could not create a backup file when trying to save a file in a VFAT partition https://launchpad.net/bugs/69184 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 69184] Re: gedit error Could not create a backup file when trying to save a file in a VFAT partition
** 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 save a file in a VFAT partition https://launchpad.net/bugs/69184 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 69184] Re: gedit error Could not create a backup file when trying to save a file in a VFAT partition
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 VFAT partition https://launchpad.net/bugs/69184 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 36014] Re: kernel can't scale cpu frequency
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 right now, and so it is difficult for me to work on. -- 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 69181] Re: firefox has bee ncrashing often in edgy
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 helpful if you could attach a backtrace of the crashes (see https://wiki.ubuntu.com/DebuggingFirefox). ** Changed in: firefox (Ubuntu) Status: Unconfirmed = Needs Info -- firefox has bee ncrashing often in edgy https://launchpad.net/bugs/69181 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 69184] Re: gedit error Could not create a backup file when trying to save a file in a VFAT partition
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 https://launchpad.net/bugs/69184 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 36014] Re: kernel can't scale cpu frequency
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 discussing. If it doesn't resolve by itself, you could try commenting out the relevant checks in the kernel, as I discussed earlier in the bug. Your sudo command didn't work because of order-of-operations problems (what you wrote was essentially (sudo (echo 1)) /file from an order of operation standpoint). But you might want to look into a howto on cpufreq operation, because it does not appear that you are going about setting it up in the right way. fishwithapipe, your problem is not related to this bug. slazZ, in the worst case, you can do what I discussed (I didn't post a patch because it was too much of a kludge): The problem occurs in the verification steps of __cpufreq_set_policy in cpufreq.c. If one comments out that (from after the memcpy to before the data-min = policy-min), cpufreq works fine. If you look at that code, you should be able to find the portions that need to be commented out. If I recall correctly, the basic idea was to comment out the part where the driver checked the PPU for the maximum frequency it allowed. -- 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 63862] Re: wacom entries appear even when not having a tablet
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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 36014] Re: [Bug 36014] Re: kernel can't scale cpu frequency
-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 experiencing a bug. Throttling is not the same as scaling. Your computer most likely does not support Intel's Speedstep, and needs some other module to be loaded. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFFDu4aejd/sU2TVARAnhvAJoDHbdMmYa2TQb5AyuwMps+iq5e5wCfTjtj RT+0kyhbUfDbuCtLzjd1PvY= =3+D9 -END PGP SIGNATURE- -- 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 32561] Re: Pango-enabled firefox is much slower
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 firefox is much slower https://launchpad.net/bugs/32561 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 56126] IMAP4rev1 should be removed as an option
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 in our version - it just serves to cause a variety of problems in evolution for users who mistakenly choose it instead of IMAP. ** Affects: evolution (Ubuntu) Importance: Untriaged Status: Unconfirmed -- IMAP4rev1 should be removed as an option https://launchpad.net/bugs/56126 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 56126] Re: IMAP4rev1 should be removed as an option
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 entirely. We are already telling everyone who files a bug report about it to stop using it. -- IMAP4rev1 should be removed as an option https://launchpad.net/bugs/56126 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 22687] Re: evolution ignoring preferred browser setting
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://launchpad.net/bugs/22687 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 56126] Re: IMAP4rev1 should be removed as an option
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 be removed as an option https://launchpad.net/bugs/56126 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 40125] Re: Doesn't bring the network back online when resuming from suspend / hibernate
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-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 55809] Re: NetworkManager detects wireless interface as wired interface after coming out of suspend.
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-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 55809] NetworkManager detects wireless interface as wired interface after coming out of suspend.
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 actually configure the interface correctly. I will post a log of NM's stderr output as soon as I get a chance. ** Affects: network-manager (Ubuntu) Importance: Untriaged Status: Confirmed -- NetworkManager detects wireless interface as wired interface after coming out of suspend. https://launchpad.net/bugs/55809 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 55809] Re: NetworkManager detects wireless interface as wired interface after coming out of suspend.
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. -- NetworkManager detects wireless interface as wired interface after coming out of suspend. https://launchpad.net/bugs/55809 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 55809] Re: NetworkManager detects wireless interface as wired interface after coming out of suspend.
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) in info.category after suspend ** Description changed: - 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 - actually configure the interface correctly. + On a Dell D600 running Edgy with an Intel 2200BG, HAL changes the + information published on the network device after coming out of suspend. + Instead of listing it as a wireless device, it changes info.category and + info.capabilities to advertise it as net.80203. - I will post a log of NM's stderr output as soon as I get a chance. + Network Manager thus 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 actually configure the interface correctly, + since it is using ZeroConf. ** Changed in: network-manager (Ubuntu) Status: Confirmed = Rejected -- HAL changes wireless interface (net.80211) to wired (net.80203) in info.category after suspend https://launchpad.net/bugs/55809 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 55809] Re: HAL changes wireless interface (net.80211) to wired (net.80203) in info.category after suspend
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) in info.category after suspend https://launchpad.net/bugs/55809 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 55814] Re: Nautilus duplicates thumbnails for files with special characters when searching
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 directory, and only that directory. 4) Use the nautilus search feature (not beagle) to search for the file name in that directory. 5) Notice that there are now two of the same thumbnail in .thumbnails/normal. I am quite surprised that the reporter was able to notice this. -- 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 55814] Re: Nautilus duplicates thumbnails for files with special characters when searching
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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 36014] Re: kernel can't scale cpu frequency
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-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 36014] Re: kernel can't scale cpu frequency
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 description in the patch for 2.6.17 is useful, reading it carefully makes it seem to me like the bug didn't manifest itself in Ubuntu because of a change in the kernel, but instead because of a change in something like init script timing, and also that the problem can appear somewhat randomly. As far as I know, the bug is not fixed for Dapper however, and my attempt to backport the 2.6.17-rc2 patch didn't seem to work. I might try it again in a few days. -- 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 36014] Re: kernel can't scale cpu frequency
I've been working on trying to fix this, and have had some success in tracking down the problem. The problem occurs in the verification steps of __cpufreq_set_policy in cpufreq.c. If one comments out that (from after the memcpy to before the data-min = policy-min), cpufreq works fine. Something seems to be going wrong with the verification step, but the debugging information doesn't appear to offer any specifics as to what step is going wrong. When the problem is there, I get the following output: cpufreq-core: setting new policy for CPU 0: 60 - 160 kHz freq-table: request for verification of policy (60 - 160 kHz) for cpu 0 freq-table: verification lead to (60 - 160 kHz) for cpu 0 freq-table: request for verification of policy (60 - 60 kHz) for cpu 0 freq-table: verification lead to (60 - 60 kHz) for cpu 0 cpufreq-core: new min and max freqs are 60 - 60 kHz I'll get more on this later. -- 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 36014] Re: kernel can't scale cpu frequency
I've further narrowed this down to the cpufreq_verify_within_limits call inside acpi_processor_ppc_notifier in acpi/processor_perflib.c. I'm not quite sure why the maximum value gets set to the minimum value, but my guess is that for some reason, ppc is getting set to the lowest frequency state instead of the highest frequency state. I've stuffed some printk's in the code and will try to see if this is the problem the next time I reboot. -- 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
