date:20180119

[Touch-packages] [Bug 289592] Re: Unknown media types in /usr/share/mime/packages/kde.xml

2018-01-19 Thread Paulo Marcel Coelho Aragão

In xubuntu 17.10, kdelibs5-data 4.14.34-0ubuntu2, file
/usr/share/mime/packages/kde.xml still includes MIME types all/all and
all/allfiles.

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

Title:
  Unknown media types in /usr/share/mime/packages/kde.xml

Status in kdelibs:
  Won't Fix
Status in shared-mime-info:
  Confirmed
Status in kde4libs package in Ubuntu:
  Confirmed
Status in shared-mime-info package in Ubuntu:
  Triaged
Status in shared-mime-info package in Debian:
  Confirmed

Bug description:
  Here is the problem:

  # update-mime-database /usr/share/mime
  [...]
  Unknown media type in type 'uri/mms'

  Unknown media type in type 'uri/mmst'

  Unknown media type in type 'uri/mmsu'

  Unknown media type in type 'uri/pnm'

  Unknown media type in type 'uri/rtspt'

  Unknown media type in type 'uri/rtspu'

  It seems to come from this file:
/usr/share/mime/packages/kde.xml

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

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

[Touch-packages] [Bug 1743710] Re: Ubuntu 16.04: since 2018 all dropdown menus black and unreadable

2018-01-19 Thread linuxcub

If I follow this link, I get to https://launchpad.net/~smusnmr/+oauth-
tokens and read

"
Authorized applications

These applications have been authorized to access Launchpad on your behalf. If 
you revoke an authorization, that application will not be allowed to do 
anything in Launchpad on your behalf.
Claimed tokens:
None

Unclaimed tokens:
None
"
Does it mean I should authorize again and leave the authorization on 
indefinetly? Should I leave my notebook on and not logout out of launchpad?

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

Title:
  Ubuntu 16.04: since 2018 all dropdown menus black and unreadable

Status in ubuntu-themes package in Ubuntu:
  Incomplete

Bug description:
  Since 23018 all dropdown menus in my Ubuntu 16.04 LTS have a black background 
and the text, i.e., file-save-as options are unreadable. After a fresh install 
the menus are ok, but after the first necessary updates, same problem! The 
menus if firefox and thunderbird are readable, but e.g., Libreoffice writer, 
Gimp you name it, are not. I have described this in detail in 
  https://ubuntuforums.org/showthread.php?t=2382505=13730458#post13730458
  and also my workaround to solve it,
  changing the file /usr/share/themes/Ambiance/gtk-2.0/gtkrc
  But I am afraid, with the next bigger Ubuntu update the error will be back 
again?

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

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

[Touch-packages] [Bug 1744429] [NEW] xorg sometimes freezes up while playing either vlc or youtube

2018-01-19 Thread gregrwm

Public bug reported:

i don't watch heaps, but enough that xorg has frozen up on me about 3
times in the last week both in vlc and youtube.  This time in particular
it was playing youtube when it froze, the sound played on a bit further
then it stopped too, the mouse was still able to move the cursor but
nothing else, for example usually merely moving the mouse would shift
the border highlight to the newly focused window, but even that wouldn't
happen when it froze up.  i logged in via ssh and invoked ubuntu-bug
xorg.  then after that i used the ssh session to kill my window manager,
twm, which caused the xorg session to logout.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
Uname: Linux 4.4.0-98-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Fri Jan 19 15:29:45 2018
InstallationDate: Installed on 2016-10-15 (460 days ago)
InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720)
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  xorg sometimes freezes up while playing either vlc or youtube

Status in xorg package in Ubuntu:
  New

Bug description:
  i don't watch heaps, but enough that xorg has frozen up on me about 3
  times in the last week both in vlc and youtube.  This time in
  particular it was playing youtube when it froze, the sound played on a
  bit further then it stopped too, the mouse was still able to move the
  cursor but nothing else, for example usually merely moving the mouse
  would shift the border highlight to the newly focused window, but even
  that wouldn't happen when it froze up.  i logged in via ssh and
  invoked ubuntu-bug xorg.  then after that i used the ssh session to
  kill my window manager, twm, which caused the xorg session to logout.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Fri Jan 19 15:29:45 2018
  InstallationDate: Installed on 2016-10-15 (460 days ago)
  InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1574667] Re: Mouse pointer occasionally jumps to the bottom-left corner

2018-01-19 Thread jpvrlaone

I had the same problem on my desktop with Ubuntu 16.04 but #32 worked
for me.  It too was driving me crazy.

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

Title:
  Mouse pointer occasionally jumps to the bottom-left corner

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Sometimes the mouse pointer jumps directly to the bottom-left corner
  of the screen, which results in opening the trash window when
  clicking.

  This seems to be related: https://ubuntu-mate.community/t/mouse-
  pointer-jumps-on-clicking-touchpad/2932.

  Thanks,
  MZ

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  BootLog: /dev/sda6: clean, 276587/40779776 files, 15261626/163117056 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Apr 25 15:55:54 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:06b2]
  InstallationDate: Installed on 2016-04-23 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:07dc Intel Corp. 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 064e:920b Suyin Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5559
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=c5bc0a1d-3fe9-4ae5-81e9-de7d141b419c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.5
  dmi.board.name: 06CMH7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.5:bd12/21/2015:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn06CMH7:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5559
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Apr 25 13:43:44 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1156 
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2

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

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

[Touch-packages] [Bug 1744421] Re: I tried to upgrade from 16.4 to 17.10

2018-01-19 Thread Seth Arnold

Hello, note that apt-get -u dist-upgrade is not actually a supported
mechanism to upgrade from one release to another. The supported
mechanism is via the do-release-upgrade tool in the ubuntu-release-
upgrader-core package.

Probably you can make this work somehow, but it might be best to look
for interactive help in #ubuntu on irc.freenode.net or
https://askubuntu.com.

Thanks

** Information type changed from Private Security to Public

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

Title:
  I tried to upgrade from 16.4 to 17.10

Status in xorg package in Ubuntu:
  New

Bug description:
  Trying to upgrade from version 16.04 to 17.10, I used the following
  command line:

  sudo apt update && sudo apt dist -upgrade

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Jan 20 00:03:32 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.40, 4.10.0-42-generic, x86_64: installed
   virtualbox, 5.0.40, 4.13.0-26-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display 
[8086:0f31] (rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Atom Processor Z36xxx/Z37xxx Series 
Graphics & Display [103c:2209]
  InstallationDate: Installed on 2017-10-27 (84 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1a40:0101 Terminus Technology Inc. Hub
   Bus 001 Device 002: ID 04f2:b40e Chicony Electronics Co., Ltd HP Truevision 
HD camera
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP Pavilion 11 x360 PC
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-26-generic 
root=UUID=9b0f7d79-6ae1-4287-8ac7-7ca5bec70fb0 ro splash quiet
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/13/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.2B
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2209
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 57.54
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.2B:bd06/13/2016:svnHewlett-Packard:pnHPPavilion11x360PC:pvr097810405F00010320180:rvnHewlett-Packard:rn2209:rvr57.54:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=MIN
  dmi.product.name: HP Pavilion 11 x360 PC
  dmi.product.version: 097810405F00010320180
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  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: Fri Jan 19 23:59:58 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: modeset

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

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

[Touch-packages] [Bug 1725840] Re: resolvconf not correctly configured after update from 17.04 to 17.10

2018-01-19 Thread nish

+1 for the issue.

Its broken for some VPN cases. Maintainer please note that some VPN
application updates DNS with resolvconf package and removes those
setting on exist. This is breaking the DNS resolution in some rare
cases.

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

Title:
  resolvconf not correctly configured after update from 17.04 to 17.10

Status in resolvconf package in Ubuntu:
  Confirmed

Bug description:
  After having updated my laptop from Ubuntu 17.04 to 17.10, the DNS
  lookup on my wireless network connection did not work any more.

  As it seems, the file /etc/resolv.conf was static and contained wrong
  data assigned by the NetworkManager. When I changed the file content
  manually to

nameserver 127.0.0.53

  DNS lookup worked fine. After reboot, however, I had to repeat this
  operation since NetworkManager seems to have replaced the file
  content.

  Finally, I found a solution. Running

  sudo dpkg-reconfigure resolvconf

  the file /etc/resolv.conf was replaced by the link

  /etc/resolv.conf -> ../run/resolvconf/resolv.conf

  Now, the wireless network seems to work properly.

  Hence, there must be some kind of bug during the update process from
  Ubuntu 17.04 to 17.10 that impedes resolvconf to be configured
  properly.

  Best regards,

  Artur

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: resolvconf 1.79ubuntu8
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 21 23:17:38 2017
  InstallationDate: Installed on 2013-10-18 (1463 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  PackageArchitecture: all
  SourcePackage: resolvconf
  UpgradeStatus: Upgraded to artful on 2017-10-19 (1 days ago)

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

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

[Touch-packages] [Bug 1736072] Re: Encrypted swap does not work

2018-01-19 Thread Brian Murray

** Tags added: rls-bb-incoming

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

Title:
Encrypted swap does not work

Status in cryptsetup package in Ubuntu:
New
Status in systemd package in Ubuntu:
New
Status in ubiquity package in Ubuntu:
New

Bug description:
On a working system, i've added a new hdd, and decided to use it as the main
device storage.
So after doing the formatage (classic: / as ext4, swap, /home as ext4), i've
set a bionic iso installation.
Ubiquity then have proposed to set an encrypted swap dir, which i have
accepted, and then smootly terminated the installation.

Booting with that new install, i hit a cryptswap1 timeout after beeing
frozen around 1 minute.

oem@ubuntu:~$ journalctl | grep cryptswap
systemd[1]: Starting Cryptography Setup for cryptswap2...
systemd[1]: Started Cryptography Setup for cryptswap2.
systemd[1]: Found device /dev/mapper/cryptswap2.
systemd[1]: Activating swap /dev/mapper/cryptswap2...
kernel: Adding 10584572k swap on /dev/mapper/cryptswap2. Priority:-1
extents:1 across:10584572k FS
systemd[1]: Activated swap /dev/mapper/cryptswap2.
systemd[1]: Starting Cryptography Setup for cryptswap1...
systemd[1]: Started Cryptography Setup for cryptswap1.

oem@ubuntu:~$ journalctl | grep timeout
systemd[1]:
dev-disk-by\x2duuid-4c8437f6\x2d677d\x2d4740\x2dbdda\x2d072efadb49f4.device:
Job
dev-disk-by\x2duuid-4c8437f6\x2d677d\x2d4740\x2dbdda\x2d072efadb49f4.device/start
failed with result 'timeout'.

Note: cryptswap2 refer to the new hdd's swap partition, cryptswap1 refer to
the old hdd's swap partition.
/etc/fstab have been tested with only the active (mounted) disk, and with
both. In both cases the timeout happens.

oem@ubuntu:~$ swapon -s
Filename TypeSizeUsedPriority
/dev/dm-0 partition 10584572
221184 -1

Conclusion:
-ubiquity is proposing a non working feature (at least with multiple storage
devices/swap partitions
- the cryptsetup version is not well supporting the kernel/systemd
settings/configs

As Debian has more recent versions: 1.7.5-1 (sid) and 2.0.0 (experimental)
with some new features and cleanups, it should be a positive test to replace
the actual not working version with one of these.

http://metadata.ftp-master.debian.org/changelogs/main/c/cryptsetup/cryptsetup_2.0.0~rc1-1_changelog

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: cryptsetup 2:1.7.3-4ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-18.21-generic 4.13.13
Uname: Linux 4.13.0-18-generic x86_64
ApportVersion: 2.20.8-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Mon Dec 4 07:26:17 2017
EcryptfsInUse: Yes
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: cryptsetup
UpgradeStatus: No upgrade log present (probably fresh install)
cmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-18-generic
root=UUID=2f22752a-ca0f-4cff-b5d7-9754e6154d56 ro

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

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

[Touch-packages] [Bug 1729836] Re: update-initramfs generating unbootable initrd files when using stderred LD_PRELOAD hook

2018-01-19 Thread Brian Murray

** Changed in: initramfs-tools (Ubuntu)
   Status: Incomplete => Triaged

** Changed in: initramfs-tools (Ubuntu)
   Importance: Undecided => Low

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

Title:
  update-initramfs generating unbootable initrd files when using
  stderred LD_PRELOAD hook

Status in initramfs-tools package in Ubuntu:
  Triaged

Bug description:
  After running 'update-initramfs -u -k $(uname -r)', Linux will not
  boot. With 'quiet splash' set in grub, it appears to freeze after the
  'Loading ramdisk...' message, and if booted in recovery mode, I see
  the following kernel panic:

  Freeing unused kernel memory: 948k
  Freeing unused kernel memory: 104K
  x86/mm: Chcked W+X mappings: passed, no W+X pages found.
  Failed to execute /init (error -2)
  Kernel panic - not syncing: No working init found.  Try passing init= optin 
to kernel. See Linux Documentation/admin-guide/init.rst for guidance.
  CPU: 6 PID: 1 Comm: swapper/0 Not tainted 4.13.0-16-generic #19-Ubuntu
  Hardware name: Dell Inc. OptiPlex 990/0D6H9T, BIOS A07 09/10/2011
  Call Trace:
dump_stack+0x63/0x8b
? rest_init+0xb0/0xc0
panic+0xe4/0x23d
? putname+0x4b/0x50
? rest_init+0xc0/0xc0
kernel_init+0xeb/0xfc
ret_from_fork0x25/0x30
  Kernel Offset: 0x1fc0 from 0x8a00 (relocation range: 
0x8000-0xbfff)
  ---[ end Kernel panic - no syncing: No working init found.  Try passing init= 
option to kernel. See Linux Documentation/admin-guide/init.rst for guidance.

  (full screenshot at https://photos.app.goo.gl/XLNKOM3cDNHsfyFt2).

  Examining the initrd files, here is a good one, as installed by the
  Ubuntu 17.10 installer:

  # file /boot/initrd.img-4.13.0-16-generic
  /boot/initrd.img-4.13.0-16-generic: ASCII cpio archive (SVR4 with no CRC)
  # ls -la /boot/initrd.img-4.13.0-16-generic
  -rw-r--r-- 1 root root 50764087 Nov  3 21:02 
/boot/initrd.img-4.13.0-16-generic

  and here is the file after 'update-initramfs -u -k 4.13.0-16-generic':

  # file /boot/initrd.img-4.13.0-16-generic
  /boot/initrd.img-4.13.0-16-generic: gzip compressed data, last modified: Thu 
Nov  2 10:51:42 2017, from Unix
  root@jturner-home:/boot# ls -la /boot/initrd.img-4.13.0-16-generic
  -rw-r--r-- 1 root root 50895514 Nov  3 21:01 
/boot/initrd.img-4.13.0-16-generic

  Good and bad initrds can be downloaded from
  
https://drive.google.com/drive/folders/1reMWj1TohrQ4K5EbBMJPhw4xXUdBi0K9?usp=sharing

  After downloading initrd.img-4.13.0-16-generic-broken, the panic can
  be replicated in qemu with:

  kvm -m 1G -kernel /boot/vmlinuz-4.13.0-16-generic -initrd
  /boot/initrd.img-4.13.0-16-generic-broken

  (tip obtained from https://lists.debian.org/debian-
  kernel/2016/02/msg00323.html)

  I've experienced this problem with Ubuntu 17.04 and 17.10 on two
  separate PCs (both Dell OptiPlex 990s). Ubuntu boots fine initially,
  until one day I update the kernel or something, and a .deb postinst
  script calls update-initramfs and trashes that kernel's initrd file.
  If I run 'update-initramfs -u -k all', all my old initrd files are
  toast.

  The "good" initrd format "ASCII cpio archive (SVR4 with no CRC)" is
  strange. I'm not getting many google hits on it. None of my other
  Ubuntu/Debian servers use that format in their initrds.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: initramfs-tools 0.125ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  Date: Fri Nov  3 21:33:12 2017
  InstallationDate: Installed on 2017-08-05 (90 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: Upgraded to artful on 2017-10-24 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1729836/+subscriptions

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

[Touch-packages] [Bug 1743401] Re: AddressSanitizer: heap-buffer-overflow in libxkbcommon-x11.so

2018-01-19 Thread Oliver Stöneberg

I rebuild the package without optimizations got some more data. The ASAN
out now matches the gdb one

READ of size 9 at 0x6040001944b8 thread T0
#0 0x14454c2 in __interceptor_strndup 
/opt/media/clang_nightly/llvm/utils/release/final/llvm.src/projects/compiler-rt/lib/asan/../sanitizer_common/sanitizer_common_interceptors.inc:327:3
#1 0x7ffa3f4b06f8 in get_atom_name 
/home/user/libxkbcommon-0.5.0/src/x11/util.c:146
#2 0x7ffa3f4afd63 in get_names 
/home/user/libxkbcommon-0.5.0/src/x11/keymap.c:1092
#3 0x7ffa3f4b026c in xkb_x11_keymap_new_from_device 
/home/user/libxkbcommon-0.5.0/src/x11/keymap.c:1169 

Looking at the variables in the debugger everything seems fine

#7  0x7fffc44236f9 in get_atom_name (conn=0x62aae200, atom=142,
out=0x61bef400) at src/x11/util.c:146
146 *out = strndup(name, length);
(gdb) print length
$1 = 8
(gdb) print name
$2 = 0x6040001944b0 "complete"
(gdb) print name[7]
$3 = 101 'e'
(gdb) print name[8]
$4 = 0 '\000'

But judging from the error message somehow the ASAN peaks beyond its
end.

I was able reproduce this behavior in a small sample and it turns out it
is caused by ASAN_OPTIONS=strict_string_checks=1. So it seems it is a
sanitizer issue. I will bring it up with that team.

Sorry about the apparently faulty report.

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

Title:
  AddressSanitizer: heap-buffer-overflow in libxkbcommon-x11.so

Status in libxkbcommon package in Ubuntu:
  New

Bug description:
  I am running an application which has a feature which utilizes Qt5. For 
testing purposes this application was built with the AddressSanitizer of the 
official clang 5.0.1 binariesfor ubuntu 16.04. This was working fine until a 
few days ago. It started out with another user reporting issues with Qt and the 
pt_BR.UTF-8 locale which I was able to confirm after I installed it. Shorty 
after that I was no longer able to run anything that used the Qt code. I tried 
removing the additional locale or setting a different one via the environment, 
but that didn't help. I also did some changes in the "Text Input" settings like 
removing removing the "English" keyboard layout before I encountered this.
  Unfortunately I didn't have the time yet to set the system back up from 
scratch and try to reproduce what exact change caused this.

  Below I added the traces of ASAN and the debugger.

  The code in question is found in xkbcommon/src/x11/util.c

  length = xcb_get_atom_name_name_length(reply);
  name = xcb_get_atom_name_name(reply);

  *out = strndup(name, length);

  Unfortunately I was not able to see what "name" is, but length was 8.

  lsb_release -rd
  Description:Ubuntu 16.04.3 LTS
  Release:16.04

  libxkbcommon0:
Installed: 0.5.0-1ubuntu2
Candidate: 0.5.0-1ubuntu2
Version table:
   *** 0.5.0-1ubuntu2 500
  500 http://de.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  qt5-default:
Installed: 5.5.1+dfsg-16ubuntu7.5
Candidate: 5.5.1+dfsg-16ubuntu7.5
Version table:
   *** 5.5.1+dfsg-16ubuntu7.5 500
  500 http://de.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   5.5.1+dfsg-16ubuntu7 500
  500 http://de.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  locale
  LANG=en_US.UTF-8
  LANGUAGE=
  LC_CTYPE="en_US.UTF-8"
  LC_NUMERIC=de_DE.UTF-8
  LC_TIME=de_DE.UTF-8
  LC_COLLATE="en_US.UTF-8"
  LC_MONETARY=de_DE.UTF-8
  LC_MESSAGES="en_US.UTF-8"
  LC_PAPER=de_DE.UTF-8
  LC_NAME=de_DE.UTF-8
  LC_ADDRESS=de_DE.UTF-8
  LC_TELEPHONE=de_DE.UTF-8
  LC_MEASUREMENT=de_DE.UTF-8
  LC_IDENTIFICATION=de_DE.UTF-8
  LC_ALL=

  ==3008==ERROR: AddressSanitizer: heap-buffer-overflow on address 
0x60400015c4b8 at pc 0x01445853 bp 0x7ffd07632920 sp 0x7ffd076320b8
  READ of size 9 at 0x60400015c4b8 thread T0
  #0 0x1445852 in __interceptor___strndup 
/opt/media/clang_nightly/llvm/utils/release/final/llvm.src/projects/compiler-rt/lib/asan/../sanitizer_common/sanitizer_common_interceptors.inc:337:3
  #1 0x7fc1481fd70e  
(/usr/lib/x86_64-linux-gnu/libxkbcommon-x11.so.0+0x470e)
  #2 0x7fc1481fcd79 in xkb_x11_keymap_new_from_device 
(/usr/lib/x86_64-linux-gnu/libxkbcommon-x11.so.0+0x3d79)
  #3 0x7fc149cb9c8f  (/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5+0x42c8f)
  #4 0x7fc149cba0ec  (/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5+0x430ec)
  #5 0x7fc149cb4931 in QXcbConnection::QXcbConnection(QXcbNativeInterface*, 
bool, unsigned int, char const*) 
(/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5+0x3d931)
  #6 0x7fc149cb7bac in QXcbIntegration::QXcbIntegration(QStringList const&, 
int&, char**) (/usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5+0x40bac)
  #7 0x7fc149d773ac in _init

[Touch-packages] [Bug 1614299] Re: install failure on python 3.5

2018-01-19 Thread Peter G. Marczis

I added Michael Vogt, as he is the author based on:

https://pypi.python.org/pypi/python-apt
and
https://launchpad.net/python-apt/

Michael, first of all thanks for your great work!
Hope you can help us out here. Do you maintain the pip version of the package? 
Or is that "abandoned", or just left on older version to be compatible with 
Debian? Or so, what should we do :)

I'm happy to maintain the pip version, if you don't have time for this
anymore.

Thanks a lot again for all the help!

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

Title:
  install failure on python 3.5

Status in python-apt package in Ubuntu:
  Confirmed

Bug description:
  Related to expired issue: https://answers.launchpad.net/ubuntu/+source
  /python-apt/+question/285522

  
  snafu$ cd /tmp

  snafu$ pyvenv apt

  snafu$ source apt/bin/activate

  (apt) snafu$ lsb_release -a; uname -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04
  Codename: xenial
  Linux snafu 4.4.0-34-generic #53-Ubuntu SMP Wed Jul 27 16:06:39 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux

  (apt) snafu$ pip install python-apt
  Collecting python-apt
Using cached python-apt-0.7.8.tar.bz2
  Complete output from command python setup.py egg_info:
  Traceback (most recent call last):
File "", line 1, in 
File "/tmp/pip-build-l1pt_xe2/python-apt/setup.py", line 6, in 
  from DistUtilsExtra.command import *
  ImportError: No module named 'DistUtilsExtra'
  
  
  Command "python setup.py egg_info" failed with error code 1 in 
/tmp/pip-build-l1pt_xe2/python-apt/
  You are using pip version 8.1.1, however version 8.1.2 is available.
  You should consider upgrading via the 'pip install --upgrade pip' command.

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

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

[Touch-packages] [Bug 1614299] Re: install failure on python 3.5

2018-01-19 Thread Peter G. Marczis

I have the same issue, while I do understand your point, it can be
installed with apt, but many python developer uses virtual environment,
in which we use pip to install packages, such as is mandatory for cross
distro development.

For example my case is so that I run an other distro on my desktop,
other distro on the build servers, and a 3rd one on the target device,
where I need the package.

I think the real question if Ubuntu is willing to support the pip
version of the package or not? Is it put into pip by canonical on the
first place ?

Thanks a lot in advance!

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

Title:
  install failure on python 3.5

Status in python-apt package in Ubuntu:
  Confirmed

Bug description:
  Related to expired issue: https://answers.launchpad.net/ubuntu/+source
  /python-apt/+question/285522

  
  snafu$ cd /tmp

  snafu$ pyvenv apt

  snafu$ source apt/bin/activate

  (apt) snafu$ lsb_release -a; uname -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04
  Codename: xenial
  Linux snafu 4.4.0-34-generic #53-Ubuntu SMP Wed Jul 27 16:06:39 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux

  (apt) snafu$ pip install python-apt
  Collecting python-apt
Using cached python-apt-0.7.8.tar.bz2
  Complete output from command python setup.py egg_info:
  Traceback (most recent call last):
File "", line 1, in 
File "/tmp/pip-build-l1pt_xe2/python-apt/setup.py", line 6, in 
  from DistUtilsExtra.command import *
  ImportError: No module named 'DistUtilsExtra'
  
  
  Command "python setup.py egg_info" failed with error code 1 in 
/tmp/pip-build-l1pt_xe2/python-apt/
  You are using pip version 8.1.1, however version 8.1.2 is available.
  You should consider upgrading via the 'pip install --upgrade pip' command.

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

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

[Touch-packages] [Bug 1744372] Re: gparted does not start - Unit -.mount does not exist, proceeding anyway.

2018-01-19 Thread Thomas Beyer

thank you #3

But it is more about having wayland as default and not beeing able to
use gparted withing 18.04 LTS!

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

Title:
  gparted does not start - Unit -.mount does not exist, proceeding
  anyway.

Status in gparted package in Ubuntu:
  New
Status in wayland package in Ubuntu:
  Invalid

Bug description:
  1. fresh ubuntu 18.04 daily: lsb_release -rd
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  2. install gparted with Software:
  gparted:
    Installiert:   0.30.0-3ubuntu1
    Installationskandidat: 0.30.0-3ubuntu1
    Versionstabelle:
   *** 0.30.0-3ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  3. launch with icon - enter password - nothing.
  4.launch in terminal:
  Unit -.mount does not exist, proceeding anyway.
  Created symlink /run/systemd/system/-.mount → /dev/null.
  Created symlink /run/systemd/system/boot-efi.mount → /dev/null.
  Created symlink /run/systemd/system/home.mount → /dev/null.
  Created symlink /run/systemd/system/run-snapd-ns-vlc.mnt.mount → /dev/null.
  Created symlink /run/systemd/system/run-snapd-ns.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-120.mount → /dev/null.
  Created symlink /run/systemd/system/snap-core-3748.mount → /dev/null.
  Created symlink /run/systemd/system/snap-vlc-113.mount → /dev/null.
  Created symlink /run/systemd/system/tmp.mount → /dev/null.
  No protocol specified

  (gpartedbin:8328): Gtk-WARNING **: cannot open display: :0
  Removed /run/systemd/system/-.mount.
  Removed /run/systemd/system/boot-efi.mount.
  Removed /run/systemd/system/home.mount.
  Removed /run/systemd/system/run-snapd-ns-vlc.mnt.mount.
  Removed /run/systemd/system/run-snapd-ns.mount.
  Removed /run/systemd/system/run-user-1000.mount.
  Removed /run/systemd/system/run-user-120.mount.
  Removed /run/systemd/system/snap-core-3748.mount.
  Removed /run/systemd/system/snap-vlc-113.mount.
  Removed /run/systemd/system/tmp.mount.

  How to Fix: run xhost +local: before gparted! # this only bypass the
  wayland restriction; meaning a security violation (not a fix !!! )

  thomas@ubuntu-1804:~$ xhost +local:
  non-network local connections being added to access control list
  thomas@ubuntu-1804:~$ gparted
  Unit -.mount does not exist, proceeding anyway.
  Created symlink /run/systemd/system/-.mount → /dev/null.
  Created symlink /run/systemd/system/boot-efi.mount → /dev/null.
  Created symlink /run/systemd/system/home.mount → /dev/null.
  Created symlink /run/systemd/system/run-snapd-ns-vlc.mnt.mount → /dev/null.
  Created symlink /run/systemd/system/run-snapd-ns.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-120.mount → /dev/null.
  Created symlink /run/systemd/system/snap-core-3748.mount → /dev/null.
  Created symlink /run/systemd/system/snap-vlc-113.mount → /dev/null.
  Created symlink /run/systemd/system/tmp.mount → /dev/null.
  Gtk-Message: Failed to load module "canberra-gtk-module"
  ==
  libparted : 3.2
  ==
  Removed /run/systemd/system/-.mount.
  Removed /run/systemd/system/boot-efi.mount.
  Removed /run/systemd/system/home.mount.
  Removed /run/systemd/system/run-snapd-ns-vlc.mnt.mount.
  Removed /run/systemd/system/run-snapd-ns.mount.
  Removed /run/systemd/system/run-user-1000.mount.
  Removed /run/systemd/system/run-user-120.mount.
  Removed /run/systemd/system/snap-core-3748.mount.
  Removed /run/systemd/system/snap-vlc-113.mount.
  Removed /run/systemd/system/tmp.mount.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gparted 0.30.0-3ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 19 19:45:14 2018
  InstallationDate: Installed on 2018-01-18 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180111)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gparted
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1744397] [NEW] "type" builtin - inconsistent behaviour for non-executable files

2018-01-19 Thread wjandrea

Public bug reported:

If you have a non-executable file in the PATH, the "type" builtin will
show it, just like an executable file. However, "type -a" does not. Is
this expected behaviour, or is it a bug?

For example:

$ touch non-exec
$ PATH=.
$ type non-exec
non-exec is ./non-exec
$ type -a non-exec
bash: type: non-exec: not found

The manpage describes this behaviour, but it doesn't explain why it
exists. Personally, I would have expected "type" and "type -a" to behave
the same.

I stumbled on this while writing a Bash function that expands on "type",
providing info like whether a function is marked for export, executable
file type, etc, and this behaviour makes it difficult to parse "type
-at".

This occurs on 17.10 with Bash 4.4.12, though I'm running 14.04 with
Bash 4.3.11.

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

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

Title:
  "type" builtin - inconsistent behaviour for non-executable files

Status in bash package in Ubuntu:
  New

Bug description:
  If you have a non-executable file in the PATH, the "type" builtin will
  show it, just like an executable file. However, "type -a" does not. Is
  this expected behaviour, or is it a bug?

  For example:

  $ touch non-exec
  $ PATH=.
  $ type non-exec
  non-exec is ./non-exec
  $ type -a non-exec
  bash: type: non-exec: not found

  The manpage describes this behaviour, but it doesn't explain why it
  exists. Personally, I would have expected "type" and "type -a" to
  behave the same.

  I stumbled on this while writing a Bash function that expands on
  "type", providing info like whether a function is marked for export,
  executable file type, etc, and this behaviour makes it difficult to
  parse "type -at".

  This occurs on 17.10 with Bash 4.4.12, though I'm running 14.04 with
  Bash 4.3.11.

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

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

[Touch-packages] [Bug 1744366] Re: xfce power manager shows wrong battery life information (Lbuntu 16.04.3)

2018-01-19 Thread Brian Murray

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

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

Title:
  xfce power manager shows wrong battery life information (Lbuntu
  16.04.3)

Status in upower package in Ubuntu:
  New

Bug description:
  As per title xfce power manager (version 1.4.4-4ubuntu2) on my Lubuntu
  16.04.3 shows a wrong battery life. What happens is that I plug in the
  laptop, it tells me the battery is 100% I unplug the write and I can
  see after maybe 10 minutes that the battery level lowered.

  I check and it gives me something like 80% and then, suddenly the
  laptop turns of because the battery is discharged.

  When i plug it back it shows as the battery is either charging
  correctly or charging and the percentage is over 70%.

  The battery is a few months old, so I think the problem lies in xfce
  power manager which displays the wrong information.Bug #1216594 opened
  in 2013 is very similar to my case, however that bug report was closed
  not because it was fixed but because it expired after 60 days.

  I tried 'upower -d' and it gives me the same info as the power manager.
  The output was:
  Device: /org/freedesktop/UPower/devices/line_power_ADP1
native-path:  ADP1
power supply: yes
updated:  XX XX XXX  17:58:48 GMT (815 seconds ago)
has history:  no
has statistics:   no
line-power
  warning-level:   none
  online:  yes
  icon-name:  'ac-adapter-symbolic'

  Device: /org/freedesktop/UPower/devices/battery_BAT0
native-path:  BAT0
vendor:   Hewlett-Packard
model:Primary
power supply: yes
updated:  Fri 19 Jan 2018 18:10:34 GMT (109 seconds ago)
has history:  yes
has statistics:   yes
battery
  present: yes
  rechargeable:yes
  state:   charging
  warning-level:   none
  energy:  22.2592 Wh
  energy-empty:0 Wh
  energy-full: 26.048 Wh
  energy-full-design:  26.048 Wh
  energy-rate: 20.0392 W
  voltage: 16.444 V
  time to full:11.3 minutes
  percentage:  85%
  capacity:100%
  technology:  lithium-ion
  icon-name:  'battery-full-charging-symbolic'
History (charge):
  151638543485.000  charging
History (rate):
  151638543420.039  charging

  Device: /org/freedesktop/UPower/devices/DisplayDevice
power supply: yes
updated:  XX XX XXX  18:10:34 GMT (109 seconds ago)
has history:  no
has statistics:   no
battery
  present: yes
  state:   charging
  warning-level:   none
  energy:  22.2592 Wh
  energy-full: 26.048 Wh
  energy-rate: 20.0392 W
  time to full:11.3 minutes
  percentage:  85%
  icon-name:  'battery-full-charging-symbolic'

  Daemon:
daemon-version:  0.99.4
on-battery:  no
lid-is-closed:   no
lid-is-present:  yes
critical-action: HybridSleep

  Any ideas?

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

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

[Touch-packages] [Bug 1744372] Re: gparted does not start - Unit -.mount does not exist, proceeding anyway.

2018-01-19 Thread Curtis Gedak

The upstream GParted team added a work-around to version 0.30.0 to
enable it to run seamlessly under Wayland.

See https://gparted.org/news.php?item=214

Unfortunately the packager for Ubuntu decided to not use the --enable-
xhost-root work-around.

See https://bugs.launchpad.net/ubuntu/+source/gparted/+bug/1737248

The consequence is that GParted only runs seamlessly on X, and not on
Wayland.

If you wish to use GParted from live media, then you might consider
using GParted Live.

See https://gparted.org/livecd.php

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

Title:
  gparted does not start - Unit -.mount does not exist, proceeding
  anyway.

Status in gparted package in Ubuntu:
  New
Status in wayland package in Ubuntu:
  Invalid

Bug description:
  1. fresh ubuntu 18.04 daily: lsb_release -rd
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  2. install gparted with Software:
  gparted:
    Installiert:   0.30.0-3ubuntu1
    Installationskandidat: 0.30.0-3ubuntu1
    Versionstabelle:
   *** 0.30.0-3ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  3. launch with icon - enter password - nothing.
  4.launch in terminal:
  Unit -.mount does not exist, proceeding anyway.
  Created symlink /run/systemd/system/-.mount → /dev/null.
  Created symlink /run/systemd/system/boot-efi.mount → /dev/null.
  Created symlink /run/systemd/system/home.mount → /dev/null.
  Created symlink /run/systemd/system/run-snapd-ns-vlc.mnt.mount → /dev/null.
  Created symlink /run/systemd/system/run-snapd-ns.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-120.mount → /dev/null.
  Created symlink /run/systemd/system/snap-core-3748.mount → /dev/null.
  Created symlink /run/systemd/system/snap-vlc-113.mount → /dev/null.
  Created symlink /run/systemd/system/tmp.mount → /dev/null.
  No protocol specified

  (gpartedbin:8328): Gtk-WARNING **: cannot open display: :0
  Removed /run/systemd/system/-.mount.
  Removed /run/systemd/system/boot-efi.mount.
  Removed /run/systemd/system/home.mount.
  Removed /run/systemd/system/run-snapd-ns-vlc.mnt.mount.
  Removed /run/systemd/system/run-snapd-ns.mount.
  Removed /run/systemd/system/run-user-1000.mount.
  Removed /run/systemd/system/run-user-120.mount.
  Removed /run/systemd/system/snap-core-3748.mount.
  Removed /run/systemd/system/snap-vlc-113.mount.
  Removed /run/systemd/system/tmp.mount.

  How to Fix: run xhost +local: before gparted! # this only bypass the
  wayland restriction; meaning a security violation (not a fix !!! )

  thomas@ubuntu-1804:~$ xhost +local:
  non-network local connections being added to access control list
  thomas@ubuntu-1804:~$ gparted
  Unit -.mount does not exist, proceeding anyway.
  Created symlink /run/systemd/system/-.mount → /dev/null.
  Created symlink /run/systemd/system/boot-efi.mount → /dev/null.
  Created symlink /run/systemd/system/home.mount → /dev/null.
  Created symlink /run/systemd/system/run-snapd-ns-vlc.mnt.mount → /dev/null.
  Created symlink /run/systemd/system/run-snapd-ns.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-120.mount → /dev/null.
  Created symlink /run/systemd/system/snap-core-3748.mount → /dev/null.
  Created symlink /run/systemd/system/snap-vlc-113.mount → /dev/null.
  Created symlink /run/systemd/system/tmp.mount → /dev/null.
  Gtk-Message: Failed to load module "canberra-gtk-module"
  ==
  libparted : 3.2
  ==
  Removed /run/systemd/system/-.mount.
  Removed /run/systemd/system/boot-efi.mount.
  Removed /run/systemd/system/home.mount.
  Removed /run/systemd/system/run-snapd-ns-vlc.mnt.mount.
  Removed /run/systemd/system/run-snapd-ns.mount.
  Removed /run/systemd/system/run-user-1000.mount.
  Removed /run/systemd/system/run-user-120.mount.
  Removed /run/systemd/system/snap-core-3748.mount.
  Removed /run/systemd/system/snap-vlc-113.mount.
  Removed /run/systemd/system/tmp.mount.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gparted 0.30.0-3ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 19 19:45:14 2018
  InstallationDate: Installed on 2018-01-18 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180111)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gparted
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

