[Bug 1463263] Re: ssh-based X11 forwarding not working in 15.04 following upgrade from 14.10
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 /etc/sshd/sshd_config and restart service. (That's assuming the AddressFamily line didn't already exist, which it didn't for my 16.04 host). Done! -- 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 following upgrade from 14.10 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1463263/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1463263] Re: ssh-based X11 forwarding not working in 15.04 following upgrade from 14.10
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 following upgrade from 14.10 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1463263/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1676476] [NEW] Unable to do nsswitch resolution on Avahi due to permissions issue
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: root@clients-1:~# ping kentest.local ping: unknown host kentest.local My nsswitch.conf file was thus: hosts: files mdns4_minimal [NOTFOUND=return] dns I did a strace on the ping, and saw this: sun_path="/var/run/avahi-daemon/socket"}, 110) = -1 EACCES (Permission denied) The socket's permissions were fine, so I looked at the directory the socket was in and saw: root@clients-1:~# ls -ald /var/run/avahi-daemon/ drwx-- 2 avahi avahi 80 Mar 27 05:35 /var/run/avahi-daemon/ It seemed to me this should have been okay -- I mean, I was trying the ping as root, and presumably user avahi would be servicing the request if it wasn't user root. But "Permission denied" is "permission denied," so I changed directory permissions and tried again: root@clients-1:~# chmod 777 /var/run/avahi-daemon/ root@clients-1:~# ping kentest.local PING kentest.local (192.168.243.16) 56(84) bytes of data. 64 bytes from 192.168.243.16: icmp_seq=1 ttl=64 time=1.31 ms 64 bytes from 192.168.243.16: icmp_seq=2 ttl=64 time=0.742 ms ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Mon Mar 27 14:55:01 2017 Ec2AMI: ami-0004 Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: GB.small Ec2Kernel: unavailable Ec2Ramdisk: unavailable ProcEnviron: TERM=xterm SHELL=/bin/bash PATH=(custom, no user) LANG=en_US.UTF-8 XDG_RUNTIME_DIR= SourcePackage: avahi UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: avahi (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ec2-images xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1676476 Title: Unable to do nsswitch resolution on Avahi due to permissions issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1676476/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1676476] Re: Unable to do nsswitch resolution on Avahi due to permissions issue
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. https://bugs.launchpad.net/bugs/1676476 Title: Unable to do nsswitch resolution on Avahi due to permissions issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1676476/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1585462] Re: Dell Latitude E7440 crash on lid close (MATE 16.04)
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 spending resources until I can make it reproducible. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1585462 Title: Dell Latitude E7440 crash on lid close (MATE 16.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1585462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1585462] Re: Dell Latitude E7440 crash on lid close (MATE 16.04)
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 blocking for 120 seconds came up, however nothing else seemed to transpire. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1585462 Title: Dell Latitude E7440 crash on lid close (MATE 16.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1585462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1585462] Re: Dell Latitude E7440 crash on lid close (MATE 16.04)
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 add the remainder of the syslog, though: ** Attachment added: "syslog-pre-crash.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1585462/+attachment/4673897/+files/syslog-pre-crash.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1585462 Title: Dell Latitude E7440 crash on lid close (MATE 16.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1585462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1585462] Re: Dell Latitude E7440 crash on lid close (MATE 16.04)
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 Title: Dell Latitude E7440 crash on lid close (MATE 16.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1585462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1585462] [NEW] Dell Latitude E7440 crash on lid close (MATE 16.04)
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 keyboard movement, does nothing. Freezes ~80% of the time; occasionally (perhaps related to WiFi not being enabled), it suspends properly. ** Affects: ubuntu Importance: Undecided Status: New ** Tags: dell freeze lid suspend -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1585462 Title: Dell Latitude E7440 crash on lid close (MATE 16.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1585462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1415566] [NEW] /etc/nova/nova.conf too minimalist
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, there is mention of [database], [glance], and [keystone_authtoken] sections, none of which exist. After asking the OpenStack list, they asked me to open a bug against the file, so that it could be a bit better fleshed-out, and do a better job as a template. Thanks! -Ken Oh -- this is Ubuntu 14.04, against the OpenStack repo called out int he documentation. ** Affects: nova (Ubuntu) Importance: Undecided Status: New ** Tags: nova.conf openstack -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1415566 Title: /etc/nova/nova.conf too minimalist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1415566/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1242115] Re: Black window borders, black terminal
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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1242115 Title: Black window borders, black terminal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1242115/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1226846] [NEW] Installer crashed after location change.
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: 2.9.2-0ubuntu8 Architecture: amd64 CasperVersion: 1.331 Date: Tue Sep 17 17:49:28 2013 InstallCmdLine: initrd=/casper/initrd.lz file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash -- BOOT_IMAGE=/casper/vmlinuz LiveMediaBuild: Ubuntu 13.04 "Raring Ringtail" - Release amd64+mac (20130424) MarkForUpload: True ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring third-party-packages ubiquity-2.14.6 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1226846 Title: Installer crashed after location change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1226846/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 712029] Re: ubiquity btrfs install fails to boot (grub rescue> prompt)
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 named "@" (sans quotes) -- I assume there's some installer magic involved here. As I read that it *had* been working in alpha-2 (with some minor glitches), I was hoping that the beta would have addressed the issues. Installing grub by hand doesn't throw errors at install time, but still doesn't boot. Note: this is for 32-bit server beta1. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/712029 Title: ubiquity btrfs install fails to boot (grub rescue> prompt) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 392337] Re: CUPS not starting due to error reading `/proc/sys/crypto/fips_enabled'
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 /proc/sys/crypto/fips_enabled Since its permissions are 444, it clearly should be allowed to read. I admit that, since it's my personal machine, I cheated, and, instead of learning how to fix it "right" in apparmor, I just did: /etc/init.d/apparmor stop chmod -x /etc/init.d/apparmor NOTE: I do *NOT* recommend that as a work-around for a production or Internet-accessible box. -- CUPS not starting due to error reading `/proc/sys/crypto/fips_enabled' https://bugs.launchpad.net/bugs/392337 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 32330] Re: Amanda fails because client thinks server is IPv6 when it's IPv4.
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 am experiencing this problem with 9.04. I noticed it while trying to > get PXE boot working. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. -- Amanda fails because client thinks server is IPv6 when it's IPv4. https://bugs.launchpad.net/bugs/32330 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
