[Bug 2028610] [NEW] bring-to-front and send-to-back not working for some apps
Public bug reported: Since I upgraded to Ubuntu 23.04, a number of my applications have stopped accepting bring-to-front (right click on the title bar) and send-to-back (middle click on the title bar). On the other hand, other apps (native Gnome apps seemingly) do still seem to work. Note I'm using X11 not Wayland. A set of apps I know do not work anymore, that used to work with Ubuntu 22.10 and below: * xterm * Emacs * Chrome * Slack * Spotify * VirtualBox manager Some apps that do still work: * Remmina * File Manager * gnome-terminal * Gnome Settings * Ubuntu Software There are many more in both categories. Please fix things so that I can use bring-to-front and send-to-back on all my apps again. Thanks! ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: mutter 44.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.14.0-1054.61-oem 5.14.21 Uname: Linux 5.14.0-1054-oem x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jul 24 23:31:31 2023 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 InstallationDate: Installed on 2022-12-02 (234 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 SourcePackage: mutter UpgradeStatus: Upgraded to lunar on 2023-06-04 (50 days ago) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2028610 Title: bring-to-front and send-to-back not working for some apps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2028610/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797734] Re: slow calculator startup
Hey, if my assertion incentivizes someone to figure out how to do that, I'm more than willing to admit I was wrong :). The thing is, IMO "fast enough" for a desktop calculator is pretty darn fast. In my opinion the current integrated DEB version is already slow enough to be frustrating, so there's plenty of work in this area without even considering the issue of snaps. People just don't expect to have to wait for a calculator on their computer: isn't calculating the thing that computers were built for and are best at?! I'm not suggesting we should do something like waste users' memory by preloading the calculator app just so it can be ready to display a window quickly, though. In reality probably not enough people use the app often enough to justify that. Cheers! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1797734 Title: slow calculator startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1797734/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797734] Re: slow calculator startup
It is not physically possible to ever get a snap to start as fast as a native application. The entire purpose of a snap is that it uses its own set of dependencies, which means that by definition it cannot share those dependencies with other applications on the system, which means that they must be loaded separately, which will take longer, use more system resources, etc. snaps should be used for applications which (a) are difficult to package, and/or (b) want to be used across multiple versions where prerequisites might change, and/or (c) snaps downsides are not as relevant (for example, they are left running for longer periods of time and are large enough that they aren't expected to start quickly, to amortize the increased start time and resource usage). None of those criteria hold true for a desktop calculator utility. We need to get to the point where I can hit the calculator button on the keyboard and a calculator window appears virtually instantaneously. gnome-calculator was always too slow to start, but now it's far slower: it's moving in exactly the wrong direction. Using it as a way to experiment with snaps just gives both snaps and gnome-calculator a bad reputation. This bug is not trying to say "we must improve snap startup times". This bug is trying to say "gnome-calculator is not an appropriate application to be snapped and should be changed back to a native application". -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1797734 Title: slow calculator startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1797734/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1797734] Re: slow calculator startup
I'm not sure why the "is 2s too slow to start" is the question being asked. Who starts and stops their calculator multiple times in a row? That's not a realistic use-case for the vast majority. Most people need a calculator once a day or every few days, and a desktop calculator is not an application people tend to leave running for long periods like a browser or word processor. They need to do a quick bit of computation so they open the app, work in it for a few minutes, then close it again. Startup speed is, after correctness, probably THE most important aspect of a utility like this. The interesting number for gnome-calculator is the FIRST number: how long it takes to be able to use the application from a cold start. 15s is much closer to what I see, EVERY TIME I start gnome-calculator. That's just... close to unusable. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1797734 Title: slow calculator startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1797734/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1729028] Re: gnome-shell crashes when monitor sleeps or is turned off
I wasn't having any problems with Ubuntu 18.04 but ever since I upgraded to Ubuntu 18.10 gnome-shell seems to crash two out of every three times the screensaver starts. I used ubuntu-bug on a /var/crash file but I have no idea what happened to it: it showed me the info in a window and I said go ahead and send it, then it disappeared and I got no email or anything. FYI, I have an older system with an old NVidia card, no 4k monitor although I do use two monitors. I use Xg not wayland. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1729028 Title: gnome-shell crashes when monitor sleeps or is turned off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1729028/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1812593] Re: gnome-shell[3159]: JS ERROR: Exception in callback for signal: activate: Error: Error invoking IBus.set_global_engine_async: Expected function for callback argument callback, got und
I was seeing this same warning. The only overlap of extensions with the list above and my list (I only use 3 extensions) is 'system- moni...@paradoxxx.zero.gmail.com'. I realized I had installed that extension from source rather than through the extensions website since it needed to be built from source for a while due to prerequisites, and I hadn't updated it. I uninstalled and re-installed it from the Extensions web site. So far I haven't seen this warning come back. I'll continue to check if I see it again. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1812593 Title: gnome-shell[3159]: JS ERROR: Exception in callback for signal: activate: Error: Error invoking IBus.set_global_engine_async: Expected function for callback argument callback, got undefined To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812593/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1730241] Re: Evolution segfaults when NVidia driver is installed but not used
Aha, looking at issue #109 then checking journalctl I see: Oct 09 09:34:34 homebase kernel: NVRM: API mismatch: the client has the version 340.107, but NVRM: this kernel module has the version 340.106. Please NVRM: make sure that this kernel module and all NVIDIA driver NVRM: components have the same version. Oct 09 09:34:34 homebase kernel: NVRM: nvidia_frontend_ioctl: minor 255, module->ioctl failed, error -22 I suspect that maybe an "apt update" ran which installed a new nvidia driver but I haven't rebooted so the old one is still active? I'll try rebooting to see if that helps. I think it would be very helpful if libcogl could be enhanced to report some sort of error rather than just dumping core... -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1730241 Title: Evolution segfaults when NVidia driver is installed but not used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clutter-gtk/+bug/1730241/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1730241] Re: Evolution segfaults when NVidia driver is installed but not used
Seems like it might be related to this: https://gitlab.gnome.org/GNOME/cogl/issues/1 which similarly was reported here: https://gitlab.gnome.org/GNOME/gnome-control- center/issues/109 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1730241 Title: Evolution segfaults when NVidia driver is installed but not used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clutter-gtk/+bug/1730241/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1730241] Re: Evolution segfaults when NVidia driver is installed but not used
I just restarted Evolution (but did not reboot my system or make any other changes) and now Evolution is crashing for me in the identical way described here. I literally just quit Evolution, it was running fine, and restarted it and now it just crashes with the same stacktrace shown above, a null pointer passed to g_ascii_strtoull() (will add it as an attachment) after this error: (evolution:14770): GLib-CRITICAL **: 19:35:04.237: g_strsplit: assertion 'string != NULL' failed I'm now a little afraid to restart my system in case more things start to fail. FYI, glxinfo shows: $ glxinfo name of display: :1 X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 154 (GLX) Minor opcode of failed request: 24 (X_GLXCreateNewContext) Value in failed request: 0x0 Serial number of failed request: 93 Current serial number in output stream: 94 I think if nothing else, a bug should be filed with libcogl asking them to be more defensive in their programming here and handle badly formatted GPU version string. For example in my backtrace I can clearly see that the strings being taken from the context are all null, and that _cogl_gpu_info_parse_version_string() simply passes this to g_ascii_strtoull() without checking. I have Ubuntu 18.04.1 with: ii evolution 3.28.5-0ubuntu0.18.04.1 ii evolution-common 3.28.5-0ubuntu0.18.04.1 ii evolution-data-server 3.28.5-0ubuntu0.18.04.1 ii evolution-data-server-common 3.28.5-0ubuntu0.18.04.1 ii evolution-plugin-bogofilter 3.28.5-0ubuntu0.18.04.1 ii evolution-plugin-pstimport3.28.5-0ubuntu0.18.04.1 ii evolution-plugins 3.28.5-0ubuntu0.18.04.1 ii libclutter-1.0-0:amd641.26.2+dfsg-4 ii libclutter-1.0-0-dbgsym:amd64 1.26.2+dfsg-4 ii libclutter-1.0-common 1.26.2+dfsg-4 ii libclutter-gst-3.0-0:amd643.0.26-1 ii libclutter-gtk-1.0-0:amd641.8.4-3 ii libclutter-gtk-1.0-0-dbgsym:amd64 1.8.4-3 ii libcogl-common1.22.2-3 ii libcogl-pango20:amd64 1.22.2-3 ii libcogl-path20:amd64 1.22.2-3 ii libcogl20:amd64 1.22.2-3 ii libcogl20-dbgsym:amd641.22.2-3 ii libglib2.0-0:amd642.56.2-0ubuntu0.18.04.2 ii libglib2.0-0-dbgsym:amd64 2.56.2-0ubuntu0.18.04.2 ii libglib2.0-bin2.56.2-0ubuntu0.18.04.2 ii libglib2.0-data 2.56.2-0ubuntu0.18.04.2 ii libglib2.0-dev:amd64 2.56.2-0ubuntu0.18.04.2 ii libglib2.0-dev-bin2.56.2-0ubuntu0.18.04.2 I'm running with NVidia proprietary drivers with my old crusty NVidia GeForce 8400 GS with the proprietary driver version 340.107 that I've been using, and has worked fine, for years. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1730241 Title: Evolution segfaults when NVidia driver is installed but not used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clutter-gtk/+bug/1730241/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1730241] Re: Evolution segfaults when NVidia driver is installed but not used
** Attachment added: "GDB backtrace for crash in libcogl" https://bugs.launchpad.net/ubuntu/+source/cogl/+bug/1730241/+attachment/5199322/+files/libcogl-crash.log -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1730241 Title: Evolution segfaults when NVidia driver is installed but not used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clutter-gtk/+bug/1730241/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1728450] [NEW] Details are not visible by default and hide important configuration
Public bug reported: When I open the gnome-control-center, I see the following menu items down the left side: Wi-Fi, Bluetooth, Background, Notifications, Search, Region & Language, Universal Access, Online Accounts, Privacy, Sharing, Sound, Power, Network, Devices (with a sub-menu). Screenshot attached. If I happen to move my mouse into the menu area I _may_ notice a very thin "scroll area" show up briefly before it disappears again, or I _may_ notice very subtle dotted lines at the bottom of the menu, and I _may_ notice that there is actually another menu item at the bottom that I have to scroll down to see: Details. And if I happen to find that and click on that sub-menu, I will find critically important items in there such as Date & Time configuration (what I was looking for to get an AM/PM clock, and couldn't find at all), Users configuration (couldn't find that either so had to add users by hand from the CLI), and Default Applications (also important so I can change the default mail client etc.) What does "Details" even mean? This menu might as well be named "Miscellaneous". Really that would be MORE helpful: at least it would be clear that there's a bunch of random stuff below that menu, which is the reality. The only thing in "Details" that feels appropriate to the name is the "About" menu. I really like the format change of gnome-control-center from the "rows of icons" to the left-side menu: it looks nice and avoiding the "go back and select something else" by just clicking along the left side is a very pleasant experience. But the menu organization here is really confusing and hard to use, and needs serious attention. There needs to be enough top-level menus to be sure everything fits on the screen without scrolling. The About menu item should be on the top-level menu at the bottom of the list... people think it's not important but it's actually REALLY important, so inexperienced people can easily obtain critical system details when asking for help. And the grouping of these menus needs love: for example, why is "Wi-Fi" a separate menu item from "Network"? I would think that Wi-Fi, Network, Online Accounts and Sharing could all be combined into one sub-menu like "Internet" or similar. Actually I don't have a Wi-Fi adapter in my system so I don't know what shows up there: maybe "Wi-Fi" is more about the hardware, and belongs under "Devices"? Either way. Also I think "Region & Language", "Universal Access", and possibly "Date & Time" could be grouped together. And "Background", "Privacy", and "Notifications" could be grouped under some sort of "desktop" menu. Or maybe "Region & Language" would stay a top-level item and "Universal Access" and "Date & Time" would be added to "Desktop". Anyway. I realize there are lots of ways to chop these items up and people will have disagreements, but the current situation is really very not good: the control center needs to avoid the need for scrolling to see all the options and if things are moved into sub-menus the names of those menus HAVE to be evocative and clear. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Oct 29 15:18:20 2017 InstallationDate: Installed on 2017-10-21 (8 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ** Attachment added: "control center screenshot" https://bugs.launchpad.net/bugs/1728450/+attachment/4999656/+files/Screenshot%20from%202017-10-29%2015-44-45.png -- 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/1728450 Title: Details are not visible by default and hide important configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1728450/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1726143] [NEW] Automatic installation of samba fails with "could not find package libpam-smbpass"
Public bug reported: I actually have no idea if this is really a Nautilus issue but didn't know where else to file it. I have a fresh install of ubuntu 17.10. I start nautilus (using File). I right-click on a folder and select "Local Network Share". When I select "Share this folder" it says the sharing service is not installed, so I select "Install Service" and it offers to install samba for me. I click "install" and it proceeds, then throws up an error dialog: Could not find package 'libpam-smbpass' I can see that Samba packages are already installed at this point. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Oct 22 15:43:28 2017 InstallationDate: Installed on 2017-10-21 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- 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/1726143 Title: Automatic installation of samba fails with "could not find package libpam-smbpass" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1726143/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1726124] [NEW] DNS domain search paths not updated when VPN started
Public bug reported: I connect to work with openvpn through network-manager-openvpn. I'm selecting automatic (DHCP) to get an IP address, and "Use this connection only for resources on its network" to support split tunneling. In the last few versions of Ubuntu I used, this all worked fine. In Ubuntu 17.10 (fresh install, not upgrade) I can access hosts on both my VPN network and the internet, BUT I have to use FQDN for my VPN network hosts: the updates to the DNS search path provided by my VPN DHCP server are never being applied. Investigating the system I see that /etc/resolv.conf is pointing to /run/systemd/resolve/stub-resolv.conf and that resolv.conf does not have any of the VPN's search path settings in it: # This file is managed by man:systemd-resolved(8). Do not edit. # # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 127.0.0.53 search home In previous versions of Ubuntu, where NetworkManager controlled the resolver not systemd, /etc/resolv.conf pointed to /run/NetworkManager/resolv.conf and there was a local dnsmasq instance that managed all the complexity. In Ubuntu 17.10 when I look in /run/NetworkManager/resolv.conf file, I see that the search paths ARE properly updated there: $ cat /run/NetworkManager/resolv.conf # Generated by NetworkManager search internal.mycorp.com other.mycorp.com home nameserver 127.0.1.1 However this file isn't being used, and also there's no dnsmasq running on the system so if I switch my /etc/resolv.conf to point to this file instead, then all lookups fail. Strangely, if I look at the systemd-resolv status I see that in theory systemd-resolve does seem to know about the proper search paths: $ systemd-resolve --status ... Link 3 (tun0) Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 10.3.0.10 10.8.42.2 DNS Domain: ~internal.mycorp.com ~other.mycorp.com but for whatever reason the search domains are not getting put into the resolv.conf file: $ host mydesk ;; connection timed out; no servers could be reached $ host mydesk.internal.mycorp.com mydesk.internal.mycorp.com has address 10.8.37.74 (BTW, the timeout in the failed attempt above takes 10s: it is SUPER frustrating when all your host lookups are taking that long just to fail). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Oct 22 15:08:57 2017 InstallationDate: Installed on 2017-10-21 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic root=UUID=4384306c-5fed-4b48-97a6-a6d594c4f72b ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2101:bd12/02/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-M/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- 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/1726124 Title: DNS domain search paths not updated when VPN started To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1726124/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1518988] Re: Switching from "Plain Text" to "HTML" mode in Evolution composer keeps fixed width font
I tested evolution 3.16.5-1ubuntu3.1 and the problem has been resolved. Thanks! ** 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 evolution in Ubuntu. https://bugs.launchpad.net/bugs/1518988 Title: Switching from "Plain Text" to "HTML" mode in Evolution composer keeps fixed width font To manage notifications about this bug go to: https://bugs.launchpad.net/evolution/+bug/1518988/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1518988] [NEW] Switching from "Plain Text" to "HTML" mode in Evolution composer keeps fixed width font
Public bug reported: I'm using Evolution 3.16.5-1ubuntu3 in Ubuntu GNOME 15.10, latest packages. My email starts by default in Plain Text mode. However sometimes I want to switch to "HTML" mode. When I do this, I get HTML-formatted email HOWEVER no matter what I do my font is still always fixed-width and never proportional. I can change the size, the slant, etc. but it's always fixed-width. After discussing this on the Evolution mailing lists https://mail.gnome.org/archives/evolution- list/2015-November/msg00112.html it appears this is a bug that was fixed in 3.18. However, the fix looks simple to backport: please consider pulling this into Ubuntu 15.10 version of Evolution to fix this extremely annoying problem: https://bugzilla.gnome.org/show_bug.cgi?id=753702 Fixed with this commit: https://git.gnome.org/browse/evolution/commit/?id=8aa930e0634b22afa38753816be824d7b1622140 ** Affects: evolution Importance: Unknown Status: Unknown ** Affects: evolution (Ubuntu) Importance: Undecided Status: New ** Bug watch added: GNOME Bug Tracker #753702 https://bugzilla.gnome.org/show_bug.cgi?id=753702 ** Also affects: evolution via https://bugzilla.gnome.org/show_bug.cgi?id=753702 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1518988 Title: Switching from "Plain Text" to "HTML" mode in Evolution composer keeps fixed width font To manage notifications about this bug go to: https://bugs.launchpad.net/evolution/+bug/1518988/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1247366] Re: Evolution is missing bogofilter integration
Thank you Iain! Is there any possibility this can get backported to 14.04? As an LTS release, it would be REALLY nice to have this fix there too... I think this patch applies cleanly to 3.11 as well as 3.12. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1247366 Title: Evolution is missing bogofilter integration To manage notifications about this bug go to: https://bugs.launchpad.net/evolution/+bug/1247366/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1247366] Re: Evolution is missing bogofilter integration
If you know of another way, than filing a bug like this one, I urge you to pursue it... ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1247366 Title: Evolution is missing bogofilter integration To manage notifications about this bug go to: https://bugs.launchpad.net/evolution/+bug/1247366/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1247366] Re: Evolution is missing bogofilter integration
Well, first it has to get fixed in Ubuntu, in any version: currently there's no fix even in the upcoming 15.04. Once that happens we can talk about whether it's possible to backport it. ** Tags removed: patch -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1247366 Title: Evolution is missing bogofilter integration To manage notifications about this bug go to: https://bugs.launchpad.net/evolution/+bug/1247366/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1247366] Re: Evolution is missing bogofilter integration
Just for completeness I'm adding the patch used to fix this issue upstream. ** Patch added: Patch for Gnome bug 1247366 https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1247366/+attachment/4331521/+files/bug-1247366.patch -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1247366 Title: Evolution is missing bogofilter integration To manage notifications about this bug go to: https://bugs.launchpad.net/evolution/+bug/1247366/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1247366] Re: Evolution is missing bogofilter integration
Milan Crha has posted a fix for the next release of Evolution, which may or may not be straightforward to cherry-pick back to the current release. See: https://bugzilla.gnome.org/show_bug.cgi?id=743109 and: https://git.gnome.org/browse/evolution/commit/?id=0b91d60 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1247366 Title: Evolution is missing bogofilter integration To manage notifications about this bug go to: https://bugs.launchpad.net/evolution/+bug/1247366/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1247366] Re: Evolution is missing bogofilter integration
Hm. It seems that newer versions of Evolution have completely removed support for runtime detection of the underlying spam filtering facility in the plugin, so my simple patch in comment #18 is not sufficient and more work is needed. See https://bugzilla.gnome.org/show_bug.cgi?id=743109 for more information. ** Bug watch added: GNOME Bug Tracker #743109 https://bugzilla.gnome.org/show_bug.cgi?id=743109 ** Also affects: evolution via https://bugzilla.gnome.org/show_bug.cgi?id=743109 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1247366 Title: Evolution is missing bogofilter integration To manage notifications about this bug go to: https://bugs.launchpad.net/evolution/+bug/1247366/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1247366] Re: Evolution is missing bogofilter integration
I believe this can be fixed with a simple patch to the rules file in the Evolution Ubuntu package: if we set the BOGOFILTER environment variable before we run configure then whatever value it has will be used during the build without checking, and at runtime if the program exists the plugin will be enabled (and if not it won't be). ** Patch added: Enable bogofilter plugin for Evolution https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1247366/+attachment/4298600/+files/evo-bogofilter.patch -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1247366 Title: Evolution is missing bogofilter integration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1247366/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1247366] Re: Evolution is missing bogofilter integration
For more info from the Evo developer: https://mail.gnome.org/archives /evolution-list/2014-May/msg00010.html -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1247366 Title: Evolution is missing bogofilter integration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1247366/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1247366] Re: Evolution is missing bogofilter integration
Please add this support! I see no point in omitting it; it's just a configure flag (and having bogofilter installed at build time). Bogofilter is much nicer than SA IMO. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1247366 Title: Evolution is missing bogofilter integration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1247366/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1062693] Re: GDM Simple Greeter No Longer Responds to Gconf-editor or Gconftool-2
** Changed in: gdm (Ubuntu) Status: New = Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/gdm/+question/210608 -- 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/1062693 Title: GDM Simple Greeter No Longer Responds to Gconf-editor or Gconftool-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1062693/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1062693] [NEW] GDM Simple Greeter No Longer Responds to Gconf-editor or Gconftool-2
Public bug reported: Using 12.04.1 I can no longer display a login warning banner or disable the user list in simple-greeter either by using gconf-editor or gconftool-2. Works in 10.04.4. Steps to Replicate: 1) Install GDM: sudo apt-get install gdm 2) Use the following script: -- #!/bin/bash sudo -u gdm gconftool-2 --set --type boolean /apps/gdm/simple-greeter/disable_user_list true sudo -u gdm gconftool-2 --set --type boolean /apps/gdm/simple-greeter/banner_message_enable true sudo -u gdm gconftool-2 --set --type string /apps/gdm/simple-greeter/banner_message_text W A R N I N G * THIS IS A PRIVATE COMPUTER SYSTEM. This computer system is provided only for authorized use. Uses of this system, authorized or unauthorized, constitutes consent to monitoring. This system may be monitored for all lawful purposes, including to ensure it's use is authorized, for management of the system, to facilitate protection against unauthorized access, and to verify security procedures, survivability and operational security. Monitoring includes active attacks by authorized personnel and their entities to test or verify the security of the system. During monitoring, information may be examined,recorded, copied and used for authorized purposes. All information including personal information, placed on or sent over this system may be monitored. Unauthorized use may subject you to criminal prosecution. Evidence of any such unauthorized use collected during monitoring may be used for administrative, criminal or other adverse action. sudo gconftool-2 --set --type string /apps/gdm/simple-greeter/banner_message_text_nochooser W A R N I N G * THIS IS A PRIVATE COMPUTER SYSTEM. This computer system is provided only for authorized use. Uses of this system, authorized or unauthorized, constitutes consent to monitoring. This system may be monitored for all lawful purposes, including to ensure it's use is authorized, for management of the system, to facilitate protection against unauthorized access, and to verify security procedures, survivability and operational security. Monitoring includes active attacks by authorized personnel and their entities to test or verify the security of the system. During monitoring, information may be examined,recorded, copied and used for authorized purposes. All information including personal information, placed on or sent over this system may be monitored. Unauthorized use may subject you to criminal prosecution. Evidence of any such unauthorized use collected during monitoring may be used for administrative, criminal or other adverse action. -- Other Package Versions: gconf2: Installed: 3.2.5-0ubuntu2 Candidate: 3.2.5-0ubuntu2 Version table: *** 3.2.5-0ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gdm 3.0.4-0ubuntu15 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic-pae 3.2.28 Uname: Linux 3.2.0-31-generic-pae i686 ApportVersion: 2.0.1-0ubuntu13 Architecture: i386 Date: Sat Oct 6 01:26:56 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423.2) ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdm (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 precise running-unity -- 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/1062693 Title: GDM Simple Greeter No Longer Responds to Gconf-editor or Gconftool-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1062693/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1062693] Re: GDM Simple Greeter No Longer Responds to Gconf-editor or Gconftool-2
** Description changed: Using 12.04.1 I can no longer display a login warning banner or disable the user list in simple-greeter either by using gconf-editor or gconftool-2. Works in 10.04.4. Steps to Replicate: 1) Install GDM: sudo apt-get install gdm 2) Use the following script: -- #!/bin/bash sudo -u gdm gconftool-2 --set --type boolean /apps/gdm/simple-greeter/disable_user_list true sudo -u gdm gconftool-2 --set --type boolean /apps/gdm/simple-greeter/banner_message_enable true sudo -u gdm gconftool-2 --set --type string /apps/gdm/simple-greeter/banner_message_text W A R N I N G * THIS IS A PRIVATE COMPUTER SYSTEM. This computer system is provided only for authorized use. Uses of this system, authorized or unauthorized, constitutes consent to monitoring. This system may be monitored for all lawful purposes, including to ensure it's use is authorized, for management of the system, to facilitate protection against unauthorized access, and to verify security procedures, survivability and operational security. Monitoring includes active attacks by authorized personnel and their entities to test or verify the security of the system. During monitoring, information may be examined,recorded, copied and used for authorized purposes. All information including personal information, placed on or sent over this system may be monitored. Unauthorized use may subject you to criminal prosecution. Evidence of any such unauthorized use collected during monitoring may be used for administrative, criminal or other adverse action. sudo gconftool-2 --set --type string /apps/gdm/simple-greeter/banner_message_text_nochooser W A R N I N G * THIS IS A PRIVATE COMPUTER SYSTEM. This computer system is provided only for authorized use. Uses of this system, authorized or unauthorized, constitutes consent to monitoring. This system may be monitored for all lawful purposes, including to ensure it's use is authorized, for management of the system, to facilitate protection against unauthorized access, and to verify security procedures, survivability and operational security. Monitoring includes active attacks by authorized personnel and their entities to test or verify the security of the system. During monitoring, information may be examined,recorded, copied and used for authorized purposes. All information including personal information, placed on or sent over this system may be monitored. Unauthorized use may subject you to criminal prosecution. Evidence of any such unauthorized use collected during monitoring may be used for administrative, criminal or other adverse action. -- - Package Versions: - - gdm: - Installed: 3.0.4-0ubuntu15 - Candidate: 3.0.4-0ubuntu15 - Version table: - *** 3.0.4-0ubuntu15 0 - 500 http://us.archive.ubuntu.com/ubuntu/ precise/universe i386 Packages - 100 /var/lib/dpkg/status + Other Package Versions: gconf2: - Installed: 3.2.5-0ubuntu2 - Candidate: 3.2.5-0ubuntu2 - Version table: - *** 3.2.5-0ubuntu2 0 - 500 http://us.archive.ubuntu.com/ubuntu/ precise/main i386 Packages - 100 /var/lib/dpkg/status + Installed: 3.2.5-0ubuntu2 + Candidate: 3.2.5-0ubuntu2 + Version table: + *** 3.2.5-0ubuntu2 0 + 500 http://us.archive.ubuntu.com/ubuntu/ precise/main i386 Packages + 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gdm 3.0.4-0ubuntu15 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic-pae 3.2.28 Uname: Linux 3.2.0-31-generic-pae i686 ApportVersion: 2.0.1-0ubuntu13 Architecture: i386 Date: Sat Oct 6 01:26:56 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423.2) ProcEnviron: - LANGUAGE=en_US:en - TERM=xterm - PATH=(custom, no user) - LANG=en_US.UTF-8 - SHELL=/bin/bash + LANGUAGE=en_US:en + TERM=xterm + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: gdm UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1062693 Title: GDM Simple Greeter No Longer Responds to Gconf-editor or Gconftool-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1062693/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 999691] [NEW] Tab to cancel selects OK instead
Public bug reported: If I start a zenity window with a text box: zenity --entry --text=add text then I press TAB one time to highlight the Cancel box and press ENTER to select Cancel, it instead selects OK. In fact no matter what element is selected in the zenity window, when I press ENTER it selects OK. Only by physically clicking on the Cancel box can I cancel. This misbehavior is potentially (depending on what question was being asked and what the action to be taken is) extremely dangerous. $ uname -rm 3.2.0-24-generic x86_64 $ lsb_release -rd Description:Ubuntu 12.04 LTS Release:12.04 $ apt-cache policy zenity zenity: Installed: 3.4.0-0ubuntu4 Candidate: 3.4.0-0ubuntu4 Version table: *** 3.4.0-0ubuntu4 0 500 http://us.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.4.0-0ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages ** Affects: zenity (Ubuntu) Importance: Undecided Status: New -- 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/999691 Title: Tab to cancel selects OK instead To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zenity/+bug/999691/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 990594] [NEW] No way to exit part mode in Rhythmbox
Public bug reported: I was messing around with Rhythmbox in Ubuntu 12.04 trying to get a display I liked. I saw Party Mode under the View menu and selected it to see what it was. I got a full-screen instance of Rhythmbox with NO WAY TO EXIT! No menus were available, no keys like ESC etc. worked to revert to regular mode. I could bring up the dash with the hotkey (Super) or use alt-tab etc. to ask to switch windows but none of that changed the display: Rhythmbox still took up the entire screen. I could find no way to get rid of it except resorting to CTRL-ALT-F1, logging on the console, using ps to find the PID and kill it. If I wasn't knowledgeable enough to do that, I guess my only option would be to use the power button on my system!! That can't be right. If Rhythmbox is going to be the official music player in Ubuntu someone needs to do some work to get it to integrate better into Unity. At the very least you should remove this menu item until such time as it can be made to work properly. ~$ apt-cache policy rhythmbox rhythmbox: Installed: 2.96-0ubuntu4 Candidate: 2.96-0ubuntu4 Version table: *** 2.96-0ubuntu4 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages 100 /var/lib/dpkg/status ~$ lsb_release -rd Description:Ubuntu 12.04 LTS Release:12.04 ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/990594 Title: No way to exit part mode in Rhythmbox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/990594/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 365270] Re: Move is Copy + Thrash, should be Move that removes all traces of the first.
It would be good if people could be explicit about what version of Evolution they're using AND (more importantly) what type of email server they're connecting to. Evolution has to interact with them differently (because the services have different capabilities). Are you using locally-delivered email to a local mailbox, as Knut seems to be? Are you connecting to an ISP mail provider using POP? Using IMAP? Are you connecting to Google mail? Are you connecting to an Exchange server? Something else? In short, please go to your email account (Edit-Preferences-Mail Accounts) and click the Recieving Mail tab and tell use what the Server Type setting is. I'm only speaking about connecting to IMAP servers here; I'm also familiar with Evolution connecting to Exchange servers but that works very differently. I've not used local mail delivery or POP (which work similarly to each other) in many years. In IMAP, there is no way that the current behavior of Evolution will lose mail in the way Knut suggests. A move operation is implemented as a copy and after the copy succeeds, the original is marked as deleted by setting a flag. No mail is actually removed from any folder during this operation and so no mail can be lost. In fact that is what typically generates complaints: that your trash folder has EXTRA mail in it that you didn't expect. Sometime later you will initiate an Expunge operation and that will go through your folders and remove emails that are marked as deleted. This operation is performed by the IMAP server, not Evolution (all Evolution does is send a single expunge command) in an atomic way so that it does not cause any mail loss (unless there's a bug in the IMAP server but there's nothing Evolution can do about that, and switching to a different mail client will not help). During Expunge, if you have an email that is marked deleted that you didn't actually want to be deleted then yes, it will be lost. But only mail marked deleted is gone: if you'd copied it to another folder and that copy is not marked for deletion, then the copy is still present. One way people using IMAP with Evolution can get frustrated is if they tend to store things in their Trash folder; they want to use Trash as a kind of longer-term storage folder. You definitely cannot do that with Evolution; you need to choose a different folder and put things you want to save there. FYI, Thunderbird connecting to an IMAP server has the same issues that Evolution does: they have to because an IMAP server only publishes a certain interface and all clients have to use the same interface. What Thunderbird does differently is it runs the Expunge operation for you all the time in the background. So, when you move mail in Thunderbird it does the same copy and mark as deleted operation that Evolution does, but then it also automatically runs Expunge so that the extra deleted copy is gone. When you delete mail in Thunderbird it actually moves (copy, mark as deleted, expunge) the email to a real folder (sometimes named Trash). Thus expunging doesn't cause that mail to go away, you have to delete it specifically from the Trash folder. Trevor: I'm sorry that you lost an important mail. It would be helpful if you could describe in detail the steps which caused the mail to be lost. There's nothing unsafe about the algorithm Evolution uses to move or delete mail--that is, there is no race condition, etc. in the design that could cause mail to be lost. However, all software has bugs and Evolution is no exception. It's possible that you've run across a bug and if so I'm sure the Evolution developers would like to fix it. In order to fix it they need more specific information on what happened. -- Move is Copy + Thrash, should be Move that removes all traces of the first. https://bugs.launchpad.net/bugs/365270 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 356702] Re: Tooltips stick when switching desktops (Compiz)
Re: Sam Spilsbury: This absolutely is a bug. Regardless of whether tooltips are marked sticky or not, they are obviously supposed to be transient. This bug says that in some fairly common circumstances, the tooltip shows up for the workspace switcher and then it NEVER GOES AWAY (unless you switch to another workspace again). I've never seen a tooltip that didn't go away after a short time, and any such tooltip is obviously buggy. I don't know where the problem lies exactly: maybe an event is missed, maybe something else, but this is unquestionably a bug. -- Tooltips stick when switching desktops (Compiz) https://bugs.launchpad.net/bugs/356702 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 365270] Re: Move is Copy + Thrash, should be Move that removes all traces of the first.
Knut: your comments reveal a relatively shallow understanding of the email environment. And they show you haven't understood the real situation with Evolution. As for discussions of how IMAP servers ought to work, you should be filing those bugs with the teams that create the IMAP servers; I'm sure they'll welcome your input. The comments around moving files into/out of Trash shows you haven't read the various discussions of the problem (even to bugs marked as duplicates in Gnome Bugzilla). There is no real Trash folder in Evolution, so there is no move or copy of email from any other folder into Trash. Trash is a virtual folder: it doesn't exist physically, but instead is constructed as a user-interface artifact, containing all the messages that are marked as deleted. Thus, to delete a message (have it appear in Trash) all that has to be done is mark that message as deleted. To undelete a message, you just remove the deleted attribute and it reappears exactly where it was before... because it was never moved anywhere else. There is no copy involved with delete, no extra space consumed, etc. And similarly, there is no copy involved with undelete either. This is why messages appear in Trash when you move them to another folder: as I've described there is no MOVE operation in IMAP, so a MOVE must be implemented as a COPY followed by a delete. When you mark a message deleted that message appears in the Trash folder. I do understand Mathias's frustration, but unfortunately it's not so simple. Mathias you suggest it's just a matter of Evolution hiding these details, but that cannot be done reliably. There is only one delete flag in IMAP, so there is no way to make a distinction on the server between messages that are deleted by hand, and those that are deleted as a side-effect of a desired move operation. They are identical as far as any IMAP client is concerned. Yes, of course, Evolution could maintain its own local list of messages that should be hidden rather than displayed in Trash because they are a side-effect of a copy/delete. However this list would be present only in that instance of Evolution. If you ever attached to your IMAP server using a different Evolution (say on a laptop or work system), or you used a webmail client or another IMAP client (maybe on your smart phone, etc.), all those extra deleted messages WOULD appear there, and you'd have even more confusion and bugs reported. -- Move is Copy + Thrash, should be Move that removes all traces of the first. https://bugs.launchpad.net/bugs/365270 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 365270] Re: Move is Copy + Thrash, should be Move that removes all traces of the first.
Ayeyiyi. Knut, please stop trying to impress everyone with your credentials and consider that you might actually not know everything about everything quite yet, regardless of how much you know about databases. I've been programming on UNIX since before POSIX even existed and I certainly understand the concepts quite well. I'll post one last message in the hopes that others reading this will understand what's going on, at least. Since you've done a lot of DB work apparently, consider Evolution as if it were a generic open source SQL client program that can connect to lots of different types of SQL servers: Oracle, Postgres, MySQL, etc. The data is left on the server (for at least some of the protocols) and the client only provides access to the data. The client can only perform the operations that the server makes available: you can't perform Oracle-specific SQL commands on a Postgres server, etc. Suppose this client could also access databases that are local and don't have a server (sqlite databases maybe). That's a good analogy for what Evolution is. You didn't tell us what kind of server you're trying to talk to but people are assuming IMAP so I will too. If you're using something different let us know: that would be very helpful information. First, SMTP is a mail *transfer* protocol. It defines the network protocol for two mail *servers* (e.g., sendmail etc.) to talk to each other to exchange mail. In SMTP parlance these are known as MTAs, or Mail Transfer Agents. Evolution is NOT an MTA. Evolution is a Mail User Agent (MUA). The SMTP standard has virtually nothing to say about the protocol that MUA's use to talk to MTA's. In short, Evolution has virtually nothing to do with with SMTP at all (Evolution has the ability to connect directly to MTA's to _send_ mail, but it cannot, and neither does any other client, use SMTP at all when _reading_ mail, as we are discussing in this bug). Second, Evolution as an email client actually can use lots of different methods to retrieve email. It can get mail from a POP server, from an IMAP server, from a Microsoft Exchange server, or from a Novell Groupwise server. It can even read from USENET. And, of course, it can read from local mail spool files of various types. One of these types is the traditional UNIX mail spool that sendmail uses, and others are spool files left by other types of local software. Each of these uses a different protocol for getting mail. Third, Evolution does not implement the server software, at all. If you connect to a POP server then someone else wrote that POP server. It may not even be free software at all; your ISP (that you download your email from) decides all that. Ditto for all the other ways Evolution gets email. Even the local spool files are created by other software such as sendmail, etc., that Evolution has no control over. Fourth, for a number of those server types, including IMAP, Exchange, Groupwise, etc., Evolution does not manage your email locally. The email is left on the server and Evolution sends commands to the server to ask it to manipulate your email. This is what I mean when I say that the IMAP protocol doesn't support MOVE: you don't have a local copy of the email so only the server can manipulate it, and you can only ask the server to perform the commands that it supports. With other types of mailbox, such as local mail spools and POP servers, Evolution downloads your mail to your local system and manipulates it there. Obviously in these environments Evolution has a lot more flexibility in the operations it can perform. Finally, WRT searching, searching is very safe, at least in IMAP. Every addition to an email folder only ever adds to the end of the folder, never inserts in the middle, and every new message number is higher than any other message number (for that folder) that has been used before so there's never duplication. Every change to the folder is atomic (you don't get half a message added, or half an expunge performed). Every search starts at the beginning of the folder and goes to the end by first finding the current maximum message ID, then going through the folder message by message (ignoring missing messages) until that maximum is reached. If new items have been added since the search started they will have larger message IDs and are not seen for that search. Alternatively sometimes the client asks the server for a complete list of message IDs, then goes through that list. In any event, it's never a problem to have new messages added during searches. -- Move is Copy + Thrash, should be Move that removes all traces of the first. https://bugs.launchpad.net/bugs/365270 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 365270] Re: Move is Copy + Thrash, should be Move that removes all traces of the first.
I'm loathe to get involved here since Knut seems intent on flaming and not so interested in understanding, but reading the comments here I've been struck by a great attention to irrelevant details and not much clear description of the real issue. Knut continually makes reference to a MOVE operation, as if such a thing existed. But it doesn't. If it did, you can be sure that Evolution would use it. Why can't Evolution create that operation? Because Evolution is a mail CLIENT. It talks to mail SERVERS. Evolution does not implement and cannot influence the servers. The only operations that the client can perform are those that the server supports. The servers implement the IMAP standard, and the IMAP standard does not define a MOVE operation. So, no IMAP server supports a MOVE operation, and so no IMAP client can use a MOVE operation. So good, there's no MOVE operation. The only way an IMAP client can effect a move from one folder to another is by first doing a COPY, then marking the original message as deleted, and this is what Evolution and ALL OTHER IMAP CLIENTS (yes, including Thunderbird) do. That by itself is enough to blunt some of Knut's criticisms, since no client will ever be able to avoid the creation of a new message via the COPY command. Similarly, the IMAP standard does not provide any way to delete a single message. The ONLY way to actually cause messages to disappear out of an IMAP folder is by an EXPUNGE, which takes all the messages that have been marked as deleted and removes them (not just one, but ALL of them). This is a very expensive operation, typically, for your server (as opposed to marking a message as deleted which is typically very fast). After the expunge is done, then often the client has to re-read and re- index the messages, because its local cache of which messages are marked deleted and which aren't might be wrong. The whole thing is very labor intensive on both the client and server, as well as the network. Evolution works the way that the IMAP standard writers intended clients to work: it hides deleted messages and leaves the decision about when to expunge them up to the user. The problem is that many other clients don't work like this. They don't hide the deleted messages, which leads to lots of confusion about duplicated messages, and they also expunge messages for you. For example other IMAP clients implement the semantics of MOVE by doing a COPY, marking the original as deleted, then running EXPUNGE. For every single email you delete. This is a big load on both clients and servers, AND it means that your email that you might have deleted but not wanted expunged yet, is deleted for you. This is a shame because if all clients worked the way the standard expected them to then they'd work together well. However, just like Evolution cannot change the way servers work, so it cannot change the way other clients work. So, or course Evolution should have an option to behave the way other clients do and have a physical trash folder and implement the COPY/delete/EXPUNGE semantics that other clients favor. You won't need this if you only ever use Evolution as a client but if you switch between different clients you may need it, and Evolution should provide that support. I believe they intend to but obviously this is a low priority, based on how long these bugs have been open. That's definitely a shame. As for Knut's other comments, he implies above that he read and understood the RFC Marc mentioned but that is clearly not the case. There's no such thing as cardinality of indexes in email, and there's no chance that searches will skip anything. When you do the COPY the message number on the copy is the next number in a monotonically increasing index, it is NOT inserted into the middle. When you EXPUNGE all deleted messages disappear and their numbers are gone, and NEVER re-used. There is no chance for confusion of duplicate message numbers, etc. during sorting or searching. -- Move is Copy + Thrash, should be Move that removes all traces of the first. https://bugs.launchpad.net/bugs/365270 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 497578] [NEW] Workspace switcher shows tooltips constantly that won't disappear
Public bug reported: Binary package hint: gnome-panel Since I've upgraded to Ubuntu 9.10, I've noticed that the tooltips in the workspace switcher that show the name of the selected window (Click to start dragging ...) will sometimes not go away. It seems to happen most if I use the mouse to click on a different screen in the switcher, then move my mouse right away (but not RIGHT away--just about the time it normally takes me to move my mouse away, apparently) out of the switcher into the normal desktop. In that case the tooltip that the switcher pops up does not go away again: it's like some event was missed or something. The tooltip will stay there forever until I (a) switch to another desktop with CTRL- ALT-arrow or similar, or (b) move my mouse over either the upper or lower panel (any part of it). Just selecting a different window on the same screen doesn't cause the tooltip to go away. It's very frustrating because it happens probably 80% of the time that I use my mouse to choose a different screen, and I have my screens organized by work activity and I'm often switching back and forth. It sounds minor but it's extremely annoying to have these yellow tooltips showing up and not going away unless I go do something. If anyone has any suggestions about ways I could narrow down the problem, etc. I'm intereested!! I'm running Ubuntu 9.10 64bit, with Workspace Switcher 2.28.0. ** Affects: gnome-panel (Ubuntu) Importance: Undecided Status: New -- Workspace switcher shows tooltips constantly that won't disappear https://bugs.launchpad.net/bugs/497578 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 13983] Re: Evolution virtual trash / real trash on IMAP server
Sebastien is correct that Carl's message is missing information. Evo most definitely DOES mark messages as deleted and does NOT expunge them (unless you use the Expunge action of course; the keybinding for this is CTRL-E so it's possible Carl hit it by accident). The entire concept of storing your email in your main INBOX, marked as deleted, but wanting to keep it around, is fraught with danger--it takes only a slip of a finger to delete all those messages. Hopefully Carl will choose a more reliable and less dangerous method of storing wanted email in the future, such as moving it to a folder: that's why people use IMAP after all, for the folder support. I don't know about the search feature issue; if it's a feature of only newer IMAP servers it's possible Evo doesn't support it. However, I don't think Sebastien's characterization of the bug is correct either. People don't want delete to erase emails. What this bug is asking for is that delete should actually move the emails to another physical folder on the IMAP server, rather than what it does now, which is mark the email as deleted on the server (and make it visible in the virtual folder Trash). Just to be clear, the way Evo works is the way the IMAP standard intends IMAP to be used. There is absolutely no question about that. I don't understand Busby's comment: I think he's just raising a straw man. The way the IMAP standard intended email moves to be done is exactly how Evo does it: you copy the message to the target folder, then mark the original for deletion. IMAP is a very problematic protocol, because it lets the underlying implementation, which is often counter-intuitive to people, show through into the standard. This not only means that the behavior of the server (what things are easy and what things are hard) is visible through the protocol, but it also biases the implementation in various ways. For example, IMAP assumes that it's very difficult to delete messages from a folder: this is because many implementations of mail servers keep all mail in a given folder in one long file: deleting a message out of the file involves rewriting the whole file... and even for medium-sized folders that's expensive. Even if your IMAP server implementation used something more intelligent such as one file per email with directories for folders, or if it used a database backend, or whatever, so that deletes are cheap, the IMAP standard carries with it the baggage of the early implementations. This also proscribes the way IMAP is intended to be used. The model IMAP intends is that you save up your deletions for a while, then do them all in bulk. Thus, the standard creates a /deleted flag (flags are typically kept in a metadata file or even a database on the server, that is much cheaper to manipulate than the very large raw email file). The idea is you delete messages, and copy-then-delete messages, etc. and at the end of these operations you run the expunge command and all those deletes finally take effect. The model is that you run expunge regularly (maybe every time you exit your mail client, or maybe after every session of using email), but NOT after every single delete or copy operation (TB by default does it this way). The way Evo works is perfectly in line with the standard. The standard assumes that the client has some intelligence behind the way it handles messages marked with the /Deleted flag. Evo uses a virtual folder for this (I understand and agree with the issues of the virtual folder hiding real folders with the same name: that's truly a bug). I've used lots of IMAP clients and I've never seen one that didn't offer some kind of Hide deleted messages by default option. Maybe there are such out there, and if so that definitely sucks for people forced to use them. Also apparently there are servers that overload the /Deleted flag for other purposes that are not compliant with the standard, such as spam, which also sucks (of course it really sucks that IMAP was developed without, and has not been enhanced to provide, any support for managing spam directly). If people want to use Evo, regardless of whether you use it by itself or with other email clients, you have to get into the habit of expunging regularly (not after every delete, mind you, but _regularly_). If you do that, then switching to a different client will be no problem. I do it all the time with various different webmail and other IMAP clients, including Evo, and I never have any issues. If you don't expunge regularly, then nothing works well. You can say it's Evo's fault, but it's not really: that's the way IMAP was designed to be used and that's the best way to use it. All that being said, I'm definitely a fan of choice and I'd dearly love for someone to implement a solution that lets the other side, who can't or won't use IMAP as designed for whatever reason, have what they want (if nothing else so we don't have to have this conversation every few frakking
[Bug 173350] Re: Caps lock LED changes state even when caps lock is mapped to ctrl
All my Hardy systems still have this problem. My one Intrepid system doesn't. Please be clear what release you're using when reporting issues. -- Caps lock LED changes state even when caps lock is mapped to ctrl https://bugs.launchpad.net/bugs/173350 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 236871] Re: seahorse-agent won't accept ssh passphrase if stdin is /dev/null
This is working for me in Hardy now. Some weeks after I reported this, it started working. Some package I updated (not sure which one) caused it to work again. -- seahorse-agent won't accept ssh passphrase if stdin is /dev/null https://bugs.launchpad.net/bugs/236871 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 210468] Re: try to access a .Trash-$USER directory on autofs mounts
I can also verify that this fixes the problem of extra Trash messages. I also have to say that I haven't seen the hang issue since I applied my changes, either. Don't know if it's a coincidence, but I'm happy! -- try to access a .Trash-$USER directory on autofs mounts https://bugs.launchpad.net/bugs/210468 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is the registrant for gvfs. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 210468] Re: try to access a .Trash-$USER directory on autofs mounts
If the messages have stopped appearing in your logs, then the problem you're having is clearly not related to this bug, since this bug is about autofs .Trash requests. Bug comments are not really the best way to ask for help, unless it's about the bug in question. You should either file a bug against the package which appears to be at fault here, which would be either Nautilus or autofs (do you get the same behavior when you try to access the automount from the command line? That should tell you which package is likely at fault), or else maybe ask on the Ubuntu user forums. When you do find the right place to ask, be sure to give more information about exactly which versions you're using, how your automount maps are distributed, what they contain (for example the map that contains the directory you're trying to access via Nautilus), whether it happens every single time or only when the filesystem is not mounted already (or only if you try to re-access the filesystem after automount has unmounted it), etc. -- try to access a .Trash-$USER directory on autofs mounts https://bugs.launchpad.net/bugs/210468 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is the registrant for gvfs. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 212098] Re: easy file sharing not notifying about logout/login
I understand that modifying groups requires a logout (although I've been hacking UNIX for 20+ years and I still don't really understand why that's true). But it's monumentally sucky to have to log out, even if there's some dialog that tells you you need to do it. I don't see why nautilus-share cannot be included as part of the base distribution so that this is not necessary. But, if it indeed cannot be, then maybe we should change the base package to add the sambashare group, even though it's not used by any packages until nautilus-share is installed. User accounts can be added to that group as they would be other groups, when the user account is created. This would fix the need to log out/in due to group updates. -- easy file sharing not notifying about logout/login https://bugs.launchpad.net/bugs/212098 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 210468] Re: try to access a .Trash-$USER directory on autofs mounts
Hi Sebastien; not sure what this means, to be uploaded as a hardy update candidate... I haven't seen anything come through in my -proposed repository. Or is this a prelude to that? I guess someone will update the bug if/when the fix migrates into the repositories? Thanks. -- try to access a .Trash-$USER directory on autofs mounts https://bugs.launchpad.net/bugs/210468 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is the registrant for gvfs. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 210468] Re: try to access a .Trash-$USER directory on autofs mounts
Thanks Etienne. Someday I'm going to learn how to use Launchpad PPA! As for the fix, I'll say this: first, the concept behind the patch is unquestionably 100% correct. As you point out, it's fundamentally wrong to look for .Trash directories in automount points, because they aren't real directories. It's like trying to look for /proc/.Trash or /sys/.Trash or something... except worse because this lookup actually does more than just fail with ENOENT. Second, I'm 99% sure that the patch does do what I expected it to do, and that it works properly. I'm definitely no expert in glib but this change seems very straightforward. Third, as I mentioned above I'm confident that this is not the most elegant way to solve the problem. However, it may be worthwhile to keep this as an Ubuntu patch, even if upstream Gnome folks don't want to apply it there, until they work out and implement the more elegant solution. -- try to access a .Trash-$USER directory on autofs mounts https://bugs.launchpad.net/bugs/210468 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is the registrant for gvfs. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 210468] Re: try to access a .Trash-$USER directory on autofs mounts
Here is a bog-simple patch I created for gvfs-0.2.4 that skips any root directory with a filesystem type of autofs. To my mind this is just a workaround: the real answer is that the list of filesystem types to skip should be configurable, I presume via an entry in gconf. However, that involves a LOT more work in code I'm not familiar with and this fix is easy. This has been working for me for the day so far: no messages in the log file. I really wanted to do this because I've been seeing a problem where, every few days, my system gets sluggish, NFS mounts hang, FireFox downloads hang, etc. I don't know what's going on (nothing much in the logs) but the one thing all these situations have in common is when I do ps I see 25-30 instances of gvfsd-trash running instead of one. The only thing concerning in the logs are these .Trash references. I have no other proof that these things are related but I figured I'd fix this one and we'll see if it helps. ** Attachment added: Simple change to ignore autofs filesystem types http://launchpadlibrarian.net/15482595/gvfsbackendtrash.diff -- try to access a .Trash-$USER directory on autofs mounts https://bugs.launchpad.net/bugs/210468 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is the registrant for gvfs. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 160264] Re: [nvidia] compiz displays white screen when locked
I can confirm that when I use fast user switch with the new drivers in hardy-proposed I don't get the white screen where I can't see the login window. I get a black screen with a login window visible, as expected. -- [nvidia] compiz displays white screen when locked https://bugs.launchpad.net/bugs/160264 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 210468] Re: try to access a .Trash-$USER directory on autofs mounts
I'm seeing this too, and something about it is causing my system to hang. Basically, when I come in the morning I can't do hardly anything, including reboot. Investigation has shown that it's because any attempt to read the /proc/mounts file causes a permanent hang on the process (can't even kill -9 etc.). Lots and lots of programs, even ones like ls, try to read this file. I have to power-cycle the system to recover. My system load is above 7, even though my CPU usage is negligible (a sure sign that processes are hung in the kernel). Last night I started a script that ran date, then cat /proc/mounts, then sleep 15 and left it running all night. I got the hang at 22:51 and looking through my logs, sure enough right at that exact time I saw a slew of these .Trash access errors show up in my /var/log/syslog file. I'm going to continue to test this theory to see if it was just coincidence or not. -- try to access a .Trash-$USER directory on autofs mounts https://bugs.launchpad.net/bugs/210468 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is the registrant for gvfs. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 210468] Re: try to access a .Trash-$USER directory on autofs mounts
Just a comment on point (c) above: I don't think this is quite as innocuous as you suppose. While looking at the root of a normal automount point for a non-existent directory (or two, in this case) isn't so bad (except for the annoying log spam), there are various types of maps which take any random set of characters and try to do something with them. For example, if you try to access /net/.Trash then (on systems where it's enabled) a script /etc/auto.net is invoked with an argument of .Trash as the putative hostname. This leads to attempts to do DNS lookups, run showmount, and other dodgy operations which, on a well- behaved system, should still not be a major concern but are significantly more costly than a simple directory lookup failure. Also, some maps, commonly /home maps, avoid very long lists in their maps by using map key substitution; so there's one entry containing a and whatever text is used for that, a mount request is made for that (for example in /home/psmith would be psmith and the mount request would be made with that--if you try /home/.Trash then is .Trash and a mount request is made for that). This can also cause problems, most especially for the server which is constantly rejecting all these invalid mount requests from all the hosts on the network. It can also cause delays if the server or network is busy. I do agree this should be fixed: I can't think of any situation where it would be legitimate and reasonable to have a .Trash directory in an automount map mount point (mount point of type autofs). Everything in an autofs mount point is, by definition, a partition mount itself which means that any .Trash entry would have to be a seperately mounted partition... which means that the real trash would be in .../.Trash/.Trash --- right? It seems reasonable to me to actually make the fs types that gvfsd-trash looks in be configurable, in some way. This is a larger change of course, but it's the common way to avoid hardcoding this stuff (for things like slocate etc.) If someone has a patch they would like me to test, I can do that. -- try to access a .Trash-$USER directory on autofs mounts https://bugs.launchpad.net/bugs/210468 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is the registrant for gvfs. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 236871] [NEW] seahorse-agent won't accept ssh passphrase if stdin is /dev/null
Public bug reported: Binary package hint: seahorse I'm running Ubuntu 8.04 with the latest proposed packages as of today: ii seahorse2.22.2-0ubuntu1 I have a script that uses SSH port forwarding to create a VPN tunnel between two machines. Since it is only for port forwarding, it doesn't need any stdin/stdout/stderr, and I redirect all these to/from /dev/null and put the ssh into the background. With Gutsy and ssh-agent this works just fine. But, in Hardy with seahorse-agent, if I have never entered my passphrase before (which is common since the first thing I usually want to do upon logging in is invoke the script to set up the tunnel) and seahorse-agent asks me for my passphrase as a result of starting ssh, then when I type it I see the dots being put into the text box, etc. and all seems fine. However, when I press return the passphrase is never accepted and I just get another chance to enter my passphrase. It will never be accepted and I eventually have to press the Deny button to quit. I have typed it into a terminal as cleartext and cut and pasted it so I know I have typed it correctly. After some experimentation, it turns out that a /dev/null stdin is causing this problem. This fails to register my passphrase: ssh -X remotehost xterm /dev/null but this works fine: ssh -X remotehost xterm /dev/null 21 ** Affects: seahorse (Ubuntu) Importance: Undecided Status: New -- seahorse-agent won't accept ssh passphrase if stdin is /dev/null https://bugs.launchpad.net/bugs/236871 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to seahorse in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 160264] Re: [nvidia] compiz displays white screen when locked
Chris: Yep, I know. I was responding to dashua's post saying it was fixed, by pointing out that it may now work properly for some situations but that doesn't mean it's fixed. Cheers! -- [nvidia] compiz displays white screen when locked https://bugs.launchpad.net/bugs/160264 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 160264] Re: [nvidia] compiz displays white screen when locked
See comment #57 for a way to reproduce this which doesn't use the screensaver; I believe that method still shows the bug. -- [nvidia] compiz displays white screen when locked https://bugs.launchpad.net/bugs/160264 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 160264] Re: [nvidia] compiz displays white screen when locked
Since this bug is marked fixed released, is there another bug tracking the remaining problems with nvidia drivers? I know we can't solve them but it seems like we should have an open bug about this until nvidia releases fixed drivers (as Chris points out, that could be a long ways away). -- [nvidia] compiz displays white screen when locked https://bugs.launchpad.net/bugs/160264 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 231898] Re: evolution-exchange-storage SIGABRT
*** This bug is a duplicate of bug 215904 *** https://bugs.launchpad.net/bugs/215904 This is really a bug in openldap which is causing lots of ldap-based apps to fail. There is more info in ubuntu bug #215904 ** This bug has been marked a duplicate of bug 215904 (ITS#5518) Assertion error in io.c:234: ber_flush2 -- evolution-exchange-storage SIGABRT https://bugs.launchpad.net/bugs/231898 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 135471] Re: Addressbook crash when searching contacts by any field contains
I've built the latest Evo from SVN and I have no problems with this search, in both my personal address book and the Exchange Contacts address book. I've tried it with searches that match only a few of my entries, and also with searches that match none of my entries, and no crash. So, it's been fixed in SVN at any rate. -- Addressbook crash when searching contacts by any field contains https://bugs.launchpad.net/bugs/135471 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 135471] Re: Addressbook crash when searching contacts by any field contains
This bug has been fixed in the upstream trunk last week: http://svn.gnome.org/viewvc/evolution-data- server?view=revisionrevision=8157 FYI. Maybe this fix can be backported to the current Gutsy version of evolution-data-server. -- Addressbook crash when searching contacts by any field contains https://bugs.launchpad.net/bugs/135471 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 147506] Re: Gutsy: Autocomplete fails for multiple addressees
I personally think the importance of this bug should be greater than low. This is (IMO) an extremely serious regression/loss of functionality and deserves to be fixed via a patch in Gutsy. The fix has been released in Evo 2.12.1. I don't know if there are any plans to upgrade to a completely new version like this (traditionally Ubuntu hasn't done that although exceptions have been made IIRC), but at the very least this fix should be backported. -- Gutsy: Autocomplete fails for multiple addressees https://bugs.launchpad.net/bugs/147506 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 120248] Need update to Gnome 2.18.2
Public bug reported: On 20 May 2007 the Gnome desktop update 2.18.2 was released. However, there has been no corresponding update to the Gnome packages in Ubuntu 7.04. I've noticed that past releases (with the exception of the 6.06 LTS release) seem to not package Gnome updates. There are some important bugfixes to applications I rely on every day (such as Evolution) in the update; does the Ubuntu team intend to provide packages for the Gnome update releases? Is there some kind of policy on this documented somewhere? ** Affects: gnome-desktop (Ubuntu) Importance: Undecided Status: Unconfirmed -- Need update to Gnome 2.18.2 https://bugs.launchpad.net/bugs/120248 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-desktop in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 120248] Re: Need update to Gnome 2.18.2
I'm sure Gutsy will ship with Gnome 2.20. As I understood it that was one of the reasons Ubuntu releases when it does; they try to release as soon as feasible after a new Gnome release. On the one hand I can certainly understand the position of not wanting to destabilize the existing release. On the other hand, the Gnome .x updates often fix bugs that are quite annoying, if not critical, and they're especially important for applications which have not yet stabilized completely (such as, as mentioned, the Evolution Exchange plugin). I guess I was assuming/hoping that the Gnome updates would be fairly simple bug fixes and would NOT contain major functionality improvements, incompatible changes, etc. (and associated potential breakage), and so they would be reasonable to add as an update. However, I guess you guys have had problems with this in the past? I guess this is the downside of releasing right after the Gnome release: it gets the NEW release of Gnome into users' hands quickly, but if Ubuntu doesn't follow up with the update releases you're leaving somewhat buggy software on everyone's desktop... and if this happens for every release then we never get a stable desktop with the most serious bugs resolved; we just jump to the next .0 or .1 release, with another, different batch of serious bugs. I wonder if this is anything to be discussed with the Gnome folks. I think Ubuntu, with its release cycle, is one of the premier movers behind Gnome these days and it seems like there should be able to be some sort of consensus on the purpose and expected quality of the point updates. I did check out the backports page but they seemed pretty firm that they were only backporting individual packages and NOT entire systems (like Gnome). -- Need update to Gnome 2.18.2 https://bugs.launchpad.net/bugs/120248 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for gnome-desktop in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 91637] Re: Evolution displays wrong time after new dst
It's hard for me to believe that after all the hype this has been given, there are still no updates to solve these problems for either Edgy or (as far as I can tell) even for Dapper. I realize it's the worst sort of drain bamage that Evo implements its own timezone management instead of just using the system defaults, but that's what we have and Ubuntu needs to work with it. What's the holdup here folks? -- Evolution displays wrong time after new dst https://launchpad.net/bugs/91637 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 58368] Re: Alert notification not shown in window list for apps in other desktops
I still see this in both my Dapper and my Edgy systems, just as reported. If SJ is extracting on the current workspace, but is not selected, when the extract ends SJ will send an alert and the window list icon on the panel with throb. However, when SJ is on a different workspace no indication at all is given that the extract has ended; no throbbing etc. I can look very carefully at the workspace switcher and see the outline of the tiny little dialog window that SJ pops up when it's done, but nothing else happens. -- Alert notification not shown in window list for apps in other desktops https://launchpad.net/bugs/58368 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 58368] Alert notification not shown in window list for apps in other desktops
Public bug reported: Binary package hint: gnome-panel I'm using Ubuntu 6.06.1, with window list applet 2.14.3. I _believe_ this is a bug in the window list applet but it could be somewhere else... I prefer to see all my windows for all desktops in my window list, so I use the window list Preferences to enable Show windows from all workspaces. Now, when I get an alert from a window which is on my current workspace the window representation in the window list throbs light and dark-- cool! However, when I get an alert from a window which is on some other workspace, I don't get any alert--not cool :-(. Currently I'm seeing this in Sound Juicer: when I use Extract to rip one of my CDs, SJ will publish an alert when it's done so if I'm in the same workspace but without SJ selected I see the alert... but I'm always always off working in another workspace and so I don't get the alert. If someone has changed their preference for window list to Show windows from all workspaces, they should get alerts for all windows in all workspaces as well. ** Affects: gnome-panel (Ubuntu) Importance: Untriaged Status: Unconfirmed -- Alert notification not shown in window list for apps in other desktops https://launchpad.net/bugs/58368 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 57941] Re: [edgy] sound-juicer parses musicbrainz data like freedb data
This also happens for soundtracks, etc. I've added another comment to the upstream bug. -- [edgy] sound-juicer parses musicbrainz data like freedb data https://launchpad.net/bugs/57941 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 23828] Re: GDM init script has weird line (breaks it for me)
I can reproduce this, but ONLY during installation from the LiveCD. Also, my testing was with Ubuntu 6.06.1 LTS ISO image. What happened: I write the above ISO to CD and tried to boot with it. The detected video driver (ati) does not work on my system for whatever reason, so X failed to start and I eventually got a console prompt. I used ps and determined that GDM was still running. I ran sudo /etc/init.d/gdm stop, then used ps again and determined GDM was STILL running. No matter how many times I ran it, GDM was never stopped. If I used kill on it, it stopped immediately. I ran sudo /bin/sh -x /etc/init.d/gdm stop and discovered that start- stop-daemon was being invoked with the --exec flag (that is, SSD_ARG was set to --exec /usr/sbin/gdm). This did not seem to work. If I ran start-stop-daemon by hand, using the same command line but leaving out the --exec, it worked fine and GDM was stopped. -- GDM init script has weird line (breaks it for me) https://launchpad.net/bugs/23828 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 57347] Option to save session settings is missing at logout
Public bug reported: I believe the log out button and the dialog it creates is managed by gnome-panel, right? If not please let me know where to file this. I'm using Ubuntu 6.06.1 LTS (standard install). In past Gnome releases the logout panel has had a checkbox that allows you to save your session at logout time. That checkbox is missing in this release, and it never asks with a separate dialog, so there's no easy way to save your session! If I open System - Preferences - Sessions I see that Ask on logout _is_ checked (but yet there is no query on logout). The only way I can see to save a session is to check the Automatically save session box, then log out, then log back in and go back to the Sessions dialog and uncheck it again. ** Affects: gnome-panel (Ubuntu) Importance: Untriaged Status: Unconfirmed -- Option to save session settings is missing at logout https://launchpad.net/bugs/57347 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 34966] Alarms do not work in Evolution
Public bug report changed: https://launchpad.net/malone/bugs/34966 Comment: Yes, I've used the method described in the ubuntuforums to build a patched version with dpkg-rebuild and it does work: alarms show up properly. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 34966] Alarms do not work in Evolution
Public bug report changed: https://launchpad.net/malone/bugs/34966 Comment: Check this thread from the Ubuntu forums: http://ubuntuforums.org/archive/index.php/t-93128.html Refers to this patch, posted to the evolution-patches mailing list: http://mail.gnome.org/archives/evolution- patches/2005-November/msg00010.html This was apparently committed as a fix to Gnome bug # 316710 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 34966] Alarms do not work in Evolution
Public bug report changed: https://launchpad.net/malone/bugs/34966 Bug watches changed: + Bug 316710 [GNOME Bug Tracker] -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 34966] Alarms do not work in Evolution
Public bug report changed: https://launchpad.net/malone/bugs/34966 - Changed attachments: Added: patch to fix evolution alarms http://librarian.launchpad.net/1735677/evolution-alarm.patch -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 34966] Alarms do not work in Evolution
Public bug report changed: https://launchpad.net/malone/bugs/34966 Comment: I'd dearly love to have this fixed in Breezy: to me it's a very critical bug in Evolution functionality if alarms don't work! I've read 2-3 people saying the patch fixed their problems right up and no one has complained about it... it seems solid. Thanks! -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 34966] Alarms do not work in Evolution
Public bug reported: https://launchpad.net/malone/bugs/34966 Affects: evolution (Ubuntu) Severity: Normal Priority: (none set) Status: Unconfirmed Description: No matter where I create my alarms (either in my Personal calendar or in my Exchange calendar) I don't get any notification. In previous versions of Evolution, this worked great and I would get a dialog pop up at a preset time before the appointment (I set this to 5 minutes). Without this feature I might as well use the Open Web Access feature of Exchange; Evolution is not giving me anything extra (and it's pretty buggy in general). I definitely do have the box asking for an alarm to be checked, both in the general preferences AND in the specific appointment. I also have my system on all the time, and running Evolution all the time, so it's not anything to do with not generating alarms that went by while the system was off. I can create an appointment to happen in a few minutes, in any of my calendars, and never get the alarm. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 34966] Alarms do not work in Evolution
Public bug report changed: https://launchpad.net/malone/bugs/34966 Comment: This is evolution-2.4.1-0ubuntu7 in breezy, BTW. All Breezy versions of Evo I've used have the same behavior. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 34966] Alarms do not work in Evolution
Public bug report changed: https://launchpad.net/malone/bugs/34966 Comment: Also, using ps I can see that /usr/lib/evolution/2.4/evolution-alarm- notify is running. It just never seems to do anything. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
