[Touch-packages] [Bug 2056627] [NEW] PHPStorm crashes when opening a project

[Christoph Reiter]

Public bug reported:

Filing mostly in case anyone else hits this and is looking for
workarounds:

Since the Update to 24.04 PHPStorm crashes on open for me. I think when
it tries to preview a markdown file, like a README.md which is shown
when opening a project.

```
[0309/094602.913394:FATAL:setuid_sandbox_host.cc(158)] The SUID sandbox helper 
binary was found, but is not configured correctly. Rather than run without 
sandboxing I'm aborting now. You need to make sure that 
/home/user/bin/phpstorm/jbr/lib/chrome-sandbox is owned by root and has mode 
4755.
```

Workaround 1 (wont persist reboots, needs root):

sudo sysctl -w kernel.apparmor_restrict_unprivileged_unconfined=0
sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=0

Workaround 2 (persists and doesn't need root):

thanks to https://youtrack.jetbrains.com/issue/IDEA-313202/IDE-crashes-
due-to-chrome-sandbox-is-owned-by-root-and-has-mode-error-when-IDE-is-
launching-the-JCEF-in-a-sandbox#focus=Comments-27-7059083.0-0

* Run `/bin/phpstorm.sh dontReopenProjects` (to avoid it 
crashing on start)
* ctrl+shift+a
* type "Registry..." and select it
* disable the "ide.browser.jcef.sandbox.enable" option
* Restart phpstorm

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

** Description changed:

  Filing mostly in case anyone else hits this and is looking for
  workarounds:
  
  Since the Update to 24.04 PHPStorm crashes on open for me. I think when
  it tries to preview a markdown file, like a README.md which is shown
  when opening a project.
  
  ```
  [0309/094602.913394:FATAL:setuid_sandbox_host.cc(158)] The SUID sandbox 
helper binary was found, but is not configured correctly. Rather than run 
without sandboxing I'm aborting now. You need to make sure that 
/home/user/bin/phpstorm/jbr/lib/chrome-sandbox is owned by root and has mode 
4755.
  ```
  
  Workaround 1 (wont persist reboots, needs root):
  
  sudo sysctl -w kernel.apparmor_restrict_unprivileged_unconfined=0
  sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=0
  
  Workaround 2 (persists and doesn't need root):
  
  thanks to https://youtrack.jetbrains.com/issue/IDEA-313202/IDE-crashes-
  due-to-chrome-sandbox-is-owned-by-root-and-has-mode-error-when-IDE-is-
  launching-the-JCEF-in-a-sandbox#focus=Comments-27-7059083.0-0
  
  * Run `/bin/phpstorm.sh dontReopenProjects` (to avoid it 
crashing on start)
  * ctrl+shift+a
- * type "Registry..."
+ * type "Registry..." and select it
  * disable the "ide.browser.jcef.sandbox.enable" option
  * Restart phpstorm

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

Title:
  PHPStorm crashes when opening a project

Status in apparmor package in Ubuntu:
  New

Bug description:
  Filing mostly in case anyone else hits this and is looking for
  workarounds:

  Since the Update to 24.04 PHPStorm crashes on open for me. I think
  when it tries to preview a markdown file, like a README.md which is
  shown when opening a project.

  ```
  [0309/094602.913394:FATAL:setuid_sandbox_host.cc(158)] The SUID sandbox 
helper binary was found, but is not configured correctly. Rather than run 
without sandboxing I'm aborting now. You need to make sure that 
/home/user/bin/phpstorm/jbr/lib/chrome-sandbox is owned by root and has mode 
4755.
  ```

  Workaround 1 (wont persist reboots, needs root):

  sudo sysctl -w kernel.apparmor_restrict_unprivileged_unconfined=0
  sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=0

  Workaround 2 (persists and doesn't need root):

  thanks to https://youtrack.jetbrains.com/issue/IDEA-313202/IDE-
  crashes-due-to-chrome-sandbox-is-owned-by-root-and-has-mode-error-
  when-IDE-is-launching-the-JCEF-in-a-
  sandbox#focus=Comments-27-7059083.0-0

  * Run `/bin/phpstorm.sh dontReopenProjects` (to avoid it 
crashing on start)
  * ctrl+shift+a
  * type "Registry..." and select it
  * disable the "ide.browser.jcef.sandbox.enable" option
  * Restart phpstorm

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


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

[Touch-packages] [Bug 2056517] Re: vsode profile still broken

[Christoph Reiter]

Thanks, I'm looking forward to it.

a bit unrelated: PHPStorm (and I'd guess all Jetbrains IDEs) is also
broken, but that is installed by unpacking a tarball to a location and
let it auto-update itself.

Is there any point in filing a bug for that too?

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

Title:
  vsode profile still broken

Status in apparmor package in Ubuntu:
  New

Bug description:
  Ubuntu 24.04, VSCode installed via their repo
  (https://packages.microsoft.com/repos/code)

  Some updates ago apparmor gained an exception for /usr/bin/code to
  work again.

  The desktop file uses `/usr/share/code/code` though (see
  /usr/share/applications/code.desktop), so starting vscode from the
  dock, or from the app search results in a crash:

  /usr/share/code/code
  [88564:0308/080414.682744:FATAL:credentials.cc(127)] Check failed: . : 
Permission denied (13)
  zsh: trace trap (core dumped)  /usr/share/code/code

  Could the profile be fixed to include all common ways to start vscode?

  My current workaround is to run this on every boot:

  sudo sysctl -w kernel.apparmor_restrict_unprivileged_unconfined=0
  sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=0

  thanks

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


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

[Touch-packages] [Bug 2056517] [NEW] vsode profile still broken

[Christoph Reiter]

Public bug reported:

Ubuntu 24.04, VSCode installed via their repo
(https://packages.microsoft.com/repos/code)

Some updates ago apparmor gained an exception for /usr/bin/code to work
again.

The desktop file uses `/usr/share/code/code` though (see
/usr/share/applications/code.desktop), so starting vscode from the dock,
or from the app search results in a crash:

/usr/share/code/code
[88564:0308/080414.682744:FATAL:credentials.cc(127)] Check failed: . : 
Permission denied (13)
zsh: trace trap (core dumped)  /usr/share/code/code

Could the profile be fixed to include all common ways to start vscode?

My current workaround is to run this on every boot:

sudo sysctl -w kernel.apparmor_restrict_unprivileged_unconfined=0
sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=0

thanks

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

** Description changed:

  Ubuntu 24.04, VSCode installed via their repo
  (https://packages.microsoft.com/repos/code)
  
  Some updates ago apparmor gained an exception for /usr/bin/code to work
  again.
  
- The desktop file uses `/usr/share/code/code` though, so starting vscode
- from the dock, or from the app search results in a crash:
+ The desktop file uses `/usr/share/code/code` though (see
+ /usr/share/applications/code.desktop), so starting vscode from the dock,
+ or from the app search results in a crash:
  
  /usr/share/code/code
  [88564:0308/080414.682744:FATAL:credentials.cc(127)] Check failed: . : 
Permission denied (13)
  zsh: trace trap (core dumped)  /usr/share/code/code
  
  Could the profile be fixed to include all common ways to start vscode?
  
  My current workaround is to run this on every boot:
  
  sudo sysctl -w kernel.apparmor_restrict_unprivileged_unconfined=0
  sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=0
  
- 
  thanks

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

Title:
  vsode profile still broken

Status in apparmor package in Ubuntu:
  New

Bug description:
  Ubuntu 24.04, VSCode installed via their repo
  (https://packages.microsoft.com/repos/code)

  Some updates ago apparmor gained an exception for /usr/bin/code to
  work again.

  The desktop file uses `/usr/share/code/code` though (see
  /usr/share/applications/code.desktop), so starting vscode from the
  dock, or from the app search results in a crash:

  /usr/share/code/code
  [88564:0308/080414.682744:FATAL:credentials.cc(127)] Check failed: . : 
Permission denied (13)
  zsh: trace trap (core dumped)  /usr/share/code/code

  Could the profile be fixed to include all common ways to start vscode?

  My current workaround is to run this on every boot:

  sudo sysctl -w kernel.apparmor_restrict_unprivileged_unconfined=0
  sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=0

  thanks

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


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

[Touch-packages] [Bug 1983794] Re: Evolution not deleting autosave files

[Christoph Petzold]

For me

  sudo apt remove libcanberra-gtk3-module

solved the problem.

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

Title:
  Evolution not deleting autosave files

Status in Evolution:
  Fix Released
Status in evolution package in Ubuntu:
  Invalid
Status in libcanberra package in Ubuntu:
  Triaged

Bug description:
  Running Ubuntu MATE, Ubuntu 22.04.1 LTS. Evolution v3.44.1-0ubuntu1
  was installed with the distribution on a new system and received
  settings imported from an earlier version on another computer.

  When composing an email, if the process takes long enough an autosave
  file is created as ~/.local/share/evolution/.evolution-
  composer.autosave-xx ("xx" is a random 6 character string).
  When the email is successfully sent, the autosave file SHOULD be
  deleted. It's not. When evolution is shut down and restarted I'm asked
  if I want to recover an unfinished email. Answering No to this will
  delete the autosave file, but otherwise it persists and the recovery
  query recurs the next time I open evolution.

  Other people are having the same issue, see
  https://gitlab.gnome.org/GNOME/evolution/-/issues/1972. The Gnome
  people aren't dealing with it, perhaps considering it a distro-
  specific bug.

  On a system used by many people this is a potential security issue.

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


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

[Touch-packages] [Bug 1779340] Re: systemd-networkd-wait-online.service Failed to start Wait for Network to be Configured with bridge

[Lupe Christoph]

** Attachment removed: "wait-online.strace"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1779340/+attachment/5577039/+files/wait-online.strace

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

Title:
  systemd-networkd-wait-online.service Failed to start Wait for Network
  to be Configured with bridge

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  The following simple netplan config results in a 2-minut unneccessary
  delay on boot. Everything works like it should in the end. The bridge
  has no interfaces due to a regression in Ubuntu migrating to netplan
  (see
  https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1779341).

  ubuntu@molnix3:~$ cat /etc/netplan/01-netcfg.yaml
  # This file describes the network interfaces available on your system
  # For more information, see netplan(5).
  network:
    version: 2
    renderer: networkd
    ethernets:
  enp4s0:
    dhcp4: yes
    dhcp6: yes

  ubuntu@molnix3:~$ cat /etc/netplan/br1.yaml
  network:
    version: 2
    bridges:
  br1:
    addresses: [10.1.0.9/16]
    interfaces: []

  ubuntu@molnix3:~$ cat /usr/lib/networkd-dispatcher/routable.d/tap0
  #!/bin/sh
  set -e
   if [ "$IFACE" = tap0 ]; then
    brctl addif br1 tap0
    ip link set tap0 promisc on
    ifmetric tap0 5
  fi

  ubuntu@molnix3:~$ journalctl -u systemd-networkd-wait-online.service -b
  -- Logs begin at Thu 2018-06-28 10:07:29 UTC, end at Fri 2018-06-29 14:09:18 
UTC. --
  Jun 29 13:58:16 molnix3 systemd[1]: Starting Wait for Network to be 
Configured...
  Jun 29 13:58:16 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo
  Jun 29 13:58:16 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo
  Jun 29 13:58:16 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo
  Jun 29 13:58:16 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo
  Jun 29 13:58:16 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo
  Jun 29 13:58:16 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo
  Jun 29 13:58:17 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo
  Jun 29 13:58:17 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo
  Jun 29 13:58:17 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo
  Jun 29 13:58:17 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo
  Jun 29 13:58:18 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo
  Jun 29 13:58:18 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo
  Jun 29 13:58:19 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo
  Jun 29 13:58:20 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo
  Jun 29 13:58:20 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo
  Jun 29 13:58:21 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo
  Jun 29 14:00:16 molnix3 systemd-networkd-wait-online[1468]: Event loop 
failed: Connection timed out
  Jun 29 14:00:16 molnix3 systemd[1]: systemd-networkd-wait-online.service: 
Main process exited, code=exited, status=1/FAILURE
  Jun 29 14:00:16 molnix3 systemd[1]: systemd-networkd-wait-online.service: 
Failed with result 'exit-code'.
  Jun 29 14:00:16 molnix3 systemd[1]: Failed to start Wait for Network to be 
Configured.

  ubuntu@molnix3:~$ /lib/systemd/systemd-networkd-wait-online
  managing: br1
  managing: enp4s0
  ignoring: lo

  ubuntu@molnix3:~$ networkctl
  IDX LINK TYPE   OPERATIONAL SETUP
    1 lo   loopback   carrier unmanaged
    2 enp4s0   ether  routableconfigured
    3 br1  ether  routableconfigured
    4 tap0 ether  routableunmanaged

  4 links listed.

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


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

[Touch-packages] [Bug 1779340] Re: systemd-networkd-wait-online.service Failed to start Wait for Network to be Configured with bridge

[Lupe Christoph]

I have not yet reproduced this on my Ubuntu 21.10 for lack of time, but
I ran into it on a Debian 11 machine I was converting to Netplan and
preparing to port the ifupdown scripts.

I tried ignoring unimportant interfaces, but no dice. So I ran an strace
on /lib/systemd/systemd-networkd-wait-online (attached). I failed to
understand what is really going on, but the program configures a epoll
instance. After some successful use of that something fails to happen
and the two minute timeout strikes. During that timeout, the program is
repeatedly looking at /run/systemd/netif/links/1, but it does not
change.

The machine has four interfaces: lo, ens3, dummy1 and tun0.
/run/systemd/netif/links/2 and /run/systemd/netif/links/3 are ens3 and
dummy1, 4 is probably tun0, being the last created, and the state is
ADDRESS_STATE=routable.

But /run/systemd/netif/links/1 is strange. This should be lo, but lo is 
configured:
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host 
   valid_lft forever preferred_lft forever

but /run/systemd/netif/links/1 is
ADMIN_STATE=unmanaged
OPER_STATE=carrier
CARRIER_STATE=carrier
ADDRESS_STATE=off

So I thought that adding a netplan configuration for lo might help.
Well, it doesn't. The strace is the same, except for the contents of the
netif file.

Please reopen this ticket and push it upstream. There is something
uncouth about systemd-networkd-wait-online's relationship with lo.

** Attachment added: "wait-online.strace"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1779340/+attachment/5577039/+files/wait-online.strace

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

Title:
  systemd-networkd-wait-online.service Failed to start Wait for Network
  to be Configured with bridge

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  The following simple netplan config results in a 2-minut unneccessary
  delay on boot. Everything works like it should in the end. The bridge
  has no interfaces due to a regression in Ubuntu migrating to netplan
  (see
  https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1779341).

  ubuntu@molnix3:~$ cat /etc/netplan/01-netcfg.yaml
  # This file describes the network interfaces available on your system
  # For more information, see netplan(5).
  network:
    version: 2
    renderer: networkd
    ethernets:
  enp4s0:
    dhcp4: yes
    dhcp6: yes

  ubuntu@molnix3:~$ cat /etc/netplan/br1.yaml
  network:
    version: 2
    bridges:
  br1:
    addresses: [10.1.0.9/16]
    interfaces: []

  ubuntu@molnix3:~$ cat /usr/lib/networkd-dispatcher/routable.d/tap0
  #!/bin/sh
  set -e
   if [ "$IFACE" = tap0 ]; then
    brctl addif br1 tap0
    ip link set tap0 promisc on
    ifmetric tap0 5
  fi

  ubuntu@molnix3:~$ journalctl -u systemd-networkd-wait-online.service -b
  -- Logs begin at Thu 2018-06-28 10:07:29 UTC, end at Fri 2018-06-29 14:09:18 
UTC. --
  Jun 29 13:58:16 molnix3 systemd[1]: Starting Wait for Network to be 
Configured...
  Jun 29 13:58:16 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo
  Jun 29 13:58:16 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo
  Jun 29 13:58:16 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo
  Jun 29 13:58:16 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo
  Jun 29 13:58:16 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo
  Jun 29 13:58:16 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo
  Jun 29 13:58:17 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo
  Jun 29 13:58:17 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo
  Jun 29 13:58:17 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo
  Jun 29 13:58:17 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo
  Jun 29 13:58:18 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo
  Jun 29 13:58:18 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo
  Jun 29 13:58:19 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo
  Jun 29 13:58:20 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo
  Jun 29 13:58:20 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo
  Jun 29 13:58:21 molnix3 systemd-networkd-wait-online[1468]: ignoring: lo
  Jun 29 14:00:16 molnix3 systemd-networkd-wait-online[1468]: Event loop 
failed: Connection timed out
  Jun 29 14:00:16 molnix3 systemd[1]: systemd-networkd-wait-online.service: 
Main process exited, code=exited, status=1/FAILURE
  Jun 29 14:00:16 molnix3 systemd[1]: systemd-networkd-wait-online.service: 
Failed with result 'exit-code'.
  Jun 29 14:00:16 molnix3 systemd[1]: Failed to start Wait for Network to be 
Configured.

  ubuntu@molnix3:~$ 

[Touch-packages] [Bug 1961898] Re: chromium-browser is refusing to start

[Christoph Singer]

Same here, Chromium does not start anymore.
System: Kubuntu 21.10 with latest updates as of today

chris@kubuntu:~$ LANG=C SNAPD_DEBUG=1 snap run chromium
2022/03/23 12:09:12.183829 tool_linux.go:204: DEBUG: restarting into 
"/snap/core/current/usr/bin/snap"
2022/03/23 12:09:12.201553 cmd_run.go:1026: DEBUG: executing snap-confine from 
/snap/core/12821/usr/lib/snapd/snap-confine
2022/03/23 12:09:12.201954 cmd_run.go:433: DEBUG: SELinux not enabled
2022/03/23 12:09:12.202219 tracking.go:46: DEBUG: creating transient scope 
snap.chromium.chromium
2022/03/23 12:09:12.202980 tracking.go:186: DEBUG: using session bus
2022/03/23 12:09:12.204386 tracking.go:319: DEBUG: create transient scope job: 
/org/freedesktop/systemd1/job/561
2022/03/23 12:09:12.205375 tracking.go:419: DEBUG: job result is "failed"
error: transient scope could not be started, job 
/org/freedesktop/systemd1/job/561 finished with result failed

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

Title:
  chromium-browser is refusing to start

Status in snapd package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu jammy box.

  I woke my box this morning & resumed it (from suspend; LXQt session) &
  everything was normal (many apps including chromium-browser visible on
  displays).  I can't say when I last logged in (many days no doubt!),
  but I shutdown session to use box for QA-test & comment on bug report.

  After normal reboot & logging in though I tried opening `chromium`
  many times but nothing happened (from dock in GNOME). As most of what
  I do is in `firefox` I ignored it...  It's been like that several
  hours with occasional tries & no exploration as to issue.

  On opening a terminal to try and open `chromium-browser` I get the
  following

  --
  guiverc@d960-ubu2:~$   chromium-browser 
  internal error, please report: running "chromium" failed: transient scope 
could not be started, job /org/freedesktop/systemd1/job/771 finished with 
result failed
  --

  In `journalctl` I notice

  --
  Feb 23 17:53:01 d960-ubu2 sudo[74762]:  guiverc : TTY=pts/0 ; 
PWD=/home/guiverc ; USER=root ; COMMAND=/usr/bin/journalctl
  Feb 23 17:53:01 d960-ubu2 sudo[74762]: pam_unix(sudo:session): session opened 
for user root(uid=0) by (uid=1000)
  Feb 23 17:53:07 d960-ubu2 systemd[12489]: 
snap.chromium.chromium.92bf8241-9710-47ef-bb6e-3642bf7db51e.scope: Couldn't 
move process 74970 to requested cgrou>
  Feb 23 17:53:07 d960-ubu2 systemd[12489]: 
snap.chromium.chromium.92bf8241-9710-47ef-bb6e-3642bf7db51e.scope: Failed to 
add PIDs to scope's control group: P>
  Feb 23 17:53:07 d960-ubu2 systemd[12489]: 
snap.chromium.chromium.92bf8241-9710-47ef-bb6e-3642bf7db51e.scope: Failed with 
result 'resources'.
  Feb 23 17:53:07 d960-ubu2 systemd[12489]: Failed to start 
snap.chromium.chromium.92bf8241-9710-47ef-bb6e-3642bf7db51e.scope.
  Feb 23 17:53:07 d960-ubu2 systemd[12489]: 
snap.chromium.chromedriver.0a6c0ea3-d0bb-4bbf-909b-ed15a870599c.scope: Couldn't 
move process 74994 to requested c>
  Feb 23 17:53:07 d960-ubu2 systemd[12489]: 
snap.chromium.chromedriver.0a6c0ea3-d0bb-4bbf-909b-ed15a870599c.scope: Failed 
to add PIDs to scope's control grou>
  Feb 23 17:53:07 d960-ubu2 systemd[12489]: 
snap.chromium.chromedriver.0a6c0ea3-d0bb-4bbf-909b-ed15a870599c.scope: Failed 
with result 'resources'.
  Feb 23 17:53:07 d960-ubu2 systemd[12489]: Failed to start 
snap.chromium.chromedriver.0a6c0ea3-d0bb-4bbf-909b-ed15a870599c.scope.
  Feb 23 17:53:07 d960-ubu2 polkitd(authority=local)[48397]: Registered 
Authentication Agent for unix-process:74411:1109253 (system bus name :1.183 
[pkttyage>
  Feb 23 17:53:11 d960-ubu2 polkit-agent-helper-1[75023]: pam_ecryptfs: 
pam_sm_authenticate: /home/guiverc is already mounted
  Feb 23 17:53:11 d960-ubu2 polkitd(authority=local)[48397]: Operator of 
unix-session:10 successfully authenticated as unix-user:guiverc to gain 
ONE-SHOT aut>
  Feb 23 17:53:11 d960-ubu2 pkexec[75020]: pam_unix(polkit-1:session): session 
opened for user root(uid=0) by (uid=1000)
  Feb 23 17:53:11 d960-ubu2 pkexec[75020]: guiverc: Executing command 
[USER=root] [TTY=/dev/pts/1] [CWD=/home/guiverc] [COMMAND=/usr/bin/dmesg]
  --
   
  I see a snap-confine error in `dmesg` but I don't think its related (nothing 
else is even close)

  [ 9697.594155] audit: type=1400 audit(1645597770.987:130):
  apparmor="DENIED" operation="capable"
  profile="/snap/core/12725/usr/lib/snapd/snap-confine" pid=73276
  comm="snap-confine" capability=4  capname="fsetid"

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: chromium-browser 1:85.0.4183.83-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu77
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  

[Touch-packages] [Bug 1915191] [NEW] ping utility displays wrong IPv4 address upon receiving ICMP Redirect

[Christoph Viethen]

Public bug reported:

* Observed behaviour *
We ping a host, say 137.226.39.170. While doing so, the router redirects us to 
137.226.42.42. (We verify, with Wireshark and taking a close look at RFC 792, 
that our redirect packet is formatted correctly on-wire.) We see the following 
output of the ping utility:

64 bytes from 137.226.39.170: icmp_seq=46 ttl=251 time=0.619 ms
64 bytes from 137.226.39.170: icmp_seq=47 ttl=251 time=0.676 ms
64 bytes from 137.226.39.170: icmp_seq=48 ttl=251 time=1.92 ms
>From 134.130.3.3 icmp_seq=47 Redirect Host(New nexthop: 42.42.226.137)
64 bytes from 137.226.39.170: icmp_seq=49 ttl=251 time=4.79 ms

The gateway address, as RFC 792 calls it, is displayed the wrong way
around. Feels like an Endianness bug right from the start.


* Expected behaviour *
ping utility should display the gateway address correctly. ("New nexthop: 
137.226.42.42")


* Inspection of source code; bug theory of operation *
iputils_20190709.orig.tar.xz --> iputils-20190709/ping.c

Bug happens in the function pr_icmph(). This gets called from one of
three different places (lines 899, 1075, and 1101 of ping.c), and only
in one case, the fourth parameter is set to NULL (when called from line
899).

The third parameter ("info") of pr_icmph() is generally meant to be
understood in host byte order. This can be seen in several places (lines
1185, 1284).

Well, but in one place, this fact is ignored and the content of this
third parameter, being in host byte order, gets copied into a structure
that, by definition, is supposed to contain that piece of information in
network byte order, which constitutes the bug.

lines 1250 etc:
{
struct sockaddr_in sin = {
.sin_family = AF_INET,
.sin_addr =  {
icp ? icp->un.gateway : info
}
};

printf(_("(New nexthop: %s)\n"), pr_addr(, sizeof sin));
}

In the first alternative of the ternary operator, icp->un.gateway is in
network byte order, and the value s_addr within struct in_addr that it
gets copied to is also in network byte order, so everything's beautiful.
But in the second alternative of the ternary operator, i.e. if icp
(parameter number four of pr_icmph) happens to be NULL, as happens when
pr_icmph() gets called from line 899, unfortunately the value of "info"
(in host byte order) gets copied into s_addr, and bad things happen.


* Bugfix patch *

--- ping.c  2019-07-09 22:55:49.0 +0200
+++ ping_fixed.c2021-02-09 20:08:18.724747594 +0100
@@ -1251,7 +1251,7 @@
struct sockaddr_in sin = {
.sin_family = AF_INET,
.sin_addr =  {
-   icp ? icp->un.gateway : info
+   icp ? icp->un.gateway : htonl(info)
}
};

Simply converts the contents of info (which is in h_ost byte order) to
n_etwork byte order, and everything's fine.

Tried it, and this reliably fixes the bug.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: iputils-ping 3:20190709-3
ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
Uname: Linux 5.4.0-65-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
Date: Tue Feb  9 19:33:57 2021
InstallationDate: Installed on 2015-12-09 (1889 days ago)
InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
SourcePackage: iputils
UpgradeStatus: Upgraded to focal on 2020-12-28 (43 days ago)

** Affects: iputils (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 iputils in Ubuntu.
https://bugs.launchpad.net/bugs/1915191

Title:
  ping utility displays wrong IPv4 address upon receiving ICMP Redirect

Status in iputils package in Ubuntu:
  New

Bug description:
  * Observed behaviour *
  We ping a host, say 137.226.39.170. While doing so, the router redirects us 
to 137.226.42.42. (We verify, with Wireshark and taking a close look at RFC 
792, that our redirect packet is formatted correctly on-wire.) We see the 
following output of the ping utility:

  64 bytes from 137.226.39.170: icmp_seq=46 ttl=251 time=0.619 ms
  64 bytes from 137.226.39.170: icmp_seq=47 ttl=251 time=0.676 ms
  64 bytes from 137.226.39.170: icmp_seq=48 ttl=251 time=1.92 ms
  From 134.130.3.3 icmp_seq=47 Redirect Host(New nexthop: 42.42.226.137)
  64 bytes from 137.226.39.170: icmp_seq=49 ttl=251 time=4.79 ms

  The gateway address, as RFC 792 calls it, is displayed the wrong way
  around. Feels like an Endianness bug right from the start.

  
  * Expected behaviour *
  ping utility should display the gateway address 

[Touch-packages] [Bug 1861358] Re: tracker search hangs and never returns results

[Christoph Gohle]

I have to correct myself. Using selective upgrades the correct upgrade
command is

$ sudo apt upgrade libtracker-miner-2.0-0/focal-proposed libtracker-
control-2.0-0/focal-proposed libtracker-sparql-2.0-0/focal-proposed
tracker/focal-proposed

in this case tracker installs correctly and seems to work.

Cheers,
Christoph

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

Title:
  tracker search hangs and never returns results

Status in tracker package in Ubuntu:
  Fix Released
Status in tracker source package in Focal:
  Fix Committed

Bug description:
  * Impact
  the tracker search utility isn't working

  * Test case
  $ tracker search something

  it should return results if there are any matching items

  * regression potential
  it's a build flag change, just check that the tracker search works including 
in the desktop and nautilus

  --

  When I run

  $ tracker search -f Bruni

  I see the following output on console
  -
  (tracker search:2): GLib-GObject-WARNING **: 00:31:10.761: cannot 
register existing type 'TrackerLanguage'

  (tracker search:2): GLib-GObject-WARNING **: 00:31:10.761: cannot
  add private field to invalid (non-instantiatable) type ''

  (tracker search:2): GLib-CRITICAL **: 00:31:10.761:
  g_once_init_leave: assertion 'result != 0' failed

  (tracker search:2): GLib-GObject-CRITICAL **: 00:31:10.761: 
g_object_new_valist: assertion 'G_TYPE_IS_OBJECT (object_type)' failed
  -

  The program hangs and never returns. Sending Control-C brings me back
  to prompt

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: tracker 2.3.0-1
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Thu Jan 30 00:31:59 2020
  ExecutablePath: /usr/bin/tracker
  InstallationDate: Installed on 2016-11-05 (1180 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: tracker
  UpgradeStatus: Upgraded to eoan on 2020-01-21 (8 days ago)

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

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

[Touch-packages] [Bug 1861358] Re: tracker search hangs and never returns results

[Christoph Gohle]

I have teste the package from focal proposed.

I confirm that searches work with the updated package. However, tracker-
miner-fs and tracker-extract get removed when installing because of the
update to libtracker-control and libtracker-sparql. This should be fixed
before backporting.

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

Title:
  tracker search hangs and never returns results

Status in tracker package in Ubuntu:
  Fix Released
Status in tracker source package in Focal:
  Fix Committed

Bug description:
  * Impact
  the tracker search utility isn't working

  * Test case
  $ tracker search something

  it should return results if there are any matching items

  * regression potential
  it's a build flag change, just check that the tracker search works including 
in the desktop and nautilus

  --

  When I run

  $ tracker search -f Bruni

  I see the following output on console
  -
  (tracker search:2): GLib-GObject-WARNING **: 00:31:10.761: cannot 
register existing type 'TrackerLanguage'

  (tracker search:2): GLib-GObject-WARNING **: 00:31:10.761: cannot
  add private field to invalid (non-instantiatable) type ''

  (tracker search:2): GLib-CRITICAL **: 00:31:10.761:
  g_once_init_leave: assertion 'result != 0' failed

  (tracker search:2): GLib-GObject-CRITICAL **: 00:31:10.761: 
g_object_new_valist: assertion 'G_TYPE_IS_OBJECT (object_type)' failed
  -

  The program hangs and never returns. Sending Control-C brings me back
  to prompt

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: tracker 2.3.0-1
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Thu Jan 30 00:31:59 2020
  ExecutablePath: /usr/bin/tracker
  InstallationDate: Installed on 2016-11-05 (1180 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: tracker
  UpgradeStatus: Upgraded to eoan on 2020-01-21 (8 days ago)

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

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

[Touch-packages] [Bug 1888041] Re: default output is ignored and reset after reboot

[Christoph]

I am also affected. I have a monitor with audio output via HDMI/DP
connected to my Ubuntu 20.04 system. After reboot, default sink is set
back to other (USB audio) device automatically. Have to manually switch
it back to the HDMI/DP device in the settings manually. Editing
/etc/pulse/default.pa in any way (even the proposed one by vanvugt) has
no effect/is ignored at restart.

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

Title:
  default output is ignored and reset after reboot

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I have lots of possible outputs, like speakers, wireless headset, and
  HDMI output. I select speakers as default, but on reboot it always
  select the wireless headset.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.3
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 18 01:59:22 2020
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/17/2020
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 7803
  dmi.board.asset.tag: Default string
  dmi.board.name: CROSSHAIR VI HERO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr7803:bd06/17/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnCROSSHAIRVIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Touch-packages] [Bug 1874661] Re: networkd sometimes doesn't set mtu received by dhcp

[Christoph Ziebuhr]

Tried with image ubuntu-minimal-2004-focal-v20200501 (systemd
245.4-4ubuntu3). No issues seen. I will then upgrade our project to
Focal, which also has LTS.

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

Title:
  networkd sometimes doesn't set mtu received by dhcp

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Eoan:
  New
Status in systemd source package in Focal:
  In Progress

Bug description:
  I'm running ubuntu-minimal-1910-eoan on google compute engine with systemd 
242-7ubuntu3.7.
  GCE has mtu 1460, set by dhcp. After having networking issues, I figured out 
that the mtu on the interface was sometimes incorrectly set to 1500.
  I manually changed it to 1420 to have a working system again and enabled 
debugging for systemd-networkd.

  Log (filtered for ens4, some columns removed for better readability):
  09:51:00 ens4: New device has no master, continuing without
  09:51:00 ens4: Flags change: +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST
  09:51:00 ens4: Link 2 added
  09:51:00 ens4: udev initialized link
  09:51:00 ens4: Saved original MTU: 1420
  09:51:00 ens4: Adding address: fe80::4001:aff:fea4:2/64 (valid forever)
  09:51:00 ens4: Gained IPv6LL
  09:51:00 ens4: Adding address: 10.164.0.2/32 (valid for 15h 15s)
  09:51:00 ens4: Adding route: dst: ff00::/8, src: n/a, gw: n/a, prefsrc: n/a
  09:51:00 ens4: Adding route: dst: fe80::4001:aff:fea4:2/128, src: n/a, gw: 
n/a, prefsrc: n/a
  09:51:00 ens4: Adding route: dst: fe80::/64, src: n/a, gw: n/a, prefsrc: n/a
  09:51:00 ens4: Adding route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 
10.164.0.2
  09:51:00 ens4: Adding route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 
10.164.0.2
  09:51:00 ens4: Adding route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 
10.164.0.2
  09:51:00 ens4: Link state is up-to-date
  09:51:00 ens4: found matching network 
'/run/systemd/network/10-netplan-ens4.network'
  09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/proxy_ndp' to '0'
  09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/use_tempaddr' to '0'
  09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/accept_ra' to '0'
  09:51:00 ens4: Started LLDP.
  09:51:00 ens4: Setting address genmode for link
  09:51:00 ens4: Setting address genmode done.
  09:51:00 ens4: Removing address 10.164.0.2
  09:51:00 ens4: Acquiring DHCPv4 lease
  09:51:00 ens4: Discovering IPv6 routers
  09:51:00 ens4: Removing address: 10.164.0.2/32 (valid for 15h 15s)
  09:51:00 ens4: Removing route: dst: 10.164.0.2/32, src: n/a, gw: n/a, 
prefsrc: 10.164.0.2
  09:51:00 ens4: DHCPv4 address 10.164.0.2/32 via 10.164.0.1
  09:51:00 ens4: Setting MTU: 1460
  09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/disable_ipv6' to '0'
  09:51:00 ens4: IPv6 successfully enabled
  09:51:00 ens4: Setting MTU done.
  09:51:00 ens4: Updating address: 10.164.0.2/32 (valid for 1d)
  09:51:00 ens4: Adding route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 
10.164.0.2
  09:51:00 ens4: Configuring route: dst: 10.164.0.1/32, src: n/a, gw: n/a, 
prefsrc: 10.164.0.2
  09:51:00 ens4: Configuring route: dst: n/a, src: n/a, gw: 10.164.0.1, 
prefsrc: 10.164.0.2
  09:51:00 ens4: Updating route: dst: 10.164.0.1/32, src: n/a, gw: n/a, 
prefsrc: 10.164.0.2
  09:51:00 ens4: Updating route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 
10.164.0.2
  09:51:00 ens4: Configured
  21:50:59 ens4: DHCP lease lost
  21:50:59 ens4: Removing address 10.164.0.2
  21:50:59 ens4: Setting MTU: 1420
  21:50:59 Setting '/proc/sys/net/ipv6/conf/ens4/disable_ipv6' to '0'
  21:50:59 ens4: IPv6 successfully enabled
  21:50:59 ens4: DHCPv4 address 10.164.0.2/32 via 10.164.0.1
  21:50:59 ens4: Removing route: dst: 10.164.0.1/32, src: n/a, gw: n/a, 
prefsrc: 10.164.0.2
  21:50:59 ens4: Removing route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 
10.164.0.2
  21:50:59 ens4: Removing address: 10.164.0.2/32 (valid for 12h 1s)
  21:50:59 ens4: Removing route: dst: 10.164.0.2/32, src: n/a, gw: n/a, 
prefsrc: 10.164.0.2
  21:50:59 ens4: Setting MTU done.
  21:50:59 ens4: Adding address: 10.164.0.2/32 (valid for 1d)
  21:50:59 ens4: Adding route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 
10.164.0.2
  21:50:59 ens4: Configuring route: dst: 10.164.0.1/32, src: n/a, gw: n/a, 
prefsrc: 10.164.0.2
  21:50:59 ens4: Configuring route: dst: n/a, src: n/a, gw: 10.164.0.1, 
prefsrc: 10.164.0.2
  21:50:59 ens4: Updating route: dst: 10.164.0.1/32, src: n/a, gw: n/a, 
prefsrc: 10.164.0.2
  21:50:59 ens4: Updating route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 
10.164.0.2
  21:50:59 ens4: Configured

  On dhcp renew (09:51:00), mtu got properly changed to 1460.
  On next dhcp renew (21:50:59) it got changed back to previous value 1420.
  In all cases, /run/systemd/netif/leases/2 correctly contained MTU=1460.

  There have been some changes to mtu handling in the past, I assume
  

[Touch-packages] [Bug 1874661] Re: networkd sometimes doesn't set mtu received by dhcp

[Christoph Ziebuhr]

245.5-2upstream202005091618~ubuntu19.10.1 from your ppa seems to be fine:
May 11 18:32:54 ct-prod systemd-networkd[435]: DHCP CLIENT (0x8c68da26): 
REQUEST (renewing)
May 11 18:32:54 ct-prod systemd-networkd[435]: DHCP CLIENT (0x8c68da26): ACK
May 11 18:32:54 ct-prod systemd-networkd[435]: DHCP CLIENT (0x8c68da26): lease 
expires in 23h 59min 57s
May 11 18:32:54 ct-prod systemd-networkd[435]: DHCP CLIENT (0x8c68da26): T2 
expires in 20h 59min 57s
May 11 18:32:54 ct-prod systemd-networkd[435]: DHCP CLIENT (0x8c68da26): T1 
expires in 11h 59min 59s
May 11 18:32:54 ct-prod systemd-networkd[435]: ens4: Remembering updated 
address: 10.164.0.2/32 (valid for 1d)
May 11 18:32:54 ct-prod systemd-networkd[435]: ens4: Configuring route: dst: 
10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2, scope: link, table: 
main, proto: dhcp, type: unicast
May 11 18:32:54 ct-prod systemd-networkd[435]: ens4: Configuring route: dst: 
n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2, scope: global, table: main, 
proto: dhcp, type: unicast
May 12 06:32:53 ct-prod systemd-networkd[435]: DHCP CLIENT (0x8c68da26): 
REQUEST (renewing)
May 12 06:32:53 ct-prod systemd-networkd[435]: DHCP CLIENT (0x8c68da26): ACK
May 12 06:32:53 ct-prod systemd-networkd[435]: DHCP CLIENT (0x8c68da26): lease 
expires in 23h 59min 57s
May 12 06:32:53 ct-prod systemd-networkd[435]: DHCP CLIENT (0x8c68da26): T2 
expires in 20h 59min 58s
May 12 06:32:53 ct-prod systemd-networkd[435]: DHCP CLIENT (0x8c68da26): T1 
expires in 11h 59min 59s
May 12 06:32:53 ct-prod systemd-networkd[435]: ens4: Remembering updated 
address: 10.164.0.2/32 (valid for 1d)
May 12 06:32:53 ct-prod systemd-networkd[435]: ens4: Configuring route: dst: 
10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 10.164.0.2, scope: link, table: 
main, proto: dhcp, type: unicast
May 12 06:32:53 ct-prod systemd-networkd[435]: ens4: Configuring route: dst: 
n/a, src: n/a, gw: 10.164.0.1, prefsrc: 10.164.0.2, scope: global, table: main, 
proto: dhcp, type: unicast

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

Title:
  networkd sometimes doesn't set mtu received by dhcp

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I'm running ubuntu-minimal-1910-eoan on google compute engine with systemd 
242-7ubuntu3.7.
  GCE has mtu 1460, set by dhcp. After having networking issues, I figured out 
that the mtu on the interface was sometimes incorrectly set to 1500.
  I manually changed it to 1420 to have a working system again and enabled 
debugging for systemd-networkd.

  Log (filtered for ens4, some columns removed for better readability):
  09:51:00 ens4: New device has no master, continuing without
  09:51:00 ens4: Flags change: +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST
  09:51:00 ens4: Link 2 added
  09:51:00 ens4: udev initialized link
  09:51:00 ens4: Saved original MTU: 1420
  09:51:00 ens4: Adding address: fe80::4001:aff:fea4:2/64 (valid forever)
  09:51:00 ens4: Gained IPv6LL
  09:51:00 ens4: Adding address: 10.164.0.2/32 (valid for 15h 15s)
  09:51:00 ens4: Adding route: dst: ff00::/8, src: n/a, gw: n/a, prefsrc: n/a
  09:51:00 ens4: Adding route: dst: fe80::4001:aff:fea4:2/128, src: n/a, gw: 
n/a, prefsrc: n/a
  09:51:00 ens4: Adding route: dst: fe80::/64, src: n/a, gw: n/a, prefsrc: n/a
  09:51:00 ens4: Adding route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 
10.164.0.2
  09:51:00 ens4: Adding route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 
10.164.0.2
  09:51:00 ens4: Adding route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 
10.164.0.2
  09:51:00 ens4: Link state is up-to-date
  09:51:00 ens4: found matching network 
'/run/systemd/network/10-netplan-ens4.network'
  09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/proxy_ndp' to '0'
  09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/use_tempaddr' to '0'
  09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/accept_ra' to '0'
  09:51:00 ens4: Started LLDP.
  09:51:00 ens4: Setting address genmode for link
  09:51:00 ens4: Setting address genmode done.
  09:51:00 ens4: Removing address 10.164.0.2
  09:51:00 ens4: Acquiring DHCPv4 lease
  09:51:00 ens4: Discovering IPv6 routers
  09:51:00 ens4: Removing address: 10.164.0.2/32 (valid for 15h 15s)
  09:51:00 ens4: Removing route: dst: 10.164.0.2/32, src: n/a, gw: n/a, 
prefsrc: 10.164.0.2
  09:51:00 ens4: DHCPv4 address 10.164.0.2/32 via 10.164.0.1
  09:51:00 ens4: Setting MTU: 1460
  09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/disable_ipv6' to '0'
  09:51:00 ens4: IPv6 successfully enabled
  09:51:00 ens4: Setting MTU done.
  09:51:00 ens4: Updating address: 10.164.0.2/32 (valid for 1d)
  09:51:00 ens4: Adding route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 
10.164.0.2
  09:51:00 ens4: Configuring route: dst: 10.164.0.1/32, src: n/a, gw: n/a, 
prefsrc: 10.164.0.2
  09:51:00 ens4: Configuring route: dst: n/a, src: n/a, gw: 10.164.0.1, 

[Touch-packages] [Bug 1874661] Re: networkd sometimes doesn't set mtu received by dhcp

[Christoph Ziebuhr]

Do you have any suggestion on what to look at?
Systemd only tracks bugs for the two most recently released versions (which 
should be 245 and 244) and I don't have the ressources to test those.

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

Title:
  networkd sometimes doesn't set mtu received by dhcp

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I'm running ubuntu-minimal-1910-eoan on google compute engine with systemd 
242-7ubuntu3.7.
  GCE has mtu 1460, set by dhcp. After having networking issues, I figured out 
that the mtu on the interface was sometimes incorrectly set to 1500.
  I manually changed it to 1420 to have a working system again and enabled 
debugging for systemd-networkd.

  Log (filtered for ens4, some columns removed for better readability):
  09:51:00 ens4: New device has no master, continuing without
  09:51:00 ens4: Flags change: +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST
  09:51:00 ens4: Link 2 added
  09:51:00 ens4: udev initialized link
  09:51:00 ens4: Saved original MTU: 1420
  09:51:00 ens4: Adding address: fe80::4001:aff:fea4:2/64 (valid forever)
  09:51:00 ens4: Gained IPv6LL
  09:51:00 ens4: Adding address: 10.164.0.2/32 (valid for 15h 15s)
  09:51:00 ens4: Adding route: dst: ff00::/8, src: n/a, gw: n/a, prefsrc: n/a
  09:51:00 ens4: Adding route: dst: fe80::4001:aff:fea4:2/128, src: n/a, gw: 
n/a, prefsrc: n/a
  09:51:00 ens4: Adding route: dst: fe80::/64, src: n/a, gw: n/a, prefsrc: n/a
  09:51:00 ens4: Adding route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 
10.164.0.2
  09:51:00 ens4: Adding route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 
10.164.0.2
  09:51:00 ens4: Adding route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 
10.164.0.2
  09:51:00 ens4: Link state is up-to-date
  09:51:00 ens4: found matching network 
'/run/systemd/network/10-netplan-ens4.network'
  09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/proxy_ndp' to '0'
  09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/use_tempaddr' to '0'
  09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/accept_ra' to '0'
  09:51:00 ens4: Started LLDP.
  09:51:00 ens4: Setting address genmode for link
  09:51:00 ens4: Setting address genmode done.
  09:51:00 ens4: Removing address 10.164.0.2
  09:51:00 ens4: Acquiring DHCPv4 lease
  09:51:00 ens4: Discovering IPv6 routers
  09:51:00 ens4: Removing address: 10.164.0.2/32 (valid for 15h 15s)
  09:51:00 ens4: Removing route: dst: 10.164.0.2/32, src: n/a, gw: n/a, 
prefsrc: 10.164.0.2
  09:51:00 ens4: DHCPv4 address 10.164.0.2/32 via 10.164.0.1
  09:51:00 ens4: Setting MTU: 1460
  09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/disable_ipv6' to '0'
  09:51:00 ens4: IPv6 successfully enabled
  09:51:00 ens4: Setting MTU done.
  09:51:00 ens4: Updating address: 10.164.0.2/32 (valid for 1d)
  09:51:00 ens4: Adding route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 
10.164.0.2
  09:51:00 ens4: Configuring route: dst: 10.164.0.1/32, src: n/a, gw: n/a, 
prefsrc: 10.164.0.2
  09:51:00 ens4: Configuring route: dst: n/a, src: n/a, gw: 10.164.0.1, 
prefsrc: 10.164.0.2
  09:51:00 ens4: Updating route: dst: 10.164.0.1/32, src: n/a, gw: n/a, 
prefsrc: 10.164.0.2
  09:51:00 ens4: Updating route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 
10.164.0.2
  09:51:00 ens4: Configured
  21:50:59 ens4: DHCP lease lost
  21:50:59 ens4: Removing address 10.164.0.2
  21:50:59 ens4: Setting MTU: 1420
  21:50:59 Setting '/proc/sys/net/ipv6/conf/ens4/disable_ipv6' to '0'
  21:50:59 ens4: IPv6 successfully enabled
  21:50:59 ens4: DHCPv4 address 10.164.0.2/32 via 10.164.0.1
  21:50:59 ens4: Removing route: dst: 10.164.0.1/32, src: n/a, gw: n/a, 
prefsrc: 10.164.0.2
  21:50:59 ens4: Removing route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 
10.164.0.2
  21:50:59 ens4: Removing address: 10.164.0.2/32 (valid for 12h 1s)
  21:50:59 ens4: Removing route: dst: 10.164.0.2/32, src: n/a, gw: n/a, 
prefsrc: 10.164.0.2
  21:50:59 ens4: Setting MTU done.
  21:50:59 ens4: Adding address: 10.164.0.2/32 (valid for 1d)
  21:50:59 ens4: Adding route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 
10.164.0.2
  21:50:59 ens4: Configuring route: dst: 10.164.0.1/32, src: n/a, gw: n/a, 
prefsrc: 10.164.0.2
  21:50:59 ens4: Configuring route: dst: n/a, src: n/a, gw: 10.164.0.1, 
prefsrc: 10.164.0.2
  21:50:59 ens4: Updating route: dst: 10.164.0.1/32, src: n/a, gw: n/a, 
prefsrc: 10.164.0.2
  21:50:59 ens4: Updating route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 
10.164.0.2
  21:50:59 ens4: Configured

  On dhcp renew (09:51:00), mtu got properly changed to 1460.
  On next dhcp renew (21:50:59) it got changed back to previous value 1420.
  In all cases, /run/systemd/netif/leases/2 correctly contained MTU=1460.

  There have been some changes to mtu handling in the past, I assume
  this is a regression, potentially from
  

[Touch-packages] [Bug 1874661] Re: networkd sometimes doesn't set mtu received by dhcp

[Christoph Ziebuhr]

After the weekend, I observed that the original MTU gets set on every second 
renew:
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: ens4: Saved original MTU: 1420
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: ens4: Setting MTU: 1460
Apr 23 21:50:59 ct-prod systemd-networkd[1737]: ens4: Setting MTU: 1420
Apr 24 09:50:59 ct-prod systemd-networkd[1737]: ens4: Setting MTU: 1460
Apr 24 21:50:58 ct-prod systemd-networkd[1737]: ens4: Setting MTU: 1420
Apr 25 09:50:59 ct-prod systemd-networkd[1737]: ens4: Setting MTU: 1460
Apr 25 21:50:59 ct-prod systemd-networkd[1737]: ens4: Setting MTU: 1420
Apr 26 09:51:00 ct-prod systemd-networkd[1737]: ens4: Setting MTU: 1460
Apr 26 21:50:59 ct-prod systemd-networkd[1737]: ens4: Setting MTU: 1420

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

Title:
  networkd sometimes doesn't set mtu received by dhcp

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I'm running ubuntu-minimal-1910-eoan on google compute engine with systemd 
242-7ubuntu3.7.
  GCE has mtu 1460, set by dhcp. After having networking issues, I figured out 
that the mtu on the interface was sometimes incorrectly set to 1500.
  I manually changed it to 1420 to have a working system again and enabled 
debugging for systemd-networkd.

  Log (filtered for ens4, some columns removed for better readability):
  09:51:00 ens4: New device has no master, continuing without
  09:51:00 ens4: Flags change: +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST
  09:51:00 ens4: Link 2 added
  09:51:00 ens4: udev initialized link
  09:51:00 ens4: Saved original MTU: 1420
  09:51:00 ens4: Adding address: fe80::4001:aff:fea4:2/64 (valid forever)
  09:51:00 ens4: Gained IPv6LL
  09:51:00 ens4: Adding address: 10.164.0.2/32 (valid for 15h 15s)
  09:51:00 ens4: Adding route: dst: ff00::/8, src: n/a, gw: n/a, prefsrc: n/a
  09:51:00 ens4: Adding route: dst: fe80::4001:aff:fea4:2/128, src: n/a, gw: 
n/a, prefsrc: n/a
  09:51:00 ens4: Adding route: dst: fe80::/64, src: n/a, gw: n/a, prefsrc: n/a
  09:51:00 ens4: Adding route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 
10.164.0.2
  09:51:00 ens4: Adding route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 
10.164.0.2
  09:51:00 ens4: Adding route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 
10.164.0.2
  09:51:00 ens4: Link state is up-to-date
  09:51:00 ens4: found matching network 
'/run/systemd/network/10-netplan-ens4.network'
  09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/proxy_ndp' to '0'
  09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/use_tempaddr' to '0'
  09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/accept_ra' to '0'
  09:51:00 ens4: Started LLDP.
  09:51:00 ens4: Setting address genmode for link
  09:51:00 ens4: Setting address genmode done.
  09:51:00 ens4: Removing address 10.164.0.2
  09:51:00 ens4: Acquiring DHCPv4 lease
  09:51:00 ens4: Discovering IPv6 routers
  09:51:00 ens4: Removing address: 10.164.0.2/32 (valid for 15h 15s)
  09:51:00 ens4: Removing route: dst: 10.164.0.2/32, src: n/a, gw: n/a, 
prefsrc: 10.164.0.2
  09:51:00 ens4: DHCPv4 address 10.164.0.2/32 via 10.164.0.1
  09:51:00 ens4: Setting MTU: 1460
  09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/disable_ipv6' to '0'
  09:51:00 ens4: IPv6 successfully enabled
  09:51:00 ens4: Setting MTU done.
  09:51:00 ens4: Updating address: 10.164.0.2/32 (valid for 1d)
  09:51:00 ens4: Adding route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 
10.164.0.2
  09:51:00 ens4: Configuring route: dst: 10.164.0.1/32, src: n/a, gw: n/a, 
prefsrc: 10.164.0.2
  09:51:00 ens4: Configuring route: dst: n/a, src: n/a, gw: 10.164.0.1, 
prefsrc: 10.164.0.2
  09:51:00 ens4: Updating route: dst: 10.164.0.1/32, src: n/a, gw: n/a, 
prefsrc: 10.164.0.2
  09:51:00 ens4: Updating route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 
10.164.0.2
  09:51:00 ens4: Configured
  21:50:59 ens4: DHCP lease lost
  21:50:59 ens4: Removing address 10.164.0.2
  21:50:59 ens4: Setting MTU: 1420
  21:50:59 Setting '/proc/sys/net/ipv6/conf/ens4/disable_ipv6' to '0'
  21:50:59 ens4: IPv6 successfully enabled
  21:50:59 ens4: DHCPv4 address 10.164.0.2/32 via 10.164.0.1
  21:50:59 ens4: Removing route: dst: 10.164.0.1/32, src: n/a, gw: n/a, 
prefsrc: 10.164.0.2
  21:50:59 ens4: Removing route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 
10.164.0.2
  21:50:59 ens4: Removing address: 10.164.0.2/32 (valid for 12h 1s)
  21:50:59 ens4: Removing route: dst: 10.164.0.2/32, src: n/a, gw: n/a, 
prefsrc: 10.164.0.2
  21:50:59 ens4: Setting MTU done.
  21:50:59 ens4: Adding address: 10.164.0.2/32 (valid for 1d)
  21:50:59 ens4: Adding route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 
10.164.0.2
  21:50:59 ens4: Configuring route: dst: 10.164.0.1/32, src: n/a, gw: n/a, 
prefsrc: 10.164.0.2
  21:50:59 ens4: Configuring route: dst: n/a, src: n/a, gw: 10.164.0.1, 
prefsrc: 10.164.0.2
  21:50:59 ens4: 

[Touch-packages] [Bug 1874661] Re: networkd sometimes doesn't set mtu received by dhcp

[Christoph Ziebuhr]

This is the full log:
Apr 23 09:51:00 ct-prod systemd[1]: Stopping Network Service...
Apr 23 09:51:00 ct-prod systemd[1]: systemd-networkd.service: Succeeded.
Apr 23 09:51:00 ct-prod systemd[1]: Stopped Network Service.
Apr 23 09:51:00 ct-prod systemd[1]: Starting Network Service...
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: Bus bus-api-network: changing 
state UNSET → OPENING
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: Bus bus-api-network: changing 
state OPENING → AUTHENTICATING
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: timestamp of 
'/etc/systemd/network' changed
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: timestamp of 
'/run/systemd/network' changed
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: No virtualization found in DMI
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: Virtualization found, 
CPUID=KVMKVMKVM
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: Found VM virtualization kvm
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: 
/usr/lib/systemd/network/80-container-host0.network: Conditions in the file do 
not match the system environment, skipping.
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth16c9a69: Flags change: +UP 
+LOWER_UP +RUNNING +MULTICAST +BROADCAST
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth16c9a69: Link 18378 added
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth16c9a69: udev initialized 
link
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth16c9a69: Saved original 
MTU: 1500
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth3db5561: Flags change: +UP 
+LOWER_UP +RUNNING +MULTICAST +BROADCAST
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth3db5561: Link 18376 added
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth3db5561: udev initialized 
link
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth3db5561: Saved original 
MTU: 1500
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth0942758: Flags change: +UP 
+LOWER_UP +RUNNING +MULTICAST +BROADCAST
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth0942758: Link 18374 added
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth0942758: udev initialized 
link
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth0942758: Saved original 
MTU: 1500
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: br-67c4527c2602: New device has 
no master, continuing without
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: br-67c4527c2602: Flags change: 
+UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: br-67c4527c2602: Link 18372 
added
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: br-67c4527c2602: udev 
initialized link
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: br-67c4527c2602: Saved original 
MTU: 1500
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: docker0: New device has no 
master, continuing without
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: docker0: Flags change: +UP 
+MULTICAST +BROADCAST
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: docker0: Link 3 added
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: docker0: udev initialized link
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: docker0: Saved original MTU: 
1500
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: ens4: New device has no master, 
continuing without
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: ens4: Flags change: +UP 
+LOWER_UP +RUNNING +MULTICAST +BROADCAST
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: ens4: Link 2 added
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: ens4: udev initialized link
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: ens4: Saved original MTU: 1420
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: lo: New device has no master, 
continuing without
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: lo: Flags change: +LOOPBACK +UP 
+LOWER_UP +RUNNING
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: lo: Link 1 added
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: lo: udev initialized link
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: lo: Saved original MTU: 65536
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth16c9a69: Adding address: 
fe80::c0e2:b6ff:fec5:c370/64 (valid forever)
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth16c9a69: Gained IPv6LL
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth3db5561: Adding address: 
fe80::bc1c:baff:fedf:f0ef/64 (valid forever)
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth3db5561: Gained IPv6LL
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth0942758: Adding address: 
fe80::d84f:edff:fe33:55a0/64 (valid forever)
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: veth0942758: Gained IPv6LL
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: br-67c4527c2602: Adding 
address: fe80::42:45ff:fed1:a3c2/64 (valid forever)
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: br-67c4527c2602: Gained IPv6LL
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: ens4: Adding address: 
fe80::4001:aff:fea4:2/64 (valid forever)
Apr 23 09:51:00 ct-prod systemd-networkd[1737]: ens4: Gained IPv6LL
Apr 23 09:51:00 ct-prod 

[Touch-packages] [Bug 1874661] [NEW] networkd sometimes doesn't set mtu received by dhcp

[Christoph Ziebuhr]

Public bug reported:

I'm running ubuntu-minimal-1910-eoan on google compute engine with systemd 
242-7ubuntu3.7.
GCE has mtu 1460, set by dhcp. After having networking issues, I figured out 
that the mtu on the interface was sometimes incorrectly set to 1500.
I manually changed it to 1420 to have a working system again and enabled 
debugging for systemd-networkd.

Log (filtered for ens4, some columns removed for better readability):
09:51:00 ens4: New device has no master, continuing without
09:51:00 ens4: Flags change: +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST
09:51:00 ens4: Link 2 added
09:51:00 ens4: udev initialized link
09:51:00 ens4: Saved original MTU: 1420
09:51:00 ens4: Adding address: fe80::4001:aff:fea4:2/64 (valid forever)
09:51:00 ens4: Gained IPv6LL
09:51:00 ens4: Adding address: 10.164.0.2/32 (valid for 15h 15s)
09:51:00 ens4: Adding route: dst: ff00::/8, src: n/a, gw: n/a, prefsrc: n/a
09:51:00 ens4: Adding route: dst: fe80::4001:aff:fea4:2/128, src: n/a, gw: n/a, 
prefsrc: n/a
09:51:00 ens4: Adding route: dst: fe80::/64, src: n/a, gw: n/a, prefsrc: n/a
09:51:00 ens4: Adding route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 
10.164.0.2
09:51:00 ens4: Adding route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 
10.164.0.2
09:51:00 ens4: Adding route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 
10.164.0.2
09:51:00 ens4: Link state is up-to-date
09:51:00 ens4: found matching network 
'/run/systemd/network/10-netplan-ens4.network'
09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/proxy_ndp' to '0'
09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/use_tempaddr' to '0'
09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/accept_ra' to '0'
09:51:00 ens4: Started LLDP.
09:51:00 ens4: Setting address genmode for link
09:51:00 ens4: Setting address genmode done.
09:51:00 ens4: Removing address 10.164.0.2
09:51:00 ens4: Acquiring DHCPv4 lease
09:51:00 ens4: Discovering IPv6 routers
09:51:00 ens4: Removing address: 10.164.0.2/32 (valid for 15h 15s)
09:51:00 ens4: Removing route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 
10.164.0.2
09:51:00 ens4: DHCPv4 address 10.164.0.2/32 via 10.164.0.1
09:51:00 ens4: Setting MTU: 1460
09:51:00 Setting '/proc/sys/net/ipv6/conf/ens4/disable_ipv6' to '0'
09:51:00 ens4: IPv6 successfully enabled
09:51:00 ens4: Setting MTU done.
09:51:00 ens4: Updating address: 10.164.0.2/32 (valid for 1d)
09:51:00 ens4: Adding route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 
10.164.0.2
09:51:00 ens4: Configuring route: dst: 10.164.0.1/32, src: n/a, gw: n/a, 
prefsrc: 10.164.0.2
09:51:00 ens4: Configuring route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 
10.164.0.2
09:51:00 ens4: Updating route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 
10.164.0.2
09:51:00 ens4: Updating route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 
10.164.0.2
09:51:00 ens4: Configured
21:50:59 ens4: DHCP lease lost
21:50:59 ens4: Removing address 10.164.0.2
21:50:59 ens4: Setting MTU: 1420
21:50:59 Setting '/proc/sys/net/ipv6/conf/ens4/disable_ipv6' to '0'
21:50:59 ens4: IPv6 successfully enabled
21:50:59 ens4: DHCPv4 address 10.164.0.2/32 via 10.164.0.1
21:50:59 ens4: Removing route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 
10.164.0.2
21:50:59 ens4: Removing route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 
10.164.0.2
21:50:59 ens4: Removing address: 10.164.0.2/32 (valid for 12h 1s)
21:50:59 ens4: Removing route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 
10.164.0.2
21:50:59 ens4: Setting MTU done.
21:50:59 ens4: Adding address: 10.164.0.2/32 (valid for 1d)
21:50:59 ens4: Adding route: dst: 10.164.0.2/32, src: n/a, gw: n/a, prefsrc: 
10.164.0.2
21:50:59 ens4: Configuring route: dst: 10.164.0.1/32, src: n/a, gw: n/a, 
prefsrc: 10.164.0.2
21:50:59 ens4: Configuring route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 
10.164.0.2
21:50:59 ens4: Updating route: dst: 10.164.0.1/32, src: n/a, gw: n/a, prefsrc: 
10.164.0.2
21:50:59 ens4: Updating route: dst: n/a, src: n/a, gw: 10.164.0.1, prefsrc: 
10.164.0.2
21:50:59 ens4: Configured

On dhcp renew (09:51:00), mtu got properly changed to 1460.
On next dhcp renew (21:50:59) it got changed back to previous value 1420.
In all cases, /run/systemd/netif/leases/2 correctly contained MTU=1460.

There have been some changes to mtu handling in the past, I assume this
is a regression, potentially from
https://github.com/systemd/systemd/issues/12552 or
https://github.com/systemd/systemd/issues/6593.

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

** Description changed:

  I'm running ubuntu-minimal-1910-eoan on google compute engine with systemd 
242-7ubuntu3.7.
  GCE has mtu 1460, set by dhcp. After having networking issues, I figured out 
that the mtu on the interface was sometimes incorrectly set to 1500.
  I manually changed it to 1420 to have a working system again and enabled 
debugging for systemd-networkd.
  
- Log (filtered for ens4):
- Apr 23 09:51:00 host systemd-networkd[1737]: ens4: New device 

[Touch-packages] [Bug 1866625] Re: OverflowError: With Python 3 Gtk.ListStore only accepts 32 Bit Integers.

[Christoph Reiter]

"int" maps to the same underlying type in Python 2 and Python 3. This
wasn't changed when pygobject was ported to Python 3 and can't really be
changed now. If you want be sure your numbers fit use the suggested
"GObject.TYPE_*", or just use "object" which means the Python int object
is stored as is, assuming you don't need to access it in C code
somewhere else.

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

Title:
  OverflowError: With Python 3 Gtk.ListStore only accepts 32 Bit
  Integers.

Status in pygobject package in Ubuntu:
  New

Bug description:
  import gi
  gi.require_version('Gtk', '3.0')
  from gi.repository import Gtk

  This works in Python 2:

  mystore = Gtk.ListStore(long)
  mystore.insert_with_valuesv(-1, [1], [long(1330400507426)])

  This does not work in Python 3:

  mystore = Gtk.ListStore(int)
  mystore.insert_with_valuesv(-1, [1], [int(1330400507426)])

  OverflowError: Item 0: out of range for int property

  

  lsb_release -rd
  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04

  apt-cache policy python3-gi
  python3-gi:
Installed: 3.26.1-2ubuntu1
Candidate: 3.26.1-2ubuntu1
Version table:
   *** 3.26.1-2ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.26.1-2 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  python3 -V
  Python 3.6.9

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

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

[Touch-packages] [Bug 1586528] Re: Avahi-daemon withdraws address record

[Christoph Duwald]

I had the same problem on an Raspberry Pi4 4GB.
Uninstalling the avahi-deamon wokrs just fine. Even if this may not the cause 
of the problem, my Pi is running for the last 12 days without a problem.

 avahi-daemon[350]: Withdrawing address record for 192.168.1.116 on eth0.
 avahi-daemon[350]: Leaving mDNS multicast group on interface eth0.IPv4 with 
address 192.168.1.116.
 avahi-daemon[350]: Interface eth0.IPv4 no longer relevant for mDNS.

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

Title:
  Avahi-daemon withdraws address record

Status in avahi package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  For some reason, if I leave my Ubuntu VM up for a prolonged period of
  time the machine will lose connection to the network.  ip addr shows
  that the nic port no longer has an address and an examination of the
  syslog shows this:

  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Withdrawing address record 
for 10.0.2.15 on enp0s3.
  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Leaving mDNS multicast 
group on interface enp0s3.IPv4 with address 10.0.2.15.
  May 27 14:19:38 matt-VirtualBox avahi-daemon[590]: Interface enp0s3.IPv4 no 
longer relevant for mDNS.

  
  for no known reason.

  The only reliable way to get the network to come back (that I have
  found) is a full reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri May 27 15:11:34 2016
  InstallationDate: Installed on 2015-10-22 (218 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: avahi
  UpgradeStatus: Upgraded to xenial on 2016-03-30 (58 days ago)

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

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

[Touch-packages] [Bug 1861358] Re: tracker search hangs and never returns results

[Christoph Gohle]

I also found a similar bug report here: 
https://gitlab.gnome.org/GNOME/tracker/issues/161


** Bug watch added: gitlab.gnome.org/GNOME/tracker/issues #161
   https://gitlab.gnome.org/GNOME/tracker/issues/161

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

Title:
  tracker search hangs and never returns results

Status in tracker package in Ubuntu:
  New

Bug description:
  When I run

  $ tracker search -f Bruni

  I see the following output on console
  -
  (tracker search:2): GLib-GObject-WARNING **: 00:31:10.761: cannot 
register existing type 'TrackerLanguage'

  (tracker search:2): GLib-GObject-WARNING **: 00:31:10.761: cannot
  add private field to invalid (non-instantiatable) type ''

  (tracker search:2): GLib-CRITICAL **: 00:31:10.761:
  g_once_init_leave: assertion 'result != 0' failed

  (tracker search:2): GLib-GObject-CRITICAL **: 00:31:10.761: 
g_object_new_valist: assertion 'G_TYPE_IS_OBJECT (object_type)' failed
  -

  The program hangs and never returns. Sending Control-C brings me back
  to prompt

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: tracker 2.3.0-1
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Thu Jan 30 00:31:59 2020
  ExecutablePath: /usr/bin/tracker
  InstallationDate: Installed on 2016-11-05 (1180 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: tracker
  UpgradeStatus: Upgraded to eoan on 2020-01-21 (8 days ago)

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

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

[Touch-packages] [Bug 1861358] [NEW] tracker search hangs and never returns results

[Christoph Gohle]

Public bug reported:

When I run

$ tracker search -f Bruni

I see the following output on console
-
(tracker search:2): GLib-GObject-WARNING **: 00:31:10.761: cannot register 
existing type 'TrackerLanguage'

(tracker search:2): GLib-GObject-WARNING **: 00:31:10.761: cannot
add private field to invalid (non-instantiatable) type ''

(tracker search:2): GLib-CRITICAL **: 00:31:10.761:
g_once_init_leave: assertion 'result != 0' failed

(tracker search:2): GLib-GObject-CRITICAL **: 00:31:10.761: 
g_object_new_valist: assertion 'G_TYPE_IS_OBJECT (object_type)' failed
-

The program hangs and never returns. Sending Control-C brings me back to
prompt

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: tracker 2.3.0-1
ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
Uname: Linux 5.3.0-29-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
Date: Thu Jan 30 00:31:59 2020
ExecutablePath: /usr/bin/tracker
InstallationDate: Installed on 2016-11-05 (1180 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
SourcePackage: tracker
UpgradeStatus: Upgraded to eoan on 2020-01-21 (8 days ago)

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


** Tags: amd64 apport-bug eoan

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

Title:
  tracker search hangs and never returns results

Status in tracker package in Ubuntu:
  New

Bug description:
  When I run

  $ tracker search -f Bruni

  I see the following output on console
  -
  (tracker search:2): GLib-GObject-WARNING **: 00:31:10.761: cannot 
register existing type 'TrackerLanguage'

  (tracker search:2): GLib-GObject-WARNING **: 00:31:10.761: cannot
  add private field to invalid (non-instantiatable) type ''

  (tracker search:2): GLib-CRITICAL **: 00:31:10.761:
  g_once_init_leave: assertion 'result != 0' failed

  (tracker search:2): GLib-GObject-CRITICAL **: 00:31:10.761: 
g_object_new_valist: assertion 'G_TYPE_IS_OBJECT (object_type)' failed
  -

  The program hangs and never returns. Sending Control-C brings me back
  to prompt

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: tracker 2.3.0-1
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Thu Jan 30 00:31:59 2020
  ExecutablePath: /usr/bin/tracker
  InstallationDate: Installed on 2016-11-05 (1180 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: tracker
  UpgradeStatus: Upgraded to eoan on 2020-01-21 (8 days ago)

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

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

[Touch-packages] [Bug 1819183] Re: FFe: Update pygobject to 3.32

[Christoph Reiter]

>From an pygobject upstream POV this cycle hasn't seen any high risk
changes, so +1 from me in case that helps :)

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

Title:
  FFe: Update pygobject to 3.32

Status in pygobject package in Ubuntu:
  New

Bug description:
  Feature Freeze exception request
  
  Since we're updating the rest of GNOME to 3.32 (including glib and 
gobject-introspection), it seems like it would be a good idea to update 
pygobject also.

  3.31.4-1 is in Debian experimental ready to be synced over once this
  FFe is approved. 3.32.0 is expected next week.

  https://gitlab.gnome.org/GNOME/pygobject/blob/master/NEWS
  https://gitlab.gnome.org/GNOME/pygobject/compare/3.30.4...3.31.4 (includes 
several commits that were already included in the current 3.30.4 version)

  Justification for lateness
  --
  Sorry, we've been a bit busy and this wasn't a high priority.

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

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

[Touch-packages] [Bug 1814519] [NEW] USB port runs not stable, kayboard not stable, sound dosent work

[Christoph Polk]

Public bug reported:

USB port is not stable, cant transfer data from any USB stick securely.
Kayboard kays seam to clamb, sometimes keyhits are missing. Sund card is
not working. Pulse audio uses dummy output.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: xorg 1:7.7+19ubuntu8
ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
Uname: Linux 4.18.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
CompositorRunning: None
Date: Mon Feb  4 11:06:21 2019
DistUpgraded: 2018-10-28 16:29:58,029 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: cosmic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series 
PCI Configuration Registers [8086:22b0] (rev 36) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series 
PCI Configuration Registers [17aa:38e3]
InstallationDate: Installed on 2018-07-29 (189 days ago)
InstallationMedia: Xubuntu 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 003: ID 8087:0a2a Intel Corp. 
 Bus 001 Device 006: ID 048d:8911 Integrated Technology Express, Inc. 
 Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 80XF
ProcEnviron:
 LANGUAGE=de_DE
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=1902ca40-b683-4cfc-84a3-d535330b42ae ro fbcon=rotate:1 splash 
fbcon=rotate:1 splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: Upgraded to cosmic on 2018-10-28 (98 days ago)
dmi.bios.date: 03/20/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: 5HCN37WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J91196WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 32
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo MIIX 320-10ICR
dmi.modalias: 
dmi:bvnLENOVO:bvr5HCN37WW:bd03/20/2018:svnLENOVO:pn80XF:pvrLenovoMIIX320-10ICR:rvnLENOVO:rnLNVNB161216:rvrSDK0J91196WIN:cvnLENOVO:ct32:cvrLenovoMIIX320-10ICR:
dmi.product.family: MIIX 320-10ICR
dmi.product.name: 80XF
dmi.product.sku: LENOVO_MT_80XF_BU_idea_FM_MIIX 320-10ICR
dmi.product.version: Lenovo MIIX 320-10ICR
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3
xserver.bootTime: Mon Feb  4 10:29:29 2019
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs: Output DP1 DP2 
DP3DSI1   HDMI1   HDMI2   HDMI3 
   VIRTUAL1
xserver.version: 2:1.20.1-3ubuntu2.1
xserver.video_driver: intel

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


** Tags: amd64 apport-bug cosmic ubuntu

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

Title:
  USB port runs not stable, kayboard not stable, sound dosent work

Status in xorg package in Ubuntu:
  New

Bug description:
  USB port is not stable, cant transfer data from any USB stick
  securely. Kayboard kays seam to clamb, sometimes keyhits are missing.
  Sund card is not working. Pulse audio uses dummy output.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CompositorRunning: None
  Date: Mon Feb  4 11:06:21 2019
  DistUpgraded: 2018-10-28 16:29:58,029 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series 
PCI Configuration Registers [8086:22b0] (rev 36) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Series PCI Configuration Registers [17aa:38e3]
  InstallationDate: Installed on 2018-07-29 (189 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 

[Touch-packages] [Bug 1812353] Re: content injection in http method (CVE-2019-3462)

[Christoph Anton Mitterer]

Or is there anything going to happen wrt to https/TLS?

I, personally, are not convinced of doing this...

In this specific case, and rogue mirror could have still exploited the
hole, and I'd assume there is nothing done to check the trustworthiness
of mirror operators (there's no real way to do so).

Also, the X.509 trust model is inherently broken. 150 root CAs alone in
the mozilla bundle (many of them which cannot be trusted per se by any
sane person) and even more sub CAs... all of which can issue literally
any certificate.

Using TLS would IMO only help (a tiny bit) if Debian (respectively the
derivates) would operate their own CA (and only accept that for services
they offer, like mirrors, BTS, gitlab, etc.).

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

Title:
  content injection in http method (CVE-2019-3462)

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Precise:
  Fix Released
Status in apt source package in Trusty:
  Fix Released
Status in apt source package in Xenial:
  Fix Released
Status in apt source package in Bionic:
  Fix Released
Status in apt source package in Cosmic:
  Fix Released
Status in apt source package in Disco:
  Fix Released

Bug description:
  apt, starting with version 0.8.15, decodes target URLs of redirects,
  but does not check them for newlines, allowing MiTM attackers (or
  repository mirrors) to inject arbitrary headers into the result
  returned to the main process.

  If the URL embeds hashes of the supposed file, it can thus be used to
  disable any validation of the downloaded file, as the fake hashes will
  be prepended in front of the right hashes.

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

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

[Touch-packages] [Bug 1812353] Re: content injection in http method (CVE-2019-3462)

[Christoph Anton Mitterer]

Hmm that's pretty bad then (which is not to be read as blaming you or
anyone else here).

Are there going to be any… "consequences"?

I mean trying to find out whether systems have been compromised is probably 
impossible... an attacker could have used this long ago to basically do 
everything, from silently taking over end user systems to secretly injecting 
code in development repos.
Sure one can argue that this might have been noticed - but it also might have 
been not.


But is there a chance to e.g. get full audits of apt done by security experts?

I'd assume that aptitude was also fully affected by this, right?

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

Title:
  content injection in http method (CVE-2019-3462)

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Precise:
  Fix Released
Status in apt source package in Trusty:
  Fix Released
Status in apt source package in Xenial:
  Fix Released
Status in apt source package in Bionic:
  Fix Released
Status in apt source package in Cosmic:
  Fix Released
Status in apt source package in Disco:
  Fix Released

Bug description:
  apt, starting with version 0.8.15, decodes target URLs of redirects,
  but does not check them for newlines, allowing MiTM attackers (or
  repository mirrors) to inject arbitrary headers into the result
  returned to the main process.

  If the URL embeds hashes of the supposed file, it can thus be used to
  disable any validation of the downloaded file, as the fake hashes will
  be prepended in front of the right hashes.

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

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

[Touch-packages] [Bug 1812353] Re: content injection in http method (CVE-2019-3462)

[Christoph Anton Mitterer]

Is there any more detailed evaluation of this hole?

It reads absolutely catastrophic, like that secure APT is basically
broken since 2011,… and if anyone has found that issue before (which one
must assume in the worst case) any code could have been rather easily
introduced in any Debian based system, from end users to DDs.

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

Title:
  content injection in http method (CVE-2019-3462)

Status in apt package in Ubuntu:
  In Progress
Status in apt source package in Precise:
  Fix Released
Status in apt source package in Trusty:
  Fix Released
Status in apt source package in Xenial:
  Fix Released
Status in apt source package in Bionic:
  Fix Released
Status in apt source package in Cosmic:
  Fix Released
Status in apt source package in Disco:
  In Progress

Bug description:
  apt, starting with version 0.8.15, decodes target URLs of redirects,
  but does not check them for newlines, allowing MiTM attackers (or
  repository mirrors) to inject arbitrary headers into the result
  returned to the main process.

  If the URL embeds hashes of the supposed file, it can thus be used to
  disable any validation of the downloaded file, as the fake hashes will
  be prepended in front of the right hashes.

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

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

[Touch-packages] [Bug 1787474] Re: pygobject fails to build in Ubuntu 18.10

[Christoph Reiter]

New 1.57.3 g-i tarball is out.

For the apport thing (I'm not sure if this is relevant in your build
environment):
https://gitlab.gnome.org/GNOME/pygobject/commit/d9ddad7bcac86d37a9010c8cd529a0e6ca1a9f48

PyGObject tests might still fail because of
https://gitlab.gnome.org/GNOME/glib/commit/0319dac01d64f9f95cf84c511a1679ba469e6cbb
-> needs a new glib release.

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

Title:
  pygobject fails to build in Ubuntu 18.10

Status in pygobject package in Ubuntu:
  New

Bug description:
  pygobject 3.28.2-1 and 3.29.2-1 fails to build in Ubuntu 18.10.

  pygobject 3.28.2-1 does build successfully on Ubuntu 18.04 LTS.
  3.29.2-1 does build successfully in Debian unstable.

  I confirmed that the problem is reproducible in a local sbuild. I
  confirm that the test hang also happens with python 3.7.

  By the way, I had to manually cancel the builds since they were still
  hanging after 20 hours.

  Build log
  -
  https://launchpad.net/ubuntu/+source/pygobject/3.29.2-1/+build/15263898

  Build log excerpt
  -

  I: pybuild base:217: cd /<>/.pybuild/cpython2_2.7/build; 
python2.7 -m pytest tests
  = test session starts 
==
  platform linux2 -- Python 2.7.15, pytest-3.6.4, py-1.5.4, pluggy-0.6.0
  rootdir: /<>, inifile:
  collected 1374 items

  tests/test_atoms.py ...  [  
0%]
  tests/test_cairo.py .[  
2%]
  tests/test_docstring.py ...x.[  
3%]
  tests/test_error.py ...  [  
4%]
  tests/test_everything.py Trace/breakpoint trap (core dumped)
  E: pybuild pybuild:338: test: plugin distutils failed with: exit code=133: cd 
/<>/.pybuild/cpython2_2.7/build; python2.7 -m pytest tests
  dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7 returned 
exit code 13
  make[1]: *** [debian/rules:29: override_dh_auto_test] Error 1
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:22: binary] Error 2
  dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
2
  RUN: /usr/share/launchpad-buildd/slavebin/in-target scan-for-processes 
--backend=chroot --series=cosmic --arch=amd64 PACKAGEBUILD-15263898
  Scanning for processes to kill in build PACKAGEBUILD-15263898
  Build killed with signal TERM after 150 minutes of inactivity

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

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

[Touch-packages] [Bug 1787474] Re: pygobject fails to build in Ubuntu 18.10

[Christoph Reiter]

We do test against gnome master now with gitlab-CI, so hopefully this
will be noticed earlier in future releases.

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

Title:
  pygobject fails to build in Ubuntu 18.10

Status in pygobject package in Ubuntu:
  New

Bug description:
  pygobject 3.28.2-1 and 3.29.2-1 fails to build in Ubuntu 18.10.

  pygobject 3.28.2-1 does build successfully on Ubuntu 18.04 LTS.
  3.29.2-1 does build successfully in Debian unstable.

  I confirmed that the problem is reproducible in a local sbuild. I
  confirm that the test hang also happens with python 3.7.

  By the way, I had to manually cancel the builds since they were still
  hanging after 20 hours.

  Build log
  -
  https://launchpad.net/ubuntu/+source/pygobject/3.29.2-1/+build/15263898

  Build log excerpt
  -

  I: pybuild base:217: cd /<>/.pybuild/cpython2_2.7/build; 
python2.7 -m pytest tests
  = test session starts 
==
  platform linux2 -- Python 2.7.15, pytest-3.6.4, py-1.5.4, pluggy-0.6.0
  rootdir: /<>, inifile:
  collected 1374 items

  tests/test_atoms.py ...  [  
0%]
  tests/test_cairo.py .[  
2%]
  tests/test_docstring.py ...x.[  
3%]
  tests/test_error.py ...  [  
4%]
  tests/test_everything.py Trace/breakpoint trap (core dumped)
  E: pybuild pybuild:338: test: plugin distutils failed with: exit code=133: cd 
/<>/.pybuild/cpython2_2.7/build; python2.7 -m pytest tests
  dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7 returned 
exit code 13
  make[1]: *** [debian/rules:29: override_dh_auto_test] Error 1
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:22: binary] Error 2
  dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
2
  RUN: /usr/share/launchpad-buildd/slavebin/in-target scan-for-processes 
--backend=chroot --series=cosmic --arch=amd64 PACKAGEBUILD-15263898
  Scanning for processes to kill in build PACKAGEBUILD-15263898
  Build killed with signal TERM after 150 minutes of inactivity

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

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

[Touch-packages] [Bug 1787474] Re: pygobject fails to build in Ubuntu 18.10

[Christoph Reiter]

I think this is https://gitlab.gnome.org/GNOME/gobject-
introspection/commit/1f5c81048d762f4866137e1e3221d85b9b611d8b which
isn't in a release yet. I'll ask for a release.

I also noticed that the pygobject test suite fails due to sys.excepthook
== apport_excepthook, I'll look into that.

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

Title:
  pygobject fails to build in Ubuntu 18.10

Status in pygobject package in Ubuntu:
  New

Bug description:
  pygobject 3.28.2-1 and 3.29.2-1 fails to build in Ubuntu 18.10.

  pygobject 3.28.2-1 does build successfully on Ubuntu 18.04 LTS.
  3.29.2-1 does build successfully in Debian unstable.

  I confirmed that the problem is reproducible in a local sbuild. I
  confirm that the test hang also happens with python 3.7.

  By the way, I had to manually cancel the builds since they were still
  hanging after 20 hours.

  Build log
  -
  https://launchpad.net/ubuntu/+source/pygobject/3.29.2-1/+build/15263898

  Build log excerpt
  -

  I: pybuild base:217: cd /<>/.pybuild/cpython2_2.7/build; 
python2.7 -m pytest tests
  = test session starts 
==
  platform linux2 -- Python 2.7.15, pytest-3.6.4, py-1.5.4, pluggy-0.6.0
  rootdir: /<>, inifile:
  collected 1374 items

  tests/test_atoms.py ...  [  
0%]
  tests/test_cairo.py .[  
2%]
  tests/test_docstring.py ...x.[  
3%]
  tests/test_error.py ...  [  
4%]
  tests/test_everything.py Trace/breakpoint trap (core dumped)
  E: pybuild pybuild:338: test: plugin distutils failed with: exit code=133: cd 
/<>/.pybuild/cpython2_2.7/build; python2.7 -m pytest tests
  dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7 returned 
exit code 13
  make[1]: *** [debian/rules:29: override_dh_auto_test] Error 1
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:22: binary] Error 2
  dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
2
  RUN: /usr/share/launchpad-buildd/slavebin/in-target scan-for-processes 
--backend=chroot --series=cosmic --arch=amd64 PACKAGEBUILD-15263898
  Scanning for processes to kill in build PACKAGEBUILD-15263898
  Build killed with signal TERM after 150 minutes of inactivity

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

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

[Touch-packages] [Bug 1759628] Re: bluez regression: Bluetooth audio fails to reconnect after resume

[Christoph Thielecke]

** Changed in: bluez (Ubuntu)
   Status: In Progress => Confirmed

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

Title:
   bluez regression: Bluetooth audio fails to reconnect after resume

Status in bluez package in Ubuntu:
  Confirmed
Status in bluez package in Fedora:
  Fix Released
Status in Suse:
  Fix Released

Bug description:
  STEPS TO REPRODUCE:
  1. Connect to Bluetooth audio device
  2. Suspend & Resume
  3. Reconnect to Bluetooth device.

  This regression in bluez 5.48 has already been identified and fixed
  upstream. Report is here  and patch is here
  
.

  Syslog reports messages as follows when this issue is happening (I have 
replaced my device's MAC address with [MAC]):
  Mar 28 12:34:29 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:29 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 28 12:34:33 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:33 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments

  Workaround is to run sudo systemctl restart bluetooth after resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Mar 28 12:37:11 2018
  InstallationDate: Installed on 2018-03-23 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Hewlett-Packard HP ProBook 640 G1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic 
root=/dev/mapper/internal-root ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 80:00:0B:C7:4D:1C  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN 
RX bytes:5025 acl:32 sco:0 events:202 errors:0
TX bytes:5785 acl:32 sco:0 commands:103 errors:0

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

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

[Touch-packages] [Bug 1303649] Re: systemd-logind spins in cgmanager_ping_sync()

[Hofer-Temmel Christoph]

Sorry for the late reply, I have not been subscribed to this bug. I have
not written earlier because the bug was limited to one location (it
seems in connection with one wireless network made available to all
users and logging in to the network before logging into the user
account), and I wanted to test all cases of old packages, Marcelo's
workaround and the new version.

@Marcelo de G. Malheiros: Thanks for your pointer to the packages. Your
temporary fix worked well. That enabled me to actually work at this
location.

@Guilherme Picooli: Thanks for version "204-5ubuntu20.28". I upgraded to
it and it the problem has disappeared.

Cordially,
  htc

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

Title:
  systemd-logind spins in cgmanager_ping_sync()

Status in cgmanager package in Ubuntu:
  Invalid
Status in libnih package in Ubuntu:
  Invalid
Status in lxc package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  systemd-logind is consuming a high level of cpu on a continual basis:

PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND   
 
676 root  20   0   43644   2144   1568 R 100.0  0.0  74:43.77 
systemd-logind

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: systemd-services 204-5ubuntu17
  ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8
  Uname: Linux 3.13.0-22-generic x86_64
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Apr  7 09:09:37 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-04-23 (348 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423)
  SourcePackage: systemd
  UpgradeStatus: Upgraded to trusty on 2013-11-11 (146 days ago)

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

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

[Touch-packages] [Bug 1050358] Re: emesene crashed with SIGSEGV in tupledealloc.24592()

[Christoph Reiter]

This crash seems to be limited to Ubuntu 12.10 and 13.04 (looking at the
duplicates and the linked upstream bug report). And that's no longer
supported.

Also the affected program is unmaintained for some years now.

** Changed in: pygobject (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  emesene crashed with SIGSEGV in tupledealloc.24592()

Status in emesene package in Ubuntu:
  Triaged
Status in pygobject package in Ubuntu:
  Fix Released
Status in pygobject-2 package in Ubuntu:
  Triaged

Bug description:
  When I try to connect to my msn account emesene crash

  ProblemType: Crash
  DistroRelease: Ubuntu 12.10
  Package: emesene 2.12.5+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 3.5.0-14.16-generic 3.5.3
  Uname: Linux 3.5.0-14-generic x86_64
  ApportVersion: 2.5.1-0ubuntu7
  Architecture: amd64
  CrashCounter: 1
  Date: Thu Sep 13 13:12:08 2012
  ExecutablePath: /usr/share/emesene/emesene/emesene
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  InterpreterPath: /usr/bin/python2.7
  PackageArchitecture: all
  ProcCmdline: python /usr/bin/emesene -s
  SegvAnalysis:
   Segfault happened at: 0x4b6058:  mov0x98(%r13),%eax
   PC (0x004b6058) ok
   source "0x98(%r13)" (0x0098) not located in a known VMA region (needed 
readable region)!
   destination "%eax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: emesene
  StacktraceTop:
   ?? ()
   ?? ()
   ?? () from /usr/lib/python2.7/dist-packages/glib/_glib.so
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: emesene crashed with SIGSEGV in g_main_context_dispatch()
  UpgradeStatus: Upgraded to quantal on 2012-04-26 (139 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

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

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

[Touch-packages] [Bug 1303649] Re: systemd-logind spins in cgmanager_ping_sync()

[Hofer-Temmel Christoph]

I am having the same issue since this morning (14 march): cgmanager and 
systemd-logind both using 60-70% of system resources, gui unusable, login via 
console possible.
Looking at /var/log/apt/term.log I see that the update has been installed on 9 
march, but did not give any issues until now.
Intermediate updates were samba packages yesterday (13 march) evening ... but 
the system worked after that just fine for the first bootup this morning.
Only on the second boot did things go wrong.

I tried to apply the fix outlined in 4 steps by Marcelo [4 steps], just for 
i386 instead of amd64.
The problem I have is getting those 3 deb packages.
I found the build for libpam 20.25 [libpam20.25], but this one offers no 
artefacts.
On the various package sites only 20.26 is available.
Do I have to build on my own?
Or is a timeline for an update known, so that I can just upgrade?

Cordially,
  htc

[4 steps]: 
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1303649/comments/20
[libpam20.25]: 
https://launchpad.net/ubuntu/+source/systemd/204-5ubuntu20.25/+build/13545611

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

Title:
  systemd-logind spins in cgmanager_ping_sync()

Status in cgmanager package in Ubuntu:
  Invalid
Status in libnih package in Ubuntu:
  Invalid
Status in lxc package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  systemd-logind is consuming a high level of cpu on a continual basis:

PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND   
 
676 root  20   0   43644   2144   1568 R 100.0  0.0  74:43.77 
systemd-logind

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: systemd-services 204-5ubuntu17
  ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8
  Uname: Linux 3.13.0-22-generic x86_64
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Apr  7 09:09:37 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-04-23 (348 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423)
  SourcePackage: systemd
  UpgradeStatus: Upgraded to trusty on 2013-11-11 (146 days ago)

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

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

[Touch-packages] [Bug 1524000] Re: PyGIWarning: UbuntuAppLaunch was imported without specifying a version first

[Christoph Reiter]

PyGObject warns that gi.require_version() wasn't used. That's something
that needs to be fixed by the library user.

** Changed in: pygobject (Ubuntu)
   Status: New => Invalid

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

Title:
  PyGIWarning: UbuntuAppLaunch was imported without specifying a version
  first

Status in Autopilot:
  Fix Released
Status in Ubuntu Music App:
  Invalid
Status in pygobject package in Ubuntu:
  Invalid

Bug description:
  When launching Autopilot tests for Music App you get an error indicating that 
UbuntuAppLaunch was imported without specifying a version first.
  This is the error:

  autopilot run music_app
  /usr/lib/python2.7/dist-packages/autopilot/application/_launcher.py:23: 
PyGIWarning: UbuntuAppLaunch was imported without specifying a version first. 
Use gi.require_version('UbuntuAppLaunch', '2') before import to ensure that the 
right version gets loaded.
from gi.repository import GLib, UbuntuAppLaunch
  Loading tests from: /home/victor/Development/music-app/tests/autopilot

  Failed to import test module: music_app.tests.test_music
  Traceback (most recent call last):
File "/usr/lib/python2.7/unittest/loader.py", line 254, in _find_tests
  module = self._get_module_from_name(name)
File "/usr/lib/python2.7/unittest/loader.py", line 232, in 
_get_module_from_name
  __import__(name)
File 
"/home/victor/Development/music-app/tests/autopilot/music_app/__init__.py", 
line 9, in 
  from ubuntuuitoolkit import (
  ImportError: No module named ubuntuuitoolkit

  Tests running...
  ==
  ERROR: unittest.loader.ModuleImportFailure.music_app.tests.test_music
  --
  Traceback (most recent call last):
  ImportError: Failed to import test module: music_app.tests.test_music
  Traceback (most recent call last):
File "/usr/lib/python2.7/unittest/loader.py", line 254, in _find_tests
  module = self._get_module_from_name(name)
File "/usr/lib/python2.7/unittest/loader.py", line 232, in 
_get_module_from_name
  __import__(name)
File 
"/home/victor/Development/music-app/tests/autopilot/music_app/__init__.py", 
line 9, in 
  from ubuntuuitoolkit import (
  ImportError: No module named ubuntuuitoolkit

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

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

[Touch-packages] [Bug 1718692] [NEW] package libgtk2.0-0:i386 2.24.30-1ubuntu1.16.04.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attemptin

[Christoph Heim]

Public bug reported:

Wanted to Update "OS Updates" and "Software". Somewhere there is issue.
Did not complete updates. Thank you!

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libgtk2.0-0:i386 2.24.30-1ubuntu1.16.04.2
ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-35-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Thu Sep 21 16:26:12 2017
DuplicateSignature:
 package:libgtk2.0-0:i386:2.24.30-1ubuntu1.16.04.2
 Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ...
 dpkg: error processing package libgtk2.0-0:i386 (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2017-03-23 (181 days ago)
InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215)
PackageArchitecture: i386
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: gtk+2.0
Title: package libgtk2.0-0:i386 2.24.30-1ubuntu1.16.04.2 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gtk+2.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 xenial

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

Title:
  package libgtk2.0-0:i386 2.24.30-1ubuntu1.16.04.2 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in gtk+2.0 package in Ubuntu:
  New

Bug description:
  Wanted to Update "OS Updates" and "Software". Somewhere there is
  issue. Did not complete updates. Thank you!

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libgtk2.0-0:i386 2.24.30-1ubuntu1.16.04.2
  ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Thu Sep 21 16:26:12 2017
  DuplicateSignature:
   package:libgtk2.0-0:i386:2.24.30-1ubuntu1.16.04.2
   Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ...
   dpkg: error processing package libgtk2.0-0:i386 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-03-23 (181 days ago)
  InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: gtk+2.0
  Title: package libgtk2.0-0:i386 2.24.30-1ubuntu1.16.04.2 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1718692/+subscriptions

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

[Touch-packages] [Bug 1375782] Re: Unable to perform search error when syncing Evolution with Google Contacts

[Christoph Grimmer-Dietrich]

Error is also present on vanilla ubuntu 17.04

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

Title:
  Unable to perform search error when syncing Evolution with Google
  Contacts

Status in libgdata package in Ubuntu:
  Fix Released
Status in libgdata source package in Utopic:
  Fix Released
Status in evolution package in Arch Linux:
  New

Bug description:
  [ Description ]

  Google changed their expected date format to fix a bug which libgdata
  was working around. We don't need the workaround any more.

  [ Fix ]

  This is fixed in 0.16.1. I think we should take this update, as it
  includes other bugfixes too. I think it falls under the GNOME MRE. If
  not, we can cherry-pick this one fix.

  This is in vivid already.

  [ QA ]

  If you get the below error, check that upgrading to the new libgdata
  fixes it for you.

  [ Original Report ]

  Hello,

  When trying to synchronise Google Contacts with Evolution, I am
  getting the error message:

  The backend for this address book was unable to parse this query. 
GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._e_2dclient_2derror_2dquark.Code16:
 Invalid request URI or header, or unsupported nonstandard parameter: 
  http://schemas.google.com/g/2005;>
   
    GData
    invalid
    Bad updated-min timestamp format: 
2014-09-30T12:48:18.01 00:00
   
  

  My system is Ubunru 14.10, Evolution 3.12.6.

  Before updating to Ubuntu 14.10 (in 14.04) it worked without an error.

  Ruben

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

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

[Touch-packages] [Bug 429533] Re: pulseaudio hangs, prevents login, home as cifs

[Christoph]

Since some time the pulse-session script has been removed from pulseaudio 
package. Quote from the pulseaudio changelog:  
 [ Luke Yelavich ]
  * Remove wrapper scripts and accessibility special case, to help with the
desktop startup time. The accessibility case should be solved in
speech-dispatcher by the time lucid ships.
[..]
- debian/pulse-session: Removed
[..]
 -- Daniel T Chen   Wed, 25 Nov 2009 16:34:54 -0500

As Ubuntu 9.04 has reached end-of-life for some time, this bug has been
overcome by events. As this is not a status, I choose fix released, as
up to date versions are not affected by it.

** Changed in: pulseaudio (Ubuntu)
   Status: Incomplete => Fix Released

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

Title:
  pulseaudio hangs, prevents login, home as cifs

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  We are using an up to date Ubuntu 9.04 with an cifs home directory for
  the users. When a user tries to login, the login hangs, until the
  pulseaudio daemon gets killed or the broken symlinks in ~/.pulse/ get
  removed. If the user has no dead symlinks in $HOME/.pulse the login
  does not hang.

  To solve this situation we edited /usr/bin/pulse-session as follows:

  --- pulse-session.orig  2009-09-14 17:10:49.0 +0200
  +++ pulse-session   2009-09-14 17:23:57.0 +0200
  @@ -9,6 +9,7 @@
   if [ -x /usr/bin/start-pulseaudio-x11 ] && \
  [ $PULSEAUDIO_SYSTEM_START -eq 0 ] && \
  [ ! -f $HOME/.pulse_a11y_nostart ]; then
  +/usr/bin/find -L $HOME/.pulse -maxdepth 1 -type l -delete
  /usr/bin/start-pulseaudio-x11
   fi

  This patch ensures, that broken symlinks and only those are remove from 
~/.pulse dir before the pulseaudio daemon starts up.
  Symlinks on cifs are known for not working very well. That getent term 
ensures that the find term gets the home directory independent of where they 
are stored. 

  
  Description:Ubuntu 9.04
  Release:9.04

  pulseaudio:
Installiert: 1:0.9.14-0ubuntu20.2
Kandidat: 1:0.9.14-0ubuntu20.2
Versions-Tabelle:
   *** 1:0.9.14-0ubuntu20.2 0

  
  This is not duplicate of 
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/330766 because, over 
there home dir is on ntfs. For more informations read my comment over there.

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

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

[Touch-packages] [Bug 1663689] [NEW] gettext() does not work on aarch64

[Christoph Müllner]

Public bug reported:

Code to reproduce the bug

I was not able to get the proper translation from gettext() on an aarch64
Ubuntu Xenial machine. The same code however works fine on x86_64.

To reproduce the issue one can use the following instructions:

1) Create the following directory structure:
   mkdir -p fi/LC_MESSAGES

2) Create the file fi/LC_MESSAGES/messages.po with the following content:
msgid ""
msgstr ""
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=ISO-8859-1\n"
"Content-Transfer-Encoding: 8bit\n"
msgid "Basic test"
msgstr "Perustesti"

3) Compile a mo:
   msgfmt -o fi/LC_MESSAGES/messages.mo fi/LC_MESSAGES/messages.po

4) Compile the attached file and run it (no special compiler flags used).
   The code essentially does:
   a. setlocale(LC_ALL, "fi_FI");
   b. bindtextdomain("messages", "./locale");
   c. textdomain("messages");
   d. gettext("Basic test")

On aarch64 this results in "Basic test".
On x86_64 this results in "Perustesti".

FWIW, I was able to reproduce this bug on the following aarch64 Linux
distributions as well:

 * Fedora 25 (see [1])
 * CentOS 7
 * OpenSUSE Leap 42.2

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1418635

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

** Attachment added: "Testcase to trigger the bug"
   
https://bugs.launchpad.net/bugs/1663689/+attachment/4816662/+files/gettext_bug.c

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

Title:
  gettext() does not work on aarch64

Status in gettext package in Ubuntu:
  New

Bug description:
  Code to reproduce the bug

  I was not able to get the proper translation from gettext() on an aarch64
  Ubuntu Xenial machine. The same code however works fine on x86_64.

  To reproduce the issue one can use the following instructions:

  1) Create the following directory structure:
 mkdir -p fi/LC_MESSAGES

  2) Create the file fi/LC_MESSAGES/messages.po with the following content:
  msgid ""
  msgstr ""
  "MIME-Version: 1.0\n"
  "Content-Type: text/plain; charset=ISO-8859-1\n"
  "Content-Transfer-Encoding: 8bit\n"
  msgid "Basic test"
  msgstr "Perustesti"

  3) Compile a mo:
 msgfmt -o fi/LC_MESSAGES/messages.mo fi/LC_MESSAGES/messages.po

  4) Compile the attached file and run it (no special compiler flags used).
 The code essentially does:
 a. setlocale(LC_ALL, "fi_FI");
 b. bindtextdomain("messages", "./locale");
 c. textdomain("messages");
 d. gettext("Basic test")

  On aarch64 this results in "Basic test".
  On x86_64 this results in "Perustesti".

  FWIW, I was able to reproduce this bug on the following aarch64 Linux
  distributions as well:

   * Fedora 25 (see [1])
   * CentOS 7
   * OpenSUSE Leap 42.2

  [1] https://bugzilla.redhat.com/show_bug.cgi?id=1418635

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

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

[Touch-packages] [Bug 1574347] Re: [SRU] Re-read the link type if the name changed

[Hans-Christoph Steiner]

I am pretty sure I'm having this problem on a Toshiba Chromebook 2
(CB35-B3340) running 16.04 fully updated as of this week.  I get the
ethernet up/down arrows, there is no ethernet on this laptop.  I also
get the state where it is disconnected and not showing any wifi
networks.  It seems to be related to suspend/wake, but doesn't always
happen.

$ lspci |grep -i net
01:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb)

ii  network-manager   1.2.0-0ubuntu0.16.04.3 amd64 
ii  network-manager-gnome 1.2.0-0ubuntu0.16.04.3 amd64 
ii  network-manager-pptp  1.1.93-1ubuntu1amd64 
ii  network-manager-pptp-gnome1.1.93-1ubuntu1amd64 

Running this got things back to normal:
$ sudo service network-manager restart

This looked noteworthy:

# dmesg |grep iwl
[   10.658028] iwlwifi :01:00.0: Direct firmware load for 
iwlwifi-7260-17.ucode failed with error -2
[   11.064468] iwlwifi :01:00.0: loaded firmware version 16.242414.0 
op_mode iwlmvm
[   11.545992] iwlwifi :01:00.0: Detected Intel(R) Dual Band Wireless AC 
7260, REV=0x144
[   11.546081] iwlwifi :01:00.0: L1 Enabled - LTR Disabled
[   11.546326] iwlwifi :01:00.0: L1 Enabled - LTR Disabled
[   11.771068] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
[   11.777060] iwlwifi :01:00.0 wlp1s0: renamed from wlan0
[   12.285642] iwlwifi :01:00.0: L1 Enabled - LTR Disabled
[   12.285883] iwlwifi :01:00.0: L1 Enabled - LTR Disabled
[   12.491349] iwlwifi :01:00.0: L1 Enabled - LTR Disabled
[   12.491592] iwlwifi :01:00.0: L1 Enabled - LTR Disabled
[  461.381354] iwlwifi :01:00.0: L1 Enabled - LTR Disabled
[  461.381596] iwlwifi :01:00.0: L1 Enabled - LTR Disabled

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

Title:
  [SRU] Re-read the link type if the name changed

Status in NetworkManager:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  NM needs to re-read the DEVTYPE after the device name changed, an example is 
that WiFi network list disappears from network manager applet

  [Testcase]
  1. Boot the system. It should include a wireless device.
  2. In a terminal, run 'nmcli dev'.
  3. In the correct case, the line for the wireless device should read "wifi" 
under the TYPE column. In a failure case, it will read "ethernet".

  After upgrading to the new version, the repeating the above steps
  should give expected behavior.

  [Regression Potential]
  Potential of causing regression is relatively small for a one line change to 
re-read a value to be known.

  ---

  Problems:-

  1. The network manager applet does not show the list of WiFI APs it can find.
  2. The network manager applet does not the name of the AP to which it is 
connected
  3. The icon of the applet shows two vertical arrows in opposite direction - 
the wired connection symbol and NOT the wifi connected icon.

  Temporary Workaround:-
  Log out and again log back in.

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

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

[Touch-packages] [Bug 1617710] [NEW] no way to configure keyboard using Chromebook mapping

[Hans-Christoph Steiner]

Public bug reported:

/usr/share/X11/xkb/symbols/inet includes the key mapping tweaks required
by Chromebook keyboards.  I can confirm that they are correct by
appending them to the /usr/share/X11/xkb/symbols/pc file and restarting.
But I can find no way to choose "Chromebook" as my keyboard type or
layout.  I looked through all of the options provided by `sudo dpkg-
reconfigure keyboard-configuration` and the Text Entry System Settings.

Ubuntu 16.04 has come a very long way in supporting Chromebooks out of
box, and Ubuntu is even easy to install on these machines. There are
just a couple details like this and it'll be a seamless out-of-box
experience!

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: keyboard-configuration 1.108ubuntu15.2
ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
Uname: Linux 4.4.0-34-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Aug 28 10:17:07 2016
InstallationDate: Installed on 2016-08-27 (0 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
PackageArchitecture: all
SourcePackage: console-setup
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: console-setup (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 console-setup in Ubuntu.
https://bugs.launchpad.net/bugs/1617710

Title:
  no way to configure keyboard using Chromebook mapping

Status in console-setup package in Ubuntu:
  New

Bug description:
  /usr/share/X11/xkb/symbols/inet includes the key mapping tweaks
  required by Chromebook keyboards.  I can confirm that they are correct
  by appending them to the /usr/share/X11/xkb/symbols/pc file and
  restarting.  But I can find no way to choose "Chromebook" as my
  keyboard type or layout.  I looked through all of the options provided
  by `sudo dpkg-reconfigure keyboard-configuration` and the Text Entry
  System Settings.

  Ubuntu 16.04 has come a very long way in supporting Chromebooks out of
  box, and Ubuntu is even easy to install on these machines. There are
  just a couple details like this and it'll be a seamless out-of-box
  experience!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: keyboard-configuration 1.108ubuntu15.2
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Aug 28 10:17:07 2016
  InstallationDate: Installed on 2016-08-27 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  SourcePackage: console-setup
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1617710/+subscriptions

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

[Touch-packages] [Bug 1451728] Re: [master] kde-config-telepathy-accounts package install error

[Christoph]

As google-im.service in kde-config-telepathy-accounts is identical to
the same-named file in account-plugin-google, a possible solution is to
dpkg-divert /usr/share/accounts/google-im.service in the preinst of the
package.

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

Title:
  [master] kde-config-telepathy-accounts package install error

Status in Kubuntu PPA:
  Fix Released
Status in Telepathy KDE:
  Fix Released
Status in kaccounts-integration package in Ubuntu:
  In Progress
Status in kaccounts-providers package in Ubuntu:
  Triaged
Status in ktp-accounts-kcm package in Ubuntu:
  Triaged
Status in libaccounts-glib package in Ubuntu:
  Fix Released
Status in kaccounts-providers source package in Wily:
  Triaged
Status in ktp-accounts-kcm source package in Wily:
  Triaged

Bug description:
  Installing from Kubuntu 15.04 backports:

  Unpacking kde-config-telepathy-accounts (15.04.0-0ubuntu1~ubuntu15.04~ppa1) 
over (0.9.0-0ubuntu1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/kde-config-telepathy-accounts_15.04.0-0ubuntu1~ubuntu15.04~ppa1_amd64.deb
 (--unpack):
   trying to overwrite '/usr/share/accounts/services/facebook-im.service', 
which is also in package account-plugin-facebook 0.12+15.04.20150415.1-0ubuntu1
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)

To manage notifications about this bug go to:
https://bugs.launchpad.net/kubuntu-ppa/+bug/1451728/+subscriptions

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

[Touch-packages] [Bug 1580266] [NEW] Computer hangs on reboot or shutdown, typically for >10 mins, Ubuntu 16.04 and previous versions

[Lilli Christoph]

Public bug reported:

I am aware of the thread here:

https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1464917

People there are asking that if you have the same/similar bug to report
it separately, so that's what I'm doing.

What I've noticed is that my shutdown process hangs as some point,
usually with the screen being black or with a single cursor.  After >10
mins, the computer will finally shut off.  I've had this issue I think
since 15.04, definitely in 15.10, and now still in 16.04.

I've tried the fix

$ sudo systemctl reboot

which worked one time, but not another time.

I've also tried

$ sudo swapoff -a sudo systemctl reboot

and that appeared to work, but I haven't tested it enough times to say
it always works.  For what it's worth, turning off the swap probably
took longer than my typical black screen shutdown so it's really not a
stopgap fix either way.

I know this isn't enough information to be sure I'm having the
swap/systemd failure, so let me know what else you need.  Thanks.

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

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

Title:
  Computer hangs on reboot or shutdown, typically for >10 mins, Ubuntu
  16.04 and previous versions

Status in systemd package in Ubuntu:
  New

Bug description:
  I am aware of the thread here:

  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1464917

  People there are asking that if you have the same/similar bug to
  report it separately, so that's what I'm doing.

  What I've noticed is that my shutdown process hangs as some point,
  usually with the screen being black or with a single cursor.  After
  >10 mins, the computer will finally shut off.  I've had this issue I
  think since 15.04, definitely in 15.10, and now still in 16.04.

  I've tried the fix

  $ sudo systemctl reboot

  which worked one time, but not another time.

  I've also tried

  $ sudo swapoff -a sudo systemctl reboot

  and that appeared to work, but I haven't tested it enough times to say
  it always works.  For what it's worth, turning off the swap probably
  took longer than my typical black screen shutdown so it's really not a
  stopgap fix either way.

  I know this isn't enough information to be sure I'm having the
  swap/systemd failure, so let me know what else you need.  Thanks.

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

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

[Touch-packages] [Bug 1434351] Re: X fonts and widgets disappear after suspend/resume cycle

[Christoph Ra]

Oh dear, I didn't think apport-collect would submit more than just an
attachment. For what it's worth, the bug wasn't in effect while doing
that, I had to read the menus. Same situation as above - Intel video,
Xubuntu, only for me the bug appeared only after updating to 16.04.

General system information & a screenshot are attached.

** Attachment added: "Screenshot_2016-05-01_10-21-05.png"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1434351/+attachment/4652692/+files/Screenshot_2016-05-01_10-21-05.png

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

Title:
  X fonts and widgets disappear after suspend/resume cycle

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  After a suspend/resume cycle, the screen comes up normally, but every
  time I move my mouse over a piece of text, button, widget, etc, the
  text vanishes and it's replaced by a plain rectangle.

  This does not affect xterm, but it does affect any GTK apps, firefox,
  etc.

  xfce-panel vanishes, although it's still responding to mouse-clicks.
  Newly opened menus are grey rectangles.

  The lines underlining menu hotkeys do NOT disappear.

  In the attached screenshot, you can clearly see which buttons I have
  waved the mouse over, and which I have not.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar 19 19:51:37 2015
  InstallationDate: Installed on 2015-03-05 (14 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago)

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

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

[Touch-packages] [Bug 1434351] Re: X fonts and widgets disappear after suspend/resume cycle

[Christoph Ra]

** Attachment added: "system_info_inxi_Fxz"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1434351/+attachment/4652693/+files/system_info_inxi_Fxz

** Attachment removed: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1434351/+attachment/4652668/+files/ProcCpuinfo.txt

** Attachment removed: "BootLog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1434351/+attachment/4652658/+files/BootLog.txt

** Attachment removed: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1434351/+attachment/4652659/+files/CurrentDmesg.txt

** Attachment removed: "Dependencies.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1434351/+attachment/4652660/+files/Dependencies.txt

** Attachment removed: "DpkgLog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1434351/+attachment/4652661/+files/DpkgLog.txt

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

Title:
  X fonts and widgets disappear after suspend/resume cycle

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  After a suspend/resume cycle, the screen comes up normally, but every
  time I move my mouse over a piece of text, button, widget, etc, the
  text vanishes and it's replaced by a plain rectangle.

  This does not affect xterm, but it does affect any GTK apps, firefox,
  etc.

  xfce-panel vanishes, although it's still responding to mouse-clicks.
  Newly opened menus are grey rectangles.

  The lines underlining menu hotkeys do NOT disappear.

  In the attached screenshot, you can clearly see which buttons I have
  waved the mouse over, and which I have not.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar 19 19:51:37 2015
  InstallationDate: Installed on 2015-03-05 (14 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago)

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

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

[Touch-packages] [Bug 1434351] Xrandr.txt

[Christoph Ra]

apport information

** Attachment added: "Xrandr.txt"
   https://bugs.launchpad.net/bugs/1434351/+attachment/4652675/+files/Xrandr.txt

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

Title:
  X fonts and widgets disappear after suspend/resume cycle

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  After a suspend/resume cycle, the screen comes up normally, but every
  time I move my mouse over a piece of text, button, widget, etc, the
  text vanishes and it's replaced by a plain rectangle.

  This does not affect xterm, but it does affect any GTK apps, firefox,
  etc.

  xfce-panel vanishes, although it's still responding to mouse-clicks.
  Newly opened menus are grey rectangles.

  The lines underlining menu hotkeys do NOT disappear.

  In the attached screenshot, you can clearly see which buttons I have
  waved the mouse over, and which I have not.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar 19 19:51:37 2015
  InstallationDate: Installed on 2015-03-05 (14 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago)

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

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

[Touch-packages] [Bug 1434351] xdpyinfo.txt

[Christoph Ra]

apport information

** Attachment added: "xdpyinfo.txt"
   
https://bugs.launchpad.net/bugs/1434351/+attachment/4652676/+files/xdpyinfo.txt

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

Title:
  X fonts and widgets disappear after suspend/resume cycle

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  After a suspend/resume cycle, the screen comes up normally, but every
  time I move my mouse over a piece of text, button, widget, etc, the
  text vanishes and it's replaced by a plain rectangle.

  This does not affect xterm, but it does affect any GTK apps, firefox,
  etc.

  xfce-panel vanishes, although it's still responding to mouse-clicks.
  Newly opened menus are grey rectangles.

  The lines underlining menu hotkeys do NOT disappear.

  In the attached screenshot, you can clearly see which buttons I have
  waved the mouse over, and which I have not.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar 19 19:51:37 2015
  InstallationDate: Installed on 2015-03-05 (14 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago)

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

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

[Touch-packages] [Bug 1434351] ProcInterrupts.txt

[Christoph Ra]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1434351/+attachment/4652670/+files/ProcInterrupts.txt

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

Title:
  X fonts and widgets disappear after suspend/resume cycle

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  After a suspend/resume cycle, the screen comes up normally, but every
  time I move my mouse over a piece of text, button, widget, etc, the
  text vanishes and it's replaced by a plain rectangle.

  This does not affect xterm, but it does affect any GTK apps, firefox,
  etc.

  xfce-panel vanishes, although it's still responding to mouse-clicks.
  Newly opened menus are grey rectangles.

  The lines underlining menu hotkeys do NOT disappear.

  In the attached screenshot, you can clearly see which buttons I have
  waved the mouse over, and which I have not.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar 19 19:51:37 2015
  InstallationDate: Installed on 2015-03-05 (14 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago)

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

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

[Touch-packages] [Bug 1434351] XorgLogOld.txt

[Christoph Ra]

apport information

** Attachment added: "XorgLogOld.txt"
   
https://bugs.launchpad.net/bugs/1434351/+attachment/4652674/+files/XorgLogOld.txt

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

Title:
  X fonts and widgets disappear after suspend/resume cycle

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  After a suspend/resume cycle, the screen comes up normally, but every
  time I move my mouse over a piece of text, button, widget, etc, the
  text vanishes and it's replaced by a plain rectangle.

  This does not affect xterm, but it does affect any GTK apps, firefox,
  etc.

  xfce-panel vanishes, although it's still responding to mouse-clicks.
  Newly opened menus are grey rectangles.

  The lines underlining menu hotkeys do NOT disappear.

  In the attached screenshot, you can clearly see which buttons I have
  waved the mouse over, and which I have not.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar 19 19:51:37 2015
  InstallationDate: Installed on 2015-03-05 (14 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago)

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

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

[Touch-packages] [Bug 1434351] XorgLog.txt

[Christoph Ra]

apport information

** Attachment added: "XorgLog.txt"
   
https://bugs.launchpad.net/bugs/1434351/+attachment/4652673/+files/XorgLog.txt

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

Title:
  X fonts and widgets disappear after suspend/resume cycle

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  After a suspend/resume cycle, the screen comes up normally, but every
  time I move my mouse over a piece of text, button, widget, etc, the
  text vanishes and it's replaced by a plain rectangle.

  This does not affect xterm, but it does affect any GTK apps, firefox,
  etc.

  xfce-panel vanishes, although it's still responding to mouse-clicks.
  Newly opened menus are grey rectangles.

  The lines underlining menu hotkeys do NOT disappear.

  In the attached screenshot, you can clearly see which buttons I have
  waved the mouse over, and which I have not.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar 19 19:51:37 2015
  InstallationDate: Installed on 2015-03-05 (14 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago)

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

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

[Touch-packages] [Bug 1434351] ProcModules.txt

[Christoph Ra]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1434351/+attachment/4652671/+files/ProcModules.txt

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

Title:
  X fonts and widgets disappear after suspend/resume cycle

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  After a suspend/resume cycle, the screen comes up normally, but every
  time I move my mouse over a piece of text, button, widget, etc, the
  text vanishes and it's replaced by a plain rectangle.

  This does not affect xterm, but it does affect any GTK apps, firefox,
  etc.

  xfce-panel vanishes, although it's still responding to mouse-clicks.
  Newly opened menus are grey rectangles.

  The lines underlining menu hotkeys do NOT disappear.

  In the attached screenshot, you can clearly see which buttons I have
  waved the mouse over, and which I have not.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar 19 19:51:37 2015
  InstallationDate: Installed on 2015-03-05 (14 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago)

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

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

[Touch-packages] [Bug 1434351] UdevDb.txt

[Christoph Ra]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1434351/+attachment/4652672/+files/UdevDb.txt

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

Title:
  X fonts and widgets disappear after suspend/resume cycle

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  After a suspend/resume cycle, the screen comes up normally, but every
  time I move my mouse over a piece of text, button, widget, etc, the
  text vanishes and it's replaced by a plain rectangle.

  This does not affect xterm, but it does affect any GTK apps, firefox,
  etc.

  xfce-panel vanishes, although it's still responding to mouse-clicks.
  Newly opened menus are grey rectangles.

  The lines underlining menu hotkeys do NOT disappear.

  In the attached screenshot, you can clearly see which buttons I have
  waved the mouse over, and which I have not.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar 19 19:51:37 2015
  InstallationDate: Installed on 2015-03-05 (14 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago)

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

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

[Touch-packages] [Bug 1434351] Lspci.txt

[Christoph Ra]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1434351/+attachment/4652666/+files/Lspci.txt

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

Title:
  X fonts and widgets disappear after suspend/resume cycle

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  After a suspend/resume cycle, the screen comes up normally, but every
  time I move my mouse over a piece of text, button, widget, etc, the
  text vanishes and it's replaced by a plain rectangle.

  This does not affect xterm, but it does affect any GTK apps, firefox,
  etc.

  xfce-panel vanishes, although it's still responding to mouse-clicks.
  Newly opened menus are grey rectangles.

  The lines underlining menu hotkeys do NOT disappear.

  In the attached screenshot, you can clearly see which buttons I have
  waved the mouse over, and which I have not.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar 19 19:51:37 2015
  InstallationDate: Installed on 2015-03-05 (14 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago)

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

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

[Touch-packages] [Bug 1434351] Lsusb.txt

[Christoph Ra]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1434351/+attachment/4652667/+files/Lsusb.txt

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

Title:
  X fonts and widgets disappear after suspend/resume cycle

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  After a suspend/resume cycle, the screen comes up normally, but every
  time I move my mouse over a piece of text, button, widget, etc, the
  text vanishes and it's replaced by a plain rectangle.

  This does not affect xterm, but it does affect any GTK apps, firefox,
  etc.

  xfce-panel vanishes, although it's still responding to mouse-clicks.
  Newly opened menus are grey rectangles.

  The lines underlining menu hotkeys do NOT disappear.

  In the attached screenshot, you can clearly see which buttons I have
  waved the mouse over, and which I have not.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar 19 19:51:37 2015
  InstallationDate: Installed on 2015-03-05 (14 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago)

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

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

[Touch-packages] [Bug 1434351] ProcCpuinfo.txt

[Christoph Ra]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1434351/+attachment/4652668/+files/ProcCpuinfo.txt

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

Title:
  X fonts and widgets disappear after suspend/resume cycle

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  After a suspend/resume cycle, the screen comes up normally, but every
  time I move my mouse over a piece of text, button, widget, etc, the
  text vanishes and it's replaced by a plain rectangle.

  This does not affect xterm, but it does affect any GTK apps, firefox,
  etc.

  xfce-panel vanishes, although it's still responding to mouse-clicks.
  Newly opened menus are grey rectangles.

  The lines underlining menu hotkeys do NOT disappear.

  In the attached screenshot, you can clearly see which buttons I have
  waved the mouse over, and which I have not.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar 19 19:51:37 2015
  InstallationDate: Installed on 2015-03-05 (14 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago)

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

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

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

[Christoph Ra]

apport information

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

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

Title:
  X fonts and widgets disappear after suspend/resume cycle

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  After a suspend/resume cycle, the screen comes up normally, but every
  time I move my mouse over a piece of text, button, widget, etc, the
  text vanishes and it's replaced by a plain rectangle.

  This does not affect xterm, but it does affect any GTK apps, firefox,
  etc.

  xfce-panel vanishes, although it's still responding to mouse-clicks.
  Newly opened menus are grey rectangles.

  The lines underlining menu hotkeys do NOT disappear.

  In the attached screenshot, you can clearly see which buttons I have
  waved the mouse over, and which I have not.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar 19 19:51:37 2015
  InstallationDate: Installed on 2015-03-05 (14 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago)

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

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

[Touch-packages] [Bug 1434351] LightdmGreeterLogOld.txt

[Christoph Ra]

apport information

** Attachment added: "LightdmGreeterLogOld.txt"
   
https://bugs.launchpad.net/bugs/1434351/+attachment/4652664/+files/LightdmGreeterLogOld.txt

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

Title:
  X fonts and widgets disappear after suspend/resume cycle

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  After a suspend/resume cycle, the screen comes up normally, but every
  time I move my mouse over a piece of text, button, widget, etc, the
  text vanishes and it's replaced by a plain rectangle.

  This does not affect xterm, but it does affect any GTK apps, firefox,
  etc.

  xfce-panel vanishes, although it's still responding to mouse-clicks.
  Newly opened menus are grey rectangles.

  The lines underlining menu hotkeys do NOT disappear.

  In the attached screenshot, you can clearly see which buttons I have
  waved the mouse over, and which I have not.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar 19 19:51:37 2015
  InstallationDate: Installed on 2015-03-05 (14 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago)

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

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

[Touch-packages] [Bug 1434351] CurrentDmesg.txt

[Christoph Ra]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1434351/+attachment/4652659/+files/CurrentDmesg.txt

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

Title:
  X fonts and widgets disappear after suspend/resume cycle

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  After a suspend/resume cycle, the screen comes up normally, but every
  time I move my mouse over a piece of text, button, widget, etc, the
  text vanishes and it's replaced by a plain rectangle.

  This does not affect xterm, but it does affect any GTK apps, firefox,
  etc.

  xfce-panel vanishes, although it's still responding to mouse-clicks.
  Newly opened menus are grey rectangles.

  The lines underlining menu hotkeys do NOT disappear.

  In the attached screenshot, you can clearly see which buttons I have
  waved the mouse over, and which I have not.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar 19 19:51:37 2015
  InstallationDate: Installed on 2015-03-05 (14 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago)

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

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

[Touch-packages] [Bug 1434351] LightdmLog.txt

[Christoph Ra]

apport information

** Attachment added: "LightdmLog.txt"
   
https://bugs.launchpad.net/bugs/1434351/+attachment/4652665/+files/LightdmLog.txt

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

Title:
  X fonts and widgets disappear after suspend/resume cycle

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  After a suspend/resume cycle, the screen comes up normally, but every
  time I move my mouse over a piece of text, button, widget, etc, the
  text vanishes and it's replaced by a plain rectangle.

  This does not affect xterm, but it does affect any GTK apps, firefox,
  etc.

  xfce-panel vanishes, although it's still responding to mouse-clicks.
  Newly opened menus are grey rectangles.

  The lines underlining menu hotkeys do NOT disappear.

  In the attached screenshot, you can clearly see which buttons I have
  waved the mouse over, and which I have not.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar 19 19:51:37 2015
  InstallationDate: Installed on 2015-03-05 (14 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago)

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

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

[Touch-packages] [Bug 1434351] LightdmDisplayLog.txt

[Christoph Ra]

apport information

** Attachment added: "LightdmDisplayLog.txt"
   
https://bugs.launchpad.net/bugs/1434351/+attachment/4652663/+files/LightdmDisplayLog.txt

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

Title:
  X fonts and widgets disappear after suspend/resume cycle

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  After a suspend/resume cycle, the screen comes up normally, but every
  time I move my mouse over a piece of text, button, widget, etc, the
  text vanishes and it's replaced by a plain rectangle.

  This does not affect xterm, but it does affect any GTK apps, firefox,
  etc.

  xfce-panel vanishes, although it's still responding to mouse-clicks.
  Newly opened menus are grey rectangles.

  The lines underlining menu hotkeys do NOT disappear.

  In the attached screenshot, you can clearly see which buttons I have
  waved the mouse over, and which I have not.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar 19 19:51:37 2015
  InstallationDate: Installed on 2015-03-05 (14 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago)

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

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

[Touch-packages] [Bug 1434351] BootLog.txt

[Christoph Ra]

apport information

** Attachment added: "BootLog.txt"
   
https://bugs.launchpad.net/bugs/1434351/+attachment/4652658/+files/BootLog.txt

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

Title:
  X fonts and widgets disappear after suspend/resume cycle

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  After a suspend/resume cycle, the screen comes up normally, but every
  time I move my mouse over a piece of text, button, widget, etc, the
  text vanishes and it's replaced by a plain rectangle.

  This does not affect xterm, but it does affect any GTK apps, firefox,
  etc.

  xfce-panel vanishes, although it's still responding to mouse-clicks.
  Newly opened menus are grey rectangles.

  The lines underlining menu hotkeys do NOT disappear.

  In the attached screenshot, you can clearly see which buttons I have
  waved the mouse over, and which I have not.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar 19 19:51:37 2015
  InstallationDate: Installed on 2015-03-05 (14 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago)

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

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

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

[Christoph Ra]

apport information

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

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

Title:
  X fonts and widgets disappear after suspend/resume cycle

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  After a suspend/resume cycle, the screen comes up normally, but every
  time I move my mouse over a piece of text, button, widget, etc, the
  text vanishes and it's replaced by a plain rectangle.

  This does not affect xterm, but it does affect any GTK apps, firefox,
  etc.

  xfce-panel vanishes, although it's still responding to mouse-clicks.
  Newly opened menus are grey rectangles.

  The lines underlining menu hotkeys do NOT disappear.

  In the attached screenshot, you can clearly see which buttons I have
  waved the mouse over, and which I have not.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar 19 19:51:37 2015
  InstallationDate: Installed on 2015-03-05 (14 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago)

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

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

[Touch-packages] [Bug 1434351] DpkgLog.txt

[Christoph Ra]

apport information

** Attachment added: "DpkgLog.txt"
   
https://bugs.launchpad.net/bugs/1434351/+attachment/4652661/+files/DpkgLog.txt

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

Title:
  X fonts and widgets disappear after suspend/resume cycle

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  After a suspend/resume cycle, the screen comes up normally, but every
  time I move my mouse over a piece of text, button, widget, etc, the
  text vanishes and it's replaced by a plain rectangle.

  This does not affect xterm, but it does affect any GTK apps, firefox,
  etc.

  xfce-panel vanishes, although it's still responding to mouse-clicks.
  Newly opened menus are grey rectangles.

  The lines underlining menu hotkeys do NOT disappear.

  In the attached screenshot, you can clearly see which buttons I have
  waved the mouse over, and which I have not.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar 19 19:51:37 2015
  InstallationDate: Installed on 2015-03-05 (14 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago)

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

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

[Touch-packages] [Bug 1434351] Dependencies.txt

[Christoph Ra]

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1434351/+attachment/4652660/+files/Dependencies.txt

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

Title:
  X fonts and widgets disappear after suspend/resume cycle

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  After a suspend/resume cycle, the screen comes up normally, but every
  time I move my mouse over a piece of text, button, widget, etc, the
  text vanishes and it's replaced by a plain rectangle.

  This does not affect xterm, but it does affect any GTK apps, firefox,
  etc.

  xfce-panel vanishes, although it's still responding to mouse-clicks.
  Newly opened menus are grey rectangles.

  The lines underlining menu hotkeys do NOT disappear.

  In the attached screenshot, you can clearly see which buttons I have
  waved the mouse over, and which I have not.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar 19 19:51:37 2015
  InstallationDate: Installed on 2015-03-05 (14 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago)

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

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

[Touch-packages] [Bug 1434351] Re: X fonts and widgets disappear after suspend/resume cycle

[Christoph Ra]

ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: XFCE
DistUpgraded: 2016-04-29 02:46:57,762 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory))
DistroCodename: xenial
DistroRelease: Ubuntu 16.04
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics 
Controller [144d:c0d3]
InstallationDate: Installed on 2013-11-15 (897 days ago)
InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 900X3C/900X3D/900X4C/900X4D
Package: xorg 1:7.7+13ubuntu3
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=737b7c59-acfa-4ca4-9089-8061376751a5 ro acpi_osi=Linux 
i915.i915_enable_rc6=1 i915.i915_enable_fbc=1 i915.lvds_downclock=1 quiet 
splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Tags:  xenial ubuntu
Uname: Linux 4.4.0-21-generic x86_64
UpgradeStatus: Upgraded to xenial on 2016-04-29 (2 days ago)
UserGroups: adm cdrom dip fuse libvirtd lpadmin netdev nopasswdlogin plugdev 
sambashare scanner sudo video
_MarkForUpload: True
dmi.bios.date: 02/08/2013
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: P06AAC
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: SAMSUNG_NP1234567890
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: FAB1
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP06AAC:bd02/08/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn900X3C/900X3D/900X4C/900X4D:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
dmi.product.name: 900X3C/900X3D/900X4C/900X4D
dmi.product.version: 0.1
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2


** Tags added: apport-collected ubuntu

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

Title:
  X fonts and widgets disappear after suspend/resume cycle

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  After a suspend/resume cycle, the screen comes up normally, but every
  time I move my mouse over a piece of text, button, widget, etc, the
  text vanishes and it's replaced by a plain rectangle.

  This does not affect xterm, but it does affect any GTK apps, firefox,
  etc.

  xfce-panel vanishes, although it's still responding to mouse-clicks.
  Newly opened menus are grey rectangles.

  The lines underlining menu hotkeys do NOT disappear.

  In the attached screenshot, you can clearly see which buttons I have
  waved the mouse over, and which I have not.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar 19 19:51:37 2015
  InstallationDate: Installed on 2015-03-05 (14 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago)

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

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

[Touch-packages] [Bug 1434351] Re: X fonts and widgets disappear after suspend/resume cycle

[Christoph Ra]

** Changed in: xorg (Ubuntu)
   Status: Expired => Confirmed

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

Title:
  X fonts and widgets disappear after suspend/resume cycle

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  After a suspend/resume cycle, the screen comes up normally, but every
  time I move my mouse over a piece of text, button, widget, etc, the
  text vanishes and it's replaced by a plain rectangle.

  This does not affect xterm, but it does affect any GTK apps, firefox,
  etc.

  xfce-panel vanishes, although it's still responding to mouse-clicks.
  Newly opened menus are grey rectangles.

  The lines underlining menu hotkeys do NOT disappear.

  In the attached screenshot, you can clearly see which buttons I have
  waved the mouse over, and which I have not.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar 19 19:51:37 2015
  InstallationDate: Installed on 2015-03-05 (14 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago)

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

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

[Touch-packages] [Bug 1502524] Re: Bluetooth - Ubuntu Touch

[Christoph Czernohous]

I have the same issue. Bluetooth cannot be enabled. Is this different
bluetooth hardware compared to the 'official' supported Nexus 7?

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

Title:
  Bluetooth - Ubuntu Touch

Status in bluetooth-touch package in Ubuntu:
  Confirmed

Bug description:
  Hi I am using a Nexus 7 - LTE (ie I get the images from http://system-
  image.tasemnice.eu/ubuntu-touch)

  While the bluetooth icon is there, it doesn't stay on.

  I can check the box, but the device does not become discoverable.

  I have just seen Michael Hall's video using a bluetooth mouse (I
  assume a keyboard will have the same effect), and am keen to utilise
  this.

  Thanks
  Steven

  PS Kari on ask ubuntu has had the same problem

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluetooth-touch/+bug/1502524/+subscriptions

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

[Touch-packages] [Bug 1329191] Re: [MacBookAir5, 1, Cirrus Logic CS4206, Blue Line In, Rear] Line In using TRRS plug does not work correctly

[christoph]

hm. for my model (MacBook 6,1) there are no pincfg table and I can't find the 
subsystem Id. 
Closest is 0x106b5600, "MacBookAir 5,2". Unfortunately there is no pincfg table 
for this model either + none for the generic "Apple" for 0x106b SSIDs

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

Title:
  [MacBookAir5,1, Cirrus Logic CS4206, Blue Line In, Rear] Line In using
  TRRS plug does not work correctly

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Microphone connected via TRRS plug on Macbook Air 5,1 is not
  recognised. Selecting "Analogue In" in Pulseaudio mixer is same as
  selecting "Microphone" - i.e. sounds recorded are always the Internal
  microphone, and not the microphone connected via the TRRS plug. When
  using OSX however, the TRRS microphone works correctly.

  Have tried booting Live CDs of 12.04, 13.04, and 14.04, and even tried
  upgrading kernel to 3.15, and problem persists.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  scrosby2172 F pulseaudio
   /dev/snd/pcmC0D0c:   scrosby2172 F...m pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jun 12 16:58:10 2014
  InstallationDate: Installed on 2014-02-24 (107 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64+mac (20140223)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Blue Line In, Rear
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
failed
  Symptom_Type: Only some of inputs are working
  Title: [MacBookAir5,1, Cirrus Logic CS4206, Blue Line In, Rear] Recording 
problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/27/2012
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBA51.88Z.00EF.B02.1211271028
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-66F35F19FE2A0D05
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookAir5,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-66F35F19FE2A0D05
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBA51.88Z.00EF.B02.1211271028:bd11/27/2012:svnAppleInc.:pnMacBookAir5,1:pvr1.0:rvnAppleInc.:rnMac-66F35F19FE2A0D05:rvrMacBookAir5,1:cvnAppleInc.:ct10:cvrMac-66F35F19FE2A0D05:
  dmi.product.name: MacBookAir5,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  modified.conffile..etc.modprobe.d.alsa.base.conf: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1329191/+subscriptions

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

[Touch-packages] [Bug 1329191] Re: [MacBookAir5, 1, Cirrus Logic CS4206, Blue Line In, Rear] Line In using TRRS plug does not work correctly

[christoph]

sorry, this is beyond my skill, and I didn't find a guide to follow. 
Maybe you can give me a little bit more precise instructions on what to do with 
the values. 
I think I found the relevant part of the windows .inf file (Section starting 
with [CDB4206DM12PinConfigOverride]), i think I have to switch the bytes e.g. 
0x1,10,1c,97,00 will become 00 97 1c 10 and I found a guide describing what 
those hex digits mean (comment #15 on 
http://www.insanelymac.com/forum/topic/275086-pin-config-patching-voodoohda-0272-project-os-x-branch/)

the info retrieved from the pins matches with the comments of the
windows .inf file.

But now? What do I do with these hex codes. Which of these and where do
I have to patch my audio driver to recognize the TRRS input signal?

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

Title:
  [MacBookAir5,1, Cirrus Logic CS4206, Blue Line In, Rear] Line In using
  TRRS plug does not work correctly

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Microphone connected via TRRS plug on Macbook Air 5,1 is not
  recognised. Selecting "Analogue In" in Pulseaudio mixer is same as
  selecting "Microphone" - i.e. sounds recorded are always the Internal
  microphone, and not the microphone connected via the TRRS plug. When
  using OSX however, the TRRS microphone works correctly.

  Have tried booting Live CDs of 12.04, 13.04, and 14.04, and even tried
  upgrading kernel to 3.15, and problem persists.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  scrosby2172 F pulseaudio
   /dev/snd/pcmC0D0c:   scrosby2172 F...m pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jun 12 16:58:10 2014
  InstallationDate: Installed on 2014-02-24 (107 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64+mac (20140223)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Blue Line In, Rear
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
failed
  Symptom_Type: Only some of inputs are working
  Title: [MacBookAir5,1, Cirrus Logic CS4206, Blue Line In, Rear] Recording 
problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/27/2012
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBA51.88Z.00EF.B02.1211271028
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-66F35F19FE2A0D05
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookAir5,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-66F35F19FE2A0D05
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBA51.88Z.00EF.B02.1211271028:bd11/27/2012:svnAppleInc.:pnMacBookAir5,1:pvr1.0:rvnAppleInc.:rnMac-66F35F19FE2A0D05:rvrMacBookAir5,1:cvnAppleInc.:ct10:cvrMac-66F35F19FE2A0D05:
  dmi.product.name: MacBookAir5,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  modified.conffile..etc.modprobe.d.alsa.base.conf: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1329191/+subscriptions

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

[Touch-packages] [Bug 1329191] Re: [MacBookAir5, 1, Cirrus Logic CS4206, Blue Line In, Rear] Line In using TRRS plug does not work correctly

[christoph]

Honestly I don't know at which values I have to look in this inf file
(and then what to do with them).

I tried to override x0c pin with hdajackretask as external Microphone which 
leaves me with 2 input devices in Settings -> Sound and 2 capture devices in 
alsamixer as well. Fiddling around with unmuting/muting etc.: they both don't 
produce signals (not even the internal laptop mic). 
I tried different settings for hdajackretask with pin x0c but they didn't 
affect sound devices at all. 
Overriding other pins mutes the headset + internal speakers (and don't affect 
input devices).

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

Title:
  [MacBookAir5,1, Cirrus Logic CS4206, Blue Line In, Rear] Line In using
  TRRS plug does not work correctly

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Microphone connected via TRRS plug on Macbook Air 5,1 is not
  recognised. Selecting "Analogue In" in Pulseaudio mixer is same as
  selecting "Microphone" - i.e. sounds recorded are always the Internal
  microphone, and not the microphone connected via the TRRS plug. When
  using OSX however, the TRRS microphone works correctly.

  Have tried booting Live CDs of 12.04, 13.04, and 14.04, and even tried
  upgrading kernel to 3.15, and problem persists.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  scrosby2172 F pulseaudio
   /dev/snd/pcmC0D0c:   scrosby2172 F...m pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jun 12 16:58:10 2014
  InstallationDate: Installed on 2014-02-24 (107 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64+mac (20140223)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Blue Line In, Rear
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
failed
  Symptom_Type: Only some of inputs are working
  Title: [MacBookAir5,1, Cirrus Logic CS4206, Blue Line In, Rear] Recording 
problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/27/2012
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBA51.88Z.00EF.B02.1211271028
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-66F35F19FE2A0D05
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookAir5,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-66F35F19FE2A0D05
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBA51.88Z.00EF.B02.1211271028:bd11/27/2012:svnAppleInc.:pnMacBookAir5,1:pvr1.0:rvnAppleInc.:rnMac-66F35F19FE2A0D05:rvrMacBookAir5,1:cvnAppleInc.:ct10:cvrMac-66F35F19FE2A0D05:
  dmi.product.name: MacBookAir5,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  modified.conffile..etc.modprobe.d.alsa.base.conf: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1329191/+subscriptions

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

[Touch-packages] [Bug 1329191] Re: [MacBookAir5, 1, Cirrus Logic CS4206, Blue Line In, Rear] Line In using TRRS plug does not work correctly

[christoph]

*push*

this happens on the MacBook 6,1 (late 2009) as well. It has the same
Cirrus CS4206.

I just tested the most recent alsa-daily which builds for wily/amd64 without 
effect. Internal Speakers, Internal Mic, Headphones all work - TRRS mic doesn't 
work (Mac OS X supports exactly this Headset device out of the box). 
I'm using 15.10 GNOME Ubuntu. In sound settings I can only activate the 
internal mic and don't even see any external (as with output where the label of 
the output device automatically changes if the headset is connected). 

uname -r
Linux macbook 4.2.0-23-generic #28-Ubuntu SMP Sun Dec 27 17:47:31 UTC 2015 
x86_64 x86_64 x86_64 GNU/Linux

running alsa-info.sh (with headset connected) =>
 Your ALSA information is located at 
http://www.alsa-project.org/db/?f=7556cfd21195211e5d8bd44184d481b0bd26d892

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

Title:
  [MacBookAir5,1, Cirrus Logic CS4206, Blue Line In, Rear] Line In using
  TRRS plug does not work correctly

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Microphone connected via TRRS plug on Macbook Air 5,1 is not
  recognised. Selecting "Analogue In" in Pulseaudio mixer is same as
  selecting "Microphone" - i.e. sounds recorded are always the Internal
  microphone, and not the microphone connected via the TRRS plug. When
  using OSX however, the TRRS microphone works correctly.

  Have tried booting Live CDs of 12.04, 13.04, and 14.04, and even tried
  upgrading kernel to 3.15, and problem persists.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  scrosby2172 F pulseaudio
   /dev/snd/pcmC0D0c:   scrosby2172 F...m pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jun 12 16:58:10 2014
  InstallationDate: Installed on 2014-02-24 (107 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64+mac (20140223)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Blue Line In, Rear
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
failed
  Symptom_Type: Only some of inputs are working
  Title: [MacBookAir5,1, Cirrus Logic CS4206, Blue Line In, Rear] Recording 
problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/27/2012
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBA51.88Z.00EF.B02.1211271028
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-66F35F19FE2A0D05
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookAir5,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-66F35F19FE2A0D05
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBA51.88Z.00EF.B02.1211271028:bd11/27/2012:svnAppleInc.:pnMacBookAir5,1:pvr1.0:rvnAppleInc.:rnMac-66F35F19FE2A0D05:rvrMacBookAir5,1:cvnAppleInc.:ct10:cvrMac-66F35F19FE2A0D05:
  dmi.product.name: MacBookAir5,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  modified.conffile..etc.modprobe.d.alsa.base.conf: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1329191/+subscriptions

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

[Touch-packages] [Bug 1098738] Re: apt-get source only checks md5 hashes in Sources files

[Christoph Anton Mitterer]

Hey Julian...

How has this been fixed eventually?

As I proposed, that all available hash algos are verified and if any
fails consider it completely failed,... plus a minimum hash algo (that
is not md5 or sha1 ^^)?

Cheers,
Chris.

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

Title:
  apt-get source only checks md5 hashes in Sources files

Status in apt package in Ubuntu:
  Fix Released

Bug description:
  'apt-get source' only validates the md5 hash in the Sources file.
  Ideally, it should check the sha hashes also.

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

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

[Touch-packages] [Bug 1430888] Re: DRI_PRIME with radeon/intel windows do not draw

[Christoph Buchner]

I see this too with Steam, only for me the log string is " reporting 6 8 17 
141". Ctrl-Win-D workaround seems to work. 
Any updates on this in the meantime?

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

Title:
  DRI_PRIME with radeon/intel windows do not draw

Status in X.Org X server:
  New
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 15.04 and Xorg version 1:7.7+7ubuntu2

  Step to reproduce:
  start "DRI_PRIME=1 steam" (or any other complex 3D program like minecraft)

  What is expected:
  the program should show it's window(s), those should have the same content as 
if started without "DRI_PRIME".

  What actually happens:
  most times the program just shows a "freezed" version of the background the 
window appeared on.

  Additional Informations:
  I have the newest BIOS version.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.16.2-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Mar 11 17:01:13 2015
  DistUpgraded: Fresh install
  DistroCodename: vivid
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.248+bdcom, 3.18.0-13-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 3.19.0-7-generic, x86_64: installed
   virtualbox, 4.3.24, 3.19.0-7-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:1486]
   Advanced Micro Devices, Inc. [AMD/ATI] Park [Mobility Radeon HD 
5430/5450/5470] [1002:68e0] (rev ff) (prog-if ff)
  MachineType: Hewlett-Packard HP TouchSmart tm2 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-7-generic 
root=UUID=35d0b52c-aa5e-48d2-9eec-f7a6036f2a56 ro splash drm.rnodes=1 
vt.handoff=7
  SourcePackage: xorg
  SystemImageInfo:
   current build number: 0
   device name: 
   channel: daily
   last update: Unknown
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/18/2011
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.25
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1486
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 83.20
  dmi.chassis.asset.tag: CNU0250216
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.25:bd02/18/2011:svnHewlett-Packard:pnHPTouchSmarttm2NotebookPC:pvr048920252A2000122:rvnHewlett-Packard:rn1486:rvr83.20:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP TouchSmart tm2 Notebook PC
  dmi.product.version: 048920252A2000122
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.1+15.04.20150303-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.59-0ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.0-0ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.0-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.2.901-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Tue Mar 10 10:39:26 2015
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   38164 
   vendor AUO
  xserver.version: 2:1.16.2.901-1ubuntu4

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1430888/+subscriptions

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

[Touch-packages] [Bug 1425891] Re: Xorg radeon freezes if firefix loads big images

[Christoph]

I upgraded to the LTS stack and now firefox loads the mentioned URLs
without Xorg freezing the desktop. Thank you very much for your help.

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

Title:
  Xorg radeon freezes if firefix loads big images

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  If I open each of this URLs

  
http://canon-premium.webcdn.stream.ne.jp/www09/canon-premium/eosd/samples/eos5dsr/downloads/02.jpg
  
http://canon-premium.webcdn.stream.ne.jp/www09/canon-premium/eosd/samples/eos5ds/downloads/02.jpg

  in a firefox 36.0 on a Xorg Server of 1.15.1 with a R9 270 and a
  Ubuntu 14.04.1  AMD64 the desktop freezes. I can only move the mouse
  pointer, although the the login via SSH is still possible and works
  fine. By restarting the Xorg Server I can gain control over the local
  terminal again.

  This happens with the radeon driver, but not with the fglrx driver.
  The problem did not manifest itself with other applications.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Uname: Linux 3.13.0-45-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Feb 26 11:19:49 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Curacao PRO [Radeon R9 270] 
[1002:6811] (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:3050]
  InstallationDate: Installed on 2014-04-22 (309 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-45-generic 
root=UUID=e0df56bb-b5a5-4b2c-9f89-ce5ff2e3b019 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLogOld:
   
  dmi.bios.date: 12/17/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.70
  dmi.board.name: Z97 Extreme6
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.70:bd12/17/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1~ubuntu2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
  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.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Thu Feb 26 11:18:17 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.1-0ubuntu2.7
  xserver.video_driver: radeon

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

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

[Touch-packages] [Bug 1425891] Re: Xorg radeon freezes if firefix loads big images

[Christoph]

I tested the vivid-desktop-amd64.iso of march 6th as a live cd and the
firefox loads the big images without a problem.

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

Title:
  Xorg radeon freezes if firefix loads big images

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  If I open each of this URLs

  
http://canon-premium.webcdn.stream.ne.jp/www09/canon-premium/eosd/samples/eos5dsr/downloads/02.jpg
  
http://canon-premium.webcdn.stream.ne.jp/www09/canon-premium/eosd/samples/eos5ds/downloads/02.jpg

  in a firefox 36.0 on a Xorg Server of 1.15.1 with a R9 270 and a
  Ubuntu 14.04.1  AMD64 the desktop freezes. I can only move the mouse
  pointer, although the the login via SSH is still possible and works
  fine. By restarting the Xorg Server I can gain control over the local
  terminal again.

  This happens with the radeon driver, but not with the fglrx driver.
  The problem did not manifest itself with other applications.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Uname: Linux 3.13.0-45-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Feb 26 11:19:49 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Curacao PRO [Radeon R9 270] 
[1002:6811] (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:3050]
  InstallationDate: Installed on 2014-04-22 (309 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-45-generic 
root=UUID=e0df56bb-b5a5-4b2c-9f89-ce5ff2e3b019 ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLogOld:
   
  dmi.bios.date: 12/17/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.70
  dmi.board.name: Z97 Extreme6
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.70:bd12/17/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1~ubuntu2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.3
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
  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.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Thu Feb 26 11:18:17 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.15.1-0ubuntu2.7
  xserver.video_driver: radeon

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

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

[Touch-packages] [Bug 1425891] [NEW] Xorg radeon freezes if firefix loads big images

[Christoph]

Public bug reported:

If I open each of this URLs

http://canon-premium.webcdn.stream.ne.jp/www09/canon-premium/eosd/samples/eos5dsr/downloads/02.jpg
http://canon-premium.webcdn.stream.ne.jp/www09/canon-premium/eosd/samples/eos5ds/downloads/02.jpg

in a firefox 36.0 on a Xorg Server of 1.15.1 with a R9 270 and a Ubuntu
14.04.1  AMD64 the desktop freezes. I can only move the mouse pointer,
although the the login via SSH is still possible and works fine. By
restarting the Xorg Server I can gain control over the local terminal
again.

This happens with the radeon driver, but not with the fglrx driver. The
problem did not manifest itself with other applications.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
Uname: Linux 3.13.0-45-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.7
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Thu Feb 26 11:19:49 2015
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Curacao PRO [Radeon R9 270] [1002:6811] 
(prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:3050]
InstallationDate: Installed on 2014-04-22 (309 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-45-generic 
root=UUID=e0df56bb-b5a5-4b2c-9f89-ce5ff2e3b019 ro quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
XorgLogOld:
 
dmi.bios.date: 12/17/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.70
dmi.board.name: Z97 Extreme6
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.70:bd12/17/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme6:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.56-1~ubuntu2
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.3
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
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.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Thu Feb 26 11:18:17 2015
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.15.1-0ubuntu2.7
xserver.video_driver: radeon

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


** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu

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

Title:
  Xorg radeon freezes if firefix loads big images

Status in xorg package in Ubuntu:
  New

Bug description:
  If I open each of this URLs

  
http://canon-premium.webcdn.stream.ne.jp/www09/canon-premium/eosd/samples/eos5dsr/downloads/02.jpg
  
http://canon-premium.webcdn.stream.ne.jp/www09/canon-premium/eosd/samples/eos5ds/downloads/02.jpg

  in a firefox 36.0 on a Xorg Server of 1.15.1 with a R9 270 and a
  Ubuntu 14.04.1  AMD64 the desktop freezes. I can only move the mouse
  pointer, although the the login via SSH is still possible and works
  fine. By restarting the Xorg Server I can gain control over the local
  terminal again.

  This happens with the radeon driver, but not with the fglrx driver.
  The problem did not manifest itself with other applications.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Uname: Linux 3.13.0-45-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: 

[Touch-packages] [Bug 1307883] Re: ca-certificates-java misses runtime dependency on initscripts

[Hans-Christoph Steiner]

I'm seeing this same issue on a minimal Ubuntu/trusty chroot, where I
deliberately didn't want initscripts and upstart installed. Using
minimal chroots is very useful for running automated build
infrastructure.  The chroots can serve as stand-ins for full systems or
VMs.  Since the base system provides the whole system, including
daemons, init, etc. the chroot does not need this stuff, and indeed it
can get in the way.

This worked before, since I was able to set up this chroot a while back
and use it.  I think I set it up around Sept 2014.

Here's the error:
Setting up openjdk-7-jre-headless:amd64 (7u71-2.5.3-0ubuntu0.14.04.1) ...
/var/lib/dpkg/info/openjdk-7-jre-headless:amd64.postinst: 18: 
/var/lib/dpkg/info/openjdk-7-jre-headless:amd64.postinst: mountpoint: not found
the java command requires a mounted proc fs (/proc).
dpkg: error processing package openjdk-7-jre-headless:amd64 (--configure):
 subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of openjdk-7-jre:amd64:
 openjdk-7-jre:amd64 depends on openjdk-7-jre-headless (= 
7u71-2.5.3-0ubuntu0.14.04.1); however:
  Package openjdk-7-jre-headless:amd64 is not configured yet.

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

Title:
  ca-certificates-java misses runtime dependency on initscripts

Status in ca-certificates-java package in Ubuntu:
  Confirmed
Status in openjdk-7 package in Ubuntu:
  Confirmed
Status in util-linux package in Ubuntu:
  Triaged

Bug description:
  Jitsi build-depends on openjdk-7-jre but the package fails to install
  in pbuilder and thus I currently cannot build the package.  Here is
  the output I get while I am logged in to the trusty chroot.

  # aptitude install default-jdk
  [...]
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  A package failed to install.  Trying to recover:
  Setting up ca-certificates-java (20130815ubuntu1) ...
  /var/lib/dpkg/info/ca-certificates-java.postinst: line 90: mountpoint: 
command not found
  the keytool command requires a mounted proc fs (/proc).
  dpkg: error processing package ca-certificates-java (--configure):
   subprocess installed post-installation script returned error exit status 1
  Setting up openjdk-7-jre-headless:i386 (7u51-2.4.6-1ubuntu4) ...
  /var/lib/dpkg/info/openjdk-7-jre-headless:i386.postinst: 18: 
/var/lib/dpkg/info/openjdk-7-jre-headless:i386.postinst: mountpoint: not found
  the java command requires a mounted proc fs (/proc).
  dpkg: error processing package openjdk-7-jre-headless:i386 (--configure):
   subprocess installed post-installation script returned error exit status 1
  Setting up default-jre-headless (2:1.7-51) ...
  dpkg: dependency problems prevent configuration of openjdk-7-jre:i386:
   openjdk-7-jre:i386 depends on openjdk-7-jre-headless (= 
7u51-2.4.6-1ubuntu4); however:
    Package openjdk-7-jre-headless:i386 is not configured yet.

  dpkg: error processing package openjdk-7-jre:i386 (--configure):
   dependency problems - leaving unconfigured
  Setting up default-jre (2:1.7-51) ...
  dpkg: dependency problems prevent configuration of openjdk-7-jdk:i386:
   openjdk-7-jdk:i386 depends on openjdk-7-jre (= 7u51-2.4.6-1ubuntu4); however:
    Package openjdk-7-jre:i386 is not configured yet.

  dpkg: error processing package openjdk-7-jdk:i386 (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of default-jdk:
   default-jdk depends on openjdk-7-jdk (= 7~u3-2.1.1); however:
    Package openjdk-7-jdk:i386 is not configured yet.

  dpkg: error processing package default-jdk (--configure):
   dependency problems - leaving unconfigured
  Processing triggers for ca-certificates (20130906ubuntu2) ...
  Updating certificates in /etc/ssl/certs... 0 added, 0 removed; done.
  Running hooks in /etc/ca-certificates/update.d
  /etc/ca-certificates/update.d/jks-keystore: 33: 
/etc/ca-certificates/update.d/jks-keystore: mountpoint: not found
  the keytool command requires a mounted proc fs (/proc).
  E: /etc/ca-certificates/update.d/jks-keystore exited with code 1.
  done.
  Errors were encountered while processing:
   ca-certificates-java
   openjdk-7-jre-headless:i386
   openjdk-7-jre:i386
   openjdk-7-jdk:i386
   default-jdk

  # mount
  /proc on /proc type proc (rw,relatime)
  tmpfs on /run/shm type tmpfs (rw,relatime)
  /dev/pts on /dev/pts type devpts 
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates-java/+bug/1307883/+subscriptions

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

[Touch-packages] [Bug 1388647] Re: DRI_PRIME=1 has no effect in Ubuntu 14.10

[Christoph Buchner]

Alain's workaround also works for me (on Intel+AMD)

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

Title:
  DRI_PRIME=1 has no effect in Ubuntu 14.10

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  On an Optimus laptop with both GPUs enabled, having run this command
  so that the Nvidia GPU can be used to offload 3D work from the Intel
  GPU:

  ```
  xrandr --setprovideroffloadsink nouveau Intel
  ```

  Then running this command:

  ```
  DRI_PRIME=1 glxinfo | grep OpenGL vendor string
  ```

  provides the incorrect output:

  ```
  OpenGL vendor string: Intel Open Source Technology Center
  ```

  when it should actually show that the Nouveau driver is in use for the
  program.

  This worked previously in Ubuntu 14.04. Apart from only having a 3.16
  kernel (instead of 3.17) Ubuntu 14.10 actually supports recent enough
  versions of the requisite packages necesarry to get DRI 3 offloading
  support, so perhaps this is part of the problem.

  Or, more likely, I notice a Nouveau failure after startup, and then
  again after running xrandr commands, for example:

  ```
  [  170.912483] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [  217.550205] thinkpad_acpi: EC reports that Thermal Table has changed
  [  223.857442] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [  223.858395] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [  223.860200] nouveau E[PBUS][:01:00.0] MMIO read of 0x 
FAULT at 0x002140 [ !ENGINE ]
  [  224.654622] thinkpad_acpi: EC reports that Thermal Table has changed
  [  825.172094] thinkpad_acpi: EC reports that Thermal Table has changed
  [  831.132156] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [  831.133030] ACPI Warning: \_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95)
  [  831.134832] nouveau E[PBUS][:01:00.0] MMIO read of 0x 
FAULT at 0x002140 [ !ENGINE ]
  ```

  Perhaps this is just a regression in either the Nouveau or Intel
  drivers for my hardware. I'm using a Lenovo T430. I can confirm that
  I'm able to start the laptop without errors when I only enable the
  Intel GPU or NVidia GPU separately, and only see this error when both
  GPUs are enabled simultaneously.

  Extra Info:

  1: Description:   Ubuntu 14.10
  Release:  14.10

  2: N/A

  3: The text 'nouveau' should have appeared in the output of the
  command.

  4: The text 'Intel' appeared in the output of the command.

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

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

[Touch-packages] [Bug 1410495] [NEW] Battery indicator goes Critical Red with more than 1 hour battery left

[Christoph Buchner]

Public bug reported:

On my current laptop, the battery indicator shows a red-with-a-little-
left icon when there is more than an hour left in the battery, which is
not really appropriate for a critical battery warning.

This bug is probably a regression of #743823, and I was asked to create a new 
bug by @mpt:
 Christoph, yes, please report a new bug including a screenshot. On phones we 
 may have to color by percentage, but on PCs we can and should color by time 
 remaining to avoid false alarms.

A screenshot is attached. Unfortunately I didn't realize at the time
that the screenshotter does not record open menus, so you'll have to
take my word that the time remaining in the indicator menu was at  1
hour. I can redo the screenshot, if necessary.

fwiw, the transition levels (based on minutes left) proposed in the bug
description of #743823 sound good to me.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: indicator-power 12.10.6+14.10.20141015-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
Uname: Linux 3.16.0-28-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Jan 13 21:08:43 2015
InstallationDate: Installed on 2014-12-22 (22 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2)
SourcePackage: indicator-power
UpgradeStatus: Upgraded to utopic on 2014-12-22 (21 days ago)

** Affects: indicator-power (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug third-party-packages utopic

** Attachment added: indicator-bug.png
   
https://bugs.launchpad.net/bugs/1410495/+attachment/4297830/+files/indicator-bug.png

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

Title:
  Battery indicator goes Critical Red with more than 1 hour battery left

Status in indicator-power package in Ubuntu:
  New

Bug description:
  On my current laptop, the battery indicator shows a red-with-a-little-
  left icon when there is more than an hour left in the battery, which
  is not really appropriate for a critical battery warning.

  This bug is probably a regression of #743823, and I was asked to create a new 
bug by @mpt:
   Christoph, yes, please report a new bug including a screenshot. On phones 
we may have to color by percentage, but on PCs we can and should color by time 
remaining to avoid false alarms.

  A screenshot is attached. Unfortunately I didn't realize at the time
  that the screenshotter does not record open menus, so you'll have to
  take my word that the time remaining in the indicator menu was at  1
  hour. I can redo the screenshot, if necessary.

  fwiw, the transition levels (based on minutes left) proposed in the
  bug description of #743823 sound good to me.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: indicator-power 12.10.6+14.10.20141015-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-28-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jan 13 21:08:43 2015
  InstallationDate: Installed on 2014-12-22 (22 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  SourcePackage: indicator-power
  UpgradeStatus: Upgraded to utopic on 2014-12-22 (21 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1410495/+subscriptions

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

[Touch-packages] [Bug 743823] Re: Battery indicator goes Critical Red with 1:10 battery left

[Christoph Buchner]

argh, why did the auto-linking of the bug id not work? here, have a link
instead: https://bugs.launchpad.net/ubuntu/+source/indicator-
power/+bug/1410495

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

Title:
  Battery indicator goes Critical Red with 1:10 battery left

Status in Ayatana Design:
  Fix Released
Status in The Power Indicator:
  Fix Released
Status in indicator-power package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: ubuntu-mono

  Since the Ubuntu-Monochrome 0.0.26 upload, the battery status icon now
  goes critical red with over an hour to spare.

  We need to confirm this in Ayatana-Design, but my hunch is the
  following would be more useful:

    external power: normal text colour (ivory/chocolate for Ambiance/Radiance)
    =1:00 remaining: normal text colour
     1:00 remaining: orange non-critical warning
    =0:10 remaining: red critical warning
    =0:02 remaining: red critical warning if suspend/hibernate action selected 
and proven working
    =0:02 remaining: red critical (flashing) warning if simply going to 
power-off

  Additionally, the Ubuntu Mono 0.0.26 change uses a battery icon with
  no fill for empty.  This is not as clear to the user as an icon that
  instead uses a very small fill at end of the battery, even for zero.
  This is more intuitive as it makes it clear that the icon is used as a
  percentage indicator;  with an empty fill the user must already know
  this for empty to be useful as a relative indicator.

  At the moment, the Red with some left state seen at 1:10 remaining
  is far more visible to the user than the (more serious) completely
  empty icon.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/743823/+subscriptions

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

[Touch-packages] [Bug 1410495] Re: Battery indicator goes Critical Red with more than 1 hour battery left

[Christoph Buchner]

The times left shown in the UPowerDump file will not be representative,
as the bug report happened quite some time after I originally made the
screenshot.

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

Title:
  Battery indicator goes Critical Red with more than 1 hour battery left

Status in indicator-power package in Ubuntu:
  New

Bug description:
  On my current laptop, the battery indicator shows a red-with-a-little-
  left icon when there is more than an hour left in the battery, which
  is not really appropriate for a critical battery warning.

  This bug is probably a regression of #743823, and I was asked to create a new 
bug by @mpt:
   Christoph, yes, please report a new bug including a screenshot. On phones 
we may have to color by percentage, but on PCs we can and should color by time 
remaining to avoid false alarms.

  A screenshot is attached. Unfortunately I didn't realize at the time
  that the screenshotter does not record open menus, so you'll have to
  take my word that the time remaining in the indicator menu was at  1
  hour. I can redo the screenshot, if necessary.

  fwiw, the transition levels (based on minutes left) proposed in the
  bug description of #743823 sound good to me.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: indicator-power 12.10.6+14.10.20141015-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
  Uname: Linux 3.16.0-28-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jan 13 21:08:43 2015
  InstallationDate: Installed on 2014-12-22 (22 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  SourcePackage: indicator-power
  UpgradeStatus: Upgraded to utopic on 2014-12-22 (21 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1410495/+subscriptions

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

[Touch-packages] [Bug 1388235] Re: Battery icon turns red at 30%

[Christoph Buchner]

Also, please keep e.g. laptop use in mind when designing this. I'm currently on 
a laptop, and the battery indicator shows a red-with-a-little-left icon, when I 
have 1h10min of battery left (which feels a bit ridiculous). The percentage is 
at 22%. 
See also the previous bug #743823, which apparently has regressed since 2011?

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

Title:
  Battery icon turns red at 30%

Status in Ubuntu UX bugs:
  Confirmed
Status in indicator-power package in Ubuntu:
  In Progress
Status in ubuntu-themes package in Ubuntu:
  In Progress

Bug description:
  This seems a bit pessimistic since the phone still has a great deal of
  capacity and time left, perhaps 15 or 20% is a better threshold

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1388235/+subscriptions

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

[Touch-packages] [Bug 743823] Re: Battery indicator goes Critical Red with 1:10 battery left

[Christoph Buchner]

Has this bug regressed since 2011? My battery indicator shows a red-
with-a-little-left icon, when I have 1h10min of battery left (so
definitely over 30min). The percentage is at 22%. (on ubuntu 14.10)

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

Title:
  Battery indicator goes Critical Red with 1:10 battery left

Status in Ayatana Design:
  Fix Released
Status in The Power Indicator:
  Fix Released
Status in indicator-power package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: ubuntu-mono

  Since the Ubuntu-Monochrome 0.0.26 upload, the battery status icon now
  goes critical red with over an hour to spare.

  We need to confirm this in Ayatana-Design, but my hunch is the
  following would be more useful:

    external power: normal text colour (ivory/chocolate for Ambiance/Radiance)
    =1:00 remaining: normal text colour
     1:00 remaining: orange non-critical warning
    =0:10 remaining: red critical warning
    =0:02 remaining: red critical warning if suspend/hibernate action selected 
and proven working
    =0:02 remaining: red critical (flashing) warning if simply going to 
power-off

  Additionally, the Ubuntu Mono 0.0.26 change uses a battery icon with
  no fill for empty.  This is not as clear to the user as an icon that
  instead uses a very small fill at end of the battery, even for zero.
  This is more intuitive as it makes it clear that the icon is used as a
  percentage indicator;  with an empty fill the user must already know
  this for empty to be useful as a relative indicator.

  At the moment, the Red with some left state seen at 1:10 remaining
  is far more visible to the user than the (more serious) completely
  empty icon.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/743823/+subscriptions

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

[Touch-packages] [Bug 1400839] [NEW] Shutdown / Poweroff does not spin down harddisk

[Christoph Lorenz]

Public bug reported:

When shutting down, my harddisk is not properly powered off before or
spun down, so that it gives a sqeeking sound, when the shutdown process
actually powers down the machine.

Additionally, the smartmontools show me an increasing Power-
Off_Rectract_count (currently: 27).

The harddisk is the second drive in my machine, mounted at /mnt/sdb1,
where from that directory, /tmp, /home, /var/lib/munin, /var/cache/munin
and /var/lib/mythtv, are mounted by bindmounts.

I've already tried to patch /etc/init.d/halt by adding the following
lines:

hdparm -f /dev/sdb
sleep 5
hdparm -y /dev/sdb
sleep 5
log_action_msg /dev/sdb spun down

but that only leads to the fact, that the disk indeed spins down during
the shutdown process, but at the very end, spins up again, just before
the power supply switches off.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: upstart 1.12.1-0ubuntu4.2
ProcVersionSignature: Ubuntu 3.13.0-40.69-lowlatency 3.13.11.10
Uname: Linux 3.13.0-40-lowlatency x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Dec  9 20:47:41 2014
InstallationDate: Installed on 2014-04-29 (224 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-lowlatency 
root=UUID=60553440-07a6-456c-8441-a6ae022e9f5e ro quiet splash
SourcePackage: upstart
UpgradeStatus: No upgrade log present (probably fresh install)
UpstartBugCategory: System
UpstartRunningSessionVersion: init (upstart 1.12.1)
UpstartRunningSystemVersion: init (upstart 1.12.1)
modified.conffile..etc.default.cups: [modified]
modified.conffile..etc.munin.plugin.conf.d.munin.node: [deleted]
mtime.conffile..etc.default.cups: 2014-04-17T03:25:57

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


** Tags: amd64 apport-bug trusty

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

Title:
  Shutdown / Poweroff does not spin down harddisk

Status in upstart package in Ubuntu:
  New

Bug description:
  When shutting down, my harddisk is not properly powered off before or
  spun down, so that it gives a sqeeking sound, when the shutdown
  process actually powers down the machine.

  Additionally, the smartmontools show me an increasing Power-
  Off_Rectract_count (currently: 27).

  The harddisk is the second drive in my machine, mounted at /mnt/sdb1,
  where from that directory, /tmp, /home, /var/lib/munin,
  /var/cache/munin and /var/lib/mythtv, are mounted by bindmounts.

  I've already tried to patch /etc/init.d/halt by adding the following
  lines:

hdparm -f /dev/sdb
sleep 5
hdparm -y /dev/sdb
sleep 5
log_action_msg /dev/sdb spun down

  but that only leads to the fact, that the disk indeed spins down
  during the shutdown process, but at the very end, spins up again, just
  before the power supply switches off.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: upstart 1.12.1-0ubuntu4.2
  ProcVersionSignature: Ubuntu 3.13.0-40.69-lowlatency 3.13.11.10
  Uname: Linux 3.13.0-40-lowlatency x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Dec  9 20:47:41 2014
  InstallationDate: Installed on 2014-04-29 (224 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-lowlatency 
root=UUID=60553440-07a6-456c-8441-a6ae022e9f5e ro quiet splash
  SourcePackage: upstart
  UpgradeStatus: No upgrade log present (probably fresh install)
  UpstartBugCategory: System
  UpstartRunningSessionVersion: init (upstart 1.12.1)
  UpstartRunningSystemVersion: init (upstart 1.12.1)
  modified.conffile..etc.default.cups: [modified]
  modified.conffile..etc.munin.plugin.conf.d.munin.node: [deleted]
  mtime.conffile..etc.default.cups: 2014-04-17T03:25:57

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

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

[Touch-packages] [Bug 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid

[Christoph Erian]

Had same issues as described above (update manager - no privilege,
shutdown/restart not working out of menu) after upgrade from 14.04 to
14.10.

Following fixed everything:
sudo apt-get install systemd-sysv

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

Title:
  Not authorized to perform operation / Unable to determine the session
  we are in: No session for pid

Status in “gdm” package in Ubuntu:
  Confirmed
Status in “lightdm” package in Ubuntu:
  Confirmed
Status in “lxdm” package in Ubuntu:
  Confirmed
Status in “policykit-desktop-privileges” package in Ubuntu:
  Confirmed

Bug description:
  After a new install of 64 bit Ubuntu 13.10 on my second partition, I
  used dpkg to reinstall all the same packages I had on my 32 bit 13.04
  partition.  I copied all my home directory files over and updated all
  the packages.  I now find that I don't have permissions to change the
  network settings; I can't mount my other hard drive or any USB stick
  using nautilus, or (udisks without using sudo)' I can't run synaptic
  by clicking on the GUI (I have to go to a terminal and sudo synaptic);
  etc.  I can't find any documentation on the configuration of
  policykit-desktop-privileges, so I'm filing this bug.  For me it
  appears to be totally broken.  Maybe someone can help me out.

  Thanks,

  Rob

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: policykit-desktop-privileges 0.16
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Tue Oct 15 20:20:55 2013
  InstallationDate: Installed on 2013-10-09 (7 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20131008)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: policykit-desktop-privileges
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1243484]

[christoph mueller]

and as a remember:

printing the odt as an pdf with okular (kde pdf-reader) 2 pages per
sheet does the job as it should be.

thanks

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

Title:
  Incorrect handling of orientation when printing PDF files

Status in CUPS - Common Unix Printing System:
  Confirmed
Status in Poppler:
  Fix Released
Status in “cups-filters” package in Ubuntu:
  Fix Released
Status in “poppler” package in Ubuntu:
  Fix Released

Bug description:
  There seems to be some problems in the CUPS filters handling PDF
  files, which can be shown without having an actual printer hooked up
  (this seems to be independent of the driver in use).

  This happens on the latest Ubuntu 13.10 but I believe the real culprit
  is in the cups-filters 1.0.40 package.

  This happens when trying to print a PDF file (such as the CUPS test
  page in /usr/share/cups/data/default.pdf) and trying to change its
  orientation with the 'landscape' option, as such :

  lp -d queue -o landscape /usr/share/cups/data/default.pdf

  The result right now would be that the job is upside down, instead of
  being in a landscape orientation.

  This happens regardless of the driver. The same behavior doesn't
  happen for documents such as PostScript files, which works as
  expected, at least with a PS printer.

  The easiest way to test this is to set up queues that print to file
  (enable FileDevice in the CUPS config first) and look at the resulting
  files with a document viewer such as evince :

  - Create a new Generic Postscript queue using the default drivers, set it to 
print to a URI such as file:///tmp/test.ps
  - Send a PDF job to the queue with the landscape option
  - Look at the output in evince or Ghostview

  I strongly suspect something is amiss with the pdftopdf filter's
  handling of these options, especially in v1.0.40. Fedora 19 didn't
  exhibit the same problem until the cups-filters package was brought up
  to the same version just today.

  I also suspect that more than the orientation options are affected, we
  have had reports from customers having trouble with options handled
  through the Collate PPD options.

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

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

[Touch-packages] [Bug 1243484]

[christoph mueller]

 not resolved !!! ***

hi

with

opensuse13.1
LO Version: 4.3.2.2 Build ID: edfb5295ba211bd31ad47d0bad0118690f76407d
print via cups
2 pages per sheet
to brother MFC-J6510DW
Name: mfcj6510dwcupswrapper
Version : 3.0.0
Release : 1
Architecture: i386
Install Date: Mit 25 Jun 2014 17:47:16 CEST
Group   : Applications
Size: 64256
License : 2004-2012 Brother Industries, Ltd. All Rights Reserved
Signature   : (none)
Source RPM  : mfcj6510dwcupswrapper-3.0.0-1.src.rpm
Build Date  : Don 22 Mär 2012 09:07:35 CET
Build Host  : localhost.domain
Relocations : (not relocatable)
Packager: root@localhost
Vendor  : Brother Industries, Ltd.
Summary : Brother CUPS Inkjet Printer Definitions
Description :
Brother Inkjet printer CUPS Driver
Distribution: (none)

LO prints the pages still as shown in the attachment current and
expected behavior.

thanks

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

Title:
  Incorrect handling of orientation when printing PDF files

Status in CUPS - Common Unix Printing System:
  Confirmed
Status in Poppler:
  Fix Released
Status in “cups-filters” package in Ubuntu:
  Fix Released
Status in “poppler” package in Ubuntu:
  Fix Released

Bug description:
  There seems to be some problems in the CUPS filters handling PDF
  files, which can be shown without having an actual printer hooked up
  (this seems to be independent of the driver in use).

  This happens on the latest Ubuntu 13.10 but I believe the real culprit
  is in the cups-filters 1.0.40 package.

  This happens when trying to print a PDF file (such as the CUPS test
  page in /usr/share/cups/data/default.pdf) and trying to change its
  orientation with the 'landscape' option, as such :

  lp -d queue -o landscape /usr/share/cups/data/default.pdf

  The result right now would be that the job is upside down, instead of
  being in a landscape orientation.

  This happens regardless of the driver. The same behavior doesn't
  happen for documents such as PostScript files, which works as
  expected, at least with a PS printer.

  The easiest way to test this is to set up queues that print to file
  (enable FileDevice in the CUPS config first) and look at the resulting
  files with a document viewer such as evince :

  - Create a new Generic Postscript queue using the default drivers, set it to 
print to a URI such as file:///tmp/test.ps
  - Send a PDF job to the queue with the landscape option
  - Look at the output in evince or Ghostview

  I strongly suspect something is amiss with the pdftopdf filter's
  handling of these options, especially in v1.0.40. Fedora 19 didn't
  exhibit the same problem until the cups-filters package was brought up
  to the same version just today.

  I also suspect that more than the orientation options are affected, we
  have had reports from customers having trouble with options handled
  through the Collate PPD options.

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

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

[Touch-packages] [Bug 1243484]

[christoph mueller]

hi tommy27

as i already told, Brother_MFC-J6510DW is a strange printer! paper feed
an ADF is rotated by 90° against each other. but only the printer should
be interested in that.

KDE printing works.

what is the difference from LO and KDE printing? they use the same
printer driver, cups, ...

i guess the problem could be somewhere in LO between prepare the print
and sending it to cups?

can i do something more?
thanks

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

Title:
  Incorrect handling of orientation when printing PDF files

Status in CUPS - Common Unix Printing System:
  Confirmed
Status in Poppler:
  Fix Released
Status in “cups-filters” package in Ubuntu:
  Fix Released
Status in “poppler” package in Ubuntu:
  Fix Released

Bug description:
  There seems to be some problems in the CUPS filters handling PDF
  files, which can be shown without having an actual printer hooked up
  (this seems to be independent of the driver in use).

  This happens on the latest Ubuntu 13.10 but I believe the real culprit
  is in the cups-filters 1.0.40 package.

  This happens when trying to print a PDF file (such as the CUPS test
  page in /usr/share/cups/data/default.pdf) and trying to change its
  orientation with the 'landscape' option, as such :

  lp -d queue -o landscape /usr/share/cups/data/default.pdf

  The result right now would be that the job is upside down, instead of
  being in a landscape orientation.

  This happens regardless of the driver. The same behavior doesn't
  happen for documents such as PostScript files, which works as
  expected, at least with a PS printer.

  The easiest way to test this is to set up queues that print to file
  (enable FileDevice in the CUPS config first) and look at the resulting
  files with a document viewer such as evince :

  - Create a new Generic Postscript queue using the default drivers, set it to 
print to a URI such as file:///tmp/test.ps
  - Send a PDF job to the queue with the landscape option
  - Look at the output in evince or Ghostview

  I strongly suspect something is amiss with the pdftopdf filter's
  handling of these options, especially in v1.0.40. Fedora 19 didn't
  exhibit the same problem until the cups-filters package was brought up
  to the same version just today.

  I also suspect that more than the orientation options are affected, we
  have had reports from customers having trouble with options handled
  through the Collate PPD options.

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

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

[Touch-packages] [Bug 1357744] [NEW] package tzdata 2012e-0ubuntu0.12.04.1 failed to install/upgrade: ErrorMessage: unable to make backup symlink for `./usr/share/zoneinfo/right/America/Ensenada': No

[Christoph Gebel]

Public bug reported:

Problem occured while upgrading from 12.04 LTS to 14.04 LTS. already
before problems with Update-Manager.

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: tzdata 2012e-0ubuntu0.12.04.1
ProcVersionSignature: Ubuntu 3.2.0-51.77-generic-pae 3.2.48
Uname: Linux 3.2.0-51-generic-pae i686
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: i386
Date: Sat Aug 16 18:16:06 2014
ErrorMessage: ErrorMessage: unable to make backup symlink for 
`./usr/share/zoneinfo/right/America/Ensenada': No space left on device
InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423)
MarkForUpload: True
PackageArchitecture: all
SourcePackage: tzdata
Title: package tzdata 2012e-0ubuntu0.12.04.1 failed to install/upgrade: 
ErrorMessage: unable to make backup symlink for 
`./usr/share/zoneinfo/right/America/Ensenada': No space left on device
UpgradeStatus: Upgraded to precise on 2014-08-16 (0 days ago)

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


** Tags: apport-package i386 precise

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

Title:
  package tzdata 2012e-0ubuntu0.12.04.1 failed to install/upgrade:
  ErrorMessage: unable to make backup symlink for
  `./usr/share/zoneinfo/right/America/Ensenada': No space left on device

Status in “tzdata” package in Ubuntu:
  New

Bug description:
  Problem occured while upgrading from 12.04 LTS to 14.04 LTS. already
  before problems with Update-Manager.

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: tzdata 2012e-0ubuntu0.12.04.1
  ProcVersionSignature: Ubuntu 3.2.0-51.77-generic-pae 3.2.48
  Uname: Linux 3.2.0-51-generic-pae i686
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: i386
  Date: Sat Aug 16 18:16:06 2014
  ErrorMessage: ErrorMessage: unable to make backup symlink for 
`./usr/share/zoneinfo/right/America/Ensenada': No space left on device
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 
(20120423)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: tzdata
  Title: package tzdata 2012e-0ubuntu0.12.04.1 failed to install/upgrade: 
ErrorMessage: unable to make backup symlink for 
`./usr/share/zoneinfo/right/America/Ensenada': No space left on device
  UpgradeStatus: Upgraded to precise on 2014-08-16 (0 days ago)

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

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

[Touch-packages] [Bug 1317449]

[Christoph-maxiom]

*** Bug 338144 has been marked as a duplicate of this bug. ***

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

Title:
  sqlite3 version 3.8.2 breaks digikam

Status in digiKam - digital photo management:
  Won't Fix
Status in SQLite:
  Won't Fix
Status in “digikam” package in Ubuntu:
  Confirmed
Status in “sqlite3” package in Ubuntu:
  Confirmed

Bug description:
  Please update sqlite to a version  3.8.2.

  According to https://bugs.kde.org/show_bug.cgi?id=329697 sqlite3 version 
3.8.2 causes crashes in digikam (and possibly other software) in various 
situations. Several reports confirm, that versions  3.8.2 fix the issue.
  I'm using the 3.8.4.3 package from debian testing right now and can't trigger 
crashes anymore.

  Workaround:
  Install sqlite3  3.8.2, e.g. you can manually install the corresponding deb 
packages from either utopic or debian.

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

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

[Touch-packages] [Bug 1317449]

[Christoph-maxiom]

*** Bug 337839 has been marked as a duplicate of this bug. ***

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

Title:
  sqlite3 version 3.8.2 breaks digikam

Status in digiKam - digital photo management:
  Won't Fix
Status in SQLite:
  Won't Fix
Status in “digikam” package in Ubuntu:
  Confirmed
Status in “sqlite3” package in Ubuntu:
  Confirmed

Bug description:
  Please update sqlite to a version  3.8.2.

  According to https://bugs.kde.org/show_bug.cgi?id=329697 sqlite3 version 
3.8.2 causes crashes in digikam (and possibly other software) in various 
situations. Several reports confirm, that versions  3.8.2 fix the issue.
  I'm using the 3.8.4.3 package from debian testing right now and can't trigger 
crashes anymore.

  Workaround:
  Install sqlite3  3.8.2, e.g. you can manually install the corresponding deb 
packages from either utopic or debian.

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

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

[Touch-packages] [Bug 1317449]

[Christoph-maxiom]

*** Bug 337607 has been marked as a duplicate of this bug. ***

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

Title:
  Please update to a version  3.8.2

Status in digiKam - digital photo management:
  Won't Fix
Status in SQLite:
  Won't Fix
Status in “sqlite3” package in Ubuntu:
  Confirmed

Bug description:
  According to https://bugs.kde.org/show_bug.cgi?id=329697 sqlite3 version 
3.8.2 causes crashes in digikam (and possibly other software) in various 
situations. There are several reports, that versions  3.8.2 fix the issue.
  I'm using the 3.8.4.3 package from debian testing right now and can't trigger 
crashes anymore.

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

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