[Touch-packages] [Bug 1744366] [NEW] xfce power manager shows wrong battery life information (Lbuntu 16.04.3)

2018-01-19 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

As per title xfce power manager (version 1.4.4-4ubuntu2) on my Lubuntu
16.04.3 shows a wrong battery life. What happens is that I plug in the
laptop, it tells me the battery is 100% I unplug the write and I can see
after maybe 10 minutes that the battery level lowered.

I check and it gives me something like 80% and then, suddenly the laptop
turns of because the battery is discharged.

When i plug it back it shows as the battery is either charging correctly
or charging and the percentage is over 70%.

The battery is a few months old, so I think the problem lies in xfce
power manager which displays the wrong information.Bug #1216594 opened
in 2013 is very similar to my case, however that bug report was closed
not because it was fixed but because it expired after 60 days.

I tried 'upower -d' and it gives me the same info as the power manager.
The output was:
Device: /org/freedesktop/UPower/devices/line_power_ADP1
  native-path:  ADP1
  power supply: yes
  updated:  XX XX XXX  17:58:48 GMT (815 seconds ago)
  has history:  no
  has statistics:   no
  line-power
warning-level:   none
online:  yes
icon-name:  'ac-adapter-symbolic'

Device: /org/freedesktop/UPower/devices/battery_BAT0
  native-path:  BAT0
  vendor:   Hewlett-Packard
  model:Primary
  power supply: yes
  updated:  Fri 19 Jan 2018 18:10:34 GMT (109 seconds ago)
  has history:  yes
  has statistics:   yes
  battery
