[Touch-packages] [Bug 1648037] Re: Ubuntu 16.10: systemd-resolved does not resolve some domains
Possible duplicate of bug 1647031. For example, I see
$ dig +no{cmd,comments,stats} buy.ubuntu.com @8.8.8.8
;buy.ubuntu.com.IN A
buy.ubuntu.com. 599 IN CNAME
ubuntu-advantage-cloud-guest.myshopify.com.
ubuntu-advantage-cloud-guest.myshopify.com. 3599 IN CNAME shops.myshopify.com.
shops.myshopify.com.1799IN A 23.227.38.32
$ dig +no{cmd,comments,stats} buy.ubuntu.com @127.0.0.53
;buy.ubuntu.com.IN A
buy.ubuntu.com. 557 IN CNAME
ubuntu-advantage-cloud-guest.myshopify.com.
--
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/1648037
Title:
Ubuntu 16.10: systemd-resolved does not resolve some domains
Status in systemd package in Ubuntu:
Incomplete
Bug description:
Some domains are not resolved with default systemd-resolved set up on
Ubuntu 16.10. This set up is querying the DNS server given by DHCP,
and is my ISP's router.
Now, checking with `dig` directly against 192.168.1.1 (the router),
dig complains that "Warning: Message parser reports malformed message
packet.". And indeed, for the domains that do not resolve, this
warning is always given by dig, when I query the router.
It would appear that the router or its upstream is somehow breaking
the DNS packets/responses and I'll have to figure that one out
separately.
The bug here is that systemd-resolved is failing on those while every
other resolver seems to be working fine with those (supposedly
malformed) replies. All other devices in the network, phones, windows,
ubuntu 16.04, etc... are resolving with those just fine.
Most notably, I can't resolve "buy.ubuntu.com". I've captured the
packet/reply I get from my router, it's attached.
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: systemd 231-9ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
Uname: Linux 4.8.0-30-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm
nvidia_modeset nvidia
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Dec 7 11:17:43 2016
InstallationDate: Installed on 2016-11-28 (8 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
MachineType: ASUS All Series
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-30-generic
root=UUID=eb750983-a34c-4b58-b5f0-a0cfa1130d1b ro
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/04/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0504
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H81M-R
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.:bvr0504:bd06/04/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH81M-R:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: All Series
dmi.product.version: System Version
dmi.sys.vendor: ASUS
modified.conffile..etc.systemd.resolved.conf: [modified]
mtime.conffile..etc.systemd.resolved.conf: 2016-12-07T10:46:19.412121
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1648037/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1647178] Re: systemd-resolved unable to resolve certain subdomains
For example, I see
$ dig +no{cmd,comments,stats} mail.google.com @8.8.8.8
;mail.google.com. IN A
mail.google.com.86312 IN CNAME googlemail.l.google.com.
googlemail.l.google.com. 212IN A 216.58.219.229
$ dig +no{cmd,comments,stats} mail.google.com @127.0.0.53
;mail.google.com. IN A
mail.google.com.321204 IN CNAME googlemail.l.google.com.
--
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/1647178
Title:
systemd-resolved unable to resolve certain subdomains
Status in systemd package in Ubuntu:
Incomplete
Bug description:
After upgrade to systemd-resolved, certain very well known subdomains
are no longer resolved. Their TLD do resolve correctly. Example given
with mail.google.com and google.com
On xenial :
$ nslookup mail.google.com
Server: 192.168.1.1
Address:192.168.1.1#53
Non-authoritative answer:
mail.google.com canonical name = googlemail.l.google.com.
Name: googlemail.l.google.com
Address: 216.58.198.197
$ dig mail.google.com
; <<>> DiG 9.10.3-P4-Ubuntu <<>> mail.google.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 57929
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4000
;; QUESTION SECTION:
;mail.google.com. IN A
;; ANSWER SECTION:
mail.google.com.441512 IN CNAME googlemail.l.google.com.
googlemail.l.google.com. 274IN A 216.58.198.197
;; Query time: 14 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Sun Dec 04 18:12:43 CET 2016
;; MSG SIZE rcvd: 87
On Zesty using systemd-resolved :
# nslookup mail.google.com
Server: 10.0.3.1
Address:10.0.3.1#53
Non-authoritative answer:
mail.google.com canonical name = googlemail.l.google.com.
# nslookup google.com
Server: 10.0.3.1
Address:10.0.3.1#53
Non-authoritative answer:
Name: google.com
Address: 216.58.198.206
# dig mail.google.com
; <<>> DiG 9.10.3-P4-Ubuntu <<>> mail.google.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10775
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;mail.google.com. IN A
;; ANSWER SECTION:
mail.google.com.441414 IN CNAME googlemail.l.google.com.
;; Query time: 0 msec
;; SERVER: 10.0.3.1#53(10.0.3.1)
;; WHEN: Sun Dec 04 17:14:21 UTC 2016
;; MSG SIZE rcvd: 81
# dig google.com
; <<>> DiG 9.10.3-P4-Ubuntu <<>> google.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 25303
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;google.com.IN A
;; ANSWER SECTION:
google.com. 160 IN A 216.58.198.206
;; Query time: 0 msec
;; SERVER: 10.0.3.1#53(10.0.3.1)
;; WHEN: Sun Dec 04 17:14:37 UTC 2016
;; MSG SIZE rcvd: 55
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1647178/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1636573] Re: xinit flooding syslog
I can confirm that updating to python openssl package from Ubuntu 17.04 fixes this issue, after a couple of days running th e system the log file stays small in size. ** Also affects: pyopenssl (Ubuntu) Importance: Undecided Status: New ** Changed in: xorg (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: pyopenssl (Ubuntu) Status: New => Fix Committed -- 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/1636573 Title: xinit flooding syslog Status in pyopenssl package in Ubuntu: Fix Committed Status in xorg package in Ubuntu: Fix Committed Bug description: I am using xinit (1.3.4-3ubuntu1) to start an X11 session as follows (kodi is a media center): /usr/bin/xinit /usr/bin/dbus-launch --exit-with-session /usr/bin/kodi- standalone -- :1 -nolisten tcp vt8 This used to work fine with Ubuntu 16.04, but since the upgrade to 16.10 lots of log messages are sent to syslog. They are all repetitions of the following two lines: Oct 24 22:54:50 tiger xinit[26430]: extern "Python": function Cryptography_rand_bytes() called, but @ffi.def_extern() was not called in the current subinterpreter. Returning 0. Oct 24 22:54:50 tiger xinit[26430]: extern "Python": function Cryptography_rand_status() called, but @ffi.def_extern() was not called in the current subinterpreter. Returning 0. These messages amount to >200 GB per day, so this is eating up all the disk space. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: KDE Date: Tue Oct 25 18:41:22 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2012-01-06 (1753 days ago) InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to yakkety on 2016-10-13 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pyopenssl/+bug/1636573/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1647178] Re: systemd-resolved unable to resolve certain subdomains
Possible duplicate of bug 1647031. -- 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/1647178 Title: systemd-resolved unable to resolve certain subdomains Status in systemd package in Ubuntu: Incomplete Bug description: After upgrade to systemd-resolved, certain very well known subdomains are no longer resolved. Their TLD do resolve correctly. Example given with mail.google.com and google.com On xenial : $ nslookup mail.google.com Server: 192.168.1.1 Address:192.168.1.1#53 Non-authoritative answer: mail.google.com canonical name = googlemail.l.google.com. Name: googlemail.l.google.com Address: 216.58.198.197 $ dig mail.google.com ; <<>> DiG 9.10.3-P4-Ubuntu <<>> mail.google.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 57929 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4000 ;; QUESTION SECTION: ;mail.google.com. IN A ;; ANSWER SECTION: mail.google.com.441512 IN CNAME googlemail.l.google.com. googlemail.l.google.com. 274IN A 216.58.198.197 ;; Query time: 14 msec ;; SERVER: 192.168.1.1#53(192.168.1.1) ;; WHEN: Sun Dec 04 18:12:43 CET 2016 ;; MSG SIZE rcvd: 87 On Zesty using systemd-resolved : # nslookup mail.google.com Server: 10.0.3.1 Address:10.0.3.1#53 Non-authoritative answer: mail.google.com canonical name = googlemail.l.google.com. # nslookup google.com Server: 10.0.3.1 Address:10.0.3.1#53 Non-authoritative answer: Name: google.com Address: 216.58.198.206 # dig mail.google.com ; <<>> DiG 9.10.3-P4-Ubuntu <<>> mail.google.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10775 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;mail.google.com. IN A ;; ANSWER SECTION: mail.google.com.441414 IN CNAME googlemail.l.google.com. ;; Query time: 0 msec ;; SERVER: 10.0.3.1#53(10.0.3.1) ;; WHEN: Sun Dec 04 17:14:21 UTC 2016 ;; MSG SIZE rcvd: 81 # dig google.com ; <<>> DiG 9.10.3-P4-Ubuntu <<>> google.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 25303 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;google.com.IN A ;; ANSWER SECTION: google.com. 160 IN A 216.58.198.206 ;; Query time: 0 msec ;; SERVER: 10.0.3.1#53(10.0.3.1) ;; WHEN: Sun Dec 04 17:14:37 UTC 2016 ;; MSG SIZE rcvd: 55 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1647178/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1648942] [NEW] Sync libwebp 0.5.1-4 (main) from Debian unstable (main)
*** This bug is a security vulnerability *** Public security bug reported: Please sync libwebp 0.5.1-4 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * debian/patches/armhf_update_neon_support.patch: configure: do not rely on arm_neon.h for neon detection. Closes LP: #1630349. That change is included in 0.5.1-4. Changelog entries since current zesty version 0.5.1-2ubuntu1: libwebp (0.5.1-4) unstable; urgency=medium * Import armh compilation patch from Ubuntu (closes: #845749) -- Jeff Breidenbach Fri, 09 Dec 2016 10:42:47 -0800 libwebp (0.5.1-3) unstable; urgency=medium * Fix CVE-2016- and CVE-2016-9085 (closes: #842714) -- Jeff Breidenbach Wed, 09 Nov 2016 16:27:04 -0800 ** Affects: libwebp (Ubuntu) Importance: Wishlist Status: New ** Changed in: libwebp (Ubuntu) Importance: Undecided => Wishlist ** Information type changed from Public to Public Security ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2016- ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2016-9085 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libwebp in Ubuntu. https://bugs.launchpad.net/bugs/1648942 Title: Sync libwebp 0.5.1-4 (main) from Debian unstable (main) Status in libwebp package in Ubuntu: New Bug description: Please sync libwebp 0.5.1-4 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * debian/patches/armhf_update_neon_support.patch: configure: do not rely on arm_neon.h for neon detection. Closes LP: #1630349. That change is included in 0.5.1-4. Changelog entries since current zesty version 0.5.1-2ubuntu1: libwebp (0.5.1-4) unstable; urgency=medium * Import armh compilation patch from Ubuntu (closes: #845749) -- Jeff Breidenbach Fri, 09 Dec 2016 10:42:47 -0800 libwebp (0.5.1-3) unstable; urgency=medium * Fix CVE-2016- and CVE-2016-9085 (closes: #842714) -- Jeff Breidenbach Wed, 09 Nov 2016 16:27:04 -0800 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libwebp/+bug/1648942/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624320] Re: systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing entries
Martin: I still wonder what the point of having resolvconf is, if it’s only ever supposed to be used to manage 127.0.0.53, and every other use of resolvconf will lead to this bug resurfacing. I still propose that systemd-resolved should read from /run/resolvconf/resolv.conf without adding 127.0.0.53 to it, and /etc/resolv.conf should be a symlink to /lib/systemd/resolv.conf rather than /run/resolvconf/resolv.conf. Willem: If systemd-resolved isn’t suitable to be the only nameserver in resolv.conf, then it isn’t suitable to be in resolv.conf at all. I would rather either see these bugs worked out during the zesty cycle, or have systemd-resolved removed entirely, than leave the system in a half-broken state where the bugs in systemd-resolved get (probabilistically?) masked by the presence of other nameservers in resolv.conf. In its current state, systemd-resolved is thoroughly broken on account of (at least) bug 1647031. I had to downgrade network-manager because switching to a resolver that doesn’t follow CNAME records breaks way too much of the internet. This might not have been noticed with other nameservers in resolv.conf. (Although now that it has, I’m getting increasingly concerned by the switch not having been reverted yet…) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1624320 Title: systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing entries Status in systemd package in Ubuntu: Incomplete Bug description: systemd-resolved, or more precisely the hook script /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf, causes resolvconf to add 127.0.0.53 to the set of nameservers in /etc/resolv.conf alongside the other nameservers. That makes no sense because systemd-resolved sets up 127.0.0.53 as a proxy for those other nameservers. The effect is similar to bug 1624071 but for applications doing their own DNS lookups. It breaks any DNSSEC validation that systemd-resolved tries to do; applications will failover to the other nameservers, bypassing validation failures. And it makes failing queries take twice as long. /etc/resolv.conf should have only 127.0.0.53 when systemd-resolved is active. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624320/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1626454] Re: can't connect with owncloud calendars
OTA-14: - I also still can't use special chars in my password. - ssl works fine whit my system though... I use a ssl certificate of letsencrytp, so my certificate is not selfsigned. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1626454 Title: can't connect with owncloud calendars Status in Canonical System Image: Fix Released Status in Ubuntu Calendar App: New Status in account-plugins package in Ubuntu: Fix Released Bug description: Running my own ownCloud (v9.1.1). Tried to connect Aquarius 4.5 with Calendar App The httpS certificate is official, up to date and not self-signed I use 7 calendars in my ownCloud-calendar-app. (yes, username and password is correct) This I tried: https://mydomain/owncloud/(suggested minimal path on the phone) Error message: Invalid username or password https://mydomain/owncloud/remote.php/ Error message: Invalid host URL https://mydomain/owncloud/remote.php/dav/ --> (This is the primary caldav address suggested by ownCloud calendar-app) Error message: Invalid host URL https://mydomain/owncloud/remote.php/dav/calendars/ Error message: Invalid host URL https://mydomain/owncloud/remote.php/dav/calendars/MYUSERNAME/ Error message: Invalid host URL https://mydomain/owncloud/remote.php/dav/calendars/MYUSERNAME/MYCALENDARNAME/ Error message: Invalid host URL --> This direct path to one of my calendars I use for example to connect my different calendars with Thunderbird lightning (its working) I tried all with and without ending "/" To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1626454/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1644994] Re: Flickering at logon, exessive CPU usage
Issue fixed since update with Linux 4.4.0.53 (there were another updates in the same pack) ** Changed in: xorg (Ubuntu) Status: New => Fix Released -- 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/1644994 Title: Flickering at logon, exessive CPU usage Status in xorg package in Ubuntu: Fix Released Bug description: At the logon, I'm noticing some random screen flickering on 90 % of the screen surface. During the session, the CPU is used by Xorg, Compiz and the applications which are displayed up to 100 % (one core). See attached screen shot as an example. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1 Uname: Linux 4.8.0-27-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Nov 26 14:46:54 2016 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer 2nd Generation Core Processor Family Integrated Graphics Controller [1297:4018] InstallationDate: Installed on 2016-04-23 (217 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Shuttle Inc. DS47D ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic root=UUID=514d94c8-1d34-422f-9230-fd44e2b92bdd ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/14/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.06 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: FS47D dmi.board.vendor: Shuttle Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.06:bd07/14/2014:svnShuttleInc.:pnDS47D:pvrV1.0:rvnShuttleInc.:rnFS47D:rvr1.0:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.: dmi.product.name: DS47D dmi.product.version: V1.0 dmi.sys.vendor: Shuttle Inc. version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Sat Nov 26 11:49:31 2016 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputVideo BusKEYBOARD, id 7 inputPower Button KEYBOARD, id 8 inputHOLTEK Wireless USB Device KEYBOARD, id 9 inputHOLTEK Wireless USB Device KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1644994/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1647178] Re: systemd-resolved unable to resolve certain subdomains
*** This bug is a duplicate of bug 1647031 *** https://bugs.launchpad.net/bugs/1647031 It definitively is. Thanks for spotting this ** This bug has been marked a duplicate of bug 1647031 systemd-resolved’s 127.0.0.53 server does not follow CNAME records -- 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/1647178 Title: systemd-resolved unable to resolve certain subdomains Status in systemd package in Ubuntu: Incomplete Bug description: After upgrade to systemd-resolved, certain very well known subdomains are no longer resolved. Their TLD do resolve correctly. Example given with mail.google.com and google.com On xenial : $ nslookup mail.google.com Server: 192.168.1.1 Address:192.168.1.1#53 Non-authoritative answer: mail.google.com canonical name = googlemail.l.google.com. Name: googlemail.l.google.com Address: 216.58.198.197 $ dig mail.google.com ; <<>> DiG 9.10.3-P4-Ubuntu <<>> mail.google.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 57929 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4000 ;; QUESTION SECTION: ;mail.google.com. IN A ;; ANSWER SECTION: mail.google.com.441512 IN CNAME googlemail.l.google.com. googlemail.l.google.com. 274IN A 216.58.198.197 ;; Query time: 14 msec ;; SERVER: 192.168.1.1#53(192.168.1.1) ;; WHEN: Sun Dec 04 18:12:43 CET 2016 ;; MSG SIZE rcvd: 87 On Zesty using systemd-resolved : # nslookup mail.google.com Server: 10.0.3.1 Address:10.0.3.1#53 Non-authoritative answer: mail.google.com canonical name = googlemail.l.google.com. # nslookup google.com Server: 10.0.3.1 Address:10.0.3.1#53 Non-authoritative answer: Name: google.com Address: 216.58.198.206 # dig mail.google.com ; <<>> DiG 9.10.3-P4-Ubuntu <<>> mail.google.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10775 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;mail.google.com. IN A ;; ANSWER SECTION: mail.google.com.441414 IN CNAME googlemail.l.google.com. ;; Query time: 0 msec ;; SERVER: 10.0.3.1#53(10.0.3.1) ;; WHEN: Sun Dec 04 17:14:21 UTC 2016 ;; MSG SIZE rcvd: 81 # dig google.com ; <<>> DiG 9.10.3-P4-Ubuntu <<>> google.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 25303 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;google.com.IN A ;; ANSWER SECTION: google.com. 160 IN A 216.58.198.206 ;; Query time: 0 msec ;; SERVER: 10.0.3.1#53(10.0.3.1) ;; WHEN: Sun Dec 04 17:14:37 UTC 2016 ;; MSG SIZE rcvd: 55 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1647178/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1648911] Re: package procps 2:3.3.10-4ubuntu2.3 failed to install/upgrade: package procps is already installed and configured
*** This bug is a duplicate of bug 1635280 *** https://bugs.launchpad.net/bugs/1635280 ** This bug has been marked a duplicate of bug 1635280 [ BUG 541595 IS BACK ] package is already installed and configured -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1648911 Title: package procps 2:3.3.10-4ubuntu2.3 failed to install/upgrade: package procps is already installed and configured Status in procps package in Ubuntu: New Bug description: i dont know. it will freeze the system ProblemType: Package DistroRelease: Ubuntu 16.04 Package: procps 2:3.3.10-4ubuntu2.3 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 AptdaemonVersion: 1.1.1+bzr982-0ubuntu14 Architecture: amd64 CrashReports: 640:0:117:1811831:2016-12-09 16:30:19.293612480 -0800:2016-12-09 16:30:20.293612480 -0800:/var/crash/libprocps4:amd64.0.crash 600:0:117:289456:2016-12-09 15:33:26.245213508 -0800:2016-12-09 15:33:27.245213508 -0800:/var/crash/udev.0.crash 600:110:117:0:2016-12-09 16:30:35.885889755 -0800:2016-12-09 16:30:35.885889755 -0800:/var/crash/libprocps4:amd64.0.uploaded 644:0:117:0:2016-12-09 16:30:28.625485733 -0800:2016-12-09 16:30:28.625485733 -0800:/var/crash/libprocps4:amd64.0.upload 600:0:117:289465:2016-12-09 15:33:26.217213392 -0800:2016-12-09 15:33:27.217213392 -0800:/var/crash/procps.0.crash Date: Fri Dec 9 15:33:27 2016 DuplicateSignature: package:procps:2:3.3.10-4ubuntu2.3 Unpacking thunderbird-locale-en-gb (1:45.5.1+build1-0ubuntu0.16.04.1) ... dpkg: error processing package libprocps4:amd64 (--configure): package libprocps4:amd64 is already installed and configured ErrorMessage: package procps is already installed and configured InstallationDate: Installed on 2016-12-09 (0 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: procps Title: package procps 2:3.3.10-4ubuntu2.3 failed to install/upgrade: package procps is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1648911/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1633845] Re: network-manager does not connect to wifi
*** This bug is a duplicate of bug 1642507 *** https://bugs.launchpad.net/bugs/1642507 ** This bug has been marked a duplicate of bug 1642507 Not internet after waking from suspend -- 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/1633845 Title: network-manager does not connect to wifi Status in network-manager package in Ubuntu: Confirmed Bug description: When trying to connect to wifi network, network-manager remains blocked in waiting for authentification state then fails after cca 1min. This started to happen after I updated to kubuntu 16.10. Stopping network manager from service and trying to manually connect with wpa_supplicant works fine. The only way to fix this for me was to stop network manager and/or networking and restart the services sometimes more than once. os: Kubuntu 16.10 network-manager: 1.2.4 hardware: dell xps 9550 network controller: BCM43602 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1633845/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1648955] [NEW] package initramfs-tools 0.122ubuntu8.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: while installing updates via Software Updater Ubuntu version:16.04.1 LTS (website version) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: initramfs-tools 0.122ubuntu8.1 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Sat Dec 10 10:16:06 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 1 PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.122ubuntu8.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1648955 Title: package initramfs-tools 0.122ubuntu8.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: while installing updates via Software Updater Ubuntu version:16.04.1 LTS (website version) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: initramfs-tools 0.122ubuntu8.1 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Sat Dec 10 10:16:06 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 1 PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.122ubuntu8.1 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/initramfs-tools/+bug/1648955/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1461934] [NEW] vlc assert failure: vlc: dri2_util.c:199: isDRI2Connected: Zusicherung »dri_state->base.fd >= 0« nicht erfüllt.
You have been subscribed to a public bug: crashed after opening a video file in Thunar ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: vlc-nox 2.2.0-1 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AssertionMessage: vlc: dri2_util.c:199: isDRI2Connected: Zusicherung »dri_state->base.fd >= 0« nicht erfüllt. CurrentDesktop: XFCE Date: Thu Jun 4 14:42:30 2015 ExecutablePath: /usr/bin/vlc InstallationDate: Installed on 2015-05-28 (6 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1) ProcCmdline: /usr/bin/vlc --started-from-file /home/username/Videos/movie.mp4 Signal: 6 SourcePackage: vlc StacktraceTop: __assert_fail_base (fmt=0x7fe4397c112e , assertion=assertion@entry=0x7fe3ee024824 "dri_state->base.fd >= 0", file=file@entry=0x7fe3ee024810 "dri2_util.c", line=line@entry=199, function=function@entry=0x7fe3ee024860 "isDRI2Connected") at assert.c:92 __GI___assert_fail (assertion=0x7fe3ee024824 "dri_state->base.fd >= 0", file=0x7fe3ee024810 "dri2_util.c", line=199, function=0x7fe3ee024860 "isDRI2Connected") at assert.c:101 isDRI2Connected () from /usr/lib/x86_64-linux-gnu/libva-x11.so.1 ?? () from /usr/lib/x86_64-linux-gnu/libva-x11.so.1 vaInitialize () from /usr/lib/x86_64-linux-gnu/libva.so.1 Title: vlc assert failure: vlc: dri2_util.c:199: isDRI2Connected: Zusicherung »dri_state->base.fd >= 0« nicht erfüllt. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Affects: libva (Ubuntu) Importance: Medium Status: Fix Released ** Tags: amd64 apport-crash third-party-packages vivid -- vlc assert failure: vlc: dri2_util.c:199: isDRI2Connected: Zusicherung »dri_state->base.fd >= 0« nicht erfüllt. https://bugs.launchpad.net/bugs/1461934 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libva 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 1648037] Re: Ubuntu 16.10: systemd-resolved does not resolve some domains
Anders, I don't think it's a duplicate of that bug. I can resolve CNAMEs just fine with systemd-resolve. The problem that I saw was with domains that dig otherwise returned the "Message malformed" complaint. -- 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/1648037 Title: Ubuntu 16.10: systemd-resolved does not resolve some domains Status in systemd package in Ubuntu: Incomplete Bug description: Some domains are not resolved with default systemd-resolved set up on Ubuntu 16.10. This set up is querying the DNS server given by DHCP, and is my ISP's router. Now, checking with `dig` directly against 192.168.1.1 (the router), dig complains that "Warning: Message parser reports malformed message packet.". And indeed, for the domains that do not resolve, this warning is always given by dig, when I query the router. It would appear that the router or its upstream is somehow breaking the DNS packets/responses and I'll have to figure that one out separately. The bug here is that systemd-resolved is failing on those while every other resolver seems to be working fine with those (supposedly malformed) replies. All other devices in the network, phones, windows, ubuntu 16.04, etc... are resolving with those just fine. Most notably, I can't resolve "buy.ubuntu.com". I've captured the packet/reply I get from my router, it's attached. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: systemd 231-9ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Wed Dec 7 11:17:43 2016 InstallationDate: Installed on 2016-11-28 (8 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-30-generic root=UUID=eb750983-a34c-4b58-b5f0-a0cfa1130d1b ro SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/04/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0504 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-R 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.:bvr0504:bd06/04/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH81M-R:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS modified.conffile..etc.systemd.resolved.conf: [modified] mtime.conffile..etc.systemd.resolved.conf: 2016-12-07T10:46:19.412121 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1648037/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1555836] [NEW] vlc crashed with SIGSEGV in QXcbWindow::mapToNative()
You have been subscribed to a public bug: i press esc to exit the fullscreen and i did get this error ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: vlc-nox 2.2.2-4 ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4 Uname: Linux 4.4.0-11-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Fri Mar 11 00:24:40 2016 Disassembly: => 0x115: Cannot access memory at address 0x115 ExecutablePath: /usr/bin/vlc InstallationDate: Installed on 2016-03-10 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) ProcCmdline: /usr/bin/vlc --no-video-title-show http://127.0.0.1:42241/ SegvAnalysis: Segfault happened at: 0x115: Cannot access memory at address 0x115 PC (0x0115) not located in a known VMA region (needed executable region)! Stack memory exhausted (SP below stack segment) SegvReason: executing NULL VMA Signal: 11 SourcePackage: vlc StacktraceTop: ?? () QXcbWindow::mapToNative(QRect const&, QXcbScreen const*) const () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 QXcbWindow::setGeometry(QRect const&) () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 QWidgetPrivate::setGeometry_sys(int, int, int, int, bool) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 QWidget::setGeometry(QRect const&) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 Title: vlc crashed with SIGSEGV in QXcbWindow::mapToNative() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo ** Affects: qtbase-opensource-src (Ubuntu) Importance: Medium Status: New ** Tags: amd64 apport-crash xenial -- vlc crashed with SIGSEGV in QXcbWindow::mapToNative() https://bugs.launchpad.net/bugs/1555836 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1461934] Re: vlc assert failure: vlc: dri2_util.c:199: isDRI2Connected: Zusicherung »dri_state->base.fd >= 0« nicht erfüllt.
Fixed in 1.6.2-1 ** Package changed: vlc (Ubuntu) => libva (Ubuntu) ** Changed in: libva (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libva in Ubuntu. https://bugs.launchpad.net/bugs/1461934 Title: vlc assert failure: vlc: dri2_util.c:199: isDRI2Connected: Zusicherung »dri_state->base.fd >= 0« nicht erfüllt. Status in libva package in Ubuntu: Fix Released Bug description: crashed after opening a video file in Thunar ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: vlc-nox 2.2.0-1 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AssertionMessage: vlc: dri2_util.c:199: isDRI2Connected: Zusicherung »dri_state->base.fd >= 0« nicht erfüllt. CurrentDesktop: XFCE Date: Thu Jun 4 14:42:30 2015 ExecutablePath: /usr/bin/vlc InstallationDate: Installed on 2015-05-28 (6 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1) ProcCmdline: /usr/bin/vlc --started-from-file /home/username/Videos/movie.mp4 Signal: 6 SourcePackage: vlc StacktraceTop: __assert_fail_base (fmt=0x7fe4397c112e , assertion=assertion@entry=0x7fe3ee024824 "dri_state->base.fd >= 0", file=file@entry=0x7fe3ee024810 "dri2_util.c", line=line@entry=199, function=function@entry=0x7fe3ee024860 "isDRI2Connected") at assert.c:92 __GI___assert_fail (assertion=0x7fe3ee024824 "dri_state->base.fd >= 0", file=0x7fe3ee024810 "dri2_util.c", line=199, function=0x7fe3ee024860 "isDRI2Connected") at assert.c:101 isDRI2Connected () from /usr/lib/x86_64-linux-gnu/libva-x11.so.1 ?? () from /usr/lib/x86_64-linux-gnu/libva-x11.so.1 vaInitialize () from /usr/lib/x86_64-linux-gnu/libva.so.1 Title: vlc assert failure: vlc: dri2_util.c:199: isDRI2Connected: Zusicherung »dri_state->base.fd >= 0« nicht erfüllt. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libva/+bug/1461934/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1555836] Re: vlc crashed with SIGSEGV in QXcbWindow::mapToNative()
Looks more like an issue in Qt to me. ** Package changed: vlc (Ubuntu) => qtbase-opensource-src (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1555836 Title: vlc crashed with SIGSEGV in QXcbWindow::mapToNative() Status in qtbase-opensource-src package in Ubuntu: New Bug description: i press esc to exit the fullscreen and i did get this error ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: vlc-nox 2.2.2-4 ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4 Uname: Linux 4.4.0-11-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Fri Mar 11 00:24:40 2016 Disassembly: => 0x115:Cannot access memory at address 0x115 ExecutablePath: /usr/bin/vlc InstallationDate: Installed on 2016-03-10 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) ProcCmdline: /usr/bin/vlc --no-video-title-show http://127.0.0.1:42241/ SegvAnalysis: Segfault happened at: 0x115: Cannot access memory at address 0x115 PC (0x0115) not located in a known VMA region (needed executable region)! Stack memory exhausted (SP below stack segment) SegvReason: executing NULL VMA Signal: 11 SourcePackage: vlc StacktraceTop: ?? () QXcbWindow::mapToNative(QRect const&, QXcbScreen const*) const () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 QXcbWindow::setGeometry(QRect const&) () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 QWidgetPrivate::setGeometry_sys(int, int, int, int, bool) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 QWidget::setGeometry(QRect const&) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 Title: vlc crashed with SIGSEGV in QXcbWindow::mapToNative() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1555836/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1648961] [NEW] Missing way to open local files
Public bug reported: I have a .html tree in my home, but I can't open it. ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1648961 Title: Missing way to open local files Status in webbrowser-app package in Ubuntu: New Bug description: I have a .html tree in my home, but I can't open it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1648961/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1648959] [NEW] package udev 229-4ubuntu12 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: after installing updates via Software Updater Ubuntu version:16.04.1 LTS ProblemType: Package DistroRelease: Ubuntu 16.04 Package: udev 229-4ubuntu12 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.2 Architecture: amd64 Date: Sat Dec 10 10:52:01 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 1 MachineType: TOSHIBA Satellite L650 ProcKernelCmdLine: file=/cdrom/multiboot/hostname-16.04.1-desktop-amd64/preseed/hostname.seed boot=casper cdrom-detect/try-usb=true persistent persistent-path=/multiboot/hostname-16.04.1-desktop-amd64 noprompt floppy.allowed_drive_mask=0 ignore_uuid live-media-path=/multiboot/hostname-16.04.1-desktop-amd64/casper/ initrd=/multiboot/hostname-16.04.1-desktop-amd64/casper/initrd.lz quiet splash --- debian-installer/language=cs keyboard-configuration/layoutcode?=cz RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: systemd Title: package udev 229-4ubuntu12 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/09/2011 dmi.bios.vendor: INSYDE dmi.bios.version: 2.40 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr2.40:bd11/09/2011:svnTOSHIBA:pnSatelliteL650:pvrPSK1JE-0CR008CZ:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Satellite L650 dmi.product.version: PSK1JE-0CR008CZ dmi.sys.vendor: TOSHIBA ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1648959 Title: package udev 229-4ubuntu12 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in systemd package in Ubuntu: New Bug description: after installing updates via Software Updater Ubuntu version:16.04.1 LTS ProblemType: Package DistroRelease: Ubuntu 16.04 Package: udev 229-4ubuntu12 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.2 Architecture: amd64 Date: Sat Dec 10 10:52:01 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 1 MachineType: TOSHIBA Satellite L650 ProcKernelCmdLine: file=/cdrom/multiboot/hostname-16.04.1-desktop-amd64/preseed/hostname.seed boot=casper cdrom-detect/try-usb=true persistent persistent-path=/multiboot/hostname-16.04.1-desktop-amd64 noprompt floppy.allowed_drive_mask=0 ignore_uuid live-media-path=/multiboot/hostname-16.04.1-desktop-amd64/casper/ initrd=/multiboot/hostname-16.04.1-desktop-amd64/casper/initrd.lz quiet splash --- debian-installer/language=cs keyboard-configuration/layoutcode?=cz RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: systemd Title: package udev 229-4ubuntu12 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/09/2011 dmi.bios.vendor: INSYDE dmi.bios.version: 2.40 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr2.40:bd11/09/2011:svnTOSHIBA:pnSatelliteL650:pvrPSK1JE-0CR008CZ:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Satellite L650 dmi.product.version: PSK1JE-0CR008CZ dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1648959/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1648959] Re: package udev 229-4ubuntu12 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Tags removed: need-duplicate-check -- 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/1648959 Title: package udev 229-4ubuntu12 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in systemd package in Ubuntu: New Bug description: after installing updates via Software Updater Ubuntu version:16.04.1 LTS ProblemType: Package DistroRelease: Ubuntu 16.04 Package: udev 229-4ubuntu12 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.2 Architecture: amd64 Date: Sat Dec 10 10:52:01 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 1 MachineType: TOSHIBA Satellite L650 ProcKernelCmdLine: file=/cdrom/multiboot/hostname-16.04.1-desktop-amd64/preseed/hostname.seed boot=casper cdrom-detect/try-usb=true persistent persistent-path=/multiboot/hostname-16.04.1-desktop-amd64 noprompt floppy.allowed_drive_mask=0 ignore_uuid live-media-path=/multiboot/hostname-16.04.1-desktop-amd64/casper/ initrd=/multiboot/hostname-16.04.1-desktop-amd64/casper/initrd.lz quiet splash --- debian-installer/language=cs keyboard-configuration/layoutcode?=cz RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: systemd Title: package udev 229-4ubuntu12 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/09/2011 dmi.bios.vendor: INSYDE dmi.bios.version: 2.40 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr2.40:bd11/09/2011:svnTOSHIBA:pnSatelliteL650:pvrPSK1JE-0CR008CZ:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Satellite L650 dmi.product.version: PSK1JE-0CR008CZ dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1648959/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1435040] Re: Ubuntu Phone does not connect to car-bluetooth
With OTA-14 I can now pair with Parrot CK3100 again, but there is still no sound (crossed note symbol). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1435040 Title: Ubuntu Phone does not connect to car-bluetooth Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Incomplete Bug description: With my FORD Focus Car, pairing does not work. The bluetooth system in the car searches for devices and shows "Aquaris E4.5 Ubuntu Edition" and then prompts me to connect with a 4-digit pin code, but the Ubuntu phone doesn't react at all and after a while the car system says that it failed to connect. image: 20150310-3201c0a KRILIN01A-S15A_BQ_L100EN_2020_150312 OS Build 20 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435040/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1648953] Re: Calendar dissapears from the pull down settings menu, after OTA-14
I have also seen this once. Rotating the phone to landscape mode and then pulling from the top made the calendar appear again. ** Also affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New -- 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/1648953 Title: Calendar dissapears from the pull down settings menu, after OTA-14 Status in Canonical System Image: New Status in indicator-datetime package in Ubuntu: New Bug description: I just noticed that calendar that used to be in dash/quick settings pulling bar is dissapearing after OTA-14. It only shows date and name of the month and the whole body of calendar is missing. See the screenshot attached. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1648953/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1483427] Re: Possible to manually set display brightness to 0 on Ubuntu Touch on Aquaris E5
Unfortunately, bug re-introduced for E5 by OTA-14. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1483427 Title: Possible to manually set display brightness to 0 on Ubuntu Touch on Aquaris E5 Status in indicator-power package in Ubuntu: Invalid Status in powerd package in Ubuntu: New Bug description: Possible to manually set display brightness to 0 on Ubuntu Touch It is possible to move the brightness slider to the very left position, which will set the display brightness of affected device to zero, or, to total darkness. This is a bug, since this leads to user's inability to set the brightness back or, generally, to operate the device. There is a slight chance, though, to return the brightness back to non-zero value (blindly, trying by user's memory). Also, this gets even more problematic, if we think about a scenario, where such Ubuntu device is locked by a PIN. User has to try to unlock the device on the dark screen, open the top panel with settings, scroll to the far right (to access the brightness settings), and then trying to hit the correct slider - all on a dark screen. This happened on Aquaris E5. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1483427/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1648965] [NEW] grafica
Public bug reported: grafica ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 Uname: Linux 4.4.0-53-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.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 Date: Sat Dec 10 13:11:10 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7520G] [1002:9990] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Trinity [Radeon HD 7520G] [103c:184a] Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] [1002:6840] (rev ff) (prog-if ff) InstallationDate: Installed on 2015-07-20 (509 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic root=UUID=c2b360dd-7125-486f-911b-14f23fa0bc6b ro plymouth:debug=1=1=1=1=1=1=1=1=1=1=1=1=1=1=1=1=1=1=1=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/21/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.26 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 184A dmi.board.vendor: Hewlett-Packard dmi.board.version: 57.35 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.26:bd02/21/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088B1130591620100:rvnHewlett-Packard:rn184A:rvr57.35:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion g6 Notebook PC dmi.product.version: 088B1130591620100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sat Dec 10 12:54:03 2016 xserver.configfile: default xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.2 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1648965 Title: grafica Status in xorg package in Ubuntu: New Bug description: grafica ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 Uname: Linux 4.4.0-53-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.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 Date: Sat Dec 10 13:11:10 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7520G] [1002:9990] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Trinity [Radeon HD 7520G] [103c:184a] Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] [1002:6840] (rev ff) (prog-if ff) InstallationDate: Installed on 2015-07-20 (509 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-53-generic root=UUID=c2b360dd-7125-486f-911b-14f23fa0bc6b ro plymouth:debug=1=1=1=1=1=1=1=1=1=1=1=1=1=1=1=1=1=1=1=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/21/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.26 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 184A dmi.board.vendor: Hewlett-Packard dmi.board.version: 57.35 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dm
[Touch-packages] [Bug 1648953] Re: Calendar dissapears from the pull down settings menu, after OTA-14
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/1648953 Title: Calendar dissapears from the pull down settings menu, after OTA-14 Status in Canonical System Image: New Status in indicator-datetime package in Ubuntu: Confirmed Bug description: I just noticed that calendar that used to be in dash/quick settings pulling bar is dissapearing after OTA-14. It only shows date and name of the month and the whole body of calendar is missing. See the screenshot attached. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1648953/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1648961] Re: Missing way to open local files
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: webbrowser-app (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1648961 Title: Missing way to open local files Status in webbrowser-app package in Ubuntu: Confirmed Bug description: I have a .html tree in my home, but I can't open it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1648961/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1590892] Re: package util-linux 2.27.1-6ubuntu3.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Has anyone had a chance to look into this yet? It's been affecting me for months - ever since I upgraded to Xenial, in fact. -- 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/1590892 Title: package util-linux 2.27.1-6ubuntu3.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in util-linux package in Ubuntu: Invalid Bug description: Could not install ProblemType: Package DistroRelease: Ubuntu 16.04 Package: util-linux 2.27.1-6ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Thu Jun 9 18:23:58 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-05-21 (18 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: util-linux Title: package util-linux 2.27.1-6ubuntu3.1 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/1590892/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1648970] [NEW] ubuntu-bug says that steam isn't installed, when it is.
Public bug reported: When running 'ubuntu-bug steam', the bug reporter falsely reports that "The report belongs to a package that is not installed.' Running 'apt install steam' confirms that the steam package is installed and that it's up to date. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: apport 2.20.3-0ubuntu8 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: KDE Date: Sat Dec 10 08:03:36 2016 InstallationDate: Installed on 2016-11-18 (21 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161118) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty -- 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/1648970 Title: ubuntu-bug says that steam isn't installed, when it is. Status in apport package in Ubuntu: New Bug description: When running 'ubuntu-bug steam', the bug reporter falsely reports that "The report belongs to a package that is not installed.' Running 'apt install steam' confirms that the steam package is installed and that it's up to date. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: apport 2.20.3-0ubuntu8 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: KDE Date: Sat Dec 10 08:03:36 2016 InstallationDate: Installed on 2016-11-18 (21 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161118) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1648970/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1648974] [NEW] package sudo 1.8.16-0ubuntu3 failed to install/upgrade: Unterprozess installiertes pre-removal-Skript gab den Fehlerwert 1 zurück
Public bug reported: I don't really know, I'm new to Linux. ProblemType: Package DistroRelease: Ubuntu 16.10 Package: sudo 1.8.16-0ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Sat Dec 10 14:37:23 2016 ErrorMessage: Unterprozess installiertes pre-removal-Skript gab den Fehlerwert 1 zurück InstallationDate: Installed on 2016-12-09 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: sudo Title: package sudo 1.8.16-0ubuntu3 failed to install/upgrade: Unterprozess installiertes pre-removal-Skript gab den Fehlerwert 1 zurück UpgradeStatus: No upgrade log present (probably fresh install) VisudoCheck: /etc/sudoers: parsed OK /etc/sudoers.d/README: parsed OK ** Affects: sudo (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package yakkety -- 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/1648974 Title: package sudo 1.8.16-0ubuntu3 failed to install/upgrade: Unterprozess installiertes pre-removal-Skript gab den Fehlerwert 1 zurück Status in sudo package in Ubuntu: New Bug description: I don't really know, I'm new to Linux. ProblemType: Package DistroRelease: Ubuntu 16.10 Package: sudo 1.8.16-0ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Sat Dec 10 14:37:23 2016 ErrorMessage: Unterprozess installiertes pre-removal-Skript gab den Fehlerwert 1 zurück InstallationDate: Installed on 2016-12-09 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: sudo Title: package sudo 1.8.16-0ubuntu3 failed to install/upgrade: Unterprozess installiertes pre-removal-Skript gab den Fehlerwert 1 zurück UpgradeStatus: No upgrade log present (probably fresh install) VisudoCheck: /etc/sudoers: parsed OK /etc/sudoers.d/README: parsed OK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1648974/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1647603] Re: Add option for semi-transparent keyboard
Hi! For me the new layout is great, but I think it might be the best solution to chance only the transparency of the background of the keyboard an not of the letters. Because with 100% transparency letters you didn’t see were you typing. At next probably for bright background dark letters are right (like the text messaging app, the web browser, the notes app, ..), but for dark backgrounds you will need bright letters (looks like the lock screen). So I think the keyboard on the lock screen and the "general" keyboard are two different types. Further we should be able to adjust the colour of the letters on the lock screen keyboard because the colour depends on your background on the Phone (Snowy Mountains need a dark colour, the Ubuntu magenta background need bright letters, ...). Sorry for my bad English, I hope you will understand what I mean. Greets! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1647603 Title: Add option for semi-transparent keyboard Status in Ubuntu UX: Fix Committed Status in ubuntu-keyboard package in Ubuntu: Confirmed Bug description: OK, this is not a real bug, rather a characteristic. But one that can be easily solved, thus I'd like to make a feature request. Especially in the landscape mode, the onscreen keyboard takes up a large portion of the screen. Potentially it can overlap the window where the text is being typed into, so you cannot see what you're typing. This could be VERY easily solved by letting users to set transparency level for the entire onscreen keyboard. Attached is my concept of maliit keyboard at 70% opacity on Ubuntu Touch phone, in landscape windowed mode. UX fix In System settings, the on screen keyboard option will allow a user to set the opacity for their OSK. This will be a slider in the on screen keyboard option in system settings, with the options to set opacity from 50%-100% To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1647603/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1646457] Re: No feedback when changing Launcher's icon size
** Changed in: unity8 (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1646457 Title: No feedback when changing Launcher's icon size Status in Canonical System Image: Confirmed Status in Ubuntu UX: New Status in unity8 package in Ubuntu: In Progress Bug description: bq M10 FHD rc-proposed r243 Steps to reproduce: 0. Make sure 'Desktop mode' is switched off 1. Go to System Setting > Launcher 2. Move the slider to change 'Icon size' Expected result: The launcher is revealed so I can see what changes I'm making with the slider What happens instead: If I move the slider to the left: nothing happens. If I move the slider to the right: the launcher 'jumps' a bit like it was trying to show up but never really shows up. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1646457/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1440360] Re: Incomplete long-left swipe resets dash
With the landing of the app drawer, the long left edge swipe does not reset the dash any more... Linking the apprawer branch to close this when it lands. ** Branch linked: lp:~mzanetti/unity8/appdrawer ** Changed in: unity8 (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1440360 Title: Incomplete long-left swipe resets dash Status in Ubuntu UX: Fix Committed Status in unity8 package in Ubuntu: In Progress Bug description: Steps to reproduce the issue: 1 - open e.g. Ubuntu Store scope (from the app scope) or Youtube scope (from the video scope) 2 - (shortly) swipe from the left to invoke launcher Expected outcome: The launcher can be used to open a pinned app (while the current scope is still kept in the background) or dismissed to return to the current scope. Actual outcome: The current scope will immediately be closed and the first (main) scope (typically the app scope on devel-images and the Today scope on RTM) will be shown. If I understand the current design guidelines correctly this is the expected behaviour for a full left-to-right swipe, but not for a short swipe from the left to invoke the launcher. This behaviour can be observed on both the current devel-proposed and RTM images. - Desired UX - Don't trigger the "go to home" action yet when the long swipe is started but when user releases the finger and all the long swipe parameters are fulfilled (distance threshold and direction) - Also trigger "go to home" action when any other scope is focused. Currently action is triggered only when app is focused and when a child scope is focused but not when one of the dash scopes is focused. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1440360/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1647603] Re: Add option for semi-transparent keyboard
pad, the kyboard transparency actually works a bit different. Buttons are a separat layer atop the backdrop. These two layers can have same opacity set, yet they seem to be composited as a sum of opacities. Besides, making only the background of the keys partialy transparrent ould defeat the goal, because the keys surface would still hide most of the area (almost all) of what's under the keyboard. Unless you actually meant everything except the letters inside the buttons, meaning, everything except for just ythe letters (font). Not sure how that would work out, interesting but I'm still in doubts. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1647603 Title: Add option for semi-transparent keyboard Status in Ubuntu UX: Fix Committed Status in ubuntu-keyboard package in Ubuntu: Confirmed Bug description: OK, this is not a real bug, rather a characteristic. But one that can be easily solved, thus I'd like to make a feature request. Especially in the landscape mode, the onscreen keyboard takes up a large portion of the screen. Potentially it can overlap the window where the text is being typed into, so you cannot see what you're typing. This could be VERY easily solved by letting users to set transparency level for the entire onscreen keyboard. Attached is my concept of maliit keyboard at 70% opacity on Ubuntu Touch phone, in landscape windowed mode. UX fix In System settings, the on screen keyboard option will allow a user to set the opacity for their OSK. This will be a slider in the on screen keyboard option in system settings, with the options to set opacity from 50%-100% To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1647603/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1648435] Re: 5 useless buttons on the lock-screen
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-keyboard (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1648435 Title: 5 useless buttons on the lock-screen Status in Canonical System Image: New Status in Ubuntu UX: New Status in ubuntu-keyboard package in Ubuntu: Confirmed Bug description: bq e4.5 OTA-14 In the case I use '4-digit passcode' for 'Lock security', the new keyboard visible on the lock screen has 5 buttons out of 18 (counting 'Cancel' and 'Emergency') which do not have any use. I marked them on the attached screenshot. The same keyboard appears when I create or change the 4-digit passcode in System Settings. IMO it'd be better to remove those useless buttons, and possibly rearrange the useful ones. That could make it look better and provide better/bigger touch target. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1648435/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1648979] [NEW] [Latitude E6400, IDT 92HD71B7X, Speaker, Internal] No sound at all
Public bug reported:
Stop suddenly the sound while playing
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: alsa-base 1.0.25+dfsg-0ubuntu1.1
ProcVersionSignature: Ubuntu 3.2.0-118.161-generic-pae 3.2.79
Uname: Linux 3.2.0-118-generic-pae i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu17.13
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: olivier2402 F pulseaudio
/dev/snd/pcmC0D0p: olivier2402 F...m pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xf6adc000 irq 48'
Mixer name : 'Intel Cantiga HDMI'
Components : 'HDA:111d76b2,10280233,00100302
HDA:80862802,80860101,0010'
Controls : 26
Simple ctrls : 12
Date: Sat Dec 10 16:04:33 2016
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
MarkForUpload: True
PackageArchitecture: all
ProcEnviron:
PATH=(custom, no user)
LANG=fr_CH.UTF-8
SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful
Symptom_Card: Audio interne - HDA Intel
Symptom_DevicesInUse:
2402 2402 olivier F pulseaudio
/dev/snd/pcmC0D0p: olivier F...m pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: No sound at all
Title: [Latitude E6400, IDT 92HD71B7X, Speaker, Internal] No sound at all
UpgradeStatus: Upgraded to precise on 2012-05-27 (1657 days ago)
dmi.bios.date: 08/19/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A27
dmi.board.name: 0HT027
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA27:bd08/19/2010:svnDellInc.:pnLatitudeE6400:pvr:rvnDellInc.:rn0HT027:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude E6400
dmi.sys.vendor: Dell Inc.
** Affects: alsa-driver (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug i386 precise running-unity
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1648979
Title:
[Latitude E6400, IDT 92HD71B7X, Speaker, Internal] No sound at all
Status in alsa-driver package in Ubuntu:
New
Bug description:
Stop suddenly the sound while playing
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: alsa-base 1.0.25+dfsg-0ubuntu1.1
ProcVersionSignature: Ubuntu 3.2.0-118.161-generic-pae 3.2.79
Uname: Linux 3.2.0-118-generic-pae i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu17.13
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: olivier2402 F pulseaudio
/dev/snd/pcmC0D0p: olivier2402 F...m pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xf6adc000 irq 48'
Mixer name : 'Intel Cantiga HDMI'
Components : 'HDA:111d76b2,10280233,00100302
HDA:80862802,80860101,0010'
Controls : 26
Simple ctrls : 12
Date: Sat Dec 10 16:04:33 2016
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
MarkForUpload: True
PackageArchitecture: all
ProcEnviron:
PATH=(custom, no user)
LANG=fr_CH.UTF-8
SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful
Symptom_Card: Audio interne - HDA Intel
Symptom_DevicesInUse:
2402 2402 olivier F pulseaudio
/dev/snd/pcmC0D0p: olivier F...m pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: No sound at all
Title: [Latitude E6400, IDT 92HD71B7X, Speaker, Internal] No sound at all
UpgradeStatus: Upgraded to precise on 2012-05-27 (1657 days ago)
dmi.bios.date: 08/19/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A27
dmi.board.name: 0HT027
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA27:bd08/19/2010:svnDellInc.:pnLatitudeE6400:pvr:rvnDellInc.:rn0HT027:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude E6400
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1648979/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://
[Touch-packages] [Bug 1648989] [NEW] Sometimes after resume there is a problem with text
Public bug reported: Sometimes (not often) after resume from suspend and unlocking screen (blocked with lightlocker) there is the problem with text in GTK applications (you can see it on screenshot). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 Uname: Linux 4.4.0-53-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.2 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Dec 10 19:15:34 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-11-19 (21 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption xenial ** Attachment added: "Screenshot of the bug" https://bugs.launchpad.net/bugs/1648989/+attachment/4790027/+files/bug_screenshot.png -- 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/1648989 Title: Sometimes after resume there is a problem with text Status in xorg package in Ubuntu: New Bug description: Sometimes (not often) after resume from suspend and unlocking screen (blocked with lightlocker) there is the problem with text in GTK applications (you can see it on screenshot). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 Uname: Linux 4.4.0-53-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.2 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Dec 10 19:15:34 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-11-19 (21 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1648989/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1648435] Re: 5 useless buttons on the lock-screen
WOW, @mpredotka, beautifull design!!! You are good!!! It would look much better! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1648435 Title: 5 useless buttons on the lock-screen Status in Canonical System Image: New Status in Ubuntu UX: New Status in ubuntu-keyboard package in Ubuntu: Confirmed Bug description: bq e4.5 OTA-14 In the case I use '4-digit passcode' for 'Lock security', the new keyboard visible on the lock screen has 5 buttons out of 18 (counting 'Cancel' and 'Emergency') which do not have any use. I marked them on the attached screenshot. The same keyboard appears when I create or change the 4-digit passcode in System Settings. IMO it'd be better to remove those useless buttons, and possibly rearrange the useful ones. That could make it look better and provide better/bigger touch target. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1648435/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1176046] Re: isc-dhcp dhclient listens on extra random ports
** Description changed: + [Impact] + + In trusty, there is only 1 version of dhclient, including #define NSUPDATE, which introduce DDNS functionnality. + The DDNS functionnality, generate 2 random extra ports between 1024-65535. + + Impact reported by users : + + "One impact of these random ports is that security hardening becomes more difficult. The purpose of these random ports and security implications are unknown." + "We have software that was using one of the lower udp ports but it happened to collide with dhclient which seems to allocate 2 random ports." + + There is a randomization mechanism in libdns that prevent dhclient to take the sysctl values into account (net.ipv4.ip_local_port_range & net.ipv4.ip_local_reserved_ports) to workaround this, and after discussion isc-dhcp upstream doesn't want to rely on kernel for randomization. + + There is no realtime configuration to disable the feature or workaround this. The only possible way is at compile time. + + I also talk with upstream maintainers, and there is no way they will + accept to reduce the range (1024-65535) for security reason. Reducing + the port range may facilitate the spoofing. + + Xenial has separated dhclient in two packages : + + isc-dhcp-client pkg : dhclient with DDNS functionality disabled (no random extra ports) + isc-dhcp-client-ddns : dhclient with DDNS functionality enabled (with random extra ports) + + The goal here is to reproduce the same situation in Trusty, for this bug + to be less painful for at least users that doesn't require DDNS + functionnality. + + [Test Case] + + Run a Trusty image with following package : + isc-dhcp-client + isc-dhcp-common + + ``` + dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc + dhclient 1110 root 20u IPv4 11516 0t0 UDP *:64589 # <--- extra random port + dhclient 1110 root 21u IPv6 11517 0t0 UDP *:7749 # <--- extra random port + ``` + + + [Regression Potential] + + * none expected + + I did the split such that users will automatically get isc-dhcp-client-ddns installed but users bothered by this bug then will have the option to switch to the one without it by uninstalling (isc-dhcp-client-ddns), + so existing Trusty users can continue to use this DDNS functionality after the SRU without any necessary intervention. + + With isc-dhcp-client-ddns : + dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc + dhclient 1110 root 20u IPv4 11516 0t0 UDP *:64589 # <--- extra random port + dhclient 1110 root 21u IPv6 11517 0t0 UDP *:7749 # <--- extra random port + + Without isc-dhcp-client-ddns : + dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc + + Note that this is how Xenial does it. + + [Other Info] + + * See : https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1176046/comments/19 to look at my discussion with rbasak on if that approach would be acceptable for SRU. + + [Original Description] + Ubuntu 13.04 Server 64-bit. Fresh install. Only one network adapter. dhclient process is listening on two randomly chosen udp ports in addition to the usual port 68. This appears to be a bug in the discovery code for probing information on interfaces in the system. Initial research of the code also suggested omapi, but adding omapi port to /etc/dhcp/dhclient.conf only opened a forth port with the two random udp ports still enabled. Version of included distro dhclient was 4.2.4. I also tested with the latest isc-dhclient-4.2.5-P1 and got the same results. Debian has the same bug: http://forums.debian.net/viewtopic.php?f=10&t=95273&p=495605#p495605 One impact of these random ports is that security hardening becomes more difficult. The purpose of these random ports and security implications are unknown. - Example netstat -lnp output: - udp0 0 0.0.0.0:21117 0.0.0.0:* 2659/dhclient - udp0 0 0.0.0.0:68 0.0.0.0:* 2659/dhclient + udp0 0 0.0.0.0:21117 0.0.0.0:* 2659/dhclient + udp0 0 0.0.0.0:68 0.0.0.0:* 2659/dhclient udp6 0 0 :::45664:::* 2659/dhclient -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1176046 Title: isc-dhcp dhclient listens on extra random ports Status in isc-dhcp package in Ubuntu: In Progress Status in isc-dhcp source package in Trusty: In Progress Bug description: [Impact] In trusty, there is only 1 version of dhclient, including #define NSUPDATE, which introduce DDNS functionnality. The DDNS functionnality, generate 2 random extra ports between 1024-65535. Impact reported by users : "One impact of these random ports is that security ha
[Touch-packages] [Bug 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec
Who knows, the detachable tablet thingy i have has another issue beside this, it has a micros SD slot but for some reason kubuntu wont read any card i put in it. Just throws out some error in dmesg. I submitted a bug report but that was a month ago(plus it was sitting on the forums for a very long time until i had enough and submitted the bug report) and there is still no solution for it :/ ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1563110 Title: No sound on Asus e200ha, intel sst with cx2072x codec Status in ALSA driver: Unknown Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I've recently bought an Asus e200ha. Sound in this laptop doesn't work. The sound card is an intel sst with codec conexant cx2072x aplay -l: aplay: device_list:268: no soundcard found... in the sound setting there is a "Dummy output" --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a InstallationDate: Installed on 2016-03-28 (0 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105 Lsusb: Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 RelatedPackageVersions: linux-restricted-modules-3.19.0-32-generic N/A linux-backports-modules-3.19.0-32-generic N/A linux-firmware 1.127.16 Tags: rosa Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: E200HA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1563110/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1647174] Re: opening menu for certain types of GtkComboBox causes Gdk-CRITICAL assertion 'GDK_IS_WINDOW (window)' failed
** Changed in: gtk+3.0 (Ubuntu) Status: Confirmed => Fix Committed ** Tags added: zesty ** Changed in: gtk+3.0 (Ubuntu) Importance: Undecided => 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/1647174 Title: opening menu for certain types of GtkComboBox causes Gdk-CRITICAL assertion 'GDK_IS_WINDOW (window)' failed Status in GTK+: Fix Released Status in gtk+3.0 package in Ubuntu: Fix Committed Status in gtk+3.0 package in Debian: New Bug description: It happens when try to open any ComboBox or a CellRendererCombo: Gdk-CRITICAL **: gdk_window_get_window_type: assertion 'GDK_IS_WINDOW (window)' failed To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1647174/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1645701] Re: desktop window regression on HiDPI
** Changed in: gtk+3.0 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1645701 Title: desktop window regression on HiDPI Status in gtk+3.0 package in Ubuntu: Fix Released Status in nautilus package in Ubuntu: Invalid Bug description: On fully updated VM (zesty) with scaling-factor set to 2 initially window size is correct, but after resizing VM, nautilus desktop window is 1/4 from size it should have. I have same problem also on my main pc (also zesty) - desktop window is only 1/4 after resolution changes. Restarting nautilus "fixes" problem until next resolution changes. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: nautilus 1:3.20.3-1ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Tue Nov 29 14:27:59 2016 SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: dropbox2015.10.28 gnome-terminal 3.20.2-1ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1645701/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1641867] Re: GtkMenu: Submenu navigation triangle doesn't work
** Changed in: gtk+3.0 (Ubuntu) Status: Confirmed => Triaged ** Bug watch added: GNOME Bug Tracker #710388 https://bugzilla.gnome.org/show_bug.cgi?id=710388 ** Also affects: gtk via https://bugzilla.gnome.org/show_bug.cgi?id=710388 Importance: Unknown Status: Unknown -- 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/1641867 Title: GtkMenu: Submenu navigation triangle doesn't work Status in GTK+: Confirmed Status in gtk+3.0 package in Ubuntu: Triaged Bug description: The navigation triangle code for keeping a submenu open when the mouse is moving diagonally toward it is broken due to incorrect rounding. This was reported upstream at: https://bugzilla.gnome.org/show_bug.cgi?id=710388 The attached patch (also submitted upstream) rounds the cursor location when calculating the navigation triangle bounds. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1641867/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1641867] Re: GtkMenu: Submenu navigation triangle doesn't work
** Changed in: gtk Status: Unknown => Confirmed ** Changed in: gtk Importance: Unknown => 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/1641867 Title: GtkMenu: Submenu navigation triangle doesn't work Status in GTK+: Confirmed Status in gtk+3.0 package in Ubuntu: Triaged Bug description: The navigation triangle code for keeping a submenu open when the mouse is moving diagonally toward it is broken due to incorrect rounding. This was reported upstream at: https://bugzilla.gnome.org/show_bug.cgi?id=710388 The attached patch (also submitted upstream) rounds the cursor location when calculating the navigation triangle bounds. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1641867/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1604062] Re: too easy to trigger the apps switcher / spread on desktop
Why would it have a edge trigger? For desktop usage there's Alt + Tab. When there's no keyboard, swipe (touch screen) or use the launcher (touch or mouse). I have only tried desktop mode a few times with mouse and keyboard but this was a problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1604062 Title: too easy to trigger the apps switcher / spread on desktop Status in Canonical System Image: New Status in Ubuntu UX: New Status in unity8 package in Ubuntu: Confirmed Bug description: too easy to trigger the apps switcher / spread on desktop :'( i liked this feature at first but now it's becoming super frustrating to use unity8. i accidentally trigger the spread way to often in many unwanted ways. 2/3 times when i want to restart and i go with the mouse on the indicator (top right) i trigger the spread, or when i want to scroll a page that is semi maximized to the right (ctrl super right), or when i'm playing neverball with the mouse etc To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1604062/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1647696] Re: the app switcher and the app drawer are a bit laggy on MX4
Opening the app switcher has become extremely laggy on mx4. When opening it there's always (since ota-14) a great lagg, it happens every time, which was not the case before the update. The scrolling is also a bit laggy but at least for me the worst part is when I swipe it open. Happens 100% of the times. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1647696 Title: the app switcher and the app drawer are a bit laggy on MX4 Status in Canonical System Image: New Status in unity8 package in Ubuntu: Confirmed Bug description: the app switcher and the app drawer are a bit laggy on MX4 i am not sure how to view the actual FPS but they feel a bit laggy mx4/rc-proposed To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1647696/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1641867] Re: GtkMenu: Submenu navigation triangle doesn't work
** Changed in: gtk+3.0 (Ubuntu) Importance: Undecided => Low -- 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/1641867 Title: GtkMenu: Submenu navigation triangle doesn't work Status in GTK+: Confirmed Status in gtk+3.0 package in Ubuntu: Triaged Bug description: The navigation triangle code for keeping a submenu open when the mouse is moving diagonally toward it is broken due to incorrect rounding. This was reported upstream at: https://bugzilla.gnome.org/show_bug.cgi?id=710388 The attached patch (also submitted upstream) rounds the cursor location when calculating the navigation triangle bounds. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1641867/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1648435] Re: 5 useless buttons on the lock-screen
I love your design Michał! Let me know if I can help you make this reality somehow -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1648435 Title: 5 useless buttons on the lock-screen Status in Canonical System Image: New Status in Ubuntu UX: New Status in ubuntu-keyboard package in Ubuntu: Confirmed Bug description: bq e4.5 OTA-14 In the case I use '4-digit passcode' for 'Lock security', the new keyboard visible on the lock screen has 5 buttons out of 18 (counting 'Cancel' and 'Emergency') which do not have any use. I marked them on the attached screenshot. The same keyboard appears when I create or change the 4-digit passcode in System Settings. IMO it'd be better to remove those useless buttons, and possibly rearrange the useful ones. That could make it look better and provide better/bigger touch target. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1648435/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1648942] Re: Sync libwebp 0.5.1-4 (main) from Debian unstable (main)
This bug was fixed in the package libwebp - 0.5.1-4 Sponsored for Jeremy Bicha (jbicha) --- libwebp (0.5.1-4) unstable; urgency=medium * Import armh compilation patch from Ubuntu (closes: #845749) -- Jeff Breidenbach Fri, 09 Dec 2016 10:42:47 -0800 libwebp (0.5.1-3) unstable; urgency=medium * Fix CVE-2016- and CVE-2016-9085 (closes: #842714) -- Jeff Breidenbach Wed, 09 Nov 2016 16:27:04 -0800 ** Changed in: libwebp (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libwebp in Ubuntu. https://bugs.launchpad.net/bugs/1648942 Title: Sync libwebp 0.5.1-4 (main) from Debian unstable (main) Status in libwebp package in Ubuntu: Fix Released Bug description: Please sync libwebp 0.5.1-4 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * debian/patches/armhf_update_neon_support.patch: configure: do not rely on arm_neon.h for neon detection. Closes LP: #1630349. That change is included in 0.5.1-4. Changelog entries since current zesty version 0.5.1-2ubuntu1: libwebp (0.5.1-4) unstable; urgency=medium * Import armh compilation patch from Ubuntu (closes: #845749) -- Jeff Breidenbach Fri, 09 Dec 2016 10:42:47 -0800 libwebp (0.5.1-3) unstable; urgency=medium * Fix CVE-2016- and CVE-2016-9085 (closes: #842714) -- Jeff Breidenbach Wed, 09 Nov 2016 16:27:04 -0800 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libwebp/+bug/1648942/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1648961] Re: Missing way to open local files
*** This bug is a duplicate of bug 1563214 *** https://bugs.launchpad.net/bugs/1563214 ** This bug has been marked a duplicate of bug 1563214 Can’t browse and view local HTML files in home folder -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1648961 Title: Missing way to open local files Status in webbrowser-app package in Ubuntu: Confirmed Bug description: I have a .html tree in my home, but I can't open it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1648961/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1643481] Re: Hardware freeze when going fullscreen in certain applications with Wayland
** Changed in: ubuntu-gnome Status: Fix Committed => New -- 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/1643481 Title: Hardware freeze when going fullscreen in certain applications with Wayland Status in Ubuntu GNOME: New Status in gtk+3.0 package in Ubuntu: Incomplete Bug description: Every time I press "F11" in Firefox or use "F" in VLC to go into fullscreen mode my laptop will freeze, only leaving the audio playing with a frozen image, without the ability to use my keyboard or move my touch pad or mouse, forcing me to restart my computer by holding down my power button. How to reproduce the bug in Ubuntu Gnome 17.04 on Wayland: - Press "F11" by default in Firefox to go into fullscreen mode. - Press "F" by default in VLC to go into and/or leave fullscreen mode. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1643481/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1176046] Re: isc-dhcp dhclient listens on extra random ports
> isc-dhcp-client pkg : dhclient with DDNS functionality disabled (no random extra ports) What will happen to existing Trusty users who are relying on the current ddns functionality? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1176046 Title: isc-dhcp dhclient listens on extra random ports Status in isc-dhcp package in Ubuntu: In Progress Status in isc-dhcp source package in Trusty: In Progress Bug description: [Impact] In trusty, there is only 1 version of dhclient, including #define NSUPDATE, which introduce DDNS functionnality. The DDNS functionnality, generate 2 random extra ports between 1024-65535. Impact reported by users : "One impact of these random ports is that security hardening becomes more difficult. The purpose of these random ports and security implications are unknown." "We have software that was using one of the lower udp ports but it happened to collide with dhclient which seems to allocate 2 random ports." There is a randomization mechanism in libdns that prevent dhclient to take the sysctl values into account (net.ipv4.ip_local_port_range & net.ipv4.ip_local_reserved_ports) to workaround this, and after discussion isc-dhcp upstream doesn't want to rely on kernel for randomization. There is no realtime configuration to disable the feature or workaround this. The only possible way is at compile time. I also talk with upstream maintainers, and there is no way they will accept to reduce the range (1024-65535) for security reason. Reducing the port range may facilitate the spoofing. Xenial has separated dhclient in two packages : isc-dhcp-client pkg : dhclient with DDNS functionality disabled (no random extra ports) isc-dhcp-client-ddns : dhclient with DDNS functionality enabled (with random extra ports) The goal here is to reproduce the same situation in Trusty, for this bug to be less painful for at least users that doesn't require DDNS functionnality. [Test Case] Run a Trusty image with following package : isc-dhcp-client isc-dhcp-common ``` dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc dhclient 1110 root 20u IPv4 11516 0t0 UDP *:64589 # <--- extra random port dhclient 1110 root 21u IPv6 11517 0t0 UDP *:7749 # <--- extra random port ``` [Regression Potential] * none expected I did the split such that users will automatically get isc-dhcp-client-ddns installed but users bothered by this bug then will have the option to switch to the one without it by uninstalling (isc-dhcp-client-ddns), so existing Trusty users can continue to use this DDNS functionality after the SRU without any necessary intervention. With isc-dhcp-client-ddns : dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc dhclient 1110 root 20u IPv4 11516 0t0 UDP *:64589 # <--- extra random port dhclient 1110 root 21u IPv6 11517 0t0 UDP *:7749 # <--- extra random port Without isc-dhcp-client-ddns : dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc Note that this is how Xenial does it. [Other Info] * See : https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1176046/comments/19 to look at my discussion with rbasak on if that approach would be acceptable for SRU. [Original Description] Ubuntu 13.04 Server 64-bit. Fresh install. Only one network adapter. dhclient process is listening on two randomly chosen udp ports in addition to the usual port 68. This appears to be a bug in the discovery code for probing information on interfaces in the system. Initial research of the code also suggested omapi, but adding omapi port to /etc/dhcp/dhclient.conf only opened a forth port with the two random udp ports still enabled. Version of included distro dhclient was 4.2.4. I also tested with the latest isc-dhclient-4.2.5-P1 and got the same results. Debian has the same bug: http://forums.debian.net/viewtopic.php?f=10&t=95273&p=495605#p495605 One impact of these random ports is that security hardening becomes more difficult. The purpose of these random ports and security implications are unknown. Example netstat -lnp output: udp0 0 0.0.0.0:21117 0.0.0.0:* 2659/dhclient udp0 0 0.0.0.0:68 0.0.0.0:* 2659/dhclient udp6 0 0 :::45664:::* 2659/dhclient To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1176046/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1612367] Re: [Touch] Incoming call gets silent randomly
With OTA-14 it's still the same - sometimes I can hear ring tone only for split a second (~200ms maybe). I can answer the call and talk normally. Attached yet another syslog (received call at 21:19). ** Attachment added: "syslog" https://bugs.launchpad.net/canonical-devices-system-image/+bug/1612367/+attachment/4790059/+files/syslog -- 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/1612367 Title: [Touch] Incoming call gets silent randomly Status in Canonical System Image: Confirmed Status in media-hub package in Ubuntu: Confirmed Status in ofono package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I've experienced this strange issue 4-5 times after OTA-12. It seems pretty random and is hard to reproduce. When I get an incoming call, the screen turns on, the incoming call pop up appears, but there is no sound at all even though the phone is not in silent mode (and also the speaker volume is not set too low). I can accept this call and keep conversing as usual. Once I asked the same caller to call me once again after a few minutes, that time the phone rang as expected. Device: E5, OTA-12, stable channel I can provide necessary logs if this happens again. Which ones should I gather? Possibly related to bug #1614943. UPDATE: As mentioned in comment #7, it seems the phone rings for a fraction of a second and then the sound pauses abruptly. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1612367/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1648953] Re: Calendar dissapears from the pull down settings menu, after OTA-14
** Description changed: - I just noticed that calendar that used to be in dash/quick settings pulling bar is dissapearing after OTA-14. + I just noticed that calendar that used to be in dash/quick settings pulling bar disappears after OTA-14. It only shows date and name of the month and the whole body of calendar is missing. + When phone is rebooted, the calendar is present for a while, then just disappears. See the screenshot attached. + Meizu Pro 5, stable, OTA-14 -- 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/1648953 Title: Calendar dissapears from the pull down settings menu, after OTA-14 Status in Canonical System Image: New Status in indicator-datetime package in Ubuntu: Confirmed Bug description: I just noticed that calendar that used to be in dash/quick settings pulling bar disappears after OTA-14. It only shows date and name of the month and the whole body of calendar is missing. When phone is rebooted, the calendar is present for a while, then just disappears. See the screenshot attached. Meizu Pro 5, stable, OTA-14 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1648953/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1435040] Re: Ubuntu Phone does not connect to car-bluetooth
BQ Aquaris E5 Volkswagen Phaeton 2011 (VW Navigation System RNS810) OTA14 Finally IT WORKS! But from the beginning: After the OTA 14 Update I tried again to connect to my in car bluetooth system and make calls. Connecting (still) worked. Next I tried to make a call and again no sound from the speakers. After random changes on both ends (phone and in car system, of course with no systematic tracking), I tried again to call somebody and now speakers/mic worked perfectly. I left my car, entered again, phone reconnected and now again no sound!?! Wtf? But I was hooked, if it worked one time, it has to be possible to make it work again ... It took me some time to track down the necessary conditions for a stable and working bluetooth connection: 1. In the phones bluetooth settings the auto connect button for the connection to the in car bluetooth system has to be disabled. If this is not disabled, the car and the phone try to establish the connection at the same time and things get messed up, up to the point where both systems eventually freeze. 2. The car system can only establish the bluetooth connection, if the screen of the phone is unlocked. That's all. If you pay attention to these 2 points, really everything works perfectly (for Volkswagen systems)! Even streaming media via bluetooth works! I'm really excited, thank you very much for your work! I use my phone for business and desperately needed a working hands free system in my car. Unlocking my screen after entering the car is no big deal to me. Switching back to android is now definitely off the table. Thank you again and keep up the great work! I really love the usability and GUI of my ubuntu phone! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1435040 Title: Ubuntu Phone does not connect to car-bluetooth Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Incomplete Bug description: With my FORD Focus Car, pairing does not work. The bluetooth system in the car searches for devices and shows "Aquaris E4.5 Ubuntu Edition" and then prompts me to connect with a 4-digit pin code, but the Ubuntu phone doesn't react at all and after a while the car system says that it failed to connect. image: 20150310-3201c0a KRILIN01A-S15A_BQ_L100EN_2020_150312 OS Build 20 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435040/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi
First of all, you just cost me a few hours trying to get my network connection back after the instructions for reinstall of network-manager upon failed WICD, themselves, failed. Second, if the default network manager system that comes with distributions has a bug, it's not "whining" to rather insist that it be fixed or replaced with something that works. On Sat, Nov 5, 2016 at 3:50 AM, Peter S <1589...@bugs.launchpad.net> wrote: > If people keep whining about bugs in network-manager, without even > trying WICD (or the like) for a couple of weeks, this thread is > meaningless! > > I'm still not sure that the problems I experience are completely > unrelated to network-manager. I seem to have a more stable connection > with WICD, so far. But I have to try it for another few weeks before I > can say anything for sure. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1589401 > > Title: > cannot view wifi networks after re-enabling wifi > > Status in NetworkManager: > Confirmed > Status in network-manager package in Ubuntu: > Incomplete > > Bug description: > after re enabling wifi, up-down arrows just like wired network. cannot > see any wifi ssid. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/network-manager/+bug/1589401/+subscriptions > -- 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/1589401 Title: cannot view wifi networks after re-enabling wifi Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Incomplete Bug description: after re enabling wifi, up-down arrows just like wired network. cannot see any wifi ssid. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1589401/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1604062] Re: too easy to trigger the apps switcher / spread on desktop
I'm using a Nexus 7 tablet. Previously (around the time this bug was raised) I ran rc-proposed. Right now I have OTA-14 stable. Sometimes I use the tablet with external mouse and keyboard. When this bug was raised I was sharing the sentiment. With a mouse I often triggered it unintentionally. But there were also times where I did want to trigger it, but failed. I moved the mouse to the right, saw the spread come up, assumed it was fully triggered and started moving the mouse left again towards whereever I wanted to click, only to realize that the spread wasn't /fully/ triggered but only in some preview state and moving left would immediately collaps it. So I had to retry. Nowadays, I still sometimes trigger the spred even though I don't want to and sometimes I don't trigger it fully even when I want, but both has become less. Maybe it's just my muscle memory learning it, or maybe there has been some finetuning recently?! As for the suggestion to disable the edge gesture (mayben when no touch is present, or when a mouse is present). I guess it would be an option, but I think I might actually miss it. I tend to /stick/ to an input device for a period of time. Meaning when I'm typing, I will most definitely switch with Alt-Tab and not reach away from the keyboard to the mouse. Similarly when I am scrolling around with my finger on the screen I would dislike if if I /had/ to reach over to keyboard or mouse for anything. And also when I'm leaned back, surfing through some websites using the mouse, then I don't want to use anything else than the mouse to switch back to my news reader or music player. In those cases I find it quite nice to have the spread available when using only the mouse. It would be /possible/ to switch applications with the laucher on the left, but I do prefer the spread on the right. Bottom line of all my babbling, while it isn't perfect yet, it is a complicated story with many aspects that should be balanced and a /quick fix/ of /just/ turning it off without touch might be too simplistic. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1604062 Title: too easy to trigger the apps switcher / spread on desktop Status in Canonical System Image: New Status in Ubuntu UX: New Status in unity8 package in Ubuntu: Confirmed Bug description: too easy to trigger the apps switcher / spread on desktop :'( i liked this feature at first but now it's becoming super frustrating to use unity8. i accidentally trigger the spread way to often in many unwanted ways. 2/3 times when i want to restart and i go with the mouse on the indicator (top right) i trigger the spread, or when i want to scroll a page that is semi maximized to the right (ctrl super right), or when i'm playing neverball with the mouse etc To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1604062/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1176046] Re: isc-dhcp dhclient listens on extra random ports
> What will happen to existing Trusty users who are relying on the current ddns functionality? Existing Trusty user at next isc-dhcp-client pkg upgrade will automatically receive (Recommends: isc-dhcp-client-ddns). And for users bother by the extra random port they will simply have to apt-get purge isc-dhcp-client-ddns. Look regression details above for additionnal details. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1176046 Title: isc-dhcp dhclient listens on extra random ports Status in isc-dhcp package in Ubuntu: In Progress Status in isc-dhcp source package in Trusty: In Progress Bug description: [Impact] In trusty, there is only 1 version of dhclient, including #define NSUPDATE, which introduce DDNS functionnality. The DDNS functionnality, generate 2 random extra ports between 1024-65535. Impact reported by users : "One impact of these random ports is that security hardening becomes more difficult. The purpose of these random ports and security implications are unknown." "We have software that was using one of the lower udp ports but it happened to collide with dhclient which seems to allocate 2 random ports." There is a randomization mechanism in libdns that prevent dhclient to take the sysctl values into account (net.ipv4.ip_local_port_range & net.ipv4.ip_local_reserved_ports) to workaround this, and after discussion isc-dhcp upstream doesn't want to rely on kernel for randomization. There is no realtime configuration to disable the feature or workaround this. The only possible way is at compile time. I also talk with upstream maintainers, and there is no way they will accept to reduce the range (1024-65535) for security reason. Reducing the port range may facilitate the spoofing. Xenial has separated dhclient in two packages : isc-dhcp-client pkg : dhclient with DDNS functionality disabled (no random extra ports) isc-dhcp-client-ddns : dhclient with DDNS functionality enabled (with random extra ports) The goal here is to reproduce the same situation in Trusty, for this bug to be less painful for at least users that doesn't require DDNS functionnality. [Test Case] Run a Trusty image with following package : isc-dhcp-client isc-dhcp-common ``` dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc dhclient 1110 root 20u IPv4 11516 0t0 UDP *:64589 # <--- extra random port dhclient 1110 root 21u IPv6 11517 0t0 UDP *:7749 # <--- extra random port ``` [Regression Potential] * none expected I did the split such that users will automatically get isc-dhcp-client-ddns installed but users bothered by this bug then will have the option to switch to the one without it by uninstalling (isc-dhcp-client-ddns), so existing Trusty users can continue to use this DDNS functionality after the SRU without any necessary intervention. With isc-dhcp-client-ddns : dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc dhclient 1110 root 20u IPv4 11516 0t0 UDP *:64589 # <--- extra random port dhclient 1110 root 21u IPv6 11517 0t0 UDP *:7749 # <--- extra random port Without isc-dhcp-client-ddns : dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc Note that this is how Xenial does it. [Other Info] * See : https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1176046/comments/19 to look at my discussion with rbasak on if that approach would be acceptable for SRU. [Original Description] Ubuntu 13.04 Server 64-bit. Fresh install. Only one network adapter. dhclient process is listening on two randomly chosen udp ports in addition to the usual port 68. This appears to be a bug in the discovery code for probing information on interfaces in the system. Initial research of the code also suggested omapi, but adding omapi port to /etc/dhcp/dhclient.conf only opened a forth port with the two random udp ports still enabled. Version of included distro dhclient was 4.2.4. I also tested with the latest isc-dhclient-4.2.5-P1 and got the same results. Debian has the same bug: http://forums.debian.net/viewtopic.php?f=10&t=95273&p=495605#p495605 One impact of these random ports is that security hardening becomes more difficult. The purpose of these random ports and security implications are unknown. Example netstat -lnp output: udp0 0 0.0.0.0:21117 0.0.0.0:* 2659/dhclient udp0 0 0.0.0.0:68 0.0.0.0:* 2659/dhclient udp6 0 0 :::45664:::* 2659/dhclient To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1176046/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to
[Touch-packages] [Bug 1167014] Re: MIssing cmake files
I agree this bug should be closed. I encountered this issue when building https://github.com/andrewssobral/bgslibrary on Xenial However, this was due to the absence of the devel package (I only had the standard OpenCV package installed). Installing libopencv-dev fixed this issue as it brings the necessary cmake files, and I could build BGS. See http://packages.ubuntu.com/xenial/amd64/libopencv-dev/filelist for where they are located. ** Changed in: opencv (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to opencv in Ubuntu. https://bugs.launchpad.net/bugs/1167014 Title: MIssing cmake files Status in opencv package in Ubuntu: Invalid Bug description: This two files are part of libopencv-core-dev package in 12.04: /usr/share/OpenCV/OpenCVConfig.cmake /usr/share/OpenCV/OpenCVConfig-version.cmake But they disappeared in 12.10 and 13.04. This is causing problems when compiling projects using cmake and opencv. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencv/+bug/1167014/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1176046] Re: isc-dhcp dhclient listens on extra random ports
I picked "Recommends:" based on following explanation : Package A recommends Package B, if the package maintainer judges that most users would not want A without also having the functionality provided by B. Ref: https://www.debian.org/doc/manuals/debian-faq/ch-pkg_basics.en.html Eric -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1176046 Title: isc-dhcp dhclient listens on extra random ports Status in isc-dhcp package in Ubuntu: In Progress Status in isc-dhcp source package in Trusty: In Progress Bug description: [Impact] In trusty, there is only 1 version of dhclient, including #define NSUPDATE, which introduce DDNS functionnality. The DDNS functionnality, generate 2 random extra ports between 1024-65535. Impact reported by users : "One impact of these random ports is that security hardening becomes more difficult. The purpose of these random ports and security implications are unknown." "We have software that was using one of the lower udp ports but it happened to collide with dhclient which seems to allocate 2 random ports." There is a randomization mechanism in libdns that prevent dhclient to take the sysctl values into account (net.ipv4.ip_local_port_range & net.ipv4.ip_local_reserved_ports) to workaround this, and after discussion isc-dhcp upstream doesn't want to rely on kernel for randomization. There is no realtime configuration to disable the feature or workaround this. The only possible way is at compile time. I also talk with upstream maintainers, and there is no way they will accept to reduce the range (1024-65535) for security reason. Reducing the port range may facilitate the spoofing. Xenial has separated dhclient in two packages : isc-dhcp-client pkg : dhclient with DDNS functionality disabled (no random extra ports) isc-dhcp-client-ddns : dhclient with DDNS functionality enabled (with random extra ports) The goal here is to reproduce the same situation in Trusty, for this bug to be less painful for at least users that doesn't require DDNS functionnality. [Test Case] Run a Trusty image with following package : isc-dhcp-client isc-dhcp-common ``` dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc dhclient 1110 root 20u IPv4 11516 0t0 UDP *:64589 # <--- extra random port dhclient 1110 root 21u IPv6 11517 0t0 UDP *:7749 # <--- extra random port ``` [Regression Potential] * none expected I did the split such that users will automatically get isc-dhcp-client-ddns installed but users bothered by this bug then will have the option to switch to the one without it by uninstalling (isc-dhcp-client-ddns), so existing Trusty users can continue to use this DDNS functionality after the SRU without any necessary intervention. With isc-dhcp-client-ddns : dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc dhclient 1110 root 20u IPv4 11516 0t0 UDP *:64589 # <--- extra random port dhclient 1110 root 21u IPv6 11517 0t0 UDP *:7749 # <--- extra random port Without isc-dhcp-client-ddns : dhclient 1110 root 6u IPv4 11535 0t0 UDP *:bootpc Note that this is how Xenial does it. [Other Info] * See : https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1176046/comments/19 to look at my discussion with rbasak on if that approach would be acceptable for SRU. [Original Description] Ubuntu 13.04 Server 64-bit. Fresh install. Only one network adapter. dhclient process is listening on two randomly chosen udp ports in addition to the usual port 68. This appears to be a bug in the discovery code for probing information on interfaces in the system. Initial research of the code also suggested omapi, but adding omapi port to /etc/dhcp/dhclient.conf only opened a forth port with the two random udp ports still enabled. Version of included distro dhclient was 4.2.4. I also tested with the latest isc-dhclient-4.2.5-P1 and got the same results. Debian has the same bug: http://forums.debian.net/viewtopic.php?f=10&t=95273&p=495605#p495605 One impact of these random ports is that security hardening becomes more difficult. The purpose of these random ports and security implications are unknown. Example netstat -lnp output: udp0 0 0.0.0.0:21117 0.0.0.0:* 2659/dhclient udp0 0 0.0.0.0:68 0.0.0.0:* 2659/dhclient udp6 0 0 :::45664:::* 2659/dhclient To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1176046/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages M
[Touch-packages] [Bug 1646517] Re: In unity8-session snap on Core 16, no battery icon is shown
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: indicator-power (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1646517 Title: In unity8-session snap on Core 16, no battery icon is shown Status in Canonical System Image: New Status in indicator-power package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: I was testing the unity8-session in a Core 16 VM, and I noticed that indicator-power wasn't showing an icon in the top panel. When I opened the indicator menu, indicator-power seemed to be filling out its menu correctly, so it is running. It just didn't give an icon that u8 knew about (or we aren't bundling the right icons into the snap?). But I bet that the indicator is giving back an absolute path that points outside the snap. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1646517/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1646517] Re: In unity8-session snap on Core 16, no battery icon is shown
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity8 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1646517 Title: In unity8-session snap on Core 16, no battery icon is shown Status in Canonical System Image: New Status in indicator-power package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: I was testing the unity8-session in a Core 16 VM, and I noticed that indicator-power wasn't showing an icon in the top panel. When I opened the indicator menu, indicator-power seemed to be filling out its menu correctly, so it is running. It just didn't give an icon that u8 knew about (or we aren't bundling the right icons into the snap?). But I bet that the indicator is giving back an absolute path that points outside the snap. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1646517/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1648901] Re: SPNEGO crash on mechanism failure
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: krb5 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1648901 Title: SPNEGO crash on mechanism failure Status in krb5 package in Ubuntu: Confirmed Bug description: Chrome (and other things) crash when Kerberos fails to authenticate: https://bugs.chromium.org/p/chromium/issues/detail?id=554905 This was fixed in MIT krb5 in January: https://github.com/krb5/krb5/pull/385 Thread 22 "Chrome_IOThread" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fffdd687700 (LWP 14851)] spnego_gss_inquire_context (minor_status=0x7fffdd68573c, context_handle=0x0, src_name=0x7fffdd685670, targ_name=0x7fffdd685668, lifetime_rec=0x7fffdd685738, mech_type=0x7fffdd685660, ctx_flags=0x7fffdd685734, locally_initiated=0x7fffdd685730, opened=0x7fffdd68572c) at ../../../../src/lib/gssapi/spnego/spnego_mech.c:2315 2315 ../../../../src/lib/gssapi/spnego/spnego_mech.c: No such file or directory. (gdb) bt #0 spnego_gss_inquire_context (minor_status=0x7fffdd68573c, context_handle=0x0, src_name=0x7fffdd685670, targ_name=0x7fffdd685668, lifetime_rec=0x7fffdd685738, mech_type=0x7fffdd685660, ctx_flags=0x7fffdd685734, locally_initiated=0x7fffdd685730, opened=0x7fffdd68572c) at ../../../../src/lib/gssapi/spnego/spnego_mech.c:2315 #1 0x7fffef72be54 in gss_inquire_context (minor_status=0x7fffdd68573c, context_handle=, src_name=0x7fffdd685788, targ_name=0x7fffdd685750, lifetime_rec=0x7fffdd685738, mech_type=0x7fffdd685780, ctx_flags=0x7fffdd685734, locally_initiated=0x7fffdd685730, opened=0x7fffdd68572c) at ../../../../src/lib/gssapi/mechglue/g_inq_context.c:114 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1648901/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1647031] Re: systemd-resolved’s 127.0.0.53 server does not follow CNAME records
** Tags added: zesty
--
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/1647031
Title:
systemd-resolved’s 127.0.0.53 server does not follow CNAME records
Status in systemd:
New
Status in systemd package in Ubuntu:
Confirmed
Bug description:
$ systemd-resolve www.freedesktop.org
www.freedesktop.org: 131.252.210.176
2610:10:20:722:a800:ff:feda:470f
(annarchy.freedesktop.org)
-- Information acquired via protocol DNS in 673.6ms.
-- Data is authenticated: no
$ ping www.freedesktop.org
ping: www.freedesktop.org: Name or service not known
$ 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 127.0.0.53
$ dig +no{cmd,comments,stats} www.freedesktop.org @127.0.0.53
;www.freedesktop.org. IN A
www.freedesktop.org. 7146IN CNAME annarchy.freedesktop.org.
$ dig +no{cmd,comments,stats} www.freedesktop.org @8.8.8.8
;www.freedesktop.org. IN A
www.freedesktop.org. 14399 IN CNAME annarchy.freedesktop.org.
annarchy.freedesktop.org. 14399 IN A 131.252.210.176
I trust it needn’t be explained why this makes the internet almost
completely useless in zesty.
To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1647031/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1648435] Re: 5 useless buttons on the lock-screen
@bogdanke8, @zyga, thanks for your kind words :) >From what I've looked in the source code, to achieve this effect there need to >be changes in: 1. Greeter Prompt http://bazaar.launchpad.net/~unity-team/unity8/trunk/view/head:/qml/Greeter/GreeterPrompt.qml 2. Keyboard for numbers: http://bazaar.launchpad.net/~phablet-team/ubuntu-keyboard/trunk/view/head:/qml/languages/Keyboard_numbers.qml Of course I could be wrong :) Let's wait for UX team decision first though. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1648435 Title: 5 useless buttons on the lock-screen Status in Canonical System Image: New Status in Ubuntu UX: New Status in ubuntu-keyboard package in Ubuntu: Confirmed Bug description: bq e4.5 OTA-14 In the case I use '4-digit passcode' for 'Lock security', the new keyboard visible on the lock screen has 5 buttons out of 18 (counting 'Cancel' and 'Emergency') which do not have any use. I marked them on the attached screenshot. The same keyboard appears when I create or change the 4-digit passcode in System Settings. IMO it'd be better to remove those useless buttons, and possibly rearrange the useful ones. That could make it look better and provide better/bigger touch target. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1648435/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1004465] Re: heimdal and mit kinit doesn't handle expired credentials
** Changed in: heimdal (Debian)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to krb5 in Ubuntu.
https://bugs.launchpad.net/bugs/1004465
Title:
heimdal and mit kinit doesn't handle expired credentials
Status in heimdal package in Ubuntu:
Confirmed
Status in krb5 package in Ubuntu:
Fix Released
Status in heimdal package in Debian:
Fix Released
Bug description:
Hi.
ubuntu 12.04 i386,amd64
For now kerberos (both - mit and heimdal) kinit doesn't handle expired (or
'must change') passwords. That's a serious regression (lucid is fine) - no
integration (pam) into kerberos environments that use password expiration could
be done. Tested with heimdal kdc (file and ldap db) and win2008r2 kdc on
several machines. This bug stops us from migrating to the next LTS in our
environment. Thinking it should be fixed.
Heimdal KDC logs are in the attachment. What I can see in these logs is that
lucid heimdal kinit doesn't send REQ-ENC-PA-REP patype while precise kinits
send. May this be the reason? If more info is needed please just ask.
How to reproduce:
# apt-get -y install heimdal-kdc
# cat > /etc/krb5.conf
[libdefaults]
default_realm = TEST.LAN
[realms]
TEST.LAN = {
kdc=127.0.0.1
}
# kadmin -l init TEST.LAN
# kadmin -l add test
Max ticket life [1 day]:
Max renewable life [1 week]:
Principal expiration time [never]:
Password expiration time [never]:2000-01-01 # Set expiration time to the
past
Attributes []:
Policy [default]:
t...@test.lan's Password:
Verify password - t...@test.lan's Password:
# apt-get -y install heimdal-clients
# dpkg -l |grep heimdal-clients
ii heimdal-clients 1.6~git20120311.dfsg.1-2 Heimdal
Kerberos - clients
# kinit --version
kinit (Heimdal 1.5.99)
Copyright 1995-2011 Kungliga Tekniska Högskolan
Send bug-reports to heimdal-b...@h5l.org
# kinit test
t...@test.lan's Password:
kinit: krb5_get_init_creds: Password has expired
And no asking for changing password.
# apt-get -y install krb5-user
# dpkg -l |grep krb5-user
ii krb5-user 1.10+dfsg~beta1-2Basic
programs to authenticate using MIT Kerberos
# kinit test
Password for t...@test.lan:
kinit: Generic preauthentication failure while getting initial credentials
And no asking for changing password again.
But kpasswd works fine (heimdal & mit):
# kpasswd test
t...@test.lan's Password:
Your password will expire at Tue Jan 2 02:59:59 2000
New password for t...@test.lan:
Verify password - New password for t...@test.lan:
Success : Password changed
The same time all works fine with ubuntu 10.04 heimdal (1.2) and
freebsd 9.0 heimdal (1.1) (kdc is still from ubuntu 12.04), it does
change password if it's required.
Thanks.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/1004465/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1490212] Re: "Modaliases" field missing from debian control file
** No longer affects: software-properties (Ubuntu) -- 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/1490212 Title: "Modaliases" field missing from debian control file Status in b43-fwcutter package in Ubuntu: Expired Bug description: The b43 module is not listed as an option by the "additional drivers" section of the software-properties-gtk utility. This takes its information from the ubuntu-drivers-common package and a bug has been reported against that package (https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers- common/+bug/1186779 ). However, if I'm reading things correctly, the firmware-b43-installer package could solve this by providing a modaliases field in the debian control file. For example, the bcmwl-kernel-source package has the line: Modaliases: wl(pci:v14E4d*sv*sd*bc02sc80i*) This would be scanned by the ubuntu-drivers-common package and consequently appear in software-properties-gtk. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/b43-fwcutter/+bug/1490212/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1637026] Re: kill incorrectly parses negative PIDs
** Changed in: procps (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1637026 Title: kill incorrectly parses negative PIDs Status in procps package in Ubuntu: Fix Released Status in procps source package in Xenial: Fix Released Bug description: [Impact] When kill is called with a negative argument, incorrect parsing can lead it to call sys_kill(-1), thus sending a signal to all permitted processes on the system. A couple of users have hit this while deploying Hadoop, which seems to tickle this - basically killing everything on the system. [Test Case] Though I don't know what Hadoop is calling, here's a couple of ways to trigger this: One possibility is if kill were called w/ a numeric signal that happened to start with a '1' and while omitting the required argument: kill -12 Another would be to specify a numeric signal (that again happened to start with a 1) multiple times: kill -13 -13 12345 [Regression Risk] This is a backport from upstream that is already available in 16.10, with no known regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1637026/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1643084] Re: [REGRESSION] kill segfaults w/ single, negative PID
** Tags added: regression-update -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1643084 Title: [REGRESSION] kill segfaults w/ single, negative PID Status in procps package in Ubuntu: Fix Released Status in procps source package in Xenial: Fix Released Bug description: [Impact] The kill binary will segfault when called w/ a single, negative PID. This breaks a use case where you maybe sending the default signal (SIGTERM) to all processes (-1) or all processes in a process group (-https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1643084/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1490349] Re: 15:10 and 16.04: bluetoothd reports "Not enough handles to register service" at start
Same issue here, bluetooth mouse often hans. journalctl --unit=bluetooth -- Logs begin at 日 2016-12-11 10:01:22 CST, end at 日 2016-12-11 11:32:43 CST. -- 12月 11 10:01:25 fengyu-laptop bluetoothd[2142]: Bluetooth daemon 5.37 12月 11 10:01:25 fengyu-laptop bluetoothd[2142]: Starting SDP server 12月 11 10:01:25 fengyu-laptop systemd[1]: Starting Bluetooth service... 12月 11 10:01:25 fengyu-laptop bluetoothd[2142]: Bluetooth management interface 1.10 initialized 12月 11 10:01:25 fengyu-laptop bluetoothd[2142]: Failed to obtain handles for "Service Changed" characteristic 12月 11 10:01:25 fengyu-laptop bluetoothd[2142]: Not enough free handles to register service 12月 11 10:01:25 fengyu-laptop bluetoothd[2142]: Error adding Link Loss service 12月 11 10:01:25 fengyu-laptop bluetoothd[2142]: Not enough free handles to register service 12月 11 10:01:25 fengyu-laptop bluetoothd[2142]: Not enough free handles to register service 12月 11 10:01:25 fengyu-laptop bluetoothd[2142]: Not enough free handles to register service 12月 11 10:01:25 fengyu-laptop bluetoothd[2142]: Current Time Service could not be registered 12月 11 10:01:25 fengyu-laptop bluetoothd[2142]: gatt-time-server: Input/output error (5) 12月 11 10:01:25 fengyu-laptop bluetoothd[2142]: Not enough free handles to register service 12月 11 10:01:25 fengyu-laptop bluetoothd[2142]: Not enough free handles to register service 12月 11 10:01:25 fengyu-laptop bluetoothd[2142]: Sap driver initialization failed. 12月 11 10:01:25 fengyu-laptop bluetoothd[2142]: sap-server: Operation not permitted (1) 12月 11 10:01:25 fengyu-laptop systemd[1]: Started Bluetooth service. 12月 11 10:01:27 fengyu-laptop bluetoothd[2142]: Endpoint registered: sender=:1.29 path=/MediaEndpoint/A2DPSource 12月 11 10:01:27 fengyu-laptop bluetoothd[2142]: Endpoint registered: sender=:1.29 path=/MediaEndpoint/A2DPSink 12月 11 10:07:31 fengyu-laptop bluetoothd[2142]: Unable to register GATT service with handle 0x000c for device C5:5B:CD:DB:C5:D1 12月 11 10:07:31 fengyu-laptop bluetoothd[2142]: Unable to register GATT service with handle 0x0017 for device C5:5B:CD:DB:C5:D1 12月 11 10:07:31 fengyu-laptop bluetoothd[2142]: Unable to register GATT service with handle 0x001b for device C5:5B:CD:DB:C5:D1 12月 11 11:16:20 fengyu-laptop bluetoothd[2142]: Unable to register GATT service with handle 0x000c for device C5:5B:CD:DB:C5:D1 12月 11 11:16:20 fengyu-laptop bluetoothd[2142]: Unable to register GATT service with handle 0x0017 for device C5:5B:CD:DB:C5:D1 12月 11 11:16:20 fengyu-laptop bluetoothd[2142]: Unable to register GATT service with handle 0x001b for device C5:5B:CD:DB:C5:D1 12月 11 11:18:09 fengyu-laptop bluetoothd[2142]: Unable to register GATT service with handle 0x000c for device C5:5B:CD:DB:C5:D1 12月 11 11:18:09 fengyu-laptop bluetoothd[2142]: Unable to register GATT service with handle 0x0017 for device C5:5B:CD:DB:C5:D1 12月 11 11:18:09 fengyu-laptop bluetoothd[2142]: Unable to register GATT service with handle 0x001b for device C5:5B:CD:DB:C5:D1 12月 11 11:26:21 fengyu-laptop bluetoothd[2142]: Unable to register GATT service with handle 0x000c for device C5:5B:CD:DB:C5:D1 12月 11 11:26:21 fengyu-laptop bluetoothd[2142]: Unable to register GATT service with handle 0x0017 for device C5:5B:CD:DB:C5:D1 12月 11 11:26:21 fengyu-laptop bluetoothd[2142]: Unable to register GATT service with handle 0x001b for device C5:5B:CD:DB:C5:D1 12月 11 11:29:41 fengyu-laptop systemd[1]: Stopping Bluetooth service... 12月 11 11:29:41 fengyu-laptop bluetoothd[2142]: Terminating 12月 11 11:29:46 fengyu-laptop bluetoothd[2142]: Endpoint unregistered: sender=:1.29 path=/MediaEndpoint/A2DPSource 12月 11 11:29:46 fengyu-laptop bluetoothd[2142]: Endpoint unregistered: sender=:1.29 path=/MediaEndpoint/A2DPSink 12月 11 11:29:46 fengyu-laptop systemd[1]: Stopped Bluetooth service. 12月 11 11:29:46 fengyu-laptop systemd[1]: Starting Bluetooth service... 12月 11 11:29:46 fengyu-laptop systemd[1]: Started Bluetooth service. 12月 11 11:29:46 fengyu-laptop bluetoothd[1348]: Bluetooth daemon 5.37 12月 11 11:29:46 fengyu-laptop bluetoothd[1348]: Starting SDP server 12月 11 11:29:46 fengyu-laptop bluetoothd[1348]: Bluetooth management interface 1.10 initialized 12月 11 11:29:46 fengyu-laptop bluetoothd[1348]: Failed to obtain handles for "Service Changed" characteristic 12月 11 11:29:46 fengyu-laptop bluetoothd[1348]: Not enough free handles to register service 12月 11 11:29:46 fengyu-laptop bluetoothd[1348]: Error adding Link Loss service 12月 11 11:29:46 fengyu-laptop bluetoothd[1348]: Not enough free handles to register service 12月 11 11:29:46 fengyu-laptop bluetoothd[1348]: Not enough free handles to register service 12月 11 11:29:46 fengyu-laptop bluetoothd[1348]: Not enough free handles to register service 12月 11 11:29:46 fengyu-laptop bluetoothd[1348]: Current Time Service could not be registered 12月 11 11:29:46 fengyu-laptop bluetoothd[1348]: gatt-time-server: Input/output error (5) 12月 11 11:29:46 fengyu-laptop bluetoo
[Touch-packages] [Bug 1644859] Re: Update Error Brokencount: I cannot load any further updates for about 4 days now...
This bug is all fixed, I don't know how to mark it completed. Thank you Tyler Hicks for helping me! Tom G. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1644859 Title: Update Error Brokencount: I cannot load any further updates for about 4 days now... Status in apt package in Ubuntu: Invalid Bug description: This package system is broken: Check if you are using third party repositories. If so disable them, since they are a common source of problems. Furthermore run the following command in a Terminal: apt-get install -f "when I run apt-get install -f" I get the following error: apt-get install -f E: Could not open lock file /var/lib/dpkg/lock - open (13: Permission denied) E: Unable to lock the administration directory (/var/lib/dpkg/), are you root? ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: firefox 50.0+build2-0ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.4.0-49.70-generic 4.4.30 Uname: Linux 4.4.0-49-generic x86_64 NonfreeKernelModules: wl AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom1796 F pulseaudio BuildID: 20161114144739 Channel: Unavailable CurrentDesktop: Unity Date: Fri Nov 25 09:49:44 2016 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2014-08-11 (836 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) IpRoute: default via 192.168.1.1 dev eth0 proto static metric 100 default via 192.168.200.1 dev wlan0 proto static metric 600 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.218 metric 100 192.168.200.0/24 dev wlan0 proto kernel scope link src 192.168.200.6 metric 600 Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-70901242-37de-43fb-9bed-f897e2161106 Plugins: iTunes Application Detector - /usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so (rhythmbox-mozilla) Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=50.0/20161114144739 (In use) RelatedPackageVersions: rhythmbox-mozilla 3.3-1ubuntu7 RunningIncompatibleAddons: False SourcePackage: firefox SubmittedCrashIDs: bp-70901242-37de-43fb-9bed-f897e2161106 bp-921bd37f-d835-43f3-b547-842c12151115 bp-638f2494-0693-45e3-a276-d36032150714 Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to xenial on 2016-05-04 (205 days ago) dmi.bios.date: 06/04/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0KU184 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd06/04/2013:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn0KU184:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D630 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1644859/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1629009] Re: Does not work inside a snap due to hardcoded paths
This bug was fixed in the package indicator-network -
0.9.0+17.04.20161205.1-0ubuntu1
---
indicator-network (0.9.0+17.04.20161205.1-0ubuntu1) zesty; urgency=medium
[ Pete ]
* Add ethernet support to indicator (and NM dbus template).
* Switch to common active connection interface throughout the codebase.
* Re-enable tests on all arches except powerpc, ppc64el, s390x.
* Fix Wi-Fi widget visibility.
[ Michael Terry ]
* Work inside a snap by prefixing hard coded paths with $SNAP. (LP:
#1629009)
-- Pete Woods Mon, 05 Dec 2016 18:16:19
+
** Changed in: indicator-network (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to address-book-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1629009
Title:
Does not work inside a snap due to hardcoded paths
Status in Canonical System Image:
In Progress
Status in Ubuntu File Manager App:
Fix Released
Status in address-book-app package in Ubuntu:
Fix Released
Status in address-book-service package in Ubuntu:
Fix Released
Status in camera-app package in Ubuntu:
In Progress
Status in dialer-app package in Ubuntu:
Fix Released
Status in gallery-app package in Ubuntu:
Fix Released
Status in history-service package in Ubuntu:
New
Status in indicator-bluetooth package in Ubuntu:
Fix Released
Status in indicator-display package in Ubuntu:
New
Status in indicator-keyboard package in Ubuntu:
In Progress
Status in indicator-location package in Ubuntu:
Fix Released
Status in indicator-messages package in Ubuntu:
Fix Released
Status in indicator-network package in Ubuntu:
Fix Released
Status in indicator-power package in Ubuntu:
Fix Released
Status in indicator-session package in Ubuntu:
Fix Released
Status in indicator-sound package in Ubuntu:
Fix Released
Status in indicator-transfer package in Ubuntu:
Fix Released
Status in maliit-framework package in Ubuntu:
In Progress
Status in mediaplayer-app package in Ubuntu:
Fix Released
Status in mediascanner2 package in Ubuntu:
Fix Released
Status in messaging-app package in Ubuntu:
Fix Released
Status in policykit-unity8 package in Ubuntu:
Fix Released
Status in sync-monitor package in Ubuntu:
New
Status in telephony-service package in Ubuntu:
In Progress
Status in ubuntu-keyboard package in Ubuntu:
In Progress
Status in ubuntu-system-settings package in Ubuntu:
Fix Released
Status in ubuntu-terminal-app package in Ubuntu:
Fix Released
Status in ubuntu-touch-session package in Ubuntu:
In Progress
Status in unity-scope-scopes package in Ubuntu:
Won't Fix
Status in unity-scopes-api package in Ubuntu:
Fix Released
Status in unity-scopes-shell package in Ubuntu:
Fix Released
Status in unity8 package in Ubuntu:
Fix Released
Status in webbrowser-app package in Ubuntu:
Fix Released
Bug description:
Some apps can't find their main qml file. Error messages like:
"file:///build/messaging-app-gcXPE6/messaging-
app-0.1+16.04.20160831/src/qml/messaging-app.qml: File not found"
(in my case, the file was in /snap/unity8-session/x24/usr/share
/messaging-app/messaging-app.qml)
Seems due to code like the following in config.h.in. Probably needs
to consider the value of $SNAP or just be a little more forgiving.
inline bool isRunningInstalled() {
static bool installed = (QCoreApplication::applicationDirPath() ==
QDir(("@CMAKE_INSTALL_PREFIX@/@CMAKE_INSTALL_BINDIR@")).canonicalPath());
return installed;
}
inline QString messagingAppDirectory() {
if (isRunningInstalled()) {
return QString("@CMAKE_INSTALL_PREFIX@/@MESSAGING_APP_DIR@/");
} else {
return QString("@CMAKE_SOURCE_DIR@/src/qml/");
}
}
inline QString ubuntuPhonePluginPath() {
if (isRunningInstalled()) {
return QString::null;
} else {
return QString("@CMAKE_SOURCE_DIR@/");
}
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1629009/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1631883] Re: aaaa
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1631883 Title: Status in xorg package in Ubuntu: Expired Bug description: aaa ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-41.61-generic 4.4.21 Uname: Linux 4.4.0-41-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: [[0;32m OK [0m] Started LSB: Set the CPU Frequency Scaling governor to "ondemand". [[0;32m OK [0m] Started Raise network interfaces. [[0;32m OK [0m] Reached target Network. CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Oct 10 11:17:27 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Core Processor Integrated Graphics Controller [1028:0428] InstallationDate: Installed on 2016-06-22 (109 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude E5510 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-41-generic root=UUID=85bcc377-e365-4b9d-8558-f6bb690436a2 ro quiet plymouth:debug drm.debug=0xe splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/03/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 09M4GV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd09/03/2010:svnDellInc.:pnLatitudeE5510:pvr0001:rvnDellInc.:rn09M4GV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5510 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Oct 10 10:31:30 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id9708 vendor AUO xserver.version: 2:1.18.4-0ubuntu0.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1631883/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1626721] Re: OwnCloud account does not accept IP address.
[Expired for account-plugins (Ubuntu) because there has been no activity for 60 days.] ** Changed in: account-plugins (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1626721 Title: OwnCloud account does not accept IP address. Status in account-plugins package in Ubuntu: Expired Bug description: I've tried to connect my bq Aquaris 4.5 with my OwnCloud instance, however I'm always getting a "Invalid host URL" message. I tried the following: 1. Open the Calendar app. 2. Open the list of calendars. 3. Select "Add online Calendar". 4. Select "ownCloud". 5. Under URL I entered the IP address of my server. Now, you have to know that my server is residing in my local network (and I have no intention of syncing my calendars to my phone outside of my local network) so I entered (without quotes, "x" is a placeholder for a valid number) "https://192.168.x.x/~user/"; as URL, however it is rejected. I tried with only the IP address and it also gives me the "Invalid host URL" message. Additionally, I use a self-signed certificate (because I'm the only one using this server), but that might be a completely unrelated topic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1626721/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
