[Touch-packages] [Bug 1511735] Re: libnl: fail to bind() netlink sockets

2016-05-13 Thread Dario Bertini
There's a new bug, I guess that pitti might pay more attention to this
over there, since this old one is now considered fixed (incorrently, but
alas)

https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1581535

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

Title:
  libnl: fail to bind() netlink sockets

Status in libnl3 package in Ubuntu:
  Fix Released
Status in libnl3 source package in Trusty:
  Fix Released
Status in libnl3 package in Debian:
  Fix Released

Bug description:
  [Triage Notes]

  The proposed fix for this bug in libnl3 caused a regression in trusty-
  proposed, tracked in bug 1539634. The regression is caused by a latent
  bug in Network Manager. We expect to fix this by landing a fix for the
  bug in Network Manager in trusty-updates at the same time as this fix.

  [Impact]

   * Applications in Trusty using libnl-3-200 which frequently open and
     close netlink sockets can easily fail when attempting to bind the
     local socket.  The problem happens when libnl choose a port id
     already used by another application and subsequently libnl fails
     instead of trying another port id.

     The original bug was discovered when attempting to start a virtual
     machine under libvirt, which is a user of this library.

   * Backporting fixes from upstream release fixes a real bug in the
     current version of the library in Trusty.  The alternative is for all
     applications to manually manage their local port allocation, or as
     upstream has accepted allowing libnl to attempt to try for other
     local ports.

   * All patches applied are already accepted upstream and newer Ubuntu
     releases are not affected.

  [Test Case]

   * On a Trusty 14.04 system
     1. sudo apt-get install libnl-3-200 libnl-3-dev libnl-3-dev \
     libnl-genl-3-dev libnl-route-3-200 \
     make gcc build-essential libnl1
     2. download and unpack attachment: lp_1511735_test.tar
     3. Run testcases:

  % if ./example.sh; then echo "libnl OK"; else echo "libnl FAILED"; fi
  gcc -o example -I/usr/include/libnl3 example.c -lnl-3 -lnl-genl-3
  set manually the local port to 6975 (pid: 6974)
  local port has been set by the libnl to 6975 (pid: 6975)
  ERROR: genl_connect(): Object exists (local port: 6975, pid: 6975)
  libnl FAILED
  % python libnl3-test-rh1249158.py a b c d
  ulimit(NOFILE) = (2048, 4096)
  Test: PID=6978
  TEST (a)...
  Traceback (most recent call last):
    File "libnl3-test-rh1249158.py", line 226, in 
  locals()["TEST_" + arg]()
    File "libnl3-test-rh1249158.py", line 140, in TEST_a
  sk = nl_get_socket()
    File "libnl3-test-rh1249158.py", line 115, in nl_get_socket
  raise IOError(-err, _nl_geterror())
  OSError: [Errno 6] b'Unspecific failure'

     4. After applying the updated packages:

  % if ./example.sh; then echo "libnl OK"; else echo "libnl FAILED"; fi
  gcc -o example -I/usr/include/libnl3 example.c -lnl-3 -lnl-genl-3
  set manually the local port to 11295 (pid: 11294)
  local port has been set by the libnl to 2894081055 (pid: 11295)
  libnl OK
  % python libnl3-test-rh1249158.py a b c d
  ulimit(NOFILE) = (2048, 4096)
  Test: PID=11296
  TEST (a)...
  ...done
  TEST (b)...
  ...done
  TEST (c)...
  ...done
  TEST (d)...
  ...done

  [Regression Potential]

   * There are quite a few high profile packages that depend on this package,
     notably libvirt and network-manager.  The complete list is here:

     # on Trusty
  % apt-rdepends -r libnl-3-200 | head -n 33
  libnl-3-200
    Reverse Depends: batctl (>= 2013.4.0-2)
    Reverse Depends: bmon (>= 1:3.1-1)
    Reverse Depends: crda (>= 1.1.2-1ubuntu2)
    Reverse Depends: hostapd (>= 1:2.1-0ubuntu1)
    Reverse Depends: ipvsadm (>= 1:1.26-2ubuntu1)
    Reverse Depends: iw (>= 3.4-1)
    Reverse Depends: keepalived (>= 1:1.2.7-1ubuntu1)
    Reverse Depends: kismet (>= 2013.03.R1b-3)
    Reverse Depends: knemo (>= 0.7.6-2)
    Reverse Depends: libfsobasics3 (>= 0.12.0-4)
    Reverse Depends: libnetcf1 (>= 1:0.2.3-4ubuntu1)
    Reverse Depends: libnl-3-200-dbg (= 3.2.21-1)
    Reverse Depends: libnl-3-dev (= 3.2.21-1)
    Reverse Depends: libnl-cli-3-200 (= 3.2.21-1)
    Reverse Depends: libnl-genl-3-200 (= 3.2.21-1)
    Reverse Depends: libnl-nf-3-200 (= 3.2.21-1)
    Reverse Depends: libnl-route-3-200 (= 3.2.21-1)
    Reverse Depends: libnl-utils (>= 3.2.21-1)
    Reverse Depends: libnss-gw-name (>= 0.3-2)
    Reverse Depends: libvirt-bin (>= 1.2.2-0ubuntu13)
    Reverse Depends: libvirt0 (>= 1.2.2-0ubuntu13)
    Reverse Depends: lowpan-test-tools (>= 0.3-1)
    Reverse Depends: 

[Touch-packages] [Bug 1581535] Re: libnl upgrade breaks Network Manager

2016-05-13 Thread Dario Bertini
A colleague of mine has been affected by this as well, there are new
threads popping up in askubuntu.com

http://askubuntu.com/questions/771627/14-04-network-manager-stopped-
working

and newly affected people are popping up in the old bug:

https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1511735

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

Title:
  libnl upgrade breaks Network Manager

Status in libnl3 package in Ubuntu:
  Confirmed

Bug description:
  I appear to have been hit by a regression problem in the libnl update
  described here:

  https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1511735

  After running a regular software update this morning and rebooting,
  I've completely lost networking access. Network Manager is down. I'm
  running Trusty 14.04. I tried this workaround:

  http://askubuntu.com/questions/727127/last-upgrade-crashes-network-
  manager-no-internet-connection-no-applet

  ... and step 1 didn't work. I'll be trying step 2 tonight when I've
  got more time.

  I'm filing this as a new bug with a regression-update, as indicated in
  the above-linked bug report.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1581535/+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 1401322] Re: Upgrade to Python 2.7.9

2016-01-27 Thread Dario Bertini
For the people annoyed at the idea to move to 16.04:

There are some alternative ways to get an updated Python version,
without relying on the one shipped by default in Ubuntu:

Pythonz: https://github.com/saghul/pythonz (disclaimer: I submitted some 
patches and integrated pythonz into my own project: 
https://github.com/berdario/pew )
Pyenv: https://github.com/yyuu/pyenv
The deadsnakes ppa: 
https://launchpad.net/~fkrull/+archive/ubuntu/deadsnakes-python2.7?field.series_filter=precise
 (this is not the main PPA, but it's the one created specially for this purpose)

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

Title:
  Upgrade to Python 2.7.9

Status in python-defaults package in Ubuntu:
  Fix Released

Bug description:
  Python 2.7.9 contains numerous security improvements for Python.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1401322/+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 1387908] Re: [udev] FIDO u2f security keys should be supported out of the box

2016-01-02 Thread Dario Bertini
This still affects Wily.

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

Title:
  [udev] FIDO u2f security keys should be supported out of the box

Status in systemd package in Ubuntu:
  Incomplete
Status in systemd source package in Trusty:
  Confirmed
Status in systemd source package in Utopic:
  Confirmed
