[Touch-packages] [Bug 2039592] [NEW] no connection via SIM card

[Denis]

Public bug reported:

Ubuntu 22.04 I can’t connect to the Internet via a SIM card.
I can see how the Measurement Manager is being developed and the plugin is 
installed..
  I'll add a module: NMWwanFactory 
(/usr/lib/x86_64-linux-gnu/NetworkManager/1.36.6/libnm-device-plugin-wwan.so)
manager: rfkill: WWAN is jammed with radio; I'll become a file.
the driver does not load!!!

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: network-manager 1.36.6-0ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-34-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 17 19:40:10 2023
InstallationDate: Installed on 2023-10-03 (13 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
IpRoute:
 default via 192.168.43.63 dev wlo1 proto dhcp metric 600 
 169.254.0.0/16 dev wlo1 scope link metric 1000 
 192.168.43.0/24 dev wlo1 proto kernel scope link src 192.168.43.83 metric 600
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
 DEVICE   TYPE  STATEIP4-CONNECTIVITY  IP6-CONNECTIVITY  DBUS-PATH  
CONNECTION   CON-UUID   
   CON-PATH   
 wlo1 wifi  connectedfull  limited   
/org/freedesktop/NetworkManager/Devices/3  ONEPLUS_A5000_co_aptsvo  
174d782e-8952-4921-b779-adbd0266fe27  
/org/freedesktop/NetworkManager/ActiveConnection/1 
 enp0s25  ethernet  unavailable  none  none  
/org/freedesktop/NetworkManager/Devices/2  --   --  
  -- 
 lo   loopback  unmanagedunknown   unknown   
/org/freedesktop/NetworkManager/Devices/1  --   --  
  --
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN 
 running  1.36.6   connected  started  full  enabled enabled  
enabled  enabled  disabled

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy wayland-session

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

Title:
  no connection via SIM card

Status in network-manager package in Ubuntu:
  New

Bug description:
  Ubuntu 22.04 I can’t connect to the Internet via a SIM card.
  I can see how the Measurement Manager is being developed and the plugin is 
installed..
I'll add a module: NMWwanFactory 
(/usr/lib/x86_64-linux-gnu/NetworkManager/1.36.6/libnm-device-plugin-wwan.so)
  manager: rfkill: WWAN is jammed with radio; I'll become a file.
  the driver does not load!!!

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: network-manager 1.36.6-0ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-34-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 17 19:40:10 2023
  InstallationDate: Installed on 2023-10-03 (13 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  IpRoute:
   default via 192.168.43.63 dev wlo1 proto dhcp metric 600 
   169.254.0.0/16 dev wlo1 scope link metric 1000 
   192.168.43.0/24 dev wlo1 proto kernel scope link src 192.168.43.83 metric 600
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATEIP4-CONNECTIVITY  IP6-CONNECTIVITY  
DBUS-PATH  CONNECTION   CON-UUID
  CON-PATH   
   wlo1 wifi  connectedfull  limited   
/org/freedesktop/NetworkManager/Devices/3  ONEPLUS_A5000_co_aptsvo  
174d782e-8952-4921-b779-adbd0266fe27  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp0s25  ethernet  unavailable  none  none  
/org/freedesktop/NetworkManager/Devices/2  --   --  
  -- 
   lo   loopback  unmanagedunknown   unknown   
/org/freedesktop/NetworkManager/Devices/1  --   --  
  --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN 
   running  1.36.6   connected  started  full  enabled enabled  
enabled  

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

[Denis Oleksiuk]

This bug still in ubuntu 20.04 :

-- 
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 console-setup package in Ubuntu:
  Confirmed
Status in gconf package in Ubuntu:
  Confirmed

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/ubuntu/+source/console-setup/+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 1918016] [NEW] [Latitude 9510, Intel Kabylake HDMI, Digital Out, HDMI] Pulseaudio fails to detect card. I

[Denis Balažić]

Public bug reported:

I don't have any sound on my laptop after installing Ubuntu. It worked well 
with Windows.
In audio settings there is no audio output detected (dummy output). No input 
also.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1-1ubuntu3.10
ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-44-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D3p', 
'/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Mar  6 19:20:52 2021
InstallationDate: Installed on 2021-03-06 (0 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
SourcePackage: pulseaudio
Symptom: audio
Symptom_Card: sof-hda-dsp - sof-hda-dsp
Symptom_Jack: Digital Out, HDMI
Title: [Latitude 9510, Intel Kabylake HDMI, Digital Out, HDMI] Pulseaudio fails 
to detect card
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/16/2020
dmi.bios.release: 1.2
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.2.2
dmi.board.name: 0G0T42
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.2:bd07/16/2020:br1.2:svnDellInc.:pnLatitude9510:pvr:rvnDellInc.:rn0G0T42:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Latitude
dmi.product.name: Latitude 9510
dmi.product.sku: 0983
dmi.sys.vendor: Dell Inc.

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

Title:
  [Latitude 9510, Intel Kabylake HDMI, Digital Out, HDMI] Pulseaudio
  fails to detect card. I

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I don't have any sound on my laptop after installing Ubuntu. It worked well 
with Windows.
  In audio settings there is no audio output detected (dummy output). No input 
also.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.10
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D3p', 
'/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar  6 19:20:52 2021
  InstallationDate: Installed on 2021-03-06 (0 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: sof-hda-dsp - sof-hda-dsp
  Symptom_Jack: Digital Out, HDMI
  Title: [Latitude 9510, Intel Kabylake HDMI, Digital Out, HDMI] Pulseaudio 
fails to detect card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/16/2020
  dmi.bios.release: 1.2
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.2
  dmi.board.name: 0G0T42
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.2:bd07/16/2020:br1.2:svnDellInc.:pnLatitude9510:pvr:rvnDellInc.:rn0G0T42:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 9510
  dmi.product.sku: 0983
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://launchpad.net/~touch-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

[denis]

Problem has NOT been fixed for my setup:

- Kernel: 5.4.0-58.64-generic
- OS: Ubuntu 20.04.1 LTS
- Machine: Dell Inspiron 7559 (0706)
- Headset: Anker Soundcore Liberty Air 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 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa

[denis]

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

Problem has NOT been fixed for my setup:

- Kernel: 5.4.0-58.64-generic
- OS: Ubuntu 20.04.1 LTS
- Machine: Dell Inspiron 7559 (0706)
- Headset: Anker Soundcore Liberty Air 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 1890170] Re: ImportError libstdc++.so.6 cannot allocate memory after importing PyQt5.Qt PyQt5.QtCore and cv2

[Rouzaud Denis]

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

from this answer https://stackoverflow.com/a/62520135/1548052, this "solved" 
the issue for me:
LD_PRELOAD=/lib/x86_64-linux-gnu/libstdc++.so.6 python3 …

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

Title:
  ImportError libstdc++.so.6 cannot allocate memory after importing
  PyQt5.Qt PyQt5.QtCore and cv2

Status in mysql-8.0 package in Ubuntu:
  Confirmed
Status in opencv package in Ubuntu:
  Confirmed
Status in pyqt5 package in Ubuntu:
  Confirmed

Bug description:
  I'm using an updated Lubuntu focal. Starting maybe last week (monday July 
27th), if in python3 I do
  from PyQt5 import Qt, QtCore
  import cv2

  I get
  ImportError: /lib/x86_64-linux-gnu/libstdc++.so.6: cannot allocate memory in 
static TLS block

  I noticed only now that the reverse (first import cv2, then Qt,
  QtCore) seems to work correctly and displays no errors. I'm afraid I
  might not be able to do the reverse in my real software...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: python3 3.8.2-0ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: LXQt
  Date: Mon Aug  3 17:49:20 2020
  InstallationDate: Installed on 2020-07-15 (19 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: python3-defaults
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

[Denis]

Can confirm 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835660/comments/26
What I did was I changed 

`COMPRESS=lz4` to `COMPRESS=gzip` in `/etc/initramfs-tools/initramfs.conf`, then
`sudo update-initramfs -u`

After, without a reboot I've changed `COMPRESS` back to `lz4`, and then
`sudo update-initramfs -u`

And after the reboot that error is gone.

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

Title:
  initramfs unpacking failed

Status in initramfs-tools package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  "initramfs unpacking failed: Decoding failed",  message appears on
  boot up.

  If I "update-initramfs" using gzip instead of lz, then boot up passes
  without decoding failed message.

  ---

  However, we currently believe that the decoding error reported in
  dmesg is actually harmless and has no impact on usability on the
  system.

  Switching from lz4 to gzip compression, simply papers over the
  warning, without any benefits, and slows down boot.

  Kernel should be fixed to correctly parse lz4 compressed initrds, or
  at least lower the warning, to not be user visible as an error.

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

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

[Touch-packages] [Bug 1843352] [NEW] systemd package version 237-3ubuntu10.28 breaks local network DNS resolution

[Denis Rut'kov]

Public bug reported:

After upgrading to the latest package the systemd-resolved service fails
to resolve names for local network.Manually invoking nslookup works
fine.

The only suspicious output from journalctl seems:
systemd-resolved[858]: Server returned error NXDOMAIN, mitigating potential DNS 
violation DVE-2018-0001, retrying transaction with reduced feature level UDP.

The latest change in that package is:
 * SECURITY UPDATE: Unprivileged users are granted access to privileged
systemd-resolved D-Bus methods
- d/p/0001-shared-but-util-drop-trusted-annotation-from-bus_ope.patch:
  drop trusted annotation from bus_open_system_watch_bind()
- CVE-2019-15718

 -- Chris Coulson   Thu, 29 Aug 2019
23:30:33 +0100

Please revert this.

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

** Attachment added: "This is output of dig command for a locally available 
resource (the name has been replaced)"
   https://bugs.launchpad.net/bugs/1843352/+attachment/5287638/+files/dig.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/1843352

Title:
  systemd package version 237-3ubuntu10.28 breaks local network DNS
  resolution

Status in systemd package in Ubuntu:
  New

Bug description:
  After upgrading to the latest package the systemd-resolved service
  fails to resolve names for local network.Manually invoking nslookup
  works fine.

  The only suspicious output from journalctl seems:
  systemd-resolved[858]: Server returned error NXDOMAIN, mitigating potential 
DNS violation DVE-2018-0001, retrying transaction with reduced feature level 
UDP.

  The latest change in that package is:
   * SECURITY UPDATE: Unprivileged users are granted access to privileged
  systemd-resolved D-Bus methods
  - d/p/0001-shared-but-util-drop-trusted-annotation-from-bus_ope.patch:
drop trusted annotation from bus_open_system_watch_bind()
  - CVE-2019-15718

   -- Chris Coulson   Thu, 29 Aug 2019
  23:30:33 +0100

  Please revert this.

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

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

[Touch-packages] [Bug 1826687] [NEW] package keyboard-configuration 1.178ubuntu2.8 failed to install/upgrade: installed keyboard-configuration package post-installation script subprocess returned erro

[Denis Gaulin]

Public bug reported:

The key combination is not a good alternative for people who have a
different langauge other than US english...

We never had this combination of key... Ithttps://bugs.launchpad.net/bugs/1826687

Title:
  package keyboard-configuration 1.178ubuntu2.8 failed to
  install/upgrade: installed keyboard-configuration package post-
  installation script subprocess returned error exit status 10

Status in console-setup package in Ubuntu:
  New

Bug description:
  The key combination is not a good alternative for people who have a
  different langauge other than US english...

  We never had this combination of key... Ithttps://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1826687/+subscriptions

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

[Touch-packages] [Bug 1808323] [NEW] gfg

[Denis Serenko]

Public bug reported:

gfg

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
Uname: Linux 4.15.0-42-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Thu Dec 13 14:09:43 2018
DistUpgraded: 2018-12-12 20:39:45,935 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 7340] [1002:9808] 
(prog-if 00 [VGA controller])
   Subsystem: Sony Corporation Wrestler [Radeon HD 7340] [104d:90ad]
InstallationDate: Installed on 2016-04-24 (963 days ago)
InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1)
MachineType: Sony Corporation SVE1112M1EW
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=40da7131-b99a-4e5b-9c5e-81ba4975e74c ro quiet splash
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2018-12-12 (0 days ago)
dmi.bios.date: 08/22/2012
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: R0120D8
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0120D8:bd08/22/2012:svnSonyCorporation:pnSVE1112M1EW:pvrC60B8BEP:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.family: VAIO
dmi.product.name: SVE1112M1EW
dmi.product.version: C60B8BEP
dmi.sys.vendor: Sony Corporation
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Wed Dec 12 18:07:04 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-0ubuntu0.8
xserver.video_driver: radeon

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


** Tags: amd64 apport-bug bionic 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/1808323

Title:
  gfg

Status in xorg package in Ubuntu:
  New

Bug description:
  gfg

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu Dec 13 14:09:43 2018
  DistUpgraded: 2018-12-12 20:39:45,935 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory) (8))
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 7340] [1002:9808] 
(prog-if 00 [VGA controller])
 Subsystem: Sony Corporation Wrestler [Radeon HD 7340] [104d:90ad]
  InstallationDate: Installed on 2016-04-24 (963 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  MachineType: Sony Corporation SVE1112M1EW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=40da7131-b99a-4e5b-9c5e-81ba4975e74c ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-12-12 (0 days ago)
  dmi.bios.date: 08/22/2012
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0120D8
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0120D8:bd08/22/2012:svnSonyCorporation:pnSVE1112M1EW:pvrC60B8BEP:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: VAIO
  dmi.product.name: SVE1112M1EW
  

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

[Denis Floch]

Fix verified in version 0.99.8-2ubuntu0.1 on a MacBook Air 11" running
Kubuntu cosmic

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

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

Status in linux package in Ubuntu:
  Invalid
Status in upower package in Ubuntu:
  Fix Committed
Status in upower source package in Cosmic:
  Fix Committed

Bug description:
  * Impact
  keyboard backlight control keys don't work in cosmic

  *  Test case
  On a laptop with keyboard backlight and keys to control the level, try using 
the keys, they should change the level

  * Regression potential
  The change is to lift some systemd process restriction, have extra access 
shouldn't create issue but check that other features like suspend, battery  
pourcentage report, etc keep working

  ---

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

  ---

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

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

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

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

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

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

[Touch-packages] [Bug 1728181] Re: systemd-networkd-wait-online waits when devices are unmanaged

[Denis Genov]

I face the same issue

> # dpkg -l systemd 
> ...
> ||/ Name   VersionArchitectureDescription
> +++-==-==-===-==
> ii  systemd237-3ubuntu10.3amd64   system and service manager

> # networkctl
> IDX LINK TYPE   OPERATIONAL SETUP 
>   1 lo   loopback   carrier unmanaged 
>   2 ens3 ether  routableconfiguring
>   3 ens4 ether  routableunmanaged

> Aug 03 14:00:53 test-vm systemd-networkd-wait-online[4273]: Event loop
failed: Connection timed out

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

Title:
  systemd-networkd-wait-online waits when devices are unmanaged

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  I started a system with cloud-init disabled, etc. and a single real
  network interface (ens3) that could be configured.

  That VM has no configuration whatsoever for systemd-networkd, as that
  would have to have been written by netplan, and cloud-init did not
  generate netplan config (because it was disabled).

  So:

  root@ubuntu:/etc/systemd/system/network-online.target.wants# ip route
  d-networkd-wait-online --ignore=lo
  ignoring: lo
  Event loop failed: Connection timed out
  root@ubuntu:/etc/systemd/system/network-online.target.wants# ip route
  root@ubuntu:/etc/systemd/system/network-online.target.wants# networkctl
  IDX LINK TYPE   OPERATIONAL SETUP 
1 lo   loopback   carrier unmanaged 
2 ens3 ether  off unmanaged 
3 sit0 sitoff unmanaged 

  3 links listed.
  root@ubuntu:/etc/systemd/system/network-online.target.wants# 

  
  The system took 120 seconds to complete boot, because wait-online had to 
finish; and running wait-online from the system afterwards also waits 120 
seconds (its default timeout). If there is no configuration for an interface, 
it's unmanaged (as shown by networkctl), so wait-online should not wait, and 
simply report that all interfaces are unmanaged, possibly returning an error so 
we don't reach network-online.

  FWIW, having wait-online look up configuration might later be useful
  also to figure out if an interface was configured, but marked as
  optional (such that it is explicitly not required to be up at boot),
  or if we want to configure network devices but specify that networkd
  should *not* bring them online (like "administratively disabled"
  interfaces in Cisco world using the "shutdown" command).

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

-- 
Mailing list: https://launchpad.net/~touch-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

[Lysenko Denis]

You may try this ppa https://launchpad.net/~graphics-
drivers/+archive/ubuntu/ppa just updated driver from this rep on 18.04
and succesfully booted.

-- 
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 460925] Re: Kernel log message corruption due to incomplete /proc separation

