[Touch-packages] [Bug 1638234] Re: package unattended-upgrades 0.90ubuntu0.1 failed to install/upgrade: subprocesso script post-installation instalado retornou erro do status de saída 10
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unattended-upgrades (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1638234 Title: package unattended-upgrades 0.90ubuntu0.1 failed to install/upgrade: subprocesso script post-installation instalado retornou erro do status de saída 10 Status in unattended-upgrades package in Ubuntu: Confirmed Bug description: yes ProblemType: Package DistroRelease: Ubuntu 16.04 Package: unattended-upgrades 0.90ubuntu0.1 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 .var.log.unattended-upgrades.unattended-upgrades.log: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Tue Nov 1 07:36:08 2016 ErrorMessage: subprocesso script post-installation instalado retornou erro do status de saída 10 InstallationDate: Installed on 2016-07-28 (95 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: unattended-upgrades Title: package unattended-upgrades 0.90ubuntu0.1 failed to install/upgrade: subprocesso script post-installation instalado retornou erro do status de saída 10 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apt.apt.conf.d.10periodic: APT::Periodic::Update-Package-Lists "1"; APT::Periodic::Download-Upgradeable-Packages "0"; APT::Periodic::AutocleanInterval "0"; APT::Periodic::Unattended-Upgrade "0"; mtime.conffile..etc.apt.apt.conf.d.10periodic: 2016-10-24T13:59:39.614980 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1638234/+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 1651818] Re: busybox-initramfs needs different compile options to work with cryptroot-unlock
This bug is still present in 17.10 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1651818 Title: busybox-initramfs needs different compile options to work with cryptroot-unlock Status in busybox package in Ubuntu: Confirmed Status in cryptsetup package in Ubuntu: Confirmed Bug description: The cryptroot-unlock script in the cryptsetup package does not work in initramfs. It fails because "ps -e" is not available in busybox for initramfs. When building the package with CONFIG_DESKTOP=y CONFIG_EXTRA_COMPAT=y the needed commands (ps, grep) with parameter are there and it works. Tetsted on Ubuntu GNOME 16.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1651818/+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 1651818] Re: busybox-initramfs needs different compile options to work with cryptroot-unlock
18.04 so far as well. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1651818 Title: busybox-initramfs needs different compile options to work with cryptroot-unlock Status in busybox package in Ubuntu: Confirmed Status in cryptsetup package in Ubuntu: Confirmed Bug description: The cryptroot-unlock script in the cryptsetup package does not work in initramfs. It fails because "ps -e" is not available in busybox for initramfs. When building the package with CONFIG_DESKTOP=y CONFIG_EXTRA_COMPAT=y the needed commands (ps, grep) with parameter are there and it works. Tetsted on Ubuntu GNOME 16.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1651818/+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 1651818] Re: busybox-initramfs needs different compile options to work with cryptroot-unlock
** Tags added: artful -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1651818 Title: busybox-initramfs needs different compile options to work with cryptroot-unlock Status in busybox package in Ubuntu: Confirmed Status in cryptsetup package in Ubuntu: Confirmed Bug description: The cryptroot-unlock script in the cryptsetup package does not work in initramfs. It fails because "ps -e" is not available in busybox for initramfs. When building the package with CONFIG_DESKTOP=y CONFIG_EXTRA_COMPAT=y the needed commands (ps, grep) with parameter are there and it works. Tetsted on Ubuntu GNOME 16.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1651818/+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 1735960] [NEW] Merge avahi 0.7 with Debian
Public bug reported: avahi 0.7 is in Debian. This merge is blocked by this FTBFS issue: https://bugs.debian.org/878911 https://bugs.debian.org/880036 ** Affects: avahi (Ubuntu) Importance: Wishlist Status: Triaged ** Tags: bionic patch upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1735960 Title: Merge avahi 0.7 with Debian Status in avahi package in Ubuntu: Triaged Bug description: avahi 0.7 is in Debian. This merge is blocked by this FTBFS issue: https://bugs.debian.org/878911 https://bugs.debian.org/880036 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1735960/+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 1735960] Re: Merge avahi 0.7 with Debian
Here's the merge I started on as a patch against the Debian package. ** Patch added: "WIP debdiff" https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1735960/+attachment/5017569/+files/0001-Add-udebs-corresponding-to-libavahi-common3-and-liba.patch ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1735960 Title: Merge avahi 0.7 with Debian Status in avahi package in Ubuntu: Triaged Bug description: avahi 0.7 is in Debian. This merge is blocked by this FTBFS issue: https://bugs.debian.org/878911 https://bugs.debian.org/880036 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1735960/+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 1689825] Re: gnome-keyring not unlocked on xenial when dbus-user-session is installed
Any update on this issue? I do not feel comfortable removing dbus-user- session as a workaround, and I have simply added --password-store=basic as an argument for Chromium/Chrome for now. However that is not completely suitable even though I only use Chromium/Chrome as a secondary browser, and I am wondering if this issue is still being looked into, and am inquiring for perhaps more details about it if anyone has any more details like if the maintainers/developers of dbus- user-session (whoever they may be?) are aware of this bug, etc. I am using Ubuntu 16.04 and Xfce 4.12 and the latest google-chrome-stable, chromium-browser, dbus-user-session, etc. I see someone has stated back in August that using Ubuntu 17.10 with Gnome shell and gdm still produces this issue, I wonder if this is still the case or if this issue has been fixed by now at least on Ubuntu 17.10? Also, on a side-note, does anyone know the exact details of what the password-store argument does? For example, if I turn password saving in Chromium off and don't use Google/Chrome sync, am I "safe" to log into websites without my passwords being stored in plain-text on my hard drive (even if temporary)? I may end up looking into Kwallet to see if this is a suitable alternative to GNOME keyring at least for Chromium. Thanks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1689825 Title: gnome-keyring not unlocked on xenial when dbus-user-session is installed Status in chromium-browser package in Ubuntu: Invalid Status in dbus package in Ubuntu: Triaged Status in flatpak package in Ubuntu: Fix Released Bug description: 1) Release: 16.04.2 2) gnome-keyring: 3.18.3-0ubuntu2 3) Login. gnome-keyring unlocks "login" features including for google chrome 4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no secure password features(sync) functioning. For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long time (maybe 2 minutes) to start. Once chrome is started, I am not able to sync and any secure password features are broken. I found out this is due to gnome-keyring not being unlocked at login. There's also no way to unlock the "login" portion of the keyring from the running daemon by default. I have to kill the gnome-keyring process and start without "--login" as a parameter. Then the "login" section shows up which I'm able to unlock. From there chrome starts up instantly but asks the following: Enter password to unlock your login keyring The login keyring did not get unlocked when you logged into your computer After that, all of it's sync and secure features are functional. Starting google-chrome-stable from a command line at boot without running the above workaround shows the following error messages: Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to decrypt token for service AccountId-108842767310111573264 [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore security token. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-keyring 3.18.3-0ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Wed May 10 09:43:37 2017 SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1689825/+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 1735895] Re: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume()
*** This bug is a duplicate of bug 1539209 *** https://bugs.launchpad.net/bugs/1539209 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1539209, so 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. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1735895/+attachment/5017339/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1735895/+attachment/5017342/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1735895/+attachment/5017345/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1735895/+attachment/5017346/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1735895/+attachment/5017348/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1735895/+attachment/5017349/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1735895/+attachment/5017350/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1539209 pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() from source_set_volume_cb() from pa_source_process_msg() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1735895 Title: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() Status in pulseaudio package in Ubuntu: New Bug description: i use:ubuntu 16.04.3LTS The sound is very loud and can not be dropped ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.4 ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-40-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: vietanh7695 F...m pulseaudio /dev/snd/controlC0: vietanh7695 F pulseaudio CrashCounter: 1 CurrentDesktop: Unity Date: Sat Dec 2 15:54:44 2017 EcryptfsInUse: Yes ExecutablePath: /usr/bin/pulseaudio ExecutableTimestamp: 1503491257 InstallationDate: Installed on 2017-12-02 (0 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog ProcCwd: / ProcEnviron: PATH=(custom, user) SHELL=/bin/bash LANG=vi_VN LANGUAGE=vi XDG_RUNTIME_DIR= Signal: 6 SourcePackage: pulseaudio StacktraceTop: pa_alsa_path_set_volume () from /usr/lib/pulse-8.0/modules/libalsa-util.so ?? () from /usr/lib/pulse-8.0/modules/libalsa-util.so pa_source_process_msg () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so ?? () from /usr/lib/pulse-8.0/modules/libalsa-util.so ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so Title: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 06/20/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 000XX0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd06/20/2017:svnDellInc.:pnInspiron3559:pvr:rvnDellInc.:rn000XX0:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 3559 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1735895/+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 1539209] Re: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() from source_set_volume_cb() from pa_source_process_msg()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu Zesty) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1539209 Title: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() from source_set_volume_cb() from pa_source_process_msg() Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Xenial: Confirmed Status in pulseaudio source package in Zesty: Confirmed Status in pulseaudio source package in Artful: Fix Released Bug description: https://errors.ubuntu.com/problem/49276ec9f717c5268dfc99940a28fb4a56fe1b4a --- [Impact] pulseaudio daemon crashes, interrupting sound output/input. [Test Case] Theoretical test case (crash does not happen for all users): 1. Find some headphones and/or microphone. Ensure you do not wear the headphones during the test as it may be loud. 2. Set audio output/input volumes to maximum. 3. Unplug and replug the headphones/microphone. 4. Check that that pulseaudio process is still running, with a start time older than when you began this test case. [Regression Potential] Low. This SRU affects the pulseaudio daemon only so the worst case would be loss of sound output/input. The same patches have been released to 17.10 for a month already and zero regressions of the crashes have occurred worldwide since then. [Original Description] Appears randomly. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:7.1-1ubuntu3 ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3 Uname: Linux 4.3.0-7-generic x86_64 ApportVersion: 2.19.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: potato12883 F...m pulseaudio /dev/snd/controlC0: potato12883 F pulseaudio /dev/snd/controlC1: potato12883 F pulseaudio CurrentDesktop: Unity Date: Thu Jan 28 22:16:03 2016 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2016-01-17 (11 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog ProcEnviron: PATH=(custom, no user) SHELL=/bin/bash LANG=ru_RU.UTF-8 LANGUAGE=ru XDG_RUNTIME_DIR= Signal: 6 SourcePackage: pulseaudio StacktraceTop: pa_alsa_path_set_volume () from /usr/lib/pulse-7.1/modules/libalsa-util.so ?? () from /usr/lib/pulse-7.1/modules/libalsa-util.so pa_source_process_msg () from /usr/lib/libpulsecore-7.1.so ?? () from /usr/lib/pulse-7.1/modules/libalsa-util.so ?? () from /usr/lib/libpulsecore-7.1.so Title: pulseaudio crashed with SIGABRT in pa_alsa_path_set_volume() UpgradeStatus: Upgraded to xenial on 2016-01-28 (0 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 12/07/2009 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: V1.11 dmi.board.name: JV71TR dmi.board.vendor: Acer dmi.board.version: Rev dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: None dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.11:bd12/07/2009:svnAcer:pnAspire7540:pvr0100:rvnAcer:rnJV71TR:rvrRev:cvnAcer:ct10:cvrNone: dmi.product.name: Aspire 7540 dmi.product.version: 0100 dmi.sys.vendor: Acer modified.conffile..etc.pulse.daemon.conf: [modified] mtime.conffile..etc.pulse.daemon.conf: 2016-01-25T21:44:07.089113 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1539209/+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 1168978] Re: Evince crashes consistently, reading 50+ pages into specific PDF document
** Bug watch added: freedesktop.org Bugzilla #103335 https://bugs.freedesktop.org/show_bug.cgi?id=103335 ** Also affects: cairo via https://bugs.freedesktop.org/show_bug.cgi?id=103335 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/1168978 Title: Evince crashes consistently, reading 50+ pages into specific PDF document Status in cairo: Unknown Status in cairo package in Ubuntu: Triaged Bug description: 1) lsb_release -rd Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 2) apt-cache policy evince libcairo2 libpoppler[0-9]evince: Installed: 3.14.1-0ubuntu1 Candidate: 3.14.1-0ubuntu1 Version table: *** 3.14.1-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status libcairo2: Installed: 1.13.0~20140204-0ubuntu1 Candidate: 1.13.0~20140204-0ubuntu1 Version table: *** 1.13.0~20140204-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status libpoppler47: Installed: 0.28.1-1ubuntu1 Candidate: 0.28.1-1ubuntu1 Version table: *** 0.28.1-1ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status 3) What is expected to happen via https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1168978/+attachment/3644236/+files/ICE1712-1.pdf is the entire document is viewable, as it is in Adobe Reader. 4) What happens instead is it consistently crashes after reading past page 61. WORKRAROUND: Use Firefox's built-in PDF viewer. Upstreamed to Evince who advised Cairo issue: https://bugzilla.gnome.org/show_bug.cgi?id=741945 https://bugs.freedesktop.org/show_bug.cgi?id=92517 https://bugs.freedesktop.org/show_bug.cgi?id=85141 ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: evince 3.6.1-1ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-18.12-lowlatency 3.8.6 Uname: Linux 3.8.0-18-lowlatency i686 ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 Date: Sun Apr 14 14:46:27 2013 InstallationDate: Installed on 2013-03-21 (24 days ago) InstallationMedia: Ubuntu-Studio 13.04 "Raring Ringtail" - Alpha i386 (20130321) KernLog: MarkForUpload: True SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/cairo/+bug/1168978/+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 1168978] Re: Evince crashes consistently, reading 50+ pages into specific PDF document
https://bugs.freedesktop.org/show_bug.cgi?id=85141#c8 says this is fixed upstream. There is following commit: https://cgit.freedesktop.org/cairo/commit/?id=5fd0b8710f125bb33c55d75fcc8252996b403e2d There you can find fixed bug with a patch: https://bugs.freedesktop.org/show_bug.cgi?id=103335 ** Bug watch added: freedesktop.org Bugzilla #85141 https://bugs.freedesktop.org/show_bug.cgi?id=85141 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/1168978 Title: Evince crashes consistently, reading 50+ pages into specific PDF document Status in cairo: Unknown Status in cairo package in Ubuntu: Triaged Bug description: 1) lsb_release -rd Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 2) apt-cache policy evince libcairo2 libpoppler[0-9]evince: Installed: 3.14.1-0ubuntu1 Candidate: 3.14.1-0ubuntu1 Version table: *** 3.14.1-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status libcairo2: Installed: 1.13.0~20140204-0ubuntu1 Candidate: 1.13.0~20140204-0ubuntu1 Version table: *** 1.13.0~20140204-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status libpoppler47: Installed: 0.28.1-1ubuntu1 Candidate: 0.28.1-1ubuntu1 Version table: *** 0.28.1-1ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status 3) What is expected to happen via https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1168978/+attachment/3644236/+files/ICE1712-1.pdf is the entire document is viewable, as it is in Adobe Reader. 4) What happens instead is it consistently crashes after reading past page 61. WORKRAROUND: Use Firefox's built-in PDF viewer. Upstreamed to Evince who advised Cairo issue: https://bugzilla.gnome.org/show_bug.cgi?id=741945 https://bugs.freedesktop.org/show_bug.cgi?id=92517 https://bugs.freedesktop.org/show_bug.cgi?id=85141 ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: evince 3.6.1-1ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-18.12-lowlatency 3.8.6 Uname: Linux 3.8.0-18-lowlatency i686 ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 Date: Sun Apr 14 14:46:27 2013 InstallationDate: Installed on 2013-03-21 (24 days ago) InstallationMedia: Ubuntu-Studio 13.04 "Raring Ringtail" - Alpha i386 (20130321) KernLog: MarkForUpload: True SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/cairo/+bug/1168978/+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 1733408] Re: package linux-image-4.10.0-40-generic 4.10.0-40.44 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1733408 Title: package linux-image-4.10.0-40-generic 4.10.0-40.44 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: Append when doing an upgrade... ProblemType: Package DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-40-generic 4.10.0-40.44 ProcVersionSignature: Ubuntu 4.10.0-38.42-generic 4.10.17 Uname: Linux 4.10.0-38-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.4-0ubuntu4.7 Architecture: amd64 Date: Mon Nov 20 20:49:10 2017 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=1e8fe466-94bf-4689-9d65-5efa77eea90a MachineType: LENOVO 30A0S0DK00 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-38-generic root=UUID=ebd53b4c-8011-4108-91a3-e8897f25ff5f ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2.2 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no SourcePackage: initramfs-tools Title: package linux-image-4.10.0-40-generic 4.10.0-40.44 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to zesty on 2017-11-11 (9 days ago) dmi.bios.date: 11/21/2016 dmi.bios.vendor: LENOVO dmi.bios.version: FBKTCCAUS dmi.board.name: SHARKBAY dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.type: 7 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnLENOVO:bvrFBKTCCAUS:bd11/21/2016:svnLENOVO:pn30A0S0DK00:pvrThinkStationE32:rvnLENOVO:rnSHARKBAY:rvrNODPK:cvnToBeFilledByO.E.M.:ct7:cvrToBeFilledByO.E.M.: dmi.product.name: 30A0S0DK00 dmi.product.version: ThinkStation E32 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1733408/+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 1734092] Re: Evince does not print hyphens in some PDF documents (cairo bug)
** Bug watch added: freedesktop.org Bugzilla #94615
https://bugs.freedesktop.org/show_bug.cgi?id=94615
** Also affects: cairo via
https://bugs.freedesktop.org/show_bug.cgi?id=94615
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cairo in Ubuntu.
https://bugs.launchpad.net/bugs/1734092
Title:
Evince does not print hyphens in some PDF documents (cairo bug)
Status in cairo:
Unknown
Status in cairo package in Ubuntu:
New
Bug description:
In some PDF files, characters like hyphen (minus sign) and others
symbols are not printed in Evince.
According to https://bugs.freedesktop.org/show_bug.cgi?id=94615, the
bug is in version 1.14 of cairo.
The bug was fixed last year in version 1.15 (see
https://cgit.freedesktop.org/cairo/commit/?id=190678f6444ad879847d603c3c9eaf8e9ab6887a).
I've backported the above patch in Ubuntu 16.04 xenial, and it fixes
the bug.
To reproduce the bug (see attached test files) in Ububtu 16.04 (with
libcairo2 1.14.6-1):
1. Create a LaTeX test document (test.tex) with the following content:
\documentclass{article}
\usepackage[T1]{fontenc}
\begin{document}
a-b---
\end{document}
2. Create a test.pdf from test.tex:
pdflatex test.tex
3. Create a cairo pdf output (or print test.pdf on a printer, using
Evince):
pdftocairo test.pdf -pdf test1.pdf
Open test1.pdf with Evince: as you can see, some of the hyphen signs
have disappeared.
To fix the bug, rebuild the cairo deb packages with the attached patch,
install the packages and do (or print test.pdf on a printer, using Evince):
pdftocairo test.pdf -pdf test2.pdf
Now, open test2.pdf with Evince: there is no more missing hyphen sign.
System: Ubuntu 16.04.3 LTS
Packages: libcairo2 (1.14.6-1)
To manage notifications about this bug go to:
https://bugs.launchpad.net/cairo/+bug/1734092/+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 1168978] Re: Evince crashes consistently, reading 50+ pages into specific PDF document
** Changed in: cairo Status: Unknown => Fix Released ** Changed in: cairo Importance: Unknown => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/1168978 Title: Evince crashes consistently, reading 50+ pages into specific PDF document Status in cairo: Fix Released Status in cairo package in Ubuntu: Triaged Bug description: 1) lsb_release -rd Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 2) apt-cache policy evince libcairo2 libpoppler[0-9]evince: Installed: 3.14.1-0ubuntu1 Candidate: 3.14.1-0ubuntu1 Version table: *** 3.14.1-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status libcairo2: Installed: 1.13.0~20140204-0ubuntu1 Candidate: 1.13.0~20140204-0ubuntu1 Version table: *** 1.13.0~20140204-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status libpoppler47: Installed: 0.28.1-1ubuntu1 Candidate: 0.28.1-1ubuntu1 Version table: *** 0.28.1-1ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status 3) What is expected to happen via https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1168978/+attachment/3644236/+files/ICE1712-1.pdf is the entire document is viewable, as it is in Adobe Reader. 4) What happens instead is it consistently crashes after reading past page 61. WORKRAROUND: Use Firefox's built-in PDF viewer. Upstreamed to Evince who advised Cairo issue: https://bugzilla.gnome.org/show_bug.cgi?id=741945 https://bugs.freedesktop.org/show_bug.cgi?id=92517 https://bugs.freedesktop.org/show_bug.cgi?id=85141 ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: evince 3.6.1-1ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-18.12-lowlatency 3.8.6 Uname: Linux 3.8.0-18-lowlatency i686 ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 Date: Sun Apr 14 14:46:27 2013 InstallationDate: Installed on 2013-03-21 (24 days ago) InstallationMedia: Ubuntu-Studio 13.04 "Raring Ringtail" - Alpha i386 (20130321) KernLog: MarkForUpload: True SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/cairo/+bug/1168978/+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 1734092] Re: Evince does not print hyphens in some PDF documents (cairo bug)
** Changed in: cairo
Status: Unknown => Fix Released
** Changed in: cairo
Importance: Unknown => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cairo in Ubuntu.
https://bugs.launchpad.net/bugs/1734092
Title:
Evince does not print hyphens in some PDF documents (cairo bug)
Status in cairo:
Fix Released
Status in cairo package in Ubuntu:
New
Bug description:
In some PDF files, characters like hyphen (minus sign) and others
symbols are not printed in Evince.
According to https://bugs.freedesktop.org/show_bug.cgi?id=94615, the
bug is in version 1.14 of cairo.
The bug was fixed last year in version 1.15 (see
https://cgit.freedesktop.org/cairo/commit/?id=190678f6444ad879847d603c3c9eaf8e9ab6887a).
I've backported the above patch in Ubuntu 16.04 xenial, and it fixes
the bug.
To reproduce the bug (see attached test files) in Ububtu 16.04 (with
libcairo2 1.14.6-1):
1. Create a LaTeX test document (test.tex) with the following content:
\documentclass{article}
\usepackage[T1]{fontenc}
\begin{document}
a-b---
\end{document}
2. Create a test.pdf from test.tex:
pdflatex test.tex
3. Create a cairo pdf output (or print test.pdf on a printer, using
Evince):
pdftocairo test.pdf -pdf test1.pdf
Open test1.pdf with Evince: as you can see, some of the hyphen signs
have disappeared.
To fix the bug, rebuild the cairo deb packages with the attached patch,
install the packages and do (or print test.pdf on a printer, using Evince):
pdftocairo test.pdf -pdf test2.pdf
Now, open test2.pdf with Evince: there is no more missing hyphen sign.
System: Ubuntu 16.04.3 LTS
Packages: libcairo2 (1.14.6-1)
To manage notifications about this bug go to:
https://bugs.launchpad.net/cairo/+bug/1734092/+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 1734106] Re: virtualbox crash after update 4.13.0-18 version
rg@rggr:~$ sudo modprobe vboxdrv
[sudo] Mot de passe de rg :
modprobe: FATAL: Module vboxdrv not found in directory
/lib/modules/4.13.0-18-generic
rg@rggr:~$
ERROR Message It is a modules problème !!! on 4.13.0-18 !!!
ok on 4.13.0-17
--
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/1734106
Title:
virtualbox crash after update 4.13.0-18 version
Status in apport package in Ubuntu:
New
Bug description:
An update to day : 4.13.0-18
virtualbox don't start prg
Échec de l'ouverture de session pour la machine virtuelle Android 7.1.
The virtual machine 'Android 7.1' has terminated unexpectedly during
startup with exit code 1 (0x1).
Code d'erreur : NS_ERROR_FAILURE (0x80004005)
Composant : MachineWrap
Interface : IMachine {b2547866-a0a1-4391-8b86-6952d82efaa0}
Good works on 4.13.0-17 version !
I had same problem with update from 4.13.0-16 to 4.13.0-17
It seems to be a problem with kernel
where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The
support driver is not installed. On linux, open returned ENOENT.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1734106/+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 1722108] Re: Sections of screen flashing, window shadows flashing, corruption
This problem seems to have been fixed in 17.10 under X11. ** Summary changed: - Sections of screen flashing, window shadows flashing, corruption + Sections of screen flashing, window shadows flashing, corruption, with extended desktop ** Description changed: + Whenever I use an extended desktop with my large monitor above my laptop + screen, there is corruption and frequent flash-to-black of the large + monitor. It seems to occur especially when a terminal window changes + output/scrolls up / etc. + Video and stills attached ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 .tmp.unity_support_test.0: - + ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 BootLog: /dev/sda4: clean, 357470/1831424 files, 3194597/7324160 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7 Date: Sun Oct 8 14:43:58 2017 DistUpgraded: Fresh install DistroCodename: zesty DistroVariant: ubuntu DkmsStatus: - virtualbox, 5.1.22, 4.10.0-33-generic, x86_64: installed - virtualbox, 5.1.22, 4.10.0-35-generic, x86_64: installed + virtualbox, 5.1.22, 4.10.0-33-generic, x86_64: installed + virtualbox, 5.1.22, 4.10.0-35-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: - Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) -Subsystem: Lenovo HD Graphics 5500 [17aa:5036] + Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) + Subsystem: Lenovo HD Graphics 5500 [17aa:5036] InstallationDate: Installed on 2017-06-16 (113 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 20BXCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic.efi.signed root=UUID=06040eea-70ae-4f11-8f45-6cde7f56eb77 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/06/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JBET54WW (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET54WW(1.19):bd11/06/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BXCTO1WW dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.17.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.17.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1 xserver.bootTime: Sun Oct 8 14:40:09 2017 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1.1 xserver.video_driver: modeset ** Description changed: Whenever I use an extended desktop with my large monitor above my laptop screen, there is corruption and frequent flash-to-black of the large monitor. It seems to occur especially when a terminal window changes - output/scrolls up / etc. + output/scrolls up / etc.' + In addition, there is much more exterme corruption when I press super-S (or whatever) to see my four desktops, and I move a window around. Video and stills attached ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 BootLog: /dev/sda4: clean, 357470/1831424 files, 3194597/7324160 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7 Date: Sun Oct 8 14:43:58 2017 DistUpgraded: Fresh install DistroCodename: zesty DistroVariant: ubuntu Dk
[Touch-packages] [Bug 1686759] Re: apparmor denies sendmsg to /run/systemd/journal/socket
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: telepathy-mission-control-5 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telepathy-mission- control-5 in Ubuntu. https://bugs.launchpad.net/bugs/1686759 Title: apparmor denies sendmsg to /run/systemd/journal/socket Status in telepathy-mission-control-5 package in Ubuntu: Confirmed Bug description: While debugging why Polari can no longer connect to IRC servers after an upgrade to Ubuntu 17.04, I noticed the following errors in my journal: Bal 27 18:05:56 platonas audit[4869]: AVC apparmor="DENIED" operation="sendmsg" profile="/usr/lib/telepathy/mission-control-5" name="/run/systemd/journal/socket" pid=4869 comm="mission-control" requested_mask="w" denied_mask="w" fsuid=1000 ouid=0 (repeated many times) I also see Bal 27 18:05:56 platonas mission-control-5[4869]: (process:4869): mcd-WARNING **: got error: Account idle/irc/mgedmin0 disconnected with reason 3 so somehow log messages from mission-control-5 still make it, despite the denied journal connection (via syslog maybe?). ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: telepathy-mission-control-5 1:5.16.3-2.1ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Apr 27 18:16:08 2017 InstallationDate: Installed on 2016-09-10 (229 days ago) InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) SourcePackage: telepathy-mission-control-5 UpgradeStatus: Upgraded to zesty on 2017-04-14 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1686759/+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 1728791] Re: [SRU] pulseaudio-droid module crashes on start
(it turned out I forgot to mark this as verification-done-xenial) adding tag. ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1728791 Title: [SRU] pulseaudio-droid module crashes on start Status in pulseaudio package in Ubuntu: Fix Committed Bug description: Ubuntu 16.04 Xenial, and pulseaudio version 8.0-0ubuntu3.4 [Impact] * This bug prevents users (currently Project Halium, UBports, Plasma Mobile) from using the pulseaudio-modules-droid on android devices. * This behavior can be seen in Ubuntu Xenial 16.04 with xenial-updates enabled. * Last 3 releases of pulseaudio included multiple patches which modified behavior of pulsecore library but required changes were not made in pulseaudio-module-droid. * This results in crash in pulseaudio-modules-droid #0 init_profile (u=0x59528) at modules/droid/module-droid-card.c:370 #1 module_droid_card_22_LTX_pa__init (m=0x3c3f8) at modules/droid/module-droid-card.c:923 #2 0xf76feb88 in pa_module_load (c=c@entry=0x33a80, name=name@entry=0x58240 "module-droid-card-22", argument=0x0) at pulsecore/module.c:180 #3 0xf76f1d7e in pa_cli_command_load (c=0x33a80, t=0x49320, buf=0x44f28, fail=0x3c1f4) at pulsecore/cli-command.c:439 #4 0xf76f6ad8 in pa_cli_command_execute_line_stateful (c=0x33a80, s=s@entry=0x59120 "load-module module-droid-card-22", buf=buf@entry=0x44f28, fail=fail@entry=0x3c1f4, ifstate=ifstate@entry=0x0) at pulsecore/cli-command.c:2134 #5 0xf76f6fc8 in pa_cli_command_execute_line (c=, s=s@entry=0x59120 "load-module module-droid-card-22", buf=buf@entry=0x44f28, fail=fail@entry=0x3c1f4) at pulsecore/cli-command.c:2155 #6 0xee32fc82 in line_callback (line=0x3c208, s=0x59120 "load-module module-droid-card-22", userdata=0x3c1e0) at pulsecore/cli.c:153 #7 0xf76a1360 in scan_for_lines (skip=, l=0x3c208) at pulsecore/ioline.c:269 #8 do_read (l=0x3c208) at pulsecore/ioline.c:337 #9 do_work (l=0x3c208) at pulsecore/ioline.c:386 #10 0xf7655fa6 in dispatch_pollfds (m=0x32bd0) at pulse/mainloop.c:655 #11 pa_mainloop_dispatch (m=m@entry=0x32bd0) at pulse/mainloop.c:898 #12 0xf765629a in pa_mainloop_iterate (m=0x32bd0, block=, retval=0xfffef1c4) at pulse/mainloop.c:929 #13 0xf7656314 in pa_mainloop_run (m=m@entry=0x32bd0, retval=retval@entry=0xfffef1c4) at pulse/mainloop.c:944 #14 0x000158ca in main (argc=, argv=) at daemon/main.c:1152 [Test Case] * Start pulseaudio * From another session run pacmd * In prompt type load-module module-droid-discover * On ubuntu touch devices, it will crash at startup [Regression Potential] * There is no regression potential for other parts of pulseaudio components. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1728791/+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 1735932] [NEW] package util-linux 2.30.2-0.1ubuntu1 failed to install/upgrade: installed util-linux package post-installation script subprocess returned error exit status 1
Public bug reported: Ran sudo do-release-upgrade -d. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: util-linux 2.30.2-0.1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95 Uname: Linux 4.4.0-101-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 Date: Sat Dec 2 17:48:12 2017 ErrorMessage: installed util-linux package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2016-08-08 (481 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.19.0.4ubuntu1 apt 1.2.24 SourcePackage: util-linux Title: package util-linux 2.30.2-0.1ubuntu1 failed to install/upgrade: installed util-linux package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2017-12-02 (0 days ago) ** Affects: util-linux (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 util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1735932 Title: package util-linux 2.30.2-0.1ubuntu1 failed to install/upgrade: installed util-linux package post-installation script subprocess returned error exit status 1 Status in util-linux package in Ubuntu: New Bug description: Ran sudo do-release-upgrade -d. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: util-linux 2.30.2-0.1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95 Uname: Linux 4.4.0-101-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 Date: Sat Dec 2 17:48:12 2017 ErrorMessage: installed util-linux package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2016-08-08 (481 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.19.0.4ubuntu1 apt 1.2.24 SourcePackage: util-linux Title: package util-linux 2.30.2-0.1ubuntu1 failed to install/upgrade: installed util-linux package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2017-12-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1735932/+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 1735934] [NEW] cron starts twice
Public bug reported: A fresh Ubuntu 16.04 server install... cron starts twice every boot. It has been running for a while but I have made no changes to cron since the fresh install, other than installing some crontabs. The first cron show systemd as its parent. The second cron shows Upstart as its parent. To work around I have disable the Upstart process: $ sudo update-rc.d cron disable This results in some jobs running around 30 times, I assume due to some sort of race condition between the two crons. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: cron 3.0pl1-128ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-17.20~16.04.1-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 Date: Sat Dec 2 18:30:05 2017 InstallationDate: Installed on 2016-08-13 (476 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: cron UpgradeStatus: No upgrade log present (probably fresh install) upstart.cron.override: manual ** Affects: cron (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cron in Ubuntu. https://bugs.launchpad.net/bugs/1735934 Title: cron starts twice Status in cron package in Ubuntu: New Bug description: A fresh Ubuntu 16.04 server install... cron starts twice every boot. It has been running for a while but I have made no changes to cron since the fresh install, other than installing some crontabs. The first cron show systemd as its parent. The second cron shows Upstart as its parent. To work around I have disable the Upstart process: $ sudo update-rc.d cron disable This results in some jobs running around 30 times, I assume due to some sort of race condition between the two crons. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: cron 3.0pl1-128ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-17.20~16.04.1-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 Date: Sat Dec 2 18:30:05 2017 InstallationDate: Installed on 2016-08-13 (476 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: cron UpgradeStatus: No upgrade log present (probably fresh install) upstart.cron.override: manual To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1735934/+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 1731981] Re: Please merge sudo (main) 1.8.21p2-2 from Debian unstable (main)
This bug was fixed in the package sudo - 1.8.21p2-2ubuntu1 --- sudo (1.8.21p2-2ubuntu1) bionic; urgency=medium * Merge from Debian unstable. (LP: #1731981) Remaining changes: - debian/rules, debian/sudo.service, debian/sudo.sudo.init: stop shipping init script and service file, as they are no longer necessary. - debian/rules: + compile with --without-lecture --with-tty-tickets --enable-admin-flag + install man/man8/sudo_root.8 in both flavours + install apport hooks - debian/source_sudo.py, debian/sudo-ldap.dirs, debian/sudo.dirs: + add usr/share/apport/package-hooks - debian/sudo.pam: + Use pam_env to read /etc/environment and /etc/default/locale environment files. Reading ~/.pam_environment is not permitted due to security reasons. - debian/sudoers: + also grant admin group sudo access + include /snap/bin in the secure_path - debian/control, debian/rules: + use dh-autoreconf - Remaining patches: + keep_home_by_default.patch: Keep HOME in the default environment Dropped changes since they are integrated in Debian: - Use tmpfs location to store timestamp files + debian/rules: change --with-rundir to /var/run/sudo + debian/*.preinst, debian/*.postinst, debian/*.postrm: remove old init script with dpkg-maintscript-helper. Dropped changes since the the transition took place already in every release the package can be upgraded from: + debian/*.postinst: remove old /var/run/sudo to /var/lib/sudo transition code, remove old /var/lib/sudo/ts timestamp directory. * Refresh patches sudo (1.8.21p2-2) unstable; urgency=medium * work harder to clean up mess left by sudo-ldap using /etc/init.d/sudo prior to version 1.8.7-1, closes: #877516 sudo (1.8.21p2-1) unstable; urgency=medium * new upstream version, closes: #873623, #873600, #874000 * remove legacy /etc/sudoers.dist we no longer deliver, closes: #873561 sudo (1.8.21-1) unstable; urgency=medium [ Bdale Garbee ] * new upstream version * don't deliver /etc/sudoers.dist, closes: #862309 * whitelist DPKG_COLORS env var, closes: #823368 [ Laurent Bigonville ] * debian/sudo*.postinst: Drop /var/run/sudo -> /var/lib/sudo migration code, this migration happened in 2010 and that code is not necessary anymore * Move timestamp files to /run/sudo, with systemd the directory is created/cleaned by tmpfiles.d now, the sudo initscript/service is not doing anything in that case anymore (Closes: #786555) * debian/sudo*.postinst: Move the debhelper marker before the creation of the sudo group, this way the snippets added by debhelper will be executed even if the group already exists. (Closes: #870456) -- Balint Reczey Mon, 13 Nov 2017 17:53:45 +0100 ** Changed in: sudo (Ubuntu) Status: Confirmed => Fix Released -- 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/1731981 Title: Please merge sudo (main) 1.8.21p2-2 from Debian unstable (main) Status in sudo package in Ubuntu: Fix Released Bug description: Changes: sudo (1.8.21p2-2ubuntu1) bionic; urgency=medium . * Merge from Debian unstable. (LP: #1731981) Remaining changes: - debian/rules, debian/sudo.service, debian/sudo.sudo.init: stop shipping init script and service file, as they are no longer necessary. - debian/rules: + compile with --without-lecture --with-tty-tickets --enable-admin-flag + install man/man8/sudo_root.8 in both flavours + install apport hooks - debian/source_sudo.py, debian/sudo-ldap.dirs, debian/sudo.dirs: + add usr/share/apport/package-hooks - debian/sudo.pam: + Use pam_env to read /etc/environment and /etc/default/locale environment files. Reading ~/.pam_environment is not permitted due to security reasons. - debian/sudoers: + also grant admin group sudo access + include /snap/bin in the secure_path - debian/control, debian/rules: + use dh-autoreconf - Remaining patches: + keep_home_by_default.patch: Keep HOME in the default environment Dropped changes since they are integrated in Debian: - Use tmpfs location to store timestamp files + debian/rules: change --with-rundir to /var/run/sudo + debian/*.preinst, debian/*.postinst, debian/*.postrm: remove old init script with dpkg-maintscript-helper. Dropped changes since the the transition took place already in every release the package can be upgraded from: + debian/*.postinst: remove old /var/run/sudo to /var/lib/sudo transition code, remove old /var/lib/sudo/ts timestamp directory. * Refresh patches . sudo (1.8.21p2-2) unstab
[Touch-packages] [Bug 1243484] Re: Incorrect handling of orientation when printing PDF files
the problem deals with the PRINTER DRIVER. SO I report the same bug affecting Kubuntu 17.04 and Brother MFC-L2700DW series with driverless cups filter 1.13. The problem is that the driver is not good. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1243484 Title: Incorrect handling of orientation when printing PDF files Status in CUPS: Confirmed Status in Poppler: Fix Released Status in cups-filters package in Ubuntu: Fix Released Status in poppler package in Ubuntu: Fix Released Bug description: There seems to be some problems in the CUPS filters handling PDF files, which can be shown without having an actual printer hooked up (this seems to be independent of the driver in use). This happens on the latest Ubuntu 13.10 but I believe the real culprit is in the cups-filters 1.0.40 package. This happens when trying to print a PDF file (such as the CUPS test page in /usr/share/cups/data/default.pdf) and trying to change its orientation with the 'landscape' option, as such : lp -d queue -o landscape /usr/share/cups/data/default.pdf The result right now would be that the job is upside down, instead of being in a landscape orientation. This happens regardless of the driver. The same behavior doesn't happen for documents such as PostScript files, which works as expected, at least with a PS printer. The easiest way to test this is to set up queues that print to file (enable FileDevice in the CUPS config first) and look at the resulting files with a document viewer such as evince : - Create a new Generic Postscript queue using the default drivers, set it to print to a URI such as file:///tmp/test.ps - Send a PDF job to the queue with the landscape option - Look at the output in evince or Ghostview I strongly suspect something is amiss with the pdftopdf filter's handling of these options, especially in v1.0.40. Fedora 19 didn't exhibit the same problem until the cups-filters package was brought up to the same version just today. I also suspect that more than the orientation options are affected, we have had reports from customers having trouble with options handled through the Collate PPD options. To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1243484/+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 1735594] Re: ubuntu automatically logs out when hovering sidebar
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nux in Ubuntu. https://bugs.launchpad.net/bugs/1735594 Title: ubuntu automatically logs out when hovering sidebar Status in nux package in Ubuntu: Confirmed Bug description: When I use the Unity session I automatically get logged out under these conditions: When I hover with my mouse over the sidebar or the top-bar. When I press the alt+tab combination. When I press the super key. running dmesg after this unwanted logout happens I get following information: compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0 error 4 in i965_dri.so[7fbca2af6000+7e4000] When I log in the first thing I see is an error message showing something like this: Could not apply the configuration stored for the monitors required virtual size does not fit available size: requested=(1,1),minimum=(320,200),maximum=(8192,8192) Sometimes this appears twice. The info about my installed compiz: compiz: Instal·lat: 1:0.9.13.1+17.10.20170901-0ubuntu1 Candidat: 1:0.9.13.1+17.10.20170901-0ubuntu1 Taula de versió: *** 1:0.9.13.1+17.10.20170901-0ubuntu1 500 500 http://es.archive.ubuntu.com/ubuntu artful/universe amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu artful/universe i386 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1735594/+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 1735941] [NEW] no stereo on reconnect or by default for Sony 1000xm2 headphones
Public bug reported: Expectation: Bluetooth headphones attach with stereo sound on every connect. Issue: only stereo after manual switch of settings on first pair. Reconnect only has mono connection. Ubuntu 17.10 on a System76 Serval WS. Mono audio with the Sony 1000XM2 bluetooth headphones is the default on first pairing and is the only option after turning off the bluetooth or headphones. On a new pairing the default is HSP with mono audio. Manually I have to change to A2DP in the sound settings and I am able to have stereo sound. Disabling bluetooth or turning off the headphones followed by a connection will result in mono audio in HSP and switching to A2DP will also be mono. Temporary Workaround: remove the headphones from the paired devices and pair again as a new device to get access to stereo sound again. This procedure has to be repeated on every reconnect. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: bluez 5.46-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Dec 2 14:54:12 2017 EcryptfsInUse: Yes InterestingModules: rfcomm bnep btusb bluetooth MachineType: System76, Inc. Serval WS ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic.efi.signed root=UUID=90a6c4ca-5b2a-461e-8792-18cd7e54a2fb ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/08/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.10RSA dmi.board.asset.tag: Tag 12345 dmi.board.name: Serval WS dmi.board.vendor: System76, Inc. dmi.board.version: serw9 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.10RSA:bd03/08/2016:svnSystem76,Inc.:pnServalWS:pvrserw9:rvnSystem76,Inc.:rnServalWS:rvrserw9:cvnSystem76,Inc.:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Serval WS dmi.product.version: serw9 dmi.sys.vendor: System76, Inc. hciconfig: hci0: Type: Primary Bus: USB BD Address: 44:85:00:36:47:F9 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN INQUIRY RX bytes:18865088 acl:249 sco:362504 events:45487 errors:0 TX bytes:53430737 acl:40447 sco:362442 commands:2995 errors:9 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- 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/1735941 Title: no stereo on reconnect or by default for Sony 1000xm2 headphones Status in bluez package in Ubuntu: New Bug description: Expectation: Bluetooth headphones attach with stereo sound on every connect. Issue: only stereo after manual switch of settings on first pair. Reconnect only has mono connection. Ubuntu 17.10 on a System76 Serval WS. Mono audio with the Sony 1000XM2 bluetooth headphones is the default on first pairing and is the only option after turning off the bluetooth or headphones. On a new pairing the default is HSP with mono audio. Manually I have to change to A2DP in the sound settings and I am able to have stereo sound. Disabling bluetooth or turning off the headphones followed by a connection will result in mono audio in HSP and switching to A2DP will also be mono. Temporary Workaround: remove the headphones from the paired devices and pair again as a new device to get access to stereo sound again. This procedure has to be repeated on every reconnect. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: bluez 5.46-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Dec 2 14:54:12 2017 EcryptfsInUse: Yes InterestingModules: rfcomm bnep btusb bluetooth MachineType: System76, Inc. Serval WS ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic.efi.signed root=UUID=90a6c4ca-5b2a-461e-8792-18cd7e54a2fb ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/08/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.10RSA dmi.board.asset.tag: Tag 12345 dmi.board.name: Serval WS dmi.board.vendor: System76, Inc. dmi.board.version: serw9 dmi.chassis.asset.tag
[Touch-packages] [Bug 1735594] Re: ubuntu automatically logs out when hovering sidebar
Ubuntu 17.10 When I use the Unity session I automatically get logged out ot I get a crash of unity under this condition: When I hover with my mouse over the sidebar I can use the top bar without problems instead. I upgraded to latest packages today. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nux in Ubuntu. https://bugs.launchpad.net/bugs/1735594 Title: ubuntu automatically logs out when hovering sidebar Status in nux package in Ubuntu: Confirmed Bug description: When I use the Unity session I automatically get logged out under these conditions: When I hover with my mouse over the sidebar or the top-bar. When I press the alt+tab combination. When I press the super key. running dmesg after this unwanted logout happens I get following information: compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0 error 4 in i965_dri.so[7fbca2af6000+7e4000] When I log in the first thing I see is an error message showing something like this: Could not apply the configuration stored for the monitors required virtual size does not fit available size: requested=(1,1),minimum=(320,200),maximum=(8192,8192) Sometimes this appears twice. The info about my installed compiz: compiz: Instal·lat: 1:0.9.13.1+17.10.20170901-0ubuntu1 Candidat: 1:0.9.13.1+17.10.20170901-0ubuntu1 Taula de versió: *** 1:0.9.13.1+17.10.20170901-0ubuntu1 500 500 http://es.archive.ubuntu.com/ubuntu artful/universe amd64 Packages 500 http://es.archive.ubuntu.com/ubuntu artful/universe i386 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1735594/+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 1721704] Re: Printer settings stuck on loading drivers database
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-settings (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1721704 Title: Printer settings stuck on loading drivers database Status in ubuntu-settings package in Ubuntu: Confirmed Bug description: 1) Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 2) ubuntu-settings: Installed: 17.10.17 Candidate: 17.10.17 3) The printer configuration goes fine and I can print 4) Printer settings stuck on loading drivers database and finally no drivers list available. Only 'cancel' button active. Note: I'm trying to configure a Brother HL-2030 connected to Network through a FritzBox 7940 router. The printer works fine both on Fedora and macOS X systems. I opened 'System Settings', then select 'Devices' > 'Printers' > 'Add a Printer'. I entered the router address and the window shows me correctly a 'JetDirect-Printer' on 192.168.178.1. I selected the printer and pressed the 'Add' button, a window 'Select Printer Driver' appears and stuck with 'Loading drivers database...'. After about 2 minutes, stopped loading and remains blank. No drivers selection is available and I can only push the 'Cancel' button. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1721704/+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 1733002] Re: Google Online Account Two Factor with hardware key fails immediately
I believe I added the appropriate bugwatch to the upstream report: https://bugzilla.gnome.org/show_bug.cgi?id=791144 ** Bug watch added: GNOME Bug Tracker #791144 https://bugzilla.gnome.org/show_bug.cgi?id=791144 ** Also affects: gnome-online-accounts via https://bugzilla.gnome.org/show_bug.cgi?id=791144 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1733002 Title: Google Online Account Two Factor with hardware key fails immediately Status in gnome-online-accounts: Unknown Status in gnome-online-accounts package in Ubuntu: New Bug description: The hardware key authentication two factor fails immediately with a web based retry dialogue when connecting a Google account to the online accounts in settings using a hardware key second factor. Steps to reproduce: 1. Set Google Account to default to a hardware security key like a Yubikey or other FIDO standard key after having two factor authentication enabled on your Google Account. 2. Open Online accounts 3. Add a Google Account 4. Enter google email address 5. Enter google password 6. (this is the login flow of two factor, if default is the hardware key the error should appear). Work around: Choose use another method to authenticate: enter the authentication code and you will proceed. Expectations were: The ability to use the hardware key to authenticate as the second factor. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.1-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4 Uname: Linux 4.13.0-16-lowlatency x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 17 16:01:11 2017 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-control-center ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash PATH=(custom, user) LANG=en_US.UTF-8 SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1733002/+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 1735945] [NEW] Brightness control not working
Public bug reported: Brightness control not working ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-40-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Dec 2 17:53:21 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:3904] InstallationDate: Installed on 2017-11-30 (1 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: LENOVO 20211 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-40-generic.efi.signed root=UUID=101a39ce-07bc-4b02-87e9-77428c23bae1 ro quiet splash acpi_backlight=vendor vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/10/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 71CN45WW(V1.18) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad P400 Touch dmi.modalias: dmi:bvnLENOVO:bvr71CN45WW(V1.18):bd05/10/2013:svnLENOVO:pn20211:pvrLenovoIdeaPadP400Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadP400Touch: dmi.product.name: 20211 dmi.product.version: Lenovo IdeaPad P400 Touch dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sat Dec 2 16:42:49 2017 xserver.configfile: default xserver.errors: intel(0): Unrecognised backlight control interface 'ideapad' xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id8254 vendor AUO xserver.version: 2:1.19.3-1ubuntu1~16.04.4 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- 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/1735945 Title: Brightness control not working Status in xorg package in Ubuntu: New Bug description: Brightness control not working ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-40-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Dec 2 17:53:21 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:3904] InstallationDate: Installed on 2017-11-30 (1 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: LENOVO 20211 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-40-generic.efi.signed root=UUID=101a39ce-07bc-4b02-87e9-77428c23bae1 ro quiet splash acpi_backlight=vendor vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/10/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 71CN45WW(V1.18) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LEN
[Touch-packages] [Bug 1733002] Re: Google Online Account Two Factor with hardware key fails immediately
** Changed in: gnome-online-accounts Status: Unknown => Confirmed ** Changed in: gnome-online-accounts Importance: Unknown => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1733002 Title: Google Online Account Two Factor with hardware key fails immediately Status in gnome-online-accounts: Confirmed Status in gnome-online-accounts package in Ubuntu: New Bug description: The hardware key authentication two factor fails immediately with a web based retry dialogue when connecting a Google account to the online accounts in settings using a hardware key second factor. Steps to reproduce: 1. Set Google Account to default to a hardware security key like a Yubikey or other FIDO standard key after having two factor authentication enabled on your Google Account. 2. Open Online accounts 3. Add a Google Account 4. Enter google email address 5. Enter google password 6. (this is the login flow of two factor, if default is the hardware key the error should appear). Work around: Choose use another method to authenticate: enter the authentication code and you will proceed. Expectations were: The ability to use the hardware key to authenticate as the second factor. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.1-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4 Uname: Linux 4.13.0-16-lowlatency x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 17 16:01:11 2017 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-control-center ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash PATH=(custom, user) LANG=en_US.UTF-8 SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1733002/+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 1729145] Re: /dev/bcache/by-uuid links not created after reboot
** Tags removed: kernel-da-key ** Tags added: kernel-key -- 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/1729145 Title: /dev/bcache/by-uuid links not created after reboot Status in linux package in Ubuntu: Triaged Status in systemd package in Ubuntu: New Status in linux source package in Xenial: Triaged Status in systemd source package in Xenial: New Status in linux source package in Zesty: Triaged Status in systemd source package in Zesty: New Status in linux source package in Artful: Triaged Status in systemd source package in Artful: New Status in linux source package in Bionic: Triaged Status in systemd source package in Bionic: New Bug description: 1. $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 2. $ apt-cache policy linux-image-`uname -r` linux-image-4.13.0-16-generic: Installed: 4.13.0-16.19 Candidate: 4.13.0-16.19 Version table: *** 4.13.0-16.19 500 500 http://nova.clouds.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status 3. After creating some bcache devices and rebooting /dev/bcache/by-uuid/ -> ../../bcacheN symlinks point to the current bcache device which is caching the dev.uuid found after creating a backing device. 4. /dev/bcache/by-uuid does not exist and there are not symlinks underneath It appears that since the initramfs loads the bcache module which probes and finds all of the cache devices and backing devices then once the rootfs is mounted and udev gets to run, the bcache kernel module does not emit the CACHED_UUID value into the environment if the underlying devices are already registered. In dmesg, one can see that prior to mounting the rootfs, we see bcache register events: [5.333973] bcache: register_bdev() registered backing device vdb2 [5.354138] bcache: register_bdev() registered backing device vdb4 [5.365665] bcache: register_bdev() registered backing device vdb3 [5.397720] bcache: bch_journal_replay() journal replay done, 0 keys in 1 entries, seq 1 [5.428683] bcache: register_cache() registered cache device vdb1 then rootfs ismounted and systemd starts systemd-udev [9.350889] systemd[1]: Listening on udev Kernel Socket. And then the coldplug replay of kernel events triggers /lib/udev/rules.d/69-bcache.rules which invokes /lib/udev/bcache-register which writes the device name (/dev/vdb1 or /dev/bcache0) into /sys/fs/bcache/register and results is the bcache kernel driver attempting to register the block device. However, there is already a bcache device associated already and registration fails [ 11.173141] bcache: register_bcache() error opening /dev/vdb2: device already registered [ 11.184617] bcache: register_bcache() error opening /dev/vdb3: device already registered [ 11.199130] bcache: register_bcache() error opening /dev/vdb1: device already registered [ 11.271694] bcache: register_bcache() error opening /dev/vdb4: device already registered The problem then is that only a kernel call to bch_cached_dev_run() which happens like this: bcache_register() register_bdev() bch_cached_dev_run() kobject_uevent_env(&disk_to_dev(d->disk)->kobj, KOBJ_CHANGE, env); where env includes: "DRIVER=bcache", kasprintf(GFP_KERNEL, "CACHED_UUID=%pU", dc->sb.uuid), NULL, NULL, }; Since that event is not emitted for any previously registered device, then the symlink will not be created. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: User Name 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 31 22:09 seq crw-rw 1 root audio 116, 33 Oct 31 22:09 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Wed Nov 1 01:39:01 2017 Ec2AMI: ami-030b Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: OpenStack Foundation OpenStack Nova PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/b
[Touch-packages] [Bug 1613184] Re: method mirror broken at 1.3
Confirmed Verified on zesty using version 1.4.8 Jarl -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1613184 Title: method mirror broken at 1.3 Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Fix Committed Status in apt source package in Zesty: Fix Committed Bug description: [Impact] The mirror method always dies with a SEGV. It does not initialize _system but calls a function that sometimes uses it. [Test case] Use a mirror sources.list entry like deb mirror://mirrors.ubuntu.com/mirrors.txt zesty main restricted universe multiverse [Regression potential] The fix is small, and simply avoids using _system if _system is NULL in the called method. There should not be any regressions due to this. https://anonscm.debian.org/cgit/apt/apt.git/commit/?id=cba5c5a26a9bf00724f8ea647ac61b30e32734ba To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1613184/+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 1613184] Re: method mirror broken at 1.3
Note that this bug is a blocker for standard upgrade path from Zesty to Artful. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1613184 Title: method mirror broken at 1.3 Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Fix Committed Status in apt source package in Zesty: Fix Committed Bug description: [Impact] The mirror method always dies with a SEGV. It does not initialize _system but calls a function that sometimes uses it. [Test case] Use a mirror sources.list entry like deb mirror://mirrors.ubuntu.com/mirrors.txt zesty main restricted universe multiverse [Regression potential] The fix is small, and simply avoids using _system if _system is NULL in the called method. There should not be any regressions due to this. https://anonscm.debian.org/cgit/apt/apt.git/commit/?id=cba5c5a26a9bf00724f8ea647ac61b30e32734ba To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1613184/+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 1721280] Re: vim.gtk3 crashed with SIGSEGV in __new_sem_wait_fast()
I got a similar crash with some other python3 plugins. To reproduce move your .vim and .vimrc out of the way and then: $ mkdir -p .vim/pack/bug/start $ cd .vim/pack/bug/start $ (git clone https://github.com/Shougo/deoplete.nvim.git && cd deoplete.nvim && git checkout e9e45ebcf7757ca7d32003cb54a0e31bf2afadb8) $ (git clone https://github.com/roxma/nvim-yarp.git && cd nvim-yarp.nvim && git checkout edb260a) $ (git clone https://github.com/roxma/vim-hug-neovim-rpc.git && cd vim-hug-neovim-rpc && git checkout 0b8e70f) $ cd $ echo 'let g:deoplete#enable_at_startup=1' >.vimrc $ touch x $ vim x Press :q Repeat a few (sometimes it crashes everytime, sometimes repeat 10-20 times to get a crash), eventually it crashes with SEGV on exit Run under valgrind, see valgrind.log, that reproduces the problem always: $ valgrind --log-file=valgrind.log vim x :q ** Attachment added: "valgrind.log" https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1721280/+attachment/5017526/+files/valgrind.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1721280 Title: vim.gtk3 crashed with SIGSEGV in __new_sem_wait_fast() Status in vim package in Ubuntu: New Bug description: Might be related to one of my extensions camelcasemotion lightline.vim vim-fetch inorirust.vim validator.vim vim-fugitive Please also double check that it's not a duplicate of #96263 "vim crashed with sigsegv" ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: vim-gtk3 2:8.0.0197-4ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Oct 4 16:13:33 2017 ExecutablePath: /usr/bin/vim.gtk3 InstallationDate: Installed on 2017-05-30 (127 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) 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. ProcCmdline: vim update_test_projects.sh Signal: 11 SourcePackage: vim StacktraceTop: kill () at ../sysdeps/unix/syscall-template.S:84 mch_exit () getout () () at /lib/x86_64-linux-gnu/libpthread.so.0 __new_sem_wait_fast (definitive_result=0, sem=0x0) at sem_waitcommon.c:135 Title: vim.gtk3 crashed with SIGSEGV in kill() UpgradeStatus: Upgraded to artful on 2017-09-25 (8 days ago) UserGroups: dialout plugdev sudo wireshark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1721280/+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 1734967] Re: tzdata info for WGT/WGST broken
Nish, Yes the Ubuntu php build is configure with tzdata as follow : debian/rules: --with-system-tzdata and tzdata is a Depends: for a quit some derived binary package of php. (The above is observation from bionic php7.1 source pkg) # debian/php-common.README.Debian -- Timezone data from system timezone database -- Debian PHP has been patched to use the system wide timezone database from the tzdata package, making sure any updates there are automatically used by PHP as well. Note that this requires that the PHP process has access to /etc/localtime and /usr/share/zoneinfo. For any regular installation this should be the case, but in specific secured environments when reading the timezone database is impossible PHP will give a "Timezone database is corrupt - this should *never* happen!" error. -- - Eric -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1734967 Title: tzdata info for WGT/WGST broken Status in php5 package in Ubuntu: New Status in php7.0 package in Ubuntu: New Status in php7.1 package in Ubuntu: New Status in tzdata package in Ubuntu: Invalid Status in php7.0 package in Debian: New Bug description: Using "America/Godthab" timezone, "WGT/WGST" is no longer displayed from date command but instead just "-03". Problem is evident in PHP applications too, which now think we're in Sao Paolo. This appears to have changed with latest tzdata update or perhaps in combination with change from DST. Same problem on 16.04, 17.10 and Debian 9. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1734967/+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 1734967] Re: tzdata info for WGT/WGST broken
Looking at the php-src git log (PHP upstream). I notice PHP is updated every time there is a new tzdata version: 56269af46c Updated to version 2017.2 (2017b) 1f9e5cc2bc Updated to version 2017.2 (2017b) eb13003f6c Updated to version 2017.2 (2017b) root@phpbisect:~/php7/php-src# git log --oneline --grep="2017a" b20879348a Updated to version 2017.1 (2017a) 1b16fb594f Updated to version 2017.1 (2017a) dfcb11d7d1 Updated to version 2017.1 (2017a) -- $ git log --oneline --grep="2017c" 973c1e3c93 Updated to version 2017.3 (2017c) 12e2fc4ab6 Updated to version 2017.3 (2017c) b07b526b95 Updated to version 2017.3 (2017c) b2dfcb30eb Updated to version 2017.3 (2017c) $ git log --oneline --format=%cd --date=local --grep="2017c" Mon Oct 23 14:31:24 2017 Mon Oct 23 14:31:23 2017 Mon Oct 23 14:31:21 2017 Mon Oct 23 14:31:20 2017 I'll give it a try in Ubuntu by merging the needed change and test. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1734967 Title: tzdata info for WGT/WGST broken Status in php5 package in Ubuntu: New Status in php7.0 package in Ubuntu: New Status in php7.1 package in Ubuntu: New Status in tzdata package in Ubuntu: Invalid Status in php7.0 package in Debian: New Bug description: Using "America/Godthab" timezone, "WGT/WGST" is no longer displayed from date command but instead just "-03". Problem is evident in PHP applications too, which now think we're in Sao Paolo. This appears to have changed with latest tzdata update or perhaps in combination with change from DST. Same problem on 16.04, 17.10 and Debian 9. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1734967/+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
