[Bug 1572876] Re: After Samba upgrade can't access unpassworded windows share
Is the status of this bug 'Fix released'? I'm asking because several people are reporting that verstion 4.3.9 does not fix the issue -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1572876 Title: After Samba upgrade can't access unpassworded windows share To manage notifications about this bug go to: https://bugs.launchpad.net/samba/+bug/1572876/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1572876] Re: After Samba upgrade can't access unpassworded windows share
BTW, in order to be able to access the shares I had to reinstall the older packages using: apt-get install samba=2:4.1.6+dfsg-1ubuntu2 samba-common=2:4.1.6+dfsg- 1ubuntu2 samba-libs=2:4.1.6+dfsg-1ubuntu2 samba-common-bin=2:4.1.6+dfsg- 1ubuntu2 samba-dsdb-modules=2:4.1.6+dfsg-1ubuntu2 python-samba=2:4.1.6 +dfsg-1ubuntu2 libldb1=1:1.1.16-1 python-ldb=1:1.1.16-1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1572876 Title: After Samba upgrade can't access unpassworded windows share To manage notifications about this bug go to: https://bugs.launchpad.net/samba/+bug/1572876/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1572876] Re: After Samba upgrade can't access unpassworded windows share
I have exactly the same problem -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1572876 Title: After Samba upgrade can't access unpassworded windows share To manage notifications about this bug go to: https://bugs.launchpad.net/samba/+bug/1572876/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 845577] Re: mii-tool reporting incorrect duplex mode
the bug is still present in 14.04.1 LTS: [root-~]# mii-tool eth0 eth0: negotiated 1000baseT-HD flow-control, link ok [root-~]# ethtool eth0 Settings for eth0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supported pause frame use: No Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Advertised pause frame use: Symmetric Receive-only Advertised auto-negotiation: Yes Link partner advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Link partner advertised pause frame use: Symmetric Link partner advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: MII PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: pumbg Wake-on: g Current message level: 0x0033 (51) drv probe ifdown ifup Link detected: yes -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to net-tools in Ubuntu. https://bugs.launchpad.net/bugs/845577 Title: mii-tool reporting incorrect duplex mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-tools/+bug/845577/+subscriptions -- 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 845577] Re: mii-tool reporting incorrect duplex mode
the bug is still present in 14.04.1 LTS: [root-~]# mii-tool eth0 eth0: negotiated 1000baseT-HD flow-control, link ok [root-~]# ethtool eth0 Settings for eth0: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supported pause frame use: No Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Advertised pause frame use: Symmetric Receive-only Advertised auto-negotiation: Yes Link partner advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Link partner advertised pause frame use: Symmetric Link partner advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: MII PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: pumbg Wake-on: g Current message level: 0x0033 (51) drv probe ifdown ifup Link detected: yes -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/845577 Title: mii-tool reporting incorrect duplex mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-tools/+bug/845577/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 883324] Re: False positive: Hidden file (symbolic link to directory) cannot be white-listed
I still have the same problem, it has been reported several months ago and the fix is known and is easy to implement, why don't you just fix the package? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/883324 Title: False positive: Hidden file (symbolic link to directory) cannot be white-listed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rkhunter/+bug/883324/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 217821] Re: command /nick don't work
This is not a bug, this never was a feature of aMSN and isn't a feature of the official client either. The /nick command is specific to IRC and not MSN and I see no reason for this bug to be open. I do agree though that it's a nice idea and that it could be made into a plugin (if it's not already supported by the amsnplus plugin). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/217821 Title: command /nick don't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amsn/+bug/217821/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 217821] Re: command /nick don't work
Actually, I just checked and the amsnplus plugin does support the /nick command. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/217821 Title: command /nick don't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amsn/+bug/217821/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 216872] Re: Provide OTR (off-the-record) for amsn
0.98.9 doesn't add OTR support, but I might write a plugin for it in the near future. In the meantime, for amsn-amsn encrypted communication, there's always Kryptonite. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/216872 Title: Provide OTR (off-the-record) for amsn To manage notifications about this bug go to: https://bugs.launchpad.net/amsn/+bug/216872/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1001958] Re: Include amsn package back in Ubuntu distribution
@LocutusOfBorg: The libgstfarsight dependency has been removed from amsn 0.98.9. It is not being used currently so you can remove the dependency safely. Please refer to the debian package. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1001958 Title: Include amsn package back in Ubuntu distribution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amsn/+bug/1001958/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1001958] Re: Include amsn package back in Ubuntu distribution
Ah sorry, I thought it was already accepted, it's in progress now. You can find it in the pipeline here : https://ftp-master.debian.org/new/amsn_0.98.9-1.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1001958 Title: Include amsn package back in Ubuntu distribution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amsn/+bug/1001958/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1001958] Re: Include amsn package back in Ubuntu distribution
By the way, here is the debian directory for the amsn 0.98.9 package : http://amsn-project.net/~vivia/amsn-debian.tar.bz2 I hope this is helpful. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1001958 Title: Include amsn package back in Ubuntu distribution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amsn/+bug/1001958/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 875302] Re: oneiric: undefined symbol errors, webcam doesn't work
@vivia looked at this and I think fixed it, I think it had something to do with the linker in the new version of ubuntu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/875302 Title: oneiric: undefined symbol errors, webcam doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/amsn/+bug/875302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 660395] Re: Set default download directory to ~/Downloads
Mark as invalid/already_fixed...
The latest version (and I think it's been for a while), aMSN reads
~/.config/user-dirs.dirs and takes the download directory from the
XDG_DOWNLOAD_DIR setting. The XDG user dirs, is a freedesktop standard, and we
follow it correctly. (If XDG_CONFIG_HOME environment variable, then we read the
${XDG_CONFIG_HOME}/user-dirs.dirs file instead).
The amsn_received directory is only used as a fallback, if there is no
XDG_DOWNLOAD_DIR setting.
However, for obvious reasons, this only affects new users of aMSN. If you are
upgrading, then your download dir settings will remain the same, for obvious
reasons. Note that, you can always change the download directory by going to
aMSN's Preferences window, in the Others tab.
If Ubuntu is correctly configured, then aMSN should use the ~/Downloads path by
default.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/660395
Title:
Set default download directory to ~/Downloads
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 663670] Re: empathy doesn't connect to msn - blocked connection
Hi, Found the bug and fixed. It should get committed and released soon. In the meantime, to fix it, apply this patch on papyon (in something like /usr/lib/python2.6/site-packages/papyon) and it should fix it : diff --git a/papyon/service/description/SingleSignOn/RequestMultipleSecurityTokens.py b/papyon/service/description/SingleSignOn/RequestMultipleSecurityTokens.py index 73c1127..42d7497 100644 --- a/papyon/service/description/SingleSignOn/RequestMultipleSecurityTokens.py +++ b/papyon/service/description/SingleSignOn/RequestMultipleSecurityTokens.py @@ -21,7 +21,7 @@ import xml.sax.saxutils as xml class LiveService(object): -CONTACTS = (contacts.msn.com, ?fs=1id=24000kv=7rn=93S9SWWwtw=0ver=2.1.6000.1) +CONTACTS = (contacts.msn.com, MBI) MESSENGER = (messenger.msn.com, ?id=507) MESSENGER_CLEAR = (messengerclear.live.com, MBI_KEY_OLD) MESSENGER_SECURE = (messengersecure.live.com, MBI_SSL) -- empathy doesn't connect to msn - blocked connection https://bugs.launchpad.net/bugs/663670 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 653828] [NEW] windows computers can't resolve samba share names in 10.04
Public bug reported: Binary package hint: samba After upgrading my ubuntu server from 9.04 to 10.04, the window computers couldn't resolve samba shared names anymore, the error code displayed by Windows was 0x80070035. I was using the ubuntu server as a samba server, using 'share' as the security authentication method, it has been working very well under previous ubuntu versions but, after upgrading to 10.04, the windows computers can't access the server shares anymore; the linux computers don't have any problems (I can access the shares from linux). As a workaround, I've added the name of the server in c:\windows\system32\drivers\etc\hosts; but I'd like to know how to fix the problem without modifying every windows computer. [root]# dpkg -l samba ii samba 2:3.4.7~dfsg-1ubuntu3.2 SMB/CIFS file, print, and login server for Unix [root]# cat /etc/issue Ubuntu 10.04.1 LTS \n \l Please let me know if you need additional information. Regards, Toshiro. ** Affects: samba (Ubuntu) Importance: Undecided Status: New -- windows computers can't resolve samba share names in 10.04 https://bugs.launchpad.net/bugs/653828 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 653828] [NEW] windows computers can't resolve samba share names in 10.04
Public bug reported: Binary package hint: samba After upgrading my ubuntu server from 9.04 to 10.04, the window computers couldn't resolve samba shared names anymore, the error code displayed by Windows was 0x80070035. I was using the ubuntu server as a samba server, using 'share' as the security authentication method, it has been working very well under previous ubuntu versions but, after upgrading to 10.04, the windows computers can't access the server shares anymore; the linux computers don't have any problems (I can access the shares from linux). As a workaround, I've added the name of the server in c:\windows\system32\drivers\etc\hosts; but I'd like to know how to fix the problem without modifying every windows computer. [root]# dpkg -l samba ii samba 2:3.4.7~dfsg-1ubuntu3.2 SMB/CIFS file, print, and login server for Unix [root]# cat /etc/issue Ubuntu 10.04.1 LTS \n \l Please let me know if you need additional information. Regards, Toshiro. ** Affects: samba (Ubuntu) Importance: Undecided Status: New -- windows computers can't resolve samba share names in 10.04 https://bugs.launchpad.net/bugs/653828 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 577169] Re: International charachters are not working.
ok, so I guess it's an ubuntu bug present on the norwegian version... maybe try one thing though.. go to amsn preferences, then appearance, then change encoding, and select utf-8.. it should be the system's default, but maybe it's not, that's why it fails. -- International charachters are not working. https://bugs.launchpad.net/bugs/577169 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 577169] Re: International charachters are not working.
the ./configure checks what tcl/tk you have installed locally, you'll have to not only install tcl8.4-dev and tk8.4-dev, but also run update-alternatives to make amsn's ./configure detect 8.4... either way, like I said, whether or not in the changelog, aMSN has nothing to do with that.. even if we wanted to, we couldn't.. all we do is receive keystrokes from Tk. -- International charachters are not working. https://bugs.launchpad.net/bugs/577169 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 537613] Re: messaging indicator integration
Humm... yeah, I don't think we're gonna do that.. reasons are as follow : - this looks like an ubuntu thing, not a system/linux/freedesktop thing.. I don't see why we should waste our time to match one of ubuntu's custom designs. - this is for Gtk stuff, we use Tcl/Tk, so it already doesn't fit.. not in the toolkit, not in the programming language. - we would need to write a custom library for aMSN that links with gtk (adds the gtk dependency to aMSN) just for that, and it doesn't make sense to us because we're cross-platform and cross-desktops. - How would this work on a KDE or Enlightenment environment? this isn't standard.. aMSN uses a tray icon like everybody else on the planet, and we use an extension that is freedesktop compliant.. your 'app indicator' stuff is not standard at all as far as I can tell, so I see no reason why we should integrate with that. My opinion is that if Ubuntu wants aMSN to fit better in their desktop, they should invest their own time in porting aMSN to this app indicator stuff, and send us a patch, we'll gladly review it and merge it, but I do not believe we should dedicate our resources for an ubuntu-specific extension to the desktop. -- messaging indicator integration https://bugs.launchpad.net/bugs/537613 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 577169] Re: International charachters are not working.
Like I said, it doesn't make sense.. downgrading to 0.98.1 could have fixed it maybe because it uses tcl/tk 8.4 instead of 8.5 or the contrary,. or maybe one package had a patch that changed 'wish' to 'wish8.5' in the amsn file... Or maybe you use some input method that fails to work properly... anyways LocutusOfBorg clearly showed a screenshot of it working, you seem to be the only one with the problem and I'm guessing you are doing something wrong.. and like I said, aMSN has ZERO CODE for handling that, it's all tk, so it's not aMSN, it can't be aMSN and it can't be a bug from one version of aMSN to another. -- International charachters are not working. https://bugs.launchpad.net/bugs/577169 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 577169] Re: International charachters are not working.
No reason for such a bug to be introduced in a new version of aMSN.. can you check if the aMSN upgrade introduced a change in the tcl/tk version installed ? I'd guess the issue is a badly compiled version of tcl/tk or something like that. -- International charachters are not working. https://bugs.launchpad.net/bugs/577169 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 594790] Re: amsn translation error
Hi, this looks like an invalid bug to me, first it can't be reproduced here, secondly, the title of the bug makes no sense with the description... -- amsn translation error https://bugs.launchpad.net/bugs/594790 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 594790] Re: amsn translation error
That's what I also thought in the beginning, but there is no 'contact refused' or anything like that, since ignoring the window means you just ignore it, it will show up the next time you connect, it won't refuse the contact or anything. So clicking cancel will not yield any popup window at all, so it couldn't be a translation error. -- amsn translation error https://bugs.launchpad.net/bugs/594790 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 594790] Re: amsn translation error
maybe you simply clicked the wrong button and actually added that contact :p -- amsn translation error https://bugs.launchpad.net/bugs/594790 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 584868] Re: input not possible in chat after amsn idle for some time
Thanks for a nice report. The issue is explained here http://www.amsn-project.net/forums/index.php/topic,414.0.html Basically, even if you don`t use the program for inptuing chinese, as long as it`s running, it will cause that issue. This was reported with SCIM and XIM too iirc. Also, I think iBus is based on SCIM so it acts the same. Anyways, it should work correctly with UIM. I don`t know how to use it or anything though. Either way, this bug is not related to aMSN, it should either be sent to Tcl/Tk developpers or to SCIM developers. -- input not possible in chat after amsn idle for some time https://bugs.launchpad.net/bugs/584868 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 584868] Re: input not possible in chat after amsn idle for some time
Humm, you can probably find other apps depending on tk8.5, but since it's a random bug that appears at a random time after using the application, it's not really easy to reproduce in order to know where it comes from... You could even probably just type 'wish' in a terminal and type 'pack [text .t]' to get a text widget in the main application and see if you can reproduce it. Either way, I thought this locking up would be discussed in that thread I sent you, maybe I'm wrong and it's discussed in other threads of the forum.. but I'm still pretty sure that this is a SCIM issue.. considering that I guessed that from the start without any input from your part I think there's a way to disable the input manager, I think something like 'export X_MODIFIERS=' or something like that.. I'm not sure, since like I said, I never used any input manager... that would probably show that the locking issue disappears if SCIM is disabled for aMSN. Maybe search aMSN forums for SCIM and you might find an answer... -- input not possible in chat after amsn idle for some time https://bugs.launchpad.net/bugs/584868 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 584868] Re: input not possible in chat after amsn idle for some time
As far as I know, this is caused because you're using a buggy input method. SCIM if I remember correctly.. Try replacing it with UIM and it should work correctly. -- input not possible in chat after amsn idle for some time https://bugs.launchpad.net/bugs/584868 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 465644] Re: Screen refresh problems when minimizing aMSN to tray using Close button or title bar
There is nothing to look at. This isn't an aMSN bug, this is quite clearly a window manager bug, and in this case, this is a Compiz bug. Please clone/reassign this bug to compiz. Note that comment #4 says that it happens sometimes with other applications too. -- Screen refresh problems when minimizing aMSN to tray using Close button or title bar https://bugs.launchpad.net/bugs/465644 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 216872] Re: Provide OTR (off-the-record) for amsn
This isn't a bug, this is just a feature request. And the answer is no (from me), I won't be writing an OTR plugin because I don't want to be writing Tcl bindings for the OTR library. But to answer comment #2, yes, we have different ways of adding encryption to messages. The best one as far as I know is Kryptonite, which encrypts data with your GPG keys and ensures an encrypted stream between you and your amsn-with-kryptonite friends. -- Provide OTR (off-the-record) for amsn https://bugs.launchpad.net/bugs/216872 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 537613] Re: messaging indicator integration
what's message indicator exactly ? -- messaging indicator integration https://bugs.launchpad.net/bugs/537613 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 407661] Re: Default download path be XDG_DOWNLOAD_DIR
Humm... nice, I didn't know about this XDG_DOWNLOAD_DIR. I will make the change and commit it to aMSN's SVN in the next hour or so. However note that the download directory is user-configurable, so we can't just change a user's config, or change the directory the user is expecting, so the change (use XDG_DOWNLOAD_DIR instead of ~/amsn_received) will only be seen by new users (when you create a new profile in aMSN). -- Default download path be XDG_DOWNLOAD_DIR https://bugs.launchpad.net/bugs/407661 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 407661] Re: Default download path be XDG_DOWNLOAD_DIR
Fixed upstream for new aMSN profiles : http://amsn.svn.sf.net/viewvc/amsn?view=revrevision=12033 Enjoy! -- Default download path be XDG_DOWNLOAD_DIR https://bugs.launchpad.net/bugs/407661 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 537613] Re: messaging indicator integration
Sorry, I don't know what that is. I don't use ubuntu, or gnome for that matter (E17 user here). So I'm a bit clueless at what this is or what i'm required to do. If someone can point me to examples, API documentation, code samples and also if possible CLI commands for doing this, I'd be grateful. aMSN is in Tcl/Tk, so there is a small chance that we'd be able to integrate into this anyways, unless there's an external command to launch, like with notify-send for libnotify (which aMSN does when you enable the notify plugin). -- messaging indicator integration https://bugs.launchpad.net/bugs/537613 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 407661] Re: Default download path be XDG_DOWNLOAD_DIR
or just apply the patch to your amsn, it's tcl so no need to compile anything, just patch it and run it -- Default download path be XDG_DOWNLOAD_DIR https://bugs.launchpad.net/bugs/407661 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 177010] Re: Provide legend for lists in privacy tab
Humm.. I think the whole interface changed a lot since this bug was created, we changed the colors and how to represent who is where. We also added a color for each group (green for AL, red for BL, yellow background for CL and red background for RL) and the colors of each entry (background and foreground) represent the colors in the header of each list. I think this can be considered as a 'legend'. It's now much more intuitive and people understand how it works much more easily (it's been years since the last user asked us how it works). If necessary, there's always the FAQ which people can refer to : http://www.amsn-project.net/wiki/FAQ#In_the_preferences.27_privacy_tab.2C_what_do_those_four_lists_mean.3F http://www.amsn-project.net/wiki/FAQ#In_the_preferences.27_privacy_tab.2C_what_do_the_different_colors_in_the_contacts_mean.3F If you think something is still needed, let us know what exactly. -- Provide legend for lists in privacy tab https://bugs.launchpad.net/bugs/177010 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 177010] Re: Provide legend for lists in privacy tab
@Locutus: no problem, as far as I'm concerned, it should be closed. @Pander: Yes, people can figure out what the colors are, and if they can't, then it's best for them not to touch that section at all.. The privacy tab is really meant for advanced users, not for beginners, and I would rather not have n00bs playing around with it. So no legend.. good, I'd consider it a feature rather than a bug :) Some kind of anti-n00b security system :) If you have something to suggest though, let me know. -- Provide legend for lists in privacy tab https://bugs.launchpad.net/bugs/177010 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 177010] Re: Provide legend for lists in privacy tab
humm.. not sure I have the rights.. I see a combobox with 'invalid, fix commited, fix released, .. but no won't fix, maybe someone else can do it. -- Provide legend for lists in privacy tab https://bugs.launchpad.net/bugs/177010 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 478899] [NEW] approx don't listen on any interface but localhost
Public bug reported: Binary package hint: approx Look at this (the local IP is 192.168.0.1, there's no iptables running): [root-~]# telnet localhost Trying ::1... Connected to localhost. Escape character is '^]'. Fatal error: exception Invalid_argument(index out of bounds) Connection closed by foreign host. [root-~]# telnet 192.168.0.1 Trying 192.168.0.1... telnet: Unable to connect to remote host: Connection refused I've also added '$interface any' in approx.conf but still doesn't work. ** Affects: approx (Ubuntu) Importance: Undecided Status: New -- approx don't listen on any interface but localhost https://bugs.launchpad.net/bugs/478899 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 478899] Re: approx don't listen on any interface but localhost
I forgot to mention: this is kubuntu 9.10 -- approx don't listen on any interface but localhost https://bugs.launchpad.net/bugs/478899 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 471794] [NEW] failed to boot if /var/tmp and /tmp specified in /etc/fstab
Public bug reported: Binary package hint: mountall I've upgraded to Karmik and now the system does not boot anymore, I get the following error: One or more of the mounts listed in /etc/fstab cannot yet be mounted: /tmp: waiting for /dev/shm /var/tmp: waiting for /dev/shm If I comment the following lines in my /etc/fstab, the system boots: /dev/shm /var/tmp none bind 0 0 /dev/shm /tmp none bind 0 0 Please let me know how to fix this, for security reasons I want to use these virtual filesystems. ** Affects: mountall (Ubuntu) Importance: Undecided Status: New -- failed to boot if /var/tmp and /tmp specified in /etc/fstab https://bugs.launchpad.net/bugs/471794 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 371103] Re: aMSN fails to launch after upgrading to Jaunty
Hi, thanks omega13a and petski for the great investigation! the PATH is set before plugins are loaded, but the plugins are loaded before you connect and the msntranslator/gnotify plugin does a simple package require http, which loads the latest version (2.7.2). We know that the version 2.7.2 of http is broken that's why we require the exact version 2.4.4 that ships with aMSN. Unfortunately, since 2.7.2 was already loaded, 2.4.4 can't be loaded, which results in this problem. The easy solution would be to do the package require -exact http 2.4.4 before loading any plugins, this way, when the plugins do require http, they'll get the currently loaded 2.4.4! Here is a patch that you could apply to fix this issue permanently for other users (quite a few jaunty users complained about this) : http://amsn.svn.sourceforge.net/viewvc/amsn?view=revrevision=11166 thanks for your help, KaKaRoTo -- aMSN fails to launch after upgrading to Jaunty https://bugs.launchpad.net/bugs/371103 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 371103] Re: aMSN fails to launch after upgrading to Jaunty
great! Pablo: I'm curious, changing the bug status to Fix committed, does it mean that ubuntu 9.04 now has a new update for aMSN that includes that patch? Thanks, KaKaRoTo -- aMSN fails to launch after upgrading to Jaunty https://bugs.launchpad.net/bugs/371103 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 367515] Re: jaunty update failed with 'package authentication error'
As a matter of fact I have a Debian machine with 'approx' installed; it has been working perfectly in previous upgrades. I don't know if you did anything on your side, but I've just tried again (without doing any modification) and now it is working ok. Thanks anyway for your help. Regards, -- jaunty update failed with 'package authentication error' https://bugs.launchpad.net/bugs/367515 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 367515] [NEW] jaunty update failed with 'package authentication error'
Public bug reported: Binary package hint: update-manager Below is the list of packages with authentication error. I'm running intrepid and tried to upgrade to jaunty. Let me know if you need additional information. bluetooth bluez bluez-alsa bluez-cups bluez-gstreamer bluez-utils consolekit cups cups-bsd cups-client cups-common cupsys cupsys-bsd cupsys-client cupsys-common libbluetooth3 libck-connector0 libcups2 libcupsimage2 libcupsys2 libmjpegtools-1.9 libpackagekit-glib11 libpackagekit-qt11 libpam-ck-connector libsoup-gnome2.4-1 libsoup2.4-1 mjpegtools packagekit packagekit-backend-apt python-cupshelpers python-packagekit screen-profiles system-config-printer-common update-manager-core update-manager-kde ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New -- jaunty update failed with 'package authentication error' https://bugs.launchpad.net/bugs/367515 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 367515] Re: jaunty update failed with 'package authentication error'
Sure, here's the zip file (I've tried several times to upgrade, but always had errors). ** Attachment added: contents of /var/log/dist-upgrade http://launchpadlibrarian.net/26011044/dist-upgrade.zip -- jaunty update failed with 'package authentication error' https://bugs.launchpad.net/bugs/367515 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 328607] Re: amsn shouldn't use notifications with actions
still waiting for an answer... -- amsn shouldn't use notifications with actions https://bugs.launchpad.net/bugs/328607 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 328607] Re: amsn shouldn't use notifications with actions
Hi Mirco, no there is no TCL bindings for libnotify, thanks for adding that text about notify-send in that guideline. As I said before, that's exactly what the notify plugin for aMSN does! From your mail, it seems that you contacted the author and that you require some changes to the notify plugin for it to work on jaunty.. however I don't understand, if we use notify-send, then it should just work, right ? Anyways, I spoke to the author in IRC, and he said that apparently (from what he understood) that the jaunty notify-send doesn't support the --timeout option.. I'd like to know more about this.. why did you drop the --timeout option? and what is the timeout if notify-send doesn't support it ? is it a global preference now or something? Anyways, in my opinion notify-send should not fail if the --timeout option is passed, it should just ignore it if the notify-osd daemon doesn't support the timeout capability (or whatever method you use for determining that stuff), it should just ignore it and maybe output a warning. Removing the option is just a break in the API and unless you rename the tool to notify-send2 or something, then it's really bad for backward compatibility, etc... Anyways, what solution do you propose? How can we see if the notify-send on the system is the one from jaunty or from an older version or other distro? Do we need a hack in the code to do a 'exec notify-send --help | grep timeout' to see if it supports the option ? I personally think that all of this is not an aMSN bug, I think it should be reassigned as a notify-send bug because it breaks compatibility... Anyways, if I misunderstood, then sorry about the rant.. then could you please explain to us in detail what exactly is it that you need modified in the notify plugin for it to be the way you like? And if some jaunty specific changes are necessary, can you describe exactly how we can do a check to see what notify-send supports or doesn't support? And if I was right, tell me what you think about reassigning the bug as a notify-send bug since it breaks backward compatibility. p.s: I gave the link to this bug to the plugin's author, so I think it would be best to keep all further discussion here for completeness and to keep everything public, instead of having half the info in a private mail to someone. Thanks, KaKaRoTo -- amsn shouldn't use notifications with actions https://bugs.launchpad.net/bugs/328607 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 328607] Re: amsn shouldn't use notifications with actions
Hi, Thanks James for making it clearer.. in my mind notification server = the main MSN server being used for presence/chat (it's called the notification server) and the supports actions in my head meant that a peer supports receiving chat messages of type 'actions' (which is a specific msn message type). anyways, well this looks complicated and we won't be planning on implementing that. You could take a look at the notify plugin for aMSN as its purpose is to replace the amsn notifications with external notifications (using 'notify-send').. If that's different than what you request then I guess it could be patched to use your own notification-daemon or something, but since this is a plugin, the aMSN team is not responsible, you would have to patch it yourself or find the original author and ask him kindly. It seems fairly easy, and the path to nofify-send is configurable, so if your application is using a notify-send compatible command arguments, then it should just work. I hope this answers your question. p.s: note that amsn is a Tcl program and is multiplatform, so the core code is meant to be multiplatform and use Tcl. For extra stuff like desktop integration and platform specific tasks, then a plugin would be created, which is the purpose of the 'notify' plugin : http://amsn.svn.sourceforge.net/viewvc/amsn/trunk/amsn- extras/plugins/notify/ -- amsn shouldn't use notifications with actions https://bugs.launchpad.net/bugs/328607 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 328607] Re: amsn shouldn't use notifications with actions
Hi, I just don't understand what your issue is. Can you be more specific ? what do you mean by whether the notification server supports actions?? about the second issue, it also makes no sense, it doesn't open your browser, if you get an IM while being offline, you'll see it in a chat window as an OIM. -- amsn shouldn't use notifications with actions https://bugs.launchpad.net/bugs/328607 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 260918] Re: needed: libv4l and associated application patches (or gspca stopped working in 2.6.27)
Hi, I'm an aMSN developper, and I just found out why the aMSN fix for libv4l wasn't working... there was a small mistake in the patch, we forgot to add the -DHAVE_LIBV4L to the CFLAGS... It should now be fixed in the latest SVN revision 10792. You can see the patch here : http://amsn.svn.sourceforge.net/viewvc/amsn?view=revrevision=10792 Please apply it to have a real fix for aMSN 0.97.2... Thanks, KaKaRoTo -- needed: libv4l and associated application patches (or gspca stopped working in 2.6.27) https://bugs.launchpad.net/bugs/260918 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
Re: [Bug 74126] Re: gkrellmapcupsd
Hi, The issue is solved! I hope this gets fixed in the binary without the need for a workaround... so others won't be affected if they use the default configuration. Thanks. KaKaRoTo -- gkrellmapcupsd https://launchpad.net/bugs/74126 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 74126] gkrellmapcupsd
Public bug reported: In ubuntu dapper : Ubuntu-Server 6.06.1 _Dapper Drake_ - Release i386 (20060807.1) with uname -a : Linux kakaroto 2.6.15-26-server #1 SMP Fri Sep 8 21:00:37 UTC 2006 i686 GNU/Linux I have gkrellm2 installed and gkrellmapcupsd installed, apcupsd is also installed and correctly configured and running. Whenever I start gkrellm, I go to the configuration window, go to plugins, then as soon as I enable the checkbox for 'gkrellmapcupsd' it crashed, showing the following error : gkrellm segmentation fault: gkrellmapcupsd (update_monitor) Aborted If I run it through gdb and ask for a backtrace, it shows me : (gdb) bt #0 0xb7816ad0 in feof () from /lib/tls/i686/cmov/libc.so.6 #1 0xb7471222 in gkrellm_init_plugin () from /usr/lib/gkrellm2/plugins/gkrellmapcupsd.so #2 0x0805a60d in gkrellm_thaw_side_frame_packing () #3 0xb794e4a8 in g_main_context_is_owner () from /usr/lib/libglib-2.0.so.0 #4 0xb794c8d6 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #5 0xb794f996 in g_main_context_check () from /usr/lib/libglib-2.0.so.0 #6 0xb794fcb8 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0 #7 0xb7daa765 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0 #8 0x0805cdd7 in main () ** Affects: gkrellmapcupsd (Ubuntu) Importance: Undecided Status: Unconfirmed -- gkrellmapcupsd https://launchpad.net/bugs/74126 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
