[Touch-packages] [Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
** Changed in: openssh (Ubuntu) Assignee: (unassigned) => Ngo Quang Thong (quangthong1981) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/201786 Title: ssh Agent admitted failure to sign using the key on big endian machines Status in seahorse: Fix Released Status in gnome-keyring package in Ubuntu: Triaged Status in openssh package in Ubuntu: Confirmed Bug description: on hardy (preserved home folder from feisty) i get the following when i try to ssh Agent admitted failure to sign using the key. Permission denied (publickey). or with verbose on sam@titania:~$ ssh -v oberon OpenSSH_4.7p1 Debian-4ubuntu1, OpenSSL 0.9.8g 19 Oct 2007 debug1: Reading configuration data /home/sam/.ssh/config debug1: Applying options for oberon debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to ## [##] port ##. debug1: Connection established. debug1: identity file /home/sam/.ssh/identity type -1 debug1: identity file /home/sam/.ssh/id_rsa type 1 debug1: identity file /home/sam/.ssh/id_dsa type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_4.6p1 Debian-5ubuntu0.1 debug1: match: OpenSSH_4.6p1 Debian-5ubuntu0.1 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_4.7p1 Debian-4ubuntu1 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client aes128-cbc hmac-md5 none debug1: kex: client->server aes128-cbc hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: using hostkeyalias: oberon debug1: Host 'oberon' is known and matches the RSA host key. debug1: Found key in /home/sam/.ssh/known_hosts:1 debug1: ssh_rsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey debug1: Next authentication method: publickey debug1: Offering public key: /home/sam/.ssh/id_rsa debug1: Server accepts key: pkalg ssh-rsa blen 277 Agent admitted failure to sign using the key. debug1: Trying private key: /home/sam/.ssh/identity debug1: Trying private key: /home/sam/.ssh/id_dsa debug1: No more authentication methods to try. Permission denied (publickey). I tried generating a new key. this worked for a few logons, but then i get back to this error. I think it is to do with the local key agent. i found that SSH_AUTH_SOCK=0 ssh oberon works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/seahorse/+bug/201786/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi
I'm using a Dell Lattitude E6230 with Intel wireless card (Centrino Advanced-N 6205 [Taylor Peak]). On Ubuntu 16.04 this bug affected (wifi icon changed to two arrows, network manager could not be controlled, have to be relaunched). But since upgrading to Ubuntu 16.10 for the past week I have not seen this bug after dozens of suspends. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1589401 Title: cannot view wifi networks after re-enabling wifi Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Incomplete Bug description: after re enabling wifi, up-down arrows just like wired network. cannot see any wifi ssid. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1589401/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1551275] Re: qmlscene crashed with SIGABRT in QMessageLogger::fatal()
** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1551275 Title: qmlscene crashed with SIGABRT in QMessageLogger::fatal() Status in qtdeclarative-opensource-src package in Ubuntu: New Bug description: Open Checkbox app, then it crash ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: qmlscene 5.5.1-2ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Mon Feb 29 22:14:01 2016 ExecutablePath: /usr/lib/x86_64-linux-gnu/qt5/bin/qmlscene InstallationDate: Installed on 2014-09-11 (535 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) ProcCmdline: /usr/lib/x86_64-linux-gnu/qt5/bin/qmlscene --settings=/usr/share/checkbox-converged/settings.json $@ /usr/share/checkbox-converged/checkbox-touch.qml Signal: 6 SourcePackage: qtdeclarative-opensource-src StacktraceTop: QMessageLogger::fatal(char const*, ...) const () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/xcbglintegrations/libqxcb-glx-integration.so ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/xcbglintegrations/libqxcb-glx-integration.so QXcbIntegration::createPlatformOpenGLContext(QOpenGLContext*) const () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 QOpenGLContext::create() () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 Title: qmlscene crashed with SIGABRT in QMessageLogger::fatal() UpgradeStatus: Upgraded to xenial on 2016-02-29 (0 days ago) UserGroups: adm bluetooth bumblebee cdrom dialout dip fuse kvm libvirtd lpadmin mlocate plugdev proxy root sambashare stapdev stapusr sudo vboxusers video wireshark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1551275/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1472826] [NEW] Motif library v4.0.4 causes segfault in legacy app
Public bug reported: Our group develops an X application that uses the Motif Library (package libxm4 v2.3.4-5). It appears that in the latest version of libXm.4.0.4 on Trusty (14.04), on certain types of X events, it causes a segfault. I've isolated this to a particular version of the library and OS rev. Our application works fine for OS older than 14.04, ie 12.04 etc. I also confirmed the version issue by copying libXm.4.0.3 from a 12.04 machine onto a 14.04 machine and it allows the program to work normally. I basically copied libXm.4.0.3 from a 12.04 machine to the 14.04 machine and created a symlink to it: ln -s /usr/lib/x86_64-linux-gnu/libXm.4.0.3 /usr/lib/x86_64-linux-gnu/libXm.4.0.4 So, whatever has changed between 4.0.3 and 4.0.4 has broken some API calls. It's hard for us to debug this from the application side b/c it generates a segfault, which causes the application to crash. Example of what causes the crash. When our application generates a child window which has text field widgets like a text field or textarea, typing into the field causes this crash. Any ideas on why the new version would cause these crashes? Looking at the release notes (/usr/share/doc/libmotif-dev/RELNOTES.gz), I see there were a number of bug fixes. Is it possible one of these fixes caused another bug? Thanks in advance. Quang ** Affects: unity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1472826 Title: Motif library v4.0.4 causes segfault in legacy app Status in unity package in Ubuntu: New Bug description: Our group develops an X application that uses the Motif Library (package libxm4 v2.3.4-5). It appears that in the latest version of libXm.4.0.4 on Trusty (14.04), on certain types of X events, it causes a segfault. I've isolated this to a particular version of the library and OS rev. Our application works fine for OS older than 14.04, ie 12.04 etc. I also confirmed the version issue by copying libXm.4.0.3 from a 12.04 machine onto a 14.04 machine and it allows the program to work normally. I basically copied libXm.4.0.3 from a 12.04 machine to the 14.04 machine and created a symlink to it: ln -s /usr/lib/x86_64-linux-gnu/libXm.4.0.3 /usr/lib/x86_64-linux-gnu/libXm.4.0.4 So, whatever has changed between 4.0.3 and 4.0.4 has broken some API calls. It's hard for us to debug this from the application side b/c it generates a segfault, which causes the application to crash. Example of what causes the crash. When our application generates a child window which has text field widgets like a text field or textarea, typing into the field causes this crash. Any ideas on why the new version would cause these crashes? Looking at the release notes (/usr/share/doc/libmotif-dev/RELNOTES.gz), I see there were a number of bug fixes. Is it possible one of these fixes caused another bug? Thanks in advance. Quang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1472826/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 980519] Re: Random log off in Ubuntu 12.04 LTS
I also got this bug recently. At random clicks on random programs (Chrome, web site links, etc), I would get logged out (black screen that flutters constantly between the login until I click on the mouse, move the mouse, type something, or in some cases wait long enough, in which a stable login screen will appear to allow me to log back in). However, I was able to fix this issue by not using unity. Instead I installed gnome and logged out and back in with gnome (I'm using the class with no effects version). Hope this helps. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/980519 Title: Random log off in Ubuntu 12.04 LTS Status in Unity: Fix Released Status in nvidia-graphics-drivers package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Status in xorg package in Ubuntu: Fix Released Status in Fedora: New Bug description: I get logged off from Ubuntu sometimes. There is no error message or any indication that it is going to log off. The screen goes black, and after 2-4 seconds, i get presented with the Ubuntu Log On Screen. There is no clear pattern (or at least if have not noticed any). One time i am working with Netbeans, another time i am using firefox. This also means that at present i can not clearly say what package might be causing this behaviour. I am fairly sure the problem lies in 12.04 (or more precise - the combination of 12.04 and the hardware i am using). I do not have the same problem running 11.04 or 11.10. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/980519/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
