[Touch-packages] [Bug 1251178] Re: qdbus and qdbusviewer crash with "No such file or directory"

2021-09-12 Thread Georges
It's 2021, and this issue still exists.
In my case with qdbus command, installing and re-installing qt5-default does 
not help.
The solution of @yatsek worked:


qdbus: could not find a Qt installation of ''

$ sudo apt-get install apt-file

$ sudo apt-file update

$ apt-file search /usr/lib/qt5/bin/qdbus
qdbus-qt5: /usr/lib/qt5/bin/qdbus 
qtbase5-dev-tools: /usr/lib/qt5/bin/qdbuscpp2xml
qtbase5-dev-tools: /usr/lib/qt5/bin/qdbusxml2cpp
qttools5-dev-tools: /usr/lib/qt5/bin/qdbusviewer

$ sudo apt-get install qdbus-qt5

Voila!

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

Title:
  qdbus and qdbusviewer crash with "No such file or directory"

Status in qt4-x11 package in Ubuntu:
  Confirmed
Status in qtchooser package in Ubuntu:
  Confirmed

Bug description:
  Release: Ubuntu 13.10 (32-bit)

  Package versions:
  qtdbus 4:4.8.4+dfsg-0ubuntu18
  qtchooser 26-3ubuntu2

  Expected behavior:

  The `qdbus` program runs, as does the related program `qdbusviewer`.

  Actual behavior:

  If I run the `qdbus` program, it always crashes:

  user@host:~$ qdbus --help
  qdbus: could not exec '/usr/lib/i386-linux-gnu/qt5/bin/qdbus': No such file 
or directory

  The `qdbus` executable is actually:

  user@host:~$ ls --full-time $(which qdbus)
  lrwxrwxrwx 1 root root 9 2013-08-07 14:48:40.0 + /usr/bin/qdbus 
-> qtchooser

  Note that `/usr/lib/i386-linux-gnu/qt4/bin/qdbus` exists and seems to
  work if I invoke it directly.

  There's a `qdbus-qt5` package in the universe repository. It was not
  pulled in as a dependency, but manually installing it fixes the issue.
  Therefore it's either a packaging error or a bug in qtchooser.

  A similar thing happens if I run `qdbusviewer`:

  user@host:~$ qdbusviewer
  qdbusviewer: could not exec '/usr/lib/i386-linux-gnu/qt5/bin/qdbusviewer': No 
such file or directory

  except that installing `qdbus-qt5` doesn't fix the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: qdbus 4:4.8.4+dfsg-0ubuntu18
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic i686
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: i386
  Date: Thu Nov 14 09:34:24 2013
  MarkForUpload: True
  SourcePackage: qt4-x11
  UpgradeStatus: Upgraded to saucy on 2013-10-23 (22 days ago)

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


-- 
Mailing list: https://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 1838022] [NEW] écran dédoublé

2019-07-26 Thread Georges Rais
Public bug reported:

