New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Arch Linux: AttributeError: 'str' object has no attribute 'splitline' #4

Closed
klardotsh opened this Issue Dec 3, 2011 · 3 comments

Comments

Projects
None yet
2 participants
@klardotsh

klardotsh commented Dec 3, 2011

Well, I installed statnot from the AUR (had to slightly modify the PKGBUILD by taking out a line or it wouldn't make, that's another story though) and I get this when trying to run statnot:

Unhandled exception in thread started by <function message_thread at 0x7f05def50758>
Traceback (most recent call last):
File "/usr/bin/statnot", line 204, in message_thread
update_text(get_statustext(current_notification_text))
File "/usr/bin/statnot", line 58, in update_text
first_line = text.splitline()[:-1]
AttributeError: 'str' object has no attribute 'splitline'

I've read about people having similar errors with the 'split' attribute, and supposedly the 'right' way to do it in that case was to instead import string, and do string.split(var, ) which I believe was the split delimiter. Regardless, statnot doesn't die at this point, it instead hangs and doesn't do anything, even when notify-send is called. I'm on the following:
statnot 0.0.4-1
python2 2.7.2-4

Thanks!

@halhen halhen closed this in ff3c7f4 Dec 3, 2011

@halhen

This comment has been minimized.

Owner

halhen commented Dec 3, 2011

Hi,

Thanks for reporting. Would you mind trying with this latest commit?

Thanks,
H

@klardotsh

This comment has been minimized.

klardotsh commented Dec 4, 2011

Fixed. Thanks, that was quick!

@halhen

This comment has been minimized.

Owner

halhen commented Dec 4, 2011

Yeah. I don't know how it's been so long before someone noticed. Thanks for a properly written bug description!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment