from:"Mantas Kriaučiūnas"

** Changed in: pepperflashplugin-nonfree (Baltix)
   Status: New = In Progress

** Changed in: pepperflashplugin-nonfree (Baltix)
 Assignee: (unassigned) = Mantas Kriaučiūnas (mantas)

** Changed in: pepperflashplugin-nonfree (Baltix)
   Importance: Undecided = Medium

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1311237

Title:
  Pepper Flash needs backport to 12.04

Status in “chromium-browser” package in Ubuntu:
  Confirmed
Status in “pepperflashplugin-nonfree” package in Ubuntu:
  Confirmed
Status in “pepperflashplugin-nonfree” package in Baltix:
  In Progress

Bug description:
  Now that this package is officially the only way to run flash on
  chromium it should be backported to 12.04, since that release is still
  supported until 26 April 2017. And I suppose 13.10 as well, but that's
  probably less pressing. Debian has released this package for wheezy,
  jessie,  sid, as you can see from the following rmadison output:

  debian:
   pepperflashplugin-nonfree | 1.2~bpo70+1 | wheezy-backports/contrib | source, 
amd64, i386
   pepperflashplugin-nonfree | 1.3 | jessie/contrib   | source, 
amd64, i386
   pepperflashplugin-nonfree | 1.3 | sid/contrib  | source, 
amd64, i386
  ubuntu:
   pepperflashplugin-nonfree | 1.3ubuntu1 | trusty/multiverse | source, amd64, 
i386

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

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

[Desktop-packages] [Bug 1192297] Re: Huawei E3131 mobile modem not recognized

