[Touch-packages] [Bug 244250] Re: Spurious reboot notifications caused by libssl upgrades.
A web server is supposed to retrieve data from database, run application logic, write back to database if needed, write an HTML document or JSON object to output, and wait for the next request. Ideally, it's stateless between requests. A desktop application, on the other hand, is more likely to have a lot of state in RAM that isn't persisted to the file system. In particular, you can't "simply restart" a web browser because when a browser restarts, it retrieves the HTML document open in each tab as if the user had navigated to it again. This incurs data loss in two ways: 1. If the user is offline, pages open in tabs for later reading will be replaced with "Cannot find server" error pages. (Chromium, for example, shows the "downasaur" minigame.) I often do this on my laptop so that I have something to read while riding the bus to work or wherever. 2. Several web applications, such as comment composition forms on Slashdot, lose DOM state if closed. When the browser navigates to the page again, the DOM is reset to what it was when the page was first opened, and the comment that the user was composing is lost. I imagine any webmail site that doesn't automatically save drafts in the background has the same problem, and even those that do save drafts will have a problem if the user is offline and the site doesn't use a Service Worker. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/244250 Title: Spurious reboot notifications caused by libssl upgrades. Status in openssl package in Ubuntu: Fix Released Bug description: The postinst script for libssl0.9.8 currently has a bug where it sends a reboot notifcation whenever libssl is configured. So reconfiguring libssl0.9.8 or even just installing libssl0.9.8 will result in a reboot notification. Sending of the reboot notification should definitely be moved inside the upgrading guard. The correct fix is likely to move it inside a version comparison guard for particular important updates like Colin suggests below -- this is what every other standard package using notify-reboot-required does. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/244250/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1193236] Re: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-*
Comment #20 appears to recommend filing a deliberate duplicate: > Please open your own report if you are affected. One such duplicate is Bug #1617630. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1193236 Title: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-* Status in at-spi: Invalid Status in at-spi2-core package in Ubuntu: Invalid Status in gnome-session package in Ubuntu: Invalid Status in at-spi2-core package in Debian: Invalid Bug description: Since a few days, xsession-errors is fullfilled by that kind of errors: ** (nautilus:22621): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-uUkE07qdBK: Connection refused ** (gedit:22640): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-uUkE07qdBK: Connection refused Similar errors are reported all over the net, but Debian have tried to fix it already: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702517 But some other devs seems to blame an atk-bridge: https://groups.google.com/forum/#!topic/yad-common/nYP0RutlxNA And some others suggest a dbus/gdbus race; the good thing is that seems not disturbing that much the system. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libgdk-pixbuf2.0-0 2.28.1-1ubuntu2 ProcVersionSignature: Ubuntu 3.9.0-6.14-generic 3.9.6 Uname: Linux 3.9.0-6-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.10.2-0ubuntu1 Architecture: i386 Date: Fri Jun 21 08:35:40 2013 MarkForUpload: True SourcePackage: gdk-pixbuf UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/at-spi/+bug/1193236/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1617630] Re: Mousepad show the warning Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus -*
I even encountered this bug when I tried to report it. $ ubuntu-bug at-spi2-core ** (apport-gtk:): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-##: Connection refused -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1617630 Title: Mousepad show the warning Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus -* Status in at-spi2-core package in Ubuntu: Confirmed Bug description: When I start mousepad in a terminal, I have this warning : ** (mousepad:25021): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-5pX3Lo3SAH: Connexion refusée When I start it with GKSU, the warning is not displayed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1617630/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1705344] [NEW] Determine file extensions supported by Game_Music_Emu
Public bug reported: lsb_release -rd says: Description:Ubuntu 16.04.2 LTS Release:16.04 apt show libgme-dev says: Package: libgme-dev Version: 0.6.0-3ubuntu0.16.04.1 I am developing a music player and want to list all types that my music player's Game_Music_Emu plug-in can play. I can iterate through types with gme_type_list(), but all I can retrieve about each gme_type_t through the C API are the name of the console it's associated with (gme_type_system()) and whether the type supports multiple movements (gme_type_multitrack()). I'd like to be able to look up the most common extension associated with a track. I can go from extension to type (gme_identify_extension()), and I expected there to be a function to go the other way, but there wasn't. I've filed related issues on other forks of GME: https://github.com/kode54/Game_Music_Emu/issues/7 https://bitbucket.org/mpyne/game-music-emu/issues/13/list-all-supported-extensions One fork maintainer plans to fix it by adding a function with the following signature: const char *gme_type_extension(gme_type_t); ** Affects: game-music-emu (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to game-music-emu in Ubuntu. https://bugs.launchpad.net/bugs/1705344 Title: Determine file extensions supported by Game_Music_Emu Status in game-music-emu package in Ubuntu: New Bug description: lsb_release -rd says: Description: Ubuntu 16.04.2 LTS Release: 16.04 apt show libgme-dev says: Package: libgme-dev Version: 0.6.0-3ubuntu0.16.04.1 I am developing a music player and want to list all types that my music player's Game_Music_Emu plug-in can play. I can iterate through types with gme_type_list(), but all I can retrieve about each gme_type_t through the C API are the name of the console it's associated with (gme_type_system()) and whether the type supports multiple movements (gme_type_multitrack()). I'd like to be able to look up the most common extension associated with a track. I can go from extension to type (gme_identify_extension()), and I expected there to be a function to go the other way, but there wasn't. I've filed related issues on other forks of GME: https://github.com/kode54/Game_Music_Emu/issues/7 https://bitbucket.org/mpyne/game-music-emu/issues/13/list-all-supported-extensions One fork maintainer plans to fix it by adding a function with the following signature: const char *gme_type_extension(gme_type_t); To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/game-music-emu/+bug/1705344/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 524454] Re: Networking is disabled on boot (usually after suspend/hibernate)
It's still happening in 14.04 LTS (Trusty) on my Dell Inspiron mini 1012 laptop, usually after a fairly long use session. But it always starts working again after either another suspend/resume cycle or restarting Network Manager. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/524454 Title: Networking is disabled on boot (usually after suspend/hibernate) Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Lucid: Won't Fix Status in network-manager source package in Maverick: Fix Released Status in network-manager package in Debian: Fix Released Bug description: Binary package hint: network-manager My networking is disabled every time I boot. To correct, I must right- click on Network Manager applet and choose "Enable Networking," after which my wireless networks become available and I can get online. I'm using Lucid on a MacBookPro2,1 --SRU details Impact: This bug keeps the the networking disabled after a resume from suspend/hibernate. Right-clicking on the Network Manager applet and choosing "Enable Networking" solves the problem. How the bug has been addressed: NM 0.8 has some bugs witch are partially listed at http://live.gnome.org/NetworkManager/ReleaseProcess The upstream has provided two patches (both are attached to this bug). There are two patches because the person who did the fix forgot something from the first commit and therefore made a second commit. The links to commits and patches can be found at comments 59 and 61. Some of these bugs including this bug are fixed in NM 0.8.1 TEST CASE: Suspend or hibernate. The upstream report isn't very detailed about this, but in my case that process is unsuccessful. On resume you should not have a working network. To solve: 1) run service network-manager stop rm /var/lib/NetworkManager/NetworkManager.state service network-manager start or 2) right-click on Network Manager applet and choose "Enable Networking," or 3) Reboot. Regression potential: Really none. This bug is a regression in the new NM 0.8. The upstream has fixed this bug and some other bugs in NM 0.8.1. ProblemType: Bug Architecture: i386 CRDA: Error: [Errno 2] No such file or directory Date: Fri Feb 19 14:25:27 2010 DistroRelease: Ubuntu 10.04 IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) IpRoute: 10.45.43.0/24 dev wlan0 proto kernel scope link src 10.45.43.23 metric 2 169.254.0.0/16 dev wlan0 scope link metric 1000 default via 10.45.43.1 dev wlan0 proto static Keyfiles: Error: [Errno 2] No such file or directory Package: network-manager 0.8~rc2-0ubuntu1 ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-13.18-generic SourcePackage: network-manager Uname: Linux 2.6.32-13-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/524454/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
