[Touch-packages] [Bug 1670313] Re: armhf unit tests as root fail on adt tests, never run on builders

2022-01-26 Thread Danny Mount
thanks all !

-- 
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/1670313

Title:
  armhf unit tests as root fail on adt tests, never run on builders

Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  armhf unit tests as root fail on adt tests, never run on builders

  xnox should fix.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1670313/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1925833] Re: apt-transport-https reparses URLs, breaking CloudFront signing

2021-04-23 Thread Danny Sauer
Great, thanks for sharing both answers. :)

-- 
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/1925833

Title:
  apt-transport-https reparses URLs, breaking CloudFront signing

Status in apt package in Ubuntu:
  Fix Released

Bug description:
  CloudFront URL signing requires that the the whole URL matches the signature, 
as compared to S3 URLs which prune the querystring before validating the 
signature. The URL re-parsing which I'm pretty sure was introduced in resolving 
#1651923 decodes some HTML entities which were encoded before signing. That 
invalidates the signature and results in permission denied errors. In my case, 
the equal and semicolon chars from the return-content-disposition header are 
being decoded, but it applies to any entity which is "optionally" encoded.
 
  Personally, I think that the URL returned in a Location: redirect header 
should be handled as-is, and if some piece of garbage http server is generating 
redirects which contain spaces or are otherwise invalid, the problem lies with 
the web server generating invalid redirects and not in apt failing to follow 
broken URLs.  I say that knowing full well that the http spec says those things 
should be identical, so CloudFront also falls into the general "garbage" 
category by breaking the spec by requiring a specific format for identical 
characters.

  Either way, things are what they are.  Rather than unnecessarily fully
  reencoding the URL, I'd suggest that apt-transport-https (and
  presumably the http transport as well, but I don't know) should at
  most just replace the spaces with plusses or %20s to keep the original
  bug resolved without breaking other stuff. :)

  PS: I tried to report this against the apt-transport-https package,
  but the bug tool says that doesn't exist in Ubuntu.  That's weird,
  considering it's definitely a package
  (https://packages.ubuntu.com/groovy/apt-transport-https), so I assume
  the apt maintainer will know how to triage. Sorry.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1925833/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1925833] [NEW] apt-transport-https reparses URLs, breaking CloudFront signing

2021-04-23 Thread Danny Sauer
Public bug reported:

CloudFront URL signing requires that the the whole URL matches the signature, 
as compared to S3 URLs which prune the querystring before validating the 
signature. The URL re-parsing which I'm pretty sure was introduced in resolving 
#1651923 decodes some HTML entities which were encoded before signing. That 
invalidates the signature and results in permission denied errors. In my case, 
the equal and semicolon chars from the return-content-disposition header are 
being decoded, but it applies to any entity which is "optionally" encoded.
   
Personally, I think that the URL returned in a Location: redirect header should 
be handled as-is, and if some piece of garbage http server is generating 
redirects which contain spaces or are otherwise invalid, the problem lies with 
the web server generating invalid redirects and not in apt failing to follow 
broken URLs.  I say that knowing full well that the http spec says those things 
should be identical, so CloudFront also falls into the general "garbage" 
category by breaking the spec by requiring a specific format for identical 
characters.

Either way, things are what they are.  Rather than unnecessarily fully
reencoding the URL, I'd suggest that apt-transport-https (and presumably
the http transport as well, but I don't know) should at most just
replace the spaces with plusses or %20s to keep the original bug
resolved without breaking other stuff. :)

PS: I tried to report this against the apt-transport-https package, but
the bug tool says that doesn't exist in Ubuntu.  That's weird,
considering it's definitely a package
(https://packages.ubuntu.com/groovy/apt-transport-https), so I assume
the apt maintainer will know how to triage. Sorry.

** Affects: apt (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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/1925833

Title:
  apt-transport-https reparses URLs, breaking CloudFront signing

Status in apt package in Ubuntu:
  New

Bug description:
  CloudFront URL signing requires that the the whole URL matches the signature, 
as compared to S3 URLs which prune the querystring before validating the 
signature. The URL re-parsing which I'm pretty sure was introduced in resolving 
#1651923 decodes some HTML entities which were encoded before signing. That 
invalidates the signature and results in permission denied errors. In my case, 
the equal and semicolon chars from the return-content-disposition header are 
being decoded, but it applies to any entity which is "optionally" encoded.
 
  Personally, I think that the URL returned in a Location: redirect header 
should be handled as-is, and if some piece of garbage http server is generating 
redirects which contain spaces or are otherwise invalid, the problem lies with 
the web server generating invalid redirects and not in apt failing to follow 
broken URLs.  I say that knowing full well that the http spec says those things 
should be identical, so CloudFront also falls into the general "garbage" 
category by breaking the spec by requiring a specific format for identical 
characters.

  Either way, things are what they are.  Rather than unnecessarily fully
  reencoding the URL, I'd suggest that apt-transport-https (and
  presumably the http transport as well, but I don't know) should at
  most just replace the spaces with plusses or %20s to keep the original
  bug resolved without breaking other stuff. :)

  PS: I tried to report this against the apt-transport-https package,
  but the bug tool says that doesn't exist in Ubuntu.  That's weird,
  considering it's definitely a package
  (https://packages.ubuntu.com/groovy/apt-transport-https), so I assume
  the apt maintainer will know how to triage. Sorry.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1925833/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1651923] Re: apt https method decodes redirect locations and sends them to the destination undecoded.

2021-04-23 Thread Danny Sauer
This fix breaks CloudFront URLs, because the reencoding of URLs results
in some HTML entities being replaced by their plain characters.
CloudFront signing requires that the the whole URL matches the
signature, as compared to S3 URLs which prune the querystring before
validating the signature.  That explains why this fix worked ok on S3.

I'll open a new bug since this is so old that reopening doesn't make
sense, but also making a note here for future web search purposes.

-- 
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/1651923

Title:
  apt https method decodes redirect locations and sends them to the
  destination undecoded.

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Released
Status in apt source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  Downloads via HTTPS fail if the URL contains a space (before yakkety only if 
there is no redirect from a previous space-free https URL). This breaks 
packages like ttf-mscorefonts-installer and various third party hosters.

  [Test case]
  Install/Upgrade apt-transport-https, that's where the fix is.

  Check that

  /usr/lib/apt/apt-helper download-file
  
http://kxstudio.linuxaudio.org/repo/pool/free/ardour4_4.7.0-1kxstudio1_i386.deb
  test.deb

  can successfully download the file (or at least start downloading it)
  and does not fail early with a 505 HTTP version not supported error
  message.

  This problem does not occur with that file on xenial, as it first
  redirects to an https URI without a space which then redirects to an
  HTTPS uri with a space (http w/o space -> https w/o space -> https w/
  space). In xenial, https->https redirects where handled internally by
  curl.

  Another test (applicable to xenial) is to install ttf-mscorefonts-
  installer.

  [Regression potential]
  The added code is:
     Uri.Path = QuoteString(Uri.Path, "+~ ");

  Some servers might not like + or ~ being quoted. We use the same
  quoting call for the http method too, though, so it seems highly
  unlikely to cause an issue.

  [Original bug report]
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.10
  Release:  16.10
  Codename: yakkety

  apt version 1.3.3 (also tried 1.4-beta2 .deb, same results)

  When trying to install a package hosted on s3 from the kxstudio repo,
  the download fails with an HTTP error:

  nico@nico-lenovo-ubuntu:~/Downloads$ sudo apt-get install wineasio-amd64
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following additional packages will be installed:
    wine1.6-amd64
  The following NEW packages will be installed
    wine1.6-amd64 wineasio-amd64
  0 to upgrade, 2 to newly install, 0 to remove and 1 not to upgrade.
  Need to get 30.9 kB/32.6 kB of archives.
  After this operation, 184 kB of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Err:1 http://kxstudio.linuxaudio.org/repo stable/free amd64 wineasio-amd64 
amd64 0.9.0+git20110613-2kxstudio3
    505  HTTP Version not supported
  E: Failed to fetch 
https://github-cloud.s3.amazonaws.com/releases/39372848/0f048802-2fb5-11e5-9d8c-907ec7b97c46.deb?X-Amz-Algorithm=AWS4-HMAC-SHA256=AKIAISTNZFOVBIJMK3TQ/20161222/us-east-1/s3/aws4_request=20161222T022041Z=300=750f9b2ee076dcb8ae6992cae911f43208b3eec41976362cebf694e3c72b7aef=host_id=0=attachment;
 
filename=wineasio-amd64_0.9.0.git20110613-2kxstudio3_amd64.deb=application/octet-stream
  505  HTTP Version not supported
  E: Unable to fetch some archives, maybe run apt-get update or try with 
--fix-missing?

  Error allegedly not present in Ubuntu 14.04 and 16.04

  More details in these forum posts:

  https://github.com/KXStudio/Repository/issues/73#issuecomment-268649503

  https://www.linuxmusicians.com/viewtopic.php?t=16056

  https://www.drupal.org/node/2324991 (clues on root cause)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: apt 1.3.3
  ProcVersionSignature: Ubuntu 4.8.0-30.32-lowlatency 4.8.6
  Uname: Linux 4.8.0-30-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Thu Dec 22 02:31:47 2016
  InstallationDate: Installed on 2016-10-20 (62 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1651923/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1809438] Re: systemd-resolved segfaults

2021-02-19 Thread Danny Brugman
I seem to be affected by the same issue. I get regular DNS query time-
outs coinciding with a lot of the following log messages (syslog):

systemd-resolved[1119]: Server returned error NXDOMAIN, mitigating
potential DNS violation DVE-2018-0001, retrying transaction with reduced
feature level UDP.

Eventually systemd-resolved crashes. This happens more frequently (/or
only) when connected to wifi.

Trace extracted from an Apport crash report (cause was a segmentation
fault):

#0  0x7efeaa3c62ed in sd_event_source_unref (p=0x1b01030036100326) at 
../src/libsystemd/sd-event/sd-event.c:1912
__PRETTY_FUNCTION__ = "sd_event_source_unref"
#1  0x561894e7f162 in dns_query_stop (q=q@entry=0x5618967255b0) at 
../src/resolve/resolved-dns-query.c:336
c = 
__PRETTY_FUNCTION__ = "dns_query_stop"
#2  0x561894e7f1d0 in dns_query_complete (q=0x5618967255b0, 
state=) at ../src/resolve/resolved-dns-query.c:528
__PRETTY_FUNCTION__ = "dns_query_complete"
#3  0x561894e7f33f in on_query_timeout (s=, usec=, userdata=) at ../src/resolve/resolved-dns-query.c:539
q = 
__PRETTY_FUNCTION__ = "on_query_timeout"
#4  0x7efeaa3ceb76 in source_dispatch (s=s@entry=0x561896722680) at 
../src/libsystemd/sd-event/sd-event.c:3201
saved_type = SOURCE_TIME_BOOTTIME
r = 
__PRETTY_FUNCTION__ = "source_dispatch"
__func__ = "source_dispatch"
#5  0x7efeaa3ceef1 in sd_event_dispatch (e=e@entry=0x5618966cfcd0) at 
../src/libsystemd/sd-event/sd-event.c:3634
ref = 
p = 
r = 
__PRETTY_FUNCTION__ = "sd_event_dispatch"
#6  0x7efeaa3d0928 in sd_event_run (e=e@entry=0x5618966cfcd0, 
timeout=timeout@entry=18446744073709551615) at 
../src/libsystemd/sd-event/sd-event.c:3692
r = 1
__PRETTY_FUNCTION__ = "sd_event_run"
#7  0x7efeaa3d0b4f in sd_event_loop (e=0x5618966cfcd0) at 
../src/libsystemd/sd-event/sd-event.c:3714
ref = 0x5618966cfcd0
r = 
__PRETTY_FUNCTION__ = "sd_event_loop"
#8  0x561894e5a22a in run (argv=, argc=) at 
../src/resolve/resolved.c:84
notify_stop = 0x561894ea3d70 "STOPPING=1\nSTATUS=Shutting down..."