Status in systemd source package in Vivid:
  Confirmed

Bug description:
  FIDO u2f is an emerging standard for public-private cryptography based
  2nd factor authentication, which improves on OTP by mitigating
  phishing, man-in-the-middle attacks and reply attacks.

  Google Chrome supports u2f devices which are now widely available from
  Yubico (new premium neo Yubikeys and Security keys).

  However, udev rules are required to setup permissions to allow the
  web-browsers which are running as regular users to access the devices
  in question.

  E.g.:

  KERNEL=="hidraw*", SUBSYSTEM=="hidraw", MODE="0664", GROUP="plugdev",
  ATTRS{idVendor}=="1050", ATTRS{idProduct}=="0113|0114|0115|0116|0120"

  Something like that should be enabled by default, however probably not
  encode on the vendor/productid as other vendors will also make u2f
  devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1387908/+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 1290847] Re: pyvenv fails due to mising ensurepip module

2015-09-14 Thread Dario Bertini
PS: the bug I found is not truly a bug, just a difference in behaviour
between venv and virtualenv:

the former won't allow you to locally install packages when created with
--system-site-packages (making that flag effectively useless, imho),
while virtualenv will allow you to layer local packages upon the
globally installed ones

** Bug watch added: Python Roundup #24875
   http://bugs.python.org/issue24875

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

Title:
  pyvenv fails due to mising ensurepip module

Status in python3-defaults package in Ubuntu:
  Fix Released
Status in python3.4 package in Ubuntu:
  Fix Released
Status in python3.4 package in Debian:
  Fix Released

Bug description:
  Hello,

  I noticed the following

  # fails
  python3.4 -m venv --clear python-venv
  Error: Command '['.../external/python-venv/bin/python3.4', '-Im', 
'ensurepip', '--upgrade', '--default-pip']' returned non-zero exit status 1

  # works, but no pip
  python3.4 -m venv --clear --without-pip python-venv

  Thank you

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1290847/+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 1290847] Re: pyvenv fails due to mising ensurepip module

2015-09-14 Thread Dario Bertini
@rspeer @wolfgang-richter

The bug is "sort of fixed"

You have to install python3-venv, this will make the ensurepip module
available, and the creation of a virtualenv will succeed

Imho this is an horrible naming choice: the error you'll get when trying
to run `python3 -m venv` mentions ensurepip, and most ubuntu/debian
users might have heard about the fact that ensurepip is disabled in the
distro

then, `apt list ensurepip` or `apt search ensurepip` won't yield any
useful results (just like I tried to do, before being puzzled about the
"fix released" status of this bug)

moreover, `--without-pip` will just work even without the new package,
making the name "python3-venv" even more misleading

Still, I'd caution you AGAINST using venv... I just found another
trivial bug. You're better off using virtualenv, given how it's battle
tested

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

Title:
  pyvenv fails due to mising ensurepip module

Status in python3-defaults package in Ubuntu:
  Fix Released
Status in python3.4 package in Ubuntu:
  Fix Released
Status in python3.4 package in Debian:
  Fix Released

Bug description:
  Hello,

  I noticed the following

  # fails
  python3.4 -m venv --clear python-venv
  Error: Command '['.../external/python-venv/bin/python3.4', '-Im', 
'ensurepip', '--upgrade', '--default-pip']' returned non-zero exit status 1

  # works, but no pip
  python3.4 -m venv --clear --without-pip python-venv

  Thank you

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1290847/+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 1290847] Re: pyvenv fails due to mising ensurepip module

2015-09-14 Thread Dario Bertini
This is it: https://bugs.python.org/issue24875

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

Title:
  pyvenv fails due to mising ensurepip module

Status in python3-defaults package in Ubuntu:
  Fix Released
Status in python3.4 package in Ubuntu:
  Fix Released
Status in python3.4 package in Debian:
  Fix Released

