kentonv changed the topic of #sandstorm to: Welcome to #sandstorm: home of all things sandstorm.io. Say hi! | Have a question but no one is here? Try asking in the discussion group: https://groups.google.com/group/sandstorm-dev | Public logs at https://botbot.me/freenode/sandstorm/
n8a has joined #sandstorm
_whitelogger has joined #sandstorm
jemc has joined #sandstorm
taktoa has joined #sandstorm
_whitelogger has joined #sandstorm
_whitelogger has joined #sandstorm
_whitelogger has joined #sandstorm
jemc has quit [Ping timeout: 255 seconds]
_whitelogger has joined #sandstorm
pie_ has joined #sandstorm
nwf has quit [Ping timeout: 240 seconds]
nwf has joined #sandstorm
_whitelogger has joined #sandstorm
NwS has joined #sandstorm
Isla_de_Muerte has quit [Ping timeout: 240 seconds]
afuentes has joined #sandstorm
icantthinkofanic has joined #sandstorm
icantthinkofanic has quit [Client Quit]
xet7 has quit [Quit: Leaving]
pie_ has quit [Ping timeout: 260 seconds]
xet7 has joined #sandstorm
larjona has quit [Read error: Connection reset by peer]
larjona has joined #sandstorm
Telesight has joined #sandstorm
pie_ has joined #sandstorm
jemc has joined #sandstorm
Lionel_Debroux has quit [Ping timeout: 240 seconds]
jemc has quit [Ping timeout: 246 seconds]
anna_k has joined #sandstorm
michaelw has quit [Quit: Bye]
<anna_k> Has anyone else noticed outbound SMTP issues on Oasis?
Lionel_Debroux has joined #sandstorm
michaelw has joined #sandstorm
<anna_k> Beginning at about midnight ET, and persisting til now, grain sharing on Oasis gives me a "Failed to send" error and roundcube throws me an "SMTP error: [-1]."
samba__ has joined #sandstorm
jemc has joined #sandstorm
taktoa has quit [Remote host closed the connection]
jemc has quit [Ping timeout: 258 seconds]
n8a has quit [Ping timeout: 255 seconds]
samba__ has quit [Read error: Connection reset by peer]
n8a has joined #sandstorm
n8a has quit [Ping timeout: 252 seconds]
n8a has joined #sandstorm
samba__ has joined #sandstorm
Telesight has quit [Remote host closed the connection]
samba__ has quit [Read error: Connection reset by peer]
n8a has quit [Quit: Leaving]
anna_k has quit [Quit: http://www.kiwiirc.com/ - A hand crafted IRC client]
bemasc has quit [Remote host closed the connection]
samba__ has joined #sandstorm
_whitelogger has joined #sandstorm
samba__ has quit [Read error: Connection reset by peer]
<kentonv> what's the over-under on this upgrade to Wayland hosing my desktop?
<kentonv> relevant: I use nvidia binary blob drivers.
anna_k has joined #sandstorm
<kentonv> time to find out I guess
kentonv has quit [Quit: Leaving]
jemc has joined #sandstorm
kentonv has joined #sandstorm
<kentonv> holy cow, it worked
<kentonv> nevermind, it installed wayland but is still using X. Funny, on my laptop it automatically switched.
jemc has quit [Ping timeout: 240 seconds]
jemc has joined #sandstorm
<biotim> looks like it's maybe not supported with nvidia drivers yet https://askubuntu.com/questions/907727/no-way-to-choose-wayland-in-gdm-using-ubuntugnome-17-04
<kentonv> there appears to be an nvidia wayland driver package in Debian Sid
<kentonv> dunno how well it works
<kentonv> apt is giving me all sorts of trouble but I'm not sure if it's wayland-related or what. dist-upgrade wants to remove my whole desktop (gnome-shell, xorg, etc.) and I can't figure out why.
<biotim> hmm that seems to happen sometimes when there are dependency issues for a big upgrade. Sometimes you just have to remove a whole bunch of desktop related stuff and reinstall after the upgrade by installing task-gnome-desktop.
<biotim> As long as the package manager and shell don't get removed, you can still proceed.
<kentonv> it appears that it's trying to switch everything to i386 instead of amd64
<kentonv> which I definitely do not want
<biotim> hmm that's not good
<kentonv> # aptitude why-not gnome-terminal
<kentonv> i gnome-core Depends gnome-terminal (>= 3.22)
<kentonv> i A gnome-terminal Conflicts gnome-terminal:i386
<kentonv> i A gnome-terminal Provides gnome-terminal:i386
<kentonv> does this say that gnome-terminal conflicts with itself?
<kentonv> because it claims to both provide and conflict with gnome-terminal:i386?
<anna_k> Hi Kenton, I got your email. I've regained my ability to invite people to grains, but even after restarting the Roundcube grain, Roundcube still is giving me the same error message
<biotim> It does seem odd that gnome-terminal is listed as a conflict for itselt. Doesn't stop me from installing it using apt-get or synaptic.
<kentonv> anna_k, if you create a brand-new roundcube grain and try sending e-mail, does it work? (Trying to determine if it's a problem specific to the grain...)
<anna_k> will do
<kentonv> biotim, to be clear, you were able to install the amd64 version? It seems only the amd64 version is a conflict for itself.
<anna_k> @kentonv yep no problem sending from a new roundcube grain
<kentonv> anna_k, ok, now try saving a backup of the broken grain, restoring the backup (hence creating a copy of the grain), and seeing if it can send...
<anna_k> kentonv ok
<kentonv> anna_k, did you recently change your primary e-mail address in your Sandstorm account settings?
<kentonv> I see an error in the log which suggests that roundcube is trying to use a different address than your primary address, and that seems to be why it's not working
<anna_k> yep
<kentonv> In theory we should make it work with any of your verified addresses, but the e-mail code predates the ability to have multiple verified addresses and it's hard to change for a few reasons. :/
<anna_k> kentonv I created a gmail for communication with people who have registered fro a conference, and am trying to have multiple people manage conference-related emails via it
<biotim> yes, installing amd64 version of gnome-terminal works for me
<biotim> but i remember i did have a lot of conflict issues when upgrading
<biotim> (when doing dist-upgrade)
<kentonv> anna_k, unfortunately you won't be able to send mail from roundcube unless the from: address matches the primary email of the user who owns the grain.
<anna_k> kentonv I was never able to send outgoing email when logged in as anna_k, so I've been switching between logging in ass anna_k and logging in as berearising to send the emails
<kentonv> but you can change your primary address in the Sandstorm account settings
<kentonv> how long have you been using this grain this way? We made a big change to the identity system a month ago which might have affected this...
<anna_k> I just installed roundcube last week.
<kentonv> ah, ok. So does switching your primary e-mail solve the problem?