écran dédoublé

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-25-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Fri Jul 26 13:47:40 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 NVIDIA Corporation G86M [GeForce 8600M GS] [10de:0425] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Hewlett-Packard Company G86M [GeForce 8600M GS] [103c:30cc]
InstallationDate: Installed on 2019-04-11 (105 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
MachineType: Hewlett-Packard HP Pavilion dv9700 Notebook PC
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-25-generic 
root=UUID=73611be8-53b3-468d-8975-31c75971cbfc ro nopat vesafb.invalid=1 
drm.debug=0xe plymouth:debug
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/27/2007
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.42
dmi.board.name: 30CB
dmi.board.vendor: Quanta
dmi.board.version: 79.27
dmi.chassis.type: 10
dmi.chassis.vendor: Quanta
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.42:bd12/27/2007:svnHewlett-Packard:pnHPPaviliondv9700NotebookPC:pvrRev1:rvnQuanta:rn30CB:rvr79.27:cvnQuanta:ct10:cvrN/A:
dmi.product.family: 103C_5335KV
dmi.product.name: HP Pavilion dv9700 Notebook PC
dmi.product.sku: KL024EA#UUZ
dmi.product.version: Rev 1
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Fri Jul 26 13:44:32 2019

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

Title:
  écran dédoublé

Status in xorg package in Ubuntu:
  New

Bug description:
  écran dédoublé

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-25-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri Jul 26 13:47:40 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation G86M [GeForce 8600M GS] [10de:0425] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Hewlett-Packard Company G86M [GeForce 8600M GS] [103c:30cc]
  InstallationDate: Installed on 2019-04-11 (105 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Hewlett-Packard HP Pavilion dv9700 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-25-generic 
root=UUID=73611be8-53b3-468d-8975-31c75971cbfc ro nopat vesafb.invalid=1 
drm.debug=0xe plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/27/2007
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.42
  dmi.board.name: 30CB
  dmi.board.vendor: Quanta
  dmi.board.version: 79.27
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.42:bd12/27/2007:svnHewlett-Packard:pnHPPaviliondv9700NotebookPC:pvrRev1:rvnQuanta:rn30CB:rvr79.27:cvnQuanta:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: HP Pavilion dv9700 Notebook PC
  dmi.product.sku: KL024EA#UUZ
  dmi.product.version: Rev 1
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Fri Jul 26 13:44:32 2019

To manage notifications about this bug go to:

[Touch-packages] [Bug 1758449] Re: skype snap does not work when home directory is not located in /home

2018-03-24 Thread Georges
I did the HOMEDIRS thing, still not working

$ cat /etc/apparmor.d/tunables/home.d/my-homes 
# set to parent directory of your user's directories. Eg, if user's dir is 
/foo/bar/USER,
# set this to /foo/bar/
@{HOMEDIRS}+=/data/home/

$ sudo service apparmor reload
$ skype
2018/03/24 14:01:56.276095 cmd_run.go:343: WARNING: XAUTHORITY environment 
value is not a clean path: "/data/home/georges/.Xauthority"
cannot create user data directory: /data/home/georges/snap/skype/23: Permission 
denied

$ sudo tail -2 /var/log/syslog
Mar 24 14:00:13 breeze anacron[30046]: Normal exit (0 jobs run)
Mar 24 14:01:56 breeze kernel: [6636053.148494] audit: type=1400 
audit(1521896516.286:6903): apparmor="DENIED" operation="open" 
profile="/snap/core/4206/usr/lib/snapd/snap-confine" name="/data/" pid=30123 
comm="snap-confine" requested_mask="r" denied_mask="r" fsuid=1001 ouid=0


I would like to add /data/home to 
/etc/apparmor.d/snap.core.4206.usr.lib.snapd.snap-confine but it's 
uncomprehensible to me.

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

Title:
  skype snap does not work when home directory is not located in /home

Status in apparmor package in Ubuntu:
  New

Bug description:
  Hi

  similar to this bug around libreoffice
  (https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1751005),
  apparmor makes the skype snap not work without any information except
  this:

  cannot create user data directory: /data/home/georges/snap/skype/23:
  Permission denied

  despite the directory being writeable.

  It would really be advisable to make apparmor specific errors, else
  end-users will never determine where the error comes from.

  The error is here:
  Mar 23 22:35:08 breeze kernel: [6580445.024083] audit: type=1400 
audit(1521840908.018:6807): apparmor="DENIED" operation="open" 
profile="/snap/core/4206/usr/lib/snapd/snap-confine" name="/data/" pid=7213 
comm="snap-confine" requested_mask="r" denied_mask="r" fsuid=1001 ouid=0

  I tried to remove the problem like this:
  sudo apparmor_parser -R 
/etc/apparmor.d/snap.core.4206.usr.lib.snapd.snap-confine 

  Which gives a new issue
  $ skype
  snap-confine has elevated permissions and is not confined but should be. 
Refusing to continue to avoid permission escalation attacks

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: apparmor 2.11.0-2ubuntu17
  ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar 23 22:38:16 2018
  InstallationDate: Installed on 2017-09-20 (184 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.10.0-42-generic.efi.signed 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: apparmor
  UpgradeStatus: Upgraded to artful on 2018-01-31 (50 days ago)

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

-- 
Mailing list: https://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 1758449] [NEW] skype snap does not work when home directory is not located in /home

2018-03-23 Thread Georges
Public bug reported:

Hi

similar to this bug around libreoffice
(https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1751005),
apparmor makes the skype snap not work without any information except
this:

cannot create user data directory: /data/home/georges/snap/skype/23:
Permission denied

despite the directory being writeable.

It would really be advisable to make apparmor specific errors, else end-
users will never determine where the error comes from.

The error is here:
Mar 23 22:35:08 breeze kernel: [6580445.024083] audit: type=1400 
audit(1521840908.018:6807): apparmor="DENIED" operation="open" 
profile="/snap/core/4206/usr/lib/snapd/snap-confine" name="/data/" pid=7213 
comm="snap-confine" requested_mask="r" denied_mask="r" fsuid=1001 ouid=0

I tried to remove the problem like this:
sudo apparmor_parser -R 
/etc/apparmor.d/snap.core.4206.usr.lib.snapd.snap-confine 

Which gives a new issue
$ skype
snap-confine has elevated permissions and is not confined but should be. 
Refusing to continue to avoid permission escalation attacks

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: apparmor 2.11.0-2ubuntu17
ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17
Uname: Linux 4.10.0-42-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: XFCE
Date: Fri Mar 23 22:38:16 2018
InstallationDate: Installed on 2017-09-20 (184 days ago)
InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
JournalErrors:
 Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
   Users in the 'systemd-journal' group can see all messages. Pass -q to
   turn off this notice.
 No journal files were opened due to insufficient permissions.
ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.10.0-42-generic.efi.signed 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: apparmor
UpgradeStatus: Upgraded to artful on 2018-01-31 (50 days ago)

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


** Tags: amd64 apport-bug artful

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

Title:
  skype snap does not work when home directory is not located in /home

Status in apparmor package in Ubuntu:
  New

Bug description:
  Hi

  similar to this bug around libreoffice
  (https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1751005),
  apparmor makes the skype snap not work without any information except
  this:

  cannot create user data directory: /data/home/georges/snap/skype/23:
  Permission denied

  despite the directory being writeable.

  It would really be advisable to make apparmor specific errors, else
  end-users will never determine where the error comes from.

  The error is here:
  Mar 23 22:35:08 breeze kernel: [6580445.024083] audit: type=1400 
audit(1521840908.018:6807): apparmor="DENIED" operation="open" 
profile="/snap/core/4206/usr/lib/snapd/snap-confine" name="/data/" pid=7213 
comm="snap-confine" requested_mask="r" denied_mask="r" fsuid=1001 ouid=0

  I tried to remove the problem like this:
  sudo apparmor_parser -R 
/etc/apparmor.d/snap.core.4206.usr.lib.snapd.snap-confine 

  Which gives a new issue
  $ skype
  snap-confine has elevated permissions and is not confined but should be. 
Refusing to continue to avoid permission escalation attacks

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: apparmor 2.11.0-2ubuntu17
  ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar 23 22:38:16 2018
  InstallationDate: Installed on 2017-09-20 (184 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.10.0-42-generic.efi.signed 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: apparmor
  UpgradeStatus: Upgraded to artful on 2018-01-31 (50 days ago)

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

-- 
Mailing list: https://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 1500242] Re: Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected with BQ Aquaris 4.5

2016-09-30 Thread Georges Thill
Meizu MX4, OTA-13
Seat Altea car, model 2009

No success to connect. At first the phone shows connected, but no
feedback is shown on the car side. Then, after a while the phone says it
is disconnected. Pretty much the same (mis-) behaviour in every OTA
since the very beginning when I bought the MX4.

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

Title:
  Bluetooth devices (Jabra BT250, Audi A3 car kit) can not be connected
  with BQ Aquaris 4.5

Status in Canonical System Image:
  In Progress
Status in bluez package in Ubuntu:
  Confirmed
Status in ofono package in Ubuntu:
  Incomplete

Bug description:
  STEPS:
  Requirements: Aquaris E4.5, Jabra BT250 blue tooth handset device (rather old 
one supports blue tooth 1.1 and therefore I thought should be no issue) or Audi 
car kit (A3 2012 model)

  1. Put Jabra BT250 into receiving mode
  2. Phone searches automatically every 15 - 30 seconds for a new blue tooth 
device
  3. Phone finds Jabra BT250 and asks for pairing code
  4. Enter code into phone
  5. Jabra BT250 automatically exits the pairing mode (which is a sign that 
pairing should have worked)
  6. Phone looses connection to Jabra BT250
  7. Manual reconnection via phone works (shows Jabra BT250 as being connected) 
but ignores the device

  Same behaviour with Audi car kit (Audi A3, 2012 model)

  EXPECTED:
  I expect that the blue tooth kits work similar to my Seat Alhambra (also 2012 
model) where the blue tooth pairing etc. works great (except some bugs which 
are already filed).

  ACTUAL:
  No connection to the blue tooth device

  VERSIONS:
  OS-Build-Number: 25
  Ubuntu-Image: 20150825.1

  POSSIBLE ROOT CAUSE:
  Is this issue also solved as soon as bluez5 is implemented? When will this be?

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

-- 
Mailing list: https://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 1398595] Re: Working printer device communication error (5012)

2015-12-10 Thread Jules Rene-Georges Ferdinand Bertholet
** Changed in: cups (Ubuntu)
   Status: Expired => Confirmed

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

Title:
  Working printer device communication error (5012)

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  My Deskjet 1000 series printer doesn't print now. It used to, but HPLIP 
confirms  a device communication error (5012). I'm using Ubuntu 14.4 LTS 
(upgrade) with AMD 64bit archetecture. It worked well up until about 2 weeks 
ago. I printed one page perfectly, but the second page failed. I then bought 
the newest model of same printer (HP 1010) thinking that the device was the 
problem. Same error.
  Any help would surely be appreciated here. 

  Thanks in advance,
  David Sprung

  P.S. I've tried deleting HPLIP and trying it without: failed.
  Installed newest HPLIP: failed. Help! I'm beginning to think it's a
  software issue, as my Dad's printer (HP) failed on his machine about
  the same time

  
  --- 
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CupsErrorLog:
   E [03/Dec/2014:17:50:54 -0500] Unknown directive BrowseAddress on line 8 of 
/etc/cups/cupsd.conf.
   E [03/Dec/2014:17:50:54 -0500] Unknown directive JobPrivateAccess on line 85 
of /etc/cups/cupsd.conf.
   E [03/Dec/2014:17:50:54 -0500] Unknown directive JobPrivateValues on line 86 
of /etc/cups/cupsd.conf.
   E [03/Dec/2014:17:50:54 -0500] Unknown directive SubscriptionPrivateAccess 
on line 87 of /etc/cups/cupsd.conf.
   E [03/Dec/2014:17:50:54 -0500] Unknown directive SubscriptionPrivateValues 
on line 88 of /etc/cups/cupsd.conf.
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  InstallationDate: Installed on 2013-09-20 (439 days ago)
  InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820.1)
  Lpstat: device for Deskjet_1000_J110: 
hp:/usb/Deskjet_1000_J110_series?serial=CN0BP22MYZ05D2
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  Package: cups 1.7.2-0ubuntu1.2
  PackageArchitecture: amd64
  Papersize: letter
  PpdFiles: Deskjet_1000_J110: HP Deskjet 1000 j110 Series, hpcups 3.14.3
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-generic 
root=UUID=d3e197fa-9ef8-4603-8f5e-88976258e568 ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-40-generic 
root=UUID=d3e197fa-9ef8-4603-8f5e-88976258e568 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10
  Tags:  trusty apparmor apparmor apparmor apparmor apparmor apparmor apparmor 
apparmor apparmor apparmor
  Uname: Linux 3.13.0-40-generic x86_64
  UpgradeStatus: Upgraded to trusty on 2014-09-01 (93 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/09/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A55M-HD2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd04/09/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A55M-HD2:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.cups.cupsd.conf: [inaccessible: [Errno 13] Permission 
denied: u'/etc/cups/cupsd.conf']

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

-- 
Mailing list: https://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 1476833] [NEW] wrong contact name is displayed for phone number

2015-07-21 Thread Georges Thill
Public bug reported:

In my address book I have two contacts with very similar numbers. (last
6 digits changed in the example)

Person A:  +352 661 123456
Person B:  +352 691 123456

When I receive a call or try to compose a message to Person B, the phone
always displays the name of Person A. The same happens in call records.

The only way to have the name of Person B displayed upon calls or
message sending is to delete Person A from the address book.

This is very strange, because phone numbers are prefix codes, thus
ignoring a leading digit in a phone number seems like the wrongest thing
to do in this context.

The bug is still present in the current MX4 image (revision 3)

** Affects: address-book-app (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  wrong contact name is displayed for phone number

Status in address-book-app package in Ubuntu:
  New

Bug description:
  In my address book I have two contacts with very similar numbers.
  (last 6 digits changed in the example)

  Person A:  +352 661 123456
  Person B:  +352 691 123456

  When I receive a call or try to compose a message to Person B, the
  phone always displays the name of Person A. The same happens in call
  records.

  The only way to have the name of Person B displayed upon calls or
  message sending is to delete Person A from the address book.

  This is very strange, because phone numbers are prefix codes, thus
  ignoring a leading digit in a phone number seems like the wrongest
  thing to do in this context.

  The bug is still present in the current MX4 image (revision 3)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/address-book-app/+bug/1476833/+subscriptions

-- 
Mailing list: https://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 1436039] Re: List of desktop environmets spills off bottom of screen when it is too long - Cannot scroll through list

2015-03-24 Thread Jules Rene-Georges Ferdinand Bertholet
** Package changed: ubuntu = lightdm (Ubuntu)

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

Title:
  List of desktop environmets spills off bottom of screen when it is too
  long - Cannot scroll through list

Status in lightdm package in Ubuntu:
  New

Bug description:
  At the logon screenwhen I boot Ubuntu (Trusty Tahr, 14.04.2 LTS), I am
  able to choose from multiple desktop environments by clicking the
  button to the right of the user name. I have many desktop environments
  installed, though, so this list is so long tha it spills off the
  bottom edge of the screen. The absence of a scrollbar, mouse-wheel
  support, or the ability to browe the list using arrow keys makes it so
  that the desktop environments near the bottom of the list cannot be
  accessed.

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

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