present: yes
rechargeable:yes
state:   charging
warning-level:   none
energy:  22.2592 Wh
energy-empty:0 Wh
energy-full: 26.048 Wh
energy-full-design:  26.048 Wh
energy-rate: 20.0392 W
voltage: 16.444 V
time to full:11.3 minutes
percentage:  85%
capacity:100%
technology:  lithium-ion
icon-name:  'battery-full-charging-symbolic'
  History (charge):
1516385434  85.000  charging
  History (rate):
1516385434  20.039  charging

Device: /org/freedesktop/UPower/devices/DisplayDevice
  power supply: yes
  updated:  XX XX XXX  18:10:34 GMT (109 seconds ago)
  has history:  no
  has statistics:   no
  battery
present: yes
state:   charging
warning-level:   none
energy:  22.2592 Wh
energy-full: 26.048 Wh
energy-rate: 20.0392 W
time to full:11.3 minutes
percentage:  85%
icon-name:  'battery-full-charging-symbolic'

Daemon:
  daemon-version:  0.99.4
  on-battery:  no
  lid-is-closed:   no
  lid-is-present:  yes
  critical-action: HybridSleep

Any ideas?

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


** Tags: battery bot-comment lubuntu manager power xfce
-- 
xfce power manager shows wrong battery life information (Lbuntu 16.04.3)
https://bugs.launchpad.net/bugs/1744366
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to upower in Ubuntu.

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

[Touch-packages] [Bug 1543799] Re: isc-dhcp-server & isc-dhcp-server6 systemd service units use the same RuntimeDirectory leading to loss of pid files

2018-01-19 Thread Ubuntu Foundations Team Bug Bot

The attachment "corrected patch to use separate RuntimeDirectory" seems
to be a patch.  If it isn't, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are a member of the
~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  isc-dhcp-server & isc-dhcp-server6 systemd service units use the same
  RuntimeDirectory leading to loss of pid files

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  dhcpd reports 'Can't create PID file /run/dhcp-server/dhcpd.pid' (or
  '/run/dhcp-server/dhcpd6.pid' for isc-dhcp-server6), and no file is
  found /run/dhcp-server.

  Additionally, both isc-dhcp-server & isc-dhcp-server6 service unit
  files specify the RuntimeDirectory 'dhcp-server', which is removed
  when either unit stops (and thus would wipe out the other unit's pid
  file, were it being successfully written).

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: isc-dhcp-server 4.3.3-5ubuntu4
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  Date: Tue Feb  9 21:34:08 2016
  InstallationDate: Installed on 2016-02-09 (0 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160206)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=linux
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: isc-dhcp
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.dhcp.dhcpd.conf: [modified]
  mtime.conffile..etc.dhcp.dhcpd.conf: 2016-02-09T21:11:20.104056

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1543799/+subscriptions

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

[Touch-packages] [Bug 1744372] Re: gparted does not start - Unit -.mount does not exist, proceeding anyway.

2018-01-19 Thread dino99

** Description changed:

  1. fresh ubuntu 18.04 daily: lsb_release -rd
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04
  
  2. install gparted with Software:
  gparted:
-   Installiert:   0.30.0-3ubuntu1
-   Installationskandidat: 0.30.0-3ubuntu1
-   Versionstabelle:
-  *** 0.30.0-3ubuntu1 500
- 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
- 100 /var/lib/dpkg/status
+   Installiert:   0.30.0-3ubuntu1
+   Installationskandidat: 0.30.0-3ubuntu1
+   Versionstabelle:
+  *** 0.30.0-3ubuntu1 500
+ 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
+ 100 /var/lib/dpkg/status
  
  3. launch with icon - enter password - nothing.
  4.launch in terminal:
  Unit -.mount does not exist, proceeding anyway.
  Created symlink /run/systemd/system/-.mount → /dev/null.
  Created symlink /run/systemd/system/boot-efi.mount → /dev/null.
  Created symlink /run/systemd/system/home.mount → /dev/null.
  Created symlink /run/systemd/system/run-snapd-ns-vlc.mnt.mount → /dev/null.
  Created symlink /run/systemd/system/run-snapd-ns.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-120.mount → /dev/null.
  Created symlink /run/systemd/system/snap-core-3748.mount → /dev/null.
  Created symlink /run/systemd/system/snap-vlc-113.mount → /dev/null.
  Created symlink /run/systemd/system/tmp.mount → /dev/null.
  No protocol specified
  
  (gpartedbin:8328): Gtk-WARNING **: cannot open display: :0
  Removed /run/systemd/system/-.mount.
  Removed /run/systemd/system/boot-efi.mount.
  Removed /run/systemd/system/home.mount.
  Removed /run/systemd/system/run-snapd-ns-vlc.mnt.mount.
  Removed /run/systemd/system/run-snapd-ns.mount.
  Removed /run/systemd/system/run-user-1000.mount.
  Removed /run/systemd/system/run-user-120.mount.
  Removed /run/systemd/system/snap-core-3748.mount.
  Removed /run/systemd/system/snap-vlc-113.mount.
  Removed /run/systemd/system/tmp.mount.
  
- 
- How to Fix: run xhost +local: before gparted!
+ How to Fix: run xhost +local: before gparted! # this only bypass the
+ wayland restriction; meaning a security violation (not a fix !!! )
  
  thomas@ubuntu-1804:~$ xhost +local:
  non-network local connections being added to access control list
  thomas@ubuntu-1804:~$ gparted
  Unit -.mount does not exist, proceeding anyway.
  Created symlink /run/systemd/system/-.mount → /dev/null.
  Created symlink /run/systemd/system/boot-efi.mount → /dev/null.
  Created symlink /run/systemd/system/home.mount → /dev/null.
  Created symlink /run/systemd/system/run-snapd-ns-vlc.mnt.mount → /dev/null.
  Created symlink /run/systemd/system/run-snapd-ns.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-120.mount → /dev/null.
  Created symlink /run/systemd/system/snap-core-3748.mount → /dev/null.
  Created symlink /run/systemd/system/snap-vlc-113.mount → /dev/null.
  Created symlink /run/systemd/system/tmp.mount → /dev/null.
  Gtk-Message: Failed to load module "canberra-gtk-module"
  ==
  libparted : 3.2
  ==
  Removed /run/systemd/system/-.mount.
  Removed /run/systemd/system/boot-efi.mount.
  Removed /run/systemd/system/home.mount.
  Removed /run/systemd/system/run-snapd-ns-vlc.mnt.mount.
  Removed /run/systemd/system/run-snapd-ns.mount.
  Removed /run/systemd/system/run-user-1000.mount.
  Removed /run/systemd/system/run-user-120.mount.
  Removed /run/systemd/system/snap-core-3748.mount.
  Removed /run/systemd/system/snap-vlc-113.mount.
  Removed /run/systemd/system/tmp.mount.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gparted 0.30.0-3ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 19 19:45:14 2018
  InstallationDate: Installed on 2018-01-18 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180111)
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=de_DE.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=de_DE.UTF-8
+  SHELL=/bin/bash
  SourcePackage: gparted
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

Title:
  gparted does not start - Unit -.mount does not exist, proceeding
  anyway.

Status in gparted package in Ubuntu:
  New
Status in wayland package in Ubuntu:
  Invalid

Bug description:
  1. fresh ubuntu 18.04 daily: lsb_release -rd
  Description:

85 matches

Mail list logo