Log statement from the kernel log:

traps: systemd-resolve[1162] general protection fault ip:7efeaa3c62ed
sp:7ffef7d6f1b0 error:0 in libsystemd-shared-245.so[7efeaa39e000+174000]

(Although the trace started with a notify_stop, the system was not
shutdown at the time)

Other details:

Release: Ubuntu 20.04.01 (amd64)
Systemd package version: 245.4-4ubuntu3.4

-- 
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/1809438

Title:
  systemd-resolved segfaults

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I regularly (once almost every hour) get segfaults resported in
  systemd-resolved. The syslog is not always the same:

  Dec 21 06:59:21 marshall kernel: [988042.071003] systemd-resolve[15794]: 
segfault at e60e8ad514 ip 00e60e8ad514 sp 7ffe0376e748 error 14 in 
systemd-resolved[556f74bcf000+59000]
  Dec 21 06:59:21 marshall systemd[1]: systemd-resolved.service: Main process 
exited, code=dumped, status=11/SEGV
  Dec 21 06:59:21 marshall systemd[1]: systemd-resolved.service: Failed with 
result 'core-dump'.

  Dec 21 08:17:47 marshall kernel: [992748.334333] systemd-resolve[16943]: 
segfault at 2a11d9b0 ip 7f4810f5ad26 sp 7fff544db0f0 error 4 in 
libsystemd-shared-237.so[7f4810e1f000+1b5000]
  Dec 21 08:17:47 marshall systemd[1]: systemd-resolved.service: Main process 
exited, code=dumped, status=11/SEGV
  Dec 21 08:17:47 marshall systemd[1]: systemd-resolved.service: Failed with 
result 'core-dump'.

  Dec 21 06:22:45 marshall systemd-resolved[15727]: Assertion 'p->n_ref > 0' 
failed at ../src/resolve/resolved-dns-packet.c:210, function 
dns_packet_unref(). Aborting.
  Dec 21 06:22:45 marshall systemd[1]: systemd-resolved.service: Main process 
exited, code=dumped, status=6/ABRT
  Dec 21 06:22:45 marshall systemd[1]: systemd-resolved.service: Failed with 
result 'core-dump'.

  Dec 21 06:17:46 marshall systemd-resolved[15662]: Assertion 
'DNS_TRANSACTION_IS_LIVE(q->state)' failed at 
../src/resolve/resolved-dns-query.c:540, function dns_query_complete(). 
Aborting.
  Dec 21 06:17:46 marshall systemd[1]: systemd-resolved.service: Main process 
exited, code=dumped, status=6/ABRT
  Dec 21 06:17:46 marshall systemd[1]: systemd-resolved.service: Failed with 
result 'core-dump'.

  The system in question uses dnsmasq as local DNS server. Logging that is 
probably unrelated, but often seen (possibly due to the setup with dnsmasq) is:
  dec 21 10:22:00 marshall systemd-resolved[3183]: Server returned error 
NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying 
transaction with reduced feature level UDP.
  dec 21 10:17:15 marshall systemd-resolved[3183]: Using degraded feature set 
(TCP) for DNS 

[Touch-packages] [Bug 1915789] Re: sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set

2021-02-16 Thread Danny
That will teach me for subscribing to hirsute-proposed updates!
Hopefully I can switch the ownership back from a LiveUSB .

-- 
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/1915789

Title:
  sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set

Status in sudo package in Ubuntu:
  Confirmed

Bug description:
  After upgrading sudo from 1.9.4p2-2ubuntu3 to 1.9.5p2-2ubuntu1, it no
  longer works.

  $ sudo
  sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set

  The file permission of /usr/bin/sudo seems to have been messed up.

  $ ls -l /usr/bin/sudo
  -rwsr-xr-x 1 2001 2501 190952 2021-02-10 19:42 /usr/bin/sudo

  System information:

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Hirsute Hippo (development branch)
  Release:  21.04
  Codename: hirsute

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1915789/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1899103] Re: libpam-cap causes PAM applications to crash

2020-10-08 Thread Danny
Confirmed the issue

** Changed in: libcap2 (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libcap2 in Ubuntu.
https://bugs.launchpad.net/bugs/1899103

Title:
  libpam-cap causes PAM applications to crash

Status in libcap2 package in Ubuntu:
  Confirmed

Bug description:
  Install ocserv and setup for PAM authentication. On second connection,
  ocserv crashes due to a double free in PAM.

  Repro steps:
  1. Create Dockerfile that installs ocserv + libpam-cap
  ```
  FROM ubuntu:20.04

  RUN apt update && apt install -y ocserv libpam-cap && apt autoremove
  && apt clean

  COPY server-cert.pem /etc/ssl/ocserv_test.cert
  COPY server-key.pem /etc/ssl/ocserv_test.key
  COPY ca-cert.pem /etc/ssl/certs/ssl-cert-snakeoil.pem
  COPY ocserv.conf /etc/ocserv/ocserv.conf

  RUN useradd test
  RUN echo "test\ntest" | passwd test

  ENV MALLOC_CHECK_=3
  CMD ocserv -f -d 1
  ```

  2. Build container:
  ```
  sudo docker build -t ocserv:20.04 .
  ```

  3. Launch container:
  ```
  docker run -p 443:443/tcp -p 443:443/udp -it --rm --device /dev/net/tun 
--cap-add net_admin ocserv:20.04
  ```

  4. From another console, connect / disconnect:
  ```
  while true; do echo test | openconnect https://localhost -u test 
--passwd-on-stdin --servercert 
pin-sha256:qBLVTyoXiFdn+0pW+eSGqnVCEnMbLigVf5vAl1ZewW4= --background && sleep 2 
&& pkill openconnect && sleep 2;done
  ```

  5. ocserv crashes:
  free(): invalid pointer
  ocserv[8]: main: main-sec-mod-cmd.c:106: command socket for sec-mod closed
  ocserv[8]: main: main.c:1179: error in command from sec-mod
  ocserv[8]: main: termination request received; waiting for children to die

  For more details see:
  https://gitlab.com/openconnect/ocserv/-/issues/361

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/1899103/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant

2020-05-24 Thread Danny Hsu
verified pulseaudio version - 1:11.1-1ubuntu7.7 in a hp sff[0] which has
dual front jacks, works well, didn't find any Regression potential.

[0]https://www8.hp.com/h20195/v2/GetPDF.aspx/4AA7-5395EEAP.pdf

** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic

** Tags removed: verification-needed

-- 
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/1869819

Title:
  [SRU] System can't detect external headset in the codec of Conexant

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project bionic series:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  Fix Committed
Status in pulseaudio source package in Focal:
  Fix Released

Bug description:
  [Impact]
  In some hp's devices, there are two audio jacks(one headset and one 
headphone) in the audio interface which is using the codec of Conexant, and 
apparently it's not working, the system can't detect the headset in current 
codec.

  [Test Case]
  1. Insert 4 rings(3 stripes) headset into front audio port (headset icon)
  2. Check System Setting->Sound->Output

  [Expected result]
  Can detect external headset

  [Actual result]
  Only shows internal speaker.
  External headset microphone was detected.
  Another front audio port (earphone icon) works fine.

  [Regression Potential]
  Low.

  [Failure rate]
  100%

  [Additional information]
  system-product-name: HP EliteDesk 800 G5 SFF
  CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:3e98] (rev 02)
  OS-version: 18.04
  kernel-version: 4.15.0-1065-oem
  pulseaudio-version: 1:11.1-1ubuntu7.2

  Upstream issue:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272

  Ubuntu-Focal-Source:
  
https://code.launchpad.net/~hugh712/ubuntu/+source/pulseaudio/+git/pulseaudio/+ref/focal-1869819

  PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1869819

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1869819/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1867421] Re: Microsoft Classic IntelliMouse moves way too fast

2020-05-16 Thread Danny Di Giacomo
Thanks, on Lubuntu 18.04.4 LTS, it's /lib/udev/hwdb.d/70-mouse.hwdb.

I found the mouse far too slow after the update. Personally, I like to
be able to quickly move the cursor from the left to right edge of my
1920 x 1080 screen in about an inch of physical movement.

-- 
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/1867421

Title:
  Microsoft Classic IntelliMouse moves way too fast

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released
Status in systemd source package in Eoan:
  Fix Released
Status in systemd source package in Focal:
  Fix Released

Bug description:
  [impact]

  Microsoft Classic IntelliMouse moves way too fast to be usable.

  [test case]

  on a bionic system, connect affected mouse and attempt to move
  pointer, note it moves too fast.

  [regression potential]

  as this adds a hwdb entry for a mouse using vendor/product id and name
  matching, any regression would likely involve incorrectly setting dpi
  on a different mouse than intended.

  [scope]

  fixed by upstream commit 26d7cf3daf08b279bdd2e484936268e1e88648d4
  which is included starting in v240, so this is already fixed in Eoan
  and later.

  This is needed only for Xenial and Bionic.

  [original description]

  Microsoft Classic IntelliMouse moves way too fast to be usable.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.39
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 14 17:12:25 2020
  InstallationDate: Installed on 2019-01-02 (436 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 045e:00db Microsoft Corp. Natural Ergonomic Keyboard 
4000 V1.0
   Bus 001 Device 003: ID 8087:0a2b Intel Corp.
   Bus 001 Device 002: ID 045e:0823 Microsoft Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 10M7CTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=e226e89e-7b9d-4135-a662-4829015a56f0 ro quiet splash vt.handoff=1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf

   3 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/06/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: M16KT47A
  dmi.board.name: 3102
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN 3259627060531
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrM16KT47A:bd02/06/2018:svnLENOVO:pn10M7CTO1WW:pvrThinkCentreM710s:rvnLENOVO:rn3102:rvrSDK0J40709WIN3259627060531:cvnLENOVO:ct3:cvrNone:
  dmi.product.family: ThinkCentre M710s
  dmi.product.name: 10M7CTO1WW
  dmi.product.sku: LENOVO_MT_10M7_BU_Think_FM_ThinkCentre M710s
  dmi.product.version: ThinkCentre M710s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1867421/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1867421] Re: Microsoft Classic IntelliMouse moves way too fast

2020-05-11 Thread Danny Di Giacomo
I'm running Lubuntu 18.04.4 LTS and recently upgraded to a Microsoft
Classic Intellimouse and find the current speed to be fine. Settings at
present are the defaults (in Input Device Preferences, acceleration 2.0
and sensitivity 10). I received notification about this update today and
am concerned I won't be able to change back to the current speed (cap
will be put in place). Please confirm that this will be possible and if
the update/changes will be easy to remove/reset later if not (steps for
this would be useful).

-- 
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/1867421

