[Bug 1987159] Re: Drop VNC support from GNOME Remote Desktop in Kinetic
> I am struggling to find any use cases where GNOME's VNC should be preferred to RDP. 1) Teacher screen broadcasting to students. There, a shared VNC session is much easier to setup and performs better than separate RDP sessions. Additionally, encrypting e.g. 10 RDP streams comes with significant CPU strain, which is unnecessary in this use case. 2) The remote support use case. To help a remote user behind NAT, I only need to ask them to run `x11vnc -connect my-ip`. On my side, `vncviewer -listen` accepts the request for help. GNOME VNC could easily support that. But there's no `xfreerdp -listen` option in the RDP protocol. So in the RDP solution, the very frequent and significant "remote support" use case is completely ignored and we need to switch to teamviewer or anydesk instead. It's understandable though that if upstream GNOME neglects VNC, downstream Ubuntu will also do the same. And such decisions are why there's a growing list of users that can't use GNOME at all anymore... -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1987159 Title: Drop VNC support from GNOME Remote Desktop in Kinetic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1987159/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1922414] Re: ssh-agent fails to start (has_option: command not found)
I also see it on Ubuntu MATE Jammy. Will the fix come from Xorg, or should we add LightDM to the affected projects list? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1922414 Title: ssh-agent fails to start (has_option: command not found) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1922414/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 206924] Re: Make it possible to create a guest account
** No longer affects: ltsp -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/206924 Title: Make it possible to create a guest account To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/206924/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1762952] Re: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default
Hi, this fix caused a regression in ubiquity: LP: #1892014 Ubiquity doesn't put alt_shift_toggle in XKBOPTIONS anymore, so we cannot switch to e.g. Greek using Alt+Shift, after going through a normal installation (or even in the live session). Are users expected to manually run `dpkg-reconfigure keyboard- configuration` right after a GUI installation of Ubuntu? E.g. ubuntu-mate-18.04.2-desktop-amd64.iso is affected while 18.04.1 isn't. Should this issue be resolved in console-setup or in ubiquity? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1762952 Title: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1762952/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1869716] Re: Removing libpango1.0-0 broke Minecraft Launcher
Anydesk too. Thanks for the fix! :) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1869716 Title: Removing libpango1.0-0 broke Minecraft Launcher To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1869716/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1861481] Re: language-options causes live CD sessions to be untranslated
The reason that this regression doesn't affect ubuntu-desktop, might be that unlike LightDM, GDM doesn't have that Ubuntu-specific patch to use /usr/share/language-tools/language-options. So, I subscribed "lightdm (Ubuntu)" to the affected packages, in case we just want to drop the Ubuntu-specific patch, and that way make lightdm not pass LANGUAGE when it shouldn't. I think that this won't address the source of the regression, but it will make the problem not appear in flavors that use lightdm which should be good enough. ** Also affects: lightdm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1861481 Title: language-options causes live CD sessions to be untranslated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1861481/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1861481] [NEW] language-options causes live CD sessions to be untranslated
Public bug reported: Since Ubuntu 19.10, for all Ubuntu live CDs that use LightDM (e.g. MATE and Xubuntu), if a user selects a language in syslinux other than those with an included langpack, the session is then untranslated. For example, if one boots Ubuntu MATE 20.04 and selects Greek in syslinux, he ends up with LANGUAGE=en in the session. The chain of events is: LightDM has an Ubuntu-specific patch that makes it call /usr/share/language-tools/language-options instead of the upstream `locale -a`. `locale -a` does list el_GR as a supported locale because casper correctly updated the locales. But language-options doesn't list el_GR, so it fools LightDM into thinking that Greek aren't supported; while they're all there, since e.g. MATE doesn't rely on langpacks; mate-panel.mo and mate-calc.mo etc are all there. I believe the correct fix would be for language-options to list el_GR on live CDs (to merge the output of locale -a in its output). Thanks! ** Affects: accountsservice (Ubuntu) Importance: High Status: New ** Tags: rls-ff-incoming -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1861481 Title: language-options causes live CD sessions to be untranslated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1861481/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 388547]
This issue got *much* worse recently, it now affects keyboard layout switching as well, so many applications like tuxpaint became completely unusable. Example: In Ubuntu 14.04, I run `tuxpaint --fullscreen`. I press Win+Space, the Gnome-defined method to switch my keyboard layout from "us,gr" to "gr,us". unity-settings-daemon cannot read the layout change because tuxpaint has the keyboard grab. (It's the same in other distros too, it's not Ubuntu specific) So I can't type Greek with the tuxpaint Text tool, making tuxpaint completely useless in fullscreen mode. Until some years ago, Gnome allowed XKB to manage the layout switching, which worked fine even in fullscreen applications. It no longer allows it, they try to manage it with gnome-settings-daemon etc. If there's no intention to fix this in Xorg, please mention it here, so that we can show that response to Gnome developers and tell them to let XKB manage the keyboard layouts instead. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/388547 Title: Volume keys don't work inside a full-screen game To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/388547/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767765] [NEW] Clicking on fcitx applet hangs Ubuntu MATE
Public bug reported: Method to reproduce in 1 minute: 1) Download the Ubuntu MATE 18.04 live CD. 2) Press space while booting to display the syslinux language menu. Select Ελληνικά (Greek) in order for fcitx to autorun. I guess the same will happen in other languages too. 3) Select Δοκιμάστε το Ubuntu MATE χωρίς εγκατάσταση (Try Ubuntu MATE without installing). 4) When the live session becomes available, the following applets show: en [keyboard icon] ... At that point, clicking on the keyboard icon causes no issues. 5) Open anything that displays a cursor, e.g. a terminal. Now the following applets show: en [keyboard icon] us It is a bug that the language is shown twice. But the main problem now is that if one clicks at the keyboard icon, an unpopulated (hanged) menu shows up, and the keyboard/mouse no longer work; no interaction with the desktop is possible. 6) If one presses Alt+Ctrl+F2 to switch to vt2, logs in with ubuntu-mate and empty pass, and types `killall fcitx`, and then presses Alt+Ctrl+F7 to switch back to vt7, the UI is unfrozen and works properly. ** Affects: fcitx (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to fcitx in Ubuntu. https://bugs.launchpad.net/bugs/1767765 Title: Clicking on fcitx applet hangs Ubuntu MATE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fcitx/+bug/1767765/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1739732] [NEW] Can't switch to Greek in Ubiquity when fcitx is running
Public bug reported: I boot with the current Ubuntu MATE 18.04 daily live CD. I select Greek on syslinux, "Try Ubuntu before installing", and I start the Ubiquity installer. At the step where I'm supposed to type my full name, for example "Διαχειριστής" (administrator), I can't switch my keyboard layout to Greek. Neither Alt+Shift nor the panel applet allow me to switch. Note that there are 2 panel applets, MATE's and fcitx's, and both have entries for Greek and English, but when I click on Greek, nothing happens. If I switch to any other application, like e.g. mate-terminal, I can properly switch to Greek. But, if I go back to Ubiquity, I automatically get switched back to English. If I exit fcitx from the panel, then everything works fine in Ubiquity as well. If I rerun fcitx, the problem starts again, so it's completely reproducible. Btw, is fcitx supposed to be running in the Greek locale? Or is this an additional issue with im-config? And is it normal to have 2 applets for keyboard layout selection?! ** Affects: fcitx (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to fcitx in Ubuntu. https://bugs.launchpad.net/bugs/1739732 Title: Can't switch to Greek in Ubiquity when fcitx is running To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fcitx/+bug/1739732/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1605571] [NEW] apt install --no-install-recommends fcitx-bin, breaks dead keys
Public bug reported: Test case: remove everything related to fcitx. Then run: apt install --no-install-recommends fcitx-bin Then login with some locale that uses dead keys, for example the Greek locale. Then type e.g. ";"+"a". It's supposed to show "ά", but instead it shows "´α". At that point, fcitx isn't running, yet `im-config -a` reports that it's the selected input method. $ env | egrep '_IM|XMOD' CLUTTER_IM_MODULE=xim QT_IM_MODULE=xim XMODIFIERS=@im=fcitx QT4_IM_MODULE=xim GTK_IM_MODULE=xim If fcitx-bin is installed along with all its recommended dependencies, then fcitx is running normally and the issue described above doesn't occur anymore. At that point, the environment variables are: $ env | egrep '_IM|XMOD' CLUTTER_IM_MODULE=xim QT_IM_MODULE=fcitx XMODIFIERS=@im=fcitx QT4_IM_MODULE=fcitx GTK_IM_MODULE=fcitx At present I've only tested with the MATE desktop environment. It also happens with the MATE live CD, as fcitx-bin is indeed preinstalled there without its recommended dependencies. ** Affects: fcitx (Ubuntu) Importance: Undecided Status: New ** Affects: ubuntu-mate-meta (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-mate-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to fcitx in Ubuntu. https://bugs.launchpad.net/bugs/1605571 Title: apt install --no-install-recommends fcitx-bin, breaks dead keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fcitx/+bug/1605571/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1566157] Re: Metacity's compositing is too slow
I just tried it and it indeed solves the performance issues: Old version 1:3.18.3-1ubuntu3: $ vblank_mode=0 glxgears 27418 frames in 5.0 seconds = 5483.539 FPS New version 1:3.18.4-0ubuntu0.1: $ vblank_mode=0 glxgears 39851 frames in 5.0 seconds = 7970.179 FPS ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1566157 Title: Metacity's compositing is too slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1566157/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1487679] Re: Breaking ordering cycle by deleting job nbd-client.service/start
** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1487679 Title: Breaking ordering cycle by deleting job nbd-client.service/start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nbd/+bug/1487679/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1512002] Re: Annoying dialog "Authentication is required to change your own user data"
@seb128, thanks for releasing the fix, but it appears that not all the patch from comment #36 was applied: - auth_self - auth_self + yes + yes is still "auth_self" in accountsservice 0.6.40-2ubuntu10, and I think that it takes priority over , so the problem still persists and can be reproduced as described in comment #36. Could you please re-release the fix while applying the whole patch? Thank you! ** Changed in: accountsservice (Ubuntu) Status: Fix Released => Triaged ** Changed in: accountsservice (Ubuntu) Assignee: (unassigned) => Sebastien Bacher (seb128) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1512002 Title: Annoying dialog "Authentication is required to change your own user data" To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/1512002/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1566157] Re: Metacity's compositing is too slow
Yup, I'm using your 1:3.18.3+git20160418-1ubuntu3 metacity many hours per day on my main work PC. i386, Xenial, Core i5-4440 @ 3.10 GHz, 8 GB RAM. I haven't seen any regressions so far, and I cannot even reproduce the issue Dmitry reported; although I've seen some recent commits of yours that might have solved it... -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1566157 Title: Metacity's compositing is too slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1566157/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1566157] Re: Metacity's compositing is too slow
Thank you Alberts, yup that indeed increased the performance a lot: xenial-metacity --no-composite: 30407 frames in 5.0 seconds = 6081.219 FPS ppa-metacity --no-composite: 37147 frames in 5.0 seconds = 7429.385 FPS marco --no-composite: 37146 frames in 5.0 seconds = 7429.081 FPS Alberts, Dmitry, please also note that Ubuntu now allows publishing upstream microreleases: https://wiki.ubuntu.com/StableReleaseUpdates#New_upstream_microreleases For example, for LTSP, I plan on maintaining a branch with bug fixes only, and I'll be SRUing it regularly to 16.04, without having to go through the bureaucracy of filing one SRU for each bug fix separately. Maybe something similar could be done for flashback? :) In any case, thanks a lot, you guys are awesome! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1566157 Title: Metacity's compositing is too slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1566157/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1566157] Re: Metacity's compositing is too slow
Alberts I'm mostly using i386 installations so I could only test amd64 in a VM. I did saw a performance improvement there, but it wasn't as big as in the real hardware case... -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1566157 Title: Metacity's compositing is too slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1566157/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1566157] Re: Metacity's compositing is too slow
I'm having a hard time applying all the last e.g. 20 upstream commits to the Xenial tree. @Dmitry, since you'll be merging the upstream with the Ubuntu tree anyway in order to test it youself, would it be possible to push the result somewhere, e.g. in launchpad, or publish a .deb in a PPA, so that it's easier for me to test it? In general, it'd be nice to have a launchpad recipe that builds upstream gnome-flashback + ubuntu packaging to some PPA, so that we can test things more easily. E.g. this is what I have for testing LTSP upstream: https://code.launchpad.net/~alkisg/+recipe/ltsp-daily -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1566157 Title: Metacity's compositing is too slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1566157/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1566157] Re: Metacity's compositing is too slow
> only when the windows repainted themselves they started to become visible. I've seen that in the past about 5 times in the last 2 years. I don't remember which LTS gnome-flashback version I was using. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1566157 Title: Metacity's compositing is too slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1566157/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1566157] Re: Metacity's compositing is too slow
Alberts, I'm sorry, the (new) client that I tested with is giving me very inconsistent results, even by just rebooting it, and I'm not going to use it in benchmarks again in the future. It's a 3-year-old AMD-based laptop; maybe the problem is in the radeon driver or in its power states, anyway, please ignore my results in comment #11. I tested again with the client from comment #7 (an old intel 8xx based laptop), and I reproduced what you said, i.e. that your patches indeed made metacity fast again: no-wm: 481.234 compiz: 473.248 xenial-metacity --no-composite: 294.148 xenial-metacity --composite: 177.516 fixed-metacity --no-composite: 470.791 fixed-metacity --composite: 283.285 marco --no-composite: 471.382 marco --composite: 286.939 xcompmgr: 291.370 I also confirmed the performance increase in the i5 desktop from comment #5. @Alberts, thank you very much, you're awesome! @Dmitry, could we please get those patches in Xenial? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1566157 Title: Metacity's compositing is too slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1566157/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1566157] Re: Metacity's compositing is too slow
Hi Alberts, I tried applying the latest 13 commits from the test-3-18 branch on top of Xenial's metacity. If my benchmarks were correct, it made things even slower. glmark2 score: xenial-metacity --no-composite: 311 test-3-18-metacity --no-composite: 154 xenial-marco --no-composite: 902 I.e. now it's 6 times, rather than 3 times, slower than marco... Can we use marco instead? Doesn't it additionally have CSD support? Or, could end users of gnome-flashback-session decide to install and use marco instead of metacity without bumping into major issues? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1566157 Title: Metacity's compositing is too slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1566157/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 221363] Re: Policy Kit Unlock Buttons Greyed Out when using NX / VNC / LTSP
Since noone has answered for 4 months, and since some related commits have been made, I'm marking it fix released in LTSP. ** Changed in: ltsp (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to system-tools-backends in Ubuntu. https://bugs.launchpad.net/bugs/221363 Title: Policy Kit Unlock Buttons Greyed Out when using NX / VNC / LTSP To manage notifications about this bug go to: https://bugs.launchpad.net/freenx-server/+bug/221363/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1512002] Re: Annoying dialog "Authentication is required to change your own user data"
** Bug watch added: freedesktop.org Bugzilla #94895 https://bugs.freedesktop.org/show_bug.cgi?id=94895 ** Also affects: accountsservice via https://bugs.freedesktop.org/show_bug.cgi?id=94895 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1512002 Title: Annoying dialog "Authentication is required to change your own user data" To manage notifications about this bug go to: https://bugs.launchpad.net/accountsservice/+bug/1512002/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1566157] Re: Metacity's compositing is too slow
To sum up, two problems: 1) `metacity (and marco) --composite` in 12.04 and 14.04 had only 60% of the compiz performance. 2) `metacity` (both composite and no-composite) got a lot slower in 16.04, at 60% and 25% respectively of the compiz performance. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1566157 Title: Metacity's compositing is too slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1566157/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1566157] Re: Metacity's compositing is too slow
> Any chance that you could track down version when it started to be slow? > Was composite already slow in previous LTS? Initial tests show that metacity had about the same performance as marco in 12.04 and in 14.04. In those versions, `metacity (or marco) --composite` performs only about 60% as well as `metacity --no-composite`, while `compiz` performs about the same as `metacity --no-composite`. glxgears example: no-wm: 394.117 compiz: 393.603 metacity --no-composite: 403.858 metacity --composite: 239.124 marco --no-composite: 404.455 marco --composite: 242.672 Unfortunately in 16.04 it got a whole lot worse, for example: no-wm: 469.506 compiz: 467.071 metacity --no-composite: 277.188 metacity --composite: 122.936 marco --no-composite: 464.281 marco --composite: 287.314 xcompmgr: 291.990 Now `marco --composite` is still at 60%, while `metacity --composite` is now at only 25% of the optimal performance. But note that `metacity --no-composite` is also a whole lot worse than `marco --no-composite`. Alberts do you want me to try with non-LTS releases as well? These tests were made by running a plain `xinit` (which gives a simple xterm) on top of a usual Ubuntu gnome-flashback installation, while also installing marco there. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1566157 Title: Metacity's compositing is too slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1566157/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1512002] Re: Annoying dialog "Authentication is required to change your own user data"
mterry, charlesk, I took the liberty of subscribing you because I think it involves this commit: https://code.launchpad.net/~mterry/indicator-messages/tell-accounts-services/+merge/93290 The issue is happening to me as well, on Ubuntu 16.04 gnome-flashback, in 2 cases: 1) sometimes when I try to unlock the screensaver, 2) sometimes when I login via ltsp thin/fat clients. I think the problem is the one mentioned by khadgaray in https://bugs.launchpad.net/ubuntu/+source/indicator- messages/+bug/1192300. I.e. that the system is trying to notify us if we have new mails etc, and that for some reason(s) it's considering us an "inactive user" (inactive means not in the active screen of the pc, either remote or in a screensaver etc) and thus we need authentication. The necessary rights are defined in this file: /usr/share/polkit-1/actions/org.freedesktop.accounts.policy ... auth_self auth_self yes ... I think that if we change "auth_self" to "yes", we'll have a temporary workaround to the problem. But the real issue is, should the system consider us "inactive" in the screen saver? Should it consider us inactive in ltsp thin clients that are remote sessions? Should it consider us inactive in ltsp fat clients where accountsservice doesn't have information about the remote user account? (similar with ldap) If the answer to the above is yes, then maybe the workaround that I mentioned above should be committed to accountsservice? ** Also affects: accountsservice (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1512002 Title: Annoying dialog "Authentication is required to change your own user data" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1512002/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1566157] Re: Metacity's compositing is too slow
Yet another benchmark, glmark2, in a very recent core i5 client. Scores: No WM: 2058 marco --no-composite: 1894 compiz : 1878 metacity --no-composite: 742 xcompmgr: 716 marco --composite: 708 metacity --composite: 441 In an ideal world, gnome-flashback would support compiz first, then `metacity --no-composite` but with the speed of `marco --no-composite`. They're 4-5 times faster than the proposed `metacity --composite`!!! /me will definitely ask the Mate people if they still support `marco --no-composite`... ** Attachment added: "glmark2.zip" https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1566157/+attachment/4628575/+files/glmark2.zip -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1566157 Title: Metacity's compositing is too slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1566157/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1565640] Re: Set compositing-manager=false by default
> Probably way easier is to document, to execute in terminal: > gsettings set org.gnome.metacity compositing-manager false It's easy for one sysadmin to run a few commands in a terminal. It's not easy for hundreds of students, e.g. 5-10 years old, to run a few commands in a terminal. Sysadmins (or packagers) can provide a system-wide override with /usr/share/glib-2.0/schemas/20_metacity.override but that will only work with new users. They can provide overrides for all users with mandatory gsettings. But the /usr/local/bin/metacity wrapper can have logic to active or deactivate compositing per user, or per machine, based on the CPU, the graphics card etc etc, and it's very easy to integrate it with LTSP. Anyway that part isn't important; the most important thing is if the non-compositing case will be a supported use case in Ubuntu gnome-flashback 16.04 or not. I'll do some more benchmarks with gnome-flashback and with other DEs like Mate/XFCE/LXDE. Thank you guys! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1565640 Title: Set compositing-manager=false by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1565640/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1565640] Re: Set compositing-manager=false by default
> @Alberts, I'll do some more tests and come up with hard numbers concerning the performance of metacity with or without compositing. I did some benchmarks and reported them in https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1566157 Now I'm more convinced that metacity's compositing-manager should be false by default. For LTSP users, I'll document how to create a /usr/local/bin/metacity wrapper that launches `metacity --no-composite`. Quoting my conclusions from that bug report: I really think that the user's choices would be: 1) compiz, for every PC that supports it, 2) metacity --no-composite, for any PC that doesn't support compiz and that isn't able to spare 50%-80% of their FPS, 3) metacity --composite, ONLY for the minority of the PCs with graphics cards that can't run compiz and with so awesome CPUs that can spare 50-80% of their FPS. If you can find an example of such a PC, please let me know, currently I don't know of any. I do know of thousands of examples in category (2) though. Since `metacity --composite` is so much slower, affecting all apps and actions from simple drawing to scrolling to moving around windows to watching videos to game playing etc, I'd like to again ask you to consider NOT making (3) the preferred session for gnome-flashback for 16.04. I.e. gnome-flashback-compiz could be the default (proposed one), and gnome-flashback-metacity the non composited version, with the --composite option only available as a gsetting for the minority of the people that would need it. Thanks! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1565640 Title: Set compositing-manager=false by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1565640/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1566157] Re: Metacity's compositing is too slow
Here's another benchmark, with an SDL 2D game, teeworlds, running full screen: no wm: 220 FPS metacity --no-composite: 220 metacity --composite: 130 compiz: 218 xcompmgr: 130 compton: 129 I really think that the user's choices would be: 1) compiz, for every PC that supports it, 2) metacity --no-composite, for any PC that doesn't support compiz and that isn't able to spare 50%-80% of their FPS, 3) metacity --composite, ONLY for the minority of the PCs with graphics cards that can't run compiz and with so awesome CPUs that can spare 50-80% of their FPS. If you can find an example of such a PC, please let me know, currently I don't know of any. I do know of thousands of examples in category (2) though. Since `metacity --composite` is so much slower, affecting all apps and actions from simple drawing to scrolling to moving around windows to watching videos to game playing etc, I'd like to again ask you to consider NOT making (3) the preferred session for gnome-flashback for 16.04. I.e. gnome-flashback-compiz could be the default (proposed one), and gnome-flashback-metacity the non composited version, with the --composite option only available as a gsetting for the minority of the people that would need it. Thanks! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1566157 Title: Metacity's compositing is too slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1566157/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1566157] Re: Metacity's compositing is too slow
And here are some numbers for glxgears again (on another pc), but with xcompmgr and compton included. The first column is the WM used, the second is the FPS for glxgears, and the third the FPS for glxgears -fullscreen: no wm 221 15 metacity --no-composite 170 15 metacity --composite83 7 compiz 225 15 xcompmgr122 7 compton 102 7 `metacity --composite` is again about 3 times slower than no-wm and compiz. With appropriate fixes, it should be able to reach at least the performance of xcompmgr, shouldn't it? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1566157 Title: Metacity's compositing is too slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1566157/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1566157] Re: Metacity's compositing is too slow
I run another set of benchmarks using x11perf. I don't know how much they can help in pinpointing the issue(s), but they do show that `metacity --composite` is extremely slower than `metacity --no-composite` or `compiz`. I'm attaching the output in LibreOffice Calc format, I think it's more readable that way. An example line from the attached .ods file: Test: 500x500 tiled rectangle (17x15 tile) no WM: 772 (100 %) metacity --no-composite: 699 (91%) metacity --composite: 233 (30 %) compiz: 688 (89 %) The numbers are the repetitions, and inside the parentheses are the normalized values, with 100% being the highest. The others are about 90% efficient, while `metacity --composite` is only 30% efficient, three times slower in that test. I can also create a similar .ods for gtkperf, if anyone thinks that it will somehow help. ** Attachment added: "x11perf.ods" https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1566157/+attachment/4624852/+files/x11perf.ods -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1566157 Title: Metacity's compositing is too slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1566157/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1566157] Re: Metacity's compositing is too slow
Ah, I forgot to include the results without a window manager as a comparison: $ killall metacity & sleep 5 && glxgears -fullscreen & sleep 20 && killall glxgears 44884 frames in 5.0 seconds = 8976.656 FPS 44905 frames in 5.0 seconds = 8980.993 FPS Normalized: 118 FPS, the fastest of all. $ killall metacity & sleep 5 && glxgears -fullscreen & sleep 20 && killall glxgears 1743 frames in 5.0 seconds = 348.422 FPS 1713 frames in 5.0 seconds = 342.471 FPS Normalized: 94 FPS, slower than compiz. That may be due to compiz not using the whole screen in glxgears -fullscreen; the drawing area didn't include the panels. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1566157 Title: Metacity's compositing is too slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1566157/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1566157] [NEW] Metacity's compositing is too slow
Public bug reported: I did the following benchmarks between `metacity --no-composite`, `metacity --composite`, and `compiz`, in Ubuntu 16.04. First, I disabled vsync: $ cat ~/.drirc Then I ran glxgears as follows: $ metacity --no-composite --replace & sleep 5 && glxgears & sleep 20 && killall glxgears 29564 frames in 5.0 seconds = 5912.721 FPS 29729 frames in 5.0 seconds = 5945.777 FPS $ metacity --composite --replace & sleep 5 && glxgears & sleep 20 && killall glxgears 10366 frames in 5.0 seconds = 2073.057 FPS 10194 frames in 5.0 seconds = 2038.702 FPS $ compiz --replace & sleep 5 && glxgears & sleep 20 && killall glxgears 37633 frames in 5.0 seconds = 7522.813 FPS 37990 frames in 5.0 seconds = 7597.965 FPS As a second set of benchmarks, I ran glxgears -fullscreen as follows: $ metacity --no-composite --replace & sleep 5 && glxgears -fullscreen & sleep 20 && killall glxgears 1652 frames in 5.0 seconds = 330.296 FPS 1667 frames in 5.0 seconds = 333.281 FPS $ metacity --composite --replace & sleep 5 && glxgears -fullscreen & sleep 20 && killall glxgears 886 frames in 5.0 seconds = 177.007 FPS 891 frames in 5.0 seconds = 178.099 FPS $ compiz --replace & sleep 5 && glxgears -fullscreen & sleep 20 && killall glxgears 1830 frames in 5.0 seconds = 365.868 FPS 1847 frames in 5.0 seconds = 369.242 FPS Normalized results (with compiz=100): Windowed: metacity --no-composite: 78 FPS metacity --composite: 27 FPS compiz: 100 FPS Full screen: metacity --no-composite: 90 FPS metacity --composite: 48 FPS compiz: 100 FPS So `metacity --composite` in this test was about 2 times slower than `metacity --no-composite` and about 3 times slower than `compiz`. This test was done an "Intel(R) Core(TM) i5-4440 CPU @ 3.10GHz" CPU, with the following embedded graphics card: $ lspci -nn -k | grep -A 2 VGA 00:02.0 VGA compatible controller [0300]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1458:d000] Kernel driver in use: i915 I'll upload more tests if I find anything newsworthy. ** Affects: metacity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1566157 Title: Metacity's compositing is too slow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1566157/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1565640] Re: Set compositing-manager=false by default
@Alberts, Dmitry: > No compositor means - no desktop window or it will be black - you will never > see background. > My plan is to fix this in Xenial+1. Less patches will mean less work for me, > too :P That's a good example, does that mean that in Ubuntu 16.10 if one doesn't use compositing he won't be seeing the desktop icons and background? @Alberts, which distro are you using or which one is closest with upstream flashback? Debian? > P.S. Do you have numbers about usage? I have somewhat exact numbers for Greece: http://www.ltsp.org/stories/widget-map/?location=Greece (less than half of the installations are shown in that map) 1000+ schools are using LTSP. They have on average one computer lab with 13 computers, serving 100 students. So 1000 installations, 13,000 computers, 100,000 users are using gnome-flashback 12.04 here. We didn't upgrade to 14.04 because of issues with the keyboard layout and the indicator. We'll upgrade them to 16.04 sometime this summer. They don't show up in the official stats much (popcon, ubuntu repository hits etc) because there's only one installation per school, the rest of the computers are netbooted from a single image. Worldwide I don't have exact numbers, the LTSP map is at http://ltsp.org/stories/ but I suspect there are 10 times more installations, but only half of them with gnome-flashback. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1565640 Title: Set compositing-manager=false by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1565640/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1565640] Re: Set compositing-manager=false by default
@Alberts, I'll do some more tests and come up with hard numbers concerning the performance of metacity with or without compositing. I do believe that in some cases it will be possible to optimize the performance through appropriate bug reports and patches; but I also strongly believe that there will be other cases where the different design choices (compositing) will come with an unavoidable performance hit. And while e.g. "3 times slower" may be acceptable in new e.g. core i5 systems, it's not acceptable in new e.g. atom systems. It doesn't affect only old PCs or networked X, it's just that it's more visible there. @Dmitry and Alberts, what if LTSP users find it necessary to have compositing off by default? (as a local setting in their installations) What issues should they expect from gnome-flashback then? - Harder window resizing due to 1 px border. - Notify-osd notifications ==> I did a quick test and they seem to work; albeit without transparency. Did I miss something? - Decorations ==> Example? I couldn't reproduce it. - Various docks ==> Example? And more significant, how much support should they expect from gnome-flashback developers for the non-compositing case? For example, your support in all the bug reports that I've filed so far was excellent! Does that mean that you won't be willing to do any non-compositing related work at all? Would you be willing to guide persons that are interested in working on such issues? Or to accept patches from them? I understand that gnome-flashback isn't specifically targeting old or networked clients, but does that also mean that it doesn't care at all about that use case? If that's the verdict, then maybe LTSP should evaluate other desktop environments like Mate as the default (I think "marco" defaults to non-compositing in 16.04). No matter the answer(s), I again want to thank you very much guys for all your work! :) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in Ubuntu. https://bugs.launchpad.net/bugs/1565640 Title: Set compositing-manager=false by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1565640/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1551283] Re: ibus/im-config in Ubuntu GNOME
> ... I'll try to raise the issue in Debian's im-config, ... I will ask
that ibus isn't running in locales where it's not needed...
I installed Debian Stretch with the Gnome desktop environment and neither
im-config nor ibus were installed by default there.
So I cannot report it in Debian, as it does make sense that if someone manually
installs ibus, he'd want to have it running by default.
The problem is Ubuntu-specific, that people that don't need ibus have it
installed by default and running anyway.
Nevertheless, since ibus isn't running under gnome-flashback in non-cjkv
locales, I'm not affected by that, so I can't complain.
Thanks again Gunnar, much appreciated! :)
About the "XDG_CURRENT_DESKTOP=Unity" part in gnome-flashback, it's caused by
unity-control-center/shell/control-center.c:
g_setenv ("XDG_CURRENT_DESKTOP", "Unity", TRUE);
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1551283
Title:
ibus/im-config in Ubuntu GNOME
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1551283/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1551283] Re: ibus/im-config in Ubuntu GNOME
Thank you very much Gunnar, the latest PPA changes work as expected for me in gnome-flashback, i.e. ibus isn't running and I can type Greek just fine. What you have in the PPA is a good compromise for 16.04, please keep it that way. For the future, post 16.04, I'll try to raise the issue in Debian's im-config, so that there's no need to have an Ubuntu debdiff (or to minimize it). I.e. I will ask that ibus isn't running in locales where it's not needed, because: 1) It's causing issues (some of them will be solved in time) 2) It's wasting 20 MB of non-shared RAM (echo 3 > /proc/sys/vm/drop_caches; free; killall ibus-daemon; echo 3 > /proc/sys/vm/drop_caches; free), which is an issue in multi-user systems like LTSP thin clients. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1551283 Title: ibus/im-config in Ubuntu GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1551283/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1551283] Re: ibus/im-config in Ubuntu GNOME
Hi Gunnar, > May I ask: Which display language are you using? If it's something else but Greek, can you please switch to Greek, log out, log in again, and then try to type in Greek (with IBus running). Does that make a difference? I tested with display language = Greek. I haven't tested with display language = English. > Also, just to make sure: Is your Xenial updated with the latest package versions? Yes. > Well, it started with bug #1550325, where it was reported that some applications need IBus to work. Maybe that's true for other flavors but MATE. Then there is the inconsistency in Ubuntu GNOME, which led to the confusion resulting in this bug report. >From what I read there, some people reported that xim doesn't work for them. Noone reported that ibus or xim are useful for people that don't need any input method at all. > Nah, I don't think IBus requires a lot of memory. Please note that IBus is running in Unity and Ubuntu GNOME, whatever the settings are. (Only some environment variables differ.) I don't know about Gnome Flashback in this respect. I did report that ibus breaks the first Greek accented character in Unity as well. Many people don't have the knowledge to pinpoint that ibus is what breaks their keyboard input, and just live with their problems. Gunnar, 1) Would you be willing to accept a patch that makes im-config default to None in all desktop environments, in locales that don't need ibus or xim? 2) If not, is it possible to make language-selector-gnome NOT depend on im-config? Or ubuntu-desktop not depend on language-selector-gnome? Now we can't even uninstall im-config without uninstalling ubuntu-desktop, so we will have to resort to dpkg-divert to bypass this current issue... i.e. that 16.04 will be the first LTS release that we won't be able to properly type in Greek, in all desktop environments. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1551283 Title: ibus/im-config in Ubuntu GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1551283/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1551283] Re: "Region & Language" settings should allow you to set keyboard input method system
> With those changes, im-config (and gnome-language-selector) will default to IBus in Ubuntu GNOME. Hi, I've tested the packages from the PPA under Xenial's gnome-flashback, and now I got ibus running by default. And it again breaks keyboard layout switching with the default Win+Space, so I can't type in Greek (LP: #1481025). Why can't im-config default to ibus in locales that need it, and to None in locales that don't need it, as it did in previous Ubuntu releases? Apart from the serious problems that it's causing, it's also wasting a lot of MB RAM per user, which is completely unacceptable for multi-user systems like LTSP. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1551283 Title: "Region & Language" settings should allow you to set keyboard input method system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1551283/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1551670] Re: Session shortcuts show up in non-Unity sessions
Fix committed in https://launchpad.net/ubuntu/+source/session- shortcuts/1.1, thank you Dmitry! ** Changed in: session-shortcuts (Ubuntu) Importance: Undecided => Low ** Changed in: session-shortcuts (Ubuntu) Status: New => Fix Released ** Changed in: session-shortcuts (Ubuntu) Assignee: (unassigned) => Dmitry Shachnev (mitya57) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to session-shortcuts in Ubuntu. https://bugs.launchpad.net/bugs/1551670 Title: Session shortcuts show up in non-Unity sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/session-shortcuts/+bug/1551670/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1551670] [NEW] Session shortcuts show up in non-Unity sessions
Public bug reported: Hi, the new logout/reboot/shutdown shortcuts show up in the Applications → Accessories menu of Gnome-flashback and other Desktop Environments. I don't think they make sense there, maybe they should be marked to only be shown in the Dash/Unity session. Btw, they're also not translatable like all the other .desktop files in /usr/share/applications. ** Affects: session-shortcuts (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to session-shortcuts in Ubuntu. https://bugs.launchpad.net/bugs/1551670 Title: Session shortcuts show up in non-Unity sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/session-shortcuts/+bug/1551670/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 221363] Re: Policy Kit Unlock Buttons Greyed Out when using NX / VNC / LTSP
Is this still an issue in recent Ubuntu/LTSP versions? ** Changed in: ltsp (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to system-tools-backends in Ubuntu. https://bugs.launchpad.net/bugs/221363 Title: Policy Kit Unlock Buttons Greyed Out when using NX / VNC / LTSP To manage notifications about this bug go to: https://bugs.launchpad.net/freenx-server/+bug/221363/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1492546] Re: Systemd runs ifdown on shutdown even when it shouldn't
Martin, I'm seeing a regression for this with systemd 228-2ubuntu1 in Ubuntu Xenial. Now I again have to remove the "ExecStop=/sbin/ifdown %I" stanza in order to get netbooted clients to shut down. Maybe something else is stopping the ifup service on shutdown now? I tried to downgrade to the version shipped with Wily, but I was blocked by some dependency issues. ** Changed in: systemd (Ubuntu) Status: Fix Released => Triaged -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1492546 Title: Systemd runs ifdown on shutdown even when it shouldn't To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ltsp/+bug/1492546/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 891793] Re: Login with USB key or smart card
Hi, LDM will be deprecated in LTSP 6, so I don't think anyone's going to work on this issue. So I'm marking it "Won't Fix". ** Changed in: ltsp Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/891793 Title: Login with USB key or smart card To manage notifications about this bug go to: https://bugs.launchpad.net/ltsp/+bug/891793/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1502570] Re: gnome-panel indirectly installs evolution
Thank you Dmitry. :) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/1502570 Title: gnome-panel indirectly installs evolution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1502570/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1502570] Re: gnome-panel indirectly installs evolution
Because then we would lose all the other recommended packages: http://packages.ubuntu.com/wily/gnome-panel alacarteeasy GNOME menu editing tool evolution-data-serverevolution database backend server gnome-appletsVarious applets for the GNOME panel - binary files gnome-session-flashback (>= 3.14.0)GNOME Session Manager - GNOME Flashback session gvfsuserspace virtual filesystem - GIO module indicator-applet-completeClone of the GNOME panel indicator applet unity-control-centerutilities to configure the GNOME desktop Listing those one-by-one in the `apt-get install` line of our installer script is possible but it makes the code too much ubuntu-version specific. And of course other users installing gnome-panel (notably LTSP users) running the `apt-get install` manually wouldn't be aware of this bug in order to read it and run it with --no-install-recommends. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/1502570 Title: gnome-panel indirectly installs evolution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1502570/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1502570] Re: gnome-panel indirectly installs evolution
Would it be at all possible to have this in Wily? We're thinking of installing 15.10 in some schools here instead of 14.04, and it would make things a bit easier for us. Thank you very much in any case. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/1502570 Title: gnome-panel indirectly installs evolution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1502570/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1502570] [NEW] gnome-panel indirectly installs evolution
Public bug reported: http://packages.ubuntu.com/wily/gnome-panel gnome-panel Recommends: evolution-common ...which in turn Recommends: evolution Is this on purpose? Could you please lower the "Recommends" to "Suggests"? Gnome-flashback isn't a flavor with a live CD etc, so it makes more sense to keep the vanilla Ubuntu defaults, i.e. thunderbird as the mailer... If evolution-common is necessary for gnome-flashback, but evolution isn't, please mention it so that we ask them instead to lower their Recommends to Suggests. ** Affects: gnome-panel (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/1502570 Title: gnome-panel indirectly installs evolution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1502570/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1492546] [NEW] Systemd runs ifdown on shutdown even when it shouldn't
Public bug reported: The unit /lib/systemd/system/ifup@.service is Debian and Ubuntu specific, it's not part of upstream systemd. On shutdown, it unconditionally ifdowns all interfaces: ExecStop=/sbin/ifdown %I This is a regression from previous init systems (sysvinit and upstart) which cared so that when a network file system was in use, they didn't ifdown the interfaces. Specifically, both /etc/init.d/networking and /etc/init/networking contain these functions: check_network_file_systems() check_network_swaps() which output the message "not deconfiguring network interfaces: network file systems still mounted" and exit. So, please call the same functions in the ExecStop= part of ifup@.service. ** Affects: ltsp (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Ubuntu) Importance: Undecided Assignee: Martin Pitt (pitti) Status: New ** Also affects: ltsp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1492546 Title: Systemd runs ifdown on shutdown even when it shouldn't To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ltsp/+bug/1492546/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 453605] Re: Make default mount umasks configurable
P.S. completely removing dmask from the mount options and letting /media/username "cover" the permission issues, couples well with UDISKS_FILESYSTEM_SHARED, so that people that want USB drives to be shared across users, can just specify UDISKS_FILESYSTEM_SHARED="1" in udev for those drives. Then /media/mountpoint will be world-readable for vfat/ntfs, as expected (as opposed to /media/username/mountpoint which is protected with the default UDISKS_FILESYSTEM_SHARED="0"). ** No longer affects: nautilus (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/453605 Title: Make default mount umasks configurable To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/453605/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 453605] Re: Make default mount umasks configurable
Quotting pitti from comment #2:
> We won't change the behaviour in udisks, there needs to be some default after
> all.
Please completely remove dmask from the vfat/ntfs mount options, like fmask
already is (absent).
Patch available at LP #482501.
I assume that dmask=0077 was added at some point in order to protect the
contents of the mountpoint?
Nowadays, all user-mounted media is protected by the attributes of the parent
directory, /media/username.
guest@pc:~$ ls /media/alkisg
ls: cannot open directory /media/alkisg: Permission denied
Inside /media/username/mountpoint, directories and files should be
world-readable to behave better when copied elsewhere (LP #592748), e.g. in
~/Documents, which is supposed to be world-readable by default.
For example, ~/.local is drwx-- but ~/.local/share is drwxr-xr-x,
similarly, /media/username should be drwx-- and
/media/username/mountpoint/folders should be drwxr-xr-x.
For people needing a quick workaround, and since none exists yet, here's a
really bad one that nevertheless does work for me:
# For the newer udisks2:
sudo sed 's/dmask=[0-9]\{4\}/dmask=0022/' -i /usr/lib/udisks2/udisksd
# For the older udisks:
sudo sed 's/dmask=[0-9]\{4\}/dmask=0022/' -i /usr/lib/udisks/udisks-daemon
# And reboot.
If udisks/udisks2 don't get fixed in some reasonable time, I'll upload
patches packages for the LTS Ubuntu releases in the Greek Schools PPA.
Unfortunately that'll be a pain, especially for udisks updates.
About configurability in nautilus, I don't think it will be needed if
dmask gets removed. And in any case configurability belongs in udisks,
not in packages that use udisks, because then every package that uses
udisks should provide such an option.
Thanks!
** Also affects: udisks (Ubuntu)
Importance: Undecided
Status: New
** Also affects: udisks2 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/453605
Title:
Make default mount umasks configurable
To manage notifications about this bug go to:
https://bugs.launchpad.net/gvfs/+bug/453605/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 592748] Re: problematic default file/directory permissions when VFAT drive connected
*** This bug is a duplicate of bug 453605 *** https://bugs.launchpad.net/bugs/453605 ** Also affects: udisks (Ubuntu) Importance: Undecided Status: New ** Also affects: udisks2 (Ubuntu) Importance: Undecided Status: New ** No longer affects: nautilus (Ubuntu) ** This bug has been marked a duplicate of bug 453605 Make default mount umasks configurable -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/592748 Title: problematic default file/directory permissions when VFAT drive connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks/+bug/592748/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1315867] Re: Don't strip XKB grp
Input from upstream:
(12:17:39 μμ) rtcm: alkisg: yeah, mutter resolves the ISO_Next_Group keysym to
keycodes and installs passive grabs for all those keycodes
(12:21:00 μμ) rtcm: alkisg: so yeah, compiz would need something like
https://git.gnome.org/browse/mutter/tree/src/core/keybindings.c#n367
So I'm guessing that metacity (which is what gnome-flashback uses) would
also need that? Should I put it in the Affects list?
Thanks a lot,
Alkis
** Description changed:
unity-settings-daemon => gsd-keyboard-manager.c has an Ubuntu specific patch
that strips the grp: part in XKB options:
- if (n_sources < 2 || g_strcmp0 (g_getenv ("XDG_CURRENT_DESKTOP"),
"Unity") == 0)
- strip_xkb_option (options, "grp:");
+ if (n_sources < 2 || g_strcmp0 (g_getenv ("XDG_CURRENT_DESKTOP"),
"Unity") == 0)
+ strip_xkb_option (options, "grp:");
The original upstream source code is:
- if (n_sources < 2)
- strip_xkb_option (options, "grp:");
+ if (n_sources < 2)
+ strip_xkb_option (options, "grp:");
That causes a problem: we're no longer able to type e.g. Greek in
- TuxPaint, because TuxPaint grabs the keyboard layout, and u-s-d then
- doesn't see the layout switching shortcut.
+ TuxPaint, because TuxPaint grabs the keyboard, and u-s-d then doesn't
+ see the layout switching shortcut.
But: if we do revert only that line of the source code to what's in upstream,
then we get another problem: that the XKB-defined layout switching shortcut
(e.g. Alt+Shift) doesn't update the keyboard indicator in the panel, only the
GNOME-defined shortcut (e.g. Win+Space) does.
To solve this, I think u-s-d needs to handle ISO_Next_Group. I don't know if
that part exists upstream, but I do know that it works fine in Fedora 20.
After solving this bug, a tiny issue will remain: that Alt+Shift inside
- keyb-grabbing applications won't update the keyboard indicator. Upstream
- GNOME doesn't want patches for that and may try to solve it in SDL, but
- the other 2 issues described above ^ are Ubuntu-specific.
+ keyboard-grabbing applications won't update the keyboard indicator.
+ Upstream GNOME doesn't want patches for that and may try to solve it in
+ SDL, but the other 2 issues described above ^ are Ubuntu-specific.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1315867
Title:
Don't strip XKB grp
To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-settings-daemon/+bug/1315867/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1315867] [NEW] Don't strip XKB grp
Public bug reported:
unity-settings-daemon => gsd-keyboard-manager.c has an Ubuntu specific patch
that strips the grp: part in XKB options:
if (n_sources < 2 || g_strcmp0 (g_getenv ("XDG_CURRENT_DESKTOP"),
"Unity") == 0)
strip_xkb_option (options, "grp:");
The original upstream source code is:
if (n_sources < 2)
strip_xkb_option (options, "grp:");
That causes a problem: we're no longer able to type e.g. Greek in
TuxPaint, because TuxPaint grabs the keyboard layout, and u-s-d then
doesn't see the layout switching shortcut.
But: if we do revert only that line of the source code to what's in upstream,
then we get another problem: that the XKB-defined layout switching shortcut
(e.g. Alt+Shift) doesn't update the keyboard indicator in the panel, only the
GNOME-defined shortcut (e.g. Win+Space) does.
To solve this, I think u-s-d needs to handle ISO_Next_Group. I don't know if
that part exists upstream, but I do know that it works fine in Fedora 20.
After solving this bug, a tiny issue will remain: that Alt+Shift inside
keyb-grabbing applications won't update the keyboard indicator. Upstream
GNOME doesn't want patches for that and may try to solve it in SDL, but
the other 2 issues described above ^ are Ubuntu-specific.
** Affects: unity-settings-daemon
Importance: Undecided
Status: New
** Affects: gnome-settings-daemon (Ubuntu)
Importance: Undecided
Status: New
** Patch added: "dont_strip_grp.patch"
https://bugs.launchpad.net/bugs/1315867/+attachment/4104866/+files/dont_strip_grp.patch
** Also affects: gnome-settings-daemon (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1315867
Title:
Don't strip XKB grp
To manage notifications about this bug go to:
https://bugs.launchpad.net/unity-settings-daemon/+bug/1315867/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1260226] Re: Xorg layout switching shortcut doesn't update indicator
As Dmitry mentioned in bug 1241284, the layout change is monitored by some *daemon. It used to be monitored by gnome-settings-daemon, and now it's monitored by unity*? Dunno I'm not using unity, but I've put gnome- settings-daemon in the Affects list. Was the code that we're looking for in ./debian/patches/61_revert_libgnomekbd_drop from gnome-settings- daemon-3.8.6.1 in Ubuntu 12.04, where this bug didn't exist yet? ** Also affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1260226 Title: Xorg layout switching shortcut doesn't update indicator To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-keyboard/+bug/1260226/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1241284] Re: iBus has problem recognizing the keyboard shortcut
I uninstalled ibus and I still had the problem. I think the Win+Space shortcut to change layouts is handled by gnome-settings-daemon, so I've put it in the Affects list. I also think it's a bad idea to have a DE-specific way to change keyboard layouts, because then we'd need to press e.g. Win+Space in Gnome and Alt+Shift in a real console (vt), which is inconsistent... gnome-settings-daemon should at least respect the xkb shortcut to change keyboard layouts like it used to until now. ** Also affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** No longer affects: ibus (Ubuntu) ** Summary changed: - iBus has problem recognizing the keyboard shortcut + gnome-settings-daemon has problem recognizing the keyboard shortcut ** Summary changed: - gnome-settings-daemon has problem recognizing the keyboard shortcut + gnome-settings-daemon has problems recognizing the layout switching shortcut -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1241284 Title: gnome-settings-daemon has problems recognizing the layout switching shortcut To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-keyboard/+bug/1241284/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1263591] Re: Add notification-area to panel-default-layout.layout
By old-style you mean XKB? And new-style is IBus? IBus is too buggy, keyboard layout switching only works if one types slowly (LP: #1241284), and sometimes it doesn't work at all, and sometimes the indicator doesn't get updated even if you use the new-style switching, and it needs 40+ MB RAM for lower quality layout switching than the one X has been offering out of the box for ages... We'll blacklist IBus for schools here as it's not yet usable, so hopefully XKB will still be in a working state for 14.04. Thank you for confirming LP #1260226! :) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/1263591 Title: Add notification-area to panel-default-layout.layout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1263591/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1241284] Re: iBus has problem recognizing the keyboard shortcut
** Also affects: indicator-keyboard Importance: Undecided Status: New ** Also affects: ibus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to indicator-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1241284 Title: iBus has problem recognizing the keyboard shortcut To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-keyboard/+bug/1241284/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1263591] Re: Add notification-area to panel-default-layout.layout
> That said, if nm-applet and pidgin get fixed for 14.04, notification- area isn't that important anymore... I tried manually applying the patch for nm-applet, it works fine. Pidgin works fine too, after playing a bit with its settings. So yup notification-area isn't that important anymore. Dmitry many gnome-panel bugs were fixed recently, thanks! The only major blocker left for deploying 14.04 with gnome-panel now, is the keyboard indicator not responding to xorg keyboard layout switches, the rest issues left are either small ones or workarounds for them exist. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/1263591 Title: Add notification-area to panel-default-layout.layout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1263591/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1263591] Re: Add notification-area to panel-default-layout.layout
OK Dmitry and thank you for trying it, but in my opinion if the ibus keyboard indicator is shown twice, that's an ibus bug and not a gnome-panel bug, and it should be solved by making that setting default to false: $ grep systray /etc/dconf/db/ibus.d/00-upstream-settings show-icon-on-systray=true Also, none of those 2 keyboard indicators get updated when using the xorg combination to switch keyboard layouts, so they should be removed anyway and be replaced by something that works before 14.04 gets released, it would be a major regression if the keyboard indicator is not working in an LTS release... What I mean is that ibus bugs shouldn't affect this one. That said, if nm-applet and pidgin get fixed for 14.04, notification-area isn't that important anymore... -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/1263591 Title: Add notification-area to panel-default-layout.layout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1263591/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1274740] Re: Re-enable traditional titlebar on 'gnome-but-not-shell' sessions too
> @Alkis: I think there is a typo in Ubuntu's patch.
> Can you stop nautilus ("nautilus -n") and then try to launch it with:
>$ env XDG_CURRENT_DESKTOP=GNOMEF nautilus
For some reason `nautilus -n` didn't do it, but `killall nautilus;
nautilus` did the trick.
I.e. after the `killall nautilus` command, XDG_CURRENT_DESKTOP works
fine, I don't get a title bar when it's GNOME, and I do get the
traditional title bar when it's not GNOME.
So I clicked "affects me too" on LP: #1277963,
thank you. :)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1274740
Title:
Re-enable traditional titlebar on 'gnome-but-not-shell' sessions too
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1274740/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1274740] Re: Re-enable traditional titlebar on 'gnome-but-not-shell' sessions too
With gnome-flashback, I did the following change: $ grep DesktopName /usr/share/xsessions/gnome-fallback.desktop X-LightDM-DesktopName=FGNOME Logout/login, my environment now is: DESKTOP_SESSION=gnome-fallback SESSIONTYPE=gnome-session XDG_CURRENT_DESKTOP=FGNOME And, nautilus 1:3.10.1-0ubuntu2 is still not showing the titlebar, was it supposed to? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1274740 Title: Re-enable traditional titlebar on 'gnome-but-not-shell' sessions too To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1274740/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1263591] Re: Add notification-area to panel-default-layout.layout
Thanks a lot for the feedback, I'm marking it as "Won't Fix" then. Some notes: 1) nm-applet integration has issues, it doesn't display the applet for me on gnome-flashback without manually adding notification-area. I also tried with a recent 14.04 live CD, some times nm-applet did appear and some times it didn't, so I think there's some race condition involved, possibly related to LP #1256961. I'll test more when that bug is resolved. With notification-area manually added, there's no race condition, nm-applet always appears. 2) About pidgin, if you're talking about http://packages.ubuntu.com/indicator-status-provider-pidgin, I see there it's only available for 12.04, maybe that's why I didn't have the integration issues there and I'm having them now in 14.04. In 14.04 I see that indicator-messages conflicts with indicator-status-provider-pidgin, is pidgin in 14.04 supposed to use indicator-messages, and for some reason it doesn't? 3) About stardict and the other apps that aren't yet ported to use the new indicators, let's hope they will soon, but until then, users have no way of knowing why some applications aren't displaying their indicators and that they need to add notification-area manually to work around that problem. Deprecating something doesn't mean it has to be removed immediately, there should be a grace period until e.g. 80% of the involved applications has had enough time to update their code base to use the new indicators. So maybe gnome-panel could grant them that grace period and add notification-area for a couple of more years, dunno... Kind regards, Alkis ** Changed in: gnome-panel (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/1263591 Title: Add notification-area to panel-default-layout.layout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1263591/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1263591] Re: Add notification-area to panel-default-layout.layout
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/1263591 Title: Add notification-area to panel-default-layout.layout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1263591/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1263591] [NEW] Add notification-area to panel-default-layout.layout
Public bug reported: Upstream gnome-panel includes notification-area: https://git.gnome.org/browse/gnome-panel/plain/data/panel-default-layout.layout In Ubuntu, debian/patches/01_layout.patch changes that file in order to make use of indicator-applet-complete. That patch is Ubuntu-specific, it doesn't exist in Debian: http://anonscm.debian.org/viewvc/pkg-gnome/desktop/unstable/gnome-panel/debian/patches/ The problem is that that patch also removes notification-area, so applications like pidgin, stardict etc (and even nm-applet in Trusty) don't show up at all. Please modify that patch so that notification-area is not removed, i.e. add the following lines to it: [Object notification-area] object-iid=NotificationAreaAppletFactory::NotificationArea toplevel-id=top-panel pack-type=end pack-index=1 I'm attaching an updated 41_classic_layout.patch. ** Affects: gnome-panel (Ubuntu) Importance: Undecided Status: New ** Patch added: "Updated debian/patches/41_classic_layout.patch" https://bugs.launchpad.net/bugs/1263591/+attachment/3934571/+files/41_classic_layout.patch -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/1263591 Title: Add notification-area to panel-default-layout.layout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1263591/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1256961] Re: new glib (2.39.1) causes some indicators & nautilus to not load promptly
I think this works around the problem: sudo -i echo '#!/bin/sh /usr/bin/gnome-panel &' > /usr/local/bin/gnome-panel chmod +x /usr/local/bin/gnome-panel Logout or reboot, the panel should load quickly now. In other words, it seems like something is waiting for gnome-panel to finish loading, and if it's put in the background, then everything goes fast again and the panel itself loads quickly... -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1256961 Title: new glib (2.39.1) causes some indicators & nautilus to not load promptly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1256961/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 60448] Re: .xsession-errors file grows out of control & saturates disk space
Xsession or xinit should install a filter on stdout/stderr that checks every line in the output, so that if the same line is written repeatedly, they'd display something like: <$REPEATED_ERROR_MESSAGE_PRODUCED_BY_WHATEVER_APPLICATION> $date - Xsession: last message repeated 1.000.000 times Pulseaudio does something similar, producing entries like this in syslog: Nov 9 10:35:42 alkisg pulseaudio[2031]: last message repeated 7000 times -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/60448 Title: .xsession-errors file grows out of control & saturates disk space To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/60448/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1094924] Re: Freeze: zenity --list … < FileName
*** This bug is a duplicate of bug 995435 *** https://bugs.launchpad.net/bugs/995435 ** This bug has been marked a duplicate of bug 995435 Zenity --list uses 100%cpu and does nothing -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to zenity in Ubuntu. https://bugs.launchpad.net/bugs/1094924 Title: Freeze: zenity --list … < FileName To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zenity/+bug/1094924/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 995435] Re: Zenity --list uses 100%cpu and does nothing
Zenity here in Trusty is still causing 100% CPU. Just run: $ zenity --list --column X Triaged -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to zenity in Ubuntu. https://bugs.launchpad.net/bugs/995435 Title: Zenity --list uses 100%cpu and does nothing To manage notifications about this bug go to: https://bugs.launchpad.net/zenity/+bug/995435/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 580961] Re: unzip fails to deal correctly with filename encodings
Thanks, that partially solves the problem (Precise, 6.0-4ubuntu2).
The question marks are gone, so LP: #1199239 can be marked 'Fix released'.
This (LP: #580961) bug is NOT fully addressed though.
The problem that remains is that only a few codepages are supported.
For example, unzipping a file that contains Greek (cp737) filenames doesn't
work out of the box:
$ unzip -l biografiko.zip
biografiko/ОЫЮЪхЬк ймгзвуирйЮк ШхлЮйЮк_Щ.doc (wrong codepage)
On the other hand, if someone manually specifies the codepage, it does work:
$ unzip -O cp737 -l biografiko.zip
biografiko/Οδηγίες συμπλήρωσης αίτησης_β.doc (right codepage)
I'm guessing it would work if we added this line:
+{ "CP1253", "CP737" },
...in the mapping table defined in debian/patches/06-unzip60-alt-iconv-utf8:
+/* A mapping of local <-> archive charsets used by default to convert filenames
+ * of DOS/Windows Zip archives. Currently very basic. */
+static CHARSET_MAP dos_charset_map[] = {
+{ "ANSI_X3.4-1968", "CP850" },
+{ "ISO-8859-1", "CP850" },
+{ "CP1252", "CP850" },
+{ "UTF-8", "CP866" },
+{ "KOI8-R", "CP866" },
+{ "KOI8-U", "CP866" },
+{ "ISO-8859-5", "CP866" }
+};
I'm not changing the verification-needed flag because it's only partially fixed,
which might mean "verification-failed, affected people do list your codepages
here so that we add them to the mapping table before we upload this to
-updates",
or it might mean "verification-done and open a new bug report for adding more
codepages",
your call. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to a duplicate bug report (34667).
https://bugs.launchpad.net/bugs/580961
Title:
unzip fails to deal correctly with filename encodings
To manage notifications about this bug go to:
https://bugs.launchpad.net/file-roller/+bug/580961/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1236752] Re: gnome-settings-daemon (3.4.2-0ubuntu0.6.3) breaks nvidia multi-monitor-config
Yes, please revert LP: #1065979 as it caused a regression: LP: #1065979 broke the default Xorg resolution, set by e.g. PreferredMode in xorg.conf or by XRANDR_MODE_0 in LTSP, now gnome-settings-daemon forces the *highest* resolution instead of the default one. It's very annoying on CRT screens where e.g. 1024x768 is preferred, and 1600x1200 is unreadable. Could you please revert #1065979 until it's properly solved? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1236752 Title: gnome-settings-daemon (3.4.2-0ubuntu0.6.3) breaks nvidia multi- monitor-config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1236752/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1065979] Re: external/internal monitors mirrored on boot when laptop lid is closed
Regression: This update broke the default Xorg resolution, set by e.g. PreferredMode in xorg.conf or by XRANDR_MODE_0 in LTSP, now gnome-settings-daemon forces the *highest* resolution instead of the default one. It's very annoying on CRT screens where e.g. 1024x768 is preferred, and 1600x1200 is unreadable. Could you please revert it until the current bug is properly solved? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1065979 Title: external/internal monitors mirrored on boot when laptop lid is closed To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1065979/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 861171] Re: Shutdown from greeter does nothing when multiple accounts open
Any progress on this one? It's very annoying on LTSP, where teachers can't shut down the LTSP servers because e.g. 2 hours ago some student had a xorg crash, and even if his thin client is now powered off, the user is still considered logged on at the server because the ssh socket isn't yet closed... This worked fine before switching from GDM to LightDM, with the confirmation dialog etc. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/861171 Title: Shutdown from greeter does nothing when multiple accounts open To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-session/+bug/861171/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1078679] Re: Gnome fallback - intermittent menus on top panel
Here's a script that makes gnome-panel try twice to get loaded properly, so it should avoid the need for a desktop launcher that kills the panel for most of the cases; for the few that will remain, a logout/login should suffice... Greek teachers shouldn't apply it, it'll come as an update from our ts.sch.gr PPA. Create /opt/ltsp/i386/usr/local/bin/gnome-panel, with the following contents: #!/bin/sh if [ "$LTSP_FATCLIENT" != "True" ]; then exec /usr/bin/gnome-panel "$@" fi /usr/bin/gnome-panel "$@" & sleep 10 if ! pgrep -nx indicator-sound -U $USER >/dev/null 2>&1; then echo "$(date) - restarting gnome-panel" >> $HOME/.xsession-errors exec /usr/bin/gnome-panel --replace fi And just a bit more debugging info, in case anyone's interested: * On a client that has the problem, the gnome-panel process is there, but all the applet processes (e.g. indicator-sound-service) aren't. * The .xsession-errors of a client that doesn't have the problem, contains: Initializing nautilus-gdu extension ** Message: applet now removed from the notification area ** Message: using fallback from indicator to GtkStatusIcon ** Message: moving back from GtkStatusIcon to indicator ...while on a client that does have the problem, the last line is missing (i.e. it hangs somewhere between outputing those 2 lines) * I tried removing everything from /etc/xdg/autostart, except for gnome- settings-daemon.desktop, and the problem did appear to become more rare, but eventually it did happen again on 1 client after rebooting 10 clients 6 times (while usually it happens on 1 out of 10 clients, every time). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/1078679 Title: Gnome fallback - intermittent menus on top panel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1078679/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1078679] Re: Gnome fallback - intermittent menus on top panel
I've just experienced it again in an LTSP fat client. Gnome-panel was showing but without any text, looked liked it hanged while loading. strace -p $(pidof gnome-panel) displayed only the following: # strace -p 1928 Process 1928 attached - interrupt to quit restart_syscall(<... resuming interrupted call ...> In .xsession-errors I saw the following but I don't know if they were printed by gnome-panel: Προειδοποίηση διαχειριστή παραθύρων: Log level 8: meta_display_unregister_x_window: assertion `g_hash_table_lookup (display->window_ids, &xwindow) != NULL' failed Προειδοποίηση διαχειριστή παραθύρων: Άκυρο WM_TRANSIENT_FOR παράθυρο 0x3a1 που καθορίστηκε για 0x3a3 (Ανώνυ). The first line translates to "window manager warning", and the second one to "window manager warning: cancelled WM_TRANSIENT_FOR window 0x3a1 that was defined for 0x3a3 (No nam...)" gnome-panel --replace did _not_ work the first time, it resulted in the same non-functioning panel without menus, but it worked fine the second time I ran it. I should also note that LTSP fat clients are using SSHFS, just in case someone finds out it's related to file locking or something. We weren't experiencing it in 10.04 with NFS /home (300 schools, worked fine for 2 years), but that was Gnome 2 though. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/1078679 Title: Gnome fallback - intermittent menus on top panel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1078679/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1078679] Re: Gnome fallback - intermittent menus on top panel
I've been seeing that too, in standalone workstations as well. It's causing significant problems in classrooms where the teacher doesn't know the commands to restart gnome-panel. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/1078679 Title: Gnome fallback - intermittent menus on top panel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1078679/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1017870] Re: Nautilus prompts to execute plain text files on sshfs mounts
The upstream sshfs-fuse developer proposed this patch to fix the issue: http://sourceforge.net/mailarchive/message.php?msg_id=29804620 Removing the Nautilus tasks as the problem was in sshfs. ** Changed in: sshfs-fuse (Ubuntu) Importance: Undecided => Medium ** Changed in: sshfs-fuse (Ubuntu) Status: New => Triaged ** No longer affects: nautilus ** No longer affects: nautilus (Ubuntu) ** No longer affects: nautilus (Ubuntu Precise) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1017870 Title: Nautilus prompts to execute plain text files on sshfs mounts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sshfs-fuse/+bug/1017870/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 491940] Re: Patch for LTSP clients to properly reboot/shutdown
Since the proposed patch was not accepted by the Ubuntu devs that maintain gnome-session, nor any alternative component was suggested to try to patch that instead, we didn't upload a patched gnome-session in the ts.sch.gr PPA for 12.04, it's only there for 10.04. So no point in adding the PPA in 12.04, it doesn't help with this problem. We've developed Epoptes instead, which can shut down the LTSP clients in any Desktop Environment. If upstream Gnome and Gnobuntu don't deprecate gnome-fallback, we'll try to send a patch there, otherwise Gnome will be unusable with LTSP in the future anyway, at least for thin clients (3d/llvmpipe over the network is extremely slow, and Unity-2D support was dropped). So maybe LTSP in the future will propose XFCE/LXDE instead of Gnome. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/491940 Title: Patch for LTSP clients to properly reboot/shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/491940/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 915468] Re: the unity-greeter keyboard's selection doesn't respect the user config
This is still an issue in Ubuntu Precise fully updated.
1) If I use autologin, everything is fine, my keyboard layout is the same as
the system default, En/El.
2) If I use the greeter:
* I only have "En" available in the greeter,
* I only have "En" available in the session,
* I don't get a keyboard layout panel applet in the session.
System settings:
alkisg@server:~$ cat /var/lib/AccountsService/users/alkisg
[User]
XSession=ubuntu
XKeyboardLayouts=
Icon=/usr/share/pixmaps/faces/guitar.jpg
alkisg@server:~$ cat .dmrc
[Desktop]
Session=ubuntu
alkisg@server:~$ cat /etc/default/keyboard
# Check /usr/share/doc/keyboard-configuration/README.Debian for
# documentation on what to do after having modified this file.
# The following variables describe your keyboard and can have the same
# values as the XkbModel, XkbLayout, XkbVariant and XkbOptions options
# in /etc/X11/xorg.conf.
XKBMODEL="pc105"
XKBLAYOUT="us,gr"
XKBVARIANT=","
XKBOPTIONS="grp:alt_shift_toggle,grp_led:scroll"
# If you don't want to use the XKB layout on the console, you can
# specify an alternative keymap. Make sure it will be accessible
# before /usr is mounted.
# KMAP=/etc/console-setup/defkeymap.kmap.gz
Result with autologin (no greeter, no problem):
===
alkisg@server:~$ setxkbmap -print
xkb_keymap {
xkb_keycodes { include "evdev+aliases(qwerty)" };
xkb_types { include "complete" };
xkb_compat{ include "complete+ledscroll(group_lock)"};
xkb_symbols { include
"pc+us+gr:2+inet(evdev)+group(alt_shift_toggle)"};
xkb_geometry { include "pc(pc105)" };
};
Result with lightdm-greeter (problem):
==
alkisg@server:~$ setxkbmap -print
xkb_keymap {
xkb_keycodes { include "evdev+aliases(qwerty)" };
xkb_types { include "complete" };
xkb_compat{ include "complete" };
xkb_symbols { include "pc+us+inet(evdev)" };
xkb_geometry { include "pc(pc105)" };
};
** Changed in: unity-greeter (Ubuntu Precise)
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/915468
Title:
the unity-greeter keyboard's selection doesn't respect the user config
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/915468/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 842768] Re: Cups notifies "printer ' xxx ' may be not connected " although printer is OK and printing is OK too
I believe the fix about making org.gnome.settings-daemon.plugins.print- notifications default to "false" may be shipped as a patch of the gnome- settings-daemon package, so I put it in the affects list. $ dpkg -S /usr/share/glib-2.0/schemas/org.gnome.settings-daemon.plugins.print-notifications.gschema.xml gnome-settings-daemon: /usr/share/glib-2.0/schemas/org.gnome.settings-daemon.plugins.print-notifications.gschema.xml ** Also affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/842768 Title: Cups notifies "printer ' xxx ' may be not connected " although printer is OK and printing is OK too To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/842768/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1017870] Re: Nautilus prompts to execute plain text files on sshfs mounts
** Bug watch added: GNOME Bug Tracker #679187 https://bugzilla.gnome.org/show_bug.cgi?id=679187 ** Also affects: nautilus via https://bugzilla.gnome.org/show_bug.cgi?id=679187 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1017870 Title: Nautilus prompts to execute plain text files on sshfs mounts To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1017870/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 872429] Re: No keyboard layout text in gnome-session-fallback
Works fine on Precise now, so somewhere along the road it was fixed. Marking as invalid though because I'm not sure which package fixed it. ** Changed in: gnome-session (Ubuntu) Status: Confirmed => Invalid ** Changed in: libgnomekbd (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/872429 Title: No keyboard layout text in gnome-session-fallback To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/872429/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1017870] [NEW] Nautilus prompts to execute plain text files on sshfs mounts
Public bug reported: Precise, nautilus 1:3.4.2-0ubuntu3 Steps to reproduce: mkdir /tmp/etc sshfs localhost:/etc /tmp/etc nautilus /tmp/etc => double click on "adduser.conf" Nautilus prompts: Do you want to run "adduser.conf", or display its contents? "adduser.conf" is an executable text file. [Run in Terminal] [Display] [Cancel] [Run] Of course the "adduser.conf" permissions are fine in the file system and in the sshfs mount, it's not executable. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Affects: sshfs-fuse (Ubuntu) Importance: Undecided Status: New ** Also affects: sshfs-fuse (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1017870 Title: Nautilus prompts to execute plain text files on sshfs mounts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1017870/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 990951] Re: Empathy Messenger 3.4.1: avatars not showing [Windows Live protocol] [Ubuntu 12.04]
Manolis, "Assigned to" means "αυτός που θα διορθώσει το πρόβλημα", όχι "αυτός που έχει το πρόβλημα". So now that you assigned this bug to "ubuntu-greek-users" it means that "ubuntu-greek-users" will fix this bug, and that the Empathy developers shouldn't bother with it. So please don't assign bugs, it doesn't mean what you think it means. ** Changed in: empathy (Ubuntu) Assignee: Ubuntu Greece (ubuntu-greek-users) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/990951 Title: Empathy Messenger 3.4.1: avatars not showing [Windows Live protocol] [Ubuntu 12.04] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/990951/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 891793] Re: Login with USB key or smart card
** Also affects: ltsp Importance: Undecided Status: New ** No longer affects: ldm (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/891793 Title: Login with USB key or smart card To manage notifications about this bug go to: https://bugs.launchpad.net/ltsp/+bug/891793/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 580961] Re: unzip fails to deal correctly with filename encodings
"assignee: madlokil" means that madlokil is the developer responsible for fixing the bug. "status: In progress" by thefusionite means that someone is working to fix the bug, so the other developers don't need to bother with it. So by setting the status to assigned+in progress, you actually discourage developers from working on this bug. Allow me to assume that it was done by mistake, and to reset the status to "unassigned" and "triaged". WRT comments #96 and 97, since the newer unzip version is not yet packaged for Debian, and doesn't look like it will be in time for Precise, could we do something so that we don't have a broken unzip in the next LTS version too? * Either package the newer upstream version, * Or check what's missing from the existing patch that prevents -I and -O from working? ** Changed in: unzip (Ubuntu) Status: In Progress => Triaged ** Changed in: unzip (Ubuntu) Assignee: Mad_Loki (madloki1) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to a duplicate bug report (34667). https://bugs.launchpad.net/bugs/580961 Title: unzip fails to deal correctly with filename encodings To manage notifications about this bug go to: https://bugs.launchpad.net/file-roller/+bug/580961/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 872429] Re: No keyboard layout text in gnome-session-fallback
Forgot to mention - using Oneiric fully updated as at 2011-10-11: gnome-session-fallback 3.2.0-0ubuntu3 libgnomekbd-common 3.2.0-0ubuntu1 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/872429 Title: No keyboard layout text in gnome-session-fallback To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/872429/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 872429] Re: No keyboard layout text in gnome-session-fallback
** Attachment added: "libgnomekbd.png" https://bugs.launchpad.net/bugs/872429/+attachment/2536793/+files/libgnomekbd.png ** Also affects: gnome-session (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/872429 Title: No keyboard layout text in gnome-session-fallback To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/872429/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 491940] Re: Patch for LTSP clients to properly reboot/shutdown
Sorry, no idea. We're using only LTS releases here, and I'm kinda pressed time-wise this year, so I won't be able to test with recent versions of the involved packages until Ubuntu 12.04, if it's still a problem then. The LTSP task mainly referred to LTSP_LOGOUT_ACTION (commit http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp- trunk/revision/1481), so yeah, either invalid or committed will do, until gnome-session can provide a method to notify the caller (LDM, xinit...) about the selected action (logout, reboot, shutdown). Another approach is to at least make indicator-session policy-kit aware, so that it doesn't display the reboot/shutdown menu items at all: https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/474392 >From a user's perspective, that's not as good as fixing gnome-session, because then the user loses logout/reboot/shutdown functionality from the menus. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/491940 Title: Patch for LTSP clients to properly reboot/shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/491940/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 580961] Re: unzip fails to deal correctly with filename encodings
@frol: ppa:frol/zip-i18n contains libnatspec 0.2.6-0ubuntu2, while ppa:r0lf/ppa contains a "later" version, libnatspec 0.2.6-1. $ dpkg --compare-versions 0.2.6-0ubuntu2 gt 0.2.6-1 || echo "Needs version bump" Needs version bump For people that have/had r0lf's ppa in their sources to be able to upgrade, you'd need to bump the version. I've tested with "sudo apt-get install libnatspec0=0.2.6-0ubuntu2" and indeed now it correctly autodetects, lists and uncompresses cp737 (Greek) zip files. Thanks! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a subscriber of a duplicate bug (34667). https://bugs.launchpad.net/bugs/580961 Title: unzip fails to deal correctly with filename encodings -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 580961] Re: unzip fails to deal correctly with filename encodings
frol wrote 51 minutes ago: > Alkis, You need to cantact libnatspec maintainer about this bug: > https://launchpad.net/~r0lf/+contactuser That person closed my bug report (LP #477755) where I was suggesting the altlinux solution that was finally accepted upstream, in order to open this bug. Then he told me that comments in this bug report were unwelcome (comment #16), so I became unable to provide feedback to the bug I reported. Then he started asking people money about his packaging job in libnatspec (developed by Vitaly Lipatov) and being rude when people weren't willing to pay. Fortunately at a point he got "insulted" because people continued to comment on this bug report, and left. What I mean is that I don't want to contact that package maintainer, and if possible, I wouldn't want to use his package either, more so when the upstream solution doesn't use it. I've been coding open source programs for almost 20 years now, and been packaging some of them in the last few years that I've switched to Linux. I'd prefer to redo any needed coding or packaging work myself before having to cooperate with such a person. For now I'll just wait for Debian to package the newer version of unzip, and then contact upstream if any problems persist. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a subscriber of a duplicate bug (34667). https://bugs.launchpad.net/bugs/580961 Title: unzip fails to deal correctly with filename encodings -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 580961] Re: unzip fails to deal correctly with filename encodings
frol wrote on 2011-04-01: > Alkis, can You please confirm that libnatspec is working correctly > on your machine, by installing natspec-bin frol ppa:r0lf/ppa and > running "natspec -i"? > Does it correclty detects charsets for your locale? > > Also can You post output of "zipinfo -v biografiko.zip"? It correctly detects the WIN encoding, which is CP1253, but it doesn't correctly detect the DOS encoding. It claims it to be 437, while the correct one is 737: http://en.wikipedia.org/wiki/Code_page_737 Attaching the output of those commands. Also attaching the correct output, which is produced if one manually specifies the encoding: $ ZIPINFO='-O CP737' zipinfo -v biografiko.zip ** Attachment added: "natspec-output" https://bugs.launchpad.net/ubuntu/+source/unzip/+bug/580961/+attachment/1974167/+files/natspec-output -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a subscriber of a duplicate bug (34667). https://bugs.launchpad.net/bugs/580961 Title: unzip fails to deal correctly with filename encodings -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 580961] Re: unzip fails to deal correctly with filename encodings
Στις 10-03-2011, ημέρα Πεμ, και ώρα 15:04 +, ο/η Martin Pitt έγραψε: > But AFAIK the new -I and -O options already work. I thought the > remainder of the problem was that the value isn't autodetected, but > needs to be specified manually? No, the -I and -O options do not work properly. It looks like something, maybe just a couple of lines, were missing from the Natty patch. I described the current situation in comment #89: * Extracting works: UNZIP="-o cp737" unzip archive.zip * Listing doesn't: UNZIP="-o cp737" unzip -l archive.zip Since listing doesn't work, file-roller also doesn't work (it uses `unzip -ZTs`, i.e. listing in zipinfo mode). And no, I'm not talking about autodetection, libnatspec wasn't used in the upstream patch and it fails to autodetect Greek anyway (haven't tested other locales). So personally for now I'd be happy if unzip was at least working with the -I and -O options and with the UNZIP environment variable. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a subscriber of a duplicate bug (34667). https://bugs.launchpad.net/bugs/580961 Title: unzip fails to deal correctly with filename encodings -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 580961] Re: unzip fails to deal correctly with filename encodings
If I'm not mistaken, a fix for this bug has been committed upstream since 2010/12/05: ftp://ftp.info-zip.org/pub/infozip/beta/unzip610b.zip A related post in their forums: http://www.info-zip.org/phpBB3/viewtopic.php?f=7&t=223&start=45#p2113 Maybe it'd be simpler to use the 6.1 package rather than applying the altlinux patch? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a subscriber of a duplicate bug (34667). https://bugs.launchpad.net/bugs/580961 Title: unzip fails to deal correctly with filename encodings -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 494096] Re: Clicking the title of a window is bringing a window underneath it into focus
The metacity from lucid-proposed works fine here. $ dpkg-query -W metacity metacity1:2.30.1-0ubuntu1.1 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in ubuntu. https://bugs.launchpad.net/bugs/494096 Title: Clicking the title of a window is bringing a window underneath it into focus -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 580961] Re: unzip fails to deal correctly with filename encodings
I just tried frol's PPA with the libnatspec dependency. It didn't correctly autodetect the encoding so I didn't see any benefit with that implementation. It did however work as good as unzip did in older Ubuntu versions, i.e. both extracting *and listing* worked if either the UNZIP/ZIPINFO environment variables were defined, or if the -O parameter was used: # autodetection doesn't work: $ echo $LANG el_GR.utf8 $ unzip -l biografiko.zip 43008 2010-05-14 12:20 biografiko/Ä¢₧Ü圪 ⌐¼úºóπ¿α⌐₧¬ ÿσ½₧⌐₧¬_Ö.doc # works with the UNZIP environment variable: $ UNZIP='-O cp737' unzip -l biografiko.zip 43008 2010-05-14 12:20 biografiko/Οδηγίες συμπλήρωσης αίτησης_β.doc # (alternatively, the same output is also produced with "-O cp737" in the command line) # and in zipinfo mode, as called by file-roller: $ ZIPINFO='-O cp737' unzip -ZTs biografiko.zip -rw-a-- 2.0 fat43008 b- defN 20100514.122016 biografiko/Οδηγίες συμπλήρωσης αίτησης_β.doc # (alternatively, the same output is also produced with "-O cp737" in the command line) So, it looks like only half of the required patch was included in unzip 6.0-4ubuntu1. Please make listing (unzip -l and unzip -ZTs) work, as it did in previous Ubuntu versions. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a subscriber of a duplicate bug (34667). https://bugs.launchpad.net/bugs/580961 Title: unzip fails to deal correctly with filename encodings -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 580961] Re: unzip fails to deal correctly with filename encodings
I confirm that 6.0-4ubuntu1 is still half-broken, compared to previous Ubuntu versions. * Extracting works: UNZIP="-o cp737" unzip archive.zip * Listing doesn't: UNZIP="-o cp737" unzip -l archive.zip Since listing doesn't work, file-roller also doesn't work. I tested with http://www.ops.gr/Ergorama/fileUploads/ypiresiaops/prokirikseis/biografiko.zip Btw, here's an easy way to provide the unzip environment variables for all users. Create the following script: $ sudo gedit /usr/local/bin/unzip Paste these 4 lines, but replace cp737 with the appropriate charset for your locale: #!/bin/sh export UNZIP="-O cp737" export ZIPINFO="-O cp737" exec /usr/bin/unzip "$@" Save, exit, and make the script executable: $ sudo chmod +x /usr/local/bin/unzip -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a subscriber of a duplicate bug (34667). https://bugs.launchpad.net/bugs/580961 Title: unzip fails to deal correctly with filename encodings -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 697112] Re: Backport fix for broken XDMCP login to Lucid
Runs fine on my i386 Lucid: $ dpkg-query -W gdm gdm 2.30.2.is.2.30.0-0ubuntu5 Connected via XDMCP about 10 times in a row with no problems. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. https://bugs.launchpad.net/bugs/697112 Title: Backport fix for broken XDMCP login to Lucid -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 697112] Re: Backport fix for broken XDMCP login to Lucid
Thank you Sebastien, attaching a .debdiff and subscribing ubuntu- sponsors. ** Patch added: "Initialize length for XdmcpFill, fixes XDMCP logins" https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/697112/+attachment/1786460/+files/xdmcpfill_length.debdiff -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. https://bugs.launchpad.net/bugs/697112 Title: Backport fix for broken XDMCP login to Lucid -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