[denis steve]

** Changed in: lxc (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: linux (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  Kernel log message corruption due to incomplete /proc separation

Status in linux package in Ubuntu:
  Fix Committed
Status in lxc package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: lxc

  When using LXC (linux containers), /proc/kmsg can be read in guest
  systems in their filtered view of /proc.  This special file should
  never be present in guest systems, and if created within a guest
  system, it should be effectively using /dev/null as it's source.  The
  effect of this bug ranges from simply annoying to potentially a
  security issue in that kernel messages are allowed to be destroyed and
  never fully logged on the host system, which could be used to cover
  evidence of some sort of attack on the system.

  I'm adding the kernel team as well, as this could be an issue inside
  the kernel.  I'm not sure if /proc filtration happens there or in the
  context of the lxc userland utilities.

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

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

[Touch-packages] [Bug 1458322] Re: NetworkManager doesn't hide virtual interfaces (e.g. Docker, VMWare)

[Denis Franco]

@bjbrewster I'm following the patch applying tutorial from here
https://superuser.com/questions/154717/how-to-apply-patch-to-gnome-on-
ubuntu/175743

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

Title:
  NetworkManager doesn't hide virtual interfaces (e.g. Docker, VMWare)

Status in One Hundred Papercuts:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Previously in Ubuntu 14.04 NetworkManager hid the veth interfaces that were 
created by Docker.
  Now since I've updated to 15.04 the veth interfaces are listed as Unmanaged 
under the gnome system tray icon which is kind of annoying.
  I'm using docker 1.6.2 and network-manager 0.9.10.0-4ubuntu15.1

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu15.1
  ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6
  Uname: Linux 3.19.0-18-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun May 24 14:22:44 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-08-29 (632 days ago)
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130214)
  IpRoute:
   default via 192.168.178.1 dev wlan0  proto static  metric 1024 
   169.254.0.0/16 dev wlan0  scope link  metric 1000 
   172.17.0.0/16 dev docker0  proto kernel  scope link  src 172.17.42.1 
   192.168.178.0/24 dev wlan0  proto kernel  scope link  src 192.168.178.40
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to vivid on 2015-05-24 (0 days ago)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2014-08-19T11:46:06.705439
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

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

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

[Touch-packages] [Bug 1736371] Re: Feature Request: Syncthing integration

[Denis Donici]

Second you here. In most cases, a user has his mobile phone on him.
There are also cases when one user has more than one computer and it's
quite a hustle to keep all these devices in sync. One of the Apple's
advantages is everything is in sync. I can see Ubuntu team bringing
Syncthing as a default server/client for syncing its files across
multiple devices. Even user-specific config files could be stored for
back-up on the mobile phone. And next time, on a fresh install, config
files are retrieved from the phone, everything is back the way it was.
Really neat and convenient. Syncthing has an android client. I think it
is an opportunity Ubuntu should take advantage of.

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

Title:
  Feature Request: Syncthing integration

Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  since the removal of Ubuntu One filehosting, a nice, well-integrated
  filesync in Ubuntu desktop is missing. It would be a welcome addition
  to have filesync back as an out-of-the box feature.

  Syncthing is a proven open-source p2p filesync software. The software
  has a track record of many years under active development, the
  developer community is alive and well. It seems to be stable and the
  architecture seems sound. (I cannot comment on its security
  implications, though.)

  Syncthing is server-less, it doesn't require a central/cloud server.
  The usability leaves a lot to be desired and the current installation
  and end-user experience is poor for a novice user.

  The most successful part of Ubuntu desktop's mission has always been
  making complicated Linux software easier to use for novice end-users.

  Therefore my request is that Ubuntu considers spending development
  resources on improving the user experience of Syncthing.

  - Make Syncthing a part of a default Ubuntu desktop installation.
  - Design a better end-user interface for remote sync device management.
  - Design a better end-user interface for seamless filemanager integration.
  - Add a possible, optional encrypted cloud storage sync service.

  Thanks.

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

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

[Touch-packages] [Bug 1269177] Re: Running 'unattended-upgrades --dry-run' reboots the machine

[Denis NIkolaenko]

A new version from xenial-proposed fixes the issue for me.
--
root@ubuntu:~# dpkg -l unattended-upgrades 
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version   
Architecture  Description
+++--=-=-==
ii  unattended-upgrades  0.90ubuntu0.9 all  
 automatic installation of security upgrades

root@ubuntu:~# touch /var/run/reboot-required  
root@ubuntu:~# unattended-upgrades --dry-run 
root@ubuntu:~# 

(reboot does not happen)

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

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

Title:
  Running 'unattended-upgrades --dry-run' reboots the machine

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Committed
Status in unattended-upgrades source package in Zesty:
  Fix Committed
Status in unattended-upgrades source package in Artful:
  Fix Committed
Status in unattended-upgrades source package in Bionic:
  Fix Released

Bug description:
  Impact
  --
  An Ubuntu system will unexpectedly reboot if reboot-required exists and you 
run unattended-upgrades in dry-run mode.

  Test Case
  -
  1) modify /etc/apt/apt.conf.d/50unattended-upgrades so that Automatic-Reboot 
is true
  2) Ensure all updates are installed
  3) sudo touch /var/run/reboot-required
  4) run 'sudo unattended-upgrades --dry-run'
  5) watch the system reboot

  With the version of unattended-upgrades from -proposed the system will
  not reboot.

  Regression Potential
  
  This checks to see if the --dry-run switch is passed to unattended-upgrades 
before calling the reboot function. I guess it would be a regression to people 
who expect the system to reboot but that seems like a very strange corner case.

  Original Description
  
  Much to my surprise, when I did a dry-run test of unattended-upgrades my 
server was forcibly rebooted. I must have had the file 
'/var/run/reboot-required' present.

  But needless to say: a --dry-run should NOT perform a reboot of the
  server with zero warning. Seriously.

  Output from /var/log/unattended-upgrades.log

  2014-01-15 11:14:26,474 INFO Initial blacklisted packages:
  2014-01-15 11:14:26,474 INFO Starting unattended upgrades script
  2014-01-15 11:14:26,475 INFO Allowed origins are: 
['o=Ubuntu,a=precise-security']
  2014-01-15 11:14:35,846 INFO Option --dry-run given, *not* performing real 
actions
  2014-01-15 11:14:35,846 INFO Packages that are upgraded: bind9-host dnsutils 
libbind9-80 libdns81 libisc83 libisccc80 libisccfg82 liblwres80 libssl1.0.0 
linux-generic-pae linux-headers-generic-pae linux-image-generic-pae 
linux-libc-dev openssl
  2014-01-15 11:14:35,847 INFO Writing dpkg log to 
'/var/log/unattended-upgrades/unattended-upgrades-dpkg_2014-01-15_11:14:35.846820.log'
  2014-01-15 11:15:10,610 INFO All upgrades installed
  2014-01-15 11:15:10,611 WARNING Found /var/run/reboot-required, rebooting

  Version: 0.76ubuntu1

  As an aside, it makes a lot of sense to me to put the reboot on a
  timer, even if it's only a one minute (i.e. shutdown -r 1). That would
  have at least given me a chance to prevent the reboot if I had seen
  the warning. If that's a configuration setting I don't see it
  anywhere.

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

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

[Touch-packages] [Bug 1269177] Re: Running 'unattended-upgrades --dry-run' reboots the machine

[Denis Nikolaenko]

I was able to reproduce it in a freshly installed VM (VMware).

--
root@ubuntu:~# egrep -v '(^\s*//.*$|^\s*$)' 
/etc/apt/apt.conf.d/50unattended-upgrades 
Unattended-Upgrade::Allowed-Origins {
"${distro_id}:${distro_codename}";
"${distro_id}:${distro_codename}-security";
"${distro_id}ESM:${distro_codename}";
};
Unattended-Upgrade::Package-Blacklist {
};
Unattended-Upgrade::Automatic-Reboot "true";

root@ubuntu:~# uname -a
Linux ubuntu 4.4.0-104-generic #127-Ubuntu SMP Mon Dec 11 12:16:42 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

root@ubuntu:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.3 LTS
Release:16.04
Codename:   xenial

root@ubuntu:~# apt-get update && apt-get dist-upgrade -y
Get:1 http://security.ubuntu.com/ubuntu xenial-security InRelease [102 kB]
Hit:2 http://us.archive.ubuntu.com/ubuntu xenial InRelease
Get:3 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease [102 kB] 
   
Get:4 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease [102 kB]   
 
Fetched 306 kB in 2s (146 kB/s)  
Reading package lists... Done
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