This bug should be fixed in Ubuntu 14.10 (Utopic, see LP bug #1354823),
could you test  modem E3131 (12d1:15ca) on Ubuntu 14.10 or install
backported to Ubuntu 14.04 usb-modeswitch-2.2.0 from ppa:baltix/ppa
(https://launchpad.net/~baltix/+archive/ubuntu/ppa )

xxvirusxx (condor20-05) wrote on 2014-08-10:
 This bug still exist in 14.04.
 This modem E3131 (12d1:15ca) work with Debian usb-modeswitch 2.2.0+repack0-1

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to usb-modeswitch-data in Ubuntu.
https://bugs.launchpad.net/bugs/1192297

Title:
  Huawei E3131 mobile modem not recognized

Status in Usb Modeswitch Data:
  Fix Released
Status in “usb-modeswitch-data” package in Ubuntu:
  Confirmed
Status in “usb-modeswitch-data” package in Baltix:
  Confirmed

Bug description:
  Modem does not work in 12.04. I heard it does work in 12.10.

  It can be made to work in 12.04 by editing 
/lib/udev/rules.d/40-usb_modeswitch.rules
  adding two lines:

  # Huawei E3131
  ATTRS{idVendor}==12d1, ATTRS{idProduct}==151a, RUN+=usb_modeswitch 
'%b/%k'

  and adding file  /etc/usb_modeswitch.d/12d1:151a
  with contents:

  # HUAWEI E3131 (DNA)

  DefaultVendor=0x12d1
  DefaultProduct=0x151a
  TargetVendor=0x12d1
  TargetProduct=0x14ac

  
MessageContent=55534243123456780a11062100

  
  I copied those file contents from this forum message: 
http://forum.ubuntu-fi.org/index.php?topic=44160.0

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: usb-modeswitch-data 20120120-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-48.74-generic 3.2.46
  Uname: Linux 3.2.0-48-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.3
  Architecture: amd64
  Date: Tue Jun 18 22:03:55 2013
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: usb-modeswitch-data
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/usb-modeswitch-data/+bug/1192297/+subscriptions

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

[Desktop-packages] [Bug 1247712] Re: Unable to install Broadcom STA wireless dirver on 3.8 / 3.11 kernel via jockey-gtk

** Also affects: bcmwl (Baltix)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to jockey in Ubuntu.
https://bugs.launchpad.net/bugs/1247712

Title:
  Unable to install Broadcom STA wireless dirver on 3.8 / 3.11 kernel
  via jockey-gtk

Status in Jockey driver manager:
  Invalid
Status in “bcmwl” package in Ubuntu:
  Confirmed
Status in “jockey” package in Ubuntu:
  Invalid
Status in “linux-lts-raring” package in Ubuntu:
  Confirmed
Status in “bcmwl” source package in Precise:
  Confirmed
Status in “jockey” source package in Precise:
  Fix Committed
Status in “linux-lts-raring” source package in Precise:
  Confirmed
Status in “bcmwl” package in Baltix:
  New

Bug description:
  SRU request:

  Please accept jockey_0.9.7-0ubuntu7.15 into precise-proposed.

  [Impact]

  Kernel versions higher than 3.8 fail to rebind the Broadcom device to
  the driver thus compromising system stability. While rebinding is a
  nice feature it can't come at the cost of system stability. For this
  reason we'll disable this feature when dealing with Linux = 3.8 and
  preserve it in the other cases.

  [Test Case]

  Install and reboot into Linux 3.8 or higher (linux-lts-saucy or linux-
  lts-trusty), then use Jockey to install the broadcom wireless driver.
  Jockey will hang and the system will probably hang on shutdown.

  [Regression Potential]

  It should be minimal i.e. there won't be device rebinding on the
  livecd. This, however, shouldn't be an issue since the open broadcom
  driver should already work out of the box.

  Furthermore the test suite now covers this test case.


  == Description ==

  CID: 201303-13027 Dell Inspiron 5535
  CID: 201012-6925 Dell Latitude E6320
  CID: 201208-11536 Dell Latitude 6430u

  Affected chipsets:
  Broadcom 4365
  Broadcom 4313 [14e4:4727] (rev 01)
  Broadcom 43132

  The bcmwl (6.20.155.1+bdcom-0ubuntu0.0.2) cannot be installed on
  12.04.4 (3.11.0-15), 12.04.3 (3.8.0-29)

  Steps:
  1. Install Ubuntu 12.04.3 (or 12.04.4) + update
  2. Boot to desktop
  3. Install the Broadcom STA wireless driver via jockey-gtk

  Driver cannot be installed, jockey-gtk will stuck at Downloading and 
installing driver
  The last message from jockey.jog is:
  unbind/rebind on driver /sys/module/wl/drivers/pci:wl: device :02:00.0

  Error message could be found in dmesg:
  Nov  3 21:34:14 201012-6925 kernel: [  528.104653] 
wlc_lcnphy_rx_gain_tbl_free_entry = 5
  Nov  3 21:34:14 201012-6925 kernel: [  528.104863] BUG: unable to handle 
kernel paging request at a045d020
  Nov  3 21:34:14 201012-6925 kernel: [  528.104906] IP: [a045d020] 
0xa045d01f
  Nov  3 21:34:14 201012-6925 kernel: [  528.104936] PGD 1c0f067 PUD 1c13063 
PMD 2ea40067 PTE 0
  Nov  3 21:34:14 201012-6925 kernel: [  528.104967] Oops: 0010 [#1] SMP
  Nov  3 21:34:14 201012-6925 kernel: [  528.104988] Modules linked in: 
lib80211_crypt_tkip(F) wl(POF) lib80211(F) rfcomm(F) bnep(F) bluetooth(F) 
snd_hda_codec_hdmi(F) snd_hda_codec_idt(F) coretemp(F) kvm_intel(F) arc4(F) 
kvm(F) joydev(F) ghash_clmulni_intel(F) aesni_intel(F) ablk_helper(F) cryptd(F) 
lrw(F) mac80211(F) snd_hda_intel(F) brcmutil(F) snd_hda_codec(F) snd_hwdep(F) 
snd_pcm(F) i915(F) snd_seq_midi(F) snd_rawmidi(F) snd_seq_midi_event(F) 
snd_seq(F) aes_x86_64(F) snd_timer(F) snd_seq_device(F) cfg80211(F) snd(F) 
cordic(F) drm_kms_helper(F) drm(F) mei(F) psmouse(F) soundcore(F) xts(F) 
ppdev(F) gf128mul(F) parport_pc(F) i2c_algo_bit(F) dell_laptop(F) dcdbas(F) 
dell_wmi(F) video(F) lpc_ich(F) serio_raw(F) mac_hid(F) sparse_keymap(F) 
snd_page_alloc(F) wmi(F) microcode(F) lp(F) parport(F) ahci(F) libahci(F) 
sdhci_pci(F) sdhci(F) e1000e(F) [last unloaded: bcma]
  Nov  3 21:34:14 201012-6925 kernel: [  528.105424] CPU 0
  Nov  3 21:34:14 201012-6925 kernel: [  528.105438] Pid: 2695, comm: 
jockey-backend Tainted: PF  O 3.8.0-33-generic #48~precise1-Ubuntu Dell 
Inc. Latitude E6320/
  Nov  3 21:34:14 201012-6925 kernel: [  528.105493] RIP: 
0010:[a045d020]  [a045d020] 0xa045d01f
  Nov  3 21:34:14 201012-6925 kernel: [  528.105533] RSP: 0018:88001b405d50 
 EFLAGS: 00010282
  Nov  3 21:34:14 201012-6925 kernel: [  528.105558] RAX: 0001 RBX: 
880031788000 RCX: 
  Nov  3 21:34:14 201012-6925 kernel: [  528.105590] RDX:  RSI: 
a0861ec0 RDI: 880031788000
  Nov  3 21:34:14 201012-6925 kernel: [  528.105623] RBP: 88001b405d78 R08: 
 R09: 
  Nov  3 21:34:14 201012-6925 kernel: [  528.105657] R10: 3684 R11: 
0293 R12: 88001b405da0
  Nov  3 21:34:14 201012-6925 kernel: [  528.105690] R13: a08643e0 R14: 
880031788098 R15: 8800317880f8
  Nov  3 21:34:14 201012-6925 kernel: [  528.105724] FS:  
7fc348968700() GS:88010020() knlGS:
  Nov  3 21:34:14

[Desktop-packages] [Bug 1247712] Re: Unable to install Broadcom STA wireless dirver on 3.8 / 3.11 kernel via jockey-gtk

** Changed in: bcmwl (Baltix)
   Status: New = Confirmed

** Changed in: bcmwl (Baltix)
   Importance: Undecided = Medium

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to jockey in Ubuntu.
https://bugs.launchpad.net/bugs/1247712

Title:
  Unable to install Broadcom STA wireless dirver on 3.8 / 3.11 kernel
  via jockey-gtk

Status in Jockey driver manager:
  Invalid
Status in “bcmwl” package in Ubuntu:
  Confirmed
Status in “jockey” package in Ubuntu:
  Invalid
Status in “linux-lts-raring” package in Ubuntu:
  Confirmed
Status in “bcmwl” source package in Precise:
  Confirmed
Status in “jockey” source package in Precise:
  Fix Committed
Status in “linux-lts-raring” source package in Precise:
  Confirmed
Status in “bcmwl” package in Baltix:
  Confirmed

Bug description:
  SRU request:

  Please accept jockey_0.9.7-0ubuntu7.15 into precise-proposed.

  [Impact]

  Kernel versions higher than 3.8 fail to rebind the Broadcom device to
  the driver thus compromising system stability. While rebinding is a
  nice feature it can't come at the cost of system stability. For this
  reason we'll disable this feature when dealing with Linux = 3.8 and
  preserve it in the other cases.

  [Test Case]

  Install and reboot into Linux 3.8 or higher (linux-lts-saucy or linux-
  lts-trusty), then use Jockey to install the broadcom wireless driver.
  Jockey will hang and the system will probably hang on shutdown.

  [Regression Potential]

  It should be minimal i.e. there won't be device rebinding on the
  livecd. This, however, shouldn't be an issue since the open broadcom
  driver should already work out of the box.

  Furthermore the test suite now covers this test case.


  == Description ==

  CID: 201303-13027 Dell Inspiron 5535
  CID: 201012-6925 Dell Latitude E6320
  CID: 201208-11536 Dell Latitude 6430u

  Affected chipsets:
  Broadcom 4365
  Broadcom 4313 [14e4:4727] (rev 01)
  Broadcom 43132

  The bcmwl (6.20.155.1+bdcom-0ubuntu0.0.2) cannot be installed on
  12.04.4 (3.11.0-15), 12.04.3 (3.8.0-29)

  Steps:
  1. Install Ubuntu 12.04.3 (or 12.04.4) + update
  2. Boot to desktop
  3. Install the Broadcom STA wireless driver via jockey-gtk

  Driver cannot be installed, jockey-gtk will stuck at Downloading and 
installing driver
  The last message from jockey.jog is:
  unbind/rebind on driver /sys/module/wl/drivers/pci:wl: device :02:00.0

  Error message could be found in dmesg:
  Nov  3 21:34:14 201012-6925 kernel: [  528.104653] 
wlc_lcnphy_rx_gain_tbl_free_entry = 5
  Nov  3 21:34:14 201012-6925 kernel: [  528.104863] BUG: unable to handle 
kernel paging request at a045d020
  Nov  3 21:34:14 201012-6925 kernel: [  528.104906] IP: [a045d020] 
0xa045d01f
  Nov  3 21:34:14 201012-6925 kernel: [  528.104936] PGD 1c0f067 PUD 1c13063 
PMD 2ea40067 PTE 0
  Nov  3 21:34:14 201012-6925 kernel: [  528.104967] Oops: 0010 [#1] SMP
  Nov  3 21:34:14 201012-6925 kernel: [  528.104988] Modules linked in: 
lib80211_crypt_tkip(F) wl(POF) lib80211(F) rfcomm(F) bnep(F) bluetooth(F) 
snd_hda_codec_hdmi(F) snd_hda_codec_idt(F) coretemp(F) kvm_intel(F) arc4(F) 
kvm(F) joydev(F) ghash_clmulni_intel(F) aesni_intel(F) ablk_helper(F) cryptd(F) 
lrw(F) mac80211(F) snd_hda_intel(F) brcmutil(F) snd_hda_codec(F) snd_hwdep(F) 
snd_pcm(F) i915(F) snd_seq_midi(F) snd_rawmidi(F) snd_seq_midi_event(F) 
snd_seq(F) aes_x86_64(F) snd_timer(F) snd_seq_device(F) cfg80211(F) snd(F) 
cordic(F) drm_kms_helper(F) drm(F) mei(F) psmouse(F) soundcore(F) xts(F) 
ppdev(F) gf128mul(F) parport_pc(F) i2c_algo_bit(F) dell_laptop(F) dcdbas(F) 
dell_wmi(F) video(F) lpc_ich(F) serio_raw(F) mac_hid(F) sparse_keymap(F) 
snd_page_alloc(F) wmi(F) microcode(F) lp(F) parport(F) ahci(F) libahci(F) 
sdhci_pci(F) sdhci(F) e1000e(F) [last unloaded: bcma]
  Nov  3 21:34:14 201012-6925 kernel: [  528.105424] CPU 0
  Nov  3 21:34:14 201012-6925 kernel: [  528.105438] Pid: 2695, comm: 
jockey-backend Tainted: PF  O 3.8.0-33-generic #48~precise1-Ubuntu Dell 
Inc. Latitude E6320/
  Nov  3 21:34:14 201012-6925 kernel: [  528.105493] RIP: 
0010:[a045d020]  [a045d020] 0xa045d01f
  Nov  3 21:34:14 201012-6925 kernel: [  528.105533] RSP: 0018:88001b405d50 
 EFLAGS: 00010282
  Nov  3 21:34:14 201012-6925 kernel: [  528.105558] RAX: 0001 RBX: 
880031788000 RCX: 
  Nov  3 21:34:14 201012-6925 kernel: [  528.105590] RDX:  RSI: 
a0861ec0 RDI: 880031788000
  Nov  3 21:34:14 201012-6925 kernel: [  528.105623] RBP: 88001b405d78 R08: 
 R09: 
  Nov  3 21:34:14 201012-6925 kernel: [  528.105657] R10: 3684 R11: 
0293 R12: 88001b405da0
  Nov  3 21:34:14 201012-6925 kernel: [  528.105690] R13: a08643e0 R14: 
880031788098 R15: 8800317880f8
  Nov  3 21:34:14 201012-6925 kernel: [  528.105724] FS:  
7fc348968700()

[Desktop-packages] [Bug 1354823] Re: FFe: Please merge or sync usb-modeswitch from Debian unstable/testing - current package is obsolete and latest usb-modeswitch-data will not work

2014-10-04 Thread Mantas Kriaučiūnas

http://draisberghof.de/usb_modeswitch/ChangeLog

Version 2.2.0, 2014/05/29
  Introduction of parameter HuaweiNewMode, wrapping the standard bulk
  message for all newer Huawei devices; support for generic fall-back
  config files, combined with OS switch (per vendor ID), implementation
  to use a specific switching command on Android for all Huawei devices (see
  README of data package for details); this change was suggested by Huawei

http://draisberghof.de/usb_modeswitch/ChangeLogData
20140529:
ATTENTION: requires usb-modeswitch version = 2.2.0 due to new para-
meter HuaweiNewMode (further reducing config file size);
Added devices: Nexperia TM TD-SCDMA, Sunplus SU-3200U, Olivetti
Olicard 160 and Olicard 500, Ericsson F5521gw, Sony Ericsson EC400,
Huawei E180, Huawei/Vod. W5101 Router, Huawei E3531, Huawei E3131
(Variant), Novatel MiFi 4082, Emobile D21LC, Prolink PCM100, Titan 3.5G,
several nameless ZTE modems, several minor device configuration
corrections (thanks once again to Lars Melin for the tedious device
research and compilation!);
Substantial change in handling of Huawei devices - generic udev rule and
additional generic configuration files (as fallback for unknown models
or as OS-specific catch-all); see README for details

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to usb-modeswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1354823

Title:
  FFe: Please merge or sync usb-modeswitch from Debian unstable/testing
  - current package is obsolete and latest usb-modeswitch-data will not
  work

Status in “usb-modeswitch” package in Ubuntu:
  Confirmed

Bug description:
  We believe that usb-modeswitch needs to be synched from Debian again:

  New upstream versions of usb-modeswitch (2.2.0) and usb-modeswitch-
  data (20140529) released 4 months ago and were packaged in Debian
  unstable since June!

  Lots of other Huawei related issues, like bug #1308895, bug #1192297
  and lots of other bugs are fixed in updated usb-modeswitch
  (2.2.0+repack0-2) and usb-modeswitch-data (20140529-1) packages in
  Debian unstable.

  Please merge usb-modeswitch 2.2.0+repack0-2 package from Debian
  unstable to Ubuntu Utopic.

  Mathieu Trudel-Lapierre already did the merging job (see branch
  bellow) - please merge usb-modeswitch 2.2.0+repack0-2 package from
  Debian unstable to Ubuntu 14.10 (Utopic).

  Here is usb-modeswitch 2.2.0+repack0-2 packaging code with patches:
  lp:~mathieu-tl/ubuntu/utopic/usb-modeswitch/merge-2.2.0
  
https://code.launchpad.net/~mathieu-tl/ubuntu/utopic/usb-modeswitch/merge-2.2.0

  Here is debian/changelog:

  usb-modeswitch (2.2.0+repack0-2) unstable; urgency=medium
     * Add patch to set TMPDIR to /run, add Build-Depends version constraint to
   pull a libjim supporting the setting of TMPDIR (Closes: #751271)

  usb-modeswitch (2.2.0+repack0-1) unstable; urgency=medium
    * New 2.2.0 upstream release
  - Introduction of parameter HuaweiNewMode, wrapping the standard bulk
    message for all newer Huawei devices;
  - Support for generic fallback config files, combined with OS switch (per
    vendor ID);
    * Repack the upstream tarball:
  - Drop the code copy of jimtcl.
    * Bump usb-modeswitch-data depends to 20140529
    * Update VCS-* fields to canonical form
   -- Didier Raboud o...@debian.org Mon, 09 Jun 2014 11:21:08 +0200

  And here is usb-modeswitch-data debian/changelog:
  
http://metadata.ftp-master.debian.org/changelogs/main/u/usb-modeswitch-data/unstable_changelog

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: usb-modeswitch 2.1.1+repack0-1ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-6.11-lowlatency 3.16.0-rc7
  Uname: Linux 3.16.0-6-lowlatency x86_64
  ApportVersion: 2.14.5-0ubuntu4
  Architecture: amd64
  Date: Sun Aug 10 07:19:28 2014
  InstallationDate: Installed on 2014-07-25 (15 days ago)
  InstallationMedia: Lubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140722)
  SourcePackage: usb-modeswitch

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

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

[Desktop-packages] [Bug 1308895] Re: FFe: Please merge usb-modeswitch from Debian unstable - Huawei E3531 does not automatically switches to modem mode (no udev rules for this modem in Ubuntu's /lib/u

2014-10-03 Thread Mantas Kriaučiūnas

** Summary changed:

- Please merge usb-modeswitch from Debian unstable - Huawei E3531 does not 
automatically switches to modem mode (no udev rules for this modem in Ubuntu's 
/lib/udev/rules.d)
+ FFe: Please merge usb-modeswitch from Debian unstable - Huawei E3531 does not 
automatically switches to modem mode (no udev rules for this modem in Ubuntu's 
/lib/udev/rules.d)

** Description changed:

- The operating system does not see the modem  maybe because usb-
- modeswitch not automatically switches the device mode the modem.
+ Lots of other Huawei related issues, like bug # 1192297 are fixed in
+ updated usb-modeswitch (2.2.0+repack0-2) and usb-modeswitch-data
+ (20140529-1) packages in Debian unstable.
+ 
+ Mathieu Trudel-Lapierre already did the merging job (see branch bellow)
+ - please merge usb-modeswitch 2.2.0+repack0-2 package from Debian
+ unstable to Ubuntu 14.10 (Utopic).
+ 
+ There is usb-modeswitch 2.2.0+repack0-2 packaging code with patches:
+ lp:~mathieu-tl/ubuntu/utopic/usb-modeswitch/merge-2.2.0
+ 
https://code.launchpad.net/~mathieu-tl/ubuntu/utopic/usb-modeswitch/merge-2.2.0
  
  ProblemType: Bug
- DistroRelease: Ubuntu 14.04
+ DistroRelease: Ubuntu 14.10
  Package: usb-modeswitch 2.1.1+repack0-1ubuntu1
- ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
- Uname: Linux 3.13.0-24-generic x86_64
- ApportVersion: 2.14.1-0ubuntu3
- Architecture: amd64
  CurrentDesktop: Unity
- Date: Thu Apr 17 11:34:11 2014
- InstallationDate: Installed on 2014-04-16 (0 days ago)
- InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140415)
  SourcePackage: usb-modeswitch
- UpgradeStatus: No upgrade log present (probably fresh install)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to usb-modeswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1308895

Title:
  FFe: Please merge usb-modeswitch from Debian unstable - Huawei E3531
  does not automatically switches to modem mode (no udev rules for this
  modem in Ubuntu's /lib/udev/rules.d)

Status in “usb-modeswitch” package in Ubuntu:
  Confirmed

Bug description:
  Lots of other Huawei related issues, like bug # 1192297 are fixed in
  updated usb-modeswitch (2.2.0+repack0-2) and usb-modeswitch-data
  (20140529-1) packages in Debian unstable.

  Mathieu Trudel-Lapierre already did the merging job (see branch
  bellow) - please merge usb-modeswitch 2.2.0+repack0-2 package from
  Debian unstable to Ubuntu 14.10 (Utopic).

  There is usb-modeswitch 2.2.0+repack0-2 packaging code with patches:
  lp:~mathieu-tl/ubuntu/utopic/usb-modeswitch/merge-2.2.0
  
https://code.launchpad.net/~mathieu-tl/ubuntu/utopic/usb-modeswitch/merge-2.2.0

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: usb-modeswitch 2.1.1+repack0-1ubuntu1
  CurrentDesktop: Unity
  SourcePackage: usb-modeswitch

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

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

[Desktop-packages] [Bug 1354823] Re: FFe: Please merge or sync usb-modeswitch from Debian unstable/testing - current package is obsolete and latest usb-modeswitch-data will not work

2014-10-03 Thread Mantas Kriaučiūnas

** Summary changed:

- Please merge or sync usb-modeswitch from Debian unstable/testing - current 
package is obsolete and latest usb-modeswitch-data will not work
+ FFe: Please merge or sync usb-modeswitch from Debian unstable/testing - 
current package is obsolete and latest usb-modeswitch-data will not work

** Description changed:

  We believe that usb-modeswitch needs to be synched from Debian again:
  
  New upstream versions of usb-modeswitch (2.2.0) and usb-modeswitch-data
- (20140529) released 3 months ago and were packaged in Debian unstable
+ (20140529) released 4 months ago and were packaged in Debian unstable
  since June!
  
- Lots of other Huawei related issues, like bug #1308895) are fixed in
- updated usb-modeswitch (2.2.0+repack0-1) and usb-modeswitch-data
- (20140529-1) packages in Debian unstable.
+ Lots of other Huawei related issues, like bug #1308895, bug #1192297 and
+ lots of other bugs are fixed in updated usb-modeswitch (2.2.0+repack0-2)
+ and usb-modeswitch-data (20140529-1) packages in Debian unstable.
  
- Please merge usb-modeswitch 2.2.0+repack0-1 package from Debian unstable
+ Please merge usb-modeswitch 2.2.0+repack0-2 package from Debian unstable
  to Ubuntu Utopic.
+ 
+ Mathieu Trudel-Lapierre already did the merging job (see branch bellow)
+ - please merge usb-modeswitch 2.2.0+repack0-2 package from Debian
+ unstable to Ubuntu 14.10 (Utopic).
+ 
+ Here is usb-modeswitch 2.2.0+repack0-2 packaging code with patches:
+ lp:~mathieu-tl/ubuntu/utopic/usb-modeswitch/merge-2.2.0
+ 
https://code.launchpad.net/~mathieu-tl/ubuntu/utopic/usb-modeswitch/merge-2.2.0
  
  Here is debian/changelog:
  
  usb-modeswitch (2.2.0+repack0-2) unstable; urgency=medium
-* Add patch to set TMPDIR to /run, add Build-Depends version constraint to
-  pull a libjim supporting the setting of TMPDIR (Closes: #751271)
+    * Add patch to set TMPDIR to /run, add Build-Depends version constraint to
+  pull a libjim supporting the setting of TMPDIR (Closes: #751271)
  
  usb-modeswitch (2.2.0+repack0-1) unstable; urgency=medium
-   * New 2.2.0 upstream release
- - Introduction of parameter HuaweiNewMode, wrapping the standard bulk
-   message for all newer Huawei devices;
- - Support for generic fallback config files, combined with OS switch (per
-   vendor ID);
-   * Repack the upstream tarball:
- - Drop the code copy of jimtcl.
-   * Bump usb-modeswitch-data depends to 20140529
-   * Update VCS-* fields to canonical form
-  -- Didier Raboud o...@debian.org Mon, 09 Jun 2014 11:21:08 +0200
+   * New 2.2.0 upstream release
+ - Introduction of parameter HuaweiNewMode, wrapping the standard bulk
+   message for all newer Huawei devices;
+ - Support for generic fallback config files, combined with OS switch (per
+   vendor ID);
+   * Repack the upstream tarball:
+ - Drop the code copy of jimtcl.
+   * Bump usb-modeswitch-data depends to 20140529
+   * Update VCS-* fields to canonical form
+  -- Didier Raboud o...@debian.org Mon, 09 Jun 2014 11:21:08 +0200
  
  And here is usb-modeswitch-data debian/changelog:
  
http://metadata.ftp-master.debian.org/changelogs/main/u/usb-modeswitch-data/unstable_changelog
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: usb-modeswitch 2.1.1+repack0-1ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-6.11-lowlatency 3.16.0-rc7
  Uname: Linux 3.16.0-6-lowlatency x86_64
  ApportVersion: 2.14.5-0ubuntu4
  Architecture: amd64
  Date: Sun Aug 10 07:19:28 2014
  InstallationDate: Installed on 2014-07-25 (15 days ago)
  InstallationMedia: Lubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140722)
  SourcePackage: usb-modeswitch

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to usb-modeswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1354823

Title:
  FFe: Please merge or sync usb-modeswitch from Debian unstable/testing
  - current package is obsolete and latest usb-modeswitch-data will not
  work

Status in “usb-modeswitch” package in Ubuntu:
  Confirmed

Bug description:
  We believe that usb-modeswitch needs to be synched from Debian again:

  New upstream versions of usb-modeswitch (2.2.0) and usb-modeswitch-
  data (20140529) released 4 months ago and were packaged in Debian
  unstable since June!

  Lots of other Huawei related issues, like bug #1308895, bug #1192297
  and lots of other bugs are fixed in updated usb-modeswitch
  (2.2.0+repack0-2) and usb-modeswitch-data (20140529-1) packages in
  Debian unstable.

  Please merge usb-modeswitch 2.2.0+repack0-2 package from Debian
  unstable to Ubuntu Utopic.

  Mathieu Trudel-Lapierre already did the merging job (see branch
  bellow) - please merge usb-modeswitch 2.2.0+repack0-2 package from
  Debian unstable to Ubuntu 14.10 (Utopic).

  Here is usb-modeswitch 2.2.0+repack0-2 packaging code with patches:
  lp:~mathieu-tl/ubuntu/utopic/usb-modeswitch/merge-2.2.0

[Desktop-packages] [Bug 1081019] Re: Benchmark for disks always fails on 32 bit systems

2014-09-10 Thread Mantas Kriaučiūnas

** Summary changed:

- Benchmark for Harddisk fail
+ Benchmark for disks always fails on 32 bit systems

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-disk-utility in Ubuntu.
https://bugs.launchpad.net/bugs/1081019

Title:
  Benchmark for disks always fails on 32 bit systems

Status in “gnome-disk-utility” package in Ubuntu:
  Confirmed

Bug description:
  I can not benchmark any harddisk I have. I tried with unmounted, 
usb-connected harddisks. 
  Steps to reproduce:

  1) Start gnome-disks
  2) Select a Harddisk and unmount all partitions so the disk is not in use
  3) Select more actions... button and then the point Benchmark volume...
  4) Run start benchmark... and use the default settings and press the new 
button start benchmarking

  Now I get:

  Error seeking to offset 10002022400 (g-io-error-quark, 0)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-disk-utility 3.6.1-1ubuntu1
  ProcVersionSignature: Ubuntu 3.7.0-2.8-generic 3.7.0-rc5
  Uname: Linux 3.7.0-2-generic i686
  ApportVersion: 2.6.2-0ubuntu5
  Architecture: i386
  Date: Tue Nov 20 09:29:43 2012
  InstallationDate: Installed on 2012-06-16 (156 days ago)
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 
(20120423.2)
  MarkForUpload: True
  SourcePackage: gnome-disk-utility
  UpgradeStatus: Upgraded to raring on 2012-11-12 (7 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1081019/+subscriptions

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

[Desktop-packages] [Bug 1276379] Re: fglrx-installer 2:13.101-0ubuntu0.0.1 fails with some legacy devices (Radeon HD 2000 3000 4000)

2014-09-09 Thread Mantas Kriaučiūnas

** Also affects: fglrx-installer (Baltix)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fglrx-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1276379

Title:
  fglrx-installer 2:13.101-0ubuntu0.0.1 fails with some legacy devices
  (Radeon HD 2000 3000 4000)

Status in “fglrx-installer” package in Ubuntu:
  Confirmed
Status in “fglrx-installer” package in Baltix:
  New

Bug description:
  [Updated description]

  Update of the fglrx-driver (version 2:13.101-0ubuntu0.0.1 on 2014-02-03) 
brought by update-manager (through ubuntu-updates repos) on Precise doesn't 
work on some legacy devices.
  The main symptom is the fallback to unity-2D.
   
  This bug seems target only Precise with no LTS Enablement Stack activated, in 
other words with Linux 3.2.x and XServer 7.6.
  == please : confirm or infirm using:
  uname -rm
  apt-cache policy xserver-xorg

  It may be in relation with #1058040, about non-support for Radeon [Mobility] 
HD 2xxx, 3xxx, 4xxx on Ubuntu 12.10 and higher.
  __

  1)Description:Ubuntu 12.04.4 LTS
  Release:  12.04
  Architecture: amd64

  2) apt-cache policy fglrx fglrx-amdcccle
  fglrx:
    Installé : 2:13.101-0ubuntu0.0.1
    Candidat : 2:13.101-0ubuntu0.0.1
   Table de version :
   *** 2:13.101-0ubuntu0.0.1 0
  500 http://fr.archive.ubuntu.com/ubuntu/ precise-updates/restricted 
amd64 Packages
  100 /var/lib/dpkg/status
   2:8.960-0ubuntu1 0
  500 http://fr.archive.ubuntu.com/ubuntu/ precise/restricted amd64 
Packages
  fglrx-amdcccle:
    Installé : 2:13.101-0ubuntu0.0.1
    Candidat : 2:13.101-0ubuntu0.0.1

  3) I expected that the driver :
   - set up
   - work

  4) It did'nt work :
   - Ubuntu was very slow
   - Unity fall in Unity-2d mode
   - when I taped CTRL+SUPER, desktops appears blue
   - fglrx-amdcccle failed
   - fans were turning at a high speed
   - lots of warning messages as described bellow

  5) Workaround
  I had to downgrade manually the driver to the old 8.960, which works without 
