[Touch-packages] [Bug 1623774] Re: Ubuntu 16 unable to create 80-container-host0.network.dpkg-new
Please file bugs with ubuntu-bug; there should already be a crash report with the apt, dmesg, and other interesting logs. This is most likely due to a corrupted file system or RAM; it could be a bug in dpkg (although very unlikely). Can you reproduce this after a clean boot and "sudo apt-get -f install"? ** Package changed: systemd (Ubuntu) => dpkg (Ubuntu) ** Changed in: dpkg (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1623774 Title: Ubuntu 16 unable to create 80-container-host0.network.dpkg-new Status in dpkg package in Ubuntu: Incomplete Bug description: When I distro upgrade Ubuntu 16x64 I get: The following packages will be upgraded: libudev1 systemd udev 3 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. Need to get 1,046 kB/4,686 kB of archives. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 udev amd64 229-4ubuntu8 [990 kB] Get:2 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 libudev1 amd64 229-4ubuntu8 [56.5 kB] Fetched 1,046 kB in 1s (977 kB/s) Reading changelogs... Done (Reading database ... 122160 files and directories currently installed.) Preparing to unpack .../systemd_229-4ubuntu8_amd64.deb ... + set -e + [ upgrade = remove ] + dpkg-maintscript-helper rm_conffile /etc/X11/xinit/xinitrc.d/50-systemd-user.sh 228-3~ -- upgrade 229-4ubuntu8 + dpkg-maintscript-helper rm_conffile /etc/dbus-1/system.d/org.freedesktop.machine1.conf 228-5~ -- upgrade 229-4ubuntu8 + dpkg-maintscript-helper mv_conffile /etc/systemd/systemd-journald.conf /etc/systemd/journald.conf 204-1~ -- upgrade 229-4ubuntu8 + dpkg-maintscript-helper mv_conffile /etc/systemd/systemd-logind.conf /etc/systemd/logind.conf 204-1~ -- upgrade 229-4ubuntu8 + dpkg-maintscript-helper rm_conffile /etc/bash_completion.d/systemd-bash-completion.sh 204-1~ -- upgrade 229-4ubuntu8 + dpkg-maintscript-helper rm_conffile /etc/bash_completion.d/systemctl-bash-completion.sh 204-1~ -- upgrade 229-4ubuntu8 Unpacking systemd (229-4ubuntu8) over (229-4ubuntu7) ... dpkg: error processing archive /var/cache/apt/archives/systemd_229-4ubuntu8_amd64.deb (--unpack): unable to create '/lib/systemd/network/80-container-host0.network.dpkg-new' (while processing './lib/systemd/network/80-container-host0.network'): No such file or directory No apport report written because the error message indicates an issue on the local system dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) addgroup: The group `systemd-journal' already exists as a system group. Exiting. Processing triggers for ureadahead (0.100.0-19) ... Processing triggers for dbus (1.10.6-1ubuntu3) ... Errors were encountered while processing: /var/cache/apt/archives/systemd_229-4ubuntu8_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1623774/+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 1615160] Re: Unable to build any GTK app, because of missing wayland-client.pc
** Tags added: gtk-mir -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1615160 Title: Unable to build any GTK app, because of missing wayland-client.pc Status in gtk+3.0 package in Ubuntu: Incomplete Bug description: lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 # apt-cache policy libgtk-3-dev libgtk-3-dev: Installed: 3.18.9-1ubuntu3.1 Candidate: 3.18.9-1ubuntu3.1 Version table: *** 3.18.9-1ubuntu3.1 500 500 http://ports.ubuntu.com/ubuntu-ports xenial-updates/main arm64 Packages 100 /var/lib/dpkg/status 3.18.9-1ubuntu3 500 500 http://ports.ubuntu.com/ubuntu-ports xenial/main arm64 Packages This bug (see Bug #1106188) has re-emerged on arm64: pkg-config gtk+-3.0 --cflags Package wayland-egl was not found in the pkg-config search path. Perhaps you should add the directory containing `wayland-egl.pc' to the PKG_CONFIG_PATH environment variable Package 'wayland-egl', required by 'gtk+-3.0', not found This affects both gtk and gdk. I edited gdk-3.0.pc and gtk-3.0.pc to remove any references to wayland or mir, and it seems to be working. I am not sure how exactly these packages can provide the correct cflags, because they may not know their backend until runtime. Can we just remove the requirement for wayland, mir and x11? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1615160/+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 1445542] Re: Using the Mir backend, secondary windows of GTK apps open behind the primary window
** Tags added: gtk-mir -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1445542 Title: Using the Mir backend, secondary windows of GTK apps open behind the primary window Status in Mir: New Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: Using the Mir backend, secondary windows of GTK apps open behind the primary window. This is odd because Mir's default behaviour is to put any new surface on top. e.g. Remmina (after you apply the fix for bug 1444132) To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1445542/+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 1619178] Re: the contents of windows often appears entirely after opening the window
Neverball is SDL, not GTK. But it sounds like you're actually describing Unity8 shell bugs instead. ** Changed in: gtk+3.0 (Ubuntu) Status: New => Invalid ** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Tags added: unity8-desktop -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1619178 Title: the contents of windows often appears entirely after opening the window Status in Canonical System Image: New Status in gtk+3.0 package in Ubuntu: Invalid Status in libsdl2 package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: the contents of windows often appears entirely after opening the box. In fact, sometimes the right side of the window does not appear, and to see it is necessary to resize the window. Tested with gtk and sdl2 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1619178/+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 1593379] Re: systemd 229-4ubuntu6 ignores net.ifnames=0 on USB or /etc/udev/rules.d/80-net-setup-link.rules being a /dev/null symlink
Committed to master branch: https://anonscm.debian.org/cgit/pkg- systemd/systemd.git/commit/?id=72a90870 Cherry-picked into xenial branch for next SRU round: https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h =ubuntu-xenial&id=f79508898 ** Changed in: systemd (Ubuntu Xenial) Status: Incomplete => Fix Committed -- 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/1593379 Title: systemd 229-4ubuntu6 ignores net.ifnames=0 on USB or /etc/udev/rules.d/80-net-setup-link.rules being a /dev/null symlink Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Committed Status in systemd package in Debian: Fix Released Bug description: Description:Ubuntu 16.04 LTS Release:16.04 The upgrade to systemd/udev 229-4ubuntu6 breaks net.ifnames=0 for USB devices. It appears the regression is here: * Set MAC based name for USB network interfaces only for universally administered (i. e. stable) MACs, not for locally administered (i. e. randomly generated) ones. Drop /lib/systemd/network/90-mac-for-usb.link (as link files don't currently support globs for MACAddress=) and replace with an udev rule in /lib/udev/rules.d/73-special-net-names.rules. (Closes: #812575, LP: #1574483) As Raspberry Pi's use eth0 via USB, this breaks running systems. Before: ii systemd229-4ubuntu4 armhfsystem and service manager ii udev 229-4ubuntu4 armhf/dev/ and hotplug management daem 3: eth0: mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000 link/ether b8:27:eb:16:39:e9 brd ff:ff:ff:ff:ff:ff After: ii systemd 229-4ubuntu6armhf system and service manager ii udev 229-4ubuntu6armhf /dev/ and hotplug management daemon 3: enxb827eb1639e9: mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000 link/ether b8:27:eb:16:39:e9 brd ff:ff:ff:ff:ff:ff cat /proc/cmdline dma.dmachans=0x7f35 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2709.boardrev=0xa01041 bcm2709.serial=0x37b38253 smsc95xx.macaddr=B8:27:EB:B3:82:53 bcm2708_fb.fbswap=1 bcm2709.disk_led_gpio=47 bcm2709.disk_led_active_low=0 sdhci-bcm2708.emmc_clock_freq=25000 vc_mem.mem_base=0x3dc0 vc_mem.mem_size=0x3f00 net.ifnames=0 dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait With the default interfaces configuration, all networking is lost on reboot after upgrade. SRU TEST CASE = * Boot with "net.ifnames=0" on the kernel command line, and connect an USB ethernet device. It will still be called enxDEADBEEF with current xenial. With the -proposed version it will instead keep the kernel name, like "usb0" as intended. * Do "sudo ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules" (the other documented way to disable ifnames) and do the above connect/name check test again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1593379/+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 1623484] Re: mir_demo_client_egltriangle crashed with SIGSEGV in dri2_destroy_context() on Yakkety
** Changed in: mir Assignee: (unassigned) => Daniel van Vugt (vanvugt) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1623484 Title: mir_demo_client_egltriangle crashed with SIGSEGV in dri2_destroy_context() on Yakkety Status in Mir: New Status in mir package in Ubuntu: New Bug description: $ mir_demo_server --launch mir_demo_client_egltriangle Then Alt+F4 to close the triangle Probably problems with mesa releasing resources, as that also appears to be a problem in lp:1623432 ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: mir-demos 0.24.0+16.10.20160815.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Wed Sep 14 13:08:04 2016 ExecutablePath: /usr/bin/mir_demo_client_egltriangle InstallationDate: Installed on 2016-09-06 (8 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160906) ProcCmdline: mir_demo_client_egltriangle SegvAnalysis: Segfault happened at: 0x7fbacaa47a3e:mov0x30(%rbp),%rax PC (0x7fbacaa47a3e) ok source "0x30(%rbp)" (0x0030) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: mir StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 eglTerminate () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 mir_eglapp_shutdown () Title: mir_demo_client_egltriangle crashed with SIGSEGV in eglTerminate() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1623484/+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 1593379] Re: systemd 229-4ubuntu6 ignores net.ifnames=0 on USB or /etc/udev/rules.d/80-net-setup-link.rules being a /dev/null symlink
Interesting observation, thanks! I cannot confirm that the single line is generally broken -- I've tested it on two different computers (although only amd64) and it works fine. However, there is no harm in splitting the rule, so I'll do that for the next SRU if it helps things. -- 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/1593379 Title: systemd 229-4ubuntu6 ignores net.ifnames=0 on USB or /etc/udev/rules.d/80-net-setup-link.rules being a /dev/null symlink Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Incomplete Status in systemd package in Debian: Fix Released Bug description: Description:Ubuntu 16.04 LTS Release:16.04 The upgrade to systemd/udev 229-4ubuntu6 breaks net.ifnames=0 for USB devices. It appears the regression is here: * Set MAC based name for USB network interfaces only for universally administered (i. e. stable) MACs, not for locally administered (i. e. randomly generated) ones. Drop /lib/systemd/network/90-mac-for-usb.link (as link files don't currently support globs for MACAddress=) and replace with an udev rule in /lib/udev/rules.d/73-special-net-names.rules. (Closes: #812575, LP: #1574483) As Raspberry Pi's use eth0 via USB, this breaks running systems. Before: ii systemd229-4ubuntu4 armhfsystem and service manager ii udev 229-4ubuntu4 armhf/dev/ and hotplug management daem 3: eth0: mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000 link/ether b8:27:eb:16:39:e9 brd ff:ff:ff:ff:ff:ff After: ii systemd 229-4ubuntu6armhf system and service manager ii udev 229-4ubuntu6armhf /dev/ and hotplug management daemon 3: enxb827eb1639e9: mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000 link/ether b8:27:eb:16:39:e9 brd ff:ff:ff:ff:ff:ff cat /proc/cmdline dma.dmachans=0x7f35 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2709.boardrev=0xa01041 bcm2709.serial=0x37b38253 smsc95xx.macaddr=B8:27:EB:B3:82:53 bcm2708_fb.fbswap=1 bcm2709.disk_led_gpio=47 bcm2709.disk_led_active_low=0 sdhci-bcm2708.emmc_clock_freq=25000 vc_mem.mem_base=0x3dc0 vc_mem.mem_size=0x3f00 net.ifnames=0 dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait With the default interfaces configuration, all networking is lost on reboot after upgrade. SRU TEST CASE = * Boot with "net.ifnames=0" on the kernel command line, and connect an USB ethernet device. It will still be called enxDEADBEEF with current xenial. With the -proposed version it will instead keep the kernel name, like "usb0" as intended. * Do "sudo ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules" (the other documented way to disable ifnames) and do the above connect/name check test again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1593379/+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 1623792] [NEW] possible sigbus
Public bug reported:
The following function looks like it will access a 32-bit data element
that is improperly aligned:
void zmq::socket_base_t::monitor_event (int event_, int value_, const
std::string &addr_)
{
if (monitor_socket) {
// Send event in first frame
zmq_msg_t msg;
zmq_msg_init_size (&msg, 6);
uint8_t *data = (uint8_t *) zmq_msg_data (&msg);
*(uint16_t *) (data + 0) = (uint16_t) event_;
*(uint32_t *) (data + 2) = (uint32_t) value_;
zmq_sendmsg (monitor_socket, &msg, ZMQ_SNDMORE);
// Send address in second frame
zmq_msg_init_size (&msg, addr_.size());
memcpy (zmq_msg_data (&msg), addr_.c_str (), addr_.size ());
zmq_sendmsg (monitor_socket, &msg, 0);
}
}
On many platforms this will cause a SIGBUS.
It looks like upstream has already fixed this issue:
https://github.com/zeromq/libzmq/blob/master/src/socket_base.cpp#L1683
The current code looks like:
void zmq::socket_base_t::monitor_event (int event_, intptr_t value_, const
std::string &addr_)
{
if (monitor_socket) {
// Send event in first frame
zmq_msg_t msg;
zmq_msg_init_size (&msg, 6);
uint8_t *data = (uint8_t *) zmq_msg_data (&msg);
// Avoid dereferencing uint32_t on unaligned address
uint16_t event = (uint16_t) event_;
uint32_t value = (uint32_t) value_;
memcpy (data + 0, &event, sizeof(event));
memcpy (data + 2, &value, sizeof(value));
zmq_sendmsg (monitor_socket, &msg, ZMQ_SNDMORE);
// Send address in second frame
zmq_msg_init_size (&msg, addr_.size());
memcpy (zmq_msg_data (&msg), addr_.c_str (), addr_.size ());
zmq_sendmsg (monitor_socket, &msg, 0);
}
}
Thanks
** Affects: zeromq3 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zeromq3 in Ubuntu.
https://bugs.launchpad.net/bugs/1623792
Title:
possible sigbus
Status in zeromq3 package in Ubuntu:
New
Bug description:
The following function looks like it will access a 32-bit data element
that is improperly aligned:
void zmq::socket_base_t::monitor_event (int event_, int value_, const
std::string &addr_)
{
if (monitor_socket) {
// Send event in first frame
zmq_msg_t msg;
zmq_msg_init_size (&msg, 6);
uint8_t *data = (uint8_t *) zmq_msg_data (&msg);
*(uint16_t *) (data + 0) = (uint16_t) event_;
*(uint32_t *) (data + 2) = (uint32_t) value_;
zmq_sendmsg (monitor_socket, &msg, ZMQ_SNDMORE);
// Send address in second frame
zmq_msg_init_size (&msg, addr_.size());
memcpy (zmq_msg_data (&msg), addr_.c_str (), addr_.size ());
zmq_sendmsg (monitor_socket, &msg, 0);
}
}
On many platforms this will cause a SIGBUS.
It looks like upstream has already fixed this issue:
https://github.com/zeromq/libzmq/blob/master/src/socket_base.cpp#L1683
The current code looks like:
void zmq::socket_base_t::monitor_event (int event_, intptr_t value_, const
std::string &addr_)
{
if (monitor_socket) {
// Send event in first frame
zmq_msg_t msg;
zmq_msg_init_size (&msg, 6);
uint8_t *data = (uint8_t *) zmq_msg_data (&msg);
// Avoid dereferencing uint32_t on unaligned address
uint16_t event = (uint16_t) event_;
uint32_t value = (uint32_t) value_;
memcpy (data + 0, &event, sizeof(event));
memcpy (data + 2, &value, sizeof(value));
zmq_sendmsg (monitor_socket, &msg, ZMQ_SNDMORE);
// Send address in second frame
zmq_msg_init_size (&msg, addr_.size());
memcpy (zmq_msg_data (&msg), addr_.c_str (), addr_.size ());
zmq_sendmsg (monitor_socket, &msg, 0);
}
}
Thanks
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zeromq3/+bug/1623792/+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 1620937] Re: konsole crashes on startup since Qt update in yakkety
Timo: I will be on vacation (and offline) until next weekend, so I will be able to commit it only after that. It got a +2 upstream, but not yet integrated. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1620937 Title: konsole crashes on startup since Qt update in yakkety Status in qtbase-opensource-src package in Ubuntu: In Progress Bug description: You can find the valgrind trace at http://paste.ubuntu.com/23144852/ Something wrong seems to be happening in the qdbusmenu code. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1620937/+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 1623774] Re: Ubuntu 16 unable to create 80-container-host0.network.dpkg-new
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- 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/1623774 Title: Ubuntu 16 unable to create 80-container-host0.network.dpkg-new Status in systemd package in Ubuntu: Confirmed Bug description: When I distro upgrade Ubuntu 16x64 I get: The following packages will be upgraded: libudev1 systemd udev 3 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. Need to get 1,046 kB/4,686 kB of archives. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 udev amd64 229-4ubuntu8 [990 kB] Get:2 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 libudev1 amd64 229-4ubuntu8 [56.5 kB] Fetched 1,046 kB in 1s (977 kB/s) Reading changelogs... Done (Reading database ... 122160 files and directories currently installed.) Preparing to unpack .../systemd_229-4ubuntu8_amd64.deb ... + set -e + [ upgrade = remove ] + dpkg-maintscript-helper rm_conffile /etc/X11/xinit/xinitrc.d/50-systemd-user.sh 228-3~ -- upgrade 229-4ubuntu8 + dpkg-maintscript-helper rm_conffile /etc/dbus-1/system.d/org.freedesktop.machine1.conf 228-5~ -- upgrade 229-4ubuntu8 + dpkg-maintscript-helper mv_conffile /etc/systemd/systemd-journald.conf /etc/systemd/journald.conf 204-1~ -- upgrade 229-4ubuntu8 + dpkg-maintscript-helper mv_conffile /etc/systemd/systemd-logind.conf /etc/systemd/logind.conf 204-1~ -- upgrade 229-4ubuntu8 + dpkg-maintscript-helper rm_conffile /etc/bash_completion.d/systemd-bash-completion.sh 204-1~ -- upgrade 229-4ubuntu8 + dpkg-maintscript-helper rm_conffile /etc/bash_completion.d/systemctl-bash-completion.sh 204-1~ -- upgrade 229-4ubuntu8 Unpacking systemd (229-4ubuntu8) over (229-4ubuntu7) ... dpkg: error processing archive /var/cache/apt/archives/systemd_229-4ubuntu8_amd64.deb (--unpack): unable to create '/lib/systemd/network/80-container-host0.network.dpkg-new' (while processing './lib/systemd/network/80-container-host0.network'): No such file or directory No apport report written because the error message indicates an issue on the local system dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) addgroup: The group `systemd-journal' already exists as a system group. Exiting. Processing triggers for ureadahead (0.100.0-19) ... Processing triggers for dbus (1.10.6-1ubuntu3) ... Errors were encountered while processing: /var/cache/apt/archives/systemd_229-4ubuntu8_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1623774/+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 1577262] Re: Screen is squashed/distorted when rotated in Mir-on-X11
** Changed in: canonical-devices-system-image Assignee: (unassigned) => Daniel van Vugt (vanvugt) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1577262 Title: Screen is squashed/distorted when rotated in Mir-on-X11 Status in Canonical System Image: Fix Committed Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: Screen is squashed/distorted when rotated in Mir-on-X11. Just run mir_proving_server and use Ctrl+Alt+arrows To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1577262/+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 1420581] Re: [enhancement] Add support for full OpenGL compositing
** Changed in: canonical-devices-system-image Assignee: (unassigned) => Daniel van Vugt (vanvugt) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1420581 Title: [enhancement] Add support for full OpenGL compositing Status in Canonical System Image: Fix Committed Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: [enhancement] Add support for full OpenGL compositing. libmirserver/platform presently is only compiled to use the "ES" subset of OpenGL. This works for mobile devices and many desktop use cases but not all. There are a few pending reasons to compile for full OpenGL on desktop (and/or switch at runtime!): 1. Qt only understands full OpenGL on desktop. Presently we use a hack that makes it call ES functions pretending to be full OpenGL, but this hack will fail when we support non-Mesa desktop drivers. 2. Proprietary desktop drivers sometimes don't support ES. 3. Proprietary desktop drivers often (last I checked) perform better with full OpenGL. Not sure why, probably just driver maturity. 4. There is evidence (bug 1420574) that ES doesn't work at all on some older chipsets and regular OpenGL is required. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1420581/+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 1602966] Re: [regression] The Super/Windows key doesn't work any more
** Changed in: mir (Ubuntu) Status: Fix Released => Invalid ** Changed in: canonical-devices-system-image Status: Fix Committed => Invalid ** Changed in: canonical-devices-system-image Milestone: 13 => None ** Changed in: canonical-devices-system-image Assignee: (unassigned) => Daniel van Vugt (vanvugt) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1602966 Title: [regression] The Super/Windows key doesn't work any more Status in Canonical System Image: Invalid Status in Mir: Fix Released Status in mir package in Ubuntu: Invalid Bug description: [regression] Zoom/contrast/negative desktop effects don't work any more in mir_proving_server on lp:mir. That's Super + mousewheel,C,N respectively To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1602966/+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 1579630] Re: mir server crashed in what(): drmModeMoveCursor failed (returned -13)
** Changed in: canonical-devices-system-image Assignee: (unassigned) => Daniel van Vugt (vanvugt) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1579630 Title: mir server crashed in what(): drmModeMoveCursor failed (returned -13) Status in Canonical System Image: Fix Committed Status in Mir: Fix Released Status in mir package in Ubuntu: Fix Released Bug description: mir-demos crashed while I was trying to kill mir_proving_server from another VT. The log says: terminate called after throwing an instance of 'boost::exception_detail::clone_impl >' what(): drmModeMoveCursor failed (returned -13) The error report is less informative: https://errors.ubuntu.com/oops/88953040-15b0-11e6-9c36-fa163ebeb28a To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1579630/+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 1565729] Re: Suspend/hibernate freezes with radeon driver loaded on AMD/ATI hybrid graphics
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- 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/1565729 Title: Suspend/hibernate freezes with radeon driver loaded on AMD/ATI hybrid graphics Status in xorg package in Ubuntu: Expired Bug description: On at least Ubuntu 15.10 and 16.04 with the radeon driver (version 7.5.0+git20150819-0ubuntu1 on 15.10, version 7.6.1-1ubuntu2 on 16.04) trying to suspend or hibernate a Lenovo G50-80 with Intel HD Graphics 5500 (Broadwell GT2) and Advanced Micro Devices [AMD/ATI] Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330] freezes the system when the radeon driver is loaded even if it is not in use. Turning off discrete graphics using the BIOS settings and using only the integrated Intel chip so that the radeon driver is not loaded does not cause this problem. Also, this problem does not occur on Ubuntu 14.04.4 using the kernel and X stack (LTS Enablement Stack) from 15.10 (Wily) even with the radeon driver loaded. There is a message from the radeon driver during boot, "radeon :04:00.0: VCE init error (-22)." which is an upstream issue occurring on other distributions too and is reported at https://bugs.freedesktop.org/show_bug.cgi?id=92722. However, even if the radeon driver is loaded, suspend/hibernate does not freeze on, e.g., Fedora 23 and, as mentioned above, even Ubuntu 14.04.4. I have tried using S1 instead of S3 sleep to no avail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1565729/+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 1623774] [NEW] Ubuntu 16 unable to create 80-container-host0.network.dpkg-new
Public bug reported: When I distro upgrade Ubuntu 16x64 I get: The following packages will be upgraded: libudev1 systemd udev 3 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. Need to get 1,046 kB/4,686 kB of archives. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 udev amd64 229-4ubuntu8 [990 kB] Get:2 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 libudev1 amd64 229-4ubuntu8 [56.5 kB] Fetched 1,046 kB in 1s (977 kB/s) Reading changelogs... Done (Reading database ... 122160 files and directories currently installed.) Preparing to unpack .../systemd_229-4ubuntu8_amd64.deb ... + set -e + [ upgrade = remove ] + dpkg-maintscript-helper rm_conffile /etc/X11/xinit/xinitrc.d/50-systemd-user.sh 228-3~ -- upgrade 229-4ubuntu8 + dpkg-maintscript-helper rm_conffile /etc/dbus-1/system.d/org.freedesktop.machine1.conf 228-5~ -- upgrade 229-4ubuntu8 + dpkg-maintscript-helper mv_conffile /etc/systemd/systemd-journald.conf /etc/systemd/journald.conf 204-1~ -- upgrade 229-4ubuntu8 + dpkg-maintscript-helper mv_conffile /etc/systemd/systemd-logind.conf /etc/systemd/logind.conf 204-1~ -- upgrade 229-4ubuntu8 + dpkg-maintscript-helper rm_conffile /etc/bash_completion.d/systemd-bash-completion.sh 204-1~ -- upgrade 229-4ubuntu8 + dpkg-maintscript-helper rm_conffile /etc/bash_completion.d/systemctl-bash-completion.sh 204-1~ -- upgrade 229-4ubuntu8 Unpacking systemd (229-4ubuntu8) over (229-4ubuntu7) ... dpkg: error processing archive /var/cache/apt/archives/systemd_229-4ubuntu8_amd64.deb (--unpack): unable to create '/lib/systemd/network/80-container-host0.network.dpkg-new' (while processing './lib/systemd/network/80-container-host0.network'): No such file or directory No apport report written because the error message indicates an issue on the local system dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) addgroup: The group `systemd-journal' already exists as a system group. Exiting. Processing triggers for ureadahead (0.100.0-19) ... Processing triggers for dbus (1.10.6-1ubuntu3) ... Errors were encountered while processing: /var/cache/apt/archives/systemd_229-4ubuntu8_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1623774 Title: Ubuntu 16 unable to create 80-container-host0.network.dpkg-new Status in systemd package in Ubuntu: New Bug description: When I distro upgrade Ubuntu 16x64 I get: The following packages will be upgraded: libudev1 systemd udev 3 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. Need to get 1,046 kB/4,686 kB of archives. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 udev amd64 229-4ubuntu8 [990 kB] Get:2 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 libudev1 amd64 229-4ubuntu8 [56.5 kB] Fetched 1,046 kB in 1s (977 kB/s) Reading changelogs... Done (Reading database ... 122160 files and directories currently installed.) Preparing to unpack .../systemd_229-4ubuntu8_amd64.deb ... + set -e + [ upgrade = remove ] + dpkg-maintscript-helper rm_conffile /etc/X11/xinit/xinitrc.d/50-systemd-user.sh 228-3~ -- upgrade 229-4ubuntu8 + dpkg-maintscript-helper rm_conffile /etc/dbus-1/system.d/org.freedesktop.machine1.conf 228-5~ -- upgrade 229-4ubuntu8 + dpkg-maintscript-helper mv_conffile /etc/systemd/systemd-journald.conf /etc/systemd/journald.conf 204-1~ -- upgrade 229-4ubuntu8 + dpkg-maintscript-helper mv_conffile /etc/systemd/systemd-logind.conf /etc/systemd/logind.conf 204-1~ -- upgrade 229-4ubuntu8 + dpkg-maintscript-helper rm_conffile /etc/bash_completion.d/systemd-bash-completion.sh 204-1~ -- upgrade 229-4ubuntu8 + dpkg-maintscript-helper rm_conffile /etc/bash_completion.d/systemctl-bash-completion.sh 204-1~ -- upgrade 229-4ubuntu8 Unpacking systemd (229-4ubuntu8) over (229-4ubuntu7) ... dpkg: error processing archive /var/cache/apt/archives/systemd_229-4ubuntu8_amd64.deb (--unpack): unable to create '/lib/systemd/network/80-container-host0.network.dpkg-new' (while processing './lib/systemd/network/80-container-host0.network'): No such file or directory No apport report written because the error message indicates an issue on the local system dpkg-deb: error: subprocess paste was killed by signal (Broken pipe
[Touch-packages] [Bug 1553328] Re: Mir crashes on nouveau (nv50) in pushbuf_kref()
Upstream says nouveau is known to not support multi-threaded rendering and will crash: https://bugs.freedesktop.org/show_bug.cgi?id=92438 So that completely explains yesterday's crash in bug 1623507. Hopefully that vaguely explains this one too. ** Bug watch added: freedesktop.org Bugzilla #92438 https://bugs.freedesktop.org/show_bug.cgi?id=92438 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1553328 Title: Mir crashes on nouveau (nv50) in pushbuf_kref() Status in Canonical System Image: Confirmed Status in Mir: Invalid Status in libdrm package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mir package in Ubuntu: Invalid Status in qtmir package in Ubuntu: Invalid Bug description: Unit8 froze up while I was trying to open system settings. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: unity8 8.11+16.04.20160216.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3 Uname: Linux 4.4.0-9-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Fri Mar 4 19:12:54 2016 ExecutablePath: /usr/bin/unity8 InstallationDate: Installed on 2015-05-10 (299 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcCmdline: unity8 SegvAnalysis: Segfault happened at: 0x7f58d568706c:mov0x8(%rsi),%edx PC (0x7f58d568706c) ok source "0x8(%rsi)" (0x0008) not located in a known VMA region (needed readable region)! destination "%edx" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity8 StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 Title: unity8 crashed with SIGSEGV UpgradeStatus: Upgraded to xenial on 2015-11-07 (118 days ago) UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1553328/+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 1623768] [NEW] Adapt to new Totem icon name
Public bug reported: Totem has changed its icon name for easier integration with flatpak -Icon=totem +Icon=org.gnome.Totem If your icon theme will be used in Ubuntu 16.04 LTS also, then I recommend making a symlink from the totem icon to the new org.gnome.Totem icon. Alternatively, you could drop the icon and let users use the high resolution icons shipped by Totem itself. See also bug 1618138 which lists some other app icon name changes but those icons aren't shipped in all themes. ** Affects: humanity-icon-theme (Ubuntu) Importance: Undecided Status: New ** Affects: lubuntu-artwork (Ubuntu) Importance: Undecided Status: New ** Affects: ubuntukylin-theme (Ubuntu) Importance: Undecided Status: New ** Affects: xubuntu-artwork (Ubuntu) Importance: Undecided Status: New ** Also affects: xubuntu-artwork (Ubuntu) Importance: Undecided Status: New ** Description changed: ** Description changed: ** Also affects: lubuntu-artwork (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntukylin-theme (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to humanity-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1623768 Title: Adapt to new Totem icon name Status in humanity-icon-theme package in Ubuntu: New Status in lubuntu-artwork package in Ubuntu: New Status in ubuntukylin-theme package in Ubuntu: New Status in xubuntu-artwork package in Ubuntu: New Bug description: Totem has changed its icon name for easier integration with flatpak -Icon=totem +Icon=org.gnome.Totem If your icon theme will be used in Ubuntu 16.04 LTS also, then I recommend making a symlink from the totem icon to the new org.gnome.Totem icon. Alternatively, you could drop the icon and let users use the high resolution icons shipped by Totem itself. See also bug 1618138 which lists some other app icon name changes but those icons aren't shipped in all themes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/1623768/+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 1575516] Re: Mir is just a black screen and mouse cursor on Nvidia GTX 900 (and sometimes "Failed to schedule page flip")
** Summary changed: - Mir is just a black screen and mouse cursor on Nvidia GTX 900 + Mir is just a black screen and mouse cursor on Nvidia GTX 900 (and sometimes "Failed to schedule page flip") -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1575516 Title: Mir is just a black screen and mouse cursor on Nvidia GTX 900 (and sometimes "Failed to schedule page flip") Status in Canonical System Image: New Status in Mir: New Status in mesa package in Ubuntu: Invalid Status in mir package in Ubuntu: Confirmed Bug description: Nvidia (using nouveau not binary drivers): Mir servers freeze on start-up for 30 seconds, and then you get just a black screen and mouse cursor (which at least moves). Using lp:mir r3480 ... [2016-04-27 15:20:19.369559] mirserver: Selected driver: mir:mesa-kms (version 0.22.0) nvc0_screen_create:762 - Error allocating PGRAPH context for M2MF: -22 [2016-04-27 15:20:51.934145] mirserver: Using hardware cursor [2016-04-27 15:20:51.937691] mirserver: Initial display configuration: [2016-04-27 15:20:51.937703] mirserver: 0.36: unused DVI-I [2016-04-27 15:20:51.937713] mirserver: 0.39: DVI-D 24.0" 520x320mm [2016-04-27 15:20:51.937722] mirserver: Current mode 1920x1200 59.95Hz [2016-04-27 15:20:51.937731] mirserver: Preferred mode 1920x1200 59.95Hz [2016-04-27 15:20:51.937740] mirserver: Logical position +0+0 [2016-04-27 15:20:51.937781] mirserver: 0.41: unused HDMI-A [2016-04-27 15:20:51.937799] mirserver: 0.43: unused DisplayPort [2016-04-27 15:20:51.937972] mircommon: Loading modules from: bin/../lib/server-modules/ [2016-04-27 15:20:51.938015] mircommon: Loading module: bin/../lib/server-modules/graphics-android.so.9 [2016-04-27 15:20:51.938107] mircommon: Failed to load module: bin/../lib/server-modules/graphics-android.so.9 (error was:libhardware.so.2: cannot open shared object file: No such file or directory) [2016-04-27 15:20:51.938119] mircommon: Loading module: bin/../lib/server-modules/graphics-mesa-kms.so.9 [2016-04-27 15:20:51.938142] mircommon: Loading module: bin/../lib/server-modules/server-mesa-x11.so.9 [2016-04-27 15:20:51.938536] mircommon: Loading module: bin/../lib/server-modules/input-evdev.so.5 [2016-04-27 15:20:51.955316] mirserver: Selected input driver: mir:evdev-input (version: 0.22.0) [2016-04-27 15:20:51.955500] mirserver: Mir version 0.22.0 [2016-04-27 15:20:51.962627] GLRenderer: EGL vendor: Mesa Project [2016-04-27 15:20:51.962645] GLRenderer: EGL version: 1.4 (DRI2) [2016-04-27 15:20:51.962651] GLRenderer: EGL client APIs: OpenGL OpenGL_ES OpenGL_ES2 OpenGL_ES3 [2016-04-27 15:20:51.962657] GLRenderer: EGL extensions: EGL_EXT_buffer_age EGL_EXT_image_dma_buf_import EGL_KHR_create_context EGL_KHR_get_all_proc_addresses EGL_KHR_gl_renderbuffer_image EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_image EGL_KHR_image_base EGL_KHR_image_pixmap EGL_KHR_surfaceless_context EGL_MESA_configless_context EGL_MESA_image_dma_buf_export [2016-04-27 15:20:51.962670] GLRenderer: GL vendor: VMware, Inc. [2016-04-27 15:20:51.962679] GLRenderer: GL renderer: Gallium 0.4 on llvmpipe (LLVM 3.8, 256 bits) [2016-04-27 15:20:51.962688] GLRenderer: GL version: OpenGL ES 3.0 Mesa 11.2.0 [2016-04-27 15:20:51.962697] GLRenderer: GLSL version: OpenGL ES GLSL ES 3.00 lspci: 01:00.0 VGA compatible controller: NVIDIA Corporation GM204 [GeForce GTX 970] (rev a1) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1575516/+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 1553328] Re: Mir crashes on nouveau (nv50) in pushbuf_kref()
Confirmed by duplicate/similar bug 1623507 ** Summary changed: - unity8 crashed with SIGSEGV on nouveau, in eglMakeCurrent() ... nv50_flush() ... pushbuf_kref() + Mir crashes on nouveau (nv50) in pushbuf_kref() ** Changed in: qtmir (Ubuntu) Status: Incomplete => Invalid ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** Changed in: mesa (Ubuntu) Importance: Undecided => High ** Changed in: libdrm (Ubuntu) Status: New => Confirmed ** Changed in: mesa (Ubuntu) Status: New => Confirmed ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Status: New => Confirmed ** Changed in: canonical-devices-system-image Importance: Undecided => High ** Tags added: nouveau -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1553328 Title: Mir crashes on nouveau (nv50) in pushbuf_kref() Status in Canonical System Image: Confirmed Status in Mir: Invalid Status in libdrm package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mir package in Ubuntu: Invalid Status in qtmir package in Ubuntu: Invalid Bug description: Unit8 froze up while I was trying to open system settings. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: unity8 8.11+16.04.20160216.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3 Uname: Linux 4.4.0-9-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Fri Mar 4 19:12:54 2016 ExecutablePath: /usr/bin/unity8 InstallationDate: Installed on 2015-05-10 (299 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcCmdline: unity8 SegvAnalysis: Segfault happened at: 0x7f58d568706c:mov0x8(%rsi),%edx PC (0x7f58d568706c) ok source "0x8(%rsi)" (0x0008) not located in a known VMA region (needed readable region)! destination "%edx" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity8 StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/nouveau_dri.so ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 Title: unity8 crashed with SIGSEGV UpgradeStatus: Upgraded to xenial on 2015-11-07 (118 days ago) UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1553328/+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 1623507] Re: unity-system-compositor crashed with "Failed to schedule page flip", but only after nouveau crashed in glClear().
*** This bug is a duplicate of bug 1553328 *** https://bugs.launchpad.net/bugs/1553328 Aha! Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1553328, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1553328 Mir crashes on nouveau (nv50) in pushbuf_kref() -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1623507 Title: unity-system-compositor crashed with "Failed to schedule page flip", but only after nouveau crashed in glClear(). Status in Canonical System Image: New Status in Mir: Triaged Status in libdrm package in Ubuntu: New Status in mesa package in Ubuntu: New Status in mir package in Ubuntu: Triaged Bug description: 16.10 first unity 8 run ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: unity-system-compositor 0.7.1+16.10.20160824-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Wed Sep 14 10:34:45 2016 ExecutablePath: /usr/sbin/unity-system-compositor GraphicsCard: Subsystem: Micro-Star International Co., Ltd. [MSI] Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1462:7817] NVIDIA Corporation G92 [GeForce 9800 GT] [10de:0614] (rev a2) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. G92 [GeForce 9800 GT] [3842:c988] InstallationDate: Installed on 2016-09-14 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160913) ProcCmdline: /usr/sbin/unity-system-compositor --disable-inactivity-policy=true --on-fatal-error-abort --file /run/mir_socket --from-dm-fd 11 --to-dm-fd 14 --vt 7 ProcEnviron: Signal: 6 SourcePackage: unity-system-compositor StacktraceTop: mir::fatal_error_abort(char const*, ...) () from /usr/lib/x86_64-linux-gnu/libmircommon.so.6 ?? () from /usr/lib/x86_64-linux-gnu/mir/server-platform/graphics-mesa-kms.so.10 ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.41 ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.41 ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 Title: unity-system-compositor crashed with SIGABRT in mir::fatal_error_abort() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: version.libdrm: libdrm2 2.4.70-1 version.lightdm: lightdm 1.19.4-0ubuntu1 version.mesa: libegl1-mesa-dev N/A To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1623507/+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 1621746] Re: Black Screen, libprotobuf FATAL program was compiled against version 2.6.1 which is not compatible with the installed version (3.0.0)
It appears this bug is still confined to 'proposed' so if you want to avoid it please just use plain 16.10 without 'proposed' enabled. ** Also affects: mir Importance: Undecided Status: New ** Changed in: mir Status: New => Invalid ** Changed in: canonical-devices-system-image Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1621746 Title: Black Screen, libprotobuf FATAL program was compiled against version 2.6.1 which is not compatible with the installed version (3.0.0) Status in Canonical System Image: Confirmed Status in Mir: Invalid Status in mir package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Invalid Bug description: Ubuntu 16.10 + proposed x86 install Black Screen, libprotobuf FATAL program was compiled against version 2.6.1 which is not compatible with the installed version (3.0.0) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1621746/+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 1584894] Re: unity-system-compositor crashes on start-up with "Mir fatal error: Failed to schedule page flip" on VirtualBox Graphics Adapter
** Changed in: canonical-devices-system-image Importance: Undecided => High ** Changed in: canonical-devices-system-image Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1584894 Title: unity-system-compositor crashes on start-up with "Mir fatal error: Failed to schedule page flip" on VirtualBox Graphics Adapter Status in Canonical System Image: Confirmed Status in Mir: Confirmed Status in mir package in Ubuntu: Confirmed Bug description: (separated from bug 1118903) unity-system-compositor crashes on start-up with "Mir fatal error: Failed to schedule page flip" on VirtualBox Graphics Adapter --- can not login to Unity8 ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: unity-system-compositor 0.4.3+16.04.20160323-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu4 Architecture: amd64 Date: Mon May 23 19:20:43 2016 ExecutablePath: /usr/sbin/unity-system-compositor GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) InstallationDate: Installed on 2016-05-19 (3 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160519) ProcCmdline: /usr/sbin/unity-system-compositor --disable-inactivity-policy=true --on-fatal-error-abort --file /run/lightdm-mir-0 --from-dm-fd 12 --to-dm-fd 21 --vt 8 ProcEnviron: Signal: 6 SourcePackage: unity-system-compositor StacktraceTop: mir::fatal_error_abort(char const*, ...) () from /usr/lib/x86_64-linux-gnu/libmircommon.so.5 ?? () from /usr/lib/x86_64-linux-gnu/mir/server-platform/graphics-mesa-kms.so.8 ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.38 ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.38 ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 Title: unity-system-compositor crashed with SIGABRT in mir::fatal_error_abort() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: version.libdrm: libdrm2 2.4.68-1 version.lightdm: lightdm 1.19.0-0ubuntu1 version.mesa: libegl1-mesa-dev N/A To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1584894/+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 1621210] Re: [MIR] fonts-android
I do not find any Ghostscript with a depends/recommends/suggests on fonts-noto-cjk. Can someone tell me which Ghostscript version? Or can someone post a patch to switch Ghostscript to fonts-noto-cjk? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-android in Ubuntu. https://bugs.launchpad.net/bugs/1621210 Title: [MIR] fonts-android Status in fonts-android package in Ubuntu: Incomplete Bug description: libgs9-common now recommends fonts-droid-fallback which is provided by the fonts-android package. fonts-android used to be in main, see LP: #1249132 for the previous MIR. apt-cache show libgs9-common Package: libgs9-common Priority: optional Section: libs Installed-Size: 5353 Maintainer: Ubuntu Developers Original-Maintainer: Debian Printing Team Architecture: all Source: ghostscript Version: 9.19~dfsg+1-0ubuntu2 Recommends: fonts-droid-fallback To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-android/+bug/1621210/+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 1621746] Re: Black Screen, libprotobuf FATAL program was compiled against version 2.6.1 which is not compatible with the installed version (3.0.0)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mir (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1621746 Title: Black Screen, libprotobuf FATAL program was compiled against version 2.6.1 which is not compatible with the installed version (3.0.0) Status in Canonical System Image: Confirmed Status in Mir: Invalid Status in mir package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Invalid Bug description: Ubuntu 16.10 + proposed x86 install Black Screen, libprotobuf FATAL program was compiled against version 2.6.1 which is not compatible with the installed version (3.0.0) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1621746/+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 1623531] Re: unity8 desktop boots to black screen on yakkety daily fresh install
*** This bug is a duplicate of bug 1621746 *** https://bugs.launchpad.net/bugs/1621746 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1621746, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Tags added: black-screen ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Tags added: unity8-desktop ** This bug has been marked a duplicate of bug 1621746 Black Screen, libprotobuf FATAL program was compiled against version 2.6.1 which is not compatible with the installed version (3.0.0) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1623531 Title: unity8 desktop boots to black screen on yakkety daily fresh install Status in Canonical System Image: New Status in unity8 package in Ubuntu: Confirmed Bug description: All new hard installs of yakketty amd64 with unity8/libertine (non- ppa) will boot to black screen on both machines with nVidia and Intel graphics adapters. This makes it virtually impossible to test current/dailys w unity8. Regards.. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: unity8 8.14+16.10.20160831.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Wed Sep 14 10:20:56 2016 InstallationDate: Installed on 2016-09-13 (1 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160913) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) upstart.unity8-filewatcher.log: Failed to open connection to "session" message bus: Failed to connect to socket /run/user/1000/bus: Connection refused Failed to open connection to "session" message bus: Failed to connect to socket /run/user/1000/bus: Connection refused Failed to open connection to "session" message bus: Failed to connect to socket /run/user/1000/bus: Connection refused Failed to open connection to "session" message bus: Failed to connect to socket /run/user/1000/bus: Connection refused To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1623531/+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 1623507] Re: unity-system-compositor crashed with SIGABRT in mir::fatal_error_abort()
I'm marking the nouveau/Mesa crash as high severity. And the secondary Mir crash is only medium because that's not really the problem at all. Here's the Mesa crash: #9 No locals. #10 0x7fe1e4c4f06c in pushbuf_kref () from /tmp/apport_sandbox_hSYpvb/usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 No symbol table info available. #11 0x7fe1e4c4f709 in pushbuf_validate () from /tmp/apport_sandbox_hSYpvb/usr/lib/x86_64-linux-gnu/libdrm_nouveau.so.2 No symbol table info available. #12 0x7fe1e2fb25ef in nv50_state_validate (nv50=nv50@entry=0x5608093d9c40, mask=mask@entry=4096, validate_list=validate_list@entry=0x7fe1e35ef660 , size=size@entry=25, dirty=dirty@entry=0x5608093da018, bufctx=0x5608093dd6f0) at ../../../../../src/gallium/drivers/nouveau/nv50/nv50_state_validate.c:554 state_mask = ret = i = #13 0x7fe1e2fb2797 in nv50_state_validate_3d (nv50=nv50@entry=0x5608093d9c40, mask=mask@entry=4096) at ../../../../../src/gallium/drivers/nouveau/nv50/nv50_state_validate.c:564 ret = #14 0x7fe1e2fb4e01 in nv50_clear (pipe=0x5608093d9c40, buffers=4, color=0x7fe1ebbf5acc, depth=1, stencil=0) at ../../../../../src/gallium/drivers/nouveau/nv50/nv50_surface.c:528 push = 0x56080930e500 fb = 0x5608093dae28 i = j = k = mode = 0 #15 0x7fe1e2c7ea32 in st_Clear (ctx=0x7fe1ebbf4010, mask=2) at ../../../src/mesa/state_tracker/st_cb_clear.c:463 depthRb = stencilRb = quad_buffers = clear_buffers = 4 i = #16 0x7fe1eb9249f1 in mir::renderer::gl::Renderer::render(std::vector, std::allocator > > const&) const (this=0x7fe1d8c0, renderables=...) at ./src/renderers/gl/renderer.cpp:246 ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** Changed in: mesa (Ubuntu) Importance: Undecided => High ** Summary changed: - unity-system-compositor crashed with SIGABRT in mir::fatal_error_abort() + unity-system-compositor crashed with SIGABRT in mir::fatal_error_abort() [nouveau crashed during glClear()] ** Tags added: nouveau ** Summary changed: - unity-system-compositor crashed with SIGABRT in mir::fatal_error_abort() [nouveau crashed during glClear()] + unity-system-compositor crashed with "Failed to schedule page flip", but only after nouveau crashed in glClear(). ** Also affects: libdrm (Ubuntu) Importance: Undecided Status: New ** Changed in: libdrm (Ubuntu) Importance: Undecided => High ** Tags added: unity8-desktop ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: mir Status: New => Triaged ** Changed in: mir (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1623507 Title: unity-system-compositor crashed with "Failed to schedule page flip", but only after nouveau crashed in glClear(). Status in Canonical System Image: New Status in Mir: Triaged Status in libdrm package in Ubuntu: New Status in mesa package in Ubuntu: New Status in mir package in Ubuntu: Triaged Bug description: 16.10 first unity 8 run ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: unity-system-compositor 0.7.1+16.10.20160824-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Wed Sep 14 10:34:45 2016 ExecutablePath: /usr/sbin/unity-system-compositor GraphicsCard: Subsystem: Micro-Star International Co., Ltd. [MSI] Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1462:7817] NVIDIA Corporation G92 [GeForce 9800 GT] [10de:0614] (rev a2) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. G92 [GeForce 9800 GT] [3842:c988] InstallationDate: Installed on 2016-09-14 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160913) ProcCmdline: /usr/sbin/unity-system-compositor --disable-inactivity-policy=true --on-fatal-error-abort --file /run/mir_socket --from-dm-fd 11 --to-dm-fd 14 --vt 7 ProcEnviron: Signal: 6 SourcePackage: unity-system-compositor StacktraceTop: mir::fatal_error_abort(char const*, ...) () from /usr/lib/x86_64-linux-gnu/libmircommon.so.6 ?? () from /usr/lib/x86_64-linux-gnu/mir/server-platform/graphics-mesa-kms.so.10 ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.41 ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.41 ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 Title: unity-system-compositor crashed with SIGABRT in mir::fatal_error_abort() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: version.libdrm: libdrm2 2.4.70-1 version.lightdm: lightdm 1.19.4-0ubuntu1 version.mesa: libegl1-mesa-dev N/A To manage n
[Touch-packages] [Bug 1623507] Re: unity-system-compositor crashed with SIGABRT in mir::fatal_error_abort()
It appears this crash is a secondary crash that's come after an earlier one. We have two compositor threads (two monitors connected). One of them has crashed in the renderer during glClear, which would be a nouveau bug(?). Then our crash handler has tried to clean up and change VTs back to their original state, which races with the other compositor thread that's still running. And once the active VT changes, that second compositor thread will fail to schedule a page flip, which is expected because Mir no longer has DRM mastership. So there are two bugs here: (1) nouveau crashed in glClear. That's the main problem because it was the trigger for the second. (2) Our DRM page flipping code can't deal with flip failures without crashing. But we already know about that thanks to bug 1489689 and bug 1584894. ** Package changed: unity-system-compositor (Ubuntu) => mir (Ubuntu) ** Also affects: mir Importance: Undecided Status: New ** Changed in: mir Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1623507 Title: unity-system-compositor crashed with "Failed to schedule page flip", but only after nouveau crashed in glClear(). Status in Canonical System Image: New Status in Mir: Triaged Status in libdrm package in Ubuntu: New Status in mesa package in Ubuntu: New Status in mir package in Ubuntu: Triaged Bug description: 16.10 first unity 8 run ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: unity-system-compositor 0.7.1+16.10.20160824-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Wed Sep 14 10:34:45 2016 ExecutablePath: /usr/sbin/unity-system-compositor GraphicsCard: Subsystem: Micro-Star International Co., Ltd. [MSI] Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1462:7817] NVIDIA Corporation G92 [GeForce 9800 GT] [10de:0614] (rev a2) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. G92 [GeForce 9800 GT] [3842:c988] InstallationDate: Installed on 2016-09-14 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160913) ProcCmdline: /usr/sbin/unity-system-compositor --disable-inactivity-policy=true --on-fatal-error-abort --file /run/mir_socket --from-dm-fd 11 --to-dm-fd 14 --vt 7 ProcEnviron: Signal: 6 SourcePackage: unity-system-compositor StacktraceTop: mir::fatal_error_abort(char const*, ...) () from /usr/lib/x86_64-linux-gnu/libmircommon.so.6 ?? () from /usr/lib/x86_64-linux-gnu/mir/server-platform/graphics-mesa-kms.so.10 ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.41 ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.41 ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 Title: unity-system-compositor crashed with SIGABRT in mir::fatal_error_abort() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: version.libdrm: libdrm2 2.4.70-1 version.lightdm: lightdm 1.19.4-0ubuntu1 version.mesa: libegl1-mesa-dev N/A To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1623507/+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 1618726] Re: ifup & ifdown crash if multiple interfaces are listed in no-scripts
This bug was fixed in the package ifupdown - 0.8.13ubuntu2 --- ifupdown (0.8.13ubuntu2) yakkety; urgency=medium * Fix a crash when multiple interfaces are specified for no-scripts (LP: #1618726) -- Richard Laager Wed, 31 Aug 2016 02:26:31 -0500 ** Changed in: ifupdown (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1618726 Title: ifup & ifdown crash if multiple interfaces are listed in no-scripts Status in ifupdown package in Ubuntu: Fix Released Status in ifupdown source package in Xenial: Fix Committed Status in ifupdown package in Debian: New Bug description: [Impact] ifup and ifupdown segfault if multiple interfaces are listed in no-scripts This is a trivially reproducible crash in ifup/ifdown, with a patch attached. [Test Case] Steps to reproduce: 1) echo no-scripts foo bar >> /etc/network/interfaces 2) ifup baz Expected results: Unknown interface baz Actual results: Segmentation fault (core dumped) It's irrelevant whether the second interface is on the same no-scripts line or separate one. This will crash just the same: echo no-scripts foo >> /etc/network/interfaces echo no-scripts bar >> /etc/network/interfaces [Regression potential] Seems slight. The patch fixes a clear bug in code that is only used to process the no-scripts (and apparently no-auto-down) stanzas. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1618726/+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 1621210] Re: [MIR] fonts-android
This was simply an oversight when I tried minimize the delta between Debian and Ubuntu, letting the new Ghostscript package be based on Debian's with the only difference that the libopenjpeg shipped with Ghostscript is used and not the system's one. I can simply reapply the change to get it recommending fonts-noto-cjk, giving us the quality advantage. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-android in Ubuntu. https://bugs.launchpad.net/bugs/1621210 Title: [MIR] fonts-android Status in fonts-android package in Ubuntu: Incomplete Bug description: libgs9-common now recommends fonts-droid-fallback which is provided by the fonts-android package. fonts-android used to be in main, see LP: #1249132 for the previous MIR. apt-cache show libgs9-common Package: libgs9-common Priority: optional Section: libs Installed-Size: 5353 Maintainer: Ubuntu Developers Original-Maintainer: Debian Printing Team Architecture: all Source: ghostscript Version: 9.19~dfsg+1-0ubuntu2 Recommends: fonts-droid-fallback To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-android/+bug/1621210/+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 1574324] Re: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?)
Joakim, sure I removed and re-paired the device. I also tried it with 2 identical devices and the issue is reproducible for both of them. My syslog: bluetoothd[3172]: a2dp-sink profile connect failed for 44:5E:F3:BD:87:41: Protocol not available That can probably happen in pulseaudio-module-bluetooth absence, but it's not the case. -- 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/1574324 Title: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?) Status in pulseaudio package in Ubuntu: In Progress Bug description: When I attempt to connect my Jaybird Bluebuds X to Ubuntu 16.04 pulseaudio crashes, this does *NOT* happen with a Jambox which leads me to believe it's an intermittent problem with some hardware. This did not happen on Ubuntu 15.10 (which was an upgrade of 15.04). Ubuntu Release: Description: Ubuntu 16.04 LTS Release: 16.04 Pulseaudio Version: pulseaudio: Installed: 1:8.0-0ubuntu3 Candidate: 1:8.0-0ubuntu3 Version table: *** 1:8.0-0ubuntu3 500 500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status Device info: [bluetooth]# info 44:5E:F3:B4:07:29 Device 44:5E:F3:B4:07:29 Name: BlueBuds X Alias: BlueBuds X Class: 0x240404 Icon: audio-card Paired: yes Trusted: yes Blocked: no Connected: no LegacyPairing: no UUID: Headset (1108--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: Handsfree (111e--1000-8000-00805f9b34fb) UUID: Unknown (80ff--1000-8000-00805f9b34fb) I have also attached a debug dump of Pulseaudio when attempting to connect to the headphones. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1574324/+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 1623484] Re: mir_demo_client_egltriangle crashed with SIGSEGV in dri2_destroy_context() on Yakkety
** Information type changed from Private to Public ** Also affects: mir Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1623484 Title: mir_demo_client_egltriangle crashed with SIGSEGV in dri2_destroy_context() on Yakkety Status in Mir: New Status in mir package in Ubuntu: New Bug description: $ mir_demo_server --launch mir_demo_client_egltriangle Then Alt+F4 to close the triangle Probably problems with mesa releasing resources, as that also appears to be a problem in lp:1623432 ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: mir-demos 0.24.0+16.10.20160815.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Wed Sep 14 13:08:04 2016 ExecutablePath: /usr/bin/mir_demo_client_egltriangle InstallationDate: Installed on 2016-09-06 (8 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160906) ProcCmdline: mir_demo_client_egltriangle SegvAnalysis: Segfault happened at: 0x7fbacaa47a3e:mov0x30(%rbp),%rax PC (0x7fbacaa47a3e) ok source "0x30(%rbp)" (0x0030) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: mir StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 eglTerminate () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 mir_eglapp_shutdown () Title: mir_demo_client_egltriangle crashed with SIGSEGV in eglTerminate() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1623484/+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 1623507] Re: unity-system-compositor crashed with SIGABRT in mir::fatal_error_abort()
** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1623507 Title: unity-system-compositor crashed with SIGABRT in mir::fatal_error_abort() Status in unity-system-compositor package in Ubuntu: New Bug description: 16.10 first unity 8 run ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: unity-system-compositor 0.7.1+16.10.20160824-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Wed Sep 14 10:34:45 2016 ExecutablePath: /usr/sbin/unity-system-compositor GraphicsCard: Subsystem: Micro-Star International Co., Ltd. [MSI] Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1462:7817] NVIDIA Corporation G92 [GeForce 9800 GT] [10de:0614] (rev a2) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. G92 [GeForce 9800 GT] [3842:c988] InstallationDate: Installed on 2016-09-14 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160913) ProcCmdline: /usr/sbin/unity-system-compositor --disable-inactivity-policy=true --on-fatal-error-abort --file /run/mir_socket --from-dm-fd 11 --to-dm-fd 14 --vt 7 ProcEnviron: Signal: 6 SourcePackage: unity-system-compositor StacktraceTop: mir::fatal_error_abort(char const*, ...) () from /usr/lib/x86_64-linux-gnu/libmircommon.so.6 ?? () from /usr/lib/x86_64-linux-gnu/mir/server-platform/graphics-mesa-kms.so.10 ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.41 ?? () from /usr/lib/x86_64-linux-gnu/libmirserver.so.41 ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 Title: unity-system-compositor crashed with SIGABRT in mir::fatal_error_abort() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: version.libdrm: libdrm2 2.4.70-1 version.lightdm: lightdm 1.19.4-0ubuntu1 version.mesa: libegl1-mesa-dev N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-system-compositor/+bug/1623507/+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 1582629] Re: mutt does not properly restore console colors on exit
** Changed in: mutt (Debian) Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ncurses in Ubuntu. https://bugs.launchpad.net/bugs/1582629 Title: mutt does not properly restore console colors on exit Status in mutt package in Ubuntu: Confirmed Status in ncurses package in Ubuntu: New Status in mutt package in Debian: Fix Released Bug description: With release of Ubuntu 16.04 Debian Bug 803405 also hits Ubuntu. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803405 After quitting mutt (with q or x) mutt doesn't restore colors of the console properly, colors are mangled, at least when colors used in mutt are different from console colors. Tested in xfce4-terminal and gnome-terminal, maybe also other terminal or text console is affected. In addition to the information in the debian report this problem only occurs when a .muttrc (even when empty) exists for the user. Without a .muttrc file the behaviour of mutt on leaving is ok. I could confirm this on amd64 and armv7l, so it seems platform independent. Even if the bug is already known in Debian I repost this in Ubuntu just to have documented it also hits Ubuntu and to maybe have some fix for current mutt version (or to get an update to next version in this LTS release). xxx@xxx:~$ lsb_release -rd Description: Ubuntu 16.04 LTS Release: 16.04 xxx@xxx:~$ apt-cache policy mutt mutt: Installiert: 1.5.24-1build1 Installationskandidat: 1.5.24-1build1 Versionstabelle: *** 1.5.24-1build1 500 500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status xxx@xxx:~$ mutt -v Mutt 1.5.24 (2015-08-30) Copyright (C) 1996-2009 Michael R. Elkins und andere. Mutt übernimmt KEINERLEI GEWÄHRLEISTUNG. Starten Sie »mutt -vv«, um weitere Details darüber zu erfahren. Mutt ist freie Software. Sie können es unter bestimmten Bedingungen weitergeben; starten Sie »mutt -vv« für weitere Details. System: Linux 4.4.0-22-generic (x86_64) ncurses: ncurses 6.0.20160213 (compiled with 6.0) libidn: 1.32 (compiled with 1.32) hcache backend: tokyocabinet 1.4.48 Compiler: Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/5/lto-wrapper Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu 5.3.1-9ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-5/README.Bugs --enable-languages=c,ada,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-5 --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-libmpx --enable-plugin --with-system-zlib --disable-browser-plugin --enable-java-awt=gtk --enable-gtk-cairo --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-5-amd64/jre --enable-java-home --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-5-amd64 --with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-5-amd64 --with-arch-directory=amd64 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --enable-objc-gc --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix gcc version 5.3.1 20160216 (Ubuntu 5.3.1-9ubuntu1) Configure options: '--prefix=/usr' '--sysconfdir=/etc' '-- mandir=/usr/share/man' '--with-docdir=/usr/share/doc' '--with- mailpath=/var/mail' '--disable-dependency-tracking' '--enable- compressed' '--enable-debug' '--enable-fcntl' '--enable-hcache' '--enable-gpgme' '--enable-imap' '--enable-smtp' '--enable-pop' '--with-curses' '--with-gnutls' '--with-gss' '--with-idn' '--with- mixmaster' '--with-sasl' '--without-gdbm' '--without-bdb' '--without- qdbm' '--build' 'x86_64-linux-gnu' 'build_alias=x86_64-linux-gnu' 'CFLAGS=-g -O2 -fstack-protector-strong -Wformat -Werror=format- security -Wall' 'LDFLAGS=-Wl,-Bsymbolic-functions -Wl,-z,relro' 'CPPFLAGS=-Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/qdbm' Compilation CFLAGS: -g -O2 -fstack-protector-strong -Wformat -Werror =format-security -Wall Einstellungen bei der Compilierung: -DOMAIN +DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE +USE_FCNTL -USE_FLOCK +USE_POP +USE_IMAP +USE_SMTP -USE_SSL_OPENSSL +USE_SSL_GNUTLS +USE_SASL +USE_GSS +HAVE_GETADDRINFO +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CL
[Touch-packages] [Bug 1623036] Re: Sync krb5 1.14.3+dfsg-2 (main) from Debian unstable (main)
This bug was fixed in the package krb5 - 1.14.3+dfsg-2 Sponsored for Sam Hartman (hartmans) --- krb5 (1.14.3+dfsg-2) UNRELEASED; urgency=medium * Fix gcc -O3, thanks Ben Kaduk/Steve Langasek, Closes: #833798 * Fix kdb5_util create on 32-bit platforms, thanks Greg Hudson, Closes: #834035 -- Sam Hartman Mon, 05 Sep 2016 21:03:14 -0400 ** Changed in: krb5 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1623036 Title: Sync krb5 1.14.3+dfsg-2 (main) from Debian unstable (main) Status in krb5 package in Ubuntu: Fix Released Bug description: Please sync krb5 1.14.3+dfsg-2 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * Merge from Debian unstable. Remaining changes: - Fix uninitialized variable warning on ppc64el. A revised version of this patch has been committed and included in the Debian release. In addition, the Debian version includes a critical fix for KDCs running on 32-bit systems. Changelog entries since current yakkety version 1.14.3+dfsg-1ubuntu1: krb5 (1.14.3+dfsg-2) UNRELEASED; urgency=medium * Fix gcc -O3, thanks Ben Kaduk/Steve Langasek, Closes: #833798 * Fix kdb5_util create on 32-bit platforms, thanks Greg Hudson, Closes: #834035 -- Sam Hartman Mon, 05 Sep 2016 21:03:14 -0400 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1623036/+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 1327412] Re: Delay during PXE Boot, IP-Config gives up
The patch added to nominally fix this issue is incorrect; it is setting the wrong bit in the BOOTP flags field for broadcast: + bootp.flags = htons(0x800); The correct value should be 0x8000. This is causing issues with switches that reject the packet as having bits set in a "must be zero" flag area. RFC 1542 defines the flags field as 16 bits, and the broadcast bit is the most significant bit: 2.2 Definition of the 'flags' Field The standard BOOTP message format defined in [1] includes a two-octet field located between the 'secs' field and the 'ciaddr' field. This field is merely designated as "unused" and its contents left unspecified, although Section 7.1 of [1] does offer the following suggestion: "Before setting up the packet for the first time, it is a good idea to clear the entire packet buffer to all zeros; this will place all fields in their default state." This memo hereby designates this two-octet field as the 'flags' field. This memo hereby defines the most significant bit of the 'flags' field as the BROADCAST (B) flag. The semantics of this flag are discussed in Sections 3.1.1 and 4.1.2 of this memo. The remaining bits of the 'flags' field are reserved for future use. They MUST be set to zero by clients and ignored by servers [...] and relay agents. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1327412 Title: Delay during PXE Boot, IP-Config gives up Status in klibc package in Ubuntu: Fix Released Status in klibc source package in Trusty: Fix Released Status in klibc source package in Wily: Won't Fix Status in klibc source package in Xenial: Fix Released Status in klibc package in Debian: New Bug description: [Impact] PXE booting users with live images or other minimal setups using klibc-utils. [Test case] Attempt to PXE boot using Ubuntu live images; see below for details. [Regression potential] This forces the yiaddr (client requested/current IP) to be set to 0 when sending DHCP messages; currently the messages are DHCPREQUEST and DHCPDISCOVER, which should typically only happen when there is no IP set on the device and it is otherwise unable to receive unicast (on account of not being configured). Should there be a need to send other messages which would require setting the yiaddr value to the current configured IP address, a naive change would break. The yiaddr variable would need to be adjusted to pull value from a new location, or initialized directly by the callers to dhcp_send() where the business logic would reside. --- Attempting to PXE boot both the 12.04.3 and 14.04 Live images. PXE boot works normally (PXE Menu, select desired image, image begins loading), then the boot process hangs while IP-Config attempts to get an IP address: IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP IP-Config: no response after 2 secs - giving up IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP IP-Config: no response after 3 secs - giving up These lines appear very quickly (5 seconds has NOT elapsed), after about a minute, we get this: IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP IP-Config: no response after 4 secs - giving up Some time later, this: IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP IP-Config: no response after 6 secs - giving up Until finally, this: IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP IP-Config: no response after 9 secs - giving up IP-Config: eth0 hardware address e0:db:55:0c:34:7e mtu 1500 DHCP IP-Config: eth1 hardware address e0:db:55:0c:34:80 mtu 1500 DHCP IP-Config: eth0 guessed broadcast address 172.25.11.31 IP-Config: eth0 complete (dhcp from 172.25.10.20): (snip) While watching the DHCP server logs, Ubuntu is either not sending a DHCP Discover at times, or is not replying back with a DHCPRequest during these sessions, presumably ignoring an response from the DHCP server. From the initial booting of the system via PXE, to when Ubuntu finally shows the desktop, almost 12 minutes will have elapsed. I am seeing this same behavior on both 12.04.3 and 14.04. After finding a number of similar erros via Google and no real resolution, I have opened this bug. The system experiencing this issue has multiple ethernet interfaces (actual HW, not a VM), some Google found solutions suggest hard coding DEVICE=eth0 in /etc/initra
[Touch-packages] [Bug 1623718] [NEW] /usr/bin/unity-scope-loader:11:malloc_consolidate:_int_malloc:__GI___libc_malloc:g_malloc:menu_realpath
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding libunity. This problem was most recently seen with version 7.1.4+16.10.20160516-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/ab6c1dc202240f4f35b4d90aba61e6d3e5e453de contains more details. ** Affects: libunity (Ubuntu) Importance: Undecided Status: New ** Tags: xenial yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libunity in Ubuntu. https://bugs.launchpad.net/bugs/1623718 Title: /usr/bin/unity-scope- loader:11:malloc_consolidate:_int_malloc:__GI___libc_malloc:g_malloc:menu_realpath Status in libunity package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding libunity. This problem was most recently seen with version 7.1.4+16.10.20160516-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/ab6c1dc202240f4f35b4d90aba61e6d3e5e453de contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1623718/+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 1593379] Re: systemd 229-4ubuntu6 ignores net.ifnames=0 on USB or /etc/udev/rules.d/80-net-setup-link.rules being a /dev/null symlink
Note that, contrary to the original bug report, this isn't an armhf issue but affects all platforms. We used an external USB ethernet adapter to verify that that fix outlined in #14 also resolves the same issue on Xenial Desktop AMD64. -- 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/1593379 Title: systemd 229-4ubuntu6 ignores net.ifnames=0 on USB or /etc/udev/rules.d/80-net-setup-link.rules being a /dev/null symlink Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Incomplete Status in systemd package in Debian: Fix Released Bug description: Description:Ubuntu 16.04 LTS Release:16.04 The upgrade to systemd/udev 229-4ubuntu6 breaks net.ifnames=0 for USB devices. It appears the regression is here: * Set MAC based name for USB network interfaces only for universally administered (i. e. stable) MACs, not for locally administered (i. e. randomly generated) ones. Drop /lib/systemd/network/90-mac-for-usb.link (as link files don't currently support globs for MACAddress=) and replace with an udev rule in /lib/udev/rules.d/73-special-net-names.rules. (Closes: #812575, LP: #1574483) As Raspberry Pi's use eth0 via USB, this breaks running systems. Before: ii systemd229-4ubuntu4 armhfsystem and service manager ii udev 229-4ubuntu4 armhf/dev/ and hotplug management daem 3: eth0: mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000 link/ether b8:27:eb:16:39:e9 brd ff:ff:ff:ff:ff:ff After: ii systemd 229-4ubuntu6armhf system and service manager ii udev 229-4ubuntu6armhf /dev/ and hotplug management daemon 3: enxb827eb1639e9: mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000 link/ether b8:27:eb:16:39:e9 brd ff:ff:ff:ff:ff:ff cat /proc/cmdline dma.dmachans=0x7f35 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2709.boardrev=0xa01041 bcm2709.serial=0x37b38253 smsc95xx.macaddr=B8:27:EB:B3:82:53 bcm2708_fb.fbswap=1 bcm2709.disk_led_gpio=47 bcm2709.disk_led_active_low=0 sdhci-bcm2708.emmc_clock_freq=25000 vc_mem.mem_base=0x3dc0 vc_mem.mem_size=0x3f00 net.ifnames=0 dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait With the default interfaces configuration, all networking is lost on reboot after upgrade. SRU TEST CASE = * Boot with "net.ifnames=0" on the kernel command line, and connect an USB ethernet device. It will still be called enxDEADBEEF with current xenial. With the -proposed version it will instead keep the kernel name, like "usb0" as intended. * Do "sudo ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules" (the other documented way to disable ifnames) and do the above connect/name check test again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1593379/+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 1621824] Comment bridged from LTC Bugzilla
--- Comment From cdead...@us.ibm.com 2016-09-14 18:54 EDT--- == Comment: #5 - Application Cdeadmin <> - 2016-08-25 12:15:34 == State: Assigned by: cde00 on 14 September 2016 17:54:03 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1621824 Title: MFG:Garrison - Ubuntu 16.04.1 dmesg error "systemd[1]: Failed to start Set console keymap." Status in console-setup package in Ubuntu: Incomplete Bug description: == Comment: #1 - Application Cdeadmin <> - 2016-08-23 15:05:14 == State: Open by: knodelk on 23 August 2016 14:00:43 Seeing the following error message in the Ubuntu dmesg log following IPL to Ubuntu on system with Ubuntu 16.04.1 installed: # dmesg -T --level=alert,crit,err [Tue Aug 23 09:20:12 2016] systemd[1]: Failed to start Set console keymap. This appears to be something that can be ignored so manufacturing will be ignoring this message until directed otherwise. ==> all systemd related messages: # dmesg -T | grep systemd [Tue Aug 23 09:20:12 2016] systemd[1]: systemd 229 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN) [Tue Aug 23 09:20:12 2016] systemd[1]: Detected architecture ppc64-le. [Tue Aug 23 09:20:12 2016] systemd[1]: Set hostname to . [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on Device-mapper event daemon FIFOs. [Tue Aug 23 09:20:12 2016] systemd[1]: Started Forward Password Requests to Wall Directory Watch. [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe. [Tue Aug 23 09:20:12 2016] systemd[1]: Reached target Encrypted Volumes. [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on Syslog Socket. [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on Journal Socket. [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on Journal Socket (/dev/log). [Tue Aug 23 09:20:12 2016] systemd[1]: Reached target User and Group Name Lookups. [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on fsck to fsckd communication Socket. [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on udev Control Socket. [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on LVM2 metadata daemon socket. [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on LVM2 poll daemon socket. [Tue Aug 23 09:20:12 2016] systemd[1]: Created slice User and Session Slice. [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on udev Kernel Socket. [Tue Aug 23 09:20:12 2016] systemd[1]: Created slice System Slice. [Tue Aug 23 09:20:12 2016] systemd[1]: Mounting POSIX Message Queue File System... [Tue Aug 23 09:20:12 2016] systemd[1]: Reached target Slices. [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Create list of required static device nodes for the current kernel... [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Nameserver information manager... [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling... [Tue Aug 23 09:20:12 2016] systemd[1]: Mounting RPC Pipe File System... [Tue Aug 23 09:20:12 2016] systemd[1]: Created slice system-serial\x2dgetty.slice. [Tue Aug 23 09:20:12 2016] systemd[1]: Started Read required files in advance. [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Load Kernel Modules... [Tue Aug 23 09:20:12 2016] systemd[1]: Mounting Debug File System... [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on Journal Audit Socket. [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Journal Service... [Tue Aug 23 09:20:12 2016] systemd[1]: Mounting Huge Pages File System... [Tue Aug 23 09:20:12 2016] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point. [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Uncomplicated firewall... [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Set console keymap... [Tue Aug 23 09:20:12 2016] systemd[1]: Mounted Debug File System. [Tue Aug 23 09:20:12 2016] systemd[1]: Mounted POSIX Message Queue File System. [Tue Aug 23 09:20:12 2016] systemd[1]: Mounted Huge Pages File System. [Tue Aug 23 09:20:12 2016] systemd[1]: Started Create list of required static device nodes for the current kernel. [Tue Aug 23 09:20:12 2016] systemd[1]: Started Nameserver information manager. [Tue Aug 23 09:20:12 2016] systemd[1]: Started Uncomplicated firewall. [Tue Aug 23 09:20:12 2016] systemd[1]: keyboard-setup.service: Main process exited, code=exited, status=1/FAILURE [Tue Aug 23 09:20:12 2016] systemd[1]: Failed to start Set console keymap. [Tue Aug 23 09:20:12 2016] systemd[1]: keyboard-setup.service: Unit entered failed state. [Tue Aug 23 09:20:12 2016] systemd[1]: keyboard-setup.service: Failed with result 'exit-code'. [Tue Aug 23 09:20:12 2016] systemd[1]: Mounted RP
[Touch-packages] [Bug 1623666] Re: iOS10 will not connect to Ubuntu
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libimobiledevice (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1623666 Title: iOS10 will not connect to Ubuntu Status in libimobiledevice package in Ubuntu: Confirmed Bug description: Plug in iOS10 device, and it doesn't show the documents on it. Please package the recent fix in libimobiledevice: https://github.com/libimobiledevice/libimobiledevice/issues/327 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1623666/+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 1621824] Re: MFG:Garrison - Ubuntu 16.04.1 dmesg error "systemd[1]: Failed to start Set console keymap."
> Here is the requested command output: > # systemctl status -l console-setup.service This is not the systemd unit producing that message; the correct unit is keyboard-setup. Please instead provide the output of: # systemctl status -l keyboard-setup.service ** Changed in: console-setup (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1621824 Title: MFG:Garrison - Ubuntu 16.04.1 dmesg error "systemd[1]: Failed to start Set console keymap." Status in console-setup package in Ubuntu: Incomplete Bug description: == Comment: #1 - Application Cdeadmin <> - 2016-08-23 15:05:14 == State: Open by: knodelk on 23 August 2016 14:00:43 Seeing the following error message in the Ubuntu dmesg log following IPL to Ubuntu on system with Ubuntu 16.04.1 installed: # dmesg -T --level=alert,crit,err [Tue Aug 23 09:20:12 2016] systemd[1]: Failed to start Set console keymap. This appears to be something that can be ignored so manufacturing will be ignoring this message until directed otherwise. ==> all systemd related messages: # dmesg -T | grep systemd [Tue Aug 23 09:20:12 2016] systemd[1]: systemd 229 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN) [Tue Aug 23 09:20:12 2016] systemd[1]: Detected architecture ppc64-le. [Tue Aug 23 09:20:12 2016] systemd[1]: Set hostname to . [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on Device-mapper event daemon FIFOs. [Tue Aug 23 09:20:12 2016] systemd[1]: Started Forward Password Requests to Wall Directory Watch. [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe. [Tue Aug 23 09:20:12 2016] systemd[1]: Reached target Encrypted Volumes. [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on Syslog Socket. [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on Journal Socket. [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on Journal Socket (/dev/log). [Tue Aug 23 09:20:12 2016] systemd[1]: Reached target User and Group Name Lookups. [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on fsck to fsckd communication Socket. [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on udev Control Socket. [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on LVM2 metadata daemon socket. [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on LVM2 poll daemon socket. [Tue Aug 23 09:20:12 2016] systemd[1]: Created slice User and Session Slice. [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on udev Kernel Socket. [Tue Aug 23 09:20:12 2016] systemd[1]: Created slice System Slice. [Tue Aug 23 09:20:12 2016] systemd[1]: Mounting POSIX Message Queue File System... [Tue Aug 23 09:20:12 2016] systemd[1]: Reached target Slices. [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Create list of required static device nodes for the current kernel... [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Nameserver information manager... [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling... [Tue Aug 23 09:20:12 2016] systemd[1]: Mounting RPC Pipe File System... [Tue Aug 23 09:20:12 2016] systemd[1]: Created slice system-serial\x2dgetty.slice. [Tue Aug 23 09:20:12 2016] systemd[1]: Started Read required files in advance. [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Load Kernel Modules... [Tue Aug 23 09:20:12 2016] systemd[1]: Mounting Debug File System... [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on Journal Audit Socket. [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Journal Service... [Tue Aug 23 09:20:12 2016] systemd[1]: Mounting Huge Pages File System... [Tue Aug 23 09:20:12 2016] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point. [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Uncomplicated firewall... [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Set console keymap... [Tue Aug 23 09:20:12 2016] systemd[1]: Mounted Debug File System. [Tue Aug 23 09:20:12 2016] systemd[1]: Mounted POSIX Message Queue File System. [Tue Aug 23 09:20:12 2016] systemd[1]: Mounted Huge Pages File System. [Tue Aug 23 09:20:12 2016] systemd[1]: Started Create list of required static device nodes for the current kernel. [Tue Aug 23 09:20:12 2016] systemd[1]: Started Nameserver information manager. [Tue Aug 23 09:20:12 2016] systemd[1]: Started Uncomplicated firewall. [Tue Aug 23 09:20:12 2016] systemd[1]: keyboard-setup.service: Main process exited, code=exited, status=1/FAILURE [Tue Aug 23 09:20:12 2016] systemd[1]: Failed to start Set console keymap. [Tue Aug 23 09:20:12 2016] systemd[1]: keyboard-setup.service: Unit entered failed state. [Tue Aug 23 09
[Touch-packages] [Bug 1623638] Re: package libssl1.0.0:i386 1.0.2g-1ubuntu4.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 29
>From the terminal log: Can't locate object method "new" via package "Text::Iconv" (perhaps you forgot to load "Text::Iconv"?) at /usr/share/perl5/Debconf/Encoding.pm line 65. ** Also affects: debconf (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1623638 Title: package libssl1.0.0:i386 1.0.2g-1ubuntu4.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 29 Status in debconf package in Ubuntu: New Status in openssl package in Ubuntu: New Bug description: My 14.04 has never worked properly, The manager has a child lockout and will not function. The cd and usb drive do not work. Terminal will not carry out commands. Downloads and upgrades have problems possibly due to my Xplornet high speed server. My computer is an Aspire 5542-1615, 3 GB memory, 320 GB HDD , DVD super multi Dl drive. My computer is clean with a lot of empty disk space. I can only use the computer for the internet and to print. All the repairs don't seem to work so as to allow an upgrade to Ubuntu 16.04. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libssl1.0.0:i386 1.0.2g-1ubuntu4.2 ProcVersionSignature: Ubuntu 3.13.0-79.123-generic 3.13.11-ckt33 Uname: Linux 3.13.0-79-generic i686 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: i386 Date: Wed Sep 14 11:07:57 2016 DuplicateSignature: package:libssl1.0.0:i386:1.0.2g-1ubuntu4.2:subprocess installed post-installation script returned error exit status 29 ErrorMessage: subprocess installed post-installation script returned error exit status 29 InstallationDate: Installed on 2015-12-19 (270 days ago) InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140723) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: openssl Title: package libssl1.0.0:i386 1.0.2g-1ubuntu4.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 29 UpgradeStatus: Upgraded to trusty on 2016-09-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1623638/+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 1574278] Re: AbiWord text cursor starts to flicker after adding some text
Uwe, do you have a method to reproduce flickering with the GTK_THEME=adwaita? Even so, the workaround is a major improvement, and the best we have, so I'll add it to my OLPC derivative of the Ubuntu sugar-write-activity package. http://dev.laptop.org/~quozl/y/1bkIWb.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1574278 Title: AbiWord text cursor starts to flicker after adding some text Status in AbiWord: Invalid Status in abiword package in Ubuntu: Invalid Status in gtk+3.0 package in Ubuntu: Fix Released Status in lubuntu-artwork package in Ubuntu: Invalid Status in abiword source package in Xenial: Invalid Status in gtk+3.0 source package in Xenial: Confirmed Status in lubuntu-artwork source package in Xenial: Invalid Bug description: After adding some text in a new document, the entire document (including gray page background, text, text cursor) starts to flicker very fast. The UI above does not flicker. This happens too on a different system in VirtualBox. (Lubuntu 16.04 i386) Workaround == 1. Open the Lubuntu menu. 2. Open Preferences>Customize Look and Feel 3. Change the theme to something other than Lubuntu-default or Lubuntu-dark-panel ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: abiword 3.0.1-6 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic i686 ApportVersion: 2.20.1-0ubuntu2 Architecture: i386 CurrentDesktop: LXDE Date: Sun Apr 24 16:12:14 2016 ExecutablePath: /usr/bin/abiword InstallationDate: Installed on 2016-04-22 (2 days ago) InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release i386 (20151021) ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: abiword UpgradeStatus: Upgraded to xenial on 2016-04-22 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/abiword/+bug/1574278/+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 1593379] Re: systemd 229-4ubuntu6 ignores net.ifnames=0 on USB or /etc/udev/rules.d/80-net-setup-link.rules being a /dev/null symlink
The problem appears to be down to a syntax error - here's the fix we're
using as a patch against current systemd in Xenial:
Splitting the IMPORT and ENV/GOTO directives onto separate lines gets
things working.
With the patch deployed, the kernel parameter works as specified,
allowing us to access hosts remotely after boot. We've tested the patch
both with and without net.ifnames boot parameter and the USB ethernet
device is assigned correctly as expected for each mode.
This should fix things for Raspberry Pi users as well..
--- /lib/udev/rules.d/73-usb-net-by-mac.rules.orig 2016-09-14
20:40:11.26878 +
+++ /lib/udev/rules.d/73-usb-net-by-mac.rules 2016-09-14 20:42:05.71834
+
@@ -3,7 +3,8 @@
# is 0). Don't do this when ifnames is disabled via kernel command line or
# customizing/disabling 80-net-setup-link.rules.
-IMPORT{cmdline}="net.ifnames", ENV{net.ifnames}=="0", GOTO="usb_net_by_mac_end"
+IMPORT{cmdline}="net.ifnames"
+ENV{net.ifnames}=="0", GOTO="usb_net_by_mac_end"
ACTION=="add", SUBSYSTEM=="net", SUBSYSTEMS=="usb", NAME=="", \
ATTR{address}=="?[014589cd]:*", \
--
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/1593379
Title:
systemd 229-4ubuntu6 ignores net.ifnames=0 on USB or
/etc/udev/rules.d/80-net-setup-link.rules being a /dev/null symlink
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Xenial:
Incomplete
Status in systemd package in Debian:
Fix Released
Bug description:
Description:Ubuntu 16.04 LTS
Release:16.04
The upgrade to systemd/udev 229-4ubuntu6 breaks net.ifnames=0 for USB
devices.
It appears the regression is here:
* Set MAC based name for USB network interfaces only for universally
administered (i. e. stable) MACs, not for locally administered (i. e.
randomly generated) ones. Drop /lib/systemd/network/90-mac-for-usb.link
(as link files don't currently support globs for MACAddress=) and replace
with an udev rule in /lib/udev/rules.d/73-special-net-names.rules.
(Closes: #812575, LP: #1574483)
As Raspberry Pi's use eth0 via USB, this breaks running systems.
Before:
ii systemd229-4ubuntu4 armhfsystem and service manager
ii udev 229-4ubuntu4 armhf/dev/ and hotplug management daem
3: eth0: mtu 1500 qdisc pfifo_fast state UP
mode DEFAULT group default qlen 1000
link/ether b8:27:eb:16:39:e9 brd ff:ff:ff:ff:ff:ff
After:
ii systemd 229-4ubuntu6armhf
system and service manager
ii udev 229-4ubuntu6armhf
/dev/ and hotplug management daemon
3: enxb827eb1639e9: mtu 1500 qdisc
pfifo_fast state UP mode DEFAULT group default qlen 1000
link/ether b8:27:eb:16:39:e9 brd ff:ff:ff:ff:ff:ff
cat /proc/cmdline
dma.dmachans=0x7f35 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416
bcm2709.boardrev=0xa01041 bcm2709.serial=0x37b38253
smsc95xx.macaddr=B8:27:EB:B3:82:53 bcm2708_fb.fbswap=1 bcm2709.disk_led_gpio=47
bcm2709.disk_led_active_low=0 sdhci-bcm2708.emmc_clock_freq=25000
vc_mem.mem_base=0x3dc0 vc_mem.mem_size=0x3f00 net.ifnames=0
dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2
rootfstype=ext4 elevator=deadline rootwait
With the default interfaces configuration, all networking is lost on
reboot after upgrade.
SRU TEST CASE
=
* Boot with "net.ifnames=0" on the kernel command line, and connect an USB
ethernet device. It will still be called enxDEADBEEF with current xenial. With
the -proposed version it will instead keep the kernel name, like "usb0" as
intended.
* Do "sudo ln -s /dev/null /etc/udev/rules.d/80-net-setup-link.rules"
(the other documented way to disable ifnames) and do the above
connect/name check test again.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1593379/+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 1622248] Re: XPS 13 Ubuntu 16.04 No sound via internal speakers
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1622248 Title: XPS 13 Ubuntu 16.04 No sound via internal speakers Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal speakers stopped working. I upgraded from Ubuntu 14.04 to Ubuntu 16.04 but to no avail. If I connect via Thunderbolt to an Thunderbolt display, the speakers of the display do work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1622248/+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 1574278] Re: AbiWord text cursor starts to flicker after adding some text
I wrote: I can confirm [...] the effectiveness of the work-around "GTK_THEME=adwaita abiword". With some more testing I have to qualify that statement a bit: With the adwaita theme the behaviour is clearly improved compared to the default. I have not seen text flickering so far. But the cursor still flickers a bit and sometimes disappears completely until some new text is entered. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1574278 Title: AbiWord text cursor starts to flicker after adding some text Status in AbiWord: Invalid Status in abiword package in Ubuntu: Invalid Status in gtk+3.0 package in Ubuntu: Fix Released Status in lubuntu-artwork package in Ubuntu: Invalid Status in abiword source package in Xenial: Invalid Status in gtk+3.0 source package in Xenial: Confirmed Status in lubuntu-artwork source package in Xenial: Invalid Bug description: After adding some text in a new document, the entire document (including gray page background, text, text cursor) starts to flicker very fast. The UI above does not flicker. This happens too on a different system in VirtualBox. (Lubuntu 16.04 i386) Workaround == 1. Open the Lubuntu menu. 2. Open Preferences>Customize Look and Feel 3. Change the theme to something other than Lubuntu-default or Lubuntu-dark-panel ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: abiword 3.0.1-6 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic i686 ApportVersion: 2.20.1-0ubuntu2 Architecture: i386 CurrentDesktop: LXDE Date: Sun Apr 24 16:12:14 2016 ExecutablePath: /usr/bin/abiword InstallationDate: Installed on 2016-04-22 (2 days ago) InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release i386 (20151021) ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: abiword UpgradeStatus: Upgraded to xenial on 2016-04-22 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/abiword/+bug/1574278/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1574278] Re: AbiWord text cursor starts to flicker after adding some text
Yes, but we can't force an app to use a custom theme, modifying all Ubuntu distros as a workaround, instead of actually fixing the problem. Apps must use any theme. On Wed, 14 Sep 2016 23:51 Uwe Geuder, wrote: > Using Xubuntu 16.04 with all updates here. > > I can confirm both the original flickering and the effectiveness of the > work-around "GTK_THEME=adwaita abiword". > > -- > You received this bug notification because you are a member of Lubuntu > Packages Team, which is subscribed to the bug report. > https://bugs.launchpad.net/bugs/1574278 > > Title: > AbiWord text cursor starts to flicker after adding some text > > Status in AbiWord: > Invalid > Status in abiword package in Ubuntu: > Invalid > Status in gtk+3.0 package in Ubuntu: > Fix Released > Status in lubuntu-artwork package in Ubuntu: > Invalid > Status in abiword source package in Xenial: > Invalid > Status in gtk+3.0 source package in Xenial: > Confirmed > Status in lubuntu-artwork source package in Xenial: > Invalid > > Bug description: > After adding some text in a new document, the entire document > (including gray page background, text, text cursor) starts to flicker > very fast. The UI above does not flicker. This happens too on a > different system in VirtualBox. (Lubuntu 16.04 i386) > > Workaround > == > 1. Open the Lubuntu menu. > 2. Open Preferences>Customize Look and Feel > 3. Change the theme to something other than Lubuntu-default or > Lubuntu-dark-panel > > > ProblemType: Bug > DistroRelease: Ubuntu 16.04 > Package: abiword 3.0.1-6 > ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 > Uname: Linux 4.4.0-21-generic i686 > ApportVersion: 2.20.1-0ubuntu2 > Architecture: i386 > CurrentDesktop: LXDE > Date: Sun Apr 24 16:12:14 2016 > ExecutablePath: /usr/bin/abiword > InstallationDate: Installed on 2016-04-22 (2 days ago) > InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release i386 > (20151021) > ProcEnviron: >LANGUAGE=de_DE >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=de_DE.UTF-8 >SHELL=/bin/bash > SourcePackage: abiword > UpgradeStatus: Upgraded to xenial on 2016-04-22 (2 days ago) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/abiword/+bug/1574278/+subscriptions > > Launchpad-Notification-Type: bug > Launchpad-Bug: product=abiword; status=Invalid; importance=High; > assignee=None; > Launchpad-Bug: distribution=ubuntu; sourcepackage=abiword; > component=universe; status=Invalid; importance=High; assignee=None; > Launchpad-Bug: distribution=ubuntu; sourcepackage=gtk+3.0; component=main; > status=Fix Released; importance=Undecided; assignee=None; > Launchpad-Bug: distribution=ubuntu; sourcepackage=lubuntu-artwork; > component=universe; status=Invalid; importance=High; assignee=None; > Launchpad-Bug: distribution=ubuntu; distroseries=xenial; > sourcepackage=abiword; component=universe; status=Invalid; > importance=Undecided; assignee=None; > Launchpad-Bug: distribution=ubuntu; distroseries=xenial; > sourcepackage=gtk+3.0; component=main; status=Confirmed; > importance=Undecided; assignee=None; > Launchpad-Bug: distribution=ubuntu; distroseries=xenial; > sourcepackage=lubuntu-artwork; component=universe; status=Invalid; > importance=Undecided; assignee=None; > Launchpad-Bug-Tags: apport-bug i386 iso-testing package-qa-testing xenial > Launchpad-Bug-Information-Type: Public > Launchpad-Bug-Private: no > Launchpad-Bug-Security-Vulnerability: no > Launchpad-Bug-Commenters: aesouza2008 antony-seedhouse cdeweerd fricki > gilir janitor jbicha jothro kiwikaki nio-wiklund quozl ruediger.kupper > sondra.kinsey teward tukozaki ubuntulp-ugeuder ubuntuqa whgiii-q > Launchpad-Bug-Reporter: Kiwikaki (kiwikaki) > Launchpad-Bug-Modifier: Uwe Geuder (ubuntulp-ugeuder) > Launchpad-Message-Rationale: Subscriber @lubuntu-packaging > Launchpad-Message-For: lubuntu-packaging > -- Rafael Laguna Graphics & UIX Design · www.rafaellaguna.net Lubuntu Artwork Team · Ubuntu Design Team -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1574278 Title: AbiWord text cursor starts to flicker after adding some text Status in AbiWord: Invalid Status in abiword package in Ubuntu: Invalid Status in gtk+3.0 package in Ubuntu: Fix Released Status in lubuntu-artwork package in Ubuntu: Invalid Status in abiword source package in Xenial: Invalid Status in gtk+3.0 source package in Xenial: Confirmed Status in lubuntu-artwork source package in Xenial: Invalid Bug description: After adding some text in a new document, the entire document (including gray page background, text, text cursor) starts to flicker very fast. The UI above does not flicker. This happens too on a different system in VirtualBox. (Lubuntu 16.04 i386) Workaround == 1. Open the Lubuntu menu. 2. Open Preferenc
[Touch-packages] [Bug 1574278] Re: AbiWord text cursor starts to flicker after adding some text
Using Xubuntu 16.04 with all updates here. I can confirm both the original flickering and the effectiveness of the work-around "GTK_THEME=adwaita abiword". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1574278 Title: AbiWord text cursor starts to flicker after adding some text Status in AbiWord: Invalid Status in abiword package in Ubuntu: Invalid Status in gtk+3.0 package in Ubuntu: Fix Released Status in lubuntu-artwork package in Ubuntu: Invalid Status in abiword source package in Xenial: Invalid Status in gtk+3.0 source package in Xenial: Confirmed Status in lubuntu-artwork source package in Xenial: Invalid Bug description: After adding some text in a new document, the entire document (including gray page background, text, text cursor) starts to flicker very fast. The UI above does not flicker. This happens too on a different system in VirtualBox. (Lubuntu 16.04 i386) Workaround == 1. Open the Lubuntu menu. 2. Open Preferences>Customize Look and Feel 3. Change the theme to something other than Lubuntu-default or Lubuntu-dark-panel ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: abiword 3.0.1-6 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic i686 ApportVersion: 2.20.1-0ubuntu2 Architecture: i386 CurrentDesktop: LXDE Date: Sun Apr 24 16:12:14 2016 ExecutablePath: /usr/bin/abiword InstallationDate: Installed on 2016-04-22 (2 days ago) InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release i386 (20151021) ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: abiword UpgradeStatus: Upgraded to xenial on 2016-04-22 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/abiword/+bug/1574278/+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 1606078] Re: No sound with Ubuntu 16.04
Might note after adding recommended line, terminal note reads: ** (gedit:5965): WARNING **: Set document metadata failed: Setting attribute metadata::gedit-position not supported -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1606078 Title: No sound with Ubuntu 16.04 Status in alsa-driver package in Ubuntu: Confirmed Bug description: After a fresh install of Ubuntu 16.04.1 on an LG S1 Express Dual laptop there was no sound from the speakers unless external speakers where hooked to the headphones socket. This applies to the Ubuntu Mate, Xubuntu and Lubuntu variants. This laptop was working fine for all previous releases up to 14.04. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bashar 3263 F pulseaudio CurrentDesktop: Unity Date: Mon Jul 25 01:51:19 2016 InstallationDate: Installed on 2016-07-24 (0 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bashar 3263 F pulseaudio Symptom_Jack: Line Out, Internal Symptom_Type: No sound at all Title: [S1-M401E1, Realtek ALC880, Line Out, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/16/2006 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: RKYWSF0B dmi.board.name: ROCKY dmi.board.vendor: LG Electronics dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LG Electronics dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrRKYWSF0B:bd02/16/2006:svnLGElectronics:pnS1-M401E1:pvrNotApplicable:rvnLGElectronics:rnROCKY:rvrNotApplicable:cvnLGElectronics:ct10:cvrN/A: dmi.product.name: S1-M401E1 dmi.product.version: Not Applicable dmi.sys.vendor: LG Electronics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1606078/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1585084] Re: Volume notification keeps popping up constantly(the notifyosd bubble on top-right corner)
Thanks for your help. Log attached. ** Attachment added: "pulseverbose.log" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1585084/+attachment/4741175/+files/pulseverbose.log -- 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/1585084 Title: Volume notification keeps popping up constantly(the notifyosd bubble on top-right corner) Status in pulseaudio package in Ubuntu: Incomplete Bug description: I upgraded to Ubuntu 16.04 yesterday, I did a clean install while preserving the home directory which is mounted in a separate partition. Even during the installation I had constant volume notification bubble appearing on the top-right corner of my screen, it would come and go about twice every minute. I just thought it was due to installing hardware drivers or something but the problem persisted even when I booted into the freshly installed system. I did some searching and two users reported the exact problem. And one more suggested this happens because constant disconnect and reconnect of the sound card which makes sense as the sound settings flashes briefly during every popup. Someone on IRC suggested to kill pulseaudio and thus restart it, that does not fix the issue. I also tried the Live environment thinking it might be due to some old config files in home partition (which was preserved during upgrade), but this problem happens in the live environment as well, which makes sense because it was present during installation as well. Users with the same issue: http://ubuntuforums.org/showthread.php?t=2323815 http://askubuntu.com/questions/773008/constant-volume-osd-in-16-04 http://askubuntu.com/questions/767466/sound-card-being-disconnected-reconnected-constantly Thanks. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: sidd 1651 F pulseaudio /dev/snd/controlC0: sidd 1651 F pulseaudio /dev/snd/controlC1: sidd 1651 F pulseaudio CurrentDesktop: Unity Date: Tue May 24 12:31:12 2016 InstallationDate: Installed on 2016-05-23 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/23/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0705 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 EVO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0705:bd08/23/2011:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKComputerINC.:rnM5A97EVO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1585084/+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 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses
To include dhclient in the initramfs; we should have a task for isc-dhcp too. ** Also affects: isc-dhcp (Ubuntu) Importance: Undecided Status: New ** Changed in: isc-dhcp (Ubuntu) Status: New => In Progress ** Changed in: initramfs-tools (Ubuntu) Status: Triaged => In Progress ** Changed in: isc-dhcp (Ubuntu) Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) ** Changed in: isc-dhcp (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1621507 Title: initramfs-tools configure_networking() fails to dhcp ipv6 addresses Status in MAAS: Confirmed Status in initramfs-tools package in Ubuntu: In Progress Status in isc-dhcp package in Ubuntu: In Progress Status in klibc package in Ubuntu: New Status in klibc package in Debian: New Bug description: initramfs' configure_networking function uses ipconfig to configure the network. ipconfig does not support dhcpv6. See: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=627164 Anyone wanting to netboot in an ipv6-only environment is affected. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1621507/+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 1411866] Re: Unconstrained download to a directory w/o permission crashes udm
This bug was fixed in the package ubuntu-download-manager - 1.3+16.10.20160909.1-0ubuntu1 --- ubuntu-download-manager (1.3+16.10.20160909.1-0ubuntu1) yakkety; urgency=medium [ Florian Boucault ] * Fixes for crossbuilding. [ Michael Sheldon ] * Make user visible strings translatable (LP: #1618892) * Fix queue blocking and error reporting when file path is unwritable (LP: #1411866) * Remove dependency on qt5-default metapackage -- Michael Sheldon Fri, 09 Sep 2016 11:49:03 + ** Changed in: ubuntu-download-manager (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-download-manager in Ubuntu. https://bugs.launchpad.net/bugs/1411866 Title: Unconstrained download to a directory w/o permission crashes udm Status in ubuntu-download-manager package in Ubuntu: Fix Released Bug description: One of my system-image test suites creates a destination directory that is unwritable. Previously, when UDM tried to download a file to this while unconstrained, it would issue an error with "Permission denied" in the error output. Now however, udm appears to either crash or freeze. It becomes unresponsive to D-Bus and the error signal is never received, thus failing the test. Further, since it usually freezes, this affects future tests because udm will not exit when its D-Bus exit method is called. Eventually it gets signal killed and then the tests can proceed. For now, I will have to skip these tests when s-i runs under udm. The same tests pass for the curl-based downloader. % dpkg-query -W ubuntu-download-manager ubuntu-download-manager 0.9+15.04.20141202-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-download-manager/+bug/1411866/+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 1618892] Re: User visible strings aren't translated
This bug was fixed in the package ubuntu-download-manager - 1.3+16.10.20160909.1-0ubuntu1 --- ubuntu-download-manager (1.3+16.10.20160909.1-0ubuntu1) yakkety; urgency=medium [ Florian Boucault ] * Fixes for crossbuilding. [ Michael Sheldon ] * Make user visible strings translatable (LP: #1618892) * Fix queue blocking and error reporting when file path is unwritable (LP: #1411866) * Remove dependency on qt5-default metapackage -- Michael Sheldon Fri, 09 Sep 2016 11:49:03 + ** Changed in: ubuntu-download-manager (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-download-manager in Ubuntu. https://bugs.launchpad.net/bugs/1618892 Title: User visible strings aren't translated Status in ubuntu-download-manager package in Ubuntu: Fix Released Bug description: UDM currently has no translations infrastructure. The majority of strings displayed to users by UDM are QNetworkReply error messages which are already translated by Qt, however there are still a number of custom errors that aren't translated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-download-manager/+bug/1618892/+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 1623666] [NEW] iOS10 will not connect to Ubuntu
Public bug reported: Plug in iOS10 device, and it doesn't show the documents on it. Please package the recent fix in libimobiledevice: https://github.com/libimobiledevice/libimobiledevice/issues/327 ** Affects: libimobiledevice (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1623666 Title: iOS10 will not connect to Ubuntu Status in libimobiledevice package in Ubuntu: New Bug description: Plug in iOS10 device, and it doesn't show the documents on it. Please package the recent fix in libimobiledevice: https://github.com/libimobiledevice/libimobiledevice/issues/327 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1623666/+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 1540702] Re: While resizing Qt apps window contents jitter about erratically (including during animations)
** Changed in: unity8 (Ubuntu) Assignee: (unassigned) => Daniel d'Andrada (dandrader) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1540702 Title: While resizing Qt apps window contents jitter about erratically (including during animations) Status in Canonical System Image: Confirmed Status in QtMir: Confirmed Status in qtmir package in Ubuntu: Confirmed Status in qtubuntu package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: Resizing a window (Scopes) the window contents jitter about erratically. Obviously they should appear to remain stationary unless being significantly repositioned. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity8 8.11+16.04.20160129-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 Date: Tue Feb 2 10:23:02 2016 InstallationDate: Installed on 2015-12-03 (60 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151202) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) upstart.unity8-dash.log: ubuntumirclient: Got invalid serialized mime data. Ignoring it. ubuntumirclient: Got invalid serialized mime data. Ignoring it. ubuntumirclient: Got invalid serialized mime data. Ignoring it. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1540702/+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 1620754] Re: hash(datetime.datetime(...)) fails with python3.5 on armhf (on an arm64 host) with a bus error
Hello Matthias, or anyone else affected, Accepted python3.5 into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/python3.5/3.5.2-2~16.04 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: python3.5 (Ubuntu Xenial) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3.4 in Ubuntu. https://bugs.launchpad.net/bugs/1620754 Title: hash(datetime.datetime(...)) fails with python3.5 on armhf (on an arm64 host) with a bus error Status in Python: New Status in python-cryptography package in Ubuntu: Fix Released Status in python3.4 package in Ubuntu: Invalid Status in python3.5 package in Ubuntu: Fix Released Status in python-cryptography source package in Trusty: New Status in python3.4 source package in Trusty: Fix Committed Status in python3.5 source package in Trusty: New Status in python3.5 source package in Xenial: Fix Committed Bug description: seen with https://launchpad.net/ubuntu/+source/python-cryptography/1.4-2/+build/10476934 https://launchpad.net/ubuntu/+source/python-cryptography/1.5-1/+build/10678695 the TestInvalidityDate.test_invalid_invalidity_date test is the first one to fail with a bus error. No reasonable traceback from gdb. Trying to build python3.5, python-cffi and python-cryptography with -mno-unaligned-access doesn't fix the issue (buildds running on a 64bit kernel). To manage notifications about this bug go to: https://bugs.launchpad.net/python/+bug/1620754/+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 1622987] Re: Auto-completion seems broken with umount command
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: util-linux (Ubuntu) Status: New => Confirmed -- 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/1622987 Title: Auto-completion seems broken with umount command Status in util-linux package in Ubuntu: Confirmed Bug description: I'm using Xubuntu with the devel version. I've seen this bug with Ubuntu also, in the daily version. The auto-completion of the command 'umount' seems broken. I have an usb key called "Xubuntu 16.10 amd64". I verify that with the command lsblk. Then, I type 'umount /media' then I press 'tab' to have the autocompletion. With 16.04, the autocompletion completes correctly with backslash : "/media/nairwolf/\ Xubuntu\ amd64" But, now, with Yakkety, the autocompletion stops before the first space. There is a screenshot to explain what I have : https://i.imgur.com/UOyUEyn.png Don't forget that I'm typing only "umount /media", and then, I press tab to have the autocompletion. And this picture is the result of the auto-completion. I'm unable to reproduce that with other basic command like "ls", "cd" or "rm". That means if I'm typing "ls /media", then "TAB" it will be completed correctly. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: util-linux 2.28.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Sep 13 13:07:22 2016 InstallationDate: Installed on 2016-08-18 (25 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: util-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1622987/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1576692] Re: fully support package installation in systemd
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1576692 Title: fully support package installation in systemd Status in cloud-init: Fix Released Status in cloud-init package in Ubuntu: Fix Released Status in init-system-helpers package in Ubuntu: Fix Released Status in cloud-init source package in Xenial: Fix Committed Status in init-system-helpers source package in Xenial: Fix Committed Bug description: in cloud-init users can install packages via cloud-config: #cloud-config packages: [apache2] Due to some intricacies of systemd and service installation that doesn't work all that well. We fixed the issue for simple services that do not have any dependencies on other services, or at least don't check those dependencies well under bug 1575572. We'd like to have a way to fully support this in cloud-init. Related bugs: * bug 1575572: apache2 fails to start if installed via cloud config (on Xenial) * bug 1611973: postgresql@9.5-main service not started if postgres installed via cloud-init * bug 1621336: snapd.boot-ok.service hangs eternally on cloud image upgrades (snapd packaging bug, but this cloud-init fix will workaround it) * bug 1620780: dev-sda2.device job running and times out * bug 1623570: Azure: cannot start walinux agent (Transaction order is cyclic.) SRU INFORMATION === FIX for init-system-helpers: https://anonscm.debian.org/cgit/collab-maint/init-system-helpers.git/commit/?id=1460d6a02 REGRESSION POTENTIAL for init-system-helpers: This changes invoke-rc.d and service, two very central pieces of packaging infrastructure. Errors in it will break installation/upgrades of packages or /etc/network/if-up.d/ hooks and the like. This changes the condition when systemd units get started without their dependencies, and the condition gets weakened. This means that behaviour in a booted system is unchanged, but during boot this could change the behaviour of if- up.d/ hooks (although they have never been defined well during boot anyway). However, I tested this change extensively in cloud images and desktop installations (particularly I recreated https://bugs.debian.org/777113 and confirmed that this approach also fixes it) and could not find any regression. TEST CASE (for both packages): Run lxc launch ubuntu-daily:x --config=user.user-data="$(printf "#cloud-config\npackages: [postgresql, samba, postfix]")" x1 This will install all three packages, but "systemctl status postgresql@9.5-main" will not be running. Now prepare a new image with the proposed cloud-init and init-system- helpers: lxc launch ubuntu-daily:x xprep lxc exec xprep bash # enable -proposed and dist-upgrade, then poweroff lxc publish xprep x-proposed Now run the initial lxc launch again, but against that new x-proposed image instead of the standard daily: lxc launch x-proposed --config=user.user-data="$(printf "#cloud- config\npackages: [postgresql, samba, postfix]")" x1 You should now have "systemctl status postgresql@9.5-main" running. Directly after rebooting the instance, check that there are no hanging jobs (systemctl list-jobs), particularly networking.service, to ensure that https://bugs.debian.org/777113 did not come back. Also test interactively installing a package that ships a service, like "apache2", and verify that it starts properly after installation. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1576692/+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 1623530] Re: Apport should be disabled by default
I agree that Apport popups are annoying and very user-unfriendly, but IMHO disabling it altogether is not the right approach, it might be better to show popups only when real user interaction is needed and available (for instance, in our case we have a lot of Apport popups on guest/public accounts that do not have enough privileges to actually send any data). That being said, as far as the wiki states Apport is disabled by default in "stable" releases (I have a freshly installed Xenial LTS and still get around a dozen Apport popups everytime I start my computer, so maybe things changed since 2012...) [https://wiki.ubuntu.com/Apport#How_to_enable_apport]. -- 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/1623530 Title: Apport should be disabled by default Status in apport package in Ubuntu: Confirmed Bug description: I work with large communities (US, India, Latin America) and almost the number one issue they have with Ubuntu or simply scares them off is the fact that errors keep popping up every time. Some times multiples times per minutes, per hour, per day. The reason is how apport works by default. The "solution" is going to /etc/default/apport and setting the option to 0 (Disable). I do understand the full benefit or submitting automatically all bug reports, but this has gotten (And most Ubuntu users will be able to confirm) out of hand with some many popup questions about some bug or another that are simply fixed the moment the report is going to be send (eg: Compiz issue that was fixed a couple of milliseconds later, unity issue, dash issue, firefox issue, etc..). All of them have mechanism to handle failures and basically heal themselves. The question regarding this is: Leaving apport enable by default on an Ubuntu installation simply scares or annoys end users (a lot may I add). Leaving it disabled, it will not send a bug report, but there is no issue in simply creating an ubuntu-bug report through the terminal. So the sending of the report is still valid, but is not forced onto the user (And not forced so many times). This report is back by about 3 years going back and forth with the same apport issue and seeing probably around 500 users I have helped myself with the same issue, since this makes Ubuntu less productive to the actual user, even from start. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apport 2.20.1-0ubuntu2.1 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportLog: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Sep 14 08:16:03 2016 InstallationDate: Installed on 2016-04-22 (144 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2016-08-12T16:38:06.249273 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1623530/+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 1623638] Re: package libssl1.0.0:i386 1.0.2g-1ubuntu4.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 29
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1623638 Title: package libssl1.0.0:i386 1.0.2g-1ubuntu4.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 29 Status in openssl package in Ubuntu: New Bug description: My 14.04 has never worked properly, The manager has a child lockout and will not function. The cd and usb drive do not work. Terminal will not carry out commands. Downloads and upgrades have problems possibly due to my Xplornet high speed server. My computer is an Aspire 5542-1615, 3 GB memory, 320 GB HDD , DVD super multi Dl drive. My computer is clean with a lot of empty disk space. I can only use the computer for the internet and to print. All the repairs don't seem to work so as to allow an upgrade to Ubuntu 16.04. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libssl1.0.0:i386 1.0.2g-1ubuntu4.2 ProcVersionSignature: Ubuntu 3.13.0-79.123-generic 3.13.11-ckt33 Uname: Linux 3.13.0-79-generic i686 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: i386 Date: Wed Sep 14 11:07:57 2016 DuplicateSignature: package:libssl1.0.0:i386:1.0.2g-1ubuntu4.2:subprocess installed post-installation script returned error exit status 29 ErrorMessage: subprocess installed post-installation script returned error exit status 29 InstallationDate: Installed on 2015-12-19 (270 days ago) InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140723) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: openssl Title: package libssl1.0.0:i386 1.0.2g-1ubuntu4.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 29 UpgradeStatus: Upgraded to trusty on 2016-09-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1623638/+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 1582629] Re: mutt does not properly restore console colors on exit
The Debian bug filed for Mutt traces this change to a bug in ncurses: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816887 ** Also affects: ncurses (Ubuntu) Importance: Undecided Status: New ** Bug watch added: Debian Bug tracker #816887 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816887 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ncurses in Ubuntu. https://bugs.launchpad.net/bugs/1582629 Title: mutt does not properly restore console colors on exit Status in mutt package in Ubuntu: Confirmed Status in ncurses package in Ubuntu: New Status in mutt package in Debian: Unknown Bug description: With release of Ubuntu 16.04 Debian Bug 803405 also hits Ubuntu. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=803405 After quitting mutt (with q or x) mutt doesn't restore colors of the console properly, colors are mangled, at least when colors used in mutt are different from console colors. Tested in xfce4-terminal and gnome-terminal, maybe also other terminal or text console is affected. In addition to the information in the debian report this problem only occurs when a .muttrc (even when empty) exists for the user. Without a .muttrc file the behaviour of mutt on leaving is ok. I could confirm this on amd64 and armv7l, so it seems platform independent. Even if the bug is already known in Debian I repost this in Ubuntu just to have documented it also hits Ubuntu and to maybe have some fix for current mutt version (or to get an update to next version in this LTS release). xxx@xxx:~$ lsb_release -rd Description: Ubuntu 16.04 LTS Release: 16.04 xxx@xxx:~$ apt-cache policy mutt mutt: Installiert: 1.5.24-1build1 Installationskandidat: 1.5.24-1build1 Versionstabelle: *** 1.5.24-1build1 500 500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status xxx@xxx:~$ mutt -v Mutt 1.5.24 (2015-08-30) Copyright (C) 1996-2009 Michael R. Elkins und andere. Mutt übernimmt KEINERLEI GEWÄHRLEISTUNG. Starten Sie »mutt -vv«, um weitere Details darüber zu erfahren. Mutt ist freie Software. Sie können es unter bestimmten Bedingungen weitergeben; starten Sie »mutt -vv« für weitere Details. System: Linux 4.4.0-22-generic (x86_64) ncurses: ncurses 6.0.20160213 (compiled with 6.0) libidn: 1.32 (compiled with 1.32) hcache backend: tokyocabinet 1.4.48 Compiler: Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/5/lto-wrapper Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu 5.3.1-9ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-5/README.Bugs --enable-languages=c,ada,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-5 --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-libmpx --enable-plugin --with-system-zlib --disable-browser-plugin --enable-java-awt=gtk --enable-gtk-cairo --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-5-amd64/jre --enable-java-home --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-5-amd64 --with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-5-amd64 --with-arch-directory=amd64 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --enable-objc-gc --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix gcc version 5.3.1 20160216 (Ubuntu 5.3.1-9ubuntu1) Configure options: '--prefix=/usr' '--sysconfdir=/etc' '-- mandir=/usr/share/man' '--with-docdir=/usr/share/doc' '--with- mailpath=/var/mail' '--disable-dependency-tracking' '--enable- compressed' '--enable-debug' '--enable-fcntl' '--enable-hcache' '--enable-gpgme' '--enable-imap' '--enable-smtp' '--enable-pop' '--with-curses' '--with-gnutls' '--with-gss' '--with-idn' '--with- mixmaster' '--with-sasl' '--without-gdbm' '--without-bdb' '--without- qdbm' '--build' 'x86_64-linux-gnu' 'build_alias=x86_64-linux-gnu' 'CFLAGS=-g -O2 -fstack-protector-strong -Wformat -Werror=format- security -Wall' 'LDFLAGS=-Wl,-Bsymbolic-functions -Wl,-z,relro' 'CPPFLAGS=-Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/qdbm' Compilation CFLAGS: -g -O2 -fstack-protector-strong -Wformat -Werror =format-security -Wall Einstellungen bei der Compilierung: -DOMAIN +DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE +USE_FCNTL -USE_FLOCK +USE_POP +USE_IMAP +USE_SMTP -USE_SSL_OPENSSL +USE_SSL_GNUTLS
[Touch-packages] [Bug 1623638] [NEW] package libssl1.0.0:i386 1.0.2g-1ubuntu4.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 29
Public bug reported: My 14.04 has never worked properly, The manager has a child lockout and will not function. The cd and usb drive do not work. Terminal will not carry out commands. Downloads and upgrades have problems possibly due to my Xplornet high speed server. My computer is an Aspire 5542-1615, 3 GB memory, 320 GB HDD , DVD super multi Dl drive. My computer is clean with a lot of empty disk space. I can only use the computer for the internet and to print. All the repairs don't seem to work so as to allow an upgrade to Ubuntu 16.04. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libssl1.0.0:i386 1.0.2g-1ubuntu4.2 ProcVersionSignature: Ubuntu 3.13.0-79.123-generic 3.13.11-ckt33 Uname: Linux 3.13.0-79-generic i686 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: i386 Date: Wed Sep 14 11:07:57 2016 DuplicateSignature: package:libssl1.0.0:i386:1.0.2g-1ubuntu4.2:subprocess installed post-installation script returned error exit status 29 ErrorMessage: subprocess installed post-installation script returned error exit status 29 InstallationDate: Installed on 2015-12-19 (270 days ago) InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140723) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: openssl Title: package libssl1.0.0:i386 1.0.2g-1ubuntu4.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 29 UpgradeStatus: Upgraded to trusty on 2016-09-14 (0 days ago) ** Affects: openssl (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1623638 Title: package libssl1.0.0:i386 1.0.2g-1ubuntu4.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 29 Status in openssl package in Ubuntu: New Bug description: My 14.04 has never worked properly, The manager has a child lockout and will not function. The cd and usb drive do not work. Terminal will not carry out commands. Downloads and upgrades have problems possibly due to my Xplornet high speed server. My computer is an Aspire 5542-1615, 3 GB memory, 320 GB HDD , DVD super multi Dl drive. My computer is clean with a lot of empty disk space. I can only use the computer for the internet and to print. All the repairs don't seem to work so as to allow an upgrade to Ubuntu 16.04. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libssl1.0.0:i386 1.0.2g-1ubuntu4.2 ProcVersionSignature: Ubuntu 3.13.0-79.123-generic 3.13.11-ckt33 Uname: Linux 3.13.0-79-generic i686 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: i386 Date: Wed Sep 14 11:07:57 2016 DuplicateSignature: package:libssl1.0.0:i386:1.0.2g-1ubuntu4.2:subprocess installed post-installation script returned error exit status 29 ErrorMessage: subprocess installed post-installation script returned error exit status 29 InstallationDate: Installed on 2015-12-19 (270 days ago) InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140723) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: openssl Title: package libssl1.0.0:i386 1.0.2g-1ubuntu4.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 29 UpgradeStatus: Upgraded to trusty on 2016-09-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1623638/+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 1619254] Re: Make sure debian/{control, rules} files are appropriate for arm64
** No longer affects: ubuntu-app-launch (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-system-settings-
online-accounts in Ubuntu.
https://bugs.launchpad.net/bugs/1619254
Title:
Make sure debian/{control,rules} files are appropriate for arm64
Status in Canonical System Image:
Confirmed
Status in telephony-service package in Ubuntu:
In Progress
Status in ubuntu-push package in Ubuntu:
New
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
Confirmed
Bug description:
We found several packages compiled with inappropriate parameters,
build deps on arm64. So here is the list of the packages with armhf
and/or arm64 strings in their debian/rules, debian/control:
./address-book-app-0.2+16.04.20160823/debian
./android-tools-5.1.1r36+git20160322/debian
./boost1.58-1.58.0+dfsg/debian
./dbus-1.10.6/debian
./elfutils-0.165/debian
./fftw3-3.3.4/debian
./gcc-5-5.4.0/debian
./gccgo-6-6.0.1/debian
./gdb-7.11.1/debian
./glibc-2.23/debian
./gnutls28-3.4.10/debian
./gst-plugins-bad1.0-1.8.2/debian
./hud-14.10+16.04.20160415/debian
./indicator-network-0.8.0+16.04.20160817.2/debian
./indicator-transfer-0.2+16.04.20160808.1/debian
./initramfs-tools-ubuntu-touch-0.94xenial1~overlay1/debian
./klibc-2.0.4/debian
./libdbusmenu-12.10.3+16.04.20160223.1/debian
./libdrm-2.4.67/debian
./libertine-1.3.1+16.04.20160812.3/debian
./libhybris-0.1.0+git20151016+6d424c9/debian
./libusermetrics-1.1.1+16.04.20160808.3/debian
./libvpx-1.5.0/debian
./libwebp-0.4.4/debian
./llvm-toolchain-3.8-3.8/debian
./location-service-3.0.0+16.04.20160811/debian
./mesa-11.2.0/debian
./mir-0.24.0+16.04.20160815.3/debian
./mpdecimal-2.4.2/debian
./nspr-4.12/debian
./pay-service-15.10+16.04.20160816.1/debian
./pulseaudio-8.0/debian
./python3.5-3.5.2/debian
./qt4-x11-4.8.7+dfsg/debian
./qtbase-opensource-src-5.6.1+dfsg/debian
./qtfeedback-opensource-src-5.0~git20130529/debian
./qtmir-0.4.8+16.04.20160826.1/debian
./qtubuntu-0.63+16.04.20160826/debian
./qtubuntu-camera-0.3.3+16.04.20160517/debian
./qtvideo-node-0.2.1+16.04.20151104/debian
./speex-1.2~rc1.2/debian
./systemd-229/debian
./telepathy-ofono-0.2+16.04.20160719/debian
./telephony-service-0.1+16.04.20160601.1/debian
./trust-store-2.0.0+16.04.20160119/debian
./ubuntu-app-launch-0.9+16.04.20160825/debian
./ubuntu-meta-1.361/debian
./ubuntu-push-0.68+16.04.20160825.4/debian
./ubuntu-system-settings-0.4+16.04.20160826/debian
./ubuntu-system-settings-online-accounts-0.7+16.04.20160718/debian
./ubuntu-touch-meta-1.264xenial12/debian
./ubuntu-ui-toolkit-1.3.2073+16.04.20160824build1~~xenialoverlay1~1/debian
./unity-7.4.0+16.04.20160801.2/debian
./unity8-8.14+16.04.20160826/debian
./unity-api-7.117+16.04.20160819/debian
./unity-scope-click-0.1.1+16.04.20160808/debian
./wavpack-4.75.2/debian
./xorg-7.7+13ubuntu3/debian
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1619254/+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 1612587] Re: Can't run two LibreOffice apps at the same time
*** This bug is a duplicate of bug 1589637 *** https://bugs.launchpad.net/bugs/1589637 ** Changed in: ubuntu-app-launch (Ubuntu) Status: New => Confirmed ** Changed in: ubuntu-app-launch (Ubuntu) Importance: Undecided => High ** This bug has been marked a duplicate of bug 1589637 Need to support multiple instances of applications -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1612587 Title: Can't run two LibreOffice apps at the same time Status in Canonical System Image: New Status in qtmir package in Ubuntu: New Status in ubuntu-app-launch package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: New Bug description: Pro 5 and Aquaris M10 on rc-proposed. Steps to reproduce: 1. Open e.g. LibreOffice Calc 2. Open e.g. LO Writer 3. It appears as the latter crashes and device goes back Desktop Scope window 4. Switch to LO Calc 5. LO Writer is displayed (although Unity 8 panel shows LO Calc) 6. Try to open LO Calc from the Desktop Scope 7. Device switches back to what it thinks is LO Calc, which now shows LO Writer 8. Goto Window menu in LO - displays both Calc and Writer, of which Calc shows as active 9. Try to switch to Writer in the menu and Calc still shows as active in the meny while Writer is the actual window displayed It is clear that Ubuntu Touch gets confused about which LO app that is open/active and that it is not possible to run more than one of the apps at once. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1612587/+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 1591192] Re: Unity8 crashes when launching apps without an icon entry in their .desktop file
*** This bug is a duplicate of bug 1617348 *** https://bugs.launchpad.net/bugs/1617348 ** This bug has been marked a duplicate of bug 1617348 unity shell is crashing for apps without icon -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1591192 Title: Unity8 crashes when launching apps without an icon entry in their .desktop file Status in Canonical System Image: New Status in ubuntu-app-launch package in Ubuntu: Incomplete Status in unity8 package in Ubuntu: New Bug description: Steps to reproduce: 1. Install the attached click package 2. Start the application Expected results: Application should start Actual results: Unity8 crashes To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1591192/+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 1620173] Re: Qt5 5.6 regression: conversion from QVariant to QString is broken
Unfortunately fixing this would be causing true regressions in at least ktexteditor and pyqt5: https://requests.ci- train.ubuntu.com/static/britney/landing-1920/yakkety/excuses.html https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety-ci-train-ppa-service-landing-1920/yakkety/amd64/k/ktexteditor/20160914_111856@/log.gz https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-yakkety-ci-train-ppa-service-landing-1920/yakkety/amd64/p/pyqt5/20160914_140056@/log.gz I'm not sure if rebuilding qtxmlpatterns would be enough or what other kind of problems there could be lurking. Since 16.10 release is coming closer, I think the set of these three patches (that remove a symbol among else) is too risky. The fix would eventually be in Qt 5.7 in Ubuntu 17.04, unless of course a less invasive fix could be had for 16.10. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1620173 Title: Qt5 5.6 regression: conversion from QVariant to QString is broken Status in qtbase-opensource-src package in Ubuntu: Confirmed Bug description: A regression was introduced in Qt5 5.5 - fixed in 5.7 - whereas conversion from QVariant to QString is broken for double and float values (you can see more details on this here: https://bugreports.qt.io/browse/QTBUG-47192). The patch fixing this issue is the following: http://code.qt.io/cgit/qt/qtbase.git/patch/src/corelib/tools/qlocale.h?id=726fed0d67013cbfac7921d3d4613ca83406fb0f Would it be possible to apply this patch against the package (based on Qt5 5.6.1) Ubuntu 16.10 will ship in October? It's a pretty ugly bug, which needs addressing. Hopefully the Qt devs can eventually merge this patch onto their 5.6 LTS branch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1620173/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1613949] Re: vim-gtk3 Has Unmet Dependencies After `apt-get upgrade` In Ubuntu 16.04.1 Xenial
On Wed, Sep 14, 2016 at 07:03:22PM -, Will Braswell wrote: > PS - I found the deb URL by the following steps: > > 1. Visit http://packages.ubuntu.com/ > 2. Search for "vim-gtk3" in xenial, which leads to > http://packages.ubuntu.com/search?keywords=vim-gtk3&searchon=names&suite=xenial§ion=all > 3. Select the package which leads to > http://packages.ubuntu.com/xenial/vim-gtk3 > 4. Select the amd64 arch which leads to > http://packages.ubuntu.com/xenial/amd64/vim-gtk3/download > 5. Select the first North America mirror which leads to > http://mirrors.kernel.org/ubuntu/pool/universe/v/vim/vim-gtk3_7.4.1689-3ubuntu1_amd64.deb My point is that isn't the latest version of vim-gtk3. You want http://mirrors.kernel.org/ubuntu/pool/universe/v/vim/vim-gtk3_7.4.1689-3ubuntu1.1_amd64.deb What does apt-cache policy vim-gtk3 say? In your original description you said you installed the package via apt-get, was / is your mirror out of date? -- Brian Murray -- 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/1613949 Title: vim-gtk3 Has Unmet Dependencies After `apt-get upgrade` In Ubuntu 16.04.1 Xenial Status in vim package in Ubuntu: Incomplete Bug description: I have a fresh install of Ubuntu v16.04.1, then I did an `apt-get upgrade` and it only had a few seemingly-minor packages to upgrade (don't remember the list, sorry). Apparently all the core vim packages have been upgraded to 2:7.4.1689-3ubuntu1.1 but vim-gtk3 (and all the other gvim-providing packages I tested) are still held back to 2:7.4.1689-3ubuntu1 so there is a version mis-match. Now I get the following error: [[[ BEGIN PASTE ]]] root@machine:/# apt-get install vim-gtk3 Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: vim-gtk3 : Depends: vim-common (= 2:7.4.1689-3ubuntu1) but 2:7.4.1689-3ubuntu1.1 is to be installed Depends: vim-runtime (= 2:7.4.1689-3ubuntu1) but 2:7.4.1689-3ubuntu1.1 is to be installed E: Unable to correct problems, you have held broken packages. [[[ END PASTE ]]] However I can still get gvim working if I force the installation of the vim-gtk3 package using dpkg. Of course this is not a good solution, because it leaves my system in a state of seemingly-broken packages! [[[ BEGIN PASTE ]]] root@machine:/# dpkg -i --force-depends ./vim-gtk3_7.4.1689-3ubuntu1_amd64.deb Selecting previously unselected package vim-gtk3. (Reading database ... 251539 files and directories currently installed.) Preparing to unpack .../vim-gtk3_7.4.1689-3ubuntu1_amd64.deb ... Unpacking vim-gtk3 (2:7.4.1689-3ubuntu1) ... dpkg: vim-gtk3: dependency problems, but configuring anyway as you requested: vim-gtk3 depends on vim-common (= 2:7.4.1689-3ubuntu1); however: Version of vim-common on system is 2:7.4.1689-3ubuntu1.1. vim-gtk3 depends on vim-runtime (= 2:7.4.1689-3ubuntu1); however: Version of vim-runtime on system is 2:7.4.1689-3ubuntu1.1. Setting up vim-gtk3 (2:7.4.1689-3ubuntu1) ... update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/vim (vim) in auto mode update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/vimdiff (vimdiff) in auto mode update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/rvim (rvim) in auto mode update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/rview (rview) in auto mode update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/vi (vi) in auto mode update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/view (view) in auto mode update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/ex (ex) in auto mode update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/editor (editor) in auto mode update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/gvim (gvim) in auto mode update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/gview (gview) in auto mode update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/rgview (rgview) in auto mode update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/rgvim (rgvim) in auto mode update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/evim (evim) in auto mode update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/eview (eview) in auto mode update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/gvimdiff (gvimdiff) in auto mode [[[ END PASTE ]]] And yes, I can confirm that gvim actu
[Touch-packages] [Bug 1613949] Re: vim-gtk3 Has Unmet Dependencies After `apt-get upgrade` In Ubuntu 16.04.1 Xenial
PS - I found the deb URL by the following steps: 1. Visit http://packages.ubuntu.com/ 2. Search for "vim-gtk3" in xenial, which leads to http://packages.ubuntu.com/search?keywords=vim-gtk3&searchon=names&suite=xenial§ion=all 3. Select the package which leads to http://packages.ubuntu.com/xenial/vim-gtk3 4. Select the amd64 arch which leads to http://packages.ubuntu.com/xenial/amd64/vim-gtk3/download 5. Select the first North America mirror which leads to http://mirrors.kernel.org/ubuntu/pool/universe/v/vim/vim-gtk3_7.4.1689-3ubuntu1_amd64.deb -- 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/1613949 Title: vim-gtk3 Has Unmet Dependencies After `apt-get upgrade` In Ubuntu 16.04.1 Xenial Status in vim package in Ubuntu: Incomplete Bug description: I have a fresh install of Ubuntu v16.04.1, then I did an `apt-get upgrade` and it only had a few seemingly-minor packages to upgrade (don't remember the list, sorry). Apparently all the core vim packages have been upgraded to 2:7.4.1689-3ubuntu1.1 but vim-gtk3 (and all the other gvim-providing packages I tested) are still held back to 2:7.4.1689-3ubuntu1 so there is a version mis-match. Now I get the following error: [[[ BEGIN PASTE ]]] root@machine:/# apt-get install vim-gtk3 Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: vim-gtk3 : Depends: vim-common (= 2:7.4.1689-3ubuntu1) but 2:7.4.1689-3ubuntu1.1 is to be installed Depends: vim-runtime (= 2:7.4.1689-3ubuntu1) but 2:7.4.1689-3ubuntu1.1 is to be installed E: Unable to correct problems, you have held broken packages. [[[ END PASTE ]]] However I can still get gvim working if I force the installation of the vim-gtk3 package using dpkg. Of course this is not a good solution, because it leaves my system in a state of seemingly-broken packages! [[[ BEGIN PASTE ]]] root@machine:/# dpkg -i --force-depends ./vim-gtk3_7.4.1689-3ubuntu1_amd64.deb Selecting previously unselected package vim-gtk3. (Reading database ... 251539 files and directories currently installed.) Preparing to unpack .../vim-gtk3_7.4.1689-3ubuntu1_amd64.deb ... Unpacking vim-gtk3 (2:7.4.1689-3ubuntu1) ... dpkg: vim-gtk3: dependency problems, but configuring anyway as you requested: vim-gtk3 depends on vim-common (= 2:7.4.1689-3ubuntu1); however: Version of vim-common on system is 2:7.4.1689-3ubuntu1.1. vim-gtk3 depends on vim-runtime (= 2:7.4.1689-3ubuntu1); however: Version of vim-runtime on system is 2:7.4.1689-3ubuntu1.1. Setting up vim-gtk3 (2:7.4.1689-3ubuntu1) ... update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/vim (vim) in auto mode update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/vimdiff (vimdiff) in auto mode update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/rvim (rvim) in auto mode update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/rview (rview) in auto mode update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/vi (vi) in auto mode update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/view (view) in auto mode update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/ex (ex) in auto mode update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/editor (editor) in auto mode update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/gvim (gvim) in auto mode update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/gview (gview) in auto mode update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/rgview (rgview) in auto mode update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/rgvim (rgvim) in auto mode update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/evim (evim) in auto mode update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/eview (eview) in auto mode update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/gvimdiff (gvimdiff) in auto mode [[[ END PASTE ]]] And yes, I can confirm that gvim actually works using this method. We just need to upgrade the package versioning so that we don't have a problem with the apt-get packaging dependency system. Thanks for all your hard work. Ubuntu is #1!!! :-) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1613949/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-pac
[Touch-packages] [Bug 1591356] Re: keyboard autorepeat in Xmir apps & GTK-on-Mir does not work
I have enabled xenial-proposed and installed xmir. I can confirm this bug is fixed. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1591356 Title: keyboard autorepeat in Xmir apps & GTK-on-Mir does not work Status in Canonical System Image: Confirmed Status in GTK+: Fix Released Status in gtk+3.0 package in Ubuntu: Triaged Status in libertine package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Fix Released Status in gtk+3.0 source package in Xenial: New Status in libertine source package in Xenial: New Status in xorg-server source package in Xenial: Fix Committed Status in xorg-server package in Ubuntu RTM: New Bug description: [Impact] Auto key repeating does not work in Libertine X apps which is very frustrating to users. [Test Case] 1. Install xterm in libertine 2. Start xterm from the "Xapps" scope 3. Wait for xterm to appear 4. Press and hold a key See how it only appears once and not multiple times as it should. [Regression Potential] Non observed. Original Description: How to reproduce: * Install xterm in libertine * Start xterm from the "Xapps" scope * Wait for xterm to appear * Press and hold a key * See how it only appears once and not multiple times as it should To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1591356/+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 1613949] Re: vim-gtk3 Has Unmet Dependencies After `apt-get upgrade` In Ubuntu 16.04.1 Xenial
Hi Brian, The following 4 commands work on my system to actually run gvim, although as I said before this leaves the packages in a broken state, so I still go ahead and run the purge command at the end to remove the broken (but working) package for now, until a proper solution is in place. $ apt-get install liblua5.2 libruby2.3 $ wget http://mirrors.kernel.org/ubuntu/pool/universe/v/vim/vim-gtk3_7.4.1689-3ubuntu1_amd64.deb $ dpkg -i --force-depends ./vim-gtk3_7.4.1689-3ubuntu1_amd64.deb $ gvim $ dpkg --purge vim-gtk3 Does this answer your question? Thanks, ~ Will -- 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/1613949 Title: vim-gtk3 Has Unmet Dependencies After `apt-get upgrade` In Ubuntu 16.04.1 Xenial Status in vim package in Ubuntu: Incomplete Bug description: I have a fresh install of Ubuntu v16.04.1, then I did an `apt-get upgrade` and it only had a few seemingly-minor packages to upgrade (don't remember the list, sorry). Apparently all the core vim packages have been upgraded to 2:7.4.1689-3ubuntu1.1 but vim-gtk3 (and all the other gvim-providing packages I tested) are still held back to 2:7.4.1689-3ubuntu1 so there is a version mis-match. Now I get the following error: [[[ BEGIN PASTE ]]] root@machine:/# apt-get install vim-gtk3 Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: vim-gtk3 : Depends: vim-common (= 2:7.4.1689-3ubuntu1) but 2:7.4.1689-3ubuntu1.1 is to be installed Depends: vim-runtime (= 2:7.4.1689-3ubuntu1) but 2:7.4.1689-3ubuntu1.1 is to be installed E: Unable to correct problems, you have held broken packages. [[[ END PASTE ]]] However I can still get gvim working if I force the installation of the vim-gtk3 package using dpkg. Of course this is not a good solution, because it leaves my system in a state of seemingly-broken packages! [[[ BEGIN PASTE ]]] root@machine:/# dpkg -i --force-depends ./vim-gtk3_7.4.1689-3ubuntu1_amd64.deb Selecting previously unselected package vim-gtk3. (Reading database ... 251539 files and directories currently installed.) Preparing to unpack .../vim-gtk3_7.4.1689-3ubuntu1_amd64.deb ... Unpacking vim-gtk3 (2:7.4.1689-3ubuntu1) ... dpkg: vim-gtk3: dependency problems, but configuring anyway as you requested: vim-gtk3 depends on vim-common (= 2:7.4.1689-3ubuntu1); however: Version of vim-common on system is 2:7.4.1689-3ubuntu1.1. vim-gtk3 depends on vim-runtime (= 2:7.4.1689-3ubuntu1); however: Version of vim-runtime on system is 2:7.4.1689-3ubuntu1.1. Setting up vim-gtk3 (2:7.4.1689-3ubuntu1) ... update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/vim (vim) in auto mode update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/vimdiff (vimdiff) in auto mode update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/rvim (rvim) in auto mode update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/rview (rview) in auto mode update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/vi (vi) in auto mode update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/view (view) in auto mode update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/ex (ex) in auto mode update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/editor (editor) in auto mode update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/gvim (gvim) in auto mode update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/gview (gview) in auto mode update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/rgview (rgview) in auto mode update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/rgvim (rgvim) in auto mode update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/evim (evim) in auto mode update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/eview (eview) in auto mode update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/gvimdiff (gvimdiff) in auto mode [[[ END PASTE ]]] And yes, I can confirm that gvim actually works using this method. We just need to upgrade the package versioning so that we don't have a problem with the apt-get packaging dependency system. Thanks for all your hard work. Ubuntu is #1!!! :-) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1613949/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post
[Touch-packages] [Bug 1621824] Re: MFG:Garrison - Ubuntu 16.04.1 dmesg error "systemd[1]: Failed to start Set console keymap."
** Package changed: ubuntu => console-setup (Ubuntu) ** Changed in: console-setup (Ubuntu) Assignee: (unassigned) => Taco Screen team (taco-screen-team) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1621824 Title: MFG:Garrison - Ubuntu 16.04.1 dmesg error "systemd[1]: Failed to start Set console keymap." Status in console-setup package in Ubuntu: New Bug description: == Comment: #1 - Application Cdeadmin <> - 2016-08-23 15:05:14 == State: Open by: knodelk on 23 August 2016 14:00:43 Seeing the following error message in the Ubuntu dmesg log following IPL to Ubuntu on system with Ubuntu 16.04.1 installed: # dmesg -T --level=alert,crit,err [Tue Aug 23 09:20:12 2016] systemd[1]: Failed to start Set console keymap. This appears to be something that can be ignored so manufacturing will be ignoring this message until directed otherwise. ==> all systemd related messages: # dmesg -T | grep systemd [Tue Aug 23 09:20:12 2016] systemd[1]: systemd 229 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN) [Tue Aug 23 09:20:12 2016] systemd[1]: Detected architecture ppc64-le. [Tue Aug 23 09:20:12 2016] systemd[1]: Set hostname to . [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on Device-mapper event daemon FIFOs. [Tue Aug 23 09:20:12 2016] systemd[1]: Started Forward Password Requests to Wall Directory Watch. [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe. [Tue Aug 23 09:20:12 2016] systemd[1]: Reached target Encrypted Volumes. [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on Syslog Socket. [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on Journal Socket. [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on Journal Socket (/dev/log). [Tue Aug 23 09:20:12 2016] systemd[1]: Reached target User and Group Name Lookups. [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on fsck to fsckd communication Socket. [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on udev Control Socket. [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on LVM2 metadata daemon socket. [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on LVM2 poll daemon socket. [Tue Aug 23 09:20:12 2016] systemd[1]: Created slice User and Session Slice. [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on udev Kernel Socket. [Tue Aug 23 09:20:12 2016] systemd[1]: Created slice System Slice. [Tue Aug 23 09:20:12 2016] systemd[1]: Mounting POSIX Message Queue File System... [Tue Aug 23 09:20:12 2016] systemd[1]: Reached target Slices. [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Create list of required static device nodes for the current kernel... [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Nameserver information manager... [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling... [Tue Aug 23 09:20:12 2016] systemd[1]: Mounting RPC Pipe File System... [Tue Aug 23 09:20:12 2016] systemd[1]: Created slice system-serial\x2dgetty.slice. [Tue Aug 23 09:20:12 2016] systemd[1]: Started Read required files in advance. [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Load Kernel Modules... [Tue Aug 23 09:20:12 2016] systemd[1]: Mounting Debug File System... [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on Journal Audit Socket. [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Journal Service... [Tue Aug 23 09:20:12 2016] systemd[1]: Mounting Huge Pages File System... [Tue Aug 23 09:20:12 2016] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point. [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Uncomplicated firewall... [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Set console keymap... [Tue Aug 23 09:20:12 2016] systemd[1]: Mounted Debug File System. [Tue Aug 23 09:20:12 2016] systemd[1]: Mounted POSIX Message Queue File System. [Tue Aug 23 09:20:12 2016] systemd[1]: Mounted Huge Pages File System. [Tue Aug 23 09:20:12 2016] systemd[1]: Started Create list of required static device nodes for the current kernel. [Tue Aug 23 09:20:12 2016] systemd[1]: Started Nameserver information manager. [Tue Aug 23 09:20:12 2016] systemd[1]: Started Uncomplicated firewall. [Tue Aug 23 09:20:12 2016] systemd[1]: keyboard-setup.service: Main process exited, code=exited, status=1/FAILURE [Tue Aug 23 09:20:12 2016] systemd[1]: Failed to start Set console keymap. [Tue Aug 23 09:20:12 2016] systemd[1]: keyboard-setup.service: Unit entered failed state. [Tue Aug 23 09:20:12 2016] systemd[1]: keyboard-setup.service: Failed with result 'exit-code'. [Tue Aug 23 09:20:12 2016] systemd[1]: Mounted RPC Pipe File System. [Tue Aug 23 09:20:12 2016]
[Touch-packages] [Bug 1621824] [NEW] MFG:Garrison - Ubuntu 16.04.1 dmesg error "systemd[1]: Failed to start Set console keymap."
You have been subscribed to a public bug: == Comment: #1 - Application Cdeadmin <> - 2016-08-23 15:05:14 == State: Open by: knodelk on 23 August 2016 14:00:43 Seeing the following error message in the Ubuntu dmesg log following IPL to Ubuntu on system with Ubuntu 16.04.1 installed: # dmesg -T --level=alert,crit,err [Tue Aug 23 09:20:12 2016] systemd[1]: Failed to start Set console keymap. This appears to be something that can be ignored so manufacturing will be ignoring this message until directed otherwise. ==> all systemd related messages: # dmesg -T | grep systemd [Tue Aug 23 09:20:12 2016] systemd[1]: systemd 229 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN) [Tue Aug 23 09:20:12 2016] systemd[1]: Detected architecture ppc64-le. [Tue Aug 23 09:20:12 2016] systemd[1]: Set hostname to . [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on Device-mapper event daemon FIFOs. [Tue Aug 23 09:20:12 2016] systemd[1]: Started Forward Password Requests to Wall Directory Watch. [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on /dev/initctl Compatibility Named Pipe. [Tue Aug 23 09:20:12 2016] systemd[1]: Reached target Encrypted Volumes. [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on Syslog Socket. [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on Journal Socket. [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on Journal Socket (/dev/log). [Tue Aug 23 09:20:12 2016] systemd[1]: Reached target User and Group Name Lookups. [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on fsck to fsckd communication Socket. [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on udev Control Socket. [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on LVM2 metadata daemon socket. [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on LVM2 poll daemon socket. [Tue Aug 23 09:20:12 2016] systemd[1]: Created slice User and Session Slice. [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on udev Kernel Socket. [Tue Aug 23 09:20:12 2016] systemd[1]: Created slice System Slice. [Tue Aug 23 09:20:12 2016] systemd[1]: Mounting POSIX Message Queue File System... [Tue Aug 23 09:20:12 2016] systemd[1]: Reached target Slices. [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Create list of required static device nodes for the current kernel... [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Nameserver information manager... [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling... [Tue Aug 23 09:20:12 2016] systemd[1]: Mounting RPC Pipe File System... [Tue Aug 23 09:20:12 2016] systemd[1]: Created slice system-serial\x2dgetty.slice. [Tue Aug 23 09:20:12 2016] systemd[1]: Started Read required files in advance. [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Load Kernel Modules... [Tue Aug 23 09:20:12 2016] systemd[1]: Mounting Debug File System... [Tue Aug 23 09:20:12 2016] systemd[1]: Listening on Journal Audit Socket. [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Journal Service... [Tue Aug 23 09:20:12 2016] systemd[1]: Mounting Huge Pages File System... [Tue Aug 23 09:20:12 2016] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point. [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Uncomplicated firewall... [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Set console keymap... [Tue Aug 23 09:20:12 2016] systemd[1]: Mounted Debug File System. [Tue Aug 23 09:20:12 2016] systemd[1]: Mounted POSIX Message Queue File System. [Tue Aug 23 09:20:12 2016] systemd[1]: Mounted Huge Pages File System. [Tue Aug 23 09:20:12 2016] systemd[1]: Started Create list of required static device nodes for the current kernel. [Tue Aug 23 09:20:12 2016] systemd[1]: Started Nameserver information manager. [Tue Aug 23 09:20:12 2016] systemd[1]: Started Uncomplicated firewall. [Tue Aug 23 09:20:12 2016] systemd[1]: keyboard-setup.service: Main process exited, code=exited, status=1/FAILURE [Tue Aug 23 09:20:12 2016] systemd[1]: Failed to start Set console keymap. [Tue Aug 23 09:20:12 2016] systemd[1]: keyboard-setup.service: Unit entered failed state. [Tue Aug 23 09:20:12 2016] systemd[1]: keyboard-setup.service: Failed with result 'exit-code'. [Tue Aug 23 09:20:12 2016] systemd[1]: Mounted RPC Pipe File System. [Tue Aug 23 09:20:12 2016] systemd[1]: Started Load Kernel Modules. [Tue Aug 23 09:20:12 2016] systemd[1]: Mounting Configuration File System... [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Apply Kernel Variables... [Tue Aug 23 09:20:12 2016] systemd[1]: Mounting FUSE Control File System... [Tue Aug 23 09:20:12 2016] systemd[1]: Started LVM2 metadata daemon. [Tue Aug 23 09:20:12 2016] systemd[1]: Starting Create Static Device Nodes in /dev... [Tue Aug 23 09:20:12 2016] systemd[1]: Mounted FUSE Control File System. [Tue Aug 23 09:20:12 2016] systemd[1]: Mounted Configuration File System. [Tue Aug 23 09:20
[Touch-packages] [Bug 1609898] Re: dhclient incorrectly assumes a /64 ipv6 prefix
The change in isc-dhcp for Xenial may be causing a NetworkManager test regression. http://autopkgtest.ubuntu.com/packages/n/network-manager/xenial/amd64 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1609898 Title: dhclient incorrectly assumes a /64 ipv6 prefix Status in isc-dhcp package in Ubuntu: Fix Committed Status in isc-dhcp source package in Precise: Fix Committed Status in isc-dhcp source package in Trusty: Fix Committed Status in isc-dhcp source package in Xenial: Fix Committed Status in isc-dhcp source package in Yakkety: Fix Committed Status in isc-dhcp package in Debian: Fix Released Bug description: [Impact] clients who get an ipv6 address from a dhcpv6 server assume the address has a /64 prefix, but that is not necessarily true, and if the subnet is different than /64 those clients will not be able to reach other addresses in that /64 prefix because the other systems are not on-link. This /64 assumption of dhclient effectively breaks the client networking for certain addresses. [Test Case] Set up a server with two interface nics, and one client connected to each of those interfaces. On the server, set up a ipv6 subnet on each interface, with a larger prefix than /64, e.g.: 2001:db8:0:0:1::/96 2001:db8:0:0:2::/96 configure dhcpv6 on the server, to provide ipv6 addresses on each interface. Set the server as the default ipv6 route for the clients. Allow the clients to get dhcpv6 ipv6 addresses from the server. The clients will each get a ipv6 address with a /64 prefix, due to the bug in dhclient. Try to ping (or otherwise communicate) between the clients. Since they have /64 prefixes, they think they are on-link with each other, but they are not, so they can't communicate. After the dhclient bug is fixed, repeat the above setup, and the clients will get /128 prefixes instead, and then will be able to communicate with each other, because they will route the traffic to each other through the server. [Regression potential] None. Non-standard (i.e. not /64) subnets served by dhcpv6 currently are broken, this fixes that. [Other info] This is fixed in debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684009 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1609898/+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 1623294] Re: Black screen on startup after HWE stack update on Ubuntu 14.04 LTS [Radeon R7 graphics]
Further info—Xorg.log.Old is completely blank after a failed boot. I'm assuming that means Xorg failed to start altogether? -- 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/1623294 Title: Black screen on startup after HWE stack update on Ubuntu 14.04 LTS [Radeon R7 graphics] Status in xorg package in Ubuntu: New Bug description: After updating the HWE stack on Ubuntu 14.04 LTS, my computer now regularly boots to a black screen upon startup. I briefly see the purple screen (but no plymouth), and then nothing. You can hear the ubuntu drum roll, though, and I can reboot using the alt+Sysrq+B option. Adding the nomodeset parameter in GRUB offers a solution of sorts, but the computer boots with Gallium 0.4 on llvmpipe graphics, which makes gaming basically impossible. I can still boot regularly using the 3.16.0-77-generic kernel saved in GRUB. Other info: 1) I tried an Ubuntu live USB stick with both 14.04.5 on it and then 16.04 and got the same problem. 2) My UEFI firmware is up-to-date as of 1 or 2 days ago. 3) The kernel in question is 4.4.0-36-generic. 4) Ubuntu release: 14.04.5 LTS 5) I have never installed the fglrx driver—I have always used the open-source driver. 6) My exact GPU: AMD A10-7700K Radeon R7 (Kaveri). 7) I'm not sure that the dmesg log automatically attached by apport will be helpful because of the "nomodeset" parameter, so I have attached a dmesg log grabbed from a failed boot. With guidance, I can do the same for other relevant logs. Hope that's helpful! ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.4.0-36.55~14.04.1-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14.1-0ubuntu3.21 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: Tue Sep 13 21:46:45 2016 DistUpgraded: 2016-08-26 20:07:12,800 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Kaveri [Radeon R7 Graphics] [1002:1313] (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation Device [1849:1313] InstallationDate: Installed on 2015-06-24 (447 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic root=UUID=228ea1db-87eb-476d-b97f-5a4a28c618f4 ro nomodeset quiet splash vt.handoff=7 Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2016-08-27 (18 days ago) dmi.bios.date: 03/15/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.30 dmi.board.name: FM2A78M-HD+ R2.0 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.30:bd03/15/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A78M-HD+R2.0:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A 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: Tue Sep 13 21:07:07 2016 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.3-1ubuntu2.2~trusty3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1623294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages
[Touch-packages] [Bug 1623295] Re: Black screen on startup after HWE stack update on Ubuntu 14.04 LTS [Radeon R7 graphics]
*** This bug is a duplicate of bug 1623294 *** https://bugs.launchpad.net/bugs/1623294 Thanks Hans! -- 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/1623295 Title: Black screen on startup after HWE stack update on Ubuntu 14.04 LTS [Radeon R7 graphics] Status in xorg package in Ubuntu: New Bug description: After updating the HWE stack on Ubuntu 14.04 LTS, my computer now regularly boots to a black screen upon startup. I briefly see the purple screen (but no plymouth), and then nothing. You can hear the ubuntu drum roll, though, and I can reboot using the alt+Sysrq+B option. Adding the nomodeset parameter in GRUB offers a solution of sorts, but the computer boots with Gallium 0.4 on llvmpipe graphics, which makes gaming basically impossible. I can still boot regularly using the 3.16.0-77-generic kernel saved in GRUB. Other info: 1) I tried an Ubuntu live USB stick with both 14.04.5 on it and then 16.04 and got the same problem. 2) My UEFI firmware is up-to-date as of 1 or 2 days ago. 3) The kernel in question is 4.4.0-36-generic. 4) Ubuntu release: 14.04.5 LTS 5) I have never installed the fglrx driver—I have always used the open-source driver. 6) My exact GPU: AMD A10-7700K Radeon R7 (Kaveri). 7) I'm not sure that the dmesg log automatically attached by apport will be helpful because of the "nomodeset" parameter, so I have attached a dmesg log grabbed from a failed boot. With guidance, I can do the same for other relevant logs. Hope that's helpful! ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.4.0-36.55~14.04.1-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14.1-0ubuntu3.21 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: Tue Sep 13 21:46:45 2016 DistUpgraded: 2016-08-26 20:07:12,800 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Kaveri [Radeon R7 Graphics] [1002:1313] (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation Device [1849:1313] InstallationDate: Installed on 2015-06-24 (447 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic root=UUID=228ea1db-87eb-476d-b97f-5a4a28c618f4 ro nomodeset quiet splash vt.handoff=7 Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2016-08-27 (18 days ago) dmi.bios.date: 03/15/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.30 dmi.board.name: FM2A78M-HD+ R2.0 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.30:bd03/15/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A78M-HD+R2.0:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A 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: Tue Sep 13 21:07:07 2016 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.3-1ubuntu2.2~trusty3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1623295/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.ne
[Touch-packages] [Bug 1579911] Re: Totem unable to play VirtualBox webm files
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gstreamer1.0 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1579911 Title: Totem unable to play VirtualBox webm files Status in gstreamer1.0 package in Ubuntu: Confirmed Bug description: Totem is unable to play VirtualBox .webm Video Capture files. I have gstreamer-plugins-good, bad and ugly installed. VLC plays these files just fine. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libgstreamer1.0-0 1.8.0-1 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Mon May 9 13:46:50 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-05-09 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1579911/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1576692] Re: fully support package installation in systemd
Thank you Neil! I've been going through my testing here, and found: * bug 1623570: Azure: cannot start walinux agent (Transaction order is cyclic.) That will require us to get that fix in and through proposed or we will break Azure boot. Its fallout of the systemd ordering. ** Description changed: in cloud-init users can install packages via cloud-config: #cloud-config packages: [apache2] Due to some intricacies of systemd and service installation that doesn't work all that well. We fixed the issue for simple services that do not have any dependencies on other services, or at least don't check those dependencies well under bug 1575572. We'd like to have a way to fully support this in cloud-init. Related bugs: * bug 1575572: apache2 fails to start if installed via cloud config (on Xenial) * bug 1611973: postgresql@9.5-main service not started if postgres installed via cloud-init * bug 1621336: snapd.boot-ok.service hangs eternally on cloud image upgrades (snapd packaging bug, but this cloud-init fix will workaround it) * bug 1620780: dev-sda2.device job running and times out + * bug 1576692: fully support package installation in systemd + * bug 1623570: Azure: cannot start walinux agent (Transaction order is cyclic.) SRU INFORMATION === FIX for init-system-helpers: https://anonscm.debian.org/cgit/collab-maint/init-system-helpers.git/commit/?id=1460d6a02 REGRESSION POTENTIAL for init-system-helpers: This changes invoke-rc.d and service, two very central pieces of packaging infrastructure. Errors in it will break installation/upgrades of packages or /etc/network/if- up.d/ hooks and the like. This changes the condition when systemd units get started without their dependencies, and the condition gets weakened. This means that behaviour in a booted system is unchanged, but during boot this could change the behaviour of if-up.d/ hooks (although they have never been defined well during boot anyway). However, I tested this change extensively in cloud images and desktop installations (particularly I recreated https://bugs.debian.org/777113 and confirmed that this approach also fixes it) and could not find any regression. TEST CASE (for both packages): Run -lxc launch ubuntu-daily:x --config=user.user-data="$(printf "#cloud-config\npackages: [postgresql, samba, postfix]")" x1 + lxc launch ubuntu-daily:x --config=user.user-data="$(printf "#cloud-config\npackages: [postgresql, samba, postfix]")" x1 This will install all three packages, but "systemctl status postgresql@9.5-main" will not be running. Now prepare a new image with the proposed cloud-init and init-system- helpers: -lxc launch ubuntu-daily:x xprep -lxc exec xprep bash -# enable -proposed and dist-upgrade, then poweroff -lxc publish xprep x-proposed + lxc launch ubuntu-daily:x xprep + lxc exec xprep bash + # enable -proposed and dist-upgrade, then poweroff + lxc publish xprep x-proposed Now run the initial lxc launch again, but against that new x-proposed image instead of the standard daily: - lxc launch x-proposed --config=user.user-data="$(printf "#cloud- + lxc launch x-proposed --config=user.user-data="$(printf "#cloud- config\npackages: [postgresql, samba, postfix]")" x1 You should now have "systemctl status postgresql@9.5-main" running. Directly after rebooting the instance, check that there are no hanging jobs (systemctl list-jobs), particularly networking.service, to ensure that https://bugs.debian.org/777113 did not come back. Also test interactively installing a package that ships a service, like "apache2", and verify that it starts properly after installation. ** Description changed: in cloud-init users can install packages via cloud-config: #cloud-config packages: [apache2] Due to some intricacies of systemd and service installation that doesn't work all that well. We fixed the issue for simple services that do not have any dependencies on other services, or at least don't check those dependencies well under bug 1575572. We'd like to have a way to fully support this in cloud-init. Related bugs: * bug 1575572: apache2 fails to start if installed via cloud config (on Xenial) * bug 1611973: postgresql@9.5-main service not started if postgres installed via cloud-init * bug 1621336: snapd.boot-ok.service hangs eternally on cloud image upgrades (snapd packaging bug, but this cloud-init fix will workaround it) * bug 1620780: dev-sda2.device job running and times out - * bug 1576692: fully support package installation in systemd - * bug 1623570: Azure: cannot start walinux agent (Transaction order is cyclic.) + * bug 1623570: Azure: cannot start walinux agent (Transaction order is cyclic.) SRU INFORMATION === FIX for init-system-helpers: https://anonscm.debian.org/cgit/collab-maint/init-system
[Touch-packages] [Bug 1622406] Re: Libertine (X11 App) page disappeared (OTA12) on BQ M10
Thanks for following up. I'm not sure there's much we can do about the keyboard crashing running X Apps, but that would be separate bug if you wish to file it. For now, I'm closing this as Invalid. ** Changed in: libertine Status: New => Invalid ** Changed in: libertine (Ubuntu) Status: New => Invalid ** Changed in: unity8 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1622406 Title: Libertine (X11 App) page disappeared (OTA12) on BQ M10 Status in Libertine: Invalid Status in libertine package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Invalid Bug description: Under OTA12 of BQ M10 (Cooler), I opened Libreoffice and tried to add an additional language layout for external keyboard (Thai). I was able to add US and Thai Pattachote keyboards (for external keyboard), but did not know how to switch the keyboard layout. I tried ALT-Shift and CTR-Shift without a success. There was no Internet connection during the keyboard layout adding. It turned out that the X11 App or Libertine page disappeared. I tried to restart and even turned of the M10. However, the X11 App page did not come back. Could it be I did type in unkonw hot keys? Is there a way to bring back the missing Libertine (X11 App) page? Or can I bring up the missing programmes under terminal (e.g. Libreoffice, Firefox, Gimp)? PS I used K380 Logitech Bluetooth external keyboard. And I use this M10 around once a week. Thanks. Namsommut To manage notifications about this bug go to: https://bugs.launchpad.net/libertine/+bug/1622406/+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 1618602] Re: sudo crashed with SIGSEGV in kill()
This seems more likely an issue with the unetbootin script. It'd be good to know what it was doing and then try and recreate the crash using sudo itself. ProcCmdline: sudo ./unetbootin-linux64-625.bin ** Changed in: sudo (Ubuntu) Status: Confirmed => Incomplete -- 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/1618602 Title: sudo crashed with SIGSEGV in kill() Status in sudo package in Ubuntu: Incomplete Bug description: Crash. ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: sudo 1.8.16-0ubuntu3 Uname: Linux 4.8.0-040800rc3-lowlatency x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Aug 30 16:28:52 2016 ExecutablePath: /usr/bin/sudo InstallationDate: Installed on 2015-07-26 (401 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723) ProcCmdline: sudo ./unetbootin-linux64-625.bin Signal: 11 SourcePackage: sudo StacktraceTop: kill () at ../sysdeps/unix/syscall-template.S:84 ?? () __libc_start_main (main=0x55f06eca89f0, argc=2, argv=0x7fffb1bcfdc8, init=, fini=, rtld_fini=, stack_end=0x7fffb1bcfdb8) at ../csu/libc-start.c:291 ?? () Title: sudo crashed with SIGSEGV in kill() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1618602/+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 1600305] Re: Touch Problem on MX4
I had the problem today three times. Now with syslog. ** Attachment added: "syslog.log" https://bugs.launchpad.net/canonical-devices-system-image/+bug/1600305/+attachment/4741107/+files/syslog.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1600305 Title: Touch Problem on MX4 Status in Canonical System Image: Incomplete Status in unity8 package in Ubuntu: Confirmed Bug description: Can't swipe on the left- and rightside Devise-Information: current build number: 13 device name: arale channel: ubuntu-touch/stable/meizu.en last update: 2016-06-02 05:58:37 version version: 13 version ubuntu: 20160524.1 version tag: OTA-11 version device: 20160331-e143fc2 version custom: 20160504-975-19-6 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1600305/+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 1487208] Re: package sudo 1.8.9p5-1ubuntu5 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1
The attached log file shows you removing multiple packages which ultimately resulted in the removal of sudo which is not advised. Removing guitarpro6 (6.1.6) ... Removing lubuntu-desktop (0.59) ... Removing gdebi (0.9.5.5+nmu1) ... Removing gksu (2.0.2-9ubuntu1) ... Removing libgksu2-0 (2.0.13~pre1-6ubuntu7) ... update-alternatives: removing manually selected alternative - switching libgksu-gconf-defaults to auto mode Removing ubuntu-minimal (1.334) ... Removing sudo (1.8.9p5-1ubuntu5) ... You have asked that the sudo package be removed, but no root password has been set. Without sudo, you may not be able to gain administrative privileges. If you would prefer to access the root account with su(1) or by logging in directly, you must set a root password with "sudo passwd". If you have arranged other means to access the root account, and you are sure this is what you want, you may bypass this check by setting an environment variable (export SUDO_FORCE_REMOVE=yes). Refusing to remove sudo. dpkg: error processing package sudo (--remove): subprocess installed pre-removal script returned error exit status 1 ** Changed in: sudo (Ubuntu) Status: Confirmed => Invalid -- 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/1487208 Title: package sudo 1.8.9p5-1ubuntu5 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 Status in sudo package in Ubuntu: Invalid Bug description: I installed new updates then installed guitar pro -> reboot pc , gp6 was delleted after reboot and thats error message are in ProblemType: Package DistroRelease: Ubuntu 15.04 Package: sudo 1.8.9p5-1ubuntu5 ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4 Uname: Linux 3.19.0-26-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.2 Architecture: amd64 Date: Fri Aug 21 00:20:35 2015 DuplicateSignature: package:sudo:1.8.9p5-1ubuntu5:subprocess installed pre-removal script returned error exit status 1 ErrorMessage: subprocess installed pre-removal script returned error exit status 1 InstallationDate: Installed on 2015-05-09 (103 days ago) InstallationMedia: Lubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4.1 SourcePackage: sudo Title: package sudo 1.8.9p5-1ubuntu5 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) VisudoCheck: /etc/sudoers: parsed OK /etc/sudoers.d/README: parsed OK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1487208/+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 1611363] Re: vim.gtk3 crashes frequently with SIGSEGV in ffi_call_unix64()
This crash looks similar to https://errors.ubuntu.com/problem/e2ebc01b52bd3bdce450fc67c4b2cdccb90d8dc3. ** Changed in: vim (Ubuntu) Importance: Medium => High ** Also affects: vim (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: vim (Ubuntu Xenial) Status: New => Confirmed ** Changed in: vim (Ubuntu Xenial) Importance: Undecided => High -- 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/1611363 Title: vim.gtk3 crashes frequently with SIGSEGV in ffi_call_unix64() Status in vim: Unknown Status in vim package in Ubuntu: Confirmed Status in vim source package in Xenial: Confirmed Bug description: Hi, vim-gtk3 crashes so often on my system that it's borderline unusable. My system is a clean install of Ubuntu 16.04. I also (temporarily) renamed my customized ~/.vimrc and ~/.vim. My system is up-to-date as of today (2016-08-09); installed vim-gtk3 is 2:7.4.1689-3ubuntu1.1. The crash happens only (but very frequently, not always) when I launch gvim, either by calling it from a shell or by double-clicking a file in Nautilus. Note that the crash is independent of whether I'm opening a file or not. (At least I tried both variations from the terminal.) There's also a report on vim's bugtracker, but since unity appears in the backtrace, the consensus is that it's probably Ubuntu-specific. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: vim-gtk3 2:7.4.1689-3ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Aug 9 14:34:31 2016 ExecutablePath: /usr/bin/vim.gtk3 InstallationDate: Installed on 2016-07-10 (29 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcCmdline: gvim -f /home/username/Documents/schoul/2016/1G-TODO/01-systemes-equations-TODO/chap01_systemes-equations-NOTES.tex Signal: 11 SourcePackage: vim StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libunity-gtk3-parser.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 Title: vim.gtk3 crashed with SIGSEGV in ffi_call_unix64() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/vim/+bug/1611363/+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 1594114] Re: Camera-app crashes when processing HDR photo
Could this be a duplicate of: https://bugs.launchpad.net/ubuntu/+source /camera-app/+bug/1537774 ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1594114 Title: Camera-app crashes when processing HDR photo Status in camera-app package in Ubuntu: Confirmed Bug description: BQ E5 OTA-11, but it has been like this since i got it. (~january 2016) 7/10 when I take a photo with HDR enabled, the app crashes while processing the photo. I get the spinning wheel and then it dies and the photo is not saved. Please let me know what logs i can give you to help you fix this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1594114/+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 1537774] Re: Viewfinder frozen and all buttons disabled after taking HDR picture
I am having this or similar issue on my MX4 ever since HDR was present in the camera app. After 1 to n photos taken in HDR mode the camera freezes, doesn't save the taken HDR picture, doesn't even show it ... stays in a black screen with just a loading animation. In addition after closing the app and starting it again the camera app has no access to the camera and the device has to be rebooted in order to take additional images. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1537774 Title: Viewfinder frozen and all buttons disabled after taking HDR picture Status in Canonical System Image: Confirmed Status in camera-app package in Ubuntu: Confirmed Bug description: Reported by royden in https://bugs.launchpad.net/ubuntu/+source /camera-app/+bug/1475895/comments/6 "Testing the fix released for Bug #1519766 (and likely #1478693) I can reliably freeze the camera-app (v. 3.0.0.616) on rc-proposed Arale r227 by taking HDR images. Freeze happens around the 3rd or 4th shot of the same subject as reported in Bug #1519766. HDR shots of shaded lamp in semi-dark room (taking up 3/4 of view) trigger freeze on 4/5th shot. HDR shots of lamp on small table at distance in semi-dark room do not reliably trigger freeze. Normal shots do not trigger freeze, with or without zoom AFAIKS. Freeze comprises either the viewfinder holding the image of the attempted capture and app being no longer responsive and needing to be closed. Re-opening produces "Cannot access camera" error message screen, with access permission or some other error as cause. Reboot needed to regain camera function. Other freeze seen was a return of the viewfinder to a dark screen, and the same error message screen appearing." To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1537774/+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 1617348] Re: unity shell is crashing for apps without icon
** Branch linked: lp:~ted/ubuntu-app-launch/relax-icon-rules -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1617348 Title: unity shell is crashing for apps without icon Status in Canonical System Image: New Status in ubuntu-app-launch package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Incomplete Bug description: Trying to launch a app from terminal that does not contains a "Icon" etry on it desktop file causes the shell to crash. How to test === * Create a desktop entry without the icon entry (something like that): [Desktop Entry] Name=Sync Monitor Comment=Ask for online account authentication if the token expires Exec=/usr/lib/arm-linux-gnueabihf/sync-monitor/sync-monitor-helper %u Terminal=false Type=Application Version=1.0 X-Ubuntu-Gettext-Domain=sync-monitor * try to launch it from terminal or url launch: /usr/lib/arm-linux-gnueabihf/sync-monitor/sync-monitor-helper --desktop-file-hint=/usr/share/applications/sync-monitor-helper.desktop Expected App appears Current === Shell crashes and go back to login screen. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1617348/+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 1623531] Re: unity8 desktop boots to black screen on yakkety daily fresh install
Thanks to whomever confirmed this bug! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1623531 Title: unity8 desktop boots to black screen on yakkety daily fresh install Status in unity8 package in Ubuntu: Confirmed Bug description: All new hard installs of yakketty amd64 with unity8/libertine (non- ppa) will boot to black screen on both machines with nVidia and Intel graphics adapters. This makes it virtually impossible to test current/dailys w unity8. Regards.. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: unity8 8.14+16.10.20160831.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Wed Sep 14 10:20:56 2016 InstallationDate: Installed on 2016-09-13 (1 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160913) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) upstart.unity8-filewatcher.log: Failed to open connection to "session" message bus: Failed to connect to socket /run/user/1000/bus: Connection refused Failed to open connection to "session" message bus: Failed to connect to socket /run/user/1000/bus: Connection refused Failed to open connection to "session" message bus: Failed to connect to socket /run/user/1000/bus: Connection refused Failed to open connection to "session" message bus: Failed to connect to socket /run/user/1000/bus: Connection refused To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1623531/+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 1623295] Re: Black screen on startup after HWE stack update on Ubuntu 14.04 LTS [Radeon R7 graphics]
*** This bug is a duplicate of bug 1623294 *** https://bugs.launchpad.net/bugs/1623294 >Accidentally submitted this bug twice . . . Not sure how to delete the duplicate. Look for "Mark as duplicate" towards the top on the right side. I've marked this issue as a duplicate of the other. ** This bug has been marked a duplicate of bug 1623294 Black screen on startup after HWE stack update on Ubuntu 14.04 LTS [Radeon R7 graphics] -- 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/1623295 Title: Black screen on startup after HWE stack update on Ubuntu 14.04 LTS [Radeon R7 graphics] Status in xorg package in Ubuntu: New Bug description: After updating the HWE stack on Ubuntu 14.04 LTS, my computer now regularly boots to a black screen upon startup. I briefly see the purple screen (but no plymouth), and then nothing. You can hear the ubuntu drum roll, though, and I can reboot using the alt+Sysrq+B option. Adding the nomodeset parameter in GRUB offers a solution of sorts, but the computer boots with Gallium 0.4 on llvmpipe graphics, which makes gaming basically impossible. I can still boot regularly using the 3.16.0-77-generic kernel saved in GRUB. Other info: 1) I tried an Ubuntu live USB stick with both 14.04.5 on it and then 16.04 and got the same problem. 2) My UEFI firmware is up-to-date as of 1 or 2 days ago. 3) The kernel in question is 4.4.0-36-generic. 4) Ubuntu release: 14.04.5 LTS 5) I have never installed the fglrx driver—I have always used the open-source driver. 6) My exact GPU: AMD A10-7700K Radeon R7 (Kaveri). 7) I'm not sure that the dmesg log automatically attached by apport will be helpful because of the "nomodeset" parameter, so I have attached a dmesg log grabbed from a failed boot. With guidance, I can do the same for other relevant logs. Hope that's helpful! ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.4.0-36.55~14.04.1-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14.1-0ubuntu3.21 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: Tue Sep 13 21:46:45 2016 DistUpgraded: 2016-08-26 20:07:12,800 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Kaveri [Radeon R7 Graphics] [1002:1313] (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation Device [1849:1313] InstallationDate: Installed on 2015-06-24 (447 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic root=UUID=228ea1db-87eb-476d-b97f-5a4a28c618f4 ro nomodeset quiet splash vt.handoff=7 Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2016-08-27 (18 days ago) dmi.bios.date: 03/15/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.30 dmi.board.name: FM2A78M-HD+ R2.0 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.30:bd03/15/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A78M-HD+R2.0:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A 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: Tue Sep 13 21:07:07 2016 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering
[Touch-packages] [Bug 1611363] Re: vim.gtk3 crashes frequently with SIGSEGV in ffi_call_unix64()
** Also affects: vim via https://github.com/vim/vim/issues/851 Importance: Unknown Status: Unknown -- 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/1611363 Title: vim.gtk3 crashes frequently with SIGSEGV in ffi_call_unix64() Status in vim: Unknown Status in vim package in Ubuntu: Confirmed Bug description: Hi, vim-gtk3 crashes so often on my system that it's borderline unusable. My system is a clean install of Ubuntu 16.04. I also (temporarily) renamed my customized ~/.vimrc and ~/.vim. My system is up-to-date as of today (2016-08-09); installed vim-gtk3 is 2:7.4.1689-3ubuntu1.1. The crash happens only (but very frequently, not always) when I launch gvim, either by calling it from a shell or by double-clicking a file in Nautilus. Note that the crash is independent of whether I'm opening a file or not. (At least I tried both variations from the terminal.) There's also a report on vim's bugtracker, but since unity appears in the backtrace, the consensus is that it's probably Ubuntu-specific. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: vim-gtk3 2:7.4.1689-3ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Aug 9 14:34:31 2016 ExecutablePath: /usr/bin/vim.gtk3 InstallationDate: Installed on 2016-07-10 (29 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcCmdline: gvim -f /home/username/Documents/schoul/2016/1G-TODO/01-systemes-equations-TODO/chap01_systemes-equations-NOTES.tex Signal: 11 SourcePackage: vim StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libunity-gtk3-parser.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 Title: vim.gtk3 crashed with SIGSEGV in ffi_call_unix64() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/vim/+bug/1611363/+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 1623531] Re: unity8 desktop boots to black screen on yakkety daily fresh install
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity8 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1623531 Title: unity8 desktop boots to black screen on yakkety daily fresh install Status in unity8 package in Ubuntu: Confirmed Bug description: All new hard installs of yakketty amd64 with unity8/libertine (non- ppa) will boot to black screen on both machines with nVidia and Intel graphics adapters. This makes it virtually impossible to test current/dailys w unity8. Regards.. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: unity8 8.14+16.10.20160831.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Wed Sep 14 10:20:56 2016 InstallationDate: Installed on 2016-09-13 (1 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160913) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) upstart.unity8-filewatcher.log: Failed to open connection to "session" message bus: Failed to connect to socket /run/user/1000/bus: Connection refused Failed to open connection to "session" message bus: Failed to connect to socket /run/user/1000/bus: Connection refused Failed to open connection to "session" message bus: Failed to connect to socket /run/user/1000/bus: Connection refused Failed to open connection to "session" message bus: Failed to connect to socket /run/user/1000/bus: Connection refused To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1623531/+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 1613949] Re: vim-gtk3 Has Unmet Dependencies After `apt-get upgrade` In Ubuntu 16.04.1 Xenial
I was unable to recreate this today: $ sudo apt-get install vim-gtk3 [sudo] password for bdmurray: Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: linux-headers-4.4.0-31 linux-headers-4.4.0-31-generic linux-image-4.4.0-31-generic linux-image-extra-4.4.0-31-generic linux-tools-4.4.0-31 linux-tools-4.4.0-31-generic Use 'sudo apt autoremove' to remove them. Suggested packages: cscope vim-doc The following NEW packages will be installed: vim-gtk3 0 upgraded, 1 newly installed, 0 to remove and 20 not upgraded. Need to get 1,222 kB of archives. After this operation, 2,948 kB of additional disk space will be used. Get:1 http://192.168.10.7/ubuntu xenial-updates/universe amd64 vim-gtk3 amd64 2:7.4.1689-3ubuntu1.1 [1,222 kB] Fetched 1,222 kB in 0s (10.6 MB/s) Sorry, your system lacks support for the snapshot feature Selecting previously unselected package vim-gtk3. (Reading database ... 918193 files and directories currently installed.) Preparing to unpack .../vim-gtk3_2%3a7.4.1689-3ubuntu1.1_amd64.deb ... Unpacking vim-gtk3 (2:7.4.1689-3ubuntu1.1) ... Setting up vim-gtk3 (2:7.4.1689-3ubuntu1.1) ... Where did you get the old version of vim-gtk3? ** Changed in: vim (Ubuntu) Status: Confirmed => Incomplete -- 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/1613949 Title: vim-gtk3 Has Unmet Dependencies After `apt-get upgrade` In Ubuntu 16.04.1 Xenial Status in vim package in Ubuntu: Incomplete Bug description: I have a fresh install of Ubuntu v16.04.1, then I did an `apt-get upgrade` and it only had a few seemingly-minor packages to upgrade (don't remember the list, sorry). Apparently all the core vim packages have been upgraded to 2:7.4.1689-3ubuntu1.1 but vim-gtk3 (and all the other gvim-providing packages I tested) are still held back to 2:7.4.1689-3ubuntu1 so there is a version mis-match. Now I get the following error: [[[ BEGIN PASTE ]]] root@machine:/# apt-get install vim-gtk3 Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: vim-gtk3 : Depends: vim-common (= 2:7.4.1689-3ubuntu1) but 2:7.4.1689-3ubuntu1.1 is to be installed Depends: vim-runtime (= 2:7.4.1689-3ubuntu1) but 2:7.4.1689-3ubuntu1.1 is to be installed E: Unable to correct problems, you have held broken packages. [[[ END PASTE ]]] However I can still get gvim working if I force the installation of the vim-gtk3 package using dpkg. Of course this is not a good solution, because it leaves my system in a state of seemingly-broken packages! [[[ BEGIN PASTE ]]] root@machine:/# dpkg -i --force-depends ./vim-gtk3_7.4.1689-3ubuntu1_amd64.deb Selecting previously unselected package vim-gtk3. (Reading database ... 251539 files and directories currently installed.) Preparing to unpack .../vim-gtk3_7.4.1689-3ubuntu1_amd64.deb ... Unpacking vim-gtk3 (2:7.4.1689-3ubuntu1) ... dpkg: vim-gtk3: dependency problems, but configuring anyway as you requested: vim-gtk3 depends on vim-common (= 2:7.4.1689-3ubuntu1); however: Version of vim-common on system is 2:7.4.1689-3ubuntu1.1. vim-gtk3 depends on vim-runtime (= 2:7.4.1689-3ubuntu1); however: Version of vim-runtime on system is 2:7.4.1689-3ubuntu1.1. Setting up vim-gtk3 (2:7.4.1689-3ubuntu1) ... update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/vim (vim) in auto mode update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/vimdiff (vimdiff) in auto mode update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/rvim (rvim) in auto mode update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/rview (rview) in auto mode update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/vi (vi) in auto mode update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/view (view) in auto mode update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/ex (ex) in auto mode update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/editor (editor) in auto mode update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/gvim (gvim) in auto mode update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/gview (gview) in auto mode update-alternatives: using /usr/bin/vim.gtk3 to provide /usr/bin/rgview (rgview) in auto mode update-alternatives: using /usr/bin/vim.gtk3 to prov
[Touch-packages] [Bug 1581801] Re: UUID base RESUME always wait 5 seconds for activating LVM swap
** Tags added: bootspeed
--
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/1581801
Title:
UUID base RESUME always wait 5 seconds for activating LVM swap
Status in initramfs-tools package in Ubuntu:
Confirmed
Bug description:
Ubuntu 16.04 with LVM have delay around LVM mount.
$ dmesg
[1.126338] FDC 0 is a S82078B
[1.830136] tsc: Refined TSC clocksource calibration: 3392.321 MHz
[1.830140] clocksource: tsc: mask: 0x max_cycles:
0x30e5f904771, max_idle_ns: 440795373543 ns
[6.984151] EXT4-fs (dm-0): mounted filesystem with ordered data
mode. Opts: (null)
[ 10.421370] systemd[1]: systemd 229 running in system mode.
(+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP
+LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID
+ELFUTILS +KMOD -IDN)
[ 10.421397] systemd[1]: Detected virtualization kvm.
LVM partition will be activated by scripts/local-top/lvm2 in initrd.
But scripts/local-top/lvm2 does not take care of resume variable which
is set from UUID base RESUME.
$ cat /usr/share/initramfs-tools/scripts/local-top/lvm2
activate() {
/dev/mapper/*)
}
activate "$ROOT"
activate "$resume"
And then, scripts/local-premount/resume in initrd will always wait 5
seconds for activating LVM swap.
After mounting root filesystem, systemd will activate LVM swap.
$ cat /usr/share/initramfs-tools/scripts/local-premount/resume
SWAPTYPE=$(wait-for-root "${resume}" ${RESUMEDELAY:-5})
RESUME is defined at /etc/initramfs-tools/conf.d/resume which is
created by plugininstall.py.
So plugininstall.py needs to support non-UUID base RESUME,
e.g. RESUME=/dev/mapper/ubuntu--vg-swap_1.
$ sudo su -c 'echo RESUME=/dev/mapper/ubuntu--vg-swap_1 \
> /etc/initramfs-tools/conf.d/resume'
$ sudo update-initramfs -u && sudo reboot
$ dmesg # after boot
[1.095876] FDC 0 is a S82078B
[1.507060] EXT4-fs (dm-0): mounted filesystem with ordered data
mode. Opts: (null)
[1.807522] tsc: Refined TSC clocksource calibration: 3392.321 MHz
[1.807526] clocksource: tsc: mask: 0x max_cycles:
0x30e5f904771, max_idle_ns: 440795373543 ns
[2.648513] systemd[1]: systemd 229 running in system mode.
(+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP
+LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID
+ELFUTILS +KMOD -IDN)
[2.648542] systemd[1]: Detected virtualization kvm.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1581801/+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 1587580] Re: No way to escape an ampersand in UCAction
** Branch linked: lp:~ubuntu-sdk-team/ubuntu-ui-
toolkit/escapeLittleAmpersand
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1587580
Title:
No way to escape an ampersand in UCAction
Status in ubuntu-ui-toolkit package in Ubuntu:
In Progress
Bug description:
Let's say we have an Ubuntu.Action as follow:
import Ubuntu.Components 1.3 as Ubuntu
Ubuntu.Action {
text: "Apps & Scopes"
}
UCAction translates the ampersand as a mnemonic, using QKeySequence.
A way to escape a mnemonic in Qt is to add another ampersand. The resulting
string is "Apps && Scopes".
The UITK component seems not to take in account this situation, since:
- How the string should be shown in e.g. an ActionBar:
"Apps & Scopes"
- How the string is displayed instead in an ActionBar:
"Apps && Scopes"
QKeySequence returns no mnemonic as expected, but UCAction shows two
ampersands.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1587580/+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 1587580] Re: No way to escape an ampersand in UCAction
** Changed in: ubuntu-ui-toolkit (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1587580
Title:
No way to escape an ampersand in UCAction
Status in ubuntu-ui-toolkit package in Ubuntu:
In Progress
Bug description:
Let's say we have an Ubuntu.Action as follow:
import Ubuntu.Components 1.3 as Ubuntu
Ubuntu.Action {
text: "Apps & Scopes"
}
UCAction translates the ampersand as a mnemonic, using QKeySequence.
A way to escape a mnemonic in Qt is to add another ampersand. The resulting
string is "Apps && Scopes".
The UITK component seems not to take in account this situation, since:
- How the string should be shown in e.g. an ActionBar:
"Apps & Scopes"
- How the string is displayed instead in an ActionBar:
"Apps && Scopes"
QKeySequence returns no mnemonic as expected, but UCAction shows two
ampersands.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1587580/+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 1623530] Re: Apport should be disabled by default
Yes, any option that helps it not involving the user would help the new users introduced to Ubuntu (Avoid getting the idea that Ubuntu is constantly having issues because of the popups) and still send the information. This can be something opt-in for the user when installing the system. -- 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/1623530 Title: Apport should be disabled by default Status in apport package in Ubuntu: Confirmed Bug description: I work with large communities (US, India, Latin America) and almost the number one issue they have with Ubuntu or simply scares them off is the fact that errors keep popping up every time. Some times multiples times per minutes, per hour, per day. The reason is how apport works by default. The "solution" is going to /etc/default/apport and setting the option to 0 (Disable). I do understand the full benefit or submitting automatically all bug reports, but this has gotten (And most Ubuntu users will be able to confirm) out of hand with some many popup questions about some bug or another that are simply fixed the moment the report is going to be send (eg: Compiz issue that was fixed a couple of milliseconds later, unity issue, dash issue, firefox issue, etc..). All of them have mechanism to handle failures and basically heal themselves. The question regarding this is: Leaving apport enable by default on an Ubuntu installation simply scares or annoys end users (a lot may I add). Leaving it disabled, it will not send a bug report, but there is no issue in simply creating an ubuntu-bug report through the terminal. So the sending of the report is still valid, but is not forced onto the user (And not forced so many times). This report is back by about 3 years going back and forth with the same apport issue and seeing probably around 500 users I have helped myself with the same issue, since this makes Ubuntu less productive to the actual user, even from start. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apport 2.20.1-0ubuntu2.1 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportLog: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Sep 14 08:16:03 2016 InstallationDate: Installed on 2016-04-22 (144 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2016-08-12T16:38:06.249273 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1623530/+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 1623530] Re: Apport should be disabled by default
I'm working with small numbers, but experience the same issue. But I would argue that if Apport is a part of a healthy Q.A. strategy then leave it in place, but don't involve the user with those pesky popups at login and run-time. -- 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/1623530 Title: Apport should be disabled by default Status in apport package in Ubuntu: Confirmed Bug description: I work with large communities (US, India, Latin America) and almost the number one issue they have with Ubuntu or simply scares them off is the fact that errors keep popping up every time. Some times multiples times per minutes, per hour, per day. The reason is how apport works by default. The "solution" is going to /etc/default/apport and setting the option to 0 (Disable). I do understand the full benefit or submitting automatically all bug reports, but this has gotten (And most Ubuntu users will be able to confirm) out of hand with some many popup questions about some bug or another that are simply fixed the moment the report is going to be send (eg: Compiz issue that was fixed a couple of milliseconds later, unity issue, dash issue, firefox issue, etc..). All of them have mechanism to handle failures and basically heal themselves. The question regarding this is: Leaving apport enable by default on an Ubuntu installation simply scares or annoys end users (a lot may I add). Leaving it disabled, it will not send a bug report, but there is no issue in simply creating an ubuntu-bug report through the terminal. So the sending of the report is still valid, but is not forced onto the user (And not forced so many times). This report is back by about 3 years going back and forth with the same apport issue and seeing probably around 500 users I have helped myself with the same issue, since this makes Ubuntu less productive to the actual user, even from start. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apport 2.20.1-0ubuntu2.1 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportLog: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Sep 14 08:16:03 2016 InstallationDate: Installed on 2016-04-22 (144 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2016-08-12T16:38:06.249273 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1623530/+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 1622893] Re: NetworkManager takes very long to start, or times out, blocked on RNG
** Summary changed: - NetworkManager takes very log to start, or times out, blocked on RNG + NetworkManager takes very long to start, or times out, blocked on RNG -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1622893 Title: NetworkManager takes very long to start, or times out, blocked on RNG Status in Auto Package Testing: Fix Released Status in gnutls28 package in Ubuntu: Triaged Status in network-manager package in Ubuntu: New Bug description: Since a few days ago, NetworkManager.service takes awfully long to start, or even times out on failure and then gets restarted. This happens in a 16.10 desktop amd64 installation in QEMU, or e. g. in the systemd "boot-smoke" autopkgtest where every boot takes > 1:30 minutes due to the NM timeout. In the journal there is no actual logging from /usr/sbin/NetworkManager yet, just the start timeout. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: network-manager 1.2.2-0ubuntu8 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: i3 Date: Tue Sep 13 10:05:05 2016 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback source-directory interfaces.d NetworkManager.conf: [main] plugins=ifupdown,keyfile,ofono [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.2connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1622893/+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 1623530] Re: Apport should be disabled by default
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apport (Ubuntu) Status: New => Confirmed -- 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/1623530 Title: Apport should be disabled by default Status in apport package in Ubuntu: Confirmed Bug description: I work with large communities (US, India, Latin America) and almost the number one issue they have with Ubuntu or simply scares them off is the fact that errors keep popping up every time. Some times multiples times per minutes, per hour, per day. The reason is how apport works by default. The "solution" is going to /etc/default/apport and setting the option to 0 (Disable). I do understand the full benefit or submitting automatically all bug reports, but this has gotten (And most Ubuntu users will be able to confirm) out of hand with some many popup questions about some bug or another that are simply fixed the moment the report is going to be send (eg: Compiz issue that was fixed a couple of milliseconds later, unity issue, dash issue, firefox issue, etc..). All of them have mechanism to handle failures and basically heal themselves. The question regarding this is: Leaving apport enable by default on an Ubuntu installation simply scares or annoys end users (a lot may I add). Leaving it disabled, it will not send a bug report, but there is no issue in simply creating an ubuntu-bug report through the terminal. So the sending of the report is still valid, but is not forced onto the user (And not forced so many times). This report is back by about 3 years going back and forth with the same apport issue and seeing probably around 500 users I have helped myself with the same issue, since this makes Ubuntu less productive to the actual user, even from start. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apport 2.20.1-0ubuntu2.1 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportLog: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Sep 14 08:16:03 2016 InstallationDate: Installed on 2016-04-22 (144 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2016-08-12T16:38:06.249273 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1623530/+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 1591356] Re: keyboard autorepeat in Xmir apps & GTK-on-Mir does not work
Hello Albert, or anyone else affected, Accepted xorg-server into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xorg- server/2:1.18.4-0ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: xorg-server (Ubuntu Xenial) Status: New => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1591356 Title: keyboard autorepeat in Xmir apps & GTK-on-Mir does not work Status in Canonical System Image: Confirmed Status in GTK+: Fix Released Status in gtk+3.0 package in Ubuntu: Triaged Status in libertine package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Fix Released Status in gtk+3.0 source package in Xenial: New Status in libertine source package in Xenial: New Status in xorg-server source package in Xenial: Fix Committed Status in xorg-server package in Ubuntu RTM: New Bug description: [Impact] Auto key repeating does not work in Libertine X apps which is very frustrating to users. [Test Case] 1. Install xterm in libertine 2. Start xterm from the "Xapps" scope 3. Wait for xterm to appear 4. Press and hold a key See how it only appears once and not multiple times as it should. [Regression Potential] Non observed. Original Description: How to reproduce: * Install xterm in libertine * Start xterm from the "Xapps" scope * Wait for xterm to appear * Press and hold a key * See how it only appears once and not multiple times as it should To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1591356/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1620994] Re: unity8-dash crashed with SIGSEGV in dri2_destroy_context()
** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1620994 Title: unity8-dash crashed with SIGSEGV in dri2_destroy_context() Status in unity8 package in Ubuntu: Confirmed Bug description: Ubuntu 16.10 + proposed x86, nvidia 8600gt nouveau unity8-dash crashed with SIGSEGV in eglDestroyContext() ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: unity8 8.14+16.10.20160831.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.6.0-10.12-generic 4.6.5 Uname: Linux 4.6.0-10-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CrashCounter: 1 Date: Wed Sep 7 13:04:53 2016 ExecutablePath: /usr/bin/unity8-dash InstallationDate: Installed on 2016-06-05 (93 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcCmdline: unity8-dash --desktop_file_hint=/usr/share/applications/unity8-dash.desktop SegvAnalysis: Segfault happened at: 0x7fcab45aea3e:mov0x30(%rbp),%rax PC (0x7fcab45aea3e) ok source "0x30(%rbp)" (0x0030) not located in a known VMA region (needed readable region)! destination "%rax" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity8 StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 eglDestroyContext () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqpa-ubuntumirclient.so QOpenGLContext::destroy() () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 Title: unity8-dash crashed with SIGSEGV in eglDestroyContext() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo upstart.unity8-dash.log: [2016-09-07:13:04:52.767] QEGLPlatformContext: eglMakeCurrent failed: 3001 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1620994/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1622827] Re: webbrowser-app crashed with SIGSEGV in dri2_create_context()
** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1622827 Title: webbrowser-app crashed with SIGSEGV in dri2_create_context() Status in webbrowser-app package in Ubuntu: Confirmed Bug description: Todays image of 16.10, updated. login to unity8 gives pretty much unusable session & 3 crashes, this is one. (- nothing actually works except opening items in the launcher, the items/scopes don't work & can't be closed/quit directly, only from the launcher. Other 2 crashes - private - Bug #1620939 Bug #1622826 ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: webbrowser-app 0.23+16.10.20160825-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Mon Sep 12 23:20:56 2016 ExecutablePath: /usr/bin/webbrowser-app InstallationDate: Installed on 2016-09-13 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160910) ProcCmdline: webbrowser-app ProcEnviron: PATH=(custom, user) LANGUAGE=en_US XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f73b78b1512:cmpq $0x0,0x38(%r13) PC (0x7f73b78b1512) ok source "$0x0" ok destination "0x38(%r13)" (0x0038) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: webbrowser-app StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 eglCreateContext () from /usr/lib/x86_64-linux-gnu/mesa-egl/libEGL.so.1 ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0 Title: webbrowser-app crashed with SIGSEGV in eglCreateContext() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1622827/+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