Title:
  Microsoft Classic IntelliMouse moves way too fast

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released
Status in systemd source package in Eoan:
  Fix Released
Status in systemd source package in Focal:
  Fix Released

Bug description:
  [impact]

  Microsoft Classic IntelliMouse moves way too fast to be usable.

  [test case]

  on a bionic system, connect affected mouse and attempt to move
  pointer, note it moves too fast.

  [regression potential]

  as this adds a hwdb entry for a mouse using vendor/product id and name
  matching, any regression would likely involve incorrectly setting dpi
  on a different mouse than intended.

  [scope]

  fixed by upstream commit 26d7cf3daf08b279bdd2e484936268e1e88648d4
  which is included starting in v240, so this is already fixed in Eoan
  and later.

  This is needed only for Xenial and Bionic.

  [original description]

  Microsoft Classic IntelliMouse moves way too fast to be usable.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.39
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 14 17:12:25 2020
  InstallationDate: Installed on 2019-01-02 (436 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 045e:00db Microsoft Corp. Natural Ergonomic Keyboard 
4000 V1.0
   Bus 001 Device 003: ID 8087:0a2b Intel Corp.
   Bus 001 Device 002: ID 045e:0823 Microsoft Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 10M7CTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=e226e89e-7b9d-4135-a662-4829015a56f0 ro quiet splash vt.handoff=1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf

   3 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/06/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: M16KT47A
  dmi.board.name: 3102
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN 3259627060531
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrM16KT47A:bd02/06/2018:svnLENOVO:pn10M7CTO1WW:pvrThinkCentreM710s:rvnLENOVO:rn3102:rvrSDK0J40709WIN3259627060531:cvnLENOVO:ct3:cvrNone:
  dmi.product.family: ThinkCentre M710s
  dmi.product.name: 10M7CTO1WW
  dmi.product.sku: LENOVO_MT_10M7_BU_Think_FM_ThinkCentre M710s
  dmi.product.version: ThinkCentre M710s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1867421/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1872028] [NEW] [HP ProOne 400 G5 20.0-in All-in-One, Conexant Generic, Speaker, Internal] No sound from internal speaker

2020-04-10 Thread Danny Hsu
Public bug reported:

[Reproduce steps]
1. Install 20.04 daily build on 4/9.
2. Do dist-upgrade after installation.
3. Go to System Setting->Sound->Output, press the test button.
4. There is no sound output while press the Front right and Front left button.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu26
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  u  1358 F pulseaudio
 /dev/snd/pcmC0D0c:   u  1358 F...m pulseaudio
 /dev/snd/pcmC0D0p:   u  1358 F...m pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 10 04:11:26 2020
InstallationDate: Installed on 2020-04-10 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  u  1358 F pulseaudio
 /dev/snd/pcmC0D0c:   u  1358 F...m pulseaudio
 /dev/snd/pcmC0D0p:   u  1358 F...m pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [HP ProOne 400 G5 20.0-in All-in-One, Conexant Generic, Speaker, 
Internal] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/26/2019
dmi.bios.vendor: HP
dmi.bios.version: R12 Ver. 02.03.01
dmi.board.name: 85A2
dmi.board.vendor: HP
dmi.board.version: KBC Version 08.93.00
dmi.chassis.type: 13
dmi.chassis.vendor: HP
dmi.modalias: 
dmi:bvnHP:bvrR12Ver.02.03.01:bd09/26/2019:svnHP:pnHPProOne400G520.0-inAll-in-One:pvr:rvnHP:rn85A2:rvrKBCVersion08.93.00:cvnHP:ct13:cvr:
dmi.product.family: 103C_53307F HP ProOne
dmi.product.name: HP ProOne 400 G5 20.0-in All-in-One
dmi.product.sku: 6AE44AV
dmi.sys.vendor: HP

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

-- 
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/1872028

