[Touch-packages] [Bug 1618590] Re: scoperunner crashed with SIGSEGV in QObject::disconnect()
Was the fix tested already with a qtbase compilation? Both it and its pre-requirement https://codereview.qt- project.org/#/c/157488 are not merged in upstream, so would need to be merged first. There may be some trouble they are causing since they are not yet merged. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1618590 Title: scoperunner crashed with SIGSEGV in QObject::disconnect() Status in qtbase-opensource-src package in Ubuntu: Confirmed Bug description: crash ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: unity-scope-click 0.1.1+16.10.20160808-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Tue Aug 30 17:54:20 2016 ExecutablePath: /usr/lib/x86_64-linux-gnu/unity-scopes/scoperunner InstallationDate: Installed on 2016-08-27 (3 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcCmdline: /usr/lib/x86_64-linux-gnu/unity-scopes/scoperunner /usr/lib/x86_64-linux-gnu/unity-scopes/clickapps/clickscope.ini Scope: Apps Signal: 11 SourcePackage: unity-scope-click StacktraceTop: QObject::disconnect(QObject const*, char const*, QObject const*, char const*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 start_thread (arg=0x7fae9eade700) at pthread_create.c:333 Title: scoperunner crashed with SIGSEGV in QObject::disconnect() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1618590/+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 1403260] Re: Undefined symbols within QtGui.so in PyQt4
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: qt4-x11 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/1403260 Title: Undefined symbols within QtGui.so in PyQt4 Status in qt4-x11 package in Ubuntu: Confirmed Bug description: Whenever I try to run a Qt program, such as this one: import sys from PyQt4.QtGui import * app = QApplication(sys.argv) button = QPushButton(“Hello World”, None) button.show() app.exec_() No application is launched, and I get the following error message: from PyQt4.QtGui import * ImportError: /usr/lib/python2.7/dist-packages/PyQt4/QtGui.so: undefined symbol: _ZN15QSessionManager16staticMetaObjectE I have reinstalled the following packages to no avail: python-qt4 python-qt4-dev python-qt4-gl libqtgui4 libqtcore4 Some system info: Description: Ubuntu 14.04.1 LTS Release: 14.04 3.13.0-32-lowlatency usr/bin/python2.7: Python 2.7.6 Using Qt version 4.8.6 python-qt4: Installed: 4.10.4+dfsg-1ubuntu1 Candidate: 4.10.4+dfsg-1ubuntu1 Version table: *** 4.10.4+dfsg-1ubuntu1 0 500 http://mx.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status python-qt4-dev: Installed: 4.10.4+dfsg-1ubuntu1 Candidate: 4.10.4+dfsg-1ubuntu1 Version table: *** 4.10.4+dfsg-1ubuntu1 0 500 http://mx.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status libqtcore4: Installed: 4:4.8.5+git192-g085f851+dfsg-2ubuntu4 Candidate: 4:4.8.5+git192-g085f851+dfsg-2ubuntu4 Version table: *** 4:4.8.5+git192-g085f851+dfsg-2ubuntu4 0 500 http://mx.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status libqtgui4: Installed: 4:4.8.5+git192-g085f851+dfsg-2ubuntu4 Candidate: 4:4.8.5+git192-g085f851+dfsg-2ubuntu4 Version table: *** 4:4.8.5+git192-g085f851+dfsg-2ubuntu4 0 500 http://mx.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status Hope anyone can help me with this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/1403260/+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 1618981] Re: Autopilot testcase hangs
** Changed in: address-book-app (Ubuntu) Importance: High => Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to address-book-app in Ubuntu. https://bugs.launchpad.net/bugs/1618981 Title: Autopilot testcase hangs Status in address-book-app package in Ubuntu: New Bug description: On krillin -> version 564 from ubuntu-touch/rc-proposed/ubuntu channel running the -> address_book_app.tests.test_create_new_from_uri.TestCreateNewContactFromURI.test_save_new_contact autopilot test starts and then it hangs with the New contact page. address-book-app 0.2+15.04.20160823-0ubuntu1 address-book-app-autopilot 0.2+15.04.20160823-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/address-book-app/+bug/1618981/+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 1548534] Re: 1.16.7 installation fails with 'failed to preconfigure with exit status 30'
[Expired for lightdm (Ubuntu) because there has been no activity for 60 days.] ** Changed in: lightdm (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1548534 Title: 1.16.7 installation fails with 'failed to preconfigure with exit status 30' Status in lightdm package in Ubuntu: Expired Bug description: I'm on Ubuntu Wily and lightdm has been failing to install for the past couple weeks. I've tried everything from removing the package and doing a clean install to reverting to an older version, but it always fails with the same error. Here's the error that I get when running the install: -- Preconfiguring packages ... lightdm failed to preconfigure, with exit status 30 Selecting previously unselected package lightdm. . . . . Setting up lightdm (1.16.7-0ubuntu1) ... dpkg: error processing package lightdm (--configure): subprocess installed post-installation script returned error exit status 30 -- With the last reboot, I can no longer load the desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1548534/+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 1623969] Re: Cannot log in to kubuntu after update (Intel graphics + ksshaskpass)
Alan Robertson, feel free to start with the oldest, and advise to the results. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1623969 Title: Cannot log in to kubuntu after update (Intel graphics + ksshaskpass) Status in xorg package in Ubuntu: Incomplete Bug description: I just took some updates to a number of graphic libraries on 16.04, and now I can't login to kubuntu. The symptom is that it takes my password on the greeter screen, but never updates the screen after that. The messages include these possibly related kernel messages: kernel: [ 701.564034] [drm:intel_set_cpu_fifo_underrun_reporting [i915]] *ERROR* uncleared fifo underrun on pipe B kernel: [ 701.564054] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe B FIFO underrun I'm currently running kernel 4.4.0-36. Here are my most recent updates. The problem started after I rebooted. Of course that was the next time I logged in too... Start-Date: 2016-09-07 08:46:04 Commandline: /usr/bin/unattended-upgrade Remove: libcdaudio1:amd64 (0.99.12p2-14), linux-image-extra-4.2.0-36-generic:amd64 (4.2.0-36.42), linux-image-extra-4.4.0-22-generic:amd64 (4.4.0-22.40), gtk2-engines-murrine:amd64 (0.98.2-0ubuntu2.1), linux-image-extra-4.4.0-24-generic:amd64 (4.4.0-24.43), libslv2-9:amd64 (0.6.6+dfsg1-3build1), linux-image-extra-4.4.0-28-generic:amd64 (4.4.0-28.47), linux-image-extra-4.4.0-31-generic:amd64 (4.4.0-31.50), libfaac0:amd64 (1.28+cvs20151130-1) End-Date: 2016-09-07 08:48:13 Start-Date: 2016-09-07 16:42:27 Install: libgnome-keyring-common:amd64 (3.12.0-1build1, automatic), libgnome-keyring0:amd64 (3.12.0-1build1, automatic) Upgrade: libgles2-mesa:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), libgles1-mesa:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), libglapi-mesa:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), libglapi-mesa:i386 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), p11-kit:amd64 (0.23.2-3, 0.23.2-5~ubuntu16.04.1), libxatracker2:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), libegl1-mesa-drivers:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), libegl1-mesa:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), libegl1-mesa:i386 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), p11-kit-modules:amd64 (0.23.2-3, 0.23.2-5~ubuntu16.04.1), libgbm1:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), libgbm1:i386 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), cups-filters:amd64 (1.8.3-2ubuntu3, 1.8.3-2ubuntu3.1), chromium-browser:amd64 (51.0.2704.79-0ubuntu0.16.04.1.1242, 52.0.2743.116-0ubuntu0.16.04.1.1250), libcupsfilters1:amd64 (1.8.3-2ubuntu3, 1.8.3-2ubuntu3.1), chromium-codecs-ffmpeg-extra:amd64 (51.0.2704.79-0ubuntu0.16.04.1.1242, 52.0.2 743.116-0ubuntu0.16.04.1.1250), libwayland-egl1-mesa:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), libfontembed1:amd64 (1.8.3-2ubuntu3, 1.8.3-2ubuntu3.1), libgl1-mesa-dri:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), libgl1-mesa-dri:i386 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), cups-filters-core-drivers:amd64 (1.8.3-2ubuntu3, 1.8.3-2ubuntu3.1), libgl1-mesa-glx:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), libgl1-mesa-glx:i386 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), libp11-kit0:amd64 (0.23.2-3, 0.23.2-5~ubuntu16.04.1), libp11-kit0:i386 (0.23.2-3, 0.23.2-5~ubuntu16.04.1), mesa-vdpau-drivers:amd64 (11.2.0-1ubuntu2.1, 11.2.0-1ubuntu2.2), chromium-browser-l10n:amd64 (51.0.2704.79-0ubuntu0.16.04.1.1242, 52.0.2743.116-0ubuntu0.16.04.1.1250), ubuntu-mono:amd64 (14.04+16.04.20160621-0ubuntu1, 14.04+16.04.20160804-0ubuntu1), cups-browsed:amd64 (1.8.3-2ubuntu3, 1.8.3-2ubuntu3.1) End-Date: 2016-09-07 16:44:34 Start-Date: 2016-09-12 14:31:39 Commandline: /usr/sbin/synaptic Requested-By: alanr (1000) Upgrade: snapd:amd64 (2.13, 2.14.2~16.04), libappstream-glib8:amd64 (0.5.13-1ubuntu2, 0.5.13-1ubuntu3), neo4j:amd64 (3.0.4, 3.0.5), accountsservice:amd64 (0.6.40-2ubuntu11.1, 0.6.40-2ubuntu11.2), libaccountsservice0:amd64 (0.6.40-2ubuntu11.1, 0.6.40-2ubuntu11.2) End-Date: 2016-09-12 14:32:17 It was after rebooting after updates that this occurred. My workaround is "rm -fr ~/.kde" - and that allows me to log in. I'm crippled, but at least I can log in... If I try to log in again without doing this, the problem recurs. This happens even if I just log in and log back out, and try to log in again. However, I may just found a better workaround - press ALT-CTRL-F1 then ALT-CTRL-F7, and then the next chunk of the login sequence occurs. This makes it consistent with an issue reported in AskUbuntu http://askubuntu.com/questions/765364/kubuntu-16-04-sddm-login-screen- hangs And it's possibly related to bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1550779 - because of the CPU underrun being apparently related to graphics. In fact, each time I do this, I get a little further in the login sequence. It ap
[Touch-packages] [Bug 1606078] Re: No sound with Ubuntu 16.04
After removing the changes made in file /etc/modprobe.d I also tried both packages as described above but neither one resulted in audio from the built in speakers. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1606078 Title: No sound with Ubuntu 16.04 Status in alsa-driver package in Ubuntu: Incomplete Bug description: After a fresh install of Ubuntu 16.04.1 on an LG S1 Express Dual laptop there was no sound from the speakers unless external speakers where hooked to the headphones socket. This applies to the Ubuntu Mate, Xubuntu and Lubuntu variants. This laptop was working fine for all previous releases up to 14.04. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bashar 3263 F pulseaudio CurrentDesktop: Unity Date: Mon Jul 25 01:51:19 2016 InstallationDate: Installed on 2016-07-24 (0 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bashar 3263 F pulseaudio Symptom_Jack: Line Out, Internal Symptom_Type: No sound at all Title: [S1-M401E1, Realtek ALC880, Line Out, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/16/2006 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: RKYWSF0B dmi.board.name: ROCKY dmi.board.vendor: LG Electronics dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LG Electronics dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrRKYWSF0B:bd02/16/2006:svnLGElectronics:pnS1-M401E1:pvrNotApplicable:rvnLGElectronics:rnROCKY:rvrNotApplicable:cvnLGElectronics:ct10:cvrN/A: dmi.product.name: S1-M401E1 dmi.product.version: Not Applicable dmi.sys.vendor: LG Electronics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1606078/+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 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
** Changed in: systemd Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS Status in systemd: New Status in systemd package in Ubuntu: Incomplete Bug description: I use a VPN configured with network-manager-openconnect-gnome in which a split-horizon DNS setup assigns different addresses to some names inside the remote network than the addresses seen for those names from outside the remote network. However, systemd-resolved often decides to ignore the VPN’s DNS servers and use the local network’s DNS servers to resolve names (whether in the remote domain or not), breaking the split-horizon DNS. This related bug, reported by Lennart Poettering himself, was closed with the current Fedora release at the time reaching EOL: https://bugzilla.redhat.com/show_bug.cgi?id=1151544 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+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 1393752] Re: missing symbols in libssl1.0.1f-1ubuntu2.7
Nope - same problem is still present: ... # Can't load '/users/nneul/.local/share/.cpan/build/Crypt-OpenSSL-CA-0.24-DUskTa/blib/arch/auto/Crypt/OpenSSL/CA/CONF/CONF.so' for module Crypt::OpenSSL::CA::CONF: /users/nneul/.local/share/.cpan/build/Crypt-OpenSSL-CA-0.24-DUskTa/blib/arch/auto/Crypt/OpenSSL/CA/CONF/CONF.so: undefined symbol: _CONF_add_string at /usr/lib/x86_64-linux-gnu/perl/5.22/DynaLoader.pm line 187. ... and no _ prefixed symbols present in the libraries. -- 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/1393752 Title: missing symbols in libssl1.0.1f-1ubuntu2.7 Status in openssl package in Ubuntu: Confirmed Bug description: _CONF_new_data is not exported. The function definition is still in the headers: # grep -r _CONF_new_data /usr/include/ /usr/include/openssl/conf_api.h:int _CONF_new_data(CONF *conf); The library itself does not export the symbol: $ readelf -Ws /lib/x86_64-linux-gnu/libcrypto.so.1.0.0 | grep CONF_new 1540: 0012f63084 FUNCGLOBAL DEFAULT 12 NCONF_new@@OPENSSL_1.0.0 LSB Relase: Description:Ubuntu 14.04.1 LTS Release:14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1393752/+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 1576692] Re: fully support package installation in systemd
verified with: printf "#cloud-config\npackages: [postgresql, samba, postfix]\n" > user-data n=x1 lxc launch ubuntu-daily:xenial $n sleep 10 lxc exec $n -- sh -c ' p=/etc/apt/sources.list.d/proposed.list echo deb http://archive.ubuntu.com/ubuntu $(lsb_release -sc)-proposed main > "$p" && apt-get update -q && apt-get -qy install cloud-init' lxc file push - $n/etc/cloud/cloud.cfg.d/update.cfg < user-data ## clean it out so next is first boot. lxc exec $n -- sh -c ' cd /var/lib/cloud && for d in *; do [ "$d" = "seed" ] || rm -Rf "$d"; done rm -Rf /var/log/cloud-init*' lxc exec $n reboot lxc exec $n -- tail -f /var/log/cloud-init-output.log ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1576692 Title: fully support package installation in systemd Status in cloud-init: Fix Released Status in cloud-init package in Ubuntu: Fix Released Status in init-system-helpers package in Ubuntu: Fix Released Status in cloud-init source package in Xenial: Fix Committed Status in init-system-helpers source package in Xenial: Fix Committed Bug description: in cloud-init users can install packages via cloud-config: #cloud-config packages: [apache2] Due to some intricacies of systemd and service installation that doesn't work all that well. We fixed the issue for simple services that do not have any dependencies on other services, or at least don't check those dependencies well under bug 1575572. We'd like to have a way to fully support this in cloud-init. Related bugs: * bug 1575572: apache2 fails to start if installed via cloud config (on Xenial) * bug 1611973: postgresql@9.5-main service not started if postgres installed via cloud-init * bug 1621336: snapd.boot-ok.service hangs eternally on cloud image upgrades (snapd packaging bug, but this cloud-init fix will workaround it) * bug 1620780: dev-sda2.device job running and times out * bug 1623570: Azure: cannot start walinux agent (Transaction order is cyclic.) * bug 1623868: cloud-final.service does not run due to dependency cycle SRU INFORMATION === FIX for init-system-helpers: https://anonscm.debian.org/cgit/collab-maint/init-system-helpers.git/commit/?id=1460d6a02 REGRESSION POTENTIAL for init-system-helpers: This changes invoke-rc.d and service, two very central pieces of packaging infrastructure. Errors in it will break installation/upgrades of packages or /etc/network/if-up.d/ hooks and the like. This changes the condition when systemd units get started without their dependencies, and the condition gets weakened. This means that behaviour in a booted system is unchanged, but during boot this could change the behaviour of if- up.d/ hooks (although they have never been defined well during boot anyway). However, I tested this change extensively in cloud images and desktop installations (particularly I recreated https://bugs.debian.org/777113 and confirmed that this approach also fixes it) and could not find any regression. TEST CASE (for both packages): Run lxc launch ubuntu-daily:x --config=user.user-data="$(printf "#cloud-config\npackages: [postgresql, samba, postfix]")" x1 This will install all three packages, but "systemctl status postgresql@9.5-main" will not be running. Now prepare a new image with the proposed cloud-init and init-system- helpers: lxc launch ubuntu-daily:x xprep lxc exec xprep bash # enable -proposed and dist-upgrade, then poweroff lxc publish xprep x-proposed Now run the initial lxc launch again, but against that new x-proposed image instead of the standard daily: lxc launch x-proposed --config=user.user-data="$(printf "#cloud- config\npackages: [postgresql, samba, postfix]")" x1 You should now have "systemctl status postgresql@9.5-main" running. Directly after rebooting the instance, check that there are no hanging jobs (systemctl list-jobs), particularly networking.service, to ensure that https://bugs.debian.org/777113 did not come back. Also test interactively installing a package that ships a service, like "apache2", and verify that it starts properly after installation. Verify that journalctl shows no dependency cycles and that all cloud init services and the target are active: $ systemctl list-units --no-legend --all 'cloud*' cloud-config.service loaded active exited Apply the settings specified in cloud-config cloud-final.service loaded active exited Execute cloud user/final scripts cloud-init-local.service loaded active exited Initial cloud-init job (pre-networking) cloud-init.service loaded active exited Initial cloud-init job (metadata service crawler) cloud-config.target loaded active active Cloud-config
[Touch-packages] [Bug 1624014] Re: Wrong bit set in klibc PXE dhcp/bootp flags
This bug was fixed in the package klibc - 2.0.4-8ubuntu3 --- klibc (2.0.4-8ubuntu3) yakkety; urgency=medium * debian/patches/broadcast_dhcp_send.patch: the patch sets the wrong bit in the bootp flags field, instead of 0x800 it must be 0x8000. (LP: #1624014) -- Dan Streetman Fri, 16 Sep 2016 20:20:58 -0400 ** Changed in: klibc (Ubuntu Yakkety) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1624014 Title: Wrong bit set in klibc PXE dhcp/bootp flags Status in klibc package in Ubuntu: Fix Released Status in klibc source package in Trusty: In Progress Status in klibc source package in Xenial: In Progress Status in klibc source package in Yakkety: Fix Released Bug description: [Description] The patch for bug 1327412 set the wrong bit in the bootp flags field. It set flags to 0x800, but the correct value is 0x8000. That sets the "broadcast" bit, and the spec requires all other bits to be 0. Setting one of the "must be zero" bits in the flags field causes some DHCP relay agents to drop the packets, causing PXE to fail. [Test Case] Get a DHCP relay agent that drops PXE packets with an invalid bootp.flags bit set, and try to PXE boot; it fails. [Regression] None, the previous patch introduced this regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1624014/+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 1624014] Re: Wrong bit set in klibc PXE dhcp/bootp flags
** Also affects: klibc (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: klibc (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: klibc (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: klibc (Ubuntu Trusty) Status: New => In Progress ** Changed in: klibc (Ubuntu Yakkety) Status: New => In Progress ** Changed in: klibc (Ubuntu Xenial) Status: New => In Progress ** Changed in: klibc (Ubuntu Yakkety) Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) ** Changed in: klibc (Ubuntu Trusty) Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) ** Changed in: klibc (Ubuntu Xenial) Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) ** Changed in: klibc (Ubuntu Trusty) Importance: Undecided => High ** Changed in: klibc (Ubuntu Xenial) Importance: Undecided => High ** Changed in: klibc (Ubuntu Yakkety) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1624014 Title: Wrong bit set in klibc PXE dhcp/bootp flags Status in klibc package in Ubuntu: In Progress Status in klibc source package in Trusty: In Progress Status in klibc source package in Xenial: In Progress Status in klibc source package in Yakkety: In Progress Bug description: [Description] The patch for bug 1327412 set the wrong bit in the bootp flags field. It set flags to 0x800, but the correct value is 0x8000. That sets the "broadcast" bit, and the spec requires all other bits to be 0. Setting one of the "must be zero" bits in the flags field causes some DHCP relay agents to drop the packets, causing PXE to fail. [Test Case] Get a DHCP relay agent that drops PXE packets with an invalid bootp.flags bit set, and try to PXE boot; it fails. [Regression] None, the previous patch introduced this regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1624014/+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 1605797] Re: [ICH - Intel 82801AA-ICH, playback] No sound at all
** Changed in: alsa-driver Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1605797 Title: [ICH - Intel 82801AA-ICH, playback] No sound at all Status in ALSA driver: Fix Released Status in alsa-driver package in Ubuntu: Confirmed Bug description: New ubuntu install on 2016-07-22; latest version. Running as virtualbox guest on latest OS X. Sound card recognized on mac, but not on guest. No sound in or out. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bobo 2690 F pulseaudio CurrentDesktop: Unity Date: Fri Jul 22 19:00:19 2016 InstallationDate: Installed on 2016-07-22 (0 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:I82801AAICH failed Symptom_Card: Built-in Audio - Intel 82801AA-ICH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bobo 2690 F pulseaudio Symptom_Type: No sound at all Title: [ICH - Intel 82801AA-ICH, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1605797/+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 1605189] Re: Authentication is required for suspending the system
This is an annoying bug that hasn't been addressed in the two and a half years it has plagued Ubuntu with the Xfce desktop. One can find bug reports going back to 14.04 after a faulty patch broke suspend. Fortunately for the terminally-skilled among us, the workaround is here: http://askubuntu.com/questions/543921/authentication-required-before- suspend -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1605189 Title: Authentication is required for suspending the system Status in systemd package in Ubuntu: Confirmed Bug description: Automatic suspend from the xfce power manager does not work, as a window opens and asks for my password. Well, if it wants to suspend the system after a given timeout, I cannot enter my password as I'm not in front of my system then. Once I'm able to enter my password it is too late to run the suspend action. The window asking for my password prints: Password: Details Action: org.freedesktop.login1.suspend Vendor: The systemd project ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu7 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Jul 21 13:13:12 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2014-08-17 (703 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: LENOVO 4236ML1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic root=/dev/mapper/ubuntu--vg-root ro intel_pstate=enable SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf 2 overridden configuration files found. UpgradeStatus: Upgraded to xenial on 2016-05-28 (53 days ago) dmi.bios.date: 07/05/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 83ET76WW (1.46 ) dmi.board.asset.tag: Not Available dmi.board.name: 4236ML1 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr83ET76WW(1.46):bd07/05/2013:svnLENOVO:pn4236ML1:pvrThinkPadT420:rvnLENOVO:rn4236ML1:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4236ML1 dmi.product.version: ThinkPad T420 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1605189/+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 1623841] Re: ActionSelectionPopover broken in latest UITK release
This bug was fixed in the package ubuntu-ui-toolkit - 1.3.2085+16.10.20160915 --- ubuntu-ui-toolkit (1.3.2085+16.10.20160915) yakkety; urgency=medium [ Zsombor Egri ] * Fix ActionList API break. (LP: #1623841) -- Zoltán Balogh Thu, 15 Sep 2016 15:17:27 + ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1623841 Title: ActionSelectionPopover broken in latest UITK release Status in ubuntu-ui-toolkit package in Ubuntu: Fix Released Status in webbrowser-app package in Ubuntu: Invalid Bug description: I upgraded packages on my laptop today (xenial + stable overlay PPA) and builds of lp:webbrowser-app started failing in tst_QmlTests. Those are the failures I’m seeing: FAIL! : QmlTests::NewTabView::test_delete_top_site() Uncaught exception: Cannot read property 'x' of undefined Loc: [/build/webbrowser-app/trunk/tests/unittests/qml/WebbrowserTestCase.qml(26)] FAIL! : QmlTests::NewTabView::test_expand_bookmarks() 'verify()' returned FALSE. () Loc: [/build/webbrowser-app/trunk/tests/unittests/qml/tst_NewTabView.qml(82)] FAIL! : QmlTests::NewTabView::test_keyboard_navigation() 'verify()' returned FALSE. () Loc: [/build/webbrowser-app/trunk/tests/unittests/qml/tst_NewTabView.qml(82)] FAIL! : QmlTests::NewTabView::test_keyboard_navigation() 'verify()' returned FALSE. () Loc: [/build/webbrowser-app/trunk/tests/unittests/qml/tst_NewTabView.qml(189)] FAIL! : QmlTests::TabsBar::test_context_menu_close() Uncaught exception: Cannot read property 'x' of undefined Loc: [/build/webbrowser-app/trunk/tests/unittests/qml/WebbrowserTestCase.qml(26)] FAIL! : QmlTests::TabsBar::test_context_menu_new_tab() Uncaught exception: Cannot read property 'x' of undefined Loc: [/build/webbrowser-app/trunk/tests/unittests/qml/WebbrowserTestCase.qml(26)] FAIL! : QmlTests::TabsBar::test_context_menu_reload() Uncaught exception: Cannot read property 'x' of undefined Loc: [/build/webbrowser-app/trunk/tests/unittests/qml/WebbrowserTestCase.qml(26)] FAIL! : QmlTests::TabsBar::test_menu_states_on_new_tab() Uncaught exception: Cannot read property 'enabled' of null Loc: [/build/webbrowser-app/trunk/tests/unittests/qml/tst_TabsBar.qml(245)] FAIL! : QmlTests::TabsBar::test_menu_states_on_page() Uncaught exception: Cannot read property 'enabled' of null Loc: [/build/webbrowser-app/trunk/tests/unittests/qml/tst_TabsBar.qml(256)] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1623841/+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 1375637] Re: Premature end of data in tag file line 247651 with libxml2
FWIW, I am currently experiencing the same error when running "createrepo" on a repo containing 20 RPMs. The host system is running Ubuntu 14.04.5 LTS, libxml2 version is 2.9.1+dfsg1-3ubuntu. For me, the error occurs every time, removing the repodata directories does not resolve this. % createrepo . Spawning worker 0 with 20 pkgs Workers Finished Saving Primary metadata Saving file lists metadata Saving other metadata Generating sqlite DBs I/O error : No such file or directory (process:18005): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: Parsing filelists.xml error: Premature end of data in tag package line 2263 (process:18005): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: Parsing filelists.xml error: Premature end of data in tag filelists line 2 Traceback (most recent call last): File "/usr/share/createrepo/genpkgmetadata.py", line 308, in main(sys.argv[1:]) File "/usr/share/createrepo/genpkgmetadata.py", line 280, in main mdgen.doRepoMetadata() File "/usr/lib/python2.7/dist-packages/createrepo/__init__.py", line 999, in doRepoMetadata rp.getFilelists(complete_path, csum) File "/usr/lib/python2.7/dist-packages/sqlitecachec.py", line 54, in getFilelists self.repoid)) TypeError: Parsing filelists.xml error: Premature end of data in tag file line 2332 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxml2 in Ubuntu. https://bugs.launchpad.net/bugs/1375637 Title: Premature end of data in tag file line 247651 with libxml2 Status in libxml2 package in Ubuntu: Confirmed Bug description: Hello, I'm getting the following behaviour of createrepo on Ubuntu 14.04.1 LTS with libxml2=2.9.1+dfsg1-3ubuntu4.3(trusty-updates/main) and libxml2=2.9.1+dfsg1-3ubuntu4(trusty/main). createrepo -g /home/jenkins/workspace/tmp/fuel_5_1_mirror/local_mirror/centos/os/x86_64/comps.xml \ -o /home/jenkins/workspace/tmp/fuel_5_1_mirror/local_mirror/centos/os/x86_64/ /home/jenkins/workspace/tmp/fuel_5_1_mirror/local_mirror/centos/os/x86_64/ I/O error : No such file or directory (process:29830): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: Parsing filelists.xml error: Premature end of data in tag package line 246828 (process:29830): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: Parsing filelists.xml error: Premature end of data in tag filelists line 2 Spawning worker 0 with 54 pkgs Spawning worker 1 with 54 pkgs Spawning worker 2 with 54 pkgs Spawning worker 3 with 54 pkgs Spawning worker 4 with 54 pkgs Spawning worker 5 with 54 pkgs Spawning worker 6 with 54 pkgs Spawning worker 7 with 54 pkgs Spawning worker 8 with 54 pkgs Spawning worker 9 with 54 pkgs Spawning worker 10 with 53 pkgs Spawning worker 11 with 53 pkgs Spawning worker 12 with 53 pkgs Spawning worker 13 with 53 pkgs Spawning worker 14 with 53 pkgs Spawning worker 15 with 53 pkgs Spawning worker 16 with 53 pkgs Spawning worker 17 with 53 pkgs Spawning worker 18 with 53 pkgs Spawning worker 19 with 53 pkgs Spawning worker 20 with 53 pkgs Spawning worker 21 with 53 pkgs Spawning worker 22 with 53 pkgs Spawning worker 23 with 53 pkgs Workers Finished Saving Primary metadata Saving file lists metadata Saving other metadata Generating sqlite DBs Traceback (most recent call last): File "/usr/share/createrepo/genpkgmetadata.py", line 308, in main(sys.argv[1:]) File "/usr/share/createrepo/genpkgmetadata.py", line 280, in main mdgen.doRepoMetadata() File "/usr/lib/python2.7/dist-packages/createrepo/__init__.py", line 999, in doRepoMetadata rp.getFilelists(complete_path, csum) File "/usr/lib/python2.7/dist-packages/sqlitecachec.py", line 55, in getFilelists self.repoid)) TypeError: Parsing filelists.xml error: Premature end of data in tag file line 247651 Problem fixes by installing libxml2=2.9.1+dfsg1 from debian sid. Comparing patchsets in debian package sources between 2.9.1+dfsg1 and 2.9.1+dfsg1-3ubuntu4.3 I see in debian package much more patches, I suppose one of them helps in my problem: 2.9.1+dfsg1-3ubuntu4.3: 0001-modify-xml2-config-and-pkgconfig-behaviour.patch 0002-Fix-an-error-in-xmlCleanupParser.patch 0003-Fix-missing-br
[Touch-packages] [Bug 1619987] Re: Cannot set custom sound for message notification
*** This bug is a duplicate of bug 1589229 *** https://bugs.launchpad.net/bugs/1589229 ** This bug has been marked a duplicate of bug 1589229 Custom sounds for incoming messages are not supported -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1619987 Title: Cannot set custom sound for message notification Status in messaging-app package in Ubuntu: New Bug description: On the E4.5 (OTA 12), I can set a custom ringtone, but not a message sound. I would like to set my own sound for incoming text messages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1619987/+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
Re: [Touch-packages] [Bug 1624553] [NEW] Panasonic CF-52 no sound built in speakers
Please run apport-collect 1624553 so we can get more information about your hardware. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1624553 Title: Panasonic CF-52 no sound built in speakers Status in alsa-driver package in Ubuntu: New Bug description: On a fresh updated install, there is no sound from built-in speakers. Headphone jack works. This bug is possibly similar to #632046. I have checked that the Fn-f4 has not muted the sound. alsamixer indicates that sound is not muted. I previously had kubuntu installed and sound worked for some time. Ubuntu release 16.04.1 LTS alsa-base version 1.0.25+dfsg-0ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1624553/+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 1620994] Re: [regression] Starting in Mesa 12.0.2, EGL clients crash with SIGSEGV in dri2_destroy_context() (from eglDestroyContext or eglTerminate)
This bug was fixed in the package mesa - 12.0.3-1ubuntu1 --- mesa (12.0.3-1ubuntu1) yakkety; urgency=medium * Merge from Debian. [ Christopher James Halse Rogers ] * egl-platform-mir.patch: Updated for upstream changes to dri2_initialize in egl_dri2.c. (LP: #1620934, #1620994) mesa (12.0.3-1) unstable; urgency=medium * New upstream release. * Enable vc4 on arm64. -- Timo Aaltonen Fri, 16 Sep 2016 10:07:05 +0300 ** Changed in: mesa (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1620994 Title: [regression] Starting in Mesa 12.0.2, EGL clients crash with SIGSEGV in dri2_destroy_context() (from eglDestroyContext or eglTerminate) Status in Canonical System Image: Confirmed Status in Mir: Invalid Status in mesa package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Invalid Bug description: Ubuntu 16.10 + proposed x86, nvidia 8600gt nouveau unity8-dash crashed with SIGSEGV in eglDestroyContext() ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: unity8 8.14+16.10.20160831.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.6.0-10.12-generic 4.6.5 Uname: Linux 4.6.0-10-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CrashCounter: 1 Date: Wed Sep 7 13:04:53 2016 ExecutablePath: /usr/bin/unity8-dash InstallationDate: Installed on 2016-06-05 (93 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcCmdline: unity8-dash --desktop_file_hint=/usr/share/applications/unity8-dash.desktop SegvAnalysis: Segfault happened at: 0x7fcab45aea3e:mov0x30(%rbp),%rax PC (0x7fcab45aea3e) ok source "0x30(%rbp)" (0x0030) not located in a known VMA region (needed readable region)! destination "%rax" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity8 StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 eglDestroyContext () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so QOpenGLContext::destroy() () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 Title: unity8-dash crashed with SIGSEGV in eglDestroyContext() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo upstart.unity8-dash.log: [2016-09-07:13:04:52.767] QEGLPlatformContext: eglMakeCurrent failed: 3001 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1620994/+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 1620934] Re: [regression] Starting in Mesa 12.0.2, Qt/QML apps don't render any more (logs say "QEGLPlatformContext: eglMakeCurrent failed: 3001")
This bug was fixed in the package mesa - 12.0.3-1ubuntu1 --- mesa (12.0.3-1ubuntu1) yakkety; urgency=medium * Merge from Debian. [ Christopher James Halse Rogers ] * egl-platform-mir.patch: Updated for upstream changes to dri2_initialize in egl_dri2.c. (LP: #1620934, #1620994) mesa (12.0.3-1) unstable; urgency=medium * New upstream release. * Enable vc4 on arm64. -- Timo Aaltonen Fri, 16 Sep 2016 10:07:05 +0300 ** Changed in: mesa (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1620934 Title: [regression] Starting in Mesa 12.0.2, Qt/QML apps don't render any more (logs say "QEGLPlatformContext: eglMakeCurrent failed: 3001") Status in Canonical System Image: Confirmed Status in Mir: Invalid Status in QtMir: Confirmed Status in qtubuntu: Confirmed Status in mesa package in Ubuntu: Fix Released Status in qtmir package in Ubuntu: Confirmed Status in qtubuntu package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Invalid Bug description: nothing works, all apps, dash are just black windows - Ubuntu 16.10 + proposed (x86, and using Nvidia 8600GT with nouveau drivers) and they fail with this error "QEGLPlatformContext: eglMakeCurrent failed: 3001" To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1620934/+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 1599952] Re: Blurred images with kernels after 4.2.x
Kernel 4.4.21 LTS The above-referenced kernel was released today. It may (might) resolve the regression I have experienced that keeps me from using Ubuntu 16.04.1 (believed to be an i915 driver issue). To find out I need to try the kernel in Ubuntu. If I install from an .iso (16.04.1) and select the option to check for updates while installing, will I end up with the new kernel installed? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1599952 Title: Blurred images with kernels after 4.2.x Status in xorg package in Ubuntu: Incomplete Bug description: Have used Ubuntu or its flavors for 3 years with no issues on this machine. Installed Ubuntu 16.04 64-bit lts, and successively xubuntu 16.04, ubuntuMATE 16.04, and lubuntu 16.04. Each installed, but with blurred images. --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: MATE DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family Integrated Graphics Controller [1043:844d] InstallationDate: Installed on 2016-07-10 (0 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: ASUSTeK Computer INC. CM6850 Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-30-generic root=UUID=30188e44-b1e6-4cdc-bd16-62f107d213a7 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-30.49-generic 4.4.13 Tags: xenial ubuntu Uname: Linux 4.4.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/21/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: CM6850 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1301:bd12/21/2011:svnASUSTeKComputerINC.:pnCM6850:pvrSystemVersion:rvnASUSTeKComputerINC.:rnCM6850:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: CM6850 dmi.product.version: System Version dmi.sys.vendor: ASUSTeK Computer INC. version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1599952/+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 1624320] Re: systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing entries
DNS resolution outside NSS shouldn’t be dismissed as an edge case for software that’s too conceited to use NSS. NSS only exposes A, , and PTR records. There’s plenty of software in the official archive that needs other records from DNS (off the top of my head: SRV, TXT, MX, SSHFP, AFSDB) and cannot get them from NSS. > resolved reads their DNS servers *from* resolv.conf. Right, so perhaps when resolvconf is in use, systemd-resolved should read those from /run/resolvconf/resolv.conf directly, and /etc/resolv.conf should be a symlink to /lib/systemd/resolv.conf rather than /run/resolvconf/resolv.conf? > you can't both chose to *not* use NSS *and* rely on NSS to do DNSSEC for you. Why not? It was working with NetworkManager managing a dnsmasq, since NetworkManager installed the local proxy as the only nameserver visible in resolv.conf, and it would work again if systemd-resolved did the same. This will also be needed to fix problems like https://github.com/systemd/systemd/issues/3421 for programs that cannot use NSS. ** Bug watch added: github.com/systemd/systemd/issues #3421 https://github.com/systemd/systemd/issues/3421 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1624320 Title: systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing entries Status in systemd package in Ubuntu: Triaged Bug description: systemd-resolved, or more precisely the hook script /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf, causes resolvconf to add 127.0.0.53 to the set of nameservers in /etc/resolv.conf alongside the other nameservers. That makes no sense because systemd-resolved sets up 127.0.0.53 as a proxy for those other nameservers. The effect is similar to bug 1624071 but for applications doing their own DNS lookups. It breaks any DNSSEC validation that systemd-resolved tries to do; applications will failover to the other nameservers, bypassing validation failures. And it makes failing queries take twice as long. /etc/resolv.conf should have only 127.0.0.53 when systemd-resolved is active. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624320/+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 1624560] [NEW] Use XCB 64-bit sequence API
Public bug reported: libx11 suffers from 32-bit sequence wraparound for programs that make a large number of calls to the server. (See: https://lists.x.org/archives /xorg-devel/2013-October/038370.html ) The Freedesktop bug is here: https://bugs.freedesktop.org/show_bug.cgi?id=71338 This was fixed with this commit: https://cgit.freedesktop.org/xorg/lib/libX11/commit/?id=a72d2d06c002b644b7040a0a9936c8525e092ba8 This fix requires libxcb >= 1.11.1 for the 64-bit sequence API. Xenial and higher ship libxcb 1.11.1. Can this patch be pulled into the Ubuntu package? ** Affects: libx11 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1624560 Title: Use XCB 64-bit sequence API Status in libx11 package in Ubuntu: New Bug description: libx11 suffers from 32-bit sequence wraparound for programs that make a large number of calls to the server. (See: https://lists.x.org/archives/xorg-devel/2013-October/038370.html ) The Freedesktop bug is here: https://bugs.freedesktop.org/show_bug.cgi?id=71338 This was fixed with this commit: https://cgit.freedesktop.org/xorg/lib/libX11/commit/?id=a72d2d06c002b644b7040a0a9936c8525e092ba8 This fix requires libxcb >= 1.11.1 for the 64-bit sequence API. Xenial and higher ship libxcb 1.11.1. Can this patch be pulled into the Ubuntu package? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1624560/+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 1624553] [NEW] Panasonic CF-52 no sound built in speakers
Public bug reported: On a fresh updated install, there is no sound from built-in speakers. Headphone jack works. This bug is possibly similar to #632046. I have checked that the Fn-f4 has not muted the sound. alsamixer indicates that sound is not muted. I previously had kubuntu installed and sound worked for some time. Ubuntu release 16.04.1 LTS alsa-base version 1.0.25+dfsg-0ubuntu5 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1624553 Title: Panasonic CF-52 no sound built in speakers Status in alsa-driver package in Ubuntu: New Bug description: On a fresh updated install, there is no sound from built-in speakers. Headphone jack works. This bug is possibly similar to #632046. I have checked that the Fn-f4 has not muted the sound. alsamixer indicates that sound is not muted. I previously had kubuntu installed and sound worked for some time. Ubuntu release 16.04.1 LTS alsa-base version 1.0.25+dfsg-0ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1624553/+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 1532899] Re: Group chat sometimes misses messages with Unknown Number Message not found
** Changed in: canonical-devices-system-image Status: In Progress => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1532899 Title: Group chat sometimes misses messages with Unknown Number Message not found Status in Canonical System Image: Confirmed Status in messaging-app package in Ubuntu: Invalid Status in nuntium package in Ubuntu: Confirmed Status in ubuntu-download-manager package in Ubuntu: Confirmed Bug description: This happened the last two times I received group chat messages. Several messages were not listed in the chat but rather under an Unknown Number contact with content Message no found. I see 4 such entries for the time covered in the log files. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1532899/+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 1531925] Re: Can't connect Logitech K830 - no PIN prompt [LE]
** Changed in: canonical-devices-system-image Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1531925 Title: Can't connect Logitech K830 - no PIN prompt [LE] Status in Canonical System Image: Fix Committed Status in bluez package in Ubuntu: In Progress Status in ubuntu-system-settings package in Ubuntu: Confirmed Bug description: Cannot connect a Logitech Illuminated Living Room keyboard to a device running bluez5. There are two versions of the keyboard, a unifying receiver version, and a Bluetooth version. The latter has a BT symbol on the 'del' key. To put the BT version in pairing mode, power on the keyboard, then briefly hold the FN and 'del' key together and release. A green LED at the top right of the keyboard should start flashing quickly. Once in pairing mode, the device will become visible on desktop using the BT settings UI, however it's *never* shown in the UI on a device running the latest Touch ( OTA9.1+ ). Note, this includes devices running a silo version of bluez 5.37, including both arale and krillin. On both devices, the keyboard *is* viewable using bluetoothctl. It should be noted that LE keyboard support on touch should be a considered a missing feature. Here's the reported attributes of the device from my macair running 15.10 + bluez 5.37: Device DF:08:A9:A0:13:93 Name: K830 Alias: K830 Appearance: 0x03c1 Icon: input-keyboard Paired: yes Trusted: no Blocked: no Connected: yes LegacyPairing: no UUID: Generic Access Profile (1800--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: Device Information (180a--1000-8000-00805f9b34fb) UUID: Battery Service (180f--1000-8000-00805f9b34fb) UUID: Human Interface Device (1812--1000-8000-00805f9b34fb) UUID: Vendor specific (0001--1000-8000-011f246d) Modalias: usb:v046DpB335d0010 From bluetoothctl on both my laptop and my desktop, I'm able to pair, trust and connect the device, and info reflects these changes, however the device never actually connects, it's LED remains blinking fast, and the keyboard cannot be used. Note, before pairing, I issued the command 'agent KeyboardOnly' and 'default-agent'. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1531925/+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 1541609] Re: Process got into a state where no downloads occur
new panel seems to have fixed this for me ** Changed in: canonical-devices-system-image Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-download-manager in Ubuntu. https://bugs.launchpad.net/bugs/1541609 Title: Process got into a state where no downloads occur Status in Canonical System Image: Fix Committed Status in ubuntu-download-manager package in Ubuntu: In Progress Status in ubuntu-system-settings package in Ubuntu: In Progress Bug description: Went to settings > Updates and asked to Install all updates, there were 3 apps available Left the panel Cam back some mins later, the first app had finished and was gone from the list. The next two were there in a new state Asked to instal the first app , progress bar appeared but nothing happened. From the attached u-d-m log I see it attempted the download but then just exited after the timer fired. Then tried to download a new app from the store. The UI changed to show it should install but no progress changes. In this case I did not see a new log created. Going back into the updates panel I see log files being created each time without issuing a new request. Arale on rc-proposed Was on cellular data at the time, wifi was off To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1541609/+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 1603157] Re: closing a tab while browsing results in closing browsing completely
I have had to unbox my BQM10 tablet (OTA12) again, as my iPad has failed. I (can) only use it for web browsing, and the almost continuous crashing of the browser is very irritating. I can induce it by closing the last tab 3 times out of 5, and by closing the 2nd of 3 almost every time. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1603157 Title: closing a tab while browsing results in closing browsing completely Status in Canonical System Image: Incomplete Status in webbrowser-app package in Ubuntu: Confirmed Bug description: When you are browsing on the internet ( using native browser ) and you have multiple tabs open... then close 1 tab... then the browser closes completely. You have to start up internet again. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1603157/+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 1595348] Re: Web browser dissapears too often
I have had to unbox my BQM10 tablet (OTA12) again, as my iPad has failed. I (can) only use it for web browsing, and the almost continuous crashing of the browser is very irritating. I can induce it by - switching tabs - double clicking on text to copy it (especially if it seems not to select a word and I do it again) - zooming in with the scroll wheel - trying to copy an url from the address bar -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1595348 Title: Web browser dissapears too often Status in Canonical System Image: New Status in webbrowser-app package in Ubuntu: Confirmed Bug description: M10 tablet.. Ever since upgrading to OTA11 the web browser has become very annoying. If I have, say, 3 tabs on and close one, the browser often dissapears.. I restart it from the apps page and it restarts with all the original tabs, including thecone I tried to close.. I can then closecit again, usually without furthervincident. Or I might open the bookmarks and try to open a new tab, and the browser vanishes. Or, very occasionally I click on a search engine result and 'poof' she is gone! Anyone care to nominate a suitable log file? To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1595348/+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 1398008] Re: "Caps. Lock" LED keyboard indicator not working
Still happens in Unity 14.04 & 16.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1398008 Title: "Caps. Lock" LED keyboard indicator not working Status in xorg package in Ubuntu: Expired Bug description: Ubuntu Trusty running on an Apple MacBook 4,1 (white, early 2008) Linux 3.13.0-40-generic #69-Ubuntu SMP Thu Nov 13 17:53:56 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux "Caps. Lock" keyboard LED indicator remains always off even if the lock its activated and working properly when writing. This issue doesn't happens when in the session log screen. There it always works fine. Issue starts when loggin into my session account. I've 2 GB RAM, 4 GB SWAP space, /home and SWAP are encrypted. Please let me know if you ned further information. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Dec 1 08:58:24 2014 DistUpgraded: 2014-08-12 15:32:20,840 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DpkgLog: EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device [106b:00a1] Subsystem: Apple Inc. Device [106b:00a1] InstallationDate: Installed on 2014-08-12 (110 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MachineType: Apple Inc. MacBook4,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-generic root=UUID=bed91342-3e5e-483d-af89-b95cc986250e ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-08-12 (110 days ago) dmi.bios.date: 02/09/08 dmi.bios.vendor: Apple Inc. dmi.bios.version: MB41.88Z.00C1.B00.0802091535 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F22788A9 dmi.board.vendor: Apple Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 2 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F22788A9 dmi.modalias: dmi:bvnAppleInc.:bvrMB41.88Z.00C1.B00.0802091535:bd02/09/08:svnAppleInc.:pnMacBook4,1:pvr1.0:rvnAppleInc.:rnMac-F22788A9:rvrPVT:cvnAppleInc.:ct2:cvrMac-F22788A9: dmi.product.name: MacBook4,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon Dec 1 08:25:50 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 40031 vendor APP xserver.version: 2:1.15.1-0ubuntu2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1398008/+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 1590776] Re: hide selection handle when start typing
** Changed in: canonical-devices-system-image Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1590776 Title: hide selection handle when start typing Status in Canonical System Image: Fix Committed Status in Oxide: Fix Released Status in Oxide 1.15 series: Fix Released Status in Oxide 1.16 series: Fix Released Status in webbrowser-app package in Ubuntu: Invalid Bug description: we are showing the selection handle (in addition to the cursor) whenever entering a text field that already has text in it. For example, if you are replying to a Gmail message, you have an annoying blue selection handle blinking where you are trying to type and you can't turn it off. Or on a form, focusing on a field to append text will also show the selection handle. Or a multi line text area, adding a new line and typing at the beginning. Tested Chrome on Android and it behaves differently, and think we should do similar: 1. Show the selection handle initially, but have it disappear when you press any key (space, character, etc.) 2. Tapping anywhere in the field will cause handle to be shown again 3. Also, can we put the selection handle on the bottom of the cursor instead of the top? This is the behavior on Chrome for Android and the rest of our non-html platform in Ubuntu touch. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590776/+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 1590804] Re: fontconfig initialization spends most of its time parsing XML configuration files in /etc/fonts/conf.d/
** Changed in: canonical-devices-system-image Importance: High => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1590804 Title: fontconfig initialization spends most of its time parsing XML configuration files in /etc/fonts/conf.d/ Status in Canonical System Image: In Progress Status in fontconfig package in Ubuntu: Confirmed Status in qtbase-opensource-src package in Ubuntu: Invalid Bug description: While profiling the startup of QML apps on the BQ E4.5 phone (armhf) I noticed that a significant amount of time (around 35ms) was spent solely on parsing the XML configuration files in /etc/fonts/conf.d/ There seems to be around 40 files on Ubuntu Phone in that directory. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1590804/+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 1594944] Re: Setup.exec() for existing account type results in blank full screen window
Any update on this issue? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-system-settings- online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1594944 Title: Setup.exec() for existing account type results in blank full screen window Status in Canonical System Image: In Progress Status in webapps-sprint: In Progress Status in ubuntu-system-settings-online-accounts package in Ubuntu: Incomplete Bug description: If an account already exists, calling Setup.exec() again results in a blank window being overlaid on top of the application which made the request. There is no way to close this window. This API is what the online accounts integration in the scopes API relies upon, to allow logging in to accounts, and so we have come to rely upon this API as well in multiple places, as a means to log into the Ubuntu One account, when it is necessary to do so. However, due to this issue, the only way to reliably present a login window at an appropriate time, is to delete the account when it appears to have been invalidated by the server, and to then present the login window to create a new account. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1594944/+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 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
3421 seems like the opposite of this problem. There, queries that belong on the local network instead go to the domain-limited VPN servers. Here, queries that should go to the VPN servers (which in my case are not domain-limited) instead go to the local servers. Also, here I am using NetworkManager, not systemd-networkd. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS Status in systemd: Unknown Status in systemd package in Ubuntu: Incomplete Bug description: I use a VPN configured with network-manager-openconnect-gnome in which a split-horizon DNS setup assigns different addresses to some names inside the remote network than the addresses seen for those names from outside the remote network. However, systemd-resolved often decides to ignore the VPN’s DNS servers and use the local network’s DNS servers to resolve names (whether in the remote domain or not), breaking the split-horizon DNS. This related bug, reported by Lennart Poettering himself, was closed with the current Fedora release at the time reaching EOL: https://bugzilla.redhat.com/show_bug.cgi?id=1151544 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+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 1575744] Re: network disk cache does not take into account the HTTP Vary header
mark fixed with workaround but leave the real qt fix task open ** Changed in: canonical-devices-system-image Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1575744 Title: network disk cache does not take into account the HTTP Vary header Status in Canonical System Image: Fix Committed Status in qtbase-opensource-src package in Ubuntu: Confirmed Status in unity-scope-click package in Ubuntu: Fix Released Bug description: Switching from English to Polish works as expected But then going back to English leaves me with store in Polish This survives reboots. Steps to reproduce: 1. Go to Ubuntu Store scope (with your current language). 2. Go to phone settings, change the language, accept & reboot the phone. 3. Go to Ubuntu Store scope. Note how scope title and some strings such as "installed" changed for the new language (since these are provided locally by the scope for current LANG), but strings such as 'Highlight of the week' or departments names (hit the search lens icon to reveal departments) which come from the store still use the old language. See upstream bug at https://bugreports.qt.io/browse/QTBUG-14750 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1575744/+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 1620553] Re: OSK becomes unusable as taps are delayed by 1-2 seconds and vibration doesn't occur any more (although gestures continue to work)
** Changed in: usensord (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: canonical-devices-system-image
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to platform-api in Ubuntu.
https://bugs.launchpad.net/bugs/1620553
Title:
OSK becomes unusable as taps are delayed by 1-2 seconds and vibration
doesn't occur any more (although gestures continue to work)
Status in Canonical System Image:
Fix Committed
Status in platform-api package in Ubuntu:
In Progress
Status in usensord package in Ubuntu:
Fix Committed
Bug description:
Krillin, rc-proposed/bq_aquaris.en r422
TEST CASE:
1. Create to alarms that'll trigger at the same time
2. Wait until they go off
3. Dismiss the alarms
4. Verify that there is still haptic feedback and OSK is still responsive
ACTUAL RESULT
Step 4 fails.
UPDATE: see comment #5, it turns out it's the haptics plugin doing SYNC dbus
calls and blocking the UI thread when the dbus service does not reply or the
replies come with a big delay
Description:
All at once taps have become incredibly delayed, by 1 or 2 secs.
Gestures still work ok, no delay there.
Swiping the greeter -> no delay. Tapping numbers to input code on the greeter
--> 2 secs delay. Even though both are parts of unity8. So it doesn't seem to
only be a problem of unity8 clients, but also unity8 itself.
I have no idea why horizontal/vertical swipes would be unaffected, though.
The virtual keyboard is also completely unusable because of the huge
delay that each tap has.
Also noticed that the vibration is gone, taps don't trigger vibration
anymore.
Webview also seemed to be unaffected by the delays (although I'm not
entirely sure, the bug is now gone)
I also restarted unity8 and unity8-dash with Mir input logging enabled. That
showed that the touch events were being delivered as expected, no delay.
restart unity8 MIR_CLIENT_INPUT_RECEIVER_REPORT=log and
restart unity8-dash MIR_CLIENT_INPUT_RECEIVER_REPORT=log
Restarting lightdm (that forces the restart of unity-system-
compositor) fixed the issue.
Additional info: I had Mir touchspots visualization enabled, which are
known to cause more stuttering, but I think they're unlikely to be the
cause of this bug, I had them enabled for 2 weeks and haven't noticed
any problem like this before.
This is the log from a tap on an icon in the shell:
[2016-09-06 10:52:51.876400] input-receiver: Received
event:touch_event(when=54593678129000 (6.030520ms ago), from=3, touch = {{id=0,
action=down, tool=finger, x=426.211, y=292.695, pressure=0.85098, major=19.963,
minor=0, size=19.963}, modifiers=1)
[2016-09-06 10:52:51.953821] input-receiver: Received
event:touch_event(when=54593751953000 (9.709366ms ago), from=3, touch = {{id=0,
action=change, tool=finger, x=426.211, y=292.695, pressure=0.843137,
major=19.963, minor=0, size=19.963}, modifiers=1)
[2016-09-06 10:52:51.954343] input-receiver: Received
event:touch_event(when=54593761256000 (0.958751ms ago), from=3, touch = {{id=0,
action=up, tool=finger, x=426.211, y=292.695, pressure=0.843137, major=19.963,
minor=0, size=19.963}, modifiers=1)
SEE VIDEO ATTACHMENT BELOW
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1620553/+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 1342031] Re: Rename QML modules to follow qml-module-foo naming
This bug was fixed in the package address-book-app -
0.2+16.10.20160913-0ubuntu1
---
address-book-app (0.2+16.10.20160913-0ubuntu1) yakkety; urgency=medium
* handle rename of qtdeclarative5-ofono0.2 to qml-module-ofono (LP:
#1342031)
-- Ken VanDine Tue, 13 Sep 2016 13:14:48
+
** Changed in: address-book-app (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to content-hub in Ubuntu.
Matching subscriptions: touch
https://bugs.launchpad.net/bugs/1342031
Title:
Rename QML modules to follow qml-module-foo naming
Status in accounts-qml-module package in Ubuntu:
Fix Released
Status in address-book-app package in Ubuntu:
Fix Released
Status in bacon2d package in Ubuntu:
Triaged
Status in clickmanager-plugin package in Ubuntu:
New
Status in content-hub package in Ubuntu:
New
Status in cordova-ubuntu package in Ubuntu:
New
Status in dee-qt package in Ubuntu:
New
Status in gsettings-qt package in Ubuntu:
New
Status in history-service package in Ubuntu:
New
Status in libhud-qt package in Ubuntu:
Won't Fix
Status in libqofono package in Ubuntu:
Fix Released
Status in libusermetrics package in Ubuntu:
New
Status in mediascanner2 package in Ubuntu:
Fix Released
Status in oxide-qt package in Ubuntu:
New
Status in poppler-qml-plugin package in Ubuntu:
New
Status in qml-box2d package in Ubuntu:
New
Status in qml-friends package in Ubuntu:
New
Status in qt3d-opensource-src package in Ubuntu:
Fix Released
Status in qtconnectivity-opensource-src package in Ubuntu:
Fix Released
Status in qtdeclarative-opensource-src package in Ubuntu:
Fix Released
Status in qtfeedback-opensource-src package in Ubuntu:
Fix Released
Status in qtgrilo package in Ubuntu:
New
Status in qtlocation-opensource-src package in Ubuntu:
Fix Released
Status in qtmultimedia-opensource-src package in Ubuntu:
Fix Released
Status in qtpim-opensource-src package in Ubuntu:
Fix Released
Status in qtquickcontrols-opensource-src package in Ubuntu:
Fix Released
Status in qtsensors-opensource-src package in Ubuntu:
Fix Released
Status in qtsystems-opensource-src package in Ubuntu:
Fix Released
Status in reminders-app package in Ubuntu:
New
Status in solid package in Ubuntu:
New
Status in sync-monitor package in Ubuntu:
New
Status in telephony-service package in Ubuntu:
Triaged
Status in thumbnailer package in Ubuntu:
Fix Released
Status in u1db-qt package in Ubuntu:
Confirmed
Status in ubuntu-download-manager package in Ubuntu:
Triaged
Status in ubuntu-keyboard package in Ubuntu:
New
Status in ubuntu-settings-components package in Ubuntu:
In Progress
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
Fix Released
Status in ubuntu-ui-extras package in Ubuntu:
New
Status in ubuntu-ui-toolkit package in Ubuntu:
Fix Released
Status in ubuntuone-credentials package in Ubuntu:
Fix Released
Status in unity-action-api package in Ubuntu:
Triaged
Status in unity-notifications package in Ubuntu:
New
Status in webbrowser-app package in Ubuntu:
Fix Released
Status in ubuntu-ui-toolkit package in Ubuntu RTM:
Fix Released
Bug description:
UPDATE: This would be a nice to have for Ubuntu 16.04 LTS, since
otherwise we will need to keep the transitional packages until 2018.
===
The package names of QML modules should be of the format qml-
module-{$modulename}[version], a transition that was started during Qt
5.3 preparation in Ubuntu. For example this could be qml-module-
qtquick-localstorage or qml-module-qtsysteminfo for non versioned
modules, and qml-module-ubuntu-webthing0.3 for versioned/co-
installable modules.
Further details in Debian e-mail:
http://lists.alioth.debian.org/pipermail/pkg-kde-
talk/2014-March/001889.html
For Ubuntu, transitional packages should be put in place for smooth
distribution upgrades, since we're shipping with the old names in previous
Ubuntus. An example of that is at
http://bazaar.launchpad.net/~kubuntu-packagers/kubuntu-packaging/qtsystems-opensource-src/revision/31
- in other words:
- Make the old package a transitional oldlibs package that depends on the new
package
- Add Breaks/Replaces to the new package for the old non-transitional
packages (be careful about the version number specification)
- Keep Multi-Arch: same and Architecture: any for the transitional package
- Write "QML module" instead of "QML plugin"
- Rename also the *.install files
---
One more example on naming:
For example, the "test" (qtdeclarative5-test-plugin) in the old
qtdeclarative5-style package naming became "qttest" (qml-module-
qttest) in the new naming since the path is actually under
/usr/lib/*/qt5/qml/QtTest/
qml-module-qtquick-xmllistmodel has path
/usr/lib/*/qt5/qml/QtQuick/XmlListModel, as an example if you have
more than one subdir. /usr/lib/*/qt5/qm
[Touch-packages] [Bug 1342031] Re: Rename QML modules to follow qml-module-foo naming
This bug was fixed in the package libqofono -
0.90+16.10.20160901-0ubuntu1
---
libqofono (0.90+16.10.20160901-0ubuntu1) yakkety; urgency=medium
* New upstream release
* debian/control
- Dropped recommends for ofono to a suggests
- Renamed QML module to follow qml-module-ofono naming (LP: #1342031)
-- Ken VanDine Thu, 01 Sep 2016 14:59:50
+
** Changed in: libqofono (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to content-hub in Ubuntu.
Matching subscriptions: touch
https://bugs.launchpad.net/bugs/1342031
Title:
Rename QML modules to follow qml-module-foo naming
Status in accounts-qml-module package in Ubuntu:
Fix Released
Status in address-book-app package in Ubuntu:
New
Status in bacon2d package in Ubuntu:
Triaged
Status in clickmanager-plugin package in Ubuntu:
New
Status in content-hub package in Ubuntu:
New
Status in cordova-ubuntu package in Ubuntu:
New
Status in dee-qt package in Ubuntu:
New
Status in gsettings-qt package in Ubuntu:
New
Status in history-service package in Ubuntu:
New
Status in libhud-qt package in Ubuntu:
Won't Fix
Status in libqofono package in Ubuntu:
Fix Released
Status in libusermetrics package in Ubuntu:
New
Status in mediascanner2 package in Ubuntu:
Fix Released
Status in oxide-qt package in Ubuntu:
New
Status in poppler-qml-plugin package in Ubuntu:
New
Status in qml-box2d package in Ubuntu:
New
Status in qml-friends package in Ubuntu:
New
Status in qt3d-opensource-src package in Ubuntu:
Fix Released
Status in qtconnectivity-opensource-src package in Ubuntu:
Fix Released
Status in qtdeclarative-opensource-src package in Ubuntu:
Fix Released
Status in qtfeedback-opensource-src package in Ubuntu:
Fix Released
Status in qtgrilo package in Ubuntu:
New
Status in qtlocation-opensource-src package in Ubuntu:
Fix Released
Status in qtmultimedia-opensource-src package in Ubuntu:
Fix Released
Status in qtpim-opensource-src package in Ubuntu:
Fix Released
Status in qtquickcontrols-opensource-src package in Ubuntu:
Fix Released
Status in qtsensors-opensource-src package in Ubuntu:
Fix Released
Status in qtsystems-opensource-src package in Ubuntu:
Fix Released
Status in reminders-app package in Ubuntu:
New
Status in solid package in Ubuntu:
New
Status in sync-monitor package in Ubuntu:
New
Status in telephony-service package in Ubuntu:
Triaged
Status in thumbnailer package in Ubuntu:
Fix Released
Status in u1db-qt package in Ubuntu:
Confirmed
Status in ubuntu-download-manager package in Ubuntu:
Triaged
Status in ubuntu-keyboard package in Ubuntu:
New
Status in ubuntu-settings-components package in Ubuntu:
In Progress
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
Fix Released
Status in ubuntu-ui-extras package in Ubuntu:
New
Status in ubuntu-ui-toolkit package in Ubuntu:
Fix Released
Status in ubuntuone-credentials package in Ubuntu:
Fix Released
Status in unity-action-api package in Ubuntu:
Triaged
Status in unity-notifications package in Ubuntu:
New
Status in webbrowser-app package in Ubuntu:
Fix Released
Status in ubuntu-ui-toolkit package in Ubuntu RTM:
Fix Released
Bug description:
UPDATE: This would be a nice to have for Ubuntu 16.04 LTS, since
otherwise we will need to keep the transitional packages until 2018.
===
The package names of QML modules should be of the format qml-
module-{$modulename}[version], a transition that was started during Qt
5.3 preparation in Ubuntu. For example this could be qml-module-
qtquick-localstorage or qml-module-qtsysteminfo for non versioned
modules, and qml-module-ubuntu-webthing0.3 for versioned/co-
installable modules.
Further details in Debian e-mail:
http://lists.alioth.debian.org/pipermail/pkg-kde-
talk/2014-March/001889.html
For Ubuntu, transitional packages should be put in place for smooth
distribution upgrades, since we're shipping with the old names in previous
Ubuntus. An example of that is at
http://bazaar.launchpad.net/~kubuntu-packagers/kubuntu-packaging/qtsystems-opensource-src/revision/31
- in other words:
- Make the old package a transitional oldlibs package that depends on the new
package
- Add Breaks/Replaces to the new package for the old non-transitional
packages (be careful about the version number specification)
- Keep Multi-Arch: same and Architecture: any for the transitional package
- Write "QML module" instead of "QML plugin"
- Rename also the *.install files
---
One more example on naming:
For example, the "test" (qtdeclarative5-test-plugin) in the old
qtdeclarative5-style package naming became "qttest" (qml-module-
qttest) in the new naming since the path is actually under
/usr/lib/*/qt5/qml/QtTest/
qml-module-qtquick-xmllistmodel has path
/usr/lib/*/qt5/qml/QtQuick/XmlListModel, as an exampl
[Touch-packages] [Bug 1592817] Re: gdebi-gtk crashed with ValueError in update_interface(): could not convert string to float: '0, 0000'
The traceback actually seems to be in python-apt. File "/usr/lib/python3/dist-packages/apt/progress/base.py", line 255, in update_interface if float(percent) != self.percent or status_str != self.status: ValueError: could not convert string to float: '0,' ** Information type changed from Private to Public ** Also affects: python-apt (Ubuntu) Importance: Undecided Status: New ** Changed in: python-apt (Ubuntu) Importance: Undecided => High ** Changed in: python-apt (Ubuntu) Status: New => Triaged ** Tags added: rls-y-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1592817 Title: gdebi-gtk crashed with ValueError in update_interface(): could not convert string to float: '0,' Status in gdebi package in Ubuntu: Confirmed Status in python-apt package in Ubuntu: Triaged Bug description: Gdebi chrahed while installing Google Chrome .deb-fil bur the error didn't appear until I logged out and back in again ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: gdebi 0.9.5.7ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-25.44-generic 4.4.13 Uname: Linux 4.4.0-25-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu4 Architecture: amd64 Date: Wed Jun 15 15:01:11 2016 ExecutablePath: /usr/share/gdebi/gdebi-gtk InstallationDate: Installed on 2016-06-15 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160511) InterpreterPath: /usr/bin/python3.5 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/gdebi-gtk --non-interactive /media/jimmy/Seagate\ Backup\ Plus\ Drive/Browser/google-chrome-stable_51.0.2704.79-1_amd64.deb ProcEnviron: PATH=(custom, no user) LANG=da_DK.UTF-8 LANGUAGE=da SHELL=/bin/bash TERM=unknown PythonArgs: ['/usr/bin/gdebi-gtk', '--non-interactive', '/media/jimmy/Seagate Backup Plus Drive/Browser/google-chrome-stable_51.0.2704.79-1_amd64.deb'] SourcePackage: gdebi Title: gdebi-gtk crashed with ValueError in update_interface(): could not convert string to float: '0,' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1592817/+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 1537484] Re: package zlib1g-dev 1:1.2.8.dfsg-2ubuntu4 failed to install/upgrade: försöker skriva över "/usr/include/i386-linux-gnu/zconf.h" som också finns i paketet lib32z1-dev
*** This bug is a duplicate of bug 1512992 *** https://bugs.launchpad.net/bugs/1512992 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1512992, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1512992 package zlib1g-dev 1:1.2.8.dfsg-2ubuntu4 failed to install/upgrade: trying to overwrite '/usr/include/i386-linux-gnu/zconf.h', which is also in package lib32z1-dev 1:1.2.8.dfsg-2ubuntu4 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1537484 Title: package zlib1g-dev 1:1.2.8.dfsg-2ubuntu4 failed to install/upgrade: försöker skriva över "/usr/include/i386-linux-gnu/zconf.h" som också finns i paketet lib32z1-dev 1:1.2.8.dfsg-2ubuntu4 Status in zlib package in Ubuntu: New Bug description: I don't know how it happened as I left the computer running during the night. ProblemType: Package DistroRelease: Ubuntu 15.10 Package: zlib1g-dev 1:1.2.8.dfsg-2ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6 Uname: Linux 4.2.0-25-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 Date: Sun Jan 24 04:08:47 2016 DuplicateSignature: package:zlib1g-dev:1:1.2.8.dfsg-2ubuntu4:försöker skriva över "/usr/include/i386-linux-gnu/zconf.h" som också finns i paketet lib32z1-dev 1:1.2.8.dfsg-2ubuntu4 ErrorMessage: försöker skriva över "/usr/include/i386-linux-gnu/zconf.h" som också finns i paketet lib32z1-dev 1:1.2.8.dfsg-2ubuntu4 InstallationDate: Installed on 2016-01-18 (5 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.2ubuntu5.1 apt 1.0.10.2ubuntu1 SourcePackage: zlib Title: package zlib1g-dev 1:1.2.8.dfsg-2ubuntu4 failed to install/upgrade: försöker skriva över "/usr/include/i386-linux-gnu/zconf.h" som också finns i paketet lib32z1-dev 1:1.2.8.dfsg-2ubuntu4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/1537484/+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 1573955] Re: package lib32z1-dev (not installed) failed to install/upgrade: tentative de remplacement de « /usr/include/i386-linux-gnu/zconf.h », qui appartient aussi au paquet z
*** This bug is a duplicate of bug 1512992 *** https://bugs.launchpad.net/bugs/1512992 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1512992, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1512992 package zlib1g-dev 1:1.2.8.dfsg-2ubuntu4 failed to install/upgrade: trying to overwrite '/usr/include/i386-linux-gnu/zconf.h', which is also in package lib32z1-dev 1:1.2.8.dfsg-2ubuntu4 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1573955 Title: package lib32z1-dev (not installed) failed to install/upgrade: tentative de remplacement de « /usr/include/i386-linux-gnu/zconf.h », qui appartient aussi au paquet zlib1g-dev:i386 1:1.2.8.dfsg-2ubuntu4 Status in zlib package in Ubuntu: New Bug description: I am trying to install package for building Cyanogenmod CM10.1 for Galaxy Tab (following tutorial: http://wiki.cyanogenmod.org/w/Build_for_p5110). I am on the way to port Ubuntu Touch to this Tab and wanted to start with a CM build. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: lib32z1-dev (not installed) ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sat Apr 23 11:45:09 2016 ErrorMessage: tentative de remplacement de « /usr/include/i386-linux-gnu/zconf.h », qui appartient aussi au paquet zlib1g-dev:i386 1:1.2.8.dfsg-2ubuntu4 InstallationDate: Installed on 2016-04-22 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: zlib Title: package lib32z1-dev (not installed) failed to install/upgrade: tentative de remplacement de « /usr/include/i386-linux-gnu/zconf.h », qui appartient aussi au paquet zlib1g-dev:i386 1:1.2.8.dfsg-2ubuntu4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/1573955/+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 1620447] Re: package zlib1g-dev 1:1.2.8.dfsg-2ubuntu4 failed to install/upgrade: trying to overwrite '/usr/include/i386-linux-gnu/zconf.h', which is also in package lib32z1-dev 1
*** This bug is a duplicate of bug 1512992 *** https://bugs.launchpad.net/bugs/1512992 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1512992, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1512992 package zlib1g-dev 1:1.2.8.dfsg-2ubuntu4 failed to install/upgrade: trying to overwrite '/usr/include/i386-linux-gnu/zconf.h', which is also in package lib32z1-dev 1:1.2.8.dfsg-2ubuntu4 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1620447 Title: package zlib1g-dev 1:1.2.8.dfsg-2ubuntu4 failed to install/upgrade: trying to overwrite '/usr/include/i386-linux-gnu/zconf.h', which is also in package lib32z1-dev 1:1.2.8.dfsg-2ubuntu4 Status in zlib package in Ubuntu: New Bug description: classic package conflict on provided files ProblemType: Package DistroRelease: Ubuntu 16.04 Package: zlib1g-dev 1:1.2.8.dfsg-2ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Tue Sep 6 11:38:27 2016 DuplicateSignature: package:zlib1g-dev:1:1.2.8.dfsg-2ubuntu4 Unpacking zlib1g-dev:i386 (1:1.2.8.dfsg-2ubuntu4) over (1:1.2.8.dfsg-2ubuntu4) ... dpkg: error processing archive /var/cache/apt/archives/zlib1g-dev_1%3a1.2.8.dfsg-2ubuntu4_i386.deb (--unpack): trying to overwrite '/usr/include/i386-linux-gnu/zconf.h', which is also in package lib32z1-dev 1:1.2.8.dfsg-2ubuntu4 ErrorMessage: trying to overwrite '/usr/include/i386-linux-gnu/zconf.h', which is also in package lib32z1-dev 1:1.2.8.dfsg-2ubuntu4 InstallationDate: Installed on 2016-08-27 (9 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: zlib Title: package zlib1g-dev 1:1.2.8.dfsg-2ubuntu4 failed to install/upgrade: trying to overwrite '/usr/include/i386-linux-gnu/zconf.h', which is also in package lib32z1-dev 1:1.2.8.dfsg-2ubuntu4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/1620447/+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 1617844] Re: package lib32z1-dev (not installed) failed to install/upgrade: trying to overwrite '/usr/include/i386-linux-gnu/zconf.h', which is also in package zlib1g-dev:i386 1:
*** This bug is a duplicate of bug 1512992 *** https://bugs.launchpad.net/bugs/1512992 Thanks for taking your time to report this issue and help making Ubuntu better. Yes, as you mention, this is a duplicate of bug 1512992, so I have marked it as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. ** This bug has been marked a duplicate of bug 1512992 package zlib1g-dev 1:1.2.8.dfsg-2ubuntu4 failed to install/upgrade: trying to overwrite '/usr/include/i386-linux-gnu/zconf.h', which is also in package lib32z1-dev 1:1.2.8.dfsg-2ubuntu4 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1617844 Title: package lib32z1-dev (not installed) failed to install/upgrade: trying to overwrite '/usr/include/i386-linux-gnu/zconf.h', which is also in package zlib1g-dev:i386 1:1.2.8.dfsg-2ubuntu4 - FRESH install Status in zlib package in Ubuntu: New Bug description: i am installing this (lib32z1-dev_1%3a1.2.8.dfsg-2ubuntu4_amd64.deb) for Android Build Environment on a Fresh Xubuntu (Xenial Xerus from 16.04.1 image) either zlib or lib32z-dev needs to be fixed, or BOTH: each package should check first if /usr/include/i386-linux-gnu/zconf.h is already provided by another package and work around it Thanks! P.S. this seems to be a duplicate / mirror-image / reverse bug of: https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/1512992 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: lib32z1-dev (not installed) ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Mon Aug 29 08:28:26 2016 DuplicateSignature: package:lib32z1-dev:(not installed) Unpacking lib32z1-dev (1:1.2.8.dfsg-2ubuntu4) ... dpkg: error processing archive /var/cache/apt/archives/lib32z1-dev_1%3a1.2.8.dfsg-2ubuntu4_amd64.deb (--unpack): trying to overwrite '/usr/include/i386-linux-gnu/zconf.h', which is also in package zlib1g-dev:i386 1:1.2.8.dfsg-2ubuntu4 ErrorMessage: trying to overwrite '/usr/include/i386-linux-gnu/zconf.h', which is also in package zlib1g-dev:i386 1:1.2.8.dfsg-2ubuntu4 InstallationDate: Installed on 2016-08-27 (1 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: zlib Title: package lib32z1-dev (not installed) failed to install/upgrade: trying to overwrite '/usr/include/i386-linux-gnu/zconf.h', which is also in package zlib1g-dev:i386 1:1.2.8.dfsg-2ubuntu4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/1617844/+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 1598300] Re: cups hang after a while
edited /lib/systemd/system/cups.socket restarted systemd and cups. waiting for the bug to come back ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1598300 Title: cups hang after a while Status in cups package in Ubuntu: Confirmed Bug description: after 6 minutes or so, cups is not responding. it do not produce error on the log, just stop working, worse, it exit with 0 ⌌—⌍ |root@cupsmachine :~# systemctl status cups | |● cups.service - CUPS Scheduler | | Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: enabled)| | Active: inactive (dead) since ven. 2016-07-01 10:31:32 TAHT; 2min 16s ago | | Docs: man:cupsd(8) | | Process: 28686 ExecStart=/usr/sbin/cupsd -l (code=exited, status=0/SUCCESS)| | Main PID: 28686 (code=exited, status=0/SUCCESS) | | | |juil. 01 10:30:01 appli-client systemd[1]: Started CUPS Scheduler. | ⌎—⌏ I got to launch it again, so I have finish with a cron job like */10 * * * * systemctl status cups.service|grep -q 'inactive (dead)' && systemctl start cups but it is a dirty solution. I have no idea of what make it stop. NB: I have seen problems related to apparmor, this machine has no apparmor package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1598300/+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 1598300] Re: cups hang after a while
hi Till, there is no client.* in /etc/cups -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1598300 Title: cups hang after a while Status in cups package in Ubuntu: Confirmed Bug description: after 6 minutes or so, cups is not responding. it do not produce error on the log, just stop working, worse, it exit with 0 ⌌—⌍ |root@cupsmachine :~# systemctl status cups | |● cups.service - CUPS Scheduler | | Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: enabled)| | Active: inactive (dead) since ven. 2016-07-01 10:31:32 TAHT; 2min 16s ago | | Docs: man:cupsd(8) | | Process: 28686 ExecStart=/usr/sbin/cupsd -l (code=exited, status=0/SUCCESS)| | Main PID: 28686 (code=exited, status=0/SUCCESS) | | | |juil. 01 10:30:01 appli-client systemd[1]: Started CUPS Scheduler. | ⌎—⌏ I got to launch it again, so I have finish with a cron job like */10 * * * * systemctl status cups.service|grep -q 'inactive (dead)' && systemctl start cups but it is a dirty solution. I have no idea of what make it stop. NB: I have seen problems related to apparmor, this machine has no apparmor package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1598300/+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 1507025] Re: Shell Command Injection with the hostname
This issue was assigned CVE-2016-0634. See the oss-security notice here: http://openwall.com/lists/oss-security/2016/09/16/8 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1507025 Title: Shell Command Injection with the hostname Status in bash package in Ubuntu: New Bug description: If the HOSTNAME of the pc contains a shell command , the command will run every time you start a terminal, tty or xterm. The command will also executed every time when you type in some command. If you for example change the directory , it will run again. Exploit Demo : 1) edit "/etc/hosts" to this : 127.0.0.1 localhost 127.0.1.1 `ls>bug` 2) edit "/etc/hostname" to this : `ls>bug` 3) reboot 4) start a terminal 5) Now a file with the name "bug" will in your home folder ! 6) Change the directory to Downloads with "cd Downloads/" 7) Now a file with the name "bug" is in your Downloads ! 8) Remove the file with "rm bug" 9) The file "bug" is still there ! Have a look on the screenshot i have attached. Solution: The hostname should be checked if there are shell commands inside !! By the way : The hostname is not always in the hands of the root. Some people rent "vservers" and the hostname is in the hands of the isp. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: bash 4.3-14ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-15.18-generic 4.2.3 Uname: Linux 4.2.0-15-generic x86_64 ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 16 22:31:46 2015 InstallationDate: Installed on 2015-10-09 (6 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151009) SourcePackage: bash UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1507025/+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 1507025] Re: Shell Command Injection with the hostname
** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2016-0634 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1507025 Title: Shell Command Injection with the hostname Status in bash package in Ubuntu: New Bug description: If the HOSTNAME of the pc contains a shell command , the command will run every time you start a terminal, tty or xterm. The command will also executed every time when you type in some command. If you for example change the directory , it will run again. Exploit Demo : 1) edit "/etc/hosts" to this : 127.0.0.1 localhost 127.0.1.1 `ls>bug` 2) edit "/etc/hostname" to this : `ls>bug` 3) reboot 4) start a terminal 5) Now a file with the name "bug" will in your home folder ! 6) Change the directory to Downloads with "cd Downloads/" 7) Now a file with the name "bug" is in your Downloads ! 8) Remove the file with "rm bug" 9) The file "bug" is still there ! Have a look on the screenshot i have attached. Solution: The hostname should be checked if there are shell commands inside !! By the way : The hostname is not always in the hands of the root. Some people rent "vservers" and the hostname is in the hands of the isp. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: bash 4.3-14ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-15.18-generic 4.2.3 Uname: Linux 4.2.0-15-generic x86_64 ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 16 22:31:46 2015 InstallationDate: Installed on 2015-10-09 (6 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151009) SourcePackage: bash UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1507025/+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 1579584] Re: installing guitarpro6 creates a situation where sudo:i386 is scheduled for install
** Summary changed: - package sudo 1.8.16-0ubuntu1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 + installing guitarpro6 creates a situation where sudo:i386 is scheduled for install -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1579584 Title: installing guitarpro6 creates a situation where sudo:i386 is scheduled for install Status in sudo package in Ubuntu: Confirmed Bug description: root@music:~/media/midi-files# sudo apt-get install ia32-libs Reading package lists... Done Building dependency tree Reading state information... Done Package ia32-libs is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source However the following packages replace it: lib32ncurses5 lib32z1 E: Package 'ia32-libs' has no installation candidate root@music:~/media/midi-files# sudo apt-get install lib32ncurses5 lib32z1 Reading package lists... Done Building dependency tree Reading state information... Done lib32ncurses5 is already the newest version (6.0+20160213-1ubuntu1). lib32z1 is already the newest version (1:1.2.8.dfsg-2ubuntu4). You might want to run 'apt-get -f install' to correct these: The following packages have unmet dependencies: guitarpro6:i386 : Depends: gksu:i386 but it is not going to be installed Depends: libportaudio0:i386 but it is not installable Depends: libportaudio2:i386 but it is not going to be installed Depends: libssl0.9.8:i386 but it is not installable E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution). root@music:~/media/midi-files# apt-get -f install Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following packages were automatically installed and are no longer required: extlinux gksu:i386 libatk1.0-0:i386 libaudit1:i386 libcairo2:i386 libdatrie1:i386 libdbus-glib-1-2:i386 libgconf-2-4:i386 libgdk-pixbuf2.0-0:i386 libgksu2-0:i386 libgnome-keyring0:i386 libgraphite2-3:i386 libgtk2.0-0:i386 libgtop-2.0-10:i386 libharfbuzz0b:i386 libpam-modules:i386 libpam0g:i386 libpango-1.0-0:i386 libpangocairo-1.0-0:i386 libpangoft2-1.0-0:i386 libpixman-1-0:i386 libstartup-notification0:i386 libthai0:i386 libxcb-render0:i386 libxcb-shm0:i386 libxcb-util1:i386 sudo:i386 syslinux syslinux-common unetbootin-translations Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: gksu:i386 libatk1.0-0:i386 libaudit1:i386 libcairo2:i386 libdatrie1:i386 libdbus-glib-1-2:i386 libgconf-2-4:i386 libgdk-pixbuf2.0-0:i386 libgksu2-0:i386 libgnome-keyring0:i386 libgraphite2-3:i386 libgtk2.0-0:i386 libgtop-2.0-10:i386 libharfbuzz0b:i386 libpam-modules:i386 libpam0g:i386 libpango-1.0-0:i386 libpangocairo-1.0-0:i386 libpangoft2-1.0-0:i386 libpixman-1-0:i386 libportaudio2:i386 libstartup-notification0:i386 libthai0:i386 libxcb-render0:i386 libxcb-shm0:i386 libxcb-util1:i386 sudo:i386 Suggested packages: librsvg2-common:i386 gvfs:i386 libpam-doc:i386 Recommended packages: update-motd:i386 The following packages will be REMOVED: gksu guitarpro6:i386 libgksu2-0 pd-deken sudo ubuntu-minimal unetbootin The following NEW packages will be installed: gksu:i386 libatk1.0-0:i386 libaudit1:i386 libcairo2:i386 libdatrie1:i386 libdbus-glib-1-2:i386 libgconf-2-4:i386 libgdk-pixbuf2.0-0:i386 libgksu2-0:i386 libgnome-keyring0:i386 libgraphite2-3:i386 libgtk2.0-0:i386 libgtop-2.0-10:i386 libharfbuzz0b:i386 libpam-modules:i386 libpam0g:i386 libpango-1.0-0:i386 libpangocairo-1.0-0:i386 libpangoft2-1.0-0:i386 libpixman-1-0:i386 libportaudio2:i386 libstartup-notification0:i386 libthai0:i386 libxcb-render0:i386 libxcb-shm0:i386 libxcb-util1:i386 sudo:i386 0 upgraded, 27 newly installed, 7 to remove and 0 not upgraded. 1 not fully installed or removed. Need to get 4,702 kB of archives. After this operation, 215 MB disk space will be freed. Do you want to continue? [Y/n] y Get:1 http://us.archive.ubuntu.com/ubuntu xenial/main i386 libaudit1 i386 1:2.4.5-1ubuntu2 [37.6 kB] Get:2 http://us.archive.ubuntu.com/ubuntu xenial/main i386 libpam0g i386 1.1.8-3.2ubuntu2 [57.8 kB] Get:3 http://us.archive.ubuntu.com/ubuntu xenial/main i386 libpam-modules i386 1.1.8-3.2ubuntu2 [256 kB] Get:4 http://us.archive.ubuntu.com/ubuntu xenial/main i386 libgnome-keyring0 i386 3.12.0-1build1 [59.5 kB] Get:5 http://us.archive.ubuntu.com/ubuntu xenial/main i386 sudo i386 1.8.16-0ubuntu1 [395 kB] Get:6 http://us.archive.ubuntu.com/ubuntu xenial/main i386 libdbus-glib-1-2 i386 0.106-1 [73.
[Touch-packages] [Bug 1624503] Re: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1624503 Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned Status in fontconfig package in Ubuntu: New Bug description: got error while upgrading from 14.04 to 16.04 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: fontconfig 2.11.94-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Fri Sep 16 22:48:53 2016 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2016-04-02 (167 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: fontconfig Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to xenial on 2016-09-16 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1624503/+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 1624503] [NEW] package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned
Public bug reported: got error while upgrading from 14.04 to 16.04 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: fontconfig 2.11.94-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Fri Sep 16 22:48:53 2016 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2016-04-02 (167 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: fontconfig Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to xenial on 2016-09-16 (0 days ago) ** Affects: fontconfig (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1624503 Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned Status in fontconfig package in Ubuntu: New Bug description: got error while upgrading from 14.04 to 16.04 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: fontconfig 2.11.94-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Fri Sep 16 22:48:53 2016 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2016-04-02 (167 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: fontconfig Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to xenial on 2016-09-16 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1624503/+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 1267531] Re: package sudo 1.8.6p3-0ubuntu3 failed to install/upgrade: подпроцесс установлен сценарий pre-removal возвратил код ошибки 1
*** This bug is a duplicate of bug 1579584 *** https://bugs.launchpad.net/bugs/1579584 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1579584, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1579584 package sudo 1.8.16-0ubuntu1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1267531 Title: package sudo 1.8.6p3-0ubuntu3 failed to install/upgrade: подпроцесс установлен сценарий pre-removal возвратил код ошибки 1 Status in sudo package in Ubuntu: Confirmed Bug description: I don't know ProblemType: Package DistroRelease: Ubuntu 13.10 Package: sudo 1.8.6p3-0ubuntu3 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Mon Jan 6 17:42:31 2014 ErrorMessage: подпроцесс установлен сценарий pre-removal возвратил код ошибки 1 InstallationDate: Installed on 2013-11-13 (56 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: sudo Title: package sudo 1.8.6p3-0ubuntu3 failed to install/upgrade: подпроцесс установлен сценарий pre-removal возвратил код ошибки 1 UpgradeStatus: No upgrade log present (probably fresh install) VisudoCheck: /etc/sudoers: parsed OK /etc/sudoers.d/README: parsed OK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1267531/+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 1399924] Re: package sudo 1.8.9p5-1ubuntu2 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1
*** This bug is a duplicate of bug 1579584 *** https://bugs.launchpad.net/bugs/1579584 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1579584, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1579584 package sudo 1.8.16-0ubuntu1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1399924 Title: package sudo 1.8.9p5-1ubuntu2 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 Status in sudo package in Ubuntu: Confirmed Status in sudo package in Ubuntu Linaro Evaluation Build: New Bug description: nothing happens just a window at every startup appears about fixing the problem ProblemType: Package DistroRelease: Ubuntu 14.10 Package: sudo 1.8.9p5-1ubuntu2 Uname: Linux 3.14.1-031401-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 Date: Fri Dec 5 01:47:59 2014 DuplicateSignature: package:sudo:1.8.9p5-1ubuntu2:subprocess installed pre-removal script returned error exit status 1 ErrorMessage: subprocess installed pre-removal script returned error exit status 1 InstallationDate: Installed on 2014-06-23 (165 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: sudo Title: package sudo 1.8.9p5-1ubuntu2 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to utopic on 2014-10-27 (39 days ago) VisudoCheck: /etc/sudoers: parsed OK /etc/sudoers.d/README: parsed OK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1399924/+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 1205581] Re: package sudo 1.8.6p3-0ubuntu3 failed to install/upgrade: el subproceso instalado el script pre-removal devolvió el código de salida de error 1
*** This bug is a duplicate of bug 1579584 *** https://bugs.launchpad.net/bugs/1579584 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1579584, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1579584 package sudo 1.8.16-0ubuntu1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1205581 Title: package sudo 1.8.6p3-0ubuntu3 failed to install/upgrade: el subproceso instalado el script pre-removal devolvió el código de salida de error 1 Status in sudo package in Ubuntu: New Bug description: rutilio@rutilio-s5510la:~/Descargas$ sudo dpkg -i gp6 [sudo] password for rutilio: dpkg: error al procesar gp6 (--install): no se puede acceder al archivo: No existe el archivo o el directorio Se encontraron errores al procesar: gp6 rutilio@rutilio-s5510la:~/Descargas$ sudo apt-fast upgrade Working... this may take a while. E: Dependencias incumplidas. Pruebe de nuevo usando -f. Ningún archivo que descargar. Leyendo lista de paquetes... Hecho Creando árbol de dependencias Leyendo la información de estado... Hecho Tal vez quiera ejecutar «apt-get -f install» para corregirlo. Los siguientes paquetes tienen dependencias incumplidas: guitarpro6:i386 : Depende: libportaudio0:i386 pero no está instalado Depende: libportaudio2:i386 pero no está instalado Depende: gksu:i386 pero no está instalado Depende: libssl0.9.8:i386 pero no está instalado E: Dependencias incumplidas. Pruebe de nuevo usando -f. rutilio@rutilio-s5510la:~/Descargas$ sudo apt-get -f install Leyendo lista de paquetes... Hecho Creando árbol de dependencias Leyendo la información de estado... Hecho Corrigiendo dependencias... Listo Los paquetes indicados a continuación se instalaron de forma automática y ya no son necesarios. gdebi-core gir1.2-gconf-2.0 gir1.2-unique-3.0 libatk1.0-0:i386 libaudit1:i386 libcairo2:i386 libdatrie1:i386 libdbus-glib-1-2:i386 libgconf-2-4:i386 libgdk-pixbuf2.0-0:i386 libgnome-keyring0:i386 libgtk2.0-0:i386 libharfbuzz0:i386 libicu48:i386 libjasper1:i386 libpam-modules:i386 libpam0g:i386 libpango1.0-0:i386 libpixman-1-0:i386 libportaudio0:i386 libssl0.9.8:i386 libstartup-notification0:i386 libthai0:i386 libunique-3.0-0 libxcb-render0:i386 libxcb-shm0:i386 libxcb-util0:i386 libxft2:i386 sudo:i386 Use 'apt-get autoremove' to remove them. Se instalarán los siguientes paquetes extras: libportaudio0:i386 libportaudio2:i386 libssl0.9.8:i386 Los siguientes paquetes se ELIMINARÁN: gdebi gksu guitarpro6:i386 libgksu2-0 sudo ubuntu-minimal ubuntu-tweak Se instalarán los siguientes paquetes NUEVOS: libportaudio0:i386 libportaudio2:i386 libssl0.9.8:i386 0 actualizados, 3 se instalarán, 7 para eliminar y 1 no actualizados. 1 no instalados del todo o eliminados. Necesito descargar 957 kB de archivos. Se liberarán 225 MB después de esta operación. ¿Desea continuar [S/n]? s Des:1 http://mx.archive.ubuntu.com/ubuntu/ raring/main libportaudio2 i386 19+svn2021-1build1 [72,7 kB] Des:2 http://mx.archive.ubuntu.com/ubuntu/ raring/universe libssl0.9.8 i386 0.9.8o-7ubuntu3.1 [868 kB] Des:3 http://mx.archive.ubuntu.com/ubuntu/ raring/universe libportaudio0 i386 18.1-7.1 [16,8 kB] Descargados 957 kB en 7seg. (127 kB/s) Preconfigurando paquetes ... (Leyendo la base de datos ... 194328 ficheros o directorios instalados actualmente.) Desinstalando guitarpro6 ... Desinstalando gdebi ... Desinstalando ubuntu-tweak ... Desinstalando gksu ... Desinstalando libgksu2-0 ... Desinstalando ubuntu-minimal ... Desinstalando sudo ... You have asked that the sudo package be removed, but no root password has been set. Without sudo, you may not be able to gain administrative privileges. If you would prefer to access the root account with su(1) or by logging in directly, you must set a root password with "sudo passwd". If you have arranged other means to access the root account, and you are sure this is what you want, you may bypass this check by setting an environment variable (export SUDO_FORCE_REMOVE=yes). Refusing to remove sudo. dpkg: error al procesar sudo (--remove): el subproceso instalado el script pre-removal devolvió el
[Touch-packages] [Bug 1186691] Re: package sudo 1.8.6p3-0ubuntu3 failed to install/upgrade: il sottoprocesso installato script di pre-removal ha restituito lo stato di errore 1
*** This bug is a duplicate of bug 1579584 *** https://bugs.launchpad.net/bugs/1579584 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1579584, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1579584 package sudo 1.8.16-0ubuntu1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1186691 Title: package sudo 1.8.6p3-0ubuntu3 failed to install/upgrade: il sottoprocesso installato script di pre-removal ha restituito lo stato di errore 1 Status in sudo package in Ubuntu: New Bug description: Don't know what happened. ProblemType: Package DistroRelease: Ubuntu 13.04 Package: sudo 1.8.6p3-0ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-24.35-generic 3.8.13 Uname: Linux 3.8.0-24-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 Date: Sun Jun 2 09:37:54 2013 DuplicateSignature: package:sudo:1.8.6p3-0ubuntu3:il sottoprocesso installato script di pre-removal ha restituito lo stato di errore 1 ErrorMessage: il sottoprocesso installato script di pre-removal ha restituito lo stato di errore 1 InstallationDate: Installed on 2013-05-01 (32 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: sudo Title: package sudo 1.8.6p3-0ubuntu3 failed to install/upgrade: il sottoprocesso installato script di pre-removal ha restituito lo stato di errore 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1186691/+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 1404623] Re: package sudo 1.8.9p5-1ubuntu1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1
*** This bug is a duplicate of bug 1579584 *** https://bugs.launchpad.net/bugs/1579584 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1579584, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1579584 package sudo 1.8.16-0ubuntu1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1404623 Title: package sudo 1.8.9p5-1ubuntu1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 Status in sudo: New Status in sudo package in Ubuntu: Incomplete Bug description: Error occurred due to Guitar Pro 6 installation ProblemType: Package DistroRelease: Ubuntu 14.04 Package: sudo 1.8.9p5-1ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 Date: Sun Dec 21 17:35:56 2014 DuplicateSignature: package:sudo:1.8.9p5-1ubuntu1:subprocess installed pre-removal script returned error exit status 1 ErrorMessage: subprocess installed pre-removal script returned error exit status 1 InstallationDate: Installed on 2014-12-20 (1 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: sudo Title: package sudo 1.8.9p5-1ubuntu1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) VisudoCheck: /etc/sudoers: parsed OK /etc/sudoers.d/README: parsed OK To manage notifications about this bug go to: https://bugs.launchpad.net/sudo/+bug/1404623/+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 1584699] Re: package sudo 1.8.16-0ubuntu1.1 failed to install/upgrade: Unterprozess installiertes pre-removal-Skript gab den Fehlerwert 1 zurück
*** This bug is a duplicate of bug 1579584 *** https://bugs.launchpad.net/bugs/1579584 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1579584, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1579584 package sudo 1.8.16-0ubuntu1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1584699 Title: package sudo 1.8.16-0ubuntu1.1 failed to install/upgrade: Unterprozess installiertes pre-removal-Skript gab den Fehlerwert 1 zurück Status in sudo package in Ubuntu: New Bug description: I tried to install guitar hero pro 6 trial version with sudo dkpg -i packagename.deb sudo apt install -f And then the error popped up ProblemType: Package DistroRelease: Ubuntu 16.04 Package: sudo 1.8.16-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Mon May 23 12:30:22 2016 ErrorMessage: Unterprozess installiertes pre-removal-Skript gab den Fehlerwert 1 zurück InstallationDate: Installed on 2016-05-19 (4 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.10ubuntu1 SourcePackage: sudo Title: package sudo 1.8.16-0ubuntu1.1 failed to install/upgrade: Unterprozess installiertes pre-removal-Skript gab den Fehlerwert 1 zurück UpgradeStatus: No upgrade log present (probably fresh install) VisudoCheck: /etc/sudoers: Analyse OK /etc/sudoers.d/README: Analyse OK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1584699/+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 1416215] Re: package sudo 1.8.9p5-1ubuntu1 failed to install/upgrade: el subproceso instalado el script pre-removal devolvió el código de salida de error 1
*** This bug is a duplicate of bug 1579584 *** https://bugs.launchpad.net/bugs/1579584 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1579584, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1579584 package sudo 1.8.16-0ubuntu1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1416215 Title: package sudo 1.8.9p5-1ubuntu1 failed to install/upgrade: el subproceso instalado el script pre-removal devolvió el código de salida de error 1 Status in sudo package in Ubuntu: New Bug description: Trying to install some libbs, this error apears... i guess that is because this is a 32x system and those libb use a 64x sudo, so that. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: sudo 1.8.9p5-1ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 Date: Thu Jan 29 13:18:02 2015 DuplicateSignature: package:sudo:1.8.9p5-1ubuntu1:el subproceso instalado el script pre-removal devolvió el código de salida de error 1 ErrorMessage: el subproceso instalado el script pre-removal devolvió el código de salida de error 1 InstallationDate: Installed on 2015-01-22 (7 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: sudo Title: package sudo 1.8.9p5-1ubuntu1 failed to install/upgrade: el subproceso instalado el script pre-removal devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) VisudoCheck: /etc/sudoers análisis OK /etc/sudoers.d/README análisis OK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1416215/+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 1591950] Re: package sudo 1.8.16-0ubuntu1.1 failed to install/upgrade: підпроцес встановлено pre-removal сценарій повернув статус помилку 1
*** This bug is a duplicate of bug 1579584 *** https://bugs.launchpad.net/bugs/1579584 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1579584, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1579584 package sudo 1.8.16-0ubuntu1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1591950 Title: package sudo 1.8.16-0ubuntu1.1 failed to install/upgrade: підпроцес встановлено pre-removal сценарій повернув статус помилку 1 Status in sudo package in Ubuntu: New Bug description: idk, just got an error every start up ProblemType: Package DistroRelease: Ubuntu 16.04 Package: sudo 1.8.16-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Sun Jun 12 21:44:16 2016 ErrorMessage: підпроцес встановлено pre-removal сценарій повернув статус помилку 1 InstallationDate: Installed on 2016-06-12 (1 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: sudo Title: package sudo 1.8.16-0ubuntu1.1 failed to install/upgrade: підпроцес встановлено pre-removal сценарій повернув статус помилку 1 UpgradeStatus: No upgrade log present (probably fresh install) VisudoCheck: /etc/sudoers: вдала обробка /etc/sudoers.d/README: вдала обробка To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1591950/+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 140467] Re: sudo-ldap not installable
*** This bug is a duplicate of bug 1103776 *** https://bugs.launchpad.net/bugs/1103776 ** This bug has been marked a duplicate of bug 1103776 installing sudo-ldap causes dpkg error removing sudo -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/140467 Title: sudo-ldap not installable Status in sudo package in Ubuntu: Triaged Bug description: Binary package hint: sudo-ldap There is a failsafe built in the sudo package that prevent sudo-ldap (which Replace/Provide sudo) from being installed. See the output transcript below . Setting SUDO_FORCE_REMOVE=yes work just as expected. = ubuntu@gutsy-i386-packaging:~$ sudo apt-get install sudo-ldap Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: python-debian python-deb822 linux-headers-2.6.22-10 linux-headers-2.6.22-10-generic Use 'apt-get autoremove' to remove them. The following packages will be REMOVED: sudo The following NEW packages will be installed: sudo-ldap 0 upgraded, 1 newly installed, 1 to remove and 182 not upgraded. Need to get 0B/179kB of archives. After unpacking 16.4kB of additional disk space will be used. Do you want to continue [Y/n]? y dpkg: sudo: dependency problems, but removing anyway as you request: ubuntu-minimal depends on sudo. gksu depends on sudo. (Reading database ... 136124 files and directories currently installed.) Removing sudo ... You have asked that the sudo package be removed, but no root password has been set. Without sudo, you may not be able to gain administrative privileges. If you would prefer to access the root account with su(1) or by logging in directly, you must set a root password with "sudo passwd". If you have arranged other means to access the root account, and you are sure this is what you want, you may bypass this check by setting an environment variable (export SUDO_FORCE_REMOVE=yes). Refusing to remove sudo. dpkg: error processing sudo (--remove): subprocess pre-removal script returned error exit status 1 Errors were encountered while processing: sudo E: Sub-process /usr/bin/dpkg returned an error code (1) ubuntu@gutsy-i386-packaging:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/140467/+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 1435040] Re: Ubuntu Phone does not connect to car-bluetooth
On my Renault Laguna (2010) with TomTom Carminat I managed to pair, but connect doesn't seem to work. I ssh'ed into the phone (Arale) while connecting and saw that it actually does connect, but is disconnected after 2 seconds. This seems to confuse the TomTom shows it is trying to connect while in reality it was connected until the connection broke. I didn't see any reason why it disconnects in log etc. But maybe I'm looking in the wrong place. I would say it's about time we get this fixed. It seems to be some sort of timing issue. I'd be happy to collect logs, just let me know how. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1435040 Title: Ubuntu Phone does not connect to car-bluetooth Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Incomplete Bug description: With my FORD Focus Car, pairing does not work. The bluetooth system in the car searches for devices and shows "Aquaris E4.5 Ubuntu Edition" and then prompts me to connect with a 4-digit pin code, but the Ubuntu phone doesn't react at all and after a while the car system says that it failed to connect. image: 20150310-3201c0a KRILIN01A-S15A_BQ_L100EN_2020_150312 OS Build 20 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435040/+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 1103776] Re: package sudo 1.8.5p2-1ubuntu1 failed to install/upgrade: le sous-processus script pre-removal installé a retourné une erreur de sortie d'état 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: sudo (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1103776 Title: installing sudo-ldap causes dpkg error removing sudo Status in sudo package in Ubuntu: Triaged Bug description: failed install webissues-server client ProblemType: Package DistroRelease: Ubuntu 12.10 Package: sudo 1.8.5p2-1ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-22.34-generic 3.5.7.2 Uname: Linux 3.5.0-22-generic x86_64 ApportVersion: 2.6.1-0ubuntu10 AptOrdering: sudo: Remove sudo-ldap: Install sudo-ldap: Configure Architecture: amd64 Date: Thu Jan 24 01:19:35 2013 ErrorMessage: le sous-processus script pre-removal installé a retourné une erreur de sortie d'état 1 MarkForUpload: True SourcePackage: sudo Title: package sudo 1.8.5p2-1ubuntu1 failed to install/upgrade: le sous-processus script pre-removal installé a retourné une erreur de sortie d'état 1 UpgradeStatus: No upgrade log present (probably fresh install) VisudoCheck: /etc/sudoers: parsed OK /etc/sudoers.d/README: parsed OK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1103776/+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 1103776] Re: installing sudo-ldap causes dpkg error removing sudo
** Summary changed: - package sudo 1.8.5p2-1ubuntu1 failed to install/upgrade: le sous-processus script pre-removal installé a retourné une erreur de sortie d'état 1 + installing sudo-ldap causes dpkg error removing sudo ** Changed in: sudo (Ubuntu) Status: Confirmed => Triaged ** Changed in: sudo (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1103776 Title: installing sudo-ldap causes dpkg error removing sudo Status in sudo package in Ubuntu: Triaged Bug description: failed install webissues-server client ProblemType: Package DistroRelease: Ubuntu 12.10 Package: sudo 1.8.5p2-1ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-22.34-generic 3.5.7.2 Uname: Linux 3.5.0-22-generic x86_64 ApportVersion: 2.6.1-0ubuntu10 AptOrdering: sudo: Remove sudo-ldap: Install sudo-ldap: Configure Architecture: amd64 Date: Thu Jan 24 01:19:35 2013 ErrorMessage: le sous-processus script pre-removal installé a retourné une erreur de sortie d'état 1 MarkForUpload: True SourcePackage: sudo Title: package sudo 1.8.5p2-1ubuntu1 failed to install/upgrade: le sous-processus script pre-removal installé a retourné une erreur de sortie d'état 1 UpgradeStatus: No upgrade log present (probably fresh install) VisudoCheck: /etc/sudoers: parsed OK /etc/sudoers.d/README: parsed OK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1103776/+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 1394802] Re: package sudo 1.8.9p5-1ubuntu1 failed to install/upgrade: sub-processo script pre-removal instalado retornou estado de saída de erro 1
*** This bug is a duplicate of bug 1103776 *** https://bugs.launchpad.net/bugs/1103776 ** This bug has been marked a duplicate of bug 1103776 package sudo 1.8.5p2-1ubuntu1 failed to install/upgrade: le sous-processus script pre-removal installé a retourné une erreur de sortie d'état 1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1394802 Title: package sudo 1.8.9p5-1ubuntu1 failed to install/upgrade: sub-processo script pre-removal instalado retornou estado de saída de erro 1 Status in sudo package in Ubuntu: Confirmed Bug description: I am a new user and I tried to install sudo-ldap without knowing what it is and then I noticed some warnings about sudo. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: sudo 1.8.9p5-1ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 AptOrdering: sudo: Remove sudo-ldap: Install sudo-ldap: Configure Architecture: amd64 Date: Thu Nov 20 20:48:38 2014 DuplicateSignature: package:sudo:1.8.9p5-1ubuntu1:sub-processo script pre-removal instalado retornou estado de saída de erro 1 ErrorMessage: sub-processo script pre-removal instalado retornou estado de saída de erro 1 InstallationDate: Installed on 2014-08-21 (91 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: sudo Title: package sudo 1.8.9p5-1ubuntu1 failed to install/upgrade: sub-processo script pre-removal instalado retornou estado de saída de erro 1 UpgradeStatus: No upgrade log present (probably fresh install) VisudoCheck: /etc/sudoers: análise OK /etc/sudoers.d/README: análise OK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1394802/+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 1623173] Re: [Asus ZenBook UX501VW] Function key to toggle the screen doesn't work
I did but the issue was modified and this part was deleted (to keep a single problem by issue I guess). And that shouldn't be confused with the touchpad toggle. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1622005 Could you reopen this one please? Thanks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1623173 Title: [Asus ZenBook UX501VW] Function key to toggle the screen doesn't work Status in xorg package in Ubuntu: Invalid Bug description: On Ubuntu Ubuntu 16.04.1 LTS with all the latest kernels installed from http://kernel.ubuntu.com/~kernel-ppa/mainline/ : 4.4.19, 4.5.7, 4.6.7, 4.7.3 nor 4.8-rc6. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 Uname: Linux 4.8.0-040800rc6-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] est un dossier: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 367.44 Wed Aug 17 22:24:07 PDT 2016 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Sep 13 21:49:46 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Skylake Integrated Graphics [1043:1080] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:1080] InstallationDate: Installed on 2016-06-01 (104 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 046d:c069 Logitech, Inc. M-U0007 [Corded Mouse M500] Bus 001 Device 002: ID 04f2:b3fd Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. N501VW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-040800rc6-generic root=UUID=ad612961-a4ae-4950-9d5a-20dcf8e56681 ro quiet splash acpi_osi= acpi_backlight=native nouveau.modeset=0 nvidia.nomodeset=0 i915.nomodeset=0 vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/09/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: N501VW.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: N501VW dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN501VW.300:bd05/09/2016:svnASUSTeKCOMPUTERINC.:pnN501VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: N501VW dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue Sep 13 21:14:29 2016 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) [drm] Failed to open DRM device for (null): -22 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 12876 vendor SDC xserver.version: 2:1.18.3-1ubuntu2.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1623173/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@list
[Touch-packages] [Bug 1103776] Re: package sudo 1.8.5p2-1ubuntu1 failed to install/upgrade: le sous-processus script pre-removal installé a retourné une erreur de sortie d'état 1
The reporter tried to install sudo-ldap which conflicts with sudo which doesn't want to be removed. Removing sudo (1.8.16-0ubuntu1.2) ... You have asked that the sudo package be removed, but no root password has been set. Without sudo, you may not be able to gain administrative privileges. If you would prefer to access the root account with su(1) or by logging in directly, you must set a root password with "sudo passwd". If you have arranged other means to access the root account, and you are sure this is what you want, you may bypass this check by setting an environment variable (export SUDO_FORCE_REMOVE=yes). Refusing to remove sudo. dpkg: error processing package sudo (--remove): subprocess installed pre-removal script returned error exit status 1 Errors were encountered while processing: sudo E: Sub-process /usr/bin/dpkg returned an error code (1) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1103776 Title: package sudo 1.8.5p2-1ubuntu1 failed to install/upgrade: le sous- processus script pre-removal installé a retourné une erreur de sortie d'état 1 Status in sudo package in Ubuntu: New Bug description: failed install webissues-server client ProblemType: Package DistroRelease: Ubuntu 12.10 Package: sudo 1.8.5p2-1ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-22.34-generic 3.5.7.2 Uname: Linux 3.5.0-22-generic x86_64 ApportVersion: 2.6.1-0ubuntu10 AptOrdering: sudo: Remove sudo-ldap: Install sudo-ldap: Configure Architecture: amd64 Date: Thu Jan 24 01:19:35 2013 ErrorMessage: le sous-processus script pre-removal installé a retourné une erreur de sortie d'état 1 MarkForUpload: True SourcePackage: sudo Title: package sudo 1.8.5p2-1ubuntu1 failed to install/upgrade: le sous-processus script pre-removal installé a retourné une erreur de sortie d'état 1 UpgradeStatus: No upgrade log present (probably fresh install) VisudoCheck: /etc/sudoers: parsed OK /etc/sudoers.d/README: parsed OK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1103776/+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 1616107] Re: Kernel oops + system freeze on network-bridge shutdown
I started a Reverse kernel bisect between v4.4 final and v4.5-rc1. The kernel bisect will require testing of about 7-10 test kernels. I built the first test kernel, up to the following commit: 1289ace5b4f70f1e68ce785735b82c7e483de863 The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1616107 Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results. Thanks in advance -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bridge-utils in Ubuntu. https://bugs.launchpad.net/bugs/1616107 Title: Kernel oops + system freeze on network-bridge shutdown Status in bridge-utils package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in bridge-utils source package in Xenial: New Status in linux source package in Xenial: Confirmed Status in bridge-utils source package in Yakkety: New Bug description: A Kernel oops leaves Ubuntu 16.04 unusable when a network bridge is brought down on a HPE 530SFP+ 10GBit NIC that uses bnx2x as a driver. This error does not appear in Ubuntu 14.04 however. The error is reproducible whenever issuing the commands "shutdown", "service networking stop" or "brctl delbr br0". Manually creating the bridge and subsequently bringing it down results in the same error. /var/log/kern.log: [...] Aug 23 15:09:46 base1 kernel: [ 617.996677] device ens1f0 left promiscuous mode Aug 23 15:09:46 base1 kernel: [ 617.996699] br0: port 1(ens1f0) entered disabled state Aug 23 15:09:46 base1 kernel: [ 617.996730] BUG: unable to handle kernel NULL pointer dereference at 00d2 Aug 23 15:09:46 base1 kernel: [ 618.008306] IP: [] __vlan_flush+0x18/0x60 [bridge] Aug 23 15:09:46 base1 kernel: [ 618.020549] PGD 10374c0067 PUD 1033927067 PMD 0 Aug 23 15:09:46 base1 kernel: [ 618.032773] Oops: 0002 [#1] SMP Aug 23 15:09:46 base1 kernel: [ 618.044434] Modules linked in: nls_iso8859_1 ipmi_ssif intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass sb_edac edac_core joydev bridge stp llc input_leds hpilo lpc_ich ioatdma ipmi_si ipmi_msghandler shpchp mac_hid acpi_power_meter ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid0 multipath linear raid1 hid_generic crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd igb usbhid hid bnx2x dca ahci i2c_algo_bit vxlan libahci ip6_udp_tunnel udp_tunnel ptp pps_core mdio libcrc32c wmi fjes Aug 23 15:09:46 base1 kernel: [ 618.058563] CPU: 3 PID: 4049 Comm: brctl Not tainted 4.4.0-34-generic #53-Ubuntu Aug 23 15:09:46 base1 kernel: [ 618.058564] Hardware name: HP ProLiant DL120 Gen9/ProLiant DL120 Gen9, BIOS P86 05/05/2016 Aug 23 15:09:46 base1 kernel: [ 618.058574] task: 881030676040 ti: 8810341e4000 task.ti: 8810341e4000 Aug 23 15:09:46 base1 kernel: [ 618.058576] RIP: 0010:[] [] __vlan_flush+0x18/0x60 [bridge] Aug 23 15:09:46 base1 kernel: [ 618.058754] RSP: 0018:8810341e7d68 EFLAGS: 00010206 Aug 23 15:09:46 base1 kernel: [ 618.058769] RAX: RBX: RCX: Aug 23 15:09:46 base1 kernel: [ 618.058774] RDX: 881038470848 RSI: RDI: Aug 23 15:09:46 base1 kernel: [ 618.058775] RBP: 8810341e7d78 R08: R09: 8170d949 Aug 23 15:09:46 base1 kernel: [ 618.058776] R10: ead61340 R11: 8810329d2c00 R12: 00c0 Aug 23 15:09:46 base1 kernel: [ 618.058777] R13: 881030044000 R14: 881038470840 R15: Aug 23 15:09:46 base1 kernel: [ 618.058782] FS: 7f9aebc94700() GS:88107fcc() knlGS: Aug 23 15:09:46 base1 kernel: [ 618.058789] CS: 0010 DS: ES: CR0: 80050033 Aug 23 15:09:46 base1 kernel: [ 618.058790] CR2: 00d2 CR3: 00102fe83000 CR4: 001406e0 Aug 23 15:09:46 base1 kernel: [ 618.058802] Stack: Aug 23 15:09:46 base1 kernel: [ 618.058806] 8810356a4c00 8810341e7d98 c0489258 Aug 23 15:09:46 base1 kernel: [ 618.058822] 8810356a4c00 881038470840 8810341e7dc0 c0479bd8 Aug 23 15:09:46 base1 kernel: [ 618.058825] 881038470838 881038470848 88103847 8810341e7df8 Aug 23 15:09:46 base1 kernel: [ 618.058827] Call Trace: Aug 23 15:09:46 base1 kernel: [ 618.058863] [] nbp_vlan_flush+0x28/0x65 [bridge] Aug 23 15:09:46 base1 kernel: [ 618.058870] [] del_nbp+0x98/0x130 [bridge] Aug 23 15:09:46 base1 kernel: [ 618.058889] [] br_dev_delete+0x42/0xb0 [bridge] Aug 23 15:09:46 base1 kernel: [ 618.058895] [] br_del_bridge+0x4
[Touch-packages] [Bug 1624437] Re: Wish: Provide a gtk/gdk friendly interface to content-hub
** Changed in: content-hub (Ubuntu) Assignee: (unassigned) => William Hua (attente) ** Changed in: content-hub (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to content-hub in Ubuntu. https://bugs.launchpad.net/bugs/1624437 Title: Wish: Provide a gtk/gdk friendly interface to content-hub Status in content-hub package in Ubuntu: In Progress Bug description: There is probably no technical limitation that blocks anyone from using the current API of content-hub to implement drag & drop features in gdk, but there might be other subtle issues with bringing in qt as a dependency to gtk+. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/content-hub/+bug/1624437/+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 1624485] [NEW] Nettle: Enable AES-NI instructions on amd64.
Public bug reported: The current build of libnettle6 does not have AES-NI enabled. There's two configure options for enabling it: --enable-x86-aesni: Use AES-NI instructions instead of the standard implementation. This will break on systems that don't have AES-NI. --enable-fat: Build a "fat" library that has the standard implementation and the AES-NI implementation. This allows the library to continue working on older systems while providing faster performance on systems that have AES-NI. Note that Nettle's AES-NI implementation as of v3.2 is only supported on amd64, not i386, so this would only affect the 64-bit package. ** Affects: nettle (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nettle in Ubuntu. https://bugs.launchpad.net/bugs/1624485 Title: Nettle: Enable AES-NI instructions on amd64. Status in nettle package in Ubuntu: New Bug description: The current build of libnettle6 does not have AES-NI enabled. There's two configure options for enabling it: --enable-x86-aesni: Use AES-NI instructions instead of the standard implementation. This will break on systems that don't have AES-NI. --enable-fat: Build a "fat" library that has the standard implementation and the AES-NI implementation. This allows the library to continue working on older systems while providing faster performance on systems that have AES-NI. Note that Nettle's AES-NI implementation as of v3.2 is only supported on amd64, not i386, so this would only affect the 64-bit package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nettle/+bug/1624485/+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 1618590] Re: scoperunner crashed with SIGSEGV in QObject::disconnect()
Sorry, the fix in Qt's code review system is at https://codereview.qt- project.org/#/c/161056/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1618590 Title: scoperunner crashed with SIGSEGV in QObject::disconnect() Status in qtbase-opensource-src package in Ubuntu: Confirmed Bug description: crash ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: unity-scope-click 0.1.1+16.10.20160808-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Tue Aug 30 17:54:20 2016 ExecutablePath: /usr/lib/x86_64-linux-gnu/unity-scopes/scoperunner InstallationDate: Installed on 2016-08-27 (3 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcCmdline: /usr/lib/x86_64-linux-gnu/unity-scopes/scoperunner /usr/lib/x86_64-linux-gnu/unity-scopes/clickapps/clickscope.ini Scope: Apps Signal: 11 SourcePackage: unity-scope-click StacktraceTop: QObject::disconnect(QObject const*, char const*, QObject const*, char const*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 start_thread (arg=0x7fae9eade700) at pthread_create.c:333 Title: scoperunner crashed with SIGSEGV in QObject::disconnect() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1618590/+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 1618590] Re: scoperunner crashed with SIGSEGV in QObject::disconnect()
This appears to be a crash inside Qt itself, and only occurs with 5.6+, apparently due to QDBus changing to use threading instead of the event loop, for asynchronous operations. There seems to be some fixes in Qt Code Review that should theoretically fix this. It would be nice if we could test these and get them into our release of Qt. I'm afraid there won't be any way to work around this crash in the scope or ubuntu- download-manager (we're keeping a u-d-m singleton object around, which is destroyed on exit) code itself. ** Package changed: unity-scope-click (Ubuntu) => qtbase-opensource-src (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1618590 Title: scoperunner crashed with SIGSEGV in QObject::disconnect() Status in qtbase-opensource-src package in Ubuntu: Confirmed Bug description: crash ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: unity-scope-click 0.1.1+16.10.20160808-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Tue Aug 30 17:54:20 2016 ExecutablePath: /usr/lib/x86_64-linux-gnu/unity-scopes/scoperunner InstallationDate: Installed on 2016-08-27 (3 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcCmdline: /usr/lib/x86_64-linux-gnu/unity-scopes/scoperunner /usr/lib/x86_64-linux-gnu/unity-scopes/clickapps/clickscope.ini Scope: Apps Signal: 11 SourcePackage: unity-scope-click StacktraceTop: QObject::disconnect(QObject const*, char const*, QObject const*, char const*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 start_thread (arg=0x7fae9eade700) at pthread_create.c:333 Title: scoperunner crashed with SIGSEGV in QObject::disconnect() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1618590/+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 1618590] [NEW] scoperunner crashed with SIGSEGV in QObject::disconnect()
You have been subscribed to a public bug: crash ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: unity-scope-click 0.1.1+16.10.20160808-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Tue Aug 30 17:54:20 2016 ExecutablePath: /usr/lib/x86_64-linux-gnu/unity-scopes/scoperunner InstallationDate: Installed on 2016-08-27 (3 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcCmdline: /usr/lib/x86_64-linux-gnu/unity-scopes/scoperunner /usr/lib/x86_64-linux-gnu/unity-scopes/clickapps/clickscope.ini Scope: Apps Signal: 11 SourcePackage: unity-scope-click StacktraceTop: QObject::disconnect(QObject const*, char const*, QObject const*, char const*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 start_thread (arg=0x7fae9eade700) at pthread_create.c:333 Title: scoperunner crashed with SIGSEGV in QObject::disconnect() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Affects: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-crash yakkety -- scoperunner crashed with SIGSEGV in QObject::disconnect() https://bugs.launchpad.net/bugs/1618590 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. -- 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 1616107] Re: Kernel oops + system freeze on network-bridge shutdown
** Also affects: bridge-utils (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Yakkety) Importance: High Status: Confirmed ** Also affects: bridge-utils (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => Confirmed ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => High ** No longer affects: linux (Ubuntu Yakkety) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bridge-utils in Ubuntu. https://bugs.launchpad.net/bugs/1616107 Title: Kernel oops + system freeze on network-bridge shutdown Status in bridge-utils package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in bridge-utils source package in Xenial: New Status in linux source package in Xenial: Confirmed Status in bridge-utils source package in Yakkety: New Bug description: A Kernel oops leaves Ubuntu 16.04 unusable when a network bridge is brought down on a HPE 530SFP+ 10GBit NIC that uses bnx2x as a driver. This error does not appear in Ubuntu 14.04 however. The error is reproducible whenever issuing the commands "shutdown", "service networking stop" or "brctl delbr br0". Manually creating the bridge and subsequently bringing it down results in the same error. /var/log/kern.log: [...] Aug 23 15:09:46 base1 kernel: [ 617.996677] device ens1f0 left promiscuous mode Aug 23 15:09:46 base1 kernel: [ 617.996699] br0: port 1(ens1f0) entered disabled state Aug 23 15:09:46 base1 kernel: [ 617.996730] BUG: unable to handle kernel NULL pointer dereference at 00d2 Aug 23 15:09:46 base1 kernel: [ 618.008306] IP: [] __vlan_flush+0x18/0x60 [bridge] Aug 23 15:09:46 base1 kernel: [ 618.020549] PGD 10374c0067 PUD 1033927067 PMD 0 Aug 23 15:09:46 base1 kernel: [ 618.032773] Oops: 0002 [#1] SMP Aug 23 15:09:46 base1 kernel: [ 618.044434] Modules linked in: nls_iso8859_1 ipmi_ssif intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass sb_edac edac_core joydev bridge stp llc input_leds hpilo lpc_ich ioatdma ipmi_si ipmi_msghandler shpchp mac_hid acpi_power_meter ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid0 multipath linear raid1 hid_generic crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd igb usbhid hid bnx2x dca ahci i2c_algo_bit vxlan libahci ip6_udp_tunnel udp_tunnel ptp pps_core mdio libcrc32c wmi fjes Aug 23 15:09:46 base1 kernel: [ 618.058563] CPU: 3 PID: 4049 Comm: brctl Not tainted 4.4.0-34-generic #53-Ubuntu Aug 23 15:09:46 base1 kernel: [ 618.058564] Hardware name: HP ProLiant DL120 Gen9/ProLiant DL120 Gen9, BIOS P86 05/05/2016 Aug 23 15:09:46 base1 kernel: [ 618.058574] task: 881030676040 ti: 8810341e4000 task.ti: 8810341e4000 Aug 23 15:09:46 base1 kernel: [ 618.058576] RIP: 0010:[] [] __vlan_flush+0x18/0x60 [bridge] Aug 23 15:09:46 base1 kernel: [ 618.058754] RSP: 0018:8810341e7d68 EFLAGS: 00010206 Aug 23 15:09:46 base1 kernel: [ 618.058769] RAX: RBX: RCX: Aug 23 15:09:46 base1 kernel: [ 618.058774] RDX: 881038470848 RSI: RDI: Aug 23 15:09:46 base1 kernel: [ 618.058775] RBP: 8810341e7d78 R08: R09: 8170d949 Aug 23 15:09:46 base1 kernel: [ 618.058776] R10: ead61340 R11: 8810329d2c00 R12: 00c0 Aug 23 15:09:46 base1 kernel: [ 618.058777] R13: 881030044000 R14: 881038470840 R15: Aug 23 15:09:46 base1 kernel: [ 618.058782] FS: 7f9aebc94700() GS:88107fcc() knlGS: Aug 23 15:09:46 base1 kernel: [ 618.058789] CS: 0010 DS: ES: CR0: 80050033 Aug 23 15:09:46 base1 kernel: [ 618.058790] CR2: 00d2 CR3: 00102fe83000 CR4: 001406e0 Aug 23 15:09:46 base1 kernel: [ 618.058802] Stack: Aug 23 15:09:46 base1 kernel: [ 618.058806] 8810356a4c00 8810341e7d98 c0489258 Aug 23 15:09:46 base1 kernel: [ 618.058822] 8810356a4c00 881038470840 8810341e7dc0 c0479bd8 Aug 23 15:09:46 base1 kernel: [ 618.058825] 881038470838 881038470848 88103847 8810341e7df8 Aug 23 15:09:46 base1 kernel: [ 618.058827] Call Trace: Aug 23 15:09:46 base1 kernel: [ 618.058863] [] nbp_vlan_flush+0x28/0x65 [bridge] Aug 23 15:09:46 base1 kernel: [ 618.058870] [] del_nbp+0x98/0x130 [bridge] Aug 23 15:09:46 base1 kernel: [ 618.058889] [] br_dev_delete+0x42/0xb0 [bridge] A
[Touch-packages] [Bug 1624480] [NEW] ir-keytable extra key presses repeating
Public bug reported: Greetings, I searched the forum and multiple others for a solution to this, but I can't seem to find one that addresses this issue directly for ir-keytable. Most seem to refer to lirc installations. I do NOT have lirc installed, but it exists natively in Ubuntu 16.04 kernel. I’m using Ubuntu LTS 16.04. ir-keytable is configured using the NEC driver for the MCE/Xbox remote I configured mappings for. What is happening, is that when I press a key, it emulates the keyboard properly without any issues and it works as designed. However, if I press the same key more than once in succession within about 250 ms, it will repeat the key about 20 times incredibly fast. I have dumps of the ir- keytable -t as well as the status and configuration I’m using. I also have confirmed that the remote sending the keypresses is NOT sending any sustain or repeats (RTI environment). I have also confirmed lirc is NOT installed by searching the config directories don't exist and irw doesn't exist. I have also tried to change the default Repeat delay and repeat period, but it takes and changes them, they just aren’t persistent after a reboot. It doesn’t seem to help anyway, I’ve changed them to 1000 and 50 respectively and tested but it doesn’t change the behavior. This is happening in Plex Home Theater as well as the OS. Any ideas? Thank you in advance. Hardware: Intel NUC6i5SYH with latest BIOS. IR onboard and configured in BIOS. Confirmed working reliably. root@nuc:~# ir-keytable Found /sys/class/rc/rc0/ (/dev/input/event7) with: Driver ite-cir, table rc-rc6-mce Supported protocols: unknown other lirc rc-5 jvc sony nec sanyo mce-kbd rc-6 sharp xmp Enabled protocols: lirc nec rc-6 Name: ITE8713 CIR transceiver bus: 25, vendor/product: 1283:, version: 0x Repeat delay = 500 ms, repeat period = 125 ms root@nuc:~# ~~First three lines of /etc/rc_maps.cfg~~ #driver table file * * xbox_remote * rc-adstech-dvb-t-pci adstech_dvb_t_pci * rc-alink-dtu-m alink_dtu_m root@nuc:~# ir-keytable -c -p RC-6,NEC -w /etc/rc_keymaps/xbox_remote root@nuc:~# ir-keytable -s rc0 -r scancode 0x80d801 = KEY_1 (0x02) scancode 0x80d802 = KEY_2 (0x03) scancode 0x80d803 = KEY_3 (0x04) scancode 0x80d804 = KEY_4 (0x05) scancode 0x80d805 = KEY_5 (0x06) scancode 0x80d806 = KEY_6 (0x07) scancode 0x80d807 = KEY_7 (0x08) scancode 0x80d808 = KEY_8 (0x09) scancode 0x80d809 = KEY_9 (0x0a) scancode 0x80d80e = KEY_0 (0x0b) scancode 0x80d813 = KEY_Q (0x10) scancode 0x80d814 = KEY_F (0x21) scancode 0x80d815 = KEY_R (0x13) scancode 0x80d819 = KEY_X (0x2d) scancode 0x80d81e = KEY_UP (0x67) scancode 0x80d81f = KEY_DOWN (0x6c) scancode 0x80d820 = KEY_LEFT (0x69) scancode 0x80d821 = KEY_RIGHT (0x6a) scancode 0x80d822 = KEY_ENTER (0x1c) scancode 0x80d823 = KEY_ESC (0x01) scancode 0x80d865 = KEY_C (0x2e) scancode 0x80d866 = KEY_P (0x19) scancode 0x80d867 = KEY_H (0x23) scancode 0x80d868 = KEY_O (0x18) scancode 0x80d86e = KEY_I (0x17) scancode 0x80d86f = KEY_M (0x32) scancode 0x80d870 = KEY_SPACE (0x39) Enabled protocols: lirc nec rc-6 root@nuc:~# root@nuc:~# ir-keytable -t Testing events. Please, press CTRL-C to abort. 1473634552.241175: event type EV_MSC(0x04): scancode = 0x80d821 1473634552.241175: event type EV_KEY(0x01) key_down: KEY_RIGHT(0x006a) 1473634552.241175: event type EV_SYN(0x00). 1473634552.251813: event type EV_MSC(0x04): scancode = 0x80d821 1473634552.251813: event type EV_SYN(0x00). 1473634552.376940: event type EV_MSC(0x04): scancode = 0x80d821 1473634552.376940: event type EV_SYN(0x00). 1473634552.484285: event type EV_MSC(0x04): scancode = 0x80d821 1473634552.484285: event type EV_SYN(0x00). 1473634552.495393: event type EV_MSC(0x04): scancode = 0x80d821 1473634552.495393: event type EV_SYN(0x00). 1473634552.695346: event type EV_MSC(0x04): scancode = 0x80d821 1473634552.695346: event type EV_SYN(0x00). 1473634552.738179: event type EV_KEY(0x01) key_down: KEY_RIGHT(0x006a) 1473634552.738179: event type EV_SYN(0x00). 1473634552.866084: event type EV_KEY(0x01) key_down: KEY_RIGHT(0x006a) 1473634552.866084: event type EV_SYN(0x00). 1473634552.946080: event type EV_KEY(0x01) key_up: KEY_RIGHT(0x006a) 1473634552.946080: event type EV_SYN(0x00). 1473634555.090156: event type EV_MSC(0x04): scancode = 0x80d821 1473634555.090156: event type EV_KEY(0x01) key_down: KEY_RIGHT(0x006a) 1473634555.090156: event type EV_SYN(0x00). 1473634555.100966: event type EV_MSC(0x04): scancode = 0x80d821 1473634555.100966: event type EV_SYN(0x00). 1473634555.301295: event type EV_MSC(0x04): scancode = 0x80d821 1473634555.301295: event type EV_SYN(0x00). 1473634555.550080: event type EV_KEY(0x01) key_up: KEY_RIGHT(0x006a) 1473634555.550080: event type EV_SYN(0x00). 1473634555.952914: event type EV_MSC(0x04): scancode = 0x80d821 1473634555.952914: event type EV_KEY(0x01) key_down: KEY_RIGHT(0x006a) 1473634555.952914: event type EV_SYN(0x00). 1473634555.963546: event type EV_MSC(0x04): scancode = 0x80d821 1473634555.963546: event type EV_SYN(0x00). 1473
[Touch-packages] [Bug 1624381] Re: add additional shortcut support for zoom/unzoom in US keyboards
you should try on your french keyboard to see.. I'm guessing they are always enabled. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1624381 Title: add additional shortcut support for zoom/unzoom in US keyboards Status in webbrowser-app package in Ubuntu: Confirmed Bug description: On US keyboards, the "+" (plus) key is in shifted position, and the "-" (minus) is not. All the other browsers (chrome, chromium, firefox) support the following shortcuts for zoom/unzoom and we should do the same, so user does not have to press ctrl+shift as that is not expected. zoom in: ctrl+plus ctrl+equals zoom out: ctrl+underscore ctrl+minus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1624381/+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 1624407] Re: Closing an application doesn’t actually close it, it merely requests all its windows to be closed
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity8 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1624407 Title: Closing an application doesn’t actually close it, it merely requests all its windows to be closed Status in qtmir package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: Currently in unity8, when requesting to "Quit" a running application from the launcher, what happens is that qtmir goes through all its associated windows/surfaces, and closes them one by one. Supposedly, when the last window is closed, the application terminates itself (but this is not necessarily the case, see https://doc.qt.io/qt-5/qguiapplication.html#quitOnLastWindowClosed- prop). This prevents application authors from doing proper cleanup before the app is closed. For example in Qt, the QCoreApplication::aboutToQuit() signal is emitted only after all windows have been closed, so the application doesn’t get a chance to e.g. save the list of open windows (real use case for multi-window browser application which saves the current session). This is similar to unity7’s implementation by the way, but I think it’s wrong. Surely there must be a way (maybe toolkit-specific) to request an app to terminate itself (and fall back to closing all windows if not). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtmir/+bug/1624407/+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 1577596] Re: ntpd not started when using ntpdate
I'm seeing same behavior as Alex where failure of ntpdate is preventing ntpd from starting. ntpdate is logging same message indicating failure due to name resolution (Bind not running yet at boot): Sep 16 10:40:09 scorpion ntpdate[1033]: name server cannot be used: Temporary failure in name resolution (-3) The script /etc/network/if-up.d/ntpdate does attempt to stop any running ntp service prior to running ntpdate but then exits without restarting ntp if ntpdate-debian fails. I modified /etc/network/if-up.d/ntpdate to only log a message and exit as a workaround and ntpd now starts at boot. I'm still a bit puzzled why ntpd doesn't attempt to start after /etc/network/if-up.d/ntpdate fails (multiple times in my case due to multiple interfaces on host). When /etc/network/if-up.d/ntpdate runs/fails, there is no log message from ntp indicating it tried to start (neither before nor after ntpdate fails). However, after applying my workaround, the log message for ntp service is one second after last run of /etc/network/if-up.d/ntpdate. I would have thought that the failure of ntpdate would not prevent the later startup of ntp. I'm guessing that /etc/network/if-up.d/ntpdate initiates a stop in parallel to systemd start of ntpd before it logs anything to syslog. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1577596 Title: ntpd not started when using ntpdate Status in init-system-helpers package in Ubuntu: Confirmed Status in ntp package in Ubuntu: Confirmed Bug description: After updating from 14.04 to 16.04 on a number of my systems, ntpd no longer starts at boot on any of those systems. `systemctl status ntp` shows: ntp.service - LSB: Start NTP daemon Loaded: loaded (/etc/init.d/ntp; bad; vendor preset: enabled) Active: inactive (dead) Docs: man:systemd-sysv-generator(8) May 02 19:10:14 host systemd[1]: Stopped LSB: Start NTP daemon. May 02 19:10:17 host systemd[1]: Stopped LSB: Start NTP daemon. Manually starting it using `systemctl start ntp` works fine. However, systemd does not seem to want to start it automatically at boot time. As best as I can tell based on trial and error, there is something special about the combination of the service being named "ntp.service" and the service depending on network.target. However, I haven't been able to identify exactly what is causing this. If I copy the init script to any other name, everything works fine: cp /etc/init.d/ntp /etc/init.d/ntpd Edit /etc/init.d/ntpd and change "Provides: ntp" to "Provides: ntpd" systemctl enable ntpd # After a reboot, ntpd.service is started, but ntp.service is not. If I remove "$network" from the "# Required-Start: $network $remote_fs $syslog" line in /etc/init.d/ntp, then systemd starts it automatically ... But of course it is started before the network comes up, so it fails. If I replace /etc/init.d/ntp with a file containing only the following, systemd won't try to start it automatically at boot: #!/bin/sh ### BEGIN INIT INFO # Provides: ntp # Required-Start: $network # Required-Stop: $network # Default-Start: 2 3 4 5 # Default-Stop: 1 # Short-Description: Start NTP daemon ### END INIT INFO echo "script was run" >> /ntp.log If I rename that same dummy script to /etc/init.d/ntp2, it is started automatically at boot. However, grepping the systemd source code and my systemd config files for ntp doesn't seem to find anything that might cause this behavior: /etc/systemd# grep -iR ntp * timesyncd.conf:#NTP= timesyncd.conf:#FallbackNTP=ntp.ubuntu.com /lib/systemd# grep -R ntp * system/systemd-timesyncd.service.d/disable-with-time-daemon.conf:ConditionFileIsExecutable=!/usr/sbin/ntpd system/systemd-timesyncd.service.d/disable-with-time-daemon.conf:ConditionFileIsExecutable=!/usr/sbin/openntpd Binary file systemd-networkd matches Binary file systemd-timedated matches Binary file systemd-timesyncd matches What else can I do to debug this further? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1577596/+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 1624261] Re: [M10 HD] Video recorded from camera app is reproduced rotate 90 degrees.
Dd you record in portrait mode? It seems the recording is fine but the playback is weird as it rotates a rotated video. In landscape it seems fine ** Changed in: canonical-devices-system-image Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1624261 Title: [M10 HD] Video recorded from camera app is reproduced rotate 90 degrees. Status in Canonical System Image: Incomplete Status in frieza: New Status in camera-app package in Ubuntu: New Bug description: Environment Product: Freezer HD FW version: UBUNTU 15.04 (r14) HW version: MP Material: Description Steps to Reproduce: 1 - Go to Camera app 2 - Go to video and start to record. 3 - Stop record, go to gallery app and reproduce it. Actual Result: Video is reproduced rotate in 90 degrees. Expected Result: Video should be reproduced as the same way it was recorded. Reproducibility: 100% Additional info: The issue is reproducible only in HD device and with rear and front camera. See related bugs lp:1601887 and lp:1590415 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1624261/+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 1570478] Re: Segfault in UCTheme::PaletteConfig::restorePalette with Qt 5.6
** Branch linked: lp:~zsombi/ubuntu-ui-toolkit/fixPaletteChange -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1570478 Title: Segfault in UCTheme::PaletteConfig::restorePalette with Qt 5.6 Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: Update: Qt 5.6.1 and UITK 20160716: 13 failures which MUST be fixed: dpr2 dpr3 performance --- original report --- Considerably less than on amd64 (bug #1560004), but still some now seen with the new UITK 20160412 and the latest Qt builds: 1 failures which MUST be fixed: tst_performance tests/xvfb.sh tests/unit/runtest.sh _build/tests/unit/performance/performance [...] #7 0x77c32034 in UCTheme::PaletteConfig::restorePalette() (this=0xeb8160) at ./src/Ubuntu/UbuntuToolkit/uctheme.cpp:278 #8 0x77c2ebf3 in UCTheme::~UCTheme() (this=0xeb8160, __in_chrg=) at ./src/Ubuntu/UbuntuToolkit/uctheme_p.h:125 https://launchpadlibrarian.net/253810125/buildlog_ubuntu-xenial-armhf .ubuntu-ui- toolkit_1.3.1938+16.04.20160412build1~xenial1~qt560~1_BUILDING.txt.gz More information about Qt 5.6 at https://wiki.ubuntu.com/Touch/QtTesting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1570478/+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 1624469] Re: compiz not work
Thank you for taking the time to report this issue and helping to make Ubuntu better. Examining the information you have given us, this does not appear to be a bug report so we are closing it and converting it to a question in the support tracker. We understand the difficulties you are facing, but it is better to raise problems you are having in the support tracker at https://answers.launchpad.net/ubuntu if you are uncertain if they are bugs. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at http://askubuntu.com or https://ubuntuforums.org. For help on reporting bugs, see https://help.ubuntu.com/community/ReportingBugs. ** Package changed: xorg (Ubuntu) => compiz (Ubuntu) ** Changed in: compiz (Ubuntu) Status: New => Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/compiz/+question/397271 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1624469 Title: compiz not work Status in compiz package in Ubuntu: Invalid Bug description: help me for setting compiz Intel® Ironlake Mobile x86/MMX/SSE2 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-95.142-generic 3.13.11-ckt39 Uname: Linux 3.13.0-95-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.21 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Sep 17 00:09:19 2016 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 12) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1702] InstallationDate: Installed on 2016-09-15 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 13d3:5130 IMC Networks Integrated Webcam Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK Computer Inc. K42F ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-95-generic root=UUID=801c9280-90f4-426a-8bc3-913757803b90 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/08/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 422 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K42F dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr422:bd12/08/2010:svnASUSTeKComputerInc.:pnK42F:pvr1.0:rvnASUSTeKComputerInc.:rnK42F:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: K42F dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Fri Sep 16 23:26:51 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 395 vendor LGD xserver.version: 2:1.15.1-0ubuntu2.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1624469/+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 1624470] Re: webbrowser_app.tests.test_contextmenu.TestContextMenuTextArea.test_actions hangs on desktop
** Changed in: webbrowser-app (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1624470 Title: webbrowser_app.tests.test_contextmenu.TestContextMenuTextArea.test_actions hangs on desktop Status in webbrowser-app package in Ubuntu: Confirmed Bug description: This is a fairly recent regression, that test used to pass reliably on desktop. As not much has changed in the browser code itself, I suspect changes somewhere else in the stack maybe. When run on my xenial+overlay laptop in a unity7 session, webbrowser_app.tests.test_contextmenu.TestContextMenuTextArea.test_actions hangs and eventually times out. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1624470/+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 1624470] Re: webbrowser_app.tests.test_contextmenu.TestContextMenuTextArea.test_actions hangs on desktop
This also occurs for me under the same conditions, therefore marking as confirmed. ** Changed in: webbrowser-app (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1624470 Title: webbrowser_app.tests.test_contextmenu.TestContextMenuTextArea.test_actions hangs on desktop Status in webbrowser-app package in Ubuntu: Confirmed Bug description: This is a fairly recent regression, that test used to pass reliably on desktop. As not much has changed in the browser code itself, I suspect changes somewhere else in the stack maybe. When run on my xenial+overlay laptop in a unity7 session, webbrowser_app.tests.test_contextmenu.TestContextMenuTextArea.test_actions hangs and eventually times out. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1624470/+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 1624470] [NEW] webbrowser_app.tests.test_contextmenu.TestContextMenuTextArea.test_actions hangs on desktop
Public bug reported: This is a fairly recent regression, that test used to pass reliably on desktop. As not much has changed in the browser code itself, I suspect changes somewhere else in the stack maybe. When run on my xenial+overlay laptop in a unity7 session, webbrowser_app.tests.test_contextmenu.TestContextMenuTextArea.test_actions hangs and eventually times out. ** Affects: webbrowser-app (Ubuntu) Importance: High Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1624470 Title: webbrowser_app.tests.test_contextmenu.TestContextMenuTextArea.test_actions hangs on desktop Status in webbrowser-app package in Ubuntu: Confirmed Bug description: This is a fairly recent regression, that test used to pass reliably on desktop. As not much has changed in the browser code itself, I suspect changes somewhere else in the stack maybe. When run on my xenial+overlay laptop in a unity7 session, webbrowser_app.tests.test_contextmenu.TestContextMenuTextArea.test_actions hangs and eventually times out. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1624470/+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 1624469] [NEW] compiz not work
Public bug reported: help me for setting compiz Intel® Ironlake Mobile x86/MMX/SSE2 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-95.142-generic 3.13.11-ckt39 Uname: Linux 3.13.0-95-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.21 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Sep 17 00:09:19 2016 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 12) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1702] InstallationDate: Installed on 2016-09-15 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 13d3:5130 IMC Networks Integrated Webcam Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK Computer Inc. K42F ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-95-generic root=UUID=801c9280-90f4-426a-8bc3-913757803b90 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/08/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 422 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K42F dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr422:bd12/08/2010:svnASUSTeKComputerInc.:pnK42F:pvr1.0:rvnASUSTeKComputerInc.:rnK42F:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: K42F dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Fri Sep 16 23:26:51 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 395 vendor LGD xserver.version: 2:1.15.1-0ubuntu2.7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 trusty ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1624469 Title: compiz not work Status in xorg package in Ubuntu: New Bug description: help me for setting compiz Intel® Ironlake Mobile x86/MMX/SSE2 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-95.142-generic 3.13.11-ckt39 Uname: Linux 3.13.0-95-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.21 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Sep 17 00:09:19 2016 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 12) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1702] InstallationDate: Installed on 2016-09-15 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 13d3:5130 IMC Networks Integrated Webcam Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK Computer Inc. K42F ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-95-generic root
[Touch-packages] [Bug 1624407] Re: Closing an application doesn’t actually close it, it merely requests all its windows to be closed
It is not out of place at all - just an enhancement request. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1624407 Title: Closing an application doesn’t actually close it, it merely requests all its windows to be closed Status in qtmir package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: New Bug description: Currently in unity8, when requesting to "Quit" a running application from the launcher, what happens is that qtmir goes through all its associated windows/surfaces, and closes them one by one. Supposedly, when the last window is closed, the application terminates itself (but this is not necessarily the case, see https://doc.qt.io/qt-5/qguiapplication.html#quitOnLastWindowClosed- prop). This prevents application authors from doing proper cleanup before the app is closed. For example in Qt, the QCoreApplication::aboutToQuit() signal is emitted only after all windows have been closed, so the application doesn’t get a chance to e.g. save the list of open windows (real use case for multi-window browser application which saves the current session). This is similar to unity7’s implementation by the way, but I think it’s wrong. Surely there must be a way (maybe toolkit-specific) to request an app to terminate itself (and fall back to closing all windows if not). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtmir/+bug/1624407/+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 1579278] Re: Keep powersave CPU frequency scaling governor for CPUs that support intel_pstate
>> The preferred governor with the intel_pstate driver is powersave. > Do you have some references/proof for that? This is contrary to what > kernel developers say, see comment 1. In my opinion, that reference is obsolete. While I don't work for Intel, the intel_pstate CPU frequency driver is pretty much the only thing that I work on, and for a few years now, and through 3 maintainers. Why would Intel expend so much effort on powersave mode, if it were better to merely set performance mode and forget about it? The objective with powersave mode is best energy/ performance tradeoff. There are still issues, yes. For example whenever clock modulation becomes involved. Also, there can be a tendency to incorrectly drive up the CPU frequency. There is work in progress that should address these issues (see: http://askubuntu.com/questions/812530 /cpu-frequency-scaling-not-working-as-intended-on-vanilla- ubuntu-16-04/812721#812721 and the reference links therein.) I'll try to come back, maybe this weekend, with some energy comparison numbers. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1579278 Title: Keep powersave CPU frequency scaling governor for CPUs that support intel_pstate Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in sysvinit package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in systemd source package in Xenial: Invalid Status in sysvinit source package in Xenial: Triaged Bug description: Hi, With the new Ubuntu archive servers, we saw constantly high load and after some tinkering, we found that it was mostly CPUs being woken up to see if they should enter idle states. Changing the CPU frequency scaling governor to "performance" saw a considerable drop. Perf report using the following commands: | perf record -g -a sleep 10 | perf report | Samples: 287K of event 'cycles:pp', Event count (approx.): 124776998906 | Children Self Command Shared Object Symbol | + 55.24% 0.20% swapper [kernel.kallsyms] [k] cpu_startup_entry | + 53.51% 0.00% swapper [kernel.kallsyms] [k] start_secondary | + 53.02% 0.08% swapper [kernel.kallsyms] [k] call_cpuidle | + 52.94% 0.02% swapper [kernel.kallsyms] [k] cpuidle_enter | + 31.81% 0.67% swapper [kernel.kallsyms] [k] cpuidle_enter_state | + 29.59% 0.12% swapper [kernel.kallsyms] [k] acpi_idle_enter | + 29.45% 0.05% swapper [kernel.kallsyms] [k] acpi_idle_do_entry | + 29.43%29.43% swapper [kernel.kallsyms] [k] acpi_processor_ffh_cstate_enter | + 20.51% 0.04% swapper [kernel.kallsyms] [k] ret_from_intr | + 20.47% 0.12% swapper [kernel.kallsyms] [k] do_IRQ | + 19.30% 0.07% swapper [kernel.kallsyms] [k] irq_exit | + 19.18% 0.07% apache2 [kernel.kallsyms] [k] entry_SYSCALL_64_fastpath | + 18.80% 0.17% swapper [kernel.kallsyms] [k] __do_softirq | + 16.45% 0.11% swapper [kernel.kallsyms] [k] net_rx_action | + 16.25% 0.43% swapper [kernel.kallsyms] [k] be_poll | + 14.74% 0.21% swapper [kernel.kallsyms] [k] be_process_rx | + 13.61% 0.07% swapper [kernel.kallsyms] [k] napi_gro_frags | + 12.58% 0.04% swapper [kernel.kallsyms] [k] netif_receive_skb_internal | + 12.48% 0.03% swapper [kernel.kallsyms] [k] __netif_receive_skb | + 12.42% 0.24% swapper [kernel.kallsyms] [k] __netif_receive_skb_core | + 12.41% 0.00% apache2 [unknown] [k] 0x7f27983b5028 | + 12.41% 0.00% apache2 [unknown] [k] 0x7f2798369028 | + 11.49% 0.16% swapper [kernel.kallsyms] [k] ip_rcv | + 11.29% 0.09% swapper [kernel.kallsyms] [k] ip_rcv_finish | + 10.77% 0.05% swapper [kernel.kallsyms] [k] ip_local_deliver | + 10.70% 0.06% swapper [kernel.kallsyms] [k] ip_local_deliver_finish | + 10.55% 0.22% swapper [kernel.kallsyms] [k] tcp_v4_rcv | + 10.10% 0.00% apache2 [unknown] [k] | + 10.01% 0.04% swapper [kernel.kallsyms] [k] tcp_v4_do_rcv Expanding in a few of those, you'll see: | - 55.24% 0.20% swapper [kernel.kallsyms] [k] cpu_startup_entry |- 55.04% cpu_startup_entry | - 52.98% call_
[Touch-packages] [Bug 1586692] Re: bluetooth speakers only work once
*** This bug is a duplicate of bug 1543179 *** https://bugs.launchpad.net/bugs/1543179 ** This bug has been marked a duplicate of bug 1543179 Audio does not get routed to BT headset/speaker -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1586692 Title: bluetooth speakers only work once Status in bluez package in Ubuntu: New Bug description: m10 tablet, OTA10.1 today I am successfully connected to keyboard, mouse, AND bluetooth spakers. All OS beeps and noises are coming out of the bluetooth speakers. If I start podbird, cloudmusic, or one of the radio apps, then they are either silent or the sound comes out of the bluetooth speakers. if I disconnect the bluetooth speakers, and reconnect them, the sound will come from the tablet. The speakers are shown as connected, but don't work. The only way to get them working again is to power down the tablet and restart it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1586692/+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 1624435] Re: systemd-udevd[409]: Process '/usr/sbin/alsactl -E HOME=/run/alsa restore 1' failed with exit code 99
** Description changed: This error is logged : systemd-udevd[409]: Process '/usr/sbin/alsactl -E HOME=/run/alsa restore 1' failed with exit code 99 note: sound works as expected when the GS session is opened; so maybe a booting race. Details: oem@u64:~$ which alsactl /usr/sbin/alsactl oem@u64:~$ df -h /usr/sbin/alsactl Filesystem Size Used Avail Use% Mounted on /dev/sdb418G 11G 6.5G 62% / oem@u64:~$ df -h /run/alsa Filesystem Size Used Avail Use% Mounted on tmpfs 396M 12M 385M 3% /run (/run/alsa does not exist but /run/alsa/ which is an empty subdir) - Found hardware: "HDA-Intel" "Realtek ALC882" "HDA:10ec0882,1043e601,00100101" "0x1043" "0x81d8" + From /usr/sbin/alsactl restore (without 'sudo'): + + Found hardware: "HDA-Intel" "Realtek ALC882" + "HDA:10ec0882,1043e601,00100101" "0x1043" "0x81d8" + + Found hardware: "HDA-Intel" "Nvidia GPU 60 HDMI/DP" + "HDA:10de0060,1458362e,00100100" "0x1458" "0x362e" + Hardware is initialized using a generic method + + Looks like that "Nvidia GPU ..." is detected but not identified by + alsactl (so the 99 exit code) + + "init tries to initialize all devices to a default state. If device is + not known, error code 99 is returned." + http://linux.die.net/man/1/alsactl + oem@u64:~$ sudo /usr/sbin/alsactl restore [sudo] password for oem: oem@u64:~$ that command works: volume is set back to 50% from 100% initialy ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-utils 1.1.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-10.11-generic 4.8.0-rc6 Uname: Linux 4.8.0-10-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Sep 16 16:31:17 2016 SourcePackage: alsa-utils UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: This error is logged : systemd-udevd[409]: Process '/usr/sbin/alsactl -E HOME=/run/alsa restore 1' failed with exit code 99 - note: sound works as expected when the GS session is opened; so maybe a - booting race. + note: sound works as expected when the GS session is opened - Details: oem@u64:~$ which alsactl /usr/sbin/alsactl oem@u64:~$ df -h /usr/sbin/alsactl Filesystem Size Used Avail Use% Mounted on /dev/sdb418G 11G 6.5G 62% / oem@u64:~$ df -h /run/alsa Filesystem Size Used Avail Use% Mounted on tmpfs 396M 12M 385M 3% /run (/run/alsa does not exist but /run/alsa/ which is an empty subdir) From /usr/sbin/alsactl restore (without 'sudo'): Found hardware: "HDA-Intel" "Realtek ALC882" "HDA:10ec0882,1043e601,00100101" "0x1043" "0x81d8" Found hardware: "HDA-Intel" "Nvidia GPU 60 HDMI/DP" "HDA:10de0060,1458362e,00100100" "0x1458" "0x362e" Hardware is initialized using a generic method Looks like that "Nvidia GPU ..." is detected but not identified by alsactl (so the 99 exit code) "init tries to initialize all devices to a default state. If device is not known, error code 99 is returned." http://linux.die.net/man/1/alsactl - oem@u64:~$ sudo /usr/sbin/alsactl restore [sudo] password for oem: oem@u64:~$ that command works: volume is set back to 50% from 100% initialy ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-utils 1.1.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-10.11-generic 4.8.0-rc6 Uname: Linux 4.8.0-10-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Sep 16 16:31:17 2016 SourcePackage: alsa-utils UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/1624435 Title: systemd-udevd[409]: Process '/usr/sbin/alsactl -E HOME=/run/alsa restore 1' failed with exit code 99 Status in alsa-utils package in Ubuntu: New Bug description: This error is logged : systemd-udevd[409]: Process '/usr/sbin/alsactl -E HOME=/run/alsa restore 1' failed with exit code 99 note: sound works as expected when the GS session is opened oem@u64:~$ which alsactl /usr/sbin/alsactl oem@u64:~$ df -h /usr/sbin/alsactl Filesystem Size Used Avail Use% Mounted on /dev/sdb418G 11G 6.5G 62% / oem@u64:~$ df -h /run/alsa Filesystem Size Used Avail Use% Mounted on tmpfs 396M 12M 385M 3% /run (/run/alsa does not exist but /run/alsa/ which is an empty subdir) From /usr/sbin/alsactl restore (without 'sudo'): Found hardware: "HDA-Intel" "Realtek ALC882" "HDA:10ec0882,1043e601,00100101" "0x1043" "0x81d8" Found hardware: "HDA-Intel" "Nvidia GPU 60 HDMI/DP" "HDA:10de0060,1458362e,0010010
[Touch-packages] [Bug 1624407] Re: Closing an application doesn’t actually close it, it merely requests all its windows to be closed
Given that, unlike X11, we have some control over Mir’s design and implementation, maybe this is something that we could consider adding? Or is that out of place? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1624407 Title: Closing an application doesn’t actually close it, it merely requests all its windows to be closed Status in qtmir package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: New Bug description: Currently in unity8, when requesting to "Quit" a running application from the launcher, what happens is that qtmir goes through all its associated windows/surfaces, and closes them one by one. Supposedly, when the last window is closed, the application terminates itself (but this is not necessarily the case, see https://doc.qt.io/qt-5/qguiapplication.html#quitOnLastWindowClosed- prop). This prevents application authors from doing proper cleanup before the app is closed. For example in Qt, the QCoreApplication::aboutToQuit() signal is emitted only after all windows have been closed, so the application doesn’t get a chance to e.g. save the list of open windows (real use case for multi-window browser application which saves the current session). This is similar to unity7’s implementation by the way, but I think it’s wrong. Surely there must be a way (maybe toolkit-specific) to request an app to terminate itself (and fall back to closing all windows if not). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtmir/+bug/1624407/+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 1624415] Re: tcsh coredumps all the time on tab
*** This bug is a duplicate of bug 1618803 *** https://bugs.launchpad.net/bugs/1618803 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1618803, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1618803 tcsh crashed with SIGSEGV in __GI___rewinddir() -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1624415 Title: tcsh coredumps all the time on tab Status in apport package in Ubuntu: New Bug description: When a users having tcsh as its [login] shell presses tab key (autocompletion), tcsh coredumps immediately, always: admin.python ~ > gdb tcsh GNU gdb (Ubuntu 7.11.90.20160906-0ubuntu1) 7.11.90.20160906-git ... (gdb) run Starting program: /local/home/admin/tcsh admin.python ~ > ls . Suspended (tty output) admin.python ~ > fg gdb tcsh Program received signal SIGSEGV, Segmentation fault. __GI___rewinddir (dirp=0x771808) at ../sysdeps/posix/rewinddir.c:34 34../sysdeps/posix/rewinddir.c: No such file or directory. (gdb) quit A debugging session is active. Inferior 1 [process 25990] will be killed. Quit anyway? (y or n) y admin.python ~ > lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Yakkety Yak (development branch) Release: 16.10 Codename: yakkety To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1624415/+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 1542733] Re: Connect to Hidden Wi-Fi Network, "Connect" grayed out
This is the second major problem I've had with the Network Manager less than one year. Ubuntu again proving that it is not robust enough for the general public. -- 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/1542733 Title: Connect to Hidden Wi-Fi Network, "Connect" grayed out Status in network-manager package in Ubuntu: Confirmed Bug description: Reproduce: 1. Create a static, connection to hidden Wi-Fi connection using nm-connection-editor 2. click nm-applet icon click "Connect to Hidden Wi-Fi Network" click pre-existing connection "Connect" is grayed out Work around is using terminal. nmcli c up id ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.0.4-0ubuntu9 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Feb 6 15:58:22 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-02-06 (0 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160206) IpRoute: default via 192.168.0.1 dev wlp2s0 proto static metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.55 metric 600 JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH Wired connection 1 7c22db8e-2026-413b-86cd-0c796f177dd5 802-3-ethernet 1454790964 Sat 06 Feb 2016 02:36:04 PM CST yes 0 no/org/freedesktop/NetworkManager/Settings/1 no -- -- -- jjjGFQQZi0U43GQNlkbUFr0j8ZXA2A d57103a5-d3d7-4fb0-a2a0-469894e184ab 802-11-wireless 1454795858 Sat 06 Feb 2016 03:57:38 PM CST yes 0 no/org/freedesktop/NetworkManager/Settings/0 yes wlp2s0 activated /org/freedesktop/NetworkManager/ActiveConnection/4 nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connected/org/freedesktop/NetworkManager/Devices/1 jjjGFQQZi0U43GQNlkbUFr0j8ZXA2A d57103a5-d3d7-4fb0-a2a0-469894e184ab /org/freedesktop/NetworkManager/ActiveConnection/4 enp1s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1542733/+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 1624406] Re: systemd-fsck test started to fail
Does not reproduce with local QEMU, and does not reproduce any more in
production environment -- I fixed the long reboot issue yesterday,
perhaps that caused it. Retried a test run.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1624406
Title:
systemd-fsck test started to fail
Status in systemd package in Ubuntu:
In Progress
Bug description:
http://autopkgtest.ubuntu.com/packages/s/systemd/yakkety/amd64 now
often fails with
==
FAIL: test_systemd_fsckd_with_failure (__main__.FsckdTest)
Ensure that a failing systemd-fsckd doesn't prevent system to boot
--
Traceback (most recent call last):
File
"/tmp/autopkgtest.WN0dWu/build.zlE/systemd-231/debian/tests/systemd-fsckd",
line 125, in test_systemd_fsckd_with_failure
self.assertTrue(self.was_running('plymouth-start'))
AssertionError: False is not true
Same assertion failure on some other systemd-fsckd tests.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624406/+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 1599692] Re: [webapp-container] URLs dispatched from an app to a webapp are not opened
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: webbrowser-app (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1599692 Title: [webapp-container] URLs dispatched from an app to a webapp are not opened Status in webapps-sprint: In Progress Status in webbrowser-app package in Ubuntu: Confirmed Bug description: There is again a failure when dispatching URLs from an app to a webapp. For example, if in the facebook webapp, one clicks on a specific twitter.com/* url that links to the Twitter webapp, the webapp opens but not to the desired URL. To manage notifications about this bug go to: https://bugs.launchpad.net/webapps-sprint/+bug/1599692/+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 1624320] Re: systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing entries
The primary purpose of adding 127.0.0.53 to resolv.conf is for client
software that wants to do DNS resolution by itself instead of using NSS
-- most notable example is Google Chrome, and third-party software which
is statically linked (e. g. Go).
However, other software like NetworkManager or isc-dhcp also calls
resolvconf and adds name servers picked up by them -- as they don't talk
to resolved directly, resolved reads their DNS servers *from*
resolv.conf.
But, software which does its own DNS lookups like the above have to do
their own DNSSEC validation too -- you can't both chose to *not* use NSS
*and* rely on NSS to do DNSSEC for you..
So, this is indeed a wart, but not easily fixed, and also not that
important IMHO. Not using NSS is already broken to some degree, as you
also ignore things like nss-{winbind,docker,ldap} etc.
** Changed in: systemd (Ubuntu)
Status: New => Triaged
** Changed in: systemd (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1624320
Title:
systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing
entries
Status in systemd package in Ubuntu:
Triaged
Bug description:
systemd-resolved, or more precisely the hook script
/lib/systemd/system/systemd-resolved.service.d/resolvconf.conf, causes
resolvconf to add 127.0.0.53 to the set of nameservers in
/etc/resolv.conf alongside the other nameservers. That makes no sense
because systemd-resolved sets up 127.0.0.53 as a proxy for those other
nameservers. The effect is similar to bug 1624071 but for
applications doing their own DNS lookups. It breaks any DNSSEC
validation that systemd-resolved tries to do; applications will
failover to the other nameservers, bypassing validation failures. And
it makes failing queries take twice as long.
/etc/resolv.conf should have only 127.0.0.53 when systemd-resolved is
active.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624320/+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 1618886] Re: unity-gtk-module.service is racy; session services don't stop if session terminates
This bug was fixed in the package gnome-session - 3.20.2-1ubuntu3 --- gnome-session (3.20.2-1ubuntu3) yakkety; urgency=medium [ Dmitry Shachnev ] * Backport upstream patch to allow users to override $QT_QPA_PLATFORMTHEME (allow_overriding_qt_platformtheme.patch). [ Martin Pitt ] * debian/data/run-systemd-session: Add missing $unit to systemctl show call, so that the cleanup of failed units actually works. (LP: #1618886) -- Martin Pitt Fri, 16 Sep 2016 15:27:56 +0200 ** Changed in: gnome-session (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1618886 Title: unity-gtk-module.service is racy; session services don't stop if session terminates Status in gnome-session package in Ubuntu: Fix Released Status in unity-gtk-module package in Ubuntu: Fix Released Status in upstart package in Ubuntu: Fix Committed Bug description: Sometimes on session start unity-gtk-module.service runs too late or something, and $GTK_MODULES does not include "unity". It is in "systemctl --user show-environment" but not in a terminal bash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1618886/+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 1624407] Re: Closing an application doesn’t actually close it, it merely requests all its windows to be closed
AFAIK Mir follows the same model as X11 (which has the WM_DELETE_WINDOW message but no WM_QUIT). I guess you could kill(pid, SIGTERM)? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1624407 Title: Closing an application doesn’t actually close it, it merely requests all its windows to be closed Status in qtmir package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: New Bug description: Currently in unity8, when requesting to "Quit" a running application from the launcher, what happens is that qtmir goes through all its associated windows/surfaces, and closes them one by one. Supposedly, when the last window is closed, the application terminates itself (but this is not necessarily the case, see https://doc.qt.io/qt-5/qguiapplication.html#quitOnLastWindowClosed- prop). This prevents application authors from doing proper cleanup before the app is closed. For example in Qt, the QCoreApplication::aboutToQuit() signal is emitted only after all windows have been closed, so the application doesn’t get a chance to e.g. save the list of open windows (real use case for multi-window browser application which saves the current session). This is similar to unity7’s implementation by the way, but I think it’s wrong. Surely there must be a way (maybe toolkit-specific) to request an app to terminate itself (and fall back to closing all windows if not). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtmir/+bug/1624407/+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 1579278] Re: Keep powersave CPU frequency scaling governor for CPUs that support intel_pstate
> The preferred governor with the intel_pstate driver is powersave. Do you have some references/proof for that? This is contrary to what kernel developers say, see comment 1. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1579278 Title: Keep powersave CPU frequency scaling governor for CPUs that support intel_pstate Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in sysvinit package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Status in systemd source package in Xenial: Invalid Status in sysvinit source package in Xenial: Triaged Bug description: Hi, With the new Ubuntu archive servers, we saw constantly high load and after some tinkering, we found that it was mostly CPUs being woken up to see if they should enter idle states. Changing the CPU frequency scaling governor to "performance" saw a considerable drop. Perf report using the following commands: | perf record -g -a sleep 10 | perf report | Samples: 287K of event 'cycles:pp', Event count (approx.): 124776998906 | Children Self Command Shared Object Symbol | + 55.24% 0.20% swapper [kernel.kallsyms] [k] cpu_startup_entry | + 53.51% 0.00% swapper [kernel.kallsyms] [k] start_secondary | + 53.02% 0.08% swapper [kernel.kallsyms] [k] call_cpuidle | + 52.94% 0.02% swapper [kernel.kallsyms] [k] cpuidle_enter | + 31.81% 0.67% swapper [kernel.kallsyms] [k] cpuidle_enter_state | + 29.59% 0.12% swapper [kernel.kallsyms] [k] acpi_idle_enter | + 29.45% 0.05% swapper [kernel.kallsyms] [k] acpi_idle_do_entry | + 29.43%29.43% swapper [kernel.kallsyms] [k] acpi_processor_ffh_cstate_enter | + 20.51% 0.04% swapper [kernel.kallsyms] [k] ret_from_intr | + 20.47% 0.12% swapper [kernel.kallsyms] [k] do_IRQ | + 19.30% 0.07% swapper [kernel.kallsyms] [k] irq_exit | + 19.18% 0.07% apache2 [kernel.kallsyms] [k] entry_SYSCALL_64_fastpath | + 18.80% 0.17% swapper [kernel.kallsyms] [k] __do_softirq | + 16.45% 0.11% swapper [kernel.kallsyms] [k] net_rx_action | + 16.25% 0.43% swapper [kernel.kallsyms] [k] be_poll | + 14.74% 0.21% swapper [kernel.kallsyms] [k] be_process_rx | + 13.61% 0.07% swapper [kernel.kallsyms] [k] napi_gro_frags | + 12.58% 0.04% swapper [kernel.kallsyms] [k] netif_receive_skb_internal | + 12.48% 0.03% swapper [kernel.kallsyms] [k] __netif_receive_skb | + 12.42% 0.24% swapper [kernel.kallsyms] [k] __netif_receive_skb_core | + 12.41% 0.00% apache2 [unknown] [k] 0x7f27983b5028 | + 12.41% 0.00% apache2 [unknown] [k] 0x7f2798369028 | + 11.49% 0.16% swapper [kernel.kallsyms] [k] ip_rcv | + 11.29% 0.09% swapper [kernel.kallsyms] [k] ip_rcv_finish | + 10.77% 0.05% swapper [kernel.kallsyms] [k] ip_local_deliver | + 10.70% 0.06% swapper [kernel.kallsyms] [k] ip_local_deliver_finish | + 10.55% 0.22% swapper [kernel.kallsyms] [k] tcp_v4_rcv | + 10.10% 0.00% apache2 [unknown] [k] | + 10.01% 0.04% swapper [kernel.kallsyms] [k] tcp_v4_do_rcv Expanding in a few of those, you'll see: | - 55.24% 0.20% swapper [kernel.kallsyms] [k] cpu_startup_entry |- 55.04% cpu_startup_entry | - 52.98% call_cpuidle | + 52.93% cpuidle_enter | + 0.00% ret_from_intr |0.00% cpuidle_enter_state |0.00% irq_entries_start | + 1.14% cpuidle_select | + 0.47% schedule_preempt_disabled | 0.10% rcu_idle_enter | 0.09% rcu_idle_exit | + 0.05% ret_from_intr | + 0.05% tick_nohz_idle_enter | + 0.04% arch_cpu_idle_enter | 0.02% cpuidle_enter | 0.02% tick_check_broadcast_expired | + 0.01% cpuidle_reflect | 0.01% menu_reflect | 0.01% atomic_notifier_call_chain | 0.01% local_touch_nmi | 0.01% cpuidle_not_available | 0.01% menu_select | 0.01% cpuidle_get_cpu_driver | + 0.01% tick_nohz_idle_exit | + 0.01% sched_ttwu_pending | 0.00% set_cpu_sd_state_idle | 0.00%
[Touch-packages] [Bug 1598300] Re: cups hang after a while
What was in your /etc/cups/client.conf (now /etc/cups/client.conf_bak)? If it pointed to a CUPS on a remote machine, all your CUPS access (from applications/command line, not web interface) was directed to the remote machine with a different CUPS setup. Now you are using always the CUPS on your local machine. Note that client.conf is deprecated but still working as originally intended (and so often an admin's nightmare). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1598300 Title: cups hang after a while Status in cups package in Ubuntu: Confirmed Bug description: after 6 minutes or so, cups is not responding. it do not produce error on the log, just stop working, worse, it exit with 0 ⌌—⌍ |root@cupsmachine :~# systemctl status cups | |● cups.service - CUPS Scheduler | | Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: enabled)| | Active: inactive (dead) since ven. 2016-07-01 10:31:32 TAHT; 2min 16s ago | | Docs: man:cupsd(8) | | Process: 28686 ExecStart=/usr/sbin/cupsd -l (code=exited, status=0/SUCCESS)| | Main PID: 28686 (code=exited, status=0/SUCCESS) | | | |juil. 01 10:30:01 appli-client systemd[1]: Started CUPS Scheduler. | ⌎—⌏ I got to launch it again, so I have finish with a cron job like */10 * * * * systemctl status cups.service|grep -q 'inactive (dead)' && systemctl start cups but it is a dirty solution. I have no idea of what make it stop. NB: I have seen problems related to apparmor, this machine has no apparmor package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1598300/+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 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
This matches https://github.com/systemd/systemd/issues/3421 very closely (I've worked on this a bit, but it got stalled, sorry). I think that is the exact symptom you are seeing, can you confirm? ** Bug watch added: github.com/systemd/systemd/issues #3421 https://github.com/systemd/systemd/issues/3421 ** Also affects: systemd via https://github.com/systemd/systemd/issues/3421 Importance: Unknown Status: Unknown ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS Status in systemd: Unknown Status in systemd package in Ubuntu: Incomplete Bug description: I use a VPN configured with network-manager-openconnect-gnome in which a split-horizon DNS setup assigns different addresses to some names inside the remote network than the addresses seen for those names from outside the remote network. However, systemd-resolved often decides to ignore the VPN’s DNS servers and use the local network’s DNS servers to resolve names (whether in the remote domain or not), breaking the split-horizon DNS. This related bug, reported by Lennart Poettering himself, was closed with the current Fedora release at the time reaching EOL: https://bugzilla.redhat.com/show_bug.cgi?id=1151544 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+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 1624435] Re: systemd-udevd[409]: Process '/usr/sbin/alsactl -E HOME=/run/alsa restore 1' failed with exit code 99
** Description changed: This error is logged : systemd-udevd[409]: Process '/usr/sbin/alsactl -E HOME=/run/alsa restore 1' failed with exit code 99 note: sound works as expected when the GS session is opened; so maybe a boot race. - - but from a terminal, an other error is found: - /usr/sbin/alsactl: sysfs_init:48: sysfs path '/sys' is invalid - Details: oem@u64:~$ which alsactl /usr/sbin/alsactl oem@u64:~$ df -h /usr/sbin/alsactl Filesystem Size Used Avail Use% Mounted on /dev/sdb418G 11G 6.5G 62% / oem@u64:~$ df -h /run/alsa Filesystem Size Used Avail Use% Mounted on tmpfs 396M 12M 385M 3% /run (/run/alsa does not exist but /run/alsa/ which is an empty subdir) - - oem@u64:~$ /usr/sbin/alsactl restore - /usr/sbin/alsactl: state_lock:125: file /var/lib/alsa/asound.state lock error: File exists - /usr/sbin/alsactl: load_state:1683: Cannot open /var/lib/alsa/asound.state for reading: File exists - /usr/sbin/alsactl: sysfs_init:48: sysfs path '/sys' is invalid - Found hardware: "HDA-Intel" "Realtek ALC882" "HDA:10ec0882,1043e601,00100101" "0x1043" "0x81d8" Hardware is initialized using a generic method /usr/sbin/alsactl: sysfs_init:48: sysfs path '/sys' is invalid note: that command works: volume is set back to 50% from 100% initialy + + oem@u64:~$ sudo /usr/sbin/alsactl restore + [sudo] password for oem: + oem@u64:~$ + ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-utils 1.1.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-10.11-generic 4.8.0-rc6 Uname: Linux 4.8.0-10-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Sep 16 16:31:17 2016 SourcePackage: alsa-utils UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: This error is logged : systemd-udevd[409]: Process '/usr/sbin/alsactl -E HOME=/run/alsa restore 1' failed with exit code 99 note: sound works as expected when the GS session is opened; so maybe a - boot race. + booting race. Details: oem@u64:~$ which alsactl /usr/sbin/alsactl oem@u64:~$ df -h /usr/sbin/alsactl Filesystem Size Used Avail Use% Mounted on /dev/sdb418G 11G 6.5G 62% / oem@u64:~$ df -h /run/alsa Filesystem Size Used Avail Use% Mounted on tmpfs 396M 12M 385M 3% /run (/run/alsa does not exist but /run/alsa/ which is an empty subdir) Found hardware: "HDA-Intel" "Realtek ALC882" "HDA:10ec0882,1043e601,00100101" "0x1043" "0x81d8" Hardware is initialized using a generic method /usr/sbin/alsactl: sysfs_init:48: sysfs path '/sys' is invalid note: that command works: volume is set back to 50% from 100% initialy oem@u64:~$ sudo /usr/sbin/alsactl restore - [sudo] password for oem: - oem@u64:~$ - + [sudo] password for oem: + oem@u64:~$ ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-utils 1.1.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-10.11-generic 4.8.0-rc6 Uname: Linux 4.8.0-10-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Sep 16 16:31:17 2016 SourcePackage: alsa-utils UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: This error is logged : systemd-udevd[409]: Process '/usr/sbin/alsactl -E HOME=/run/alsa restore 1' failed with exit code 99 note: sound works as expected when the GS session is opened; so maybe a booting race. Details: oem@u64:~$ which alsactl /usr/sbin/alsactl oem@u64:~$ df -h /usr/sbin/alsactl Filesystem Size Used Avail Use% Mounted on /dev/sdb418G 11G 6.5G 62% / oem@u64:~$ df -h /run/alsa Filesystem Size Used Avail Use% Mounted on tmpfs 396M 12M 385M 3% /run (/run/alsa does not exist but /run/alsa/ which is an empty subdir) Found hardware: "HDA-Intel" "Realtek ALC882" "HDA:10ec0882,1043e601,00100101" "0x1043" "0x81d8" Hardware is initialized using a generic method - /usr/sbin/alsactl: sysfs_init:48: sysfs path '/sys' is invalid - - note: that command works: volume is set back to 50% from 100% initialy oem@u64:~$ sudo /usr/sbin/alsactl restore [sudo] password for oem: oem@u64:~$ + that command works: volume is set back to 50% from 100% initialy ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-utils 1.1.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-10.11-generic 4.8.0-rc6 Uname: Linux 4.8.0-10-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Sep 16 16:31:17 2016 SourcePackage: alsa-utils UpgradeStatus: No upgrade log present (probably fresh install) -- Yo
[Touch-packages] [Bug 1598300] Re: cups hang after a while
I have done some tests and have found a solution. Please try it out. Edit the file (with sudo): /lib/systemd/system/cups.socket adding a line ListenStream=631 in the "[Socket]" section. The file should look like this then: -- [Unit] Description=CUPS Scheduler [Socket] ListenStream=/var/run/cups/cups.sock ListenStream=631 [Install] WantedBy=sockets.target -- Now make sure that this does not produce any editor backup files, like /lib/systemd/system/cups.socket~ or /lib/systemd/system/cups.socket.backup. Remove such files now. Now restart systemd with the command sudo systemctl daemon-reload Now systemd does not only restart CUPS via the domain socket but also via port 631, meaning that it also gets started when trying to access via the web interface (or any other application which accesses only via port 631). Please try it out. If you do not want to wait everytime until CUPS stops by itself for doing the tests, you can stop it with sudo systemctl stop cups -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1598300 Title: cups hang after a while Status in cups package in Ubuntu: Confirmed Bug description: after 6 minutes or so, cups is not responding. it do not produce error on the log, just stop working, worse, it exit with 0 ⌌—⌍ |root@cupsmachine :~# systemctl status cups | |● cups.service - CUPS Scheduler | | Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: enabled)| | Active: inactive (dead) since ven. 2016-07-01 10:31:32 TAHT; 2min 16s ago | | Docs: man:cupsd(8) | | Process: 28686 ExecStart=/usr/sbin/cupsd -l (code=exited, status=0/SUCCESS)| | Main PID: 28686 (code=exited, status=0/SUCCESS) | | | |juil. 01 10:30:01 appli-client systemd[1]: Started CUPS Scheduler. | ⌎—⌏ I got to launch it again, so I have finish with a cron job like */10 * * * * systemctl status cups.service|grep -q 'inactive (dead)' && systemctl start cups but it is a dirty solution. I have no idea of what make it stop. NB: I have seen problems related to apparmor, this machine has no apparmor package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1598300/+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 1624407] Re: Closing an application doesn’t actually close it, it merely requests all its windows to be closed
AFAICS Mir has means to ask clients to close windows, but I don't see an API to ask the client itself to quit. ** No longer affects: unity (Ubuntu) ** Changed in: qtmir (Ubuntu) Status: New => Confirmed ** Changed in: qtmir (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1624407 Title: Closing an application doesn’t actually close it, it merely requests all its windows to be closed Status in qtmir package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: New Bug description: Currently in unity8, when requesting to "Quit" a running application from the launcher, what happens is that qtmir goes through all its associated windows/surfaces, and closes them one by one. Supposedly, when the last window is closed, the application terminates itself (but this is not necessarily the case, see https://doc.qt.io/qt-5/qguiapplication.html#quitOnLastWindowClosed- prop). This prevents application authors from doing proper cleanup before the app is closed. For example in Qt, the QCoreApplication::aboutToQuit() signal is emitted only after all windows have been closed, so the application doesn’t get a chance to e.g. save the list of open windows (real use case for multi-window browser application which saves the current session). This is similar to unity7’s implementation by the way, but I think it’s wrong. Surely there must be a way (maybe toolkit-specific) to request an app to terminate itself (and fall back to closing all windows if not). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtmir/+bug/1624407/+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
