[Bug 377383] [NEW] Can not uncheck Close when finished box in Online Banking Connection Window
Public bug reported: OFX online banking with gnucash 2.2.6-2ubuntu5 is not working for me in a clean install of Unbuntu 9.04 i386. The first step in diagnosing the underlying problem would seem to be reading the messages that appear in the Online Banking Connection Window. This is not possible because the default condition of the Close when finished check box is checked, and it appears to be impossible to uncheck it. Again, fixing this bug would only be a first step - aqbanking is giving a false negative when attempting to download transactions. ** Affects: gnucash (Ubuntu) Importance: Undecided Status: New -- Can not uncheck Close when finished box in Online Banking Connection Window https://bugs.launchpad.net/bugs/377383 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 354243] Re: Nautilus fails to browse any share on network to which Iomega Home Network Hard Drive (MDHD500-N, firmware K108.W15) is attached.
Thank you Thierry and Braam. Thierry, I didn't try all the tricks you linked to above, some were speculative or more difficult than the CLI or fstab mount work-around. The earlier version of the Iomega firmware did not work for me. Braam, I confirm your good result with an installed version of 9.04, with this exception: if the network also contains a computer running 8.10, Nautilus still fails to browse the NAS. I will soon upgrade the other computer. Thanks again. -- Nautilus fails to browse any share on network to which Iomega Home Network Hard Drive (MDHD500-N, firmware K108.W15) is attached. https://bugs.launchpad.net/bugs/354243 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 354243] Re: Nautilus fails to browse any share on network to which Iomega Home Network Hard Drive (MDHD500-N, firmware K108.W15) is attached.
Thank you Thierry and Braam. Thierry, I didn't try all the tricks you linked to above, some were speculative or more difficult than the CLI or fstab mount work-around. The earlier version of the Iomega firmware did not work for me. Braam, I confirm your good result with an installed version of 9.04, with this exception: if the network also contains a computer running 8.10, Nautilus still fails to browse the NAS. I will soon upgrade the other computer. Thanks again. -- Nautilus fails to browse any share on network to which Iomega Home Network Hard Drive (MDHD500-N, firmware K108.W15) is attached. https://bugs.launchpad.net/bugs/354243 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 354243] Re: Nautilus fails to browse any share on network to which Iomega Home Network Hard Drive (MDHD500-N, firmware K108.W15) is attached.
Thank you. I confirm your summary. smbtree -b -N returns no output Opening the location as specified creates browse-able locations in Nautilus, and mounts them on the Desktop. This is somewhat easier (in my situation) than using the command line or modifying fstab. I will test this in my real-life home network. Shouldn't the operation of obtaining the NAS's IP address, as with findsmb, and passing it to the browsing function be written into Nautilus? It seems to me that it advances Ubuntu to have it just work with cheap, widely-available hardware. ** Attachment added: Screenshot.png http://launchpadlibrarian.net/25491703/Screenshot.png -- Nautilus fails to browse any share on network to which Iomega Home Network Hard Drive (MDHD500-N, firmware K108.W15) is attached. https://bugs.launchpad.net/bugs/354243 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 354243] Re: Nautilus fails to browse any share on network to which Iomega Home Network Hard Drive (MDHD500-N, firmware K108.W15) is attached.
Bad news in real-life network (not the controlled experiment in bug report): Running Intrepid, desktop and laptop on network, each with own Samba server (i.e. three total, including NAS), Nautilus Locationsmb://192.168.1.66/ does not work. It shows shares, but does not mount them on desktop, and attempting to browse them through Nautilus results in being kicked to home directory. CLI and fstab mounting works. Essentially, Iomega NAS kills default Nautilus network browsing for any user on the network. -- Nautilus fails to browse any share on network to which Iomega Home Network Hard Drive (MDHD500-N, firmware K108.W15) is attached. https://bugs.launchpad.net/bugs/354243 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 354243] Re: Nautilus fails to browse any share on network to which Iomega Home Network Hard Drive (MDHD500-N, firmware K108.W15) is attached.
Thank you. I confirm your summary. smbtree -b -N returns no output Opening the location as specified creates browse-able locations in Nautilus, and mounts them on the Desktop. This is somewhat easier (in my situation) than using the command line or modifying fstab. I will test this in my real-life home network. Shouldn't the operation of obtaining the NAS's IP address, as with findsmb, and passing it to the browsing function be written into Nautilus? It seems to me that it advances Ubuntu to have it just work with cheap, widely-available hardware. ** Attachment added: Screenshot.png http://launchpadlibrarian.net/25491703/Screenshot.png -- Nautilus fails to browse any share on network to which Iomega Home Network Hard Drive (MDHD500-N, firmware K108.W15) is attached. https://bugs.launchpad.net/bugs/354243 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 296673] Re: Nautilus failes connecting to IOMEGA NAS Drives!
Still an issue in Jaunty: Bug 354243 -- Nautilus failes connecting to IOMEGA NAS Drives! https://bugs.launchpad.net/bugs/296673 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 354243] Re: Nautilus fails to browse any share on network to which Iomega Home Network Hard Drive (MDHD500-N, firmware K108.W15) is attached.
Bad news in real-life network (not the controlled experiment in bug report): Running Intrepid, desktop and laptop on network, each with own Samba server (i.e. three total, including NAS), Nautilus Locationsmb://192.168.1.66/ does not work. It shows shares, but does not mount them on desktop, and attempting to browse them through Nautilus results in being kicked to home directory. CLI and fstab mounting works. Essentially, Iomega NAS kills default Nautilus network browsing for any user on the network. -- Nautilus fails to browse any share on network to which Iomega Home Network Hard Drive (MDHD500-N, firmware K108.W15) is attached. https://bugs.launchpad.net/bugs/354243 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 354243] Re: Nautilus fails to browse any share on network to which Iomega Home Network Hard Drive (MDHD500-N, firmware K108.W15) is attached.
Thank you for addressing the specific case I have set up. In answer to your first five assumptions, YES except I failed to recreate the browser result shown in the attachment to Comment 4. Now, the NAS shares do not show, only Windows Network. Double-clicking on Windows Network yields Failed to retrieve share list from server. See attachment for complete illustration. The following are or may be different from Comment 4: - The NAS was not hard-reset immediately prior to latest experiment. - I have given the NAS a static IP address. - I am not sure of the power-up order for the computer, router, and NAS. From now on, I will leave the NAS and router on while re-booting the computer. I hope we can solve the now slightly revised bug under these conditions, because it allows undisrupted use of the NAS from Windows, and fstab-mounted Ubuntu, in between experiments. ** Attachment added: Screen001.png http://launchpadlibrarian.net/25210825/Screen001.png -- Nautilus fails to browse any share on network to which Iomega Home Network Hard Drive (MDHD500-N, firmware K108.W15) is attached. https://bugs.launchpad.net/bugs/354243 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 354243] Re: Nautilus fails to browse any share on network to which Iomega Home Network Hard Drive (MDHD500-N, firmware K108.W15) is attached.
To run a command as administrator (user root), use sudo command. See man sudo_root for details. ubu...@ubuntu:~$ smbtree -N ubu...@ubuntu:~$ -- Nautilus fails to browse any share on network to which Iomega Home Network Hard Drive (MDHD500-N, firmware K108.W15) is attached. https://bugs.launchpad.net/bugs/354243 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 354243] Re: Nautilus fails to browse any share on network to which Iomega Home Network Hard Drive (MDHD500-N, firmware K108.W15) is attached.
I was able to sudo gedit /etc/samba/smb.conf and killall x-session- manager as requested, but there is no change in diagnostics, see attachment. ** Attachment added: Screen003.png http://launchpadlibrarian.net/25211477/Screen003.png -- Nautilus fails to browse any share on network to which Iomega Home Network Hard Drive (MDHD500-N, firmware K108.W15) is attached. https://bugs.launchpad.net/bugs/354243 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 354243] Re: Nautilus fails to browse any share on network to which Iomega Home Network Hard Drive (MDHD500-N, firmware K108.W15) is attached.
Addendum to Comment 18: Other differences from previous trial, along with setting static IP address on the NAS, I set host name to IOMEGA-36AE (was STORAGE- 36AE) and domain name to UTOPIA_BEACH (was WORKGROUP). I'm going to guess that when the domain names match, the shares are displayed at the same level as Windows Network. I don't think this was the problem, however. -- Nautilus fails to browse any share on network to which Iomega Home Network Hard Drive (MDHD500-N, firmware K108.W15) is attached. https://bugs.launchpad.net/bugs/354243 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 354243] Re: Nautilus fails to browse any share on network to which Iomega Home Network Hard Drive (MDHD500-N, firmware K108.W15) is attached.
Thank you for addressing the specific case I have set up. In answer to your first five assumptions, YES except I failed to recreate the browser result shown in the attachment to Comment 4. Now, the NAS shares do not show, only Windows Network. Double-clicking on Windows Network yields Failed to retrieve share list from server. See attachment for complete illustration. The following are or may be different from Comment 4: - The NAS was not hard-reset immediately prior to latest experiment. - I have given the NAS a static IP address. - I am not sure of the power-up order for the computer, router, and NAS. From now on, I will leave the NAS and router on while re-booting the computer. I hope we can solve the now slightly revised bug under these conditions, because it allows undisrupted use of the NAS from Windows, and fstab-mounted Ubuntu, in between experiments. ** Attachment added: Screen001.png http://launchpadlibrarian.net/25210825/Screen001.png -- Nautilus fails to browse any share on network to which Iomega Home Network Hard Drive (MDHD500-N, firmware K108.W15) is attached. https://bugs.launchpad.net/bugs/354243 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 354243] Re: Nautilus fails to browse any share on network to which Iomega Home Network Hard Drive (MDHD500-N, firmware K108.W15) is attached.
To run a command as administrator (user root), use sudo command. See man sudo_root for details. ubu...@ubuntu:~$ smbtree -N ubu...@ubuntu:~$ -- Nautilus fails to browse any share on network to which Iomega Home Network Hard Drive (MDHD500-N, firmware K108.W15) is attached. https://bugs.launchpad.net/bugs/354243 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 354243] Re: Nautilus fails to browse any share on network to which Iomega Home Network Hard Drive (MDHD500-N, firmware K108.W15) is attached.
I was able to sudo gedit /etc/samba/smb.conf and killall x-session- manager as requested, but there is no change in diagnostics, see attachment. ** Attachment added: Screen003.png http://launchpadlibrarian.net/25211477/Screen003.png -- Nautilus fails to browse any share on network to which Iomega Home Network Hard Drive (MDHD500-N, firmware K108.W15) is attached. https://bugs.launchpad.net/bugs/354243 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 354243] Re: Nautilus fails to browse any share on network to which Iomega Home Network Hard Drive (MDHD500-N, firmware K108.W15) is attached.
Addendum to Comment 18: Other differences from previous trial, along with setting static IP address on the NAS, I set host name to IOMEGA-36AE (was STORAGE- 36AE) and domain name to UTOPIA_BEACH (was WORKGROUP). I'm going to guess that when the domain names match, the shares are displayed at the same level as Windows Network. I don't think this was the problem, however. -- Nautilus fails to browse any share on network to which Iomega Home Network Hard Drive (MDHD500-N, firmware K108.W15) is attached. https://bugs.launchpad.net/bugs/354243 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 354243] Re: Nautilus fails to browse any share on network to which Iomega Home Network Hard Drive (MDHD500-N, firmware K108.W15) is attached.
Given the confusion introduced by my Comment 9, I will restrict my further comments to the original case of Bug 354243: a LIVE SESSION run from a Ubuntu 9.04 beta Desktop i386 CD. That being the case, I ask: Once I have edited and saved /etc/samba/smb.conf, how am I to restart smbclient? The usual sudo /etc/init.d/samba restart will not work, because samba itself is not installed in the live session. I hesitate to install samba for the live session if there is another way to restart smbclient. === Also, does the case I present show that the underlying problem, of which https://bugs.launchpad.net/ubuntu/intrepid/+source/samba/+bug/264943 was a symptom, has not been fixed? -- Nautilus fails to browse any share on network to which Iomega Home Network Hard Drive (MDHD500-N, firmware K108.W15) is attached. https://bugs.launchpad.net/bugs/354243 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 354243] Re: Nautilus fails to browse any share on network to which Iomega Home Network Hard Drive (MDHD500-N, firmware K108.W15) is attached.
Given the confusion introduced by my Comment 9, I will restrict my further comments to the original case of Bug 354243: a LIVE SESSION run from a Ubuntu 9.04 beta Desktop i386 CD. That being the case, I ask: Once I have edited and saved /etc/samba/smb.conf, how am I to restart smbclient? The usual sudo /etc/init.d/samba restart will not work, because samba itself is not installed in the live session. I hesitate to install samba for the live session if there is another way to restart smbclient. === Also, does the case I present show that the underlying problem, of which https://bugs.launchpad.net/ubuntu/intrepid/+source/samba/+bug/264943 was a symptom, has not been fixed? -- Nautilus fails to browse any share on network to which Iomega Home Network Hard Drive (MDHD500-N, firmware K108.W15) is attached. https://bugs.launchpad.net/bugs/354243 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 354243] Re: Nautilus fails to browse any share on network to which Iomega Home Network Hard Drive (MDHD500-N, firmware K108.W15) is attached.
Whoa - stop! Comment 9 does not describe Bug 354243 directly, but rather, a related situation. That's what all those words I typed into Comment 9 mean. I had hoped the the additional information would be helpful. I'm sorry it wasn't. I opened Bug 354243 specifically because of the confusion evident in Bug 209520. But the gist of both bugs is this: There is something wrong with Nautilus and/or its dependencies - recent versions of Nautilus are not robust in browsing network shares. I intended, in Bug 354243, to offer a reproducible demonstration of this failure. Comments 1 and 4 outline that demonstration, but again: The network in Bug 354243 is a vanilla router; a vanilla computer; an Iomega MDHD500-N network hard drive, running firmware K1.08 L1.0 W1.5; and an Ubuntu 9.04 beta desktop i386 CD, running in LIVE SESSION. (Sorry to shout, but last is important: live session eliminates user error in configuration, and, more important, live session is supposed to demonstrate Ubuntu's capabilities with a wide variety of hardware.) And I will anticipate the objection that this is an Iomega problem: Windows finds the Iomega NAS; smbclient finds it; smb4k even mounts it - it's not trying to hide itself. The Iomega NAS is just one among many black-box embedded SAMBA servers that a robust, desktop-ready file manager needs to be able to browse. Current Nautilus fails. -- Nautilus fails to browse any share on network to which Iomega Home Network Hard Drive (MDHD500-N, firmware K108.W15) is attached. https://bugs.launchpad.net/bugs/354243 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 354243] Re: Nautilus fails to browse any share on network to which Iomega Home Network Hard Drive (MDHD500-N, firmware K108.W15) is attached.
Whoa - stop! Comment 9 does not describe Bug 354243 directly, but rather, a related situation. That's what all those words I typed into Comment 9 mean. I had hoped the the additional information would be helpful. I'm sorry it wasn't. I opened Bug 354243 specifically because of the confusion evident in Bug 209520. But the gist of both bugs is this: There is something wrong with Nautilus and/or its dependencies - recent versions of Nautilus are not robust in browsing network shares. I intended, in Bug 354243, to offer a reproducible demonstration of this failure. Comments 1 and 4 outline that demonstration, but again: The network in Bug 354243 is a vanilla router; a vanilla computer; an Iomega MDHD500-N network hard drive, running firmware K1.08 L1.0 W1.5; and an Ubuntu 9.04 beta desktop i386 CD, running in LIVE SESSION. (Sorry to shout, but last is important: live session eliminates user error in configuration, and, more important, live session is supposed to demonstrate Ubuntu's capabilities with a wide variety of hardware.) And I will anticipate the objection that this is an Iomega problem: Windows finds the Iomega NAS; smbclient finds it; smb4k even mounts it - it's not trying to hide itself. The Iomega NAS is just one among many black-box embedded SAMBA servers that a robust, desktop-ready file manager needs to be able to browse. Current Nautilus fails. -- Nautilus fails to browse any share on network to which Iomega Home Network Hard Drive (MDHD500-N, firmware K108.W15) is attached. https://bugs.launchpad.net/bugs/354243 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 354243] Re: Nautilus fails to browse any share on network to which Iomega Home Network Hard Drive (MDHD500-N, firmware K108.W15) is attached.
Just want to make sure it's understood that smbtree doesn't browse the share when run under specific conditions outlined above - particularly the fact that it was in a live CD session. Under my current, evolving (implementing work-arounds) configuration, smbtree does produce output, listed below. Are there bad interactions among multiple SAMBA servers that cannot be isolated to configuration of single server? Given that many network devices use embedded SAMBA servers, shouldn't Nautilus, hence gvfs, be extremely robust in browsing and mounting shares? I post the following (from current, not-controlled-experiment configuration), noting the LANMAN error message, and hoping extraneous information does not muddy diagnosis; but stand by previous experimental results - Iomega NAS should have been browse-able from a live CD session, and was not: === step...@inspiron-ubuntu:~$ findsmb *=DMB +=LMB IP ADDR NETBIOS NAME WORKGROUP/OS/VERSION - 192.168.1.66IOMEGA-36AE[UTOPIA_BEACH] [R] [R] 192.168.1.100 INSPIRON-UBUNTU [UTOPIA_BEACH] [Unix] [Samba 3.2.3] 192.168.1.102 UBUNTU-810+[UTOPIA_BEACH] [Unix] [Samba 3.2.3] step...@inspiron-ubuntu:~$ smbclient -L 192.168.1.66 Enter stephen's password: Domain=[UTOPIA_BEACH] OS=[R] Server=[R] Server requested LANMAN password (share-level security) but 'client lanman auth' is disabled tree connect failed: SUCCESS - 0 step...@inspiron-ubuntu:~$ smbtree Password: UTOPIA_BEACH \\UBUNTU-810Samba 3.2.3 \\UBUNTU-810\clp300 Samsung CLP-300N at 192.168.1.88 \\UBUNTU-810\IPC$ IPC Service (Samba 3.2.3) \\UBUNTU-810\the.kamms the.kamms Samba Share \\UBUNTU-810\household Read Only Samba Share \\UBUNTU-810\gnucashGnucash Samba Share \\UBUNTU-810\betsey Betsey's Samba Share \\UBUNTU-810\stephenStephen's Samba Share \\IOMEGA-36AE Server requested LANMAN password (share-level security) but 'client lanman auth' is disabled failed tcon_X with NT_STATUS_OK \\INSPIRON-UBUNTU Inspiron-Ubuntu server (Samba, Ubuntu) \\INSPIRON-UBUNTU\CLP-300N Samsung Color Laser Printer \\INSPIRON-UBUNTU\IPC$ IPC Service (Inspiron-Ubuntu server (Samba, Ubuntu)) \\INSPIRON-UBUNTU\print$Printer Drivers step...@inspiron-ubuntu:~$ -- Nautilus fails to browse any share on network to which Iomega Home Network Hard Drive (MDHD500-N, firmware K108.W15) is attached. https://bugs.launchpad.net/bugs/354243 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 354243] Re: Nautilus fails to browse any share on network to which Iomega Home Network Hard Drive (MDHD500-N, firmware K108.W15) is attached.
Just want to make sure it's understood that smbtree doesn't browse the share when run under specific conditions outlined above - particularly the fact that it was in a live CD session. Under my current, evolving (implementing work-arounds) configuration, smbtree does produce output, listed below. Are there bad interactions among multiple SAMBA servers that cannot be isolated to configuration of single server? Given that many network devices use embedded SAMBA servers, shouldn't Nautilus, hence gvfs, be extremely robust in browsing and mounting shares? I post the following (from current, not-controlled-experiment configuration), noting the LANMAN error message, and hoping extraneous information does not muddy diagnosis; but stand by previous experimental results - Iomega NAS should have been browse-able from a live CD session, and was not: === step...@inspiron-ubuntu:~$ findsmb *=DMB +=LMB IP ADDR NETBIOS NAME WORKGROUP/OS/VERSION - 192.168.1.66IOMEGA-36AE[UTOPIA_BEACH] [R] [R] 192.168.1.100 INSPIRON-UBUNTU [UTOPIA_BEACH] [Unix] [Samba 3.2.3] 192.168.1.102 UBUNTU-810+[UTOPIA_BEACH] [Unix] [Samba 3.2.3] step...@inspiron-ubuntu:~$ smbclient -L 192.168.1.66 Enter stephen's password: Domain=[UTOPIA_BEACH] OS=[R] Server=[R] Server requested LANMAN password (share-level security) but 'client lanman auth' is disabled tree connect failed: SUCCESS - 0 step...@inspiron-ubuntu:~$ smbtree Password: UTOPIA_BEACH \\UBUNTU-810Samba 3.2.3 \\UBUNTU-810\clp300 Samsung CLP-300N at 192.168.1.88 \\UBUNTU-810\IPC$ IPC Service (Samba 3.2.3) \\UBUNTU-810\the.kamms the.kamms Samba Share \\UBUNTU-810\household Read Only Samba Share \\UBUNTU-810\gnucashGnucash Samba Share \\UBUNTU-810\betsey Betsey's Samba Share \\UBUNTU-810\stephenStephen's Samba Share \\IOMEGA-36AE Server requested LANMAN password (share-level security) but 'client lanman auth' is disabled failed tcon_X with NT_STATUS_OK \\INSPIRON-UBUNTU Inspiron-Ubuntu server (Samba, Ubuntu) \\INSPIRON-UBUNTU\CLP-300N Samsung Color Laser Printer \\INSPIRON-UBUNTU\IPC$ IPC Service (Inspiron-Ubuntu server (Samba, Ubuntu)) \\INSPIRON-UBUNTU\print$Printer Drivers step...@inspiron-ubuntu:~$ -- Nautilus fails to browse any share on network to which Iomega Home Network Hard Drive (MDHD500-N, firmware K108.W15) is attached. https://bugs.launchpad.net/bugs/354243 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 354243] Re: Nautilus fails to browse any share on network to which Iomega Home Network Hard Drive (MDHD500-N, firmware K108.W15) is attached.
Yes this bug is reproducible, which I had attempted to make that clear in the original bug report. The following is more explicit. This bug occurs when Ubuntu is being run live from an i386 distribution CD: 7.10, 8.04, 8.04.2, 8.10, or 9.04 beta - the kind one burns from the isos available here: http://www.ubuntu.com/GetUbuntu/download To reproduce this bug, you will also need the following: -An i386-type vanilla box with an optical drive and an ethernet port, fully capable of running the Ubuntu distribution CD referenced above. -A vanilla router - I use a Linksys WRT54G. My router is also connected to the internet through PPPoE to a DSL modem. -An Iomega Home Network Hard Drive (MDHD500-N), running firmware K108.W15. Iomega advertises this as supporting Debian 3.0. Have the Gnome developers written code which is not backwards compatible with this hardware? -Two ethernet cables. Connect your vanilla i386 computer and Iomega NAS to the router, each with its own ethernet cable. Feel free to hard-reset the Iomega NAS, to remove any configuration questions. Reboot the computer using the live Ubuntu disk - be sure the optical drive has a high priority in the BIOS boot order. Attempt to browse to the PUBLIC share of the Iomega NAS using Nautilus; you won't find it. However, findsmb and smbclient -L 192.168.1.xxx do find it. There's your bug. A computer running Windows Explorer in Windows XP would find the Iomega share(s). Further experimentation will show that the Iomega drive effectively shileds itself and all other SAMBA shares on the network from Nautilus browsing. The full configuration of the Iomega NAS is not available to the end user, but that would actually be the typical situation for most end users on networks. Nautilus browsing of the network apparently yields a stream of similar bugs. I contend that I have outlined a simple experiment that is universally reproducible by Gnome maintainers, an experiment that should solve many bugs in that stream. -- Nautilus fails to browse any share on network to which Iomega Home Network Hard Drive (MDHD500-N, firmware K108.W15) is attached. https://bugs.launchpad.net/bugs/354243 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 354243] Re: Nautilus fails to browse any share on network to which Iomega Home Network Hard Drive (MDHD500-N, firmware K108.W15) is attached.
Nautilus: PlaceNetwork produces attach001.png ** Attachment added: attach001.png http://launchpadlibrarian.net/24766726/attach001.png -- Nautilus fails to browse any share on network to which Iomega Home Network Hard Drive (MDHD500-N, firmware K108.W15) is attached. https://bugs.launchpad.net/bugs/354243 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 354243] Re: Nautilus fails to browse any share on network to which Iomega Home Network Hard Drive (MDHD500-N, firmware K108.W15) is attached.
... then clicking on any share produces attach002.png (This drive has had a firmware upgrade and hardware reset immediately before answering your questions, which apparently does not delete drive contents.) ** Attachment added: attach002.png http://launchpadlibrarian.net/24766798/attach002.png -- Nautilus fails to browse any share on network to which Iomega Home Network Hard Drive (MDHD500-N, firmware K108.W15) is attached. https://bugs.launchpad.net/bugs/354243 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 354243] Re: Nautilus fails to browse any share on network to which Iomega Home Network Hard Drive (MDHD500-N, firmware K108.W15) is attached.
Having been just reset, workgroup=WORKGROUP, which I assume is appropriate for live session. It appears smbtree does not browse correctly; see terminal grab below: To run a command as administrator (user root), use sudo command. See man sudo_root for details. ubu...@ubuntu:~$ findsmb *=DMB +=LMB IP ADDR NETBIOS NAME WORKGROUP/OS/VERSION - 192.168.1.104 STORAGE-36AE [WORKGROUP] [R] [R] ubu...@ubuntu:~$ ubu...@ubuntu:~$ ubu...@ubuntu:~$ smbclient -L 192.168.1.104 Enter ubuntu's password: Domain=[WORKGROUP] OS=[R] Server=[R] Sharename Type Comment - --- PUBLIC Disk Betsey_Net Disk Stephen_Net Disk linux-backupDisk IPC$IPC Domain=[WORKGROUP] OS=[R] Server=[R] Server Comment ---- WorkgroupMaster ---- ubu...@ubuntu:~$ ubu...@ubuntu:~$ ubu...@ubuntu:~$ smbtree Password: ubu...@ubuntu:~$ -- Nautilus fails to browse any share on network to which Iomega Home Network Hard Drive (MDHD500-N, firmware K108.W15) is attached. https://bugs.launchpad.net/bugs/354243 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 354243] Re: Nautilus fails to browse any share on network to which Iomega Home Network Hard Drive (MDHD500-N, firmware K108.W15) is attached.
If you're looking for a specific log I have yet to produce, please point to it. These results were produced with a live session of Ubuntu 9.04 beta desktop i386. I intend to proceed with a work-around on my installations, so the Iomega NAS will no longer be in its hard-reset state. I am willing to follow further instructions using a boot from a live session disk, however. Let me know if you prefer an earlier version. sdk -- Nautilus fails to browse any share on network to which Iomega Home Network Hard Drive (MDHD500-N, firmware K108.W15) is attached. https://bugs.launchpad.net/bugs/354243 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 354243] [NEW] Nautilus fails to browse any share on network to which Iomega Home Network Hard Drive (MDHD500-N, firmware K108.W15) is attached.
Public bug reported: Binary package hint: gvfs Nautilus fails to browse any share on network to which Iomega Home Network Hard Drive (MDHD500-N, firmware K108.W15) is attached. Might be 209520 or 296673 - but this should make diagnosis easier. Reproduced bug using Ubuntu i386 distribution disks for 7.10, 8.04, 8.04.2, 8.10 and 9.04 beta - in other word, standard Ubuntu configuration. The Iomega NAS had immediately prior had a firmware upgrade with subsequent hard reset. This should be reproducible by maintainers. The Iomega server is SAMBA or SAMBA-like, with a rudimentary html interface. It is normal for end users to not have control over all server settings in many situations, so this is still a gvfs bug. As with similar bugs, all SAMBA shares are reported correctly with findsmb and smbclient, and can be mounted using smb4k. ** Affects: gvfs (Ubuntu) Importance: Undecided Status: New -- Nautilus fails to browse any share on network to which Iomega Home Network Hard Drive (MDHD500-N, firmware K108.W15) is attached. https://bugs.launchpad.net/bugs/354243 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 300162] Re: bad security update
Same here: [EMAIL PROTECTED]:~$ sudo apt-get --fix-missing upgrade Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be upgraded: hpijs hplip hplip-data 3 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 7522kB of archives. After unpacking 0B of additional disk space will be used. Do you want to continue [Y/n]? Y Get:1 http://us.archive.ubuntu.com gutsy-updates/main hplip-data 2.7.7.dfsg.1-0ubuntu5.1 [6898kB] Get:2 http://us.archive.ubuntu.com gutsy-updates/main hplip 2.7.7.dfsg.1-0ubuntu5.1 [290kB] Get:3 http://us.archive.ubuntu.com gutsy-updates/main hpijs 2.7.7+2.7.7.dfsg.1-0ubuntu5.1 [334kB] Fetched 7523kB in 1m33s (80.5kB/s) Failed to fetch http://us.archive.ubuntu.com/ubuntu/pool/main/h/hplip/hplip-data_2.7.7.dfsg.1-0ubuntu5.1_all.deb Size mismatch Failed to fetch http://us.archive.ubuntu.com/ubuntu/pool/main/h/hplip/hplip_2.7.7.dfsg.1-0ubuntu5.1_i386.deb Size mismatch Failed to fetch http://us.archive.ubuntu.com/ubuntu/pool/main/h/hplip/hpijs_2.7.7+2.7.7.dfsg.1-0ubuntu5.1_i386.deb Size mismatch [EMAIL PROTECTED]:~$ -- bad security update https://bugs.launchpad.net/bugs/300162 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 151145] Re: Evince print fails with Postscript driver
evince 2.20.1 Samsung CLP-300N Won't print: ** Attachment added: CoolMax17-159-058Feb01Feb2508lh15.pdf http://launchpadlibrarian.net/11989188/CoolMax17-159-058Feb01Feb2508lh15.pdf -- Evince print fails with Postscript driver https://bugs.launchpad.net/bugs/151145 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 151145] Re: Evince print fails with Postscript driver
evince 2.20.1 Samsung CLP-300N Will print ** Attachment added: EVGA11MIRsFeb1Feb2908ll97.pdf http://launchpadlibrarian.net/11989227/EVGA11MIRsFeb1Feb2908ll97.pdf -- Evince print fails with Postscript driver https://bugs.launchpad.net/bugs/151145 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 151145] Re: Evince print fails with Postscript driver
(Sorry about multiple posts - It is not clear to me how to include multiple attachments in single comment or edit previous comments.) In the Won't print: case, evince creates blank output.ps and blank preview, as well as not printing. Given these are rebate forms, I'd agree this is critical. -- Evince print fails with Postscript driver https://bugs.launchpad.net/bugs/151145 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 173148] Openoffice.org apps start with tiny toolbar fonts
Public bug reported: Binary package hint: openoffice.org I fresh-installed Gutsy i386 recently. I used the spreadsheet once without noticing any problems, but the first time I opened a Powerpoint presentation, the openoffice.org menu bars had a tiny font. Other Oo.org apps now also had tiny fonts. The ToolsOptionsViewUser InterfaceScaling function maxed out at 130% (a separate bug?). While attempting to fix or at least circumscribe the problem, I adjusted my Gnome SystemPreferencesAppearanceFontsDetailsResolution, which I had manually set to 114 dpi almost immediately after the Gutsy install. I reduced it to 96 dpi and below. This had the odd effect of reducing the apparent size of my Desktop fonts (expected) while _increasing_ the apparent size of the Openoffice.org toolbar and dialog fonts. Furthermore, increasing the Gnome System Font Resolution back up to 111 dpi (based on my monitor specs and display resolution) made the Openoffice.org fonts grow yet bigger. I could then set ToolsOptionsViewUser InterfaceScaling at 100%. That is to say, I solved my problem, but I don't understand why it happened in the first place, and why the system did not respond reproducibly to some simple adjustments. This seems to be more of a bug than a feature. ** Affects: openoffice.org (Ubuntu) Importance: Undecided Status: New ** Description changed: Binary package hint: openoffice.org - I fresh-installed Gutsy i386 a recently. I used the spreadsheet once + I fresh-installed Gutsy i386 recently. I used the spreadsheet once without noticing any problems, but the first time I opened a Powerpoint presentation, the openoffice.org menu bars had a tiny font. The ToolsOptionsViewUser InterfaceScaling function maxes out at 130% (a separate bug?). While attempting to fix or at least circumscribe the problem, I adjusted my Gnome SystemPreferencesAppearanceFontsDetailsResolution, which I had manually set to 114 dpi almost immediately after the Gutsy install. I reduced it to 96 dpi and below. This had the odd effect of reducing the apparent size of my Desktop fonts (expected) while _increasing_ the apparent size of the Openoffice.org toolbar and dialog fonts. Furthermore, increasing the Gnome System Font Resolution back up to 111 dpi (based on my monitor specs and display resolution) made the Openoffice.org fonts grow yet bigger. I could then set ToolsOptionsViewUser InterfaceScaling at 100%. That is to say, I solved my problem, but I don't understand why it happened in the first place, and why the system did not respond reproducibly to some simple adjustments. This seems to be more of a bug than a feature. ** Description changed: Binary package hint: openoffice.org I fresh-installed Gutsy i386 recently. I used the spreadsheet once without noticing any problems, but the first time I opened a Powerpoint - presentation, the openoffice.org menu bars had a tiny font. The - ToolsOptionsViewUser InterfaceScaling function maxes out at 130% (a - separate bug?). + presentation, the openoffice.org menu bars had a tiny font. Other + Oo.org apps now also had tiny fonts. The ToolsOptionsViewUser + InterfaceScaling function maxed out at 130% (a separate bug?). While attempting to fix or at least circumscribe the problem, I adjusted my Gnome SystemPreferencesAppearanceFontsDetailsResolution, which I had manually set to 114 dpi almost immediately after the Gutsy install. I reduced it to 96 dpi and below. This had the odd effect of reducing the apparent size of my Desktop fonts (expected) while _increasing_ the apparent size of the Openoffice.org toolbar and dialog fonts. Furthermore, increasing the Gnome System Font Resolution back up to 111 dpi (based on my monitor specs and display resolution) made the Openoffice.org fonts grow yet bigger. I could then set ToolsOptionsViewUser InterfaceScaling at 100%. That is to say, I solved my problem, but I don't understand why it happened in the first place, and why the system did not respond reproducibly to some simple adjustments. This seems to be more of a bug than a feature. -- Openoffice.org apps start with tiny toolbar fonts https://bugs.launchpad.net/bugs/173148 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 57923] Re: Opening firefox by clicking on links in thunderbird breaks https
I am using Ubuntu 6.06 LTS desktop, 64-bit; updated as prompted by Synaptic. My e-mail client is mozilla-thunderbird; firefox is selected as Web Browser in Preferred Applications. After experiencing Bug #89023, I Completely Removed firefox (and thunderbird) using Synaptic. After re-booting, I installed firefox 1.5.dfsg+1.5.0.10-0ubuntu0.6.06.2 and mozilla-thunderbird 1.5.0.9-0ubuntu0.6.06. See details https://launchpad.net/ubuntu/+source/firefox/+bug/89023. Https function was restored in the case where firefox was already open, however, in the case where firefox is closed, thunderbird is open, and I click a link to an https site, the Personal Security Manager error message referred above and in the initial Bug #89023 report appears. I cannot open a link to https from within an e-mail unless firefox is already open. It appears that other browers, such as dillo and mozilla, work correctly as Preferred Application. -- Opening firefox by clicking on links in thunderbird breaks https https://launchpad.net/bugs/57923 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89023] Re: Update of Firefox disables PSM (not more SSL or saved passwords)
Sorry, but a simple Synaptic update using Firefox 1.5.dfsg+1.5.0.10-0ubuntu0.6.06.2 re-broke my partially functional Firefox. The patch did not work for me I will try complete removal and re-install, and see if that works, again. -- Update of Firefox disables PSM (not more SSL or saved passwords) https://launchpad.net/bugs/89023 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89023] Re: Update of Firefox disables PSM (not more SSL or saved passwords)
OK, after Complete Removal and re-installation, I am in the same situation reported in my comment of 2007-03-02 02:51:13 UTC. In other words, in my installation, 1.5.dfsg+1.5.0.10-0ubuntu0.6.06.2 is, from the user's perspective, functionally the same as 1.5.dfsg+1.5.0.10-0ubuntu0.6.06.1 Could there be a 64-bit issue left unpatched? -- Update of Firefox disables PSM (not more SSL or saved passwords) https://launchpad.net/bugs/89023 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 89023] Re: Update of Firefox disables PSM (not more SSL or saved passwords)
Alexander Sack wrote: Most likely you did not just restart firefox after upgrade properly. ??? I clicked on the launcher on the panel, as usual. If you mean I didn't shut down Firefox before upgrade, my recollection is that I in fact did, out of normal habit. But to test your hypothesis, using Synaptic I performed Complete Removal of: mozilla-thunderbird firefox firefox-gnome-support mozilla-browser j2re1.4-mozilla-plugin mozilla-psm Then re-booted. The, using Synaptic, I installed: firefox 1.5.dfsg+1.5.0.10-0ubuntu0.6.06.2 firefox-gnome-support 1.5.dfsg+1.5.0.10-0ubuntu0.6.06.2 mozilla-thunderbird 1.5.0.9-0ubuntu0.6.06 and I replicated exactly the situation described in my post of 2007-03-02 02:51:13 UTC: https works from within Firefox, but clicking on link from Thunderbird e-mail produces PSM error. Does this need to be opened as a separate bug? -- Update of Firefox disables PSM (not more SSL or saved passwords) https://launchpad.net/bugs/89023 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89023] Re: Update of Firefox disables PSM (not more SSL or saved passwords)
I too am experiencing this. I use Ubuntu Dapper 6.06 LTS x86_64, kernel 2.6.15.26 Firefox update 1.5.dfsg+1.5.0.10-0ubuntu0.6.06.1 apparently broke many sites (e.g. amazon.com personal account maintenance; launchpad.net) due to above problem with PSM. Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.7.12) Gecko/20060216 Debian/1.7.12-1.1ubuntu2 allowed me to access this site. -- Update of Firefox disables PSM (not more SSL or saved passwords) https://launchpad.net/bugs/89023 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89023] Re: Update of Firefox disables PSM (not more SSL or saved passwords)
This is weird - I hope it's a clue. Using Synaptic, I Completely Removed Firefox (which automatically entailed removing two Epiphany programs and Yelp). Then I immediately re-installed FIrefox and firefox-gnome-support. Now I can access https://www.amazon.com, https://launchpad.net, etc. HOWEVER, when I click on the link https://launchpad.net/bugs/89023 as it appears in the bouncesatcanonical.com e-mail, I still get the PSM error message (I use Thunderbird). BUT I can type the same address into the address bar of an open Firefox window, and get the page. -- Update of Firefox disables PSM (not more SSL or saved passwords) https://launchpad.net/bugs/89023 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
