Did a '-vv' on the ssh session, and got this:
X11 forwarding request failed on channel 0
Which I googled, and got this page:
http://ask.xmodulo.com/fix-broken-x11-forwarding-ssh.html
It appears to be an IPv6 issue -- i.e., I'm not using it -- so this fixed the
problem:
Add
AddressFamily inet
to
Oh -- so the OP should probably associate this bug report with the
openssh-server package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1463263
Title:
ssh-based X11 forwarding not working in 15.04
Public bug reported:
I set up Avahi on two 16.04 systems, but was unable to resolve between
them via ping; note, however, that avahi-resolve worked fine:
root@clients-1:~# avahi-resolve -n -4 kentest.local
kentest.local192.168.243.16 # This is a good thing
These, not so much good:
Note that this bug report should be filed against package avahi-daemon,
and not avahi, since avahi, itself, isn't even a package, but the
Launcpad form wouldn't let me submit it as such.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Unsure what has changed; don't recall installing or updating any new
packages, or altering any settings after my initial post, but I can't
make it crash any more. I'm not outright closing this, as it happened
*so many times* that I'm hesitant to call it gone, but neither do I want
someone
I killed lightdm and shut the lid from the command prompt. System was
largely unresponsive after opening -- I was still able to switch between
virtual consoles, but that was *it*; console accepted no input, nor did
any of the login prompts. After 120 seconds (I presume), and error
about kworker
Hi. Original poster, here. Indeed, I am unable to run that command, as
the system is hard frozen, and requires a full power cycle.
( does nothing, but this appears to be a key mapping
issue, so I don't know if the kernel has actually panic, or if the UI is
simply 100% crashed.) I did think to
NOTE: I install to btrfs. I don't imagine that plays a role, but it is
something that's probably a differentiator for my system vs. others'.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1585462
Public bug reported:
Fresh install of 16.04 (installed twice, now -- same issue both times;
apt-get update; apt-get dist-upgrade run in both cases, so latest
packages). On lid close, system hard freezes, requiring power cycle.
On opening lid, is frozen on lockscreen. No mouse movement, no
Public bug reported:
Working through the documentation (in this case, specifically
http://docs.openstack.org/juno/install-guide/install/apt/openstack-
install-guide-apt-juno.pdf), most all of the config files reflect the
things that need tweaking, with sections carefully defined. For
nova.conf,
Public bug reported:
Working through the documentation (in this case, specifically
http://docs.openstack.org/juno/install-guide/install/apt/openstack-
install-guide-apt-juno.pdf), most all of the config files reflect the
things that need tweaking, with sections carefully defined. For
nova.conf,
Sadly, please add my name to the list. Black borders, black terminal.
I *LOOOVE* my Compiz, so I'm not planning on giving up, but I also need
to stay employed, so I'll revert... for now. If someone figures this
out, please post to this thread.
Thanks kindly!
-Ken
--
You received this bug
Public bug reported:
I was starting an install at my job; I had to leave. Continued install
from home, and it crashed.
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: ubiquity 2.14.6
ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
Uname: Linux 3.8.0-19-generic x86_64
ApportVersion:
btrfs still isn't working as a boot destination. Indeed, when I try to
use it, I usually throw a grub error during install (and, obviously,
boot). The part that puzzles me the most is that, when I mount the
partition, it seems that all the root-level files and directories are in
a subdirectory
I had the same problem; happened after I installed linux-
image-2.6.28-6-386 (possibly a coincidence, but I'd be surprised). For
me, at least, it was an apparmor issue:
r...@bree:/etc/apparmor.d# ls -al /proc/sys/crypto/fips_enabled
-r--r--r-- 1 root root 0 Jul 7 10:18
Someone else recently mentioned -- on the same bug at launchpad -- a
different fix. It might have been to delete the IPv6 entries in
/etc/hosts (IIRC), but you'll want to check the bug to be sure.
Let us know if it works, and good luck!
-Ken
On Tue, June 2, 2009 8:40 am, Chaim Krause wrote:
I
16 matches
Mail list logo