Title:
  [HP ProOne 400 G5 20.0-in All-in-One, Conexant Generic, Speaker,
  Internal] No sound from internal speaker

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  [Reproduce steps]
  1. Install 20.04 daily build on 4/9.
  2. Do dist-upgrade after installation.
  3. Go to System Setting->Sound->Output, press the test button.
  4. There is no sound output while press the Front right and Front left button.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1358 F pulseaudio
   /dev/snd/pcmC0D0c:   u  1358 F...m pulseaudio
   /dev/snd/pcmC0D0p:   u  1358 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 10 04:11:26 2020
  InstallationDate: Installed on 2020-04-10 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1358 F pulseaudio
   /dev/snd/pcmC0D0c:   u  1358 F...m pulseaudio
   /dev/snd/pcmC0D0p:   u  1358 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [HP ProOne 400 G5 20.0-in All-in-One, Conexant Generic, Speaker, 
Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/26/2019
  dmi.bios.vendor: HP
  dmi.bios.version: R12 Ver. 02.03.01
  dmi.board.name: 85A2
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 08.93.00
  dmi.chassis.type: 13
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrR12Ver.02.03.01:bd09/26/2019:svnHP:pnHPProOne400G520.0-inAll-in-One:pvr:rvnHP:rn85A2:rvrKBCVersion08.93.00:cvnHP:ct13:cvr:
  dmi.product.family: 103C_53307F HP ProOne
  dmi.product.name: HP ProOne 400 G5 20.0-in All-in-One
  dmi.product.sku: 6AE44AV
  dmi.sys.vendor: HP

To manage notifications about this bug go to:

[Touch-packages] [Bug 1849368] Re: apt-get update issues invalid range requests for previously completed downloads

2019-10-22 Thread Danny Thomas
Looking deeper, I think we might also have a backend that's not
correctly handling If-Range and returning the 416 before considering if
the Release file is out of date, which is why we get stuck in a file
size mismatch between Releases and Packages.gz.

Does look like there are maybe some issues around the handling of that
error, and certainly the check for the host supporting range support.

-- 
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/1849368

Title:
  apt-get update issues invalid range requests for previously completed
  downloads

Status in apt package in Ubuntu:
  New

Bug description:
  When an apt-get update fails, for instance due to a mismatch between
  the Release and Packages.gz due to a mirror sync/index update, it
  leaves files in the /var/lib/apt/lists/partial for the distribution:

  15466565 16 -rw-r--r--   1 root root13860 Oct 22 12:50 
/var/lib/apt/lists/partial/ourhost_internal_repo_dists_main_Release
   1543  4 -rw-r--r--   1 root root  475 Oct 22 12:50 
/var/lib/apt/lists/partial/ourhost_internal_repo_dists_main_Release.gpg
   15471150  0 -rw-r--r--   1 root root0 Oct 22 12:52 
/var/lib/apt/lists/partial/ourhost_internal_repo_dists_main_main_binary-amd64_Packages.gz.FAILED

  In this case both Release and Release.gpg were complete, however when
  running apt-get update again it issues the revalidation requests for
  these resources with Range headers that are the length of the file
  resulting in '416 Requested Range Not Satisfiable':

  GET .../Release HTTP/1.1
  Cache-Control: max-age=0
  Accept: text/*
  Range: bytes=13860-
  If-Range: Tue, 22 Oct 2019 12:50:05 GMT
  User-Agent: Debian APT-HTTP/1.3 (1.6.12)

  HTTP/1.1 416 Requested Range Not Satisfiable

  It appears:

  - There's no way for apt-get to know if the file is complete so this logic 
will always be hit if the file exists 
https://github.com/Debian/apt/blob/master/methods/http.cc#L956-L962
  - The logic for determining whether a server supports range requests is only 
entered if an Accept-Range header exists, however an absence of this header 
means support is not available - 
https://github.com/Debian/apt/blob/master/methods/basehttp.cc#L251

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1849368/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1849368] Re: apt-get update issues invalid range requests for previously completed downloads

2019-10-22 Thread Danny Thomas
Excuse the slightly bogus filenames in that listing - I manually
redacted our host/distribution details.

-- 
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/1849368

Title:
  apt-get update issues invalid range requests for previously completed
  downloads

Status in apt package in Ubuntu:
  New

Bug description:
  When an apt-get update fails, for instance due to a mismatch between
  the Release and Packages.gz due to a mirror sync/index update, it
  leaves files in the /var/lib/apt/lists/partial for the distribution:

  15466565 16 -rw-r--r--   1 root root13860 Oct 22 12:50 
/var/lib/apt/lists/partial/ourhost_internal_repo_dists_main_Release
   1543  4 -rw-r--r--   1 root root  475 Oct 22 12:50 
/var/lib/apt/lists/partial/ourhost_internal_repo_dists_main_Release.gpg
   15471150  0 -rw-r--r--   1 root root0 Oct 22 12:52 
/var/lib/apt/lists/partial/ourhost_internal_repo_dists_main_main_binary-amd64_Packages.gz.FAILED

  In this case both Release and Release.gpg were complete, however when
  running apt-get update again it issues the revalidation requests for
  these resources with Range headers that are the length of the file
  resulting in '416 Requested Range Not Satisfiable':

  GET .../Release HTTP/1.1
  Cache-Control: max-age=0
  Accept: text/*
  Range: bytes=13860-
  If-Range: Tue, 22 Oct 2019 12:50:05 GMT
  User-Agent: Debian APT-HTTP/1.3 (1.6.12)

  HTTP/1.1 416 Requested Range Not Satisfiable

  It appears:

  - There's no way for apt-get to know if the file is complete so this logic 
will always be hit if the file exists 
https://github.com/Debian/apt/blob/master/methods/http.cc#L956-L962
  - The logic for determining whether a server supports range requests is only 
entered if an Accept-Range header exists, however an absence of this header 
means support is not available - 
https://github.com/Debian/apt/blob/master/methods/basehttp.cc#L251

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1849368/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1849368] [NEW] apt-get update issues invalid range requests for previously completed downloads

2019-10-22 Thread Danny Thomas
Public bug reported:

When an apt-get update fails, for instance due to a mismatch between the
Release and Packages.gz due to a mirror sync/index update, it leaves
files in the /var/lib/apt/lists/partial for the distribution:

15466565 16 -rw-r--r--   1 root root13860 Oct 22 12:50 
/var/lib/apt/lists/partial/ourhost_internal_repo_dists_main_Release
 1543  4 -rw-r--r--   1 root root  475 Oct 22 12:50 
/var/lib/apt/lists/partial/ourhost_internal_repo_dists_main_Release.gpg
 15471150  0 -rw-r--r--   1 root root0 Oct 22 12:52 
/var/lib/apt/lists/partial/ourhost_internal_repo_dists_main_main_binary-amd64_Packages.gz.FAILED

In this case both Release and Release.gpg were complete, however when
running apt-get update again it issues the revalidation requests for
these resources with Range headers that are the length of the file
resulting in '416 Requested Range Not Satisfiable':

GET .../Release HTTP/1.1
Cache-Control: max-age=0
Accept: text/*
Range: bytes=13860-
If-Range: Tue, 22 Oct 2019 12:50:05 GMT
User-Agent: Debian APT-HTTP/1.3 (1.6.12)

HTTP/1.1 416 Requested Range Not Satisfiable

It appears:

- There's no way for apt-get to know if the file is complete so this logic will 
always be hit if the file exists 
https://github.com/Debian/apt/blob/master/methods/http.cc#L956-L962
- The logic for determining whether a server supports range requests is only 
entered if an Accept-Range header exists, however an absence of this header 
means support is not available - 
https://github.com/Debian/apt/blob/master/methods/basehttp.cc#L251

** Affects: apt (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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/1849368

Title:
  apt-get update issues invalid range requests for previously completed
  downloads

Status in apt package in Ubuntu:
  New

Bug description:
  When an apt-get update fails, for instance due to a mismatch between
  the Release and Packages.gz due to a mirror sync/index update, it
  leaves files in the /var/lib/apt/lists/partial for the distribution:

  15466565 16 -rw-r--r--   1 root root13860 Oct 22 12:50 
/var/lib/apt/lists/partial/ourhost_internal_repo_dists_main_Release
   1543  4 -rw-r--r--   1 root root  475 Oct 22 12:50 
/var/lib/apt/lists/partial/ourhost_internal_repo_dists_main_Release.gpg
   15471150  0 -rw-r--r--   1 root root0 Oct 22 12:52 
/var/lib/apt/lists/partial/ourhost_internal_repo_dists_main_main_binary-amd64_Packages.gz.FAILED

  In this case both Release and Release.gpg were complete, however when
  running apt-get update again it issues the revalidation requests for
  these resources with Range headers that are the length of the file
  resulting in '416 Requested Range Not Satisfiable':

  GET .../Release HTTP/1.1
  Cache-Control: max-age=0
  Accept: text/*
  Range: bytes=13860-
  If-Range: Tue, 22 Oct 2019 12:50:05 GMT
  User-Agent: Debian APT-HTTP/1.3 (1.6.12)

  HTTP/1.1 416 Requested Range Not Satisfiable

  It appears:

  - There's no way for apt-get to know if the file is complete so this logic 
will always be hit if the file exists 
https://github.com/Debian/apt/blob/master/methods/http.cc#L956-L962
  - The logic for determining whether a server supports range requests is only 
entered if an Accept-Range header exists, however an absence of this header 
means support is not available - 
https://github.com/Debian/apt/blob/master/methods/basehttp.cc#L251

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1849368/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1796550] Re: [regression] Keyboard brightness control keys (down/up) don't work in cosmic (upower 0.99.8)

2018-10-23 Thread Danny Stieben
I have an Apple MacBook Pro 11,2 running Cosmic with this same issue.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1796550

Title:
  [regression] Keyboard brightness control keys (down/up) don't work in
  cosmic (upower 0.99.8)

Status in linux package in Ubuntu:
  Invalid
Status in upower package in Ubuntu:
  Triaged

Bug description:
  https://gitlab.freedesktop.org/upower/upower/issues/73

  ---

  On laptops with two separate (down,up) keys to control the backlit
  keyboard, both keys seem to do nothing. The OSD for the backlit
  keyboard is displayed but no progress bar and no actual effect to the
  backlight. Almost as if the shell only understands laptops with a
  single key for controlling the keyboard backlight...

  Bug verified in cosmic on:
    * Asus UX331UAL
    * Apple Macbook Pro 12,1
    * Apple Macbook Air

  All of them have these keys and they all fail in the same way. However
  it is not a kernel bug. The kernel interface
  (/sys/class/leds/*::kbd_backlight/*) works when I write to it
  directly. This seems to be a problem with Gnome Shell only.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.0-3ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  7 13:41:50 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-09-11 (25 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796550/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1727174] ProcEnviron.txt

2017-11-05 Thread Danny
apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1727174/+attachment/5004420/+files/ProcEnviron.txt

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1727174

Title:
  ibus not working, Error: traps: ibus-ui-gtk3[4578] general protection
  ip:7fb85293d253 sp:7ffeecf73800 error:0 in
  libX11.so.6.3.0[7fb8528a+134000]

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  uname -a
  Linux Danny-Yoga 4.13.0-16-lowlatency #19-Ubuntu SMP PREEMPT Wed Oct 11 
19:51:52 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

  
  lsb_release -a
  LSB Version:  
core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 17.10
  Release:  17.10
  Codename: artful

  read-config
  SCHEMA: org.freedesktop.ibus.general
dconf-preserve-name-prefixes: ['/desktop/ibus/engine/pinyin', 
'/desktop/ibus/engine/bopomofo', '/desktop/ibus/engine/hangul']
use-system-keyboard-layout: true
embed-preedit-text: true
enable-by-default: false
use-global-engine: false
use-xmodmap: true
switcher-delay-time: 400
version: '1.5.14'
engines-order: ['libpinyin']
preload-engines: ['libpinyin', 'xkb:us::eng']
xkb-latin-layouts: ['ara', 'bg', 'cz', 'dev', 'gr', 'gur', 'in', 
'jp(kana)', 'mal', 'mkd', 'ru', 'ua']
  SCHEMA: org.freedesktop.ibus.general.hotkey
next-engine: ['Alt+Shift_L']
disable-unconditional: @as []
enable-unconditional: @as []
trigger: ['Control+space', 'Zenkaku_Hankaku', 'Alt+Kanji', 'Alt+grave', 
'Hangul', 'Alt+Release+Alt_R']
previous-engine: @as []
prev-engine: @as []
next-engine-in-menu: ['Alt+Shift_L']
triggers: ['space']
  SCHEMA: org.freedesktop.ibus.panel
x: -1
property-icon-delay-time: 500
y: -1
lookup-table-orientation: 1
show: 2
xkb-icon-rgba: '#415099'
auto-hide-timeout: 1
show-im-name: false
follow-input-cursor-when-always-shown: false
custom-font: 'Sans 10'
show-icon-on-systray: true
use-custom-font: false

  ibus engine
  xkb:us::eng

  ps -ef|grep ibus
  gdm   1969  1647  0 12:42 tty1 00:00:00 ibus-daemon --xim --panel 
disable
  gdm   1972  1969  0 12:42 tty1 00:00:00 /usr/lib/ibus/ibus-dconf
  gdm   1975 1  0 12:42 tty1 00:00:00 /usr/lib/ibus/ibus-x11 
--kill-daemon
  gdm   2046  1969  0 12:42 tty1 00:00:00 
/usr/lib/ibus/ibus-engine-simple
  hdzhong   2516  2433  0 12:42 tty2 00:00:02 ibus-daemon --xim --panel 
disable
  hdzhong   3966  2516  0 12:53 tty2 00:00:00 /usr/lib/ibus/ibus-dconf
  hdzhong   3968 1  0 12:53 tty2 00:00:00 /usr/lib/ibus/ibus-x11 
--kill-daemon
  hdzhong   3984  2516  0 12:53 tty2 00:00:00 
/usr/lib/ibus/ibus-engine-simple
  hdzhong   4198  3939  0 12:58 pts/100:00:00 grep --color=auto ibus

  dpkg:

  ii  ibus 1.5.14-2ubuntu1  amd64
Intelligent Input Bus - core
  ii  ibus-anthy   1.5.9-2  amd64anthy 
engine for IBus
  ii  ibus-clutter:amd64   0.0+git20090728.a936bacf-5.1 amd64ibus 
input method framework for clutter
  ii  ibus-gtk:amd64   1.5.14-2ubuntu1  amd64
Intelligent Input Bus - GTK+2 support
  ii  ibus-gtk3:amd64  1.5.14-2ubuntu1  amd64
Intelligent Input Bus - GTK+3 support
  ii  ibus-libpinyin   1.7.3-2  amd64
Intelligent Pinyin engine based on libpinyin for IBus
  ii  ibus-qt4 1.3.3-1  amd64
qt-immodule for ibus (QT4) (plugin)
  ii  ibus-sunpinyin   2.0.3-5build3amd64
sunpinyin engine for ibus
  ii  ibus-table   1.9.14-3 all  table 
engine for IBus
  ii  ibus-table-wubi  1.8.2-2  all  
ibus-table input method: Wubi
  ii  ibus-wayland 1.5.14-2ubuntu1  amd64
Intelligent Input Bus - Wayland support
  ii  libibus-1.0-5:amd64   1.5.14-2ubuntu1 amd64Intelligent Input Bus 
- shared library
  ii  libibus-1.0-dev:amd64 1.5.14-2ubuntu1 amd64Intelligent Input Bus 
- development file
  ii  libibus-qt1   1.3.3-1 amd64qt-immodule for ibus 
(QT4) (library)

  
  execute command: "ibus-daemon -rdx" won't fixed the issue.

  and no system tray in the topbar.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2014-05-02 (1283 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Package: ibus 1.5.14-2ubuntu1
  PackageArchitecture: amd64
  ProcVersion

[Touch-packages] [Bug 1727174] ProcCpuinfoMinimal.txt

2017-11-05 Thread Danny
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1727174/+attachment/5004419/+files/ProcCpuinfoMinimal.txt

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1727174

Title:
  ibus not working, Error: traps: ibus-ui-gtk3[4578] general protection
  ip:7fb85293d253 sp:7ffeecf73800 error:0 in
  libX11.so.6.3.0[7fb8528a+134000]

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  uname -a
  Linux Danny-Yoga 4.13.0-16-lowlatency #19-Ubuntu SMP PREEMPT Wed Oct 11 
19:51:52 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

  
  lsb_release -a
  LSB Version:  
core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 17.10
  Release:  17.10
  Codename: artful

  read-config
  SCHEMA: org.freedesktop.ibus.general
dconf-preserve-name-prefixes: ['/desktop/ibus/engine/pinyin', 
'/desktop/ibus/engine/bopomofo', '/desktop/ibus/engine/hangul']
use-system-keyboard-layout: true
embed-preedit-text: true
enable-by-default: false
use-global-engine: false
use-xmodmap: true
switcher-delay-time: 400
version: '1.5.14'
engines-order: ['libpinyin']
preload-engines: ['libpinyin', 'xkb:us::eng']
xkb-latin-layouts: ['ara', 'bg', 'cz', 'dev', 'gr', 'gur', 'in', 
'jp(kana)', 'mal', 'mkd', 'ru', 'ua']
  SCHEMA: org.freedesktop.ibus.general.hotkey
next-engine: ['Alt+Shift_L']
disable-unconditional: @as []
enable-unconditional: @as []
trigger: ['Control+space', 'Zenkaku_Hankaku', 'Alt+Kanji', 'Alt+grave', 
'Hangul', 'Alt+Release+Alt_R']
previous-engine: @as []
prev-engine: @as []
next-engine-in-menu: ['Alt+Shift_L']
triggers: ['space']
  SCHEMA: org.freedesktop.ibus.panel
x: -1
property-icon-delay-time: 500
y: -1
lookup-table-orientation: 1
show: 2
xkb-icon-rgba: '#415099'
auto-hide-timeout: 1
show-im-name: false
follow-input-cursor-when-always-shown: false
custom-font: 'Sans 10'
show-icon-on-systray: true
use-custom-font: false

  ibus engine
  xkb:us::eng

  ps -ef|grep ibus
  gdm   1969  1647  0 12:42 tty1 00:00:00 ibus-daemon --xim --panel 
disable
  gdm   1972  1969  0 12:42 tty1 00:00:00 /usr/lib/ibus/ibus-dconf
  gdm   1975 1  0 12:42 tty1 00:00:00 /usr/lib/ibus/ibus-x11 
--kill-daemon
  gdm   2046  1969  0 12:42 tty1 00:00:00 
/usr/lib/ibus/ibus-engine-simple
  hdzhong   2516  2433  0 12:42 tty2 00:00:02 ibus-daemon --xim --panel 
disable
  hdzhong   3966  2516  0 12:53 tty2 00:00:00 /usr/lib/ibus/ibus-dconf
  hdzhong   3968 1  0 12:53 tty2 00:00:00 /usr/lib/ibus/ibus-x11 
--kill-daemon
  hdzhong   3984  2516  0 12:53 tty2 00:00:00 
/usr/lib/ibus/ibus-engine-simple
  hdzhong   4198  3939  0 12:58 pts/100:00:00 grep --color=auto ibus

  dpkg:

  ii  ibus 1.5.14-2ubuntu1  amd64
Intelligent Input Bus - core
  ii  ibus-anthy   1.5.9-2  amd64anthy 
engine for IBus
  ii  ibus-clutter:amd64   0.0+git20090728.a936bacf-5.1 amd64ibus 
input method framework for clutter
  ii  ibus-gtk:amd64   1.5.14-2ubuntu1  amd64
Intelligent Input Bus - GTK+2 support
  ii  ibus-gtk3:amd64  1.5.14-2ubuntu1  amd64
Intelligent Input Bus - GTK+3 support
  ii  ibus-libpinyin   1.7.3-2  amd64
Intelligent Pinyin engine based on libpinyin for IBus
  ii  ibus-qt4 1.3.3-1  amd64
qt-immodule for ibus (QT4) (plugin)
  ii  ibus-sunpinyin   2.0.3-5build3amd64
sunpinyin engine for ibus
  ii  ibus-table   1.9.14-3 all  table 
engine for IBus
  ii  ibus-table-wubi  1.8.2-2  all  
ibus-table input method: Wubi
  ii  ibus-wayland 1.5.14-2ubuntu1  amd64
Intelligent Input Bus - Wayland support
  ii  libibus-1.0-5:amd64   1.5.14-2ubuntu1 amd64Intelligent Input Bus 
- shared library
  ii  libibus-1.0-dev:amd64 1.5.14-2ubuntu1 amd64Intelligent Input Bus 
- development file
  ii  libibus-qt1   1.3.3-1 amd64qt-immodule for ibus 
(QT4) (library)

  
  execute command: "ibus-daemon -rdx" won't fixed the issue.

  and no system tray in the topbar.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2014-05-02 (1283 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Package: ibus 1.5.14-2ubuntu1
  PackageArchitecture

[Touch-packages] [Bug 1727174] Re: ibus not working, Error: traps: ibus-ui-gtk3[4578] general protection ip:7fb85293d253 sp:7ffeecf73800 error:0 in libX11.so.6.3.0[7fb8528a0000+134000]

2017-11-05 Thread Danny
apport information

** Tags added: apport-collected wayland-session

** Description changed:

  uname -a
  Linux Danny-Yoga 4.13.0-16-lowlatency #19-Ubuntu SMP PREEMPT Wed Oct 11 
19:51:52 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
  
  
  lsb_release -a
  LSB Version:  
core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 17.10
  Release:  17.10
  Codename: artful
  
  read-config
  SCHEMA: org.freedesktop.ibus.general
dconf-preserve-name-prefixes: ['/desktop/ibus/engine/pinyin', 
'/desktop/ibus/engine/bopomofo', '/desktop/ibus/engine/hangul']
use-system-keyboard-layout: true
embed-preedit-text: true
enable-by-default: false
use-global-engine: false
use-xmodmap: true
switcher-delay-time: 400
version: '1.5.14'
engines-order: ['libpinyin']
preload-engines: ['libpinyin', 'xkb:us::eng']
xkb-latin-layouts: ['ara', 'bg', 'cz', 'dev', 'gr', 'gur', 'in', 
'jp(kana)', 'mal', 'mkd', 'ru', 'ua']
  SCHEMA: org.freedesktop.ibus.general.hotkey
next-engine: ['Alt+Shift_L']
disable-unconditional: @as []
enable-unconditional: @as []
trigger: ['Control+space', 'Zenkaku_Hankaku', 'Alt+Kanji', 'Alt+grave', 
'Hangul', 'Alt+Release+Alt_R']
previous-engine: @as []
prev-engine: @as []
next-engine-in-menu: ['Alt+Shift_L']
triggers: ['space']
  SCHEMA: org.freedesktop.ibus.panel
x: -1
property-icon-delay-time: 500
y: -1
lookup-table-orientation: 1
show: 2
xkb-icon-rgba: '#415099'
auto-hide-timeout: 1
show-im-name: false
follow-input-cursor-when-always-shown: false
custom-font: 'Sans 10'
show-icon-on-systray: true
use-custom-font: false
  
  ibus engine
  xkb:us::eng
  
  ps -ef|grep ibus
  gdm   1969  1647  0 12:42 tty1 00:00:00 ibus-daemon --xim --panel 
disable
  gdm   1972  1969  0 12:42 tty1 00:00:00 /usr/lib/ibus/ibus-dconf
  gdm   1975 1  0 12:42 tty1 00:00:00 /usr/lib/ibus/ibus-x11 
--kill-daemon
  gdm   2046  1969  0 12:42 tty1 00:00:00 
/usr/lib/ibus/ibus-engine-simple
  hdzhong   2516  2433  0 12:42 tty2 00:00:02 ibus-daemon --xim --panel 
disable
  hdzhong   3966  2516  0 12:53 tty2 00:00:00 /usr/lib/ibus/ibus-dconf
  hdzhong   3968 1  0 12:53 tty2 00:00:00 /usr/lib/ibus/ibus-x11 
--kill-daemon
  hdzhong   3984  2516  0 12:53 tty2 00:00:00 
/usr/lib/ibus/ibus-engine-simple
  hdzhong   4198  3939  0 12:58 pts/100:00:00 grep --color=auto ibus
  
  dpkg:
  
  ii  ibus 1.5.14-2ubuntu1  amd64
Intelligent Input Bus - core
  ii  ibus-anthy   1.5.9-2  amd64anthy 
engine for IBus
  ii  ibus-clutter:amd64   0.0+git20090728.a936bacf-5.1 amd64ibus 
input method framework for clutter
  ii  ibus-gtk:amd64   1.5.14-2ubuntu1  amd64
Intelligent Input Bus - GTK+2 support
  ii  ibus-gtk3:amd64  1.5.14-2ubuntu1  amd64
Intelligent Input Bus - GTK+3 support
  ii  ibus-libpinyin   1.7.3-2  amd64
Intelligent Pinyin engine based on libpinyin for IBus
  ii  ibus-qt4 1.3.3-1  amd64
qt-immodule for ibus (QT4) (plugin)
  ii  ibus-sunpinyin   2.0.3-5build3amd64
sunpinyin engine for ibus
  ii  ibus-table   1.9.14-3 all  table 
engine for IBus
  ii  ibus-table-wubi  1.8.2-2  all  
ibus-table input method: Wubi
  ii  ibus-wayland 1.5.14-2ubuntu1  amd64
Intelligent Input Bus - Wayland support
  ii  libibus-1.0-5:amd64   1.5.14-2ubuntu1 amd64Intelligent Input Bus 
- shared library
  ii  libibus-1.0-dev:amd64 1.5.14-2ubuntu1 amd64Intelligent Input Bus 
- development file
  ii  libibus-qt1   1.3.3-1 amd64qt-immodule for ibus 
(QT4) (library)
  
  
  execute command: "ibus-daemon -rdx" won't fixed the issue.
  
  and no system tray in the topbar.
+ --- 
+ ApportVersion: 2.20.7-0ubuntu3.1
+ Architecture: amd64
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 17.10
+ InstallationDate: Installed on 2014-05-02 (1283 days ago)
+ InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
+ Package: ibus 1.5.14-2ubuntu1
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4
+ Tags:  wayland-session artful
+ Uname: Linux 4.13.0-16-lowlatency x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo www-data
+ _MarkForUpload: True
+ modified.conffile..etc.dconf.db.ibus.d.00-upstream-settings: [deleted]
+ modified.conffile..etc.dconf.profile.ibus: [deleted]

** Attachment added: "De

[Touch-packages] [Bug 1727174] JournalErrors.txt

2017-11-05 Thread Danny
apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1727174/+attachment/5004418/+files/JournalErrors.txt

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1727174

Title:
  ibus not working, Error: traps: ibus-ui-gtk3[4578] general protection
  ip:7fb85293d253 sp:7ffeecf73800 error:0 in
  libX11.so.6.3.0[7fb8528a+134000]

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  uname -a
  Linux Danny-Yoga 4.13.0-16-lowlatency #19-Ubuntu SMP PREEMPT Wed Oct 11 
19:51:52 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

  
  lsb_release -a
  LSB Version:  
core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 17.10
  Release:  17.10
  Codename: artful

  read-config
  SCHEMA: org.freedesktop.ibus.general
dconf-preserve-name-prefixes: ['/desktop/ibus/engine/pinyin', 
'/desktop/ibus/engine/bopomofo', '/desktop/ibus/engine/hangul']
use-system-keyboard-layout: true
embed-preedit-text: true
enable-by-default: false
use-global-engine: false
use-xmodmap: true
switcher-delay-time: 400
version: '1.5.14'
engines-order: ['libpinyin']
preload-engines: ['libpinyin', 'xkb:us::eng']
xkb-latin-layouts: ['ara', 'bg', 'cz', 'dev', 'gr', 'gur', 'in', 
'jp(kana)', 'mal', 'mkd', 'ru', 'ua']
  SCHEMA: org.freedesktop.ibus.general.hotkey
next-engine: ['Alt+Shift_L']
disable-unconditional: @as []
enable-unconditional: @as []
trigger: ['Control+space', 'Zenkaku_Hankaku', 'Alt+Kanji', 'Alt+grave', 
'Hangul', 'Alt+Release+Alt_R']
previous-engine: @as []
prev-engine: @as []
next-engine-in-menu: ['Alt+Shift_L']
triggers: ['space']
  SCHEMA: org.freedesktop.ibus.panel
x: -1
property-icon-delay-time: 500
y: -1
lookup-table-orientation: 1
show: 2
xkb-icon-rgba: '#415099'
auto-hide-timeout: 1
show-im-name: false
follow-input-cursor-when-always-shown: false
custom-font: 'Sans 10'
show-icon-on-systray: true
use-custom-font: false

  ibus engine
  xkb:us::eng

  ps -ef|grep ibus
  gdm   1969  1647  0 12:42 tty1 00:00:00 ibus-daemon --xim --panel 
disable
  gdm   1972  1969  0 12:42 tty1 00:00:00 /usr/lib/ibus/ibus-dconf
  gdm   1975 1  0 12:42 tty1 00:00:00 /usr/lib/ibus/ibus-x11 
--kill-daemon
  gdm   2046  1969  0 12:42 tty1 00:00:00 
/usr/lib/ibus/ibus-engine-simple
  hdzhong   2516  2433  0 12:42 tty2 00:00:02 ibus-daemon --xim --panel 
disable
  hdzhong   3966  2516  0 12:53 tty2 00:00:00 /usr/lib/ibus/ibus-dconf
  hdzhong   3968 1  0 12:53 tty2 00:00:00 /usr/lib/ibus/ibus-x11 
--kill-daemon
  hdzhong   3984  2516  0 12:53 tty2 00:00:00 
/usr/lib/ibus/ibus-engine-simple
  hdzhong   4198  3939  0 12:58 pts/100:00:00 grep --color=auto ibus

  dpkg:

  ii  ibus 1.5.14-2ubuntu1  amd64
Intelligent Input Bus - core
  ii  ibus-anthy   1.5.9-2  amd64anthy 
engine for IBus
  ii  ibus-clutter:amd64   0.0+git20090728.a936bacf-5.1 amd64ibus 
input method framework for clutter
  ii  ibus-gtk:amd64   1.5.14-2ubuntu1  amd64
Intelligent Input Bus - GTK+2 support
  ii  ibus-gtk3:amd64  1.5.14-2ubuntu1  amd64
Intelligent Input Bus - GTK+3 support
  ii  ibus-libpinyin   1.7.3-2  amd64
Intelligent Pinyin engine based on libpinyin for IBus
  ii  ibus-qt4 1.3.3-1  amd64
qt-immodule for ibus (QT4) (plugin)
  ii  ibus-sunpinyin   2.0.3-5build3amd64
sunpinyin engine for ibus
  ii  ibus-table   1.9.14-3 all  table 
engine for IBus
  ii  ibus-table-wubi  1.8.2-2  all  
ibus-table input method: Wubi
  ii  ibus-wayland 1.5.14-2ubuntu1  amd64
Intelligent Input Bus - Wayland support
  ii  libibus-1.0-5:amd64   1.5.14-2ubuntu1 amd64Intelligent Input Bus 
- shared library
  ii  libibus-1.0-dev:amd64 1.5.14-2ubuntu1 amd64Intelligent Input Bus 
- development file
  ii  libibus-qt1   1.3.3-1 amd64qt-immodule for ibus 
(QT4) (library)

  
  execute command: "ibus-daemon -rdx" won't fixed the issue.

  and no system tray in the topbar.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2014-05-02 (1283 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Package: ibus 1.5.14-2ubuntu1
  PackageArchitecture: amd64
  ProcV

[Touch-packages] [Bug 1321958] Re: resize2fs does not start to actually grow an ext4

2017-10-14 Thread Danny Mann
Doesn't look like the fixed version was ever pushed out to Trusty. If you are 
using trusty and need this fixed, simply download the source to your machine 
and compile it. If you have the build-essential and git packages installed, 
it's quite simple. Clone the git repo source for the latest version and then cd 
into it and type:
./configure
make

After that, you will have the needed binaries in that folder. You can
run them directly from there when you want to use that version rather
than the on in Trusty.

I compiled 1.43.6 from source and used resize2fs from there to
successfully resize from 21 -> 24 TB on a RAID6.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu.
https://bugs.launchpad.net/bugs/1321958

Title:
  resize2fs does not start to actually grow an ext4

Status in e2fsprogs package in Ubuntu:
  Fix Released
Status in e2fsprogs source package in Trusty:
  Confirmed

Bug description:
  Ubuntu 14.04 LTS, all proposed updates done
  Kernel: 3.13.0-24-generic, 
  Package: e2fsprogs 1.42.9-3ubuntu1, 
  System: Haswell i7, 32GB RAM, LSI SAS 9207-8i HBA and LSI SAS 9211-8i HBA

  I tried to increse the size of an ext4 filesystem. Old size 20TB,
  wanted new size 28TB. I tried offline resize with "resize2fs -fp
  /dev/md2" and later online resize using "resize2fs -f /dev/md2". In
  both cases, after giving the command a rezise2fs process is created
  that uses nearly 100% cpu according to top, but it does not perform
  any actual resize. It only prints its version and date and then it
  does not finish for hours. I had it running for more than a day
  without finishing:

  root@marvin:~# resize2fs -f /dev/md2
  resize2fs 1.42.9 (4-Feb-2014)

  There is never more terminal output than that. It looks to me that
  resize2fs hangs in a endless calcualtion or loop or something similar.

  Some more info about the filesystem:

  root@marvin:~# tune2fs -l /dev/md2
  tune2fs 1.42.9 (4-Feb-2014)
  Filesystem volume name:   data
  Last mounted on:  /media/data01
  Filesystem UUID:  e3845e15-0336-47ae-8aec-df75acb217c5
  Filesystem magic number:  0xEF53
  Filesystem revision #:1 (dynamic)
  Filesystem features:  has_journal ext_attr resize_inode dir_index 
filetype needs_recovery extent 64bit flex_bg sparse_super large_file huge_file 
uninit_bg dir_nlink extra_isize
  Filesystem flags: signed_directory_hash 
  Default mount options:user_xattr acl
  Filesystem state: clean
  Errors behavior:  Continue
  Filesystem OS type:   Linux
  Inode count:  305225728
  Block count:  4883606400
  Reserved block count: 0
  Free blocks:  22919919
  Free inodes:  302894731
  First block:  0
  Block size:   4096
  Fragment size:4096
  Group descriptor size:64
  Reserved GDT blocks:  1024
  Blocks per group: 32768
  Fragments per group:  32768
  Inodes per group: 2048
  Inode blocks per group:   128
  RAID stride:  128
  RAID stripe width:640
  Flex block group size:16
  Filesystem created:   Fri Sep 20 19:45:01 2013
  Last mount time:  Tue May 20 02:14:37 2014
  Last write time:  Tue May 20 02:14:37 2014
  Mount count:  3
  Maximum mount count:  -1
  Last checked: Tue May 20 01:34:05 2014
  Check interval:   0 ()
  Lifetime writes:  34 TB
  Reserved blocks uid:  0 (user root)
  Reserved blocks gid:  0 (group root)
  First inode:  11
  Inode size:  256
  Required extra isize: 28
  Desired extra isize:  28
  Journal inode:8
  Default directory hash:   half_md4
  Directory Hash Seed:  569ec5fc-4d5e-4639-bef3-42cde5fbe948
  Journal backup:   inode blocks

  
  I did also run an filesystem check:

  root@marvin:~# e2fsck -vfp /dev/md2
  
   2330890 inodes used (0.76%, out of 305225728)
 14882 non-contiguous files (0.6%)
   949 non-contiguous directories (0.0%)
   # of inodes with ind/dind/tind blocks: 0/0/0
   Extent depth histogram: 2317190/13041/651
4868171016 blocks used (99.68%, out of 4883606400)
 0 bad blocks
  1654 large files

   2273776 regular files
 57105 directories
 0 character device files
 0 block device files
 0 fifos
 0 links
 0 symbolic links (0 fast symbolic links)
 0 sockets
  
   2330881 files

  The underlying device is an mdadm RAID6 that was grown from 7 

[Touch-packages] [Bug 1717984] [NEW] [Precision 5510, Realtek ALC3266, Black Headphone Out, Left] Pulseaudio fails to detect card

2017-09-18 Thread Danny Howard
Public bug reported:

I can not get audio out. I try the headphone jack, the headphone jack on
my HDMI display, internal speakers, no nothing zip nada.

In Miltimedia > PulseAudio Volume Control > Output Devices, there are no
audio devices. If I Show All Output Devices then a device called
"silence" is listed. I can turn up the volume on that and see the level
jumping around but nothing in my ears. The Configuration tab says no
cards available.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: pulseaudio 1:8.0-0ubuntu3.3
ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
Uname: Linux 4.4.0-93-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: XFCE
Date: Mon Sep 18 10:27:49 2017
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-trusty-amd64-osp1-20150720-0
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-10-14 (339 days ago)
InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150720-04:06
SourcePackage: pulseaudio
Symptom: audio
Symptom_Card: HDA-Intel - HDA Intel PCH
Symptom_Jack: Black Headphone Out, Left
Title: [Precision 5510, Realtek ALC3266, Black Headphone Out, Left] Pulseaudio 
fails to detect card
UpgradeStatus: Upgraded to xenial on 2016-10-14 (339 days ago)
dmi.bios.date: 08/08/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.2.13
dmi.board.name: 0N8J4R
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.13:bd08/08/2016:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn0N8J4R:rvrA01:cvnDellInc.:ct9:cvr:
dmi.product.name: Precision 5510
dmi.sys.vendor: Dell Inc.

** Affects: pulseaudio (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1717984

Title:
  [Precision 5510, Realtek ALC3266, Black Headphone Out, Left]
  Pulseaudio fails to detect card

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I can not get audio out. I try the headphone jack, the headphone jack
  on my HDMI display, internal speakers, no nothing zip nada.

  In Miltimedia > PulseAudio Volume Control > Output Devices, there are
  no audio devices. If I Show All Output Devices then a device called
  "silence" is listed. I can turn up the volume on that and see the
  level jumping around but nothing in my ears. The Configuration tab
  says no cards available.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.3
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  Date: Mon Sep 18 10:27:49 2017
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150720-0
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-10-14 (339 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150720-04:06
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Left
  Title: [Precision 5510, Realtek ALC3266, Black Headphone Out, Left] 
Pulseaudio fails to detect card
  UpgradeStatus: Upgraded to xenial on 2016-10-14 (339 days ago)
  dmi.bios.date: 08/08/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.13
  dmi.board.name: 0N8J4R
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.13:bd08/08/2016:svnDellInc.:pnPrecision5510:pvr:rvnDellInc.:rn0N8J4R:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision 5510
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1717984/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : 

[Touch-packages] [Bug 1670959] Re: systemd-resolved using 100% CPU

2017-04-16 Thread Danny
** Description changed:

  Sometimes systemd-resolved process is using 100% CPU.
  After a while it changes back to normal.
  
  It happens usually after connecting to the (wifi) network, like starting
  the OS.
  
  strace output:
  
  sendmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589), 
sin_addr=inet_addr("127.0.0.1")}, 
msg_iov(1)=[{"6\215\201\200\0\1\0\1\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\300\f\0\34\0\1\0\0\10\235\0\20&\6(\0\0024\0Y%L\4\6#f&\214\0\0)\377\326\0\0\0\0\0\0",
 81}], msg_controllen=28, [{cmsg_len=28, cmsg_level=SOL_IP, 
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"), 
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}], 
msg_flags=0}, 0) = 81
  sendmsg(3, {msg_name(0)=NULL, 
msg_iov(4)=[{"PRIORITY=6\nSYSLOG_FACILITY=3\nCODE_FILE=../src/resolve/resolved-dns-stub.c\nCODE_LINE=363\nCODE_FUNCTION=dns_stub_process_query\nSYSLOG_IDENTIFIER=systemd-resolved\n",
 160}, {"MESSAGE=", 8}, {"Processing query...", 19}, {"\n", 1}], 
msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 188
  epoll_wait(4, [{EPOLLIN, {u32=3176459184, u64=94565471415216}}], 16, -1) = 1
  clock_gettime(CLOCK_BOOTTIME, {44665, 938069872}) = 0
  recvfrom(12, NULL, 0, MSG_PEEK|MSG_TRUNC, NULL, NULL) = 53
  recvmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589), 
sin_addr=inet_addr("127.0.0.1")}, 
msg_iov(1)=[{"Z\262\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
 3936}], msg_controllen=56, [{cmsg_len=28, cmsg_level=SOL_IP, 
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"), 
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}, 
{cmsg_len=20, cmsg_level=SOL_IP, cmsg_type=IP_TTL, {ttl=64}}], msg_flags=0}, 0) 
= 53
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  getrandom("\365I", 2, GRND_NONBLOCK)= 2
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  getrandom("\203;", 2, GRND_NONBLOCK)= 2
  clock_gettime(CLOCK_BOOTTIME, {44665, 938446937}) = 0
  open("/run/systemd/netif/links/3", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such 
file or directory)
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  socket(AF_INET, SOCK_DGRAM|SOCK_CLOEXEC|SOCK_NONBLOCK, IPPROTO_IP) = 18
  connect(18, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("127.0.0.1")}, 16) = 0
  epoll_ctl(4, EPOLL_CTL_ADD, 18, {EPOLLIN, {u32=3176610576, 
u64=94565471566608}}) = 0
  write(18, 
"\203;\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
 53) = 53
  clock_gettime(CLOCK_BOOTTIME, {44665, 938833717}) = 0
  clock_gettime(CLOCK_BOOTTIME, {44665, 938875138}) = 0
  epoll_ctl(4, EPOLL_CTL_DEL, 18, NULL)   = 0
  close(18)   = 0
  
- 
  journalctl output:
  
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:41 parsec dnsmasq[1545]: Maximum number of concurrent DNS 
queries reached (max: 150)
- 
- 
  
  As you can see, I would use it together with dnsmasq.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-18ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0
  Uname: Linux 4.10.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  Date: Wed Mar  8 08:20:18 2017
  MachineType: Hewlett-Packard HP EliteBook Folio 1020 G1
  ProcEnviron:
-  LANGUAGE=en_US:en
-  TERM=xterm
-  PATH=(custom, no user)
-  LANG=en_US.UTF-8
-  SHELL=/bin/zsh
+  LANGUAGE=en_US:en
+  TERM=xterm
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.10.0-9-generic 
root=UUID=a54fe703-35d4-47ac-9c6e-4034421531fb ro rootflags=subvol=@
  SourcePackage: systemd
  UpgradeStatus: Upgraded to zesty on 2015-05-24 (653 days ago)
  dmi.bios.date: 03/09/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: M77 Ver. 01.05
  dmi.board.name: 2271
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 91.4C
  dmi.chassis.asset.tag: CNU51199KV
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrM77Ver.01.05:bd03/09/2015:svnHewlett-Packard:pnHPEliteBookFolio1020G1:pvrA3009DD18303:rvnHewlett-Packard:rn2271:rvrKBCVersion91.4C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook Folio 1020 G1
  

[Touch-packages] [Bug 1670959] Re: systemd-resolved using 100% CPU

2017-04-15 Thread Danny
1. top
  PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND
19147 systemd+  20   0   50848   6232   4572 R  99.0  0.1   5:43.81 
systemd-resolve 
  
 1472 dnsmasq   20   0   57020   3084   2620 R  63.1  0.0  44:03.49 dnsmasq

2. journalctl -u systemd-resolved.service
Apr 16 13:01:59 Danny systemd-resolved[19147]: DNSSEC validation failed for 
question clients-china.l.google.com IN A: failed-auxiliary
Apr 16 13:02:02 Danny systemd-resolved[19147]: Using degraded feature set 
(UDP+EDNS0) for DNS server 127.0.0.1.
Apr 16 13:02:08 Danny systemd-resolved[19147]: Server 127.0.0.1 does not 
support DNSSEC, downgrading to non-DNSSEC mode.
Apr 16 13:06:24 Danny systemd-resolved[19147]: Server 192.168.128.1 does not 
support DNSSEC, downgrading to non-DNSSEC mode.
Apr 16 13:11:24 Danny systemd-resolved[19147]: Grace period over, resuming full 
feature set (UDP+EDNS0+DO+LARGE) for DNS server 127.0.0.1.

3. journalctl -u dnsmasq.service
Apr 16 13:18:27 Danny dnsmasq[1472]: Maximum number of concurrent DNS queries 
reached (max: 150)
Apr 16 13:18:33 Danny dnsmasq[1472]: Maximum number of concurrent DNS queries 
reached (max: 150)
Apr 16 13:18:39 Danny dnsmasq[1472]: Maximum number of concurrent DNS queries 
reached (max: 150)
Apr 16 13:18:45 Danny dnsmasq[1472]: Maximum number of concurrent DNS queries 
reached (max: 150)
Apr 16 13:18:51 Danny dnsmasq[1472]: Maximum number of concurrent DNS queries 
reached (max: 150)

4. lsb_release -a
Distributor ID: Ubuntu
Description:Ubuntu 17.04
Release:17.04
Codename:   zesty

5. sudo strace -p 1472 --- dnsmasq
bind(12, {sa_family=AF_INET, sin_port=htons(37051), 
sin_addr=inet_addr("0.0.0.0")}, 16) = 0
sendto(12, "g\325\1\20\0\1\0\0\0\0\0\1\rclients-china\1l\6goo"..., 55, 0, 
{sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("127.0.0.53")}, 16) 
= 55
poll([{fd=3, events=POLLIN}, {fd=4, events=POLLIN}, {fd=5, events=POLLIN}, 
{fd=6, events=POLLIN}, {fd=7, events=POLLIN}, {fd=8, events=POLLIN}, {fd=9, 
events=POLLIN}, {fd=12, events=POLLIN}], 8, -1) = 2 ([{fd=4, revents=POLLIN}, 
{fd=12, revents=POLLIN}])
recvfrom(12, "g\325\201\200\0\1\0\6\0\0\0\1\rclients-china\1l\6goo"..., 5131, 
0, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("127.0.0.53")}, 
[16]) = 151
sendmsg(4, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33355), 
sin_addr=inet_addr("127.0.0.1")}, 
msg_iov(1)=[{"\272\303\201\220\0\1\0\6\0\0\0\1\rclients-china\1l\6goo"..., 
151}], msg_controllen=0, msg_flags=0}, 0) = 151
close(12)   = 0
recvmsg(4, {msg_name(16)={sa_family=AF_INET, sin_port=htons(57326), 
sin_addr=inet_addr("127.0.0.1")}, 
msg_iov(1)=[{"C\21\1\20\0\1\0\0\0\0\0\1\rclients-china\1l\6goo"..., 4096}], 
msg_controllen=0, msg_flags=0}, 0) = 55
socket(AF_INET, SOCK_DGRAM, IPPROTO_IP) = 12
fcntl(12, F_GETFL)  = 0x2 (flags O_RDWR)
fcntl(12, F_SETFL, O_RDWR|O_NONBLOCK)   = 0

6. sudo strace -p 1914
clock_gettime(CLOCK_BOOTTIME, {5858, 172230641}) = 0
open("/run/systemd/netif/links/2", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such 
file or directory)
stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
socket(AF_INET, SOCK_DGRAM|SOCK_CLOEXEC|SOCK_NONBLOCK, IPPROTO_IP) = 18
connect(18, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("127.0.0.1")}, 16) = 0
epoll_ctl(4, EPOLL_CTL_ADD, 18, {EPOLLIN, {u32=1040890848, 
u64=94559040879584}}) = 0
write(18, ";q\1\20\0\1\0\0\0\0\0\1\17ec2-52-7-217-10\tcom"..., 68) = 68
clock_gettime(CLOCK_BOOTTIME, {5858, 172456596}) = 0
clock_gettime(CLOCK_BOOTTIME, {5858, 172482649}) = 0
epoll_ctl(4, EPOLL_CTL_DEL, 18, NULL)   = 0
close(18)   = 0
sendmsg(15, {msg_name(16)={sa_family=AF_INET, sin_port=htons(45041), 
sin_addr=inet_addr("127.0.0.1")}, 
msg_iov(1)=[{"qX\201\200\0\1\0\1\0\0\0\1\17ec2-52-7-217-10\tcom"..., 84}], 
msg_controllen=28, [{cmsg_len=28, cmsg_level=SOL_IP, cmsg_type=IP_PKTINFO, 
{ipi_ifindex=if_nametoindex("lo"), ipi_spec_dst=inet_addr("127.0.0.53"), 
ipi_addr=inet_addr("127.0.0.53")}}], msg_flags=0}, 0) = 84
epoll_wait(4, [{EPOLLIN, {u32=1039855040, u64=94559039843776}}], 16, -1) = 1
clock_gettime(CLOCK_BOOTTIME, {5858, 172675790}) = 0
recvfrom(15, NULL, 0, MSG_PEEK|MSG_TRUNC, NULL, NULL) = 68
recvmsg(15, {msg_name(16)={sa_family=AF_INET, sin_port=htons(48677), 
sin_addr=inet_addr("127.0.0.1")}, 
msg_iov(1)=[{"\313{\1\20\0\1\0\0\0\0\0\1\17ec2-52-7-217-10\tcom"..., 3936}], 
msg_controllen=56, [{cmsg_len=28, cmsg_level=SOL_IP, cmsg_type=IP_PKTINFO, 
{ipi_ifindex=if_nametoindex("lo"), ipi_spec_dst=inet_addr("127.0.0.53"), 
ipi_addr=inet_addr("127.

[Touch-packages] [Bug 1670959] Re: systemd-resolved using 100% CPU

2017-04-15 Thread Danny
This bug still exists in ubuntu 17.04 release version!

100% CPU with "Unassigned", OMG!

-- 
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/1670959

Title:
  systemd-resolved using 100% CPU

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Sometimes systemd-resolved process is using 100% CPU.
  After a while it changes back to normal.

  It happens usually after connecting to the (wifi) network, like
  starting the OS.

  strace output:

  sendmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589), 
sin_addr=inet_addr("127.0.0.1")}, 
msg_iov(1)=[{"6\215\201\200\0\1\0\1\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\300\f\0\34\0\1\0\0\10\235\0\20&\6(\0\0024\0Y%L\4\6#f&\214\0\0)\377\326\0\0\0\0\0\0",
 81}], msg_controllen=28, [{cmsg_len=28, cmsg_level=SOL_IP, 
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"), 
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}], 
msg_flags=0}, 0) = 81
  sendmsg(3, {msg_name(0)=NULL, 
msg_iov(4)=[{"PRIORITY=6\nSYSLOG_FACILITY=3\nCODE_FILE=../src/resolve/resolved-dns-stub.c\nCODE_LINE=363\nCODE_FUNCTION=dns_stub_process_query\nSYSLOG_IDENTIFIER=systemd-resolved\n",
 160}, {"MESSAGE=", 8}, {"Processing query...", 19}, {"\n", 1}], 
msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 188
  epoll_wait(4, [{EPOLLIN, {u32=3176459184, u64=94565471415216}}], 16, -1) = 1
  clock_gettime(CLOCK_BOOTTIME, {44665, 938069872}) = 0
  recvfrom(12, NULL, 0, MSG_PEEK|MSG_TRUNC, NULL, NULL) = 53
  recvmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589), 
sin_addr=inet_addr("127.0.0.1")}, 
msg_iov(1)=[{"Z\262\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
 3936}], msg_controllen=56, [{cmsg_len=28, cmsg_level=SOL_IP, 
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"), 
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}, 
{cmsg_len=20, cmsg_level=SOL_IP, cmsg_type=IP_TTL, {ttl=64}}], msg_flags=0}, 0) 
= 53
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  getrandom("\365I", 2, GRND_NONBLOCK)= 2
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  getrandom("\203;", 2, GRND_NONBLOCK)= 2
  clock_gettime(CLOCK_BOOTTIME, {44665, 938446937}) = 0
  open("/run/systemd/netif/links/3", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such 
file or directory)
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  socket(AF_INET, SOCK_DGRAM|SOCK_CLOEXEC|SOCK_NONBLOCK, IPPROTO_IP) = 18
  connect(18, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("127.0.0.1")}, 16) = 0
  epoll_ctl(4, EPOLL_CTL_ADD, 18, {EPOLLIN, {u32=3176610576, 
u64=94565471566608}}) = 0
  write(18, 
"\203;\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
 53) = 53
  clock_gettime(CLOCK_BOOTTIME, {44665, 938833717}) = 0
  clock_gettime(CLOCK_BOOTTIME, {44665, 938875138}) = 0
  epoll_ctl(4, EPOLL_CTL_DEL, 18, NULL)   = 0
  close(18)   = 0


  journalctl output:

  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:41 parsec dnsmasq[1545]: Maximum number of concurrent DNS 
queries reached (max: 150)


  
  As you can see, I would use it together with dnsmasq.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-18ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0
  Uname: Linux 4.10.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  Date: Wed Mar  8 08:20:18 2017
  MachineType: Hewlett-Packard HP EliteBook Folio 1020 G1
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.10.0-9-generic 
root=UUID=a54fe703-35d4-47ac-9c6e-4034421531fb ro rootflags=subvol=@
  SourcePackage: systemd
  UpgradeStatus: Upgraded to zesty on 2015-05-24 (653 days ago)
  dmi.bios.date: 03/09/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: M77 Ver. 01.05
  dmi.board.name: 2271
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 91.4C
  dmi.chassis.asset.tag: CNU51199KV
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 

[Touch-packages] [Bug 1658921] Re: NetworkManager does not manage wired connection

2017-04-08 Thread Danny B
Just had this happen after an ordinary desktop upgrade from 16.04 to
16.10, had to do the touch thing, because 10-globally-managed-
devices.conf was missing.

For the default user-friendly desktop linux distro option, Ubuntu seems
pretty bad at this just working out of the box thing. I've had less
random bugs during my several years with Gentoo, and I didn't ditch it
so I could waste more of my time installing obscure kernel patches and
having to configure things I don't care about.

-- 
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/1658921

Title:
  NetworkManager does not manage wired connection

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  NetworkManager does not manage my wired eth0 connection, no matter how
  I set /etc/network/interfaces or
  /etc/NetworkManager/NetworkManager.conf

  Using ubuntu 16.04, /etc/network/interfaces only managed lo, and
  [ifupdown] section of NetworkManager.conf had set managed=false.

  With these same settings, after upgrading to ubuntu 16.10, eth0
  appears as unmanaged in nm-applet.

  If I modify /etc/network/interfaces and add

  auto eth0
  iface eth0 inet dhcp

  And set managed=true in NetworkManager.conf [ifupdown] section, eth0
  is still unmanaged despite it does get an IP from DHCP server.

  This is happening in my five computers (two laptops and three
  desktops).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1658921/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1302270] Re: [regression] Poor performance with recent update with i965: libGL error: failed to open drm device: Permission denied

2016-10-05 Thread Danny Howard
*** This bug is a duplicate of bug 1415104 ***
https://bugs.launchpad.net/bugs/1415104

I found this bug trying to launch firefox Ubuntu 16.04 server:

djh@test0:~$ firefox
libGL error: failed to open drm device: Permission denied
libGL error: failed to load driver: i965

-- 
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/1302270

Title:
  [regression] Poor performance with recent update with i965: libGL
  error: failed to open drm device: Permission denied

Status in Compiz:
  Invalid
Status in Unity:
  Invalid
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  I rebooted into up to date trusty and noticed Unity was incredibly
  slow. I hadn't rebooted in a while, so I'm not sure what package
  caused the issue, though I'm guessing it is mesa (I saw i965 pci ids
  were ifdef'd in the Launchpad diff, but I didn't look super closely).

  ~/.xsession-errors has this to say:
  libGL error: failed to open drm device: Permission denied
  libGL error: failed to load driver: i965

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8
  Uname: Linux 3.13.0-22-generic x86_64
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.14-0ubuntu1
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Apr  3 20:08:18 2014
  DistUpgraded: 2013-11-04 08:48:34,282 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:215a]
  InstallationDate: Installed on 2011-06-28 (1010 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110425.2)
  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: LENOVO 5129CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-22-generic 
root=UUID=88689ad2-74b5-442c-9290-8ae60b63e16b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to trusty on 2013-11-04 (150 days ago)
  dmi.bios.date: 02/24/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6QET64WW (1.34 )
  dmi.board.name: 5129CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6QET64WW(1.34):bd02/24/2011:svnLENOVO:pn5129CTO:pvrThinkPadX201s:rvnLENOVO:rn5129CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 5129CTO
  dmi.product.version: ThinkPad X201s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11+14.04.20140328-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Thu Apr  3 19:38:17 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   16404 
   vendor LEN
  xserver.version: 2:1.15.0-1ubuntu7

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/1302270/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1611058] [NEW] Cannot login into cinnamon from lightdm

2016-08-08 Thread Danny Trunk
Public bug reported:

I'm not sure if it's related to Cinnamon.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: dbus 1.10.6-1ubuntu3
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: Mon Aug  8 19:06:45 2016
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-08-07 (1 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: dbus
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: dbus (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1611058

Title:
  Cannot login into cinnamon from lightdm

Status in dbus package in Ubuntu:
  New

Bug description:
  I'm not sure if it's related to Cinnamon.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: dbus 1.10.6-1ubuntu3
  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: Mon Aug  8 19:06:45 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-07 (1 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: dbus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1611058/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1464917] Re: reboot hangs at 'Reached target Shutdown'

2016-06-13 Thread Danny Yates
Since there hasn't been an answer for a month, I'll ask the question
again...

Is there any chance that this will be backported for Xenial? At the
moment, folks on an LTS release are struggling to cleanly shut their
machines down.

-- 
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/1464917

Title:
  reboot hangs at 'Reached target Shutdown'

Status in systemd:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  This bug is resolved.  Do not follow up to this bug.  Shutdown bugs
  are specific to the software installed and its configuration.  If you
  are experiencing a shutdown hang, please file a separate bug report
  and follow the debugging instructions described in the "Debugging
  boot/shutdown problems" section of
  /usr/share/doc/systemd/README.Debian.gz to check if there are any
  hanging jobs at shutdown. Capturing a screen photo of "journalctl -b"
  in the rescue shell might be enlightening.

  [Original report]
  I rebooted my 15.04 system, and found it hanging indefinitely at the plymouth 
shutdown screen.  Hitting esc to reveal the console showed a normal set of 
shutdown messages, ending with 'Reached target Shutdown' (paraphrased from 
memory).

  The system never rebooted on its own.  I had to use SysRq to finish
  the shutdown.


  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: systemd 219-7ubuntu6
  ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
  Uname: Linux 3.19.0-20-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Jun 13 11:53:10 2015
  InstallationDate: Installed on 2010-09-24 (1723 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MachineType: LENOVO 2306CTO
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-20-generic 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to vivid on 2014-12-06 (189 days ago)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2306CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1464917/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1446921] [NEW] package missing term openssl in initial description

2015-04-21 Thread Danny Sauer
Public bug reported:

When attempting to compile a product, the ./configure stage indicates
that openssl-dev is missing.  I have openssl installed, but there is no
package named anything like openssl-dev or openssl-devel.  Also, running
aptitude search openssl does not show libssl-dev.  It seems
reasonable to expect that the development package would show up in a
general search for the name of the package.  It's not hard to do a good
search for ubuntu openssl dev and come up with several people asking
the question (and getting an answer), but it seems likely that I'll
probably forget this again next time I need to do it.

It would be nice to either add an openssl-dev virtual package which
points at libssl-dev, or to work the term openssl into the first
part of the description that something like aptitude search would
find.  Yes, apt-cache search openssl | grep dev does find it, so maybe
the real bug is that I seem to remember aptitude search instead of
apt-cache search. :)

I'd prioritize this pretty low.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: libssl-dev 1.0.1f-1ubuntu9.4
ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
Uname: Linux 3.13.0-43-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.14.7-0ubuntu8.4
Architecture: i386
Date: Tue Apr 21 20:05:04 2015
InstallationDate: Installed on 2014-07-01 (295 days ago)
InstallationMedia: Lubuntu 14.04 LTS Trusty Tahr - Release i386 (20140416.2)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: openssl
UpgradeStatus: Upgraded to utopic on 2015-01-10 (102 days ago)

** Affects: openssl (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug i386 utopic

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1446921

Title:
  package missing term openssl in initial description

Status in openssl package in Ubuntu:
  New

Bug description:
  When attempting to compile a product, the ./configure stage
  indicates that openssl-dev is missing.  I have openssl installed, but
  there is no package named anything like openssl-dev or openssl-devel.
  Also, running aptitude search openssl does not show libssl-dev.
  It seems reasonable to expect that the development package would show
  up in a general search for the name of the package.  It's not hard to
  do a good search for ubuntu openssl dev and come up with several
  people asking the question (and getting an answer), but it seems
  likely that I'll probably forget this again next time I need to do it.

  It would be nice to either add an openssl-dev virtual package which
  points at libssl-dev, or to work the term openssl into the first
  part of the description that something like aptitude search would
  find.  Yes, apt-cache search openssl | grep dev does find it, so
  maybe the real bug is that I seem to remember aptitude search
  instead of apt-cache search. :)

  I'd prioritize this pretty low.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: libssl-dev 1.0.1f-1ubuntu9.4
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8.4
  Architecture: i386
  Date: Tue Apr 21 20:05:04 2015
  InstallationDate: Installed on 2014-07-01 (295 days ago)
  InstallationMedia: Lubuntu 14.04 LTS Trusty Tahr - Release i386 (20140416.2)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: openssl
  UpgradeStatus: Upgraded to utopic on 2015-01-10 (102 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1446921/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1162781] Re: bluez package out of date, 5.3 is available

2014-08-25 Thread Danny
they better update it. now.

-- 
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/1162781

Title:
  bluez package out of date, 5.3 is available

Status in “bluez” package in Ubuntu:
  Triaged

Bug description:
  Looks like there have been a lot of improvements to bluez since the
  4.x series. Would be nice to get the latest release pulled in.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1162781/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1360893] [NEW] Wii U Pro Controller requires PIN

2014-08-24 Thread Danny
Public bug reported:

The Wii U Pro controller requires a PIN and is used as a mouse.

** Affects: bluez (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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/1360893

Title:
  Wii U Pro Controller requires PIN

Status in “bluez” package in Ubuntu:
  New

Bug description:
  The Wii U Pro controller requires a PIN and is used as a mouse.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1360893/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1348259] Re: Openldap config modify tls error

2014-07-24 Thread Danny Hernandez
Thank you!  That was it!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1348259

Title:
  Openldap config modify tls error

Status in “openldap” package in Ubuntu:
  Invalid

Bug description:
  Following the steps to setup and configure openldap with a master and
  a slave.  When configuring the slave for TLS running the command as
  per the instructions on https://help.ubuntu.com/14.04/serverguide
  /openldap-server.html#openldap-tls-replication the following error
  occurs:

  sudo ldapmodify -Y EXTERNAL -H ldapi:/// -f consumer_sync_tls.ldif
  SASL/EXTERNAL authentication started
  SASL username: gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth
  SASL SSF: 0
  modifying entry olcDatabase={1}hdb,cn=config
  ldap_modify: Other (e.g., implementation specific) error (80)
additional info: Error: parse_syncrepl_line: unable to parse 
bindmethod=simplebinddn=cn=admin,dc=example,dc=com

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1348259/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp