[Touch-packages] [Bug 2053228] Re: software-properties-gtk does not start

[Roman]

For me app works fine now, don't see anything like @corradoventu does.
I've run a full-upgrade though (don't do this, I've broken my system a
bit, lol).

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

Title:
  software-properties-gtk does not start

Status in software-properties package in Ubuntu:
  Fix Released

Bug description:
  On a new install with the new format sources.list software-properties-gtk 
does not start:
  corrado@corrado-n4-nn-0215:~$ software-properties-gtk
  Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in 
  app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, 
file=file)

^^^
File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 163, in __init__
  SoftwareProperties.__init__(self, options=options, datadir=datadir,
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
109, in __init__
  self.backup_sourceslist()
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
437, in backup_sourceslist
  source_bkp = SourceEntry(line=source.line,file=source.file)
   ^^
File "/usr/lib/python3/dist-packages/aptsources/sourceslist.py", line 509, 
in __init__
  raise ValueError("Classic SourceEntry cannot be written to .sources file")
  ValueError: Classic SourceEntry cannot be written to .sources file
  corrado@corrado-n4-nn-0215:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: software-properties-gtk 0.99.42
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 15 10:07:43 2024
  InstallationDate: Installed on 2024-02-15 (0 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240215)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2053228/+subscriptions


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

[Touch-packages] [Bug 2059651] Re: network-manager gets uninstalled on apt full-upgrade

[Roman]

Yeah, I guess making a full-upgrade instead of upgrade was a bad idea :)

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

Title:
  network-manager gets uninstalled on apt full-upgrade

Status in network-manager package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  network-manager gets uninstalled on apt full-upgrade

  I've tried two Noble systems this evening and both got their network-
  manager packages removed. So wifi is gone.

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


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

[Touch-packages] [Bug 2059651] Re: network-manager gets uninstalled on apt full-upgrade

[Roman]

Temporary bypass:
wget 
http://mirrors.kernel.org/ubuntu/pool/main/n/network-manager/network-manager_1.45.90-1ubuntu1_amd64.deb
dpkg --force-all -i network-manager_1.45.90-1ubuntu1_amd64.deb

dpkg output on my system:
Preparing to unpack network-manager_1.45.90-1ubuntu1_amd64.deb ...
Unpacking network-manager (1.45.90-1ubuntu1) over (1.45.90-1ubuntu1) ...
dpkg: network-manager: dependency problems, but configuring anyway as you 
requested:
 network-manager depends on libnm0 (= 1.45.90-1ubuntu1); however:
  Version of libnm0:amd64 on system is 1.45.90-1ubuntu3.
Setting up network-manager (1.45.90-1ubuntu1) ...
...

After that everything works fine.

Did the same with network-manager-openvpn and network-manager-openvpn-
gnome to bring back VPN, also works.

Btw, after full-upgrade I have a ton (114) of "not gonna be installed"
packages in apt output because some libs are missing from repos, seems
something went wrong when uploading new packages.

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

Title:
  network-manager gets uninstalled on apt full-upgrade

Status in network-manager package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  network-manager gets uninstalled on apt full-upgrade

  I've tried two Noble systems this evening and both got their network-
  manager packages removed. So wifi is gone.

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


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

[Touch-packages] [Bug 2059651] Re: network-manager gets uninstalled on apt full-upgrade

[Roman]

Guess it uninstalls network-manager to install new version but new
version can't be installed because it depends on libnetplan1 which is
missing from repos.

https://packages.ubuntu.com/noble/network-manager currently shows
[depends on] libnetplan1 (>= 0.106)
Package not available 

You can't simply install previous version 1.45.90-1ubuntu1, which still
shows in `apt show network-manager`, because its dependency libnm0 of
the same version is already missing from repos.

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

Title:
  network-manager gets uninstalled on apt full-upgrade

Status in network-manager package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  network-manager gets uninstalled on apt full-upgrade

  I've tried two Noble systems this evening and both got their network-
  manager packages removed. So wifi is gone.

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


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

[Touch-packages] [Bug 2058693] Re: NetworkManager crashed with SIGABRT in g_assertion_message_expr()

[Roman]

All reports from my machine are getting this "core dump is invalid"
messages, why? It is frustrating when you try to properly report bugs
just to get them automatically closed as invalid.

Also seems that this robot automatically removes dumps so you can't even
see them afterwards?

I tried to contact Brian via email without respond, let's try ping him
here somehow - not sure how this is done properly.

** Information type changed from Private to Public

** Changed in: network-manager (Ubuntu)
   Status: Invalid => New

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

Title:
  NetworkManager crashed with SIGABRT in g_assertion_message_expr()

Status in network-manager package in Ubuntu:
  New

Bug description:
  ?

  ProblemType: Crash
  DistroRelease: Ubuntu 24.04
  Package: network-manager 1.45.90-1ubuntu1
  Uname: Linux 6.8.1 x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Mar 20 23:12:46 2024
  ExecutablePath: /usr/sbin/NetworkManager
  InstallationDate: Installed on 2024-02-14 (37 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240212)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcAttrCurrent: Error: [Errno 22] Invalid argument
  ProcCmdline: /usr/sbin/NetworkManager --no-daemon
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  Signal: 6
  SignalName: SIGABRT
  SourcePackage: network-manager
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   ?? ()
  Title: NetworkManager crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf:
   [connection]
   wifi.powersave = 2
  mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 
2024-02-18T15:43:08.117195
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.45.90  connected  started  full  enabled enabled  
enabled  missing  enabled
  separator:

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


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

[Touch-packages] [Bug 1761382] Re: Unable to connect to ibus: Could not connect: Connection refused

[Roman]

Still present on 24.04 with gnome-shell=45.3-1ubuntu1 and ibus=1.5.29-1

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

Title:
  Unable to connect to ibus: Could not connect: Connection refused

Status in gnome-shell package in Ubuntu:
  Expired
Status in ibus package in Ubuntu:
  Expired

Bug description:
  Get this logged:

  oem@ubuntu:~$ journalctl -b | grep ibus

  dbus-daemon[1074]: [session uid=120 pid=1074] Activating service
  name='org.freedesktop.portal.IBus' requested by ':1.18' (uid=120
  pid=1135 comm="ibus-daemon --xim --panel disable " label="unconfined")

  gnome-shell[1084]: Unable to connect to ibus: Could not connect:
  Connection refused

  /usr/lib/gdm3/gdm-x-session[1281]: dbus-update-activation-environment:
  setting QT_IM_MODULE=ibus

  /usr/lib/gdm3/gdm-x-session[1281]: dbus-update-activation-environment:
  setting XMODIFIERS=@im=ibus

  /usr/lib/gdm3/gdm-x-session[1281]: dbus-update-activation-environment:
  setting GTK_IM_MODULE=ibus

  dbus-daemon[1293]: [session uid=1000 pid=1293] Activating service
  name='org.freedesktop.portal.IBus' requested by ':1.27' (uid=1000
  pid=1458 comm="ibus-daemon --xim --panel disable " label="unconfined")

  gnome-shell[1435]: Unable to connect to ibus: Could not connect:
  Connection refused

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Apr  5 07:43:59 2018
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1761382/+subscriptions


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

[Touch-packages] [Bug 1887655] Re: unattended-upgrades triggers reboot despite configuration

[Roman Smid]

I can confirm this behavior on our server with Ubuntu Server 20.04. The
occurence is random and the symptoms and log information is the same.

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

Title:
  unattended-upgrades triggers reboot despite configuration

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  I've been having problems with my Ubuntu machine suddenly rebooting
  without any warning.  To my knowledge Ubuntu Desktop is not supposed
  to reboot without warning by default.

  I believe this is being triggered by unattended-upgrades

  unattended-upgrades 2.3 (amd64)

  Ubuntu Desktop:
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  One pattern that emerges is that the reboot happens right after
  unattended-upgrades completes successfully. There are multiple
  examples in my /var/log/syslog, but all show "unattended-
  upgrades.service: Succeeded." the same second everything begins to
  shut down, with nothing for a minute or two prior. Example:

  Jul 15 11:17:01 pc systemd[2065]: Starting Notification regarding a new 
release of Ubuntu...
  Jul 15 11:17:14 pc charon: 08[IKE] sending keep alive to 10.10.10.10[4500]
  Jul 15 11:17:22 pc check-new-release-gtk[71843]: 
/usr/lib/ubuntu-release-upgrader/check-new-release-gtk:30: PyGIWarning: Gtk was 
imported without specifying a version first. Use gi.require_version('Gtk'
  , '3.0') before import to ensure that the right version gets loaded.
  Jul 15 11:17:22 pc check-new-release-gtk[71843]:   from gi.repository import 
Gtk
  Jul 15 11:17:22 pc check-new-release-gtk[71843]: WARNING:root:timeout 
reached, exiting
  Jul 15 11:17:22 pc systemd[2065]: update-notifier-release.service: Succeeded.
  Jul 15 11:17:22 pc systemd[2065]: Finished Notification regarding a new 
release of Ubuntu.
  Jul 15 11:17:48 pc mysql-workbench[33350]: gtk_tree_view_unref_tree_helper: 
assertion 'node != NULL' failed
  Jul 15 11:17:54 pc charon: 09[IKE] sending keep alive to 10.10.10.10[4500]
  Jul 15 11:18:03 pc systemd[1]: unattended-upgrades.service: Succeeded.
  Jul 15 11:18:03 pc systemd[1]: Stopping Session 3 of user philip.
  Jul 15 11:18:03 pc systemd[1]: Removed slice 
system-clean\x2dmount\x2dpoint.slice.
  Jul 15 11:18:03 pc systemd[1]: Removed slice system-getty.slice.
  Jul 15 11:18:03 pc systemd[1]: Removed slice system-modprobe.slice.
  Jul 15 11:18:03 pc systemd[1]: Stopped target Block Device Preparation for 
/dev/mapper/ubuntu.
  Jul 15 11:18:03 pc systemd[2065]: Stopped target GNOME Wayland Session 
(session: gnome).

  From memory I've never edited the contents of /etc/apt/apt.conf.d/ and
  the configuration for unattended upgrades claims to be default (NOT to
  reboot):

  $ grep -irnC4 reboot /etc/apt/apt.conf.d/
  /etc/apt/apt.conf.d/50unattended-upgrades-88-// Do automatic removal of 
unused packages after the upgrade
  /etc/apt/apt.conf.d/50unattended-upgrades-89-// (equivalent to apt-get 
autoremove)
  
/etc/apt/apt.conf.d/50unattended-upgrades-90-//Unattended-Upgrade::Remove-Unused-Dependencies
 "false";
  /etc/apt/apt.conf.d/50unattended-upgrades-91-
  /etc/apt/apt.conf.d/50unattended-upgrades:92:// Automatically reboot *WITHOUT 
CONFIRMATION* if
  /etc/apt/apt.conf.d/50unattended-upgrades:93://  the file 
/var/run/reboot-required is found after the upgrade
  
/etc/apt/apt.conf.d/50unattended-upgrades:94://Unattended-Upgrade::Automatic-Reboot
 "false";
  /etc/apt/apt.conf.d/50unattended-upgrades-95-
  /etc/apt/apt.conf.d/50unattended-upgrades:96:// Automatically reboot even if 
there are users currently logged in
  /etc/apt/apt.conf.d/50unattended-upgrades:97:// when 
Unattended-Upgrade::Automatic-Reboot is set to true
  
/etc/apt/apt.conf.d/50unattended-upgrades:98://Unattended-Upgrade::Automatic-Reboot-WithUsers
 "true";
  /etc/apt/apt.conf.d/50unattended-upgrades-99-
  /etc/apt/apt.conf.d/50unattended-upgrades:100:// If automatic reboot is 
enabled and needed, reboot at the specific
  /etc/apt/apt.conf.d/50unattended-upgrades-101-// time instead of immediately
  /etc/apt/apt.conf.d/50unattended-upgrades-102-//  Default: "now"
  
/etc/apt/apt.conf.d/50unattended-upgrades:103://Unattended-Upgrade::Automatic-Reboot-Time
 "02:00";
  /etc/apt/apt.conf.d/50unattended-upgrades-104-
  /etc/apt/apt.conf.d/50unattended-upgrades-105-// Use apt bandwidth limit 
feature, this example limits the download
  /etc/apt/apt.conf.d/50unattended-upgrades-106-// speed to 70kb/sec
  /etc/apt/apt.conf.d/50unattended-upgrades-107-//Acquire::http::Dl-Limit "70";

  journalctl -u unattended-upgrades

  Jul 10 07:52:31 PC systemd[1]: Started Unattended Upgrades Shutdown.
  Jul 14 10:03:03 PC systemd[1]: unattended-upgrades.service: Succeeded.
  -- Reboot --
  Jul 14 10:04:11 PC systemd[1]: Started Unattended Upgrades Shutdown.
  Jul 15 11:18:03 PC systemd[1]: unattended-upgrades.service: 

[Touch-packages] [Bug 1370953] Re: layout switch is delayed

[Roman Shipovskij]

Yes, this bug is still present in 22.04, the reason and workaround
described here https://gitlab.gnome.org/GNOME/gnome-
shell/-/issues/1154#note_1065418

** Patch added: "keyboard-layout-switching-delay-workaround.patch"
   
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1370953/+attachment/5602294/+files/keyboard-layout-switching-delay-workaround.patch

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

Title:
  layout switch is delayed

Status in GNOME Shell:
  Unknown
Status in console-setup package in Ubuntu:
  Incomplete
Status in gconf package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  I have two layouts configured En and Ru with Ctrl-Shift as layout
  switch combo.

  When I start typing in wrong layout I notice it, hit Ctrl-Shift and type 
again, but more often than not it is wrong layout again.
  I repeat the action, but there is no luck. On the third attemt it usually 
either works OR the first letter is still in wrong layout, but the second is in 
correct one - i.e. layout switches as I type.

  The explanation for this is that layout switch takes very unreasonable
  time - much longer than it is needed to move your fingers from  one
  key to the other. Each time I encounter the error I retry slower so on
  the third attempt it is slow enough to actually recognize that layout
  switch is happening, but with a delay.

  This is extremely annoying and unacceptable. If someone knows how to
  work around it - please post your suggestions here. It would be nice
  to have a solution for 3+ layouts setup as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1370953/+subscriptions


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

[Touch-packages] [Bug 1948882] Re: PulseEffects does not properly initialize on startup

[Roman]

I am very unfamiliar with flatpak, but I noticed that current Debian sid
includes PulseEffects 4.8.7. I've downloaded the following set from
there: pulseeffects main package, the supporting set of
gstreamer1.0-*-pulseffects packages, and also newer versions of
libglibmm-2.4-1v5 and libgtkmm-3.0-1v5 that were required by
dependencies. And, finally, upgraded DConf packages back to their normal
Jammy version. Now everything seems to work well. PulseEffects starts
normally.

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

Title:
  PulseEffects does not properly initialize on startup

Status in d-conf package in Ubuntu:
  Confirmed
Status in pulseeffects package in Ubuntu:
  Confirmed

Bug description:
  In KUbuntu 21.10, PulseEffects no longer initializes its effects chain
  on startup. I usually use only Equalizer, so when I log into KDE, this
  equalizer does not get activated. To ativate it I need (i) start
  PulseEffects GUI, (ii) untic and tic again the "Equalizer" box. This
  is rarher annoying sequence that I have to repeat each time I login.

  Previousy, in ubuntu 21.04, all this was unnecessary. PluseEffets just
  worked immediately after logging in, without any additional actions. I
  would expect the same behaviour in 21.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: pulseeffects 4.8.4-1
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Uname: Linux 5.13.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Oct 27 02:56:47 2021
  InstallationDate: Installed on 2017-04-03 (1667 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   LANGUAGE=ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseeffects
  UpgradeStatus: Upgraded to impish on 2021-09-24 (32 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/1948882/+subscriptions


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

[Touch-packages] [Bug 1948882] Re: PulseEffects does not properly initialize on startup

[Roman]

Just confirming that the issue moved to Ubuntu Jammy stable relese. The
workaround with downgrading DConf to the Hirsute version still works.

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

Title:
  PulseEffects does not properly initialize on startup

Status in d-conf package in Ubuntu:
  Confirmed
Status in pulseeffects package in Ubuntu:
  New

Bug description:
  In KUbuntu 21.10, PulseEffects no longer initializes its effects chain
  on startup. I usually use only Equalizer, so when I log into KDE, this
  equalizer does not get activated. To ativate it I need (i) start
  PulseEffects GUI, (ii) untic and tic again the "Equalizer" box. This
  is rarher annoying sequence that I have to repeat each time I login.

  Previousy, in ubuntu 21.04, all this was unnecessary. PluseEffets just
  worked immediately after logging in, without any additional actions. I
  would expect the same behaviour in 21.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: pulseeffects 4.8.4-1
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Uname: Linux 5.13.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Oct 27 02:56:47 2021
  InstallationDate: Installed on 2017-04-03 (1667 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   LANGUAGE=ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseeffects
  UpgradeStatus: Upgraded to impish on 2021-09-24 (32 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/1948882/+subscriptions


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

[Touch-packages] [Bug 1948882] Re: PulseEffects does not properly initialize on startup

[Roman]

An update: I've noticed that my PE had the button "Global Bypass"
occasionally activated (somehow without my consent), and after
unpressing it the entire chain now works again. But the initial bug is
unfortunately there, that is PE does not get activated on sturtup
properly. So in 22.04 devel, the bug is still there.

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

Title:
  PulseEffects does not properly initialize on startup

Status in d-conf package in Ubuntu:
  Confirmed
Status in pulseeffects package in Ubuntu:
  New

Bug description:
  In KUbuntu 21.10, PulseEffects no longer initializes its effects chain
  on startup. I usually use only Equalizer, so when I log into KDE, this
  equalizer does not get activated. To ativate it I need (i) start
  PulseEffects GUI, (ii) untic and tic again the "Equalizer" box. This
  is rarher annoying sequence that I have to repeat each time I login.

  Previousy, in ubuntu 21.04, all this was unnecessary. PluseEffets just
  worked immediately after logging in, without any additional actions. I
  would expect the same behaviour in 21.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: pulseeffects 4.8.4-1
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Uname: Linux 5.13.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Oct 27 02:56:47 2021
  InstallationDate: Installed on 2017-04-03 (1667 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   LANGUAGE=ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseeffects
  UpgradeStatus: Upgraded to impish on 2021-09-24 (32 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/1948882/+subscriptions


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

[Touch-packages] [Bug 1948882] Re: PulseEffects does not properly initialize on startup

[Roman]

OK, in devel 22.04 the sound restored after an update, though PE does
not actually perform any transformation from the chain... I just hope
that after all it will be fixed in the final release, and will work well
like it worked in 20.04... If not it seems we have to use the flatpak
version.

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

Title:
  PulseEffects does not properly initialize on startup

Status in d-conf package in Ubuntu:
  Confirmed
Status in pulseeffects package in Ubuntu:
  New

Bug description:
  In KUbuntu 21.10, PulseEffects no longer initializes its effects chain
  on startup. I usually use only Equalizer, so when I log into KDE, this
  equalizer does not get activated. To ativate it I need (i) start
  PulseEffects GUI, (ii) untic and tic again the "Equalizer" box. This
  is rarher annoying sequence that I have to repeat each time I login.

  Previousy, in ubuntu 21.04, all this was unnecessary. PluseEffets just
  worked immediately after logging in, without any additional actions. I
  would expect the same behaviour in 21.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: pulseeffects 4.8.4-1
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Uname: Linux 5.13.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Oct 27 02:56:47 2021
  InstallationDate: Installed on 2017-04-03 (1667 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   LANGUAGE=ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseeffects
  UpgradeStatus: Upgraded to impish on 2021-09-24 (32 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/1948882/+subscriptions


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

[Touch-packages] [Bug 1948882] Re: PulseEffects does not properly initialize on startup

[Roman]

After a recent daily update Pulseeffects just stopped working entirely
(literal silence from the PE(apps) stream). No idea if this is related
to this bug in any way. Difficult to say which package update was
responsible for that, seemingly nothing obviously related. I tried to
upgrade the system to the current development realese of 22.04, and the
same the issue remains.

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

Title:
  PulseEffects does not properly initialize on startup

Status in d-conf package in Ubuntu:
  Confirmed
Status in pulseeffects package in Ubuntu:
  New

Bug description:
  In KUbuntu 21.10, PulseEffects no longer initializes its effects chain
  on startup. I usually use only Equalizer, so when I log into KDE, this
  equalizer does not get activated. To ativate it I need (i) start
  PulseEffects GUI, (ii) untic and tic again the "Equalizer" box. This
  is rarher annoying sequence that I have to repeat each time I login.

  Previousy, in ubuntu 21.04, all this was unnecessary. PluseEffets just
  worked immediately after logging in, without any additional actions. I
  would expect the same behaviour in 21.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: pulseeffects 4.8.4-1
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Uname: Linux 5.13.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Oct 27 02:56:47 2021
  InstallationDate: Installed on 2017-04-03 (1667 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   LANGUAGE=ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseeffects
  UpgradeStatus: Upgraded to impish on 2021-09-24 (32 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/1948882/+subscriptions


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

[Touch-packages] [Bug 1948877] Re: Bluetooth headphones media buttons no longer work

[Roman]

The bug is not present in the current development release of Ubuntu
22.04. Moreover, I've noticed that OS volume control is tied directly to
the headphones.

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

Title:
  Bluetooth headphones media buttons no longer work

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  In KUbuntu 21.10, most media buttons in my bluetooth headphones
  stopped working. This includes the "play/pause" button, "play next"
  (calls after long press of volume increase), and "play previous" (long
  press of volume decrease). The volume +/- buttons themselves are
  working, but this seemingly is implemented entirely in the headphones
  and does not require any communication over bluetooth.

  In previous ubuntu (21.04) these buttons worked, and I expect them
  working.

  My headset is Qumo Accord 3.

  Here is output of "inxi -Eaz" in terminal:

  Bluetooth: Device-1: Realtek Bluetooth Radio type: USB driver: btusb v: 0.8 
bus-ID: 1-7:3 chip-ID: 0bda:b008 class-ID: e001
     serial: 
     Report: hciconfig ID: hci0 rfk-id: 1 state: up address:  
bt-v: 2.1 lmp-v: 4.0 sub-v: 9f73 hci-v: 4.0
     rev: e2f
     Info: acl-mtu: 820:8 sco-mtu: 255:16 link-policy: rswitch hold 
sniff park link-mode: slave accept
     service-classes: rendering, capturing, object transfer, audio, 
telephony

  Some possible workarounds that I found suggest to "modprobe uinput",
  but the uinput module does not get loaded (lsmod does not list it even
  after modprobe'ing).

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


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

[Touch-packages] [Bug 1948882] Re: PulseEffects does not properly initialize on startup

[Roman]

** Also affects: pulseeffects (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  PulseEffects does not properly initialize on startup

Status in d-conf package in Ubuntu:
  Confirmed
Status in pulseeffects package in Ubuntu:
  New

Bug description:
  In KUbuntu 21.10, PulseEffects no longer initializes its effects chain
  on startup. I usually use only Equalizer, so when I log into KDE, this
  equalizer does not get activated. To ativate it I need (i) start
  PulseEffects GUI, (ii) untic and tic again the "Equalizer" box. This
  is rarher annoying sequence that I have to repeat each time I login.

  Previousy, in ubuntu 21.04, all this was unnecessary. PluseEffets just
  worked immediately after logging in, without any additional actions. I
  would expect the same behaviour in 21.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: pulseeffects 4.8.4-1
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Uname: Linux 5.13.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Oct 27 02:56:47 2021
  InstallationDate: Installed on 2017-04-03 (1667 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   LANGUAGE=ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseeffects
  UpgradeStatus: Upgraded to impish on 2021-09-24 (32 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/1948882/+subscriptions


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

[Touch-packages] [Bug 1948882] Re: PulseEffects does not properly initialize on startup

[Roman]

Changing this to d-conf because its downgrade helps to eliminate the
issue

** Package changed: pulseeffects (Ubuntu) => d-conf (Ubuntu)

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

Title:
  PulseEffects does not properly initialize on startup

Status in d-conf package in Ubuntu:
  Confirmed
Status in pulseeffects package in Ubuntu:
  New

Bug description:
  In KUbuntu 21.10, PulseEffects no longer initializes its effects chain
  on startup. I usually use only Equalizer, so when I log into KDE, this
  equalizer does not get activated. To ativate it I need (i) start
  PulseEffects GUI, (ii) untic and tic again the "Equalizer" box. This
  is rarher annoying sequence that I have to repeat each time I login.

  Previousy, in ubuntu 21.04, all this was unnecessary. PluseEffets just
  worked immediately after logging in, without any additional actions. I
  would expect the same behaviour in 21.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: pulseeffects 4.8.4-1
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Uname: Linux 5.13.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Oct 27 02:56:47 2021
  InstallationDate: Installed on 2017-04-03 (1667 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   LANGUAGE=ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseeffects
  UpgradeStatus: Upgraded to impish on 2021-09-24 (32 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/1948882/+subscriptions


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

[Touch-packages] [Bug 1948877] Re: Bluetooth headphones media buttons no longer work

[Roman]

Exact package causing the issue is not obvious, but I add bluez.

** Package changed: ubuntu => bluez (Ubuntu)

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

Title:
  Bluetooth headphones media buttons no longer work

Status in bluez package in Ubuntu:
  New

Bug description:
  In KUbuntu 21.10, most media buttons in my bluetooth headphones
  stopped working. This includes the "play/pause" button, "play next"
  (calls after long press of volume increase), and "play previous" (long
  press of volume decrease). The volume +/- buttons themselves are
  working, but this seemingly is implemented entirely in the headphones
  and does not require any communication over bluetooth.

  In previous ubuntu (20.04) these buttons worked, and I expect them
  working.

  My headset is Qumo Accord 3.

  Here is output of "inxi -Eaz" in terminal:

  Bluetooth: Device-1: Realtek Bluetooth Radio type: USB driver: btusb v: 0.8 
bus-ID: 1-7:3 chip-ID: 0bda:b008 class-ID: e001 
 serial:  
 Report: hciconfig ID: hci0 rfk-id: 1 state: up address:  
bt-v: 2.1 lmp-v: 4.0 sub-v: 9f73 hci-v: 4.0 
 rev: e2f 
 Info: acl-mtu: 820:8 sco-mtu: 255:16 link-policy: rswitch hold 
sniff park link-mode: slave accept 
 service-classes: rendering, capturing, object transfer, audio, 
telephony

  Some possible workarounds that I found suggest to "modprobe uinput",
  but the uinput module does not get loaded (lsmod does not list it even
  after modprobe'ing).

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


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

[Touch-packages] [Bug 1941795] [NEW] Only half of MST display is visible after boot or sleep

[Roman Novikov]

Public bug reported:

Only left half of a 4K display in MST mode visible after sleep. The same
problem often appears after boot as well. Changing mode to any arbitrary
resolution and reverting back resolves the problem.

Display Asus PQ321qe

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Aug 26 21:47:12 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 lttng-modules, 2.12.5, 5.11.0-25-generic, x86_64: installed
 lttng-modules, 2.12.5, 5.11.0-27-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Subsystem: Gigabyte Technology Co., Ltd UHD Graphics 630 (Desktop 9 Series) 
[1458:d000]
 Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XL/XT [Radeon RX Vega 56/64] 
[1002:687f] (rev c0) (prog-if 00 [VGA controller])
   Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] RX Vega64 [1002:0b36]
InstallationDate: Installed on 2021-05-27 (90 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
MachineType: Gigabyte Technology Co., Ltd. Z390 AORUS PRO WIFI
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic 
root=UUID=a46531ab-2bd9-4b9c-a1c1-f3a83760a66c ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/19/2021
dmi.bios.release: 5.13
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F12k
dmi.board.asset.tag: Default string
dmi.board.name: Z390 AORUS PRO WIFI-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF12k:bd01/19/2021:br5.13:svnGigabyteTechnologyCo.,Ltd.:pnZ390AORUSPROWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ390AORUSPROWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: Z390 AORUS PRO WIFI
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal ubuntu

** Attachment added: "IMG_6386.jpg"
   
https://bugs.launchpad.net/bugs/1941795/+attachment/5520959/+files/IMG_6386.jpg

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

Title:
  Only half of MST display is visible after boot or sleep

Status in xorg package in Ubuntu:
  New

Bug description:
  Only left half of a 4K display in MST mode visible after sleep. The
  same problem often appears after boot as well. Changing mode to any
  arbitrary resolution and reverting back resolves the problem.

  Display Asus PQ321qe

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 26 21:47:12 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   lttng-modules, 2.12.5, 5.11.0-25-generic, x86_64: installed
   lttng-modules, 2.12.5, 5.11.0-27-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Subsystem: Gigabyte Technology Co., Ltd UHD Graphics 630 (Desktop 9 Series) 
[1458:d000]
   Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XL/XT [Radeon RX Vega 56/64] 
[1002:687f] (rev c0) (prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] RX Vega64 [1002:0b36]
  InstallationDate: Installed on 2021-05-27 (90 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Gigabyte Technology Co., Ltd. Z390 AORUS PRO WIFI
  

[Touch-packages] [Bug 1872802] Re: Resizing any window will randomly result in graphics corruption for a fraction of a second (in Xorg sessions)

[Roman]

> * Logging into 'Ubuntu on Wayland' (select it on the login screen).

I've tried this before commenting last time and it had way worse
performance with the desktop itself. For example the dash would take a
minute or so to load all the icons. Also applications like OBS, Discord
and Teams have issues with recording and/or streaming, so I have to stay
on X.

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

Title:
  Resizing any window will randomly result in graphics corruption for a
  fraction of a second (in Xorg sessions)

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  When resizing any window in any direction the window can appear glitchy as 
presented in the screenshot.
  This glitchy appearance is restored immediately.
  The issue seems to be seen less often when the CPU is utilized more heavily, 
as when I recorded the screen with OBS to grab the screenshot.
  The screenshots shows gnome-system-monitor, but I could trigger it with 
Firefox, gnome-terminal and others.

  No such issues were experienced with previously installed Ubuntu Mate
  or Windows 10.

  Graphics: Mesa Intel® HD Graphics 620 (KBL GT2) on the Intel® Core™
  i5-7200U CPU @ 2.50GHz × 4

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 14 20:45:47 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-14 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872802/+subscriptions

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

[Touch-packages] [Bug 1872802] Re: Resizing any window will randomly result in graphics corruption for a fraction of a second (in Xorg sessions)

[Roman]

Yes, it is still the same configuration.

I also get another issue all the time, maybe it is somewhat connected to
this one: When switching between users, either Gnome or X crashes. The
OS asks me each time to send a report and I did it a few times. Or maybe
this is worth a separate bug report?

** Attachment added: "newjournal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872802/+attachment/5501256/+files/newjournal.txt

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

Title:
  Resizing any window will randomly result in graphics corruption for a
  fraction of a second (in Xorg sessions)

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  When resizing any window in any direction the window can appear glitchy as 
presented in the screenshot.
  This glitchy appearance is restored immediately.
  The issue seems to be seen less often when the CPU is utilized more heavily, 
as when I recorded the screen with OBS to grab the screenshot.
  The screenshots shows gnome-system-monitor, but I could trigger it with 
Firefox, gnome-terminal and others.

  No such issues were experienced with previously installed Ubuntu Mate
  or Windows 10.

  Graphics: Mesa Intel® HD Graphics 620 (KBL GT2) on the Intel® Core™
  i5-7200U CPU @ 2.50GHz × 4

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 14 20:45:47 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-14 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872802/+subscriptions

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

[Touch-packages] [Bug 1872802] Re: Resizing any window will randomly result in graphics corruption for a fraction of a second (in Xorg sessions)

[Roman]

Well. My installation of Ubuntu 20.04 is one week old + all the updates
and it is still happening occasionally. I just did what I did a year ago
and I can reproduce the bug again and again. See attachment for a
screenshot I did a few minutes ago.

** Attachment added: "Screenshot from 2021-05-28 17-57-22.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872802/+attachment/5500920/+files/Screenshot%20from%202021-05-28%2017-57-22.png

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

Title:
  Resizing any window will randomly result in graphics corruption for a
  fraction of a second (in Xorg sessions)

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  When resizing any window in any direction the window can appear glitchy as 
presented in the screenshot.
  This glitchy appearance is restored immediately.
  The issue seems to be seen less often when the CPU is utilized more heavily, 
as when I recorded the screen with OBS to grab the screenshot.
  The screenshots shows gnome-system-monitor, but I could trigger it with 
Firefox, gnome-terminal and others.

  No such issues were experienced with previously installed Ubuntu Mate
  or Windows 10.

  Graphics: Mesa Intel® HD Graphics 620 (KBL GT2) on the Intel® Core™
  i5-7200U CPU @ 2.50GHz × 4

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 14 20:45:47 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-14 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872802/+subscriptions

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

[Touch-packages] [Bug 1849886] Re: lightdm does not work on eoan on raspberry pi 4

[Roman]

Using the GTK greeter and also tried Slick greeter, both show nothing -
a blank screen - and I would have to ctrl alt f1, get to a terminal
screen, put in a username and password there and then "startx" but the
f7 or wherever the lightdm goes, that does not work when switching to
it.

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

Title:
  lightdm does not work on eoan on raspberry pi 4

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  if you follow the directions on
  https://wiki.ubuntu.com/ARM/RaspberryPi

  sudo apt-get install xubuntu-desktop

  about 20% thru the installation it will ask which window manager you want 
(using dpkg-reconfigure).
  if you select lightdm, you will only get a blank greeter screen after you 
reboot.

  using sudo dpkg-reconfigure gdm3

  resets this to gdm3 and after a reboot, everything is fine.

  this was done on a clean armhf eoan install on a 4gb raspberry pi 4B.

  I have done the install several times.   This bug is repeatable.

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

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

[Touch-packages] [Bug 1849886] Re: lightdm does not work on eoan on raspberry pi 4

[Roman]

Not only is this bug still present on 20.0 with a Pi 3B+ but switching
to Slick greeter doesn't help at all. XDM works fine, etc. but Slick
Greeter is still based on LightDM which is where the issue appears to
be, not just with the particular GTK greeter.

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

Title:
  lightdm does not work on eoan on raspberry pi 4

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  if you follow the directions on
  https://wiki.ubuntu.com/ARM/RaspberryPi

  sudo apt-get install xubuntu-desktop

  about 20% thru the installation it will ask which window manager you want 
(using dpkg-reconfigure).
  if you select lightdm, you will only get a blank greeter screen after you 
reboot.

  using sudo dpkg-reconfigure gdm3

  resets this to gdm3 and after a reboot, everything is fine.

  this was done on a clean armhf eoan install on a 4gb raspberry pi 4B.

  I have done the install several times.   This bug is repeatable.

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

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

[Touch-packages] [Bug 1906394] [NEW] Displays blinking after Ubuntu 20.10 upgrade

[Roman]

Public bug reported:

Hi!

MY Displays are blinking after Ubuntu 20.10 upgrade. Please see the log.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: xorg 1:7.7+19ubuntu15
ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14
Uname: Linux 5.8.0-29-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.11-0ubuntu50.2
Architecture: amd64
CasperMD5CheckResult: skip
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Tue Dec  1 14:02:04 2020
DistUpgraded: 2020-11-26 14:18:08,201 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-xenial-amd64-osp1-20171027-1
DistroCodename: groovy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
   Subsystem: Dell UHD Graphics 630 (Mobile) [1028:0818]
InstallationDate: Installed on 2019-01-24 (677 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20171027-10:57
MachineType: Dell Inc. Latitude 5491
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-29-generic 
root=UUID=33b5750d-e24c-406f-924e-050b03935415 ro alx.enable_wol=1 
mem_sleep_default=deep quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to groovy on 2020-11-26 (4 days ago)
dmi.bios.date: 02/25/2020
dmi.bios.release: 1.12
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.12.0
dmi.board.name: 0R8P2H
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.0:bd02/25/2020:br1.12:svnDellInc.:pnLatitude5491:pvr:rvnDellInc.:rn0R8P2H:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Latitude
dmi.product.name: Latitude 5491
dmi.product.sku: 0818
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu1
version.libdrm2: libdrm2 2.4.102-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.1-1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
xserver.bootTime: Tue Jul 28 12:22:12 2020
xserver.configfile: default
xserver.errors:
 open /dev/dri/card0: No such file or directory
 open /dev/dri/card0: No such file or directory
 Screen 0 deleted because of no matching config section.
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.20.8-2ubuntu2.2

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


** Tags: amd64 apport-bug groovy 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/1906394

Title:
  Displays blinking after Ubuntu 20.10 upgrade

Status in xorg package in Ubuntu:
  New

Bug description:
  Hi!

  MY Displays are blinking after Ubuntu 20.10 upgrade. Please see the
  log.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14
  Uname: Linux 5.8.0-29-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu50.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Dec  1 14:02:04 2020
  DistUpgraded: 2020-11-26 14:18:08,201 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-osp1-20171027-1
  DistroCodename: groovy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 630 (Mobile) [1028:0818]
  InstallationDate: Installed on 2019-01-24 (677 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20171027-10:57
  MachineType: Dell Inc. Latitude 5491
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-29-generic 
root=UUID=33b5750d-e24c-406f-924e-050b03935415 ro alx.enable_wol=1 
mem_sleep_default=deep quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded 

[Touch-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode

[Roman Gralevsky]

Affecting me as well

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

Title:
  [Bluetooth] No audio output/input in HSP/HFP mode

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I'm testing with Sony bluetooth headset SBH20, works fine in A2DP
  profile, but I can't get audio input and output work in HSP/HFP
  profile.

  [Reproduce steps]
  1. Scan and pair BT headset in Bluetooth setting
  2. Switch to HSP/HFP profile in Sound setting
  3. Test sound output/input

  [Machine information]
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  9 16:26:52 2020
  InstallationDate: Installed on 2020-04-09 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: SBH20
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  Symptom_Type: No sound at all
  Title: [SBH20, recording] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/17/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.13
  dmi.board.name: 0188D1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390 2-in-1
  dmi.product.sku: 08B0
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa

[Roman Gralevsky]

*** This bug is a duplicate of bug 1871794 ***
https://bugs.launchpad.net/bugs/1871794

Affecting me as well on Sennheiser Momentum True Wireless 2

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

Title:
  [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting
  HSP/HFP audio profile in Focal Fossa

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After updating the release from Ubuntu 19.10 to 20.04, the bluetooth
  headset doesn't work anymore when HSP/HFP profile is selected.

  With Ubuntu 19.10 the headset was working, there was audio and the mic
  was perfect for video conferencing.

  [Steps to reproduce]
  1. Connect headset (used blueman to setup and connect)
  1.1. When connected the system automatically selects A2DP profile
  2. Start playing audio (browser or other)
  3. Change profile to HSP/HFP with pavucontrol (or blueman)
  4. The audio disappears and microphone is not working (no input)
  5. Optionally switch back to A2DP and the audio comes back

  [Expected]
  When switching to HSP/HFP the audio should keep playing and the microphone 
should start working

  [Notes]
  I tried with pavucontrol to switch between profiles while playing audio from 
a browser.
  As side note there's a led in the headset that still blinks when switching 
profile.

  I tried deleting the pulse folder under user's profile .config without
  success, also reinstalled packages and did a `sudo alsa force-reload`
  and rebooting several times.

  Note: not sure this is a duplicate of [Bug #1576559], it looks quite
  different since the profile changes but the headset stops working.

  [System info]
  Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64
  pulseaudio: 1:13.99.1-1ubuntu3
  bluez: 5.53-0ubuntu3

  Headset: Sennheiser HD 4.50 BTNC

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

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

[Touch-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode

[Roman Gralevsky]

Sennheiser Momentum True Wireless 2

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

Title:
  [Bluetooth] No audio output/input in HSP/HFP mode

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I'm testing with Sony bluetooth headset SBH20, works fine in A2DP
  profile, but I can't get audio input and output work in HSP/HFP
  profile.

  [Reproduce steps]
  1. Scan and pair BT headset in Bluetooth setting
  2. Switch to HSP/HFP profile in Sound setting
  3. Test sound output/input

  [Machine information]
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  9 16:26:52 2020
  InstallationDate: Installed on 2020-04-09 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: SBH20
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  Symptom_Type: No sound at all
  Title: [SBH20, recording] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/17/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.13
  dmi.board.name: 0188D1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390 2-in-1
  dmi.product.sku: 08B0
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1872802] Re: Resizing any window will randomly result in graphics corruption for a fraction of a second

[Roman]

I just recently switched to PopOS and it has the same issue in gnome, if
that helps.

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

Title:
  Resizing any window will randomly result in graphics corruption for a
  fraction of a second

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  When resizing any window in any direction the window can appear glitchy as 
presented in the screenshot.
  This glitchy appearance is restored immediately.
  The issue seems to be seen less often when the CPU is utilized more heavily, 
as when I recorded the screen with OBS to grab the screenshot.
  The screenshots shows gnome-system-monitor, but I could trigger it with 
Firefox, gnome-terminal and others.

  No such issues were experienced with previously installed Ubuntu Mate
  or Windows 10.

  Graphics: Mesa Intel® HD Graphics 620 (KBL GT2) on the Intel® Core™
  i5-7200U CPU @ 2.50GHz × 4

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 14 20:45:47 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-14 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872802/+subscriptions

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

[Touch-packages] [Bug 1872802] Re: Resizing any window will randomly result in graphics corruption for a fraction of a second

[Roman]

** Attachment added: "journal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872802/+attachment/5403355/+files/journal.txt

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

Title:
  Resizing any window will randomly result in graphics corruption for a
  fraction of a second

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  When resizing any window in any direction the window can appear glitchy as 
presented in the screenshot.
  This glitchy appearance is restored immediately.
  The issue seems to be seen less often when the CPU is utilized more heavily, 
as when I recorded the screen with OBS to grab the screenshot.
  The screenshots shows gnome-system-monitor, but I could trigger it with 
Firefox, gnome-terminal and others.

  No such issues were experienced with previously installed Ubuntu Mate
  or Windows 10.

  Graphics: Mesa Intel® HD Graphics 620 (KBL GT2) on the Intel® Core™
  i5-7200U CPU @ 2.50GHz × 4

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 14 20:45:47 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-14 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872802/+subscriptions

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

[Touch-packages] [Bug 1872802] Re: Resizing any window will randomly result in graphics corruption for a fraction of a second

[Roman]

** Attachment added: "lspcik.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872802/+attachment/5403356/+files/lspcik.txt

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

Title:
  Resizing any window will randomly result in graphics corruption for a
  fraction of a second

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  When resizing any window in any direction the window can appear glitchy as 
presented in the screenshot.
  This glitchy appearance is restored immediately.
  The issue seems to be seen less often when the CPU is utilized more heavily, 
as when I recorded the screen with OBS to grab the screenshot.
  The screenshots shows gnome-system-monitor, but I could trigger it with 
Firefox, gnome-terminal and others.

  No such issues were experienced with previously installed Ubuntu Mate
  or Windows 10.

  Graphics: Mesa Intel® HD Graphics 620 (KBL GT2) on the Intel® Core™
  i5-7200U CPU @ 2.50GHz × 4

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 14 20:45:47 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-14 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872802/+subscriptions

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

[Touch-packages] [Bug 1888494] [NEW] ss outputs lots of trailing spaces

[Roman Odaisky]

Public bug reported:

$ ss -atn | head -n 5 | tr ' ' '_'
State__Recv-Q_Send-Q___Local_Address:Port_Peer_Address:Port_Process_
LISTEN_0__4096_127.0.0.53%lo:530.0.0.0:*
LISTEN_0__224__127.0.0.1:5430__0.0.0.0:*
LISTEN_0__1280.0.0.0:220.0.0.0:*
LISTEN_0__5127.0.0.1:631___0.0.0.0:*

These trailing spaces cause problems when piping ss output through grep
or anything else unless the terminal window is very wide. The spaces are
present even when stdout is a terminal, indeed if I maximize my terminal
window (its width becomes a very reasonable 172 characters) and run ss
without arguments, the output is interleaved with blank lines. env -i
changes nothing.

The spaces should be trimmed before output regardless of whether stdout
is a terminal.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: iproute2 5.5.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
Uname: Linux 5.4.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Wed Jul 22 14:05:53 2020
SourcePackage: iproute2
UpgradeStatus: Upgraded to focal on 2020-04-26 (86 days ago)

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

Title:
  ss outputs lots of trailing spaces

Status in iproute2 package in Ubuntu:
  New

Bug description:
  $ ss -atn | head -n 5 | tr ' ' '_'
  
State__Recv-Q_Send-Q___Local_Address:Port_Peer_Address:Port_Process_
  
LISTEN_0__4096_127.0.0.53%lo:530.0.0.0:*
  
LISTEN_0__224__127.0.0.1:5430__0.0.0.0:*
  
LISTEN_0__1280.0.0.0:220.0.0.0:*
  
LISTEN_0__5127.0.0.1:631___0.0.0.0:*

  These trailing spaces cause problems when piping ss output through
  grep or anything else unless the terminal window is very wide. The
  spaces are present even when stdout is a terminal, indeed if I
  maximize my terminal window (its width becomes a very reasonable 172
  characters) and run ss without arguments, the output is interleaved
  with blank lines. env -i changes nothing.

  The spaces should be trimmed before output regardless of whether
  stdout is a terminal.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: iproute2 5.5.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Wed Jul 22 14:05:53 2020
  SourcePackage: iproute2
  UpgradeStatus: Upgraded to focal on 2020-04-26 (86 days ago)

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

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

[Touch-packages] [Bug 1876065] Re: After unplug headphones and plug them again no sound can be heard

[Roman Konieczny]

Hi,

I tested the package contained in the proposed repo (v13.99.1).
I plugged and unplugged the jack several times. It worked well. Worked fine 
also after reboot.

I am now again a happy user of my headset :D

Thanks,
Roman

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

Title:
  After unplug headphones and plug them again no sound can be heard

Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in pulseaudio source package in Focal:
  Fix Committed

Bug description:
  * Impact
  Sound isn't automatically redirected to headphones when those are connected 
to a jack interface

  * Test case
  Disconnect the headsets
  Start your webbrowser/music player/video player and play some sound
  Connect the headsets to the jack interface

  -> the sound should be directly redirected to the plugged headsets

  * Regression potential
  Check that audio routing when connecting/disconnecting devices to the hack 
entry is working correctly

  

  After startup with headset plugged in they play sound nicely - no
  issue. When they are unplugged, the sound is switched to the speaker
  (laptop) - all good. However, when I plug the headset back there is no
  sound. I see the app on pavucontrol, the volume is fine - everything
  looks fine except there is no sound. I dumped output of "pactl list"
  command on startup (headset plugged), after unplugging the headset,
  and when it is plugged back. From the comparison of these outputs, it
  looks like the source has got muted after the headset is plugged.

  Source #1
   State: RUNNING
   Name: alsa_input.pci-_00_1f.3.analog-stereo
   Description: Built-in Audio Analog Stereo
   Driver: module-alsa-card.c
   Sample Specification: s16le 2ch 44100Hz
   Channel Map: front-left,front-right
   Owner Module: 7
   Mute: yes

  Attached three outputs:
  headset-in.txt - after startup with headset plugged - all fine.
  headset-out.txt - after unplugged headset - sound through the speaker - all 
fine.
  headset-back.txt - after plugged headset back - no sound.

  Any help greatly appreciated.

  Regards,
  Roman

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

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

[Touch-packages] [Bug 1876065] Re: After unplug headphones and plug them again no sound can be heard

[Roman Konieczny]

Hi Kai-Heng,

Your repo works!
I didn't expect my problem will be addressed that fast.
Thanks a lot for a super quick response and fix - that is great!

Cheers,
Roman

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

Title:
  After unplug headphones and plug them again no sound can be heard

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After startup with headset plugged in they play sound nicely - no
  issue. When they are unplugged, the sound is switched to the speaker
  (laptop) - all good. However, when I plug the headset back there is no
  sound. I see the app on pavucontrol, the volume is fine - everything
  looks fine except there is no sound. I dumped output of "pactl list"
  command on startup (headset plugged), after unplugging the headset,
  and when it is plugged back. From the comparison of these outputs, it
  looks like the source has got muted after the headset is plugged.

  Source #1
State: RUNNING
Name: alsa_input.pci-_00_1f.3.analog-stereo
Description: Built-in Audio Analog Stereo
Driver: module-alsa-card.c
Sample Specification: s16le 2ch 44100Hz
Channel Map: front-left,front-right
Owner Module: 7
Mute: yes

  Attached three outputs:
  headset-in.txt - after startup with headset plugged - all fine.
  headset-out.txt - after unplugged headset - sound through the speaker - all 
fine.
  headset-back.txt - after plugged headset back - no sound.

  Any help greatly appreciated.

  Regards,
  Roman

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

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

[Touch-packages] [Bug 1876065] Re: After unplug headphones and plug them again no sound can be heard

[Roman Konieczny]

Forgot to add my system details:

Dell Lattitude E5570.

Sound card:
  product: 100 Series/C230 Series Chipset Family HD Audio Controller
  vendor: Intel Corporation

System: Ubuntu Budgie 20.04 with pulseaudio version 13.99.1.

Linux 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020
x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  After unplug headphones and plug them again no sound can be heard

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After startup with headset plugged in they play sound nicely - no
  issue. When they are unplugged, the sound is switched to the speaker
  (laptop) - all good. However, when I plug the headset back there is no
  sound. I see the app on pavucontrol, the volume is fine - everything
  looks fine except there is no sound. I dumped output of "pactl list"
  command on startup (headset plugged), after unplugging the headset,
  and when it is plugged back. From the comparison of these outputs, it
  looks like the source has got muted after the headset is plugged.

  Source #1
State: RUNNING
Name: alsa_input.pci-_00_1f.3.analog-stereo
Description: Built-in Audio Analog Stereo
Driver: module-alsa-card.c
Sample Specification: s16le 2ch 44100Hz
Channel Map: front-left,front-right
Owner Module: 7
Mute: yes

  Attached three outputs:
  headset-in.txt - after startup with headset plugged - all fine.
  headset-out.txt - after unplugged headset - sound through the speaker - all 
fine.
  headset-back.txt - after plugged headset back - no sound.

  Any help greatly appreciated.

  Regards,
  Roman

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

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

[Touch-packages] [Bug 1876065] [NEW] After unplug headphones and plug them again no sound can be heard

[Roman Konieczny]

Public bug reported:

After startup with headset plugged in they play sound nicely - no issue.
When they are unplugged, the sound is switched to the speaker (laptop) -
all good. However, when I plug the headset back there is no sound. I see
the app on pavucontrol, the volume is fine - everything looks fine
except there is no sound. I dumped output of "pactl list" command on
startup (headset plugged), after unplugging the headset, and when it is
plugged back. From the comparison of these outputs, it looks like the
source has got muted after the headset is plugged.

Source #1
State: RUNNING
Name: alsa_input.pci-_00_1f.3.analog-stereo
Description: Built-in Audio Analog Stereo
Driver: module-alsa-card.c
Sample Specification: s16le 2ch 44100Hz
Channel Map: front-left,front-right
Owner Module: 7
Mute: yes

Attached three outputs:
headset-in.txt - after startup with headset plugged - all fine.
headset-out.txt - after unplugged headset - sound through the speaker - all 
fine.
headset-back.txt - after plugged headset back - no sound.

Any help greatly appreciated.

Regards,
Roman

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

** Attachment added: "pa-issue.tar.gz"
   
https://bugs.launchpad.net/bugs/1876065/+attachment/5363918/+files/pa-issue.tar.gz

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

Title:
  After unplug headphones and plug them again no sound can be heard

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After startup with headset plugged in they play sound nicely - no
  issue. When they are unplugged, the sound is switched to the speaker
  (laptop) - all good. However, when I plug the headset back there is no
  sound. I see the app on pavucontrol, the volume is fine - everything
  looks fine except there is no sound. I dumped output of "pactl list"
  command on startup (headset plugged), after unplugging the headset,
  and when it is plugged back. From the comparison of these outputs, it
  looks like the source has got muted after the headset is plugged.

  Source #1
State: RUNNING
Name: alsa_input.pci-_00_1f.3.analog-stereo
Description: Built-in Audio Analog Stereo
Driver: module-alsa-card.c
Sample Specification: s16le 2ch 44100Hz
Channel Map: front-left,front-right
Owner Module: 7
Mute: yes

  Attached three outputs:
  headset-in.txt - after startup with headset plugged - all fine.
  headset-out.txt - after unplugged headset - sound through the speaker - all 
fine.
  headset-back.txt - after plugged headset back - no sound.

  Any help greatly appreciated.

  Regards,
  Roman

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

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

[Touch-packages] [Bug 1768026] Re: echo message hides cursor

[Roman Kovtyukh]

We need it.

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

Title:
  echo message hides cursor

Status in vim:
  Fix Released
Status in vim package in Ubuntu:
  Confirmed

Bug description:
  https://github.com/w0rp/ale/issues/1536#issuecomment-385056702
  upstream bug https://github.com/vim/vim/issues/2612

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: vim 2:8.0.1453-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 30 14:16:35 2018
  InstallationDate: Installed on 2017-05-17 (347 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  SourcePackage: vim
  UpgradeStatus: Upgraded to bionic on 2018-04-26 (3 days ago)

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

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

[Touch-packages] [Bug 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop

[Roman]

Reproduced on `Acer Aspire VN7-592G`. Runnung on Ubuntu 19.10, kernel
version 5.3.

Firstly had no sound devices detected at all. Adding 
`options snd-hda-intel dmic_detect=0` to `/etc/modprobe.d/alsa-base.conf`
Fixed the issue and sound appeared. 

But after that found out, that no input sound device is detected by system, 
along with headset mic.
adding
`options snd-hda-intel mode=aspire-headset-mic`
resolved issue for headset, obviously, but still no default input device is 
detected by system.

Also've been trying to use
`options snd-hda-intel index=0 model=laptop-dmic`
after that. Device appeared in sound panel, but it's recording only static 
noise, nothing more.

Still finding a way to resolve issue for built-in mic.

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

Title:
  Microphone not working in Ubuntu 18.04.3 LTS on new hp-
  spectre-x360-convertible-15 laptop

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp-
  spectre-x360-convertible-15 laptop. The microphone works perfectly on
  Windows 10 (present in Dual boot mode).

  Initially, Internal Microphone was not even detected but installing
  alsa-tools-gui and overriding pin 0x12 to the Internal Microphone
  fixed that issue. [Pin 0x13 does not work and causes static in a
  headphone if it is plugged in.]

  Microphone is not able to pick up any sound. I changed levels/settings in 
alsamixer, pavucontrol without any success:
  In alsamixer: Experimented with levels ranging from very low to very high for 
Internal Mic, Capture, etc.
  In pavucontrol: Set the Internal Mic as a fallback device, unlocked the 
channels for the mic, experimented with reducing the level for one of the 
channels (reduced right mic level to Silence while keeping the left mic level 
normal/high and vice versa).

  alsa-info:
  http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f

  arecord -l
   List of CAPTURE Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0

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

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

[Touch-packages] [Bug 1836721] Re: Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu 18.04

[Roman Shipovskij]

I have just updated from bionic-proposed and everything is fine, as I
see the problem was fixed since kernel 4.15.0-62, so the patch for mesa
can be safely dropped.

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

Title:
  Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu
  18.04

Status in mesa package in Ubuntu:
  Won't Fix
Status in mesa source package in Bionic:
  Fix Released

Bug description:
  Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu
  18.04.

  ~# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  Codename: bionic

  ~# uname -a
  Linux WS 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:12 UTC 2019 i686 
i686 i686 GNU/Linux

  ~# lspci -nn -k -d ::0300
  00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e90]
Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
Kernel driver in use: i915
Kernel modules: i915

  mesa: 19.0.2-1ubuntu1.1~18.04.1

  X crashes with message:
   i965: Failed to submit batchbuffer: Invalid argument

  The same issue was after updating mesa from 18.0 to 18.2:
  https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1815172

  I have tried the same fix and it works for me:
  
https://launchpadlibrarian.net/410418147/mesa_18.2.8-0ubuntu0~18.10.1_18.2.8-0ubuntu0~18.10.2.diff.gz

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

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

[Touch-packages] [Bug 1799265] Re: avahi-daemon high cpu, unusable networking

[Roman]

Same problem with high CPU, but I'm not able to disable ipv6 (ipv6
network). avahi-daemon is almost always at first place by CPU usage.

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

Title:
  avahi-daemon high cpu, unusable networking

Status in Avahi:
  New
Status in avahi package in Ubuntu:
  Triaged

Bug description:
  Currently running Kubuntu 18.10, Dell XPS 13 9350

  Since updating from Kubuntu 18.04 to 18.10, the avahi-daemon has been
  consistently hampering network performance and using CPU for long
  periods of time.

  When booting machine from off state, avahi-daemon uses an entire CPU
  at max load for approx 10 minutes. During this time, internet
  connectivity via wifi is essentially unusable. The wifi connection is
  good, but it seems that http transactions are cutoff mid-way so no
  webpage is able to load.

  When waking from sleep, the avahi-daemon causes similar symptoms, but
  with less than 1 full cpu usage, and with somewhat less degraded
  network performance, but still quite unusable.

  I have never had issues with avahi prior to the 18.10 upgrade, so I am
  fairly confident the issue is rooted in that change.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: avahi-daemon 0.7-4ubuntu2
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Oct 22 10:00:34 2018
  InstallationDate: Installed on 2017-07-24 (455 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   LD_PRELOAD=
   SHELL=/bin/bash
  SourcePackage: avahi
  UpgradeStatus: Upgraded to cosmic on 2018-10-20 (2 days ago)

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

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

[Touch-packages] [Bug 1836721] Re: Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu 18.04

[Roman Shipovskij]

I have just updated mesa from bionic-proposed and now everything is fine
on i386 Ubuntu 18.04:

~# apt-cache policy libgl1-mesa-glx 
libgl1-mesa-glx:
  Встановлено: 19.0.2-1ubuntu1.1~18.04.2
  Кандидат:19.0.2-1ubuntu1.1~18.04.2
  Таблиця версій:
 *** 19.0.2-1ubuntu1.1~18.04.2 500
500 http://archive.ubuntu.com/ubuntu bionic-proposed/main i386 Packages
100 /var/lib/dpkg/status

I have also tried different kernels with bad mesa
19.0.2-1ubuntu1.1~18.04.1 from bionic-updates:

linux-generic (4.15.0-54-generic) - problem exists
linux-generic-hwe-18.04 (4.18.0-25-generic) - problem exists
linux-generic-hwe-18.04-edge (5.0.0-20-generic) - everything is fine

With mesa 19.0.2-1ubuntu1.1~18.04.1 from bionic-proposed everything is
fine on all these kernels

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

** Tags removed: verification-needed-bionic

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

Title:
  Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu
  18.04

Status in mesa package in Ubuntu:
  Won't Fix
Status in mesa source package in Bionic:
  Fix Committed

Bug description:
  Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu
  18.04.

  ~# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  Codename: bionic

  ~# uname -a
  Linux WS 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:12 UTC 2019 i686 
i686 i686 GNU/Linux

  ~# lspci -nn -k -d ::0300
  00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e90]
Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
Kernel driver in use: i915
Kernel modules: i915

  mesa: 19.0.2-1ubuntu1.1~18.04.1

  X crashes with message:
   i965: Failed to submit batchbuffer: Invalid argument

  The same issue was after updating mesa from 18.0 to 18.2:
  https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1815172

  I have tried the same fix and it works for me:
  
https://launchpadlibrarian.net/410418147/mesa_18.2.8-0ubuntu0~18.10.1_18.2.8-0ubuntu0~18.10.2.diff.gz

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

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

[Touch-packages] [Bug 1836721] Re: Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu 18.04

[Roman Shipovskij]

I have just updated from ppa:ubuntu-x-swat/updates, now everything is
fine on i386 Ubuntu 18.04

~# apt-cache policy libgl1-mesa-glx
libgl1-mesa-glx:
  Installed: 19.0.8-0ubuntu0~18.04.1
  Candidate: 19.0.8-0ubuntu0~18.04.1
  Version table:
 *** 19.0.8-0ubuntu0~18.04.1 500
500 http://ppa.launchpad.net/ubuntu-x-swat/updates/ubuntu bionic/main 
i386 Packages
100 /var/lib/dpkg/status

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

Title:
  Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu
  18.04

Status in mesa package in Ubuntu:
  Won't Fix
Status in mesa source package in Bionic:
  In Progress

Bug description:
  Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu
  18.04.

  ~# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  Codename: bionic

  ~# uname -a
  Linux WS 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:12 UTC 2019 i686 
i686 i686 GNU/Linux

  ~# lspci -nn -k -d ::0300
  00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e90]
Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
Kernel driver in use: i915
Kernel modules: i915

  mesa: 19.0.2-1ubuntu1.1~18.04.1

  X crashes with message:
   i965: Failed to submit batchbuffer: Invalid argument

  The same issue was after updating mesa from 18.0 to 18.2:
  https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1815172

  I have tried the same fix and it works for me:
  
https://launchpadlibrarian.net/410418147/mesa_18.2.8-0ubuntu0~18.10.1_18.2.8-0ubuntu0~18.10.2.diff.gz

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

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

[Touch-packages] [Bug 1836721] [NEW] Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu 18.04

[Roman Shipovskij]

Public bug reported:

Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu 18.04.

~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.2 LTS
Release:18.04
Codename:   bionic

~# uname -a
Linux WS 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:12 UTC 2019 i686 
i686 i686 GNU/Linux

~# lspci -nn -k -d ::0300
00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e90]
Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
Kernel driver in use: i915
Kernel modules: i915

mesa: 19.0.2-1ubuntu1.1~18.04.1

X crashes with message:
 i965: Failed to submit batchbuffer: Invalid argument

The same issue was after updating mesa from 18.0 to 18.2:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1815172

I have tried the same fix and it works for me:
https://launchpadlibrarian.net/410418147/mesa_18.2.8-0ubuntu0~18.10.1_18.2.8-0ubuntu0~18.10.2.diff.gz

** Affects: mesa (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: bionic i386 regression-update

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

Title:
  Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu
  18.04

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu
  18.04.

  ~# lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  Codename: bionic

  ~# uname -a
  Linux WS 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:12 UTC 2019 i686 
i686 i686 GNU/Linux

  ~# lspci -nn -k -d ::0300
  00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:3e90]
Subsystem: ASUSTeK Computer Inc. Device [1043:8694]
Kernel driver in use: i915
Kernel modules: i915

  mesa: 19.0.2-1ubuntu1.1~18.04.1

  X crashes with message:
   i965: Failed to submit batchbuffer: Invalid argument

  The same issue was after updating mesa from 18.0 to 18.2:
  https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1815172

  I have tried the same fix and it works for me:
  
https://launchpadlibrarian.net/410418147/mesa_18.2.8-0ubuntu0~18.10.1_18.2.8-0ubuntu0~18.10.2.diff.gz

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

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

[Touch-packages] [Bug 1831470] Re: systemd dhcp don't work on vlan

[Roman]

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

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

Title:
  systemd dhcp don't work on vlan

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  root@gwd:~# uname -a
  Linux gwd 4.15.0-50-generic #54-Ubuntu SMP Mon May 6 18:46:08 UTC 2019 x86_64 
x86_64 x86_64 GNU/Linux

  root@gwd:~# lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04.2 LTS
  Release:18.04
  Codename:   bionic

  root@gwd:~# cat /etc/systemd/network/enp3s0.network
  [Match]
  Name=enp3s0

  [Link]
  MACAddress=C8:D3:A3:50:02:33

  [Network]
  VLAN=enp3s0.2

  root@gwd:~# cat /etc/systemd/network/enp3s0.2.netdev
  [NetDev]
  Name=enp3s0.2
  Kind=vlan

  [VLAN]
  Id=2

  root@gwd:~# cat /etc/systemd/network/enp3s0.2.network
  [Match]
  Name=enp3s0.2

  [Network]
  DHCP=ipv4

  [DHCP]
  UseRoutes=true

  -
  No ip on enp3s0.2 after boot!
  dhclient enp3s0.2 works fine, i create systemd service for it as temporary 
workaround

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

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

[Touch-packages] [Bug 1831470] Re: systemd dhcp don't work on vlan

[Roman]

ok. bug may be closed, i locate problem.

dhcp don't get lease on discovery if where is a valid lease. After
release current lease systemd dhcp discover request was answered.

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

Title:
  systemd dhcp don't work on vlan

Status in systemd package in Ubuntu:
  New

Bug description:
  root@gwd:~# uname -a
  Linux gwd 4.15.0-50-generic #54-Ubuntu SMP Mon May 6 18:46:08 UTC 2019 x86_64 
x86_64 x86_64 GNU/Linux

  root@gwd:~# lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04.2 LTS
  Release:18.04
  Codename:   bionic

  root@gwd:~# cat /etc/systemd/network/enp3s0.network
  [Match]
  Name=enp3s0

  [Link]
  MACAddress=C8:D3:A3:50:02:33

  [Network]
  VLAN=enp3s0.2

  root@gwd:~# cat /etc/systemd/network/enp3s0.2.netdev
  [NetDev]
  Name=enp3s0.2
  Kind=vlan

  [VLAN]
  Id=2

  root@gwd:~# cat /etc/systemd/network/enp3s0.2.network
  [Match]
  Name=enp3s0.2

  [Network]
  DHCP=ipv4

  [DHCP]
  UseRoutes=true

  -
  No ip on enp3s0.2 after boot!
  dhclient enp3s0.2 works fine, i create systemd service for it as temporary 
workaround

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

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

[Touch-packages] [Bug 1831470] Re: systemd dhcp don't work on vlan

[Roman]

here is two tcpdumps of dhcp ports

root@gwd:~# tcpdump -vv -i enp3s0 -n port 67 and port 68
tcpdump: listening on enp3s0, link-type EN10MB (Ethernet), capture size 262144 
bytes

SYSTEMD [NOT WORKED]
19:58:01.261864 IP (tos 0xc0, ttl 64, id 0, offset 0, flags [none], proto UDP 
(17), length 300)
0.0.0.0.68 > 255.255.255.255.67: [udp sum ok] BOOTP/DHCP, Request from 
c8:d3:a3:50:02:33, length 272, xid 0x495060a3, secs 1539, Flags [none] (0x)
  Client-Ethernet-Address c8:d3:a3:50:02:33
  Vendor-rfc1048 Extensions
Magic Cookie 0x63825363
DHCP-Message Option 53, length 1: Discover
Client-ID Option 61, length 7: ether c8:d3:a3:50:02:33
Parameter-Request Option 55, length 8:
  Subnet-Mask, Default-Gateway, Hostname, Domain-Name
  Domain-Name-Server, MTU, Static-Route, Classless-Static-Route
MSZ Option 57, length 2: 576
Hostname Option 12, length 3: "gwd"


DHCLIENT [WORKED]
20:02:33.187353 IP (tos 0x10, ttl 128, id 0, offset 0, flags [none], proto UDP 
(17), length 328)
0.0.0.0.68 > 255.255.255.255.67: [udp sum ok] BOOTP/DHCP, Request from 
c8:d3:a3:50:02:33, length 300, xid 0x5986fc7c, Flags [none] (0x)
  Client-Ethernet-Address c8:d3:a3:50:02:33
  Vendor-rfc1048 Extensions
Magic Cookie 0x63825363
DHCP-Message Option 53, length 1: Request
Requested-IP Option 50, length 4: 213.141.128.50
Hostname Option 12, length 3: "gwd"
Parameter-Request Option 55, length 13:
  Subnet-Mask, BR, Time-Zone, Default-Gateway
  Domain-Name, Domain-Name-Server, Option 119, Hostname
  Netbios-Name-Server, Netbios-Scope, MTU, Classless-Static-Route
  NTP

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

Title:
  systemd dhcp don't work on vlan

Status in systemd package in Ubuntu:
  New

Bug description:
  root@gwd:~# uname -a
  Linux gwd 4.15.0-50-generic #54-Ubuntu SMP Mon May 6 18:46:08 UTC 2019 x86_64 
x86_64 x86_64 GNU/Linux

  root@gwd:~# lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04.2 LTS
  Release:18.04
  Codename:   bionic

  root@gwd:~# cat /etc/systemd/network/enp3s0.network
  [Match]
  Name=enp3s0

  [Link]
  MACAddress=C8:D3:A3:50:02:33

  [Network]
  VLAN=enp3s0.2

  root@gwd:~# cat /etc/systemd/network/enp3s0.2.netdev
  [NetDev]
  Name=enp3s0.2
  Kind=vlan

  [VLAN]
  Id=2

  root@gwd:~# cat /etc/systemd/network/enp3s0.2.network
  [Match]
  Name=enp3s0.2

  [Network]
  DHCP=ipv4

  [DHCP]
  UseRoutes=true

  -
  No ip on enp3s0.2 after boot!
  dhclient enp3s0.2 works fine, i create systemd service for it as temporary 
workaround

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

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

[Touch-packages] [Bug 1831470] Re: systemd dhcp don't work on vlan

[Roman]

netif.tar http://paste.ubuntu.com/p/DvPcmNs6Jb/

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

Title:
  systemd dhcp don't work on vlan

Status in systemd package in Ubuntu:
  New

Bug description:
  root@gwd:~# uname -a
  Linux gwd 4.15.0-50-generic #54-Ubuntu SMP Mon May 6 18:46:08 UTC 2019 x86_64 
x86_64 x86_64 GNU/Linux

  root@gwd:~# lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04.2 LTS
  Release:18.04
  Codename:   bionic

  root@gwd:~# cat /etc/systemd/network/enp3s0.network
  [Match]
  Name=enp3s0

  [Link]
  MACAddress=C8:D3:A3:50:02:33

  [Network]
  VLAN=enp3s0.2

  root@gwd:~# cat /etc/systemd/network/enp3s0.2.netdev
  [NetDev]
  Name=enp3s0.2
  Kind=vlan

  [VLAN]
  Id=2

  root@gwd:~# cat /etc/systemd/network/enp3s0.2.network
  [Match]
  Name=enp3s0.2

  [Network]
  DHCP=ipv4

  [DHCP]
  UseRoutes=true

  -
  No ip on enp3s0.2 after boot!
  dhclient enp3s0.2 works fine, i create systemd service for it as temporary 
workaround

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

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

[Touch-packages] [Bug 1831470] Re: systemd dhcp don't work on vlan

[Roman]

here is debug log
http://paste.ubuntu.com/p/mTxRb5s4Qc/

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

Title:
  systemd dhcp don't work on vlan

Status in systemd package in Ubuntu:
  New

Bug description:
  root@gwd:~# uname -a
  Linux gwd 4.15.0-50-generic #54-Ubuntu SMP Mon May 6 18:46:08 UTC 2019 x86_64 
x86_64 x86_64 GNU/Linux

  root@gwd:~# lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04.2 LTS
  Release:18.04
  Codename:   bionic

  root@gwd:~# cat /etc/systemd/network/enp3s0.network
  [Match]
  Name=enp3s0

  [Link]
  MACAddress=C8:D3:A3:50:02:33

  [Network]
  VLAN=enp3s0.2

  root@gwd:~# cat /etc/systemd/network/enp3s0.2.netdev
  [NetDev]
  Name=enp3s0.2
  Kind=vlan

  [VLAN]
  Id=2

  root@gwd:~# cat /etc/systemd/network/enp3s0.2.network
  [Match]
  Name=enp3s0.2

  [Network]
  DHCP=ipv4

  [DHCP]
  UseRoutes=true

  -
  No ip on enp3s0.2 after boot!
  dhclient enp3s0.2 works fine, i create systemd service for it as temporary 
workaround

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

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

[Touch-packages] [Bug 1831470] Re: systemd dhcp don't work on vlan

[Roman]

here is lease gained from dhclient 
dhcp-lease-time present

lease {
  interface "enp3s0.2";
  fixed-address 213.141.128.50;
  option subnet-mask 255.255.224.0;
  option routers 213.141.159.252;
  option dhcp-lease-time 7200;
  option dhcp-message-type 5;
  option domain-name-servers 212.1.224.6,212.1.244.6;
  option dhcp-server-identifier 212.1.254.199;
  option vendor-encapsulated-options "http://acs.netbynet.ru;;
  renew 2 2019/06/04 16:09:10;
  rebind 2 2019/06/04 17:06:44;
  expire 2 2019/06/04 17:21:44;
}

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

Title:
  systemd dhcp don't work on vlan

Status in systemd package in Ubuntu:
  New

Bug description:
  root@gwd:~# uname -a
  Linux gwd 4.15.0-50-generic #54-Ubuntu SMP Mon May 6 18:46:08 UTC 2019 x86_64 
x86_64 x86_64 GNU/Linux

  root@gwd:~# lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04.2 LTS
  Release:18.04
  Codename:   bionic

  root@gwd:~# cat /etc/systemd/network/enp3s0.network
  [Match]
  Name=enp3s0

  [Link]
  MACAddress=C8:D3:A3:50:02:33

  [Network]
  VLAN=enp3s0.2

  root@gwd:~# cat /etc/systemd/network/enp3s0.2.netdev
  [NetDev]
  Name=enp3s0.2
  Kind=vlan

  [VLAN]
  Id=2

  root@gwd:~# cat /etc/systemd/network/enp3s0.2.network
  [Match]
  Name=enp3s0.2

  [Network]
  DHCP=ipv4

  [DHCP]
  UseRoutes=true

  -
  No ip on enp3s0.2 after boot!
  dhclient enp3s0.2 works fine, i create systemd service for it as temporary 
workaround

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

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

[Touch-packages] [Bug 1831470] Re: systemd dhcp don't work on vlan

[Roman]

yes full config. Many cables unplugged because router not fully functional
enp3s0 connected to swithch in Tagged port, configured only with Vlan 2.
ClientIdentifier=mac not helped

my problem looks similar to
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1779721

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

Title:
  systemd dhcp don't work on vlan

Status in systemd package in Ubuntu:
  New

Bug description:
  root@gwd:~# uname -a
  Linux gwd 4.15.0-50-generic #54-Ubuntu SMP Mon May 6 18:46:08 UTC 2019 x86_64 
x86_64 x86_64 GNU/Linux

  root@gwd:~# lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04.2 LTS
  Release:18.04
  Codename:   bionic

  root@gwd:~# cat /etc/systemd/network/enp3s0.network
  [Match]
  Name=enp3s0

  [Link]
  MACAddress=C8:D3:A3:50:02:33

  [Network]
  VLAN=enp3s0.2

  root@gwd:~# cat /etc/systemd/network/enp3s0.2.netdev
  [NetDev]
  Name=enp3s0.2
  Kind=vlan

  [VLAN]
  Id=2

  root@gwd:~# cat /etc/systemd/network/enp3s0.2.network
  [Match]
  Name=enp3s0.2

  [Network]
  DHCP=ipv4

  [DHCP]
  UseRoutes=true

  -
  No ip on enp3s0.2 after boot!
  dhclient enp3s0.2 works fine, i create systemd service for it as temporary 
workaround

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

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

[Touch-packages] [Bug 1831470] Re: systemd dhcp don't work on vlan

[Roman]

make it through crontab and redirect output

root@gwd:~# cat /root/networkctl
IDX LINK TYPE   OPERATIONAL SETUP
  1 lo   loopback   carrier unmanaged
  2 enp2s0   ether  carrier configured
  3 enp3s0   ether  degradedconfigured
  4 wg0  none   routableconfigured
  5 br-mgmt  ether  routableconfigured
  6 br-lan   ether  no-carrier  configuring
  7 enp3s0.2 ether  degradedconfiguring

7 links listed.

root@gwd:~# cat /root/journal-systemd
-- Logs begin at Sun 2018-01-28 18:58:18 MSK, end at Tue 2019-06-04 16:06:01 
MSK. --
Jun 04 16:02:15 gwd systemd[1]: Starting Network Service...
Jun 04 16:02:15 gwd systemd-networkd[635]: br-lan: netdev ready
Jun 04 16:02:15 gwd systemd-networkd[635]: br-mgmt: netdev ready
Jun 04 16:02:15 gwd systemd-networkd[635]: wg0: netdev ready
Jun 04 16:02:15 gwd systemd-networkd[635]: Enumeration completed
Jun 04 16:02:15 gwd systemd[1]: Started Network Service.
Jun 04 16:02:15 gwd systemd-networkd[635]: enp2s0: Link is not managed by us
Jun 04 16:02:15 gwd systemd-networkd[635]: br-mgmt: Link is not managed by us
Jun 04 16:02:15 gwd systemd-networkd[635]: lo: Link is not managed by us
Jun 04 16:02:15 gwd systemd-networkd[635]: br-lan: Link is not managed by us
Jun 04 16:02:15 gwd systemd-networkd[635]: wg0: Link is not managed by us
Jun 04 16:02:15 gwd systemd-networkd[635]: br-mgmt: Link is not managed by us
Jun 04 16:02:15 gwd systemd-networkd[635]: lo: Link is not managed by us
Jun 04 16:02:15 gwd systemd-networkd[635]: br-lan: Link is not managed by us
Jun 04 16:02:15 gwd systemd-networkd[635]: wg0: Link is not managed by us
Jun 04 16:02:15 gwd systemd-networkd[635]: enp3s0.2: netdev ready
Jun 04 16:02:15 gwd systemd-networkd[635]: enp3s0: IPv6 successfully enabled
Jun 04 16:02:15 gwd systemd-networkd[635]: enp2s0: IPv6 successfully disabled
Jun 04 16:02:18 gwd systemd-networkd[635]: enp3s0: Gained carrier
Jun 04 16:02:18 gwd systemd-networkd[635]: enp3s0.2: Gained carrier
Jun 04 16:02:18 gwd systemd-networkd[635]: br-lan: IPv6 successfully enabled
Jun 04 16:02:18 gwd systemd-networkd[635]: br-mgmt: IPv6 successfully enabled
Jun 04 16:02:18 gwd systemd-networkd[635]: wg0: IPv6 successfully disabled
Jun 04 16:02:18 gwd systemd-networkd[635]: wg0: Gained carrier
Jun 04 16:02:18 gwd systemd-networkd[635]: wg0: Configured
Jun 04 16:02:18 gwd systemd-networkd[635]: lo: Link is not managed by us
Jun 04 16:02:19 gwd systemd-networkd[635]: enp2s0: Gained carrier
Jun 04 16:02:19 gwd systemd-networkd[635]: enp2s0: Configured
Jun 04 16:02:19 gwd systemd-networkd[635]: br-mgmt: Gained carrier
Jun 04 16:02:20 gwd systemd-networkd[635]: enp3s0: Gained IPv6LL
Jun 04 16:02:20 gwd systemd-networkd[635]: enp3s0: Configured
Jun 04 16:02:20 gwd systemd-networkd[635]: enp3s0.2: Gained IPv6LL
Jun 04 16:02:20 gwd systemd-networkd[635]: br-mgmt: Gained IPv6LL
Jun 04 16:02:20 gwd systemd-networkd[635]: br-mgmt: Configured

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

Title:
  systemd dhcp don't work on vlan

Status in systemd package in Ubuntu:
  New

Bug description:
  root@gwd:~# uname -a
  Linux gwd 4.15.0-50-generic #54-Ubuntu SMP Mon May 6 18:46:08 UTC 2019 x86_64 
x86_64 x86_64 GNU/Linux

  root@gwd:~# lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04.2 LTS
  Release:18.04
  Codename:   bionic

  root@gwd:~# cat /etc/systemd/network/enp3s0.network
  [Match]
  Name=enp3s0

  [Link]
  MACAddress=C8:D3:A3:50:02:33

  [Network]
  VLAN=enp3s0.2

  root@gwd:~# cat /etc/systemd/network/enp3s0.2.netdev
  [NetDev]
  Name=enp3s0.2
  Kind=vlan

  [VLAN]
  Id=2

  root@gwd:~# cat /etc/systemd/network/enp3s0.2.network
  [Match]
  Name=enp3s0.2

  [Network]
  DHCP=ipv4

  [DHCP]
  UseRoutes=true

  -
  No ip on enp3s0.2 after boot!
  dhclient enp3s0.2 works fine, i create systemd service for it as temporary 
workaround

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

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

[Touch-packages] [Bug 1831470] Re: systemd dhcp don't work on vlan

[Roman]

I wrote earlier that the dhclient works fine on this interface, so the
problem is apparently that dhcp does not work as requested for the vlan
network

** Changed in: systemd (Ubuntu)
   Status: Incomplete => New

** Description changed:

  root@gwd:~# uname -a
  Linux gwd 4.15.0-50-generic #54-Ubuntu SMP Mon May 6 18:46:08 UTC 2019 x86_64 
x86_64 x86_64 GNU/Linux
  
  root@gwd:~# lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04.2 LTS
  Release:18.04
  Codename:   bionic
  
  root@gwd:~# cat /etc/systemd/network/enp3s0.network
  [Match]
  Name=enp3s0
  
  [Link]
  MACAddress=C8:D3:A3:50:02:33
  
  [Network]
  VLAN=enp3s0.2
  
+ root@gwd:~# cat /etc/systemd/network/enp3s0.2.netdev
+ [NetDev]
+ Name=enp3s0.2
+ Kind=vlan
+ 
+ [VLAN]
+ Id=2
+ 
  root@gwd:~# cat /etc/systemd/network/enp3s0.2.network
  [Match]
  Name=enp3s0.2
  
  [Network]
  DHCP=ipv4
  
  [DHCP]
  UseRoutes=true
  
  -
  No ip on enp3s0.2 after boot!
  dhclient enp3s0.2 works fine, i create systemd service for it as temporary 
workaround

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

Title:
  systemd dhcp don't work on vlan

Status in systemd package in Ubuntu:
  New

Bug description:
  root@gwd:~# uname -a
  Linux gwd 4.15.0-50-generic #54-Ubuntu SMP Mon May 6 18:46:08 UTC 2019 x86_64 
x86_64 x86_64 GNU/Linux

  root@gwd:~# lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04.2 LTS
  Release:18.04
  Codename:   bionic

  root@gwd:~# cat /etc/systemd/network/enp3s0.network
  [Match]
  Name=enp3s0

  [Link]
  MACAddress=C8:D3:A3:50:02:33

  [Network]
  VLAN=enp3s0.2

  root@gwd:~# cat /etc/systemd/network/enp3s0.2.netdev
  [NetDev]
  Name=enp3s0.2
  Kind=vlan

  [VLAN]
  Id=2

  root@gwd:~# cat /etc/systemd/network/enp3s0.2.network
  [Match]
  Name=enp3s0.2

  [Network]
  DHCP=ipv4

  [DHCP]
  UseRoutes=true

  -
  No ip on enp3s0.2 after boot!
  dhclient enp3s0.2 works fine, i create systemd service for it as temporary 
workaround

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

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

[Touch-packages] [Bug 1831470] Re: systemd dhcp don't work on vlan

[Roman]

root@gwd:~# cat /etc/systemd/network/enp3s0.2.netdev
[NetDev]
Name=enp3s0.2
Kind=vlan

[VLAN]
Id=2

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

Title:
  systemd dhcp don't work on vlan

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  root@gwd:~# uname -a
  Linux gwd 4.15.0-50-generic #54-Ubuntu SMP Mon May 6 18:46:08 UTC 2019 x86_64 
x86_64 x86_64 GNU/Linux

  root@gwd:~# lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04.2 LTS
  Release:18.04
  Codename:   bionic

  root@gwd:~# cat /etc/systemd/network/enp3s0.network
  [Match]
  Name=enp3s0

  [Link]
  MACAddress=C8:D3:A3:50:02:33

  [Network]
  VLAN=enp3s0.2

  root@gwd:~# cat /etc/systemd/network/enp3s0.2.network
  [Match]
  Name=enp3s0.2

  [Network]
  DHCP=ipv4

  [DHCP]
  UseRoutes=true

  -
  No ip on enp3s0.2 after boot!
  dhclient enp3s0.2 works fine, i create systemd service for it as temporary 
workaround

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

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

[Touch-packages] [Bug 1831470] Re: systemd dhcp don't work on vlan

[Roman]

on same machine usb modem works fine with DHCP option

root@gwd:~# cat /etc/systemd/network/yota.network
[Match]
Name=enx0c5b8f279a64

[Network]
DHCP=yes

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

Title:
  systemd dhcp don't work on vlan

Status in systemd package in Ubuntu:
  New

Bug description:
  root@gwd:~# uname -a
  Linux gwd 4.15.0-50-generic #54-Ubuntu SMP Mon May 6 18:46:08 UTC 2019 x86_64 
x86_64 x86_64 GNU/Linux

  root@gwd:~# lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04.2 LTS
  Release:18.04
  Codename:   bionic

  root@gwd:~# cat /etc/systemd/network/enp3s0.network
  [Match]
  Name=enp3s0

  [Link]
  MACAddress=C8:D3:A3:50:02:33

  [Network]
  VLAN=enp3s0.2

  root@gwd:~# cat /etc/systemd/network/enp3s0.2.network
  [Match]
  Name=enp3s0.2

  [Network]
  DHCP=ipv4

  [DHCP]
  UseRoutes=true

  -
  No ip on enp3s0.2 after boot!
  dhclient enp3s0.2 works fine, i create systemd service for it as temporary 
workaround

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

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

[Touch-packages] [Bug 1831470] Re: systemd dhcp don't work on vlan

[Roman]

netplan and cloud-init not used and was purged

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

Title:
  systemd dhcp don't work on vlan

Status in systemd package in Ubuntu:
  New

Bug description:
  root@gwd:~# uname -a
  Linux gwd 4.15.0-50-generic #54-Ubuntu SMP Mon May 6 18:46:08 UTC 2019 x86_64 
x86_64 x86_64 GNU/Linux

  root@gwd:~# lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04.2 LTS
  Release:18.04
  Codename:   bionic

  root@gwd:~# cat /etc/systemd/network/enp3s0.network
  [Match]
  Name=enp3s0

  [Link]
  MACAddress=C8:D3:A3:50:02:33

  [Network]
  VLAN=enp3s0.2

  root@gwd:~# cat /etc/systemd/network/enp3s0.2.network
  [Match]
  Name=enp3s0.2

  [Network]
  DHCP=ipv4

  [DHCP]
  UseRoutes=true

  -
  No ip on enp3s0.2 after boot!
  dhclient enp3s0.2 works fine, i create systemd service for it as temporary 
workaround

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

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

[Touch-packages] [Bug 1831470] [NEW] systemd dhcp don't work on vlan

[Roman]

Public bug reported:

root@gwd:~# uname -a
Linux gwd 4.15.0-50-generic #54-Ubuntu SMP Mon May 6 18:46:08 UTC 2019 x86_64 
x86_64 x86_64 GNU/Linux

root@gwd:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.2 LTS
Release:18.04
Codename:   bionic

root@gwd:~# cat /etc/systemd/network/enp3s0.network
[Match]
Name=enp3s0

[Link]
MACAddress=C8:D3:A3:50:02:33

[Network]
VLAN=enp3s0.2

root@gwd:~# cat /etc/systemd/network/enp3s0.2.network
[Match]
Name=enp3s0.2

[Network]
DHCP=ipv4

[DHCP]
UseRoutes=true

-
No ip on enp3s0.2 after boot!
dhclient enp3s0.2 works fine, i create systemd service for it as temporary 
workaround

** 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/1831470

Title:
  systemd dhcp don't work on vlan

Status in systemd package in Ubuntu:
  New

Bug description:
  root@gwd:~# uname -a
  Linux gwd 4.15.0-50-generic #54-Ubuntu SMP Mon May 6 18:46:08 UTC 2019 x86_64 
x86_64 x86_64 GNU/Linux

  root@gwd:~# lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04.2 LTS
  Release:18.04
  Codename:   bionic

  root@gwd:~# cat /etc/systemd/network/enp3s0.network
  [Match]
  Name=enp3s0

  [Link]
  MACAddress=C8:D3:A3:50:02:33

  [Network]
  VLAN=enp3s0.2

  root@gwd:~# cat /etc/systemd/network/enp3s0.2.network
  [Match]
  Name=enp3s0.2

  [Network]
  DHCP=ipv4

  [DHCP]
  UseRoutes=true

  -
  No ip on enp3s0.2 after boot!
  dhclient enp3s0.2 works fine, i create systemd service for it as temporary 
workaround

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

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

[Touch-packages] [Bug 1816404] [NEW] on_ac_power fails if the path contains a whitespace

[Roman Shipovskij]

Public bug reported:

Distributor ID: Ubuntu
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic
powermgmt-base: 1.33

on_ac_power fails if the path contains a whitespace, solution is
attached as patch.

before patch:
~# sh -x /usr/bin/on_ac_power; echo $?
+ set -e
+ OFF_LINE_P=no
+ [ -d /sys/class/power_supply/ ]
+ test -d /sys/class/power_supply/hid-S!N:A7E462F2A0494518B37F374DE00488AA 
Rev:PAACFS00-002-R003-battery
+ test -r /sys/class/power_supply/hid-S!N:A7E462F2A0494518B37F374DE00488AA 
Rev:PAACFS00-002-R003-battery/type
+ cat /sys/class/power_supply/hid-S!N:A7E462F2A0494518B37F374DE00488AA 
Rev:PAACFS00-002-R003-battery/type
cat: '/sys/class/power_supply/hid-S!N:A7E462F2A0494518B37F374DE00488AA': No 
such file or directory
cat: 'Rev:PAACFS00-002-R003-battery/type': No such file or directory
+ type=
1

after patch:
~# sh -x /usr/bin/on_ac_power; echo $?
+ set -e
+ OFF_LINE_P=no
+ [ -d /sys/class/power_supply/ ]
+ test -d /sys/class/power_supply/hid-S!N:A7E462F2A0494518B37F374DE00488AA 
Rev:PAACFS00-002-R003-battery
+ test -r /sys/class/power_supply/hid-S!N:A7E462F2A0494518B37F374DE00488AA 
Rev:PAACFS00-002-R003-battery/type
+ cat /sys/class/power_supply/hid-S!N:A7E462F2A0494518B37F374DE00488AA 
Rev:PAACFS00-002-R003-battery/type
+ type=Battery
+ [ no = yes ]
+ [ -d /proc/acpi/ac_adapter ]
+ [ -r /proc/pmu/info ]
+ [ -r /proc/apm ]
+ exit 255
255

** Affects: powermgmt-base (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: patch

** Patch added: "whitespace.patch"
   
https://bugs.launchpad.net/bugs/1816404/+attachment/5239496/+files/whitespace.patch

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

Title:
  on_ac_power fails if the path contains a whitespace

Status in powermgmt-base package in Ubuntu:
  Confirmed

Bug description:
  Distributor ID: Ubuntu
  Description: Ubuntu 18.04.1 LTS
  Release: 18.04
  Codename: bionic
  powermgmt-base: 1.33

  on_ac_power fails if the path contains a whitespace, solution is
  attached as patch.

  before patch:
  ~# sh -x /usr/bin/on_ac_power; echo $?
  + set -e
  + OFF_LINE_P=no
  + [ -d /sys/class/power_supply/ ]
  + test -d /sys/class/power_supply/hid-S!N:A7E462F2A0494518B37F374DE00488AA 
Rev:PAACFS00-002-R003-battery
  + test -r /sys/class/power_supply/hid-S!N:A7E462F2A0494518B37F374DE00488AA 
Rev:PAACFS00-002-R003-battery/type
  + cat /sys/class/power_supply/hid-S!N:A7E462F2A0494518B37F374DE00488AA 
Rev:PAACFS00-002-R003-battery/type
  cat: '/sys/class/power_supply/hid-S!N:A7E462F2A0494518B37F374DE00488AA': No 
such file or directory
  cat: 'Rev:PAACFS00-002-R003-battery/type': No such file or directory
  + type=
  1

  after patch:
  ~# sh -x /usr/bin/on_ac_power; echo $?
  + set -e
  + OFF_LINE_P=no
  + [ -d /sys/class/power_supply/ ]
  + test -d /sys/class/power_supply/hid-S!N:A7E462F2A0494518B37F374DE00488AA 
Rev:PAACFS00-002-R003-battery
  + test -r /sys/class/power_supply/hid-S!N:A7E462F2A0494518B37F374DE00488AA 
Rev:PAACFS00-002-R003-battery/type
  + cat /sys/class/power_supply/hid-S!N:A7E462F2A0494518B37F374DE00488AA 
Rev:PAACFS00-002-R003-battery/type
  + type=Battery
  + [ no = yes ]
  + [ -d /proc/acpi/ac_adapter ]
  + [ -r /proc/pmu/info ]
  + [ -r /proc/apm ]
  + exit 255
  255

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/powermgmt-base/+bug/1816404/+subscriptions

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

[Touch-packages] [Bug 1025388] Re: Internal mic stops working when plugging in headphones

[Roman]

Confirming x1 5th gen. Any updates?

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

Title:
  Internal mic stops working when plugging in headphones

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I am currently running Quantal and when I plug headphones into my
  headphone socket (which has an icon of a headset next to it, so I
  presume it can take some kind of headset), the internal mic on my
  laptop stops working. If I unplug the headphones the internal mic
  works as normal.

  I tried this with two different sets of headphones (one of which has a
  mic, and the other I think has a mic too).

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: pulseaudio 1:2.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.5.0-4.4-generic 3.5.0-rc6
  Uname: Linux 3.5.0-4-generic i686
  ApportVersion: 2.3-0ubuntu4
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jono   1860 F pulseaudio
   /dev/snd/pcmC0D0c:   jono   1860 F...m pulseaudio
  Date: Mon Jul 16 11:01:32 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/06/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8AET56WW (1.36 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4239CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8AET56WW(1.36):bd12/06/2011:svnLENOVO:pn4239CTO:pvrThinkPadT520:rvnLENOVO:rn4239CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4239CTO
  dmi.product.version: ThinkPad T520
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1794517] Re: Empty Display property in org.freedesktop.login1.session

[Roman Shipovskij]

** Tags added: bionic

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

Title:
  Empty Display property in org.freedesktop.login1.session

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 18.04 when get property of Display variable using DBus
  org.freedesktop.login1.session get empty value.

  In Ubuntu 16.04 release these values isn`t empty and get for example
  Display = :0.

  I use:
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  Package info:

  Package: systemd
  Version: 237-3ubuntu10.3
  Priority: important
  Section: admin
  Origin: Ubuntu
  Maintainer: Ubuntu Developers 
  Original-Maintainer: Debian systemd Maintainers 

  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Installed-Size: 12,9 MB
  Pre-Depends: libacl1 (>= 2.2.51-8), libblkid1 (>= 2.19.1), libc6 (>= 2.27), 
libcap2 (>= 1:2.10), libcryptsetup12 (>= 2:1.4), libgcrypt20 (>= 1.8.0), 
libidn11 (>= 1.13), libip4tc0 (>= 1.6.0+snapshot20161117), liblz4-1 (>= 
0.0~r130), liblzma5 (>= 5.1.1alpha+20120614), libseccomp2 (>= 2.3.1), 
libselinux1 (>= 2.1.9)
  Depends: libapparmor1 (>= 2.9.0-3+exp2), libaudit1 (>= 1:2.2.1), 
libcryptsetup12 (>= 2:1.4.3), libgpg-error0 (>= 1.14), libkmod2 (>= 5~), 
libmount1 (>= 2.26.2), libpam0g (>= 0.99.7.1), libsystemd0 (= 237-3ubuntu10.3), 
util-linux (>= 2.27.1), mount (>= 2.26), adduser, procps
  Recommends: libpam-systemd, dbus, networkd-dispatcher
  Suggests: systemd-container, policykit-1
  Breaks: apparmor (<< 2.9.2-1), ifupdown (<< 0.8.5~), laptop-mode-tools (<< 
1.68~), systemd-shim (<< 10-3~), udev (<< 228-5)
  Replaces: udev (<< 228-5)
  Homepage: https://www.freedesktop.org/wiki/Software/systemd
  Task: minimal, ubuntu-core
  Supported: 5y
  Download-Size: 2 947 kB
  APT-Manual-Installed: yes
  APT-Sources: http://my.repo/ubuntu-current bionic-updates/main i386 Packages
  Description: system and service manager

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

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

[Touch-packages] [Bug 1794516] Re: systemd-logind does not track all user processes

[Roman Shipovskij]

** Tags added: bionic

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

Title:
  systemd-logind does not track all user processes

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 16.04(xenial) release all user processes are in session
  scope for example:

  └─user.slice
└─user-200463.slice
  ├─user@200463.service
  │ └─init.scope
  │   ├─5886 /lib/systemd/systemd --user
  │   └─5888 (sd-pam) 
  └─session-c2.scope
├─  419 bash
├─  471 mc
├─  473 bash -rcfile .bashrc
├─ 1432 bash
├─ 1455 mc
├─ 1457 bash -rcfile .bashrc
├─ 1915 /usr/sbin/sssd -D -f

  In Ubuntu 18.04 (bionic) some processes are in session scope and other
  are in user service for example:

  ├─user.slice
  │ ├─user-200463.slice
  │ │ ├─session-84.scope
  │ │ │ ├─14992 gdm-session-worker [pam/gdm-password]
  │ │ │ ├─15013 /usr/bin/gnome-keyring-daemon --daemonize --login
  │ │ │ ├─15057 /usr/lib/gdm3/gdm-x-session --run-script env 
GNOME_SHELL_SESSION_MODE=ubuntu gnome-session --session=ubuntu
  │ │ │ ├─15059 /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth 
/run/user/200463/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  │ │ │ ├─15114 /usr/lib/gnome-session/gnome-session-binary --session=ubuntu
  │ │ │ ├─15205 /usr/bin/ssh-agent /usr/bin/im-launch env 
GNOME_SHELL_SESSION_MODE=ubuntu gnome-session --session=ubuntu
  │ │ │ ├─15317 /usr/bin/gnome-shell
  │ │ │ ├─15326 /usr/bin/pulseaudio --start --log-target=syslog
  │ │ │ ├─15345 ibus-daemon --xim --panel disable
  │ │ │ ├─15349 /usr/lib/ibus/ibus-dconf
  │ │ │ ├─15353 /usr/lib/ibus/ibus-x11 --kill-daemon
  │ │ │ ├─15417 /usr/lib/gnome-settings-daemon/gsd-power
  │ │ │ ├─15419 /usr/lib/gnome-settings-daemon/gsd-print-notifications
  │ │ │ ├─15420 /usr/lib/gnome-settings-daemon/gsd-rfkill
  │ │ │ ├─15423 /usr/lib/gnome-settings-daemon/gsd-screensaver-proxy
  │ │ │ ├─15425 /usr/lib/gnome-settings-daemon/gsd-sharing
  │ │ │ ├─15431 /usr/lib/gnome-settings-daemon/gsd-smartcard
  │ │ │ ├─15434 /usr/lib/gnome-settings-daemon/gsd-xsettings
  │ │ │ ├─15439 /usr/lib/gnome-settings-daemon/gsd-wacom
  │ │ │ ├─15442 /usr/lib/gnome-settings-daemon/gsd-sound
  │ │ │ ├─15452 /usr/lib/gnome-settings-daemon/gsd-clipboard
  │ │ │ ├─15454 /usr/lib/gnome-settings-daemon/gsd-a11y-settings
  │ │ │ ├─15457 /usr/lib/gnome-settings-daemon/gsd-datetime
  │ │ │ ├─15461 /usr/lib/gnome-settings-daemon/gsd-color
  │ │ │ ├─15464 /usr/lib/gnome-settings-daemon/gsd-keyboard
  │ │ │ ├─15465 /usr/lib/gnome-settings-daemon/gsd-housekeeping
  │ │ │ ├─15469 /usr/lib/gnome-settings-daemon/gsd-mouse
  │ │ │ ├─15472 /usr/lib/gnome-settings-daemon/gsd-media-keys
  │ │ │ ├─15510 diodon
  │ │ │ ├─15515 /usr/lib/gnome-disk-utility/gsd-disk-utility-notify
  │ │ │ ├─15516 
/usr/lib/i386-linux-gnu/indicator-messages/indicator-messages-service
  │ │ │ ├─15519 
/usr/lib/i386-linux-gnu/indicator-application/indicator-application-service
  │ │ │ ├─15527 /usr/lib/gnome-settings-daemon/gsd-printer
  │ │ │ ├─15531 nautilus-desktop
  │ │ │ ├─15593 /usr/lib/ibus/ibus-engine-simple
  │ │ │ ├─15711 update-notifier
  │ │ │ └─16083 /usr/lib/deja-dup/deja-dup-monitor
  │ │ └─user@200463.service
  │ │   ├─zeitgeist.service
  │ │   │ └─15551 /usr/bin/zeitgeist-daemon
  │ │   ├─gnome-terminal-server.service
  │ │   │ ├─15661 /usr/lib/gnome-terminal/gnome-terminal-server
  │ │   │ ├─15671 bash
  │ │   │ ├─15682 systemd-cgls
  │ │   │ └─15683 pager
  │ │   ├─gvfs-gphoto2-volume-monitor.service
  │ │   │ └─15400 /usr/lib/gvfs/gvfs-gphoto2-volume-monitor
  │ │   ├─zeitgeist-fts.service
  │ │   │ └─15557 /usr/lib/zeitgeist/zeitgeist/zeitgeist-fts
  │ │   ├─at-spi-dbus-bus.service
  │ │   │ ├─15267 /usr/lib/at-spi2-core/at-spi-bus-launcher
  │ │   │ ├─15277 /usr/bin/dbus-daemon 
--config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork 
--print-address 3
  │ │   │ └─15282 /usr/lib/at-spi2-core/at-spi2-registryd --use-gnome-session
  │ │   ├─dbus.service
  │ │   │ ├─15110 /usr/bin/dbus-daemon --session --address=systemd: --nofork 
--nopidfile --systemd-activation --syslog-only
  │ │   │ ├─15298 /usr/bin/gnome-keyring-daemon --start --foreground 
--components=secrets
  │ │   │ ├─15357 /usr/lib/ibus/ibus-portal
  │ │   │ ├─15364 /usr/lib/gnome-shell/gnome-shell-calendar-server
  │ │   │ ├─15376 /usr/lib/gnome-online-accounts/goa-daemon
  │ │   │ ├─15387 /usr/lib/gnome-online-accounts/goa-identity-service
  │ │   │ └─15602 /usr/lib/dconf/dconf-service
  │ │   ├─gvfs-udisks2-volume-monitor.service
  │ │   │ └─15396 /usr/lib/gvfs/gvfs-udisks2-volume-monitor
  │ │   ├─evolution-calendar-factory.service
  │ │   │ ├─15567 /usr/lib/evolution/evolution-calendar-factory
  │ │   │ └─15603 /usr/lib/evolution/evolution-calendar-factory-subprocess 
--factory all --bus-name 

[Touch-packages] [Bug 1788321] Re: swapon failed: invalid argument

[Roman Fiedler]

Maybe this is the fix:
x86/speculation/l1tf: fix overflow on l1tf_pfn_limit() on 32bit
https://lkml.org/lkml/2018/8/20/222

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

Title:
  swapon failed: invalid argument

Status in linux package in Ubuntu:
  Confirmed
Status in util-linux package in Ubuntu:
  Invalid

Bug description:
  Environment:
   - Ubuntu 18.04.1 LTS
   - Linux 4.15.0-32-generic i686

  Description:
  When I try to mount my swap partition or my swap file, I get "swapon failed: 
invalid argument" .

  Steps to reproduce:
  1) sudo bash
  2) dd if=/dev/zero of=/swapfile bs=1024 count=524288
  3) mkswap /swapfile
  4) chown root:root /swapfile
  5) chmod 0600 /swapfile
  6) swapon /swapfile
  Last execution returns "swapon failed: invalid argument" .

  I'm almost sure it's a bug because I have no problems using Linux
  4.15.0-29-generic instead of Linux 4.15.0-32-generic. Also, no
  problems using Ubuntu 18.04.1 LTS Live CD.

  Regards.

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

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

[Touch-packages] [Bug 1788321] Re: swapon failed: invalid argument

[Roman Fiedler]

On Xenial, update to "linux-image-4.4.0-135-generic 4.4.0-135.161" did
not fix the problem, but I noticed a message, that might be related to
the issue:

[3.083083] Truncating oversized swap area, only using 0k out of
261116k

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

Title:
  swapon failed: invalid argument

Status in linux package in Ubuntu:
  Confirmed
Status in util-linux package in Ubuntu:
  Invalid

Bug description:
  Environment:
   - Ubuntu 18.04.1 LTS
   - Linux 4.15.0-32-generic i686

  Description:
  When I try to mount my swap partition or my swap file, I get "swapon failed: 
invalid argument" .

  Steps to reproduce:
  1) sudo bash
  2) dd if=/dev/zero of=/swapfile bs=1024 count=524288
  3) mkswap /swapfile
  4) chown root:root /swapfile
  5) chmod 0600 /swapfile
  6) swapon /swapfile
  Last execution returns "swapon failed: invalid argument" .

  I'm almost sure it's a bug because I have no problems using Linux
  4.15.0-29-generic instead of Linux 4.15.0-32-generic. Also, no
  problems using Ubuntu 18.04.1 LTS Live CD.

  Regards.

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

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

[Touch-packages] [Bug 1788321] Re: swapon failed: invalid argument

[Roman Fiedler]

This is the failing "swapon" sequence from updated Xenial i386 on
vmware:

3915  open("/dev/sda2", O_RDONLY|O_LARGEFILE) = 3
3915  uname({sysname="Linux", nodename="v3ls1717", ...}) = 0
3915  ioctl(3, BLKGETSIZE64, [535822336]) = 0
3915  read(3, 
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...,
 65536) = 65536
3915  close(3)  = 0
3915  swapon("/dev/sda2", 0)= -1 EINVAL (Invalid argument)

Sequence is identical to other, native/amd64 system with same kernel
version but without the problem where swapon() will return 0.

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

Title:
  swapon failed: invalid argument

Status in linux package in Ubuntu:
  Confirmed
Status in util-linux package in Ubuntu:
  Invalid

Bug description:
  Environment:
   - Ubuntu 18.04.1 LTS
   - Linux 4.15.0-32-generic i686

  Description:
  When I try to mount my swap partition or my swap file, I get "swapon failed: 
invalid argument" .

  Steps to reproduce:
  1) sudo bash
  2) dd if=/dev/zero of=/swapfile bs=1024 count=524288
  3) mkswap /swapfile
  4) chown root:root /swapfile
  5) chmod 0600 /swapfile
  6) swapon /swapfile
  Last execution returns "swapon failed: invalid argument" .

  I'm almost sure it's a bug because I have no problems using Linux
  4.15.0-29-generic instead of Linux 4.15.0-32-generic. Also, no
  problems using Ubuntu 18.04.1 LTS Live CD.

  Regards.

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

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

[Touch-packages] [Bug 1638842] Re: network-manager does not manage ethernet and bluetooth interfaces when Ubuntu 16.10 is installed using chroot/netboot method

[Roman]

*** This bug is a duplicate of bug 1676547 ***
https://bugs.launchpad.net/bugs/1676547

I've experienced this bug in a clean install of 18.04 via the server
edition first then adding a GUI. In the past editing
/etc/NetworkManager/NetworkManager.conf and setting managed=true was the
solution, that doesn't work anymore. Instead, first I needed to create a
file under /usr/lib/NetworkManager/conf.d/10-globally-managed-
devices.conf and put the following text in it:

[keyfile]
unmanaged-devices=*,except:type:wifi,except:type:wwan

then copy that file to /etc/NetworkManager/conf.d/10-globally-managed-
devices.conf

and then edit the file /etc/NetworkManager/conf.d/10-globally-managed-
devices.conf and change the line to say unmanaged-devices=none

that is finally, at long last what solved it for me.

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

Title:
  network-manager does not manage ethernet and bluetooth interfaces when
  Ubuntu 16.10 is installed using chroot/netboot method

Status in network-manager package in Ubuntu:
  Won't Fix

Bug description:
  Hello,

  I installed Ubuntu 16.10 using a chroot. I use network-manager to
  manage connections. My system is up-to-date (so I use network-manager
  1.2.4-0ubuntu1).

  Wifi works perfectly but I cannot connect to wired networks and using
  my phone's Bluetooth connection. Corresponding devices are said to be
  unmanaged by network-manager. nmcli dev outputs:

  DEVICETYPE  STATE CONNECTION 
  enp1s0ethernet  unmanaged -- 
  wlp2s0wifi  disconnected  --
  6C:9B:02:2C:EE:2C btunmanaged -- 
  hfp/org/bluez/hci0/dev_6C_9B_02_2C_EE_2C  gsm   unmanaged -- 
  loloopback  unmanaged -- 

  The following command has no effect:
  sudo nmcli dev set enp1s0 managed yes

  I can connect to a wired connection by doing:
  ifconfig enp1s0 up
  dhclient enp1s0

  There is nothing in the file /etc/network/interfaces.

  Everything works perfectly if I downgrade network-manager to this
  version: network-manager_1.2.2-0ubuntu0.16.04.3_amd64.deb
  (http://packages.ubuntu.com/xenial-updates/amd64/network-
  manager/download). I had to install libreadline6 and downgrade nplan
  to meet dependencies.

  I don't know what to join to this bug report so please ask in case
  anything is needed.

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

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

[Touch-packages] [Bug 1481871] Re: apt-key del silently fails to delete keys due to limited understanding of GPG key ID formats

[Roman Fiedler]

Just as a side note:

1) apt-key via debootstrap is currently broken on Bionic anyway (gpgv1
to gpgv2 side effects probably), see
https://bugs.launchpad.net/ubuntu/+source/debootstrap/+bug/1767319

2) apt-key seems to be deprecated and should not be used any more on
newer systems, so maybe the bug is a good starter for enforcing
deprecation after bionic: https://lists.gnupg.org/pipermail/gnupg-
users/2018-May/060428.html

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

Title:
  apt-key del silently fails to delete keys due to limited understanding
  of GPG key ID formats

Status in apt package in Ubuntu:
  Triaged

Bug description:
  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04

  apt:
    Installed: 1.0.1ubuntu2.10

  apt-key adv --recv-keys --keyserver hkp://keyserver.ubuntu.com:80
  7A82B743B9B8E46F12C733FA4759FA960E27C0A6

  apt-key export 7A82B743B9B8E46F12C733FA4759FA960E27C0A6 # key is here

  apt-key del  7A82B743B9B8E46F12C733FA4759FA960E27C0A6 # delete key

  apt-key export 7A82B743B9B8E46F12C733FA4759FA960E27C0A6 # key is still
  here

  # Works fine with IDs

  apt-key del  0E27C0A6

  apt-key export 7A82B743B9B8E46F12C733FA4759FA960E27C0A6 # nothing
  exported

  # Works fine with fingerprint on Precise

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

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

[Touch-packages] [Bug 1720364] Re: Unable to use <Ctrl+Shift+key> shortcuts with <Ctrl+Shift> keyboard layout switcher on Ubuntu MATE, 16.04 (with HWE), 17.10 and 18.04 LTS

[Roman Shchekin]

*** This bug is a duplicate of bug 1683383 ***
https://bugs.launchpad.net/bugs/1683383

This is very old and annoying bug. Can someone fix it, please???

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

Title:
  Unable to use  shortcuts with  keyboard
  layout switcher on Ubuntu MATE, 16.04 (with HWE), 17.10 and 18.04 LTS

Status in MATE Desktop:
  New
Status in ubuntu-mate:
  New
Status in X.Org X server:
  Confirmed
Status in marco package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed
Status in xorg-hwe-16.04 package in Ubuntu:
  Confirmed
Status in xorg package in Debian:
  New

Bug description:
  Steps to reproduce:
  1. Install ubuntu-mate-desktop on Ubuntu 16.04 LTS with HWE (Xorg 1.19.5), or 
17.10 or 18.04 LTS.
  2. Set-up two keyboard layouts - English and Russian
  3. Set  as keyboard layout switcher
  4. Try to use shortcuts starting from :
  4.1. Open Firefox, open new tab, go to some site in it, close tab, try to 
click  to restore closed tab.
  4.2. Open mate-terminal, try to open new tab with , or copy 
(), or paste ().
  4.3. Open pluma, write some text, try to navigate in it with 
.

  Expected results:
   switches keyboard layout, shortcuts starting from 
 work normally.

  Actual results:
   switches keyboard layout, shortcuts starting from 
 do not work.

  Notes:
  1. Ubuntu 16.04 LTS (Xorg 1.18.4) with Marco and Compton work normally with 
 keyboard layout switcher.
  2. This problem was discovered before on 13.10, 14.04 and other modern 
versions with GNOME desktop (Metacity and Compiz) - see bug 1245473.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: marco 1.18.1-3ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic i686
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: i386
  CurrentDesktop: MATE
  Date: Fri Sep 29 16:18:02 2017
  InstallationDate: Installed on 2017-08-26 (33 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826)
  SourcePackage: marco
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mate-desktop/+bug/1720364/+subscriptions

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

[Touch-packages] [Bug 1763872] [NEW] package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

[Roman Hdo Rodriguez]

*** This bug is a duplicate of bug 1760128 ***
https://bugs.launchpad.net/bugs/1760128

Public bug reported:

estaba actualizando el 13abr 2018 ubuntui mate ..

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-38-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Fri Apr 13 19:49:25 2018
ErrorMessage: subprocess new pre-removal script returned error exit status 1
InstallationDate: Installed on 2017-04-16 (362 days ago)
InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.26
SourcePackage: avahi
Title: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to
  install/upgrade: subprocess new pre-removal script returned error exit
  status 1

Status in avahi package in Ubuntu:
  New

Bug description:
  estaba actualizando el 13abr 2018 ubuntui mate ..

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Fri Apr 13 19:49:25 2018
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2017-04-16 (362 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: avahi
  Title: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display

[Roman Dinga]

Ok I see that there already is a bug for this 
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752739

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

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

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

[Touch-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display

[Roman Dinga]

Is there an open bug for discrete GPU switch not working? Or should I
open a new one?

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

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

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

[Touch-packages] [Bug 1742695] Re: apt-get update silently fails fetching security updates

[Roman Fiedler]

** Changed in: apt (Ubuntu)
   Status: Incomplete => New

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

Title:
  apt-get update silently fails fetching security updates

Status in apt package in Ubuntu:
  New

Bug description:
  On Ubuntu Xenial, apt-get fails silently when security update server
  cannot be reached. This state could be detected by scanning the apt-
  get output afterwards. But manually adding workarounds to each apt-get
  invocation in production automation is prone to error, thus leaving
  machines without security updates.

  Expected behaviour (e.g.):
  * 0 - all OK
  * 1 - temporary failure (e.g. network)
  * 2 - permanent failure

  
  Test:
  * Change your update server IP in /etc/hosts to something unreachable
  * Run apt-get update (might take a while)
  * Check exit status

  
  $ lsb_release -r -d
  Description:Ubuntu 16.04.3 LTS
  Release:16.04
  rfiedler@n3ahit1403:~$ 

  ii  apt 1.2.24
  amd64commandline package manager

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

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

[Touch-packages] [Bug 1742695] Re: apt-get update silently fails fetching security updates

[Roman Fiedler]

See also
https://unix.stackexchange.com/questions/175146/apt-get-update-exit-status

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

Title:
  apt-get update silently fails fetching security updates

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  On Ubuntu Xenial, apt-get fails silently when security update server
  cannot be reached. This state could be detected by scanning the apt-
  get output afterwards. But manually adding workarounds to each apt-get
  invocation in production automation is prone to error, thus leaving
  machines without security updates.

  Expected behaviour (e.g.):
  * 0 - all OK
  * 1 - temporary failure (e.g. network)
  * 2 - permanent failure

  
  Test:
  * Change your update server IP in /etc/hosts to something unreachable
  * Run apt-get update (might take a while)
  * Check exit status

  
  $ lsb_release -r -d
  Description:Ubuntu 16.04.3 LTS
  Release:16.04
  rfiedler@n3ahit1403:~$ 

  ii  apt 1.2.24
  amd64commandline package manager

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

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

[Touch-packages] [Bug 1742695] Re: apt-get update silently fails fetching security updates

[Roman Fiedler]

Here the output:

# apt-get update

Err:3 http://mirror.[domain]/ubuntu xenial-security InRelease
  Unable to connect to mirror.[domain]:80:
Reading package lists... Done
...
W: Failed to fetch 
http://mirror.[domain]/ubuntu/dists/xenial-security/InRelease  Unable to 
connect to mirror.[domain]:80:
W: Some index files failed to download. They have been ignored, or old ones 
used instead.
# echo $?
0

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

Title:
  apt-get update silently fails fetching security updates

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  On Ubuntu Xenial, apt-get fails silently when security update server
  cannot be reached. This state could be detected by scanning the apt-
  get output afterwards. But manually adding workarounds to each apt-get
  invocation in production automation is prone to error, thus leaving
  machines without security updates.

  Expected behaviour (e.g.):
  * 0 - all OK
  * 1 - temporary failure (e.g. network)
  * 2 - permanent failure

  
  Test:
  * Change your update server IP in /etc/hosts to something unreachable
  * Run apt-get update (might take a while)
  * Check exit status

  
  $ lsb_release -r -d
  Description:Ubuntu 16.04.3 LTS
  Release:16.04
  rfiedler@n3ahit1403:~$ 

  ii  apt 1.2.24
  amd64commandline package manager

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

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

[Touch-packages] [Bug 1742695] [NEW] apt-get update silently fails fetching security updates

[Roman Fiedler]

Public bug reported:

On Ubuntu Xenial, apt-get fails silently when security update server
cannot be reached. This state could be detected by scanning the apt-get
output afterwards. But manually adding workarounds to each apt-get
invocation in production automation is prone to error, thus leaving
machines without security updates.

Expected behaviour (e.g.):
* 0 - all OK
* 1 - temporary failure (e.g. network)
* 2 - permanent failure


Test:
* Change your update server IP in /etc/hosts to something unreachable
* Run apt-get update (might take a while)
* Check exit status


$ lsb_release -r -d
Description:Ubuntu 16.04.3 LTS
Release:16.04
rfiedler@n3ahit1403:~$ 

ii  apt 1.2.24
amd64commandline package manager

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

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

Title:
  apt-get update silently fails fetching security updates

Status in apt package in Ubuntu:
  New

Bug description:
  On Ubuntu Xenial, apt-get fails silently when security update server
  cannot be reached. This state could be detected by scanning the apt-
  get output afterwards. But manually adding workarounds to each apt-get
  invocation in production automation is prone to error, thus leaving
  machines without security updates.

  Expected behaviour (e.g.):
  * 0 - all OK
  * 1 - temporary failure (e.g. network)
  * 2 - permanent failure

  
  Test:
  * Change your update server IP in /etc/hosts to something unreachable
  * Run apt-get update (might take a while)
  * Check exit status

  
  $ lsb_release -r -d
  Description:Ubuntu 16.04.3 LTS
  Release:16.04
  rfiedler@n3ahit1403:~$ 

  ii  apt 1.2.24
  amd64commandline package manager

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

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

[Touch-packages] [Bug 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6

[Roman Vrublevskiy]

As a workaround, I commented out dns=dnsmasq in 
/etc/NetworkManager/NetworkManager.conf.
Now network manager adds VPN DNS servers to /etc/resolv.conf and everything 
works as expected.

As an additional benefit, it also adds and uses additional search domains but 
only with "Use this connection only for resources on its network" unchecked, so 
all traffic is routed to the tunnel.
With working DNS I can live with it for now.

I'm on Mint 18.3 Cinnamon.

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

Title:
  DNS server from vpn connection is not being used after network-manager
  upgrade to 1.2.6

Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Yakkety:
  Triaged

Bug description:
  This was initially opened as #1671606 then later duped to #1639776.
  Discussion in #1639776 indicate that we need new bug for this so I am
  opening one ... Please don't mark this as duplicate to #1639776 or
  other similar bug report. We already lost several months and we are
  again at beginning ...

  TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by
  VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from
  DHCP instead of one defined by VPN (wrong).

  DNS resolver should query only DNS servers defined by VPN while
  connection is active.

  =

  Test steps / result:

  - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 
(dnsmasq-base-2.75-1ubuntu0.16.04.2)
  - restated my laptop to ensure clean start
  - connected to VPN using openconnect / network-manager-openconnect-gnome

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by LAN connection (this is wrong / connection not working at
  all)

  - "killall dnsmasq"
  - dnsmasq get automatically restarted by system

  Observed results -> most of the the queries are forwarded to DNS
  servers defined by VPN, but lot of queries get forwarded to DNS
  servers defined by LAN connection (this is still wrong / DNS leaks,
  attacker can hijack connection even if VPN is enabled)

  - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base 
stay same)
  - restated my laptop to ensure clean test
  - connected to same VPN using openconnect

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by VPN connection. There are no leaks to LAN DNS server (this
  is correct behavior).

  =

  Paul Smith requested additional details in #1639776. Here are:

  * If you're using IPv4 vs. IPv6
  -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi 
/vpn)

  * If you have checked or unchecked the "Use this connection only for 
resources on its network"
  -> unchecked on all nw definition

  * If you have this checked, try unchecking it and see if that makes a 
difference
  -> no change if I toggle this option. Behavior is same.

  * When you say "DNS lookups" please be clear about whether the hostnames 
being looked up are public (e.g., www.google.com or whatever), on your local 
LAN, or in the network accessed via the VPN. Does it make a difference which 
one you choose?
  -> No difference.

  * Are you using fully-qualified hostnames, or relying on the DNS domain 
search path? Does it make a difference if you do it differently?
  -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see 
difference when I try same using hostname + domain search.

  =

  I am using openconnect (cisco) and openvpn. Test result are by using
  openconnect but I saw same behaviour also while using openvpn.

  =

  Thanks

  Lukas

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

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

[Touch-packages] [Bug 1733185] [NEW] package apport-gtk 2.20.1-0ubuntu2.12 failed to install/upgrade: проблемы зависимостей — оставляем не настроенным

[Roman Novikow]

Public bug reported:

Включаю компьютер, загружается и выдаёт это.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: apport-gtk 2.20.1-0ubuntu2.12
ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-38-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
ApportLog:
 
ApportVersion: 2.20.1-0ubuntu2.12
Architecture: amd64
Date: Fri Nov 17 11:39:54 2017
ErrorMessage: проблемы зависимостей — оставляем не настроенным
InstallationDate: Installed on 2017-09-19 (60 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: apport
Title: package apport-gtk 2.20.1-0ubuntu2.12 failed to install/upgrade: 
проблемы зависимостей — оставляем не настроенным
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package apport-gtk 2.20.1-0ubuntu2.12 failed to install/upgrade:
  проблемы зависимостей — оставляем не настроенным

Status in apport package in Ubuntu:
  New

Bug description:
  Включаю компьютер, загружается и выдаёт это.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport-gtk 2.20.1-0ubuntu2.12
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportLog:
   
  ApportVersion: 2.20.1-0ubuntu2.12
  Architecture: amd64
  Date: Fri Nov 17 11:39:54 2017
  ErrorMessage: проблемы зависимостей — оставляем не настроенным
  InstallationDate: Installed on 2017-09-19 (60 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: apport
  Title: package apport-gtk 2.20.1-0ubuntu2.12 failed to install/upgrade: 
проблемы зависимостей — оставляем не настроенным
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1733183] [NEW] package apport 2.20.1-0ubuntu2.12 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1

[Roman Novikow]

Public bug reported:

Включаю компьютер, загружается и выдаёт это.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: apport 2.20.1-0ubuntu2.12
ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-38-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.12
Architecture: amd64
Date: Fri Nov 17 11:39:54 2017
ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код 
ошибки 1
InstallationDate: Installed on 2017-09-19 (60 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: apport
Title: package apport 2.20.1-0ubuntu2.12 failed to install/upgrade: подпроцесс 
установлен сценарий post-installation возвратил код ошибки 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package apport 2.20.1-0ubuntu2.12 failed to install/upgrade:
  подпроцесс установлен сценарий post-installation возвратил код ошибки
  1

Status in apport package in Ubuntu:
  New

Bug description:
  Включаю компьютер, загружается и выдаёт это.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.12
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.12
  Architecture: amd64
  Date: Fri Nov 17 11:39:54 2017
  ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код 
ошибки 1
  InstallationDate: Installed on 2017-09-19 (60 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: apport
  Title: package apport 2.20.1-0ubuntu2.12 failed to install/upgrade: 
подпроцесс установлен сценарий post-installation возвратил код ошибки 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1587142] Re: Shutdown hangs in md kworker after "Reached target Shutdown."

[Roman Ledovskiy]

Confirm this on:
Supermicro X10DAi board and ASUS ESC4000 G3 server
Ubuntu 16.04.2 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/1587142

Title:
  Shutdown hangs in md kworker after "Reached target Shutdown."

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I'm booting a fully patched 16.04 from an Intel Rapid Storage
  Technology enterprise RAID1 volume (ThinkServer TS140 with two SATA
  ST1000NM0033-9ZM drives, ext4 root partition, no LVM, UEFI mode).

  If the RAID volume is recovering or resyncing for whatever reason, then `sudo 
systemctl reboot` and `sudo systemctl poweroff` work fine (I had to `sudo 
systemctl --now disable lvm2-lvmetad lvm2-lvmpolld lvm2-monitor` in order to 
consistently get that). However, once the recovery/resync is complete and 
clean, the reboot and poweroff commands above hang forever after "Reached 
target Shutdown.". Note that issuing `sudo swapoff -a` beforehand (suggested in 
the bug #1464917) does not help.
  [EDIT]Actually, the shutdown also hangs from time to time during a resync. 
But I've never seen it succeed once the resync is complete.[/EDIT]

  Then, if the server has been forcibly restarted with the power button,
  the Intel Matrix Storage Manager indicates a "Normal" status for the
  RAID1 volume, but Ubuntu then resyncs the volume anyway:

  [1.223649] md: bind
  [1.228426] md: bind
  [1.230030] md: bind
  [1.230738] md: bind
  [1.232985] usbcore: registered new interface driver usbhid
  [1.233494] usbhid: USB HID core driver
  [1.234022] md: raid1 personality registered for level 1
  [1.234876] md/raid1:md126: not clean -- starting background reconstruction
  [1.234956] input: CHESEN USB Keyboard as 
/devices/pci:00/:00:14.0/usb3/3-10/3-10:1.0/0003:0A81:0101.0001/input/input5
  [1.236273] md/raid1:md126: active with 2 out of 2 mirrors
  [1.236797] md126: detected capacity change from 0 to 1000202043392
  [1.246271] md: md126 switched to read-write mode.
  [1.246834] md: resync of RAID array md126
  [1.247325] md: minimum _guaranteed_  speed: 1000 KB/sec/disk.
  [1.247503]  md126: p1 p2 p3 p4
  [1.248269] md: using maximum available idle IO bandwidth (but not more 
than 20 KB/sec) for resync.
  [1.248774] md: using 128k window, over a total of 976759940k.

  Note that the pain of "resync upon every (re)boot" cannot even be a
  bit relieved thanks to bitmaps because mdadm does not support them for
  IMSM containers:

  $ sudo mdadm --grow --bitmap=internal /dev/md126
  mdadm: Cannot add bitmaps to sub-arrays yet

  I also get this in syslog during boot when the individual drives are
  detected, but this seems to be harmless:

  May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/sbin/mdadm --incremental 
/dev/sdb --offroot' failed with exit code 1.
  May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/lib/udev/hdparm' failed 
with exit code 1.

  May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/sbin/mdadm --incremental 
/dev/sda --offroot' failed with exit code 1.
  May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/lib/udev/hdparm' failed 
with exit code 1.

  During a resync, `sudo sh -c 'echo idle >
  /sys/block/md126/md/sync_action'` actually stops it as expected, but
  it restarts immediately though nothing seems to have triggered it:

  May 30 18:17:02 wssrv1 kernel: [ 3106.826710] md: md126: resync interrupted.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836320] md: checkpointing resync of 
md126.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836623] md: resync of RAID array md126
  May 30 18:17:02 wssrv1 kernel: [ 3106.836625] md: minimum _guaranteed_  
speed: 1000 KB/sec/disk.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836626] md: using maximum available 
idle IO bandwidth (but not more than 20 KB/sec) for resync.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836627] md: using 128k window, over a 
total of 976759940k.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836628] md: resuming resync of md126 
from checkpoint.
  May 30 18:17:02 wssrv1 mdadm[982]: RebuildStarted event detected on md device 
/dev/md/Volume0

  I attach screenshots of the hanging shutdown log after a `sudo sh -c 'echo 8 
> /proc/sys/kernel/printk'`. The second screenshot shows that the kernel has 
deadlocked in md_write_start(). Note that `sudo systemctl start debug-shell` is 
unusable on this machine at this point because Ctrl+Alt+F9 brings tty9 without 
any keyboard.
  [EDIT]But I can still switch back to tty1.[/EDIT]

  I have also tried with much lower values for vm.dirty_background_ratio
  and vm.dirty_ratio, but to no avail.

  Linux 4.6.0-040600-generic_4.6.0-040600.201605151930_amd64 from
  http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-yakkety/ did not
  help either.

  More information below:

  $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  

[Touch-packages] [Bug 1705807] Re: 2ccf Hypersecu HyperFIDO idVendor missing from 70-debian-uaccess.rules

[Roman Yepishev]

Adding lsusb output for the device.

** Attachment added: "lsusb -d 2ccf:0880 -v"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1705807/+attachment/4919125/+files/lsusb-2ccf.txt

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

Title:
  2ccf Hypersecu HyperFIDO idVendor missing from 70-debian-uaccess.rules

Status in systemd package in Ubuntu:
  New

Bug description:
  As per
  https://hypersecu.com/downloads/files/configurations/70-u2f.rules
  linked to from https://hypersecu.com/support/faq:

  """
  # HyperSecu HyperFIDO
  KERNEL=="hidraw*", SUBSYSTEM=="hidraw", ATTRS{idVendor}=="096e|2ccf", 
ATTRS{idProduct}=="0880", TAG+="uaccess"
  """

  Currently 70-u2f.rules contains only:
  """
  # HyperSecu HyperFIDO
  ATTRS{idVendor}=="096e", ATTRS{idProduct}=="0880", TAG+="uaccess"
  """

  This prevents the U2F devices currently sold from being used out of
  the box.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: udev 233-8ubuntu3 [modified: 
lib/udev/rules.d/70-debian-uaccess.rules]
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Jul 21 22:59:03 2017
  InstallationDate: Installed on 2017-07-14 (8 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 04f3:2494 Elan Microelectronics Corp. 
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:58c2 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 13-7378
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-10-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to artful on 2017-07-20 (2 days ago)
  dmi.bios.date: 03/14/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.0
  dmi.board.name: 0FF2FN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd03/14/2017:svnDellInc.:pnInspiron13-7378:pvr:rvnDellInc.:rn0FF2FN:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 13-7378
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1705807] [NEW] 2ccf Hypersecu HyperFIDO idVendor missing from 70-debian-uaccess.rules

[Roman Yepishev]

Public bug reported:

As per https://hypersecu.com/downloads/files/configurations/70-u2f.rules
linked to from https://hypersecu.com/support/faq:

"""
# HyperSecu HyperFIDO
KERNEL=="hidraw*", SUBSYSTEM=="hidraw", ATTRS{idVendor}=="096e|2ccf", 
ATTRS{idProduct}=="0880", TAG+="uaccess"
"""

Currently 70-u2f.rules contains only:
"""
# HyperSecu HyperFIDO
ATTRS{idVendor}=="096e", ATTRS{idProduct}=="0880", TAG+="uaccess"
"""

This prevents the U2F devices currently sold from being used out of the
box.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: udev 233-8ubuntu3 [modified: lib/udev/rules.d/70-debian-uaccess.rules]
ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
Uname: Linux 4.11.0-10-generic x86_64
ApportVersion: 2.20.6-0ubuntu4
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Jul 21 22:59:03 2017
InstallationDate: Installed on 2017-07-14 (8 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 005: ID 04f3:2494 Elan Microelectronics Corp. 
 Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
 Bus 001 Device 002: ID 0bda:58c2 Realtek Semiconductor Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Inspiron 13-7378
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-10-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: systemd
UpgradeStatus: Upgraded to artful on 2017-07-20 (2 days ago)
dmi.bios.date: 03/14/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.7.0
dmi.board.name: 0FF2FN
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd03/14/2017:svnDellInc.:pnInspiron13-7378:pvr:rvnDellInc.:rn0FF2FN:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Inspiron 13-7378
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug artful third-party-packages wayland-session

** Attachment removed: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1705807/+attachment/4919116/+files/CurrentDmesg.txt

** Attachment removed: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1705807/+attachment/4919120/+files/ProcCpuinfo.txt

** Attachment removed: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1705807/+attachment/4919121/+files/ProcCpuinfoMinimal.txt

** Attachment removed: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1705807/+attachment/4919122/+files/ProcInterrupts.txt

** Attachment removed: "ProcModules.txt"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1705807/+attachment/4919123/+files/ProcModules.txt

** Attachment removed: "Dependencies.txt"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1705807/+attachment/4919117/+files/Dependencies.txt

** Attachment removed: "JournalErrors.txt"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1705807/+attachment/4919118/+files/JournalErrors.txt

** Attachment removed: "Lspci.txt"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1705807/+attachment/4919119/+files/Lspci.txt

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

Title:
  2ccf Hypersecu HyperFIDO idVendor missing from 70-debian-uaccess.rules

Status in systemd package in Ubuntu:
  New

Bug description:
  As per
  https://hypersecu.com/downloads/files/configurations/70-u2f.rules
  linked to from https://hypersecu.com/support/faq:

  """
  # HyperSecu HyperFIDO
  KERNEL=="hidraw*", SUBSYSTEM=="hidraw", ATTRS{idVendor}=="096e|2ccf", 
ATTRS{idProduct}=="0880", TAG+="uaccess"
  """

  Currently 70-u2f.rules contains only:
  """
  # HyperSecu HyperFIDO
  ATTRS{idVendor}=="096e", ATTRS{idProduct}=="0880", TAG+="uaccess"
  """

  This prevents the U2F devices currently sold from being used out of
  the box.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: udev 233-8ubuntu3 [modified: 
lib/udev/rules.d/70-debian-uaccess.rules]
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Jul 21 22:59:03 2017
  InstallationDate: Installed on 2017-07-14 (8 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 04f3:2494 Elan Microelectronics Corp. 
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:58c2 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 

[Touch-packages] [Bug 1533631] Re: dhclient killed when DHCPv6 lease is out-of date

[Roman]

root@gw:~# cat /var/lib/dhcp/dhclient6.br1.leases
default-duid "\000\001\000\001 \302\271\313\000\002D\032>\251";
lease6 {
  interface "br1";
  ia-na 44:1a:3e:a9 {
starts 1496317261;
renew 900;
rebind 1500;
iaaddr 2a02:2168:82d:949::1 {
  starts 1496317261;
  preferred-life 1800;
  max-life 1800;
}
  }
  option dhcp6.client-id 0:1:0:1:20:c2:b9:cb:0:2:44:1a:3e:a9;
  option dhcp6.server-id 0:3:0:1:0:16:4d:7e:df:5c;
  option dhcp6.name-servers 2a02:2168:208:1::1,2a02:2168:208:2::1;
}

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

Title:
  dhclient killed when DHCPv6 lease is out-of date

Status in NetworkManager:
  Confirmed
Status in isc-dhcp package in Ubuntu:
  In Progress
Status in network-manager package in Ubuntu:
  In Progress

Bug description:
  Network Manager summarily kills the IPv6 dhclient process when the
  DHCPv6 lease contained in the dhclient6-${UUID}.lease file is out-of
  date, leaving the IPv6 interface without a stateful IPv6 address, or,
  if the "require IPv6 address on this interface" option is enabled,
  causes NM to cycle continuously deactivating and reactivating the
  interface (including the IPv4 addresses).

  This is effectively a Denial Of Service. It can be trivially induced
  if, for example, the dhclient6-$(UUID}.lease file contains a lease
  that was issued before the user went away on vacation or the PC wasn't
  connected to the same network for a few days (depending on the lease
  renew/rebind/expiry times). Calculation on the old lease of

  start + preferred_lifetime < NOW

  triggers dhclient to 'DEPREFER6' the lease (withdraw the address
  record) and ask the DHCPv6 server for a new lease, but Network Manager
  will kill the dhclient because it only sees an 'EXPIRE6' state change.

  In summary, when the DHCPv6 state transitions from "bound" to
  "unknown" then "expire" to "done" Network Manager kills the 'dhclient'
  process before it has chance to request and bind a fresh lease, If
  'dhclient' is run manually with the same command-line options and
  allowed to continue running it correctly gains a new lease.

  Network Manager doesn't know how to handle "DEPREF6", which is sent
  from isc-dhcp dhclient to the helper script (set by "-sf" option).

  So it seems that to correctly solve this issue Network Manager must be
  taught how to handle DEPREF6.

  /var/log/syslog will show a message from dhclient of the form:

  dhclient: PRC: Address 2a02:8011:2007::2 depreferred.

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

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

[Touch-packages] [Bug 1533631] Re: dhclient killed when DHCPv6 lease is out-of date

[Roman]

I have no Network Manager in Ubuntu server 16.04 LTS, but this bug present.
After booting where is no dhclient in the processes if accept_ra set to 2 and 
syslog contains 

Jun  1 13:55:33 gw dhclient[3663]: PRC: Prefix 2a02:2168:176b:4800::/56 
depreferred.
Jun  1 14:05:44 gw dhclient[2762]: PRC: Address 2a02:2168:82d:949::4 
depreferred.

if i remove setting accept_ra from sysctl on same leases all works fine
except of course DHCP-PD.

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

Title:
  dhclient killed when DHCPv6 lease is out-of date

Status in NetworkManager:
  Confirmed
Status in isc-dhcp package in Ubuntu:
  In Progress
Status in network-manager package in Ubuntu:
  In Progress

Bug description:
  Network Manager summarily kills the IPv6 dhclient process when the
  DHCPv6 lease contained in the dhclient6-${UUID}.lease file is out-of
  date, leaving the IPv6 interface without a stateful IPv6 address, or,
  if the "require IPv6 address on this interface" option is enabled,
  causes NM to cycle continuously deactivating and reactivating the
  interface (including the IPv4 addresses).

  This is effectively a Denial Of Service. It can be trivially induced
  if, for example, the dhclient6-$(UUID}.lease file contains a lease
  that was issued before the user went away on vacation or the PC wasn't
  connected to the same network for a few days (depending on the lease
  renew/rebind/expiry times). Calculation on the old lease of

  start + preferred_lifetime < NOW

  triggers dhclient to 'DEPREFER6' the lease (withdraw the address
  record) and ask the DHCPv6 server for a new lease, but Network Manager
  will kill the dhclient because it only sees an 'EXPIRE6' state change.

  In summary, when the DHCPv6 state transitions from "bound" to
  "unknown" then "expire" to "done" Network Manager kills the 'dhclient'
  process before it has chance to request and bind a fresh lease, If
  'dhclient' is run manually with the same command-line options and
  allowed to continue running it correctly gains a new lease.

  Network Manager doesn't know how to handle "DEPREF6", which is sent
  from isc-dhcp dhclient to the helper script (set by "-sf" option).

  So it seems that to correctly solve this issue Network Manager must be
  taught how to handle DEPREF6.

  /var/log/syslog will show a message from dhclient of the form:

  dhclient: PRC: Address 2a02:8011:2007::2 depreferred.

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

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

[Touch-packages] [Bug 1667669] [NEW] package netbase 5.3 failed to install/upgrade: не удалось установить «/etc/services.dpkg-new» в качестве «/etc/services»: Операция не позволена

[Roman]

Public bug reported:

after do-relise-upgrade

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: netbase 5.3
ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
Uname: Linux 3.16.0-30-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Wed Feb 22 20:00:57 2017
ErrorMessage: не удалось установить «/etc/services.dpkg-new» в качестве 
«/etc/services»: Операция не позволена
InstallationDate: Installed on 2015-08-22 (550 days ago)
InstallationMedia: Ubuntu-Server 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.19
SourcePackage: netbase
Title: package netbase 5.3 failed to install/upgrade: не удалось установить 
«/etc/services.dpkg-new» в качестве «/etc/services»: Операция не позволена
UpgradeStatus: Upgraded to xenial on 2017-02-22 (0 days ago)

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


** Tags: amd64 apport-package xenial

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

Title:
  package netbase 5.3 failed to install/upgrade: не удалось установить
  «/etc/services.dpkg-new» в качестве «/etc/services»: Операция не
  позволена

Status in netbase package in Ubuntu:
  New

Bug description:
  after do-relise-upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: netbase 5.3
  ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Wed Feb 22 20:00:57 2017
  ErrorMessage: не удалось установить «/etc/services.dpkg-new» в качестве 
«/etc/services»: Операция не позволена
  InstallationDate: Installed on 2015-08-22 (550 days ago)
  InstallationMedia: Ubuntu-Server 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: netbase
  Title: package netbase 5.3 failed to install/upgrade: не удалось установить 
«/etc/services.dpkg-new» в качестве «/etc/services»: Операция не позволена
  UpgradeStatus: Upgraded to xenial on 2017-02-22 (0 days ago)

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

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

[Touch-packages] [Bug 1648224] Re: [krilin] Dialer-app surface freezes during outgoing calls

[Roman B]

Hi Pat.

I just made some tests:

Start dialer from launcher: 3 attempts outgoing call, dialer app freezes
3 times.

Start dialer from app scope: 3 attempts outgoing call, dialer app
freezes 3 times.

Start call from contact app: 3 attempts outgoing call, dialer app
freezes 3 times.

One remarkable thing: The freezed dialer app is different with every
call. Sometimes I see the called number only, sometimes the number and
the all the symbols above the red stop phone call button, sometimes only
some symbols, e.g. the loud voice symbol, sometimes only the red button
... But every time the interface is freezed and the red button for
stopping the call etc is not working.

Every time I can close the dialer app in the app task manager and then
open it again touching the green bar on top during the call. Then the
interface is working.

Then I tested some incoming calls. 3 attempts with incoming call, dialer
app did not freeze a single time. All buttons for loud voice, stopping
call etc are working. Every time the dialer app shows all symbols, the
calling number etc.

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

Title:
  [krilin] Dialer-app surface freezes during outgoing calls

Status in dialer-app package in Ubuntu:
  Confirmed

Bug description:
  My phone is a BQ Aquaris E4.5 Ubuntu Edition, running with Ubuntu
  15.04 OTA 14 (stable channel).

  The dialer app version installed is 0.1+15.04.20160825.2-0ubuntu1.

  1. What I do
  When I do an outgoing call.

  2. What I expect
  The surface of the app continues to work, I can hang up, put on the 
microphone etc.

  3. What happens 
  The surface of the dialer-app freezes, the call goes on. But I cannot hang 
up, turn on the microphone etc. 

  The only workaround is:
  - close dialer app in Task Manager
  - Open other app.
  - Re-open dialer app via the green bar on the top.
  - Re-opened dialer app has working surface, so I can hang up, turn on the 
microphone etc.

  The bug did already appear in OTA13 and is still present now in OTA
  14.

  The bug does not occure when I accept an incoming call.

  The bus is reproducible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1648224/+subscriptions

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

[Touch-packages] [Bug 1648224] [NEW] [krilin] Dialer-app surface freezes during outgoing calls

[Roman B]

Public bug reported:

My phone is a BQ Aquaris E4.5 Ubuntu Edition, running with Ubuntu 15.04
OTA 14 (stable channel).

The dialer app version installed is 0.1+15.04.20160825.2-0ubuntu1.

1. What I do
When I do an outgoing call.

2. What I expect
The surface of the app continues to work, I can hang up, put on the microphone 
etc.

3. What happens 
The surface of the dialer-app freezes, the call goes on. But I cannot hang up, 
turn on the microphone etc. 

The only workaround is:
- close dialer app in Task Manager
- Open other app.
- Re-open dialer app via the green bar on the top.
- Re-opened dialer app has working surface, so I can hang up, turn on the 
microphone etc.

The bug did already appear in OTA13 and is still present now in OTA 14.

The bug does not occure when I accept an incoming call.

The bus is reproducible.

** Affects: dialer-app (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  [krilin] Dialer-app surface freezes during outgoing calls

Status in dialer-app package in Ubuntu:
  New

Bug description:
  My phone is a BQ Aquaris E4.5 Ubuntu Edition, running with Ubuntu
  15.04 OTA 14 (stable channel).

  The dialer app version installed is 0.1+15.04.20160825.2-0ubuntu1.

  1. What I do
  When I do an outgoing call.

  2. What I expect
  The surface of the app continues to work, I can hang up, put on the 
microphone etc.

  3. What happens 
  The surface of the dialer-app freezes, the call goes on. But I cannot hang 
up, turn on the microphone etc. 

  The only workaround is:
  - close dialer app in Task Manager
  - Open other app.
  - Re-open dialer app via the green bar on the top.
  - Re-opened dialer app has working surface, so I can hang up, turn on the 
microphone etc.

  The bug did already appear in OTA13 and is still present now in OTA
  14.

  The bug does not occure when I accept an incoming call.

  The bus is reproducible.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1648224/+subscriptions

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

[Touch-packages] [Bug 1615559] [NEW] package sudo 1.8.16-0ubuntu1.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 9

[Roman Směták]

Public bug reported:

During installation, appears information about this problem.
Installation can't install or remove package sudo.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: sudo 1.8.16-0ubuntu1.1
ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
Uname: Linux 4.4.0-22-generic i686
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: i386
Date: Mon Aug 22 10:54:03 2016
ErrorMessage: subprocess installed post-installation script returned error exit 
status 9
InstallationDate: Installed on 2015-12-27 (238 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: sudo
Title: package sudo 1.8.16-0ubuntu1.1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 9
UpgradeStatus: Upgraded to xenial on 2016-07-31 (21 days ago)
VisudoCheck:
 /etc/sudoers: rozbor úspěšný
 /etc/sudoers.d/README: rozbor úspěšný

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

Title:
  package sudo 1.8.16-0ubuntu1.1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 9

Status in sudo package in Ubuntu:
  New

Bug description:
  During installation, appears information about this problem.
  Installation can't install or remove package sudo.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: sudo 1.8.16-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic i686
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  Date: Mon Aug 22 10:54:03 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 9
  InstallationDate: Installed on 2015-12-27 (238 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: sudo
  Title: package sudo 1.8.16-0ubuntu1.1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 9
  UpgradeStatus: Upgraded to xenial on 2016-07-31 (21 days ago)
  VisudoCheck:
   /etc/sudoers: rozbor úspěšný
   /etc/sudoers.d/README: rozbor úspěšný

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

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

[Touch-packages] [Bug 1605117] Re: Unity greeter indicators don't show on second launch

[Roman Shipovskij]

Updating from xenial-proposed fixes the problem:

~# apt-cache policy lightdm
lightdm:
  Installed: 1.18.2-0ubuntu2
  Candidate: 1.18.2-0ubuntu2
  Version table:
 *** 1.18.2-0ubuntu2 500
500 http://archive.ubuntu.com/ubuntu xenial-proposed/main i386 Packages
100 /var/lib/dpkg/status
 1.18.2-0ubuntu1 500
500 http://archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages
 1.18.1-0ubuntu1 500
500 http://archive.ubuntu.com/ubuntu xenial/main i386 Packages


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

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

Title:
  Unity greeter indicators don't show on second launch

Status in Light Display Manager:
  Fix Committed
Status in lightdm package in Ubuntu:
  Fix Committed
Status in lightdm source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  Unity Greeter indicators don't show second time greeter started.

  [Test Case]
  1. Log in with greeter
  2. Log out

  Expected result:
  Unity greeter is shown with all UI elements as in step 1.

  Observed result:
  Unity greeter is shown but only one indicator shows (accessibility)

  [Regression potential]
  Low. The fix was already present in the Bzr branch (removed some unneeded 
code that would accidentally close stdin). The fix was not released since it 
hadn't been shown to be a problem before this report.

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

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

[Touch-packages] [Bug 1605117] [NEW] LightDM tray items disappear after logout

[Roman Shipovskij]

Public bug reported:

LightDM tray items disappear after logout

Steps to reproduce:
1) install latest LightDM updates (reboot)
2) login
3) logout

Downgrading to LightDM 1.18.1-0ubuntu1 fix problem

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: lightdm 1.18.2-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic i686
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: i386
CurrentDesktop: Unity
Date: Thu Jul 21 10:57:44 2016
InstallationDate: Installed on 2016-05-23 (58 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: lightdm (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: apport-bug i386 regression-update xenial

** Attachment added: "LightDM tray items disappear after logout"
   
https://bugs.launchpad.net/bugs/1605117/+attachment/4704445/+files/VirtualBox_Ubuntu%2016.04_21_07_2016_10_57_07.png

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

Title:
  LightDM tray items disappear after logout

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  LightDM tray items disappear after logout

  Steps to reproduce:
  1) install latest LightDM updates (reboot)
  2) login
  3) logout

  Downgrading to LightDM 1.18.1-0ubuntu1 fix problem

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: Unity
  Date: Thu Jul 21 10:57:44 2016
  InstallationDate: Installed on 2016-05-23 (58 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1592004] [NEW] Old version of json.vim doesn't allow turning off quote concealment

[Roman Levin]

Public bug reported:

The version of syntax/json.vim bundled with Ubuntu conceals quotes in
JSON files by default (which is bad enough on its own), and does not
allow turning off this behavior without setting conceallevel to 0.

The slightly newer version available at https://github.com/elzr/vim-
json/blob/master/syntax/json.vim has a setting to turn it off.

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

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

Title:
  Old version of json.vim doesn't allow turning off quote concealment

Status in vim package in Ubuntu:
  New

Bug description:
  The version of syntax/json.vim bundled with Ubuntu conceals quotes in
  JSON files by default (which is bad enough on its own), and does not
  allow turning off this behavior without setting conceallevel to 0.

  The slightly newer version available at https://github.com/elzr/vim-
  json/blob/master/syntax/json.vim has a setting to turn it off.

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

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

[Touch-packages] [Bug 1424263] Re: Broken dependencies

[Roman Romanov]

After copying content of sources list:

sudo apt-get install  libc6:i386  libgl1-mesa-dri-lts-wily:i386  
libgl1-mesa-glx-lts-wily:i386
Reading package lists... Done
Building dependency tree   
Reading state information... Done
libc6:i386 is already the newest version.
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libgl1-mesa-glx-lts-wily:i386 : Depends: libudev1:i386 but it is not going to 
be installed
E: Unable to correct problems, you have held broken packages.

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

Title:
  Broken dependencies

Status in mesa package in Ubuntu:
  Confirmed
Status in steam package in Ubuntu:
  Confirmed

Bug description:
  I can not install Steam from Steam website because reported package
  has broken dependencies. This bug affect any user that will install
  Ubuntu 14.04.2. Please fix it fast, cause i can not play my games on
  Linux.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libgl1-mesa-dri:i386 (not installed)
  ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  346.35  Sat Jan 10 21:27:15 
PST 2015
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Feb 21 21:40:49 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 346.35, 3.16.0-30-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GM107 [GeForce GTX 750 Ti] [10de:1380] (rev a2) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:84ac]
  InstallationDate: Installed on 2015-02-20 (1 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic.efi.signed 
root=UUID=ea315497-1076-4f76-a2da-dc65caca572f ro quiet splash loglevel=0 
vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.10
  dmi.board.name: H87 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd07/09/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH87Pro4: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 N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sat Feb 21 17:22:09 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.16.0-1ubuntu1.2~trusty2

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

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

[Touch-packages] [Bug 1424263] Re: Broken dependencies

[Roman Romanov]

< https://www.dropbox.com/s/xm1svcm694sph46/repo?dl=0

All content of my sources.list:

# deb cdrom:[Ubuntu 14.04.4 LTS _Trusty Tahr_ - Release amd64
(20160217.1)]/ trusty main restricted

# See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to
# newer versions of the distribution.
deb http://linux.psu.ru/ubuntu/ trusty main restricted
deb-src http://linux.psu.ru/ubuntu/ trusty main restricted

## Major bug fix updates produced after the final release of the
## distribution.
deb http://linux.psu.ru/ubuntu/ trusty-updates main restricted
deb-src http://linux.psu.ru/ubuntu/ trusty-updates main restricted

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team. Also, please note that software in universe WILL NOT receive any
## review or updates from the Ubuntu security team.
deb http://linux.psu.ru/ubuntu/ trusty universe
deb-src http://linux.psu.ru/ubuntu/ trusty universe
deb http://linux.psu.ru/ubuntu/ trusty-updates universe
deb-src http://linux.psu.ru/ubuntu/ trusty-updates universe

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu 
## team, and may not be under a free licence. Please satisfy yourself as to 
## your rights to use the software. Also, please note that software in 
## multiverse WILL NOT receive any review or updates from the Ubuntu
## security team.
deb http://linux.psu.ru/ubuntu/ trusty multiverse
deb-src http://linux.psu.ru/ubuntu/ trusty multiverse
deb http://linux.psu.ru/ubuntu/ trusty-updates multiverse
deb-src http://linux.psu.ru/ubuntu/ trusty-updates multiverse

## N.B. software from this repository may not have been tested as
## extensively as that contained in the main release, although it includes
## newer versions of some applications which may provide useful features.
## Also, please note that software in backports WILL NOT receive any review
## or updates from the Ubuntu security team.
deb http://linux.psu.ru/ubuntu/ trusty-backports main restricted universe 
multiverse
deb-src http://linux.psu.ru/ubuntu/ trusty-backports main restricted universe 
multiverse

deb http://linux.psu.ru/ubuntu/ trusty-security main restricted
deb-src http://linux.psu.ru/ubuntu/ trusty-security main restricted
deb http://linux.psu.ru/ubuntu/ trusty-security universe
deb-src http://linux.psu.ru/ubuntu/ trusty-security universe
deb http://linux.psu.ru/ubuntu/ trusty-security multiverse
deb-src http://linux.psu.ru/ubuntu/ trusty-security multiverse

## Uncomment the following two lines to add software from Canonical's
## 'partner' repository.
## This software is not part of Ubuntu, but is offered by Canonical and the
## respective vendors as a service to Ubuntu users.
deb http://archive.canonical.com/ubuntu trusty partner
deb-src http://archive.canonical.com/ubuntu trusty partner

## This software is not part of Ubuntu, but is offered by third-party
## developers who want to ship their latest software.
deb http://extras.ubuntu.com/ubuntu trusty main
deb-src http://extras.ubuntu.com/ubuntu trusty main
deb http://archive.canonical.com/ trusty partner
# deb-src http://archive.canonical.com/ trusty partner
deb http://llvm.org/apt/trusty/ llvm-toolchain-trusty-3.8 main
# deb-src http://llvm.org/apt/trusty/ llvm-toolchain-trusty-3.8 main

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

Title:
  Broken dependencies

Status in mesa package in Ubuntu:
  Confirmed
Status in steam package in Ubuntu:
  Confirmed

Bug description:
  I can not install Steam from Steam website because reported package
  has broken dependencies. This bug affect any user that will install
  Ubuntu 14.04.2. Please fix it fast, cause i can not play my games on
  Linux.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libgl1-mesa-dri:i386 (not installed)
  ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  346.35  Sat Jan 10 21:27:15 
PST 2015
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Feb 21 21:40:49 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 346.35, 3.16.0-30-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GM107 [GeForce GTX 750 Ti] [10de:1380] (rev a2) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:84ac]
  InstallationDate: Installed on 2015-02-20 (1 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   

[Touch-packages] [Bug 1424263] Re: Broken dependencies

[Roman Romanov]

I have Ubuntu 64 bit

sudo apt-get install --install-recommends linux-generic-lts-wily
xserver-xorg-core-lts-wily xserver-xorg-lts-wily xserver-xorg-video-all-
lts-wily xserver-xorg-input-all-lts-wily libwayland-egl1-mesa-lts-wily
libgl1-mesa-glx-lts-wily libgl1-mesa-glx-lts-wily:i386 libglapi-mesa-
lts-wily:i386

Reading package lists... Done
Building dependency tree   
Reading state information... Done
Package libgl1-mesa-glx-lts-wily:i386 is not available, but is referred to by 
another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'libgl1-mesa-glx-lts-wily:i386' has no installation candidate
E: Unable to locate package libglapi-mesa-lts-wily


In my sources.list:

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
## team. Also, please note that software in universe WILL NOT receive any
## review or updates from the Ubuntu security team.
deb http://linux.psu.ru/ubuntu/ trusty universe
deb-src http://linux.psu.ru/ubuntu/ trusty universe
deb http://linux.psu.ru/ubuntu/ trusty-updates universe
deb-src http://linux.psu.ru/ubuntu/ trusty-updates universe

## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu 
## team, and may not be under a free licence. Please satisfy yourself as to 
## your rights to use the software. Also, please note that software in 
## multiverse WILL NOT receive any review or updates from the Ubuntu
## security team.
deb http://linux.psu.ru/ubuntu/ trusty multiverse
deb-src http://linux.psu.ru/ubuntu/ trusty multiverse
deb http://linux.psu.ru/ubuntu/ trusty-updates multiverse
deb-src http://linux.psu.ru/ubuntu/ trusty-updates multiverse

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

Title:
  Broken dependencies

Status in mesa package in Ubuntu:
  Confirmed
Status in steam package in Ubuntu:
  Confirmed

Bug description:
  I can not install Steam from Steam website because reported package
  has broken dependencies. This bug affect any user that will install
  Ubuntu 14.04.2. Please fix it fast, cause i can not play my games on
  Linux.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libgl1-mesa-dri:i386 (not installed)
  ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  346.35  Sat Jan 10 21:27:15 
PST 2015
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Feb 21 21:40:49 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 346.35, 3.16.0-30-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GM107 [GeForce GTX 750 Ti] [10de:1380] (rev a2) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:84ac]
  InstallationDate: Installed on 2015-02-20 (1 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic.efi.signed 
root=UUID=ea315497-1076-4f76-a2da-dc65caca572f ro quiet splash loglevel=0 
vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.10
  dmi.board.name: H87 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd07/09/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH87Pro4: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 N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  

[Touch-packages] [Bug 1424263] Re: Broken dependencies

[Roman Romanov]

sudo apt-get install  libc6:i386  libgl1-mesa-dri-lts-wily:i386  
libgl1-mesa-glx-lts-wily:i386
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Package libgl1-mesa-dri-lts-wily:i386 is not available, but is referred to by 
another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
  libgl1-mesa-glx-lts-wily

Package libgl1-mesa-glx-lts-wily:i386 is not available, but is referred to by 
another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'libgl1-mesa-dri-lts-wily:i386' has no installation candidate
E: Package 'libgl1-mesa-glx-lts-wily:i386' has no installation candidate

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

Title:
  Broken dependencies

Status in mesa package in Ubuntu:
  Confirmed
Status in steam package in Ubuntu:
  Confirmed

Bug description:
  I can not install Steam from Steam website because reported package
  has broken dependencies. This bug affect any user that will install
  Ubuntu 14.04.2. Please fix it fast, cause i can not play my games on
  Linux.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libgl1-mesa-dri:i386 (not installed)
  ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  346.35  Sat Jan 10 21:27:15 
PST 2015
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Feb 21 21:40:49 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 346.35, 3.16.0-30-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GM107 [GeForce GTX 750 Ti] [10de:1380] (rev a2) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:84ac]
  InstallationDate: Installed on 2015-02-20 (1 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic.efi.signed 
root=UUID=ea315497-1076-4f76-a2da-dc65caca572f ro quiet splash loglevel=0 
vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.10
  dmi.board.name: H87 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd07/09/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH87Pro4: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 N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sat Feb 21 17:22:09 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.16.0-1ubuntu1.2~trusty2

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

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

[Touch-packages] [Bug 1424263] Re: Broken dependencies

[Roman Romanov]

I confirm the bug on a clean installation 14.04.4

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

Title:
  Broken dependencies

Status in mesa package in Ubuntu:
  Confirmed
Status in steam package in Ubuntu:
  Confirmed

Bug description:
  I can not install Steam from Steam website because reported package
  has broken dependencies. This bug affect any user that will install
  Ubuntu 14.04.2. Please fix it fast, cause i can not play my games on
  Linux.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: libgl1-mesa-dri:i386 (not installed)
  ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  346.35  Sat Jan 10 21:27:15 
PST 2015
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Feb 21 21:40:49 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 346.35, 3.16.0-30-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GM107 [GeForce GTX 750 Ti] [10de:1380] (rev a2) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:84ac]
  InstallationDate: Installed on 2015-02-20 (1 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-30-generic.efi.signed 
root=UUID=ea315497-1076-4f76-a2da-dc65caca572f ro quiet splash loglevel=0 
vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/09/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.10
  dmi.board.name: H87 Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.10:bd07/09/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH87Pro4: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 N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sat Feb 21 17:22:09 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.16.0-1ubuntu1.2~trusty2

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

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

[Touch-packages] [Bug 1406203] Re: Xerox WorkCentre 3220 needs usb-no-reattach-default=true

[Roman Shipovskij]

Problem still exist in 16.04 (Xenial Xerus)

** Tags added: xenial

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

Title:
  Xerox WorkCentre 3220 needs usb-no-reattach-default=true

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  release: Ubuntu 14.04
  cups: 1.7.2-0ubuntu1.2

  same as for Xerox WorkCentre 3210:
  https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1102470

  following instruction from this bug in post #55:
  https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1032456

  this command was help me to solve printing problems

  lpadmin -p  -o usb-no-reattach-default=true

  lsusb
  ...
  Bus 001 Device 002: ID 0924:4294 Xerox
  ...

  please fix this issue

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

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

[Touch-packages] [Bug 1537317] [NEW] package openssh-server 1:6.9p1-2ubuntu0.1 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1

[Roman]

Public bug reported:

Настраивается пакет openssh-server (1:6.9p1-2ubuntu0.1) …
insserv: warning: script 'K07smfpd' missing LSB tags and overrides
insserv: warning: script 'smfpd' missing LSB tags and overrides
insserv: There is a loop at service rc.local if started
insserv: There is a loop between service rc.local and urandom if started
insserv:  loop involving service urandom at depth 4
insserv:  loop involving service hwclock at depth 3
insserv: There is a loop between service smfpd and udev if started
insserv:  loop involving service udev at depth 1
insserv:  loop involving service networking at depth 6
insserv:  loop involving service mountdevsubfs at depth 3
insserv:  loop involving service mountkernfs at depth 1
insserv: There is a loop at service smfpd if started
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!

[Touch-packages] [Bug 1536930] [NEW] package rsync 3.1.1-3ubuntu0.15.10.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Roman]

Public bug reported:

Настраивается пакет rsync (3.1.1-3ubuntu0.15.10.1) …
insserv: warning: script 'K07smfpd' missing LSB tags and overrides
insserv: warning: script 'smfpd' missing LSB tags and overrides
insserv: There is a loop at service rc.local if started
insserv: There is a loop between service rc.local and urandom if started
insserv:  loop involving service urandom at depth 4
insserv:  loop involving service hwclock at depth 3
insserv: There is a loop between service smfpd and udev if started
insserv:  loop involving service udev at depth 1
insserv:  loop involving service networking at depth 6
insserv:  loop involving service mountdevsubfs at depth 3
insserv:  loop involving service mountkernfs at depth 1
insserv: There is a loop at service smfpd if started
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on rc.local and therefore on system facility 
`$all' which can not be true!
insserv: 

[Touch-packages] [Bug 1124071] Re: [tabs] + [header sections] Cannot add Tabs programmatically

[Roman Shchekin]

Sooo? Should we use another component for tabs?

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

Title:
  [tabs] + [header sections] Cannot add Tabs programmatically

Status in Ubuntu Shorts App:
  Confirmed
Status in Ubuntu UI Toolkit:
  Fix Released
Status in Ubuntu UX:
  Fix Committed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Released
Status in ubuntu-ui-toolkit source package in Trusty:
  Confirmed
Status in ubuntu-ui-toolkit source package in Vivid:
  New

Bug description:
  There seems to be no easy way to add a Tab to Tabs programmatically.

  I would be nice to be able add, remove and edit Tabs dynamically. So
  far I haven't found a way to do this.

  I have made an Android style ViewPager based on ListView. It is quite
  easy to update the pages with ListModel methods.

  
   UX Comment ---

  Tabs component is not deprecated from UITK point of view. Design uses 
slightly different naming than UITK for components they design, we call "Tabs" 
now "Header Sections". This is a bar which sits below the main header. 
  An other option to add "tabs" to your UI, allowing user to navigate through 
different sections of the app, is a navigation drawer on the left hand side of 
the header.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-rssreader-app/+bug/1124071/+subscriptions

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

[Touch-packages] [Bug 1525072] [NEW] package lightdm 1.16.6-0ubuntu1 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1

[Roman]

Public bug reported:

Настраивается пакет lightdm (1.16.6-0ubuntu1) …
insserv: warning: script 'K01smfpd' missing LSB tags and overrides
insserv: warning: script 'smfpd' missing LSB tags and overrides
insserv: There is a loop between service ondemand and urandom if started
insserv:  loop involving service urandom at depth 4
insserv:  loop involving service hwclock at depth 3
insserv: There is a loop between service ondemand and udev if started
insserv:  loop involving service udev at depth 1
insserv: Starting smfpd depends on ondemand and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on ondemand and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on ondemand and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on ondemand and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on ondemand and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on ondemand and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on ondemand and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on ondemand and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on ondemand and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on ondemand and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on ondemand and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on ondemand and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on ondemand and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on ondemand and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on ondemand and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on ondemand and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on ondemand and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on ondemand and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on ondemand and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on ondemand and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on ondemand and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on ondemand and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on ondemand and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on ondemand and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on ondemand and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on ondemand and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on ondemand and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on ondemand and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on ondemand and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on ondemand and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on ondemand and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on ondemand and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on ondemand and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on ondemand and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on ondemand and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on ondemand and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on ondemand and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on ondemand and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on ondemand and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on ondemand and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on ondemand and therefore on system facility 
`$all' which can not be true!
insserv: Starting smfpd depends on ondemand and therefore on system 

[Touch-packages] [Bug 1512111] Re: "Ubuntu Light" font has heavier weight than "Ubuntu"

[Roman Litvinenko]

** Also affects: ubuntu-font-family
   Importance: Undecided
   Status: New

** No longer affects: ubuntu-font-family

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

Title:
  "Ubuntu Light" font has heavier weight than "Ubuntu"

Status in ubuntu-font-family-sources package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from Vivid to Wily, pages using the "Ubuntu light" font 
actually renders with a weight heavier than the regular one in web pages.
  This happens with Chrome/Chromium and also the Ubuntu browser.

  After manually reinstalling the 0.80-0ubuntu6 version from Vivid (in
  place of 0.83-0ubuntu1), the issue is fixed.

  See the attached screenshot showing the result seen browing
  https://www.google.com/fonts#UsePlace:use/Collection:Ubuntu

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: ttf-ubuntu-font-family 0.83-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-17.21-generic 4.2.3
  Uname: Linux 4.2.0-17-generic x86_64
  ApportVersion: 2.19.1-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Nov  1 17:55:19 2015
  Dependencies:

  InstallationDate: Installed on 2014-10-14 (382 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140923)
  PackageArchitecture: all
  SourcePackage: ubuntu-font-family-sources
  UpgradeStatus: Upgraded to wily on 2015-10-31 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-font-family-sources/+bug/1512111/+subscriptions

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

[Touch-packages] [Bug 1508363] Re: Coordinated migration to UITK 1.3

[Roman Shchekin]

** Also affects: ubuntu-rssreader-app
   Importance: Undecided
   Status: New

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

Title:
  Coordinated migration to UITK 1.3

Status in Canonical System Image:
  In Progress
Status in Ubuntu Music App:
  In Progress
Status in Ubuntu Notes app:
  New
Status in Ubuntu Calculator App:
  In Progress
Status in Ubuntu Calendar App:
  New
Status in Ubuntu Clock App:
  In Progress
Status in Ubuntu Document Viewer App:
  In Progress
Status in Ubuntu Shorts App:
  New
Status in Ubuntu Weather App:
  Triaged
Status in Weather:
  New
Status in address-book-app package in Ubuntu:
  In Progress
Status in calendar-app package in Ubuntu:
  Confirmed
Status in camera-app package in Ubuntu:
  In Progress
Status in dialer-app package in Ubuntu:
  In Progress
Status in gallery-app package in Ubuntu:
  In Progress
Status in messaging-app package in Ubuntu:
  In Progress
Status in music-app package in Ubuntu:
  Confirmed
Status in reminders-app package in Ubuntu:
  Fix Committed
Status in ubuntu-clock-app package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  In Progress
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  In Progress
Status in ubuntu-weather-app package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  In Progress
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  The migration to 1.3 needs to happen in a coordinated way, so that
  shell and all apps we care of migrate within the same OTA window to
  reduce visual inconsistencies to a minimum.

  This bug is a means to collect all the projects affected and keep tabs
  on what's happening.

  NOTES:
  - *All* Ubuntu.Components imports (including ListItems, Popups, Pickers,
    Theme, Styles etc.) should go to 1.3.
  - Theme is now theme (lowercase)
  - PageHeadStyle now has a "config" property

  QUESTION:
  In manifest.json file, should we use:
 "framework": "ubuntu-sdk-15.04-qml",
  or
 "framework": "ubuntu-sdk-15.04.1-qml",
  ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1508363/+subscriptions

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

[Touch-packages] [Bug 1501617] Re: X crashes on my intel card

[Roman Shipovskij]

It would be good to fix the problem on Trusty not in LTS enablement
stack.

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

Title:
  X crashes on my intel card

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  X crashes on my intel card on LibreOffice print dialog.

  How to reproduce:
  just open attached X_crash_on_ LibreOffice print dialog.odt and try to print 
it by pressing Ctrl+P or from menu, do not use quick print, problem appears on 
print dialog

  Switching to UXA AccelMethod solve this problem:
  ~# cat /usr/share/X11/xorg.conf.d/10-disable-sna.conf
  Section "Device"
  Identifier "Intel Graphics"
  Driver "intel"
  Option "AccelMethod" "uxa"
  EndSection

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-63.103-generic 3.13.11-ckt25
  Uname: Linux 3.13.0-63-generic i686
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.1-0ubuntu3.13
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: Unity
  Date: Thu Oct  1 09:59:23 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated Graphics 
Controller [8086:a001] (rev 02) (prog-if 00 [VGA controller])
     Subsystem: Acer Incorporated [ALI] Device [1025:039d]
     Subsystem: Acer Incorporated [ALI] Device [1025:039d]
  MachineType: eMachines EZ1700
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-63-generic 
root=UUID=8ffec55a-01eb-4d77-8f7d-ebe714e7dc27 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/14/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P01-A0L
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: EZ1700
  dmi.board.vendor: eMachines
  dmi.chassis.type: 13
  dmi.chassis.vendor: eMachines
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP01-A0L:bd07/14/2010:svneMachines:pnEZ1700:pvr:rvneMachines:rnEZ1700:rvr:cvneMachines:ct13:cvr:
  dmi.product.name: EZ1700
  dmi.sys.vendor: eMachines
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.4
  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.6
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Thu Oct  1 09:56:20 2015
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputChicony 2.4G Multimedia Wireless Kit KEYBOARD, id 8
   inputChicony 2.4G Multimedia Wireless Kit KEYBOARD, id 9
   inputUSB 2.0 Camera   KEYBOARD, id 10
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 256
   vendor ACR
  xserver.version: 2:1.15.1-0ubuntu2.7

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

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