date:20160118

[Touch-packages] [Bug 1533839] Re: vms shutting down on libvirt upgrade

2016-01-18 Thread Martin Pitt

** No longer affects: init-system-helpers (Ubuntu)

** No longer affects: init-system-helpers (Ubuntu Wily)

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

Title:
  vms shutting down on libvirt upgrade

Status in libvirt package in Ubuntu:
  Triaged
Status in libvirt source package in Wily:
  New

Bug description:
  Server running ubuntu wily, kvm and a few virtual machines

  Today installed security updates which contained a libvirt update.
  After finishing the updates i found al my virtual machines were
  shutdown. Previous libvirt updates did not shutdown running virtual
  machines.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1533839/+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 1535219] [NEW] HP ZBook 15u mic mute button doesn't work

2016-01-18 Thread Ippolitov Igor

Public bug reported:

This is mostly similar to this one:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1334968

I have an HP Zbook 15u laptop with a mic mute button at fn+f8. I didn't
work for me with xubuntu LTS 14.04.03

What is wished: keyboard shortcut fn+f8 should produce XF86AudioMicMute X key 
code which mutes microphone.
What is happening: keyboard shotcut has keycode 465 which does nothing, while 
muting microphone through GUI enables led on the keyboard.

How to debug similar issues and fix:
Enable keyboard debug, find your scancode, remap it to f20, restart X.

Now in step by step instruction:
NB: keyboard sends scancodes, kernel makes keycodes from those. Keycodes are 
remapped in X before getting into applications

1) enable keyboard debug to make things easier: edit /etc/default/grub, add the 
following options
GRUB_CMDLINE_LINUX="atkbd.softraw=0", Reboot to enable this.
2) install "evtest" utility
3) using "evtest" find your keyboard (was /dev/input/event3 for me)
4) look for the key down and key up scancodes for fn+f8 button. Fixed version 
looks like this:
Event: time 1453101052.604985, -- SYN_REPORT 
Event: time 1453101053.883744, type 4 (EV_MSC), code 3 (MSC_RAW), value e0
Event: time 1453101053.883744, type 4 (EV_MSC), code 3 (MSC_RAW), value 01
Event: time 1453101053.883744, type 4 (EV_MSC), code 4 (MSC_SCAN), value 81
Event: time 1453101053.883744, type 1 (EV_KEY), code 190 (KEY_F20), value 1
Event: time 1453101053.883744, -- SYN_REPORT 
Event: time 1453101053.955411, type 4 (EV_MSC), code 3 (MSC_RAW), value e0
Event: time 1453101053.955411, type 4 (EV_MSC), code 3 (MSC_RAW), value 81
Event: time 1453101053.955411, type 4 (EV_MSC), code 4 (MSC_SCAN), value 81
Event: time 1453101053.955411, type 1 (EV_KEY), code 190 (KEY_F20), value 0

the "code 190 (KEY_F20)" will be different for you.

5) using "eventX" from the above, find corresponding device using "find /sys/ 
-name event3". 
6) find out udev modalias for your keyboard: "udevadm --debug test 
/devices/platform/i8042/serio0/input/input3/event3 2>&1 | grep dmi/id", The 
long path is from p.5 'find' output
7) create and change /etc/udev/hwdb.d/60-hp-mic-mute-hotkey.hwdb file. Add 
following lines there:
keyboard:dmi:bvnHewlett-Packard:bvrM71Ver.01.07:bd07/28/2015:svnHewlett-Packard:pnHPZBook15uG2:pvrA3009D510303:rvnHewlett-Packard:rn2216:rvrKBCVersion96.55:cvnHewlett-Packard:ct10:cvr:
 KEYBOARD_KEY_81=f20
The long identifier is from udevadm point 6 output.  "81" is the scan code. f20 
- is an alias for the keycode we wish to have (can be replaced with '190' 
keycode itself)
8) udevadm hwdb --update; udevadm trigger /dev/input/event3
9) test with evtest that you have appropriate keycode for the button. To make 
it work in X11 you have to restart X (or reboot, don't know for sure)
10) test with xev after reboot: fn+f8 should work as intended this time. 
(xmodmap maps f20 to XF86AudioMicMute). 
11) for xfce4 you might need to map XF86AudioMicMute to a pactl action, but 
this is xfce specific.

For the maintainers:
Mose of HPProBooks, EliteBooks, ZBooks has the same issue. Could anyone contact 
HP and request some help with all those keyboards?...

Please, add ZBook into keyboard.hwdb file.

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

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

Title:
  HP ZBook 15u mic mute button doesn't work

Status in systemd package in Ubuntu:
  New

Bug description:
  This is mostly similar to this one:
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1334968

  I have an HP Zbook 15u laptop with a mic mute button at fn+f8. I
  didn't work for me with xubuntu LTS 14.04.03

  What is wished: keyboard shortcut fn+f8 should produce XF86AudioMicMute X key 
code which mutes microphone.
  What is happening: keyboard shotcut has keycode 465 which does nothing, while 
muting microphone through GUI enables led on the keyboard.

  How to debug similar issues and fix:
  Enable keyboard debug, find your scancode, remap it to f20, restart X.

  Now in step by step instruction:
  NB: keyboard sends scancodes, kernel makes keycodes from those. Keycodes are 
remapped in X before getting into applications

  1) enable keyboard debug to make things easier: edit /etc/default/grub, add 
the following options
  GRUB_CMDLINE_LINUX="atkbd.softraw=0", Reboot to enable this.
  2) install "evtest" utility
  3) using "evtest" find your keyboard (was /dev/input/event3 for me)
  4) look for the key down and key up scancodes for fn+f8 button. Fixed version 
looks like this:
  Event: time 1453101052.604985, -- SYN_REPORT 
  Event: time 1453101053.883744, type 4 (EV_MSC), code 3 (MSC_RAW), value e0
  Event: time 1453101053.883744, type 4 (EV_MSC), code 3 (MSC_RAW), value 01
  Event: time

[Touch-packages] [Bug 1535335] [NEW] Change prompt "wants to record audio" to "wants to access microphone"

2016-01-18 Thread Jean-Baptiste Lallement

Public bug reported:

The prompt when the camera wants to access the hardware to record audio
is currently "wants to record audio". This is not really accurate since
an app can request access to the microphone without actually recording
anything. furthermore the direct translation to French as an example is
not really meaningful.

Something like "wants to access the microphone." would be more accurate
since it's actually what the application tries to do.

** Affects: canonical-devices-system-image
 Importance: Undecided
 Status: New

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

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

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

Title:
  Change prompt "wants to record audio" to "wants to access microphone"

Status in Canonical System Image:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  The prompt when the camera wants to access the hardware to record
  audio is currently "wants to record audio". This is not really
  accurate since an app can request access to the microphone without
  actually recording anything. furthermore the direct translation to
  French as an example is not really meaningful.

  Something like "wants to access the microphone." would be more
  accurate since it's actually what the application tries to do.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1535335/+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 1430479] Re: "telinit u" under upstart (upstart's Restart command) with systemd-sysv installed runs systemd

2016-01-18 Thread Martin Pitt

** Bug watch added: Debian Bug tracker #789524
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789524

** Also affects: upstart (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789524
   Importance: Unknown
   Status: Unknown

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

Title:
  "telinit u" under upstart (upstart's Restart command) with systemd-
  sysv installed runs systemd

Status in systemd package in Ubuntu:
  Fix Released
Status in upstart package in Ubuntu:
  Triaged
Status in upstart package in Debian:
  Unknown

Bug description:
  I've today had two machines kill my X session during dist-upgrade, and
  it happened during libc6 postinst. Dmesg shows that systemd got
  somehow started during the earlier phase of the upgrade. X logs show a
  failure with "(EE) Cannot establish any listening sockets" etc..

  Adam can fill in the more detailed analysis of what's happening
  there.. but I think it should be fairly easy to reproduce by
  installing vivid from an earlier image and dist-upgrading to current,
  if needed.

  Reproducer:
   - Start with a standard utopic VM (e. g. adt-buildvm-ubuntu-cloud -r utopic)
   - Switch apt sources to vivid
   - sudo apt install systemd-sysv
   - sudo telinit u  # systemd command, forwards to upstart's 
/lib/sysvinit/telinit
   - Or directly: sudo /lib/sysvinit/telinit u

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1430479/+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 1532868] Re: [Avila] OSK generates random touch events after switching from physical keyboard

2016-01-18 Thread Victor Tuson Palau

Sorry I was travelling. This seem to happen with all the apps, including
the shell. I wonder if it is related to
https://bugs.launchpad.net/avila/+bug/1532862 as it only happens after
that bug has triggered. I will do more testing now that I have a bt
keyboard too, to see if I can reproduce with both.

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

Title:
  [Avila] OSK generates random touch events after switching from
  physical keyboard

Status in The Avila project:
  New
Status in canonical-pocket-desktop:
  New
Status in mir package in Ubuntu:
  Opinion
Status in xorg-server package in Ubuntu:
  New

Bug description:
  Steps:
  connect a USB keyboard 
  Use for a bit
  Disconnect keyboard
  try using the onboard keyboard

  Result:
  The keyboard starts producing random touch events as soon as you try to use 
it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/avila/+bug/1532868/+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 1532553] Re: /etc/halt.local has become /usr/sbin/halt.local

2016-01-18 Thread Martin Pitt

http://anonscm.debian.org/cgit/pkg-
systemd/systemd.git/commit/?id=944c47b

** Changed in: systemd (Ubuntu)
   Status: Triaged => Fix Committed

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

Title:
  /etc/halt.local has become /usr/sbin/halt.local

Status in systemd package in Ubuntu:
  Fix Committed

Bug description:
  Ubuntu 15.10, amd64
  systemd-225-1ubuntu9

  /etc/halt.local seems to have moved to /usr/sbin/halt.local which IMO
  is bad for a couple of reasons.

  1) This is not where it's supposed to be
  2) Locally modified (non-dpkg managed) scripts under /usr is bad

  I have not been able to find anywhere documenting this as a decided
  change, so it seems like a bug to me.

  Please let me know if you need more info from me

  /Thomas

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1532553/+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 1535151] Re: black screen with mouse pointer after changing to unity 8 on nVidia GT525M (ubuntu 15.10)

2016-01-18 Thread wegosh

** Changed in: unity8 (Ubuntu)
 Assignee: (unassigned) => wegosh (wegosh16-g)

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

Title:
  black screen with mouse pointer after changing to unity 8 on nVidia
  GT525M (ubuntu 15.10)

Status in unity8 package in Ubuntu:
  New

Bug description:
  I installed unity8 mir with terminal and after all I can see is black
  screen with a mouse pointer. Graphic card I using is nVidia GT 525M
  with the latest drivers. I'm using Ubuntu 15.10. I hope that this will
  be fixed soon.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1535151/+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 1535151] Re: black screen with mouse pointer after changing to ubuntu 8 on nVidia GT525M

2016-01-18 Thread wegosh

@dinamic6661 I upgraded from 15.10 to 16.04, changed my drivers to open
source ones (nouveau ) and now the screen is still black, but there is
no mouse pointer and at the top-left corner there is one underline and
that's all I see. Any suggestions?

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

Title:
  black screen with mouse pointer after changing to ubuntu 8 on nVidia
  GT525M

Status in unity8 package in Ubuntu:
  New

Bug description:
  I installed unity8 mir with terminal and after all I can see is black
  screen with a mouse pointer. Graphic card I using is nVidia GT 525M
  with the latest drivers. I'm using Ubuntu 15.10. I hope that this will
  be fixed soon.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1535151/+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 1440608] Re: /etc/kernel/postinst.d/apt-auto-removal wants to remove all kernels except the latest one

2016-01-18 Thread Robert Euhus

Jarno Suni, thanks for the reply.

First I would like to stress, that I still don't think that running all
the KERNELS postINSTALL hooks while REMOVING the -extra package is the
right thing todo. The only thing I can see that is really needed is the
recreation of the initrd on installation and revmoval of that package
(please correct me if I'm wrong!). So I think this is the only thing
that should be done. Even recreating the GRUB config is unnessecary and
a waste of time.

So working around this in the /etc/kernel/postinst.d/apt-auto-removal
script is imho not the right way to do this.

That being said, this seems like the only available option right now.

I have taken a closer look at your "Fixed again" script and made some
adjustments (comparing with apt 1.0.1ubuntu2.10 from 14.04):
- The version you have uploaded does not run properly, because some
backslash-escapes for line breaks are missing (leading to "broken pipe" error).
- In the check if the kernel given in argument is desired to be removed the
"exit" from the awk statement causes another broken pipe if the match is not
the last kernel. It is not needed, so I removed it.
- The awk regex for creating the "list" of installed kernel versions is wrong (
only ' ' instead of '[ ]+' ), so the list is always empty. I don't see the
advantage of using DPKG_QUERY here compared to the original which just uses
DPKG. So to keep changes minimal I have reverted it to the old version.
- The shortened check if we have more than two kernels to keep already may lead
to keeping one more kernel (3 in total) than in the original, which is fine by
me.
- Again to keep changes (diff) minimal I have reordered the versions for the
"kernel" variable like they are in the original.
- The use of dpkg-query looks somehow awkward to me (but maybe it's just
me).

I'll attach my updated version of the /etc/kernel/postinst.d/apt-auto-
removal script

I have just run a few tests and it seems to work better than the
original for now. I'll do some more testing right now.

Regards,
Robert.

** Attachment added: "updated /etc/kernel/postinst.d/apt-auto-removal script"

https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1440608/+attachment/4551868/+files/apt-auto-removal

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

Title:
/etc/kernel/postinst.d/apt-auto-removal wants to remove all kernels
except the latest one

Status in One Hundred Papercuts:
Triaged
Status in apt package in Ubuntu:
Triaged
Status in linux package in Ubuntu:
Triaged

Bug description:
After installing a 3rd kernel currently 3.19.0-12-generic, the
/etc/apt/apt.conf.d/01autoremove-kernels file looks normal listing the
3.19.0-11-generic and 3.19.0-12-generic with 3.19.0-10-generic listed
to be autoremoved. But once autoremove is completed the machine
requests to be rebooted and at that time the /etc/apt/apt.conf.d
/01autoremove-kernels file lists the 3.19.0-12-generic and
3.19.0-10-generic kernels. So upon rebooting the 3.19.0-11-generic is
requested to be autoremoved leaving only one kernel the latest one
3.19.0-12-generic.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: apt 1.0.9.7ubuntu3
ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
Uname: Linux 3.19.0-12-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.17-0ubuntu1
Architecture: amd64
CurrentDesktop: MATE
Date: Sun Apr 5 17:03:01 2015
InstallationDate: Installed on 2015-04-02 (3 days ago)
InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Beta amd64 (20150401)
SourcePackage: apt
UpgradeStatus: No upgrade log present (probably fresh install)

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

1 2 3 >

1 - 100 of 254 matches

Mail list logo