problem.
  You could do it using Synaptics our using the CLI

  I tried to do an apt-get remove fglrx fglrx-amdcccle but apt-get gaves me 
fglrx-updates in replacement , with the same issues. I experimented 
fglrx-update some months (a year?) ago with similar problems, but at that time 
it was a conscient experimentation.
  The 13.101-0ubuntu0.0.1 could maybe stay in fglrx-updates, and no fglrx ?

  

  
  ~$ sudo aticonfig
  aticonfig: No supported adapters detected

  ~$ lspci -nn | grep VGA02:00.0 VGA compatible controller [0300]:
  Advanced Micro Devices, Inc. [AMD/ATI] RV710/M92 [Mobility Radeon HD
  4530/4570/545v] [1002:9553]

   ~$ grep /drivers/ /var/log/Xorg.0.log
  [26.888] (II) Loading 
/usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so
  [27.015] (II) Loading 
/usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so
  [27.016] (II) Loading /usr/lib/xorg/modules/drivers/ati_drv.so
  [27.017] (II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so
  [27.018] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
  [27.019] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
  [27.122] (II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so

  ~$ dmesg | grep fglrx
  [   28.612217] [fglrx] Maximum main memory to use for locked dma buffers: 
3657 MBytes.
  [   28.613015] [fglrx:firegl_init_device_list] *ERROR* No supported display 
adapters were found
  [   28.613021] [fglrx:firegl_init_module] *ERROR* firegl_init_devices failed
  [   28.775649] [fglrx] Maximum main memory to use for locked dma buffers: 
3657 MBytes.
  [   28.776032] [fglrx:firegl_init_device_list] *ERROR* No supported display 
adapters were found
  [   28.776036] [fglrx:firegl_init_module] *ERROR* firegl_init_devices failed

  ~$ fglrxinfo
  X Error of failed request:  BadRequest (invalid request code or no such 
operation)
    Major opcode of failed request:  153 (GLX)
    Minor opcode of failed request:  19 (X_GLXQueryServerString)
    Serial number of failed request:  12
    Current serial number in output stream:  12

  ~$ glxinfo
  name of display: :0.0
  X Error of failed request:  BadRequest (invalid request code or no such 
operation)
    Major opcode of failed request:  153 (GLX)
    Minor opcode of failed request:  19 (X_GLXQueryServerString)
    Serial number of failed request:  12
    Current serial number in output stream:  12

  
  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: fglrx 2:8.960-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.2.0-58.88-generic 3.2.53
  Uname: Linux 3.2.0-58-generic x86_64
  NonfreeKernelModules: wl fglrx
  .tmp.unity.support.test.0:

  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  CompizPlugins:

[Desktop-packages] [Bug 1354823] Re: Please merge or sync usb-modeswitch from Debian unstable/testing - current package is obsolete and latest usb-modeswitch-data will not work

2014-09-02 Thread Mantas Kriaučiūnas

** Summary changed:

- usb-modeswitch is obsolete and usb-modeswitch-data will not install
+ Please merge or sync usb-modeswitch from Debian unstable/testing - current 
package is obsolete and latest usb-modeswitch-data will not work

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to usb-modeswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1354823

Title:
  Please merge or sync usb-modeswitch from Debian unstable/testing -
  current package is obsolete and latest usb-modeswitch-data will not
  work

Status in “usb-modeswitch” package in Ubuntu:
  Confirmed

Bug description:
  I believe that usb-modeswitch needs to be synched from Debian again.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: usb-modeswitch 2.1.1+repack0-1ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-6.11-lowlatency 3.16.0-rc7
  Uname: Linux 3.16.0-6-lowlatency x86_64
  ApportVersion: 2.14.5-0ubuntu4
  Architecture: amd64
  Date: Sun Aug 10 07:19:28 2014
  InstallationDate: Installed on 2014-07-25 (15 days ago)
  InstallationMedia: Lubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140722)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: usb-modeswitch
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1354823] Re: Please merge or sync usb-modeswitch from Debian unstable/testing - current package is obsolete and latest usb-modeswitch-data will not work

2014-09-02 Thread Mantas Kriaučiūnas

** Description changed:

- I believe that usb-modeswitch needs to be synched from Debian again.
+ We believe that usb-modeswitch needs to be synched from Debian again:
+ 
+ New upstream versions of usb-modeswitch (2.2.0) and usb-modeswitch-data
+ (20140529) released 3 months ago and were packaged in Debian unstable
+ since June!
+ 
+ Lots of other Huawei related issues, like bug #1308895) are fixed in
+ updated usb-modeswitch (2.2.0+repack0-1) and usb-modeswitch-data
+ (20140529-1) packages in Debian unstable.
+ 
+ Please merge usb-modeswitch 2.2.0+repack0-1 package from Debian unstable
+ to Ubuntu Utopic.
+ 
+ Here is debian/changelog:
+ 
+ usb-modeswitch (2.2.0+repack0-2) unstable; urgency=medium
+* Add patch to set TMPDIR to /run, add Build-Depends version constraint to
+  pull a libjim supporting the setting of TMPDIR (Closes: #751271)
+ 
+ usb-modeswitch (2.2.0+repack0-1) unstable; urgency=medium
+   * New 2.2.0 upstream release
+ - Introduction of parameter HuaweiNewMode, wrapping the standard bulk
+   message for all newer Huawei devices;
+ - Support for generic fallback config files, combined with OS switch (per
+   vendor ID);
+   * Repack the upstream tarball:
+ - Drop the code copy of jimtcl.
+   * Bump usb-modeswitch-data depends to 20140529
+   * Update VCS-* fields to canonical form
+  -- Didier Raboud o...@debian.org Mon, 09 Jun 2014 11:21:08 +0200
+ 
+ And here is usb-modeswitch-data debian/changelog:
+ 
http://metadata.ftp-master.debian.org/changelogs/main/u/usb-modeswitch-data/unstable_changelog
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: usb-modeswitch 2.1.1+repack0-1ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-6.11-lowlatency 3.16.0-rc7
  Uname: Linux 3.16.0-6-lowlatency x86_64
  ApportVersion: 2.14.5-0ubuntu4
  Architecture: amd64
  Date: Sun Aug 10 07:19:28 2014
  InstallationDate: Installed on 2014-07-25 (15 days ago)
  InstallationMedia: Lubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140722)
- ProcEnviron:
-  TERM=xterm
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=set
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
  SourcePackage: usb-modeswitch
- UpgradeStatus: No upgrade log present (probably fresh install)

** Tags removed: amd64
** Tags added: merge trusty

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to usb-modeswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1354823

Title:
  Please merge or sync usb-modeswitch from Debian unstable/testing -
  current package is obsolete and latest usb-modeswitch-data will not
  work

Status in “usb-modeswitch” package in Ubuntu:
  Confirmed

Bug description:
  We believe that usb-modeswitch needs to be synched from Debian again:

  New upstream versions of usb-modeswitch (2.2.0) and usb-modeswitch-
  data (20140529) released 3 months ago and were packaged in Debian
  unstable since June!

  Lots of other Huawei related issues, like bug #1308895) are fixed in
  updated usb-modeswitch (2.2.0+repack0-1) and usb-modeswitch-data
  (20140529-1) packages in Debian unstable.

  Please merge usb-modeswitch 2.2.0+repack0-1 package from Debian
  unstable to Ubuntu Utopic.

  Here is debian/changelog:

  usb-modeswitch (2.2.0+repack0-2) unstable; urgency=medium
 * Add patch to set TMPDIR to /run, add Build-Depends version constraint to
   pull a libjim supporting the setting of TMPDIR (Closes: #751271)

  usb-modeswitch (2.2.0+repack0-1) unstable; urgency=medium
* New 2.2.0 upstream release
  - Introduction of parameter HuaweiNewMode, wrapping the standard bulk
message for all newer Huawei devices;
  - Support for generic fallback config files, combined with OS switch (per
vendor ID);
* Repack the upstream tarball:
  - Drop the code copy of jimtcl.
* Bump usb-modeswitch-data depends to 20140529
* Update VCS-* fields to canonical form
   -- Didier Raboud o...@debian.org Mon, 09 Jun 2014 11:21:08 +0200

  And here is usb-modeswitch-data debian/changelog:
  
http://metadata.ftp-master.debian.org/changelogs/main/u/usb-modeswitch-data/unstable_changelog

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: usb-modeswitch 2.1.1+repack0-1ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-6.11-lowlatency 3.16.0-rc7
  Uname: Linux 3.16.0-6-lowlatency x86_64
  ApportVersion: 2.14.5-0ubuntu4
  Architecture: amd64
  Date: Sun Aug 10 07:19:28 2014
  InstallationDate: Installed on 2014-07-25 (15 days ago)
  InstallationMedia: Lubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140722)
  SourcePackage: usb-modeswitch

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

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

[Desktop-packages] [Bug 1328412] Re: Huawei E398 GSM modem configuration data not included

2014-08-27 Thread Mantas Kriaučiūnas

New upstream versions of usb-modeswitch (2.2.0) and usb-modeswitch-data
(20140529) released 3 months ago and were packaged in Debian unstable
since June!

This Huawei E398 issue (and lots of other Huawei related issues, like
bug #1308895) are fixed in updated usb-modeswitch (2.2.0+repack0-1) and
usb-modeswitch-data (20140529-1) packages in Debian unstable.

Please merge usb-modeswitch 2.2.0+repack0-1 package from Debian unstable
to Ubuntu Utopic.

Here is debian/changelog:

usb-modeswitch (2.2.0+repack0-2) unstable; urgency=medium
   * Add patch to set TMPDIR to /run, add Build-Depends version constraint to
 pull a libjim supporting the setting of TMPDIR (Closes: #751271)

usb-modeswitch (2.2.0+repack0-1) unstable; urgency=medium
  * New 2.2.0 upstream release
- Introduction of parameter HuaweiNewMode, wrapping the standard bulk
  message for all newer Huawei devices;
- Support for generic fallback config files, combined with OS switch (per
  vendor ID);
  * Repack the upstream tarball:
- Drop the code copy of jimtcl.
  * Bump usb-modeswitch-data depends to 20140529
  * Update VCS-* fields to canonical form
 -- Didier Raboud o...@debian.org Mon, 09 Jun 2014 11:21:08 +0200

And here is usb-modeswitch-data debian/changelog:
http://metadata.ftp-master.debian.org/changelogs/main/u/usb-modeswitch-data/unstable_changelog

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to usb-modeswitch-data in Ubuntu.
https://bugs.launchpad.net/bugs/1328412

Title:
  Huawei E398 GSM modem configuration data not included

Status in “usb-modeswitch-data” package in Ubuntu:
  Confirmed

Bug description:
  Configuration data for the Huawei E398 modem is not included in the
  usb-modeswitch-data package, and its mode is not switched upon
  insertion.  Bug #1192297 is for a similar device, and the instructions
  included there describe a working fix.  (The second comment includes
  the correct information for the E398, which is USB vendor:product
  12d1:15ca.)

  lsusb info for this device (after mode switch) is:

  Bus 002 Device 008: ID 12d1:1506 Huawei Technologies Co., Ltd. E398 
LTE/UMTS/GSM Modem/Networkcard
  Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB   2.00
bDeviceClass0 (Defined at Interface level)
bDeviceSubClass 0 
bDeviceProtocol 0 
bMaxPacketSize064
idVendor   0x12d1 Huawei Technologies Co., Ltd.
idProduct  0x1506 E398 LTE/UMTS/GSM Modem/Networkcard
bcdDevice1.02
iManufacturer   1 HUAWEI
iProduct2 HUAWEI Mobile
iSerial 0 
bNumConfigurations  1
Configuration Descriptor:
  bLength 9
  bDescriptorType 2
  wTotalLength  225
  bNumInterfaces  6
  bConfigurationValue 1
  iConfiguration  0 
  bmAttributes 0x80
(Bus Powered)
  MaxPower  500mA
  Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber0
bAlternateSetting   0
bNumEndpoints   3
bInterfaceClass   255 Vendor Specific Class
bInterfaceSubClass  2 
bInterfaceProtocol  1 
iInterface  0 
** UNRECOGNIZED:  05 24 00 10 01
** UNRECOGNIZED:  04 24 02 02
** UNRECOGNIZED:  05 24 01 00 00
** UNRECOGNIZED:  05 24 06 00 00
Endpoint Descriptor:
  bLength 7
  bDescriptorType 5
  bEndpointAddress 0x83  EP 3 IN
  bmAttributes3
Transfer TypeInterrupt
Synch Type   None
Usage Type   Data
  wMaxPacketSize 0x0040  1x 64 bytes
  bInterval   5
Endpoint Descriptor:
  bLength 7
  bDescriptorType 5
  bEndpointAddress 0x82  EP 2 IN
  bmAttributes2
Transfer TypeBulk
Synch Type   None
Usage Type   Data
  wMaxPacketSize 0x0200  1x 512 bytes
  bInterval   0
Endpoint Descriptor:
  bLength 7
  bDescriptorType 5
  bEndpointAddress 0x02  EP 2 OUT
  bmAttributes2
Transfer TypeBulk
Synch Type   None
Usage Type   Data
  wMaxPacketSize 0x0200  1x 512 bytes
  bInterval   0
  Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber1
bAlternateSetting   0
bNumEndpoints   1

[Desktop-packages] [Bug 1285746] Re: password dialog for chrome on automatic login

Appearing keyring password dialog in Chromium web browser after
automatic login setup problem can be solved by instaling gdm and purging
lightdm package (sudo apt-get install gdm  sudo apt-get purge lightdm
). Sometimes keyring password dialog problem can be fixed only after
creating a new user.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1285746

Title:
  password dialog for chrome on automatic login

Status in “gnome-keyring” package in Ubuntu:
  Opinion

Bug description:
  Steps to reproduce:

  1. install chrome or chromium
  2. set automatic login
  3. reboot and try to use chrome

  Expected result: browse the web
  What I get: an password input dialog. That is stealing input focus and I can 
not share an print-screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-keyring 3.10.1-1ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4
  Uname: Linux 3.13.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Feb 27 17:36:50 2014
  InstallationDate: Installed on 2014-02-26 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140224)
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1285746] Re: password dialog for chrome on automatic login

See bug #1242654 and https://bugzilla.redhat.com/show_bug.cgi?id=1012844
, https://bbs.archlinux.org/viewtopic.php?id=169320 for more info about
seahorse and GNOME Shell crashes when empty password is used for keyring

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1285746

Title:
  password dialog for chrome on automatic login

Status in “gnome-keyring” package in Ubuntu:
  Opinion

Bug description:
  Steps to reproduce:

  1. install chrome or chromium
  2. set automatic login
  3. reboot and try to use chrome

  Expected result: browse the web
  What I get: an password input dialog. That is stealing input focus and I can 
not share an print-screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-keyring 3.10.1-1ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4
  Uname: Linux 3.13.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Feb 27 17:36:50 2014
  InstallationDate: Installed on 2014-02-26 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140224)
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1285746] Re: password dialog for chrome on automatic login

Btw, I've noticed, that seahorse and GNOME Shell in Ubuntu 14.04 (Trusty) with 
lightdm crashes if you enter a blank password in Seahorse keyring password 
changing dialog.
But crash doesn't appear when lightdm is removed and gdm is used instead, 
that's why keyring password dialog in Chromium web browser after automatic 
login setup can be dismissed by instaling gdm and purging lightdm :)

** Bug watch added: Red Hat Bugzilla #1012844
   https://bugzilla.redhat.com/show_bug.cgi?id=1012844

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1285746

Title:
  password dialog for chrome on automatic login

Status in “gnome-keyring” package in Ubuntu:
  Opinion

Bug description:
  Steps to reproduce:

  1. install chrome or chromium
  2. set automatic login
  3. reboot and try to use chrome

  Expected result: browse the web
  What I get: an password input dialog. That is stealing input focus and I can 
not share an print-screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-keyring 3.10.1-1ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4
  Uname: Linux 3.13.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Feb 27 17:36:50 2014
  InstallationDate: Installed on 2014-02-26 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140224)
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1285746] Re: password dialog for chrome on automatic login

Btw, I've noticed, that seahorse and GNOME Shell in Ubuntu 14.04
(Trusty) crashes if you enter a blank password in Seahorse keyring
password changing dialog.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1285746

Title:
  password dialog for chrome on automatic login

Status in “gnome-keyring” package in Ubuntu:
  Opinion

Bug description:
  Steps to reproduce:

  1. install chrome or chromium
  2. set automatic login
  3. reboot and try to use chrome

  Expected result: browse the web
  What I get: an password input dialog. That is stealing input focus and I can 
not share an print-screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-keyring 3.10.1-1ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4
  Uname: Linux 3.13.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Feb 27 17:36:50 2014
  InstallationDate: Installed on 2014-02-26 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140224)
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1285746] Re: password dialog for chrome on automatic login

** Also affects: gnome-keyring (Baltix)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1285746

Title:
  password dialog for chrome on automatic login

Status in “gnome-keyring” package in Ubuntu:
  Opinion
Status in “gnome-keyring” package in Baltix:
  New

Bug description:
  Steps to reproduce:

  1. install chrome or chromium
  2. set automatic login
  3. reboot and try to use chrome

  Expected result: browse the web
  What I get: an password input dialog. That is stealing input focus and I can 
not share an print-screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-keyring 3.10.1-1ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4
  Uname: Linux 3.13.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Feb 27 17:36:50 2014
  InstallationDate: Installed on 2014-02-26 (1 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140224)
  SourcePackage: gnome-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1245874] Re: [SRU] Java JAR files are opened in file-roller instead of Java Runtime (remove application/x-jar=file-roller.desktop from /etc/gnome/defaults.list)

2014-07-03 Thread Mantas Kriaučiūnas

Please fix this bug in Ubuntu 14.04 LTS, I don't understant why you
fixed only in 13.10 (Saucy) ?

Launchpad Janitor (janitor) wrote on 2013-11-18: 
This bug was fixed in the package desktop-file-utils - 0.21-1ubuntu3
---
desktop-file-utils (0.21-1ubuntu3) saucy; urgency=low
  * debian/defaults.list: use jre as default for java runtime (lp: #1245874)
 -- Sebastien Bacher seb...@ubuntu.com Mon, 04 Nov 2013 11:56:46 +0100


** Summary changed:

- Java JAR files are opened in file-roller instead of Java Runtime (remove 
application/x-jar=file-roller.desktop from /etc/gnome/defaults.list) 
+ [SRU] Java JAR files are opened in file-roller instead of Java Runtime 
(remove application/x-jar=file-roller.desktop from /etc/gnome/defaults.list)

** Tags removed: verification-done
** Tags added: trusty

** Summary changed:

- [SRU] Java JAR files are opened in file-roller instead of Java Runtime 
(remove application/x-jar=file-roller.desktop from /etc/gnome/defaults.list)
+ Java JAR files are opened in file-roller instead of Java Runtime (remove 
application/x-jar=file-roller.desktop from /etc/gnome/defaults.list)

** Tags removed: trusty

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to desktop-file-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1245874

Title:
  Java JAR files are opened in file-roller instead of Java Runtime
  (remove application/x-jar=file-roller.desktop from
  /etc/gnome/defaults.list)

Status in “desktop-file-utils” package in Ubuntu:
  Fix Committed
Status in “desktop-file-utils” source package in Saucy:
  Fix Released
Status in “desktop-file-utils” package in Baltix:
  Fix Committed

Bug description:
  * Impact:
  Java JAR files are opened in file-roller instead of Java Runtime Environment

  * Steps to reproduce:
  Install JRE, for example Oracle Java7
  In File manager (nautilus) click on Jar file, for example download 
Minecraft.jar file from 
https://s3.amazonaws.com/Minecraft.Download/launcher/Minecraft.jar

  Actual result:
  minecraft.jar file is opened in file-roller instead of Java Runtime 
Environment (but Java Runtime Environment can be choosed by right-click-Open 
With-Java7 Runtime)

  Expected result:
  .jar file should be opened in Java Runtime

  * Regression potential:
  verify that clicking on java types in nautilus works as it should

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1245874/+subscriptions

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

[Desktop-packages] [Bug 1304531] Re: Removing an external monitor will move a maximized window to the current workspace

2014-07-02 Thread Mantas Kriaučiūnas

** Changed in: compiz (Ubuntu Trusty)
   Status: Confirmed = Fix Committed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to compiz in Ubuntu.
https://bugs.launchpad.net/bugs/1304531

Title:
  Removing an external monitor will move a maximized window to the
  current workspace

Status in Compiz:
  Fix Committed
Status in Compiz 0.9.11 series:
  In Progress
Status in “compiz” package in Ubuntu:
  Fix Released
Status in “compiz” source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

  Many users tend to have maximized window opened on other workspaces
  and use an external monitor such as a projector or one connected to a
  laptop docking station.  When removing this monitor, these maximized
  windows will get shuffled to the current workspace.  This can be
  aggravating for users and is not a good user experience.

  [Test case]

  1. Have an external monitor.
  2. Use multiple workspaces.
  3. Open a window and maximize it on a workspace such as workspace 2.
  4. Move to another workspace such as workspace 3.
  5. Remove the external monitor.

  [Regression potential]

  The code here is quite fragile and can be prone to some unexpected
  behaviors.  I took great care in trying to make sure no new
  regressions are caused by this fix, but there may be some corner case
  that is unaccounted for.  Also note that there are already some broken
  behaviors in this area that are unfixed by this code, so keep that in
  mind when testing that it truly isn't a regression.

  * Debdiff is found at https://launchpadlibrarian.net/178439518/compiz-
  trusty-sru-2.debdiff *

  Original Description:

  Removing an external monitor when using multiple workspaces will cause
  maximized windows on other workspaces to move to the current
  workspace.

  Scenario:
  1. Have an external monitor.
  2. Use multiple workspaces.
  3. Open a window and maximize it on a workspace such as workspace 2.
  4. Move to another workspace such as workspace 3.
  5. Remove the external monitor.

  Expected behavior:
  Maximized window will remain on the workspace it was opened on.

  Observed behavior:
  Maximized window moves to the current workspace

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

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

[Desktop-packages] [Bug 1311443] Re: switching input method is not reliable

2014-07-01 Thread Mantas Kriaučiūnas

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1311443

Title:
  switching input method is not reliable

Status in “gnome-settings-daemon” package in Ubuntu:
  Fix Released
Status in “unity-settings-daemon” package in Ubuntu:
  Invalid
Status in “gnome-settings-daemon” package in Baltix:
  Fix Committed

Bug description:
  [Impact]
  Under GNOME Shell, sometimes the input switcher popup (accessible via 
Super+Space by default) doesn't allow switching beyond the second input source.

  [Test Case]
  Under GNOME Shell, open gnome-control-center  Region  Language  Input 
Sources  +  Add at least two input sources (I use us, ru, and gr). Then open 
gnome-control-center  Keyboard  Shortcuts  Typing  Switch to next source  
Set to Super+Space.

  Try pressing Super+Space to pop open the input switcher. Then press
  Super+Space again. The input switcher might not switch the second
  time. It happens unreliably, so if it works, restarting gnome-
  settings-daemon may allow reproducing the bug.

  [Regression Potential]
  The reason this is happening is because of an old patch that enables input 
switching for non-GNOME desktops (Unity, GNOME Flashback) by handling it in 
gnome-settings-daemon. But GNOME Shell handles it itself, so 
gnome-settings-daemon's shortcuts may be conflicting with GNOME Shell's 
sometimes. The fix is to remove it, which is ok because that code isn't used by 
those other non-GNOME desktops any more (they use unity-settings-daemon 
instead). For that reason, there should be low risk of regression.

  --

  The behaviour of switching input method is strange.
  There are 2 ways to change input method. And both behave against expectation:

  1. super-space: When hitting super-space, the system can only switch from 
English to Chinese. But not the other way round.
  2. indicator: When switching language with the indicator, I can select both 
language. But the indicator is always showing en.

  OS: Ubuntu 14.04
  Input Method: English (US), Chinese (Cangjie)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1311443/+subscriptions

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

[Desktop-packages] [Bug 1311443] Re: switching input method is not reliable

gnome-settings-daemon ver. 3.8.6.1-0ubuntu11.2 from trusty-proposed fixes
several keyboard layouts switching problems in GNOME Shell, please upload this
version to trusty-updates ASAP.
Only one issue left in Trusty GNOME Shell - sometimes keyboard layout indicator
stops work when keyboard layouts (input methods) are removed or keyboard
shotcuts to change input methots are changed, but this issue disappears after
restarting GNOME-Shell :)

** Changed in: gnome-settings-daemon (Baltix)
Assignee: (unassigned) = Mantas Kriaučiūnas (mantas)

** Changed in: gnome-settings-daemon (Baltix)
Importance: Undecided = High

** Changed in: gnome-settings-daemon (Baltix)
Status: New = Fix Committed

--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1311443

Title:
switching input method is not reliable

Status in “gnome-settings-daemon” package in Ubuntu:
Fix Released
Status in “unity-settings-daemon” package in Ubuntu:
Invalid
Status in “gnome-settings-daemon” package in Baltix:
Fix Committed

Bug description:
[Impact]
Under GNOME Shell, sometimes the input switcher popup (accessible via
Super+Space by default) doesn't allow switching beyond the second input source.

[Test Case]
Under GNOME Shell, open gnome-control-center Region Language Input
Sources + Add at least two input sources (I use us, ru, and gr). Then open
gnome-control-center Keyboard Shortcuts Typing Switch to next source
Set to Super+Space.

Try pressing Super+Space to pop open the input switcher. Then press
Super+Space again. The input switcher might not switch the second
time. It happens unreliably, so if it works, restarting gnome-
settings-daemon may allow reproducing the bug.

[Regression Potential]
The reason this is happening is because of an old patch that enables input
switching for non-GNOME desktops (Unity, GNOME Flashback) by handling it in
gnome-settings-daemon. But GNOME Shell handles it itself, so
gnome-settings-daemon's shortcuts may be conflicting with GNOME Shell's
sometimes. The fix is to remove it, which is ok because that code isn't used by
those other non-GNOME desktops any more (they use unity-settings-daemon
instead). For that reason, there should be low risk of regression.

The behaviour of switching input method is strange.
There are 2 ways to change input method. And both behave against expectation:

1. super-space: When hitting super-space, the system can only switch from
English to Chinese. But not the other way round.
2. indicator: When switching language with the indicator, I can select both
language. But the indicator is always showing en.

OS: Ubuntu 14.04
Input Method: English (US), Chinese (Cangjie)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1311443/+subscriptions

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

[Desktop-packages] [Bug 1311237] Re: Pepper Flash needs backport to 12.04

** Also affects: pepperflashplugin-nonfree (Baltix)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1311237

Title:
  Pepper Flash needs backport to 12.04

Status in “chromium-browser” package in Ubuntu:
  Confirmed
Status in “pepperflashplugin-nonfree” package in Ubuntu:
  Confirmed
Status in “pepperflashplugin-nonfree” package in Baltix:
  New

Bug description:
  Now that this package is officially the only way to run flash on
  chromium it should be backported to 12.04, since that release is still
  supported until 26 April 2017. And I suppose 13.10 as well, but that's
  probably less pressing. Debian has released this package for wheezy,
  jessie,  sid, as you can see from the following rmadison output:

  debian:
   pepperflashplugin-nonfree | 1.2~bpo70+1 | wheezy-backports/contrib | source, 
amd64, i386
   pepperflashplugin-nonfree | 1.3 | jessie/contrib   | source, 
amd64, i386
   pepperflashplugin-nonfree | 1.3 | sid/contrib  | source, 
amd64, i386
  ubuntu:
   pepperflashplugin-nonfree | 1.3ubuntu1 | trusty/multiverse | source, amd64, 
i386

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

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

[Desktop-packages] [Bug 1184720] Re: Nautilus does not properly navigate symbolic links

VERIFICATION DONE one week ago, please upload nautilus to trusty-updates
I can confirm too: nautilus 1:3.10.1-0ubuntu9.2 from trusty-proposed works 
correctly, I just checked - 
creating symlinks and navigating those works correctly with nautilus 
1:3.10.1-0ubuntu9.2

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1184720

Title:
  Nautilus does not properly navigate symbolic links

Status in Nautilus:
  Fix Released
Status in “nautilus” package in Ubuntu:
  Fix Released
Status in “nautilus” source package in Trusty:
  Fix Committed

Bug description:
  Impact:
  Navigating symlinks in nautilus leads to incorrect directories

  Test case:
  1. Create a directory in Home called Folder
  2. Right click on Folder in Nautilus and select 'make link'
  3. Drag created link to Desktop
  4. Double-click on Link to Folder to open it in Nautilus

  Clicking the back arrow in Nautilus behaves as it should--it takes you
  back to Desktop, not the parent folder of the target of the link.

  However, the architecture displayed near the top of the Nautilus
  window shows the parent directory of the target, not of the link
  (i.e., it shows [Home][Folder], not [Home][Desktop][Link to Folder]

  Pressing alt+up also takes you to the parent of the target, not the
  link.

  Regression potential:
  check that creating symlinks and navigating those works correctly

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

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

[Desktop-packages] [Bug 1332426] Re: WOFF format not associated with gnome-font-viewer

** Also affects: baltix-default-settings
   Importance: Undecided
   Status: New

** Changed in: baltix-default-settings
 Assignee: (unassigned) = Mantas Kriaučiūnas (mantas)

** Changed in: baltix-default-settings
   Importance: Undecided = Medium

** Changed in: baltix-default-settings
   Status: New = Triaged

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-font-viewer in Ubuntu.
https://bugs.launchpad.net/bugs/1332426

Title:
  WOFF format not associated with gnome-font-viewer

Status in Default settings for the Baltix GNU/Linux OS and desktop:
  Triaged
Status in Gnome Font Viewer:
  New
Status in “gnome-font-viewer” package in Ubuntu:
  Triaged

Bug description:
  In a default Ubuntu 14.04 installation, OTF and WOFF files are not
  associated with gnome-font-viewer, even thou gnome-font-viewers is
  perfectly capable of showing these files.

  By default...
  * OTF files are shown with a generic document icon and are associated with 
LibreOffice Math (why?);
  * WOFF files are shown with a font icon but are associated with no programs.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-font-viewer 3.8.0-1build1
  Uname: Linux 3.15.0-031500rc8-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jun 20 08:24:09 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-05-15 (35 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  SourcePackage: gnome-font-viewer
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/baltix-default-settings/+bug/1332426/+subscriptions

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

[Desktop-packages] [Bug 1223226] Re: ubuntu gnome - pitivi - default window size out of screen bounds (horizontal)

You are using very old Pitivi release (0.15) - please install latest
Pitivi 0.93 (it's already in Ubuntu 14.04, if you can't upgrade to 14.04
then please add 'ppa:baltix-members/ppa' repository) and test if Pitivi
0.9x still has a default horizontal width greater than 1024 pixels.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pitivi in Ubuntu.
https://bugs.launchpad.net/bugs/1223226

Title:
  ubuntu gnome - pitivi - default window size out of screen bounds
  (horizontal)

Status in PiTiVi , Non-linear video editor:
  Fix Released
Status in “pitivi” package in Ubuntu:
  New

Bug description:
  Running ubuntu gnome 13.10 dev with all updates. Pitivi has a default
  horizontal width of greater than the monitor screen resolution and you
  are unable to manually change to fit by maximinse or manually resizing
  window edges.

  My screen res is 1024x768 on one monitor.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: pitivi 0.15.2-0.1ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0
  Uname: Linux 3.11.0-5-generic x86_64
  ApportVersion: 2.12.1-0ubuntu3
  Architecture: amd64
  Date: Tue Sep 10 09:04:59 2013
  InstallationDate: Installed on 2013-09-09 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Release amd64 
(20130424)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: pitivi
  UpgradeStatus: Upgraded to saucy on 2013-09-09 (0 days ago)

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

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

[Desktop-packages] [Bug 1311443] Re: switching input method is not reliable

2014-06-27 Thread Mantas Kriaučiūnas

** Also affects: gnome-settings-daemon (Baltix)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1311443

Title:
  switching input method is not reliable

Status in “gnome-settings-daemon” package in Ubuntu:
  Fix Released
Status in “unity-settings-daemon” package in Ubuntu:
  Invalid
Status in “gnome-settings-daemon” package in Baltix:
  New

Bug description:
  [Impact]
  Under GNOME Shell, sometimes the input switcher popup (accessible via 
Super+Space by default) doesn't allow switching beyond the second input source.

  [Test Case]
  Under GNOME Shell, open gnome-control-center  Region  Language  Input 
Sources  +  Add at least two input sources (I use us, ru, and gr). Then open 
gnome-control-center  Keyboard  Shortcuts  Typing  Switch to next source  
Set to Super+Space.

  Try pressing Super+Space to pop open the input switcher. Then press
  Super+Space again. The input switcher might not switch the second
  time. It happens unreliably, so if it works, restarting gnome-
  settings-daemon may allow reproducing the bug.

  [Regression Potential]
  The reason this is happening is because of an old patch that enables input 
switching for non-GNOME desktops (Unity, GNOME Flashback) by handling it in 
gnome-settings-daemon. But GNOME Shell handles it itself, so 
gnome-settings-daemon's shortcuts may be conflicting with GNOME Shell's 
sometimes. The fix is to remove it, which is ok because that code isn't used by 
those other non-GNOME desktops any more (they use unity-settings-daemon 
instead). For that reason, there should be low risk of regression.

  --

  The behaviour of switching input method is strange.
  There are 2 ways to change input method. And both behave against expectation:

  1. super-space: When hitting super-space, the system can only switch from 
English to Chinese. But not the other way round.
  2. indicator: When switching language with the indicator, I can select both 
language. But the indicator is always showing en.

  OS: Ubuntu 14.04
  Input Method: English (US), Chinese (Cangjie)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1311443/+subscriptions

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

[Desktop-packages] [Bug 1320189] Re: Libreoffice 4.2.3 cannot open encrypted microsoft xlsx and docx documents

2014-06-23 Thread Mantas Kriaučiūnas

It seems this bug should be already fixed in latest upload to Ubuntu
14.04 (Trusty)

libreoffice (1:4.2.4-0ubuntu2) trusty; urgency=medium
* bump upstream version
  * refresh patch queue
  * remove upstreamed patches:
- fdo-74981.diff
- fdo-50672.diff
  * bump help virtual version to 4.2
  * fix unity menu after insert formula (LP: #1296715)
  * avoid use of invalidated pointers (LP: #1219245)
  * add VBA macro patch
  * use internal npapi as this breaks with Firefox 30
 -- Bjoern Michaelsen bjoern.michael...@canonical.com   Fri, 13 Jun 2014 
17:11:09 +0200

See
https://launchpad.net/ubuntu/trusty/+source/libreoffice/1:4.2.4-0ubuntu2

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1320189

Title:
  Libreoffice 4.2.3 cannot open encrypted microsoft xlsx and docx
  documents

Status in “libreoffice” package in Ubuntu:
  Confirmed

Bug description:
  Libreoffice 4.2.3 cannot open encrypted xlsx and docx files.
  Previous versions 4.1 could open them.
  Libreoffice team have acknowledged the bug and released fix in version 4.2.4 
(https://bugs.freedesktop.org/show_bug.cgi?id=76222)

  I have tested with the libreoffice-4-2 paa
  (https://launchpad.net/~libreoffice/+archive/libreoffice-4-2) and
  4.2.4 does resolve the bug.

  Can this be considered for inclusion into 14.04 as an update/point
  release/backport?

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

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

[Desktop-packages] [Bug 1226962] Re: Hotkeys not functional in non-latin keyboard layout in 13.10 and 14.04

2014-06-19 Thread Mantas Kriaučiūnas

** Also affects: baltix-default-settings
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
Matching subscriptions: dp-unity
https://bugs.launchpad.net/bugs/1226962

Title:
  Hotkeys not functional in non-latin keyboard layout in 13.10 and 14.04

Status in Aptana Studio Installer:
  New
Status in Default settings for the Baltix GNU/Linux OS and desktop:
  New
Status in LibreOffice Productivity Suite:
  Confirmed
Status in IBus:
  New
Status in Indicator keyboard:
  Fix Released
Status in Inkscape: A Vector Drawing Tool:
  New
Status in Mutter:
  Fix Released
Status in The OpenOffice.org Suite:
  New
Status in Unity:
  Fix Released
Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged
Status in “gnome-terminal” package in Ubuntu:
  Triaged
Status in “indicator-keyboard” package in Ubuntu:
  Triaged
Status in “openjdk-7” package in Ubuntu:
  Triaged
Status in “unity” package in Ubuntu:
  Triaged
Status in “unity-settings-daemon” package in Ubuntu:
  Triaged
Status in “gnome-settings-daemon” package in Fedora:
  Unknown
Status in “gnome-shell” package in Fedora:
  Unknown

Bug description:
  New keyboard layout changer in Ubuntu 13.10 introduce  old-new bug. Any 
system or application hotkey witch use char (for example: ctrl+alt+t for 
terminal or ctrl+t for new tab in browser) become unfunctional when selected 
non-latin keyboard layout.
  Hotkeys with F1-12, numbers and other non-character buttons works perfectly.

  Window manager hotkeys not affected by this bug. All hotkeys in system
  parameters-keyboard-hotkeys-windows works perfect with any keyboard
  layout.

  Workaround for some system hotkeys and two layouts (english and non-
  latin): rebind all hotkeys in your local layout. For example instead
  of ctrl+alt+t use ctrl+alt+τ (greek tau). That hotkey still work with
  english layout.  If you use english and two different non-latin
  layouts this workaround helps only with one of them.


  Dear Ubuntu users and developers! 
  Please include the following information to your comment about non-latin 
shortcuts problems:
  1. What Ubuntu version do you have (Ubuntu 13.10, Ubuntu 13.10 GNOME, Ubuntu 
14.04, Ubuntu 14.04 GNOME and so on), upgraded (describe version) or clean 
installed
  2. What keyboard layout do you have
  3. What shortcut for keyboard layout switching do you use 
  4. On which session you have problems - that is one from Unity, GNOME Shell, 
GNOME FlashBack/Fallback (Metacity), GNOME FlashBack/Fallback (Compiz)
  5. With which program and its version and origin (Ubuntu repositories, PPA, 
non-deb binary package from some website) you have problems.

  By providing this information you can make bug-fixing much simpler and
  may be faster.

  --
  For other layout switching problems introduced in Ubuntu 13.10 you can see 
bug 1218322.
  --

To manage notifications about this bug go to:
https://bugs.launchpad.net/aptana-studio-installer/+bug/1226962/+subscriptions

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

[Desktop-packages] [Bug 1319105] Re: Cisco AM10 no longer switches mode

2014-06-18 Thread Mantas Kriaučiūnas

Please test if your Cisco AM10 valet connector works with new upstream
versions of usb-modeswitch (2.2.0) and usb-modeswitch-data (20140529)
released 2 weeks ago (already packaged in Debian unstable).

You can download new usb-modeswitch and usb-modeswitch-data deb packages from 
here:
https://packages.debian.org/sid/usb-modeswitch
https://packages.debian.org/sid/all/usb-modeswitch-data/download

Please install these usb-modeswitch version 2.2.0+repack0-1 and usb-
modeswitch-data version 20140529-1 packages from Debian unstable (don't
forget to do 'apt-get -f install' to have libjim0.74 installed), reboot
your Ubuntu system and test if your problem with Cisco AM10 valet
connector still occurs with new usb-modeswitch

Lots of other switching related issues (like LP bug #1308895, bug
#1192297) are fixed in updated usb-modeswitch (2.2.0+repack0-1) and usb-
modeswitch-data (20140529-1) packages from Debian unstable.

Here is debian/changelog:

usb-modeswitch (2.2.0+repack0-1) unstable; urgency=medium
  * New 2.2.0 upstream release
- Introduction of parameter HuaweiNewMode, wrapping the standard bulk
  message for all newer Huawei devices;
- Support for generic fallback config files, combined with OS switch (per
  vendor ID);
  * Repack the upstream tarball:
- Drop the code copy of jimtcl.
  * Bump usb-modeswitch-data depends to 20140529
  * Update VCS-* fields to canonical form
 -- Didier Raboud o...@debian.org Mon, 09 Jun 2014 11:21:08 +0200

And here is usb-modeswitch-data debian/changelog: 
http://metadata.ftp-master.debian.org/changelogs/main/u/usb-modeswitch-data/unstable_changelog

** Tags added: regression-release

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to usb-modeswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1319105

Title:
  Cisco AM10 no longer switches mode

Status in “usb-modeswitch” package in Ubuntu:
  New

Bug description:
  My Cisco AM10 valet connector WiFi adaptor

  This worked under Saucy but broke when I upgraded to Trusty.  I've
  attached usb_modeswitch.log obtained from turning debugging on.

  From before the upgrade, I didn't ever run in debugging mode but
  syslog entries looked like:

  syslog.7.gz:May  7 10:08:34 nyantiger usb_modeswitch: switching device 
1307:1169 on 003/025
  syslog.7.gz:May  7 10:08:36 nyantiger usb_modeswitch: switched to 13b1:0031 
on 003/025

  Now there's just:

  syslog:May 13 10:37:24 nyantiger usb_modeswitch: switch device
  1307:1169 on 003/010

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: usb-modeswitch 2.1.1+repack0-1ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  Date: Tue May 13 12:02:54 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-02-02 (100 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Release amd64 
(20131017)
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=screen
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: usb-modeswitch
  UpgradeStatus: Upgraded to trusty on 2014-05-13 (0 days ago)
  mtime.conffile..etc.usb.modeswitch.conf: 2014-05-13T11:51:17.900534

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

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

[Desktop-packages] [Bug 1331418] [NEW] Please update gnome-applets to latest devel version - current Ubuntu version (released 2012-09) has several important bugs fixed in upstream git

2014-06-18 Thread Mantas Kriaučiūnas

Public bug reported:

Please update gnome-applets to latest development version - current
Ubuntu version (3.5.92, released 2012-09) has several bugs fixed in
upstream git, for example upower support instead of HAL, lots of
translation updates, etc, see

https://git.gnome.org/browse/gnome-applets/log/?ofs=50

** Affects: gnome-applets (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  Please update gnome-applets to latest development version - current
  Ubuntu version (3.5.92, released 2012-09) has several bugs fixed in
- upstream git, for example upower support instead of HAL lots of
+ upstream git, for example upower support instead of HAL, lots of
  translation updates, etc, see
  
  https://git.gnome.org/browse/gnome-applets/log/?ofs=50

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-applets in Ubuntu.
https://bugs.launchpad.net/bugs/1331418

Title:
  Please update gnome-applets to latest devel version - current Ubuntu
  version (released 2012-09) has several important bugs fixed in
  upstream git

Status in “gnome-applets” package in Ubuntu:
  New

Bug description:
  Please update gnome-applets to latest development version - current
  Ubuntu version (3.5.92, released 2012-09) has several bugs fixed in
  upstream git, for example upower support instead of HAL, lots of
  translation updates, etc, see

  https://git.gnome.org/browse/gnome-applets/log/?ofs=50

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

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

[Desktop-packages] [Bug 1295207] Re: Migrate to farsight 0.2* / gstreamer 1.0

2014-06-18 Thread Mantas Kriaučiūnas

** Description changed:

  1) Ubuntu 14.04
  2) 1:2.10.9-0ubuntu2
  3) I expect it to depend against the latest farsight/gstreamer 1.0
  4) Instead, it's one of the reasons we still have gstreamer0.10 on the trusty 
cd, through libpurple.
  
- It seems upstream support might be there: 
https://developer.pidgin.im/wiki/Dependencies
- If not, we can track it in this bug.
+ It seems upstream already supports building against farstream-0.2 and 
gstreamer1.0, see:
+ https://developer.pidgin.im/wiki/Dependencies

** Bug watch added: Red Hat Bugzilla #962028
   https://bugzilla.redhat.com/show_bug.cgi?id=962028

** Also affects: pidgin (Fedora) via
   https://bugzilla.redhat.com/show_bug.cgi?id=962028
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pidgin in Ubuntu.
https://bugs.launchpad.net/bugs/1295207

Title:
  Migrate to farsight 0.2* / gstreamer 1.0

Status in “pidgin” package in Ubuntu:
  Confirmed
Status in “pidgin” package in Fedora:
  Unknown

Bug description:
  1) Ubuntu 14.04
  2) 1:2.10.9-0ubuntu2
  3) I expect it to depend against the latest farsight/gstreamer 1.0
  4) Instead, it's one of the reasons we still have gstreamer0.10 on the trusty 
cd, through libpurple.

  It seems upstream already supports building against farstream-0.2 and 
gstreamer1.0, see:
  https://developer.pidgin.im/wiki/Dependencies

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

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

[Desktop-packages] [Bug 1308895] Re: Huawei E3531 does not automatically switches to modem mode (no udev rules for this modem in /lib/udev/rules.d.)

New upstream versions of usb-modeswitch (2.2.0) and usb-modeswitch-data
(20140529) released 2 weeks ago and are already packaged in Debian
unstable!

This Huawei E3531 issue (and lots of other Huawei related issues, like
bug # 1192297) is fixed in updated usb-modeswitch (2.2.0+repack0-1)  and
usb-modeswitch-data (20140529-1) packages in Debian unstable.

Please merge usb-modeswitch 2.2.0+repack0-1 package from Debian unstable to 
Ubuntu Utopic.
Here is debian/changelog:

usb-modeswitch (2.2.0+repack0-1) unstable; urgency=medium
  * New 2.2.0 upstream release
- Introduction of parameter HuaweiNewMode, wrapping the standard bulk
  message for all newer Huawei devices;
- Support for generic fallback config files, combined with OS switch (per
  vendor ID);
  * Repack the upstream tarball:
- Drop the code copy of jimtcl.
  * Bump usb-modeswitch-data depends to 20140529
  * Update VCS-* fields to canonical form
 -- Didier Raboud o...@debian.org  Mon, 09 Jun 2014 11:21:08 +0200

And here is usb-modeswitch-data debian/changelog:

usb-modeswitch-data (20140529-1) unstable; urgency=medium
  * New upstream release
+ New devices
 [0408:f001] SpeedUp SU-8500U
 [04cc:226e] Nexperia TM TD-SCDMA
 [04cc:226f] Nexperia TM TD-SCDMA (Variant)
 [04fc:2140] Sunplus Techn. SU-3200U
 [0b3c:f00c] Olivetti Olicard 500
 [0b3c:f017] Olivetti Olicard 160
 [0bdb:190d] Ericsson F5521gw
 [0bdb:1910] Ericsson F5521gw (Variant)
 [0fce:d0df] Sony Ericsson EC400
 [1410:5055] Novatel MiFi 4082
 [19d2:1232] ZTE MFxxx
 [1c9e:9101] Emobile D21LC (Variant)
 [1c9e:9401] Emobile D21LC
 [1c9e:9d00] Prolink PCM100
 [2020:f00f] SpeedUp SU-8000U
 [23a2:1010] Titan 3.5G
- Substantial change in handling of Huawei devices
- Generic udev rule and additional generic configuration files
  (as fallback for unknown models or as OS-specific catch-all)
  * Bump Recommends/Breaks against usb-modeswitch to 2.2.0
  * Update VCS-* fields to canonical forms
 -- Didier Raboud o...@debian.org  Mon, 09 Jun 2014 11:19:43 +0200

See http://metadata.ftp-master.debian.org/changelogs/main/u/usb-
modeswitch/unstable_changelog and http://metadata.ftp-
master.debian.org/changelogs/main/u/usb-modeswitch-
data/unstable_changelog and

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to usb-modeswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1308895

Title:
  Huawei E3531 does not automatically switches to modem mode (no udev
  rules for this modem in /lib/udev/rules.d.)

Status in “usb-modeswitch” package in Ubuntu:
  Confirmed

Bug description:
  The operating system does not see the modem  maybe because usb-
  modeswitch not automatically switches the device mode the modem.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: usb-modeswitch 2.1.1+repack0-1ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr 17 11:34:11 2014
  InstallationDate: Installed on 2014-04-16 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140415)
  SourcePackage: usb-modeswitch
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1314842] Re: usb_modeswitch not run correctly for 3G dongle

New upstream versions of usb-modeswitch (2.2.0) and usb-modeswitch-data
(20140529) released 2 weeks ago and are already packaged in Debian
unstable!

Lots of other Huawei related issues (like LP bug #1192297) are fixed in
updated usb-modeswitch (2.2.0+repack0-1) and usb-modeswitch-data
(20140529-1) packages in Debian unstable.

Please install usb-modeswitch version 2.2.0+repack0-1 and usb-
modeswitch-data version 20140529-1 packages from Debian unstable, reboot
your Ubuntu system and test if your problem with Huawei 3G dongle still
occurs with new usb-modeswitch

You can download new usb-modeswitch and usb-modeswitch-data from here:
https://packages.debian.org/sid/usb-modeswitch
https://packages.debian.org/sid/all/usb-modeswitch-data/download

Here is debian/changelog:

usb-modeswitch (2.2.0+repack0-1) unstable; urgency=medium
  * New 2.2.0 upstream release
- Introduction of parameter HuaweiNewMode, wrapping the standard bulk
  message for all newer Huawei devices;
- Support for generic fallback config files, combined with OS switch (per
  vendor ID);
  * Repack the upstream tarball:
- Drop the code copy of jimtcl.
  * Bump usb-modeswitch-data depends to 20140529
  * Update VCS-* fields to canonical form
 -- Didier Raboud o...@debian.org Mon, 09 Jun 2014 11:21:08 +0200

And here is usb-modeswitch-data debian/changelog:

usb-modeswitch-data (20140529-1) unstable; urgency=medium
  * New upstream release
+ New devices
 [0408:f001] SpeedUp SU-8500U
 [04cc:226e] Nexperia TM TD-SCDMA
 [04cc:226f] Nexperia TM TD-SCDMA (Variant)
 [04fc:2140] Sunplus Techn. SU-3200U
 [0b3c:f00c] Olivetti Olicard 500
 [0b3c:f017] Olivetti Olicard 160
 [0bdb:190d] Ericsson F5521gw
 [0bdb:1910] Ericsson F5521gw (Variant)
 [0fce:d0df] Sony Ericsson EC400
 [1410:5055] Novatel MiFi 4082
 [19d2:1232] ZTE MFxxx
 [1c9e:9101] Emobile D21LC (Variant)
 [1c9e:9401] Emobile D21LC
 [1c9e:9d00] Prolink PCM100
 [2020:f00f] SpeedUp SU-8000U
 [23a2:1010] Titan 3.5G
- Substantial change in handling of Huawei devices
- Generic udev rule and additional generic configuration files
  (as fallback for unknown models or as OS-specific catch-all)
  * Bump Recommends/Breaks against usb-modeswitch to 2.2.0
  * Update VCS-* fields to canonical forms
 -- Didier Raboud o...@debian.org Mon, 09 Jun 2014 11:19:43 +0200

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to usb-modeswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1314842

Title:
  usb_modeswitch not run correctly for 3G dongle

Status in “usb-modeswitch” package in Ubuntu:
  New

Bug description:
  I am using a laptop (Asus N56VZ) with Ubuntu 14.04 LTS (recently
  upgraded from 12.04 LTS) and until recently none of my 3G USB dongles
  worked (I have a few). Note that the very same problem occurred on
  12.04 and I upgraded early hoping for this issue to go away. It
  didn't.

  After investigation, it seems that usb_modeswitch is't doing its
  magic:

  My test dongle is a Huawei Technologies Co., Ltd.  ID 12d1:14c1

  According to the udev rules and the usb_modeswitch data I could dig
  up, the product ID should switch to 14c6 to make it work correctly.

  A file named 12d1:14c1 IS in the tgz package of usb-modeswitch-data,
  but nonetheless this is all I see in /var/log/syslog when I plug the
  dongle in:

  
===
  May  1 00:44:49 rramondalap02 kernel: [   54.336137] usb 3-1: new high-speed 
USB device number 3 using xhci_hcd
  May  1 00:44:49 rramondalap02 kernel: [   54.354566] usb 3-1: New USB device 
found, idVendor=12d1, idProduct=14c1
  May  1 00:44:49 rramondalap02 kernel: [   54.354570] usb 3-1: New USB device 
strings: Mfr=3, Product=2, SerialNumber=0
  May  1 00:44:49 rramondalap02 kernel: [   54.354571] usb 3-1: Product: 
Vodafone Mobile Broadband (Huawei) 
  May  1 00:44:49 rramondalap02 kernel: [   54.354572] usb 3-1: Manufacturer: 
Vodafone Group (Huawei) 
  May  1 00:44:49 rramondalap02 kernel: [   54.355682] usb-storage 3-1:1.0: USB 
Mass Storage device detected
  May  1 00:44:49 rramondalap02 kernel: [   54.355814] scsi7 : usb-storage 
3-1:1.0
  May  1 00:44:49 rramondalap02 kernel: [   54.355879] usb-storage 3-1:1.1: USB 
Mass Storage device detected
  May  1 00:44:49 rramondalap02 kernel: [   54.355985] scsi8 : usb-storage 
3-1:1.1
  May  1 00:44:49 rramondalap02 mtp-probe: checking bus 3, device 3: 
/sys/devices/pci:00/:00:14.0/usb3/3-1
  May  1 00:44:49 rramondalap02 mtp-probe: bus: 3, device: 3 was not an MTP 
device
  May  1 00:44:50 rramondalap02 kernel: [   55.354598] scsi 7:0:0:0: CD-ROM 
   Vodafone CD ROM (Huawei)  2.31 PQ: 0 ANSI: 2
  May  1 00:44:50 rramondalap02 kernel: [   55.355275] scsi 8:0:0:0: 
Direct-Access Vodafone Storage (Huawei)  PQ: 0 ANSI: 2
  May  1 00:44:50 rramondalap02 kernel: [   55.356963] sr1:

[Desktop-packages] [Bug 1192297] Re: Huawei E3131 mobile modem not recognized

New upstream versions of usb-modeswitch (2.2.0) and usb-modeswitch-data
(20140529) released 2 weeks ago and are already packaged in Debian
unstable!

This Huawei E3131 issue (and lots of other Huawei related issues, like
bug #1308895) is fixed in updated usb-modeswitch (2.2.0+repack0-1) and
usb-modeswitch-data (20140529-1) packages in Debian unstable.

Please merge usb-modeswitch 2.2.0+repack0-1 package from Debian unstable to 
Ubuntu Utopic.
Here is debian/changelog:

usb-modeswitch (2.2.0+repack0-1) unstable; urgency=medium
  * New 2.2.0 upstream release
- Introduction of parameter HuaweiNewMode, wrapping the standard bulk
  message for all newer Huawei devices;
- Support for generic fallback config files, combined with OS switch (per
  vendor ID);
  * Repack the upstream tarball:
- Drop the code copy of jimtcl.
  * Bump usb-modeswitch-data depends to 20140529
  * Update VCS-* fields to canonical form
 -- Didier Raboud o...@debian.org Mon, 09 Jun 2014 11:21:08 +0200

And here is usb-modeswitch-data debian/changelog:
http://metadata.ftp-master.debian.org/changelogs/main/u/usb-modeswitch-data/unstable_changelog

** Changed in: usb-modeswitch-data
   Status: New = Fix Released

** Changed in: usb-modeswitch-data
 Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to usb-modeswitch-data in Ubuntu.
https://bugs.launchpad.net/bugs/1192297

Title:
  Huawei E3131 mobile modem not recognized

Status in Usb Modeswitch Data:
  Fix Released
Status in “usb-modeswitch-data” package in Ubuntu:
  Confirmed
Status in “usb-modeswitch-data” package in Baltix:
  Confirmed

Bug description:
  Modem does not work in 12.04. I heard it does work in 12.10.

  It can be made to work in 12.04 by editing 
/lib/udev/rules.d/40-usb_modeswitch.rules
  adding two lines:

  # Huawei E3131
  ATTRS{idVendor}==12d1, ATTRS{idProduct}==151a, RUN+=usb_modeswitch 
'%b/%k'

  and adding file  /etc/usb_modeswitch.d/12d1:151a
  with contents:

  # HUAWEI E3131 (DNA)

  DefaultVendor=0x12d1
  DefaultProduct=0x151a
  TargetVendor=0x12d1
  TargetProduct=0x14ac

  
MessageContent=55534243123456780a11062100

  
  I copied those file contents from this forum message: 
http://forum.ubuntu-fi.org/index.php?topic=44160.0

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: usb-modeswitch-data 20120120-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-48.74-generic 3.2.46
  Uname: Linux 3.2.0-48-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.3
  Architecture: amd64
  Date: Tue Jun 18 22:03:55 2013
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: usb-modeswitch-data
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/usb-modeswitch-data/+bug/1192297/+subscriptions

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

[Desktop-packages] [Bug 1308895] Re: Please merge usb-modeswitch from Debian unstable - Huawei E3531 does not automatically switches to modem mode (no udev rules for this modem in Ubuntu's /lib/udev/r

** Summary changed:

- Huawei E3531 does not automatically switches to modem mode (no udev rules for 
this modem in /lib/udev/rules.d.)
+ Please merge usb-modeswitch from Debian unstable - Huawei E3531 does not 
automatically switches to modem mode (no udev rules for this modem in Ubuntu's 
/lib/udev/rules.d)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to usb-modeswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1308895

Title:
  Please merge usb-modeswitch from Debian unstable - Huawei E3531 does
  not automatically switches to modem mode (no udev rules for this modem
  in Ubuntu's /lib/udev/rules.d)

Status in “usb-modeswitch” package in Ubuntu:
  Confirmed

Bug description:
  The operating system does not see the modem  maybe because usb-
  modeswitch not automatically switches the device mode the modem.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: usb-modeswitch 2.1.1+repack0-1ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Apr 17 11:34:11 2014
  InstallationDate: Installed on 2014-04-16 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140415)
  SourcePackage: usb-modeswitch
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 997370] Re: Totem does not use the va-api gstreamer backend

2014-06-07 Thread Mantas Kriaučiūnas

If I've gstreamer1.0-vaapi installed in Ubuntu 14.04 Totem thinks it doesn't 
have anything to play h.264 with :(
But when I remove gstreamer1.0-vaapi package this video file plays fine in 
Totem:
https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1290368/+attachment/4095344/+files/4.MTS
 
This issue was noticed also by Ubuntu developer Mirv (Timo Jyrinki AFAIK), see
http://irclogs.ubuntu.com/2014/04/24/%23ubuntu-desktop.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/997370

Title:
  Totem does not use the va-api gstreamer backend

Status in Totem Movie Player:
  Confirmed
Status in “totem” package in Ubuntu:
  Confirmed

Bug description:
  installing gstreamer -vaapi from ubuntu repos breaks thumbnail generation in 
nautilus
  furthermore acceleration does not work in totem - cpu usage is as high as 
with software rendering.

  mplayer-vaapi works perfectly on the same system.

  gst-launch-0.10 -v filesrc location=~/test.mkv ! matroskademux ! vaapidecode 
! vaapisink
  makes it possible to use vaapi via commandline

  i did not find a way to use vaapi for mpeg4 part 2 video streams.

  and i wasnt able to find proper values for gstreamer-properties that
  fix thumbnails and acceleration in totem.

  id like to share debug information. just tell me what you need.

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

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

[Desktop-packages] [Bug 965941] Re: Microphone (web cam's microphone) settings changes after restart

2014-05-29 Thread Mantas Kriaučiūnas

Skirmantai, could you test if this bug still occurs with Ubuntu/Baltix
12.04.4 LTS (with installed all updates)?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/965941

Title:
  Microphone (web cam's microphone) settings changes after restart

Status in “gnome-control-center” package in Ubuntu:
  New
Status in Baltix GNU/Linux:
  New

Bug description:
  It's about Ubuntu 12.04 (precise pangolin).

  I'm using my web cam's microphone, which is Logitech HD Webcam C270
  (http://www.logitech.com/en-gb/webcam-
  communications/webcams/devices/7079).

  The annoying thing is that after some restarts (not each), input
  setting for microphone is changed from C270 web cam's microphone to
  sound card's.

  It's very annoying as Skype should be restarted, so changes would be
  reflected to it's settings.

  I believe that this is related somehow to the fact, that webcam and
  it's microphone is connected via usb - not via sound card's sound
  input.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/965941/+subscriptions

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

[Desktop-packages] [Bug 1192297] Re: Huawei E3131 mobile modem not recognized

2014-05-29 Thread Mantas Kriaučiūnas

** Changed in: usb-modeswitch-data (Baltix)
   Status: New = Confirmed

** Changed in: usb-modeswitch-data (Baltix)
 Assignee: (unassigned) = Mantas Kriaučiūnas (mantas)

** Changed in: usb-modeswitch-data (Baltix)
   Importance: Undecided = Medium

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to usb-modeswitch-data in Ubuntu.
https://bugs.launchpad.net/bugs/1192297

Title:
  Huawei E3131 mobile modem not recognized

Status in Usb Modeswitch Data:
  New
Status in “usb-modeswitch-data” package in Ubuntu:
  Confirmed
Status in “usb-modeswitch-data” package in Baltix:
  Confirmed

Bug description:
  Modem does not work in 12.04. I heard it does work in 12.10.

  It can be made to work in 12.04 by editing 
/lib/udev/rules.d/40-usb_modeswitch.rules
  adding two lines:

  # Huawei E3131
  ATTRS{idVendor}==12d1, ATTRS{idProduct}==151a, RUN+=usb_modeswitch 
'%b/%k'

  and adding file  /etc/usb_modeswitch.d/12d1:151a
  with contents:

  # HUAWEI E3131 (DNA)

  DefaultVendor=0x12d1
  DefaultProduct=0x151a
  TargetVendor=0x12d1
  TargetProduct=0x14ac

  
MessageContent=55534243123456780a11062100

  
  I copied those file contents from this forum message: 
http://forum.ubuntu-fi.org/index.php?topic=44160.0

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: usb-modeswitch-data 20120120-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-48.74-generic 3.2.46
  Uname: Linux 3.2.0-48-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.3
  Architecture: amd64
  Date: Tue Jun 18 22:03:55 2013
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120425)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: usb-modeswitch-data
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/usb-modeswitch-data/+bug/1192297/+subscriptions

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

[Desktop-packages] [Bug 1316383] Re: Vanilla gnome-control-center 3.8

2014-05-18 Thread Mantas Kriaučiūnas

Is it safe to backport this vanilla gnome-control-center 3.8 packages to Ubuntu 
14.04 (Trusty)?
We have several computers with both desktop environments (Unity and GNOME 
Shell) installed - some users prefer GNOME, some - Unity.

Another question - why you packaged gnome-control-center 3.8 not, latest
- 3.10 or 3.12 versions? Ubuntu 14.04 and 14.10 currently has GNOME
3.10, not 3.8

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1316383

Title:
  Vanilla gnome-control-center 3.8

Status in “gnome-control-center” package in Ubuntu:
  Fix Released

Bug description:
  This was supposed to land last cycle but it slipped through the
  cracks.

  It updates gnome-control-center to 3.8 and drop all unity specific
  hacks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1316383/+subscriptions

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

[Desktop-packages] [Bug 1250868] Re: [FFe] Please update gnome-control-center to latest stable version 3.10

2014-05-18 Thread Mantas Kriaučiūnas

Gnome-Control-Center 3.8 was uploaded to Ubuntu Utopic a week ago, see LP bug 
#1316383
Still don't understand why g-c-c 3.10 (or 3.12) isn't uploaded and even 
unstable Ubuntu Utopic release has 1 year old Gnome-Control-Center 3.8 :(

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1250868

Title:
  [FFe] Please update gnome-control-center to latest stable version 3.10

Status in “gnome-control-center” package in Ubuntu:
  Triaged

Bug description:
  The most recent version of gnome-control-center is 1:3.6.3-0ubuntu54

  While the latest stable version of gnome-shell is 3.10

  This causes several reported and unexpected bugs :(

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1250868/+subscriptions

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

[Desktop-packages] [Bug 1316383] Re: Vanilla gnome-control-center 3.8

2014-05-18 Thread Mantas Kriaučiūnas

There is a request, reported 6 months ago, for updating gnome-control-
center to version 3.10, see bug #1250868

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1316383

Title:
  Vanilla gnome-control-center 3.8

Status in “gnome-control-center” package in Ubuntu:
  Fix Released

Bug description:
  This was supposed to land last cycle but it slipped through the
  cracks.

  It updates gnome-control-center to 3.8 and drop all unity specific
  hacks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1316383/+subscriptions

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

[Desktop-packages] [Bug 1261608] Re: [FFe] Update GNOME System Monitor to 3.10.2-2 or sync latest 3.12.0-1 release from Debian testing

2014-05-02 Thread Mantas Kriaučiūnas

I've installed gnome-system-monitor version 3.10.2-0ubuntu1~trusty1 from
ppa:gnome3-team/gnome3
(https://launchpad.net/~gnome3-team/+archive/gnome3/) and didn't noticed
any problems in few weeks.

Why Ubuntu Unicorn and Trusty still has old and buggy gnome-system-
monitor 3.8 ?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-system-monitor in Ubuntu.
https://bugs.launchpad.net/bugs/1261608

Title:
  [FFe] Update GNOME System Monitor to 3.10.2-2 or sync latest 3.12.0-1
  release from Debian testing

Status in “gnome-system-monitor” package in Ubuntu:
  Triaged

Bug description:
  Please update GNOME System Monitor to 3.10.2 - this release contains
  important bugfixes, for example LP bug #93847 (Excessive CPU usage by
  Gnome System Monitor) or sync latest 3.12.0-1 release from Debian
  testing - see debian/changelog:

  gnome-system-monitor (3.12.0-1) unstable; urgency=medium

* New upstream release.
* Drop debian/patches/01-fix_ftbfs_hurd.patch, merged upstream.

   -- Andreas Henriksson andr...@fatal.se  Mon, 24 Mar 2014 22:33:35
  +0100

  gnome-system-monitor (3.11.90-1) experimental; urgency=medium

* New upstream release.

   -- Andreas Henriksson andr...@fatal.se  Mon, 17 Feb 2014 22:12:59
  +0100

  gnome-system-monitor (3.10.2-2) unstable; urgency=medium

* Upload to unstable
* debian/patches/01-fix_ftbfs_hurd.patch: Fix FTBFS on hurd-i386
  (Closes: #738280)
* Only enable systemd-logind support on linux architectures

   -- Laurent Bigonville bi...@debian.org  Sun, 16 Feb 2014 13:05:55
  +0100

  gnome-system-monitor (3.10.2-1) experimental; urgency=low

* New upstream release.
  - Drop debian/patches/01-kfreebsd-define.patch: Applied upstream
  - debian/control.in: Bump build-dependencies
* debian/control.in:
  - Bump Standards-Version to 3.9.5 (no further changes)
  - Add dependency against libsystemd-login-dev (= 44)
* debian/rules: Explicitly pass --enable-wnck and --enable-systemd to the
  configure

   -- Laurent Bigonville bi...@debian.org  Sat, 14 Dec 2013 16:17:43
  +0100

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1261608/+subscriptions

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

[Desktop-packages] [Bug 1261608] Re: [FFe] Update GNOME System Monitor to 3.10.2-2 or sync latest 3.12.0-1 release from Debian testing

2014-05-02 Thread Mantas Kriaučiūnas

gnome-system-monitor 3.8 has several bugs, some are already reported in 
Launchpad, see for example 
LP bug #1174197 (gnome-system-monitor freezes when reordering columns in procs 
view), also 
LP bug #93847 (Excessive CPU usage by Gnome System Monitor)

Btw, are you 100% sure, that 3.10 and 3.12 releases doesn't work
correctly in other desktop environments than GNOME-Shell?

Sebastien Bacher (seb128) wrote 45 minutes ago:
 @Mantas: how is 3.8 buggy?
 The reason why 3.10 is not used has been stated in previous comment, it uses 
 widgets that correctly only under gnome-shell and would be buggy/a 
 regressions for users from other desktop environments

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-system-monitor in Ubuntu.
https://bugs.launchpad.net/bugs/1261608

Title:
  [FFe] Update GNOME System Monitor to 3.10.2-2 or sync latest 3.12.0-1
  release from Debian testing

Status in “gnome-system-monitor” package in Ubuntu:
  Triaged

Bug description:
  Please update GNOME System Monitor to 3.10.2 - this release contains
  important bugfixes, for example LP bug #93847 (Excessive CPU usage by
  Gnome System Monitor) or sync latest 3.12.0-1 release from Debian
  testing - see debian/changelog:

  gnome-system-monitor (3.12.0-1) unstable; urgency=medium

* New upstream release.
* Drop debian/patches/01-fix_ftbfs_hurd.patch, merged upstream.

   -- Andreas Henriksson andr...@fatal.se  Mon, 24 Mar 2014 22:33:35
  +0100

  gnome-system-monitor (3.11.90-1) experimental; urgency=medium

* New upstream release.

   -- Andreas Henriksson andr...@fatal.se  Mon, 17 Feb 2014 22:12:59
  +0100

  gnome-system-monitor (3.10.2-2) unstable; urgency=medium

* Upload to unstable
* debian/patches/01-fix_ftbfs_hurd.patch: Fix FTBFS on hurd-i386
  (Closes: #738280)
* Only enable systemd-logind support on linux architectures

   -- Laurent Bigonville bi...@debian.org  Sun, 16 Feb 2014 13:05:55
  +0100

  gnome-system-monitor (3.10.2-1) experimental; urgency=low

* New upstream release.
  - Drop debian/patches/01-kfreebsd-define.patch: Applied upstream
  - debian/control.in: Bump build-dependencies
* debian/control.in:
  - Bump Standards-Version to 3.9.5 (no further changes)
  - Add dependency against libsystemd-login-dev (= 44)
* debian/rules: Explicitly pass --enable-wnck and --enable-systemd to the
  configure

   -- Laurent Bigonville bi...@debian.org  Sat, 14 Dec 2013 16:17:43
  +0100

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1261608/+subscriptions

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

[Desktop-packages] [Bug 118935] Re: [Upstream] [hardy] Writer page numbering offset not working

2014-04-28 Thread Mantas Kriaučiūnas

It seems there are no intuitive way to insert page numbers into text document 
with different starting number :(  
Official WORKAROUND (Format - Paragraph - Text Flow tab - Insert checkbox 
checked - With Page Style checkbox checked - Page number combobox) is not 
designed for users...

How we can help to fix this important problem?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/118935

Title:
  [Upstream] [hardy] Writer page numbering offset not working

Status in LibreOffice Productivity Suite:
  Invalid
Status in The OpenOffice.org Suite:
  Confirmed
Status in “libreoffice” package in Ubuntu:
  Invalid
Status in “openoffice.org” package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: openoffice.org
  1) lsb_release -rd
  Description:  Ubuntu 11.04
  Release:  11.04

  2) apt-cache policy libreoffice-writer
  libreoffice-writer:
Installed: 1:3.3.2-1ubuntu5
Candidate: 1:3.3.2-1ubuntu5
Version table:
   *** 1:3.3.2-1ubuntu5 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   1:3.3.2-1ubuntu4 0
  500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages

  3) What is expected to happen in Writer is when one clicks Insert -
  Field - Page Numbers - double click page number - change offset
  from 0 to 6 - OK button

  -OR-

  Insert - Field - Other - Page - Page Numbers - Offset 6 - Insert
  button

  it shows the first Page Number object with 6 inside.

  4) What happens instead is it shows a blank object.

  WORKAROUND: click Format - Paragraph - Text Flow tab - Insert
  checkbox checked - With Page Style checkbox checked - Page number
  combobox 6 - OK button

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/118935/+subscriptions

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

[Desktop-packages] [Bug 1263591] Re: Add notification-area to panel-default-layout.layout

2014-04-24 Thread Mantas Kriaučiūnas

** Changed in: gnome-panel (Baltix)
   Importance: Undecided = Medium

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-panel in Ubuntu.
https://bugs.launchpad.net/bugs/1263591

Title:
  Add notification-area to panel-default-layout.layout

Status in “gnome-panel” package in Ubuntu:
  Won't Fix
Status in “gnome-panel” package in Baltix:
  Confirmed

Bug description:
  Upstream gnome-panel includes notification-area:
  
https://git.gnome.org/browse/gnome-panel/plain/data/panel-default-layout.layout

  In Ubuntu, debian/patches/01_layout.patch changes that file in order to make 
use of indicator-applet-complete. That patch is Ubuntu-specific, it doesn't 
exist in Debian:
  
http://anonscm.debian.org/viewvc/pkg-gnome/desktop/unstable/gnome-panel/debian/patches/

  The problem is that that patch also removes notification-area, so
  applications like pidgin, stardict etc (and even nm-applet in Trusty)
  don't show up at all.

  Please modify that patch so that notification-area is not removed,
  i.e. add the following lines to it:

  [Object notification-area]
  object-iid=NotificationAreaAppletFactory::NotificationArea
  toplevel-id=top-panel
  pack-type=end
  pack-index=1

  I'm attaching an updated 41_classic_layout.patch.

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

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

[Desktop-packages] [Bug 1241284] Re: gnome-settings-daemon has problems recognizing the layout switching shortcut

2014-04-24 Thread Mantas Kriaučiūnas

** Also affects: gnome-settings-daemon (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1241284

Title:
  gnome-settings-daemon has problems recognizing the layout switching
  shortcut

Status in Indicator keyboard:
  Invalid
Status in “gnome-settings-daemon” package in Ubuntu:
  Confirmed
Status in “indicator-keyboard” package in Ubuntu:
  Invalid
Status in “unity-settings-daemon” package in Ubuntu:
  Confirmed

Bug description:
  After the upgrade to Ubuntu 13.10, I notice the iBus(or indicator-keyboard 
I'm not sure) does not recognize the keyboard shortcut.
  After some trying, I find that iBus change the way it recognize the keyboard 
shortcut in an really strict way.

  Suppose, I use Ctrl+Space for keyboard shortcut for iBus.
  In order to make iBus recognizing the keyboard shortcut,
  I must do following key sequence.

  1. Press down Ctrl.
  2. Press down Space.
  3. Release Space

  If, for example, after the step 2, released Ctrl before the release of
  Space, iBus doesn't recognize the keyboard shortcut regardless of how
  many seconds you press down both Ctrl and Space.

  This change is so inconvenient for me as I have to constantly switching 
between English and Japanese(Mozc) while typing text.
  (Unification of Keyboard Layout and IME is really bad idea, but that's 
another story.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-keyboard/+bug/1241284/+subscriptions

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

[Desktop-packages] [Bug 873370] Re: [Lenovo ThinkPad T60, Analog Devices AD1981] Sound playback distorted, especially when moving cursor with trackpoint, touchpad, or mouse

ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  ubuntu 2469 F pulseaudio
CasperVersion: 1.340
CurrentDesktop: Unity
DistroRelease: Ubuntu 14.04
LiveMediaBuild: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
Package: alsa-driver (not installed)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=lt_LT.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Tags:  trusty
Uname: Linux 3.13.0-24-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 04/01/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 7IET37WW (1.18 )
dmi.board.name: 8744HDG
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr7IET37WW(1.18):bd04/01/2010:svnLENOVO:pn8744HDG:pvrThinkPadT60:rvnLENOVO:rn8744HDG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 8744HDG
dmi.product.version: ThinkPad T60
dmi.sys.vendor: LENOVO


** Tags added: apport-collected trusty

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/873370

Title:
  [Lenovo ThinkPad T60, Analog Devices AD1981] Sound playback distorted,
  especially when moving cursor with trackpoint, touchpad, or mouse

Status in “alsa-driver” package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 11.10, clean install, Thinkpad t60 [200772U]
  Sound worked properly with good output in 11.04.
  In 11.10, sound playback is distorted, with noisy clicks and 'burps.' The 
problem is worse when I move the mouse cursor by any method, including 
trackpoint or touchpad. I am not using a wireless mouse. I have installed 
ubuntu-restricted-extras. Sound is distorted using Banshee, VLC, Movie Player 
to play back .mp3 or .ogg. Audio quality from Youtube is similarly affected. 

  Will happily post additional troubleshooting info.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: alsa-base 1.0.24+dfsg-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu3
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kolin  1499 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xee40 irq 47'
 Mixer name : 'Analog Devices AD1981'
 Components : 'HDA:11d41981,17aa2025,00100200'
 Controls  : 20
 Simple ctrls  : 11
  Card29.Amixer.info:
   Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 
79HT50WW-1.07'
 Mixer name : 'ThinkPad EC 79HT50WW-1.07'
 Components : ''
 Controls  : 2
 Simple ctrls  : 1
  Card29.Amixer.values:
   Simple mixer control 'Console',0
 Capabilities: pvolume pvolume-joined pswitch pswitch-joined penum
 Playback channels: Mono
 Limits: Playback 0 - 14
 Mono: Playback 6 [43%] [on]
  Date: Thu Oct 13 16:06:23 2011
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111011)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Internal Audio - HDA Intel
  Symptom_Jack: Green Line Out, Left
  Symptom_Type: Digital clip or distortion, or overdriven sound
  Title: [200772U, Analog Devices AD1981, Green Line Out, Left] Sound is 
distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/12/2008
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 79ETE3WW (2.23 )
  dmi.board.name: 200772U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr79ETE3WW(2.23):bd09/12/2008:svnLENOVO:pn200772U:pvrThinkPadT60:rvnLENOVO:rn200772U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 200772U
  dmi.product.version: ThinkPad T60
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 873370] AlsaInfo.txt

apport information

** Attachment added: AlsaInfo.txt
   
https://bugs.launchpad.net/bugs/873370/+attachment/4088488/+files/AlsaInfo.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/873370

Title:
  [Lenovo ThinkPad T60, Analog Devices AD1981] Sound playback distorted,
  especially when moving cursor with trackpoint, touchpad, or mouse

Status in “alsa-driver” package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 11.10, clean install, Thinkpad t60 [200772U]
  Sound worked properly with good output in 11.04.
  In 11.10, sound playback is distorted, with noisy clicks and 'burps.' The 
problem is worse when I move the mouse cursor by any method, including 
trackpoint or touchpad. I am not using a wireless mouse. I have installed 
ubuntu-restricted-extras. Sound is distorted using Banshee, VLC, Movie Player 
to play back .mp3 or .ogg. Audio quality from Youtube is similarly affected. 

  Will happily post additional troubleshooting info.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: alsa-base 1.0.24+dfsg-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu3
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kolin  1499 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xee40 irq 47'
 Mixer name : 'Analog Devices AD1981'
 Components : 'HDA:11d41981,17aa2025,00100200'
 Controls  : 20
 Simple ctrls  : 11
  Card29.Amixer.info:
   Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 
79HT50WW-1.07'
 Mixer name : 'ThinkPad EC 79HT50WW-1.07'
 Components : ''
 Controls  : 2
 Simple ctrls  : 1
  Card29.Amixer.values:
   Simple mixer control 'Console',0
 Capabilities: pvolume pvolume-joined pswitch pswitch-joined penum
 Playback channels: Mono
 Limits: Playback 0 - 14
 Mono: Playback 6 [43%] [on]
  Date: Thu Oct 13 16:06:23 2011
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111011)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Internal Audio - HDA Intel
  Symptom_Jack: Green Line Out, Left
  Symptom_Type: Digital clip or distortion, or overdriven sound
  Title: [200772U, Analog Devices AD1981, Green Line Out, Left] Sound is 
distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/12/2008
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 79ETE3WW (2.23 )
  dmi.board.name: 200772U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr79ETE3WW(2.23):bd09/12/2008:svnLENOVO:pn200772U:pvrThinkPadT60:rvnLENOVO:rn200772U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 200772U
  dmi.product.version: ThinkPad T60
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 873370] BootDmesg.txt

apport information

** Attachment added: BootDmesg.txt
   
https://bugs.launchpad.net/bugs/873370/+attachment/4088489/+files/BootDmesg.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/873370

Title:
  [Lenovo ThinkPad T60, Analog Devices AD1981] Sound playback distorted,
  especially when moving cursor with trackpoint, touchpad, or mouse

Status in “alsa-driver” package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 11.10, clean install, Thinkpad t60 [200772U]
  Sound worked properly with good output in 11.04.
  In 11.10, sound playback is distorted, with noisy clicks and 'burps.' The 
problem is worse when I move the mouse cursor by any method, including 
trackpoint or touchpad. I am not using a wireless mouse. I have installed 
ubuntu-restricted-extras. Sound is distorted using Banshee, VLC, Movie Player 
to play back .mp3 or .ogg. Audio quality from Youtube is similarly affected. 

  Will happily post additional troubleshooting info.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: alsa-base 1.0.24+dfsg-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu3
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kolin  1499 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xee40 irq 47'
 Mixer name : 'Analog Devices AD1981'
 Components : 'HDA:11d41981,17aa2025,00100200'
 Controls  : 20
 Simple ctrls  : 11
  Card29.Amixer.info:
   Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 
79HT50WW-1.07'
 Mixer name : 'ThinkPad EC 79HT50WW-1.07'
 Components : ''
 Controls  : 2
 Simple ctrls  : 1
  Card29.Amixer.values:
   Simple mixer control 'Console',0
 Capabilities: pvolume pvolume-joined pswitch pswitch-joined penum
 Playback channels: Mono
 Limits: Playback 0 - 14
 Mono: Playback 6 [43%] [on]
  Date: Thu Oct 13 16:06:23 2011
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111011)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Internal Audio - HDA Intel
  Symptom_Jack: Green Line Out, Left
  Symptom_Type: Digital clip or distortion, or overdriven sound
  Title: [200772U, Analog Devices AD1981, Green Line Out, Left] Sound is 
distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/12/2008
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 79ETE3WW (2.23 )
  dmi.board.name: 200772U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr79ETE3WW(2.23):bd09/12/2008:svnLENOVO:pn200772U:pvrThinkPadT60:rvnLENOVO:rn200772U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 200772U
  dmi.product.version: ThinkPad T60
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 873370] PulseList.txt

