[Bug 771661] Re: Allow .xsession-errors to be a symlink
Same here, tested gdm 2.30.2.is.2.30.0-0ubuntu5.2 from lucid proposed, and it preserve .xsession-errors being a symlink across reboot and session logout. Looks good to me! -- 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/771661 Title: Allow .xsession-errors to be a symlink -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 494096] Re: Clicking the title of a window is bringing a window underneath it into focus
Michael's test-case is all good, except it should refer lucid-proposed. So, I tested the package in lucid-proposed, and it work as expected. +1 from me! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in ubuntu. https://bugs.launchpad.net/bugs/494096 Title: Clicking the title of a window is bringing a window underneath it into focus -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 494096] Re: Clicking the title of a window is bringing a window underneath it into focus
Tested, and I confirm Scott's PPA package of metacity fix the bug for me here. Thanks Scott! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in ubuntu. https://bugs.launchpad.net/bugs/494096 Title: Clicking the title of a window is bringing a window underneath it into focus -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 686834] Re: metacity gets confused about which window to move
*** This bug is a duplicate of bug 494096 *** https://bugs.launchpad.net/bugs/494096 I can reproduce it here no problem. Fabio, are you sure you tested with System Preferences Appearance Visual Effects set to None? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in ubuntu. https://bugs.launchpad.net/bugs/686834 Title: metacity gets confused about which window to move -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 686834] Re: metacity gets confused about which window to move
*** This bug is a duplicate of bug 494096 *** https://bugs.launchpad.net/bugs/494096 ** This bug has been marked a duplicate of bug 494096 Clicking the title of a window is bringing a window underneath it into focus * You can subscribe to bug 494096 by following this link: https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/494096/+subscribe -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in ubuntu. https://bugs.launchpad.net/bugs/686834 Title: metacity gets confused about which window to move -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 686834] Re: metacity gets confused about which window to move
** Also affects: metacity via https://bugzilla.gnome.org/show_bug.cgi?id=599181 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to metacity in ubuntu. https://bugs.launchpad.net/bugs/686834 Title: metacity gets confused about which window to move -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 654249] Re: libnss-ldap create troubles in gnome session when ldap server is unreacheable
By design, the NSS library is expecting the database to be available and fast to query. When the NSS database become unresponsive (as is the case when using libnss-ldap and the the LDAP directory become unavailable), this assumption breaks and functions such as getpwnam() blocks, which can cause any kinds of funny symptoms in the calling application. This is not really a bug, more like a design flaw in NSS, so there really isn't a good solution for that. If it was my call, I would close this bug as Invalid, even though it is a very real problem, because it is not strictly speaking a bug, or at least not one we can solve in the context of one specific package or library. ld2ndR: the solution to your problem is to use a NSS backend that can work offline, such as SSSD, libnss-ldapd or winbind. Using nscd may help. You can also alleviate the symptoms somewhat by setting bindpolicy to soft, and timelimit and bind_timelimit to low value in /etc/ldap.conf. -- libnss-ldap create troubles in gnome session when ldap server is unreacheable https://bugs.launchpad.net/bugs/654249 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 471542] Re: gdm doesn't load with large passwd file
Gotta love the version number! :) Using 2.30.2.is.2.30.0-0ubuntu1, the home directory are not mounted as soon as GDM runs, which would resolve the bug as reported here. However, shortly after a user logs in, the directory do get automounted. I presume there is another process poking into user's home directory that triggers the automount (user-switcher, perhaps?). But that is not the topic of this bug, which can be considered resolved. Thanks guys! EtienneG -- gdm doesn't load with large passwd file https://bugs.launchpad.net/bugs/471542 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 471542] Re: gdm doesn't load with large passwd file
Tested 2.30.2-0ubuntu1, and home directories still get all automounted as soon as a user (any user) logs in. I am testing the correct package? Thanks! -- gdm doesn't load with large passwd file https://bugs.launchpad.net/bugs/471542 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 471542] Re: gdm doesn't load with large passwd file
** Changed in: gdm (Ubuntu) Status: New = Confirmed -- gdm doesn't load with large passwd file https://bugs.launchpad.net/bugs/471542 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 471542] Re: gdm doesn't load with large passwd file
Confirmed here. = Steps to reproduce = On the server: - Create user1 (uid 1001), user2 (uid 1002) and user3 (uid 1003), with home directory under /home/autofs/ - Install package nfs-kernel-server, configure /etc/exports with: /home/autofs*(rw) On the client: - Create user1 (uid 1001), user2 (uid 1002) and user3 (uid 1003) with home under /home/autofs/. Notice the uid are consistent with the server. - Install package autofs5, configure /etc/auto.master with: /home/autofs/etc/auto.home and /home/auto.home with: * -fstype=nfs,soft,intr,nosuidnfsserver:/home/autofs/ (where nfsserver is the hostname of the aserver above) - Reboot (for good measure) - At the GDM prompt, switch to a VT with Ctrl-Alt-F1, login as a non- autofs user - Witness all autofs home directory are currently mounted When we disable the user listing as explained in the bug description, the home directory would not get mounted when GDM started, but they all will as soon as a single user log on. When testing using a different display manager (xdm), it only mount the user home directory on log in, as expected. -- gdm doesn't load with large passwd file https://bugs.launchpad.net/bugs/471542 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 431088] [NEW] evince do not render smooth shading properly
Public bug reported: Binary package hint: evince Using evince 2.26.1-0ubuntu1 on 9.04 (jaunty), the attached file (produced by Inkscape) do not render properly. You can notice that the blue smooth shading (the kind of frame around the flyer content) renders with vertical line of lighter shade. In xpdf and Adobe Acrobat, that blue frame shading render smoothly. ** Affects: evince (Ubuntu) Importance: Undecided Status: New -- evince do not render smooth shading properly https://bugs.launchpad.net/bugs/431088 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 431088] Re: evince do not render smooth shading properly
** Attachment added: flyer_en.pdf http://launchpadlibrarian.net/31931818/flyer_en.pdf -- evince do not render smooth shading properly https://bugs.launchpad.net/bugs/431088 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 431088] Re: evince do not render smooth shading properly
** Attachment added: Screenshot.png http://launchpadlibrarian.net/31931904/Screenshot.png -- evince do not render smooth shading properly https://bugs.launchpad.net/bugs/431088 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 431088] Re: evince do not render smooth shading properly
I have been told by a colleague that it render correctly in karmic, which mean it must have been fixed. See the attached screenshot for how it render on jaunty. Also, I forgot to mention that it also print with the lighter lines in the shading area, which mean it is not a problem specific to screen rendering. -- evince do not render smooth shading properly https://bugs.launchpad.net/bugs/431088 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 207072] Re: nautilus does not display samba shares for machines inside an ADS network.
The proposed fix was pulled from hardy-proposed, but Steve made it available again on his PPA at http://ppa.launchpad.net/vorlon/ppa/ubuntu for further confirmation of the regression. Using gvfs and gvfs-backends 0.2.5-0ubuntu8~ppa1 from there, along with nautilus 2.22.5.1-0ubuntu1 from hardy-updates, I get exactly the same results described by Renzo Bagnati in comment 220. The Ubuntu machine is up-to-date and joined to an AD using likewise-open. -- nautilus does not display samba shares for machines inside an ADS network. https://bugs.launchpad.net/bugs/207072 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 207072] Re: nautilus does not display samba shares for machines inside an ADS network.
I also experience the same behavior using nautilus 2.22.5.1-0ubuntu2 from hardy-proposed. -- nautilus does not display samba shares for machines inside an ADS network. https://bugs.launchpad.net/bugs/207072 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 216104] Re: Hardy - Nautilus shortcut to Samba Share reports wrong password, double icons
The fix in hardy-proposed (gvfs-backends 0.2.5-0ubuntu7) appear to be working just fine here. Thanks! -- Hardy - Nautilus shortcut to Samba Share reports wrong password, double icons https://bugs.launchpad.net/bugs/216104 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 235782] Re: P3: Regression, multiple problems when using Places Connect to Server to connect to Windows share in hardy (reposted)
** Description changed: This private bug is a support escalation to parallel Public Bug #216104 which explains the same issue. This was mistakenly filed without the private flag as bug #235774. Notification went out to various non-Canonical people, including the Ubuntu Bugs team. The first bug was closed as Invalid for now, this is a repost. The Places Connect to Server... dialog in hardy do not work to connect to Windows share in hardy. There are multiple failure, and its behavior is extremely confusing. This worked without any problem on gutsy using the same server and same credentials. The share we are trying to connect to is hosted on a Windows Small Business Server 2003 server. - Local username: ubuntu - Remote username: ubuntu - Windows server name: win2003 - Windows domain name: canonical (it is an Active Directory) - Share name we connect to: clients To be sure this is not a problem that have been fixed in an upcoming update already, I installed the following package from hardy-proposed: nautilus 2.22.3-0ubuntu1 gvfs, gvfs-backends and libgvfscommon0 0.2.4-0ubuntu1 == Steps to reproduce == 1. Go to Places Connect to Server..., choose Windows Share in Service Type, fill in Server, Share, Username and Domain Name appropriately with the value above, click the Connect button (see Screenshot-1.png) 2. Enter Password dialog is shown. Provide password and then click Connect (see Screenshot-2.png) 3. An error message is displayed: 'Can't display location smb://win2003/clients -- The specificed location is not mounted'. However, the shortcut icon appear on the desktop nonetheless (see Screenshot-3.png). Click Ok to dismiss. 4. Double-click the shortcut icon titled clients on win2003 on the desktop. The Enter Password dialog is displayed again, this time with a wrong value for Domain (see Screenshot-4.png). Change Domain from MSHOME to canonical, provide password and click Connect. 5. The content of the share is displayed as expected, but a second shortcut icon appear on the desktop, with the same name (see Screenshot-5.png). == Problems == 1. Confusing Can't display location smb://win2003/clients -- The specificed location is not mounted message, even tough a shortcut icon for the share appear on the desktop. 2. Enter Password dialog is displayed twice: once after filling the info in Place Connect to Server, and then again when trying to open the share from the shortcut icon on the desktop. 3. The Enter Password have wrong value for Domain the second time it is shown. It should display the value entered originally. 4. When the correct domain and password are provided in the second Enter Password dialog, a second shortcut to the share appear on the desktop with the same name. Not sure if this bug should be filed against Nautilus or GVFS or something else, so I left the package field blank for now. If required, it is possible to give access to the VM for both the 8.04 clients and the Windows server. The client VM on the Montréal VMWare server is Ubuntu-8.04-desktop-i386, the server VM is Windows Small Business Server 2003. Related Canonical support case is #2267. I did not report a public bug right away, as there are a couple bugs on the subject already in Launchpad and it is unclear if and how they relate to this one. Also, I was not sure if the bug should be reported as a single one, or as multiple independent ones. QA Team response deadline: May 30th 2008 11h AM EDT. + + REF: 5002002qQ1a -- P3: Regression, multiple problems when using Places Connect to Server to connect to Windows share in hardy (reposted) https://bugs.launchpad.net/bugs/235782 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a direct subscriber. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 250993] Re: The 'check for support types' button doesn't report errors
In fact, the Check for Supported Types does not appear to do *anything* whatsoever. On the server side, monitoring incoming connection from the Evolution client using tcpdump when we press the Check for Supported Types button, we can see it does not even try to connect. I tried on both hardy and jaunty, same behavior. -- The 'check for support types' button doesn't report errors https://bugs.launchpad.net/bugs/250993 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 250993] Re: The 'check for support types' button doesn't report errors
The problem is really in the Evolution Setup Assistant (the wizard that is run the first time Evolution is started). In the Receiving Email dialog, clicking the Check for Supported Types does not even try to connect to the server (tried with all three of No Encryption, TLS Encryption and SSL Encryption). In the Sending Email dialog of the Evolution Setup Assistant, it does connect though. Once Evolution is configured, going to Edit Preferences Mail Accounts Edit Receiving Email, it does work too. So, in my case, it seems to be related only to the Receiving Email dialog of the Evolution Setup Assistant. I guess it is a different bug than what was originally discussed here (results wrong when server is not reachable). -- The 'check for support types' button doesn't report errors https://bugs.launchpad.net/bugs/250993 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 207072] Re: nautilus does not display samba shares for machines inside an ADS network.
Tab, this is a different issue than the one being discussed here. The problem you are reporting is discussed in bug #216104. -- nautilus does not display samba shares for machines inside an ADS network. https://bugs.launchpad.net/bugs/207072 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 235782] Re: P3: Regression, multiple problems when using Places Connect to Server to connect to Windows share in hardy (reposted)
Indeed, BrianDrab is the customer. It is not a large account, but we are doing due diligence by escalating bugs when they are impacting use- case that are general enough. -- P3: Regression, multiple problems when using Places Connect to Server to connect to Windows share in hardy (reposted) https://bugs.launchpad.net/bugs/235782 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a direct subscriber. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 207072] Re: nautilus does not display samba shares for machines inside an ADS network.
IIRC, Debian Etch ship with the older GnomeVFS instead of the newer GVFS, which would explain why you do not get the problem using it. -- nautilus does not display samba shares for machines inside an ADS network. https://bugs.launchpad.net/bugs/207072 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
I have deleted the patched 2.4.0 package in my PPA, as it been made obsolete by the new 2.5.0 upstream in hardy-proposed. -- 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
Did a very quick check, and it seem to work. The Trash behave as expected: show full when something is deleted in one of the autofs mount, we can empty trash just fine and we do not get the error in the log anymore. Looks good to me! -- 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
Looking at the ChangeLog of GVFS 0.2.5, there is mention of this bug being fixed. A casual inspection of the code confirm it. Sebastien, did a patch to fix this bug was added to the package you uploaded? -- 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
Above comment should read ..., there is *no* mention of this bug being fixed Sorry for the confusion! -- 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
I built a gvfs package for hardy using the patch Paul Smith posted above. You can get it from: https://edge.launchpad.net/~etienne-goyer-outlands/+archive I am fairly certain the patch is correct, as there is no point in actually polling for a trash in an autofs base mountpoint anyway. File system mounted by automount actually get their own mtab entry, with their own file system type (by default, NFS), which are treated just like any other file system mounted manually or through /etc/fstab. automount base mountpoint are a special case, and should be handled as such. At least, that is how I understand it! Sebastien/Steve: if you need a testbed, ping me out-of-band. -- 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 235786] [NEW] Connect to Server... dialog in hardy fail to connect to Windows share
Public bug reported: Binary package hint: nautilus The Places Connect to Server... dialog in Ubuntu 8.04 do not work to connect to Windows share. There are multiple failure, and its behavior is extremely confusing. This worked without any problem on Ubuntu 7.10 (gutsy) using the same server and same credentials. The share we are trying to connect to is hosted on a Windows Small Business Server 2003 server. - Local username: ubuntu - Remote username: ubuntu - Windows server name: win2003 - Windows domain name: canonical (it is an Active Directory) - Share name we connect to: clients To be sure this is not a problem that have been fixed in an upcoming update already, I installed the following package from hardy-proposed: nautilus 2.22.3-0ubuntu1 gvfs, gvfs-backends and libgvfscommon0 0.2.4-0ubuntu1 == Steps to reproduce == 1. Go to Places Connect to Server..., choose Windows Share in Service Type, fill in Server, Share, Username and Domain Name appropriately with the value above, click the Connect button (see Screenshot-1.png) 2. Enter Password dialog is shown. Provide password and then click Connect (see Screenshot-2.png) 3. An error message is displayed: 'Can't display location smb://win2003/clients -- The specificed location is not mounted'. However, the shortcut icon appear on the desktop nonetheless (see Screenshot-3.png). Click Ok to dismiss. 4. Double-click the shortcut icon titled clients on win2003 on the desktop. The Enter Password dialog is displayed again, this time with a wrong value for Domain (see Screenshot-4.png). Change Domain from MSHOME to canonical, provide password and click Connect. 5. The content of the share is displayed as expected, but a second shortcut icon appear on the desktop, with the same name (see Screenshot-5.png). == Problems == 1. Confusing Can't display location smb://win2003/clients -- The specified location is not mounted message, even tough a shortcut icon for the share appear on the desktop. 2. Enter Password dialog is displayed twice: once after filling the info in Place Connect to Server, and then again when trying to open the share from the shortcut icon on the desktop. 3. The Enter Password have wrong value for Domain the second time it is shown. It should display the value entered originally. 4. When the correct domain and password are provided in the second Enter Password dialog, a second shortcut to the share appear on the desktop with the same name. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- Connect to Server... dialog in hardy fail to connect to Windows share https://bugs.launchpad.net/bugs/235786 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 235786] Re: Connect to Server... dialog in hardy fail to connect to Windows share
** Attachment added: Screenshot-1.png http://launchpadlibrarian.net/14796145/Screenshot-1.png -- Connect to Server... dialog in hardy fail to connect to Windows share https://bugs.launchpad.net/bugs/235786 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 235786] Re: Connect to Server... dialog in hardy fail to connect to Windows share
** Attachment added: Screenshot-2.png http://launchpadlibrarian.net/14796148/Screenshot-2.png -- Connect to Server... dialog in hardy fail to connect to Windows share https://bugs.launchpad.net/bugs/235786 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 235786] Re: Connect to Server... dialog in hardy fail to connect to Windows share
** Attachment added: Screenshot-3.png http://launchpadlibrarian.net/14796152/Screenshot-3.png -- Connect to Server... dialog in hardy fail to connect to Windows share https://bugs.launchpad.net/bugs/235786 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 235786] Re: Connect to Server... dialog in hardy fail to connect to Windows share
** Attachment added: Screenshot-4.png http://launchpadlibrarian.net/14796160/Screenshot-4.png -- Connect to Server... dialog in hardy fail to connect to Windows share https://bugs.launchpad.net/bugs/235786 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 235786] Re: Connect to Server... dialog in hardy fail to connect to Windows share
** Attachment added: Screenshot-5.png http://launchpadlibrarian.net/14796167/Screenshot-5.png -- Connect to Server... dialog in hardy fail to connect to Windows share https://bugs.launchpad.net/bugs/235786 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 63094] Re: Evolution crash when opening a mail
Indeed, Edgy it is. -- Evolution crash when opening a mail https://launchpad.net/bugs/63094 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 63094] Re: Evolution crash when opening a mail
Work for me, thanks ! -- Evolution crash when opening a mail https://launchpad.net/bugs/63094 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 63094] Re: Evolution crash when opening a mail
** Attachment added: Mail causing the crash http://librarian.launchpad.net/4555734/Update%20Caf%C3%A9%20Haags%20Filmhuis%20in%20bestand%20van%20de%20Nederlandse%20Kalenderfabriek.eml.eml -- Evolution crash when opening a mail https://launchpad.net/bugs/63094 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 63094] Re: Evolution crash when opening a mail
** Attachment added: backtrace http://librarian.launchpad.net/4555738/evolution.backtrace -- Evolution crash when opening a mail https://launchpad.net/bugs/63094 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 63094] Evolution crash when opening a mail
Public bug reported: Not sure if this is related to #58365 ... Evolution crash when opening the mail in attachment. evolution_2.8.0-0ubuntu3 and evolution-data-server-dbg_1.8.0-0ubuntu1 on Edgy. ** Affects: evolution (Ubuntu) Importance: Undecided Status: Unconfirmed -- Evolution crash when opening a mail https://launchpad.net/bugs/63094 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 63094] Re: Evolution crash when opening a mail
I had sent a Bug Buddy report the first time I experienced the problem. The bug that was open automatically just got classified as a duplicate of 353430 on bugzilla.gnome.org, so there is no point in reporting upstream. I guess this one can be closed too, but I will leave it open for now since I am not quite sure. -- Evolution crash when opening a mail https://launchpad.net/bugs/63094 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
