Re: [Bug 37214] Re: [dapper] metacity does not respect /apps/metacity/general/mouse_button_modifier properly
I'm talking about mapping to Meta using the gnome keyboard dialog, I don't
use anything else, it's one of those things that I've done since my first
day using Ubuntu.
As for this:
$ gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd
layouts = []
model =
options = []
overrideSettings = true
It didn't look very useful, so I didn't send it.
On 9/30/06, Sebastien Bacher <[EMAIL PROTECTED]> wrote:
>
> you still didn't reply to the question about the configuration stored to
> gconf ("gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd"). How do
> you do that key mapping? Using xkbcomp?
>
> --
> [dapper] metacity does not respect
> /apps/metacity/general/mouse_button_modifier properly
> https://launchpad.net/bugs/37214
>
--
[dapper] metacity does not respect /apps/metacity/general/mouse_button_modifier
properly
https://launchpad.net/bugs/37214
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 37214] Re: [dapper] metacity does not respect /apps/metacity/general/mouse_button_modifier properly
I like to map Meta to the windows keys, so that I can bind Meta+ to shortcuts that use the key. My workaround for this bug has been to pick Super in the window properties, and then map meta to the windows keys. This makes the win keys move windows, leaving alt untouched, while letting me use the windows key for shortcuts. Sorry for not replying to your comment, twice, it wasn't intentional. On 9/30/06, Sebastien Bacher <[EMAIL PROTECTED]> wrote: > You still didn't reply to my "What keyboard configuration do you use > (gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd)? " question. > Picking the "Super (or "Windows logo") option from gnome-window- > properties makes windows_key+click make move windows on my edgy desktop -- [dapper] metacity does not respect /apps/metacity/general/mouse_button_modifier properly https://launchpad.net/bugs/37214 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 22349] Re: [Bug 22349] Re: Cpufreq applet locks up desktop with hand Icon (double click) or gnome-panel
I can test this on Dapper if you'd like, I've taken to backporting packages from edgy sources when it suits me. -- Cpufreq applet locks up desktop with hand Icon (double click) or gnome-panel https://launchpad.net/bugs/22349 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 22349] Re: Cpufreq applet locks up desktop with hand Icon (double click) or gnome-panel
Well, this was pretty hard to get working because of the dependencies on newer stuff, and I ended up ignoring them whenever I could get away with it, but I eventually got something built with 2.15.2, and installed it. When I left click or double click on the applet, it doesn't lock up, but a menu doesn't pop up either. Contrast this with the version 2.14.2: when I clicked on that, the applet and the neighboring system monitor applet would stop responding, but only for about 5 seconds. Not as bad as the bug description, but I remember older versions of the applet being worse, to the point where I'd have to kill the panel. Hope this is useful to know. -- Cpufreq applet locks up desktop with hand Icon (double click) or gnome-panel https://launchpad.net/bugs/22349 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 37214] Re: [dapper] metacity does not respect /apps/metacity/general/mouse_button_modifier properly
Oops, I didn't notice that comment. I use the win key to move windows around, and I don't want alt to be used for this, because then I can't alt-click on links in firefox. It doesn't seem to matter what I use to set the setting, but I use either gconf-editor or the Window prefs dialog (with identical effects). The dialog lets the user select between either Ctrl, Alt, and Super or Ctrl, Alt, and Meta, depending on whether the layout settings are default, or Meta is mapped to the Win keys, respectively. I can't say any more than that, cause I'm using Gentoo right now, and the above is what I can remember off the top of my head. However, it might be useful to note that I've experienced the bug in both distributions, which would indicate that it's an upstream issue, right? -- [dapper] metacity does not respect /apps/metacity/general/mouse_button_modifier properly https://launchpad.net/bugs/37214 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 37214] Re: [dapper] metacity does not respect /apps/metacity/general/mouse_button_modifier properly
I'm very sorry, but I was completely wrong about this having gone away, since my last comment, I've observed the issue on both a computer running Breezy, and this fresh install of Dapper that I'm using right now, which is on a different computer from the one that I reported the bug on. -- [dapper] metacity does not respect /apps/metacity/general/mouse_button_modifier properly https://launchpad.net/bugs/37214 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 42503] CPU Frequency Applet causes panel hangup when left-clicked
Public bug reported: Affects: gnome-panel (Ubuntu) Severity: Normal Priority: (none set) Status: Unconfirmed Description: Add a CPU Frequency applet to your panel (I only have tried this with one panel), then left-click on it. Your panel will cease to respond to input, though the panel otherwise looks normal. I usually work around this by running killall gnome-panel. -- CPU Frequency Applet causes panel hangup when left-clicked https://launchpad.net/bugs/42503 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 37214] Re: [dapper] metacity does not respect /apps/metacity/general/mouse_button_modifier properly
The issue seems to have gone away. Apologies for the long response time, I haven't used Ubuntu in a while. -- [dapper] metacity does not respect /apps/metacity/general/mouse_button_modifier properly https://launchpad.net/bugs/37214 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 39296] intentionally flawed desktop background
Public bug reported: Affects: ubuntu-artwork (Ubuntu) Severity: Normal Priority: (none set) Status: Unconfirmed Description: I won't argue with the logic behind "This is not the final artwork", but it isn't necessary to remind the user of that constantly, it makes too much of a difference in the user experience. Plus, I think this background is generally disgreeable, it looks like whoever made it was trying to cover every possible shade my food may turn out looking like, from dark brown to light brown to deep reddish brown. I'm being perfectly serious here, this wallpaper is a definite step back from the previous one, even if one were to remove the text and crane. Being the developer branch isn't an acceptable excuse to foist bad artwork on people, much like you wouldn't intentionally create bugs in other packages just for the sake of having bugs in the distibution. Apologies to the author if they disagree with my assessment of their picture. -- intentionally flawed desktop background https://launchpad.net/malone/bugs/39296 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 37214] Re: [Bug 37214] [dapper] metacity does not respect /apps/metacity/general/mouse_button_modifier properly
I was setting it using the GUI dialog, but I wanted to narrow down the problem to metacity, so I verified that it was actually being set properly in gconf. Setting it to super would be a decent workaround though. I dislike the way GNOME refuses to expose all of its functionality in the dialogs, it's annoying ( and makes for a KDE switcher). Simon On 3/30/06, Holger Bauer <[EMAIL PROTECTED]> wrote: > > Public bug report changed: > https://launchpad.net/malone/bugs/37214 > > Comment: > Setting the key to instead of works here. The graphical > dialog from system->preferences->windows does this too btw. > -- [dapper] metacity does not respect /apps/metacity/general/mouse_button_modifier properly https://launchpad.net/malone/bugs/37214 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 37214] [dapper] metacity does not respect /apps/metacity/general/mouse_button_modifier properly
Public bug reported: https://launchpad.net/malone/bugs/37214 Affects: metacity (Ubuntu) Severity: Normal Priority: (none set) Status: Unconfirmed Description: I usually set the gconf key /apps/metacity/general/mouse_button_modifier to , both because I prefer this key and because occasionally if I need to alt or ctrl click on something, I should be able to do that. However, in Dapper, now metacity thinks it should move windows when I alt-click on them, even when that key is set to . Running xev confirms that my keyboard is functioning properly. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 35449] Random disk access, every second every day
Public bug report changed: https://launchpad.net/malone/bugs/35449 Comment: I know this is a very tough thing to track down, but I do agree that if I computer isn't being touched, chances are whatever is accessing the disk can wait, without impacting the user experience. I urge developers to take this issue seriously if they have the time. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 30015] /dev/pilot/ is never used by PDAs
Public bug report changed:
https://launchpad.net/malone/bugs/30015
Comment:
The default symlinks can be changed by adding a rule to any file in
/etc/udev/rules.d/. For example, in my installation, I have a file at
/etc/udev/rules.d/10-custom.rules, and in it I have two lines:
KERNEL=="tty*" SYSFS{product}=="Palm Handheld", SYMLINK="pilot%m pilot"
GROUP="plugdev"
KERNEL=="tty*" SYSFS{manufacturer}=="Palm_ Inc." SYMLINK="pilot%m pilot"
GROUP="plugdev"
To figure out what this means, there's a very helpful udev guide at
http://www.reactivated.net/writing_udev_rules.html. In short, though,
udev rules let you customise certain properties of devices. The ==
statements are rules that decide which devices to customize, where
KERNEL is the node name in dev (eg. /dev/ttyUSB0 will match tty*,
/dev/dsp will not), and SYSFS{manufacter} matches a property of the
device that can be found by using udevinfo.
The = statements assign properties to the device in question, and are a
bit easier to understand. SYMLINK creates symlinks in dev, and GROUP
changes the group of the device node (the original one) so that regular
users can access the device if they are in the correct group. Syntax
can be found in man udev
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