apport information

** Attachment added: PulseList.txt
   
https://bugs.launchpad.net/bugs/873370/+attachment/4088491/+files/PulseList.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/873370

Title:
  [Lenovo ThinkPad T60, Analog Devices AD1981] Sound playback distorted,
  especially when moving cursor with trackpoint, touchpad, or mouse

Status in “alsa-driver” package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 11.10, clean install, Thinkpad t60 [200772U]
  Sound worked properly with good output in 11.04.
  In 11.10, sound playback is distorted, with noisy clicks and 'burps.' The 
problem is worse when I move the mouse cursor by any method, including 
trackpoint or touchpad. I am not using a wireless mouse. I have installed 
ubuntu-restricted-extras. Sound is distorted using Banshee, VLC, Movie Player 
to play back .mp3 or .ogg. Audio quality from Youtube is similarly affected. 

  Will happily post additional troubleshooting info.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: alsa-base 1.0.24+dfsg-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu3
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kolin  1499 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xee40 irq 47'
 Mixer name : 'Analog Devices AD1981'
 Components : 'HDA:11d41981,17aa2025,00100200'
 Controls  : 20
 Simple ctrls  : 11
  Card29.Amixer.info:
   Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 
79HT50WW-1.07'
 Mixer name : 'ThinkPad EC 79HT50WW-1.07'
 Components : ''
 Controls  : 2
 Simple ctrls  : 1
  Card29.Amixer.values:
   Simple mixer control 'Console',0
 Capabilities: pvolume pvolume-joined pswitch pswitch-joined penum
 Playback channels: Mono
 Limits: Playback 0 - 14
 Mono: Playback 6 [43%] [on]
  Date: Thu Oct 13 16:06:23 2011
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111011)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Internal Audio - HDA Intel
  Symptom_Jack: Green Line Out, Left
  Symptom_Type: Digital clip or distortion, or overdriven sound
  Title: [200772U, Analog Devices AD1981, Green Line Out, Left] Sound is 
distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/12/2008
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 79ETE3WW (2.23 )
  dmi.board.name: 200772U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr79ETE3WW(2.23):bd09/12/2008:svnLENOVO:pn200772U:pvrThinkPadT60:rvnLENOVO:rn200772U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 200772U
  dmi.product.version: ThinkPad T60
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 873370] CurrentDmesg.txt

apport information

** Attachment added: CurrentDmesg.txt
   
https://bugs.launchpad.net/bugs/873370/+attachment/4088490/+files/CurrentDmesg.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/873370

Title:
  [Lenovo ThinkPad T60, Analog Devices AD1981] Sound playback distorted,
  especially when moving cursor with trackpoint, touchpad, or mouse

Status in “alsa-driver” package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 11.10, clean install, Thinkpad t60 [200772U]
  Sound worked properly with good output in 11.04.
  In 11.10, sound playback is distorted, with noisy clicks and 'burps.' The 
problem is worse when I move the mouse cursor by any method, including 
trackpoint or touchpad. I am not using a wireless mouse. I have installed 
ubuntu-restricted-extras. Sound is distorted using Banshee, VLC, Movie Player 
to play back .mp3 or .ogg. Audio quality from Youtube is similarly affected. 

  Will happily post additional troubleshooting info.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: alsa-base 1.0.24+dfsg-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu3
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kolin  1499 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xee40 irq 47'
 Mixer name : 'Analog Devices AD1981'
 Components : 'HDA:11d41981,17aa2025,00100200'
 Controls  : 20
 Simple ctrls  : 11
  Card29.Amixer.info:
   Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 
79HT50WW-1.07'
 Mixer name : 'ThinkPad EC 79HT50WW-1.07'
 Components : ''
 Controls  : 2
 Simple ctrls  : 1
  Card29.Amixer.values:
   Simple mixer control 'Console',0
 Capabilities: pvolume pvolume-joined pswitch pswitch-joined penum
 Playback channels: Mono
 Limits: Playback 0 - 14
 Mono: Playback 6 [43%] [on]
  Date: Thu Oct 13 16:06:23 2011
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111011)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Internal Audio - HDA Intel
  Symptom_Jack: Green Line Out, Left
  Symptom_Type: Digital clip or distortion, or overdriven sound
  Title: [200772U, Analog Devices AD1981, Green Line Out, Left] Sound is 
distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/12/2008
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 79ETE3WW (2.23 )
  dmi.board.name: 200772U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr79ETE3WW(2.23):bd09/12/2008:svnLENOVO:pn200772U:pvrThinkPadT60:rvnLENOVO:rn200772U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 200772U
  dmi.product.version: ThinkPad T60
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 873370] Re: [Lenovo ThinkPad T60, Analog Devices AD1981] Sound playback distorted, especially when moving cursor with trackpoint, touchpad, or mouse

I think this Lenovo ThinkPad T60 sound bug is a duplicate of bug #879790 and 
should be assigned to xserver-xorg-driver-radeon, because there are no audio 
playing problems in Unity 2D on Ubuntu 12.04.3, I have fixed this problem by 
switching to Unity 2D, see 
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/879790/comments/112

** Changed in: alsa-driver (Ubuntu)
   Status: Incomplete = Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/873370

Title:
  [Lenovo ThinkPad T60, Analog Devices AD1981] Sound playback distorted,
  especially when moving cursor with trackpoint, touchpad, or mouse

Status in “alsa-driver” package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 11.10, clean install, Thinkpad t60 [200772U]
  Sound worked properly with good output in 11.04.
  In 11.10, sound playback is distorted, with noisy clicks and 'burps.' The 
problem is worse when I move the mouse cursor by any method, including 
trackpoint or touchpad. I am not using a wireless mouse. I have installed 
ubuntu-restricted-extras. Sound is distorted using Banshee, VLC, Movie Player 
to play back .mp3 or .ogg. Audio quality from Youtube is similarly affected. 

  Will happily post additional troubleshooting info.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: alsa-base 1.0.24+dfsg-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu3
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kolin  1499 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xee40 irq 47'
 Mixer name : 'Analog Devices AD1981'
 Components : 'HDA:11d41981,17aa2025,00100200'
 Controls  : 20
 Simple ctrls  : 11
  Card29.Amixer.info:
   Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 
79HT50WW-1.07'
 Mixer name : 'ThinkPad EC 79HT50WW-1.07'
 Components : ''
 Controls  : 2
 Simple ctrls  : 1
  Card29.Amixer.values:
   Simple mixer control 'Console',0
 Capabilities: pvolume pvolume-joined pswitch pswitch-joined penum
 Playback channels: Mono
 Limits: Playback 0 - 14
 Mono: Playback 6 [43%] [on]
  Date: Thu Oct 13 16:06:23 2011
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111011)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Internal Audio - HDA Intel
  Symptom_Jack: Green Line Out, Left
  Symptom_Type: Digital clip or distortion, or overdriven sound
  Title: [200772U, Analog Devices AD1981, Green Line Out, Left] Sound is 
distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/12/2008
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 79ETE3WW (2.23 )
  dmi.board.name: 200772U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr79ETE3WW(2.23):bd09/12/2008:svnLENOVO:pn200772U:pvrThinkPadT60:rvnLENOVO:rn200772U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 200772U
  dmi.product.version: ThinkPad T60
  dmi.sys.vendor: LENOVO

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

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

[Desktop-packages] [Bug 682788] Re: Improve Unity Global Menu

2014-04-18 Thread Mantas Kriaučiūnas

** Changed in: baltix
   Importance: Undecided = Medium

** Changed in: baltix
 Assignee: (unassigned) = Mantas Kriaučiūnas (mantas)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/682788

Title:
  Improve Unity Global Menu

Status in Ayatana Design:
  Fix Committed
Status in Compiz:
  Invalid
Status in Unity:
  Fix Released
Status in “unity” package in Ubuntu:
  Triaged
Status in “unity-control-center” package in Ubuntu:
  Triaged
Status in Baltix GNU/Linux:
  Confirmed

Bug description:
  ===+++ _ ! ALL USERS ! _ +++===
  ===+++ READ THIS BEFORE MAKING A COMMENT OR MODIFICATION +++===

  IMPORTANT 1: Please don't post any me too message; use the Does
  this bug affect you? feature you can find a bit above this bug
  description on Launchpad.

  IMPORTANT 2: Do not post anything if you haven't read all comments to
  verify that your point hasn't been made. If you feel tempted to stop
  reading because there are too many messages, that is a strong
  indicator that you shouldn't add even more comments. Developers have a
  tough time to find anything if you post redundant stuff. So please
  abstain from doing that.

  =
  Global menu in general (not only in Unity) is very unergonomic on large 
screens (see the attached screenshot) because if you have a small window 
somewhere near the low right corner you have to move the cursor all the way up 
to to panel to reach the menu. I understand why the global menu was used for 
the netbook edition (it saves space and most windows are maximized), but since 
Unity is intended to be for the desktop edition there should be an option to 
switch to the traditional position of the app menu. It would be welcomed by 
many desktop users. Please try to find a solution for it that works.

  A commonly suggested solution is:
   [ ] Global Menu on
   [ ] Global Menu off
   [ ] Global Menu only for maximized windows
  The default is usually suggested as either the first (on) or last (on only 
for maximized windows).

  -
  Desired change:

  Implement the 'Enhanced Menu' project for 12.10.  This project will
  address the issue described in this bug and also issues described in
  the duplicates of this bus.  Note this is the 'official' bug that
  tracks the implementation of this project.

  The following options will be added to 'System Settings/Appearance':

  ---
  Menus
  Location:Global/Local
  Visibility:  Hidden/Always displayed
  ---

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

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

[Desktop-packages] [Bug 682788] Re: Improve Unity Global Menu

2014-04-18 Thread Mantas Kriaučiūnas

I can't find any dconf (gsettings) setting to make the menu permanently
visible in Ubuntu 14.04 (Unity 7.2.0+14.04.20140416) :(

Marco Trevisan, it seems you forgot to add dconf setting to make the
menu permanently visible, right?

Aleve Sicofante (sicofante) wrote on 2014-04-02:
Here's my proposal:
http://blog.3v1n0.net/informatica/linux/ubuntu-introducing-locally-integrated-menus-to-unity-7/?utm_source=twitterfeedutm_medium=twitter#comment-1270843203
(there's a pretty interesting talk in the comments at that Marco's post)
While it probably is too late to put the title on the screen top bar and the
menu permanently visible on the
window title bar, Marco said he would put some gconf/dconf setting to make
the menu permanently visible.

--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/682788

Title:
Improve Unity Global Menu

Status in Ayatana Design:
Fix Committed
Status in Compiz:
Invalid
Status in Unity:
Fix Released
Status in “unity” package in Ubuntu:
Triaged
Status in “unity-control-center” package in Ubuntu:
Triaged
Status in Baltix GNU/Linux:
Confirmed

Bug description:
===+++ _ ! ALL USERS ! _ +++===
===+++ READ THIS BEFORE MAKING A COMMENT OR MODIFICATION +++===

IMPORTANT 1: Please don't post any me too message; use the Does
this bug affect you? feature you can find a bit above this bug
description on Launchpad.

IMPORTANT 2: Do not post anything if you haven't read all comments to
verify that your point hasn't been made. If you feel tempted to stop
reading because there are too many messages, that is a strong
indicator that you shouldn't add even more comments. Developers have a
tough time to find anything if you post redundant stuff. So please
abstain from doing that.

=
Global menu in general (not only in Unity) is very unergonomic on large
screens (see the attached screenshot) because if you have a small window
somewhere near the low right corner you have to move the cursor all the way up
to to panel to reach the menu. I understand why the global menu was used for
the netbook edition (it saves space and most windows are maximized), but since
Unity is intended to be for the desktop edition there should be an option to
switch to the traditional position of the app menu. It would be welcomed by
many desktop users. Please try to find a solution for it that works.

A commonly suggested solution is:
[ ] Global Menu on
[ ] Global Menu off
[ ] Global Menu only for maximized windows
The default is usually suggested as either the first (on) or last (on only
for maximized windows).

-
Desired change:

Implement the 'Enhanced Menu' project for 12.10. This project will
address the issue described in this bug and also issues described in
the duplicates of this bus. Note this is the 'official' bug that
tracks the implementation of this project.

The following options will be added to 'System Settings/Appearance':

---
Menus
Location:Global/Local
Visibility: Hidden/Always displayed
---

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

[Desktop-packages] [Bug 841046] Re: GNOME3 misses an option to change the mouse pointer

** Changed in: baltix
   Status: New = Triaged

** Changed in: baltix
   Importance: Undecided = Medium

** Changed in: baltix
 Assignee: (unassigned) = Mantas Kriaučiūnas (mantas)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/841046

Title:
  GNOME3 misses an option to change the mouse pointer

Status in GNOME Control Center:
  New
Status in “gnome-control-center” package in Ubuntu:
  Triaged
Status in Baltix GNU/Linux:
  Triaged

Bug description:
  In the previous Ubuntu versions, it was possible to choose a mouse
  pointer to use with a theme. It also allowed you to set the mouse
  pointer size.

  I can no longer find this option in Ubuntu 11.10 (development branch).
  Version of gnome-control-center: 1:3.1.90-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/841046/+subscriptions

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

[Desktop-packages] [Bug 841046] Re: GNOME3 misses an option to change the mouse pointer

** Also affects: unity-control-center (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/841046

Title:
  GNOME3 misses an option to change the mouse pointer

Status in GNOME Control Center:
  New
Status in “gnome-control-center” package in Ubuntu:
  Triaged
Status in “unity-control-center” package in Ubuntu:
  New
Status in Baltix GNU/Linux:
  Triaged

Bug description:
  In the previous Ubuntu versions, it was possible to choose a mouse
  pointer to use with a theme. It also allowed you to set the mouse
  pointer size.

  I can no longer find this option in Ubuntu 11.10 (development branch).
  Version of gnome-control-center: 1:3.1.90-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/841046/+subscriptions

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

[Desktop-packages] [Bug 1299912] Re: Ubuntu 14.04 report as 13.10

Isn't this bug a duplicate of bug #1281155 ?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1299912

Title:
   Ubuntu 14.04 report as 13.10

Status in Ubuntu GNOME:
  New
Status in “gnome-control-center” package in Ubuntu:
  New

Bug description:
  aaron@mac-the-knife:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Trusty Tahr (development branch)
  Release:  14.04
  Codename: trusty

  aaron@mac-the-knife:~$ apt-cache policy gnome-control-center
  gnome-control-center:
Installed: 1:3.6.3-0ubuntu54
Candidate: 1:3.6.3-0ubuntu54
Version table:
   *** 1:3.6.3-0ubuntu54 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  100 /var/lib/dpkg/status

  
  In the Details section of the System Settings it shows 14.04 as 13.10. It 
also should be the Ubuntu GNOME icon and not Ubuntu's icon.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: gnome-control-center 1:3.6.3-0ubuntu54
  ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
  Uname: Linux 3.13.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Mar 30 16:55:41 2014
  InstallationDate: Installed on 2014-03-28 (2 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Release amd64 
(20131017)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to trusty on 2014-03-29 (1 days ago)
  usr_lib_gnome-control-center: deja-dup 30.0-0ubuntu2

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

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

[Desktop-packages] [Bug 841046] Re: Unity GNOME3 misses an option to change the mouse pointer size color