root@ubuntu:~# file /var/run/reboot-required
/var/run/reboot-required: cannot open `/var/run/reboot-required' (No such file 
or directory)

root@ubuntu:~# touch /var/run/reboot-required

root@ubuntu:~# unattended-upgrades --dry-run

(ssh disconnects, system reboots)

root@ubuntu:~# cat /var/log/unattended-upgrades/unattended-upgrades.log 
2017-12-16 09:59:17,772 INFO Initial blacklisted packages: 
2017-12-16 09:59:17,773 INFO Initial whitelisted packages: 
2017-12-16 09:59:17,773 INFO Starting unattended upgrades script
2017-12-16 09:59:17,773 INFO Allowed origins are: ['o=Ubuntu,a=xenial', 
'o=Ubuntu,a=xenial-security', 'o=UbuntuESM,a=xenial']
2017-12-16 09:59:21,610 INFO No packages found that can be upgraded unattended 
and no pending auto-removals
2017-12-16 09:59:21,611 WARNING Found /var/run/reboot-required, rebooting

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

Title:
  Running 'unattended-upgrades --dry-run' reboots the machine

Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  Much to my surprise, when I did a dry-run test of unattended-upgrades
  my server was forcibly rebooted. I must have had the file '/var/run
  /reboot-required' present.

  But needless to say: a --dry-run should NOT perform a reboot of the
  server with zero warning. Seriously.

  Output from /var/log/unattended-upgrades.log

  2014-01-15 11:14:26,474 INFO Initial blacklisted packages: 
  2014-01-15 11:14:26,474 INFO Starting unattended upgrades script
  2014-01-15 11:14:26,475 INFO Allowed origins are: 
['o=Ubuntu,a=precise-security']
  2014-01-15 11:14:35,846 INFO Option --dry-run given, *not* performing real 
actions
  2014-01-15 11:14:35,846 INFO Packages that are upgraded: bind9-host dnsutils 
libbind9-80 libdns81 libisc83 libisccc80 libisccfg82 liblwres80 libssl1.0.0 
linux-generic-pae linux-headers-generic-pae linux-image-generic-pae 
linux-libc-dev openssl
  2014-01-15 11:14:35,847 INFO Writing dpkg log to 
'/var/log/unattended-upgrades/unattended-upgrades-dpkg_2014-01-15_11:14:35.846820.log'
  2014-01-15 11:15:10,610 INFO All upgrades installed
  2014-01-15 11:15:10,611 WARNING Found /var/run/reboot-required, rebooting

  Version: 0.76ubuntu1

  As an aside, it makes a lot of sense to me to put the reboot on a
  timer, even if it's only a one minute (i.e. shutdown -r 1). That would
  have at least given me a chance to prevent the reboot if I had seen
  the warning. If that's a configuration setting I don't see it
  anywhere.

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

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

[Touch-packages] [Bug 1269177] Re: Running 'unattended-upgrades --dry-run' reboots the machine

[Denis Nikolaenko]

The bug is still reproducible in xenial.

--
# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.3 LTS
Release:16.04
Codename:   xenial

# grep Automatic-Reboot /etc/apt/apt.conf.d/50unattended-upgrades   
Unattended-Upgrade::Automatic-Reboot "true";
//Unattended-Upgrade::Automatic-Reboot-Time "02:00";


# dpkg -l unattended-upgrades 
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ NameVersion
Architecture   Description
+++-===-==-==-===
ii  unattended-upgrades 0.90ubuntu0.8  all  
  automatic installation of security upgrades


# touch /var/run/reboot-required

# unattended-upgrades --dry-run

(System reboots)

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

Title:
  Running 'unattended-upgrades --dry-run' reboots the machine

Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  Much to my surprise, when I did a dry-run test of unattended-upgrades
  my server was forcibly rebooted. I must have had the file '/var/run
  /reboot-required' present.

  But needless to say: a --dry-run should NOT perform a reboot of the
  server with zero warning. Seriously.

  Output from /var/log/unattended-upgrades.log

  2014-01-15 11:14:26,474 INFO Initial blacklisted packages: 
  2014-01-15 11:14:26,474 INFO Starting unattended upgrades script
  2014-01-15 11:14:26,475 INFO Allowed origins are: 
['o=Ubuntu,a=precise-security']
  2014-01-15 11:14:35,846 INFO Option --dry-run given, *not* performing real 
actions
  2014-01-15 11:14:35,846 INFO Packages that are upgraded: bind9-host dnsutils 
libbind9-80 libdns81 libisc83 libisccc80 libisccfg82 liblwres80 libssl1.0.0 
linux-generic-pae linux-headers-generic-pae linux-image-generic-pae 
linux-libc-dev openssl
  2014-01-15 11:14:35,847 INFO Writing dpkg log to 
'/var/log/unattended-upgrades/unattended-upgrades-dpkg_2014-01-15_11:14:35.846820.log'
  2014-01-15 11:15:10,610 INFO All upgrades installed
  2014-01-15 11:15:10,611 WARNING Found /var/run/reboot-required, rebooting

  Version: 0.76ubuntu1

  As an aside, it makes a lot of sense to me to put the reboot on a
  timer, even if it's only a one minute (i.e. shutdown -r 1). That would
  have at least given me a chance to prevent the reboot if I had seen
  the warning. If that's a configuration setting I don't see it
  anywhere.

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

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

[Touch-packages] [Bug 1722508] Re: Font hinting appears broken on 17.10 beta

[Denis Kalinin]

Yeah, I'm not sure what progress could be made at this point. 
The way I see it, the issue was resolved in a new version of libfreetype 
(2.8.1). The only thing that is left is to propagate the fix to main Ubuntu 
repo.

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

Title:
  Font hinting appears broken on 17.10 beta

Status in freetype package in Ubuntu:
  Confirmed
Status in freetype source package in Artful:
  Confirmed

Bug description:
  It appears that font hinting in 17.10 (beta) doesn't work as expected.
  The issue is easy to miss if you have antialiasing enabled system-
  wise. However, if you install "gnome-tweak-tool" and disable
  antialiasing there, the problem becomes obvious.

  Here is how it looks on 17.10 beta:
  https://postimg.org/image/3auqsbkqtn/

  And here is how it looks on my 16.04 machine (and this is pretty much how 
it's supposed to look):
  https://postimg.org/image/85n5ss3l4b/

  * When comparing the pictures make sure you "Open image in new tab"
  and see them without browser zoom, otherwise the problem may no be
  obvious.

  I suspect that this issue is caused by a bug in some base font
  rendering package that Ubuntu uses (edit: the problem is probably
  caused by FreeType 2.8.0, see my comments below). A couple of months
  ago a similar issue was reported (and promptly fixed) in Chromium
  after they had changed something in FreeType rendering
  (https://bugs.chromium.org/p/chromium/issues/detail?id=748997).

  lsb_release -rd
  Description: Ubuntu Artful Aardvark (development branch)
  Release: 17.10

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

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

[Touch-packages] [Bug 1722508] Re: Font hinting appears broken on 17.10 beta

[Denis Kalinin]

Oh, totally missed your comment. That confirms it.

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

Title:
  Font hinting appears broken on 17.10 beta

Status in freetype package in Ubuntu:
  Confirmed

Bug description:
  It appears that font hinting in 17.10 (beta) doesn't work as expected.
  The issue is easy to miss if you have antialiasing enabled system-
  wise. However, if you install "gnome-tweak-tool" and disable
  antialiasing there, the problem becomes obvious.

  Here is how it looks on 17.10 beta:
  https://postimg.org/image/3auqsbkqtn/

  And here is how it looks on my 16.04 machine (and this is pretty much how 
it's supposed to look):
  https://postimg.org/image/85n5ss3l4b/

  * When comparing the pictures make sure you "Open image in new tab"
  and see them without browser zoom, otherwise the problem may no be
  obvious.

  I suspect that this issue is caused by a bug in some base font
  rendering package that Ubuntu uses (edit: the problem is probably
  caused by FreeType 2.8.0, see my comments below). A couple of months
  ago a similar issue was reported (and promptly fixed) in Chromium
  after they had changed something in FreeType rendering
  (https://bugs.chromium.org/p/chromium/issues/detail?id=748997).

  lsb_release -rd
  Description: Ubuntu Artful Aardvark (development branch)
  Release: 17.10

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

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

[Touch-packages] [Bug 1722508] Re: Font hinting appears broken on 17.10 beta

[Denis Kalinin]

The title of Konsole definitely doesn't look right, but I'm not sure I
would blame FreeType for that. It could be some KDE or Qt problem.

On my installation, Ubuntu Tweak Tool doesn't allow me to set Window
Font to "Ubuntu Bold 9". It simply switches to "Ubuntu Medium 9" and
makes window titles look regular, not bold. However, when I increase the
font size, it does make the title appear bold and it looks perfectly
fine to me (attaching the screenshot).

I also updated to Michael's PPA and tried installing Konsole - the fonts
still look OK.

** Attachment added: "Bold titles"
   
https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/1722508/+attachment/4970305/+files/comparison-bold.png

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

Title:
  Font hinting appears broken on 17.10 beta

Status in freetype package in Ubuntu:
  Confirmed

Bug description:
  It appears that font hinting in 17.10 (beta) doesn't work as expected.
  The issue is easy to miss if you have antialiasing enabled system-
  wise. However, if you install "gnome-tweak-tool" and disable
  antialiasing there, the problem becomes obvious.

  Here is how it looks on 17.10 beta:
  https://postimg.org/image/3auqsbkqtn/

  And here is how it looks on my 16.04 machine (and this is pretty much how 
it's supposed to look):
  https://postimg.org/image/85n5ss3l4b/

  * When comparing the pictures make sure you "Open image in new tab"
  and see them without browser zoom, otherwise the problem may no be
  obvious.

  I suspect that this issue is caused by a bug in some base font
  rendering package that Ubuntu uses (edit: the problem is probably
  caused by FreeType 2.8.0, see my comments below). A couple of months
  ago a similar issue was reported (and promptly fixed) in Chromium
  after they had changed something in FreeType rendering
  (https://bugs.chromium.org/p/chromium/issues/detail?id=748997).

  lsb_release -rd
  Description: Ubuntu Artful Aardvark (development branch)
  Release: 17.10

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

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

[Touch-packages] [Bug 1722508] Re: Font hinting appears broken on 17.10 beta

[Denis Kalinin]

That's strange because bold letters of "Courier New" certainly look fine with 
freetype 2.8.1. 
Do you mind telling me which font you're using?

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

Title:
  Font hinting appears broken on 17.10 beta

Status in freetype package in Ubuntu:
  Confirmed

Bug description:
  It appears that font hinting in 17.10 (beta) doesn't work as expected.
  The issue is easy to miss if you have antialiasing enabled system-
  wise. However, if you install "gnome-tweak-tool" and disable
  antialiasing there, the problem becomes obvious.

  Here is how it looks on 17.10 beta:
  https://postimg.org/image/3auqsbkqtn/

  And here is how it looks on my 16.04 machine (and this is pretty much how 
it's supposed to look):
  https://postimg.org/image/85n5ss3l4b/

  * When comparing the pictures make sure you "Open image in new tab"
  and see them without browser zoom, otherwise the problem may no be
  obvious.

  I suspect that this issue is caused by a bug in some base font
  rendering package that Ubuntu uses (edit: the problem is probably
  caused by FreeType 2.8.0, see my comments below). A couple of months
  ago a similar issue was reported (and promptly fixed) in Chromium
  after they had changed something in FreeType rendering
  (https://bugs.chromium.org/p/chromium/issues/detail?id=748997).

  lsb_release -rd
  Description: Ubuntu Artful Aardvark (development branch)
  Release: 17.10

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

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

[Touch-packages] [Bug 1722508] Re: Font hinting appears broken on 17.10 beta

[Denis Kalinin]

OK, I've just compiled freetype 2.8.1 from the latest source

https://sourceforge.net/projects/freetype/files/freetype2/2.8.1/

and re-pointed the `libfreetype.so.6` link to a newly built .SO-file. I
restarted the system and the hinting started working great. So,
apparently only the 2.8.0 version of "freetype" is affected.
Unfortunately, this is the version that's going to be shipped with
Artful.

** Description changed:

  It appears that font hinting in 17.10 (beta) doesn't work as expected.
  The issue is easy to miss if you have antialiasing enabled system-wise.
  However, if you install "gnome-tweak-tool" and disable antialiasing
  there, the problem becomes obvious.
  
  Here is how it looks on 17.10 beta:
  https://postimg.org/image/3auqsbkqtn/
  
  And here is how it looks on my 16.04 machine (and this is pretty much how 
it's supposed to look):
  https://postimg.org/image/85n5ss3l4b/
  
  * When comparing the pictures make sure you "Open image in new tab" and
  see them without browser zoom, otherwise the problem may no be obvious.
  
  I suspect that this issue is caused by a bug in some base font rendering
- package that Ubuntu uses. A couple of months ago a similar issue was
- reported (and promptly fixed) in Chromium after they had changed
- something in FreeType rendering
+ package that Ubuntu uses (edit: the problem is probably caused by
+ FreeType 2.8.0, see my comments below). A couple of months ago a similar
+ issue was reported (and promptly fixed) in Chromium after they had
+ changed something in FreeType rendering
  (https://bugs.chromium.org/p/chromium/issues/detail?id=748997).
- 
  
  lsb_release -rd
  Description: Ubuntu Artful Aardvark (development branch)
  Release: 17.10

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

Title:
  Font hinting appears broken on 17.10 beta

Status in freetype package in Ubuntu:
  New

Bug description:
  It appears that font hinting in 17.10 (beta) doesn't work as expected.
  The issue is easy to miss if you have antialiasing enabled system-
  wise. However, if you install "gnome-tweak-tool" and disable
  antialiasing there, the problem becomes obvious.

  Here is how it looks on 17.10 beta:
  https://postimg.org/image/3auqsbkqtn/

  And here is how it looks on my 16.04 machine (and this is pretty much how 
it's supposed to look):
  https://postimg.org/image/85n5ss3l4b/

  * When comparing the pictures make sure you "Open image in new tab"
  and see them without browser zoom, otherwise the problem may no be
  obvious.

  I suspect that this issue is caused by a bug in some base font
  rendering package that Ubuntu uses (edit: the problem is probably
  caused by FreeType 2.8.0, see my comments below). A couple of months
  ago a similar issue was reported (and promptly fixed) in Chromium
  after they had changed something in FreeType rendering
  (https://bugs.chromium.org/p/chromium/issues/detail?id=748997).

  lsb_release -rd
  Description: Ubuntu Artful Aardvark (development branch)
  Release: 17.10

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

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

[Touch-packages] [Bug 1722508] Re: Font hinting appears broken on 17.10 beta

[Denis Kalinin]

I've just checked 17.04, and it also looks fine. My guess is that
something has changed in "freetype" when it was updated from 2.6.3 to
2.8.0, so I'm setting "freetype" as the package for this bug.

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

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

Title:
  Font hinting appears broken on 17.10 beta

Status in freetype package in Ubuntu:
  New

Bug description:
  It appears that font hinting in 17.10 (beta) doesn't work as expected.
  The issue is easy to miss if you have antialiasing enabled system-
  wise. However, if you install "gnome-tweak-tool" and disable
  antialiasing there, the problem becomes obvious.

  Here is how it looks on 17.10 beta:
  https://postimg.org/image/3auqsbkqtn/

  And here is how it looks on my 16.04 machine (and this is pretty much how 
it's supposed to look):
  https://postimg.org/image/85n5ss3l4b/

  * When comparing the pictures make sure you "Open image in new tab"
  and see them without browser zoom, otherwise the problem may no be
  obvious.

  I suspect that this issue is caused by a bug in some base font
  rendering package that Ubuntu uses. A couple of months ago a similar
  issue was reported (and promptly fixed) in Chromium after they had
  changed something in FreeType rendering
  (https://bugs.chromium.org/p/chromium/issues/detail?id=748997).

  
  lsb_release -rd
  Description: Ubuntu Artful Aardvark (development branch)
  Release: 17.10

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

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

[Touch-packages] [Bug 1712433] Re: man page typo

[Denis Molony]

The word 'strogly' should be 'strongly'

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

Title:
  man page typo

Status in util-linux package in Ubuntu:
  New

Bug description:
  Note  that mount is very strict about non-root users and all paths specified 
on command line are verified before fstab is
 parsed or a helper program is executed. It's strogly recommended to 
use a valid mountpoint to specify filesystem,  other‐
 wise mount may fail. For example it's bad idea to use NFS or CIFS 
source on command line.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: mount 2.29-1ubuntu2.1
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Wed Aug 23 07:48:32 2017
  InstallationDate: Installed on 2017-03-23 (152 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  SourcePackage: util-linux
  UpgradeStatus: Upgraded to zesty on 2017-08-13 (9 days ago)

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

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

[Touch-packages] [Bug 1712433] [NEW] man page typo

[Denis Molony]

Public bug reported:

Note  that mount is very strict about non-root users and all paths specified on 
command line are verified before fstab is
   parsed or a helper program is executed. It's strogly recommended to use 
a valid mountpoint to specify filesystem,  other‐
   wise mount may fail. For example it's bad idea to use NFS or CIFS source 
on command line.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: mount 2.29-1ubuntu2.1
ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
Uname: Linux 4.10.0-32-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
Date: Wed Aug 23 07:48:32 2017
InstallationDate: Installed on 2017-03-23 (152 days ago)
InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
SourcePackage: util-linux
UpgradeStatus: Upgraded to zesty on 2017-08-13 (9 days ago)

** Affects: util-linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug zesty

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

Title:
  man page typo

Status in util-linux package in Ubuntu:
  New

Bug description:
  Note  that mount is very strict about non-root users and all paths specified 
on command line are verified before fstab is
 parsed or a helper program is executed. It's strogly recommended to 
use a valid mountpoint to specify filesystem,  other‐
 wise mount may fail. For example it's bad idea to use NFS or CIFS 
source on command line.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: mount 2.29-1ubuntu2.1
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Wed Aug 23 07:48:32 2017
  InstallationDate: Installed on 2017-03-23 (152 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  SourcePackage: util-linux
  UpgradeStatus: Upgraded to zesty on 2017-08-13 (9 days ago)

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

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

[Touch-packages] [Bug 1698673] [NEW] package nano 2.5.3-2ubuntu2 failed to install/upgrade: пакет абсолютно неработоспособен; перед настройкой его следует переустановить

[Denis Pastushenko]

Public bug reported:

1) Ubuntu 16.04 LTS
2) Nano 2.5.3-2ubuntu2
3) Nothing
4) Start system

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: nano 2.5.3-2ubuntu2
ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-54-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
Date: Fri Jun 16 23:46:17 2017
ErrorMessage: пакет абсолютно неработоспособен; перед настройкой его  следует 
переустановить
InstallationDate: Installed on 2017-06-16 (2 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: nano
Title: package nano 2.5.3-2ubuntu2 failed to install/upgrade: пакет абсолютно 
неработоспособен; перед настройкой его  следует переустановить
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package nano 2.5.3-2ubuntu2 failed to install/upgrade: пакет абсолютно
  неработоспособен; перед настройкой его  следует переустановить

Status in nano package in Ubuntu:
  New

Bug description:
  1) Ubuntu 16.04 LTS
  2) Nano 2.5.3-2ubuntu2
  3) Nothing
  4) Start system

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nano 2.5.3-2ubuntu2
  ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-54-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Fri Jun 16 23:46:17 2017
  ErrorMessage: пакет абсолютно неработоспособен; перед настройкой его  следует 
переустановить
  InstallationDate: Installed on 2017-06-16 (2 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: nano
  Title: package nano 2.5.3-2ubuntu2 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/nano/+bug/1698673/+subscriptions

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

[Touch-packages] [Bug 1687019] Re: Cannot add a Google account using Online Accounts in Ubuntu Gnome

[Denis Lochman]

Installed Ubuntu GNOME 16.04 yesterday. Same problem. I get blank window
after password. Not sure if if matters, but I'm using 2-step
verification on my Google account.

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

Title:
  Cannot add a Google account using Online Accounts in Ubuntu Gnome

Status in gnome-online-accounts package in Ubuntu:
  Confirmed
Status in gnome-online-accounts package in Arch Linux:
  New

Bug description:
  With Ubuntu Gnome 17.04 (brand new 64bit install on a Dell XPS13
  laptop), I cannot add a Google account using Online-Accounts. If I
  choose to add a new Google account in Online Accounts, a window
  appears where I can enter my Google email. After entering my email and
  pressing the Next button, a window appears where I can enter my Google
  password. After entering the password and pressing the Next button, an
  empty window appears and nothing else happens. I expected this to show
  something useful, and actually add the Google account to my Gnome
  environment.

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

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

[Touch-packages] [Bug 1637201] [NEW] clvm initscript relies on corosync-quorumtool -s which is always retrun 1

[Denis]

Public bug reported:

clvm initscript relies on corosync-quorumtool -s to detect whether corosync 
running or not. quorumtool returns 1 as it's boolean flag for "Quorate".
thus running corosync may be detected just by listing corosync nodes, so 
corosync-quorumtool -l will be more reliable.
a small patch is attached

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

** Patch added: "clvm.init.patch"
   
https://bugs.launchpad.net/bugs/1637201/+attachment/4768227/+files/clvm.init.patch

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

Title:
  clvm initscript relies on corosync-quorumtool -s which is always
  retrun 1

Status in lvm2 package in Ubuntu:
  New

Bug description:
  clvm initscript relies on corosync-quorumtool -s to detect whether corosync 
running or not. quorumtool returns 1 as it's boolean flag for "Quorate".
  thus running corosync may be detected just by listing corosync nodes, so 
corosync-quorumtool -l will be more reliable.
  a small patch is attached

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

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

[Touch-packages] [Bug 1637201] Re: clvm initscript relies on corosync-quorumtool -s which is always retrun 1

[Denis]

sorry, vice-verse changed lines in patch

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

Title:
  clvm initscript relies on corosync-quorumtool -s which is always
  retrun 1

Status in lvm2 package in Ubuntu:
  New

Bug description:
  clvm initscript relies on corosync-quorumtool -s to detect whether corosync 
running or not. quorumtool returns 1 as it's boolean flag for "Quorate".
  thus running corosync may be detected just by listing corosync nodes, so 
corosync-quorumtool -l will be more reliable.
  a small patch is attached

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

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

[Touch-packages] [Bug 1584158] [NEW] Click fails to create chroot behind proxy

[Denis A. Grigoriev]

Public bug reported:

I'm using network proxy. On Ubuntu Xenial using the Ubuntu SDK from the
SDK team ppa the initial click kit creation fails with the error:

Traceback (most recent call last):
  File "/usr/lib/python3.4/urllib/request.py", line 1182, in do_open
h.request(req.get_method(), req.selector, req.data, headers)
  File "/usr/lib/python3.4/http/client.py", line 1088, in request
self._send_request(method, url, body, headers)
  File "/usr/lib/python3.4/http/client.py", line 1126, in _send_request
self.endheaders(body)
  File "/usr/lib/python3.4/http/client.py", line 1084, in endheaders
self._send_output(message_body)
  File "/usr/lib/python3.4/http/client.py", line 922, in _send_output
self.send(msg)
  File "/usr/lib/python3.4/http/client.py", line 857, in send
self.connect()
  File "/usr/lib/python3.4/http/client.py", line 1223, in connect
super().connect()
  File "/usr/lib/python3.4/http/client.py", line 834, in connect
self.timeout, self.source_address)
  File "/usr/lib/python3.4/socket.py", line 512, in create_connection
raise err
  File "/usr/lib/python3.4/socket.py", line 503, in create_connection
sock.connect(sa)
TimeoutError: [Errno 110] Connection timed out

...

Command returned 1: schroot -u root -c source:click-ubuntu-
sdk-15.04-armhf -- /finish.sh

To solve the problem I had to manually run

  click chroot -a armhf -f ubuntu-sdk-15.04 create --keep-broken-chroot

then edit /var/lib/schroot/chroots/click-ubuntu-
sdk-15.04-armhf/finish.sh and add to the beginning of file:

  export http_proxy="http://proxy:port;

then run /finish.sh via maint shell.

---

Possible solution is: modify ClickChroot._generate_finish_script and add
http_proxy environment variable.

Ubuntu 16.04 LTS
click version 0.4.43+16.04.20160203-0ubuntu3

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

** Description changed:

  I'm using network proxy. On Ubuntu Xenial using the Ubuntu SDK from the
  SDK team ppa the initial click kit creation fails with the error:
  
  Traceback (most recent call last):
-   File "/usr/lib/python3.4/urllib/request.py", line 1182, in do_open
- h.request(req.get_method(), req.selector, req.data, headers)
-   File "/usr/lib/python3.4/http/client.py", line 1088, in request
- self._send_request(method, url, body, headers)
-   File "/usr/lib/python3.4/http/client.py", line 1126, in _send_request
- self.endheaders(body)
-   File "/usr/lib/python3.4/http/client.py", line 1084, in endheaders
- self._send_output(message_body)
-   File "/usr/lib/python3.4/http/client.py", line 922, in _send_output
- self.send(msg)
-   File "/usr/lib/python3.4/http/client.py", line 857, in send
- self.connect()
-   File "/usr/lib/python3.4/http/client.py", line 1223, in connect
- super().connect()
-   File "/usr/lib/python3.4/http/client.py", line 834, in connect
- self.timeout, self.source_address)
-   File "/usr/lib/python3.4/socket.py", line 512, in create_connection
- raise err
-   File "/usr/lib/python3.4/socket.py", line 503, in create_connection
- sock.connect(sa)
+   File "/usr/lib/python3.4/urllib/request.py", line 1182, in do_open
+ h.request(req.get_method(), req.selector, req.data, headers)
+   File "/usr/lib/python3.4/http/client.py", line 1088, in request
+ self._send_request(method, url, body, headers)
+   File "/usr/lib/python3.4/http/client.py", line 1126, in _send_request
+ self.endheaders(body)
+   File "/usr/lib/python3.4/http/client.py", line 1084, in endheaders
+ self._send_output(message_body)
+   File "/usr/lib/python3.4/http/client.py", line 922, in _send_output
+ self.send(msg)
+   File "/usr/lib/python3.4/http/client.py", line 857, in send
+ self.connect()
+   File "/usr/lib/python3.4/http/client.py", line 1223, in connect
+ super().connect()
+   File "/usr/lib/python3.4/http/client.py", line 834, in connect
+ self.timeout, self.source_address)
+   File "/usr/lib/python3.4/socket.py", line 512, in create_connection
+ raise err
+   File "/usr/lib/python3.4/socket.py", line 503, in create_connection
+ sock.connect(sa)
  TimeoutError: [Errno 110] Connection timed out
  
  ...
  
  Command returned 1: schroot -u root -c source:click-ubuntu-
  sdk-15.04-armhf -- /finish.sh
  
- 
  To solve the problem I had to manually run
  
-   click chroot -a armhf -f ubuntu-sdk-15.04 create --keep-broken-chroot
+   click chroot -a armhf -f ubuntu-sdk-15.04 create --keep-broken-chroot
  
- then edit /var/lib/schroot/chroots/click-ubuntu-sdk-15.04-armhf/finish.sh and
- add to the beginning of file:
+ then edit /var/lib/schroot/chroots/click-ubuntu-
+ sdk-15.04-armhf/finish.sh and add to the beginning of file:
  
-   export http_proxy="http://proxy:port;
+   export http_proxy="http://proxy:port;
  
  then run /finish.sh via maint shell.
  
  ---
  
  Possible solution is: modify ClickChroot._generate_finish_script and add
  http_proxy environment variable.
  
  

[Touch-packages] [Bug 1569718] Re: Ubuntu Touch (BQ Aquaris 4.5) - Black screen on boot

[Antoine Denis]

The only output I have during the flashing process is what the phone can
display, it says :

-- Wiping data...
Formatting /cache...
Data wipe complete.

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

Title:
  Ubuntu Touch (BQ Aquaris 4.5) - Black screen on boot

Status in Mir:
  Incomplete
Status in mir package in Ubuntu:
  Incomplete
Status in qtmir package in Ubuntu:
  Incomplete
Status in ubuntu-system-settings package in Ubuntu:
  Incomplete
Status in unity-system-compositor package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  Today, I tried to factory reset my BQ Aquaris 4.5 Ubuntu Touch Edition
  with the [Volume Up] + [Power] method but since then, the phone won't
  boot. It only displays the BQ logo and then a black screen (it is
  still on but it's displaying nothing). I tried to connect the phone
  with adb but it doesn't seem to be recognized by the computer.

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

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

[Touch-packages] [Bug 1552467] [NEW] hat computer to this. Copied the dropbox folder from bad disk to this. Had problems installing DB. Looks ok now.

[Denis]

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

Public bug reported:

I had a hard drive crash. I replaced it with this hard drive being used
in another computer. I copied the drop box folder from the defective
hard drive to this hard drive. Then I decided to install drop box. It
wouldn't install from app grid. It wouldn't install from Drop box
download. I was able to install from the command line.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: lightdm 1.17.5-0ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
Uname: Linux 4.4.0-6-generic x86_64
ApportVersion: 2.20-0ubuntu3
AptOrdering:
 nautilus-dropbox: Install
 lightdm: Configure
 ubuntu-mate-core: Configure
 nautilus-dropbox: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Wed Mar  2 18:16:21 2016
DpkgHistoryLog:
 Start-Date: 2016-03-02  18:16:17
 Commandline: aptdaemon role='role-commit-packages' sender=':1.85'
 Install: nautilus-dropbox:amd64 (2.10.0-2)
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2016-02-21 (10 days ago)
InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160127.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1
 apt  1.2.3
SourcePackage: lightdm
Title: package lightdm 1.17.5-0ubuntu2 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  hat computer to this. Copied the dropbox folder from bad disk to this.
  Had problems installing  DB. Looks ok now.

Status in lightdm package in Ubuntu:
  New

Bug description:
  I had a hard drive crash. I replaced it with this hard drive being
  used in another computer. I copied the drop box folder from the
  defective hard drive to this hard drive. Then I decided to install
  drop box. It wouldn't install from app grid. It wouldn't install from
  Drop box download. I was able to install from the command line.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.17.5-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  AptOrdering:
   nautilus-dropbox: Install
   lightdm: Configure
   ubuntu-mate-core: Configure
   nautilus-dropbox: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Wed Mar  2 18:16:21 2016
  DpkgHistoryLog:
   Start-Date: 2016-03-02  18:16:17
   Commandline: aptdaemon role='role-commit-packages' sender=':1.85'
   Install: nautilus-dropbox:amd64 (2.10.0-2)
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-02-21 (10 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160127.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.3
  SourcePackage: lightdm
  Title: package lightdm 1.17.5-0ubuntu2 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1503979] Re: ubuntu-support-status throws exeption No date tag found (regression)

[Denis Gubanov]

root@controller:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 14.04.4 LTS
Release:14.04
Codename:   trusty
root@controller:~# apt-cache policy python-apt python3-apt update-manager-core
python-apt:
  Installed: 0.9.3.5ubuntu2
  Candidate: 0.9.3.5ubuntu2
  Version table:
 *** 0.9.3.5ubuntu2 0
500 http://ru.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 0.9.3.5 0
500 http://ru.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
python3-apt:
  Installed: 0.9.3.5ubuntu2
  Candidate: 0.9.3.5ubuntu2
  Version table:
 *** 0.9.3.5ubuntu2 0
500 http://ru.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 0.9.3.5 0
500 http://ru.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
update-manager-core:
  Installed: 1:0.196.14
  Candidate: 1:0.196.14
  Version table:
 *** 1:0.196.14 0
500 http://ru.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 1:0.196.11 0
500 http://ru.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
root@controller:~# ubuntu-support-status 
Traceback (most recent call last):
  File "/usr/bin/ubuntu-support-status", line 133, in 
pkg.name, support_tag)
  File "/usr/bin/ubuntu-support-status", line 49, in get_maintenance_status
raise Exception("No date tag found")
Exception: No date tag found
root@controller:~#

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

Title:
  ubuntu-support-status throws exeption No date tag found (regression)

Status in python-apt package in Ubuntu:
  Fix Released
Status in python-apt source package in Trusty:
  Fix Released
Status in python-apt source package in Wily:
  Fix Released

Bug description:
  Test Case
  -
  1) Run ubuntu-support-status and observe a crash
  2) Install python3-apt from the -proposed repository
  3) Run ubuntu-support-status and see your status

  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04
  update-manager-core:  1:0.196.14

  Since the last update  ubuntu-support-status throws

  Traceback (most recent call last):
    File "/usr/bin/ubuntu-support-status", line 133, in 
  pkg.name, support_tag)
    File "/usr/bin/ubuntu-support-status", line 49, in get_maintenance_status
  raise Exception("No date tag found")
  Exception: No date tag found

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

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

[Touch-packages] [Bug 1544936] Re: PPC: no mpeg-2 video playback

[Rémi Denis-Courmont]

** Package changed: vlc (Ubuntu) => mesa (Ubuntu)

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

Title:
  PPC: no mpeg-2 video playback

Status in mesa package in Ubuntu:
  New

Bug description:
  Running Ubuntu Mate 16.04a2 on a PowerBook5,8 (15" G4, 2 GB RAM and
  ATI Radeon 9700 128 MB RAM) with latest updates.

  VLC (media player 2.2.2 Weatherwax (revision 2.2.2-0-g6259d80)) does
  not display video encoded with mpeg-2, only audio. The videos are not
  css-encrypted.

  Other formats like mpeg4, h.264 or h.265 work well with VLC!

  DVD playback with VLC failed too.

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

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

Re: [Touch-packages] [Bug 1516716] Re: mon clavier azerty bascule en qzerty

[denis]

Bjr,

Merci de votre reponse rapide;

Je suis sous UBUNTU 14.04 LTS matériel pc portable ACER ASPIRE 77367G
pour règler mon problème je saisis dans le terminal : setxkbmap fr mais 
je suis obligée de le faire à chaque ouverture de session, pour revenir 
au clavier azerty


j'ai aussi essayé (trouvez sur internet ds le forum linux ubuntu)

 1.

/Vérifier les paramètres d'agencement du clavier et que la
disposition française est en première position22/

 2.

/Cliquer sur "Fr" en haut à droite dans la zone de notification,
passer en "En" et revenir en "Fr" Ceci peut régler le problème
généralement pour la session en cours/

 3.

/Taper dans un terminal comme décrit ci-dessus la commande /

setxkbmap fr *__CA FONCTIONNE MAIS A REFAIRE A CHAQUE OUVERTURE DE
SESSION__*

/Ceci règle le problème généralement pour la session en cours /

//
 4.

Taper dans un terminal comme décrit ci-dessus la commande

sudo dpkg-reconfigure keyboard-configuration

/et répondez aux questions. /

//
 5.

/Lancer depuis un terminal "//*ibus-setup*//" et dans l'onglet
"//*avancé*//" cocher "//*utiliser la disposition clavier système*//" /

//


/Exécuter automatiquement la commande setxkbmap fr à chaque
démarrage/

//

 1.

/mettre dans "applications aux démarrage" la commande :/

//

/sh -c "setxkbmap fr"/


permet de remettre le clavier français à chaque connexion *_ca ne
fonctionne pas_*

 1.



Le 17/11/2015 10:17, Sebastien Bacher a écrit :
> Thank you for your bug report. What desktop environment do you use?
> Where did it switch? Did you try to use the indicator to change it back?
>
> ** Changed in: lightdm (Ubuntu)
> Importance: Undecided => Low
>
> ** Changed in: lightdm (Ubuntu)
> Status: New => Incomplete
>

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

Title:
  mon clavier azerty bascule en qzerty

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  Depuis un mois j'utilise ubuntu 14.04 et mon clavier azerty  vient de
  basculer  en qzerty,

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

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

[Touch-packages] [Bug 1516716] [NEW] mon clavier azerty bascule en qzerty

[denis]

Public bug reported:

Depuis un mois j'utilise ubuntu 14.04 et mon clavier azerty  vient de
basculer  en qzerty,

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

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

Title:
  mon clavier azerty bascule en qzerty

Status in lightdm package in Ubuntu:
  New

Bug description:
  Depuis un mois j'utilise ubuntu 14.04 et mon clavier azerty  vient de
  basculer  en qzerty,

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

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

[Touch-packages] [Bug 1482850] Re: cups sucks my system

[Lysenko Denis]

** Changed in: cups (Ubuntu)
   Status: Incomplete => Opinion

** Changed in: cups (Ubuntu)
   Status: Opinion => Invalid

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

Title:
  cups sucks my system

Status in cups package in Ubuntu:
  Invalid

Bug description:
  i setup my Brother HL-5340D on Xubuntu, restart Xubuntu, cups error
  (appor tells)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: cups 2.0.2-1ubuntu3.2
  ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CupsErrorLog: W [07/Aug/2015:17:52:38 +0200] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 
'Brother-HL-5340D-series-Gray..' already exists
  CurrentDesktop: XFCE
  Date: Sat Aug  8 12:09:22 2015
  InstallationDate: Installed on 2015-08-06 (1 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  Lpstat: device for Brother-HL-5340D-series: 
usb://Brother/HL-5340D%20series?serial=C2J484409
  MachineType: Hewlett-Packard HP Compaq dc5700 Microtower
  Papersize: a4
  PpdFiles: Brother-HL-5340D-series: Brother HL-5350DN Foomatic/Postscript
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic 
root=UUID=c5e300de-8101-447b-9e29-3f1529ac4805 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/13/2007
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786E2 v02.04
  dmi.board.name: 0A60h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: CZC74262YK
  dmi.chassis.type: 6
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786E2v02.04:bd04/13/2007:svnHewlett-Packard:pnHPCompaqdc5700Microtower:pvr:rvnHewlett-Packard:rn0A60h:rvr:cvnHewlett-Packard:ct6:cvr:
  dmi.product.name: HP Compaq dc5700 Microtower
  dmi.sys.vendor: Hewlett-Packard

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

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

[Touch-packages] [Bug 1505368] Re: Bug reports after segmentation fault are never generated

[Lysenko Denis]

Tested in 15.04, not confirmed. Tested with "apport-bug -w" in terminal
on calculator, it's collected data and opened for me browser to create
report with all data.

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

Title:
  Bug reports after segmentation fault are never generated

Status in apport package in Ubuntu:
  New

Bug description:
  After `apport` recognizes a segmentation fault it displays a dialog
  which allows to close or restart the application and contains a
  checkbox which offers the option to file a bug online. Even if the box
  is checked no online form to open a new bug report is opened in the
  browser.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: apport 2.17.2-0ubuntu1.5
  ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-31-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Oct 12 21:29:18 2015
  InstallationDate: Installed on 2015-09-14 (27 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1391521] Re: can't type accented letters in ubuntu 14.10 [ast]

[Lysenko Denis]

I have tried on 15.10 its working. 
> http://i.imgur.com/KCQ5T0K.png

** Changed in: unity
   Status: Confirmed => Invalid

** Changed in: unity (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  can't type accented letters in ubuntu 14.10 [ast]

Status in Unity:
  Invalid
Status in unity package in Ubuntu:
  Invalid

Bug description:
  Hi, 
  after a fresh install of Ubuntu 14.10, ( and repositories proposed, and 
backports enabled )  , and a full update, it's impossible to use/type/write 
accented letters in Asturian languages. I've tested in other languages and this 
issue is not present.

  If user choose Asturian language, and Asturian keyboard, it's
  impossible to type á,é,í,ó,ú, ü, ñ.

  Steps to reproduce it:
  1- Change language to Asturian
  2- Change keyboard (Launcher-->System settings-->Text entry-->Asturian 
(Spain, with bottom-dot H and bottom-dot L).
  3- Add it.
  4- In the top panel, clic and select the text entry: Asturian
  5- Open a .txt file, and try to type á,é,í, ó,ú, ü,ñ  (it will doesn't work)

  (if language system is another one, all keyboards works. If we choose
  Asturian, no one keyboard works, and is not possible to use accents)

  I thought this bug was related to:
  https://bugs.launchpad.net/unity/+bug/1330041  but we think they are
  different issues. Anyway, this bug has high importance for Asturian
  users, because they can't write a document, search in browser or write
  an email properly.

  More information:
  lsb_release -rd
  Description:  Ubuntu 14.10
  Release:  14.10

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity 7.3.1+14.10.20141016-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Tue Nov 11 14:39:13 2014
  InstallationDate: Installed on 2014-11-10 (0 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1391521] Re: can't type accented letters in ubuntu 14.10 [ast]

[Lysenko Denis]

Thank you for taking the time to report this bug. We have tried to
recreate this on the latest release of Ubuntu and cannot reproduce it.
This bug is being marked as Invalid. If you believe the problem to still
exist in the latest version of Ubuntu please comment on why that is the
case and change the bug status to NEW.

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

Title:
  can't type accented letters in ubuntu 14.10 [ast]

Status in Unity:
  Invalid
Status in unity package in Ubuntu:
  Invalid

Bug description:
  Hi, 
  after a fresh install of Ubuntu 14.10, ( and repositories proposed, and 
backports enabled )  , and a full update, it's impossible to use/type/write 
accented letters in Asturian languages. I've tested in other languages and this 
issue is not present.

  If user choose Asturian language, and Asturian keyboard, it's
  impossible to type á,é,í,ó,ú, ü, ñ.

  Steps to reproduce it:
  1- Change language to Asturian
  2- Change keyboard (Launcher-->System settings-->Text entry-->Asturian 
(Spain, with bottom-dot H and bottom-dot L).
  3- Add it.
  4- In the top panel, clic and select the text entry: Asturian
  5- Open a .txt file, and try to type á,é,í, ó,ú, ü,ñ  (it will doesn't work)

  (if language system is another one, all keyboards works. If we choose
  Asturian, no one keyboard works, and is not possible to use accents)

  I thought this bug was related to:
  https://bugs.launchpad.net/unity/+bug/1330041  but we think they are
  different issues. Anyway, this bug has high importance for Asturian
  users, because they can't write a document, search in browser or write
  an email properly.

  More information:
  lsb_release -rd
  Description:  Ubuntu 14.10
  Release:  14.10

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity 7.3.1+14.10.20141016-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Tue Nov 11 14:39:13 2014
  InstallationDate: Installed on 2014-11-10 (0 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1486723] [NEW] Xorg crash (i guess)

[Lysenko Denis]

Public bug reported:

Using 15.04 and https://launchpad.net/~oibaf/+archive/ubuntu/graphics-
drivers ppa, for quite a long time, last few days start receiving bug
when whatching full screen videos in youtube or other sites, when
exiting from full screen mode (using google chrome) Unity DE
dissapearing, and i can't do anything, helping only alt+ctrl+f1 and
shutdown -r now or killall Xorg

Also when i'm quitting DOTA 2 Reborn (exiting game) i have the same bug,
everything just stops.

Write me if i can provide more info.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 3.16.0-39.53-generic 3.16.7-ckt11
Uname: Linux 3.16.0-39-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.17.2-0ubuntu1.3
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Wed Aug 19 22:22:52 2015
DistUpgraded: 2015-07-22 17:46:23,053 DEBUG enabling apt cron job
DistroCodename: vivid
DistroVariant: ubuntu
DkmsStatus: vboxhost, 5.0.2, 3.16.0-39-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:844d]
InstallationDate: Installed on 2015-03-04 (168 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-39-generic.efi.signed 
root=UUID=53a91acc-adc1-403f-a2e3-f1c75163920e ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to vivid on 2015-07-22 (28 days ago)
dmi.bios.date: 12/19/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0711
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8H61-MX
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0711:bd12/19/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.64+git1508181830.ab2fad~gd~v
version.libgl1-mesa-dri: libgl1-mesa-dri 11.0~git1508190730.897593~gd~v
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.0~git1508190730.897593~gd~v
version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git1508181931.18e484~gd~v
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Wed Aug 19 22:19:05 2015
xserver.configfile: default
xserver.errors:
 Failed to load module fbdev (module does not exist, 0)
 Failed to load module vesa (module does not exist, 0)
 Failed to load module fbdev (module does not exist, 0)
 Failed to load module vesa (module does not exist, 0)
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.17.1-0ubuntu3

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


** Tags: amd64 apport-bug third-party-packages ubuntu vivid

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

Title:
  Xorg crash (i guess)

Status in xorg package in Ubuntu:
  New

Bug description:
  Using 15.04 and https://launchpad.net/~oibaf/+archive/ubuntu/graphics-
  drivers ppa, for quite a long time, last few days start receiving bug
  when whatching full screen videos in youtube or other sites, when
  exiting from full screen mode (using google chrome) Unity DE
  dissapearing, and i can't do anything, helping only alt+ctrl+f1 and
  shutdown -r now or killall Xorg

  Also when i'm quitting DOTA 2 Reborn (exiting game) i have the same
  bug, everything just stops.

  Write me if i can provide more info.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 3.16.0-39.53-generic 3.16.7-ckt11
  Uname: Linux 3.16.0-39-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.17.2-0ubuntu1.3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Aug 19 22:22:52 2015
  DistUpgraded: 2015-07-22 17:46:23,053 DEBUG enabling apt cron job
  

[Touch-packages] [Bug 1439101] Re: impossible receive MMS any operator on bq aquaris E4.5

[denis f]

Edit #45 
everything works at last!
congrats Canonical!

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

Title:
  impossible receive MMS any operator on bq aquaris E4.5

Status in Canonical System Image:
  Confirmed
Status in Ubuntu Mobile Phone:
  Incomplete
Status in messaging-app package in Ubuntu:
  Confirmed
Status in telephony-service package in Ubuntu:
  Confirmed

Bug description:
  In France no MMS is received regardless of the operator used on bq
  aquaris E4.5 ubuntu Edition

  For information, my operator is Free even if it seems it doesn't
  matter.

  In the same time, let me tell you than I had detect than MMS didn't
  sent when WIFI is ON. I've read some other people who send the same
  information so it's seems to be a real bug.

  Anyway, for resume, For send a MMS, it's OK whan WIFI is OFF, don'T if
  ON, and in all of case we don't receive MMS :-((

  Thank's to you for fix it faster.

  Sorry for my approximativ english.

  Fabien

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1439101/+subscriptions

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

[Touch-packages] [Bug 1439101] Re: impossible receive MMS any operator on bq aquaris E4.5

[denis f]

something new has happened:
I can receive MMS with my Bq Ubuntu Edition, ONLY if sent from another Ubuntu 
OS phone.
OS version is 24.In France, with Free as provider.
Personalized MMS settings:
APN MMS mmsfree
MMSC http://mms.free.fr

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

Title:
  impossible receive MMS any operator on bq aquaris E4.5

Status in Canonical System Image:
  Confirmed
Status in Ubuntu Mobile Phone:
  Incomplete
Status in messaging-app package in Ubuntu:
  Confirmed
Status in telephony-service package in Ubuntu:
  Confirmed

Bug description:
  In France no MMS is received regardless of the operator used on bq
  aquaris E4.5 ubuntu Edition

  For information, my operator is Free even if it seems it doesn't
  matter.

  In the same time, let me tell you than I had detect than MMS didn't
  sent when WIFI is ON. I've read some other people who send the same
  information so it's seems to be a real bug.

  Anyway, for resume, For send a MMS, it's OK whan WIFI is OFF, don'T if
  ON, and in all of case we don't receive MMS :-((

  Thank's to you for fix it faster.

  Sorry for my approximativ english.

  Fabien

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1439101/+subscriptions

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

[Touch-packages] [Bug 1448634] Re: VLC menu items don't enable during playback

[Rémi Denis-Courmont]

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

** This bug is no longer a duplicate of bug 1447224
   Regression: Unable to select audio or subtitle tracks

** This bug has been marked a duplicate of bug 1430059
   LyX menu is not updated by indicator-appmenu in mode unity-all-menus

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

Title:
  VLC menu items don't enable during playback

Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading to 15.04 (and hence Unity 7.3.2) I'm having trouble
  with the menus in VLC.

  Several items on the Video menu are disabled when playback is
  stopped and are meant to become enabled during playback.

  I initially reported this as a bug in VLC, but they reckon it's a
  Unity issue as the right-click context menu works fine:
  https://forum.videolan.org/viewtopic.php?f=13t=125719p=422755#p422755

  I have confirmed this happens with both Statusbar menus and Locally
  Integrated menus. And I can also confirm that on the last day of 14.10
  before I upgraded it was working fine in that version of Unity.

  I've also confirmed that changing to different VLC packages (such as
  those from PPAs) does not resolve the issue.

  Thanks for your help!

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: unity 7.3.2+15.04.20150420-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Sun Apr 26 10:51:54 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-01-30 (85 days ago)
  InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
  SourcePackage: unity
  UpgradeStatus: Upgraded to vivid on 2015-04-23 (2 days ago)

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

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

[Touch-packages] [Bug 798445] Re: can't discern between two files or folder with identical names

[Denis Prost]

I just wanted to know what that status change means.
Should users provide some proposal about how to implement it ?
If this is the case, I should simply propose to display a tooltip showing the 
file path when mouse pointer hovers over it.

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

Title:
  can't discern between two files or folder with identical names

Status in Ayatana Design:
  New
Status in Unity:
  Incomplete
Status in Unity Files Lens:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: dash

  1. create two folders/files with the same name (in two different locations).
  2. press the BFB (Big Freakin Button aka Home Button) and search for that 
folder/file name

  see that there is no way to tell which folder/file is which.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: dash 0.5.5.1-7.2ubuntu1
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic i686
  NonfreeKernelModules: nvidia
  Architecture: i386
  Date: Thu Jun 16 17:50:38 2011
  InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429)
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: dash
  UpgradeStatus: Upgraded to natty on 2011-04-21 (55 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/798445/+subscriptions

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

[Touch-packages] [Bug 798445] Re: can't discern between two files or folder with identical names

[Denis Prost]

Thanks for the answer, I understand.

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

Title:
  can't discern between two files or folder with identical names

Status in Ayatana Design:
  New
Status in Unity:
  Incomplete
Status in Unity Files Lens:
  Incomplete
Status in unity package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: dash

  1. create two folders/files with the same name (in two different locations).
  2. press the BFB (Big Freakin Button aka Home Button) and search for that 
folder/file name

  see that there is no way to tell which folder/file is which.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: dash 0.5.5.1-7.2ubuntu1
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic i686
  NonfreeKernelModules: nvidia
  Architecture: i386
  Date: Thu Jun 16 17:50:38 2011
  InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429)
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: dash
  UpgradeStatus: Upgraded to natty on 2011-04-21 (55 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/798445/+subscriptions

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

[Touch-packages] [Bug 1433319] Re: vlc crashed with SIGSEGV in __memcpy_ia32()

[Rémi Denis-Courmont]

** Package changed: vlc (Ubuntu) = taglib (Ubuntu)

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

Title:
  vlc crashed with SIGSEGV in __memcpy_ia32()

Status in taglib package in Ubuntu:
  New

Bug description:
  VLC crashed when i try play some Flac audio (in Guayadeque cause
  problem too, no cause problem with Audacious, Audacity niether Gnome
  MPlayer).

  VLC 2.2.0-rc2
  Guayadegue 0.3.7 
https://bugs.launchpad.net/ubuntu/+source/guayadeque/+bug/1428673
  flac 1.3.1.1ubuntu1
  Lubuntu 15.04

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: vlc-nox 2.2.0~rc2-2
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic i686
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Tue Mar 17 22:08:00 2015
  ExecutablePath: /usr/bin/vlc
  InstallationDate: Installed on 2013-03-16 (731 days ago)
  InstallationMedia: Lubuntu 12.10 Quantal Quetzal - Release i386 (20121017.1)
  ProcCmdline: /usr/bin/vlc --started-from-file 
file:///home/username/Hudba/American%20beauty/American%20Beauty.flac
  SegvAnalysis:
   Segfault happened at: 0xb7542dd1 __memcpy_ia32+97: rep movsl 
%ds:(%esi),%es:(%edi)
   PC (0xb7542dd1) ok
   source %ds:(%esi) (0xaea2107a) in non-readable VMA region: 
0xaea21000-0xaeb0 ---p None
   destination %es:(%edi) (0xaea20ea0) ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading VMA None
  Signal: 11
  SourcePackage: vlc
  StacktraceTop:
   __memcpy_ia32 () at ../sysdeps/i386/i686/multiarch/../memcpy.S:94
   TagLib::ByteVector::replace(TagLib::ByteVector const, TagLib::ByteVector 
const) () from /usr/lib/i386-linux-gnu/libtag.so.1
   TagLib::ID3v2::SynchData::decode(TagLib::ByteVector const) () from 
/usr/lib/i386-linux-gnu/libtag.so.1
   TagLib::ID3v2::FrameFactory::createFrame(TagLib::ByteVector const, 
TagLib::ID3v2::Header*) const () from /usr/lib/i386-linux-gnu/libtag.so.1
   TagLib::ID3v2::Tag::parse(TagLib::ByteVector const) () from 
/usr/lib/i386-linux-gnu/libtag.so.1
  Title: vlc crashed with SIGSEGV in __memcpy_ia32()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip disk fax floppy fuse lpadmin netdev 
plugdev sambashare scanner sudo tape video

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

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

Re: [Touch-packages] [Bug 1354924] Re: Networkmanager does not autoconnect to wireless network

[Denis Garcia]

I agree I hope that it gets fixed soon. I tried a 15.04 beta and it was not
happening I think. It's really Ubuntu (maybe Debian) specific. It was not
happening in Archlinux for example.

On 12 March 2015 at 22:42, Søren Holm s...@sgh.dk wrote:

 But #13 is not a solution - it's a workaround.

 I changed to Debian becasue of this bug. I've never looked back. The bug
 has been present for 5 months now.

 Btw. is this still occurring in the current 15.04? If it is and it's not
 fixed for the release this bug has potential to be present until 15.10
 which would be really disappointing for most users.

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1354924

 Title:
   Networkmanager does not autoconnect to wireless network

 To manage notifications about this bug go to:

 https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1354924/+subscriptions


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

Title:
  Networkmanager does not autoconnect to wireless network

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  When adding a net wireless network and enable connect automatically'
  networkmanager does not automatically connect to the network wenever
  possible.

  I'm running kubuntu 14.10 daily.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: network-manager 0.9.8.8-0ubuntu23
  ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
  Uname: Linux 3.16.0-6-generic x86_64
  ApportVersion: 2.14.5-0ubuntu4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Aug 10 21:30:03 2014
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-07-11 (29 days ago)
  InstallationMedia: Kubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140710)
  IpRoute:
   default via 192.168.0.2 dev wlan0  proto static 
   192.168.0.0/24 dev wlan0  proto kernel  scope link  src 192.168.0.213  
metric 9
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/1  
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

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

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

[Touch-packages] [Bug 1354924] Re: Networkmanager does not autoconnect to wireless network

[Denis Garcia]

The All users may connect to this network box as explained is #13
worked for me too! Thank you!

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

Title:
  Networkmanager does not autoconnect to wireless network

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  When adding a net wireless network and enable connect automatically'
  networkmanager does not automatically connect to the network wenever
  possible.

  I'm running kubuntu 14.10 daily.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: network-manager 0.9.8.8-0ubuntu23
  ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
  Uname: Linux 3.16.0-6-generic x86_64
  ApportVersion: 2.14.5-0ubuntu4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Aug 10 21:30:03 2014
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-07-11 (29 days ago)
  InstallationMedia: Kubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140710)
  IpRoute:
   default via 192.168.0.2 dev wlan0  proto static 
   192.168.0.0/24 dev wlan0  proto kernel  scope link  src 192.168.0.213  
metric 9
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/1  
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

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

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

[Touch-packages] [Bug 1354924] Re: Networkmanager does not autoconnect to wireless network

[Denis Garcia]

Didn't work for me. My WLAN driver is iwlwifi. I'm still having the bug!
I would really like to see it fix before Kubuntu 15.04 is release.

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

Title:
  Networkmanager does not autoconnect to wireless network

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  When adding a net wireless network and enable connect automatically'
  networkmanager does not automatically connect to the network wenever
  possible.

  I'm running kubuntu 14.10 daily.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: network-manager 0.9.8.8-0ubuntu23
  ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
  Uname: Linux 3.16.0-6-generic x86_64
  ApportVersion: 2.14.5-0ubuntu4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Aug 10 21:30:03 2014
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-07-11 (29 days ago)
  InstallationMedia: Kubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140710)
  IpRoute:
   default via 192.168.0.2 dev wlan0  proto static 
   192.168.0.0/24 dev wlan0  proto kernel  scope link  src 192.168.0.213  
metric 9
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/1  
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

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

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

[Touch-packages] [Bug 1252121] Re: missing PrepareForSleep signal after resuming, causing networking to stay disabled

[Denis Prost]

Same feeling, I'm disappointed no one seems to take care of that basic
bug that keeps me from using Ubuntu as my daily distro.

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

Title:
  missing PrepareForSleep signal after resuming, causing networking to
  stay disabled

Status in NetworkManager:
  New
Status in wicd:
  New
Status in systemd-shim package in Ubuntu:
  Confirmed
Status in systemd-shim source package in Saucy:
  Won't Fix
Status in systemd-shim source package in Trusty:
  Confirmed

Bug description:
  As per request from bug #1184262, this is a new report, along with
  dbus (to be attached)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: systemd-services 204-0ubuntu19
  Uname: Linux 3.12.0-custom x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Sun Nov 17 20:24:41 2013
  MarkForUpload: True
  SourcePackage: systemd
  UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago)

  SRU INFORMATION:
  FIX: https://github.com/desrt/systemd-shim/commit/9e1ebe3ab (in trusty 
already)

  Regression potential: Low. Flushing the session bus was introduced in
  version 4 and is obviously bogus as in a system D-BUS service there is
  no session bus. This causes lots of confusing error messages and
  unnecessary overhead like trying to start dbus-launch. Flushing the
  system bus is low-risk, in most cases it's a no-op and it would
  otherwise prevent losing signals after waking up. No known
  regressions.

  TEST CASE: Run several suspend/resume cycles with the lid, session
  indicator menu, and verify that the network comes back up. It is known
  that this fix is necessary but not sufficient, so it is not expected
  to fix all cases. But it should not make things worse, so if network
  now does not come up any more on a machine where it previously worked
  this would count as failure/regression.

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

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

[Touch-packages] [Bug 943162] Re: libgl1-mesa-dev links libGL.so to mesa/libGL.so which conflicts with nvidia's libGL.

[Denis Bernard]

Same issue with libgles1-mesa-dev and libgles2-mesa-dev in 14.04

As a workaround, it is safe to remove the following:

/usr/lib/x86_64-linux-gnu/libGL.so
/usr/lib/x86_64-linux-gnu/libEGL.so
/usr/lib/x86_64-linux-gnu/libGLESv1_CM.so
/usr/lib/x86_64-linux-gnu/libGLESv2.so

Then run ldconfig

This only affects programs that try to dlopen() lib*GL*.so instead of
lib*GL*.so.1 (like Factor)

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

Title:
  libgl1-mesa-dev links libGL.so to mesa/libGL.so which conflicts with
  nvidia's libGL.

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  It seems like libgl1-mesa-dev creates the symbolic link
  /usr/lib/x86_64-linux-gnu/libGL.so, pointing to mesa/libGL.so. This
  conflicts with NVidia's libGL.so and ignores the alternative settings.
  For instance, a call to dlopen will load the mesa library instead of
  the nvidia library. This is in particular a problem when using OpenGL
  in dynamic languages such as Python or Common Lisp since they foreign
  function interfaces use something like dlopen.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: libgl1-mesa-dev 7.11-0ubuntu3
  ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17
  Uname: Linux 3.0.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  280.13  Wed Jul 27 16:53:56 
PDT 2011
   GCC version:  gcc version 4.6.1 (Ubuntu/Linaro 4.6.1-9ubuntu3)
  .tmp.unity.support.test.0:
   
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,compiztoolbox,grid,vpswitch,resize,imgpng,snap,regex,animation,workarounds,mousepoll,expo,place,move,gnomecompat,unitymtgrabhandles,wall,ezoom,session,fade,scale,unityshell]
  CompositorRunning: None
  Date: Wed Feb 29 11:13:06 2012
  DistUpgraded: Fresh install
  DistroCodename: oneiric
  DistroVariant: ubuntu
  DkmsStatus: nvidia-current-updates, 280.13, 3.0.0-16-generic, x86_64: 
installed
  ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu
  GraphicsCard:
   nVidia Corporation G94 [GeForce 9600 GT] [10de:0622] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:827c]
  JockeyStatus:
   xorg:nvidia_173 - NVIDIA accelerated graphics driver (Proprietary, Disabled, 
Not in use)
   xorg:nvidia_173_updates - NVIDIA accelerated graphics driver (post-release 
updates) (Proprietary, Disabled, Not in use)
   xorg:nvidia_current - NVIDIA accelerated graphics driver (Proprietary, 
Disabled, Not in use)
   xorg:nvidia_current_updates - NVIDIA accelerated graphics driver 
(post-release updates) (Proprietary, Enabled, In use)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
   LC_PAPER=de_DE.UTF-8
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-16-generic 
root=UUID=cc3cd9ea-6f90-44c3-a6e8-67758cff1603 ro splash quiet vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/27/2009
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: ASUS M3N78 PRO ACPI BIOS Revision 0801
  dmi.board.name: M3N78 PRO
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: 1.XX
  dmi.chassis.asset.tag: 123456789000
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrASUSM3N78PROACPIBIOSRevision0801:bd03/27/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM3N78PRO:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu6.1
  version.ia32-libs: ia32-libs 20090808ubuntu26
  version.libdrm2: libdrm2 2.4.26-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu7.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20110811.g93fc084-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.15.901-1ubuntu2.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20110411+8378443-1

To manage notifications about this bug go to:

[Touch-packages] [Bug 1354924] Re: Networkmanager does not autoconnect to wireless network

[Denis Garcia]

Hey,

So I just tried with an Ubuntu 14.10 live USB key and after resuming the
wifi reconnects. With the Kubuntu 14.10 live USB after the resume it
asks for the wifi password again...

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

Title:
  Networkmanager does not autoconnect to wireless network

Status in “network-manager” package in Ubuntu:
  Confirmed

Bug description:
  When adding a net wireless network and enable connect automatically'
  networkmanager does not automatically connect to the network wenever
  possible.

  I'm running kubuntu 14.10 daily.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: network-manager 0.9.8.8-0ubuntu23
  ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
  Uname: Linux 3.16.0-6-generic x86_64
  ApportVersion: 2.14.5-0ubuntu4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Aug 10 21:30:03 2014
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-07-11 (29 days ago)
  InstallationMedia: Kubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140710)
  IpRoute:
   default via 192.168.0.2 dev wlan0  proto static 
   192.168.0.0/24 dev wlan0  proto kernel  scope link  src 192.168.0.213  
metric 9
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/1  
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

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

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

[Touch-packages] [Bug 1354924] Re: Networkmanager does not autoconnect to wireless network

[Denis Garcia]

Hi, I have a similar problem on my X230. I was previously using Arch and
didn't have that bug. How can I help?

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

Title:
  Networkmanager does not autoconnect to wireless network

Status in “network-manager” package in Ubuntu:
  Confirmed

Bug description:
  When adding a net wireless network and enable connect automatically'
  networkmanager does not automatically connect to the network wenever
  possible.

  I'm running kubuntu 14.10 daily.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: network-manager 0.9.8.8-0ubuntu23
  ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
  Uname: Linux 3.16.0-6-generic x86_64
  ApportVersion: 2.14.5-0ubuntu4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Aug 10 21:30:03 2014
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-07-11 (29 days ago)
  InstallationMedia: Kubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140710)
  IpRoute:
   default via 192.168.0.2 dev wlan0  proto static 
   192.168.0.0/24 dev wlan0  proto kernel  scope link  src 192.168.0.213  
metric 9
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/1  
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

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

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

[Touch-packages] [Bug 1027410] Re: Crash when opening a WMV file

[Rémi Denis-Courmont]

** Changed in: vlc (Ubuntu)
   Status: Confirmed = Invalid

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

Title:
  Crash when opening a WMV file

Status in “libav” package in Ubuntu:
  Confirmed
Status in “vlc” package in Ubuntu:
  Invalid

Bug description:
  There is a WMV file I am trying to play but VLC crashes when I open it
  :

  VLC media player 2.0.1 Twoflower (revision 2.0.1-0-gf432547)
  [0x9cbd908] main libvlc: Lancement de vlc avec l'interface par défaut. 
Utilisez « cvlc » pour démarrer VLC sans interface.
  [vc1 @ 0xb5304200] Bits overconsumption: 102040  102032
  [vc1 @ 0xb5304200] concealing 837 DC, 837 AC, 837 MV errors
  [vc1 @ 0xb5304200] Bits overconsumption: 22776  22768
  [vc1 @ 0xb5304200] concealing 980 DC, 980 AC, 980 MV errors
  [vc1 @ 0xb5304200] Bits overconsumption: 74392  74384
  [vc1 @ 0xb5304200] concealing 366 DC, 366 AC, 366 MV errors
  [vc1 @ 0xb5304200] Bits overconsumption: 39104  39096 at 38x19
  [vc1 @ 0xb5304200] concealing 369 DC, 369 AC, 369 MV errors
  [0xb5100618] main input error: ES_OUT_SET_(GROUP_)PCR  is called too late 
(pts_delay increased to 300 ms)
  [0xb5100618] main input error: ES_OUT_RESET_PCR called
  [wmav2 @ 0xb5322a20] prev_block_len_bits 6 out of range
  [wmav2 @ 0xb5322a20] next_block_len_bits 5 out of range
  [wmav2 @ 0xb5322a20] prev_block_len_bits 4 out of range
  [wmav2 @ 0xb5322a20] block_len_bits 6 out of range
  [vc1 @ 0xb5304200] Bits overconsumption: 94824  94816
  [vc1 @ 0xb5304200] concealing 1004 DC, 1004 AC, 1004 MV errors
  [vc1 @ 0xb5304200] Bits overconsumption: 69064  69056
  [vc1 @ 0xb5304200] concealing 630 DC, 630 AC, 630 MV errors
  [wmav2 @ 0xb5322a20] prev_block_len_bits 6 out of range
  [wmav2 @ 0xb5322a20] prev_block_len_bits 4 out of range
  [wmav2 @ 0xb5322a20] frame_len overflow
  [wmav2 @ 0xb5322a20] prev_block_len_bits 4 out of range
  [wmav2 @ 0xb5322a20] prev_block_len_bits 5 out of range
  [wmav2 @ 0xb5322a20] overflow in spectral RLE, ignoring
  [wmav2 @ 0xb5322a20] next_block_len_bits 5 out of range
  [wmav2 @ 0xb5322a20] next_block_len_bits 5 out of range
  [wmav2 @ 0xb5322a20] prev_block_len_bits 5 out of range
  [wmav2 @ 0xb5322a20] next_block_len_bits 4 out of range
  [wmav2 @ 0xb5322a20] block_len_bits 5 out of range
  [wmav2 @ 0xb5322a20] block_len_bits 6 out of range
  [wmav2 @ 0xb5322a20] prev_block_len_bits 6 out of range
  [wmav2 @ 0xb5322a20] prev_block_len_bits 4 out of range
  [wmav2 @ 0xb5322a20] block_len_bits 4 out of range
  [wmav2 @ 0xb5322a20] next_block_len_bits 4 out of range
  [vc1 @ 0xb5304200] Bits overconsumption: 80344  80336
  [vc1 @ 0xb5304200] concealing 411 DC, 411 AC, 411 MV errors
  [vc1 @ 0xb5304200] Bits overconsumption: 61368  61360
  [vc1 @ 0xb5304200] concealing 753 DC, 753 AC, 753 MV errors
  [vc1 @ 0xb5304200] Bits overconsumption: 53624  53616 at 0x22
  [vc1 @ 0xb5304200] concealing 229 DC, 229 AC, 229 MV errors
  Erreur de segmentation (core dumped)

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: vlc 2.0.1-4
  ProcVersionSignature: Ubuntu 3.2.0-26.41-generic-pae 3.2.19
  Uname: Linux 3.2.0-26-generic-pae i686
  ApportVersion: 2.0.1-0ubuntu11
  Architecture: i386
  Date: Sat Jul 21 16:00:32 2012
  ProcEnviron:
   LANGUAGE=fr_FR:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: vlc
  UpgradeStatus: Upgraded to precise on 2012-04-27 (85 days ago)

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

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

[Touch-packages] [Bug 1369103] Re: brightness keys don't work after resume from hibernate

[Denis Prost]

This problem still exists with Ubuntu 14.10

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

Title:
  brightness keys don't work after resume from hibernate

Status in “xorg” package in Ubuntu:
  New

Bug description:
  This is an hibernate specific problem. After resume from suspend to ram, 
brightness keys do work.
  So I guess this is a different problem than issue 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/935778.
  (I tried the different solutions described in this bug comments, such as 
modifying /etc/default/grub default command line, adding a script in 
/etc/pm/sleep.d, creating a special xorg.conf file, none worked).
  My computer is a Toshiba Tecra A10-11T laptop.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Sep 13 16:47:21 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems Device [1179:0004]
 Subsystem: Toshiba America Info Systems Device [1179:0004]
  InstallationDate: Installed on 2014-06-20 (85 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417)
  MachineType: TOSHIBA TECRA A10
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic 
root=UUID=4854df34-2476-44dc-a6e1-0a69ef18a7ff ro quiet splash resume=/dev/sda7 
acpi_backlight=vendor vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/08/2009
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 3.00
  dmi.board.asset.tag: 00
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion3.00:bd09/08/2009:svnTOSHIBA:pnTECRAA10:pvrPTSB1E-01T009FR:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.name: TECRA A10
  dmi.product.version: PTSB1E-01T009FR
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1
  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.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Sat Sep 13 16:11:20 2014
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.15.1-0ubuntu2.1

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

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

[Touch-packages] [Bug 1284308] Re: Bogus another operation in progress error. Can't copy files from a bluetooth device

[denis]

I have upgraded to Ubuntu 13.10.

And as usual, with the upgrade, a whole new bluetooth issue, which this
times makes transferring files from the phone to the computer (which
already was painful) completely impossible!

How I reproduce (100% systematic):
1 - click on the Bluetooth icon in the notification area
2 - from the dropdown menu, choose bluetooth settings
3 - select the phone among the listed devices
4 - click on Browse files
5 - A Nautilus windows opens, allowing me to browse files on the phone. Open 
the DCIM/Camera folder
6 - Select a couple of files. Either drag and drop them, or copy and then paste 
them, into a folder on the computer

= I systematically get an error, but it can be any of the two variants
shown in the two screenshots (one says there was an error copying the
file, the other says there was an error getting information about the
file; in both cases the given reason is another operation in progress.
Note also that in one case there is a Retry button, in the other there
is not - pure nonsense).

I then ejected the phone with the eject button next to its name in
Nautilus, and repeated the whole process.

I randomly get any of three outcomes:
- the one described above (MOST of the times)
- at step 4, I get an error This location could not be displayed. Another 
operation in progress, so I cannot even browse files
or
- at some point (not sure whether it was at step 4 above or when ejecting the 
phone) something CRASHES (I get the usual Ubuntu message informing me of that).

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

Title:
  Bogus another operation in progress error. Can't copy files from a
  bluetooth device

Status in “bluez” package in Ubuntu:
  Confirmed
Status in “gnome-vfs-obexftp” package in Ubuntu:
  Confirmed
Status in “gvfs” package in Ubuntu:
  Confirmed
Status in “obex-data-server” package in Ubuntu:
  Confirmed

Bug description:
  I have upgraded to Ubuntu 13.10.

  And as usual, with the upgrade, a whole new bluetooth issue, which
  this times makes transferring files from the phone to the computer
  (which already was painful) completely impossible!

  How I reproduce (100% systematic):
  1 - click on the Bluetooth icon in the notification area
  2 - from the dropdown menu, choose bluetooth settings
  3 - select the phone among the listed devices
  4 - click on Browse files
  5 - A Nautilus windows opens, allowing me to browse files on the phone. Open 
the DCIM/Camera folder
  6 - Select a couple of files. Either drag and drop them, or copy and then 
paste them, into a folder on the computer

  = I systematically get an error, but it can be any of the two
  variants shown in the two screenshots (one says there was an error
  copying the file, the other says there was an error getting
  information about the file; in both cases the given reason is another
  operation in progress. Note also that in one case there is a Retry
  button, in the other there is not - pure nonsense).

  I then ejected the phone with  the eject button next to its name in
  Nautilus, and repeated the whole process.

  I randomly get any of three outcomes:
  - the one described above (MOST of the times)
  - at step 4, I get an error This location could not be displayed. Another 
operation in progress, so I cannot even browse files
  or
  - at some point (not sure whether it was at step 4 above or when ejecting 
the phone) something CRASHES (I get the usual Ubuntu message informing me of 
that).

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
  Uname: Linux 3.11.0-17-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Mon Feb 24 21:24:05 2014
  InstallationDate: Installed on 2013-10-11 (136 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  InterestingModules: bnep rfcomm btusb bluetooth
  MachineType: Acer Aspire V3-571G
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic 
root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to saucy on 2014-02-23 (1 days ago)
  dmi.bios.date: 10/15/2012
  dmi.bios.vendor: Acer
  dmi.bios.version: V2.07
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: VA50_HC_CR
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.07
  dmi.modalias: 
dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07:
  dmi.product.name: Aspire V3-571G
  dmi.product.version: V2.07
  dmi.sys.vendor: Acer
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
    BD Address: A4:17:31:0D:4A:70  ACL MTU: 1022:8  SCO 

[Touch-packages] [Bug 1374825] Re: VDPAU does not work in libav on Utopic

[Rémi Denis-Courmont]

[7f909958] vdpau_avcodec generic error: decoder profile not
supported: 6 means that:

1) your libavcodec installation does support VDPAU properly, and
2 ) your VDPAU driver does not support H.264 decoding at all (or reports 
incorrect capabilities).

Closing as invalid.

** Changed in: vlc (Ubuntu)
   Status: New = Invalid

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

Title:
  VDPAU does not work in libav on Utopic

Status in “libav” package in Ubuntu:
  Invalid
Status in “mplayer” package in Ubuntu:
  New
Status in “mplayer2” package in Ubuntu:
  New
Status in “mpv” package in Ubuntu:
  New
Status in “vlc” package in Ubuntu:
  Invalid

Bug description:
  After upgrading a Kubuntu Trusty x86_64 system to Utopic, VDPAU
  support has stopped working in all applications that use libav.  In
  mplayer2, it prints Cannot find codec 'h264_vdpau' in libavcodec...
  and in VLC I get [7f909958] vdpau_avcodec generic error:
  decoder profile not supported: 6.

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

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

[Touch-packages] [Bug 1369103] [NEW] brightness heys don't work after resume from hibernate

[Denis Prost]

Public bug reported:

This is an hibernate specific problem. After resume from suspend to ram, 
brightness keys do work.
So I guess this is a different problem than issue 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/935778.
(I tried the different solutions described in this bug comments, such as 
modifying /etc/default/grub default command line, adding a script in 
/etc/pm/sleep.d, creating a special xorg.conf file, none worked).
My computer is a Toshiba Tecra A10-11T laptop.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
Uname: Linux 3.13.0-35-generic i686
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.4
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Sat Sep 13 16:47:21 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
   Subsystem: Toshiba America Info Systems Device [1179:0004]
   Subsystem: Toshiba America Info Systems Device [1179:0004]
InstallationDate: Installed on 2014-06-20 (85 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417)
MachineType: TOSHIBA TECRA A10
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic 
root=UUID=4854df34-2476-44dc-a6e1-0a69ef18a7ff ro quiet splash resume=/dev/sda7 
acpi_backlight=vendor vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/08/2009
dmi.bios.vendor: TOSHIBA
dmi.bios.version: Version 3.00
dmi.board.asset.tag: 00
dmi.board.name: Portable PC
dmi.board.vendor: TOSHIBA
dmi.board.version: Version A0
dmi.chassis.asset.tag: 00
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: Version 1.0
dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion3.00:bd09/08/2009:svnTOSHIBA:pnTECRAA10:pvrPTSB1E-01T009FR:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
dmi.product.name: TECRA A10
dmi.product.version: PTSB1E-01T009FR
dmi.sys.vendor: TOSHIBA
version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1
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.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Sat Sep 13 16:11:20 2014
xserver.configfile: /etc/X11/xorg.conf
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.15.1-0ubuntu2.1

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


** Tags: apport-bug compiz-0.9 i386 trusty ubuntu

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

Title:
  brightness heys don't work after resume from hibernate

Status in “xorg” package in Ubuntu:
  New

Bug description:
  This is an hibernate specific problem. After resume from suspend to ram, 
brightness keys do work.
  So I guess this is a different problem than issue 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/935778.
  (I tried the different solutions described in this bug comments, such as 
modifying /etc/default/grub default command line, adding a script in 
/etc/pm/sleep.d, creating a special xorg.conf file, none worked).
  My computer is a Toshiba Tecra A10-11T laptop.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Sep 13 16:47:21 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset 

[Touch-packages] [Bug 1369103] Re: brightness keys don't work after resume from hibernate

[Denis Prost]

** Summary changed:

- brightness heys don't work after resume from hibernate
+ brightness keys don't work after resume from hibernate

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

Title:
  brightness keys don't work after resume from hibernate

Status in “xorg” package in Ubuntu:
  New

Bug description:
  This is an hibernate specific problem. After resume from suspend to ram, 
brightness keys do work.
  So I guess this is a different problem than issue 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/935778.
  (I tried the different solutions described in this bug comments, such as 
modifying /etc/default/grub default command line, adding a script in 
/etc/pm/sleep.d, creating a special xorg.conf file, none worked).
  My computer is a Toshiba Tecra A10-11T laptop.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.4
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Sep 13 16:47:21 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems Device [1179:0004]
 Subsystem: Toshiba America Info Systems Device [1179:0004]
  InstallationDate: Installed on 2014-06-20 (85 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417)
  MachineType: TOSHIBA TECRA A10
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic 
root=UUID=4854df34-2476-44dc-a6e1-0a69ef18a7ff ro quiet splash resume=/dev/sda7 
acpi_backlight=vendor vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/08/2009
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 3.00
  dmi.board.asset.tag: 00
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion3.00:bd09/08/2009:svnTOSHIBA:pnTECRAA10:pvrPTSB1E-01T009FR:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.name: TECRA A10
  dmi.product.version: PTSB1E-01T009FR
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1
  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.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Sat Sep 13 16:11:20 2014
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.15.1-0ubuntu2.1

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

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

Re: [Touch-packages] [Bug 1077032] Re: printing gets wrong after some pages on Epson Stylus Photo 750

[Denis Prost]

Unfortunately, I cannot perform tests anymore, my printer broke down and 
I couldn't get it repaired.

Le 09/08/2014 14:36, Pascal De Vuyst a écrit :
 Any luck with the Foomatic/stcolor printer driver (probably good for
 black and white)?

 ** Changed in: cups (Ubuntu)
 Status: New = Incomplete


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

Title:
  printing gets wrong after some pages on Epson Stylus Photo 750

Status in “cups” package in Ubuntu:
  Incomplete

Bug description:
  When I print several documents on my Epson Stylus Photo 750, after some 
pages, the printing gets wrong : the attached file shows what I get.
  I tried different drivers (gutenprint-ijs-simplified.5.2, Gutenprint 
v5.2.8-pre1) but the result is the same.
  This happens both on Ubuntu 12.04 and 12.10, while I don't get such problem 
with Debian Squeeze.

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

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

[Touch-packages] [Bug 408719] Re: QtDbus: KIO scheduler exit handler crashes VLC

[Rémi Denis-Courmont]

Fixed in Qt 4.8.6 according to upstream bug.

** Changed in: qt
   Status: New = Fix Released

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

Title:
  QtDbus: KIO scheduler exit handler crashes VLC

Status in kdelibs:
  Won't Fix
Status in Qt:
  Fix Released
Status in VLC media player:
  Invalid
Status in “qt4-x11” package in Ubuntu:
  Confirmed
Status in “vlc” package in Ubuntu:
  Invalid
Status in “kde4libs” package in Debian:
  Fix Released
Status in Fedora:
  New
Status in “qt4-x11” package in Mandriva:
  Unknown

Bug description:
  Binary package hint: vlc

  Description:  Ubuntu karmic (development branch)
  Release:  9.10

  On Kubuntu, VLC crashes at exit if the open file (or save file) dialog
  has been ever used.

  ProblemType: Crash
  Architecture: i386
  Date: Tue Aug  4 08:36:19 2009
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/bin/vlc
  Package: vlc-nox 1.0.0-1ubuntu1
  ProcCmdline: vlc
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-5.24-generic
  SegvAnalysis:
   Segfault happened at: 0x5b1b846: mov0x4(%edx),%ecx
   PC (0x05b1b846) ok
   source 0x4(%edx) (0x0004) not located in a known VMA region (needed 
readable region)!
   destination %ecx ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: vlc
  StacktraceTop:
   ?? () from /usr/lib/libQtDBus.so.4
   ?? () from /usr/lib/libQtDBus.so.4
   QMetaObject::activate(QObject*, int, int, void**) ()
   QMetaObject::activate(QObject*, QMetaObject const*, int, int, void**) () 
from /usr/lib/libQtCore.so.4
   QObject::destroyed(QObject*) () from /usr/lib/libQtCore.so.4
  Title: vlc crashed with SIGSEGV in QMetaObject::activate()
  Uname: Linux 2.6.31-5-generic i686
  UserGroups: adm admin audio cdrom dialout lpadmin plugdev pulse sambashare 
video

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

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