[Bug 1467695] Re: Alt-Grave (`) switcher has flickering/pulsing shadow artifacts
Hello, one question: Is everyone affected by this bug using indicator- multiload? I noticed just now that the frequency of the "pulsing" effect depends directly on the rate of update of the multiload indicator. Removing the multiload indicator here on my computer also stopped the pulsing effect. Also, just speculating here but I think it's possible that other animated indicator applets might cause the same behavior. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1467695 Title: Alt-Grave (`) switcher has flickering/pulsing shadow artifacts To manage notifications about this bug go to: https://bugs.launchpad.net/nux/+bug/1467695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1342123] Re: evolution-calendar-factory always running with high memory usage
@ledoc Hi Eric, same as you, I later realized that a certain delay was needed for it to work reliably, since there'd be times when the autostart entry would get invoked before the datetime indicator. The Exec line on my .desktop file now reads like this: Exec=bash -c 'sleep 1m; /usr/lib/evolution/evolution-calendar-factory' An Upstart-based solution might be better given that timing is involved, but this simple approach works well enough for me. Perhaps you'd like to try it out? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1342123 Title: evolution-calendar-factory always running with high memory usage To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1342123/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1550680] Re: Setting org.gnome.desktop.background show-desktop-icons to false removes wallpaper
Hello, By any chance, did you disable your Nautilus startup item? It's the one defined in: /etc/xdg/autostart/nautilus-autostart.desktop -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1550680 Title: Setting org.gnome.desktop.background show-desktop-icons to false removes wallpaper To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1550680/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1550680] Re: Setting org.gnome.desktop.background show-desktop-icons to false removes wallpaper
Or... wait, sorry, I think I have another bug in mind when I wrote comment #17. In any case, the file I mentioned above has this autostart condition, that might be what's causing your problem: AutostartCondition=GSettings org.gnome.desktop.background show-desktop- icons -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1550680 Title: Setting org.gnome.desktop.background show-desktop-icons to false removes wallpaper To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1550680/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1467695] Re: Alt-Grave (`) switcher has flickering/pulsing shadow artifacts
Hello, a workaround that I have discovered is to disable framebuffer objects in the Compiz OpenGL plugin: gsettings set org.compiz.opengl:/org/compiz/profiles/unity/plugins/opengl/ framebuffer-object false Enter that in the terminal and it would take effect immediately; no logout required. Of course, we can expect that other desktop features that absolutely need OpenGL framebuffer objects might glitch or be affected in some way. And again, this is just a workaround to make the unsightly behaviour go away, and by no means a fix. It does give a clue, though, that it's related to the use of framebuffer objects by whatever it is that renders shadows and glow effects. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1467695 Title: Alt-Grave (`) switcher has flickering/pulsing shadow artifacts To manage notifications about this bug go to: https://bugs.launchpad.net/nux/+bug/1467695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1342123] Re: evolution-calendar-factory always running with high memory usage
Small update: > Bill Filler (bfiller) wrote on 2014-09-23: > I'm assuming evolution-calendar-factory gets loaded by indicator-datetime > initially such that the indicator can show calendar events. As a troubleshooting step, I tried disabling the Upstart entry for indicator-datetime-service so that it doesn't get started and respawned automatically, and launched it manually using the terminal. Sure enough, evolution-calendar-factory starts only after indicator-datetime-service starts, and stops a few seconds after the indicator-datetime-service process is terminated (by Ctrl-C during my testing). So what actually happens in the workaround I posted earlier was that invoking another instance of evolution-calendar-factory manually will sever the link that the date/time indicator has to the calendar service. The new, manually invoked evolution-calendar-factory instance that replaced the old one will then terminate itself after a few seconds. It should be fine for people like me who never use the calendar, but people who do use the calendar should watch out. There are a few questions I can think of at this point: 1. Is it by design that indicator-datetime-service needs continuous access to the org.gnome.evolution.dataserver.Calendar4 D-Bus service? 2. Does it really need to maintain a connection to that service even if the user doesn't use the calendar feature at all? (this needs to be asked because the current implementation of evolution-calendar-factory occupies an above-average amount of memory, even for empty calendars) 3. If not, what could be preventing it from disconnecting from the service once it's done with its business? I'll try to see what else I can uncover. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1342123 Title: evolution-calendar-factory always running with high memory usage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1342123/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1342123] Re: evolution-calendar-factory always running with high memory usage
If anyone is interested in a workaround, here's something that seems to
work on my Ubuntu install.
I noticed that running /usr/lib/evolution/evolution-calendar-factory by
itself manually will cause it to perform some initializations and
terminate after a few seconds. I'm not using any calendar-related
services.
Registering ECalBackendContactsEventsFactory ('contacts:VEVENT')
<>
Registering ECalBackendCalDAVTodosFactory ('caldav:VTODO')
Server is up and running...
Bus name 'org.gnome.evolution.dataserver.Calendar4' acquired.
Bye.
I also noticed that if I ran /usr/lib/evolution/evolution-calendar-
factory while there is already an instance running, the new instance
will take over the 'org.gnome.evolution.dataserver.Calendar4' bus and
will cause the older one to terminate:
Registering ECalBackendContactsEventsFactory ('contacts:VEVENT')
<>
Registering ECalBackendCalDAVTodosFactory ('caldav:VTODO')
Server is up and running...
Bus name 'org.gnome.evolution.dataserver.Calendar4' acquired.
<>
Bus name 'org.gnome.evolution.dataserver.Calendar4' lost.
Bye.
Since I'm not using any calendar-related services, I added a startup
item via GUI that invokes /usr/lib/evolution/evolution-calendar-factory
without any options:
> cat ~/.config/autostart/evolution-calendar-factory.desktop
[Desktop Entry]
Type=Application
Exec=/usr/lib/evolution/evolution-calendar-factory
Hidden=false
NoDisplay=false
X-GNOME-Autostart-enabled=true
Name=Workaround for evolution-calendar-factory
This causes the original "stuck" startup process to lose its hold on
org.gnome.evolution.dataserver.Calendar4 and terminate.
This workaround is a lot less invasive than the suggestions I have seen
elsewhere to uninstall packages or remove the file's execute bit, since
org.gnome.evolution.dataserver.Calendar4 will still be available.
Again, this is a workaround. Unfortunately, I haven't been able to find
out what causes the process to be stuck in the first place, or whether
or not it really needs to run all the time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1342123
Title:
evolution-calendar-factory always running with high memory usage
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1342123/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322275] Re: lightdm sessions started by dm-tool lock (or a session locker) never get closed
Hello, here's what I did on my Xubuntu installation that seems to work: In this file: /etc/xdg/xdg-xubuntu/lightdm/ In line 27, in a default installation, it reads: show-indicators=power;~session;~language;~a11y;~power; Remove the first "power" entry, leaving only the built-in indicators: show-indicators=~session;~language;~a11y;~power; Save the file, and any subsequent lock screens and the processes they spawn should now exit properly upon screen unlock. I can't say for sure why it solves the issue on my Xubuntu, but I suspect that trying to include two power indicators might cause one or the other to prevent lightdm's indicator services instance from properly terminating. Can you see if this solves the issue on your computers? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322275 Title: lightdm sessions started by dm-tool lock (or a session locker) never get closed To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1322275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322275] Re: lightdm sessions started by dm-tool lock (or a session locker) never get closed
Hi Sergio, Yes I did mean /etc/xdg/xdg-xubuntu/lightdm/lightdm-gtk-greeter.conf , thanks for that. Here's what I have for x-1-greeter.log: (lightdm-gtk-greeter:2212): Gtk-CRITICAL **: gtk_container_foreach: assertion 'GTK_IS_CONTAINER (container)' failed (lightdm-gtk-greeter:2212): Gtk-CRITICAL **: gtk_container_foreach: assertion 'GTK_IS_CONTAINER (container)' failed (lightdm-gtk-greeter:2212): Gtk-CRITICAL **: gtk_container_foreach: assertion 'GTK_IS_CONTAINER (container)' failed g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. Unfortunately, I don't know what these entries mean. The .old file contains exactly the same messages, except for having a different PID listed. Also, it might be worth mentioning that I'm on Xubuntu 14.04, and have these indicator related entries unchecked in my Session and Startup GUI, under Application Autostart: Indicator Application Indicator Power Indicator Sound I unchecked these as a previous troubleshooting step, and left them unchecked since they'll be started anyway by the indicator panel applet. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322275 Title: lightdm sessions started by dm-tool lock (or a session locker) never get closed To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1322275/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
