[Bug 1067951] Re: Firefox loses window decorations in GNOME Classic and MATE with Compiz
Here is a patch I wrote for Hypra not so long ago to properly fix this. Not sure if it has a chance of ever getting merged given the maintenance status of upstream Compiz 0.9, but it works great so far for us. ** Attachment added: "Fix missing Firefox's frame in certain cases" https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1067951/+attachment/5239824/+files/16_firefox_frame -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1067951 Title: Firefox loses window decorations in GNOME Classic and MATE with Compiz To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1067951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1594097] Re: [Xenial] Geany 1.27 eats all the CPU and RAM then the session freezes
> open("/home/melodie/badblocks.log.txt", O_RDONLY) = 9
> fstat(9, {st_mode=S_IFREG|0644, st_size=1547706436, ...}) = 0
You try to open a 1547706436 bytes (1.5Gb) file: /home/melodie/badblocks.log.txt
Geany will try and load this file into memory, which as it records a style
information byte with each data byte, will lead to at the very least 3Gb of
memory. It's likely to use even more temporarily at some points (I wouldn't be
surprised to see +1 times the file size when passing the buffer to the editing
component, Scintilla, so that would make it 4.5Gb).
Yes, it's kinda unfortunate, but doing it like this has other advantages (well,
temporary duplication only makes things simpler, no other advantages).
Realistically, the best we could do is ask the users whether they really want
to open such huge files, allowing to back off early.
If the file is loaded automatically at startup because it's part of the
session, you can either drop the session with the `-s` command-line
switch, or manually edit your ~/.config/geany/geany.conf (with something
else than Geany, or `geany -i`), and remove the `FILE_NAME_` line
corresponding to that file.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1594097
Title:
[Xenial] Geany 1.27 eats all the CPU and RAM then the session freezes
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/geany/+bug/1594097/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1584149] Re: [Ctrl-+] key-combo is disabled.
The default keybinding is [Ctrl]+[+]. If your keyboard layout requires a modifier to reach [+], then you need it there too. You can however rebind *View/Zoom In* to [Ctrl]+[=] in the preferences (Preferences/Keybindings) if you like. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1584149 Title: [Ctrl-+] key-combo is disabled. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geany/+bug/1584149/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1586317] Re: Geany exits with fatal error when starting it
Duplicate of https://bugs.launchpad.net/ubuntu/+source/geany/+bug/1536760 IMO. See the answer to it for further details, but the baseline is that the socket file is in the user's directory and so shouldn't ever be accessed by different users in a correct setup. Your problem probably is that you ran Geany through a misconfigured `sudo`, which accessed your user's home (rather than root's). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1586317 Title: Geany exits with fatal error when starting it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geany/+bug/1586317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1337015] Re: Geany incorrectly folds Ruby code
Fixed since Geany 1.25, available in Ubuntu since 15.10 (Wily) ** Changed in: geany (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1337015 Title: Geany incorrectly folds Ruby code To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geany/+bug/1337015/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1572182] Re: Geany removes executable bits when saving shell script
This is likely not a bug but a configuration issue. Did you change the value of the "various" preference `use_atomic_file_saving`? It is off by default for this very reason: it doesn't maintain metadata and attributes. See https://wiki.geany.org/config/all_you_never_wanted_to_know_about_file_saving and Edit→Preferences→Various→use_atomic_file_saving. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1572182 Title: Geany removes executable bits when saving shell script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geany/+bug/1572182/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1256506] Re: Configuration directory owned by root
** Changed in: geany (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1256506 Title: Configuration directory owned by root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geany/+bug/1256506/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1256506] Re: Configuration directory owned by root
Running Geany as an user with the environment pointing at another is not supported, and won't be changed. `sudo` should be configured to reset the environment so applications don't try and use another user's configuration directory. There are many reasons why resetting the environment is useful, and among other things avoiding the kind of issues at hand. Geany is definitely not the only application suffering from it (try bash history, nano configuration and whatnot). FWIW, the default sudo configuration on Debian Jessie/testing/unstable properly resets the environment (at least the offending part here) and does not suffer from the problem. You may want to reassign the issue to the sudo package maybe. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1256506 Title: Configuration directory owned by root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geany/+bug/1256506/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1482558] Re: geany does not handle properly creating multiple times the same document
Fixed upstream in https://github.com/geany/geany/commit/7215c5027711546cbe899fe4ccf828bd945c1d66 ** Changed in: geany (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1482558 Title: geany does not handle properly creating multiple times the same document To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1482558/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1498026] Re: Compile Geany with GTK3 rather than GTK2
Beware that currently a few plugins for Geany don't support GTK3, so would not be available with a GTK3 build of Geany. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1498026 Title: Compile Geany with GTK3 rather than GTK2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geany/+bug/1498026/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1536760] Re: geany cannot open simultaneously by multiple user
For me this is a bug in sudo configuration, because it does not properly resets the environment to use root's own home. It will have several other issues related to sharing configuration between users, that aren't resolved by simply adding the UID to the socket name. S/A https://sourceforge.net/p/geany/bugs/968/#0067 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1536760 Title: geany cannot open simultaneously by multiple user To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geany/+bug/1536760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 221112]
(In reply to comment #69) > (In reply to comment #66) > > > Regarding the voting, is there generic popular Linux-oriented site in > > France? Like slashdot.org or smth... > > There is a popular Linux-oriented site in France (linuxfr.org) and the > final ajustments of this layout were done after discussion on this site. But this has the same pitfall as any volunteered survey, it isn't any kind of representative. I for example myself barely ever read a linuxfr article, and wouldn't participate or even see a survey there. That doesn't mean I'm not a French fr/oss user :) Also note that people suffering from the situations are a lot more likely to do something and speak their mind than people perfectly happy with the situation. So probably "discussing" a problem is likely to only include opinion from people not happy with the current state, and people closely involved. > I realise there is a vocal minority that does not like some of those choices > but Just to be fair, I see *no one* else here arguing towards keeping right Ctrl Level5 modifier -- but sure, as I state above, people happy with it won't see the discussion or care, so it may be biased. > 1. the other alternatives used in the ancestors of this layout generated a > lot more hate mail If it broke people's apps (or apps broke with it, I don't care who's fault it is), I surely can understand people being angry. But similarly, since the change from this report broke people's right Ctrl key, I can understand they get angry. > 2. because I knew there was no choice everyone would like spacebar layout is > modular (and I'm the person who modularized it as part of the creation of > this layout). People can choose the previous behaviour if they want and a > few other possibilities were added as part of the modularization And we thank you for your work. But I don't think it's realistic to think everyone can "choose the previous behavior" if it means editing the keymap. I already said it, but it took me quite some time to find what caused my right Ctrl key to no longer work and fix it, and I think it's fair to consider myself a quite advanced user. If really reverting the addition of Level5 is not an option (but see below), please add an alternative layout. > 3. so far no one proposed any better option appart from removing symbols > which are necessary to write proper French (arguably proper French is not > the same as C code). The change in this particular report did not add or remove any symbol, it only moved one to Level5 because some apps couldn't handle Space with this layout. And as I said earlier, most of the incriminated apps (at least that I know of) don't even use Space anymore, rendering the change moot for them. And even if we wanted to please those apps, we mayb be able to without adding a new modifier (Level5) and a key for it -- again, see (comment #46). Also note that event though I admittedly don't use short-nbsp (I'm afraid I don't know the rules where this one should be used in French typography), I'm an heavy user of nbsp everywhere French typography tells me to do it. So no, I don't want to remove anything, don't worry -- but I'd like my right Ctrl key back :) > It's a lot easier to clamor for removal of the bits you > do not use than to try to design a general-purpose solution without cutting > corners It sure is, but although my nearly non-existent knowledge of keymaps may make my message somewhat irrelevant (e.g. I don't know how to apply my ideas), I investigated possible solutions in comment #46 -- although no one followed up on those. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/221112 Title: Can't use space bar in search bar when using french alternative keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/libgnomekbd/+bug/221112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1013881]
(In reply to comment #69) > (In reply to comment #66) > > > Regarding the voting, is there generic popular Linux-oriented site in > > France? Like slashdot.org or smth... > > There is a popular Linux-oriented site in France (linuxfr.org) and the > final ajustments of this layout were done after discussion on this site. But this has the same pitfall as any volunteered survey, it isn't any kind of representative. I for example myself barely ever read a linuxfr article, and wouldn't participate or even see a survey there. That doesn't mean I'm not a French fr/oss user :) Also note that people suffering from the situations are a lot more likely to do something and speak their mind than people perfectly happy with the situation. So probably "discussing" a problem is likely to only include opinion from people not happy with the current state, and people closely involved. > I realise there is a vocal minority that does not like some of those choices > but Just to be fair, I see *no one* else here arguing towards keeping right Ctrl Level5 modifier -- but sure, as I state above, people happy with it won't see the discussion or care, so it may be biased. > 1. the other alternatives used in the ancestors of this layout generated a > lot more hate mail If it broke people's apps (or apps broke with it, I don't care who's fault it is), I surely can understand people being angry. But similarly, since the change from this report broke people's right Ctrl key, I can understand they get angry. > 2. because I knew there was no choice everyone would like spacebar layout is > modular (and I'm the person who modularized it as part of the creation of > this layout). People can choose the previous behaviour if they want and a > few other possibilities were added as part of the modularization And we thank you for your work. But I don't think it's realistic to think everyone can "choose the previous behavior" if it means editing the keymap. I already said it, but it took me quite some time to find what caused my right Ctrl key to no longer work and fix it, and I think it's fair to consider myself a quite advanced user. If really reverting the addition of Level5 is not an option (but see below), please add an alternative layout. > 3. so far no one proposed any better option appart from removing symbols > which are necessary to write proper French (arguably proper French is not > the same as C code). The change in this particular report did not add or remove any symbol, it only moved one to Level5 because some apps couldn't handle Space with this layout. And as I said earlier, most of the incriminated apps (at least that I know of) don't even use Space anymore, rendering the change moot for them. And even if we wanted to please those apps, we mayb be able to without adding a new modifier (Level5) and a key for it -- again, see (comment #46). Also note that event though I admittedly don't use short-nbsp (I'm afraid I don't know the rules where this one should be used in French typography), I'm an heavy user of nbsp everywhere French typography tells me to do it. So no, I don't want to remove anything, don't worry -- but I'd like my right Ctrl key back :) > It's a lot easier to clamor for removal of the bits you > do not use than to try to design a general-purpose solution without cutting > corners It sure is, but although my nearly non-existent knowledge of keymaps may make my message somewhat irrelevant (e.g. I don't know how to apply my ideas), I investigated possible solutions in comment #46 -- although no one followed up on those. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1013881 Title: Right-Ctrl key broken on French OSS keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/1013881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 221112]
(In reply to comment #72) > The old layout was never removed and kept its historical name (fr latin9) No, we are speaking here of fr/oss, but before it got right Ctrl as level5 modifier (what this bug end up changing). I bet everyone complaining here was very happy with fr/oss before this Level5 modifier -- at least I was, this map has so everything useful (and more) on handy locations :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/221112 Title: Can't use space bar in search bar when using french alternative keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/libgnomekbd/+bug/221112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1013881]
(In reply to comment #72) > The old layout was never removed and kept its historical name (fr latin9) No, we are speaking here of fr/oss, but before it got right Ctrl as level5 modifier (what this bug end up changing). I bet everyone complaining here was very happy with fr/oss before this Level5 modifier -- at least I was, this map has so everything useful (and more) on handy locations :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1013881 Title: Right-Ctrl key broken on French OSS keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/1013881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 221112]
(In reply to comment #76) > Compose is not appropriate for basic symbols you need to write pretty much > any correct sentence in the target language. And adding a specific input > method for one symbol just because some people can't live with the modifier > ISO chose for level 5 is disproportionnate. Woow, calm down guys. What's disproportionate is the reaction here! *before* the change this report introduced, and which many of us are trying to get reverted, *both* nbsp and nbspc were easily available: nbsp AltGr+Shift+Space nbspc Ctrl+Shift+Space Reverting the change this report introduced would get this behavior. Please understand we just want to get nbspc moved back where it *was* (or for me, anywhere on a 1-4 level), not removed or anything. Also, realize that currently there is only *one* Level5-specific symbol, and that's nbspc, so we basically have a key only for that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/221112 Title: Can't use space bar in search bar when using french alternative keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/libgnomekbd/+bug/221112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1013881]
(In reply to comment #76) > Compose is not appropriate for basic symbols you need to write pretty much > any correct sentence in the target language. And adding a specific input > method for one symbol just because some people can't live with the modifier > ISO chose for level 5 is disproportionnate. Woow, calm down guys. What's disproportionate is the reaction here! *before* the change this report introduced, and which many of us are trying to get reverted, *both* nbsp and nbspc were easily available: nbsp AltGr+Shift+Space nbspc Ctrl+Shift+Space Reverting the change this report introduced would get this behavior. Please understand we just want to get nbspc moved back where it *was* (or for me, anywhere on a 1-4 level), not removed or anything. Also, realize that currently there is only *one* Level5-specific symbol, and that's nbspc, so we basically have a key only for that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1013881 Title: Right-Ctrl key broken on French OSS keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/1013881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 221112]
(In reply to comment #50) > Could someone create poll on some french(belgian) web site, linux-oriented. > Which behavior would be preferable? Is this even necessary? I mean, the change wasn't made in the first place because an user wasn't happy with the state, but because some apps couldn't handle it. And nowadays, at least some of those apps (Rhythmbox, Totem, …) have been fixed or altered in a way they do not suffer from it anymore, actually mostly nullifying the original point. Also, what a poll would do? This looks like a pretty subtle problem to me, and an uneducated user couldn't really tell. As far as they are concerned, I would think they just want everything working. Even me, if you ask I would say (as in my previous reply) just fix the XLookupString while keeping the original mapping, since IIUC it would fix everybody's issue. But I have no real clue whether it's a pertinent answer or not. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/221112 Title: Can't use space bar in search bar when using french alternative keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/libgnomekbd/+bug/221112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1013881]
(In reply to comment #50) > Could someone create poll on some french(belgian) web site, linux-oriented. > Which behavior would be preferable? Is this even necessary? I mean, the change wasn't made in the first place because an user wasn't happy with the state, but because some apps couldn't handle it. And nowadays, at least some of those apps (Rhythmbox, Totem, …) have been fixed or altered in a way they do not suffer from it anymore, actually mostly nullifying the original point. Also, what a poll would do? This looks like a pretty subtle problem to me, and an uneducated user couldn't really tell. As far as they are concerned, I would think they just want everything working. Even me, if you ask I would say (as in my previous reply) just fix the XLookupString while keeping the original mapping, since IIUC it would fix everybody's issue. But I have no real clue whether it's a pertinent answer or not. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1013881 Title: Right-Ctrl key broken on French OSS keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/1013881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1001841] Re: Nautilus-wipe should not require root privileges
Works as expected here, and never worked otherwise. Please note however that Nautilus needs to be restarted after installing nautilus-wipe for the item to appear, which may be the reason why you didn't find the item in your user's nautilus menus. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1001841 Title: Nautilus-wipe should not require root privileges To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus-wipe/+bug/1001841/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1013881]
(In reply to comment #45) > (In reply to comment #44) > > Until a solution is to be found, could 518c769d be reverted for now? > > Breaking the very standard behavior of right control > > It does not break the very standard behavior of right control any more than > altrgr breaks the very standard behavior of right alt For me it does. My keyboard has an "Alt Gr" label on the AltR key, so it indeed is expected to behave differently from Alt_L, but my ControlR key is labeled as "Ctrl", just like the ControlL key. And all other keyboards and OSes I ever used did handle ControlR the same as ControlL, as far as I was concerned as a user. Also, I find it more generically problematic to change the behavior of a common key on a widely used keymap. For example the change annoyed me for about a month before I took the time to debug this and edit my keymap -- and I can't imagine what a lambda user could do but learn to deal with it. Also, what is Level5 used for? IIUC, currently nothing but short-nbsp (or at least that I can find, which is practically the same from a user POV), turning Ctrl_R into a virtually useless key. So, what can we do? First, please note, for what is worth, that both Rhythmbox and Totem, which were cited as the applications having a problem with the previous state of things, are not affected anymore. Rhythmbox don't use Control+Space as a shortcut anymore, and Totem seem to react to any space keysym, no matter the modifiers. So, unless there actually are other applications using Control+Space and suffering of the issue (Code::Blocks?), the problem does not even exist anymore. Also, maybe I just don't know how one is supposed to process the events, but those bugs look like an application or toolkit issue to me, is it? Then, practical changes. Before the change, Space behaved like this: Shift* | Control* | Level3 || keysym| XLookupString ---||-- | ||| 0x20 | 20 X | ||| 0x20 | 20 | X||| 0x20 | 20 | | X || 0x20 | 20 X | X||| 0x100202f | e2 80 af X | | X || 0xa0 | c2 a0 | X| X || NoSymbol | X | X| X || NoSymbol | And now we have: Shift* | ControlL | Level3 | Level5 || keysym| XLookupString ||- | |||| 0x20 | 20 X | |||| 0x20 | 20 | X|||| 0x20 | 00 | | X ||| 0x20 | 20 | || X || 0x20 | 20 X | X|||| 0x20 | 00 X | | X ||| 0xa0 | c2 a0 X | || X || 0x100202f | e2 80 af | X| X ||| 0x20 | 00 | X|| X || 0x20 | 00 | | X | X || NoSymbol | X | X| X ||| 0xa0 | (empty) X | X|| X || | (no event on Xev???) X | | X | X || NoSymbol | X | X| X | X || | (no event on Xev???) So. IIUC, the problem is having naked Space emit the same XLookupString that Control+Space, right? The new behavior is emitting lookup string "00" with modifier Control, so I guess this is the fix. So, what about simply changing the original map to have a different lookup string on Control? Like this: Shift* | Control* | Level3 || keysym| XLookupString ---||-- | ||| 0x20 | 20 X | ||| 0x20 | 20 | X||| 0x20 | 00 | | X || 0x20 | 20 X | X||| 0x100202f | e2 80 af X | | X || 0xa0 | c2 a0 | X| X || NoSymbol | X | X| X || NoSymbol | Or, if we don't want to have anything useful using Control, what about moving 0x100202f to Level3? Like this: Shift* | Control* | Level3 || keysym| XLookupString ---||-- | ||| 0x20 | 20 X | ||| 0x20 | 20 | X||| 0x20 | 00 | | X || 0x100202f | e2 80 af X | X||| 0x20 | 00 X | | X || 0xa0 | c2 a0 | X| X || NoSymbol | X | X| X || NoSymbol | Alternatively, the mapping of ControlR to Level5 could be an option (or a slightly different variant, whatever's better). Anything that could prevent me from manually editing my map to have ControlR again would be totally great. -- Y
[Bug 221112]
(In reply to comment #45) > (In reply to comment #44) > > Until a solution is to be found, could 518c769d be reverted for now? > > Breaking the very standard behavior of right control > > It does not break the very standard behavior of right control any more than > altrgr breaks the very standard behavior of right alt For me it does. My keyboard has an "Alt Gr" label on the AltR key, so it indeed is expected to behave differently from Alt_L, but my ControlR key is labeled as "Ctrl", just like the ControlL key. And all other keyboards and OSes I ever used did handle ControlR the same as ControlL, as far as I was concerned as a user. Also, I find it more generically problematic to change the behavior of a common key on a widely used keymap. For example the change annoyed me for about a month before I took the time to debug this and edit my keymap -- and I can't imagine what a lambda user could do but learn to deal with it. Also, what is Level5 used for? IIUC, currently nothing but short-nbsp (or at least that I can find, which is practically the same from a user POV), turning Ctrl_R into a virtually useless key. So, what can we do? First, please note, for what is worth, that both Rhythmbox and Totem, which were cited as the applications having a problem with the previous state of things, are not affected anymore. Rhythmbox don't use Control+Space as a shortcut anymore, and Totem seem to react to any space keysym, no matter the modifiers. So, unless there actually are other applications using Control+Space and suffering of the issue (Code::Blocks?), the problem does not even exist anymore. Also, maybe I just don't know how one is supposed to process the events, but those bugs look like an application or toolkit issue to me, is it? Then, practical changes. Before the change, Space behaved like this: Shift* | Control* | Level3 || keysym| XLookupString ---||-- | ||| 0x20 | 20 X | ||| 0x20 | 20 | X||| 0x20 | 20 | | X || 0x20 | 20 X | X||| 0x100202f | e2 80 af X | | X || 0xa0 | c2 a0 | X| X || NoSymbol | X | X| X || NoSymbol | And now we have: Shift* | ControlL | Level3 | Level5 || keysym| XLookupString ||- | |||| 0x20 | 20 X | |||| 0x20 | 20 | X|||| 0x20 | 00 | | X ||| 0x20 | 20 | || X || 0x20 | 20 X | X|||| 0x20 | 00 X | | X ||| 0xa0 | c2 a0 X | || X || 0x100202f | e2 80 af | X| X ||| 0x20 | 00 | X|| X || 0x20 | 00 | | X | X || NoSymbol | X | X| X ||| 0xa0 | (empty) X | X|| X || | (no event on Xev???) X | | X | X || NoSymbol | X | X| X | X || | (no event on Xev???) So. IIUC, the problem is having naked Space emit the same XLookupString that Control+Space, right? The new behavior is emitting lookup string "00" with modifier Control, so I guess this is the fix. So, what about simply changing the original map to have a different lookup string on Control? Like this: Shift* | Control* | Level3 || keysym| XLookupString ---||-- | ||| 0x20 | 20 X | ||| 0x20 | 20 | X||| 0x20 | 00 | | X || 0x20 | 20 X | X||| 0x100202f | e2 80 af X | | X || 0xa0 | c2 a0 | X| X || NoSymbol | X | X| X || NoSymbol | Or, if we don't want to have anything useful using Control, what about moving 0x100202f to Level3? Like this: Shift* | Control* | Level3 || keysym| XLookupString ---||-- | ||| 0x20 | 20 X | ||| 0x20 | 20 | X||| 0x20 | 00 | | X || 0x100202f | e2 80 af X | X||| 0x20 | 00 X | | X || 0xa0 | c2 a0 | X| X || NoSymbol | X | X| X || NoSymbol | Alternatively, the mapping of ControlR to Level5 could be an option (or a slightly different variant, whatever's better). Anything that could prevent me from manually editing my map to have ControlR again would be totally great. -- Y
[Bug 1253129] Re: Geany floods the terminal with tagmanager errors when using the "source" keyword in R
OK, indeed. This is a bug in the R symbol parser that should now be fixed with commit http://git.geany.org/geany/commit/?id=10893c4ada3be907a97dd4e472de029442e687bc BTW, it only happens if `source()` has an argument, without it doesn't trigger. Thanks for the report. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1253129 Title: Geany floods the terminal with tagmanager errors when using the "source" keyword in R To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geany/+bug/1253129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1066018] Re: speed on large file
Hi, You probably upgraded from pre-0.21 to 0.21 or newer. 0.21 introduced "real-time" tag parsing, which makes it possible to have an up-to-date symbols tree without having to save the file. The PHP parser is probably too slow on your 5000 lines file, so you see the lags every time the reparsing kicks on. You can change how often (and if) the reparsing happens, see Edit→Preferences→Editor→Completions→Symbol list update frequency. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1066018 Title: speed on large file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geany/+bug/1066018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1066018] Re: speed on large file
Le 13/10/2012 21:26, Okonkole a écrit : > How do i delete this entry ? As the popup and the manual says, set it to 0 to entirely disable real-time updates. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1066018 Title: speed on large file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geany/+bug/1066018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1066018] Re: speed on large file
Oh, my bad, you probably were speaking about the report. I don't know but you probably can't remove it, and it's fine to have it around closed as invalid in case somebody else has the same problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1066018 Title: speed on large file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geany/+bug/1066018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1072445] Re: geany crash when selecting shift up-down
Could you please provide a backtrace of the crash? (e.g. using GDB) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1072445 Title: geany crash when selecting shift up-down To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geany/+bug/1072445/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1072445] Re: geany crash when selecting with shift up-down
OK, I see. It's a typo in the Turkish translation that improperly translates "%dL" to "%sS" (%d being a c-format here, expecting a digit, but %s is the format for a string -- thus, a digit is read like it was a string, leading to the crash). Fixed upstream, and patch attached. In the meanwhile, you can either run Geany with another language (e.g. `LANG=C geany`), or rebuild your translation file tourself using the upstream fixed tr.po (`msgfmt tr.po -o /usr/share/locale/tr/LC_MESSAGES/geany.mo` using http://git.geany.org/geany/tree/po/tr.po). ** Patch added: "Fix a c-format typo in the Turkish translation leading to a crash" https://bugs.launchpad.net/ubuntu/+source/geany/+bug/1072445/+attachment/3419165/+files/0001-Fix-a-c-format-typo-in-the-Turkish-translation-leadi.patch ** Summary changed: - geany crash when selecting with shift up-down + geany crashes when selecting wholes lines with Turkish locale -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1072445 Title: geany crashes when selecting wholes lines with Turkish locale To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geany/+bug/1072445/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1072445] Re: geany crashes when selecting whole lines with Turkish locale
** Summary changed: - geany crashes when selecting wholes lines with Turkish locale + geany crashes when selecting whole lines with Turkish locale -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1072445 Title: geany crashes when selecting whole lines with Turkish locale To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geany/+bug/1072445/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1007205] Re: Geany often crashes when closing last tab by a middle click
I'm afraid I can't reproduce this neither on Ubuntu 12.04 nor under Debian nor Fedora. Have you some Geany plugins enabled? If yes, which ones? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1007205 Title: Geany often crashes when closing last tab by a middle click To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geany/+bug/1007205/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1036096] Re: geany crashed with SIGABRT in g_assertion_message()
'Assertion "r == n_visible_rows" failed' in GTK, that good ol' GTK bug :) Anyway it's not Geany's fault, and a workaround for such GTK bugs was introduced in Geany 0.21 (released 2011-10-02). See upstream reports: https://sourceforge.net/tracker/?func=detail&aid=3311258&group_id=153444&atid=787791 https://sourceforge.net/tracker/?func=detail&aid=3304273&group_id=153444&atid=787791 https://sourceforge.net/tracker/?func=detail&aid=3201050&group_id=153444&atid=787791 https://sourceforge.net/tracker/?func=detail&aid=3163742&group_id=153444&atid=787791 https://sourceforge.net/tracker/?func=detail&aid=3153120&group_id=153444&atid=787791 https://sourceforge.net/tracker/?func=detail&aid=2985896&group_id=153444&atid=787791 ** Bug watch added: SourceForge.net Tracker #3311258 http://sourceforge.net/support/tracker.php?aid=3311258 ** Bug watch added: SourceForge.net Tracker #3304273 http://sourceforge.net/support/tracker.php?aid=3304273 ** Bug watch added: SourceForge.net Tracker #3201050 http://sourceforge.net/support/tracker.php?aid=3201050 ** Bug watch added: SourceForge.net Tracker #3163742 http://sourceforge.net/support/tracker.php?aid=3163742 ** Bug watch added: SourceForge.net Tracker #3153120 http://sourceforge.net/support/tracker.php?aid=3153120 ** Bug watch added: SourceForge.net Tracker #2985896 http://sourceforge.net/support/tracker.php?aid=2985896 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1036096 Title: geany crashed with SIGABRT in g_assertion_message() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geany/+bug/1036096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1176612] Re: Feature Idea: Delete Void Lines
I'm afraid I don't see the use case for such a feature, in source code formatting blank lines often are important for readability. So, this probably won't be added in Geany core, maybe a plugin. However, note that using the Custom Command feature you can quite easily implement the feature using grep: grep -v '^[ \t]*$' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1176612 Title: Feature Idea: Delete Void Lines To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geany/+bug/1176612/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1076934] Re: Duplicated menu items
Those are not duplicates, but the item's label is wrong. Looks like a Unity/dbusmenu bug where it shows the label associated with the stock icon rather than the proper label itself… Anyway, I doubt it's a Geany bug, especially if it appeared after a upgrade of Unity or dbusmenu update. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1076934 Title: Duplicated menu items To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geany/+bug/1076934/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 965715] Re: File open in geany and other editors fails over ssh mount
The reporter said: > I've tried all sorts of different editors So I guess Geany isn't the only application suffering from the bug? This said, note that Geany *does not* handle remotes locations by itself, and thus requires gvfs-fuse to be installed and running for such locations to work. This makes me think that it's not a bug in Geany, but rather one in gvfs-fuse, or simply a lack of gvfs-fuse in reporter's machine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/965715 Title: File open in geany and other editors fails over ssh mount To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geany/+bug/965715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 948321] [NEW] -e (execute) option mishanldes spaces
Public bug reported: The -e option of Konsole has a very strange behavior if one of the first argument has a space in it. Actually, everything after the space is simply ignored: $ konsole -e "/bin/sh somescript" executes "/bin/sh" $ konsole -e "/bin/some program with spaces" tries to execute "/bin/some" $ konsole -e "/bin/some\ program\ with\ spaces" tries to execute "/bin/some program with spaces" This behavior doesn't follow XTerm (and other) behavior and seems simply wrong. I would've expected either 1) execute as a shell-formed command, so splitting at spaces and passing extra arguments to the command, or 2) execute the argument, e.g. with the spaces This makes it hard to use konsole as a random terminal emulator from a script or application, e.g. when mapped to x-terminal-emulator. For example, LP:#282972 made the Geany editor use "x-terminal-emulator" as its terminal emulator, but broke Geany under KDE because it tries to run "'x-terminal-emulator' '-e' '/bin/sh somescript'", and then Konsole simply runs "/bin/sh". Ubuntu version: 11.10 Konsole version: 4:4.7.1-0ubuntu2 ** Affects: konsole (Ubuntu) Importance: Undecided Status: New ** Description changed: The -e option of Konsole has a very strange behavior if one of the first argument has a space in it. Actually, everything after the space is simply ignored: $ konsole -e "/bin/sh somescript" executes "/bin/sh" $ konsole -e "/bin/some program with spaces" tries to execute "/bin/some" $ konsole -e "/bin/some\ program\ with\ spaces" tries to execute "/bin/some program with spaces" This behavior doesn't follow XTerm (and other) behavior and seems simply wrong. I would've expected either 1) execute as a shell-formed command, so splitting at spaces and passing extra arguments to the command, or 2) execute the argument, e.g. with the spaces This makes it hard to use konsole as a random terminal emulator from a script or application, e.g. when mapped to x-terminal-emulator. For - example, #282972 made the Geany editor use "x-terminal-emulator" as its - terminal emulator, but broke Geany under KDE because it tries to run "'x - -terminal-emulator' '-e' '/bin/sh somescript'", and then Konsole simply - runs "/bin/sh". - + example, LP:#282972 made the Geany editor use "x-terminal-emulator" as + its terminal emulator, but broke Geany under KDE because it tries to run + "'x-terminal-emulator' '-e' '/bin/sh somescript'", and then Konsole + simply runs "/bin/sh". Ubuntu version: 11.10 Konsole version: 4:4.7.1-0ubuntu2 -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to konsole in Ubuntu. https://bugs.launchpad.net/bugs/948321 Title: -e (execute) option mishanldes spaces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/konsole/+bug/948321/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 282972] Re: 'xterm' should be 'x-terminal-emulator' to be consistent with the desktop
Please note that this breaks under Kubuntu/KDE because Konsole has a strange way of handling the -e argument (see https://bugs.launchpad.net/ubuntu/+source/konsole/+bug/948321) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/282972 Title: 'xterm' should be 'x-terminal-emulator' to be consistent with the desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geany/+bug/282972/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 949623] Re: wrong directory/folder location in terminal of Geany
Geany can follow the path of the current document in the terminal, see "Preferences->Terminal->Follow path of the current file". I think it should address your issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/949623 Title: wrong directory/folder location in terminal of Geany To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geany/+bug/949623/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 750588] [NEW] Geany's "New with template" submenu missing
Public bug reported: Binary package hint: appmenu-gtk Geany's sub-menu of the "New (with Template)" file menu item is missing when using appmenu-gtk (the default in 11.04). This is because Geany shares the submenu between the menubar and the toolbar. It reparents it to the menu item when this one is shown, and put it back to the toolbar when hidden. However, appmenu-gtk don't seem to export these signals, so don't allowing Geany to do the proper reparenting, thus never showing the submenu of the menu item. appmenu-gtk: 0.2.0-0ubuntu1 geany: 0.20-0ubuntu2 (also applies to upstream SVN) ** Affects: appmenu-gtk (Ubuntu) Importance: Undecided Status: New ** Tags: geany -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/750588 Title: Geany's "New with template" submenu missing -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 744874] Re: geany crashed with SIGSEGV in g_cclosure_marshal_VOID__OBJECT()
*** This bug is a duplicate of bug 741658 *** https://bugs.launchpad.net/bugs/741658 ** This bug has been marked a duplicate of bug 741658 geany crashed with SIGSEGV in g_closure_invoke() * You can subscribe to bug 741658 by following this link: https://bugs.launchpad.net/ubuntu/+source/geany/+bug/741658/+subscribe -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/744874 Title: geany crashed with SIGSEGV in g_cclosure_marshal_VOID__OBJECT() -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 750588] Re: Geany's "New with template" submenu missing
Hi, I just built and installed dbusmenu from bazaar trunk (>= 0.4.2), and now the submenu appears correctly in Geany. However, the items in the submenu doesn't work when it is attached to the menubar (and strangely make the menubar flicker when getting activated). So it's only a partial fix for now, sorry. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/750588 Title: Geany's "New with template" submenu missing -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 750588] Re: Geany's "New with template" submenu missing
The branch sudo-make-me-an-activation-sandwich (nice name BTW :D) seems to work fine :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/750588 Title: Geany's "New with template" submenu missing -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