Bug description:
  Hello,

  I noticed the following

  # fails
  python3.4 -m venv --clear python-venv
  Error: Command '['.../external/python-venv/bin/python3.4', '-Im', 
'ensurepip', '--upgrade', '--default-pip']' returned non-zero exit status 1

  # works, but no pip
  python3.4 -m venv --clear --without-pip python-venv

  Thank you

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1290847/+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 1435108] [NEW] Volume hotkeys stop working (dozens of seconds of delay)

2015-03-22 Thread Dario Bertini
Public bug reported:

This seems to be a similar problem to the one described here:
http://ubuntuforums.org/showthread.php?t=1829744

With recent Ubuntu versions, though, gnome-settings-daemon is not there
anymore. I tried to kill unity-settings-daemon as a workaround, but it
doesn't work.

I followed the instructions here:

https://wiki.ubuntu.com/Hotkeys/Troubleshooting

and I can correctly see the keypresses be received correctly both with
xev and with evtest

with the latter, I can see that the interesting hotkeys codes:

Event: time 1427077143.513820, -- SYN_REPORT 
Event: time 1427077143.616493, type 4 (EV_MSC), code 4 (MSC_SCAN), value ae
Event: time 1427077143.616493, type 1 (EV_KEY), code 114 (KEY_VOLUMEDOWN), 
value 0
Event: time 1427077143.616493, -- SYN_REPORT 
Event: time 1427077144.292461, type 4 (EV_MSC), code 4 (MSC_SCAN), value b0
Event: time 1427077144.292461, type 1 (EV_KEY), code 115 (KEY_VOLUMEUP), value 1

And the events can be seen even when the volume hotkeys are unresponsive
(the volume is not updated).

