[Bug 1968467] Re: CSD scripts do not work on jammy
Thanks for testing that. We may need to apply something like this to OpenConnect, to get it to try harder to disable the OpenSSL minimum security level. Ugh. https://gitlab.com/openconnect/openconnect/-/commit/4e07eecaf04a48c3253a5dfd69d817673194e154#note_921595179 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968467 Title: CSD scripts do not work on jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openconnect/+bug/1968467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968467] Re: CSD scripts do not work on jammy
@jgunthorpe, what if you do something like this, where you create an OPENSSL_CONF that explicitly (re)enables unsafe legacy negotiation? Instead of using /dev/null. ``` $ cat > /tmp/openssl.conf < ``` That comes from https://github.com/dlenski/gp-saml-gui/issues/42 ** Bug watch added: github.com/dlenski/gp-saml-gui/issues #42 https://github.com/dlenski/gp-saml-gui/issues/42 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968467 Title: CSD scripts do not work on jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openconnect/+bug/1968467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968467] Re: CSD scripts do not work on jammy
I’m one of the upstream OpenConnect developers. Thanks for bringing this to our attention. This is one of a seemingly-endless stream of issues (e.g. https://gitlab.com/openconnect/openconnect/-/issues/211) that OpenConnect users have encountered as a result of distros’ recent mania for enforcing “minimum TLS security levels” on a system-wide level. It’s a frustrating situation for OpenConnect because users often have to connect to ancient unpatched VPNs to do their work, can’t do anything about the server configuration, and have no real expectation of “security” anyway. > My feeling is that curl should set the SSL option when -k is used. openconnect itself sets this option already, it was fixed in commit c8dcf10 If you replace the cURL invocation in the CSD/Trojan script with… ``` OPENSSL_CONF=/dev/null curl ``` … does this make it work? (For some hints about how/why it should work, start with https://gitlab.com/openconnect/openconnect/-/commit/7e862f2f0352409357fa7a4762481fde49909eb8#406e031b8824ea26ae0bf4d7579a1d89e3fb5906) ** Bug watch added: gitlab.com/openconnect/openconnect/-/issues #211 https://gitlab.com/openconnect/openconnect/-/issues/211 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968467 Title: CSD scripts do not work on jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openconnect/+bug/1968467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874257] Re: SSH fails with connection timed out - in VPN and hangs here "expecting SSH2_MSG_KEX_ECDH_REPLY" + Ubuntu 16.04.6 LTS
@Stuart-ward wrote… > This is still a current problem > > $ dpkg -l | grep -i openvpn > ii network-manager-openvpn 1.8.14-1 amd64 network management framework > (OpenVPN plugin core) > ii network-manager-openvpn-gnome 1.8.14-1 amd64 network management framework > (OpenVPN plugin GNOME GUI) > ii openvpn 2.5.1-3ubuntu1 amd64 virtual private network daemon Once again, OpenConnect and OpenVPN are *not* the same thing. At all. For your VPN connection, are you using OpenConenct (the original subject of this bug report), or are you using OpenVPN (completely different and should have a separate bug files)? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874257 Title: SSH fails with connection timed out - in VPN and hangs here "expecting SSH2_MSG_KEX_ECDH_REPLY" + Ubuntu 16.04.6 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921828] Re: Cisco AnyConnect 4.8+ server requires a trivial patch to connect
@Tony Spets, if you're willing to share the identity of an affected server (privately) with us developers, my email is on my profile page at https://gitlab.com/dlenski. I wouldn't share it publicly, but would like to use it to improve a tool for *detection* of servers that have had this modification/breakage. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921828 Title: Cisco AnyConnect 4.8+ server requires a trivial patch to connect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openconnect/+bug/1921828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921828] Re: Cisco AnyConnect 4.8+ server requires a trivial patch to connect
The patch will be including in OpenConnect v9.0 (coming real soon now, we swear 😅). The _dependencies_ of OpenConnect have been essentially unchanged for years, so frankly everyone would probably be happier to have OpenConnect v9.0 built for xenial/bionic/focal, rather than building an openconnect-v7.08-ubuntu123 that only includes this one tiny fix. :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921828 Title: Cisco AnyConnect 4.8+ server requires a trivial patch to connect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openconnect/+bug/1921828/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754601] Re: openconnect has trouble maintaining a VPN connection
I'm one of the OpenConnect developers. This thread appears to be describing THREE SEPARATE PROBLEMS, which likely have nothing to do with Ubuntu's packaging specifically. Please submit bug reports at https://gitlab.com/openconnect/openconnect/-/issues. @Ingo Karkat: > What helped for me was switching from > > $ sudo openconnect --protocol=pulse ... > > to > > $ sudo openconnect --juniper ... > > Which is odd, because my company's VPN is Pulse Secure?! All Pulse Secure VPNs are backwards-compatible with the Juniper protocol. The two protocols are completely different, and both are *terrible* messes… but our understanding of the Juniper protocol is more complete. If you want to improve the Pulse protocol support, please contribute over at Gitlab. Read https://www.infradead.org/openconnect/juniper.html for a bit more explanation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754601 Title: openconnect has trouble maintaining a VPN connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1754601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874257] Re: SSH fails with connection timed out - in VPN and hangs here "expecting SSH2_MSG_KEX_ECDH_REPLY" + Ubuntu 16.04.6 LTS
It appears you are using *OpenConnect*, although both the strings OpenVPN and OpenConnect appear in prior posts. These are *completely different* VPN clients. You are using an *ancient* old release of OpenConnect v7.06. The automatic MTU detection logic has been vastly improved in newer versions of OpenConnect: https://www.infradead.org/openconnect/changelog.html So yes, this is indeed a bug in OpenConnect's MTU handling, but likely one which we've long since fixed upstream. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874257 Title: SSH fails with connection timed out - in VPN and hangs here "expecting SSH2_MSG_KEX_ECDH_REPLY" + Ubuntu 16.04.6 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876968] Re: Error "Usage: ip route { list | flush } SELECTOR"
*** This bug is a duplicate of bug 1871184 ***
https://bugs.launchpad.net/bugs/1871184
This is a duplicate of #1871184. It's actually a bug in vpnc-script.
I explain more details here: https://bugs.launchpad.net/ubuntu/+source
/vpnc-scripts/+bug/1871184/comments/2
** This bug has been marked a duplicate of bug 1871184
openconnect throws errors and routing issues after connection.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876968
Title:
Error "Usage: ip route { list | flush } SELECTOR"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openconnect/+bug/1876968/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871184] Re: openconnect throws errors and routing issues after connection.
@laspokemon, yes, you should be able to overwrite your global vpnc- script with the latest version from the master branch. Raw source here: https://gitlab.com/openconnect/vpnc-scripts/-/raw/master/vpnc-script You will likely want to overwrite `/usr/share/vpnc-scripts/vpnc-script`, since this is the location used by Debian/Ubuntu packaging, and where the Debian/Ubuntu openconnect packages look for the script by default. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871184 Title: openconnect throws errors and routing issues after connection. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vpnc-scripts/+bug/1871184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871184] Re: openconnect throws errors and routing issues after connection.
This is a bug in vpnc-scripts, not in OpenConnect per se. Upstream Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955016 We fixed this bug a few months ago in: https://gitlab.com/openconnect /vpnc-scripts/-/merge_requests/5 Long story short: 1) Old versions of `vpnc-script` with old versions iproute2 were silently doing the wrong thing (creating split-exclude routes always as `/32`) 2) Old `vpnc-script` with new iproute2 fails noisily, as you're showing. 3) New `vpnc-script` with new iproute2 works correctly. We need the Ubuntu package maintainers to pull in the latest vpnc- script, as Debian packagers have already done: https://bugs.debian.org /cgi-bin/bugreport.cgi?bug=955016 ** Bug watch added: Debian Bug tracker #955016 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955016 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871184 Title: openconnect throws errors and routing issues after connection. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openconnect/+bug/1871184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867184] Re: Cannot connect to Cisco ASA with openconnect
OpenConnect v8.06 is now available, and we added options to override the ciphersuite from the command-line, so that users in the future won't need to recompile to fix these kinds of problems. For example, you can now use this command line to enable use of the legacy SHA256 MAC, if that were the only one supported by your VPN server's TLS stack: `openconnect my.vpn.com --gnutls-priority=LEGACY:+SHA256` I hope Ubuntu packaging will pick up the new version, because it contains many other improvements as well: https://www.infradead.org/openconnect/changelog.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867184 Title: Cannot connect to Cisco ASA with openconnect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openconnect/+bug/1867184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822467] Re: OpeonConnect fails with generic TLS Fatal Alert Error
It's not an immediate fix for anyone, but we are working on a patch set which will allow the user to override the ciphersuite priority string from the command line, so that future issues related to ciphersuite incompatibility don't require recompilation to fix. https://gitlab.com/openconnect/openconnect/-/merge_requests/71 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822467 Title: OpeonConnect fails with generic TLS Fatal Alert Error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openconnect/+bug/1822467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822467] Re: OpeonConnect fails with generic TLS Fatal Alert Error
@dwmw2, did you delete issue #21? Or make it confidential? I can't see it even when logged in to Gitlab. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822467 Title: OpeonConnect fails with generic TLS Fatal Alert Error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openconnect/+bug/1822467/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764047] Re: Unable to switch realm on authentication dialog
I fixed this issue in 669c7d3e7a45aabc3035f8f538bbd36e23dbd3d8 (https://gitlab.com/openconnect/openconnect/commit/669c7d3e7a45aabc3035f8f538bbd36e23dbd3d8) and a related one for GlobalProtect VPNs in 7224312999fb5601d4c7e76ea9afe7eb6b2ca761 (https://gitlab.com/openconnect/openconnect/commit/7224312999fb5601d4c7e76ea9afe7eb6b2ca761). It's in OpenConnect v8.0 and subsequent point releases. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764047 Title: Unable to switch realm on authentication dialog To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager-openconnect/+bug/1764047/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814502] Re: VPN does not work with MTU of 1400
You can still work around it by setting a lower MTU manually though, right? (openconnect --mtu=X) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814502 Title: VPN does not work with MTU of 1400 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openconnect/+bug/1814502/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814502] Re: VPN does not work with MTU of 1400
Ah, that's useful to know. The Juniper NC protocol (what OpenConnect implements) has a mechanism for the server to tell the client what MTU to use, but no mechanism AFAIK for the client to tell the server what MTU it thinks it has at the IP level — unlike AnyConnect which has both. This makes the Juniper protocol pretty bad for negotiating a usable MTU. (GlobalProtect protocol is even worse, though.) ``` $ openconnect --prot=nc - juniper.company.com ... Received MTU 1400 from server ``` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814502 Title: VPN does not work with MTU of 1400 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openconnect/+bug/1814502/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814502] Re: VPN does not work with MTU of 1400
Thanks, that's interesting. There were almost no changes to the Juniper code between v7.06 and v7.08, and none that affected MTU handling (git diff v7.06 v7.08 -- oncp.c auth-juniper.c) What version are you running on MacOS? MTU detection is a perenially-unreliable issue with VPNs. I'm going to mention this issue upstream at http://gitlab.com/openconnect/openconnect -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814502 Title: VPN does not work with MTU of 1400 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openconnect/+bug/1814502/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814502] Re: VPN does not work with MTU of 1400
Are you sure this is actually a regression from 17.10 -> 18.04? It sounds more like the behavior of the *server* changed. Can you install the 17.10 version of the openconnect and libopenconnect5 packages and see if it actually makes any difference in the functionality? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814502 Title: VPN does not work with MTU of 1400 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openconnect/+bug/1814502/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773708] Re: Log in to VPN with TOTP codes
This was a typo, which I fixed in https://gitlab.com/openconnect/openconnect/commit/e9647a08bb4613227fd371752910cb32e54f8870, which is included in the OpenConnect v8.01 release. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1773708 Title: Log in to VPN with TOTP codes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openconnect/+bug/1773708/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 667963] Re: vpnc disconnects after 7-8 hours consistently
I've tested @Ralph Schmieder's patch and it gets the job done. Prevents my VPN from hanging at the expiration of the IKE key lifetime. You can find a slightly cleaned-up source tree with it applied here: https://github.com/dlenski/vpnc/commit/27a7a1b9daee88e000c18001222e2e53e348e378 Any reason the Ubuntu maintainers didn't apply this one already? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/667963 Title: vpnc disconnects after 7-8 hours consistently To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vpnc/+bug/667963/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809839] Re: Daily build 2667 broken for protocol=GP
Thanks. This was also reported on the OpenConnect mailing list (http://lists.infradead.org/pipermail/openconnect- devel/2018-December/005164.html) and I've submitted a quick patch to fix it at: https://gitlab.com/openconnect/openconnect/merge_requests/22 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809839 Title: Daily build 2667 broken for protocol=GP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openconnect/+bug/1809839/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789268] Re: Openconnect doesn't connect to cisco vpn
> Looks like it lacks of any build option. What does this mean? > When I look at build requirements here: http://www.infradead.org/openconnect/building.html - I can't find GnuTLS (v3.2.10+) in my host packages. I've built the package myself - no success. Your problem has nothing to do with GnuTLS. > Unfortunately or big bloody enterprise company is using cisco anydisconnect vpn which is very buggy and introduces desktop trojans being run within a SUID binary. It works on my Kubuntu 18.04. If you are trying to use OpenConnect's "CSD wrapper" feature, then refer to the page about CSD on the OpenConnect site: http://www.infradead.org/openconnect/csd.html These days, you *don't have to run a Trojan at all*. You can run a script which spoofs the output of the Trojan: https://gitlab.com/openconnect/openconnect/blob/master/csd-post.sh Save that script, mark it executable (`chmod +x csd-post.sh`) and use `openconnect --csd-wrapper csd-post.sh vpn-amer-dco.genesys.com`. -Dan Lenski (openconnect contributor) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789268 Title: Openconnect doesn't connect to cisco vpn To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openconnect/+bug/1789268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789268] Re: Openconnect doesn't connect to cisco vpn
This doesn't appear to be a bug, just a lack of knowledge about how to invoke OpenConnect correctly. ** Changed in: openconnect (Ubuntu) Status: New => Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/openconnect/+question/673034 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789268 Title: Openconnect doesn't connect to cisco vpn To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openconnect/+bug/1789268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1783610] Re: Openconnect fails to connect to VPN servers which blacklist TLS 1.0
Copying from what I wrote on the openconnect-devel mailing list… Nikos's proposed fix is to change "-VERS-TLS-ALL:+VERS-TLS1.0" to "-VERS-SSL3.0". It's useful to consider the total set of possible effects of this change on Ubuntu 14.04's openconnect: 1) Good: Fixes the incompatibility reported here, allowing it to connect to gateways that require TLS1.1 or TLS1.2. 2) Neutral: No effect on ancient gateways that only support SSLv3 (insecure, already locked out). 3) Neutral: No effect on ancient gateways that only support TLS1.0 (still possible to connect). 4) Bad: May prevent connections to TLS-version-intolerant (aka "broken") servers and middleboxes which support TLS1.0 but fail to correctly negotiate down to it when presented with TLS1.1/1.2 ClientHellos. The upside (1) is pretty obvious and clear, because lots of newer gateways simply refuse TLS1.0 these days. The downside (4) is harder to estimate… I don't think there are too many TLS1.0-only version-intolerant middleboxes out there these days because they would be breaking pretty much all the modern clients with the misfortune to go through them. And I don't think I've ever seen a report on the mailing list of a TLS1.0-only version-intolerant Cisco ASA. Basically, this change would vastly improve compatibility with newer gateways that refuse TLS1.0… and it would *only* reduce compatibility with really obsolete middleboxes that are intolerant to TLS1.1 and newer. I doubt that many such middleboxes still exist on the public Internet, because they would be breaking most modern clients. So I'm in favor. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1783610 Title: Openconnect fails to connect to VPN servers which blacklist TLS 1.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openconnect/+bug/1783610/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1655279] Re: OpenConnect does not properly logout from Juniper VPNs
Okay, although I think this one is a fairly straightforward fix, it's a good idea to wait and see the discussion on the list. On Tue, Jan 10, 2017 at 3:05 PM, Mike Miller wrote: > It would also be ideal to wait until the proposed patch has been > reviewed and applied upstream. The patch is from the upstream mailing > list, not yet acknowledged or committed. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1655279 > > Title: > OpenConnect does not properly logout from Juniper VPNs > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/openconnect/+ > bug/1655279/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1655279 Title: OpenConnect does not properly logout from Juniper VPNs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openconnect/+bug/1655279/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655279] [NEW] OpenConnect does not properly logout from Juniper VPNs
*** This bug is a security vulnerability *** Public security bug reported: The Juniper protocol lacks a .vpn_close_session function; without logout, the VPN cookie remains active and can be used to restart the session from an unrelated computer. This is a security hazard, especially when passing around OpenConnect logs on the mailing list for development and troubleshooting. Patch is straightforward: http://lists.infradead.org/pipermail /openconnect-devel/2017-January/004161.html (Ubuntu 16.04.1 LTS, openconnect v7.06) ** Affects: openconnect (Ubuntu) Importance: Undecided Status: New ** Patch added: "juniper_logout.patch" https://bugs.launchpad.net/bugs/1655279/+attachment/4802292/+files/juniper_logout.patch ** Information type changed from Private Security to Public Security ** Description changed: - The Juniper protocol lacks a .vpn_close_session function; without logout, the - VPN cookie remains active and can be used to restart the session from an unrelated computer. + The Juniper protocol lacks a .vpn_close_session function; without + logout, the VPN cookie remains active and can be used to restart the + session from an unrelated computer. - This is a security hazard, especially when passing around OpenConnect logs on the - mailing list for development and troubleshooting. + This is a security hazard, especially when passing around OpenConnect + logs on the mailing list for development and troubleshooting. Patch is straightforward: http://lists.infradead.org/pipermail /openconnect-devel/2017-January/004161.html (Ubuntu 16.04.1 LTS, openconnect v7.06) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1655279 Title: OpenConnect does not properly logout from Juniper VPNs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openconnect/+bug/1655279/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1612100] [NEW] CWD for vpnc-script changes between connect and disconnect calls
Public bug reported: I reported this on the vpnc-devel mailing list but haven't seen any response: http://lists.unix-ag.uni-kl.de/pipermail/vpnc- devel/2016-August/004199.html I've attached a patch that fixes the issue (combination of the two patches that I posted to the mailing list). This patch applies cleanly on the source package for vpnc 0.5.3r550-2 ** Affects: vpnc (Ubuntu) Importance: Undecided Status: New ** Patch added: "restore_original_cwd_after_vpnc_main_loop.patch" https://bugs.launchpad.net/bugs/1612100/+attachment/4718887/+files/restore_original_cwd_after_vpnc_main_loop.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1612100 Title: CWD for vpnc-script changes between connect and disconnect calls To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vpnc/+bug/1612100/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1061195] Re: Evolution appears unable to create EWS or Exchange MAPI account
I had pretty much the exact same experience as @scottbomb: EWS account creation worked find for me on 14.04-15.10, but then I tried adding an EWS account on 16.04, and it repeatedly failed to appear. After killing *all* evolution-related processes and restarting, it worked. Evolution 3.18.5.2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1061195 Title: Evolution appears unable to create EWS or Exchange MAPI account To manage notifications about this bug go to: https://bugs.launchpad.net/evolution-ews/+bug/1061195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1574622] Re: RTL8723AU No WiFi after reboot
I've had similar problems with the rtl8xxxu driver and the same hardware: [ 8.097402] usb 1-1.4: RTL8723AU rev B (TSMC) 1T1R, TX queues 2, WiFi=1, BT=1, GPS=0, HI PA=0 I presume yours is also a Lenovo Yoga 13? I submitted a small patch to increase the firmware polling delay. This patch appears to resolve the issue for me: http://thread.gmane.org/gmane.linux.kernel.wireless.general/152169 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1574622 Title: RTL8723AU No WiFi after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1574622/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1579216] Re: [needs-packaging] why was crystalhd-dkms package removed?
The thing is, this package *USED TO EXIST* as crystalhd-dkms. It was only removed because of an incorrect understanding about the relevant driver becoming part of the mainline kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1579216 Title: [needs-packaging] why was crystalhd-dkms package removed? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crystalhd/+bug/1579216/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1127157] Re: File Overlap Between linux-firmware-nonfree and firmware-crystalhd
The file bcmFilePlayFw.bin **does not actually do anything** and can be removed. It was **replaced** by bcm70012fw.bin in a very early version of libcrystalhd3 driver (2010): https://github.com/dbason/crystalhd/commit/14640128497e8e6d8d01d7fc85c4eef043d428c2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1127157 Title: File Overlap Between linux-firmware-nonfree and firmware-crystalhd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firmware-crystalhd/+bug/1127157/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1579216] Re: why was crystalhd-dkms package removed?
Long story short: the crystalhd-dkms package shouldn't have been removed because the in-kernel version was not a useful replacement for it. (The kernel staging driver was in fact an older already-obsolete verison.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1579216 Title: why was crystalhd-dkms package removed? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crystalhd/+bug/1579216/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1579216] Re: why was crystalhd-dkms package removed?
I attempted to catalog the large number of variants of this driver floating around the web: https://github.com/dbason/crystalhd/blob/master/HISTORY.md Here are the ones I've found, roughly in order of most obsolete/broken to newest: 1. Staging driver from Linux kernel v3.16 version (https://git.kernel.org/cgit/linux/kernel/git/gregkh/staging.git/tree/drivers/staging/crystalhd?h=v3.16) — this version was removed in 2014 from v3.1 (http://lkml.iu.edu/hypermail/linux/kernel/1408.0/01475.html) due to the fact that it was unmaintained and obsolete; it only supported the BCM70012 chip, for example. * See this LKML kernel thread from 2013 where Steven Newbury and Greg K-H discuss this code: https://lkml.org/lkml/2013/10/27/103 2. The Debian version, which appears to be based on a ~2010 version of the code from the mainline kernel, and like it only supports the BCM70012 chip. 3. Jarod Wilson's tree, last updated in 2012: http://git.linuxtv.org/cgit.cgi/jarod/crystalhd.git/ 4. Yeradis's tree, forked from Jarod's tree, and last updated in 2013: https://github.com/yeradis/crystalhd 5. Dbason's tree, forked from Yeradis's tree, and last updated in 2016: https://github.com/dbason/crystalhd Only the last version can be built and used without error on a modern kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1579216 Title: why was crystalhd-dkms package removed? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crystalhd/+bug/1579216/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1579216] [NEW] why was crystalhd-dkms package removed?
Public bug reported: The crystalhd-dkms package was removed from the source package back in http://bazaar.launchpad.net/~ubuntu- branches/ubuntu/wily/crystalhd/wily/revision/7 > * Remove dkms package which contained buggy driver. > Driver already existed in mainline kernel. Any issues with the driver > should be directed to the kernel package. > (Closes: #682252) > (Closes: #699470) The crystalhd module has *not* been included in the mainline kernel for about 2 years, since it was removed from staging in v3.17 (http://lkml.iu.edu/hypermail/linux/kernel/1408.0/01475.html). In fact, it appears that the version that used to exist in the mainline kernel was much older and basically abandoned. It only supported the BCM70012 chip, not the more featureful and useful BCM70015: https://git.kernel.org/cgit/linux/kernel/git/gregkh/staging.git/tree/drivers/staging/crystalhd?h=v3.16 The CrystalHD hardware is still useful and functional with recent kernels. I have an old Atom-based mini-PC which still plays HD video nicely thanks to the BCM crystalhd decoder card. Over at Github, we've updated the driver source to build correctly under more recent kernels. https://github.com/dbason/crystalhd I'm currently using https://github.com/dbason/crystalhd/tree/82f4477b579b88fc9168b23c6c259598b3678fce with xenial/16.04 and the 4.4.0-21 kernel. -- It would be great to release updated crystalhd-dkms packages to make this still-useful hardware more accessible to other Ubuntu users. I am not very clear on the packaging conventions that I would need to follow in order to update the current package. ** Affects: crystalhd (Ubuntu) Importance: Undecided Status: New ** Tags: needs-packaging -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1579216 Title: why was crystalhd-dkms package removed? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crystalhd/+bug/1579216/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1572536] Re: module fails to load under kernel 4.6 or 4.2
Hi Owen, you might want to take a look over on Github where I and others have modified the source package to build without errors for recent kernels. I'm using it on kernel 4.4.0 under Ubuntu Xenial current: https://github.com/dbason/crystalhd -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1572536 Title: module fails to load under kernel 4.6 or 4.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crystalhd/+bug/1572536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 447803] Re: [gm45] closing screen/lid results in flickering and high CPU usage by Xorg
I too still have this problem after upgrading to 10.04 :-( I've tried the solution of tweaking /proc/acpi/video/*/DOS, suggested in this related bug: https://bugs.launchpad.net/ubuntu/+source/xserver- xorg-video-intel/+bug/156824 And I've read the upstream bug: https://bugs.freedesktop.org/show_bug.cgi?id=16706 But nothing's fixing it. ** Bug watch added: freedesktop.org Bugzilla #16706 http://bugs.freedesktop.org/show_bug.cgi?id=16706 -- [gm45] closing screen/lid results in flickering and high CPU usage by Xorg https://bugs.launchpad.net/bugs/447803 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
[Bug 445889] Re: no sound from integrated speakers (Realtek ALC269, snd-hda-intel driver)
I read with great interest about a recent change to the HDA audio driver in the 2.6.32 kernel: http://www.h-online.com/open/features /Configuration-Storage-Audio-and-Video-872724.html Apparently, there's now a module option to communicate hardware details or quirks to the HDA driver *without* recompiling or reloading it. Does this mean I could experiment with HDA sound settings more easily now? Does anyone know if there's any documentation written on how to do so under the 2.6.32 kernel? -- no sound from integrated speakers (Realtek ALC269, snd-hda-intel driver) https://bugs.launchpad.net/bugs/445889 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
[Bug 437747] Re: How to hide the "Accessibility" icon is very unintuitive
+1 ... I've had this icon sitting around for months, and never figured out how to disable it. It takes up space, and I've accidentally invoked a couple of unwanted accessibility features a few times. Very annoying. It'd be nice to have a straight-forward right-click option to remove it. -- How to hide the "Accessibility" icon is very unintuitive https://bugs.launchpad.net/bugs/437747 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
[Bug 445889] Re: no sound from integrated speakers (Realtek ALC269, snd-hda-intel driver)
Pat, if you explicitly modprobe the sound driver, you can do it like this: # modprobe snd-hda-intel model=basic Or you can edit /etc/modprobe.d/alsa-base.conf and add the line: options snd-hda-intel model=basic This will cause the correct options to be loaded automatically. In practice, I've found that changing the model option does not have a reliable effect after unloading and reloading the driver, so you should probably edit alsa-base.conf, and then reboot. -- no sound from integrated speakers (Realtek ALC269, snd-hda-intel driver) https://bugs.launchpad.net/bugs/445889 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
[Bug 447803] Re: [GM45] closing screen/lid results in flickering and high CPU usage by Xorg
Kwinz, I experience the same problem of the sound stopping for a second when closing the lid! This also occurs when Gnome decides to turn the display off via DPMS... the sound hiccups for a second. -- [GM45] closing screen/lid results in flickering and high CPU usage by Xorg https://bugs.launchpad.net/bugs/447803 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
[Bug 445889] Re: no sound from integrated speakers (Realtek ALC269, snd-hda-intel driver)
Hey Jim, unfortunately resetting the BIOS settings to factory defaults doesn't fix the issue (either under Linux or Windows). I'm wondering if the "factory default" settings offered by the BIOS don't match the actual factory default settings of the as-shipped laptop :-( I'll try to find out if there's an easy way to remove the CMOS backup battery on this laptop. I'm unclear on why you say that the CMOS RAM/NVRAM can't be read by software... isn't that what the snd_hda_intel driver does when it tries to use the BIOS settings?? -- no sound from integrated speakers (Realtek ALC269, snd-hda-intel driver) https://bugs.launchpad.net/bugs/445889 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
[Bug 445889] Re: no sound from integrated speakers (Realtek ALC269, snd-hda-intel driver)
Hi Jim, thanks for the reply! By NVRAM, do you mean the BIOS NVRAM? Is there any way to access it without possibly trashing the BIOS? I did get in touch with Acer's customer support, who were not so helpful. At first they told me it must be a hardware issue, which of course I was suspicious of. Then after I figured out the speakers *do* work under Linux, ignoring the BIOS settings, they said that I would still have to send it to them to diagnose the problems. I told them I had applied the latest BIOS updates, and they admonished me that updating the BIOS was risky and dangerous (even with the official Acer images???). So, not so useful :-p. But you can read the whole back-and-forth on the incident by clicking here: http://acer.custhelp.com/cgi-bin/acer.cfg/php/enduser/myq_idp.php?p_iid=730494&p_created=1255133171&p_sid=5q23S_Kj&p_accessibility=0&p_redirect=&p_lva=&p_sp=&p_li=&p_page=1&p_allorg=1&p_sort_by=&p_gridsort=&p_row_cnt=1%2C1&p_prods=&p_cats=&p_pv=&p_cv= and then entering the email address dlen...@gmail.com Two days ago, they released another BIOS update and I was hoping that would fix the problem... but it doesn't. If the issue is in the NVRAM, I don't understand why BIOS updates don't fix it, since they seem to erase all the other BIOS setting stored in NVRAM. So, weird bug... if I could figure out how to read the NVRAM settings and tweak them into a format that snd_hda_intel could use, I could probably fix it. -- no sound from integrated speakers (Realtek ALC269, snd-hda-intel driver) https://bugs.launchpad.net/bugs/445889 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
[Bug 445889] Re: no sound from integrated speakers (Realtek ALC269, snd-hda-intel driver)
Okay, I've got the situation slightly improved... I read HD-audio.txt in the kernel documentation (http://www.kernel.org/doc/Documentation/sound/alsa/HD-Audio.txt) and it mentioned the great frequency of problems with internal speaker outputs with this driver. It explained that the following /var/log/messages error is not a huge deal *IF* the BIOS is correctly configured: hda_codec: Unknown model for XX, trying auto-probe from BIOS... Well, presumably my BIOS is *not* correctly configured, since neither Linux nor Windows can use the internal speaker with the default settings. So, as suggested by HD-audio.txt, I tried different "model" parameter values with snd-hda-intel (list of choices is here: http://www.kernel.org/doc/Documentation/sound/alsa/HD-Audio-Models.txt). I tried the "model=basic" option listed for the ALC269 codec. And now the internal speakers work!!! *But* there are other problems: (1) When I plug headphones into the heaphone jack, the internal speakers are not muted. There is apparently no way to get this to happen automatically with the basic model. (Pulseaudio gets confused if I try to tweak the front vs. headphone settings separately via Alsamixer... but I'll call that a Pulseaudio bug.) (2) Alsamixer doesn't know about the correct microphone input options for this computer (3) There's a little red LED inside the headphone jack which is supposed to be used to transmit digital audio using IEC958 or S/PDIF. With the "model=auto" setting, I can turn this LED on or off by enabling or disabling "digital audio" via the mixer controls. But with the "model=basic" setting, the LED stays off. Although I don't have the equipment to use digital audio myself, I assume that it wouldn't work with "model=basic". SUMMARY: Basically, it seems that there is a BIOS problem on this computer that does not set up the correct defaults to allow the internal speakers to work. So probably a new snd-hda-intel "model profile" should be constructed for this notebook. I would be happy to explore this further, if someone would give me advice on how to get started doing it. Thanks!! -- no sound from integrated speakers (Realtek ALC269, snd-hda-intel driver) https://bugs.launchpad.net/bugs/445889 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
[Bug 445889] Re: no sound from integrated speakers (Realtek ALC269, snd-hda-intel driver)
Well... after playing around in Linux for a while, trying to get the internal speakers to work, I went back to check the Windows settings. And *now* the internal speakers don't work in Windows either. Vey strange. I tried a hard reboot, tried removing and reinstalling the battery, tried reinstalling the Realtek Audio drivers in Windows... still nothing. Is it possible that this hardware stores some state in NVRAM or something like that, which neither Windows nor Linux driver normally accesses?? -- no sound from integrated speakers (Realtek ALC269, snd-hda-intel driver) https://bugs.launchpad.net/bugs/445889 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
[Bug 447803] Re: closing screen/lid results in flickering and high CPU usage by Xorg
** Attachment added: "BootDmesg.gz" http://launchpadlibrarian.net/33392777/BootDmesg.gz ** Attachment added: "CurrentDmesg.txt" http://launchpadlibrarian.net/33392778/CurrentDmesg.txt ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/33392779/Dependencies.txt ** Attachment added: "GdmLog.txt" http://launchpadlibrarian.net/33392781/GdmLog.txt ** Attachment added: "GdmLogOld.txt" http://launchpadlibrarian.net/33392783/GdmLogOld.txt ** Attachment added: "Lspci.txt" http://launchpadlibrarian.net/33392784/Lspci.txt ** Attachment added: "Lsusb.txt" http://launchpadlibrarian.net/33392785/Lsusb.txt ** Attachment added: "PciDisplay.txt" http://launchpadlibrarian.net/33392786/PciDisplay.txt ** Attachment added: "ProcCpuinfo.txt" http://launchpadlibrarian.net/33392787/ProcCpuinfo.txt ** Attachment added: "ProcInterrupts.txt" http://launchpadlibrarian.net/33392788/ProcInterrupts.txt ** Attachment added: "ProcModules.txt" http://launchpadlibrarian.net/33392789/ProcModules.txt ** Attachment added: "UdevDb.txt" http://launchpadlibrarian.net/33392790/UdevDb.txt ** Attachment added: "UdevLog.txt" http://launchpadlibrarian.net/33392791/UdevLog.txt ** Attachment added: "XorgLog.txt" http://launchpadlibrarian.net/33392792/XorgLog.txt ** Attachment added: "XorgLogOld.txt" http://launchpadlibrarian.net/33392793/XorgLogOld.txt ** Attachment added: "Xrandr.txt" http://launchpadlibrarian.net/33392794/Xrandr.txt ** Attachment added: "XsessionErrors.txt" http://launchpadlibrarian.net/33392795/XsessionErrors.txt ** Attachment added: "glxinfo.txt" http://launchpadlibrarian.net/33392796/glxinfo.txt ** Attachment added: "monitors.xml.txt" http://launchpadlibrarian.net/33392797/monitors.xml.txt ** Attachment added: "setxkbmap.txt" http://launchpadlibrarian.net/33392798/setxkbmap.txt ** Attachment added: "xdpyinfo.txt" http://launchpadlibrarian.net/33392799/xdpyinfo.txt ** Attachment added: "xkbcomp.txt" http://launchpadlibrarian.net/33392800/xkbcomp.txt -- closing screen/lid results in flickering and high CPU usage by Xorg https://bugs.launchpad.net/bugs/447803 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
[Bug 447803] [NEW] closing screen/lid results in flickering and high CPU usage by Xorg
Public bug reported: Binary package hint: xserver-xorg-video-intel This is a brand new Acer AS1410 laptop, running i386 Ubuntu Karmic, Netbook Remix. The graphics adapter is Intel X4500MHD (8086:2a42 PCI ID), supported by the i915 kernel driver. Yesterday, I tried closing the screen lid to save power while listening to music. The music began to stutter when I did this, and the fan came on. After I opened the lid again, several windows continued to flicker for 10-20 seconds, and running top showed that the Xorg server was consumed 80-100% of the CPU cycles. Inspecting the /var/log/messages, I find the following error repeatedly rapidly when the screen is closed: Oct 10 01:59:56 dlenski-laptop kernel: [ 1292.698045] i915 :00:02.0: DVI-D-2: no EDID data Oct 10 02:00:20 dlenski-laptop kernel: [ 1336.707144] i2c-adapter i2c-2: unable to read EDID block. Oct 10 02:00:20 dlenski-laptop kernel: [ 1336.707149] i915 :00:02.0: DVI-D-1: no EDID data Oct 10 02:00:20 dlenski-laptop kernel: [ 1336.712273] i2c-adapter i2c-2: unable to read EDID block. Oct 10 02:00:20 dlenski-laptop kernel: [ 1336.712278] i915 :00:02.0: DVI-D-1: no EDID data Oct 10 02:00:20 dlenski-laptop kernel: [ 1336.716760] i2c-adapter i2c-4: unable to read EDID block. Oct 10 02:00:20 dlenski-laptop kernel: [ 1336.716763] i915 :00:02.0: DVI-D-2: no EDID data Oct 10 02:00:20 dlenski-laptop kernel: [ 1336.721312] i2c-adapter i2c-4: unable to read EDID block. Oct 10 02:00:20 dlenski-laptop kernel: [ 1336.721316] i915 :00:02.0: DVI-D-2: no EDID data Apparently, the i915 driver fails to acquire information about the LCD panel when the lid is closed??? Disabling the screen by some other mechanism, such as running "xset dpms force off", does not seem to cause this problem. This bug is similar to, but not identical to, https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- intel/+bug/156824, which also involves problems that appear after closing the lid on a laptop with the i915 graphics driver. ProblemType: Bug Architecture: i386 Date: Sat Oct 10 01:59:50 2009 DistroRelease: Ubuntu 9.10 MachineType: Acer Aspire 1410 Package: xserver-xorg-video-intel 2:2.8.1-1ubuntu2 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-11-generic root=UUID=b41da73a-d227-4ee1-b9e7-092cda40dbb6 ro quiet splash ProcEnviron: PATH=(custom, no user) LANG=C SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-11.38-generic RelatedPackageVersions: xserver-xorg 1:7.4+3ubuntu5 libgl1-mesa-glx 7.6.0~git20090817.7c422387-0ubuntu7 libdrm2 2.4.13-1ubuntu1 xserver-xorg-video-intel 2:2.8.1-1ubuntu2 xserver-xorg-video-ati 1:6.12.99+git20090825.fc74e119-0ubuntu2 SourcePackage: xserver-xorg-video-intel Tags: ubuntu-unr Uname: Linux 2.6.31-11-generic i686 XorgConf: Error: [Errno 2] No such file or directory: '/etc/X11/xorg.conf' dmi.bios.date: 09/08/2009 dmi.bios.vendor: INSYDE dmi.bios.version: v0.3117 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Base Board Product Name dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvrv0.3117:bd09/08/2009:svnAcer:pnAspire1410:pvrv0.3117:rvnAcer:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.name: Aspire 1410 dmi.product.version: v0.3117 dmi.sys.vendor: Acer fglrx: Not loaded system: distro: Ubuntu architecture: i686kernel: 2.6.31-11-generic ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 ubuntu-unr -- closing screen/lid results in flickering and high CPU usage by Xorg https://bugs.launchpad.net/bugs/447803 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
[Bug 445889] Re: no sound from integrated speakers (Realtek ALC269, snd-hda-intel driver)
** Attachment added: "AlsaDevices.txt" http://launchpadlibrarian.net/33262596/AlsaDevices.txt ** Attachment added: "AplayDevices.txt" http://launchpadlibrarian.net/33262597/AplayDevices.txt ** Attachment added: "BootDmesg.gz" http://launchpadlibrarian.net/33262598/BootDmesg.gz ** Attachment added: "Card0.Amixer.values.txt" http://launchpadlibrarian.net/33262599/Card0.Amixer.values.txt ** Attachment added: "Card0.Codecs.codec.0.txt" http://launchpadlibrarian.net/33262600/Card0.Codecs.codec.0.txt ** Attachment added: "Card0.Codecs.codec.1.txt" http://launchpadlibrarian.net/33262601/Card0.Codecs.codec.1.txt ** Attachment added: "CurrentDmesg.txt" http://launchpadlibrarian.net/33262602/CurrentDmesg.txt ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/33262622/Dependencies.txt ** Attachment added: "IwConfig.txt" http://launchpadlibrarian.net/33262623/IwConfig.txt ** Attachment added: "Lspci.txt" http://launchpadlibrarian.net/33262625/Lspci.txt ** Attachment added: "Lsusb.txt" http://launchpadlibrarian.net/33262626/Lsusb.txt ** Attachment added: "PciMultimedia.txt" http://launchpadlibrarian.net/33262627/PciMultimedia.txt ** Attachment added: "ProcCpuinfo.txt" http://launchpadlibrarian.net/33262628/ProcCpuinfo.txt ** Attachment added: "ProcInterrupts.txt" http://launchpadlibrarian.net/33262629/ProcInterrupts.txt ** Attachment added: "ProcModules.txt" http://launchpadlibrarian.net/33262630/ProcModules.txt ** Attachment added: "RfKill.txt" http://launchpadlibrarian.net/33262631/RfKill.txt ** Attachment added: "UdevDb.txt" http://launchpadlibrarian.net/33262632/UdevDb.txt ** Attachment added: "UdevLog.txt" http://launchpadlibrarian.net/33262633/UdevLog.txt ** Attachment added: "WifiSyslog.gz" http://launchpadlibrarian.net/33262634/WifiSyslog.gz ** Attachment added: "XsessionErrors.txt" http://launchpadlibrarian.net/33262635/XsessionErrors.txt -- no sound from integrated speakers (Realtek ALC269, snd-hda-intel driver) https://bugs.launchpad.net/bugs/445889 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
[Bug 445889] [NEW] no sound from integrated speakers (Realtek ALC269, snd-hda-intel driver)
Public bug reported: I'm using a brand-new Acer AS1410 notebook/netbook, with Ubuntu 9.10 Netbook Remix. The manufacturer reports the audio chip as Realtek ALC269, although lspci says it's an Intel ICH9 HD Audio Controller (pci id 8086:293c). With the snd-hda-intel driver, configured for analog output, the sound card works correctly with headphones plugged in. However, with no headphones plugged in, there is *no sound* from the integrated speakers. This includes the PC speaker beep. I modprobe pcspkr and try to get a beep, and there's nothing. I know that the internal speakers work fine under Windows Vista Home Premium with the supplied drivers from Realtek. I've tried some of the suggestions about tweaking the model parameter of snd-hda-intel module: http://ubuntuforums.org/showthread.php?t=616845 None of these makes a difference. Regardless of the chosen model name, I get the following warning in /var/log/messages: hda_codec: Unknown model for ALC269, trying auto-probe from BIOS... Any ideas what might be causing this bug? ProblemType: Bug Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dlenski2418 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xd450 irq 22' Mixer name : 'Intel G45 DEVCTG' Components : 'HDA:10ec0269,1025029b,0014 HDA:80862802,80860101,0010' Controls : 23 Simple ctrls : 12 Date: Wed Oct 7 19:16:54 2009 DistroRelease: Ubuntu 9.10 MachineType: Acer Aspire 1410 Package: linux-image-2.6.31-11-generic 2.6.31-11.38 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-11-generic root=UUID=b41da73a-d227-4ee1-b9e7-092cda40dbb6 ro quiet splash ProcEnviron: PATH=(custom, no user) LANG=C SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-11.38-generic RelatedPackageVersions: linux-backports-modules-2.6.31-11-generic N/A linux-firmware 1.20 SourcePackage: linux Tags: ubuntu-unr Uname: Linux 2.6.31-11-generic i686 dmi.bios.date: 09/08/2009 dmi.bios.vendor: INSYDE dmi.bios.version: v0.3117 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Base Board Product Name dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvrv0.3117:bd09/08/2009:svnAcer:pnAspire1410:pvrv0.3117:rvnAcer:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.name: Aspire 1410 dmi.product.version: v0.3117 dmi.sys.vendor: Acer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 ubuntu-unr -- no sound from integrated speakers (Realtek ALC269, snd-hda-intel driver) https://bugs.launchpad.net/bugs/445889 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
[Bug 418246] Re: it87 module error, ACPI conflict
I have the same problem here... motherboard is BIOSTAR TA780G+ with Athlon 64 x2 BE-2400 CPU. The acpi_enforce_resources=lax fix works for me as well. So what's the deal... we have to wait for motherboard manufacturers to write correct ACPI drivers for their sensor chips? And flying pigs? :-( -- it87 module error, ACPI conflict https://bugs.launchpad.net/bugs/418246 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
[Bug 355613] Re: wireshark/libpcap does not support sniffing USB streams
I don't think this problem is just with Jaunty. I'm having the same problem with Intrepid (found this while Googling for it). Also, neither tcpdump nor wireshark will actually log the *contents* of the USB packets (aka URBs), merely things like the length and type of packet. Is this a problem with AppArmor, or with libpcap? -- wireshark/libpcap does not support sniffing USB streams https://bugs.launchpad.net/bugs/355613 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
[Bug 355998] Re: usb-storage: waiting for device to settle before scanning
A related (?) bug: After using Tim's fix, the e2x0 shows up as a mass storage device. So far so good. But when I start Rhythmbox, the device disappears! It seems that Rhythmbox tries to reinitialize it as a MTP device when the mtpdevice plugin is enabled. I am having trouble determining how Rhythmbox/libmtp decides that it should try to open the device via MTP. Does anyone know where libmtp is getting this from? -- usb-storage: waiting for device to settle before scanning https://bugs.launchpad.net/bugs/355998 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
[Bug 355317] Re: Sansa E280 MP3 mplayer not detected (regression)
*** This bug is a duplicate of bug 355998 *** https://bugs.launchpad.net/bugs/355998 ** This bug has been marked a duplicate of bug 355998 usb-storage: waiting for device to settle before scanning -- Sansa E280 MP3 mplayer not detected (regression) https://bugs.launchpad.net/bugs/355317 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
[Bug 236422] Re: sansa mp3 players not mounted when plugged in
*** This bug is a duplicate of bug 355998 *** https://bugs.launchpad.net/bugs/355998 This bug should be merged with 355998 (https://bugs.launchpad.net/ubuntu/+source/libgphoto2/+bug/355998) Long story short: the gphoto2 library handles MP3 players in MTP mode. Due to a bug in gphoto2 *and* a problem with its HAL configuration files, it tries to take over the Sansa MP3 player when it is plugged in to the computer. Thus no /dev/sdXX nodes get created. gphoto2 has been patched upstream, and there are temporary fixes by modifying the gphoto2/HAL configuration files. See the bug I linked to. ** This bug has been marked a duplicate of bug 355998 usb-storage: waiting for device to settle before scanning -- sansa mp3 players not mounted when plugged in https://bugs.launchpad.net/bugs/236422 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
[Bug 355998] Re: usb-storage: waiting for device to settle before scanning
Another "me too." :-) Tim Kosse, your original solution (removing the Sansa e2x0 entries from /usr/share/hal/fdi/preprobe/10osvendor/20-libgphoto2.fdi) works great for me. I have not yet tried patching gPhoto to not try and handle USB mass storage devices, but in my opinion this is a sorely needed update. It is quite mystifying to connect a USB drive and not see any device nodes get created!!! And /var/lib/messages gives no indication of the voodoo done by HAL, which made it even harder to track this bug down for me... :-( -- usb-storage: waiting for device to settle before scanning https://bugs.launchpad.net/bugs/355998 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
[Bug 355317] Re: Sansa E280 MP3 mplayer not detected (regression)
I believe this bug is the same as this one: https://bugs.launchpad.net/ubuntu/+bug/345916 It turns out it is due to the "gphoto" process (which handles MTP mode) attempting to take over access to the Sansa as soon as it is plugged in *EVEN IN MSC MODE*. If you look at the report for that bug, you can fix it by disabling gphoto, by patching gphoto, or by editing its configuration file to prevent it from accessing the Sansa in MSC mode. -- Sansa E280 MP3 mplayer not detected (regression) https://bugs.launchpad.net/bugs/355317 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
[Bug 366101] Re: Evolution slows down and nearly freezes when bringing up a new compose window
It's pretty hard to follow since it launches a large number of new threads during this apparent hang. However, it's also kernel-dependent: booting with the Intrepid kernel (2.6.27-14) fixes the problem. -- Evolution slows down and nearly freezes when bringing up a new compose window https://bugs.launchpad.net/bugs/366101 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
[Bug 366101] Re: Evolution slows down and nearly freezes when bringing up a new compose window
Hi Sebastien, there is no backtrace! Evolution doesn't actually crash... just hangs for 60-100 seconds and then resumes working. Running "evolution --debug" unfortunately provides absolutely no useful information. Any other suggestions for data gathering? -- Evolution slows down and nearly freezes when bringing up a new compose window https://bugs.launchpad.net/bugs/366101 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
[Bug 366101] [NEW] Evolution slows down and nearly freezes when bringing up a new compose window
Public bug reported: Binary package hint: evolution This bug has just appeared for me with the upgrade to Jaunty 9.04. When clicking on the button to compose a new message, Evolution become totally unresponsive for 60-100 seconds before it brings up the window. (Applies equally when replying to a message, or forwarding, or any other action that would bring up a new Compose window.) There is a brief (1-2 second) spike in CPU usage by Evolution right after I click the New Message button, then its CPU usage falls to zero until it suddenly pops up the window a minute or two later. This is on an Athlon 64 X2 with 4gb of RAM, running the amd64 version of Jaunty. This appears to be similar, but even worse, than this old unresolved bug reported here: https://bugs.launchpad.net/bugs/159153 As you can imagine, waiting 1-2 minutes to compose a new message makes the program darn near unusable. ** Affects: evolution (Ubuntu) Importance: Undecided Status: New -- Evolution slows down and nearly freezes when bringing up a new compose window https://bugs.launchpad.net/bugs/366101 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
[Bug 179042] Re: Videos tear and "blink" when enabling compiz [AMD Feature #7647] [EPR#257833]
Ditto here! Intrepid 64-bit, xv windows flicker horribly when Desktop Effects are enabled, no problems when Desktop Effects are disabled. It's not a big deal to disable Xv for video playback, but there seems to be no way to disable Xv for the proprietary Skype client, so it's virtually unusable for video chat with this bug :-( Here's my lspci -vvnn for the onboard graphics card: 01:05.0 VGA compatible controller [0300]: ATI Technologies Inc Radeon HD 3200 Graphics [1002:9610] Subsystem: Biostar Microtech Int'l Corp Device [1565:0017] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: fglrx_pci Kernel modules: fglrx And my Xorg.0.log is attached. ** Attachment added: "Xorg.0.log" http://launchpadlibrarian.net/24619587/Xorg.0.log -- Videos tear and "blink" when enabling compiz [AMD Feature #7647] [EPR#257833] https://bugs.launchpad.net/bugs/179042 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
[Bug 269079] Re: wrong linked smarty
Any chance of fixing this in Intrepid as well??? -- wrong linked smarty https://bugs.launchpad.net/bugs/269079 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
[Bug 269079] Re: wrong linked smarty
Here is a trivial patch to the gallery2-2.2.6 source package which fixes the bug. Please apply :-) ** Attachment added: "patch to fix the bug" http://launchpadlibrarian.net/21575773/gallery2-fix-smarty.patch -- wrong linked smarty https://bugs.launchpad.net/bugs/269079 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
[Bug 320538] Re: evolution segfaults in libeutil.so immediately on startup
Ah, yes. Here's the gdb output attached. I found a "fix". I notice in the gdb output that it's during initialization of the Tasks component of Evolution that the crash occurs. So I deleted the GConf key: /apps/evolution/tasks/sources Now Evolution starts and works fine. Hmmm... ** Attachment added: "gdb-evolution.txt" http://launchpadlibrarian.net/21574949/gdb-evolution.txt -- evolution segfaults in libeutil.so immediately on startup https://bugs.launchpad.net/bugs/320538 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
[Bug 320538] [NEW] evolution segfaults in libeutil.so immediately on startup
Public bug reported: Binary package hint: evolution Using Ubuntu 8.10 x86_64, evolution-2.24.3-0ubuntu1: As soon as I start Evolution, it *immediately* segfaults. I get the following message in /var/log/messages: [ 908.660924] evolution[7250]: segfault at 38 ip 7ff9f6943f24 sp 7fff01b8a870 error 4 in libeutil.so.0.0.0[7ff9f691b000+3d000] This only happens if I try to invoke the GUI. For example: $ evolution & Segmentation fault $ evolution --help $ evolution --force-shutdown I have tried deleting my ~/.evolution directory, to no avail. The problem happens regardless... What to do??? I don't even know how to start investigating this bug. ** Affects: evolution (Ubuntu) Importance: Undecided Status: New -- evolution segfaults in libeutil.so immediately on startup https://bugs.launchpad.net/bugs/320538 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
[Bug 269079] Re: wrong linked smarty
+1, this bit me too. RRRGGGHGH. Just fix the symlink already :-) (By the way, the 4 files still missing after upgrade are only license/copyright info files and not needed for proper functioning of Gallery2) -- wrong linked smarty https://bugs.launchpad.net/bugs/269079 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
[Bug 216146] Re: firefox field for file selection doesn't let me copy paste paths
This has been driving me nuts too!! With Firefox 2.x, I could choose either: (a) type the filename by hand in the text box (b) click the Browse button and get a file selector dialog Great! Now, with Firefox 3.0, clicking on either pops up the file selector dialog. Maddening when I know the path and don't want to wait a few seconds for the dialog to load :-) Is there any way to fix this? Maybe a config hack?? -- firefox field for file selection doesn't let me copy paste paths https://bugs.launchpad.net/bugs/216146 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
[Bug 196285] Re: [Regression] Realtek RTL-8185 Wifi not recognized in Hardy 8.04 Alpha 5
Will, thanks a ton for your patch! I have my RTL-8185 working flawlessly under 2.6.24-18 and 2.6.24-19, even under fairly heavy load as a server :-) This is the first time I have had this card working stably on a Linux system, and it is just great to finally have it working!! I certainly hope that your patch will be picked up by Ubuntu and other distributors (*cough* 8.10 *cough*) -- [Regression] Realtek RTL-8185 Wifi not recognized in Hardy 8.04 Alpha 5 https://bugs.launchpad.net/bugs/196285 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
[Bug 152999] Re: DPMS cannot suspend monitor in Gutsy
Bryce, I've got Hardy running now, and the bug still recurs :-( Now the ATI driver works, but only at 1280x1024 and below... -- DPMS cannot suspend monitor in Gutsy https://bugs.launchpad.net/bugs/152999 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
[Bug 152999] Re: DPMS cannot suspend monitor in Gutsy
Bryce, I wouldn't say that xset "triggers" this bug, since the bug is due to a lack of behavior, rather than its presence. Also, with the -ati driver running, xset and DPMS work fine... so I do NOT think the problem is with the server. I am downloading the Hardy packages right now, the mirrors are a bit overloaded but I'll be sure to update on its status under Hardy. -- DPMS cannot suspend monitor in Gutsy https://bugs.launchpad.net/bugs/152999 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
[Bug 111771] Re: can't ssh out; seahorse-agent seems dead
Another way to work around it: delete the temporary named pipe that SSH uses to communicate with the authentication agent. $ rm $SSH_AUTH_SOCK Then SSH will work, prompting for a passphrase for your key... of course, it won't actually be able to store any keys! I still don't know what makes seahorse crash so much :-( -- can't ssh out; seahorse-agent seems dead https://bugs.launchpad.net/bugs/111771 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
[Bug 111771] Ditto.
I have the same problem here. Sometimes seahorse crashes, and then ssh seems not to work. My workaround is to blank out the ssh-agent variables on the command line: $ SSH_AGENT_PID= SSH_AUTH_SOCK= ssh wherever It's a really frustrating bug, because ssh doesn't work and gives no indication why unless you do ssh -v. Otherwise it just waits forever. I wish there was a way to tell GNOME that seahorse has crashed, and to restart it and update the environment variables for new shells. -- can't ssh out; seahorse-agent seems dead https://bugs.launchpad.net/bugs/111771 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 174200] "Next Song" doesn't work with Last.fm
Public bug reported: Binary package hint: rhythmbox First, I would just like to say that I am very happy to see Last.fm support added to Rhythmbox... thank you! Now, the one problem I have is that the "Next Song" button doesn't work for me! When I am playing my Neighbor Radio stream, if I press the "Next Song" button nothing happens other than that button getting grayed out! The only way to skip a song is to stop and then restart the stream, which causes a new song to be chosen. ( Because of this bug, as well as the lack of tag and neighbor display, I mostly use BMPx for listening to Last.fm. I would consider Rhythmbox to be a much better and more polished player overall, but BMPx does have the edge in terms of a really nice Last.fm interface. ) ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New -- "Next Song" doesn't work with Last.fm https://bugs.launchpad.net/bugs/174200 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 141404] Re: No user authentication coming back from suspend
Jamie, some update in the last couple of days seems to have fixed it, actually... so no more problems for me at least. Was this bug fixed in gnome-power-manager or gnome-screensaver or something? Thanks! -- No user authentication coming back from suspend https://bugs.launchpad.net/bugs/141404 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
[Bug 141404] Re: No user authentication coming back from suspend
Ditto. I upgraded to gutsy and suspend from the Gnome|Quit menu *works*, but it never demands my username/password after coming back from suspend. My /etc/default/acpi-support file has the line: LOCK_SCREEN=true ... so I'm not sure what the problem is. -- No user authentication coming back from suspend https://bugs.launchpad.net/bugs/141404 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
[Bug 152999] DPMS cannot suspend monitor in Gutsy
Public bug reported: Binary package hint: xserver-xorg-video-vesa I have an "ATI Technologies Inc RS482 [Radeon Xpress 200]" on- motherboard display adapter. I have to run it with the VESA driver rather than the ATI driver, due to various problems with the ATI driver that prevent it from using resolutions above 640x480 with my monitor. Under Feisty, DPMS worked fine... the monitor would suspend itself according to the settings in the GNOME Power Management applet. Under Gutsy, DPMS does not work. The monitor never suspends itself, and it fails even when explicitly activating DPMS from the command line: $ xset dpms force off # nothing happens! $ xset q ... DPMS (Energy Star): Standby: 0Suspend: 0Off: 0 DPMS is Enabled Monitor is On ... *HOWEVER*, I *can* activate DPMS using vbetool which directly accesses the BIOS: $ sudo vbetool dpms off # monitor suspends! $ sudo vebtool dpms on # monitor turns back on! So I believe this is a problem with the VESA driver. Here are the relevant portions of my /etc/X11/xorg.conf: Section "Device" Identifier "ATI Technologies Inc RS482 [Radeon Xpress 200]" Driver "vesa" BusID "PCI:1:5:0" EndSection Section "Monitor" Identifier "DELL P991" Option "DPMS" HorizSync 30-107 VertRefresh 48-120 EndSection Section "Screen" Identifier "Default Screen" Device "ATI Technologies Inc RS482 [Radeon Xpress 200]" Monitor "DELL P991" DefaultDepth24 SubSection "Display" Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480" EndSubSection EndSection Section "ServerLayout" Identifier "Default Layout" Screen "Default Screen" InputDevice "Generic Keyboard" InputDevice "Configured Mouse" # Uncomment if you have a wacom tablet # InputDevice "stylus""SendCoreEvents" # InputDevice "cursor""SendCoreEvents" # InputDevice "eraser""SendCoreEvents" EndSection ** Affects: xserver-xorg-video-vesa (Ubuntu) Importance: Undecided Status: New -- DPMS cannot suspend monitor in Gutsy https://bugs.launchpad.net/bugs/152999 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 151025] Re: FAT: Unrecognized mount option "usefree" or missing value
Hi all, I have the same problem, but I found a fix :-) I too am running Gutsy-with-Feisty-kernel because the 2.26.22 kernel panics on boot on my system. THE PROBLEM -- Basically, the problem is with the options that gnome-mount uses. If you run gnome-mount -vt from the command line, you'll see the problem: $ gnome-mount -vtd /dev/sdh2 gnome-mount 0.6 ** (gnome-mount:1378): DEBUG: Mounting /org/freedesktop/Hal/devices/volume_uuid_E0FD_8510 ** (gnome-mount:1378): DEBUG: read default option 'shortname=mixed' from gconf strlist key /system/storage/default_options/vfat/mount_options ** (gnome-mount:1378): DEBUG: read default option 'uid=' from gconf strlist key /system/storage/default_options/vfat/mount_options ** (gnome-mount:1378): DEBUG: read default option 'utf8' from gconf strlist key /system/storage/default_options/vfat/mount_options ** (gnome-mount:1378): DEBUG: read default option 'umask=077' from gconf strlist key /system/storage/default_options/vfat/mount_options ** (gnome-mount:1378): DEBUG: read default option 'exec' from gconf strlist key /system/storage/default_options/vfat/mount_options ** (gnome-mount:1378): DEBUG: read default option 'usefree' from gconf strlist key /system/storage/default_options/vfat/mount_options ** (gnome-mount:1378): DEBUG: Mounting /org/freedesktop/Hal/devices/volume_uuid_E0FD_8510 with mount_point='DAN LENSKI', fstype='', num_options=6 ** (gnome-mount:1378): DEBUG: option='shortname=mixed' ** (gnome-mount:1378): DEBUG: option='uid=1000' ** (gnome-mount:1378): DEBUG: option='utf8' ** (gnome-mount:1378): DEBUG: option='umask=077' ** (gnome-mount:1378): DEBUG: option='exec' ** (gnome-mount:1378): DEBUG: option='usefree' ** (gnome-mount:1378): WARNING **: Mount failed for /org/freedesktop/Hal/devices/volume_uuid_E0FD_8510 org.freedesktop.Hal.Device.Volume.UnknownFailure : mount: wrong fs type, bad option, bad superblock on /dev/sdh2,missing codepage or helper program, or other errorIn some cases useful info is found in syslog - try dmesg | tail or so HERE'S THE FIX: Go into gconf-editor and navigate to /system/storage/default_options/vfat/mount_options, and then remove the "usefree" option from the list. Exit gconf-editor, and try hotplugging your drive again. It works :-) -- FAT: Unrecognized mount option "usefree" or missing value https://bugs.launchpad.net/bugs/151025 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 102097] Re: Auto mount does not work for USB drive
I can confirm this bug as well. I have tried a USB-IDE enclosure, a
thumb drive, two different cameras in UMS mode, and an MP3 player in UMS
mode. They mostly have vfat filesystems, though I have tried ext3 as
well. *ALL* of them automount just fine under Edgy.
If I run "udevmonitor -e" while inserting my Kingston DataTraveler 1gb
flash drive, with one ext3 partition and one vfat partition, it reports
that correctly:
UDEV [1191447365.558892] add /block/sdb/sdb2 (block)
UDEV_LOG=3
ACTION=add
DEVPATH=/block/sdb/sdb2
SUBSYSTEM=block
SEQNUM=2829
MINOR=18
MAJOR=8
PHYSDEVPATH=/devices/pci:00/:00:13.2/usb1/1-6/1-6:1.0/host6/target6:0:0/6:0:0:0
PHYSDEVBUS=scsi
PHYSDEVDRIVER=sd
UDEVD_EVENT=1
DEVTYPE=partition
ID_VENDOR=Kingston
ID_MODEL=DataTraveler_2.0
ID_REVISION=1.00
ID_SERIAL=Kingston_DataTraveler_2.0_015955-0:0
ID_SERIAL_SHORT=015955
ID_TYPE=disk
ID_INSTANCE=0:0
ID_BUS=usb
ID_PATH=pci-:00:13.2-usb-0:6:1.0-scsi-0:0:0:0
ID_FS_USAGE=filesystem
ID_FS_TYPE=vfat
ID_FS_VERSION=FAT32
ID_FS_UUID=46E1-B3BA
ID_FS_UUID_ENC=46E1-B3BA
ID_FS_LABEL=
ID_FS_LABEL_ENC=
ID_FS_LABEL_SAFE=
DEVNAME=/dev/sdb2
DEVLINKS=/dev/disk/by-id/usb-Kingston_DataTraveler_2.0_015955-0:0-part2
/dev/disk/by-path/pci-:00:13.2-usb-0:6:1.0-scsi-0:0:0:0-part2
/dev/disk/by-uuid/46E1-B3BA
UDEV [1191447365.598111] add /block/sdb/sdb1 (block)
UDEV_LOG=3
ACTION=add
DEVPATH=/block/sdb/sdb1
SUBSYSTEM=block
SEQNUM=2828
MINOR=17
MAJOR=8
PHYSDEVPATH=/devices/pci:00/:00:13.2/usb1/1-6/1-6:1.0/host6/target6:0:0/6:0:0:0
PHYSDEVBUS=scsi
PHYSDEVDRIVER=sd
UDEVD_EVENT=1
DEVTYPE=partition
ID_VENDOR=Kingston
ID_MODEL=DataTraveler_2.0
ID_REVISION=1.00
ID_SERIAL=Kingston_DataTraveler_2.0_015955-0:0
ID_SERIAL_SHORT=015955
ID_TYPE=disk
ID_INSTANCE=0:0
ID_BUS=usb
ID_PATH=pci-:00:13.2-usb-0:6:1.0-scsi-0:0:0:0
ID_FS_USAGE=filesystem
ID_FS_TYPE=ext3
ID_FS_VERSION=1.0
ID_FS_UUID=9c19c221-e338-49a7-9614-df76a4b940e2
ID_FS_UUID_ENC=9c19c221-e338-49a7-9614-df76a4b940e2
ID_FS_LABEL=Xubuntu
ID_FS_LABEL_ENC=Xubuntu
ID_FS_LABEL_SAFE=Xubuntu
DEVNAME=/dev/sdb1
DEVLINKS=/dev/disk/by-id/usb-Kingston_DataTraveler_2.0_015955-0:0-part1
/dev/disk/by-path/pci-:00:13.2-usb-0:6:1.0-scsi-0:0:0:0-part1
/dev/disk/by-uuid/9c19c221-e338-49a7-9614-df76a4b940e2
/dev/disk/by-label/Xubuntu
Also, dbus-monitor seems to be sending out signals to Gnome to mount the
two new partitions:
signal sender=:1.4 -> dest=(null destination) path=/org/gnome/GnomeVFS/Daemon;
interface=org.gnome.GnomeVFS.Daemon; member=DriveConnectedSignal
struct {
int32 8
int32 3
array [
]
string "/dev/sdb2"
string ""
string "Kingston DataTraveler 2.0"
string "gnome-dev-removable-usb"
string "/org/freedesktop/Hal/devices/volume_uuid_46E1_B3BA"
boolean true
boolean true
boolean false
}
signal sender=:1.4 -> dest=(null destination) path=/org/gnome/GnomeVFS/Daemon;
interface=org.gnome.GnomeVFS.Daemon; member=DriveConnectedSignal
struct {
int32 9
int32 3
array [
]
string "/dev/sdb1"
string ""
string "Kingston DataTraveler 2.0 (2)"
string "gnome-dev-removable-usb"
string
"/org/freedesktop/Hal/devices/volume_uuid_9c19c221_e338_49a7_9614_df76a4b940e2"
boolean true
boolean true
boolean false
}
Furthermore, vol_id AND blkid both correctly report the newly inserted
volumes.
On my system at least, the problem seems to be with gnome-volume-
manager, which reports the following:
$ gnome-volume-manager -n
# wait a few seconds...
# insert flash drive
manager.c/3306: gvm_user_active_at_console: check-foreground-console returned
with 0
manager.c/2538: Device added:
/org/freedesktop/Hal/devices/usb_device_951_1603_015955
manager.c/3306: gvm_user_active_at_console: check-foreground-console returned
with 0
manager.c/2538: Device added:
/org/freedesktop/Hal/devices/usb_device_951_1603_015955_if0
manager.c/3306: gvm_user_active_at_console: check-foreground-console returned
with 0
manager.c/2538: Device added:
/org/freedesktop/Hal/devices/usb_device_951_1603_015955_usbraw
manager.c/3306: gvm_user_active_at_console: check-foreground-console returned
with 0
manager.c/2538: Device added:
/org/freedesktop/Hal/devices/usb_device_951_1603_015955_if0_scsi_host
manager.c/3306: gvm_user_active_at_console: check-foreground-console returned
with 0
manager.c/2538: Device added:
/org/freedesktop/Hal/devices/usb_device_951_1603_015955_if0_scsi_host_scsi_device_lun0
manager.c/3306: gvm_user_active_at_console: check-foreground-console returned
with 0
manager.c/2538: Device added:
/org/freedesktop/Hal/devices/usb_device_951_1603_015955_if0_scsi_host_scsi_device_lun0_scsi_generic
manager.c/3306: gvm_user_active_at_console: check-foreground-console returned
with 0
manager.c/2538: Device added:
/org/freedesktop/Hal/devices/storage_serial_Kingston_DataTraveler_2_0_015955_0_0
manager.c/2303: not a mountab
[Bug 128543] suspend works from command line, but not via GNOME menu
Public bug reported: Distro: Ubuntu Feisty (x86_64) Hardware: Athlon 64 X2 processor, Radeon Xpress 200 integrated graphics, ECS RS485M-M motherboard Using the open-source "radeon" Xorg driver: 01:05.0 VGA compatible controller: ATI Technologies Inc RS482 [Radeon Xpress 200] (prog-if 00 [VGA]) Subsystem: Elitegroup Computer Systems Unknown device 2140 Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 5 Memory at f800 (32-bit, prefetchable) [size=64M] I/O ports at ee00 [size=256] Memory at fdef (32-bit, non-prefetchable) [size=64K] [virtual] Expansion ROM at fde0 [disabled] [size=128K] Capabilities: [50] Power Management version 2 I have recently gotten suspend to work on my desktop computer, via acpi-support, by setting a few parameters in /etc/default/acpi-support appropriately (and by a slight modification to the /etc/acpi/suspend.d/80-video-vesa-state.sh script, see this bug: https://bugs.launchpad.net/ubuntu/+source/acpi-support/+bug/128323). If I invoke /etc/acpi/sleep.sh directly via the command line, the computer goes into suspend mode, and when I press the power button it comes back up completely correctly. The X server log reports the following: (**) RADEON(0): Map applied, resetting engine ... (**) RADEON(0): Updating display base addresses... (**) RADEON(0): Memory map updated. (**) RADEON(0): Programming CRTC1, offset: 0x (**) RADEON(0): Wrote: 0x0006 0x0062 0x (0xa400) (**) RADEON(0): Wrote: rd=6, fd=98, pd=0 (**) RADEON(0): GRPH_BUFFER_CNTL from 20004c4c to 20407c7c (**) RADEON(0): EngineRestore (32/32) (**) RADEON(0): RADEONSaveScreen(2) (II) Configured Mouse: ps2EnableDataReporting: succeeded (**) RADEON(0): RADEONLeaveVT # here's the point where I suspend and restore (**) RADEON(0): RADEONRestore (**) RADEON(0): RADEONRestoreMode() (**) RADEON(0): RADEONRestoreMode(0x7de498) (**) RADEON(0): RADEONRestoreMemMapRegisters() : (**) RADEON(0): MC_FB_LOCATION : 0x3fff3e00 (**) RADEON(0): MC_AGP_LOCATION : 0x003f (**) RADEON(0): Map Changed ! Applying ... (**) RADEON(0): Map applied, resetting engine ... (**) RADEON(0): Updating display base addresses... (**) RADEON(0): Memory map updated. (**) RADEON(0): Programming CRTC1, offset: 0x (**) RADEON(0): Wrote: 0x00180006 0x0003005f 0x (0xa400) (**) RADEON(0): Wrote: rd=6, fd=95, pd=3 (**) RADEON(0): Ok, leaving now... (II) Open ACPI successful (/var/run/acpid.socket) (**) RADEON(0): RADEONEnterVT (**) RADEON(0): RADEONModeInit() 1920x1440 234.00 1920 2048 2256 2600 1440 1441 1444 1500 (24,32) -H +V 1920x1440 234.00 1920 2048 2256 2600 1440 1441 1444 1500 (24,32) -H +V (**) RADEON(0): Pitch = 15728880 bytes (virtualX = 1920, displayWidth = 1920) (**) RADEON(0): dc=23400, of=23400, fd=98, pd=1 (**) RADEON(0): RADEONInit returns 0x7dee48 (**) RADEON(0): RADEONRestoreMode() (**) RADEON(0): RADEONRestoreMode(0x7dee48) (**) RADEON(0): RADEONRestoreMemMapRegisters() : (**) RADEON(0): MC_FB_LOCATION : 0x3fff3e00 (**) RADEON(0): MC_AGP_LOCATION : 0xffc0 (**) RADEON(0): Map Changed ! Applying ... (**) RADEON(0): Map applied, resetting engine ... (**) RADEON(0): Updating display base addresses... (**) RADEON(0): Memory map updated. (**) RADEON(0): Programming CRTC1, offset: 0x (**) RADEON(0): Wrote: 0x0006 0x0062 0x (0xa400) (**) RADEON(0): Wrote: rd=6, fd=98, pd=0 (**) RADEON(0): GRPH_BUFFER_CNTL from 20004c4c to 20407c7c (**) RADEON(0): EngineRestore (32/32) (**) RADEON(0): RADEONSaveScreen(2) (II) Configured Mouse: ps2EnableDataReporting: succeeded (**) RADEON(0): RADEONLeaveVT (**) RADEON(0): RADEONRestore (**) RADEON(0): RADEONRestoreMode() (**) RADEON(0): RADEONRestoreMode(0x7de498) (**) RADEON(0): RADEONRestoreMemMapRegisters() : (**) RADEON(0): MC_FB_LOCATION : 0x3fff3e00 (**) RADEON(0): MC_AGP_LOCATION : 0x003f (**) RADEON(0): Map Changed ! Applying ... (**) RADEON(0): Map applied, resetting engine ... (**) RADEON(0): Updating display base addresses... (**) RADEON(0): Memory map updated. (**) RADEON(0): Programming CRTC1, offset: 0x (**) RADEON(0): Wrote: 0x00180006 0x0003005f 0x (0xa400) (**) RADEON(0): Wrote: rd=6, fd=95, pd=3 (**) RADEON(0): Ok, leaving now... (II) Open ACPI successful (/var/run/acpid.socket) (**) RADEON(0): RADEONEnterVT (**) RADEON(0): RADEONModeInit() 1920x1440 234.00 1920 2048 2256 2600 1440 1441 1444 1500 (24,32) -H +V 1920x1440 234.00 1920 2048 2256 2600 1440 1441 1444 1500 (24,32) -H +V (**) RADEON(0): Pitch = 15728880 bytes (virtualX = 1920, displayWidth = 1920) (**) RADEON(0): dc=23400, of=23400, fd=98, pd=1 (**) RADEON(0): RADEONInit returns 0x7dee48 (**) RADEON(0): RADEONRestoreMode() (**) RADEON(0): RADEONRestoreMode(0x7dee48) (**) RADEON(0): RADEONRestoreMemMapRegisters() : (**) RADEON(0): MC_FB_LOCATION : 0x3fff3e00 (**) RADEON(0): MC_AGP_LOCATION
[Bug 128323] incorrect assumption about saved VESA state
Public bug reported: Some background: this is an Athlon 64 X2 system running Ubuntu Feisty. Budget ECS RS485M-M motherboard with onboard ATI graphics: 01:05.0 VGA compatible controller: ATI Technologies Inc RS482 [Radeon Xpress 200] I've had a rough time getting suspend-to-RAM to work. First of all, the system CRASHES if "vbetool post" is run. I eventually figured out that I could use uswsusp to suspend, provided I execute the following commands: /bin/s2ram -f -s # saves and restores VBESTATE /usr/sbin/vbetool dpms on # display won't come back on without this So, I figured that I should be able to make suspend work within the framework of the ACPI suspend script (/etc/acpi/sleep.sh) by simply editing a few parameters in /etc/default/acpi-support: POST_VIDEO=false USE_DPMS=true SAVE_VBE_STATE=true To my surprise, this didn't work! I eventually tracked down the culprit in the VBE save/restore scripts: /etc/acpi/suspend.d/80-video-vesa- state.sh and /etc/acpi/resume.d/17-video-restore.sh Here's the default 80-video-vesa-state.sh script: > #!/bin/sh > > if [ x$SAVE_VBE_STATE = "xtrue" ]; then > # Check if we're in a VESA mode - if so, we need to do things more > # awkwardly. Otherwise, just use the state from boot. > VBEMODE=`vbetool vbemode get`; > if [ $VBEMODE != "3" ]; then > vbetool vbemode set 3; > vbetool vbestate save >$VBESTATE; > fi > fi Basically, this script *DOES NOT ACTUALLY SAVE THE VESA STATE* if we are in VBEMODE=3 (which indicates a non-VESA mode). Rather, it assumes that an appropriate state was saved at boot time. Which is not the case on *ANY* of my Ubuntu Feisty machines. So, when the system comes back up and runs the restore script, there is no saved state to restore!!! Does anyone know where the boot-time save is *SUPPOSED TO* occur? I have fixed this bug with a very slight alteration to /etc/acpi/suspend.d/80-video-vesa-state.sh. I modify the script so that it ALWAYS saves the vbestate if SAVE_VBE_STATE=true: > #!/bin/sh > > if [ x$SAVE_VBE_STATE = "xtrue" ]; then > # Check if we're in a VESA mode - if so, we need to do things more > # awkwardly. Otherwise, just use the state from boot. > VBEMODE=`vbetool vbemode get`; > if [ $VBEMODE != "3" ]; then > vbetool vbemode set 3; > fi > vbetool vbestate save >$VBESTATE; > fi With this modification, my system suspends and restores flawlessly from the GNOME menu, or by directly invoking the acpi-support scripts. How does it work for others? I don't think it should break anyone's system, since at worst it redundantly saved the VBESTATE a second time. ** Affects: acpi-support (Ubuntu) Importance: Undecided Status: New -- incorrect assumption about saved VESA state https://bugs.launchpad.net/bugs/128323 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 84145] tg-admin doesn't work with python 2.5
Public bug reported:
I am running Feisty on x86_64 and just installed TurboGears via "apt-get
install python-turbogears".
Now tg-admin crashes when I run it:
$ tg-admin
Traceback (most recent call last):
File "/usr/bin/tg-admin", line 8, in
load_entry_point('TurboGears==1.0b1', 'console_scripts', 'tg-admin')()
File "/usr/lib/python2.5/site-packages/pkg_resources.py", line 236, in
load_entry_point
return get_distribution(dist).load_entry_point(group, name)
File "/usr/lib/python2.5/site-packages/pkg_resources.py", line 2097, in
load_entry_point
return ep.load()
File "/usr/lib/python2.5/site-packages/pkg_resources.py", line 1830, in load
entry = __import__(self.module_name, globals(),globals(), ['__name__'])
File "/var/lib/python-support/python2.5/turbogears/__init__.py", line 6, in
from turbogears.controllers import expose, flash, validate, redirect, \
File "/var/lib/python-support/python2.5/turbogears/controllers.py", line 9,
in
import kid
File "/var/lib/python-support/python2.5/kid/__init__.py", line 30, in
from kid.codewriter import KID_XMLNS
File "/var/lib/python-support/python2.5/kid/codewriter.py", line 16, in
from kid.parser import *
File "/var/lib/python-support/python2.5/kid/parser.py", line 9, in
from kid.et import * # ElementTree
AttributeError: 'module' object has no attribute 'ElementTree'
If I explicitly run with python2.4, it works fine:
$ python2.4 /usr/bin/tg-admin
All the relevant files in /var/lib/python-support/python2.X are simply
symlinks to /usr/share/python-support. That's to say, the exact same
source files are accessed by python2.4 and python2.5.
I haven't been able to figure out what is causing this problem, so I've
simply modified tg-admin to explicitly run under python2.4:
#!/usr/bin/python2.4
#EASY-INSTALL-ENTRY-SCRIPT: ...
I've found that launching the start-server.py scripts produced by tg-
admin produces the same error when run with python2.5, but they work
fine with 2.4
** Affects: turbogears (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
tg-admin doesn't work with python 2.5
https://launchpad.net/bugs/84145
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 75765] Re: This package should depends on mtools
The mtools dependence of syslinux is kind of silly ... Since only root can mount filesystems, but mtools can operate on any msdos filesystem with the appropriate permissions, the author decided to simply use mtools to copy the bootloader (LDLINUX.SYS) onto the disk. The latest version of syslinux, 3.35, can be built so as not to depend on mtools... in this version, the msdos filesystem is mounted in the usual manner and then the bootloader is copied on the usual Linux way. Version 3.35 also makes syslinux more like isolinux in that the configuration files can be in a subdirectory. Hopefully there will be a 3.35 package for Ubuntu soon!! -- This package should depends on mtools https://launchpad.net/bugs/75765 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 80813] powernowd fails to start under Feisty
Public bug reported: Binary package hint: powernowd I'm running Feisty on an Athlon 64 (socket 939) system. $ uname -a Linux tonquil 2.6.19-7-generic #2 SMP Mon Dec 4 12:39:22 UTC 2006 x86_64 GNU/Linux When the computer boots, the powernow-k8 module is loaded: $dmesg | grep powernow [ 93.306823] powernow-k8: Found 1 AMD Athlon(tm) 64 Processor 3500+ processors (version 2.00.00) [ 93.306864] powernow-k8:0 : fid 0xe (2200 MHz), vid 0x6 [ 93.306866] powernow-k8:1 : fid 0xc (2000 MHz), vid 0x8 [ 93.306868] powernow-k8:2 : fid 0xa (1800 MHz), vid 0xa [ 93.306871] powernow-k8:3 : fid 0x2 (1000 MHz), vid 0x12 However, the powernowd process never starts up. I can start it manually by running /etc/init.d/powernowd start, in which case it runs fine. Under Edgy, I never had this problem. Powernowd would start up reliably every time I booted. ** Affects: powernowd (Ubuntu) Importance: Undecided Status: Unconfirmed -- powernowd fails to start under Feisty https://launchpad.net/bugs/80813 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 80468] one thing to add
Perhaps the worst thing about this bug is there is NO indication of what has gone wrong... if you dist-upgrade from edgy to feisty, then your USB printer will stop working and quite mysteriously. When you try to print to a USB printer that CUPS does not have permissions to access, the graphical utilities give ZERO indication of the problem: gnome-cups-icon simply says that the print job is "paused". The only way to discover the problem is to inspect the log files: E [20/Jan/2007:21:11:54 -0500] PID 27330 (/usr/lib/cups/backend/parallel) stopped with status 1! E [20/Jan/2007:21:11:54 -0500] [Job 75] Unable to open parallel port device file "/dev/usblp0": Permission denied E [20/Jan/2007:21:11:54 -0500] [Job 75] No %%BoundingBox: comment in header! It would be a big improvement if the Gnome CUPS utilities notified the user of this problem. -- [Feisty]At this moment can't detected printers https://launchpad.net/bugs/80468 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 80662] Re: Permissions problem prevens printers from printing (Feisty)
*** This bug is a duplicate of bug 80468 *** The problem is that the "cupsys" user does not belong to the "plugdev" group, and all printer access actually is initiated by a process running as that user. You need to add the "cupsys" user to the "pludev" group. I posted this solution to the dupe bug: https://launchpad.net/bugs/80468 -- Permissions problem prevens printers from printing (Feisty) https://launchpad.net/bugs/80662 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 80468] source of this bug determined
I've determined the source of this bug, which should only affect USB printers $ ls -l /dev/usblp0 /dev/lp0 crw-rw 1 root lp6, 0 2007-01-20 12:34 /dev/lp0 crw-rw 1 root plugdev 180, 0 2007-01-20 12:34 /dev/usblp0 The problem is this: udev makes ALL usb devices owned by group "plugdev", but it makes built-in parallel ports owned by group "lp". Now, when attempting to detect printers or print, CUPS runs with the permissions of the user "cupsys". This user belongs to the "lp" group, but NOT to the "plugdev" group: $ groups cupsys cupsys : lpadmin lp dialout scanner ssl-cert There are two possible solutions (both of which I have confirmed to work): (a) make "cupsys" a member of the "plugdev" group (b) make /dev/usblp0 owned by the group "lp" rather than by "plugdev" I'm not sure which solution is better. Anyone? -- [Feisty]At this moment can't detected printers https://launchpad.net/bugs/80468 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 31857] Re: r818x driver freezes randomly
Okay, I have tracked down a bit more info on this bug: it is evidently a
soft lockup resulting from a spinlock. I can reproduce it by trying to
upload a 1gb file to a remote server without limiting the upload rate...
my system will freeze within a few seconds or minutes of starting this.
The system freezes, and then a few seconds later it spews out debug info
onto the console.
uname -a: Linux localhost 2.6.19-7-generic #2 SMP Mon Dec 4 12:39:22 UTC
2006 x86_64 GNU/Linux
Unfortunately I haven't got a serial console set up, but here are the
top few levels of the call trace, which are always the same:
Call trace:
:ieee80211_rtl:rtl_ieee80211_stop_queue+0x20/0x60
:ieee80211_rtl:rtl_ieee80211_softmac_xmit+0x74/0xc0
:ieee80211_rtl:rtl_ieee80211_xmit+0x886/0x960
__qdisc_run+0x11c/0x200
dev_queue_xmit+0x125/0x270
ip_output+0x217/0x270
ip_queue_xmit+0x446/0x4a0
tcp_transmit_skb+0x666/0x700
tcp_push_one+0xfc/0x150
tcp_sendmsg+0x88f/0xb10
Code: 83 3f 00 7e fa eb f2 c3 0f 1f 80
00 00 00 00 0f 1f 80 00 00
Here is the code of the offending function (in the file /usr/src/linux-
source-2.6.19/ubuntu/wireless/rtl_ieee80211/rtl_ieee80211_softmac.c from
the Ubuntu package linux-source-2.6.19):
void rtl_ieee80211_stop_queue(struct rtl_ieee80211_device *ieee)
{
unsigned long flags;
spin_lock_irqsave(&ieee->lock,flags);
if (! netif_queue_stopped(ieee->dev)){
netif_stop_queue(ieee->dev);
ieee->softmac_stats.swtxstop++;
}
ieee->queue_stop = 1;
spin_unlock_irqrestore(&ieee->lock,flags);
}
Okay, will this help get the ball rolling for finding a fix to this
problem? Any hints on how to fix it? I haven't done much kernel
hacking...
--
r818x driver freezes randomly
https://launchpad.net/bugs/31857
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 31857] Re: r818x driver freezes randomly
I can confirm this bug under both Edgy and Feisty (stock kernels). I am using a wireless card with a Realtek 8225 front-end chip. I have found that the system freezes ONLY when I am SENDING lots of data, NEVER when receiving. For example, if I throttle a file upload to 10 kB/s, it will continue to work indefinitely, but if I allow it to run at full speed the system will normally crash in a few seconds. Who is maintaining this driver? I emailed the maintainer listed in the log files several months ago, but never received a response... I would like to try to fix this problem myself, but haven't made much headway. There's no indication in the system logs of anything going wrong before it crashes. -- r818x driver freezes randomly https://launchpad.net/bugs/31857 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 74672] ESSID gets truncated
Public bug reported: I upgraded from edgy to feisty a couple days ago, and found that my wireless network connection no longer worked. It seemed that whatever I used as my ESSID would get truncated by one character: $ sudo iwconfig wlan0 essid linksys $ sudo iwconfig lono wireless extensions. eth0 no wireless extensions. wlan0 802.11b/g ESSID:"linksy" Mode:Managed Frequency=2.427 GHz Access Point: Not-Associated Bit Rate=54 Mb/s Retry:on Fragment thr:off Encryption key:off Power Management:off Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 In order to get connected, I had to append an extra character to the correct ESSID: $ sudo iwconfig wlan0 essid linksysZ $ sudo iwconfig lono wireless extensions. eth0 no wireless extensions. wlan0 802.11b/g ESSID:"linksys" Mode:Managed Frequency=2.427 GHz Access Point: Not-Associated Bit Rate=54 Mb/s Retry:on Fragment thr:off Encryption key:off Power Management:off Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 I posted about this bug on Ubuntuforums, and another user tracked down the apparent source of the bug in wireless_tools_28, in the file iwconfig.c. Here's a link to his findings: http://ubuntuforums.org/showpost.php?p=1849606&postcount=2 ** Affects: wireless-tools (Ubuntu) Importance: Undecided Status: Unconfirmed -- ESSID gets truncated https://launchpad.net/bugs/74672 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 63905] mouse cursor disappears
Public bug reported: Binary package hint: xserver-xorg-driver-nv I upgraded from Dapper to Edgy beta a few weeks ago, and decided to switch from the closed-source nvidia X driver to the open-source nv driver. Everything has been fine EXCEPT: When I log out of GNOME, or press CTRL-ALT-DEL to kill the X-server, or otherwise kill gdm or my X session, the mouse cursor disappears and I can't make it come back other than by rebooting. I've tried several workarounds to get the mouse cursor to reappear: * restarting gdm (/etc/init.d/gdm restart) * changing the Gnome mouse cursor theme (has no effect, mouse cursor does not reappear) * restarting X with the "nvidia" driver rather than the "nv" driver; I was *very* surprised, but this did not fix the problem!!! The only way to get the cursor to reappear is by rebooting, as far as I can tell. My video card is an NVidia GeForce 6100 (integrated into motherboards for AMD K8 processors). ** Affects: xserver-xorg-driver-nv (Ubuntu) Importance: Undecided Status: Unconfirmed -- mouse cursor disappears https://launchpad.net/bugs/63905 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
