[Touch-packages] [Bug 1752411] Re: bind9-host, avahi-daemon-check-dns.sh hang forever causes network connections to get stuck
Unsubscribing sponsors for now, awaiting the fixes Robie commented about. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1752411 Title: bind9-host, avahi-daemon-check-dns.sh hang forever causes network connections to get stuck Status in avahi package in Ubuntu: Confirmed Status in bind9 package in Ubuntu: Confirmed Status in openconnect package in Ubuntu: Invalid Status in avahi package in Debian: New Bug description: On 18.04 Openconnect connects successfully to any of multiple VPN concentrators but network traffic does not flow across the VPN tunnel connection. When testing on 16.04 this works flawlessly. This also worked on this system when it was on 17.10. I have tried reducing the mtu of the tun0 network device but this has not resulted in me being able to successfully ping the IP address. Example showing ping attempt to the IP of DNS server: ~$ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 172.29.88.11 nameserver 127.0.0.53 liam@liam-lat:~$ netstat -nr Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 0.0.0.0 192.168.1.1 0.0.0.0 UG0 0 0 wlp2s0 105.27.198.106 192.168.1.1 255.255.255.255 UGH 0 0 0 wlp2s0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 docker0 172.17.0.0 0.0.0.0 255.255.0.0 U 0 0 0 docker0 172.29.0.0 0.0.0.0 255.255.0.0 U 0 0 0 tun0 172.29.88.110.0.0.0 255.255.255.255 UH0 0 0 tun0 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 wlp2s0 liam@liam-lat:~$ ping 172.29.88.11 PING 172.29.88.11 (172.29.88.11) 56(84) bytes of data. ^C --- 172.29.88.11 ping statistics --- 4 packets transmitted, 0 received, 100% packet loss, time 3054ms ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: openconnect 7.08-3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 28 22:11:33 2018 InstallationDate: Installed on 2017-06-15 (258 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: openconnect UpgradeStatus: Upgraded to bionic on 2018-02-22 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1752411/+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 1385903] Re: imagemagick crashes with "stack smashing detected"
Security sponsors should be subscribed, not just sponsors. It should get attention soon. Thanks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libjpeg-turbo in Ubuntu. https://bugs.launchpad.net/bugs/1385903 Title: imagemagick crashes with "stack smashing detected" Status in libjpeg-turbo package in Ubuntu: Confirmed Status in libjpeg-turbo source package in Precise: Won't Fix Status in libjpeg-turbo source package in Trusty: Confirmed Status in libjpeg-turbo source package in Utopic: Won't Fix Status in libjpeg-turbo source package in Vivid: Won't Fix Bug description: Every now and then imagemagick convert crashes like this: $ convert -rotate 270 003632r270.jpg koe.jpg *** stack smashing detected ***: convert terminated Aborted (core dumped) This is perfectly reproducible and happens in every Ubuntu 14.04 box I have at hand that has ImageMagick in it, but not in 12.04. I'll attach the file used in above example (I have several more in case someone wants them). --- ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tt 2149 F pulseaudio CurrentDesktop: LXDE CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied dmesg: write failed: Broken pipe DistroRelease: Ubuntu 14.04 IwConfig: br0 no wireless extensions. lono wireless extensions. eth0 no wireless extensions. Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-37-generic root=/dev/mapper/hostname-root ro acpi_enforce_resources=lax ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 RfKill: Tags: trusty Uname: Linux 3.13.0-37-generic i686 UpgradeStatus: Upgraded to trusty on 2014-07-15 (103 days ago) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 08/09/2007 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 6.00 PG dmi.board.name: 945GM dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd08/09/2007:svn:pn:pvr:rvn:rn945GM:rvr:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1385903/+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 1733321] Re: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18
Artful is End Of Life, and thus, there is nothing else to sponsor; sorry. Please resubscribe ~ubuntu-sponsors if there's something else to sponsor. ** Changed in: network-manager (Ubuntu Artful) Status: New => Won't Fix -- 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/1733321 Title: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18 Status in network-manager package in Ubuntu: New Status in network-manager source package in Artful: Won't Fix Bug description: [Impact] The killswitches-no-urfkill autopkgtest fails sometimes because nmcli reports the old state when it's called right after rfkill block/unblock. Adding a sleep before calling nmcli fixes the issue. ppc64el ADT log from failed testcase: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-artful/artful/ppc64el/n/network- manager/20171120_100719_28642@/log.gz Testcase output: - autopkgtest [10:04:48]: test killswitches-no-urfkill: [--- make -C /lib/modules/4.13.0-17-generic/build KBUILD_SRC=/lib/modules/4.13.0-17-generic/build M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic' AR /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o CC [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o Building modules, stage 2. MODPOST 1 modules CC /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o LD [M] /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic' ERROR: NM could not track device state. autopkgtest [10:05:20]: test killswitches-no-urfkill: ---] autopkgtest [10:05:20]: test killswitches-no-urfkill: - - - - - - - - - - results - - - - - - - - - - killswitches-no-urfkill FAIL non-zero exit status 1 - Package versions [artful/ppc64el]: network-manager 1.8.4-1ubuntu3 linux-meta 4.13.0.17.18 [Test Case] 2.1. Download network-manager package source code $ apt-get source network-manager 2.2. Run killswitches-no-urfkill testcase $ cd network-manager-1.8.4 $ sudo ./debian/tests/killswitches-no-urfkill [Regression Potential] No regression potential. The fix touches only the testcase shipped with the source package and it doesn't change the binary package. The sleep time added is very small, so no possibility of causing testcase timeout. [Other Info] On ppc64el architecture, it was observed that a fix for systemd is also needed (see bug 1734908) for the testcase to be successful. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1733321/+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 1714518] Re: GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network shares in file chooser
Artful is EOL.
** Changed in: gtk+3.0 (Ubuntu Artful)
Status: Triaged => Won't Fix
--
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/1714518
Title:
GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network
shares in file chooser
Status in GTK+:
Fix Released
Status in gtk+3.0 package in Ubuntu:
Fix Released
Status in gtk+3.0 source package in Trusty:
Triaged
Status in gtk+3.0 source package in Xenial:
Triaged
Status in gtk+3.0 source package in Artful:
Won't Fix
Bug description:
Steps to reproduce:
1. Install any Gtk3 application such as Firefox or Chromium which use modern
file-chooser dialog.
2. Mount network location through fstab or file-manager ("smb://" = SMB/CIFS,
"sftp://; = SFTP/SSH and so on)
3. Try to save/open file to/from the remote location from Gtk3 application.
Expected results:
* user is able to find network folder and save/open file to/from it with
GtkFileChooser dialog
Actual results:
* user is unable to find network folder and save/open file to/from it with
GtkFileChooser dialog and many user applications are affected
-
Original bug description is below:
GTK+3 doesn't show FUSE network shares in file chooser - it used to do
so in GTK+2, and the GTK+3 documentation still mentions it should do
it.
In the mean time, every user of every application switching to GTK+3
-- including Chromium, at some point between 58 and 60 -- (a change
which happened in 16.04 LTS!!), loses the functionality to open or
save directly to a network share.
I had chosen 16.04 LTS for deploying our workstations at work, and my 50
users have been suddenly unable to do a simple operation they have to do dozens
of times a day.
They now have to "buffer" these files to their local filesystem when saving
them and before uploading them, and then copy them to the company's network
shares.
They were already a little bit grumpy when it stopped working with Firefox,
and are now really side-eyeing me when they apply updates and find Chromium
broken.
I have reported the bug upstream and provided a patch to fix this. I
hope you'll be able and willing to include it to Ubuntu's GTK+3
package.
Thanks in advance.
Colin
To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1714518/+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 1686183] Re: Ship ubuntu-advantage in ubuntu-minimal
Unsubscribing ~ubuntu-sponsors as there seems to be nothing to sponsor here. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1686183 Title: Ship ubuntu-advantage in ubuntu-minimal Status in ubuntu-advantage-tools package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-advantage-tools source package in Precise: Fix Released Status in ubuntu-meta source package in Precise: Fix Released Status in ubuntu-advantage-tools source package in Trusty: Fix Released Status in ubuntu-meta source package in Trusty: Confirmed Status in ubuntu-advantage-tools source package in Xenial: Fix Released Status in ubuntu-meta source package in Xenial: Confirmed Status in ubuntu-advantage-tools source package in Yakkety: Won't Fix Status in ubuntu-meta source package in Yakkety: Won't Fix Status in ubuntu-advantage-tools source package in Zesty: Fix Released Status in ubuntu-meta source package in Zesty: Won't Fix Status in ubuntu-advantage-tools source package in Artful: Fix Released Status in ubuntu-meta source package in Artful: Fix Released Bug description: The ubuntu-advantage-tools package is a bit odd as it was first landed in precise to support the ESM effort inside canonical. [0] In order to bring this package up to date across other series in ubuntu, it has been recommended by the Ubuntu Foundations team to land into trusty next, then forward-port pocket-copy to all supported series until we get to the devel release. The version here: https://github.com/CanonicalLtd/ubuntu-advantage- script/releases/tag/v2 ... has all on-disk bits correctly working, for all series, but no-ops on any release other than precise (ESM is only for "unsupported" LTS releases as it were). This is a request to land ubuntu-advantage- tools into trusty, then pocket-copy it to supported series of ubuntu once that is finished. [Impact] * Allow ubuntu-advantage users to access the extended security maintenance script with a simple command line tool. This script needs to hit precise machines and be easy for ubuntu-advantage customers to enable, thus basefiles was chosen as a home. [Test Case] * Run ubuntu-advantage, it should print out help * Run sudo ubuntu-advantage enable (without sudo it will warn you), but you need to be an ubuntu-advantage customer to get that token. In the end, the script simply adds and removes an /etc/apt/sources.list.d entry. * Verify that the MOTD does not contain any mention of ubuntu- advantage esm or precise and its end of life * Verify that ubuntu-advantage enable-esm installs needed dependencies: - create the following file and its contents to have apt not install recommended packages by default: $ cat /etc/apt/apt.conf.d/no-recommends APT::Install-Recommends "false"; - remove ca-certificates and apt-transport-https: $ sudo apt remove ca-certificates apt-transport-https - run sudo ubuntu-advantage enable-esm and verify that the two removed packages are reinstalled * you can contact me (d...@canonical.com) if you would like a token for test purposes. [Regression Potential] * Low, this is a new script, not included in any automated startup paths. [Other Info] * http://blog.dustinkirkland.com/2017/03/ubuntu-1204-esm.html [0] https://insights.ubuntu.com/2017/03/14/introducing-ubuntu-12-04 -esm-extended-security-maintenance/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1686183/+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 1696418] Re: gnome-help/shell-introduction.page link to removed files
Sponsoring this now with minor tweaks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to language-pack-gnome-es- base in Ubuntu. https://bugs.launchpad.net/bugs/1696418 Title: gnome-help/shell-introduction.page link to removed files Status in gnome-user-docs package in Ubuntu: Invalid Status in language-pack-gnome-es-base package in Ubuntu: Invalid Status in gnome-user-docs source package in Trusty: In Progress Status in language-pack-gnome-es-base source package in Trusty: Won't Fix Bug description: [Impact] The latest language pack update for trusty at 2016-07-20 did (for unknown reason) not include the localized gnome-help pages, so gnome- help is displayed in English whatever the session language is. The proposed upload sets the NO_PKG_MANGLE variable, so the package is built without language stripping. This works around the failure with the language packs. [Test Case] Open gnome-help with a non-English language (using Spanish as example): LANGUAGE=es yelp help:gnome-help Current package: Showed in English Proposed package: Showed in Spanish [Regression Potential] Negligible. This is in practice a no-change rebuild. [Original description] p.e.: /usr/share/help/es/gnome-help/shell-introduction.page is a link to /usr/share/help-langpack/es/gnome-help/shell-introduction.page A lot of pages became broken links since some update of language-pack- gnome-*-base lost target files. Most of missing files are listed at: https://packages.ubuntu.com/trusty/all/language-pack-gnome-*-base/filelist (Replace "*" by any packaged language, such as "es") ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-user-guide 3.8.2-1 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic i686 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 CasperVersion: 1.340 CurrentDesktop: GNOME Date: Wed Jun 7 13:15:08 2017 LiveMediaBuild: Ubuntu-GNOME 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: gnome-user-docs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-user-docs/+bug/1696418/+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 1427807] Re: usermod's man refers to --*-sub-uids but accepts only --*-subuids
Artful is no longer supported; sorry this couldn't get in. If you think it's useful for Xenial, please change the status, attach another debdiff, and resubscribe sponsors. ** Changed in: shadow (Ubuntu) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1427807 Title: usermod's man refers to --*-sub-uids but accepts only --*-subuids Status in shadow package in Ubuntu: Won't Fix Bug description: The man page refers to sub-uids and sub-gids but those don't take any "-" between sub and [ug]ids. The help message conforms to what the command accepts though. $ man usermod | grep -F -- -sub -v, --add-sub-uids FIRST-LAST -V, --del-sub-uids FIRST-LAST This option may be specified multiple times to remove multiple ranges to a users account. When both --del-sub-uids and --add-sub-uids are specified remove of all subordinate uid ranges happens before any -w, --add-sub-gids FIRST-LAST -W, --del-sub-gids FIRST-LAST This option may be specified multiple times to remove multiple ranges to a users account. When both --del-sub-gids and --add-sub-gids are specified remove of all subordinate gid ranges happens before any $ usermod --help | grep -F -- -sub -v, --add-subuids FIRST-LAST add range of subordinate uids -V, --del-subuids FIRST-LAST remvoe range of subordinate uids -w, --add-subgids FIRST-LAST add range of subordinate gids -W, --del-subgids FIRST-LAST remvoe range of subordinate gids More info on the environment: $ lsb_release -rd Description: Ubuntu 14.04.2 LTS Release: 14.04 $ apt-cache policy passwd passwd: Installed: 1:4.1.5.1-1ubuntu9 Candidate: 1:4.1.5.1-1ubuntu9 Version table: *** 1:4.1.5.1-1ubuntu9 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: passwd 1:4.1.5.1-1ubuntu9 ProcVersionSignature: Ubuntu 3.13.0-46.77-generic 3.13.11-ckt15 Uname: Linux 3.13.0-46-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 3 13:37:50 2015 InstallationDate: Installed on 2014-01-26 (400 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140124) SourcePackage: shadow UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1427807/+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 1783571] Re: Set Yaru as default
** Merge proposal linked: https://code.launchpad.net/~3v1n0/ubuntu/+source/gnome-session/+git/gnome-session/+merge/353283 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1783571 Title: Set Yaru as default Status in gnome-session package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Status in ubuntu-settings package in Ubuntu: Confirmed Status in yaru-theme package in Ubuntu: Fix Released Bug description: Set Yaru as default ubuntu 18.10 theme. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1783571/+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 1785764] Re: Ubuntu default colour profile distorts colours on some machines (white looks green, too dark, or under-saturated)
On the other hand, maybe we need to treat disabling the default colour profile as a workaround. I forgot to mention that in at least one case I noticed similar problems in web browsers and image viewers even when using a properly custom calibrated profile for my display. So a real fix might have to come in the apps themselves, or maybe just one or two image decoding libraries that are misinterpreting the profile data (maybe they don't know or expect the whole compositor is applying the profile already?). To do this someone would need to dig into the code of an affected app and see how/where it is using the colour profile data. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/1785764 Title: Ubuntu default colour profile distorts colours on some machines (white looks green, too dark, or under-saturated) Status in colord package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Bug description: Using Ubuntu 18.04.1 LTS Running on an i7-6700k with a GTX 1080 Reproducible with nvidia-driver-396 or xserver-xorg-video-nouveau and a single 4K screen (TV) connected via HDMI. The issue: Any dark content displayed by an effected application (e.g. a very dark image or dark themed web page) is much darker than intended making it almost unusable. This only effects applications that are launched when the 4K screen is connected. If i disconnect the 4K screen, launch the app via a different 1080p monitor then reconnect the 4K screen the app remains unaffected. The only apps i have found so far that are effected by this are Google Chrome and Image Viewer. That said this is only noticeable when the app is displaying dark contend so if other apps are affected it may be impossible to tell. The attached screenshot uses a black to white gradient image to clearly demonstrate the issue. Is seems like it may be an issue with colour depth as bellow a certain brightness it just goes strait to black. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1785764/+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 1416261] Re: package dbus 1.8.12-1ubuntu1 failed to install/upgrade: triggers looping, abandoned
ealthuis, please file a new bug report with ubuntu-bug dpkg This will collect logs that could help diagnose the situation. Thanks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1416261 Title: package dbus 1.8.12-1ubuntu1 failed to install/upgrade: triggers looping, abandoned Status in dbus package in Ubuntu: Won't Fix Bug description: i upgred and i get the error ProblemType: Package DistroRelease: Ubuntu 15.04 Package: dbus 1.8.12-1ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-11.12-generic 3.18.3 Uname: Linux 3.18.0-11-generic i686 ApportVersion: 2.15.1-0ubuntu4 Architecture: i386 Date: Fri Jan 30 08:40:40 2015 DuplicateSignature: package:dbus:1.8.12-1ubuntu1:triggers looping, abandoned ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2014-10-03 (118 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha i386 (20140923) SourcePackage: dbus Title: package dbus 1.8.12-1ubuntu1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1416261/+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 1785764] Re: Some applications render too dark when a 4K screen is attached.
Great! I checked and it was only a year ago that the rest of us noticed the problem and found a solution (including Matthew Paul Thomas, Robert Ancell and myself). If the problem is still occurring in 18.04 then we need to do something about it. That something is to ensure Ubuntu ships with NO ACTIVE colour profile, which has been the fix for all of us so far... ** Tags added: bionic ** Summary changed: - Some applications render too dark when a 4K screen is attached. + Ubuntu default colour profile distorts colours on some machines (white looks green, too dark, or under-saturated) ** Package changed: ubuntu => colord (Ubuntu) ** Changed in: colord (Ubuntu) Status: Invalid => Confirmed ** Also affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-control-center (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/1785764 Title: Ubuntu default colour profile distorts colours on some machines (white looks green, too dark, or under-saturated) Status in colord package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Bug description: Using Ubuntu 18.04.1 LTS Running on an i7-6700k with a GTX 1080 Reproducible with nvidia-driver-396 or xserver-xorg-video-nouveau and a single 4K screen (TV) connected via HDMI. The issue: Any dark content displayed by an effected application (e.g. a very dark image or dark themed web page) is much darker than intended making it almost unusable. This only effects applications that are launched when the 4K screen is connected. If i disconnect the 4K screen, launch the app via a different 1080p monitor then reconnect the 4K screen the app remains unaffected. The only apps i have found so far that are effected by this are Google Chrome and Image Viewer. That said this is only noticeable when the app is displaying dark contend so if other apps are affected it may be impossible to tell. The attached screenshot uses a black to white gradient image to clearly demonstrate the issue. Is seems like it may be an issue with colour depth as bellow a certain brightness it just goes strait to black. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1785764/+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 1760818] Re: gedit and gnome-calculator transparency/graphics corruption issue
** Package changed: mutter (Ubuntu) => gtk+3.0 (Ubuntu) ** No longer affects: ubuntu-themes (Ubuntu) ** Summary changed: - gedit and gnome-calculator transparency/graphics corruption issue + gedit and gnome-calculator transparency/graphics corruption issue when GTK_IM_MODULE=xim is set -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1760818 Title: gedit and gnome-calculator transparency/graphics corruption issue when GTK_IM_MODULE=xim is set Status in gtk+3.0 package in Ubuntu: Confirmed Status in im-config package in Ubuntu: Confirmed Bug description: In a "Ubuntu" (Xorg) session on 18.04 gedit and gnome-calculator suffer from a graphics issue where parts of their windows hold parts of wallpaper or other windows' contents as background. See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: light-themes 16.10+18.04.20180328-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 3 09:12:31 2018 PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: Upgraded to bionic on 2018-02-07 (54 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1760818/+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 1785764] [NEW] Ubuntu default colour profile distorts colours on some machines (white looks green, too dark, or under-saturated)
You have been subscribed to a public bug: Using Ubuntu 18.04.1 LTS Running on an i7-6700k with a GTX 1080 Reproducible with nvidia-driver-396 or xserver-xorg-video-nouveau and a single 4K screen (TV) connected via HDMI. The issue: Any dark content displayed by an effected application (e.g. a very dark image or dark themed web page) is much darker than intended making it almost unusable. This only effects applications that are launched when the 4K screen is connected. If i disconnect the 4K screen, launch the app via a different 1080p monitor then reconnect the 4K screen the app remains unaffected. The only apps i have found so far that are effected by this are Google Chrome and Image Viewer. That said this is only noticeable when the app is displaying dark contend so if other apps are affected it may be impossible to tell. The attached screenshot uses a black to white gradient image to clearly demonstrate the issue. Is seems like it may be an issue with colour depth as bellow a certain brightness it just goes strait to black. ** Affects: colord (Ubuntu) Importance: Undecided Status: Invalid ** Tags: 4k bionic bot-comment colour depth display -- Ubuntu default colour profile distorts colours on some machines (white looks green, too dark, or under-saturated) https://bugs.launchpad.net/bugs/1785764 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to colord in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1416261] Re: package dbus 1.8.12-1ubuntu1 failed to install/upgrade: triggers looping, abandoned
In fact this is the first time in 11years an upgrade failed with this error. Upgrade from 16.04 to 18.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1416261 Title: package dbus 1.8.12-1ubuntu1 failed to install/upgrade: triggers looping, abandoned Status in dbus package in Ubuntu: Won't Fix Bug description: i upgred and i get the error ProblemType: Package DistroRelease: Ubuntu 15.04 Package: dbus 1.8.12-1ubuntu1 ProcVersionSignature: Ubuntu 3.18.0-11.12-generic 3.18.3 Uname: Linux 3.18.0-11-generic i686 ApportVersion: 2.15.1-0ubuntu4 Architecture: i386 Date: Fri Jan 30 08:40:40 2015 DuplicateSignature: package:dbus:1.8.12-1ubuntu1:triggers looping, abandoned ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2014-10-03 (118 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha i386 (20140923) SourcePackage: dbus Title: package dbus 1.8.12-1ubuntu1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1416261/+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 1787508] [NEW] (non-syslog) log file entries are missing the newline when loglinelen is set to a non-positive number (sudo version 1.8.14 - 1.8.16)
Public bug reported: This is basically a request to have an upstream patch applied to the current Ubuntu Xenial package. Changes made in sudo 1.8.14 introduced this bug. It was fixed upstream in 1.8.17 https://www.sudo.ws/devel.html#1.8.17b1 https://bugzilla.sudo.ws/show_bug.cgi?id=742 Ubuntu release: Ubuntu 16.04.5 LTS Package version: sudo/xenial-updates,now 1.8.16-0ubuntu1.5 amd64 I am willing to help fix this (literally a one-liner in the patch), I just don't know the proper channels. ** Affects: sudo (Ubuntu) Importance: Undecided Status: New -- 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/1787508 Title: (non-syslog) log file entries are missing the newline when loglinelen is set to a non-positive number (sudo version 1.8.14 - 1.8.16) Status in sudo package in Ubuntu: New Bug description: This is basically a request to have an upstream patch applied to the current Ubuntu Xenial package. Changes made in sudo 1.8.14 introduced this bug. It was fixed upstream in 1.8.17 https://www.sudo.ws/devel.html#1.8.17b1 https://bugzilla.sudo.ws/show_bug.cgi?id=742 Ubuntu release: Ubuntu 16.04.5 LTS Package version: sudo/xenial-updates,now 1.8.16-0ubuntu1.5 amd64 I am willing to help fix this (literally a one-liner in the patch), I just don't know the proper channels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1787508/+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 1760358] Re: Bash read into array is not working
Ah!!! Actually, this does work,
$ simon=( $( ls -1 /usr ) )
$ echo ${#simon[@]}
8
$ echo ${simon[@]}
bin games include lib local sbin share src
This will still cause scripts in the wild to break. But at least there's
a workaround.
Simon
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bash in Ubuntu.
https://bugs.launchpad.net/bugs/1760358
Title:
Bash read into array is not working
Status in bash package in Ubuntu:
New
Bug description:
This issue is found in the Bionic Beaver (Ubuntu 18) beta.
How it should work (e.g. on Xenial)
---
$ read -a simon <<< $( ls -1 /usr )
$ echo ${#simon[@]}
9
$ echo ${simon[@]}
bin games include lib local sbin share src var
How it works (wrongly) on Bionic
$ read -a simon <<< $( ls -1 /usr )
$ echo ${#simon[@]}
1
$ echo ${simon[@]}
bin
Release
---
Description: Ubuntu Bionic Beaver (development branch)
Release: 18.04
Package Version
---
Installed: 4.4.18-1ubuntu1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1760358/+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 1762952] Re: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default
This bug was fixed in the package console-setup - 1.178ubuntu2.6
---
console-setup (1.178ubuntu2.6) bionic; urgency=medium
* keyboard-configuration.config: Only treat missing XKBOPTIONS as
empty.
console-setup (1.178ubuntu2.5) bionic; urgency=medium
* keyboard-configuration.config: While sourcing config files to re-seed
debconf, load missing variables as empty values of same (LP: #1762952)
console-setup (1.178ubuntu2.4) bionic; urgency=medium
* keyboard-configuration.{config,templates}: There is no good default for
layout toggling, stop pretending there is. Console users can set one
with dpkg-reconfigure or editing /etc/defaults/keyboard (LP: #1762952)
-- Adam Conrad Wed, 08 Aug 2018 17:32:23 -0600
** Changed in: console-setup (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
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/1762952
Title:
Alternative shortcut for layout switching Alt+Shift unexpectedly set
by default
Status in console-setup package in Ubuntu:
Fix Released
Status in gnome-control-center package in Ubuntu:
Invalid
Status in console-setup source package in Bionic:
Fix Released
Status in gnome-control-center source package in Bionic:
Invalid
Bug description:
[Impact]
The keyboard-configuration package provides a tool for configuring the
keyboard via /etc/default/keyboard. However, there are desktop GUIs
which provide such tools as well, and in the case of gnome-control-
center it has another idea of what /etc/default/keyboard should
contain. In short: The different tools don't play well together.
The proposed upload does not claim to fix all issues with this
incompatibility. But one of the annoyances is that a pure upgrade of
the keyboard-configuration package may result in a changed keyboard
configuration without the user asking for it. The proposed upload does
address that particular issue on desktop systems.
[Test Case]
1. On an Ubuntu 18.04 system, make sure that the contents of
/etc/default/keyboard is 'the g-c-c style', for instance:
XKBLAYOUT=se,us
BACKSPACE=guess
XKBVARIANT=,
2. Reboot.
3. Upgrade to the version of the keyboard-configuration package in
bionic-proposed.
=> Find that /etc/default/keyboard was not changed through the
upgrade.
4. Run the command
sudo dpkg-reconfigure keyboard-configuration
=> Find that you are now offered to change your keyboard
configuration.
[Regression Potential]
As a result of this upload, and unlike before, no keyboard
configuration will happen behind the scenes on a desktop system due to
an upgrade of the keyboard-configuration package. This is the desired
change, and I can't think of a case when a user would want the
configuration to be changed without having asked for it.
[Original description]
Version: Ubuntu 18.04 Final Beta with default Gnome Shell included in
18.04
Steps to reproduce:
1. Define two keyboard input methods in Settings -> Region & Language ->
Input Sources
2. Open several applications
3. Observe that application windows can be iterated with Alt + Tab
4. Once application window iteration was begun with Alt + Tab, try to iterate
backwards with Alt + Shift + Tab.
5. Try to change keyboard input method switching hotkeys in Settings ->
Region & Language -> Input Sources -> Options.
6. Observe that Keyboard shortcut for "Alternative switch to next source" is
set to "Alt + Shift" and that keyboard shortcuts can only be changed in
Settings -> Devices -> Keyboard -> Keyboard Shortcuts.
7. Observe that the shortcut for "Alternative switch to next source" is not
available for configuration in Settings -> Devices -> Keyboard -> Keyboard
Shortcuts.
Actual state:
* Performing step 4 does not select the previous app in application switcher
but instead changes keyboard input method.
Expected state:
* The shortcut for "Alternative switch to next source" can be changed and /
or deactivated in Settings -> Devices -> Keyboard -> Keyboard Shortcuts.
Notes:
* The above was working fine in Ubuntu 17.10. I assume "Alternative switch to
next source" did not exist in that version of Gnome Shell.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1762952/+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 1760358] Re: Bash read into array is not working
Hello
This still affects Bionic final release version: Ubuntu 18.04.1 LTS,
bash 4.4.19(1).
Using bash's array capabilities in this way is extremely useful and
being unable to use it makes bash scripting much harder work. I'm
surprised such a serious issue remains unfixed some 4 months after
Bionic was released! I'm sure this would be affecting all sorts of
sysadmin scripts in the wild.
Simon
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bash in Ubuntu.
https://bugs.launchpad.net/bugs/1760358
Title:
Bash read into array is not working
Status in bash package in Ubuntu:
New
Bug description:
This issue is found in the Bionic Beaver (Ubuntu 18) beta.
How it should work (e.g. on Xenial)
---
$ read -a simon <<< $( ls -1 /usr )
$ echo ${#simon[@]}
9
$ echo ${simon[@]}
bin games include lib local sbin share src var
How it works (wrongly) on Bionic
$ read -a simon <<< $( ls -1 /usr )
$ echo ${#simon[@]}
1
$ echo ${simon[@]}
bin
Release
---
Description: Ubuntu Bionic Beaver (development branch)
Release: 18.04
Package Version
---
Installed: 4.4.18-1ubuntu1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1760358/+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 1200009] Re: HP 1102 does not print
Thanks for the update, Istarion-rus. I will close the report now. Have a great day! :) G Closed per reporter’s feedback. ** Changed in: cups (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/129 Title: HP 1102 does not print Status in cups package in Ubuntu: Invalid Bug description: In printer status i see error message Printer "HP-LaserJet- Professional-p1102": "hplip.plugin" orlan@orlan-i5-3570k:~$ cupsd cupsd: Child exited on signal 15 orlan@orlan-i5-3570k:~$ orlan@orlan-i5-3570k:~$ lsb_release -rd Description: Ubuntu 13.04 Release: 13.04 orlan@orlan-i5-3570k:~$ apt-cache policy cups cups: Установлен: 1.6.2-1ubuntu7 Кандидат: 1.6.2-1ubuntu7 Таблица версий: *** 1.6.2-1ubuntu7 0 500 http://ru.archive.ubuntu.com/ubuntu/ raring-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1.6.2-1ubuntu5 0 500 http://ru.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages orlan@orlan-i5-3570k:~$ apt-cache policy cups hplip cups: Установлен: 1.6.2-1ubuntu7 Кандидат: 1.6.2-1ubuntu7 Таблица версий: *** 1.6.2-1ubuntu7 0 500 http://ru.archive.ubuntu.com/ubuntu/ raring-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1.6.2-1ubuntu5 0 500 http://ru.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages hplip: Установлен: 3.13.3-1 Кандидат: 3.13.3-1 Таблица версий: *** 3.13.3-1 0 500 http://ru.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: cups 1.6.2-1ubuntu7 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 Uname: Linux 3.8.0-27-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Thu Jul 11 09:05:57 2013 InstallationDate: Installed on 2013-09-07 (-58 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) Lpstat: device for HP-LaserJet-Professional-p1102: smb://1/SMIRNOF/HP%20LaserJet%20Professional%20P1102 MachineType: System manufacturer System Product Name MarkForUpload: True Papersize: a4 PpdFiles: HP-LaserJet-Professional-p1102: HP LaserJet Professional p1102, hpcups 3.13.3, requires proprietary plugin ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-27-generic root=UUID=2713a651-6fe1-43a6-ae53-9d453172ecdc ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1002 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8B75-M dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1002:bd10/16/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8B75-M:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/129/+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 1241643] Re: package cups 1.7.0~rc1-0ubuntu5 failed to install/upgrade: subproces installed post-installation script gaf een foutwaarde 1 terug
Thanks for the update, Sven. I will close the report now. Have a great day! :) G Closed per reporter’s feedback. ** Changed in: cups (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1241643 Title: package cups 1.7.0~rc1-0ubuntu5 failed to install/upgrade: subproces installed post-installation script gaf een foutwaarde 1 terug Status in cups package in Ubuntu: Invalid Bug description: I tried to install a canon ip4000 printer, installation got stuck. ProblemType: Package DistroRelease: Ubuntu 13.10 Package: cups 1.7.0~rc1-0ubuntu5 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 CupsErrorLog: Date: Fri Oct 18 15:34:53 2013 DuplicateSignature: package:cups:1.7.0~rc1-0ubuntu5:subproces installed post-installation script gaf een foutwaarde 1 terug ErrorMessage: subproces installed post-installation script gaf een foutwaarde 1 terug InstallationDate: Installed on 2013-10-10 (8 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Sony Corporation VPCF11M1E MarkForUpload: True Papersize: a4 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=20f1a842-8225-44fc-99e8-fb648057f991 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=20f1a842-8225-44fc-99e8-fb648057f991 ro quiet splash vt.handoff=7 SourcePackage: cups Title: package cups 1.7.0~rc1-0ubuntu5 failed to install/upgrade: subproces installed post-installation script gaf een foutwaarde 1 terug UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/14/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R0280Y6 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR0280Y6:bd05/14/2010:svnSonyCorporation:pnVPCF11M1E:pvrC603VG5N:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VPCF11M1E dmi.product.version: C603VG5N dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1241643/+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 1087075] Re: Duplex options ignored for printing Postscript
Hi Reuben. Thanks for the update. I will change the status back to “new” and will look at next steps. Take care :) G ** Changed in: cups (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1087075 Title: Duplex options ignored for printing Postscript Status in cups package in Ubuntu: New Bug description: Printing a Postscript file using lp -o Duplex=DuplexNoTumble foo.ps does not give duplex output. I have read other bug reports, turned collation off and I can't see anything else that might be causing the problem. Printing from the gtk print dialog, the duplex setting I choose is respected, but because of a font-related bug with gtkprint, I'm using the lp command directly to print my Postscript file. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: cups 1.6.1-0ubuntu11.3 ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7 Uname: Linux 3.5.0-19-generic x86_64 ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Thu Dec 6 00:59:07 2012 InstallationDate: Installed on 2011-10-14 (418 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) Lpstat: device for bunyan: dnssd://Lexmark%20X543._ipp._tcp.local/ MachineType: Apple Inc. MacBookAir4,2 MarkForUpload: True Papersize: a4 PpdFiles: bunyan: Lexmark X543 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-19-generic root=UUID=3f1df709-5d4e-4a93-8844-6cf574c52f87 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to quantal on 2012-10-20 (46 days ago) dmi.bios.date: 06/30/2011 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA41.88Z.0077.B00.1106300929 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-742912EFDBEE19B3 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir4,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-742912EFDBEE19B3 dmi.modalias: dmi:bvnAppleInc.:bvrMBA41.88Z.0077.B00.1106300929:bd06/30/2011:svnAppleInc.:pnMacBookAir4,2:pvr1.0:rvnAppleInc.:rnMac-742912EFDBEE19B3:rvrMacBookAir4,2:cvnAppleInc.:ct10:cvrMac-742912EFDBEE19B3: dmi.product.name: MacBookAir4,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1087075/+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 1134036] Re: Failure when using ssh with a locale that is not configured on the server
** Also affects: base-files (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: maas (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1134036 Title: Failure when using ssh with a locale that is not configured on the server Status in base-files package in Ubuntu: Fix Released Status in maas package in Ubuntu: Invalid Status in base-files source package in Bionic: New Status in maas source package in Bionic: New Bug description: If LC_ALL is not set (which seems to be the default on a few server installations I've done now), mid way through installing, you get this backtrace and then the installation just hangs. You can ctrl-c out of it but the package is left half configured. Traceback (most recent call last): File "/usr/bin/django-admin", line 5, in management.execute_from_command_line() File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", line 443, in execute_from_command_line utility.execute() File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", line 382, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 196, in run_from_argv self.execute(*args, **options.__dict__) File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 232, in execute output = self.handle(*args, **options) File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 371, in handle return self.handle_noargs(**options) File "/usr/lib/python2.7/dist-packages/south/management/commands/syncdb.py", line 90, in handle_noargs syncdb.Command().execute(**options) File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 232, in execute output = self.handle(*args, **options) File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 371, in handle return self.handle_noargs(**options) File "/usr/lib/python2.7/dist-packages/django/core/management/commands/syncdb.py", line 57, in handle_noargs cursor = connection.cursor() File "/usr/lib/python2.7/dist-packages/django/db/backends/__init__.py", line 308, in cursor cursor = util.CursorWrapper(self._cursor(), self) File "/usr/lib/python2.7/dist-packages/django/db/backends/postgresql_psycopg2/base.py", line 177, in _cursor self.connection = Database.connect(**conn_params) File "/usr/lib/python2.7/dist-packages/psycopg2/__init__.py", line 179, in connect connection_factory=connection_factory, async=async) psycopg2.OperationalError: FATAL: password authentication failed for user "maas" FATAL: password authentication failed for user "maas" Related bugs: * bug 969462: [postgres] fails to start after install if invalid locale is set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1134036/+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 1787460] Re: Unattended upgrades removed linux-image-generic
Looking some more at the apt history log file we can see mutter version 3.28.3-2~ubuntu18.04.1 being installed. This package only exists in the -proposed version of the repository. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1787460 Title: Unattended upgrades removed linux-image-generic Status in unattended-upgrades package in Ubuntu: New Bug description: On a fairly fresh install of 18.04 with no modifications whatsoever to the unattended-upgrades configuration, it decided to remove linux- image-generic which also removed linux-modules-extra which caused sound drivers to disappear, etc. The relative snippet from /var/log/unattended-upgrades/unattended- upgrades.log is: 2018-08-15 06:18:00,048 INFO Starting unattended upgrades script 2018-08-15 06:18:00,048 INFO Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic 2018-08-15 06:18:01,552 INFO Removing unused kernel packages: linux-headers-generic linux-image-generic linux-headers-4.15.0-32-generic linux-headers-4.15.0-32 2018-08-15 06:18:01,588 WARNING Keeping auto-removable linux-headers-generic package(s) because it would also remove the following packages which should be kept in this step: libxml2 linux-image-4.15.0-32-generic linux-modules-4.15.0-32-generic linux-modules-extra-4.15.0-32-generic 2018-08-15 06:18:09,476 INFO Packages that were successfully auto-removed: linux-headers-4.15.0-32 linux-headers-4.15.0-32-generic linux-headers-generic linux-image-generic 2018-08-15 06:18:09,477 INFO Packages that are kept back: linux-headers-generic 2018-08-15 06:18:10,300 INFO Packages that will be upgraded: libxml2 linux-image-generic 2018-08-15 06:18:10,300 INFO Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log 2018-08-15 06:18:39,238 INFO All upgrades installed 2018-08-15 06:18:42,818 INFO Packages that were successfully auto-removed: linux-image-generic linux-modules-extra-4.15.0-32-generic 2018-08-15 06:18:42,818 INFO Packages that are kept back: ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: unattended-upgrades 1.1ubuntu1.18.04.5 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 16 13:17:30 2018 InstallationDate: Installed on 2018-07-24 (23 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180724) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1787460/+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 1787297] Re: Clock : incorrect date format in FR in Unity panel …bionic.
@kikito you're not under Unity neither under Bionic 18.04 ;-) But it seems your clock is also à l'Anglaise… -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1787297 Title: Clock : incorrect date format in FR in Unity panel …bionic. Status in indicator-datetime package in Ubuntu: Confirmed Status in unity package in Ubuntu: Invalid Bug description: Hi, Here is Ubuntu 18.04 with Unity session ( I know… ) System language and regional settings are set to French. In regional setting the date reads day number month year hour minute… which is correct for French. But the clock in the Unity panel reads day month number year hour minute… which looks more English than French order. Any config file I might edit to make my clock « more French » ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1787297/+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 1787297] Re: Clock : incorrect date format in FR in Unity panel …bionic.
Thank you Khurshid Alam that's exactly what I was looking for ! That does not fix the default clock non-matching the locale clock settings but it allows to have a customized clock. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1787297 Title: Clock : incorrect date format in FR in Unity panel …bionic. Status in indicator-datetime package in Ubuntu: Confirmed Status in unity package in Ubuntu: Invalid Bug description: Hi, Here is Ubuntu 18.04 with Unity session ( I know… ) System language and regional settings are set to French. In regional setting the date reads day number month year hour minute… which is correct for French. But the clock in the Unity panel reads day month number year hour minute… which looks more English than French order. Any config file I might edit to make my clock « more French » ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1787297/+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 1760818] Re: gedit and gnome-calculator transparency/graphics corruption issue
I experienced this bug today. Restart didn't help initially. Then I changed the Input Method from xim to ibus and the problem was gone. Changing back to xim did not bring the problem back. I'm confused that it worked. Would be nice if somebody else could try the same. I did not install any new packages, neither did I re-install any packages. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1760818 Title: gedit and gnome-calculator transparency/graphics corruption issue Status in im-config package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: Invalid Bug description: In a "Ubuntu" (Xorg) session on 18.04 gedit and gnome-calculator suffer from a graphics issue where parts of their windows hold parts of wallpaper or other windows' contents as background. See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: light-themes 16.10+18.04.20180328-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 3 09:12:31 2018 PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: Upgraded to bionic on 2018-02-07 (54 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1760818/+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 1787396] Re: ss crashes when using --no-header
This is fixed in Debian since 4.16.0-4 at least. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1787396 Title: ss crashes when using --no-header Status in iproute2 package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1) Listen on port 8989: $ nc -l 8989 & 2) Check that ss can list this listener: $ ss --no-header -nto state listening 'sport = 8989' 010.0.0.0:8989 0.0.0.0:* 3) Ask ss to list listeners on a port where nothing listens $ kill %1 # stops nc $ ss --no-header -nto state listening 'sport = 8989' Segmentation fault (core dumped) In the above, removing "--no-header" avoids the segfault. Additional information: $ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 $ apt-cache policy iproute2 iproute2: Installed: 4.15.0-2ubuntu1 Candidate: 4.15.0-2ubuntu1 Version table: *** 4.15.0-2ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: iproute2 4.15.0-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 16 08:17:52 2018 InstallationDate: Installed on 2018-07-15 (32 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180714) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: iproute2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1787396/+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 1787297] Re: Clock : incorrect date format in FR in Unity panel …bionic.
coeurnoir-1804@ASGARD:~$ locale LANG=fr_FR.UTF-8 LANGUAGE=fr_FR:fr_CA:en LC_CTYPE="fr_FR.UTF-8" LC_NUMERIC=fr_FR.UTF-8 LC_TIME=fr_FR.UTF-8 LC_COLLATE="fr_FR.UTF-8" LC_MONETARY=fr_FR.UTF-8 LC_MESSAGES="fr_FR.UTF-8" LC_PAPER=fr_FR.UTF-8 LC_NAME=fr_FR.UTF-8 LC_ADDRESS=fr_FR.UTF-8 LC_TELEPHONE=fr_FR.UTF-8 LC_MEASUREMENT=fr_FR.UTF-8 LC_IDENTIFICATION=fr_FR.UTF-8 LC_ALL= coeurnoir-1804@ASGARD:~$ ** Attachment added: "Illustration of difference between clock format vs clock displayed" https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1787297/+attachment/5176517/+files/clock_format_and_displayed.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1787297 Title: Clock : incorrect date format in FR in Unity panel …bionic. Status in indicator-datetime package in Ubuntu: Confirmed Status in unity package in Ubuntu: Invalid Bug description: Hi, Here is Ubuntu 18.04 with Unity session ( I know… ) System language and regional settings are set to French. In regional setting the date reads day number month year hour minute… which is correct for French. But the clock in the Unity panel reads day month number year hour minute… which looks more English than French order. Any config file I might edit to make my clock « more French » ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1787297/+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 1787474] Re: pygobject fails to build in Ubuntu 18.10
Oh maybe this is just incompatibility with the new glib. There was a new
pygobject release today.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pygobject in Ubuntu.
https://bugs.launchpad.net/bugs/1787474
Title:
pygobject fails to build in Ubuntu 18.10
Status in pygobject package in Ubuntu:
New
Bug description:
pygobject 3.28.2-1 and 3.29.2-1 fails to build in Ubuntu 18.10.
pygobject 3.28.2-1 does build successfully on Ubuntu 18.04 LTS.
3.29.2-1 does build successfully in Debian unstable.
I confirmed that the problem is reproducible in a local sbuild. I
confirm that the test hang also happens with python 3.7.
By the way, I had to manually cancel the builds since they were still
hanging after 20 hours.
Build log
-
https://launchpad.net/ubuntu/+source/pygobject/3.29.2-1/+build/15263898
Build log excerpt
-
I: pybuild base:217: cd /<>/.pybuild/cpython2_2.7/build;
python2.7 -m pytest tests
= test session starts
==
platform linux2 -- Python 2.7.15, pytest-3.6.4, py-1.5.4, pluggy-0.6.0
rootdir: /<>, inifile:
collected 1374 items
tests/test_atoms.py ... [
0%]
tests/test_cairo.py .[
2%]
tests/test_docstring.py ...x.[
3%]
tests/test_error.py ... [
4%]
tests/test_everything.py Trace/breakpoint trap (core dumped)
E: pybuild pybuild:338: test: plugin distutils failed with: exit code=133: cd
/<>/.pybuild/cpython2_2.7/build; python2.7 -m pytest tests
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7 returned
exit code 13
make[1]: *** [debian/rules:29: override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:22: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status
2
RUN: /usr/share/launchpad-buildd/slavebin/in-target scan-for-processes
--backend=chroot --series=cosmic --arch=amd64 PACKAGEBUILD-15263898
Scanning for processes to kill in build PACKAGEBUILD-15263898
Build killed with signal TERM after 150 minutes of inactivity
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/1787474/+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 1787480] Re: bugpattern checking not working for a ubiquity bug report
11:19 < bdmurray> psusi: How could I recreate the bug? It might be best to test it in a live cd environment. 12:38 < psusi> bdmurray: take an existing hard disk with at least one partition on it but no ESP, boot the installer in UEFI mode and it will crash when it tries to install grub 13:08 < psusi> bdmurray: ohh, and don't do the auto use whole disk install or it will make an esp... manual partitioning, and don't make an ESP -- 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/1787480 Title: bugpattern checking not working for a ubiquity bug report Status in apport package in Ubuntu: Confirmed Bug description: Phillip Susi wrote a bug pattern for ubiquity / grub-installer at https://bazaar.launchpad.net/~ubuntu-bugcontrol/apport/ubuntu- bugpatterns/revision/584. While the bug pattern works, tested with test-local and search-bugs from that branch new bug reports are still appearing in Launchpad. I confirmed that the pattern exists in https://people.canonical.com /~ubuntu-archive/bugpatterns/bugpatterns.xml and that using that url instead of a local file in test-local works. So it seems to be something with apport's ui.py or report.py when the bug report is being filed. The best way to test this would be a Live CD where the bug will actually occur. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1787480/+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 1787480] Re: bugpattern checking not working for a ubiquity bug report
It's unknown whether this affects bug pattern checking from all systems or just those running Live CDs. -- 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/1787480 Title: bugpattern checking not working for a ubiquity bug report Status in apport package in Ubuntu: Confirmed Bug description: Phillip Susi wrote a bug pattern for ubiquity / grub-installer at https://bazaar.launchpad.net/~ubuntu-bugcontrol/apport/ubuntu- bugpatterns/revision/584. While the bug pattern works, tested with test-local and search-bugs from that branch new bug reports are still appearing in Launchpad. I confirmed that the pattern exists in https://people.canonical.com /~ubuntu-archive/bugpatterns/bugpatterns.xml and that using that url instead of a local file in test-local works. So it seems to be something with apport's ui.py or report.py when the bug report is being filed. The best way to test this would be a Live CD where the bug will actually occur. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1787480/+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 1787480] [NEW] bugpattern checking not working for a ubiquity bug report
Public bug reported: Phillip Susi wrote a bug pattern for ubiquity / grub-installer at https://bazaar.launchpad.net/~ubuntu-bugcontrol/apport/ubuntu- bugpatterns/revision/584. While the bug pattern works, tested with test- local and search-bugs from that branch new bug reports are still appearing in Launchpad. I confirmed that the pattern exists in https://people.canonical.com /~ubuntu-archive/bugpatterns/bugpatterns.xml and that using that url instead of a local file in test-local works. So it seems to be something with apport's ui.py or report.py when the bug report is being filed. The best way to test this would be a Live CD where the bug will actually occur. ** Affects: apport (Ubuntu) Importance: High Status: Confirmed ** Changed in: apport (Ubuntu) Status: New => Confirmed ** Changed in: apport (Ubuntu) Importance: Undecided => High -- 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/1787480 Title: bugpattern checking not working for a ubiquity bug report Status in apport package in Ubuntu: Confirmed Bug description: Phillip Susi wrote a bug pattern for ubiquity / grub-installer at https://bazaar.launchpad.net/~ubuntu-bugcontrol/apport/ubuntu- bugpatterns/revision/584. While the bug pattern works, tested with test-local and search-bugs from that branch new bug reports are still appearing in Launchpad. I confirmed that the pattern exists in https://people.canonical.com /~ubuntu-archive/bugpatterns/bugpatterns.xml and that using that url instead of a local file in test-local works. So it seems to be something with apport's ui.py or report.py when the bug report is being filed. The best way to test this would be a Live CD where the bug will actually occur. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1787480/+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 1489154] Re: NetworkManager does not start / fails to start
This is a bug for me. I used my wifi just today and after shutting down my laptop and turning it on again I get all of this. no wifi and same errors. I use xenial so the versions are different. I have network manager 1.2.6-0ubuntu0.16.04.2. -- 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/1489154 Title: NetworkManager does not start / fails to start Status in One Hundred Papercuts: Incomplete Status in network-manager package in Ubuntu: Confirmed Bug description: Yesterday i did the upgrade to version 1.0.4 of NetworkManger. Today my Xubuntu 15.10 cannot connect to the net, and wants to upload a crash report. This also fails cause the start of the NetworkManger fails after booting. Trying manually to start with ~$ sudo systemctl start NetworkManager leads that the icon comes up, disappears, comes up, disappears for 3, 4 times and then it's gone forever. ~$ journalctl -xe Aug 26 22:02:34 Wily NetworkManager[1578]: monitoring ifupdown state file '/run/network/ifstate'. Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMVxlanFactory (internal) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMVlanFactory (internal) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMVethFactory (internal) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMTunFactory (internal) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMMacvlanFactory (internal) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMInfinibandFactory (internal) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMGreFactory (internal) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMEthernetFactory (internal) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMBridgeFactory (internal) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMBondFactory (internal) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMAtmManager (/usr/lib/i386-linux-gnu/NetworkManager/libnm-device-plugin-adsl.so) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMWifiFactory (/usr/lib/i386-linux-gnu/NetworkManager/libnm-device-plugin-wifi.so) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMBluezManager (/usr/lib/i386-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMWwanFactory (/usr/lib/i386-linux-gnu/NetworkManager/libnm-device-plugin-wwan.so) Aug 26 22:02:34 Wily NetworkManager[1578]: WiFi enabled by radio killswitch; enabled by state file Aug 26 22:02:34 Wily NetworkManager[1578]: WWAN enabled by radio killswitch; enabled by state file Aug 26 22:02:34 Wily NetworkManager[1578]: WiMAX enabled by radio killswitch; enabled by state file Aug 26 22:02:34 Wily NetworkManager[1578]: Networking is enabled by state file Aug 26 22:02:34 Wily NetworkManager[1578]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed Aug 26 22:02:34 Wily NetworkManager[1578]: (lo): link connected Aug 26 22:02:34 Wily NetworkManager[1578]: (lo): new Generic device (carrier: ON, driver: 'unknown', ifindex: 1) Aug 26 22:02:34 Wily NetworkManager[1578]: (enp0s3): link connected Aug 26 22:02:34 Wily NetworkManager[1578]: (enp0s3): new Ethernet device (carrier: ON, driver: 'e1000', ifindex: 2) Aug 26 22:02:34 Wily NetworkManager[1578]: (enp0s3): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] Aug 26 22:02:34 Wily NetworkManager[1578]: keyfile: add connection in-memory (4251ae7f-22a1-4de8-8f11-7a62fd420d65,"Kabelnetzwerkverbindung 1") Aug 26 22:02:34 Wily NetworkManager[1578]: (enp0s3): created default wired connection 'Kabelnetzwerkverbindung 1' Aug 26 22:02:34 Wily NetworkManager[1578]: urfkill disappeared from the bus Aug 26 22:02:34 Wily NetworkManager[1578]: wpa_supplicant running Aug 26 22:02:34 Wily NetworkManager[1578]: ModemManager available in the bus Aug 26 22:02:34 Wily NetworkManager[1578]: ofono is now available Aug 26 22:02:34 Wily NetworkManager[1578]: (NetworkManager:1578): GLib-GObject-WARNING **: /build/glib2.0-6GfMH1/glib2.0-2.45.4/./gobject/gsignal.c:2480: signal 'ModemAdded' is invalid for instance Aug 26 22:02:34 Wily NetworkManager[1578]: (NetworkManager:1578): GLib-GObject-WARNING **: /build/glib2.0-6GfMH1/glib2.0-2.45.4/./gobject/gsignal.c:2480: signal 'ModemRemoved' is invalid for instan Aug 26 22:02:34 Wily NetworkManager[1578]: (NetworkManager:1578): GLib-CRITICAL **: g_variant_get_va: assertion 'value != NULL' failed Aug 26 22:02:34 Wily kernel: NetworkManager[1578]: segfault at c ip b6f4b97a sp bffb4890 error 4 in
[Touch-packages] [Bug 1738630] Re: [improvement] xkb configuration cannot be extended without rebuilding xkb-data package
** Changed in: xkeyboard-config (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1738630 Title: [improvement] xkb configuration cannot be extended without rebuilding xkb-data package Status in xkeyboard-config package in Ubuntu: Confirmed Bug description: Currently, the only way to specify xkb settings in a fully compatible way that behaves well with Gnome is through using xkb rules. However, rules are not user-editable (NOBODY should have to manually edit ANYTHING under /usr/share on a system with an automatic package upgrade system) and xkb has no hook for adding rules. Heck, rules/evdev even has a big message on top saying that it shouldn't be edited. This is an extremely big problem in my opinion. Both local configuration beyond what's supported, and creating redistributable keyboard layouts and options is extremely complex and ugly. As a minimum, I'd like to be able to package up a 3rd party keyboard layout, geometry, or option as a deb file that contains the symbols, and a rules/evdev.part file, and be able to rebuild rules/evdev, evdev.lst and evdev.xml from .part's on a live system using dpkg- reconfigure... Ideally however, an end user should be able to just drop an appropriate rules fragment file under /etc/X11/xkb/rules, and have it automatically parsed on startup. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1738630/+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 1738630] Re: [improvement] xkb configuration cannot be extended without rebuilding xkb-data package
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xkeyboard-config (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1738630 Title: [improvement] xkb configuration cannot be extended without rebuilding xkb-data package Status in xkeyboard-config package in Ubuntu: Confirmed Bug description: Currently, the only way to specify xkb settings in a fully compatible way that behaves well with Gnome is through using xkb rules. However, rules are not user-editable (NOBODY should have to manually edit ANYTHING under /usr/share on a system with an automatic package upgrade system) and xkb has no hook for adding rules. Heck, rules/evdev even has a big message on top saying that it shouldn't be edited. This is an extremely big problem in my opinion. Both local configuration beyond what's supported, and creating redistributable keyboard layouts and options is extremely complex and ugly. As a minimum, I'd like to be able to package up a 3rd party keyboard layout, geometry, or option as a deb file that contains the symbols, and a rules/evdev.part file, and be able to rebuild rules/evdev, evdev.lst and evdev.xml from .part's on a live system using dpkg- reconfigure... Ideally however, an end user should be able to just drop an appropriate rules fragment file under /etc/X11/xkb/rules, and have it automatically parsed on startup. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1738630/+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 1787460] Re: Unattended upgrades removed linux-image-generic
Looking at .var.apt.history.log.txt we can see that in a previous package operation linux-generic was removed. Start-Date: 2018-08-14 13:37:10 Commandline: apt dist-upgrade Install: linux-headers-4.15.0-32-generic:amd64 (4.15.0-32.35, automatic), linux-headers-4.15.0-32:amd64 (4.15.0-32.35, automatic) Upgrade: linux-headers-generic:amd64 (4.15.0.31.33, 4.15.0.32.34), linux-libc-dev:amd64 (4.15.0-31.33, 4.15.0-32.35) Remove: linux-signed-generic:amd64 (4.15.0.31.33), linux-generic:amd64 (4.15.0.31.33) End-Date: 2018-08-14 13:37:16 Subsequently during the unattended-upgrades run linux-image-generic is identified as an unused package. I'm only able to recreate this if I first remove the linux-generic package e.g.: bdmurray@clean-bionic-amd64:~$ sudo apt remove linux-generic [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: amd64-microcode intel-microcode iucode-tool linux-headers-generic linux-image-generic thermald Use 'sudo apt autoremove' to remove them. The following packages will be REMOVED: linux-generic 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. After this operation, 15.4 kB disk space will be freed. Do you want to continue? [Y/n] Y (Reading database ... 165999 files and directories currently installed.) Removing linux-generic (4.15.0.30.32) ... bdmurray@clean-bionic-amd64:~$ sudo unattended-upgrades -v Initial blacklisted packages: Initial whitelisted packages: Starting unattended upgrades script Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic Removing unused kernel packages: linux-headers-generic linux-image-generic (Reading database ... 165996 files and directories currently installed.) Removing linux-headers-generic (4.15.0.30.32) ... (Reading database ... 165993 files and directories currently installed.) Removing linux-image-generic (4.15.0.30.32) ... Packages that were successfully auto-removed: linux-headers-generic linux-image-generic Packages that are kept back: No packages found that can be upgraded unattended and no pending auto-removals -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1787460 Title: Unattended upgrades removed linux-image-generic Status in unattended-upgrades package in Ubuntu: New Bug description: On a fairly fresh install of 18.04 with no modifications whatsoever to the unattended-upgrades configuration, it decided to remove linux- image-generic which also removed linux-modules-extra which caused sound drivers to disappear, etc. The relative snippet from /var/log/unattended-upgrades/unattended- upgrades.log is: 2018-08-15 06:18:00,048 INFO Starting unattended upgrades script 2018-08-15 06:18:00,048 INFO Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic 2018-08-15 06:18:01,552 INFO Removing unused kernel packages: linux-headers-generic linux-image-generic linux-headers-4.15.0-32-generic linux-headers-4.15.0-32 2018-08-15 06:18:01,588 WARNING Keeping auto-removable linux-headers-generic package(s) because it would also remove the following packages which should be kept in this step: libxml2 linux-image-4.15.0-32-generic linux-modules-4.15.0-32-generic linux-modules-extra-4.15.0-32-generic 2018-08-15 06:18:09,476 INFO Packages that were successfully auto-removed: linux-headers-4.15.0-32 linux-headers-4.15.0-32-generic linux-headers-generic linux-image-generic 2018-08-15 06:18:09,477 INFO Packages that are kept back: linux-headers-generic 2018-08-15 06:18:10,300 INFO Packages that will be upgraded: libxml2 linux-image-generic 2018-08-15 06:18:10,300 INFO Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log 2018-08-15 06:18:39,238 INFO All upgrades installed 2018-08-15 06:18:42,818 INFO Packages that were successfully auto-removed: linux-image-generic linux-modules-extra-4.15.0-32-generic 2018-08-15 06:18:42,818 INFO Packages that are kept back: ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: unattended-upgrades 1.1ubuntu1.18.04.5 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 16 13:17:30 2018 InstallationDate: Installed on 2018-07-24 (23 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180724) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) To
[Touch-packages] [Bug 1787456] Re: Locally modified keyboard layouts overwritten on update without asking the user
*** This bug is a duplicate of bug 1738630 *** https://bugs.launchpad.net/bugs/1738630 ** This bug has been marked a duplicate of bug 1738630 [improvement] xkb configuration cannot be extended without rebuilding xkb-data package -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1787456 Title: Locally modified keyboard layouts overwritten on update without asking the user Status in xkeyboard-config package in Ubuntu: New Bug description: Locally modified keyboard layouts are overwritten on package upgrades (in my case from 16.04 to 18.04) without asking if the user wants to keep the local version or install the maintainers version. This leads to problems and extra work for the system administrator. The correct solution would be (in my opinion at least) to do the same checks for files in /usr/share/X11/xkb/* as is done for (most) config files in /etc. E.g. check the file against the currently installed package before upgrading, if it differs, ask the user what to do. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xkb-data 2.23.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: CurrentDesktop: XFCE Date: Thu Aug 16 19:57:02 2018 Dependencies: DistUpgraded: 2018-08-16 14:12:51,407 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=UUID=4f184485-213c-4467-b6d1-3bf9fa0c69c8 ro SourcePackage: xkeyboard-config UpgradeStatus: Upgraded to bionic on 2018-08-16 (0 days ago) dmi.bios.date: 02/13/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.70 dmi.board.name: X79 Extreme4 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.:bvrP3.70:bd02/13/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX79Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.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 N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1787456/+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 1787474] [NEW] pygobject fails to build in Ubuntu 18.10
Public bug reported:
pygobject 3.28.2-1 and 3.29.2-1 fails to build in Ubuntu 18.10.
pygobject 3.28.2-1 does build successfully on Ubuntu 18.04 LTS. 3.29.2-1
does build successfully in Debian unstable.
I confirmed that the problem is reproducible in a local sbuild. I
confirm that the test hang also happens with python 3.7.
By the way, I had to manually cancel the builds since they were still
hanging after 20 hours.
Build log
-
https://launchpad.net/ubuntu/+source/pygobject/3.29.2-1/+build/15263898
Build log excerpt
-
I: pybuild base:217: cd /<>/.pybuild/cpython2_2.7/build; python2.7
-m pytest tests
= test session starts ==
platform linux2 -- Python 2.7.15, pytest-3.6.4, py-1.5.4, pluggy-0.6.0
rootdir: /<>, inifile:
collected 1374 items
tests/test_atoms.py ... [ 0%]
tests/test_cairo.py .[ 2%]
tests/test_docstring.py ...x.[ 3%]
tests/test_error.py ... [ 4%]
tests/test_everything.py Trace/breakpoint trap (core dumped)
E: pybuild pybuild:338: test: plugin distutils failed with: exit code=133: cd
/<>/.pybuild/cpython2_2.7/build; python2.7 -m pytest tests
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7 returned
exit code 13
make[1]: *** [debian/rules:29: override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:22: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
RUN: /usr/share/launchpad-buildd/slavebin/in-target scan-for-processes
--backend=chroot --series=cosmic --arch=amd64 PACKAGEBUILD-15263898
Scanning for processes to kill in build PACKAGEBUILD-15263898
Build killed with signal TERM after 150 minutes of inactivity
** Affects: pygobject (Ubuntu)
Importance: Undecided
Status: New
** Tags: cosmic ftbfs
** Description changed:
pygobject 3.28.2-1 and 3.29.2-1 fails to build in Ubuntu 18.10.
pygobject 3.28.2-1 does build successfully on Ubuntu 18.04 LTS. 3.29.2-1
does build successfully in Debian unstable.
I confirmed that the problem is reproducible in a local sbuild. I
confirm that the test hang also happens with python 3.7.
By the way, I had to manually cancel the builds since they were still
hanging after 20 hours.
+ Build log
+ -
+ https://launchpad.net/ubuntu/+source/pygobject/3.29.2-1/+build/15263898
+
Build log excerpt
-
-
I: pybuild base:217: cd /<>/.pybuild/cpython2_2.7/build;
python2.7 -m pytest tests
= test session starts
==
platform linux2 -- Python 2.7.15, pytest-3.6.4, py-1.5.4, pluggy-0.6.0
rootdir: /<>, inifile:
collected 1374 items
tests/test_atoms.py ... [
0%]
tests/test_cairo.py .[
2%]
tests/test_docstring.py ...x.[
3%]
tests/test_error.py ... [
4%]
tests/test_everything.py Trace/breakpoint trap (core dumped)
E: pybuild pybuild:338: test: plugin distutils failed with: exit code=133: cd
/<>/.pybuild/cpython2_2.7/build; python2.7 -m pytest tests
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7 returned
exit code 13
make[1]: *** [debian/rules:29: override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:22: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status
2
RUN: /usr/share/launchpad-buildd/slavebin/in-target scan-for-processes
--backend=chroot --series=cosmic --arch=amd64 PACKAGEBUILD-15263898
Scanning for processes to kill in build PACKAGEBUILD-15263898
Build killed with signal TERM after 150 minutes of inactivity
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pygobject in Ubuntu.
https://bugs.launchpad.net/bugs/1787474
Title:
pygobject fails to build in Ubuntu 18.10
Status in pygobject package in Ubuntu:
New
Bug description:
pygobject 3.28.2-1 and 3.29.2-1 fails to build in Ubuntu 18.10.
pygobject 3.28.2-1 does build successfully on Ubuntu 18.04 LTS.
3.29.2-1 does build successfully in Debian unstable.
I confirmed that the problem is reproducible in a local sbuild. I
confirm that the test hang also happens with python 3.7.
By the way, I had to manually cancel the builds since they were still
hanging after 20 hours.
Build log
-
https://launchpad.net/ubuntu/+source/pygobject/3.29.2-1/+build/15263898
Build log excerpt
-
I: pybuild base:217: cd /<>/.pybuild/cpython2_2.7/build;
python2.7 -m pytest tests
[Touch-packages] [Bug 1787460] Re: Unattended upgrades removed linux-image-generic
** Changed in: unattended-upgrades (Ubuntu) Importance: High => Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1787460 Title: Unattended upgrades removed linux-image-generic Status in unattended-upgrades package in Ubuntu: New Bug description: On a fairly fresh install of 18.04 with no modifications whatsoever to the unattended-upgrades configuration, it decided to remove linux- image-generic which also removed linux-modules-extra which caused sound drivers to disappear, etc. The relative snippet from /var/log/unattended-upgrades/unattended- upgrades.log is: 2018-08-15 06:18:00,048 INFO Starting unattended upgrades script 2018-08-15 06:18:00,048 INFO Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic 2018-08-15 06:18:01,552 INFO Removing unused kernel packages: linux-headers-generic linux-image-generic linux-headers-4.15.0-32-generic linux-headers-4.15.0-32 2018-08-15 06:18:01,588 WARNING Keeping auto-removable linux-headers-generic package(s) because it would also remove the following packages which should be kept in this step: libxml2 linux-image-4.15.0-32-generic linux-modules-4.15.0-32-generic linux-modules-extra-4.15.0-32-generic 2018-08-15 06:18:09,476 INFO Packages that were successfully auto-removed: linux-headers-4.15.0-32 linux-headers-4.15.0-32-generic linux-headers-generic linux-image-generic 2018-08-15 06:18:09,477 INFO Packages that are kept back: linux-headers-generic 2018-08-15 06:18:10,300 INFO Packages that will be upgraded: libxml2 linux-image-generic 2018-08-15 06:18:10,300 INFO Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log 2018-08-15 06:18:39,238 INFO All upgrades installed 2018-08-15 06:18:42,818 INFO Packages that were successfully auto-removed: linux-image-generic linux-modules-extra-4.15.0-32-generic 2018-08-15 06:18:42,818 INFO Packages that are kept back: ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: unattended-upgrades 1.1ubuntu1.18.04.5 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 16 13:17:30 2018 InstallationDate: Installed on 2018-07-24 (23 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180724) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1787460/+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 1676547] Re: No network connectivity (NIC unmanaged) after upgrade
On Thu, Aug 16, 2018 at 04:45:21PM -, Shahar Or wrote: > Brian, I did something similar to what you just described and got hit by > that. Is that a different issue? Yes, the original bug report here was about upgrading Ubuntu desktop systems. -- Brian Murray -- 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/1676547 Title: No network connectivity (NIC unmanaged) after upgrade Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Yakkety: Fix Released Status in network-manager source package in Zesty: Fix Released Bug description: Impact -- When upgrading from Xenial (with all updates installed) to Yakkety/Zesty you will boot to a system without networking - sad! Test Case - 1) Boot a xenial desktop system 2) Ensure network-manager version 1.2.6-0ubuntu0.16.04.1 from -updates is installed 3) Upgrade to yakkety or zesty 3.5) Enable -proposed and download the new version of n-m "apt-get download network-manager" 4) Reboot 5) Observe you have no network If you install the version of network-manager from yakkety-proposed and then reboot you should have a network connection. 1) Boot a xenial desktop system. 2) ensure network-manager version 1.2.6-0ubuntu0.16.04.1 from -updates is installed. 3) Install nplan, configure to set up static network on an ethernet device using nplan. 4) Upgrade to yakkety or zesty 5) Reboot 6) Observe that your system is still being managed by networkd rather than NetworkManager. Regression Potential Any failure to manage ethernet or wireless devices after upgrade, or issues with the use of netplan in conjunction with NetworkManager should be investigated as potential regressions. For example, if after upgrading, ethernet devices are no longer managed, or if devices that should be explicitly ignored by NetworkManager due to existing user configuration are now managed, these would indicate a possible regression caused by this update. Original Description nplan was installed during the upgrade process but I had no network connectivity after upgrading. Apparently, no package wanted to manage my ethernet connection. ProblemType: BugDistroRelease: Ubuntu 16.10 Package: ubuntu-release-upgrader-core 1:16.10.10 ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17 Uname: Linux 4.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Mon Mar 27 11:34:04 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2013-01-16 (1531 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116) PackageArchitecture: allSourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to yakkety on 2017-03-17 (10 days ago) VarLogDistupgradeTermlog: modified.conffile..etc.update-manager.meta-release: [modified] mtime.conffile..etc.update-manager.meta-release: 2013-10-08T06:39:09.818913 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1676547/+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 1787460] [NEW] Unattended upgrades removed linux-image-generic
Public bug reported: On a fairly fresh install of 18.04 with no modifications whatsoever to the unattended-upgrades configuration, it decided to remove linux-image- generic which also removed linux-modules-extra which caused sound drivers to disappear, etc. The relative snippet from /var/log/unattended-upgrades/unattended- upgrades.log is: 2018-08-15 06:18:00,048 INFO Starting unattended upgrades script 2018-08-15 06:18:00,048 INFO Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic 2018-08-15 06:18:01,552 INFO Removing unused kernel packages: linux-headers-generic linux-image-generic linux-headers-4.15.0-32-generic linux-headers-4.15.0-32 2018-08-15 06:18:01,588 WARNING Keeping auto-removable linux-headers-generic package(s) because it would also remove the following packages which should be kept in this step: libxml2 linux-image-4.15.0-32-generic linux-modules-4.15.0-32-generic linux-modules-extra-4.15.0-32-generic 2018-08-15 06:18:09,476 INFO Packages that were successfully auto-removed: linux-headers-4.15.0-32 linux-headers-4.15.0-32-generic linux-headers-generic linux-image-generic 2018-08-15 06:18:09,477 INFO Packages that are kept back: linux-headers-generic 2018-08-15 06:18:10,300 INFO Packages that will be upgraded: libxml2 linux-image-generic 2018-08-15 06:18:10,300 INFO Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log 2018-08-15 06:18:39,238 INFO All upgrades installed 2018-08-15 06:18:42,818 INFO Packages that were successfully auto-removed: linux-image-generic linux-modules-extra-4.15.0-32-generic 2018-08-15 06:18:42,818 INFO Packages that are kept back: ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: unattended-upgrades 1.1ubuntu1.18.04.5 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 16 13:17:30 2018 InstallationDate: Installed on 2018-07-24 (23 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180724) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unattended-upgrades (Ubuntu) Importance: High Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1787460 Title: Unattended upgrades removed linux-image-generic Status in unattended-upgrades package in Ubuntu: New Bug description: On a fairly fresh install of 18.04 with no modifications whatsoever to the unattended-upgrades configuration, it decided to remove linux- image-generic which also removed linux-modules-extra which caused sound drivers to disappear, etc. The relative snippet from /var/log/unattended-upgrades/unattended- upgrades.log is: 2018-08-15 06:18:00,048 INFO Starting unattended upgrades script 2018-08-15 06:18:00,048 INFO Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic 2018-08-15 06:18:01,552 INFO Removing unused kernel packages: linux-headers-generic linux-image-generic linux-headers-4.15.0-32-generic linux-headers-4.15.0-32 2018-08-15 06:18:01,588 WARNING Keeping auto-removable linux-headers-generic package(s) because it would also remove the following packages which should be kept in this step: libxml2 linux-image-4.15.0-32-generic linux-modules-4.15.0-32-generic linux-modules-extra-4.15.0-32-generic 2018-08-15 06:18:09,476 INFO Packages that were successfully auto-removed: linux-headers-4.15.0-32 linux-headers-4.15.0-32-generic linux-headers-generic linux-image-generic 2018-08-15 06:18:09,477 INFO Packages that are kept back: linux-headers-generic 2018-08-15 06:18:10,300 INFO Packages that will be upgraded: libxml2 linux-image-generic 2018-08-15 06:18:10,300 INFO Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log 2018-08-15 06:18:39,238 INFO All upgrades installed 2018-08-15 06:18:42,818 INFO Packages that were successfully auto-removed: linux-image-generic linux-modules-extra-4.15.0-32-generic 2018-08-15 06:18:42,818 INFO Packages that are kept back: ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: unattended-upgrades 1.1ubuntu1.18.04.5 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 16 13:17:30 2018 InstallationDate: Installed on 2018-07-24 (23 days ago) InstallationMedia: Ubuntu
[Touch-packages] [Bug 1787456] [NEW] Locally modified keyboard layouts overwritten on update without asking the user
Public bug reported: Locally modified keyboard layouts are overwritten on package upgrades (in my case from 16.04 to 18.04) without asking if the user wants to keep the local version or install the maintainers version. This leads to problems and extra work for the system administrator. The correct solution would be (in my opinion at least) to do the same checks for files in /usr/share/X11/xkb/* as is done for (most) config files in /etc. E.g. check the file against the currently installed package before upgrading, if it differs, ask the user what to do. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xkb-data 2.23.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: CurrentDesktop: XFCE Date: Thu Aug 16 19:57:02 2018 Dependencies: DistUpgraded: 2018-08-16 14:12:51,407 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=UUID=4f184485-213c-4467-b6d1-3bf9fa0c69c8 ro SourcePackage: xkeyboard-config UpgradeStatus: Upgraded to bionic on 2018-08-16 (0 days ago) dmi.bios.date: 02/13/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.70 dmi.board.name: X79 Extreme4 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.:bvrP3.70:bd02/13/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX79Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.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 N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xkeyboard-config (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1787456 Title: Locally modified keyboard layouts overwritten on update without asking the user Status in xkeyboard-config package in Ubuntu: New Bug description: Locally modified keyboard layouts are overwritten on package upgrades (in my case from 16.04 to 18.04) without asking if the user wants to keep the local version or install the maintainers version. This leads to problems and extra work for the system administrator. The correct solution would be (in my opinion at least) to do the same checks for files in /usr/share/X11/xkb/* as is done for (most) config files in /etc. E.g. check the file against the currently installed package before upgrading, if it differs, ask the user what to do. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xkb-data 2.23.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: CurrentDesktop: XFCE Date: Thu Aug 16 19:57:02 2018 Dependencies: DistUpgraded: 2018-08-16 14:12:51,407 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=UUID=4f184485-213c-4467-b6d1-3bf9fa0c69c8 ro SourcePackage: xkeyboard-config UpgradeStatus: Upgraded to bionic on 2018-08-16 (0 days ago) dmi.bios.date: 02/13/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.70 dmi.board.name: X79 Extreme4 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:
[Touch-packages] [Bug 1787396] Re: ss crashes when using --no-header
** Tags added: cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1787396 Title: ss crashes when using --no-header Status in iproute2 package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1) Listen on port 8989: $ nc -l 8989 & 2) Check that ss can list this listener: $ ss --no-header -nto state listening 'sport = 8989' 010.0.0.0:8989 0.0.0.0:* 3) Ask ss to list listeners on a port where nothing listens $ kill %1 # stops nc $ ss --no-header -nto state listening 'sport = 8989' Segmentation fault (core dumped) In the above, removing "--no-header" avoids the segfault. Additional information: $ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 $ apt-cache policy iproute2 iproute2: Installed: 4.15.0-2ubuntu1 Candidate: 4.15.0-2ubuntu1 Version table: *** 4.15.0-2ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: iproute2 4.15.0-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 16 08:17:52 2018 InstallationDate: Installed on 2018-07-15 (32 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180714) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: iproute2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1787396/+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 1769386] Re: Cable network does not get recognized anymore, wifi works
FIX Updates 16.04.5 @ 16/8/18 made the realtek chipset work again kernel 4.15 ** Changed in: network-manager (Ubuntu) Status: Confirmed => Fix Released -- 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/1769386 Title: Cable network does not get recognized anymore, wifi works Status in network-manager package in Ubuntu: Fix Released Status in Arch Linux: New Bug description: ubuntu 16.04 LTS cable does not connect anymore, wifi working ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 CurrentDesktop: Unity Date: Sat May 5 19:27:18 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-09-30 (217 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IpRoute: default via 192.168.1.1 dev wlp3s0 proto static metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.2 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICETYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlp3s0wifi connected /org/freedesktop/NetworkManager/Devices/1 WiFi-2.4-3569 7103236e-31c4-43d6-871d-14f3cda4b657 /org/freedesktop/NetworkManager/ActiveConnection/1 enp2s0f1 ethernet disconnected /org/freedesktop/NetworkManager/Devices/2 -- ---- loloopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1769386/+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 1773859] Re: upgrades to 18.04 fail
I have tried with mine: bug #1787367. Okay, the usual update / upgrade runs through now, though what got was just the removal of the systemd-shim, and nothing else. feh and flowblade have been kept back. OpenOffice 6.0 (just as example) remains uninstalled. How can I know what else remains missing? The awk command lists a dozen of rather irrelevant stuff. Thanks anyway for the trick to remove the systemd-shim blocker! -- 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/1773859 Title: upgrades to 18.04 fail Status in systemd package in Ubuntu: Confirmed Status in systemd-shim package in Ubuntu: Incomplete Status in systemd source package in Bionic: Confirmed Status in systemd-shim source package in Bionic: Confirmed Bug description: $ sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be REMOVED: systemd-shim 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 71.7 kB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 63 files and directories currently installed.) Removing systemd-shim (9-1bzr4ubuntu1) ... Removing 'diversion of /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by systemd-shim' dpkg-divert: error: rename involves overwriting '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with different file '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', not allowed dpkg: error processing package systemd-shim (--remove): subprocess installed post-removal script returned error exit status 2 Errors were encountered while processing: systemd-shim E: Sub-process /usr/bin/dpkg returned an error code (1) Commenting out the dpkg-divert in systemd-shim's postrm solved this for me and I was about to continue the upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1773859/+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 1676547] Re: No network connectivity (NIC unmanaged) after upgrade
Brian, I did something similar to what you just described and got hit by that. Is that a different issue? -- 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/1676547 Title: No network connectivity (NIC unmanaged) after upgrade Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Yakkety: Fix Released Status in network-manager source package in Zesty: Fix Released Bug description: Impact -- When upgrading from Xenial (with all updates installed) to Yakkety/Zesty you will boot to a system without networking - sad! Test Case - 1) Boot a xenial desktop system 2) Ensure network-manager version 1.2.6-0ubuntu0.16.04.1 from -updates is installed 3) Upgrade to yakkety or zesty 3.5) Enable -proposed and download the new version of n-m "apt-get download network-manager" 4) Reboot 5) Observe you have no network If you install the version of network-manager from yakkety-proposed and then reboot you should have a network connection. 1) Boot a xenial desktop system. 2) ensure network-manager version 1.2.6-0ubuntu0.16.04.1 from -updates is installed. 3) Install nplan, configure to set up static network on an ethernet device using nplan. 4) Upgrade to yakkety or zesty 5) Reboot 6) Observe that your system is still being managed by networkd rather than NetworkManager. Regression Potential Any failure to manage ethernet or wireless devices after upgrade, or issues with the use of netplan in conjunction with NetworkManager should be investigated as potential regressions. For example, if after upgrading, ethernet devices are no longer managed, or if devices that should be explicitly ignored by NetworkManager due to existing user configuration are now managed, these would indicate a possible regression caused by this update. Original Description nplan was installed during the upgrade process but I had no network connectivity after upgrading. Apparently, no package wanted to manage my ethernet connection. ProblemType: BugDistroRelease: Ubuntu 16.10 Package: ubuntu-release-upgrader-core 1:16.10.10 ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17 Uname: Linux 4.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Mon Mar 27 11:34:04 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2013-01-16 (1531 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116) PackageArchitecture: allSourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to yakkety on 2017-03-17 (10 days ago) VarLogDistupgradeTermlog: modified.conffile..etc.update-manager.meta-release: [modified] mtime.conffile..etc.update-manager.meta-release: 2013-10-08T06:39:09.818913 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1676547/+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 1537566] Re: LibreOffice crashed but apport didn't log a crash file in /var/crash despite being enabled
In libreoffice 4.2.8 on Ubuntu 14.04, when the program crashes (or is
made to crash with pkill -11), apport kicks in. At the next libreoffice
run, it offers the user to try and recover the document that was being
worked on when the crash occurred.
In contrast, in libreoffice 5.1.6 on Ubuntu 16.04, when the program
crashes, its built-in document recovery handler kicks in, offering the
user to recover the document immediately. In that case, the built-in
handler is hooked to a SIGSEGV handler that prevents the creation of a
core file.
--
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/1537566
Title:
LibreOffice crashed but apport didn't log a crash file in /var/crash
despite being enabled
Status in apport package in Ubuntu:
New
Status in libreoffice package in Ubuntu:
Triaged
Bug description:
What is expected to happen is when LibreOffice crashes, a crash report
is created in the /var/crash folder.
What happened instead is LibreOffice crashed but apport didn't create
a crash file in the /var/crash folder, despite running and being
enabled. Apport creating crash files in /var/crash used to happen in
Xenial, and in prior releases. Other programs that crash are picked up
by apport so appears LO+apport issue.
LibreOffice has reference to placing crash files as per:
cat /etc/libreoffice/sofficerc | grep crash
CrashDirectory=${$BRAND_BASE_DIR/program/bootstraprc:UserInstallation}/crash
I don't have any 3rd party LO plugins installed.
apt-show-versions -r libreoffice*
libreoffice-avmedia-backend-gstreamer:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
libreoffice-avmedia-backend-gstreamer:i386 not installed
libreoffice-base-core:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
libreoffice-base-core:i386 not installed
libreoffice-calc:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
libreoffice-calc:i386 not installed
libreoffice-common:all/xenial 1:5.0.2-0ubuntu7 uptodate
libreoffice-core:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
libreoffice-core:i386 not installed
libreoffice-dev:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
libreoffice-dev:i386 not installed
libreoffice-draw:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
libreoffice-draw:i386 not installed
libreoffice-gnome:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
libreoffice-gnome:i386 not installed
libreoffice-gtk:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
libreoffice-gtk:i386 not installed
libreoffice-help-en-us:all/xenial 1:5.0.2-0ubuntu4 uptodate
libreoffice-impress:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
libreoffice-impress:i386 not installed
libreoffice-java-common:all/xenial 1:5.0.2-0ubuntu7 uptodate
libreoffice-math:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
libreoffice-math:i386 not installed
libreoffice-ogltrans:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
libreoffice-ogltrans:i386 not installed
libreoffice-pdfimport:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
libreoffice-pdfimport:i386 not installed
libreoffice-style-breeze:all/xenial 1:5.0.2-0ubuntu7 uptodate
libreoffice-style-galaxy:all/xenial 1:5.0.2-0ubuntu7 uptodate
libreoffice-style-human:all/xenial 1:5.0.2-0ubuntu7 uptodate
libreoffice-writer:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
libreoffice-writer:i386 not installed
cat /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=1
cat /etc/apport/crashdb.conf
# map crash database names to CrashDatabase implementations and URLs
default = 'ubuntu'
def get_oem_project():
'''Determine OEM project name from Distribution Channel Descriptor
Return None if it cannot be determined or does not exist.
'''
try:
dcd = open('/var/lib/ubuntu_dist_channel').read()
if dcd.startswith('canonical-oem-'):
return dcd.split('-')[2]
except IOError:
return None
databases = {
'ubuntu': {
'impl': 'launchpad',
'bug_pattern_url':
'http://people.canonical.com/~ubuntu-archive/bugpatterns/bugpatterns.xml',
'dupdb_url':
'http://people.canonical.com/~ubuntu-archive/apport-duplicates',
'distro': 'ubuntu',
'problem_types': ['Bug', 'Package'],
'escalation_tag': 'bugpattern-needed',
'escalated_tag': 'bugpattern-written',
},
'canonical-oem': {
'impl': 'launchpad',
'bug_pattern_url':
'http://people.canonical.com/~ubuntu-archive/bugpatterns/bugpatterns.xml',
'project': get_oem_project(),
},
'debug': {
# for debugging
'impl': 'memory',
'bug_pattern_url': '/tmp/bugpatterns.xml',
'distro': 'debug'
},
}
mo
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: libreoffice-calc 1:5.0.2-0ubuntu7
ProcVersionSignature: Ubuntu 4.3.0-6.17-generic
[Touch-packages] [Bug 1537566] Re: LibreOffice crashed but apport didn't log a crash file in /var/crash despite being enabled
Looks like
https://github.com/LibreOffice/core/commit/61c0c81caeb97dad0ed5bd201d06ad4e27f618c2
might be responsible for that behaviour change.
--
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/1537566
Title:
LibreOffice crashed but apport didn't log a crash file in /var/crash
despite being enabled
Status in apport package in Ubuntu:
New
Status in libreoffice package in Ubuntu:
Triaged
Bug description:
What is expected to happen is when LibreOffice crashes, a crash report
is created in the /var/crash folder.
What happened instead is LibreOffice crashed but apport didn't create
a crash file in the /var/crash folder, despite running and being
enabled. Apport creating crash files in /var/crash used to happen in
Xenial, and in prior releases. Other programs that crash are picked up
by apport so appears LO+apport issue.
LibreOffice has reference to placing crash files as per:
cat /etc/libreoffice/sofficerc | grep crash
CrashDirectory=${$BRAND_BASE_DIR/program/bootstraprc:UserInstallation}/crash
I don't have any 3rd party LO plugins installed.
apt-show-versions -r libreoffice*
libreoffice-avmedia-backend-gstreamer:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
libreoffice-avmedia-backend-gstreamer:i386 not installed
libreoffice-base-core:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
libreoffice-base-core:i386 not installed
libreoffice-calc:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
libreoffice-calc:i386 not installed
libreoffice-common:all/xenial 1:5.0.2-0ubuntu7 uptodate
libreoffice-core:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
libreoffice-core:i386 not installed
libreoffice-dev:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
libreoffice-dev:i386 not installed
libreoffice-draw:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
libreoffice-draw:i386 not installed
libreoffice-gnome:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
libreoffice-gnome:i386 not installed
libreoffice-gtk:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
libreoffice-gtk:i386 not installed
libreoffice-help-en-us:all/xenial 1:5.0.2-0ubuntu4 uptodate
libreoffice-impress:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
libreoffice-impress:i386 not installed
libreoffice-java-common:all/xenial 1:5.0.2-0ubuntu7 uptodate
libreoffice-math:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
libreoffice-math:i386 not installed
libreoffice-ogltrans:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
libreoffice-ogltrans:i386 not installed
libreoffice-pdfimport:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
libreoffice-pdfimport:i386 not installed
libreoffice-style-breeze:all/xenial 1:5.0.2-0ubuntu7 uptodate
libreoffice-style-galaxy:all/xenial 1:5.0.2-0ubuntu7 uptodate
libreoffice-style-human:all/xenial 1:5.0.2-0ubuntu7 uptodate
libreoffice-writer:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
libreoffice-writer:i386 not installed
cat /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=1
cat /etc/apport/crashdb.conf
# map crash database names to CrashDatabase implementations and URLs
default = 'ubuntu'
def get_oem_project():
'''Determine OEM project name from Distribution Channel Descriptor
Return None if it cannot be determined or does not exist.
'''
try:
dcd = open('/var/lib/ubuntu_dist_channel').read()
if dcd.startswith('canonical-oem-'):
return dcd.split('-')[2]
except IOError:
return None
databases = {
'ubuntu': {
'impl': 'launchpad',
'bug_pattern_url':
'http://people.canonical.com/~ubuntu-archive/bugpatterns/bugpatterns.xml',
'dupdb_url':
'http://people.canonical.com/~ubuntu-archive/apport-duplicates',
'distro': 'ubuntu',
'problem_types': ['Bug', 'Package'],
'escalation_tag': 'bugpattern-needed',
'escalated_tag': 'bugpattern-written',
},
'canonical-oem': {
'impl': 'launchpad',
'bug_pattern_url':
'http://people.canonical.com/~ubuntu-archive/bugpatterns/bugpatterns.xml',
'project': get_oem_project(),
},
'debug': {
# for debugging
'impl': 'memory',
'bug_pattern_url': '/tmp/bugpatterns.xml',
'distro': 'debug'
},
}
mo
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: libreoffice-calc 1:5.0.2-0ubuntu7
ProcVersionSignature: Ubuntu 4.3.0-6.17-generic 4.3.3
Uname: Linux 4.3.0-6-generic x86_64
ApportVersion: 2.19.3-0ubuntu3
Architecture: amd64
CurrentDesktop: GNOME-Flashback:Unity
Date: Sun Jan 24 17:03:37 2016
InstallationDate: Installed on 2015-12-18 (37 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: libreoffice
UpgradeStatus: Upgraded to xenial on 2016-01-20 (4 days ago)
[Touch-packages] [Bug 1666432] Re: Internet drops every few minutes on wired and wireless connection
I am also having a similar issue in Ubuntu 18.04. This happens right after opening some tabs and streams. The network icon stays there, but internet drops. Restarting the wifi doesn't solve the problem most times. The laptop is ASUS Vivobook S14. *-network description: Wireless interface product: QCA9377 802.11ac Wireless Network Adapter vendor: Qualcomm Atheros physical id: 0 bus info: pci@:02:00.0 logical name: wlp2s0 version: 31 serial: 40:9f:38:db:ca:0b width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=ath10k_pci driverversion=4.15.0-30-generic firmware=WLAN.TF.1.0-2-QCATFSWPZ-5 ip=192.168.1.157 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:129 memory:ef20-ef3f I've also tried using a realtek wifi dongle, which solved the problem to a point. However when I use that, it fails to connect to the wifi and takes about 3-5 minutes of constant connection attempts. So I gave up on that too. I don't have this problem with my other laptops. -- 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/1666432 Title: Internet drops every few minutes on wired and wireless connection Status in network-manager package in Ubuntu: Confirmed Bug description: Internet drops every 1-30 minutes when connected via wired or wireless (i.e., this is a problem on both wired and wireless) even though connection icon indicates the computer is still connected. Disconnecting and reconnecting via the connection icon resets internet temporarily until the next time. Dropped internet is discovered with "The site can't be reached" screens in Chromium, or error messages when downloading/updating in Terminal, or missing connection in Ubuntu Software app, or stalled syncing in Insync application (occurred even without Insync). Internet drops more frequently on wireless than on wired. It seems to disconnect more frequently with heavier internet use (e.g., downloading multiple files, opening several webpages in quick succession). This is a fresh install (yesterday) of Ubuntu 16.04 on a Dell Inspiron 15 5567 (dual boot). It occurs when running Live CD as well though. Ethernet and wifi both work without randomly disconnecting in Windows 10 on the same machine, and ethernet and wifi work on other machines running Ubuntu and Windows with the same router, so it is not a hardware or router issue. Output from sudo lshw -class network *-network description: Wireless interface product: Wireless 3165 vendor: Intel Corporation physical id: 0 bus info: pci@:02:00.0 logical name: wlp2s0 version: 79 serial: 58:fb:84:55:21:52 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=4.4.0-62-generic firmware=17.352738.0 ip=192.168.1.15 latency=0 link=yes multicast=yes wireless=IEEE 802.11abgn resources: irq:283 memory:df10-df101fff *-network description: Ethernet interface product: RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:03:00.0 logical name: enp3s0 version: 07 serial: 18:db:f2:3c:d5:37 size: 10Mbit/s capacity: 100Mbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=half firmware=rtl8106e-1_0.0.1 06/29/12 latency=0 link=no multicast=yes port=MII speed=10Mbit/s resources: irq:279 ioport:d000(size=256) memory:df00-df000fff memory:d030-d0303fff ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.2-0ubuntu0.16.04.3 ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40 Uname: Linux 4.4.0-62-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Tue Feb 21 16:36:55 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-02-20 (1 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.1.1 dev wlp2s0 proto static metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src
[Touch-packages] [Bug 1676547] Re: No network connectivity (NIC unmanaged) after upgrade
TJ - this isn't exactly the same issue if I understand correctly what you are doing. I ran into what I think is your issue last week. I installed using the 18.04.1 alternate server installation and then installed the 'ubuntu-desktop' meta package which pulled in network- manager. My interface was working, but not managed by network-manager until I added it as the renderer in the netplan yaml file. Is that the same issue you are reporting? -- 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/1676547 Title: No network connectivity (NIC unmanaged) after upgrade Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Yakkety: Fix Released Status in network-manager source package in Zesty: Fix Released Bug description: Impact -- When upgrading from Xenial (with all updates installed) to Yakkety/Zesty you will boot to a system without networking - sad! Test Case - 1) Boot a xenial desktop system 2) Ensure network-manager version 1.2.6-0ubuntu0.16.04.1 from -updates is installed 3) Upgrade to yakkety or zesty 3.5) Enable -proposed and download the new version of n-m "apt-get download network-manager" 4) Reboot 5) Observe you have no network If you install the version of network-manager from yakkety-proposed and then reboot you should have a network connection. 1) Boot a xenial desktop system. 2) ensure network-manager version 1.2.6-0ubuntu0.16.04.1 from -updates is installed. 3) Install nplan, configure to set up static network on an ethernet device using nplan. 4) Upgrade to yakkety or zesty 5) Reboot 6) Observe that your system is still being managed by networkd rather than NetworkManager. Regression Potential Any failure to manage ethernet or wireless devices after upgrade, or issues with the use of netplan in conjunction with NetworkManager should be investigated as potential regressions. For example, if after upgrading, ethernet devices are no longer managed, or if devices that should be explicitly ignored by NetworkManager due to existing user configuration are now managed, these would indicate a possible regression caused by this update. Original Description nplan was installed during the upgrade process but I had no network connectivity after upgrading. Apparently, no package wanted to manage my ethernet connection. ProblemType: BugDistroRelease: Ubuntu 16.10 Package: ubuntu-release-upgrader-core 1:16.10.10 ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17 Uname: Linux 4.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Mon Mar 27 11:34:04 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2013-01-16 (1531 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116) PackageArchitecture: allSourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to yakkety on 2017-03-17 (10 days ago) VarLogDistupgradeTermlog: modified.conffile..etc.update-manager.meta-release: [modified] mtime.conffile..etc.update-manager.meta-release: 2013-10-08T06:39:09.818913 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1676547/+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 1787440] [NEW] systemd 237-3ubuntu10 ADT test failure with linux 4.18.0-5.6
Public bug reported: Testing failed on: i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic-canonical-kernel-team-unstable/cosmic/i386/s/systemd/20180816_145803_9e627@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic-canonical-kernel-team-unstable/cosmic/s390x/s/systemd/20180816_140152_9e627@/log.gz ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure -- 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/1787440 Title: systemd 237-3ubuntu10 ADT test failure with linux 4.18.0-5.6 Status in systemd package in Ubuntu: New Bug description: Testing failed on: i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic-canonical-kernel-team-unstable/cosmic/i386/s/systemd/20180816_145803_9e627@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic-canonical-kernel-team-unstable/cosmic/s390x/s/systemd/20180816_140152_9e627@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1787440/+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 1787436] [NEW] lxc 3.0.1-0ubuntu2 ADT test failure with linux 4.18.0-5.6
Public bug reported: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic-canonical-kernel-team-unstable/cosmic/amd64/l/lxc/20180816_134239_340a6@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic-canonical-kernel-team-unstable/cosmic/arm64/l/lxc/20180816_135423_340a6@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic-canonical-kernel-team-unstable/cosmic/i386/l/lxc/20180816_134641_340a6@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic-canonical-kernel-team-unstable/cosmic/ppc64el/l/lxc/20180816_134231_340a6@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic-canonical-kernel-team-unstable/cosmic/s390x/l/lxc/20180816_134140_340a6@/log.gz ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1787436 Title: lxc 3.0.1-0ubuntu2 ADT test failure with linux 4.18.0-5.6 Status in lxc package in Ubuntu: New Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic-canonical-kernel-team-unstable/cosmic/amd64/l/lxc/20180816_134239_340a6@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic-canonical-kernel-team-unstable/cosmic/arm64/l/lxc/20180816_135423_340a6@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic-canonical-kernel-team-unstable/cosmic/i386/l/lxc/20180816_134641_340a6@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic-canonical-kernel-team-unstable/cosmic/ppc64el/l/lxc/20180816_134231_340a6@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic-canonical-kernel-team-unstable/cosmic/s390x/l/lxc/20180816_134140_340a6@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1787436/+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 1537566] Re: LibreOffice crashed but apport didn't log a crash file in /var/crash despite being enabled
Re comment #7, lowriter is a shell script that runs "soffice --writer",
crashing it with "pkill -11 lowriter" doesn't actually crash
libreoffice, only the wrapper script, so it's not a valid counter-
example.
To really crash libreoffice, one needs to run "pkill -11 soffice.bin".
This results in the libreoffice crash handler (and recovery tool)
kicking in, which apparently overrides whatever processing apport would
do.
--
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/1537566
Title:
LibreOffice crashed but apport didn't log a crash file in /var/crash
despite being enabled
Status in apport package in Ubuntu:
New
Status in libreoffice package in Ubuntu:
Triaged
Bug description:
What is expected to happen is when LibreOffice crashes, a crash report
is created in the /var/crash folder.
What happened instead is LibreOffice crashed but apport didn't create
a crash file in the /var/crash folder, despite running and being
enabled. Apport creating crash files in /var/crash used to happen in
Xenial, and in prior releases. Other programs that crash are picked up
by apport so appears LO+apport issue.
LibreOffice has reference to placing crash files as per:
cat /etc/libreoffice/sofficerc | grep crash
CrashDirectory=${$BRAND_BASE_DIR/program/bootstraprc:UserInstallation}/crash
I don't have any 3rd party LO plugins installed.
apt-show-versions -r libreoffice*
libreoffice-avmedia-backend-gstreamer:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
libreoffice-avmedia-backend-gstreamer:i386 not installed
libreoffice-base-core:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
libreoffice-base-core:i386 not installed
libreoffice-calc:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
libreoffice-calc:i386 not installed
libreoffice-common:all/xenial 1:5.0.2-0ubuntu7 uptodate
libreoffice-core:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
libreoffice-core:i386 not installed
libreoffice-dev:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
libreoffice-dev:i386 not installed
libreoffice-draw:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
libreoffice-draw:i386 not installed
libreoffice-gnome:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
libreoffice-gnome:i386 not installed
libreoffice-gtk:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
libreoffice-gtk:i386 not installed
libreoffice-help-en-us:all/xenial 1:5.0.2-0ubuntu4 uptodate
libreoffice-impress:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
libreoffice-impress:i386 not installed
libreoffice-java-common:all/xenial 1:5.0.2-0ubuntu7 uptodate
libreoffice-math:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
libreoffice-math:i386 not installed
libreoffice-ogltrans:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
libreoffice-ogltrans:i386 not installed
libreoffice-pdfimport:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
libreoffice-pdfimport:i386 not installed
libreoffice-style-breeze:all/xenial 1:5.0.2-0ubuntu7 uptodate
libreoffice-style-galaxy:all/xenial 1:5.0.2-0ubuntu7 uptodate
libreoffice-style-human:all/xenial 1:5.0.2-0ubuntu7 uptodate
libreoffice-writer:amd64/xenial 1:5.0.2-0ubuntu7 uptodate
libreoffice-writer:i386 not installed
cat /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=1
cat /etc/apport/crashdb.conf
# map crash database names to CrashDatabase implementations and URLs
default = 'ubuntu'
def get_oem_project():
'''Determine OEM project name from Distribution Channel Descriptor
Return None if it cannot be determined or does not exist.
'''
try:
dcd = open('/var/lib/ubuntu_dist_channel').read()
if dcd.startswith('canonical-oem-'):
return dcd.split('-')[2]
except IOError:
return None
databases = {
'ubuntu': {
'impl': 'launchpad',
'bug_pattern_url':
'http://people.canonical.com/~ubuntu-archive/bugpatterns/bugpatterns.xml',
'dupdb_url':
'http://people.canonical.com/~ubuntu-archive/apport-duplicates',
'distro': 'ubuntu',
'problem_types': ['Bug', 'Package'],
'escalation_tag': 'bugpattern-needed',
'escalated_tag': 'bugpattern-written',
},
'canonical-oem': {
'impl': 'launchpad',
'bug_pattern_url':
'http://people.canonical.com/~ubuntu-archive/bugpatterns/bugpatterns.xml',
'project': get_oem_project(),
},
'debug': {
# for debugging
'impl': 'memory',
'bug_pattern_url': '/tmp/bugpatterns.xml',
'distro': 'debug'
},
}
mo
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: libreoffice-calc 1:5.0.2-0ubuntu7
ProcVersionSignature: Ubuntu 4.3.0-6.17-generic 4.3.3
Uname: Linux 4.3.0-6-generic x86_64
ApportVersion: 2.19.3-0ubuntu3
Architecture: amd64
CurrentDesktop:
[Touch-packages] [Bug 1787349] Re: postgresql-plperl-9.5 blocks do-release-upgrade from 16.04 to 18.04
** Package changed: ubuntu-meta (Ubuntu) => ubuntu-release-upgrader (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1787349 Title: postgresql-plperl-9.5 blocks do-release-upgrade from 16.04 to 18.04 Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: The packet postgresql-plperl (and probably other addon packages for postgresql) blocks do-release-upgrade from 16.04LTS to 18.04LTS. This requiresthen requires a complete dump-and-restore cycle: 1) Stop user applications 2) do a full database export 3) stop postgresql 4) uninstall postgresql and all subpackages 5) delete remaining tablespace directories 6) do-release-upgrade 7) reinstall postgresql and the required subpackages 8) restore database from backup 9) start user applications This requires a much longer downtime than just using pg_upgradecluster, because the database is offline during the whole do-release-upgrade cycle. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1787349/+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 1787396] Re: ss crashes when using --no-header
This also happens on Cosmic that has the same version of ss/iproute2: # apt-cache policy iproute2 iproute2: Installed: 4.15.0-2ubuntu1 Candidate: 4.15.0-2ubuntu1 Version table: *** 4.15.0-2ubuntu1 500 500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1787396 Title: ss crashes when using --no-header Status in iproute2 package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1) Listen on port 8989: $ nc -l 8989 & 2) Check that ss can list this listener: $ ss --no-header -nto state listening 'sport = 8989' 010.0.0.0:8989 0.0.0.0:* 3) Ask ss to list listeners on a port where nothing listens $ kill %1 # stops nc $ ss --no-header -nto state listening 'sport = 8989' Segmentation fault (core dumped) In the above, removing "--no-header" avoids the segfault. Additional information: $ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 $ apt-cache policy iproute2 iproute2: Installed: 4.15.0-2ubuntu1 Candidate: 4.15.0-2ubuntu1 Version table: *** 4.15.0-2ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: iproute2 4.15.0-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 16 08:17:52 2018 InstallationDate: Installed on 2018-07-15 (32 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180714) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: iproute2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1787396/+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 1787396] Re: ss crashes when using --no-header
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: iproute2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1787396 Title: ss crashes when using --no-header Status in iproute2 package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1) Listen on port 8989: $ nc -l 8989 & 2) Check that ss can list this listener: $ ss --no-header -nto state listening 'sport = 8989' 010.0.0.0:8989 0.0.0.0:* 3) Ask ss to list listeners on a port where nothing listens $ kill %1 # stops nc $ ss --no-header -nto state listening 'sport = 8989' Segmentation fault (core dumped) In the above, removing "--no-header" avoids the segfault. Additional information: $ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 $ apt-cache policy iproute2 iproute2: Installed: 4.15.0-2ubuntu1 Candidate: 4.15.0-2ubuntu1 Version table: *** 4.15.0-2ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: iproute2 4.15.0-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 16 08:17:52 2018 InstallationDate: Installed on 2018-07-15 (32 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180714) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: iproute2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1787396/+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 1787396] Re: ss crashes when using --no-header
I've replicated the problem and the way I see it, all you need is --no- header and a filter with no matches. Filters with matches (found connections) won't cause a segfault. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1787396 Title: ss crashes when using --no-header Status in iproute2 package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1) Listen on port 8989: $ nc -l 8989 & 2) Check that ss can list this listener: $ ss --no-header -nto state listening 'sport = 8989' 010.0.0.0:8989 0.0.0.0:* 3) Ask ss to list listeners on a port where nothing listens $ kill %1 # stops nc $ ss --no-header -nto state listening 'sport = 8989' Segmentation fault (core dumped) In the above, removing "--no-header" avoids the segfault. Additional information: $ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 $ apt-cache policy iproute2 iproute2: Installed: 4.15.0-2ubuntu1 Candidate: 4.15.0-2ubuntu1 Version table: *** 4.15.0-2ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: iproute2 4.15.0-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 16 08:17:52 2018 InstallationDate: Installed on 2018-07-15 (32 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180714) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: iproute2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1787396/+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 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6
Well, that was pretty straightforward! Thanks for pointing that one out, we'll know in a couple hours if it worked. Peace & Joy; Love & Gratitude -- 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/1688018 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6 Status in network-manager package in Ubuntu: Triaged Status in network-manager source package in Xenial: In Progress Status in network-manager source package in Yakkety: Triaged Bug description: This was initially opened as #1671606 then later duped to #1639776. Discussion in #1639776 indicate that we need new bug for this so I am opening one ... Please don't mark this as duplicate to #1639776 or other similar bug report. We already lost several months and we are again at beginning ... TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from DHCP instead of one defined by VPN (wrong). DNS resolver should query only DNS servers defined by VPN while connection is active. = Test steps / result: - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 (dnsmasq-base-2.75-1ubuntu0.16.04.2) - restated my laptop to ensure clean start - connected to VPN using openconnect / network-manager-openconnect-gnome Observed results -> DNS queries are forwarded only to DNS servers defined by LAN connection (this is wrong / connection not working at all) - "killall dnsmasq" - dnsmasq get automatically restarted by system Observed results -> most of the the queries are forwarded to DNS servers defined by VPN, but lot of queries get forwarded to DNS servers defined by LAN connection (this is still wrong / DNS leaks, attacker can hijack connection even if VPN is enabled) - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base stay same) - restated my laptop to ensure clean test - connected to same VPN using openconnect Observed results -> DNS queries are forwarded only to DNS servers defined by VPN connection. There are no leaks to LAN DNS server (this is correct behavior). = Paul Smith requested additional details in #1639776. Here are: * If you're using IPv4 vs. IPv6 -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi /vpn) * If you have checked or unchecked the "Use this connection only for resources on its network" -> unchecked on all nw definition * If you have this checked, try unchecking it and see if that makes a difference -> no change if I toggle this option. Behavior is same. * When you say "DNS lookups" please be clear about whether the hostnames being looked up are public (e.g., www.google.com or whatever), on your local LAN, or in the network accessed via the VPN. Does it make a difference which one you choose? -> No difference. * Are you using fully-qualified hostnames, or relying on the DNS domain search path? Does it make a difference if you do it differently? -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see difference when I try same using hostname + domain search. = I am using openconnect (cisco) and openvpn. Test result are by using openconnect but I saw same behaviour also while using openvpn. = Thanks Lukas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1688018/+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 1783138] Re: hinic interfaces aren't getting predictable names
This bug was fixed in the package linux - 4.17.0-7.8
---
linux (4.17.0-7.8) cosmic; urgency=medium
* linux: 4.17.0-7.8 -proposed tracker (LP: #1785242)
* Cosmic update to 4.17.12 stable release (LP: #1785211)
- spi: spi-s3c64xx: Fix system resume support
- Input: elan_i2c - add ACPI ID for lenovo ideapad 330
- Input: i8042 - add Lenovo LaVie Z to the i8042 reset list
- Input: elan_i2c - add another ACPI ID for Lenovo Ideapad 330-15AST
- mm: disallow mappings that conflict for devm_memremap_pages()
- kvm, mm: account shadow page tables to kmemcg
- delayacct: fix crash in delayacct_blkio_end() after delayacct init failure
- tracing: Fix double free of event_trigger_data
- tracing: Fix possible double free in event_enable_trigger_func()
- kthread, tracing: Don't expose half-written comm when creating kthreads
- tracing/kprobes: Fix trace_probe flags on enable_trace_kprobe() failure
- tracing: Quiet gcc warning about maybe unused link variable
- arm64: fix vmemmap BUILD_BUG_ON() triggering on !vmemmap setups
- drm/i915/glk: Add Quirk for GLK NUC HDMI port issues.
- mlxsw: spectrum_switchdev: Fix port_vlan refcounting
- kcov: ensure irq code sees a valid area
- mm: check for SIGKILL inside dup_mmap() loop
- drm/amd/powerplay: Set higher SCLK frequency than dpm7 in OD (v2)
- xen/netfront: raise max number of slots in xennet_get_responses()
- hv_netvsc: fix network namespace issues with VF support
- skip LAYOUTRETURN if layout is invalid
- ixgbe: Fix setting of TC configuration for macvlan case
- ALSA: emu10k1: add error handling for snd_ctl_add
- ALSA: fm801: add error handling for snd_ctl_add
- NFSv4.1: Fix the client behaviour on NFS4ERR_SEQ_FALSE_RETRY
- nfsd: fix error handling in nfs4_set_delegation()
- nfsd: fix potential use-after-free in nfsd4_decode_getdeviceinfo
- vfio: platform: Fix reset module leak in error path
- vfio/mdev: Check globally for duplicate devices
- vfio/type1: Fix task tracking for QEMU vCPU hotplug
- kernel/hung_task.c: show all hung tasks before panic
- mem_cgroup: make sure moving_account, move_lock_task and stat_cpu in the
same cacheline
- mm: /proc/pid/pagemap: hide swap entries from unprivileged users
- mm: vmalloc: avoid racy handling of debugobjects in vunmap
- mm/slub.c: add __printf verification to slab_err()
- rtc: ensure rtc_set_alarm fails when alarms are not supported
- rxrpc: Fix terminal retransmission connection ID to include the channel
- perf tools: Fix pmu events parsing rule
- netfilter: ipset: forbid family for hash:mac sets
- netfilter: ipset: List timing out entries with "timeout 1" instead of zero
- irqchip/ls-scfg-msi: Map MSIs in the iommu
- watchdog: da9063: Fix updating timeout value
- media: arch: sh: migor: Fix TW9910 PDN gpio
- printk: drop in_nmi check from printk_safe_flush_on_panic()
- bpf, arm32: fix inconsistent naming about emit_a32_lsr_{r64,i64}
- ceph: fix alignment of rasize
- ceph: fix use-after-free in ceph_statfs()
- e1000e: Ignore TSYNCRXCTL when getting I219 clock attributes
- infiniband: fix a possible use-after-free bug
- powerpc/lib: Adjust .balign inside string functions for PPC32
- powerpc/64s: Add barrier_nospec
- powerpc/eeh: Fix use-after-release of EEH driver
- hvc_opal: don't set tb_ticks_per_usec in udbg_init_opal_common()
- powerpc/64s: Fix compiler store ordering to SLB shadow area
- clk-si544: Properly round requested frequency to nearest match
- clk: ingenic: jz4770: Modify C1CLK clock to disable CPU clock stop on idle
- RDMA/mad: Convert BUG_ONs to error flows
- lightnvm: fix partial read error path
- lightnvm: proper error handling for pblk_bio_add_pages
- lightnvm: pblk: warn in case of corrupted write buffer
- netfilter: nf_tables: check msg_type before nft_trans_set(trans)
- pnfs: Don't release the sequence slot until we've processed layoutget on
open
- NFS: Fix up nfs_post_op_update_inode() to force ctime updates
- disable loading f2fs module on PAGE_SIZE > 4KB
- f2fs: fix error path of move_data_page
- f2fs: don't drop dentry pages after fs shutdown
- f2fs: fix to don't trigger writeback during recovery
- f2fs: fix to wait page writeback during revoking atomic write
- f2fs: Fix deadlock in shutdown ioctl
- f2fs: fix missing clear FI_NO_PREALLOC in some error case
- f2fs: fix to detect failure of dquot_initialize
- f2fs: fix race in between GC and atomic open
- block, bfq: remove wrong lock in bfq_requests_merged
- usbip: usbip_detach: Fix memory, udev context and udev leak
- usbip: dynamically allocate idev by nports found in sysfs
- perf/x86/intel/uncore: Correct fixed counter index check in generic code
- perf/x86/intel/uncore: Correct fixed counter index check for NHM
-
[Touch-packages] [Bug 1780227] Re: locking sockets broken due to missing AppArmor socket mediation patches
This bug was fixed in the package linux - 4.17.0-7.8
---
linux (4.17.0-7.8) cosmic; urgency=medium
* linux: 4.17.0-7.8 -proposed tracker (LP: #1785242)
* Cosmic update to 4.17.12 stable release (LP: #1785211)
- spi: spi-s3c64xx: Fix system resume support
- Input: elan_i2c - add ACPI ID for lenovo ideapad 330
- Input: i8042 - add Lenovo LaVie Z to the i8042 reset list
- Input: elan_i2c - add another ACPI ID for Lenovo Ideapad 330-15AST
- mm: disallow mappings that conflict for devm_memremap_pages()
- kvm, mm: account shadow page tables to kmemcg
- delayacct: fix crash in delayacct_blkio_end() after delayacct init failure
- tracing: Fix double free of event_trigger_data
- tracing: Fix possible double free in event_enable_trigger_func()
- kthread, tracing: Don't expose half-written comm when creating kthreads
- tracing/kprobes: Fix trace_probe flags on enable_trace_kprobe() failure
- tracing: Quiet gcc warning about maybe unused link variable
- arm64: fix vmemmap BUILD_BUG_ON() triggering on !vmemmap setups
- drm/i915/glk: Add Quirk for GLK NUC HDMI port issues.
- mlxsw: spectrum_switchdev: Fix port_vlan refcounting
- kcov: ensure irq code sees a valid area
- mm: check for SIGKILL inside dup_mmap() loop
- drm/amd/powerplay: Set higher SCLK frequency than dpm7 in OD (v2)
- xen/netfront: raise max number of slots in xennet_get_responses()
- hv_netvsc: fix network namespace issues with VF support
- skip LAYOUTRETURN if layout is invalid
- ixgbe: Fix setting of TC configuration for macvlan case
- ALSA: emu10k1: add error handling for snd_ctl_add
- ALSA: fm801: add error handling for snd_ctl_add
- NFSv4.1: Fix the client behaviour on NFS4ERR_SEQ_FALSE_RETRY
- nfsd: fix error handling in nfs4_set_delegation()
- nfsd: fix potential use-after-free in nfsd4_decode_getdeviceinfo
- vfio: platform: Fix reset module leak in error path
- vfio/mdev: Check globally for duplicate devices
- vfio/type1: Fix task tracking for QEMU vCPU hotplug
- kernel/hung_task.c: show all hung tasks before panic
- mem_cgroup: make sure moving_account, move_lock_task and stat_cpu in the
same cacheline
- mm: /proc/pid/pagemap: hide swap entries from unprivileged users
- mm: vmalloc: avoid racy handling of debugobjects in vunmap
- mm/slub.c: add __printf verification to slab_err()
- rtc: ensure rtc_set_alarm fails when alarms are not supported
- rxrpc: Fix terminal retransmission connection ID to include the channel
- perf tools: Fix pmu events parsing rule
- netfilter: ipset: forbid family for hash:mac sets
- netfilter: ipset: List timing out entries with "timeout 1" instead of zero
- irqchip/ls-scfg-msi: Map MSIs in the iommu
- watchdog: da9063: Fix updating timeout value
- media: arch: sh: migor: Fix TW9910 PDN gpio
- printk: drop in_nmi check from printk_safe_flush_on_panic()
- bpf, arm32: fix inconsistent naming about emit_a32_lsr_{r64,i64}
- ceph: fix alignment of rasize
- ceph: fix use-after-free in ceph_statfs()
- e1000e: Ignore TSYNCRXCTL when getting I219 clock attributes
- infiniband: fix a possible use-after-free bug
- powerpc/lib: Adjust .balign inside string functions for PPC32
- powerpc/64s: Add barrier_nospec
- powerpc/eeh: Fix use-after-release of EEH driver
- hvc_opal: don't set tb_ticks_per_usec in udbg_init_opal_common()
- powerpc/64s: Fix compiler store ordering to SLB shadow area
- clk-si544: Properly round requested frequency to nearest match
- clk: ingenic: jz4770: Modify C1CLK clock to disable CPU clock stop on idle
- RDMA/mad: Convert BUG_ONs to error flows
- lightnvm: fix partial read error path
- lightnvm: proper error handling for pblk_bio_add_pages
- lightnvm: pblk: warn in case of corrupted write buffer
- netfilter: nf_tables: check msg_type before nft_trans_set(trans)
- pnfs: Don't release the sequence slot until we've processed layoutget on
open
- NFS: Fix up nfs_post_op_update_inode() to force ctime updates
- disable loading f2fs module on PAGE_SIZE > 4KB
- f2fs: fix error path of move_data_page
- f2fs: don't drop dentry pages after fs shutdown
- f2fs: fix to don't trigger writeback during recovery
- f2fs: fix to wait page writeback during revoking atomic write
- f2fs: Fix deadlock in shutdown ioctl
- f2fs: fix missing clear FI_NO_PREALLOC in some error case
- f2fs: fix to detect failure of dquot_initialize
- f2fs: fix race in between GC and atomic open
- block, bfq: remove wrong lock in bfq_requests_merged
- usbip: usbip_detach: Fix memory, udev context and udev leak
- usbip: dynamically allocate idev by nports found in sysfs
- perf/x86/intel/uncore: Correct fixed counter index check in generic code
- perf/x86/intel/uncore: Correct fixed counter index check for NHM
-
[Touch-packages] [Bug 1783328] Re: The option to select LTS notifications should be masked in non-LTS versions
** Changed in: ubuntu-release-upgrader (Ubuntu Cosmic) Status: Confirmed => Invalid ** Changed in: update-manager (Ubuntu Cosmic) Status: New => Triaged ** Changed in: update-manager (Ubuntu Cosmic) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1783328 Title: The option to select LTS notifications should be masked in non-LTS versions Status in software-properties package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Triaged Status in software-properties source package in Cosmic: Confirmed Status in ubuntu-release-upgrader source package in Cosmic: Invalid Status in update-manager source package in Cosmic: Triaged Bug description: I have been bitten by _not_ knowing that selecting "Notify me of a new Ubuntu version: For long-term support versions" in a non-LTS(17.10) software-properties-gtk dialog box would simply silently fail to inform users that they are no longer receiving updates to their Ubuntu installs. Please mask or hide the option to select "For long-term support versions" if the currently running version is a non-LTS version(grep or awk the /etc/os-release file or some-such for the LTS string). It is non-intuitive to see this option as available to select and not receive warning of its hazards. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.21 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CrashDB: ubuntu Date: Tue Jul 24 07:30:11 2018 InstallationDate: Installed on 2018-05-21 (64 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.update-manager.release-upgrades: 2018-05-24T11:23:48.670462 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1783328/+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 1671951] Re: networkd should allow configuring IPV6 MTU
** Tags added: id-5b74352f76a21f210334eafd -- 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/1671951 Title: networkd should allow configuring IPV6 MTU Status in systemd package in Ubuntu: Confirmed Bug description: 1) Zesty 2) systemd-232-19 3) I need to configure the IPV6 MTU for tunneling by adding an IPv6MTUBytes=1480 value in the .network file for an interface with an IPV6 static address in the [Network] section 4) networkd does not parse or read the value and does not apply this configuration to the interface. Upstream has discussed this issue here: https://github.com/systemd/systemd/pull/1533 But it's been closed in favor of only setting via RA. However, we know of multiple use-case which are currently supported in ifdupdown where we want to retain control over IPV6 MTU values outside of PMTU Discovery configurations. Some context from those discussions >> Client systems that route their ipv6 packets to a 6in4 router also >> have to have their ipv6 mtu lowered. They could lower their link mtu, >> so their ipv6 packets are small enough, but that reduces performance >> of their ipv4 network. Yes. Anything that creates a PMTUD black hole can result in situations where the higher header overhead of IPv6 will cause IPv4 to pass but IPv6 traffic to be dropped. One example here is egress from an ipsec tunnel wherein the next hop MTU is too low for IPv6 datagrams to pass. Another is VM -> whatever -> host bridge -> tunnel ingress. If the datagram cannot enter the tunnel due to size, it is dropped, and an ICMP response uses the tunnel address as a source, which may not be routable back to the origin. This one is an issue with IPv4 as well, and is one case where manually setting the IPv6 MTU lower than the (also manually set) device MTU is of benefit. In essence, any of these sort of cases that require an explicit setting of the device MTU will likely require a setting of the IPv6 mtu as well to account for its larger header overhead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1671951/+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 1787354] Re: Add modified german keyboard layout for programming to reduce RSI
The attachment "Patch for german keyboard layout file" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu- reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1787354 Title: Add modified german keyboard layout for programming to reduce RSI Status in ubuntu-meta package in Ubuntu: New Bug description: I'm a software developer writing quite a lot of code. The way the german keybooard is layed out, some essential keys like brackets and backslash are very awkward to type (right hand holding Alt-GR in bottom row and pressing the key right of the 0-key in top row to get a backslash). After years of doing this, i started to suffer from RSI (repetitive strain injury). I'm attaching a patch for an additional keyboard layout that puts all those hard to reach one-handed brackets, braces and backslash on the Umlaut keys. The Umlauts are still available in their normal place through Alt-GR for occasional use, but i mostly use Scroll-Lock to switch to an unmodified no-deadkeys layout when typing german text. I have been using this layout now for 3 years, and it has greatly reduced suffering, while still enabling me to do my job. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1787354/+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 1787396] [NEW] ss crashes when using --no-header
Public bug reported: Steps to reproduce: 1) Listen on port 8989: $ nc -l 8989 & 2) Check that ss can list this listener: $ ss --no-header -nto state listening 'sport = 8989' 010.0.0.0:8989 0.0.0.0:* 3) Ask ss to list listeners on a port where nothing listens $ kill %1 # stops nc $ ss --no-header -nto state listening 'sport = 8989' Segmentation fault (core dumped) In the above, removing "--no-header" avoids the segfault. Additional information: $ lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 $ apt-cache policy iproute2 iproute2: Installed: 4.15.0-2ubuntu1 Candidate: 4.15.0-2ubuntu1 Version table: *** 4.15.0-2ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: iproute2 4.15.0-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 16 08:17:52 2018 InstallationDate: Installed on 2018-07-15 (32 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180714) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: iproute2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: iproute2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1787396 Title: ss crashes when using --no-header Status in iproute2 package in Ubuntu: New Bug description: Steps to reproduce: 1) Listen on port 8989: $ nc -l 8989 & 2) Check that ss can list this listener: $ ss --no-header -nto state listening 'sport = 8989' 010.0.0.0:8989 0.0.0.0:* 3) Ask ss to list listeners on a port where nothing listens $ kill %1 # stops nc $ ss --no-header -nto state listening 'sport = 8989' Segmentation fault (core dumped) In the above, removing "--no-header" avoids the segfault. Additional information: $ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 $ apt-cache policy iproute2 iproute2: Installed: 4.15.0-2ubuntu1 Candidate: 4.15.0-2ubuntu1 Version table: *** 4.15.0-2ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: iproute2 4.15.0-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 16 08:17:52 2018 InstallationDate: Installed on 2018-07-15 (32 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180714) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: iproute2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1787396/+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 1785383] Re: missing EDNS0 record confuses systemd-resolved
In my opinion the log message from system also needs to be dropped - a
number of systems will use NXDOMAIN as a means of domain blocking/ad
blocking, and this isn't thus an exceptional event that needs logging
each time.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1785383
Title:
missing EDNS0 record confuses systemd-resolved
Status in dnsmasq package in Ubuntu:
New
Status in systemd package in Ubuntu:
New
Bug description:
dnsmasq 2.79 and below omits EDNS0 OPT records when returning an empty
answer for a domain it is authoritative for. systemd-resolved seems to
get confused by this in certain circumstances; when using the stub
resolver and requesting an address for which there are no
records, there can sometimes be a five second hang in resolution.
This is fixed by upstream commit
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=1682d15a744880b0398af75eadf68fe66128af78
Not sure if it is worth cherry picking? I imagine the most likely
trigger will be dnsmasq on routers which are not likely to be running
Ubuntu, but maybe just in case.
I also think there are some logic issues in systemd-resolved, upstream
bug filed:
https://github.com/systemd/systemd/issues/9785
Simple-ish test case:
---
IFACE=dummy0
SUBNET=10.0.0
ip link add $IFACE type dummy
ifconfig $IFACE ${SUBNET}.1/24
dnsmasq -h -R -d -C /dev/null -2 $IFACE -z -i $IFACE -I lo
--host-record=test.test,${SUBNET}.1 &
dig -t a test.test @10.0.0.1 | grep EDNS
# should return "; EDNS ..."
dig -t test.test @10.0.0.1 | grep EDNS
# again, should return "; EDNS ..." but doesn't
---
To reproduce the systemd-resolved side of the problem
---
# as above, but
# now configure systemd-resolved to look at only 10.0.0.1, then
systemd-resolve --reset-server-features
# should exhibit five second delay then connect, assuming sshd is running :)
ssh test.test
---
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: dnsmasq-base 2.79-1
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Sat Aug 4 11:33:56 2018
InstallationDate: Installed on 2018-05-31 (64 days ago)
InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64
(20180426)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
SourcePackage: dnsmasq
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1785383/+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 1748839] Re: Problem to connect to WPA2/PEAP WIFI - gnome-shell
** Description changed: - Connection to open or WPA secured wifi works without any issues. - Connection to WPA2/PEAP fails. Repeatedly asks for username/password. + This problem is also happened on my desktop. - Possible gnome-shell integration issue. + After upgrading OS from Ubuntu 16.04 to Ubuntu 18.04.1 LTS, my PC could + not connect and authenticate on WiFi with WPA2/PEAP/MSCHAPv2/no CA + certificate/true username and password. - The system was updated from Xenial to Bionic in mid-January. At that - time this WPA2/PEAP setup worked without any issues. With the updates - coming in the last week of January / First February week - the bug was - experienced. - 1) - ➜ syncthing git:(master) lsb_release -rd - Description: Ubuntu Bionic Beaver (development branch) - Release: 18.04 + I tried to solve the problem following URL link; however, it could not help me also. + https://askubuntu.com/questions/279762/how-to-connect-to-wpa2-peap-mschapv2-enterprise-wifi-networks-that-dont-use-a-c - 2) - up to date packages - [code] - ➜ cat /etc/apt/sources.list |egrep -v '^#' - deb http://cz.archive.ubuntu.com/ubuntu/ bionic main restricted - deb http://cz.archive.ubuntu.com/ubuntu/ bionic-updates main restricted - deb http://cz.archive.ubuntu.com/ubuntu/ bionic universe - deb http://cz.archive.ubuntu.com/ubuntu/ bionic-updates universe - deb http://cz.archive.ubuntu.com/ubuntu/ bionic multiverse - deb http://cz.archive.ubuntu.com/ubuntu/ bionic-updates multiverse - deb http://security.ubuntu.com/ubuntu/ bionic-security multiverse main universe restricted - [/code] - Note: - # some pkg version related to problem might be from proposed-updates repo + My PC is HP Compaq Pro 4300, CPU: Intel® Core™ i3-3220 CPU @ 3.30GHz × 4, OS: Ubuntu 18.04.1 (64-bit). - 2b) - [code] - dpkg -l |egrep -i 'network manager|networkm|libnm' - ii gir1.2-networkmanager-1.0:amd641.8.4-1ubuntu4 amd64GObject introspection data for the libnm-glib/libnm-util library - ii gir1.2-nm-1.0:amd641.8.4-1ubuntu4 amd64GObject introspection data for the libnm library - ii gir1.2-nmgtk-1.0:amd64 1.8.10-2ubuntu1 amd64GObject introspection data for libnm-gtk - ii libnm-glib-vpn1:amd64 1.8.4-1ubuntu4 amd64network management framework (GLib VPN shared library) - ii libnm-glib4:amd64 1.8.4-1ubuntu4 amd64network management framework (GLib shared library) - ii libnm-gtk0:amd64 1.8.10-2ubuntu1 amd64library for wireless and mobile dialogs (libnm-glib version) - ii libnm-util2:amd64 1.8.4-1ubuntu4 amd64network management framework (shared library) - ii libnm0:amd64 1.8.4-1ubuntu4 amd64GObject-based client library for NetworkManager - ii libnma0:amd64 1.8.10-2ubuntu1 amd64library for wireless and mobile dialogs (libnm version) - ii libproxy1-plugin-networkmanager:amd64 0.4.15-0ubuntu1 amd64automatic proxy configuration management library (Network Manager plugin) - ii network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu4 all NetworkManager configuration to enable connectivity checking - ii strongswan-nm 5.6.1-2ubuntu1 amd64strongSwan plugin to interact with NetworkManager + root@joe-UBTPC:/root # lspci - ii wpasupplicant 2:2.6-15ubuntu2 - amd64client support for WPA and WPA2 (IEEE 802.11i) - - [/code] - - 3,4) - Connection to open or WPA secured wifi works withou any issues. Connection to WPA2/PLEAP (without cert, just with username/password fails). Although wifi layer get's is associated the client (network-manager) possibly due to bug deauthenticate itself without establishing an IP connection. - - Connect to network. - - 5) - Logs (syslog/kernel) - - Core moments: - - [code] - Feb 12 09:19:02 dontpanic NetworkManager[1125]: [1518423542.9125] keyfile: update /etc/NetworkManager/system-connections/WiFi (82c55e94-907a-458a-ae31-8cbd75db0fa5,"WiFi") - Feb 12 09:19:02 dontpanic gnome-shell[4284]: g_value_get_string: assertion 'G_VALUE_HOLDS_STRING (value)' failed - - and ... - - Feb 12
[Touch-packages] [Bug 1787297] Re: Clock : incorrect date format in FR in Unity panel …bionic.
Ah, i am not under Unity: -Version- Kernel : Linux 4.17.0-6-generic (x86_64) Version: #7-Ubuntu SMP Tue Jul 24 23:07:00 UTC 2018 C Library : GNU C Library / (Ubuntu GLIBC 2.27-3ubuntu1) 2.27 Distribution : Ubuntu Cosmic Cuttlefish (development branch) -Current Session- Language : fr_FR.UTF-8 (fr_FR.UTF-8) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1787297 Title: Clock : incorrect date format in FR in Unity panel …bionic. Status in indicator-datetime package in Ubuntu: Confirmed Status in unity package in Ubuntu: Invalid Bug description: Hi, Here is Ubuntu 18.04 with Unity session ( I know… ) System language and regional settings are set to French. In regional setting the date reads day number month year hour minute… which is correct for French. But the clock in the Unity panel reads day month number year hour minute… which looks more English than French order. Any config file I might edit to make my clock « more French » ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1787297/+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 1036001] Re: GVim tear-off menus don't work
Thanks for your reply. You probably have vim-gtk installed rather than vim-gnome. Don't worry about updating the logs. I'll revert the change to "Incomplete" and update the tags. Vim version assumed to be 7.4. ** Changed in: vim (Ubuntu) Status: Incomplete => New ** Tags added: xenial -- 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/1036001 Title: GVim tear-off menus don't work Status in vim package in Ubuntu: New Bug description: The GVim text editor, as installed from the software center (I checked with Synaptic and its package is vim-gnome 2:7.3.429-2ubuntu2.1) has a bug with its tear-off menus (occurs on Xfce and KDE, not sure about Unity). Steps to reproduce: Open Gvim. Click on the Edit menu. Point to the Color scheme menu item (third from the bottom). A submenu will open. Click on the first item of the submenu (the one that looks like “”). The menu will become a separate window. Click on any menu item and notice that the color scheme of the window doesn't change at all. It changes correctly when the menu is used normally (without tearing it off first). Distro --- Description: Ubuntu 12.04 LTS Release: 12.04 --- xubuntu-desktop and kubuntu-desktop installed after the main system installation. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: vim-gnome 2:7.3.429-2ubuntu2.1 ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24 Uname: Linux 3.2.0-29-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu12 Architecture: amd64 Date: Sun Aug 12 22:04:51 2012 ExecutablePath: /usr/bin/vim.gnome InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) SourcePackage: vim UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1036001/+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 1787297] Re: Clock : incorrect date format in FR in Unity panel …bionic.
hello ! in panel indicator i have: "jeu. août 16 13:15" in calendar i have: "jeudi 16 août 2018" in terminal, date: "jeudi 16 août 2018, 13:17:44 (UTC+0200)" i don't have "/com/canonical/indicator" in dconf ? ? ? bye -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1787297 Title: Clock : incorrect date format in FR in Unity panel …bionic. Status in indicator-datetime package in Ubuntu: Confirmed Status in unity package in Ubuntu: Invalid Bug description: Hi, Here is Ubuntu 18.04 with Unity session ( I know… ) System language and regional settings are set to French. In regional setting the date reads day number month year hour minute… which is correct for French. But the clock in the Unity panel reads day month number year hour minute… which looks more English than French order. Any config file I might edit to make my clock « more French » ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1787297/+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 1787378] [NEW] Merge with Debian 3.23.2-1
Public bug reported: Merge with Debian 3.23.2-1 ** Affects: gtk+3.0 (Ubuntu) Importance: Medium Assignee: Andrea Azzarone (azzar1) Status: In Progress ** Tags: upgrade-software-version ** Changed in: gtk+3.0 (Ubuntu) Status: New => In Progress ** Changed in: gtk+3.0 (Ubuntu) Assignee: (unassigned) => Andrea Azzarone (azzar1) ** Changed in: gtk+3.0 (Ubuntu) Importance: Wishlist => Medium -- 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/1787378 Title: Merge with Debian 3.23.2-1 Status in gtk+3.0 package in Ubuntu: In Progress Bug description: Merge with Debian 3.23.2-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1787378/+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 1787297] Re: Clock : incorrect date format in FR in Unity panel …bionic.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: indicator-datetime (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1787297 Title: Clock : incorrect date format in FR in Unity panel …bionic. Status in indicator-datetime package in Ubuntu: Confirmed Status in unity package in Ubuntu: Invalid Bug description: Hi, Here is Ubuntu 18.04 with Unity session ( I know… ) System language and regional settings are set to French. In regional setting the date reads day number month year hour minute… which is correct for French. But the clock in the Unity panel reads day month number year hour minute… which looks more English than French order. Any config file I might edit to make my clock « more French » ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1787297/+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 1787374] [NEW] resolvconf fails to update DNS server after resuming laptop from suspend
Public bug reported: This bug has been present since I have updated to Ubuntu 17.10 and it is still present in Ubuntu 18.04. It seems pretty simple to understand and a solution should be straightforward, but I lack understanding for what application is failing to update the right configuration file. When I go to work and I start my laptop, my /run/resolvconf/interface/systemd-resolved is filled with this: nameserver 127.0.0.53 search broadinstitute.org plc.hootoo.com When I come back home, DNS resolution does not work or works very slowly, most likely because my work DNS server broadinstitute.org is not reachable anymore, or maybe it is reachable but it is excruciatingly slow at responding. The solution is for me to edit /run/resolvconf/interface/systemd-resolved and remove the work DNS server: nameserver 127.0.0.53 search plc.hootoo.com And then update /etc/resolv.conf with the following command: $ sudo /etc/init.d/resolvconf restart Alternatively, another solution is to reboot the laptop. Then everything works fine. This is clearly a bug, but I am not sure whether it is a NetworkManager's bug, a resolvconf's bug, or a systemd bug. Please help! :-) ** Affects: resolvconf (Ubuntu) Importance: Undecided Status: New ** Package changed: systemd (Ubuntu) => resolvconf (Ubuntu) -- 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/1787374 Title: resolvconf fails to update DNS server after resuming laptop from suspend Status in resolvconf package in Ubuntu: New Bug description: This bug has been present since I have updated to Ubuntu 17.10 and it is still present in Ubuntu 18.04. It seems pretty simple to understand and a solution should be straightforward, but I lack understanding for what application is failing to update the right configuration file. When I go to work and I start my laptop, my /run/resolvconf/interface/systemd-resolved is filled with this: nameserver 127.0.0.53 search broadinstitute.org plc.hootoo.com When I come back home, DNS resolution does not work or works very slowly, most likely because my work DNS server broadinstitute.org is not reachable anymore, or maybe it is reachable but it is excruciatingly slow at responding. The solution is for me to edit /run/resolvconf/interface/systemd-resolved and remove the work DNS server: nameserver 127.0.0.53 search plc.hootoo.com And then update /etc/resolv.conf with the following command: $ sudo /etc/init.d/resolvconf restart Alternatively, another solution is to reboot the laptop. Then everything works fine. This is clearly a bug, but I am not sure whether it is a NetworkManager's bug, a resolvconf's bug, or a systemd bug. Please help! :-) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1787374/+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 1773859] Re: upgrades to 18.04 fail
I just ran into this during do-release-upgrade from 16.04.5 to 18.04.1 as well among other issues. The suggested mv solution worked. I ended up in a situation where some to-be-upgraded packages like network-manager-gnome were removed at first but never reinstalled, which turned out to be problematic, although I'm not certain it was this interruption's fault that apt somehow "forgot". -- 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/1773859 Title: upgrades to 18.04 fail Status in systemd package in Ubuntu: Confirmed Status in systemd-shim package in Ubuntu: Incomplete Status in systemd source package in Bionic: Confirmed Status in systemd-shim source package in Bionic: Confirmed Bug description: $ sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be REMOVED: systemd-shim 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 71.7 kB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 63 files and directories currently installed.) Removing systemd-shim (9-1bzr4ubuntu1) ... Removing 'diversion of /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by systemd-shim' dpkg-divert: error: rename involves overwriting '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with different file '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', not allowed dpkg: error processing package systemd-shim (--remove): subprocess installed post-removal script returned error exit status 2 Errors were encountered while processing: systemd-shim E: Sub-process /usr/bin/dpkg returned an error code (1) Commenting out the dpkg-divert in systemd-shim's postrm solved this for me and I was about to continue the upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1773859/+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 1787297] Re: Clock : incorrect date format in FR in Unity panel …bionic.
Ah I forgot, For your own custom time format, you need to first set `time-format` from 'locale-default' to 'custom'. You can customize the format as long as they are understood by strftime. http://manpages.ubuntu.com/strftime -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1787297 Title: Clock : incorrect date format in FR in Unity panel …bionic. Status in indicator-datetime package in Ubuntu: New Status in unity package in Ubuntu: Invalid Bug description: Hi, Here is Ubuntu 18.04 with Unity session ( I know… ) System language and regional settings are set to French. In regional setting the date reads day number month year hour minute… which is correct for French. But the clock in the Unity panel reads day month number year hour minute… which looks more English than French order. Any config file I might edit to make my clock « more French » ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1787297/+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 1787365] [NEW] Nautilus hangs when using the location bar
Public bug reported: After updating to 18.04 from 16.04, every time I try to type a character that's not a letter or a number in the nautilus location bar, like "/" or "~", it hangs. Something related to this happens with the calculator. The attachment is after opening it over the window where I'm typing this. Firefox also just crashed while typing this, so maybe it's also related. https://crash-stats.mozilla.com/report/index/7dd510f7-fbaa-4554-8ccc-0b2530180816 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.2 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:Unity7:ubuntu Date: Thu Aug 16 11:27:37 2018 DistUpgraded: 2018-08-06 11:31:08,622 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller [103c:1497] InstallationDate: Installed on 2016-05-30 (808 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) MachineType: Hewlett-Packard HP Compaq 6200 Pro SFF PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=06ad5aeb-7d23-4cb7-8bda-fc035ae54b4b ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-08-06 (9 days ago) dmi.bios.date: 09/20/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J01 v02.24 dmi.board.asset.tag: MXL2401SD8 dmi.board.name: 1497 dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: MXL2401SD8 dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ01v02.24:bd09/20/2013:svnHewlett-Packard:pnHPCompaq6200ProSFFPC:pvr:rvnHewlett-Packard:rn1497:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP Compaq 6200 Pro SFF PC dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Thu Aug 16 10:39:21 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic compiz-0.9 third-party-packages ubuntu ** Attachment added: "Selection_004.jpg" https://bugs.launchpad.net/bugs/1787365/+attachment/5176225/+files/Selection_004.jpg ** Description changed: After updating to 18.04 from 16.04, every time I try to type a character - that's not a letter or a number on the location bar, like "/" or "~", it - hangs. + that's not a letter or a number in the nautilus location bar, like "/" + or "~", it hangs. Something related to this happens with the calculator. The attachment is after opening it over the window where I'm typing this. Firefox also just crashed while typing this, so maybe it's also related. https://crash-stats.mozilla.com/report/index/7dd510f7-fbaa-4554-8ccc-0b2530180816 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 .tmp.unity_support_test.0: - + ApportVersion: 2.20.9-0ubuntu7.2 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:Unity7:ubuntu Date: Thu Aug 16 11:27:37 2018 DistUpgraded: 2018-08-06 11:31:08,622 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: - Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) -Subsystem: Hewlett-Packard Company 2nd
[Touch-packages] [Bug 1787297] Re: Clock : incorrect date format in FR in Unity panel …bionic.
For me it works though. What is the output of `locale` ? It is possible that indicator-datetime is not building with language packs. Do you have "french" installed? If not you can install it from System language and regional settings. Also check if you have geoclue installed. 1) Install dconf-editor. 2) Go to /com/canonical/indicator/datetime 3) Check timezone name 4) You can change time-format with "custom-time-format" key ** Also affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New ** Changed in: unity (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1787297 Title: Clock : incorrect date format in FR in Unity panel …bionic. Status in indicator-datetime package in Ubuntu: New Status in unity package in Ubuntu: Invalid Bug description: Hi, Here is Ubuntu 18.04 with Unity session ( I know… ) System language and regional settings are set to French. In regional setting the date reads day number month year hour minute… which is correct for French. But the clock in the Unity panel reads day month number year hour minute… which looks more English than French order. Any config file I might edit to make my clock « more French » ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1787297/+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 1787362] Re: gnome-shell UI unresponsive
** Summary changed: - gnome-shell crash, UI unresponsive + gnome-shell UI unresponsive ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Tags added: no-click ** Tags removed: no-click ** Tags added: noclick -- 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/1787362 Title: gnome-shell UI unresponsive Status in gnome-shell package in Ubuntu: Incomplete Bug description: Whilst working normally, I was unable to interact with gnome-shell. The clock at the top of the screen continued to increment, and I could ssh in to the machine, but clicking anywhere on the screen resulted in nothing. Changing to another VTY and back again had no effect. I logged in via ssh, killed gnome-shell and re-ran it using 'DISPLAY=:0.0 gnome-shell' which resolved the problem enough for me to save work and reboot. The following appeared in syslog - the crash was possibly around 1001: Aug 16 10:02:17 angel gnome-shell[2530]: pushModal: invocation of begin_modal failed Aug 16 10:04:45 angel gnome-shell[2530]: g_array_unref: assertion 'array' failed Aug 16 10:04:45 angel gnome-shell[2530]: g_array_unref: assertion 'array' failed Aug 16 10:04:45 angel gnome-shell[2530]: g_array_unref: assertion 'array' failed Aug 16 10:04:45 angel gnome-shell[2530]: g_array_unref: assertion 'array' failed Aug 16 10:04:45 angel gnome-shell[2530]: message repeated 2 times: [ g_array_unref: assertion 'array' failed] Aug 16 10:04:54 angel gnome-shell[2530]: g_array_unref: assertion 'array' failed Aug 16 10:04:54 angel gnome-shell[2530]: g_array_unref: assertion 'array' failed Aug 16 10:05:45 angel gnome-shell[2530]: Object St.Bin (0x55efe0934460), has been already finalized. Impossible to set any property to it. Aug 16 10:05:45 angel gnome-shell[2530]: Object St.Bin (0x55efe0934460), has been already finalized. Impossible to set any property to it. Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: == Stack trace for context 0x55efd9792340 == Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #0 0x55efd9bb42a0 i resource:///org/gnome/shell/ui/userWidget.js:59 (0x7f1d3c555b38 @ 212) Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #1 0x55efd9bb41f8 i resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f1d5c0b5de0 @ 71) Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #2 0x55efd9bb4178 i resource:///org/gnome/shell/ui/components/polkitAgent.js:342 (0x7f1cc1869ab0 @ 59) Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #3 0x55efd9bb40d0 i resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f1d5c0b5de0 @ 71) Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #4 0x55efd9bb4010 i self-hosted:915 (0x7f1d5c0f12b8 @ 367) Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: == Stack trace for context 0x55efd9792340 == Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #0 0x55efd9bb42a0 i resource:///org/gnome/shell/ui/userWidget.js:60 (0x7f1d3c555b38 @ 274) Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #1 0x55efd9bb41f8 i resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f1d5c0b5de0 @ 71) Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #2 0x55efd9bb4178 i resource:///org/gnome/shell/ui/components/polkitAgent.js:342 (0x7f1cc1869ab0 @ 59) Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #3 0x55efd9bb40d0 i resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f1d5c0b5de0 @ 71) Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #4 0x55efd9bb4010 i self-hosted:915 (0x7f1d5c0f12b8 @ 367) Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: == Stack trace for context 0x55efd9792340 == Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #0 0x55efd9bb42a0 i resource:///org/gnome/shell/ui/userWidget.js:65 (0x7f1d3c555b38 @ 365) Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #1 0x55efd9bb41f8 i resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f1d5c0b5de0 @ 71) Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #2 0x55efd9bb4178 i resource:///org/gnome/shell/ui/components/polkitAgent.js:342 (0x7f1cc1869ab0 @ 59) Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #3 0x55efd9bb40d0 i resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f1d5c0b5de0 @ 71) Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #4 0x55efd9bb4010 i self-hosted:915 (0x7f1d5c0f12b8 @ 367) Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: == Stack trace for context 0x55efd9792340 == Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #0 0x55efd9bb4178 i resource:///org/gnome/shell/ui/components/polkitAgent.js:343 (0x7f1cc1869ab0 @ 84) Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #1 0x55efd9bb40d0 i resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f1d5c0b5de0 @ 71) Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #2 0x55efd9bb4010 i self-hosted:915
[Touch-packages] [Bug 1787359] Re: Update to 1.1.6
Daniel, could you have a look to this one? ** Changed in: alsa-utils (Ubuntu) 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 alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/1787359 Title: Update to 1.1.6 Status in alsa-utils package in Ubuntu: New Bug description: There is a new version available, would be nice to get it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1787359/+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 1787359] [NEW] Update to 1.1.6
Public bug reported: There is a new version available, would be nice to get it ** Affects: alsa-utils (Ubuntu) Importance: Wishlist Assignee: Daniel van Vugt (vanvugt) Status: New ** Tags: upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/1787359 Title: Update to 1.1.6 Status in alsa-utils package in Ubuntu: New Bug description: There is a new version available, would be nice to get it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1787359/+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 1787362] [NEW] gnome-shell crash, UI unresponsive
Public bug reported: Whilst working normally, I was unable to interact with gnome-shell. The clock at the top of the screen continued to increment, and I could ssh in to the machine, but clicking anywhere on the screen resulted in nothing. Changing to another VTY and back again had no effect. I logged in via ssh, killed gnome-shell and re-ran it using 'DISPLAY=:0.0 gnome-shell' which resolved the problem enough for me to save work and reboot. The following appeared in syslog - the crash was possibly around 1001: Aug 16 10:02:17 angel gnome-shell[2530]: pushModal: invocation of begin_modal failed Aug 16 10:04:45 angel gnome-shell[2530]: g_array_unref: assertion 'array' failed Aug 16 10:04:45 angel gnome-shell[2530]: g_array_unref: assertion 'array' failed Aug 16 10:04:45 angel gnome-shell[2530]: g_array_unref: assertion 'array' failed Aug 16 10:04:45 angel gnome-shell[2530]: g_array_unref: assertion 'array' failed Aug 16 10:04:45 angel gnome-shell[2530]: message repeated 2 times: [ g_array_unref: assertion 'array' failed] Aug 16 10:04:54 angel gnome-shell[2530]: g_array_unref: assertion 'array' failed Aug 16 10:04:54 angel gnome-shell[2530]: g_array_unref: assertion 'array' failed Aug 16 10:05:45 angel gnome-shell[2530]: Object St.Bin (0x55efe0934460), has been already finalized. Impossible to set any property to it. Aug 16 10:05:45 angel gnome-shell[2530]: Object St.Bin (0x55efe0934460), has been already finalized. Impossible to set any property to it. Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: == Stack trace for context 0x55efd9792340 == Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #0 0x55efd9bb42a0 i resource:///org/gnome/shell/ui/userWidget.js:59 (0x7f1d3c555b38 @ 212) Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #1 0x55efd9bb41f8 i resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f1d5c0b5de0 @ 71) Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #2 0x55efd9bb4178 i resource:///org/gnome/shell/ui/components/polkitAgent.js:342 (0x7f1cc1869ab0 @ 59) Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #3 0x55efd9bb40d0 i resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f1d5c0b5de0 @ 71) Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #4 0x55efd9bb4010 i self-hosted:915 (0x7f1d5c0f12b8 @ 367) Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: == Stack trace for context 0x55efd9792340 == Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #0 0x55efd9bb42a0 i resource:///org/gnome/shell/ui/userWidget.js:60 (0x7f1d3c555b38 @ 274) Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #1 0x55efd9bb41f8 i resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f1d5c0b5de0 @ 71) Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #2 0x55efd9bb4178 i resource:///org/gnome/shell/ui/components/polkitAgent.js:342 (0x7f1cc1869ab0 @ 59) Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #3 0x55efd9bb40d0 i resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f1d5c0b5de0 @ 71) Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #4 0x55efd9bb4010 i self-hosted:915 (0x7f1d5c0f12b8 @ 367) Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: == Stack trace for context 0x55efd9792340 == Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #0 0x55efd9bb42a0 i resource:///org/gnome/shell/ui/userWidget.js:65 (0x7f1d3c555b38 @ 365) Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #1 0x55efd9bb41f8 i resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f1d5c0b5de0 @ 71) Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #2 0x55efd9bb4178 i resource:///org/gnome/shell/ui/components/polkitAgent.js:342 (0x7f1cc1869ab0 @ 59) Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #3 0x55efd9bb40d0 i resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f1d5c0b5de0 @ 71) Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #4 0x55efd9bb4010 i self-hosted:915 (0x7f1d5c0f12b8 @ 367) Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: == Stack trace for context 0x55efd9792340 == Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #0 0x55efd9bb4178 i resource:///org/gnome/shell/ui/components/polkitAgent.js:343 (0x7f1cc1869ab0 @ 84) Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #1 0x55efd9bb40d0 i resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f1d5c0b5de0 @ 71) Aug 16 10:05:45 angel org.gnome.Shell.desktop[2530]: #2 0x55efd9bb4010 i self-hosted:915 (0x7f1d5c0f12b8 @ 367) Aug 16 10:05:45 angel gnome-shell[2530]: Object St.Bin (0x55efe0934460), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Aug 16 10:05:45 angel gnome-shell[2530]: Object St.Bin (0x55efe0934460), has been already deallocated - impossible to access to it. This might be caused by the fact that the object has been destroyed from C code using something such as destroy(), dispose(), or remove()
[Touch-packages] [Bug 1086783] Re: New PolicyKit 0.106 changes configuration file format
** Tags added: version-blocked -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1086783 Title: New PolicyKit 0.106 changes configuration file format Status in policykit-1 package in Ubuntu: Triaged Status in policykit-1 package in Debian: Fix Released Bug description: From the NEWS file: This is polkit 0.106. There's a major change in this release which is a switch from .pkla files (keyfile-format) to .rules files (JavaScript). We may want to hold off on the new version because it requires rewriting the configuration files, and adds a dependency on mozjs185, which will need a MIR (and getting a MIR may be problematic) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1086783/+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 1787354] Re: Add modified german keyboard layout for programming to reduce RSI
Patch for evdev.xml ** Patch added: "evdev.xml.patch" https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1787354/+attachment/5176179/+files/evdev.xml.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1787354 Title: Add modified german keyboard layout for programming to reduce RSI Status in ubuntu-meta package in Ubuntu: New Bug description: I'm a software developer writing quite a lot of code. The way the german keybooard is layed out, some essential keys like brackets and backslash are very awkward to type (right hand holding Alt-GR in bottom row and pressing the key right of the 0-key in top row to get a backslash). After years of doing this, i started to suffer from RSI (repetitive strain injury). I'm attaching a patch for an additional keyboard layout that puts all those hard to reach one-handed brackets, braces and backslash on the Umlaut keys. The Umlauts are still available in their normal place through Alt-GR for occasional use, but i mostly use Scroll-Lock to switch to an unmodified no-deadkeys layout when typing german text. I have been using this layout now for 3 years, and it has greatly reduced suffering, while still enabling me to do my job. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1787354/+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 1787354] [NEW] Add modified german keyboard layout for programming to reduce RSI
Public bug reported: I'm a software developer writing quite a lot of code. The way the german keybooard is layed out, some essential keys like brackets and backslash are very awkward to type (right hand holding Alt- GR in bottom row and pressing the key right of the 0-key in top row to get a backslash). After years of doing this, i started to suffer from RSI (repetitive strain injury). I'm attaching a patch for an additional keyboard layout that puts all those hard to reach one-handed brackets, braces and backslash on the Umlaut keys. The Umlauts are still available in their normal place through Alt-GR for occasional use, but i mostly use Scroll-Lock to switch to an unmodified no-deadkeys layout when typing german text. I have been using this layout now for 3 years, and it has greatly reduced suffering, while still enabling me to do my job. ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Patch added: "Patch for german keyboard layout file" https://bugs.launchpad.net/bugs/1787354/+attachment/5176178/+files/de.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1787354 Title: Add modified german keyboard layout for programming to reduce RSI Status in ubuntu-meta package in Ubuntu: New Bug description: I'm a software developer writing quite a lot of code. The way the german keybooard is layed out, some essential keys like brackets and backslash are very awkward to type (right hand holding Alt-GR in bottom row and pressing the key right of the 0-key in top row to get a backslash). After years of doing this, i started to suffer from RSI (repetitive strain injury). I'm attaching a patch for an additional keyboard layout that puts all those hard to reach one-handed brackets, braces and backslash on the Umlaut keys. The Umlauts are still available in their normal place through Alt-GR for occasional use, but i mostly use Scroll-Lock to switch to an unmodified no-deadkeys layout when typing german text. I have been using this layout now for 3 years, and it has greatly reduced suffering, while still enabling me to do my job. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1787354/+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 1787349] [NEW] postgresql-plperl-9.5 blocks do-release-upgrade from 16.04 to 18.04
Public bug reported: The packet postgresql-plperl (and probably other addon packages for postgresql) blocks do-release-upgrade from 16.04LTS to 18.04LTS. This requiresthen requires a complete dump-and-restore cycle: 1) Stop user applications 2) do a full database export 3) stop postgresql 4) uninstall postgresql and all subpackages 5) delete remaining tablespace directories 6) do-release-upgrade 7) reinstall postgresql and the required subpackages 8) restore database from backup 9) start user applications This requires a much longer downtime than just using pg_upgradecluster, because the database is offline during the whole do-release-upgrade cycle. ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1787349 Title: postgresql-plperl-9.5 blocks do-release-upgrade from 16.04 to 18.04 Status in ubuntu-meta package in Ubuntu: New Bug description: The packet postgresql-plperl (and probably other addon packages for postgresql) blocks do-release-upgrade from 16.04LTS to 18.04LTS. This requiresthen requires a complete dump-and-restore cycle: 1) Stop user applications 2) do a full database export 3) stop postgresql 4) uninstall postgresql and all subpackages 5) delete remaining tablespace directories 6) do-release-upgrade 7) reinstall postgresql and the required subpackages 8) restore database from backup 9) start user applications This requires a much longer downtime than just using pg_upgradecluster, because the database is offline during the whole do-release-upgrade cycle. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1787349/+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 1786465] Re: package util-linux 2.27.1-6ubuntu3.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Thank You, it works Am 15.08.2018 um 16:59 schrieb Phillip Susi: > You have a broken third party init script named ".depend.boot" and > ".depend.start" that you will need to remove. > > > ** Changed in: util-linux (Ubuntu) > Status: New => Invalid > -- 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/1786465 Title: package util-linux 2.27.1-6ubuntu3.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in util-linux package in Ubuntu: Invalid Bug description: I dont know, it was a automatic update ProblemType: Package DistroRelease: Ubuntu 16.04 Package: util-linux 2.27.1-6ubuntu3.6 ProcVersionSignature: Ubuntu 4.15.0-30.32~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Thu Aug 9 11:57:45 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2018-02-26 (164 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.27 SourcePackage: util-linux Title: package util-linux 2.27.1-6ubuntu3.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 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/1786465/+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 1676547] Re: No network connectivity (NIC unmanaged) after upgrade
This issue effects a manual (debootstrap) installation of 18.04.1. Ethernet devices are unmanaged by NetworkManager until a netplan configuration is added. -- 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/1676547 Title: No network connectivity (NIC unmanaged) after upgrade Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Yakkety: Fix Released Status in network-manager source package in Zesty: Fix Released Bug description: Impact -- When upgrading from Xenial (with all updates installed) to Yakkety/Zesty you will boot to a system without networking - sad! Test Case - 1) Boot a xenial desktop system 2) Ensure network-manager version 1.2.6-0ubuntu0.16.04.1 from -updates is installed 3) Upgrade to yakkety or zesty 3.5) Enable -proposed and download the new version of n-m "apt-get download network-manager" 4) Reboot 5) Observe you have no network If you install the version of network-manager from yakkety-proposed and then reboot you should have a network connection. 1) Boot a xenial desktop system. 2) ensure network-manager version 1.2.6-0ubuntu0.16.04.1 from -updates is installed. 3) Install nplan, configure to set up static network on an ethernet device using nplan. 4) Upgrade to yakkety or zesty 5) Reboot 6) Observe that your system is still being managed by networkd rather than NetworkManager. Regression Potential Any failure to manage ethernet or wireless devices after upgrade, or issues with the use of netplan in conjunction with NetworkManager should be investigated as potential regressions. For example, if after upgrading, ethernet devices are no longer managed, or if devices that should be explicitly ignored by NetworkManager due to existing user configuration are now managed, these would indicate a possible regression caused by this update. Original Description nplan was installed during the upgrade process but I had no network connectivity after upgrading. Apparently, no package wanted to manage my ethernet connection. ProblemType: BugDistroRelease: Ubuntu 16.10 Package: ubuntu-release-upgrader-core 1:16.10.10 ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17 Uname: Linux 4.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Mon Mar 27 11:34:04 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2013-01-16 (1531 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116) PackageArchitecture: allSourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to yakkety on 2017-03-17 (10 days ago) VarLogDistupgradeTermlog: modified.conffile..etc.update-manager.meta-release: [modified] mtime.conffile..etc.update-manager.meta-release: 2013-10-08T06:39:09.818913 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1676547/+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 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6
@hckrmagoo I had this problem as well, try making NetworkManager run OpenVPN as root: https://askubuntu.com/a/906055/844205. -- 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/1688018 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6 Status in network-manager package in Ubuntu: Triaged Status in network-manager source package in Xenial: In Progress Status in network-manager source package in Yakkety: Triaged Bug description: This was initially opened as #1671606 then later duped to #1639776. Discussion in #1639776 indicate that we need new bug for this so I am opening one ... Please don't mark this as duplicate to #1639776 or other similar bug report. We already lost several months and we are again at beginning ... TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from DHCP instead of one defined by VPN (wrong). DNS resolver should query only DNS servers defined by VPN while connection is active. = Test steps / result: - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 (dnsmasq-base-2.75-1ubuntu0.16.04.2) - restated my laptop to ensure clean start - connected to VPN using openconnect / network-manager-openconnect-gnome Observed results -> DNS queries are forwarded only to DNS servers defined by LAN connection (this is wrong / connection not working at all) - "killall dnsmasq" - dnsmasq get automatically restarted by system Observed results -> most of the the queries are forwarded to DNS servers defined by VPN, but lot of queries get forwarded to DNS servers defined by LAN connection (this is still wrong / DNS leaks, attacker can hijack connection even if VPN is enabled) - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base stay same) - restated my laptop to ensure clean test - connected to same VPN using openconnect Observed results -> DNS queries are forwarded only to DNS servers defined by VPN connection. There are no leaks to LAN DNS server (this is correct behavior). = Paul Smith requested additional details in #1639776. Here are: * If you're using IPv4 vs. IPv6 -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi /vpn) * If you have checked or unchecked the "Use this connection only for resources on its network" -> unchecked on all nw definition * If you have this checked, try unchecking it and see if that makes a difference -> no change if I toggle this option. Behavior is same. * When you say "DNS lookups" please be clear about whether the hostnames being looked up are public (e.g., www.google.com or whatever), on your local LAN, or in the network accessed via the VPN. Does it make a difference which one you choose? -> No difference. * Are you using fully-qualified hostnames, or relying on the DNS domain search path? Does it make a difference if you do it differently? -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see difference when I try same using hostname + domain search. = I am using openconnect (cisco) and openvpn. Test result are by using openconnect but I saw same behaviour also while using openvpn. = Thanks Lukas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1688018/+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 1787340] Re: package libjpeg-turbo8:amd64 1.5.2-0ubuntu5.18.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attemptin
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libjpeg-turbo in Ubuntu. https://bugs.launchpad.net/bugs/1787340 Title: package libjpeg-turbo8:amd64 1.5.2-0ubuntu5.18.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in libjpeg-turbo package in Ubuntu: New Bug description: NA ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libjpeg-turbo8:amd64 1.5.2-0ubuntu5.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 AptOrdering: google-chrome-stable:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Thu Aug 16 12:21:02 2018 Dependencies: gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 multiarch-support 2.27-3ubuntu1 DuplicateSignature: package:libjpeg-turbo8:amd64:1.5.2-0ubuntu5.18.04.1 Processing triggers for desktop-file-utils (0.23-1ubuntu3) ... dpkg: error processing package libjpeg-turbo8:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2018-05-12 (95 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: libjpeg-turbo Title: package libjpeg-turbo8:amd64 1.5.2-0ubuntu5.18.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1787340/+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 1787340] [NEW] package libjpeg-turbo8:amd64 1.5.2-0ubuntu5.18.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempt
Public bug reported: NA ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libjpeg-turbo8:amd64 1.5.2-0ubuntu5.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 AptOrdering: google-chrome-stable:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Thu Aug 16 12:21:02 2018 Dependencies: gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 multiarch-support 2.27-3ubuntu1 DuplicateSignature: package:libjpeg-turbo8:amd64:1.5.2-0ubuntu5.18.04.1 Processing triggers for desktop-file-utils (0.23-1ubuntu3) ... dpkg: error processing package libjpeg-turbo8:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2018-05-12 (95 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: libjpeg-turbo Title: package libjpeg-turbo8:amd64 1.5.2-0ubuntu5.18.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libjpeg-turbo (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libjpeg-turbo in Ubuntu. https://bugs.launchpad.net/bugs/1787340 Title: package libjpeg-turbo8:amd64 1.5.2-0ubuntu5.18.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in libjpeg-turbo package in Ubuntu: New Bug description: NA ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libjpeg-turbo8:amd64 1.5.2-0ubuntu5.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 AptOrdering: google-chrome-stable:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Thu Aug 16 12:21:02 2018 Dependencies: gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 multiarch-support 2.27-3ubuntu1 DuplicateSignature: package:libjpeg-turbo8:amd64:1.5.2-0ubuntu5.18.04.1 Processing triggers for desktop-file-utils (0.23-1ubuntu3) ... dpkg: error processing package libjpeg-turbo8:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2018-05-12 (95 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: libjpeg-turbo Title: package libjpeg-turbo8:amd64 1.5.2-0ubuntu5.18.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1787340/+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 1787324] Re: Snap policy module denies recording access to classic snaps
** Merge proposal linked: https://code.launchpad.net/~ubuntu-audio-dev/pulseaudio/+git/pulseaudio/+merge/353214 -- 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/1787324 Title: Snap policy module denies recording access to classic snaps Status in pulseaudio package in Ubuntu: Confirmed Bug description: With the recent updates to the snap policy module, recording access is denied to clients with a snap AppArmor label when that snap doesn't have a connected plug for "pulseaudio" or "audio-record". This is not appropriate for classic confinement snaps, which will have an AppArmor label but should still have access to recording even when there is no plug, as described by @jdstrand: https://forum.snapcraft.io/t/pulseaudio-recording/6361/14?u=jamesh This is broken with the 1:12.2-0ubuntu2 release, as can be seen with e.g.: $ aa-exec -p snap.skype.skype /usr/bin/parecord foo.wav Stream error: Access denied [note that the Skype app itself still functions because it bypasses PulseAudio all together] The above command should result in audio being recorded from the microphone. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1787324/+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 1787324] [NEW] Snap policy module denies recording access to classic snaps
Public bug reported: With the recent updates to the snap policy module, recording access is denied to clients with a snap AppArmor label when that snap doesn't have a connected plug for "pulseaudio" or "audio-record". This is not appropriate for classic confinement snaps, which will have an AppArmor label but should still have access to recording even when there is no plug, as described by @jdstrand: https://forum.snapcraft.io/t/pulseaudio-recording/6361/14?u=jamesh This is broken with the 1:12.2-0ubuntu2 release, as can be seen with e.g.: $ aa-exec -p snap.skype.skype /usr/bin/parecord foo.wav Stream error: Access denied [note that the Skype app itself still functions because it bypasses PulseAudio all together] The above command should result in audio being recorded from the microphone. ** Affects: pulseaudio (Ubuntu) Importance: High Assignee: James Henstridge (jamesh) Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1787324 Title: Snap policy module denies recording access to classic snaps Status in pulseaudio package in Ubuntu: Confirmed Bug description: With the recent updates to the snap policy module, recording access is denied to clients with a snap AppArmor label when that snap doesn't have a connected plug for "pulseaudio" or "audio-record". This is not appropriate for classic confinement snaps, which will have an AppArmor label but should still have access to recording even when there is no plug, as described by @jdstrand: https://forum.snapcraft.io/t/pulseaudio-recording/6361/14?u=jamesh This is broken with the 1:12.2-0ubuntu2 release, as can be seen with e.g.: $ aa-exec -p snap.skype.skype /usr/bin/parecord foo.wav Stream error: Access denied [note that the Skype app itself still functions because it bypasses PulseAudio all together] The above command should result in audio being recorded from the microphone. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1787324/+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