This seems to happen more often (or at least it's more noticeable to me)
when watching something in fullscreen.

Keypresses usually aren't lost, but are simply delayed and buffered, and
thus if I press the button 5/10 times, after half a minute of so, all
the keypresses will trigger the corresponding action all together

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: udev 208-8ubuntu8.2
ProcVersionSignature: Ubuntu 3.16.0-31.43-generic 3.16.7-ckt5
Uname: Linux 3.16.0-31-generic x86_64
ApportVersion: 2.14.7-0ubuntu8.2
Architecture: amd64
CurrentDesktop: Unity
CustomUdevRuleFiles: 80-docker.rules
Date: Mon Mar 23 02:07:48 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-08-17 (217 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2)
MachineType: LENOVO 20AQCTO1WW
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic.efi.signed 
root=UUID=259bbe5f-d5f2-42de-89f9-58a9d77e4a21 ro quiet splash vt.handoff=7
SourcePackage: systemd
UpgradeStatus: Upgraded to utopic on 2014-10-16 (157 days ago)
dmi.bios.date: 05/20/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: GJET77WW (2.27 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20AQCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50512 STD
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrGJET77WW(2.27):bd05/20/2014:svnLENOVO:pn20AQCTO1WW:pvrThinkPadT440s:rvnLENOVO:rn20AQCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 20AQCTO1WW
dmi.product.version: ThinkPad T440s
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug utopic

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

Title:
  Volume hotkeys stop working (dozens of seconds of delay)

Status in systemd package in Ubuntu:
  New

Bug description:
  This seems to be a similar problem to the one described here:
  http://ubuntuforums.org/showthread.php?t=1829744

  With recent Ubuntu versions, though, gnome-settings-daemon is not
  there anymore. I tried to kill unity-settings-daemon as a workaround,
  but it doesn't work.

  I followed the instructions here:

  https://wiki.ubuntu.com/Hotkeys/Troubleshooting

  and I can correctly see the keypresses be received correctly both with
  xev and with evtest

  with the latter, I can see that the interesting hotkeys codes:

  Event: time 1427077143.513820, -- SYN_REPORT 
  Event: time 1427077143.616493, type 4 (EV_MSC), code 4 (MSC_SCAN), value ae
  Event: time 1427077143.616493, type 1 (EV_KEY), code 114 (KEY_VOLUMEDOWN), 
value 0
  Event: time 1427077143.616493, -- SYN_REPORT 
  Event: time 1427077144.292461, type 4 (EV_MSC), code 4 (MSC_SCAN), value b0
  Event: time 1427077144.292461, type 1 (EV_KEY), code 115 (KEY_VOLUMEUP), 
value 1

  And the events can be seen even when the volume hotkeys are
  unresponsive (the volume is not updated).

  This seems to happen more often (or at least it's more noticeable to
  me) when watching something in fullscreen.

  Keypresses usually aren't lost, but are simply delayed and buffered,
  and thus if I press the button 5/10 times, after half a minute of so,
  all the keypresses will trigger the corresponding action all together

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: udev 208-8ubuntu8.2
  ProcVersionSignature: Ubuntu 3.16.0-31.43-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: Unity
  CustomUdevRuleFiles: 80-docker.rules
  Date: Mon Mar 23 02:07:48 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed 

[Touch-packages] [Bug 1309806] Re: Unity Broken Today - No Panels or Launcher After Logon

2014-11-05 Thread Dario Bertini
Maybe this could be bug #1166765 ?
If it happens again, try to run `gsettings get 
org.compiz.core:/org/compiz/profiles/unity/plugins/core/ active-plugins` on a 
terminal, if 'opengl' and 'unityshell' are missing it's probably 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/1309806

Title:
  Unity Broken Today - No Panels or Launcher After Logon

Status in Unity:
  New
Status in “unity” package in Ubuntu:
  New

Bug description:
  I installed the Ubuntu 14.04 64bit desktop on this ASUS F75A a few
  weeks ago while it was still in beta.

  Today, upon logging into this machine, the Unity Dekstop was missing
  the top-panel and the launcher. I had to then press the power button
  for 5 seconds to turn off this laptop because crtl-alt-t would not
  bring up a terminal.

  In order to submit this bug, I've had to boot from the recently
  released live DVD.

  I reinstalled Ubuntu 14.04 again today, onto this machine, but it
  didn't fix the problem; as soon as I logged in for the first time
  there was no panels or launchers.

  Ironically, when booting from the Live DVD, the launchers and panels
  show up fine.

  The laptop ran great for weeks on the 14.04 beta, but now a fresh
  install produces a corrupted Unity Dekstop.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140416-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CasperVersion: 1.340
  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 Apr 19 00:03:37 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:14c7]
  LiveMediaBuild: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: ASUSTeK COMPUTER INC. X75A
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash --
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/22/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X75A.415
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X75A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX75A.415:bd05/22/2013:svnASUSTeKCOMPUTERINC.:pnX75A:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX75A:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X75A
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  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
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Sat Apr 19 00:01:20 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   12623 
   vendor SEC
  xserver.version: 2:1.15.1-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1309806/+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 1210842] Re: Unity does not show launcher or status bar

2014-11-05 Thread Dario Bertini
Maybe this could be bug #1166765 ?
If it happens again, try to run `gsettings get 
org.compiz.core:/org/compiz/profiles/unity/plugins/core/ active-plugins` on a 
terminal, if 'opengl' and 'unityshell' are missing it's probably 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/1210842

Title:
  Unity does not show launcher or status bar

Status in Unity:
  New
Status in “unity” package in Ubuntu:
  New

Bug description:
  When logining in to the computer ubuntu fails to start unity. allows
  you to open the terminal though

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: unity 5.20.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.5.0-37.58~precise1-generic 3.5.7.16
  Uname: Linux 3.5.0-37-generic i686
  ApportVersion: 2.0.1-0ubuntu17.4
  Architecture: i386
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,workarounds,scale,expo,ezoom]
  Date: Sat Aug 10 13:50:45 2013
  InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release i386 
(20130213)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1210842/+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