[Desktop-packages] [Bug 1884299] Re: Snaps don't run with NFS home on AutoFS

2022-11-12 Thread Oleg Davydov
I ran into a similar issue when trying to use sshfs-mounted profile for
firefox.

My setup:

$ mkdir .remote
$ sshfs  .remote -o idmap=user
$ ln -s .remote/snap

So now /home/ubuntu/snap is a symlink to a directory
/home/ubuntu/.remote/snap. When trying to run firefox, it fails with:

$ firefox
cannot create user data directory: /home/ubuntu/snap/firefox/1232: Not a 
directory

Which is confusing, as /home/ubuntu/snap/firefox/1232 is a directory.
Trying to strace what's going on (details in
https://pastebin.com/gbeHV8L1) I found out that firefox (or snap) is
confused that snap is a symlink to directory, not a directory by itself
(and this limitation doesn't makes sense to me, looks like just
implementation flaw of creating user directory).

Not sure if this is related to the above, but experience is similar.

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

Title:
  Snaps don't run with NFS home on AutoFS

Status in firefox package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Confirmed

Bug description:
  My physical computer lab uses AutoFS home drives (per
  https://help.ubuntu.com/community/Autofs#Wildcard_characters).   If
  any user tries to run chromium browser, it fails.

  I assume it is related to these:
  https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1662552
  But that says a fix was released, but seems toi only work for NFS home drives
  https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1782873
  That ones is reported as a dupe but it's not, AutoFS home drives still don't 
work.

  $ chromium -v
  cannot create user data directory: /home/test.student2/snap/chromium/1193: 
Stale file handle

  $ tail -f /var/log/syslog
  Jun 19 11:21:09 tbl-h10-4 kernel: [18949.188657] nfs: RPC call returned error 
13
  Jun 19 11:21:09 tbl-h10-4 kernel: [18949.188666] nfs: RPC call returned error 
13
  Jun 19 11:21:09 tbl-h10-4 kernel: [18949.188695] audit: type=1400 
audit(1592590869.460:59): apparmor="DENIED" operation="sendmsg" 
profile="/snap/snapd/8140/usr/lib/snapd/snap-confine" pid=12884 
comm="snap-confine" laddr=192.168.43.216 lport=766 faddr=192.168.43.4 
fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" 
denied_mask="send"
  Jun 19 11:21:09 tbl-h10-4 kernel: [18949.188697] audit: type=1400 
audit(1592590869.460:60): apparmor="DENIED" operation="sendmsg" 
profile="/snap/snapd/8140/usr/lib/snapd/snap-confine" pid=12884 
comm="snap-confine" laddr=192.168.43.216 lport=766 faddr=192.168.43.4 
fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" 
denied_mask="send"

  $ lsb_release -rd
  Description:  Ubuntu 20.04 LTS

  $ apt policy chromium-browser
  chromium-browser:
    Installed: 81.0.4044.129-0ubuntu0.20.04.1
    Candidate: 81.0.4044.129-0ubuntu0.20.04.1
    Version table:
   *** 81.0.4044.129-0ubuntu0.20.04.1 500
  500 http://ca.archive.ubuntu.com/ubuntu focal-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   80.0.3987.163-0ubuntu1 500
  500 http://ca.archive.ubuntu.com/ubuntu focal/universe amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1884299/+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 1927063] Re: Terminal prompt got strangely replicated when resizing terminal horizontally

2022-08-20 Thread Oleg Klyuchkin
** Also affects: zsh (Ubuntu)
   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.
https://bugs.launchpad.net/bugs/1927063

Title:
  Terminal prompt got strangely replicated when resizing terminal
  horizontally

Status in bash package in Ubuntu:
  Confirmed
Status in gnome-terminal package in Ubuntu:
  Confirmed
Status in mate-terminal package in Ubuntu:
  Confirmed
Status in readline package in Ubuntu:
  Confirmed
Status in tilix package in Ubuntu:
  Confirmed
Status in vte2.91 package in Ubuntu:
  Confirmed
Status in zsh package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Have Ubuntu installed
  2. Launch MATE Terminal
  3. Navigate to some folder with long name - `cd 
/usr/share/doc/ayatana-indicator-application`
  4. Resize terminal horizontally

  Expected results:
  * terminal shows the same 
"user@host:/usr/share/doc/ayatana-indicator-application$" with single occurrence

  Actual results:
  * terminal shows multiple occurrencies of 
"user@host:/usr/share/doc/ayatana-indicator-application$"

  (see attached screencast)

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: mate-terminal 1.24.1-1
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Tue May  4 10:54:59 2021
  InstallationDate: Installed on 2021-04-23 (10 days ago)
  InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Release amd64 
(20210420)
  SourcePackage: mate-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1927063/+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 1680784] Re: Glitches

2022-02-12 Thread oleg
I already moved to arch lol
That was not a bug but hardware feature i assume?

When PC get in sleep videocard had less power so some graphical
athlas/spites/pars in videocard memory got a little "corrupted" so they
had to be reloaded to overvrite corupted/rooted visuals

You can close/ignore this bug, or make optional reload-all-graphical-
resources feature i you think it worth of it

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

Title:
  Glitches

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I switch pc to sleep, then i wake up him, now i get glitchs lines, if
  i reboot pc, lines will lost. There is screenshot of screen with
  glitch
  https://drive.google.com/file/d/0B7w7R6IlBX7CR0c2TkpiQXQtRFk/view?usp=sharing

  ProblemType: Graphic glitch
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-46-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Это каталог: 
'/proc/driver/nvidia/gpus/:04:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  375.39  Tue Jan 31 20:47:00 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Apr  7 13:12:56 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GF119 [GeForce GT 610] [10de:104a] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] GF119 [GeForce GT 610] 
[1462:809f]
  InstallationDate: Installed on 2017-03-22 (15 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   LANGUAGE=ru
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic 
root=UUID=5ab9fb9f-7d9b-4ec4-ab26-936456251d31 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/14/2006
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0113
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5LD2-VM DH
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0113:bd03/14/2006:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5LD2-VMDH:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Fri Apr  7 10:17:12 2017
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputUSB OPTICAL MOUSEMOUSE, id 8
   inputLogitech K270KEYBOARD, id 9
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1

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


-- 
Mailing 

[Desktop-packages] [Bug 755342] Re: Samsung Xcover 271 B2710 mass storage does not mount automatically

2021-09-19 Thread Oleg Moiseichuk
This bug still exists in Kubuntu 20.04. Samsung Xcover B2710 isn't connected 
properly.
Long ago I fixed it on Ubuntu 12.04 by "DisableSwitching=1" and forgot about 
it. Now found this bugreport once again and old fix still works.
If my help is needed in debugging of this issue, I'm ready.
P.S. Does this disabled switching affects other USB devices somehow or only 
mobile phones?

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

Title:
  Samsung Xcover 271 B2710 mass storage does not mount automatically

Status in usb-modeswitch package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce:
  1. In the interface of the Samsung Xcover 271 B2710, set it to connect as 
mass storage.
  2. Connect it to the computer via USB cabel.

  Notice that it does not mount automatically. Also it does mount
  automatically when instead of step 1 it is set to connect to Samsung
  Kies or to sync with a media player.

  Below I provide output from dmesg and lsusb -vv.

  Output from dmesg as it is connected (step 2):
  [101332.680133] usb 2-6: new high speed USB device using ehci_hcd and address 
6
  [101333.630726] Initializing USB Mass Storage driver...
  [101333.630861] scsi5 : usb-storage 2-6:1.0
  [101333.630956] usbcore: registered new interface driver usb-storage
  [101333.630958] USB Mass Storage support registered.

  Output from lsusb -vv:
  Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Device Descriptor:
    bLength18
    bDescriptorType 1
    bcdUSB   1.10
    bDeviceClass9 Hub
    bDeviceSubClass 0 Unused
    bDeviceProtocol 0 Full speed (or root) hub
    bMaxPacketSize064
    idVendor   0x1d6b Linux Foundation
    idProduct  0x0001 1.1 root hub
    bcdDevice2.06
    iManufacturer   3
    iProduct2
    iSerial 1
    bNumConfigurations  1
    Configuration Descriptor:
  bLength 9
  bDescriptorType 2
  wTotalLength   25
  bNumInterfaces  1
  bConfigurationValue 1
  iConfiguration  0
  bmAttributes 0xe0
    Self Powered
    Remote Wakeup
  MaxPower0mA
  Interface Descriptor:
    bLength 9
    bDescriptorType 4
    bInterfaceNumber0
    bAlternateSetting   0
    bNumEndpoints   1
    bInterfaceClass 9 Hub
    bInterfaceSubClass  0 Unused
    bInterfaceProtocol  0 Full speed (or root) hub
    iInterface  0
    Endpoint Descriptor:
  bLength 7
  bDescriptorType 5
  bEndpointAddress 0x81  EP 1 IN
  bmAttributes3
    Transfer TypeInterrupt
    Synch Type   None
    Usage Type   Data
  wMaxPacketSize 0x0002  1x 2 bytes
  bInterval 255
  can't get hub descriptor: Operation not permitted
  cannot read device status, Operation not permitted (1)

  Bus 006 Device 002: ID 046d:c01b Logitech, Inc. MX310 Optical Mouse
  Device Descriptor:
    bLength18
    bDescriptorType 1
    bcdUSB   2.00
    bDeviceClass0 (Defined at Interface level)
    bDeviceSubClass 0
    bDeviceProtocol 0
    bMaxPacketSize0 8
    idVendor   0x046d Logitech, Inc.
    idProduct  0xc01b MX310 Optical Mouse
    bcdDevice   18.00
    iManufacturer   1
    iProduct2
    iSerial 0
    bNumConfigurations  1
    Configuration Descriptor:
  bLength 9
  bDescriptorType 2
  wTotalLength   34
  bNumInterfaces  1
  bConfigurationValue 1
  iConfiguration  0
  bmAttributes 0xa0
    (Bus Powered)
    Remote Wakeup
  MaxPower   98mA
  Interface Descriptor:
    bLength 9
    bDescriptorType 4
    bInterfaceNumber0
    bAlternateSetting   0
    bNumEndpoints   1
    bInterfaceClass 3 Human Interface Device
    bInterfaceSubClass  1 Boot Interface Subclass
    bInterfaceProtocol  2 Mouse
    iInterface  0
  HID Device Descriptor:
    bLength 9
    bDescriptorType33
    bcdHID   1.10
    bCountryCode0 Not supported
    bNumDescriptors 1
    bDescriptorType34 Report
    wDescriptorLength  64
   Report Descriptors:
     ** UNAVAILABLE **
    Endpoint Descriptor:
  bLength   

[Desktop-packages] [Bug 1872504] Re: date modified is wrong for files on an exfat formatted drive

2020-11-22 Thread Oleg
Same issue here with the files copied from my Sony a6000 camera. Any
suggestions how to fix it?

>After installing fuse-exfat 
It gives me "E: Unable to locate package fuse-exfat"

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

Title:
  date modified is wrong for files on an exfat formatted drive

Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  When using exfat formatted drives (e.g. my camera card) with focal
  fossa any access causes the date modified to be set, even when it
  would not normally be set, and it is set a month into the future.

  Installing exfat-fuse and exfat-utils results in the correct
  behaviour.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.18
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 13 17:27:30 2020
  InstallationDate: Installed on 2020-04-12 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1872504/+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 1870736] Re: [nvidia] Screen scaling 125% gives 200%

2020-11-02 Thread Oleg "Nightwing" Lomakin
@cica-kutya there is solution - nvidia kms. And fractional scaling work without 
any issues(like tearing on intel) for me. I have single gpu setup(no hybrid 
graphics).
You can activate it by:
1. Set nvidia_drm module option:
$ cat /etc/modprobe.d/nvidia-modeset.conf 
options nvidia_drm modeset=1
2. Add same option to kernel cmdline:
$ cat /etc/default/grub

GRUB_CMDLINE_LINUX_DEFAULT="nvidia_drm.modeset=1 quiet splash"

3. Update initrd
$ sudo update-initramfs -u -k all
4. Reboot
5. Check it
$ sudo cat /sys/module/nvidia_drm/parameters/modeset
Y
6. Activate fraction scaling

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

Title:
  [nvidia] Screen scaling 125% gives 200%

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Procedure used:
  1.
  Fully updated system via apt update && apt upgrade

  2.
  Select the screen setup in gnome control center

  3. 
  Click the "Fractional scaling" toggle

  4. 
  Select 125% and click the green "use" button top right (it says "Anvend" in 
dansih)

  5.
  Observe that the window has grown a lot, click the "use new settings" button

  6.
  The window tells me, I am at 200% scaling. The "200%" option is now 
highlighted.

  7.
  Switch back to 100% and file this bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.16
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 09:42:34 2020
  InstallationDate: Installed on 2018-01-14 (810 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+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 1870736] Re: [nvidia] Screen scaling 125% gives 200%

2020-09-08 Thread Oleg "Nightwing" Lomakin
Fractional scaling on intel don't work well too(it causes tearing, lags, etc). 
And it works good only with wayland.
David, you can try #53 workaround(activate drm modeset for nvidia driver). It 
disabled by default, may be this is root of this problem?

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

Title:
  [nvidia] Screen scaling 125% gives 200%

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Procedure used:
  1.
  Fully updated system via apt update && apt upgrade

  2.
  Select the screen setup in gnome control center

  3. 
  Click the "Fractional scaling" toggle

  4. 
  Select 125% and click the green "use" button top right (it says "Anvend" in 
dansih)

  5.
  Observe that the window has grown a lot, click the "use new settings" button

  6.
  The window tells me, I am at 200% scaling. The "200%" option is now 
highlighted.

  7.
  Switch back to 100% and file this bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.16
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 09:42:34 2020
  InstallationDate: Installed on 2018-01-14 (810 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+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 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop

2020-07-01 Thread Oleg Prosekov
Hi Dell G3 (DMI: Dell Inc. G3 3590/0201H1, BIOS 1.6.0 08/08/2019) 
with the same issue (internal mic doesn't work, with external headset works)

~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.4 LTS
Release:18.04
Codename:   bionic

~$ uname -a
Linux ws165 5.3.0-61-generic #55~18.04.1-Ubuntu SMP Mon Jun 22 16:40:20 UTC 
2020 x86_64 x86_64 x86_64 GNU/Linux

~$ arecord -l
 List of CAPTURE Hardware Devices 
card 0: PCH [HDA Intel PCH], device 0: ALC3254 Analog [ALC3254 Analog]
  Subdevices: 0/1
  Subdevice #0: subdevice #0
card 0: PCH [HDA Intel PCH], device 2: ALC3254 Alt Analog [ALC3254 Alt Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

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

Title:
  Microphone not working in Ubuntu 18.04.3 LTS on new hp-
  spectre-x360-convertible-15 laptop

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp-
  spectre-x360-convertible-15 laptop. The microphone works perfectly on
  Windows 10 (present in Dual boot mode).

  Initially, Internal Microphone was not even detected but installing
  alsa-tools-gui and overriding pin 0x12 to the Internal Microphone
  fixed that issue. [Pin 0x13 does not work and causes static in a
  headphone if it is plugged in.]

  Microphone is not able to pick up any sound. I changed levels/settings in 
alsamixer, pavucontrol without any success:
  In alsamixer: Experimented with levels ranging from very low to very high for 
Internal Mic, Capture, etc.
  In pavucontrol: Set the Internal Mic as a fallback device, unlocked the 
channels for the mic, experimented with reducing the level for one of the 
channels (reduced right mic level to Silence while keeping the left mic level 
normal/high and vice versa).

  alsa-info:
  http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f

  arecord -l
   List of CAPTURE Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+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 1870356] Re: Can't connect to paired bluetooth devices via g-c-c

2020-06-15 Thread Oleg Gorobets
Restarting ubuntu doesn't help either. The only thing that helped me is
"Remove device" and then set up again.

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

Title:
  Can't connect to paired bluetooth devices via g-c-c

Status in gnome-control-center:
  Unknown
Status in gnome-control-center package in Ubuntu:
  Triaged

Bug description:
  I have a paired bluetooth device listed as "Disconnected" in the
  Bluetooth section of gnome-control-center. In order to connect to it I
  click on the device name and switch the "Connection" slider to the
  "on" position. The slider moves but immediately bounces back to the
  "off" position, and nothing happens: the connection is not
  established. It never works even if I try several times.

  This happens on an up-to-date Focal system and it's always
  reproducible across reboots and power cycles of the device. I don't
  think it's a problem of the device itself or of the underlying
  bluetooth stack, as connecting/disconnecting to the device works
  perfectly if I use blueman-manager instead of gnome-control-center.

  I don't know if this is a regression as I was not using bluetooth before 
installing Focal. FWIW (very little), the device connects/disconnects perfectly 
to Android phones.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-02-26 (400 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190226)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: gnome-control-center 1:3.36.1-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-20.24-generic 5.4.27
  Tags: focal uec-images wayland-session third-party-packages
  Uname: Linux 5.4.0-20-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-01-21 (72 days ago)
  UserGroups: adm cdrom dialout dip docker libvirt lpadmin lxd plugdev 
sambashare sbuild sudo utah
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1870356/+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 1870356] Re: Can't connect to paired bluetooth devices via g-c-c

2020-06-15 Thread Oleg Gorobets
Same issue here, Ubuntu 20.04. External bluetooth speakers stay in
"disconnected" mode in Bluetooth Settings, without a possibility to
connect (slider moves but immediately bounces back)

"sudo service bluetooth status" shows: connect error: Device or resource
busy (16)

Restarting bluetooth service doesn't help.

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

Title:
  Can't connect to paired bluetooth devices via g-c-c

Status in gnome-control-center:
  Unknown
Status in gnome-control-center package in Ubuntu:
  Triaged

Bug description:
  I have a paired bluetooth device listed as "Disconnected" in the
  Bluetooth section of gnome-control-center. In order to connect to it I
  click on the device name and switch the "Connection" slider to the
  "on" position. The slider moves but immediately bounces back to the
  "off" position, and nothing happens: the connection is not
  established. It never works even if I try several times.

  This happens on an up-to-date Focal system and it's always
  reproducible across reboots and power cycles of the device. I don't
  think it's a problem of the device itself or of the underlying
  bluetooth stack, as connecting/disconnecting to the device works
  perfectly if I use blueman-manager instead of gnome-control-center.

  I don't know if this is a regression as I was not using bluetooth before 
installing Focal. FWIW (very little), the device connects/disconnects perfectly 
to Android phones.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-02-26 (400 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190226)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: gnome-control-center 1:3.36.1-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-20.24-generic 5.4.27
  Tags: focal uec-images wayland-session third-party-packages
  Uname: Linux 5.4.0-20-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-01-21 (72 days ago)
  UserGroups: adm cdrom dialout dip docker libvirt lpadmin lxd plugdev 
sambashare sbuild sudo utah
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1870356/+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 1870736] Re: [nvidia] Screen scaling 125% gives 200%

2020-06-06 Thread Oleg "Nightwing" Lomakin
This option work only with hybrid graphics. If you select "NVIDIA On-Demand" 
all will run on intel\amd integrated GPU(but you can run selected app on nvidia 
discrete GPU).
Without integrated GPU this workaround don't work.

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

Title:
  [nvidia] Screen scaling 125% gives 200%

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Procedure used:
  1.
  Fully updated system via apt update && apt upgrade

  2.
  Select the screen setup in gnome control center

  3. 
  Click the "Fractional scaling" toggle

  4. 
  Select 125% and click the green "use" button top right (it says "Anvend" in 
dansih)

  5.
  Observe that the window has grown a lot, click the "use new settings" button

  6.
  The window tells me, I am at 200% scaling. The "200%" option is now 
highlighted.

  7.
  Switch back to 100% and file this bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.16
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 09:42:34 2020
  InstallationDate: Installed on 2018-01-14 (810 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+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 1875665] Re: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04

2020-06-04 Thread Oleg B
The fix does not work for me:

uname -r
5.4.0-33-generic

ournalctl -b0 -u rtkit-daemon
-- Logs begin at Wed 2020-04-29 18:57:09 EEST, end at Thu 2020-06-04 18:41:05 
EEST. --
Jun 04 18:26:06 n552vw systemd[1]: Starting RealtimeKit Scheduling Policy 
Service...
Jun 04 18:26:06 n552vw systemd[1]: Started RealtimeKit Scheduling Policy 
Service.
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Successfully called chroot.
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Successfully dropped privileges.
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Successfully limited resources.
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Running.
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Canary thread running.
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Watchdog thread running.
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Supervising 0 threads of 0 processes 
of 1 users.
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Supervising 0 threads of 0 processes 
of 1 users.
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Supervising 0 threads of 0 processes 
of 1 users.
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Supervising 0 threads of 0 processes 
of 1 users.
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Supervising 0 threads of 0 processes 
of 1 users.
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Supervising 0 threads of 0 processes 
of 1 users.
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Supervising 0 threads of 0 processes 
of 1 users.
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Supervising 0 threads of 0 processes 
of 1 users.
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Supervising 0 threads of 0 processes 
of 1 users.
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Supervising 0 threads of 0 processes 
of 1 users.
Jun 04 18:26:06 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:49 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:49 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:49 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:49 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:49 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:49 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:49 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:49 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:49 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:49 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:49 n552vw rtkit-daemon[1430]: Failed to make ourselves RT: 
Operation not permitted
Jun 04 18:26:49 n552vw rtkit-daemon[1430]: Supervising 0 threads of 0 processes 
of 1 users.
Jun 04 18:26:49 

[Desktop-packages] [Bug 1869829] [NEW] File collision between libreoffice-writer-nogui-dbgsym and libreoffice-core-nogui-dbgsym

2020-03-30 Thread Oleg Schelicalnov
Public bug reported:

I'm trying to catch error and installed libreoffice-core-nogui-dbgsym.
After  it I installed libreoffice-writer-nogui-dbgsym and got error:

Unpacking libreoffice-writer-nogui-dbgsym (1:6.4.2-0ubuntu0.18.04.3) ...
dpkg: error processing archive /var/cache/apt/archives/libreoffice-
writer-nogui-dbgsym_1%3a6.4.2-0ubuntu0.18.04.3_amd64.ddeb (--unpack):
 trying to overwrite '/usr/share/libreoffice/gdb/libreoffice/sw.py',
which is also in package libreoffice-core-nogui-dbgsym
1:6.4.2-0ubuntu0.18.04.3
E: Sub-process /usr/bin/dpkg returned an error code (1)

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

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

Title:
  File collision between libreoffice-writer-nogui-dbgsym and
  libreoffice-core-nogui-dbgsym

Status in libreoffice package in Ubuntu:
  New

Bug description:
  I'm trying to catch error and installed libreoffice-core-nogui-dbgsym.
  After  it I installed libreoffice-writer-nogui-dbgsym and got error:

  Unpacking libreoffice-writer-nogui-dbgsym (1:6.4.2-0ubuntu0.18.04.3) ...
  dpkg: error processing archive /var/cache/apt/archives/libreoffice-
  writer-nogui-dbgsym_1%3a6.4.2-0ubuntu0.18.04.3_amd64.ddeb (--unpack):
   trying to overwrite '/usr/share/libreoffice/gdb/libreoffice/sw.py',
  which is also in package libreoffice-core-nogui-dbgsym
  1:6.4.2-0ubuntu0.18.04.3
  E: Sub-process /usr/bin/dpkg returned an error code (1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1869829/+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 303140]

2019-10-28 Thread S-oleg
I don't think 1282701 is a duplicate of this. Original post talks about
sign icon being broken after an attachment is deleted. Referenced bug
talks about inability to easily remove attachments in signed emails.

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

Title:
  No more "Save all" / "detach all" / "delete all" for attachments

Status in Mozilla Thunderbird:
  Confirmed
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: thunderbird

  After receiving an email with more than one attachment, I have to 
open/detach/save them one by one, cause "Save all" / "detach all" / "delete 
all" in the GUI are not available
  This happens since version 2.0.0.18

  1) Description:Ubuntu 8.04.1 Release:8.04
  User-Agent: Thunderbird 2.0.0.18 (X11/20081125)
  MIME-Version: 1.0

  2) Package: Linux-Mint 5

  3) "Save all" / "detach all" / "delete all" available when right-
  klicking on an attachment

  4 )"Save all" / "detach all" / "delete all" greyed out, so not
  available

  ProblemType: Bug
  Architecture: i386
  Date: Fri Nov 28 11:34:16 2008
  DistroRelease: Ubuntu 8.04
  NonfreeKernelModules: wl fglrx
  Package: mozilla-thunderbird 2.0.0.18+nobinonly-0ubuntu0.8.04.1
  PackageArchitecture: all
  ProcEnviron:
   
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: thunderbird
  Uname: Linux 2.6.24-21-generic i686

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

2019-06-12 Thread S-oleg
David, yes i understood that correctly and was able to remove
attachments;) My second statement wasn't directed at you, but at the
situation in general.

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

Title:
  No more "Save all" / "detach all" / "delete all" for attachments

Status in Mozilla Thunderbird:
  Confirmed
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: thunderbird

  After receiving an email with more than one attachment, I have to 
open/detach/save them one by one, cause "Save all" / "detach all" / "delete 
all" in the GUI are not available
  This happens since version 2.0.0.18

  1) Description:Ubuntu 8.04.1 Release:8.04
  User-Agent: Thunderbird 2.0.0.18 (X11/20081125)
  MIME-Version: 1.0

  2) Package: Linux-Mint 5

  3) "Save all" / "detach all" / "delete all" available when right-
  klicking on an attachment

  4 )"Save all" / "detach all" / "delete all" greyed out, so not
  available

  ProblemType: Bug
  Architecture: i386
  Date: Fri Nov 28 11:34:16 2008
  DistroRelease: Ubuntu 8.04
  NonfreeKernelModules: wl fglrx
  Package: mozilla-thunderbird 2.0.0.18+nobinonly-0ubuntu0.8.04.1
  PackageArchitecture: all
  ProcEnviron:
   
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: thunderbird
  Uname: Linux 2.6.24-21-generic i686

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

2019-06-12 Thread S-oleg
David, thanks for the workaround. It seems that this and other tickets a
more about dealing with errors about broken signature and not about the
thing that a user should be able to deal with attachments no matter if
it will show an error or not.

+1 annoyed Thunderbird user

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

Title:
  No more "Save all" / "detach all" / "delete all" for attachments

Status in Mozilla Thunderbird:
  Confirmed
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: thunderbird

  After receiving an email with more than one attachment, I have to 
open/detach/save them one by one, cause "Save all" / "detach all" / "delete 
all" in the GUI are not available
  This happens since version 2.0.0.18

  1) Description:Ubuntu 8.04.1 Release:8.04
  User-Agent: Thunderbird 2.0.0.18 (X11/20081125)
  MIME-Version: 1.0

  2) Package: Linux-Mint 5

  3) "Save all" / "detach all" / "delete all" available when right-
  klicking on an attachment

  4 )"Save all" / "detach all" / "delete all" greyed out, so not
  available

  ProblemType: Bug
  Architecture: i386
  Date: Fri Nov 28 11:34:16 2008
  DistroRelease: Ubuntu 8.04
  NonfreeKernelModules: wl fglrx
  Package: mozilla-thunderbird 2.0.0.18+nobinonly-0ubuntu0.8.04.1
  PackageArchitecture: all
  ProcEnviron:
   
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: thunderbird
  Uname: Linux 2.6.24-21-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/303140/+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 1754702] Re: Delay before you can type after switching input source

2019-05-13 Thread Oleg
Hi!

I've made a workaround python script which switches layout itself using
`gsettings` command. Apparently, it helped some people reduce the delay
(including myself), so I'm going to post it here. Though, I don't know
why it works.

https://github.com/yamnikov-oleg/switch-layout

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

Title:
  Delay before you can type after switching input source

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  In ubuntu 18.04 I installed different keyboard languages: spanish
  latin american, japanese, japanese-ibus.  To change the input method
  you press the selected key, and an indicator menu appears on-screen to
  indicate which language is selected next.  The menu disapears after
  2~3 seconds and during which time typing is blocked.  If you type
  while the language input method menu is displayed, the menu will not
  disapear and stay as long as you type.

  The language input menu should not block typing, and the disapearance
  of the menu should not be delayed by typing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1754702/+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 1823176] [NEW] After connecting the usb docking station, the gnome-shell process loads one processor core 100%

2019-04-04 Thread Oleg Novikov
Public bug reported:

After connecting the usb docking station, the gnome-shell process loads
one processor core 100%

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.3-0ubuntu0.18.04.4
ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-17-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr  4 20:15:25 2019
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
InstallationDate: Installed on 2019-03-20 (15 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  After connecting the usb docking station, the gnome-shell process
  loads one processor core 100%

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  After connecting the usb docking station, the gnome-shell process
  loads one processor core 100%

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.3-0ubuntu0.18.04.4
  ProcVersionSignature: Ubuntu 4.18.0-17.18~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  4 20:15:25 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2019-03-20 (15 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1823176/+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 1781049] Re: WiFi hard blocked after resuming laptop from suspend

2019-01-20 Thread Oleg Andriyanov
Have exactly the same issue with Acer ex2519 n15w4 with Qualcomm Atheros
QCA9565 wi-fi card in it. Wi-fi worked during system installation (with
secure boot disabled as the original reporter mentioned). Not sure if
computer was suspended or powered off, but once I booted it and wi-fi
just stopped working and rfkill reported that device phy0 is hard
blocked.

The computer runs kernel 4.18.0-13-generic. I am happy to provide any
additional information to solve the issue.

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

Title:
  WiFi hard blocked after resuming laptop from suspend

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I installed a fresh copy of Ubuntu 18.04 and everything seems to work
  fine, till I suspended and resumed the laptop. After resume, the wifi
  is hard blocked is rfkill. Reinstalling drivers, different drivers,
  nothing helped. All this was done under Secure Boot disabled under
  Ubuntu and BIOS (UEFI).

  The WiFI card is Realtek 8723BE. laptop is HP AB035TX Pavilion 15. If
  any further info is required, I'll add it on notification. I am
  familiar with Linux, any help will be really appreciated.

  
  P.S: If this wifi card is the issue, please suggest some PCI-mini card that 
will work with my Ubuntu, even after suspend and resume (Ideally a 2.4/5G + BT 
5.0)

  Thank you all!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mythreya   1281 F pulseaudio
   /dev/snd/controlC1:  mythreya   1281 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-06-26 (16 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IpRoute:
   default via 192.168.1.1 dev wlo1 proto dhcp metric 600 
   169.254.0.0/16 dev wlo1 scope link metric 1000 
   192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.6 metric 600
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:b006 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 05c8:0379 Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP Pavilion Notebook
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.10.6-2ubuntu1
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=300b2c4a-387a-49b5-9cb6-93de471ebbdb ro quiet splash nouveau.runpm=0 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/26/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.87
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8096
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 89.33
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.87:bd02/26/2018:svnHewlett-Packard:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8096:rvr89.33:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: Hewlett-Packard
  modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf:
   [connection]
   wifi.powersave = 2
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-06-30T14:39:45.608645
  mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 
2018-06-28T16:23:51.596655
  nmcli-con:
   NAME   UUID  TYPE  TIMESTAMP   
TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH SLAVE 
   NETGEAR71  1a9d81bf-e7f5-4f8a-956f-96180dc493e1  wifi  1531450229  Thu 
12 Jul 2018 09:50:29 PM CDT  yes  0 no
/org/freedesktop/NetworkManager/Settings/2  yes wlo1activated  

[Desktop-packages] [Bug 1783452] Re: Some font glyphs are rendered incorrectly (with additional vertical spacing) in GTK applications

2018-10-28 Thread Oleg
I added another screenshot that shows how to easily reproduce this issue
using pango-view utility.

It also shows the difference in rendering between 16.04 and 18.04.

** Attachment added: "Screenshot demonstrating how to reproduce the issue with 
pango-view"
   
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1783452/+attachment/5206604/+files/pango-view-example.png

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

Title:
  Some font glyphs are rendered incorrectly (with additional vertical
  spacing) in GTK applications

Status in gtk+2.0 package in Ubuntu:
  New

Bug description:
  After switching from 16.04 to 18.04 I noticed that fonts are now (in
  18.04) rendered differently in GTK+ apps.

  For example, there is a vertical bar charcter `│` 
[U+2502](https://unicode-table.com/en/2502), that is used extensively to create 
solid vertical lines using just text characters.
  You can see it in console apps such as `mc` or `pstree`.
  While it is rendered correctly in Terminal in both 16.04 and 18.04, when 
rendered inside GTK apps it has unexpected vertical gap in-between characters 
on 18.04 (16.04 renders it correctly).
  The issue can be seen in GTK apps such as gVIM, Geany, GEdit, but Qt apps 
seem to render it properly.

  I have attached a screenshot that clearly demonstrates the difference.
  It shows brand new Ubuntu 16.04 on a left side where you can see
  vertical line in GEdit is completely solid, as it should be. On a
  right side it shows Ubuntu 18.04 where you can see line now has gaps
  that should not be there.

  I built a small GTK2 test app that reproduces the problem (sources at
  https://pastebin.com/WCH1ds4P), and using it I found that the problem
  occurs when libfreetype 2.8+ is used. I tested FreeType 2.6, 2.7,
  2.7.1 and all of them work fine. While 2.8 and above has this gap.

  I am not 100% sure if this is an Ubuntu font configuration issue, or
  bug in FreeType, or GTK or some other Ubuntu components, but I hope
  someone at least can point me at the right direction.

  Please also check my post on AskUbuntu which has additional detail and
  screenshots: https://askubuntu.com/questions/1054779/incorrect-font-
  glyphs-rendering-in-gtk-applications-in-ubuntu-18-04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1783452/+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 1370953] Re: layout switch is delayed

2018-10-25 Thread Oleg
I'm experiencing this bug on elementary OS 5.0. After looking through
different reports I can see that it comes from ubuntu.

Sad that there seems to be no progress on its resolution after several
years :(

Did somebody found a workaround with setxkbmap or something else?

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

Title:
  layout switch is delayed

Status in console-setup package in Ubuntu:
  Confirmed
Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  I have two layouts configured En and Ru with Ctrl-Shift as layout
  switch combo.

  When I start typing in wrong layout I notice it, hit Ctrl-Shift and type 
again, but more often than not it is wrong layout again.
  I repeat the action, but there is no luck. On the third attemt it usually 
either works OR the first letter is still in wrong layout, but the second is in 
correct one - i.e. layout switches as I type.

  The explanation for this is that layout switch takes very unreasonable
  time - much longer than it is needed to move your fingers from  one
  key to the other. Each time I encounter the error I retry slower so on
  the third attempt it is slow enough to actually recognize that layout
  switch is happening, but with a delay.

  This is extremely annoying and unacceptable. If someone knows how to
  work around it - please post your suggestions here. It would be nice
  to have a solution for 3+ layouts setup as well.

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

-- 
Mailing list: https://launchpad.net/~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 1131072] Re: Test page is printed on available printer if the printer under test is unavailable

2018-10-03 Thread Oleg Moiseichuk
In Ubuntu 14.04.5 this issue seems to be fixed. Now the test page is
sent to the appropriate printer rather than to the default printer. So
this bug can be closed.

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

Title:
  Test page is printed on available printer if the printer under test is
  unavailable

Status in system-config-printer package in Ubuntu:
  Incomplete

Bug description:
  I'm using Ubuntu 12.04.1 with GNOME Classic.
  I've got one printer in my system, HP LaserJet 3052, which is connected as 
network printer. Obviously, it is set as default. Its URI is 
'hp:/net/HP_LaserJet_3052?zc=NPIE50CCB' and its driver is 'HP LaserJet 3052 
Postscript (recommended)'.
  Later I added second printer using GNOME Printers applet. Second printer 
model is HP LaserJet 1220, it is connected via SAMBA with URI 
'smb://XX.XX.XX.XX/HPLaserJ' and I used recommended driver for this printer.
  When the setup was finished I sent test page to this printer and nothing 
happened. I switched from recommended driver to CUPS+Gutenprint v5.2.8 driver 
and sent another test page, but nothing happened again.
  My default HP LaserJet 3052 pinter was turned off at this moment, but when I 
switched it on, both test pages were printed on this printer instead. They got 
Job ID, Driver Version and Description of HP LaserJet 1220, but both tests were 
sent from the spool to the default HP LaserJet 3052 printer, not to the printer 
they were intended for.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1131072/+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 1756506] [NEW] snd_hda_intel module rejected by new kernel with retpoline

2018-03-17 Thread Oleg Korobkin
Public bug reported:

After a routine software update (which updated the kernel) alsa
recognises no sound card although lspci reports an audio device: Audio
device: Intel Corporation 8 Series HD Audio Controller (rev 04).

$ uname -a
Linux 3.13.0-143-generic #192-Ubuntu SMP Tue Feb 27 10:45:36 UTC 2018 x86_64 
x86_64 x86_64 GNU/Linux

$ aplay -l
aplay: device_list:268: no soundcards found...

$ dmesg | grep snd
[4.794976] snd_hda_core: version magic '3.13.0-143-generic SMP mod_unload 
modversions ' should be '3.13.0-143-generic SMP mod_unload modversions 
retpoline '

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: Confirmed

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

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

Title:
  snd_hda_intel module rejected by new kernel with retpoline

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  After a routine software update (which updated the kernel) alsa
  recognises no sound card although lspci reports an audio device: Audio
  device: Intel Corporation 8 Series HD Audio Controller (rev 04).

  $ uname -a
  Linux 3.13.0-143-generic #192-Ubuntu SMP Tue Feb 27 10:45:36 UTC 2018 x86_64 
x86_64 x86_64 GNU/Linux

  $ aplay -l
  aplay: device_list:268: no soundcards found...

  $ dmesg | grep snd
  [4.794976] snd_hda_core: version magic '3.13.0-143-generic SMP mod_unload 
modversions ' should be '3.13.0-143-generic SMP mod_unload modversions 
retpoline '

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1756506/+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 1730430] [NEW] package libsane1 1.0.27-1~experimental2ubuntu1 failed to install/upgrade: попытка перезаписать общий «/lib/udev/hwdb.d/20-sane.hwdb», который отличается от други

2017-11-06 Thread Oleg
Public bug reported:

При обработке следующих пакетов произошли ошибки:
 
/tmp/apt-dpkg-install-GQo8xC/133-libsane1_1.0.27-1~experimental2ubuntu1_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libsane1 1.0.27-1~experimental2ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
Date: Mon Nov  6 19:04:26 2017
ErrorMessage: попытка перезаписать общий «/lib/udev/hwdb.d/20-sane.hwdb», 
который отличается от других экземпляров пакета libsane1:i386
InstallationDate: Installed on 2017-11-05 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5
SourcePackage: sane-backends
Title: package libsane1 1.0.27-1~experimental2ubuntu1 failed to 
install/upgrade: попытка перезаписать общий «/lib/udev/hwdb.d/20-sane.hwdb», 
который отличается от других экземпляров пакета libsane1:i386
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: sane-backends (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package artful

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

Title:
  package libsane1 1.0.27-1~experimental2ubuntu1 failed to
  install/upgrade: попытка перезаписать общий
  «/lib/udev/hwdb.d/20-sane.hwdb», который отличается от других
  экземпляров пакета libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  При обработке следующих пакетов произошли ошибки:
   
/tmp/apt-dpkg-install-GQo8xC/133-libsane1_1.0.27-1~experimental2ubuntu1_i386.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  Date: Mon Nov  6 19:04:26 2017
  ErrorMessage: попытка перезаписать общий «/lib/udev/hwdb.d/20-sane.hwdb», 
который отличается от других экземпляров пакета libsane1:i386
  InstallationDate: Installed on 2017-11-05 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu1 failed to 
install/upgrade: попытка перезаписать общий «/lib/udev/hwdb.d/20-sane.hwdb», 
который отличается от других экземпляров пакета libsane1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1730430/+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 1730065] [NEW] Hedgewars crashing starting a game on artful

2017-11-04 Thread Oleg Shevchenko
Public bug reported:

After I upgraded to Artful I noticed the Hedgewars game crashing while starting 
a new game.
After some debugging I found this happens in the following library:

Program received signal SIGSEGV, Segmentation fault.
0xb0fd2a75 in ?? () from /usr/lib/i386-linux-gnu/dri/i965_dri.so

It is from libgl1-mesa-dri package (version 17.2.2-0ubuntu1).

So I decided to roll this package back to previous version. I downloaded
and installed the following packages from Zesty:

- libgl1-mesa-dri_17.0.3-1ubuntu1_i386.deb
- libegl1-mesa_17.0.3-1ubuntu1_i386.deb
- libgbm1_17.0.3-1ubuntu1_i386.deb
- libllvm4.0_4.0-1ubuntu1_i386.deb

And this solved the issue.

Below some technical details. Please let me know if you need something
else.

Distro: Ubuntu 17.10
Architecture: i386
MachineType: Acer Extensa 5620
Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) 
[8086:2a02] (rev 03) (prog-if 00 [VGA controller])
  Subsystem: Acer Incorporated [ALI] Mobile GM965/GL960 Integrated Graphics 
Controller (primary) [1025:011f]
  Subsystem: Acer Incorporated [ALI] Mobile GM965/GL960 Integrated Graphics 
Controller (secondary) [1025:011f]

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

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

Title:
  Hedgewars crashing starting a game on artful

Status in mesa package in Ubuntu:
  New

Bug description:
  After I upgraded to Artful I noticed the Hedgewars game crashing while 
starting a new game.
  After some debugging I found this happens in the following library:

  Program received signal SIGSEGV, Segmentation fault.
  0xb0fd2a75 in ?? () from /usr/lib/i386-linux-gnu/dri/i965_dri.so

  It is from libgl1-mesa-dri package (version 17.2.2-0ubuntu1).

  So I decided to roll this package back to previous version. I
  downloaded and installed the following packages from Zesty:

  - libgl1-mesa-dri_17.0.3-1ubuntu1_i386.deb
  - libegl1-mesa_17.0.3-1ubuntu1_i386.deb
  - libgbm1_17.0.3-1ubuntu1_i386.deb
  - libllvm4.0_4.0-1ubuntu1_i386.deb

  And this solved the issue.

  Below some technical details. Please let me know if you need something
  else.

  Distro: Ubuntu 17.10
  Architecture: i386
  MachineType: Acer Extensa 5620
  Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) 
[8086:2a02] (rev 03) (prog-if 00 [VGA controller])
Subsystem: Acer Incorporated [ALI] Mobile GM965/GL960 Integrated Graphics 
Controller (primary) [1025:011f]
Subsystem: Acer Incorporated [ALI] Mobile GM965/GL960 Integrated Graphics 
Controller (secondary) [1025:011f]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1730065/+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 1728056] [NEW] package libsane1 1.0.27-1~experimental2ubuntu1 failed to install/upgrade: попытка перезаписать общий «/lib/udev/hwdb.d/20-sane.hwdb», который отличается от други

2017-10-27 Thread oleg
Public bug reported:

xa

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libsane1 1.0.27-1~experimental2ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
Date: Fri Oct 27 16:50:26 2017
ErrorMessage: попытка перезаписать общий «/lib/udev/hwdb.d/20-sane.hwdb», 
который отличается от других экземпляров пакета libsane1:i386
InstallationDate: Installed on 2017-10-27 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] Нет такого файла или каталога: "/root/Error: command 
['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 
'python'] failed with exit code 1:", unpackaged
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5
SourcePackage: sane-backends
Title: package libsane1 1.0.27-1~experimental2ubuntu1 failed to 
install/upgrade: попытка перезаписать общий «/lib/udev/hwdb.d/20-sane.hwdb», 
который отличается от других экземпляров пакета libsane1:i386
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: sane-backends (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package artful

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

Title:
  package libsane1 1.0.27-1~experimental2ubuntu1 failed to
  install/upgrade: попытка перезаписать общий
  «/lib/udev/hwdb.d/20-sane.hwdb», который отличается от других
  экземпляров пакета libsane1:i386

Status in sane-backends package in Ubuntu:
  New

Bug description:
  xa

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libsane1 1.0.27-1~experimental2ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  Date: Fri Oct 27 16:50:26 2017
  ErrorMessage: попытка перезаписать общий «/lib/udev/hwdb.d/20-sane.hwdb», 
который отличается от других экземпляров пакета libsane1:i386
  InstallationDate: Installed on 2017-10-27 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] Нет такого файла или каталога: "/root/Error: command 
['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 
'python'] failed with exit code 1:", unpackaged
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5
  SourcePackage: sane-backends
  Title: package libsane1 1.0.27-1~experimental2ubuntu1 failed to 
install/upgrade: попытка перезаписать общий «/lib/udev/hwdb.d/20-sane.hwdb», 
который отличается от других экземпляров пакета libsane1:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1728056/+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 1680784] Re: Glitches

2017-04-10 Thread oleg
** Description changed:

- I switch pc to sleep? then i wake up him, now i get glitchs lines, if i
+ I switch pc to sleep, then i wake up him, now i get glitchs lines, if i
  reboot pc, lines will lost. There is screenshot of screen with glitch
  https://drive.google.com/file/d/0B7w7R6IlBX7CR0c2TkpiQXQtRFk/view?usp=sharing
  
  ProblemType: Graphic glitch
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-46-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Это каталог: 
'/proc/driver/nvidia/gpus/:04:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  375.39  Tue Jan 31 20:47:00 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  .tmp.unity_support_test.0:
  
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Apr  7 13:12:56 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GF119 [GeForce GT 610] [10de:104a] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] GF119 [GeForce GT 610] 
[1462:809f]
  InstallationDate: Installed on 2017-03-22 (15 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   LANGUAGE=ru
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic 
root=UUID=5ab9fb9f-7d9b-4ec4-ab26-936456251d31 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/14/2006
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0113
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5LD2-VM DH
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0113:bd03/14/2006:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5LD2-VMDH:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Fri Apr  7 10:17:12 2017
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputUSB OPTICAL MOUSEMOUSE, id 8
   inputLogitech K270KEYBOARD, id 9
  xserver.errors:
  
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
  
  xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1

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

Title:
  Glitches

Status in xorg package in Ubuntu:
  New

Bug description:
  I switch pc to sleep, then i wake up him, now i get glitchs lines, if
  i reboot pc, lines will lost. There is screenshot of screen with
  glitch
  https://drive.google.com/file/d/0B7w7R6IlBX7CR0c2TkpiQXQtRFk/view?usp=sharing

  ProblemType: Graphic glitch
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-46-generic 

[Desktop-packages] [Bug 1680784] [NEW] Glitches

2017-04-07 Thread oleg
Public bug reported:

I switch pc to sleep? then i wake up him, now i get glitchs lines, if i
reboot pc, lines will lost. There is screenshot of screen with glitch
https://drive.google.com/file/d/0B7w7R6IlBX7CR0c2TkpiQXQtRFk/view?usp=sharing

ProblemType: Graphic glitch
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-46-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Это каталог: 
'/proc/driver/nvidia/gpus/:04:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  375.39  Tue Jan 31 20:47:00 
PST 2017
 GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
.proc.driver.nvidia.warnings.fbdev:
 Your system is not currently configured to drive a VGA console
 on the primary VGA device. The NVIDIA Linux graphics driver
 requires the use of a text-mode VGA console. Use of other console
 drivers including, but not limited to, vesafb, may result in
 corruption and stability problems, and is not supported.
.tmp.unity_support_test.0:

ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Fri Apr  7 13:12:56 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 NVIDIA Corporation GF119 [GeForce GT 610] [10de:104a] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] GF119 [GeForce GT 610] 
[1462:809f]
InstallationDate: Installed on 2017-03-22 (15 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
MachineType: System manufacturer System Product Name
ProcEnviron:
 LANGUAGE=ru
 PATH=(custom, no user)
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic 
root=UUID=5ab9fb9f-7d9b-4ec4-ab26-936456251d31 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/14/2006
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0113
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5LD2-VM DH
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0113:bd03/14/2006:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5LD2-VMDH:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Fri Apr  7 10:17:12 2017
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputUSB OPTICAL MOUSEMOUSE, id 8
 inputLogitech K270KEYBOARD, id 9
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:

xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

** Description changed:

- I switch pc to sleep? then i wake up him, now i get glitchs lines
+ I switch pc to sleep, then i wake up him, now i get glitchs lines
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-46-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Это каталог: 
'/proc/driver/nvidia/gpus/:04:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
-  NVRM version: NVIDIA UNIX x86_64 Kernel Module  375.39  Tue Jan 31 20:47:00 
PST 2017
-  GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
+  NVRM version: 

[Desktop-packages] [Bug 1179933] Re: fails to install on a multi-arch on a raring system

2017-03-31 Thread Oleg Moiseichuk
This bug still exists in 16.04LTS. flashplugin-installer:i386 cannot be
installed in AMD64 system due to unresolved dependency: update-notifier-
common.

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

Title:
  fails to install on a multi-arch on a raring system

Status in Adobe Flash Plugin Tools:
  Fix Committed
Status in flashplugin-nonfree package in Ubuntu:
  Confirmed

Bug description:
  flashplugin-installer fails to install on a raring system in multi-
  arch mode.

  To reproduce, start from an x86_64 system and try to install the i386
  version of flashplugin-installer:

  $ sudo apt-get install flashplugin-installer:i386

  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   flashplugin-installer:i386 : Depends: update-notifier-common:i386 (>= 
0.119ubuntu2) but it is not installable
Recommends: libasound2-plugins:i386 (>= 1.0.16) 
but it is not going to be installed
  E: Unable to correct problems, you have held broken packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/adobe-flash-plugin-tools/+bug/1179933/+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 1092899] Re: flashplugin-installer not multiarch co-installable

2017-03-31 Thread Oleg Moiseichuk
*** This bug is a duplicate of bug 1179933 ***
https://bugs.launchpad.net/bugs/1179933

** This bug has been marked a duplicate of bug 1179933
   fails to install on a multi-arch on a raring system

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

Title:
  flashplugin-installer not multiarch co-installable

Status in flashplugin-nonfree package in Ubuntu:
  Confirmed

Bug description:
  Attempting to install flashplugin-installer:i386 on an amd64 machine
  running Ubuntu 12.10 causes apt-get to return the following error:

  The following packages have unmet dependencies.
   flashplugin-installer:i386 : Depends: update-notifier-common:i386 (>= 
0.119ubuntu2) but it is not installable
  E: Unable to correct problems, you have held broken packages.

  apt-get is apparently trying to install update-notifier-common:i386,
  but update-notifier-common is or architecture 'all', which I assume is
  an error in the packaging of flashplugin-installer.

  This is an issue with the Steam client which requires the i386
  flashplayer library, and this problem forces one to install it by
  hand. See https://github.com/ValveSoftware/steam-for-linux/issues/36 .

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: flashplugin-installer:i386 (not installed)
  ProcVersionSignature: Ubuntu 3.5.0-21.19-lowlatency 3.5.7.1
  Uname: Linux 3.5.0-21-lowlatency x86_64
  ApportVersion: 2.6.1-0ubuntu9
  Architecture: amd64
  Date: Fri Dec 21 13:32:20 2012
  InstallationDate: Installed on 2012-09-26 (86 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20120926)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: flashplugin-nonfree
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flashplugin-nonfree/+bug/1092899/+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 1597437] Re: X with nouveau driver, 2 nvidia cards, 4 monitors, does not use all monitors

2017-03-10 Thread Oleg Moiseichuk
Then you are more lucky than I am. My system hangs from time to time
with this patched driver - mouse and screen are frozen, only reboot
cures that. It happens approximately once a week, and that doesn't suit
me because my system should be up 24/7. Nothing can be found in
/var/log/syslog, only Xorg log shows some info about "EQ overflowing"
[https://nouveau.freedesktop.org/wiki/TroubleShooting/#index5h3]. So it
seems that this patch needs proper testing and its stability depends on
PC configuration. Good that it helped someone, but that's not my case.

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

Title:
  X with nouveau driver, 2 nvidia cards, 4 monitors, does not use all
  monitors

Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  
  Ubuntu 16.04 with two identical nvidia cards and four identical LG monitors.  
At the graphical login screen only the first 3 monitors appear alive (i.e. have 
backgrounds and the mouse can move to them).  A pop-up appears:

  "Could not switch the monitor configuration" (bold text with do-not-enter 
icon)
  "could not set the configuration for CRTC 64" (normal text)

  After logging in (gnome flashback Metacity session) the same 3
  monitors are alive and the same pop-up appears.

  Using Applications > System Tools > System Settings > Displays,
  the 4th monitor is shown in grey and when clicking it, it shows that the 
slider is off.  When turning it to On (leaving default resolution and rotation) 
and clicking Apply

  "The selected configuration for displays could not be applied" (bold text 
with do-not-enter icon)
  "could not set the configuration for CRTC 64" (normal text)

  a few seconds later (if the first one is not closed) another pop up
  with do-not-enter icon:

  "Failed to apply configuration: %s"
  "Timeout was reached"

  or trying again, if the first pop-up is closed within a few seconds,
  the second one is

  "Failed to apply configuration: %s"
  
"GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._gsd_2drr_2derror_2dquark.Code2:
 could not set the configuration for CRTC 64"

  ...and the Displays GUI makes it look like the 4th monitor is enabled
  but it is still blank.

  At the time of doing this, /var/log/Xorg.0.log shows:
  [ 96283.251] resize called 7680 1080
  [ 96283.299] Cannot do multiple crtcs without X server dirty tracking 2 
interface
  [ 96283.299] randr: failed to set shadow slave pixmap
  [ 96283.300] (EE) NOUVEAU(G0): failed to set mode: No space left on device

  
  I have also tried this with xrandr command line:

  $ xrandr --output DVI-I-1-4 --right-of DVI-I-1-3 --auto
  xrandr: Configure crtc 3 failed

  ...and the Xorg.0.log at this time is almost the same as above, plus
  the (I guess) fall back resizing to 3 monitors (5760x1080):

  [ 96645.224] Cannot do multiple crtcs without X server dirty tracking 2 
interface
  [ 96645.224] randr: failed to set shadow slave pixmap
  [ 96645.224] (EE) NOUVEAU(G0): failed to set mode: No space left on device
  [ 96645.227] resize called 0 0
  [ 96645.227] -22
  [ 96645.228] resize called 0 0
  [ 96645.228] -22
  [ 96645.229] resize called 7680 1080
  [ 96645.281] resize called 5760 1080

  
  I have previously tried to get around this with /etc/X11/xorg.conf with 
various Xinerama or ZaphodHeads settings but at the moment (of starting this 
"ubuntu-bug xserver-xorg-core" report) I have no xorg.conf and no 
~/.config/monitors.xml.  Obviously monitors.xml has been re-created as I test 
the Displays GUI to describe the pop-ups above, but it was not there at login.

  The 2-connector video cards to all four monitors are connected with
  DVI cables.  The monitors are LG E2240TI, the video cards are (lspci):

  01:00.0 VGA compatible controller: NVIDIA Corporation GF114 [GeForce GTX 560 
Ti] (rev a1)
  02:00.0 VGA compatible controller: NVIDIA Corporation GF114 [GeForce GTX 560 
Ti] (rev a1)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed Jun 29 12:21:13 2016
  DistUpgraded: 2016-06-23 10:16:50,641 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.18, 4.4.0-24-generic, x86_64: installed
   virtualbox, 5.0.18, 4.4.0-28-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GF114 [GeForce GTX 560 Ti] [10de:1200] (rev a1) (prog-if 
00 [VGA controller])
   

[Desktop-packages] [Bug 1597437] Re: X with nouveau driver, 2 nvidia cards, 4 monitors, does not use all monitors

2017-03-07 Thread Oleg Moiseichuk
Almost 2 months have passed since I posted the patch. Martin, if you are
still tracking this bug, does this patch work stable for you?

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

Title:
  X with nouveau driver, 2 nvidia cards, 4 monitors, does not use all
  monitors

Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  
  Ubuntu 16.04 with two identical nvidia cards and four identical LG monitors.  
At the graphical login screen only the first 3 monitors appear alive (i.e. have 
backgrounds and the mouse can move to them).  A pop-up appears:

  "Could not switch the monitor configuration" (bold text with do-not-enter 
icon)
  "could not set the configuration for CRTC 64" (normal text)

  After logging in (gnome flashback Metacity session) the same 3
  monitors are alive and the same pop-up appears.

  Using Applications > System Tools > System Settings > Displays,
  the 4th monitor is shown in grey and when clicking it, it shows that the 
slider is off.  When turning it to On (leaving default resolution and rotation) 
and clicking Apply

  "The selected configuration for displays could not be applied" (bold text 
with do-not-enter icon)
  "could not set the configuration for CRTC 64" (normal text)

  a few seconds later (if the first one is not closed) another pop up
  with do-not-enter icon:

  "Failed to apply configuration: %s"
  "Timeout was reached"

  or trying again, if the first pop-up is closed within a few seconds,
  the second one is

  "Failed to apply configuration: %s"
  
"GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._gsd_2drr_2derror_2dquark.Code2:
 could not set the configuration for CRTC 64"

  ...and the Displays GUI makes it look like the 4th monitor is enabled
  but it is still blank.

  At the time of doing this, /var/log/Xorg.0.log shows:
  [ 96283.251] resize called 7680 1080
  [ 96283.299] Cannot do multiple crtcs without X server dirty tracking 2 
interface
  [ 96283.299] randr: failed to set shadow slave pixmap
  [ 96283.300] (EE) NOUVEAU(G0): failed to set mode: No space left on device

  
  I have also tried this with xrandr command line:

  $ xrandr --output DVI-I-1-4 --right-of DVI-I-1-3 --auto
  xrandr: Configure crtc 3 failed

  ...and the Xorg.0.log at this time is almost the same as above, plus
  the (I guess) fall back resizing to 3 monitors (5760x1080):

  [ 96645.224] Cannot do multiple crtcs without X server dirty tracking 2 
interface
  [ 96645.224] randr: failed to set shadow slave pixmap
  [ 96645.224] (EE) NOUVEAU(G0): failed to set mode: No space left on device
  [ 96645.227] resize called 0 0
  [ 96645.227] -22
  [ 96645.228] resize called 0 0
  [ 96645.228] -22
  [ 96645.229] resize called 7680 1080
  [ 96645.281] resize called 5760 1080

  
  I have previously tried to get around this with /etc/X11/xorg.conf with 
various Xinerama or ZaphodHeads settings but at the moment (of starting this 
"ubuntu-bug xserver-xorg-core" report) I have no xorg.conf and no 
~/.config/monitors.xml.  Obviously monitors.xml has been re-created as I test 
the Displays GUI to describe the pop-ups above, but it was not there at login.

  The 2-connector video cards to all four monitors are connected with
  DVI cables.  The monitors are LG E2240TI, the video cards are (lspci):

  01:00.0 VGA compatible controller: NVIDIA Corporation GF114 [GeForce GTX 560 
Ti] (rev a1)
  02:00.0 VGA compatible controller: NVIDIA Corporation GF114 [GeForce GTX 560 
Ti] (rev a1)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed Jun 29 12:21:13 2016
  DistUpgraded: 2016-06-23 10:16:50,641 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.18, 4.4.0-24-generic, x86_64: installed
   virtualbox, 5.0.18, 4.4.0-28-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GF114 [GeForce GTX 560 Ti] [10de:1200] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. GF114 [GeForce GTX 560 Ti] 
[19da:1665]
   NVIDIA Corporation GF114 [GeForce GTX 560 Ti] [10de:1200] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. GF114 [GeForce GTX 560 Ti] 
[19da:1665]
  InstallationDate: Installed on 2015-11-12 (229 days ago)
  InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  

[Desktop-packages] [Bug 1571806] Re: Backup files are silently ignored when using certain archive types

2017-02-13 Thread Oleg Moiseichuk
I met with the same issue in 16.04.1 (amd64). Tested several 'tar' archives 
(namely tar.7z and tar.gz) - none of them stored backup files. Maybe some 
problem with generation of the lists of files for archiving? '7z' and 'zip' 
archives do save backup files, but it seems that they rely on 'p7zip-full' 
package which provides 7-Zip backend for the File Roller. Until I installed 
this package 'zip' archives were also losing backup files.
In my older system which is 12.04LTS (i386) all the mentioned archive types 
properly store backup files.

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

Title:
  Backup files are silently ignored when using certain archive types

Status in file-roller package in Ubuntu:
  Confirmed

Bug description:
  Depending on the kind of archive you create using file-roller, backup
  files (files with a `~` on the end of their names) are included or
  ignored. The user doesn't see any warning at all and will probably
  only discover this when they try to extract the archive.

  # How to reproduce the symptom.
  (I'm assuming you're using Nautilus with file-roller integration.)
  Create a folder `testFolder` (or any name but I'll use this one to refer to 
it) and create a file called `testFile~` in it. Then move to the parent folder 
of `testFolder`. Right-click test folder and choose "Compress".
  ## Correct behavior.
  Choose `.7z` as the archive format making it a 7zip archive and click 
"Create". The archive will contain the folder `testFolder` and in it the file 
`testFile~`.
  ## Incorrect behavior.
  Choose `.tar` as the archive format making it a tarball and click "Create". 
The tarball will contain the folder `testFolder` but it will be empty.

  Note that this isn't the fault of `tar`. If you create the tarball
  from the command line using the command `tar`, `testFile~` will be
  included.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1571806/+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 1597437] Re: X with nouveau driver, 2 nvidia cards, 4 monitors, does not use all monitors

2017-02-10 Thread Oleg Moiseichuk
If debugging symbols weren't disabled during compilation and the
resulting file size looks intimidating you can decrease it. Run 'strip
-s nouveau_drv.so' and debugging symbols will be purged completely.

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

Title:
  X with nouveau driver, 2 nvidia cards, 4 monitors, does not use all
  monitors

Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  
  Ubuntu 16.04 with two identical nvidia cards and four identical LG monitors.  
At the graphical login screen only the first 3 monitors appear alive (i.e. have 
backgrounds and the mouse can move to them).  A pop-up appears:

  "Could not switch the monitor configuration" (bold text with do-not-enter 
icon)
  "could not set the configuration for CRTC 64" (normal text)

  After logging in (gnome flashback Metacity session) the same 3
  monitors are alive and the same pop-up appears.

  Using Applications > System Tools > System Settings > Displays,
  the 4th monitor is shown in grey and when clicking it, it shows that the 
slider is off.  When turning it to On (leaving default resolution and rotation) 
and clicking Apply

  "The selected configuration for displays could not be applied" (bold text 
with do-not-enter icon)
  "could not set the configuration for CRTC 64" (normal text)

  a few seconds later (if the first one is not closed) another pop up
  with do-not-enter icon:

  "Failed to apply configuration: %s"
  "Timeout was reached"

  or trying again, if the first pop-up is closed within a few seconds,
  the second one is

  "Failed to apply configuration: %s"
  
"GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._gsd_2drr_2derror_2dquark.Code2:
 could not set the configuration for CRTC 64"

  ...and the Displays GUI makes it look like the 4th monitor is enabled
  but it is still blank.

  At the time of doing this, /var/log/Xorg.0.log shows:
  [ 96283.251] resize called 7680 1080
  [ 96283.299] Cannot do multiple crtcs without X server dirty tracking 2 
interface
  [ 96283.299] randr: failed to set shadow slave pixmap
  [ 96283.300] (EE) NOUVEAU(G0): failed to set mode: No space left on device

  
  I have also tried this with xrandr command line:

  $ xrandr --output DVI-I-1-4 --right-of DVI-I-1-3 --auto
  xrandr: Configure crtc 3 failed

  ...and the Xorg.0.log at this time is almost the same as above, plus
  the (I guess) fall back resizing to 3 monitors (5760x1080):

  [ 96645.224] Cannot do multiple crtcs without X server dirty tracking 2 
interface
  [ 96645.224] randr: failed to set shadow slave pixmap
  [ 96645.224] (EE) NOUVEAU(G0): failed to set mode: No space left on device
  [ 96645.227] resize called 0 0
  [ 96645.227] -22
  [ 96645.228] resize called 0 0
  [ 96645.228] -22
  [ 96645.229] resize called 7680 1080
  [ 96645.281] resize called 5760 1080

  
  I have previously tried to get around this with /etc/X11/xorg.conf with 
various Xinerama or ZaphodHeads settings but at the moment (of starting this 
"ubuntu-bug xserver-xorg-core" report) I have no xorg.conf and no 
~/.config/monitors.xml.  Obviously monitors.xml has been re-created as I test 
the Displays GUI to describe the pop-ups above, but it was not there at login.

  The 2-connector video cards to all four monitors are connected with
  DVI cables.  The monitors are LG E2240TI, the video cards are (lspci):

  01:00.0 VGA compatible controller: NVIDIA Corporation GF114 [GeForce GTX 560 
Ti] (rev a1)
  02:00.0 VGA compatible controller: NVIDIA Corporation GF114 [GeForce GTX 560 
Ti] (rev a1)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Wed Jun 29 12:21:13 2016
  DistUpgraded: 2016-06-23 10:16:50,641 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.18, 4.4.0-24-generic, x86_64: installed
   virtualbox, 5.0.18, 4.4.0-28-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GF114 [GeForce GTX 560 Ti] [10de:1200] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. GF114 [GeForce GTX 560 Ti] 
[19da:1665]
   NVIDIA Corporation GF114 [GeForce GTX 560 Ti] [10de:1200] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ZOTAC International (MCO) Ltd. GF114 [GeForce GTX 560 Ti] 
[19da:1665]
  InstallationDate: Installed on 2015-11-12 (229 days ago)
  InstallationMedia: 

[Desktop-packages] [Bug 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.

2017-01-22 Thread Oleg Moiseichuk
This bug affects my system (Ubuntu 16.04.1 amd64, Gnome Flashback
session with Compiz). One-key keyboard layout switchers (I tested Right
Alt, Right Super, Right Control) don't work, while two-key switchers
work (checked several of them). If I run Unity session, these one-key
switchers work properly. Is it a bug of g-s-d, or I should open the bug
in gnome-flashback section?

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

Title:
  Can't set keyboard layout change to alt+shift, ctrl+shift, etc.

Status in gnome-settings-daemon:
  Unknown
Status in Ubuntu GNOME:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon package in Ubuntu:
  Triaged
Status in gnome-control-center package in ALT Linux:
  Unknown
Status in gnome-control-center package in Baltix:
  Confirmed
Status in gnome-control-center package in Gentoo Linux:
  Unknown
Status in gnome-control-center package in Mandriva:
  Unknown

Bug description:
  [Impact]

  Can't set keyboard layout change to Ctrl+Shift, Caps Lock, Alt+Shift,
  etc. Shift, Caps Lock keys are just ignored in settings.

  [Test Case]

  - open gnome-control-center's text input settings
  - click on the "next layout key" entry
  - try entering a combination of two modifier keys such as Ctrl+Shift
  -> the UI should reflect the new keys

  - add at least two input sources through gnome-control-center's text entry
settings
  - press and release Ctrl+Shift
  -> the current input source should change

  [Regression Potential]

  That UI was not working before, it should only be an improvement (some
  key combos are not working as expected, that's another issue and
  shouldn't be mixed with this one)

  The input switching shortcut might capture other non-modifier
  shortcuts, but users will need to consider this when choosing their
  switching shortcut anyways. For users this bug affects, this
  represents a working solution for a critical bug.

  --

  Test results for different keyboard layout change hotkeys may be
  viewed and added in the Google Docs table, created by Norbert
  
(https://docs.google.com/spreadsheet/ccc?key=0Ao5e713Ig9g_dEJrX2NRYlpLWWVzSWxsVXU4ck9HYVE=sharing).

  You can use the tag keyboard-layout-switching-hotkeys to find related bugs.
  
https://bugs.launchpad.net/ubuntu/+bugs?field.tag=keyboard-layout-switching-hotkeys

  For using layout switching hotkeys in Unity Greeter, see bug 1245137.
  For using layout switching hotkeys in GNOME lockscreen, see bug 1244548.

  --

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: indicator-keyboard 0.0.0+13.10.20130829.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5
  Uname: Linux 3.11.0-2-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.1-0ubuntu2
  Architecture: amd64
  Date: Thu Aug 29 14:21:54 2013
  InstallationDate: Installed on 2013-07-31 (28 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130730)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  SourcePackage: indicator-keyboard
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1218322/+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 1597437] Re: X with nouveau driver, 2 nvidia cards, 4 monitors, does not use all monitors

2017-01-16 Thread Oleg Moiseichuk
Martin, you've done everything well. Indeed, additional packages are needed for 
the successful compilation. They can be installed by the command 'sudo apt-get 
build-dep package_name' (there can be hefty pack, that's why I'm usually using 
virtual machine for the compilation and revert it to the last snapshot 
afterwards).
The size of the resulting library can be decreased by setting specific compiler 
options. If you examine Makefile which was created after './configure' has 
finished its work, you'll find CFLAGS string in it containing -g option (the 
level of debugging information) and -O2 option (optimization level). Disabling 
debugging information affects size of the resulting file but isn't advised 
(this may cause undesired results). Increasing optimization level will reduce 
the compiled file size (higher levels of optimisation also may cause undesired 
code behavior). Better leave it as it is. Those who perform packaging are 
better aware how this specific package should be compiled to ensure its minimal 
size for the distribution.

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

Title:
  X with nouveau driver, 2 nvidia cards, 4 monitors, does not use all
  monitors

Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  
  Ubuntu 16.04 with two identical nvidia cards and four identical LG monitors.  
At the graphical login screen only the first 3 monitors appear alive (i.e. have 
backgrounds and the mouse can move to them).  A pop-up appears:

  "Could not switch the monitor configuration" (bold text with do-not-enter 
icon)
  "could not set the configuration for CRTC 64" (normal text)

  After logging in (gnome flashback Metacity session) the same 3
  monitors are alive and the same pop-up appears.

  Using Applications > System Tools > System Settings > Displays,
  the 4th monitor is shown in grey and when clicking it, it shows that the 
slider is off.  When turning it to On (leaving default resolution and rotation) 
and clicking Apply

  "The selected configuration for displays could not be applied" (bold text 
with do-not-enter icon)
  "could not set the configuration for CRTC 64" (normal text)

  a few seconds later (if the first one is not closed) another pop up
  with do-not-enter icon:

  "Failed to apply configuration: %s"
  "Timeout was reached"

  or trying again, if the first pop-up is closed within a few seconds,
  the second one is

  "Failed to apply configuration: %s"
  
"GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._gsd_2drr_2derror_2dquark.Code2:
 could not set the configuration for CRTC 64"

  ...and the Displays GUI makes it look like the 4th monitor is enabled
  but it is still blank.

  At the time of doing this, /var/log/Xorg.0.log shows:
  [ 96283.251] resize called 7680 1080
  [ 96283.299] Cannot do multiple crtcs without X server dirty tracking 2 
interface
  [ 96283.299] randr: failed to set shadow slave pixmap
  [ 96283.300] (EE) NOUVEAU(G0): failed to set mode: No space left on device

  
  I have also tried this with xrandr command line:

  $ xrandr --output DVI-I-1-4 --right-of DVI-I-1-3 --auto
  xrandr: Configure crtc 3 failed

  ...and the Xorg.0.log at this time is almost the same as above, plus
  the (I guess) fall back resizing to 3 monitors (5760x1080):

  [ 96645.224] Cannot do multiple crtcs without X server dirty tracking 2 
interface
  [ 96645.224] randr: failed to set shadow slave pixmap
  [ 96645.224] (EE) NOUVEAU(G0): failed to set mode: No space left on device
  [ 96645.227] resize called 0 0
  [ 96645.227] -22
  [ 96645.228] resize called 0 0
  [ 96645.228] -22
  [ 96645.229] resize called 7680 1080
  [ 96645.281] resize called 5760 1080

  
  I have previously tried to get around this with /etc/X11/xorg.conf with 
various Xinerama or ZaphodHeads settings but at the moment (of starting this 
"ubuntu-bug xserver-xorg-core" report) I have no xorg.conf and no 
~/.config/monitors.xml.  Obviously monitors.xml has been re-created as I test 
the Displays GUI to describe the pop-ups above, but it was not there at login.

  The 2-connector video cards to all four monitors are connected with
  DVI cables.  The monitors are LG E2240TI, the video cards are (lspci):

  01:00.0 VGA compatible controller: NVIDIA Corporation GF114 [GeForce GTX 560 
Ti] (rev a1)
  02:00.0 VGA compatible controller: NVIDIA Corporation GF114 [GeForce GTX 560 
Ti] (rev a1)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME-Flashback:Unity
  

[Desktop-packages] [Bug 1597437] Re: X with nouveau driver, 2 nvidia cards, 4 monitors, does not use all monitors

2017-01-11 Thread Oleg Moiseichuk
I met with the same bug in Ubuntu 16.04.1 (amd64): 2 NVIDIA adapters with DVI 
and HDMI connectors on each of them, 4 identical Samsung monitors, 4th monitor 
is dead, 3rd is sometimes garbled, sometimes is OK. All the error messages 
described by Martin are the same.
Luckily in #2 he provided the method which cures the bug with ATI cards in 
Fedora. I decided to try it with Nouveau driver in Ubuntu and it worked!
I downloaded the sources using 'apt-get source xserver-xorg-video-nouveau', 
found the string in drmmode_display.c which checks whether HAS_DIRTYTRACKING2 
is defined and fixed it. Then I compiled the driver and replaced 
'/usr/lib/xorg/modules/drivers/nouveau_drv.so' with the fixed version. After 
reboot all 4 monitors were working on login screen, '~/.config/monitors.xml' 
was created properly and all monitors were present when I logged in.
I'm attaching the patch. Maybe the developers will notice it and fix the 
Nouveau driver?
(BTW, ATI driver in Ubuntu 16.04 seems already fixed - I checked its sources 
and the mentioned string is already in place in drmmode_display.c)

** Patch added: "Fixes improper handling of 3rd and 4th monitors"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1597437/+attachment/4802770/+files/nouveau_drv.patch

** Package changed: xorg-server (Ubuntu) => xserver-xorg-video-nouveau
(Ubuntu)

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

Title:
  X with nouveau driver, 2 nvidia cards, 4 monitors, does not use all
  monitors

Status in xserver-xorg-video-nouveau package in Ubuntu:
  Confirmed

Bug description:
  
  Ubuntu 16.04 with two identical nvidia cards and four identical LG monitors.  
At the graphical login screen only the first 3 monitors appear alive (i.e. have 
backgrounds and the mouse can move to them).  A pop-up appears:

  "Could not switch the monitor configuration" (bold text with do-not-enter 
icon)
  "could not set the configuration for CRTC 64" (normal text)

  After logging in (gnome flashback Metacity session) the same 3
  monitors are alive and the same pop-up appears.

  Using Applications > System Tools > System Settings > Displays,
  the 4th monitor is shown in grey and when clicking it, it shows that the 
slider is off.  When turning it to On (leaving default resolution and rotation) 
and clicking Apply

  "The selected configuration for displays could not be applied" (bold text 
with do-not-enter icon)
  "could not set the configuration for CRTC 64" (normal text)

  a few seconds later (if the first one is not closed) another pop up
  with do-not-enter icon:

  "Failed to apply configuration: %s"
  "Timeout was reached"

  or trying again, if the first pop-up is closed within a few seconds,
  the second one is

  "Failed to apply configuration: %s"
  
"GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._gsd_2drr_2derror_2dquark.Code2:
 could not set the configuration for CRTC 64"

  ...and the Displays GUI makes it look like the 4th monitor is enabled
  but it is still blank.

  At the time of doing this, /var/log/Xorg.0.log shows:
  [ 96283.251] resize called 7680 1080
  [ 96283.299] Cannot do multiple crtcs without X server dirty tracking 2 
interface
  [ 96283.299] randr: failed to set shadow slave pixmap
  [ 96283.300] (EE) NOUVEAU(G0): failed to set mode: No space left on device

  
  I have also tried this with xrandr command line:

  $ xrandr --output DVI-I-1-4 --right-of DVI-I-1-3 --auto
  xrandr: Configure crtc 3 failed

  ...and the Xorg.0.log at this time is almost the same as above, plus
  the (I guess) fall back resizing to 3 monitors (5760x1080):

  [ 96645.224] Cannot do multiple crtcs without X server dirty tracking 2 
interface
  [ 96645.224] randr: failed to set shadow slave pixmap
  [ 96645.224] (EE) NOUVEAU(G0): failed to set mode: No space left on device
  [ 96645.227] resize called 0 0
  [ 96645.227] -22
  [ 96645.228] resize called 0 0
  [ 96645.228] -22
  [ 96645.229] resize called 7680 1080
  [ 96645.281] resize called 5760 1080

  
  I have previously tried to get around this with /etc/X11/xorg.conf with 
various Xinerama or ZaphodHeads settings but at the moment (of starting this 
"ubuntu-bug xserver-xorg-core" report) I have no xorg.conf and no 
~/.config/monitors.xml.  Obviously monitors.xml has been re-created as I test 
the Displays GUI to describe the pop-ups above, but it was not there at login.

  The 2-connector video cards to all four monitors are connected with
  DVI cables.  The monitors are LG E2240TI, the video cards are (lspci):

  01:00.0 VGA compatible controller: NVIDIA Corporation GF114 [GeForce GTX 560 
Ti] (rev a1)
  02:00.0 VGA compatible controller: NVIDIA Corporation GF114 [GeForce GTX 560 
Ti] (rev a1)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  

[Desktop-packages] [Bug 1589401] Re: cannot view wifi networks after re-enabling wifi

2016-12-06 Thread Oleg "Nightwing" Lomakin
network-manager 1.2.2-0ubuntu0.16.04.3 and network-manager-gnome 
1.2.0-0ubuntu0.16.04.4 still had this bug. 
Only nm-applet restart help

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

Title:
  cannot view wifi networks after re-enabling wifi

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  after re enabling wifi, up-down arrows just like wired network. cannot
  see any wifi ssid.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1589401/+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 1549163] Re: Bluetooth headset HSP/HFP mode not working in Xenial

2016-10-20 Thread Oleg
2 Bernie:

I had similar issue with Xenial. Two things to be mentioned:

1) It was not clean OS install, Xenial was upgraded from 14.04
2) There were error messages, when I tried to choose HSP profile:

[pulseaudio] module-bluez5-device.c: Refused to switch profile to
headset_head_unit: Not connected

So, I reinstalled the bluez package and the problem disappeared.
Something like this:

sudo apt-get install --reinstall bluez

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

Title:
  Bluetooth headset HSP/HFP mode not working in Xenial

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  Using the 2/14 Xenial daily build, paired bluetooth headsets' do not
  work in HSP/HFP mode.

  [Steps to reproduce]
  1. Pair a bluetooth headset with laptop installed with Xenial 2/14 daily build
  2. In the laptop, go to sound settings > output tab > try switching mode to 
HSP/HFP mode
  3. Press the "test sound" button and try playing sound
  4. Go to the input tab and check if bluetooth headset mic is listed

  [Expected result]
  After step 3, a window for mono audio test should pop up
  After step 4, the input tab should list a bluetooth headset mic device

  [Actual result]
  After step 3, the window that pops up is for stereo (A2DP) audio test
  After step 4, the input tab does not list any bluetooth headset mic

  [Details]
  BT wireless module:
   * Intel 3160
  BT headset:
   * Jabra CLI
  Xenial: 2/14 daily build:
   * Kernel: 4.4.0-6
   * bluez: 5.36-0ubuntu1
   * gstreamer1.0-pulseaudio:amd64: 1.7.2-1ubuntu1
   * pulseaudio: 1:8.0-0ubuntu2
   * pulseaudio-module-bluetooth: 1:8.0-0ubuntu2

  [Note]
  Also double checked with same set of hardware, but with 15.10 installed.
  Bluetooth headset HSP/HFP mode worked correctly in 15.10.

  15.10 details:
   * kernel: 4.2.0-19
   * bluez: 5.35-0ubuntu2
   * gstreamer1.0-pulseaudio:amd64: 1.6.0-1ubuntu1
   * pulseaudio: 1:6.0-0ubuntu13
   * pulseaudio-module-bluetooth: 1:6.0-0ubuntu13

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1549163/+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 1624876] [NEW] package nvidia-304 304.131-0ubuntu0.14.04.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting co

2016-09-18 Thread Oleg
Public bug reported:

I don't know what I should write here

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: nvidia-304 304.131-0ubuntu0.14.04.2
ProcVersionSignature: Ubuntu 4.4.0-36.55~14.04.1-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
Date: Sun Sep 18 17:27:37 2016
DuplicateSignature: package:nvidia-304:304.131-0ubuntu0.14.04.2:package is in a 
very bad inconsistent state; you should  reinstall it before attempting 
configuration
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2016-03-04 (197 days ago)
InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1)
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.7
 apt  1.0.1ubuntu2.14
SourcePackage: nvidia-graphics-drivers-304
Title: package nvidia-304 304.131-0ubuntu0.14.04.2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-304 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package third-party-packages trusty

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

Title:
  package nvidia-304 304.131-0ubuntu0.14.04.2 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  New

Bug description:
  I don't know what I should write here

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-304 304.131-0ubuntu0.14.04.2
  ProcVersionSignature: Ubuntu 4.4.0-36.55~14.04.1-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Sun Sep 18 17:27:37 2016
  DuplicateSignature: package:nvidia-304:304.131-0ubuntu0.14.04.2:package is in 
a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-03-04 (197 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.14
  SourcePackage: nvidia-graphics-drivers-304
  Title: package nvidia-304 304.131-0ubuntu0.14.04.2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1624876/+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 1540088] Re: NetworkManager crashes after upgrade, preventing nm-applet to show

2016-05-16 Thread Oleg
*** This bug is a duplicate of bug 1539634 ***
https://bugs.launchpad.net/bugs/1539634

Hi, there.

I've encountered same problem.
After getting network to work without nm I've reinstalled nm with command:

sudo apt-get install --reinstall network-manager

then, after reboot, nm works in normal mode.

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

Title:
  NetworkManager crashes after upgrade, preventing nm-applet to show

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After the last upgrade of Ubuntu 14.04.3 LTS , NetworkManager keeps
  crashing.

  after `sudo service network-manager start` I get the following output
  in dmesg:

  [2016-01-31 14:28:47]  traps: NetworkManager[11040] general protection 
ip:469fee sp:7ffc6879aa00 error:0 in NetworkManager[40+10d000]
  [2016-01-31 14:28:47]  init: network-manager main process (11040) killed by 
SEGV signal
  [2016-01-31 14:28:47]  init: network-manager main process ended, respawning
  [2016-01-31 14:28:47]  traps: NetworkManager[11049] general protection 
ip:469fee sp:7ffecca7d9d0 error:0 in NetworkManager[40+10d000]
  [2016-01-31 14:28:47]  init: network-manager main process (11049) killed by 
SEGV signal
  [2016-01-31 14:28:47]  init: network-manager main process ended, respawning
  [2016-01-31 14:28:47]  traps: NetworkManager[11062] general protection 
ip:469fee sp:7ffc218a9f50 error:0 in NetworkManager[40+10d000]
  [2016-01-31 14:28:47]  init: network-manager main process (11062) killed by 
SEGV signal
  [2016-01-31 14:28:47]  init: network-manager main process ended, respawning
  [2016-01-31 14:28:47]  traps: NetworkManager[11076] general protection 
ip:469fee sp:7fff7f128270 error:0 in NetworkManager[40+10d000]
  [2016-01-31 14:28:47]  init: network-manager main process (11076) killed by 
SEGV signal
  [2016-01-31 14:28:47]  init: network-manager main process ended, respawning
  [2016-01-31 14:28:47]  traps: NetworkManager[11088] general protection 
ip:469fee sp:7fff66528f90 error:0 in NetworkManager[40+10d000]
  [2016-01-31 14:28:47]  init: network-manager main process (11088) killed by 
SEGV signal
  [2016-01-31 14:28:47]  init: network-manager main process ended, respawning
  [2016-01-31 14:28:47]  traps: NetworkManager[11092] general protection 
ip:469fee sp:7fffab819070 error:0 in NetworkManager[40+10d000]
  [2016-01-31 14:28:47]  init: network-manager main process (11092) killed by 
SEGV signal
  [2016-01-31 14:28:47]  init: network-manager main process ended, respawning
  [2016-01-31 14:28:47]  traps: NetworkManager[11096] general protection 
ip:469fee sp:7ffe7aa91c20 error:0 in NetworkManager[40+10d000]
  [2016-01-31 14:28:47]  init: network-manager main process (11096) killed by 
SEGV signal
  [2016-01-31 14:28:47]  init: network-manager main process ended, respawning
  [2016-01-31 14:28:47]  traps: NetworkManager[11100] general protection 
ip:469fee sp:7ffedfe81460 error:0 in NetworkManager[40+10d000]
  [2016-01-31 14:28:47]  init: network-manager main process (11100) killed by 
SEGV signal
  [2016-01-31 14:28:47]  init: network-manager main process ended, respawning
  [2016-01-31 14:28:47]  traps: NetworkManager[11104] general protection 
ip:469fee sp:7ffdc475f140 error:0 in NetworkManager[40+10d000]
  [2016-01-31 14:28:47]  init: network-manager main process (11104) killed by 
SEGV signal
  [2016-01-31 14:28:47]  init: network-manager main process ended, respawning
  [2016-01-31 14:28:47]  traps: NetworkManager[11108] general protection 
ip:469fee sp:7ffdeb437010 error:0 in NetworkManager[40+10d000]
  [2016-01-31 14:28:47]  init: network-manager main process (11108) killed by 
SEGV signal
  [2016-01-31 14:28:47]  init: network-manager main process ended, respawning
  [2016-01-31 14:28:47]  init: network-manager main process (2) killed by 
SEGV signal
  [2016-01-31 14:28:47]  init: network-manager respawning too fast, stopped

  
  This problem prevents me to see nm-applet, and makes me unable to connect to 
WiFi network.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1540088/+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 1577505] [NEW] gnome-terminal window does not restore it's size after been maximized

2016-05-02 Thread Oleg
Public bug reported:

gnome-terminal window does not restore it's size after been maximized

how to reproduce:

1) open terminal
2) click maximize button in the window title 
3) click maximize button once again

window returns from maximize mode, you can see it's title, but it
doesn't restore it's size: it still fills all the screen

Release:Ubuntu 16.04 LTS
gnome-terminal: 3.18.3-1ubuntu1

** Affects: gnome-terminal (Ubuntu)
 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.
https://bugs.launchpad.net/bugs/1577505

Title:
  gnome-terminal window does not restore it's size after been maximized

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  gnome-terminal window does not restore it's size after been maximized

  how to reproduce:

  1) open terminal
  2) click maximize button in the window title 
  3) click maximize button once again

  window returns from maximize mode, you can see it's title, but it
  doesn't restore it's size: it still fills all the screen

  Release:  Ubuntu 16.04 LTS
  gnome-terminal: 3.18.3-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1577505/+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 1499680] [NEW] package gir1.2-accountsservice-1.0 0.6.35-0ubuntu7.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before atte

2015-09-25 Thread Oleg Mordach
Public bug reported:

I dont know

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: gir1.2-accountsservice-1.0 0.6.35-0ubuntu7.2
ProcVersionSignature: Ubuntu 3.19.0-30.33~14.04.1-generic 3.19.8-ckt6
Uname: Linux 3.19.0-30-generic i686
ApportVersion: 2.14.1-0ubuntu3.15
AptOrdering:
 google-chrome-stable: Install
 gir1.2-accountsservice-1.0: Configure
 google-chrome-stable: Configure
Architecture: i386
Date: Fri Sep 25 09:58:10 2015
DuplicateSignature: 
package:gir1.2-accountsservice-1.0:0.6.35-0ubuntu7.2:package is in a very bad 
inconsistent state; you should  reinstall it before attempting configuration
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2015-09-06 (18 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.4
 apt  1.0.1ubuntu2.10
SourcePackage: accountsservice
Title: package gir1.2-accountsservice-1.0 0.6.35-0ubuntu7.2 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package i386 trusty

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

Title:
  package gir1.2-accountsservice-1.0 0.6.35-0ubuntu7.2 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in accountsservice package in Ubuntu:
  New

Bug description:
  I dont know

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: gir1.2-accountsservice-1.0 0.6.35-0ubuntu7.2
  ProcVersionSignature: Ubuntu 3.19.0-30.33~14.04.1-generic 3.19.8-ckt6
  Uname: Linux 3.19.0-30-generic i686
  ApportVersion: 2.14.1-0ubuntu3.15
  AptOrdering:
   google-chrome-stable: Install
   gir1.2-accountsservice-1.0: Configure
   google-chrome-stable: Configure
  Architecture: i386
  Date: Fri Sep 25 09:58:10 2015
  DuplicateSignature: 
package:gir1.2-accountsservice-1.0:0.6.35-0ubuntu7.2:package is in a very bad 
inconsistent state; you should  reinstall it before attempting configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2015-09-06 (18 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.4
   apt  1.0.1ubuntu2.10
  SourcePackage: accountsservice
  Title: package gir1.2-accountsservice-1.0 0.6.35-0ubuntu7.2 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1499680/+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 1496427] [NEW] package gir1.2-accountsservice-1.0 0.6.35-0ubuntu7.2 failed to install/upgrade: пакунок знаходиться у поганому стані; потрібно перевстановити його до початку нал

2015-09-16 Thread Oleg Mordach
Public bug reported:

package gir1.2-accountsservice-1.0 0.6.35-0ubuntu7.2 failed to
install/upgrade: пакунок знаходиться у поганому стані; потрібно
перевстановити його до початку налаштування

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: gir1.2-accountsservice-1.0 0.6.35-0ubuntu7.2
ProcVersionSignature: Ubuntu 3.19.0-29.31~14.04.1-generic 3.19.8-ckt6
Uname: Linux 3.19.0-29-generic i686
ApportVersion: 2.14.1-0ubuntu3.13
AptOrdering:
 python-scapy: Install
 gir1.2-accountsservice-1.0: Configure
 python-scapy: Configure
Architecture: i386
Date: Wed Sep 16 15:56:31 2015
ErrorMessage: пакунок знаходиться у поганому стані; потрібно перевстановити 
його до початку налаштування
InstallationDate: Installed on 2015-09-06 (9 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.4
 apt  1.0.1ubuntu2.10
SourcePackage: accountsservice
Title: package gir1.2-accountsservice-1.0 0.6.35-0ubuntu7.2 failed to 
install/upgrade: пакунок знаходиться у поганому стані; потрібно перевстановити 
його до початку налаштування
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package i386 third-party-packages trusty

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

Title:
  package gir1.2-accountsservice-1.0 0.6.35-0ubuntu7.2 failed to
  install/upgrade: пакунок знаходиться у поганому стані; потрібно
  перевстановити його до початку налаштування

Status in accountsservice package in Ubuntu:
  New

Bug description:
  package gir1.2-accountsservice-1.0 0.6.35-0ubuntu7.2 failed to
  install/upgrade: пакунок знаходиться у поганому стані; потрібно
  перевстановити його до початку налаштування

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: gir1.2-accountsservice-1.0 0.6.35-0ubuntu7.2
  ProcVersionSignature: Ubuntu 3.19.0-29.31~14.04.1-generic 3.19.8-ckt6
  Uname: Linux 3.19.0-29-generic i686
  ApportVersion: 2.14.1-0ubuntu3.13
  AptOrdering:
   python-scapy: Install
   gir1.2-accountsservice-1.0: Configure
   python-scapy: Configure
  Architecture: i386
  Date: Wed Sep 16 15:56:31 2015
  ErrorMessage: пакунок знаходиться у поганому стані; потрібно перевстановити 
його до початку налаштування
  InstallationDate: Installed on 2015-09-06 (9 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.4
   apt  1.0.1ubuntu2.10
  SourcePackage: accountsservice
  Title: package gir1.2-accountsservice-1.0 0.6.35-0ubuntu7.2 failed to 
install/upgrade: пакунок знаходиться у поганому стані; потрібно перевстановити 
його до початку налаштування
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1496427/+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 1431582] Re: there is no wi-fi after suspend/hybernate mode

2015-04-05 Thread Oleg
Same problem on macbook 3,1

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

Title:
  there is no wi-fi after suspend/hybernate mode

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  During last three days: after suspend/hybernate mode there is no wi-
  fi. I have to turn off Network-manager and turn it on again- only
  after that wi-fi works again

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: network-manager 0.9.10.0-4ubuntu10
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.16.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Mar 13 00:56:10 2015
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-10-18 (510 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  IpRoute:
   default via 10.0.1.1 dev wlan0  proto static  metric 1024
   10.0.1.0/24 dev wlan0  proto kernel  scope link  src 10.0.1.18
   169.254.0.0/16 dev wlan0  scope link  metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME  UUID  TYPE TIMESTAMP   
TIMESTAMP-REAL  AUTOCONNECT  READONLY  DBUS-PATH
   ACTIVE  DEVICE  STATE  ACTIVE-PATH
   k3b   66a32a2c-3eac-46e3-a111-0c63e94bd135  802-11-wireless  1426197268  Пт. 
13 марта 2015 00:54:28  yes  no
/org/freedesktop/NetworkManager/Settings/0  yes wlan0   activated  
/org/freedesktop/NetworkManager/ActiveConnection/0
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH
   wlan0   wifi  connected  /org/freedesktop/NetworkManager/Devices/1  k3b  
   66a32a2c-3eac-46e3-a111-0c63e94bd135  
/org/freedesktop/NetworkManager/ActiveConnection/0
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/0  --   
   ----
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1431582/+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 1386379] Re: Audio Input switches after opening Sound Settings/Input

2015-02-12 Thread Oleg Cherkasov
I have got the same issue with Lenovo T540p and dock station connected
to DP monitor.  If my T540p docked then I have to manually selected DP
output every time I boot it.  If my laptop is undocked then fallback
output (built-in stereo) is used however there is a caveat.

Unity-control-center and sound indicator/applet do not sync sound
volume.  That means if I switch to different output manually or fallback
to stereo then sound volume stays the same from previously selected
output.  It is really annoying because I have to do it twice per day to
change the output and adjust volume.  Even if I tick Mute it may not
help because I have to really adjust the volume before doing anything
else.

I am using my laptop docked and undocked every day so it is extremely
annoying adjust output and volume.  The bug is very easy to reproduce
indeed.  Taking in account that many people use dock stations with
multiple outputs it must be fixed.  It is obvious to remember previous
output choice, keep sound volume for that output and fallback to built-
in speakers in case no other output sources found restoring volume as
well.

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

Title:
  Audio Input switches after opening Sound Settings/Input

Status in unity-control-center package in Ubuntu:
  Confirmed

Bug description:
  I use my webcam microphone as my main audio input. Under the Sound Settings, 
Input tab, I have selected my webcam. The settings are saved after a reboot or 
a log without a problem. When I open the Sound Settings again, the input 
switches to the built-in audio automatically. This happens every time I open 
the Sound Settings, no matter what.
  I've selected hundreds of times my webcam, and as long as I don't go the the 
Sound Settings, the audio input won't switch.
  This is very frustrating and it never happened until Ubuntu 14.04.

  Is there a way I can make Ubuntu respect my selection? At least a
  workaround?

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.3+14.04.20140922-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4
  Uname: Linux 3.13.0-34-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Oct 27 15:01:24 2014
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2014-08-19 (69 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_unity-control-center:
   activity-log-manager 0.9.7-0ubuntu14
   deja-dup 30.0-0ubuntu4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1386379/+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 1277245] Re: nvidia prime causing mouse and screen to freeze

2015-01-13 Thread Oleg Cherkasov
Hi, I am still having that issue on 14.04 Lenovo T540p with nvidia-prime
activated.

I had suspected it is 'Disable while typing' option in MouseTouchpad
configuration however disabling the option does not solve the problem.
At the same time 14.04 on Dell V131 does not have any issues with
touchpad at all.  Switching to any virtual console and back C-A-F7 is a
workaround as mentioned above however does not solve actual problem.  I
wonder it is still 'Disable while typing' issue because I had similar
issue in a past.

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

Title:
  nvidia prime causing mouse and screen to freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I upgraded to Ubuntu Trusty Tahr . Currently running with updates as of 6th 
Feb. 64bit. 
  After installing nvidia-prime and nvidia-331, i can see frequent mouse 
freezes. Once the mouse is frozen, it doesn't allow Alt+Tab functionality. Only 
way to get out of this is by pressing Ctrl+Alt+F1 . I can bring back by 
unloading and loading the psmouse module

  modprobe -r psmouse.

  lspci | grep VGA
  00:02.0 VGA compatible controller: Intel Corporation Core Processor 
Integrated Graphics Controller (rev 18)
  01:00.0 VGA compatible controller: NVIDIA Corporation GT218M [GeForce 310M] 
(rev a2)

  
  uname -a
  Linux Vostro-3300 3.13.0-6-generic #23-Ubuntu SMP Thu Jan 30 09:48:03 UTC 
2014 x86_64 x86_64 x86_64 GNU/Linux
  cat /etc/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=14.04
  DISTRIB_CODENAME=trusty
  DISTRIB_DESCRIPTION=Ubuntu Trusty Tahr (development branch)

  This issue does not occur while running the opensource driver.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1277245/+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 1409868] [NEW] nvidia-331 331.113-0ubuntu0.0.4: nvidia-331 kernel module failed to build

2015-01-12 Thread Bejenari Oleg
Public bug reported:

automatic update failed

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: nvidia-331 331.113-0ubuntu0.0.4
ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
Uname: Linux 3.13.0-44-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: i386
DKMSKernelVersion: 3.13.0-44-generic
Date: Mon Jan 12 21:12:28 2015
InstallationDate: Installed on 2014-04-25 (262 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417)
PackageVersion: 331.113-0ubuntu0.0.4
SourcePackage: nvidia-graphics-drivers-331
Title: nvidia-331 331.113-0ubuntu0.0.4: nvidia-331 kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-331 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 trusty

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

Title:
  nvidia-331 331.113-0ubuntu0.0.4: nvidia-331 kernel module failed to
  build

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  New

Bug description:
  automatic update failed

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331 331.113-0ubuntu0.0.4
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: i386
  DKMSKernelVersion: 3.13.0-44-generic
  Date: Mon Jan 12 21:12:28 2015
  InstallationDate: Installed on 2014-04-25 (262 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417)
  PackageVersion: 331.113-0ubuntu0.0.4
  SourcePackage: nvidia-graphics-drivers-331
  Title: nvidia-331 331.113-0ubuntu0.0.4: nvidia-331 kernel module failed to 
build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1409868/+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 1401595] [NEW] nvidia-331 331.113-0ubuntu0.0.4: nvidia-331 kernel module failed to build

2014-12-11 Thread Oleg Cherkasov
Public bug reported:

Failed to build new module after upgrading to kernel  3.13.0-43-generic.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: nvidia-331 331.113-0ubuntu0.0.4
ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10
Uname: Linux 3.13.0-40-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
DKMSKernelVersion: 3.13.0-43-generic
Date: Thu Dec 11 17:36:13 2014
InstallationDate: Installed on 2013-04-25 (594 days ago)
InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
PackageVersion: 331.113-0ubuntu0.0.4
SourcePackage: nvidia-graphics-drivers-331
Title: nvidia-331 331.113-0ubuntu0.0.4: nvidia-331 kernel module failed to build
UpgradeStatus: Upgraded to trusty on 2014-04-22 (233 days ago)
modified.conffile..etc.modprobe.d.nvidia.331.hybrid.conf: [deleted]

** Affects: nvidia-graphics-drivers-331 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package third-party-packages trusty

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

Title:
  nvidia-331 331.113-0ubuntu0.0.4: nvidia-331 kernel module failed to
  build

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  New

Bug description:
  Failed to build new module after upgrading to kernel
  3.13.0-43-generic.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331 331.113-0ubuntu0.0.4
  ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10
  Uname: Linux 3.13.0-40-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  DKMSKernelVersion: 3.13.0-43-generic
  Date: Thu Dec 11 17:36:13 2014
  InstallationDate: Installed on 2013-04-25 (594 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  PackageVersion: 331.113-0ubuntu0.0.4
  SourcePackage: nvidia-graphics-drivers-331
  Title: nvidia-331 331.113-0ubuntu0.0.4: nvidia-331 kernel module failed to 
build
  UpgradeStatus: Upgraded to trusty on 2014-04-22 (233 days ago)
  modified.conffile..etc.modprobe.d.nvidia.331.hybrid.conf: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1401595/+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 1401595] Re: nvidia-331 331.113-0ubuntu0.0.4: nvidia-331 kernel module failed to build

2014-12-11 Thread Oleg Cherkasov
Have got an error message:

run-parts: executing /etc/kernel/postinst.d/dkms 3.13.0-43-generic /boot/vmlinuz
-3.13.0-43-generic
Error! Bad return status for module build on kernel: 3.13.0-43-generic (x86_64)
Consult /var/lib/dkms/nvidia-331/331.113/build/make.log for more information.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.13.0-43-generic /b
oot/vmlinuz-3.13.0-43-generic

However actual nvidia module had been build and installed with no
problem!

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

Title:
  nvidia-331 331.113-0ubuntu0.0.4: nvidia-331 kernel module failed to
  build

Status in nvidia-graphics-drivers-331 package in Ubuntu:
  New

Bug description:
  Failed to build new module after upgrading to kernel
  3.13.0-43-generic.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: nvidia-331 331.113-0ubuntu0.0.4
  ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10
  Uname: Linux 3.13.0-40-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  DKMSKernelVersion: 3.13.0-43-generic
  Date: Thu Dec 11 17:36:13 2014
  InstallationDate: Installed on 2013-04-25 (594 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  PackageVersion: 331.113-0ubuntu0.0.4
  SourcePackage: nvidia-graphics-drivers-331
  Title: nvidia-331 331.113-0ubuntu0.0.4: nvidia-331 kernel module failed to 
build
  UpgradeStatus: Upgraded to trusty on 2014-04-22 (233 days ago)
  modified.conffile..etc.modprobe.d.nvidia.331.hybrid.conf: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1401595/+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 1389842] [NEW] nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build

2014-11-05 Thread Oleg Pogorilyi
Public bug reported:

autoreport during update

ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: nvidia-331 331.89-0ubuntu5
ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
Uname: Linux 3.16.0-24-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
DKMSKernelVersion: 3.16.0-25-generic
Date: Wed Nov  5 19:31:54 2014
InstallationDate: Installed on 2014-08-12 (84 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2)
PackageVersion: 331.89-0ubuntu5
SourcePackage: nvidia-graphics-drivers-331
Title: nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build
UpgradeStatus: Upgraded to utopic on 2014-11-01 (4 days ago)

** Affects: nvidia-graphics-drivers-331 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package utopic

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

Title:
  nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build

Status in “nvidia-graphics-drivers-331” package in Ubuntu:
  New

Bug description:
  autoreport during update

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: nvidia-331 331.89-0ubuntu5
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  DKMSKernelVersion: 3.16.0-25-generic
  Date: Wed Nov  5 19:31:54 2014
  InstallationDate: Installed on 2014-08-12 (84 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  PackageVersion: 331.89-0ubuntu5
  SourcePackage: nvidia-graphics-drivers-331
  Title: nvidia-331 331.89-0ubuntu5: nvidia-331 kernel module failed to build
  UpgradeStatus: Upgraded to utopic on 2014-11-01 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1389842/+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 1217585]

2014-10-19 Thread Oleg-3
Created attachment 107979
noise example

In glxgears on some frames appears color noise, and it disappears or changes on 
next frame.
Noise appears at some frames in glxgears, and it disappears or on next frame.
Same style noise may appear (shuffled pixels) while scrolling in Firefox or 
switching tabs.

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

Title:
  System hangs after some time with nouveau and GT240

Status in Accelerated Xorg driver for nVidia cards:
  Confirmed
Status in “xserver-xorg-video-nouveau” package in Ubuntu:
  Confirmed
Status in “xserver-xorg-video-nouveau” package in Fedora:
  Unknown

Bug description:
  With the Nouveau driver I get random system hangs in the Live CD - any
  version since it was switched to nouveau up until today's daily
  images. It happens after half an hour to a couple of hours usage and
  affects installed systems as well, until they are switched to the
  proprietary driver.

  This is a well known bug in other trackers but I can't see it anywhere
  on Launchpad, so I'm reporting it and will add bug watches.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xserver-xorg-video-nouveau 1:1.0.8-0ubuntu3
  ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
  Uname: Linux 3.11.0-4-generic x86_64
  ApportVersion: 2.12.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.336
  Date: Tue Aug 27 22:16:06 2013
  LiveMediaBuild: Xubuntu 13.10 Saucy Salamander - Alpha amd64 (20130827)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: No upgrade log present (probably fresh install)

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

2014-10-19 Thread Oleg-3
Awesome, it works for me.

Linux 3.14.14-gentoo
OpenGL vendor string: nouveau
OpenGL renderer string: Gallium 0.4 on NVA3
OpenGL core profile version string: 3.3 (Core Profile) Mesa 10.2.7
OpenGL core profile shading language version string: 3.30

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

Title:
  System hangs after some time with nouveau and GT240

Status in Accelerated Xorg driver for nVidia cards:
  Confirmed
Status in “xserver-xorg-video-nouveau” package in Ubuntu:
  Confirmed
Status in “xserver-xorg-video-nouveau” package in Fedora:
  Unknown

Bug description:
  With the Nouveau driver I get random system hangs in the Live CD - any
  version since it was switched to nouveau up until today's daily
  images. It happens after half an hour to a couple of hours usage and
  affects installed systems as well, until they are switched to the
  proprietary driver.

  This is a well known bug in other trackers but I can't see it anywhere
  on Launchpad, so I'm reporting it and will add bug watches.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xserver-xorg-video-nouveau 1:1.0.8-0ubuntu3
  ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
  Uname: Linux 3.11.0-4-generic x86_64
  ApportVersion: 2.12.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.336
  Date: Tue Aug 27 22:16:06 2013
  LiveMediaBuild: Xubuntu 13.10 Saucy Salamander - Alpha amd64 (20130827)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: No upgrade log present (probably fresh install)

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

2014-10-19 Thread Oleg-3
Created attachment 107980
kernel log for weston freeze

In weston at some time computer stops responding at keyboard and mouse
events.

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

Title:
  System hangs after some time with nouveau and GT240

Status in Accelerated Xorg driver for nVidia cards:
  Confirmed
Status in “xserver-xorg-video-nouveau” package in Ubuntu:
  Confirmed
Status in “xserver-xorg-video-nouveau” package in Fedora:
  Unknown

Bug description:
  With the Nouveau driver I get random system hangs in the Live CD - any
  version since it was switched to nouveau up until today's daily
  images. It happens after half an hour to a couple of hours usage and
  affects installed systems as well, until they are switched to the
  proprietary driver.

  This is a well known bug in other trackers but I can't see it anywhere
  on Launchpad, so I'm reporting it and will add bug watches.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xserver-xorg-video-nouveau 1:1.0.8-0ubuntu3
  ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
  Uname: Linux 3.11.0-4-generic x86_64
  ApportVersion: 2.12.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.336
  Date: Tue Aug 27 22:16:06 2013
  LiveMediaBuild: Xubuntu 13.10 Saucy Salamander - Alpha amd64 (20130827)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/nouveau/+bug/1217585/+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 1328305] Re: [HP Pavilion 15 Notebook PC, Realtek ALC282, Speaker, Internal] fails after a while

2014-08-09 Thread Oleg Fritz
Sorry for not-related to this issue message, but i want to notify, i was 
erroneously added second options line, which causes issues with mic-detection. 
It may be misleading other users.
Correct module options line is:

options snd_hda_intel index=0 model=auto vid=1022 pid=780d enable_msi=0

and no more.

Having another issue. I'm using external speakers through converter
TRRS to TRS splitter because this machine has 2 in 1 headphones/mic
3.5mm jack. When i plug this cable, pavucontrol says my internal
microphone is unavailable, and microphone is plugged in. And i can't use
it for skype.

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

Title:
  [HP Pavilion 15 Notebook PC, Realtek ALC282, Speaker, Internal] fails
  after a while

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

Bug description:
  My sound stutters and skips in different web browser and on offline
  media players like rhythembox and vlc.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tat1842 F pulseaudio
   /dev/snd/controlC0:  tat1842 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Jun  9 23:56:42 2014
  InstallationDate: Installed on 2014-05-22 (18 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_Type: Sound works for a while, then breaks
  Title: [HP Pavilion 15 Notebook PC, Realtek ALC282, Speaker, Internal] fails 
after a while
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/19/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.11
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2163
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 29.22
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.11:bd07/19/2013:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr08961030410620100:rvnHewlett-Packard:rn2163:rvr29.22:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion 15 Notebook PC
  dmi.product.version: 08961030410620100
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1328305/+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 1354580] [NEW] Keyboard layout cannot be changed with keyboard shortcut when entering a password at unlock screen

2014-08-08 Thread Oleg
Public bug reported:

If my keyboard layout was different from English (Russian, for example), and 
the screen locks, then it stays in this nondefault layout and it may be changed 
to English only with mouse. That is very unconvinient.
This behaviour appeared only in Ubuntu 14.04
I use the default desktop manager (I believe it is Unity) and the default login 
manager (I believe it is LightDM).
It is not related only to my computer. A friend of mine also suffered from this 
new behaviour since 14.04, and that was one of the reasons why he switched to 
another distro.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic i686
NonfreeKernelModules: nvidia
.proc.driver.nvidia.gpus.0: Error: [Errno 21] Это каталог: 
'/proc/driver/nvidia/gpus/0'
.proc.driver.nvidia.registry: Binary: 
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86 Kernel Module  331.38  Wed Jan  8 18:44:57 PST 
2014
 GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.3
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Fri Aug  8 23:27:01 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:10bc]
 NVIDIA Corporation GF108M [GeForce GT 630M] [10de:0de9] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:10bc]
InstallationDate: Installed on 2014-05-01 (99 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417)
MachineType: ASUSTeK COMPUTER INC. K75VM
ProcEnviron:
 LANGUAGE=ru_UA:ru
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=ru_UA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic 
root=UUID=4ce764bf-e756-4c1d-b53b-a1af72c0cc55 ro quiet splash
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/22/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 232
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: K75VM
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No  Asset  Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr232:bd05/22/2014:svnASUSTeKCOMPUTERINC.:pnK75VM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK75VM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: K75VM
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Fri Aug  8 22:51:48 2014
xserver.configfile: /etc/X11/xorg.conf
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 721 
 vendor LGD
xserver.version: 2:1.15.1-0ubuntu2.1

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


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

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

Title:
  Keyboard layout cannot be changed with keyboard shortcut when entering
  a password at unlock screen

Status in “xorg” package in Ubuntu:
  New

Bug description:
  If my keyboard layout was different from English (Russian, for example), and 
the screen locks, then it stays in this nondefault layout and it may be changed 
to English only with mouse. That is very unconvinient.
  This behaviour appeared only in Ubuntu 14.04
  I use the default desktop manager (I believe it is Unity) and the default 
login manager (I believe it is LightDM).
  It is not related only to my computer. A friend of mine also suffered from 
this new behaviour since 14.04, and that was one of the reasons why he switched 
to another distro.


[Desktop-packages] [Bug 1354582] [NEW] Keyboard shortcuts like Ctrl-C do not work in non-english keyboard layout

2014-08-08 Thread Oleg
Public bug reported:

When my keyboard layout is different from English (I use Russian quite often), 
keyboard shortcuts do not work in any applications. For example, Ctrl-C and 
Ctrl-V do not work. They work only in English keyboard layout.
This has never happened in previous distros before 14.04. I doubt it very much 
that it is related to my hardware or nondefault settings, because a friend of 
mine suffered from the same problem and decided to switch to another distro.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic i686
NonfreeKernelModules: nvidia
.proc.driver.nvidia.gpus.0: Error: [Errno 21] Это каталог: 
'/proc/driver/nvidia/gpus/0'
.proc.driver.nvidia.registry: Binary: 
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86 Kernel Module  331.38  Wed Jan  8 18:44:57 PST 
2014
 GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.3
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Fri Aug  8 23:37:19 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:10bc]
 NVIDIA Corporation GF108M [GeForce GT 630M] [10de:0de9] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:10bc]
InstallationDate: Installed on 2014-05-01 (99 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417)
MachineType: ASUSTeK COMPUTER INC. K75VM
ProcEnviron:
 LANGUAGE=ru_UA:ru
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=ru_UA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic 
root=UUID=4ce764bf-e756-4c1d-b53b-a1af72c0cc55 ro quiet splash
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/22/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 232
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: K75VM
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No  Asset  Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr232:bd05/22/2014:svnASUSTeKCOMPUTERINC.:pnK75VM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK75VM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: K75VM
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Fri Aug  8 22:51:48 2014
xserver.configfile: /etc/X11/xorg.conf
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 721 
 vendor LGD
xserver.version: 2:1.15.1-0ubuntu2.1

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


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

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

Title:
  Keyboard shortcuts like Ctrl-C do not work in non-english keyboard
  layout

Status in “xorg” package in Ubuntu:
  New

Bug description:
  When my keyboard layout is different from English (I use Russian quite 
often), keyboard shortcuts do not work in any applications. For example, Ctrl-C 
and Ctrl-V do not work. They work only in English keyboard layout.
  This has never happened in previous distros before 14.04. I doubt it very 
much that it is related to my hardware or nondefault settings, because a friend 
of mine suffered from the same problem and decided to switch to another distro.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic i686
  NonfreeKernelModules: nvidia
  

[Desktop-packages] [Bug 1354580] Re: Keyboard layout cannot be changed with keyboard shortcut when entering a password at unlock screen

2014-08-08 Thread Oleg
Please close the bug, it was solved with the latest update

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

Title:
  Keyboard layout cannot be changed with keyboard shortcut when entering
  a password at unlock screen

Status in “xorg” package in Ubuntu:
  New

Bug description:
  If my keyboard layout was different from English (Russian, for example), and 
the screen locks, then it stays in this nondefault layout and it may be changed 
to English only with mouse. That is very unconvinient.
  This behaviour appeared only in Ubuntu 14.04
  I use the default desktop manager (I believe it is Unity) and the default 
login manager (I believe it is LightDM).
  It is not related only to my computer. A friend of mine also suffered from 
this new behaviour since 14.04, and that was one of the reasons why he switched 
to another distro.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic i686
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Это каталог: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86 Kernel Module  331.38  Wed Jan  8 18:44:57 PST 
2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Aug  8 23:27:01 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:10bc]
   NVIDIA Corporation GF108M [GeForce GT 630M] [10de:0de9] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:10bc]
  InstallationDate: Installed on 2014-05-01 (99 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417)
  MachineType: ASUSTeK COMPUTER INC. K75VM
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic 
root=UUID=4ce764bf-e756-4c1d-b53b-a1af72c0cc55 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/22/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 232
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: K75VM
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr232:bd05/22/2014:svnASUSTeKCOMPUTERINC.:pnK75VM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK75VM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: K75VM
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Fri Aug  8 22:51:48 2014
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 721 
   vendor LGD
  xserver.version: 2:1.15.1-0ubuntu2.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1354580/+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 1354582] Re: Keyboard shortcuts like Ctrl-C do not work in non-english keyboard layout

2014-08-08 Thread Oleg
Please, close the ticket, it was solved with the latest updated

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

Title:
  Keyboard shortcuts like Ctrl-C do not work in non-english keyboard
  layout

Status in “xorg” package in Ubuntu:
  New

Bug description:
  When my keyboard layout is different from English (I use Russian quite 
often), keyboard shortcuts do not work in any applications. For example, Ctrl-C 
and Ctrl-V do not work. They work only in English keyboard layout.
  This has never happened in previous distros before 14.04. I doubt it very 
much that it is related to my hardware or nondefault settings, because a friend 
of mine suffered from the same problem and decided to switch to another distro.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic i686
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Это каталог: 
'/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: 
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86 Kernel Module  331.38  Wed Jan  8 18:44:57 PST 
2014
   GCC version:  gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1)
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Aug  8 23:37:19 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:10bc]
   NVIDIA Corporation GF108M [GeForce GT 630M] [10de:0de9] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:10bc]
  InstallationDate: Installed on 2014-05-01 (99 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417)
  MachineType: ASUSTeK COMPUTER INC. K75VM
  ProcEnviron:
   LANGUAGE=ru_UA:ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=ru_UA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic 
root=UUID=4ce764bf-e756-4c1d-b53b-a1af72c0cc55 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/22/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 232
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: K75VM
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr232:bd05/22/2014:svnASUSTeKCOMPUTERINC.:pnK75VM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK75VM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: K75VM
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Fri Aug  8 22:51:48 2014
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 721 
   vendor LGD
  xserver.version: 2:1.15.1-0ubuntu2.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1354582/+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 1328305] Re: [HP Pavilion 15 Notebook PC, Realtek ALC282, Speaker, Internal] fails after a while

2014-08-03 Thread Oleg Fritz
Forgot to answer, but that option enable_msi=0 helped me, thanks!

Now my /etc/modprobe.d/alsa-base.conf:

options snd-usb-audio index=-2

options snd_hda_intel index=0 model=auto vid=1022 pid=780d probe_mask=1 
enable_msi=0
options snd_hda_intel index=1 model=auto vid=1002 pid=9840

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

Title:
  [HP Pavilion 15 Notebook PC, Realtek ALC282, Speaker, Internal] fails
  after a while

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

Bug description:
  My sound stutters and skips in different web browser and on offline
  media players like rhythembox and vlc.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tat1842 F pulseaudio
   /dev/snd/controlC0:  tat1842 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Jun  9 23:56:42 2014
  InstallationDate: Installed on 2014-05-22 (18 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_Type: Sound works for a while, then breaks
  Title: [HP Pavilion 15 Notebook PC, Realtek ALC282, Speaker, Internal] fails 
after a while
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/19/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.11
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2163
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 29.22
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.11:bd07/19/2013:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr08961030410620100:rvnHewlett-Packard:rn2163:rvr29.22:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion 15 Notebook PC
  dmi.product.version: 08961030410620100
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1328305/+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 1347645] [NEW] Nautilus frames provide incorrect accessibility info for menus

2014-07-23 Thread Oleg Barbashov
Public bug reported:

The Nautilus frames exposes incorrect a11y info for menus.

To reproduce:
1. Open any folder in the Nautilus.
2. Install (if not installed) Accerciser Accessibility Explorer.
3. Browse the accessibility info for opened folder frame.

Physically (by default) the menu items are located in the global menu.
But according to the exposed accessible tree the menu items parent has
unknown role and negative coordinates [-2147483648; -2147483648] and
zero sizes, the screen coordinates of menu items  are wrong (it is
placed near the top left corner of the folder frame).

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

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

Title:
  Nautilus frames provide incorrect accessibility info for menus

Status in “nautilus” package in Ubuntu:
  New

Bug description:
  The Nautilus frames exposes incorrect a11y info for menus.

  To reproduce:
  1. Open any folder in the Nautilus.
  2. Install (if not installed) Accerciser Accessibility Explorer.
  3. Browse the accessibility info for opened folder frame.

  Physically (by default) the menu items are located in the global menu.
  But according to the exposed accessible tree the menu items parent has
  unknown role and negative coordinates [-2147483648; -2147483648] and
  zero sizes, the screen coordinates of menu items  are wrong (it is
  placed near the top left corner of the folder frame).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1347645/+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 1310489] Re: xorg.conf overwritten by booting system

2014-07-23 Thread Oleg Fritz
Same issue on HP Pavilion 15-n031sr (F2U14EA)  with Ubuntu 14.04 and
lastest fglrx beta drivers.

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

Title:
  xorg.conf overwritten by booting system

Status in “ubuntu-drivers-common” package in Ubuntu:
  Confirmed
Status in “xorg” package in Ubuntu:
  In Progress

Bug description:
  Description:  Ubuntu 14.04 LTS
  Release:  14.04

  Hello,

  I am using a notebook with a quadcore AMD A10 and hybrid graficcard AMD/ATI 
Radeon HD 8650G / AMD/ATI Sun XT Radeon HD 8670A/8670M/8690M.
  After installing fglrx I generated the xorg.conf in the terminal with 'sudo 
aticonfig --adapter=all --initial' and it looked pretty good. Up to this point 
I was able to switch between the cards with the commands 'sudo aticonfig 
--px-dgpu' for the discrete card and 'sudo aticonfig --px-igpu' for the 
intigrated card to save power.
  After rebooting I realized that I was no longer able to switch between the 
cards and found that the xorg.conf will be overwritten whenever I modified it 
and reboot the system. The new (by boot) generated xorg.conf contains not the 
relevant information for switing between the cards.
  I attached both configuration in one file (xorg.conf.comparison). I will also 
provide the atisysteminfo-report.txt so far I will find the place where to 
attach.

  Edit: I fixed the error -- AIGLX error: failed to open
  /usr/lib64/dri/fglrx_dri.so, error[/usr/lib64/dri/fglrx_dri.so: cannot
  open shared object file: No such file or directory] but it changed
  not the bug of overwriting the xorg.conf.

  Regards,
  Uwe

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: fglrx
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: Unity
  Date: Mon Apr 21 08:43:29 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: fglrx, 13.350.1, 3.13.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8650G] 
[1002:990b] (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:1985]
     Subsystem: Hewlett-Packard Company Device [103c:1985]
  InstallationDate: Installed on 2014-04-20 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed 
root=UUID=fdcb1eaf-eda9-48ee-9d5b-b44e1fc06687 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/26/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.22
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1985
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 01.13
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.22:bd09/26/2013:svnHewlett-Packard:pnHPPavilion17NotebookPC:pvr0892100059160:rvnHewlett-Packard:rn1985:rvr01.13:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion 17 Notebook PC
  dmi.product.version: 0892100059160
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
  version.fglrx-installer: fglrx-installer N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Apr 21 08:29:06 2014
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, 
error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object 
file: No such file or directory]
   AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, 
error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file 
or directory]
   AIGLX error: failed to open /usr/X11R6/lib/modules/dri/fglrx_dri.so, 

[Desktop-packages] [Bug 1310489] Re: xorg.conf overwritten by booting system

2014-07-23 Thread Oleg Fritz
** Attachment added: atisysteminfo-report.txt
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1310489/+attachment/4161409/+files/atisysteminfo-report.txt

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

Title:
  xorg.conf overwritten by booting system

Status in “ubuntu-drivers-common” package in Ubuntu:
  Confirmed
Status in “xorg” package in Ubuntu:
  In Progress

Bug description:
  Description:  Ubuntu 14.04 LTS
  Release:  14.04

  Hello,

  I am using a notebook with a quadcore AMD A10 and hybrid graficcard AMD/ATI 
Radeon HD 8650G / AMD/ATI Sun XT Radeon HD 8670A/8670M/8690M.
  After installing fglrx I generated the xorg.conf in the terminal with 'sudo 
aticonfig --adapter=all --initial' and it looked pretty good. Up to this point 
I was able to switch between the cards with the commands 'sudo aticonfig 
--px-dgpu' for the discrete card and 'sudo aticonfig --px-igpu' for the 
intigrated card to save power.
  After rebooting I realized that I was no longer able to switch between the 
cards and found that the xorg.conf will be overwritten whenever I modified it 
and reboot the system. The new (by boot) generated xorg.conf contains not the 
relevant information for switing between the cards.
  I attached both configuration in one file (xorg.conf.comparison). I will also 
provide the atisysteminfo-report.txt so far I will find the place where to 
attach.

  Edit: I fixed the error -- AIGLX error: failed to open
  /usr/lib64/dri/fglrx_dri.so, error[/usr/lib64/dri/fglrx_dri.so: cannot
  open shared object file: No such file or directory] but it changed
  not the bug of overwriting the xorg.conf.

  Regards,
  Uwe

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: fglrx
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: Unity
  Date: Mon Apr 21 08:43:29 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: fglrx, 13.350.1, 3.13.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8650G] 
[1002:990b] (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:1985]
     Subsystem: Hewlett-Packard Company Device [103c:1985]
  InstallationDate: Installed on 2014-04-20 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed 
root=UUID=fdcb1eaf-eda9-48ee-9d5b-b44e1fc06687 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/26/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.22
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1985
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 01.13
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.22:bd09/26/2013:svnHewlett-Packard:pnHPPavilion17NotebookPC:pvr0892100059160:rvnHewlett-Packard:rn1985:rvr01.13:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion 17 Notebook PC
  dmi.product.version: 0892100059160
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
  version.fglrx-installer: fglrx-installer N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Apr 21 08:29:06 2014
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, 
error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object 
file: No such file or directory]
   AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, 
error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file 
or directory]
   AIGLX error: 

[Desktop-packages] [Bug 1310489] Re: xorg.conf overwritten by booting system

2014-07-23 Thread Oleg Fritz
** Attachment added: gpu-manager.log
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1310489/+attachment/4161410/+files/gpu-manager.log

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

Title:
  xorg.conf overwritten by booting system

Status in “ubuntu-drivers-common” package in Ubuntu:
  Confirmed
Status in “xorg” package in Ubuntu:
  In Progress

Bug description:
  Description:  Ubuntu 14.04 LTS
  Release:  14.04

  Hello,

  I am using a notebook with a quadcore AMD A10 and hybrid graficcard AMD/ATI 
Radeon HD 8650G / AMD/ATI Sun XT Radeon HD 8670A/8670M/8690M.
  After installing fglrx I generated the xorg.conf in the terminal with 'sudo 
aticonfig --adapter=all --initial' and it looked pretty good. Up to this point 
I was able to switch between the cards with the commands 'sudo aticonfig 
--px-dgpu' for the discrete card and 'sudo aticonfig --px-igpu' for the 
intigrated card to save power.
  After rebooting I realized that I was no longer able to switch between the 
cards and found that the xorg.conf will be overwritten whenever I modified it 
and reboot the system. The new (by boot) generated xorg.conf contains not the 
relevant information for switing between the cards.
  I attached both configuration in one file (xorg.conf.comparison). I will also 
provide the atisysteminfo-report.txt so far I will find the place where to 
attach.

  Edit: I fixed the error -- AIGLX error: failed to open
  /usr/lib64/dri/fglrx_dri.so, error[/usr/lib64/dri/fglrx_dri.so: cannot
  open shared object file: No such file or directory] but it changed
  not the bug of overwriting the xorg.conf.

  Regards,
  Uwe

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  NonfreeKernelModules: fglrx
  .tmp.unity.support.test.0:

  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: Unity
  Date: Mon Apr 21 08:43:29 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: fglrx, 13.350.1, 3.13.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8650G] 
[1002:990b] (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:1985]
     Subsystem: Hewlett-Packard Company Device [103c:1985]
  InstallationDate: Installed on 2014-04-20 (0 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed 
root=UUID=fdcb1eaf-eda9-48ee-9d5b-b44e1fc06687 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/26/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.22
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1985
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 01.13
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.22:bd09/26/2013:svnHewlett-Packard:pnHPPavilion17NotebookPC:pvr0892100059160:rvnHewlett-Packard:rn1985:rvr01.13:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion 17 Notebook PC
  dmi.product.version: 0892100059160
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
  version.fglrx-installer: fglrx-installer N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Mon Apr 21 08:29:06 2014
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, 
error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object 
file: No such file or directory]
   AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, 
error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file 
or directory]
   AIGLX error: failed to open 

[Desktop-packages] [Bug 1328305] Re: [HP Pavilion 15 Notebook PC, Realtek ALC282, Speaker, Internal] fails after a while

2014-07-18 Thread Oleg Fritz
attaching lshw output.

Also in /etc/modprobe.d/alsa-base.conf i added

options snd_hda_intel index=0 model=auto vid=1022 pid=780d probe_mask=1
options snd_hda_intel index=1 model=auto vid=1002 pid=9840

and i tried http://ubuntuforums.org/showthread.php?t=2173738 but without
success

** Attachment added: lshw
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1328305/+attachment/4155759/+files/lshw.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/1328305

Title:
  [HP Pavilion 15 Notebook PC, Realtek ALC282, Speaker, Internal] fails
  after a while

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

Bug description:
  My sound stutters and skips in different web browser and on offline
  media players like rhythembox and vlc.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tat1842 F pulseaudio
   /dev/snd/controlC0:  tat1842 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Jun  9 23:56:42 2014
  InstallationDate: Installed on 2014-05-22 (18 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_Type: Sound works for a while, then breaks
  Title: [HP Pavilion 15 Notebook PC, Realtek ALC282, Speaker, Internal] fails 
after a while
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/19/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.11
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2163
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 29.22
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.11:bd07/19/2013:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr08961030410620100:rvnHewlett-Packard:rn2163:rvr29.22:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion 15 Notebook PC
  dmi.product.version: 08961030410620100
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1328305/+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 1328305] Re: [HP Pavilion 15 Notebook PC, Realtek ALC282, Speaker, Internal] fails after a while

2014-07-18 Thread Oleg Fritz
Have same issue too. 
I removed pulseaudio, but sound still freezes randomly in browsers, local 
audacious playback and skype (most annoying) too.   Very often my sound repeats 
with one fragment 10-20 times, then continue play in normal way


# uname -a
Linux oleg-HP-Pavilion 3.13.0-30-generic #55-Ubuntu SMP Fri Jul 4 21:40:53 UTC 
2014 x86_64 x86_64 x86_64 GNU/Linux


** Attachment added: alsa-info.sh
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1328305/+attachment/4155758/+files/alsa-info.txt.zDfpfBsNxe

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

Title:
  [HP Pavilion 15 Notebook PC, Realtek ALC282, Speaker, Internal] fails
  after a while

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

Bug description:
  My sound stutters and skips in different web browser and on offline
  media players like rhythembox and vlc.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tat1842 F pulseaudio
   /dev/snd/controlC0:  tat1842 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Jun  9 23:56:42 2014
  InstallationDate: Installed on 2014-05-22 (18 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_Type: Sound works for a while, then breaks
  Title: [HP Pavilion 15 Notebook PC, Realtek ALC282, Speaker, Internal] fails 
after a while
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/19/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.11
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2163
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 29.22
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.11:bd07/19/2013:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr08961030410620100:rvnHewlett-Packard:rn2163:rvr29.22:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion 15 Notebook PC
  dmi.product.version: 08961030410620100
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1328305/+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 1184451] Re: Ubuntu 13.10 random screen freeze while Normal OS activites

2014-06-01 Thread Oleg Cherkasov
The same problem with 14.04 on Lenovo T540p using NVIDIA.  It seems if I
am using UltraDock with mouse and keyboard no issues however with
trackpad the coursor may freeze eventually and the only way to fix the
problem would be C-A-F1 and then back C-A-F7.

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

Title:
  Ubuntu 13.10 random screen freeze while Normal OS activites

Status in “xorg-server” package in Ubuntu:
  Incomplete

Bug description:
  *PLEASE DO NOT MAKE A COMMENT IN THIS REPORT*
  As this issue is hardware dependent, not symptom(s), and the original 
reporter (Naveen) has not provided the hardware in use, this bug report is not 
about you or your hardware, so please do not make a comment. Instead, file a 
new bug report. Thanks.
  *

  I have recently, re-installed fresh ubuntu 13.10 distribution release. But 
everything worked fine. until recently i had strange problem of my display 
screen getting freezed randomly; but no response to either mouse/keyboard.
  But i want to point it out; it happens randomly and is not specific ?
  Other day, i had music player playing in background, but screen freezed. but 
my music was still running.
  Kindly note, i used multiple monitor setup and same issue of screen freeze 
also cropped up.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1184451/+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 1316092] [NEW] When the launcher is hidden, tearing occurs when scrolling/switching contents inside one window

2014-05-05 Thread Oleg O Andreev
Public bug reported:

When launcher is hidden, scrolling or switching in the maximized window
tears along the vertical line, where the launcher would've ended if it
was shown (i.e. (48, 0) - (48, screen height) if the launcher is 48px
wide). The easiest way to see is opening two tabs with black and white
backgrounds correspondingly and constantly switching between them.

I am not certain, but it looks like redrawing the part under the
hidden launcher is sometimes delayed for one frame.

Neither fullscreen windows nor switching between windows exhibit the
problem.

The bug did not manifest in Ubuntu 13.10.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.0+14.04.20140423-0ubuntu1.2
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic i686
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Mon May  5 15:16:01 2014
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
EcryptfsInUse: Yes
GraphicsCard:
 Intel Corporation Mobile 945GSE Express Integrated Graphics Controller 
[8086:27ae] (rev 03) (prog-if 00 [VGA controller])
   Subsystem: Samsung Electronics Co Ltd Device [144d:c062]
   Subsystem: Samsung Electronics Co Ltd Device [144d:c062]
InstallationDate: Installed on 2014-05-05 (0 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417)
MachineType: SAMSUNG ELECTRONICS CO., LTD. N140
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=0fd5a4c0-0a6d-41c9-8357-70d5248f49b2 ro quiet splash vt.handoff=7
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/30/2009
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 04CU.M010.20090930.CYH
dmi.board.name: N140
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr04CU.M010.20090930.CYH:bd09/30/2009:svnSAMSUNGELECTRONICSCO.,LTD.:pnN140:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnN140:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
dmi.product.name: N140
dmi.product.version: Not Applicable
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Mon May  5 13:39:03 2014
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id1001 
 vendor HSD
xserver.version: 2:1.15.1-0ubuntu2

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


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

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

Title:
  When the launcher is hidden, tearing occurs when scrolling/switching
  contents inside one window

Status in “unity” package in Ubuntu:
  New

Bug description:
  When launcher is hidden, scrolling or switching in the maximized
  window tears along the vertical line, where the launcher would've
  ended if it was shown (i.e. (48, 0) - (48, screen height) if the
  launcher is 48px wide). The easiest way to see is opening two tabs
  with black and white backgrounds correspondingly and constantly
  switching between them.

  I am not certain, but it looks like redrawing the part under the
  hidden launcher is sometimes delayed for one frame.

  Neither fullscreen windows nor switching between windows exhibit the
  problem.

  The bug did not manifest in Ubuntu 13.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.2.0+14.04.20140423-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  

[Desktop-packages] [Bug 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.

2014-04-22 Thread Oleg Shevelyov
Wow! Ana you're the savior! The command

 gsettings set org.gnome.desktop.wm.keybindings switch-input-source
['AltShift_L']

worked for me! Thanks a lot.

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

Title:
  Can't set keyboard layout change to alt+shift, ctrl+shift, etc.

Status in Gnome Settings Daemon:
  Invalid
Status in Ubuntu GNOME:
  Confirmed
Status in “gnome-control-center” package in Ubuntu:
  Fix Released
Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged
Status in “gnome-settings-daemon” source package in Saucy:
  Triaged
Status in “gnome-control-center” package in ALT Linux:
  Unknown
Status in “gnome-control-center” package in Baltix:
  Confirmed
Status in “gnome-control-center” package in Gentoo Linux:
  Invalid
Status in “gnome-control-center” package in Mandriva:
  Invalid

Bug description:
  ***
  The old PPA, ppa:attente/1218322 is superceded by the following one. You can 
remove the old repository using ppa-purge.
  ***

  A PPA which should provide some relief for this issue is available at
  https://launchpad.net/~attente/+archive/modifier-only-input-switch. To
  install:

  sudo add-apt-repository ppa:attente/modifier-only-input-switch
  sudo apt-get update
  sudo apt-get upgrade
  (log out, log in)

  If the packages improve the situation for you, you can pin them using:

  sudo apt-mark hold compiz
  sudo apt-mark hold gnome-settings-daemon
  sudo apt-mark hold unity

  If the packages don't work for you, you can purge them using:

  sudo ppa-purge ppa:attente/modifier-only-input-switch

  === compiz ===

  Impact: modifier-only key bindings need to be independent of key-press
  order, there's no support for double tapping two modifier keys of the
  same type

  Test case:
  - add at least two input sources through gnome-control-center's text entry 
settings
  - use gsettings to set the input switching shortcut to ctrl+left shift: 
gsettings set org.gnome.desktop.wm.keybindings switch-input-source 
['PrimaryShift_L']
  - holding left shift, press and release ctrl
  - the current input source should change

  Regression potential: possible, but highly unlikely, that some key
  bindings may be triggered due to the removal of some code that would
  normally prevent a possible tap from occurring.

  === unity ===

  Impact: gnome-settings-daemon eats modifier-only shortcuts preventing
  them from propagating down to applications

  Test case:
  - open gnome-control-center's text input settings
  - set the next input source key binding to ctrl+left shift
  - open gnome-terminal
  - press ctrl+shift+t
  - gnome-terminal should open a new tab

  Regression potential: the additional input switch key bindings could
  collide with other functionality such as opening the dash or hud

  === gnome-control-center ===

  Impact: the UI to change the layout switching keys doesn't work

  Test case:
  - open gnome-control-center's text input settings
  - click on the next layout key entry
  - try entering a key combinaison (e.g ctrl-space)
  - the UI should reflect the new keys

  Regression potential: that UI was not working before, it should only
  be an improvement (some key combos are not working as expected, that's
  another issue and shouldn't be mixed with this one)

  === gnome-settings-daemon ===

  Impact: attempting to change keyboard layouts using only modifier keys
  doesn't work

  Test case:
  - add at least two input sources through gnome-control-center's text entry 
settings
  - use gsettings to set the input switching shortcut to ctrl+left shift: 
gsettings set org.gnome.desktop.wm.keybindings switch-input-source 
['PrimaryShift_L']
  - press and release ctrl+left shift
  - the current input source should change

  Regression potential: The input switching shortcut might capture other
  non-modifier shortcuts, but users will need to consider this when
  choosing their switching shortcut anyways. For users this bug affects,
  this represents a working solution for a critical bug.

  --

  Test results for different keyboard layout change hotkeys may be
  viewed and added in the Google Docs table, created by Norbert
  
(https://docs.google.com/spreadsheet/ccc?key=0Ao5e713Ig9g_dEJrX2NRYlpLWWVzSWxsVXU4ck9HYVEusp=sharing).

  --
  Recent discovered bugs related to keyboard layouts:
     * keyboard layout settings must be consistent between gnome-control-center 
keyboard, indicator-keyboard and gnome-tweak-tool and /etc/default/keyboard 
(bug 1270574)
     * Ubuntu 14.04 should have gnome-tweak-tool installed by default because 
of many settings that are missed gnome-control-center (bug 1270572)
     * Please add ability to set keyboard shortcuts to unity-control-center 
launched from GNOME session FlashBack (Compiz and Metacity) (bug 1282637)
     * Unable to rename new folder in GtkFileChooserDialog 

[Desktop-packages] [Bug 1310596] [NEW] Video flickering after pause if VDPAU hardware acceleration used

2014-04-21 Thread Oleg Nightwing Lomakin
Public bug reported:

1. Open any file compatible file with vdpau and your hardware in mplayer or mpv.
2. Pause for 5 sec.
3. Unpause and get flickering.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: mesa-vdpau-drivers 10.1.0-4ubuntu5
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
.tmp.unity.support.test.0:

ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Mon Apr 21 16:20:50 2014
DistUpgraded: 2014-04-19 21:04:48,002 DEBUG enabling apt cron job
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus:
 fwts-efi-runtime-dkms, 14.03.01, 3.13.0-24-generic, x86_64: installed
 vboxhost, 4.3.10, 3.13.0-24-generic, x86_64: installed
 virtualbox-guest, 4.3.10, 3.13.0-24-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8210] [1002:9834] 
(prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:3803]
InstallationDate: Installed on 2013-12-23 (118 days ago)
InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1)
MachineType: LENOVO 20240
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed 
root=UUID=9f5c3b8c-19fd-40e7-9750-f6239869a300 ro quiet splash elevator=noop 
radeon.dpm=1 vt.handoff=7
SourcePackage: mesa
UpgradeStatus: Upgraded to trusty on 2014-04-19 (1 days ago)
dmi.bios.date: 11/05/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: 82CN24WW(V2.04)
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Lenovo G505
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo G505
dmi.modalias: 
dmi:bvnLENOVO:bvr82CN24WW(V2.04):bd11/05/2013:svnLENOVO:pn20240:pvrLenovoG505:rvnLENOVO:rnLenovoG505:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoG505:
dmi.product.name: 20240
dmi.product.version: Lenovo G505
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.52-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Mon Apr 21 09:10:59 2014
xserver.configfile: default
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.15.1-0ubuntu2
xserver.video_driver: radeon

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


** Tags: amd64 apport-bug compiz-0.9 mesa trusty ubuntu

** Description changed:

  1. Open any file compatible file with vdpau and your hardware in mplayer or 
mpv.
  2. Pause for 5 sec.
  3. Unpause and get flickering.
- $ lsb_release -rd
- Ubuntu 14.04, 3.13.0-24-generic kernel. 
- $ LANG=C apt-cache policy mesa-vdpau-drivers
- mesa-vdpau-drivers:
-   Installed: 10.1.0-4ubuntu5
-   Candidate: 10.1.0-4ubuntu5
-   Version table:
-  *** 10.1.0-4ubuntu5 0
- 500 http://ru.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
- 100 /var/lib/dpkg/status
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: mesa-vdpau-drivers 10.1.0-4ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  .tmp.unity.support.test.0:
-  
+ 
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Apr 21 16:20:50 2014
  DistUpgraded: 2014-04-19 21:04:48,002 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
-  fwts-efi-runtime-dkms, 14.03.01, 3.13.0-24-generic, x86_64: installed
-  vboxhost, 4.3.10, 3.13.0-24-generic, x86_64: installed
-  virtualbox-guest, 4.3.10, 3.13.0-24-generic, x86_64: installed
+  fwts-efi-runtime-dkms, 14.03.01, 3.13.0-24-generic, x86_64: installed
+  vboxhost, 4.3.10, 3.13.0-24-generic, x86_64: installed
+  virtualbox-guest, 4.3.10, 3.13.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8210] [1002:9834] 
(prog-if 00 [VGA controller])
-Subsystem: Lenovo Device [17aa:3803]
+  Advanced Micro 

[Desktop-packages] [Bug 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.

2014-04-10 Thread Oleg Shevelyov
The command gives me ['esperanto:qwerty'], nothing similar to grp:...
Looks like it's not my case. Thank you for explanation, anyway!

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

Title:
  Can't set keyboard layout change to alt+shift, ctrl+shift, etc.

Status in Gnome Settings Daemon:
  Invalid
Status in Ubuntu GNOME:
  Confirmed
Status in “gnome-control-center” package in Ubuntu:
  Fix Released
Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged
Status in “gnome-settings-daemon” source package in Saucy:
  Triaged
Status in “gnome-control-center” package in ALT Linux:
  Unknown
Status in “gnome-control-center” package in Baltix:
  Confirmed
Status in “gnome-control-center” package in Gentoo Linux:
  Invalid
Status in “gnome-control-center” package in Mandriva:
  Invalid

Bug description:
  ***
  The old PPA, ppa:attente/1218322 is superceded by the following one. You can 
remove the old repository using ppa-purge.
  ***

  A PPA which should provide some relief for this issue is available at
  https://launchpad.net/~attente/+archive/modifier-only-input-switch. To
  install:

  sudo add-apt-repository ppa:attente/modifier-only-input-switch
  sudo apt-get update
  sudo apt-get upgrade
  (log out, log in)

  If the packages improve the situation for you, you can pin them using:

  sudo apt-mark hold compiz
  sudo apt-mark hold gnome-settings-daemon
  sudo apt-mark hold unity

  If the packages don't work for you, you can purge them using:

  sudo ppa-purge ppa:attente/modifier-only-input-switch

  === compiz ===

  Impact: modifier-only key bindings need to be independent of key-press
  order, there's no support for double tapping two modifier keys of the
  same type

  Test case:
  - add at least two input sources through gnome-control-center's text entry 
settings
  - use gsettings to set the input switching shortcut to ctrl+left shift: 
gsettings set org.gnome.desktop.wm.keybindings switch-input-source 
['PrimaryShift_L']
  - holding left shift, press and release ctrl
  - the current input source should change

  Regression potential: possible, but highly unlikely, that some key
  bindings may be triggered due to the removal of some code that would
  normally prevent a possible tap from occurring.

  === unity ===

  Impact: gnome-settings-daemon eats modifier-only shortcuts preventing
  them from propagating down to applications

  Test case:
  - open gnome-control-center's text input settings
  - set the next input source key binding to ctrl+left shift
  - open gnome-terminal
  - press ctrl+shift+t
  - gnome-terminal should open a new tab

  Regression potential: the additional input switch key bindings could
  collide with other functionality such as opening the dash or hud

  === gnome-control-center ===

  Impact: the UI to change the layout switching keys doesn't work

  Test case:
  - open gnome-control-center's text input settings
  - click on the next layout key entry
  - try entering a key combinaison (e.g ctrl-space)
  - the UI should reflect the new keys

  Regression potential: that UI was not working before, it should only
  be an improvement (some key combos are not working as expected, that's
  another issue and shouldn't be mixed with this one)

  === gnome-settings-daemon ===

  Impact: attempting to change keyboard layouts using only modifier keys
  doesn't work

  Test case:
  - add at least two input sources through gnome-control-center's text entry 
settings
  - use gsettings to set the input switching shortcut to ctrl+left shift: 
gsettings set org.gnome.desktop.wm.keybindings switch-input-source 
['PrimaryShift_L']
  - press and release ctrl+left shift
  - the current input source should change

  Regression potential: The input switching shortcut might capture other
  non-modifier shortcuts, but users will need to consider this when
  choosing their switching shortcut anyways. For users this bug affects,
  this represents a working solution for a critical bug.

  --

  Test results for different keyboard layout change hotkeys may be
  viewed and added in the Google Docs table, created by Norbert
  
(https://docs.google.com/spreadsheet/ccc?key=0Ao5e713Ig9g_dEJrX2NRYlpLWWVzSWxsVXU4ck9HYVEusp=sharing).

  --
  Recent discovered bugs related to keyboard layouts:
     * keyboard layout settings must be consistent between gnome-control-center 
keyboard, indicator-keyboard and gnome-tweak-tool and /etc/default/keyboard 
(bug 1270574)
     * Ubuntu 14.04 should have gnome-tweak-tool installed by default because 
of many settings that are missed gnome-control-center (bug 1270572)
     * Please add ability to set keyboard shortcuts to unity-control-center 
launched from GNOME session FlashBack (Compiz and Metacity) (bug 1282637)
     * Unable to rename new folder in GtkFileChooserDialog while changing 

[Desktop-packages] [Bug 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.

2014-04-09 Thread Oleg Shevelyov
Roman, could you, please, give us some details of how did you exactly
worked it around? I've tried most of options suggested in this thread,
but the bug is still there. At the moment, I use Alt-Shift-Space
combination to change layouts which is very inconvenient.

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

Title:
  Can't set keyboard layout change to alt+shift, ctrl+shift, etc.

Status in Gnome Settings Daemon:
  Invalid
Status in Ubuntu GNOME:
  Confirmed
Status in “gnome-control-center” package in Ubuntu:
  Fix Released
Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged
Status in “gnome-settings-daemon” source package in Saucy:
  Triaged
Status in “gnome-control-center” package in ALT Linux:
  Unknown
Status in “gnome-control-center” package in Baltix:
  Confirmed
Status in “gnome-control-center” package in Gentoo Linux:
  Invalid
Status in “gnome-control-center” package in Mandriva:
  Invalid

Bug description:
  ***
  The old PPA, ppa:attente/1218322 is superceded by the following one. You can 
remove the old repository using ppa-purge.
  ***

  A PPA which should provide some relief for this issue is available at
  https://launchpad.net/~attente/+archive/modifier-only-input-switch. To
  install:

  sudo add-apt-repository ppa:attente/modifier-only-input-switch
  sudo apt-get update
  sudo apt-get upgrade
  (log out, log in)

  If the packages improve the situation for you, you can pin them using:

  sudo apt-mark hold compiz
  sudo apt-mark hold gnome-settings-daemon
  sudo apt-mark hold unity

  If the packages don't work for you, you can purge them using:

  sudo ppa-purge ppa:attente/modifier-only-input-switch

  === compiz ===

  Impact: modifier-only key bindings need to be independent of key-press
  order, there's no support for double tapping two modifier keys of the
  same type

  Test case:
  - add at least two input sources through gnome-control-center's text entry 
settings
  - use gsettings to set the input switching shortcut to ctrl+left shift: 
gsettings set org.gnome.desktop.wm.keybindings switch-input-source 
['PrimaryShift_L']
  - holding left shift, press and release ctrl
  - the current input source should change

  Regression potential: possible, but highly unlikely, that some key
  bindings may be triggered due to the removal of some code that would
  normally prevent a possible tap from occurring.

  === unity ===

  Impact: gnome-settings-daemon eats modifier-only shortcuts preventing
  them from propagating down to applications

  Test case:
  - open gnome-control-center's text input settings
  - set the next input source key binding to ctrl+left shift
  - open gnome-terminal
  - press ctrl+shift+t
  - gnome-terminal should open a new tab

  Regression potential: the additional input switch key bindings could
  collide with other functionality such as opening the dash or hud

  === gnome-control-center ===

  Impact: the UI to change the layout switching keys doesn't work

  Test case:
  - open gnome-control-center's text input settings
  - click on the next layout key entry
  - try entering a key combinaison (e.g ctrl-space)
  - the UI should reflect the new keys

  Regression potential: that UI was not working before, it should only
  be an improvement (some key combos are not working as expected, that's
  another issue and shouldn't be mixed with this one)

  === gnome-settings-daemon ===

  Impact: attempting to change keyboard layouts using only modifier keys
  doesn't work

  Test case:
  - add at least two input sources through gnome-control-center's text entry 
settings
  - use gsettings to set the input switching shortcut to ctrl+left shift: 
gsettings set org.gnome.desktop.wm.keybindings switch-input-source 
['PrimaryShift_L']
  - press and release ctrl+left shift
  - the current input source should change

  Regression potential: The input switching shortcut might capture other
  non-modifier shortcuts, but users will need to consider this when
  choosing their switching shortcut anyways. For users this bug affects,
  this represents a working solution for a critical bug.

  --

  Test results for different keyboard layout change hotkeys may be
  viewed and added in the Google Docs table, created by Norbert
  
(https://docs.google.com/spreadsheet/ccc?key=0Ao5e713Ig9g_dEJrX2NRYlpLWWVzSWxsVXU4ck9HYVEusp=sharing).

  --
  Recent discovered bugs related to keyboard layouts:
     * keyboard layout settings must be consistent between gnome-control-center 
keyboard, indicator-keyboard and gnome-tweak-tool and /etc/default/keyboard 
(bug 1270574)
     * Ubuntu 14.04 should have gnome-tweak-tool installed by default because 
of many settings that are missed gnome-control-center (bug 1270572)
     * Please add ability to set keyboard shortcuts to unity-control-center 
launched from GNOME 

[Desktop-packages] [Bug 1217585]

2014-03-16 Thread Oleg-3
Created attachment 95418
another patch for gddr5 ram

I made this patch using my mmiotrace, but it doesn't help either.

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

Title:
  System hangs after some time with nouveau and GT240

Status in Accelerated Xorg driver for nVidia cards:
  Confirmed
Status in “xserver-xorg-video-nouveau” package in Ubuntu:
  Confirmed
Status in “xserver-xorg-video-nouveau” package in Fedora:
  Unknown

Bug description:
  With the Nouveau driver I get random system hangs in the Live CD - any
  version since it was switched to nouveau up until today's daily
  images. It happens after half an hour to a couple of hours usage and
  affects installed systems as well, until they are switched to the
  proprietary driver.

  This is a well known bug in other trackers but I can't see it anywhere
  on Launchpad, so I'm reporting it and will add bug watches.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xserver-xorg-video-nouveau 1:1.0.8-0ubuntu3
  ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
  Uname: Linux 3.11.0-4-generic x86_64
  ApportVersion: 2.12.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.336
  Date: Tue Aug 27 22:16:06 2013
  LiveMediaBuild: Xubuntu 13.10 Saucy Salamander - Alpha amd64 (20130827)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: No upgrade log present (probably fresh install)

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

2014-03-16 Thread Oleg-3
For me, with this patch the problem is still present. I sent my
mmiotrace (NVIDIA Corporation GT215 [GeForce GT 240]).

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

Title:
  System hangs after some time with nouveau and GT240

Status in Accelerated Xorg driver for nVidia cards:
  Confirmed
Status in “xserver-xorg-video-nouveau” package in Ubuntu:
  Confirmed
Status in “xserver-xorg-video-nouveau” package in Fedora:
  Unknown

Bug description:
  With the Nouveau driver I get random system hangs in the Live CD - any
  version since it was switched to nouveau up until today's daily
  images. It happens after half an hour to a couple of hours usage and
  affects installed systems as well, until they are switched to the
  proprietary driver.

  This is a well known bug in other trackers but I can't see it anywhere
  on Launchpad, so I'm reporting it and will add bug watches.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xserver-xorg-video-nouveau 1:1.0.8-0ubuntu3
  ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
  Uname: Linux 3.11.0-4-generic x86_64
  ApportVersion: 2.12.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.336
  Date: Tue Aug 27 22:16:06 2013
  LiveMediaBuild: Xubuntu 13.10 Saucy Salamander - Alpha amd64 (20130827)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: No upgrade log present (probably fresh install)

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

2014-03-16 Thread Oleg-3
Comment on attachment 95408
initialize stuff for gddr5 ram

Review of attachment 95408:
-

::: drivers/gpu/drm/nouveau/core/subdev/fb/ramnva3.c
@@ +365,5 @@
 + /* XXX this algorithm is insane, find some sanity to it. */
 + /* [1] MMIO32 R 0x100268 0x30030200 PFB.SUBPART_CONFIG = { 
 SELECT_MASK = 0x2 | UNK16 = 0x3 | ENABLE_MASK = 0x3 } */
 + nv_wr32(pfb, 0x10fcac, 0x1f01);
 + for (o = 0; o  4; o++) {
 + int off = offsets[i];

maybe int off = offsets[o]; ?

@@ +387,5 @@
 + for (i = 0x20, idx = 0; i  0x30; i++, idx++) {
 + int pat = pattern[2 + (idx % 2)];
 + if (i == 0x26)
 + pat = 0;
 + if (i == 0x1f)

looks like this condition is always false in this for-loop

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

Title:
  System hangs after some time with nouveau and GT240

Status in Accelerated Xorg driver for nVidia cards:
  Confirmed
Status in “xserver-xorg-video-nouveau” package in Ubuntu:
  Confirmed
Status in “xserver-xorg-video-nouveau” package in Fedora:
  Unknown

Bug description:
  With the Nouveau driver I get random system hangs in the Live CD - any
  version since it was switched to nouveau up until today's daily
  images. It happens after half an hour to a couple of hours usage and
  affects installed systems as well, until they are switched to the
  proprietary driver.

  This is a well known bug in other trackers but I can't see it anywhere
  on Launchpad, so I'm reporting it and will add bug watches.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xserver-xorg-video-nouveau 1:1.0.8-0ubuntu3
  ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
  Uname: Linux 3.11.0-4-generic x86_64
  ApportVersion: 2.12.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.336
  Date: Tue Aug 27 22:16:06 2013
  LiveMediaBuild: Xubuntu 13.10 Saucy Salamander - Alpha amd64 (20130827)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/nouveau/+bug/1217585/+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 937822] Re: [precise] F10 always opens the menu, cannot be overriden (after xkeyboard-config update)

2014-03-10 Thread Oleg Moiseichuk
I can confirm that upgrading xkb-data package to version 2.5-1ubuntu1.5
in LTS 12.04.4 doesn't resolve the problem. When I disable the mentioned
fix in ~/.config/gtk-3.0/gtk.css (F10 is disabled in terminal keyboard
combinations), F10 press still opens context menu as if Shift-F10 was
pressed.

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

Title:
  [precise] F10 always opens the menu, cannot be overriden (after
  xkeyboard-config update)

Status in GTK+ GUI Toolkit:
  Fix Released
Status in central project for keyboard configuration:
  Fix Released
Status in “gtk+2.0” package in Ubuntu:
  Fix Released
Status in “gtk+3.0” package in Ubuntu:
  Fix Released
Status in “xkeyboard-config” package in Ubuntu:
  Fix Released
Status in “gtk+2.0” source package in Precise:
  Invalid
Status in “xkeyboard-config” source package in Precise:
  Fix Released
Status in “gtk+2.0” source package in Quantal:
  Fix Released
Status in “gtk+3.0” source package in Quantal:
  Fix Released
Status in “xkeyboard-config” source package in Quantal:
  Fix Released
Status in “gtk+2.0” package in Debian:
  Fix Released
Status in “gtk+3.0” package in Debian:
  Fix Released
Status in “xkeyboard-config” package in Debian:
  Fix Released

Bug description:
  [Impact]
  F10 behaves the same as Shift-F10.  This causes menus to pop up incorrectly.

  [Fix]
  Upstream patch preserves Shift so that Shift-F10 and F10 act as separate keys.

  [Test Case]
  1.  Open a gnome-terminal window
  2.  Run aptitude
  3.  Press F10

  Expected behavior:  Aptitude's menu opens
  Broken behavior:  Menus for both aptitude and gnome-terminal are shown.

  In different window environments (e.g. unity) other menus can be
  triggered than should be.

  [Regression Potential]
  The patch simply changes a keyboard layout config file, so the severity of 
any possible regression would be limited to keyboard configuration 
misbehaviors.  This is a well reviewed, tested patch from upstream and not 
expected to have any regression.

  [Original Report]
  Upstream bug report: https://bugzilla.gnome.org/show_bug.cgi?id=661973

  Visible in Unity - change keybinding for opening first global menu
  entry to Alt+F10.

  Pressing F10 triggers short flash of global menu nevertheless. When
  you disable the F10 shortcut in gnome-terminal, pressing the key
  triggers context menu in gnome terminal.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: libgtk-3-0 3.3.14-0ubuntu4
  ProcVersionSignature: Ubuntu 3.2.0-17.26-generic-pae 3.2.6
  Uname: Linux 3.2.0-17-generic-pae i686
  ApportVersion: 1.92-0ubuntu1
  Architecture: i386
  Date: Tue Feb 21 16:29:08 2012
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha i386 (20120119)
  SourcePackage: gtk+3.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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

2014-02-22 Thread Oleg-3
Still present in 3.13.2-gentoo. I found that -EBUSY returns from
nv50_fbcon_imageblit.

 what is wrong in nouveau's way of setting up pgraph.
Does it mean that the bug somewhere in nv50_grctx_generate? Just to be sure 
that bug in this function, is it possible to replace it using data from 
mmiotrace of nvidia driver? For me it is not obvious how to modificate 
nv50_grctx_fill in that case, what nv50_grctx_init should write to *size and, 
after all, may it help somehow?

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

Title:
  System hangs after some time with nouveau and GT240

Status in Accelerated Xorg driver for nVidia cards:
  Confirmed
Status in “xserver-xorg-video-nouveau” package in Ubuntu:
  Confirmed
Status in “xserver-xorg-video-nouveau” package in Fedora:
  Unknown

Bug description:
  With the Nouveau driver I get random system hangs in the Live CD - any
  version since it was switched to nouveau up until today's daily
  images. It happens after half an hour to a couple of hours usage and
  affects installed systems as well, until they are switched to the
  proprietary driver.

  This is a well known bug in other trackers but I can't see it anywhere
  on Launchpad, so I'm reporting it and will add bug watches.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xserver-xorg-video-nouveau 1:1.0.8-0ubuntu3
  ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
  Uname: Linux 3.11.0-4-generic x86_64
  ApportVersion: 2.12.1-0ubuntu2
  Architecture: amd64
  CasperVersion: 1.336
  Date: Tue Aug 27 22:16:06 2013
  LiveMediaBuild: Xubuntu 13.10 Saucy Salamander - Alpha amd64 (20130827)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: xserver-xorg-video-nouveau
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/nouveau/+bug/1217585/+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 1232726] Re: Dash bg color doesn't match its surroundings

2014-02-09 Thread Oleg
** Information type changed from Public to Public Security

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

Title:
  Dash bg color doesn't match its surroundings

Status in Unity:
  Fix Committed
Status in Unity 7.1 series:
  Fix Committed
Status in “mesa” package in Ubuntu:
  Invalid
Status in “unity” package in Ubuntu:
  Fix Released
Status in “unity” source package in Saucy:
  In Progress

Bug description:
  Lately, after login the Dash keeps a black background even if the
  Launcher and panel follow the current wallpaper color. I've added a
  screenshot. If I change the wallpaper, Dash recovers its chameleonic
  effect (until next reboot).

  Also, this started happening at the same time that a new error message
  (at log time) appeared, I've attached this error message, too.

  Description:  Ubuntu Saucy Salamander (development branch)
  Release:  13.10

  unity:
    Installed: 7.1.1+13.10.20130927.1-0ubuntu1
    Candidate: 7.1.1+13.10.20130927.1-0ubuntu1
    Version table:
   *** 7.1.1+13.10.20130927.1-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ saucy/main i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity 7.1.1+13.10.20130927.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2
  Uname: Linux 3.11.0-9-generic i686
  .tmp.unity.support.test.0:

  ApportVersion: 2.12.5-0ubuntu1
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Sep 29 08:00:07 2013
  DistUpgraded: Fresh install
  DistroCodename: saucy
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics 
Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:30a2]
     Subsystem: Hewlett-Packard Company Device [103c:30a2]
  InstallationDate: Installed on 2013-08-31 (28 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130830)
  MachineType: Hewlett-Packard HP Compaq nx7400 (GF451LA#ABM)
  MarkForUpload: True
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     no card
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-9-generic 
root=UUID=cab2c6d5-2bf8-4db8-ba85-daaf28b1afec ro quiet splash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2006
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68YGU Ver. F.0A
  dmi.board.name: 30A2
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 40.17
  dmi.chassis.asset.tag: CNU7111JLR
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68YGUVer.F.0A:bd12/18/2006:svnHewlett-Packard:pnHPCompaqnx7400(GF451LA#ABM):pvrF.0A:rvnHewlett-Packard:rn30A2:rvrKBCVersion40.17:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP Compaq nx7400 (GF451LA#ABM)
  dmi.product.version: F.0A
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.10+13.10.20130927.1-0ubuntu1
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu9
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.9-2ubuntu1
  xserver.bootTime: Sun Sep 29 07:53:46 2013
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs: OutputTV-0   
VGA-0
  xserver.version: 2:1.14.2.901-2ubuntu6
  xserver.video_driver: intel

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1232726/+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 1232726] Re: Dash bg color doesn't match its surroundings

2014-02-09 Thread Oleg
** Information type changed from Public Security to Private Security

** Information type changed from Private Security to Public

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

Title:
  Dash bg color doesn't match its surroundings

Status in Unity:
  Fix Committed
Status in Unity 7.1 series:
  Fix Committed
Status in “mesa” package in Ubuntu:
  Invalid
Status in “unity” package in Ubuntu:
  Fix Released
Status in “unity” source package in Saucy:
  In Progress

Bug description:
  Lately, after login the Dash keeps a black background even if the
  Launcher and panel follow the current wallpaper color. I've added a
  screenshot. If I change the wallpaper, Dash recovers its chameleonic
  effect (until next reboot).

  Also, this started happening at the same time that a new error message
  (at log time) appeared, I've attached this error message, too.

  Description:  Ubuntu Saucy Salamander (development branch)
  Release:  13.10

  unity:
    Installed: 7.1.1+13.10.20130927.1-0ubuntu1
    Candidate: 7.1.1+13.10.20130927.1-0ubuntu1
    Version table:
   *** 7.1.1+13.10.20130927.1-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ saucy/main i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: unity 7.1.1+13.10.20130927.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2
  Uname: Linux 3.11.0-9-generic i686
  .tmp.unity.support.test.0:

  ApportVersion: 2.12.5-0ubuntu1
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Sep 29 08:00:07 2013
  DistUpgraded: Fresh install
  DistroCodename: saucy
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics 
Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company Device [103c:30a2]
     Subsystem: Hewlett-Packard Company Device [103c:30a2]
  InstallationDate: Installed on 2013-08-31 (28 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha i386 (20130830)
  MachineType: Hewlett-Packard HP Compaq nx7400 (GF451LA#ABM)
  MarkForUpload: True
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     no card
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-9-generic 
root=UUID=cab2c6d5-2bf8-4db8-ba85-daaf28b1afec ro quiet splash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2006
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68YGU Ver. F.0A
  dmi.board.name: 30A2
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 40.17
  dmi.chassis.asset.tag: CNU7111JLR
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68YGUVer.F.0A:bd12/18/2006:svnHewlett-Packard:pnHPCompaqnx7400(GF451LA#ABM):pvrF.0A:rvnHewlett-Packard:rn30A2:rvrKBCVersion40.17:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP Compaq nx7400 (GF451LA#ABM)
  dmi.product.version: F.0A
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.10+13.10.20130927.1-0ubuntu1
  version.libdrm2: libdrm2 2.4.46-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu9
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.9-2ubuntu1
  xserver.bootTime: Sun Sep 29 07:53:46 2013
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs: OutputTV-0   
VGA-0
  xserver.version: 2:1.14.2.901-2ubuntu6
  xserver.video_driver: intel

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1232726/+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 1276448] [NEW] Please update pidgin to 2.10.9

2014-02-05 Thread Oleg Nightwing Lomakin
*** This bug is a security vulnerability ***

Public security bug reported:

New version contains important security updates:
CVE-2013-6484
CVE-2013-6479
CVE-2013-6485
CVE-2013-6478
CVE-2013-6486
CVE-2013-6487
CVE-2014-0020
CVE-2013-6482
CVE-2013-6489
CVE-2013-6490
CVE-2013-6483
CVE-2013-6477
CVE-2012-6152
CVE-2013-6481
It also add Unity integration plugin. 

lsb_release -rd
Description:Ubuntu 13.10
Release:13.10

apt-cache policy pidgin
pidgin:
  Installed: 1:2.10.7-0ubuntu4.1
  Candidate: 1:2.10.7-0ubuntu4.1
  Version table:
 *** 1:2.10.7-0ubuntu4.1 0
500 http://ru.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages
100 /var/lib/dpkg/status

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


** Tags: upgrade-software-version

** Information type changed from Private Security to Public Security

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

Title:
  Please update pidgin to 2.10.9

Status in “pidgin” package in Ubuntu:
  New

Bug description:
  New version contains important security updates:
  CVE-2013-6484
  CVE-2013-6479
  CVE-2013-6485
  CVE-2013-6478
  CVE-2013-6486
  CVE-2013-6487
  CVE-2014-0020
  CVE-2013-6482
  CVE-2013-6489
  CVE-2013-6490
  CVE-2013-6483
  CVE-2013-6477
  CVE-2012-6152
  CVE-2013-6481
  It also add Unity integration plugin. 

  lsb_release -rd
  Description:  Ubuntu 13.10
  Release:  13.10

  apt-cache policy pidgin
  pidgin:
Installed: 1:2.10.7-0ubuntu4.1
Candidate: 1:2.10.7-0ubuntu4.1
Version table:
   *** 1:2.10.7-0ubuntu4.1 0
  500 http://ru.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/1276448/+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 1276448] Re: Please update pidgin to 2.10.9

2014-02-05 Thread Oleg Nightwing Lomakin
** Description changed:

  New version contains important security updates:
  CVE-2013-6484
  CVE-2013-6479
  CVE-2013-6485
  CVE-2013-6478
  CVE-2013-6486
  CVE-2013-6487
  CVE-2014-0020
  CVE-2013-6482
  CVE-2013-6489
  CVE-2013-6490
  CVE-2013-6483
  CVE-2013-6477
  CVE-2012-6152
  CVE-2013-6481
- It also add Unity integration plugin. 
+ It also add Unity integration plugin.
+ 
+ https://developer.pidgin.im/wiki/ChangeLog
  
  lsb_release -rd
  Description:  Ubuntu 13.10
  Release:  13.10
  
  apt-cache policy pidgin
  pidgin:
-   Installed: 1:2.10.7-0ubuntu4.1
-   Candidate: 1:2.10.7-0ubuntu4.1
-   Version table:
-  *** 1:2.10.7-0ubuntu4.1 0
- 500 http://ru.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages
- 100 /var/lib/dpkg/status
+   Installed: 1:2.10.7-0ubuntu4.1
+   Candidate: 1:2.10.7-0ubuntu4.1
+   Version table:
+  *** 1:2.10.7-0ubuntu4.1 0
+ 500 http://ru.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages
+ 100 /var/lib/dpkg/status

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

Title:
  Please update pidgin to 2.10.9

Status in “pidgin” package in Ubuntu:
  New

Bug description:
  New version contains important security updates:
  CVE-2013-6484
  CVE-2013-6479
  CVE-2013-6485
  CVE-2013-6478
  CVE-2013-6486
  CVE-2013-6487
  CVE-2014-0020
  CVE-2013-6482
  CVE-2013-6489
  CVE-2013-6490
  CVE-2013-6483
  CVE-2013-6477
  CVE-2012-6152
  CVE-2013-6481
  It also add Unity integration plugin.

  https://developer.pidgin.im/wiki/ChangeLog

  lsb_release -rd
  Description:  Ubuntu 13.10
  Release:  13.10

  apt-cache policy pidgin
  pidgin:
    Installed: 1:2.10.7-0ubuntu4.1
    Candidate: 1:2.10.7-0ubuntu4.1
    Version table:
   *** 1:2.10.7-0ubuntu4.1 0
  500 http://ru.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/1276448/+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 1268298] Re: Xubuntu 13.10 can not start X with Rage 128 graphic cards

2014-01-19 Thread Oleg Blashchuk
So I tested Rage 128 cards on Xubuntu 12.10 and 13.04 - in both cases
they work just fine. There are some minor picture defects but all GUI
elements are well drawn.

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

Title:
  Xubuntu 13.10 can not start X with Rage 128 graphic cards

Status in “xserver-xorg-video-r128” package in Ubuntu:
  Incomplete

Bug description:
  Xubuntu 13.10 i386 , default installation.

  Black screen after boot. lightdm service immediately stops after being 
started.
  In /var/log/lightdm/lightdm.log:
  ..
  [+0.26s] DEBUG: Launching process 964: /usr/bin/X -core :0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  [+0.26s] DEBUG: DisplayServer x-0: Waiting for ready signal from X server :0
  [+0.27s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
  [+0.27s] DEBUG: Registering seat with bus path 
/org/freedesktop/DisplayManager/Seat0
  [+2.40s] DEBUG: Process 964 exited with return value 127
  [+2.40s] DEBUG: DisplayServer x-0: X server stopped
  ..

  In /var/log/lightdm/x-0.log
  ..
  Loading extension GLX
  /usr/bin/X: symbol lookup error: /usr/lib/xorg/modules/drivers/r128_drv.so: 
undefined symbol: miInitializeBackingStore

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-r128/+bug/1268298/+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 1268298] Re: Xubuntu 13.10 can not start X with Rage 128 graphic cards

2014-01-15 Thread Oleg Blashchuk
** Attachment added: Good screen
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-r128/+bug/1268298/+attachment/3949785/+files/Screenshot-radeon.png

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

Title:
  Xubuntu 13.10 can not start X with Rage 128 graphic cards

Status in “xserver-xorg-video-r128” package in Ubuntu:
  Incomplete

Bug description:
  Xubuntu 13.10 i386 , default installation.

  Black screen after boot. lightdm service immediately stops after being 
started.
  In /var/log/lightdm/lightdm.log:
  ..
  [+0.26s] DEBUG: Launching process 964: /usr/bin/X -core :0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  [+0.26s] DEBUG: DisplayServer x-0: Waiting for ready signal from X server :0
  [+0.27s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
  [+0.27s] DEBUG: Registering seat with bus path 
/org/freedesktop/DisplayManager/Seat0
  [+2.40s] DEBUG: Process 964 exited with return value 127
  [+2.40s] DEBUG: DisplayServer x-0: X server stopped
  ..

  In /var/log/lightdm/x-0.log
  ..
  Loading extension GLX
  /usr/bin/X: symbol lookup error: /usr/lib/xorg/modules/drivers/r128_drv.so: 
undefined symbol: miInitializeBackingStore

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-r128/+bug/1268298/+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 1268298] Re: Xubuntu 13.10 can not start X with Rage 128 graphic cards

2014-01-15 Thread Oleg Blashchuk
On the one hand initial problem is gone - X starts ok now.
On the other hand final picture is buggy - video-buffer seems to be corrupted 
and system is not really usable. I attach two screenshots of fresh Xubuntu 
13.10 i386 desktop - one on Radeon (good picture), other on Rage 128 (corrupted 
one). I tested different video-cards (Rage 128 and Rage 128 Pro, 16 and 32 MB, 
all AGP) and three different motherboards (AMD on VIA and nVidia chipset and P4 
on Intel chipset) - the same issue with all configurations. Effects (desktop 
composition) can be turned on or off - does not really matter. Even lightdm 
screen have corruptions.

As for now I have plenty of such PCs working smoothly under Xubuntu
12.04 - have not tested 13.04 yet.

** Attachment added: Bad screen
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-r128/+bug/1268298/+attachment/3949783/+files/Screenshot-r128.png

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

Title:
  Xubuntu 13.10 can not start X with Rage 128 graphic cards

Status in “xserver-xorg-video-r128” package in Ubuntu:
  Incomplete

Bug description:
  Xubuntu 13.10 i386 , default installation.

  Black screen after boot. lightdm service immediately stops after being 
started.
  In /var/log/lightdm/lightdm.log:
  ..
  [+0.26s] DEBUG: Launching process 964: /usr/bin/X -core :0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  [+0.26s] DEBUG: DisplayServer x-0: Waiting for ready signal from X server :0
  [+0.27s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
  [+0.27s] DEBUG: Registering seat with bus path 
/org/freedesktop/DisplayManager/Seat0
  [+2.40s] DEBUG: Process 964 exited with return value 127
  [+2.40s] DEBUG: DisplayServer x-0: X server stopped
  ..

  In /var/log/lightdm/x-0.log
  ..
  Loading extension GLX
  /usr/bin/X: symbol lookup error: /usr/lib/xorg/modules/drivers/r128_drv.so: 
undefined symbol: miInitializeBackingStore

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-r128/+bug/1268298/+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 1268298] [NEW] Xubuntu 13.10 can not start X with Rage 128 graphic cards

2014-01-12 Thread Oleg Blashchuk
Public bug reported:

Xubuntu 13.10 i386 , default installation.

Black screen after boot. lightdm service immediately stops after being started.
In /var/log/lightdm/lightdm.log:
..
[+0.26s] DEBUG: Launching process 964: /usr/bin/X -core :0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.26s] DEBUG: DisplayServer x-0: Waiting for ready signal from X server :0
[+0.27s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.27s] DEBUG: Registering seat with bus path 
/org/freedesktop/DisplayManager/Seat0
[+2.40s] DEBUG: Process 964 exited with return value 127
[+2.40s] DEBUG: DisplayServer x-0: X server stopped
..

In /var/log/lightdm/x-0.log
..
Loading extension GLX
/usr/bin/X: symbol lookup error: /usr/lib/xorg/modules/drivers/r128_drv.so: 
undefined symbol: miInitializeBackingStore

** Affects: xserver-xorg-video-r128 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Xubuntu 13.10 can not start X with Rage 128 graphic cards

Status in “xserver-xorg-video-r128” package in Ubuntu:
  New

Bug description:
  Xubuntu 13.10 i386 , default installation.

  Black screen after boot. lightdm service immediately stops after being 
started.
  In /var/log/lightdm/lightdm.log:
  ..
  [+0.26s] DEBUG: Launching process 964: /usr/bin/X -core :0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  [+0.26s] DEBUG: DisplayServer x-0: Waiting for ready signal from X server :0
  [+0.27s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
  [+0.27s] DEBUG: Registering seat with bus path 
/org/freedesktop/DisplayManager/Seat0
  [+2.40s] DEBUG: Process 964 exited with return value 127
  [+2.40s] DEBUG: DisplayServer x-0: X server stopped
  ..

  In /var/log/lightdm/x-0.log
  ..
  Loading extension GLX
  /usr/bin/X: symbol lookup error: /usr/lib/xorg/modules/drivers/r128_drv.so: 
undefined symbol: miInitializeBackingStore

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-r128/+bug/1268298/+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 1219677] Re: if empathy start hidden it will fail to work with indicator-messages

2013-10-24 Thread Oleg
Same problem. Ubuntu 13.10 x64, empathy 3.8.4-1ubuntu1

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

Title:
  if empathy start hidden it will fail to work with indicator-messages

Status in “empathy” package in Ubuntu:
  Confirmed

Bug description:
  if empathy start hidden it will fail to work with indicator-messages. Simple 
test: run empathy -h in command line
  then try to open it from indicator-messages.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: empathy 3.6.4-0ubuntu4.1
  Uname: Linux 3.11.0-999-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  Date: Mon Sep  2 09:32:45 2013
  InstallationDate: Installed on 2013-08-31 (1 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: empathy
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1219677/+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 1072199] Re: Alt+Print Screen shortcut does not work in Ubuntu

2013-10-23 Thread Oleg Cherkasov
It seems the old bug returns.  I may see the same issue in 13.10
release.  The bug has to be reopened for 13.10 or spawn a new one.

The workaround would be Ctrl-PrtSc/Shift-PrtSc or use Shutter.

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

Title:
  Alt+Print Screen shortcut does not work in Ubuntu

Status in Unity:
  Fix Released
Status in “gnome-screenshot” package in Ubuntu:
  Fix Released

Bug description:
  According to Ubuntu Desktop Guide (see attached screenshot of the
  Ubuntu Desktop Guide) pressing Alt+Print Screen should take a
  screenshot of a window.

  However when I press Alt+Print Screen it always takes the screenshot
  of the launcher and not of the active window.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1072199/+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 1103394] Re: [raring] History dialog does not decode UTF-8 (displays за symbols)

2013-10-15 Thread Oleg Nightwing Lomakin
Bug still here. Please backport fix!

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

Title:
  [raring] History dialog does not decode UTF-8 (displays за symbols)

Status in Chat app, and Telepathy user interface:
  Fix Released
Status in “empathy” package in Ubuntu:
  Triaged
Status in “empathy” package in Fedora:
  Unknown

Bug description:
  STR:

  1. Send e.g. Привет (Hello in Russian)
  2. Open Previous conversations

  Expected results:
  Last entry will be Привет

  Actual results:
  The last entry is Привет - UTF-8 bytes as if the encoding was latin1

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: empathy 3.6.3-0ubuntu2
  ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4
  Uname: Linux 3.8.0-1-generic x86_64
  ApportVersion: 2.8-0ubuntu2
  Architecture: amd64
  Date: Wed Jan 23 11:54:54 2013
  InstallationDate: Installed on 2013-01-04 (18 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130104)
  MarkForUpload: True
  SourcePackage: empathy
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/empathy/+bug/1103394/+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 1173073] Re: Broken sounds in Skype

2013-07-10 Thread Oleg German
1:3.0-0ubuntu6.1~diwicppa
skype is now completely silent

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

Title:
  Broken sounds in Skype

Status in “pulseaudio” package in Ubuntu:
  Incomplete
Status in “skype” package in Ubuntu:
  Confirmed

Bug description:
  When skype notify something and play sound (for i.e., contact became
  online or send me message, or calling), it sounds with wheezing. In
  another programs all OK. If I playing this wav files all is OK too.

  robotex@robotex-laptop:~$ lsb_release -rd
  Description:  Ubuntu 13.04
  Release:  13.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1173073/+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 1173180] Re: Dragdrop doesn't work

2013-05-07 Thread Oleg
Program tested on Ubuntu 12.10 and then by update-manager ubuntu was
updated to 13.04 and here dragdrop doesn't work.

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

Title:
  Dragdrop  doesn't work

Status in “pygtk” package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 13.04, Pygtk 2.24.0-3ubuntu1. DragDrop doesn't work.
  parts of code:

  self.window.connect(drag_data_received, self.getDrop)
  self.window.connect(drag_drop, self.drop_cb)
  self.window.drag_dest_set(0, [], 0)
  self.window.connect(drag_motion, self.motion_cb)

  def getDrop(self, winID, context, x, y, data, info, time):
self.filechooser.set_uri((data.data).strip())
context.finish(True, False, time)

  def drop_cb(self,wid, context, x, y, time):
wid.drag_get_data(context, context.targets[0], time)
context.finish(True, False, time)
return True

  def motion_cb(self,wid, context, x, y, time):
context.drag_status(gtk.gdk.ACTION_COPY, time)
return True

  On previous version this code worked ok!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pygtk/+bug/1173180/+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 1172178] Re: WWAN Connection: DNS Error / PPPd not starting?

2013-05-07 Thread Oleg Cherkasov
Following some tips I have set /etc/modprobe.d/cdc_ncm.conf:

options cdc_ncm prefer_mbim=N

and it seems solve the problem.

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

Title:
  WWAN Connection: DNS Error / PPPd not starting?

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

Bug description:
  I have a problem connecting on my x1 carbon - actually I didn' suceed
  to connect on win8 either even though I updated all drivers firmaware
  etc.

  On windows I don't know how to see whats going on and I use ubuntu for
  my everday work anway.

  I will attach / post a snipplet from syslog that showas whats
  happening. On another machine I am using the same SIM and also 13.04
  but it works fine.

  There pppd ist started before dhclient. I don't see any ppp launch
  here and this seems stange to me.

  Anyway I have no Idea where to look or what to try to make it work.
  Could somebody help me?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1172178/+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 629667] Re: Doesn't boot without nomodeset option on GT240

2013-04-27 Thread Oleg Nightwing Lomakin
** Changed in: xserver-xorg-video-nouveau (Ubuntu)
   Status: Confirmed = Fix Released

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

Title:
  Doesn't boot without nomodeset option on GT240

Status in “xserver-xorg-video-nouveau” package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: xserver-xorg-video-nouveau

  Similiar problem on lucid: https://bugs.launchpad.net/ubuntu/+source
  /xserver-xorg-video-nouveau/+bug/574045 but lucid can boot(with screen
  in standby, hehe). 10.10 beta do nothing, It does not do anything,
  just shows me a black screen with a blinking cursor.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/629667/+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 574045] Re: Ubuntu hang on startup (may be kms or nouveau problem)

2013-04-27 Thread Oleg Nightwing Lomakin
Fixed in 13.04. System can boot, but xorg won't work.

** Changed in: xserver-xorg-video-nouveau (Ubuntu)
   Status: Confirmed = Fix Released

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

Title:
  Ubuntu hang on startup (may be kms or nouveau problem)

Status in “xserver-xorg-video-nouveau” package in Ubuntu:
  Fix Released

Bug description:
  When i start Ubuntu 10.04 x86_64 desktop livecd (same on installed
  system), system just hang. It seems that it load something, and i see
  black screen at this moment(2-3 seconds). Then, my monitor goes into
  standby and loading stops. ctrl+alt+del or power button does nothing.
  Booting the system with nomodeset work around the issue.

  01:00.0 VGA compatible controller: nVidia Corporation GT215 [GeForce
  GT 240] (rev a2)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/574045/+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 1172823] [NEW] pointstick and mouse buttons isn't working (on thinkpad) after upgrade to 13.04

2013-04-25 Thread Oleg
Public bug reported:

pointstick and mouse buttons isn't working (on thinkpad) after upgrade to 
13.04
--- 
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  jumper 2039 F pulseaudio
CRDA:
 country GB:
(2402 - 2482 @ 40), (N/A, 20)
(5170 - 5250 @ 40), (N/A, 20)
(5250 - 5330 @ 40), (N/A, 20), DFS
(5490 - 5710 @ 40), (N/A, 27), DFS
DistroRelease: Ubuntu 13.04
HibernationDevice: RESUME=UUID=ba603f6d-230a-4479-a307-bc030929dabb
InstallationDate: Installed on 2013-01-18 (97 days ago)
InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
MachineType: LENOVO 2324HF4
MarkForUpload: True
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic 
root=UUID=e189f839-8390-44b5-abff-dd8b750a7a20 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-19-generic N/A
 linux-backports-modules-3.8.0-19-generic  N/A
 linux-firmware1.106
Tags:  raring
Uname: Linux 3.8.0-19-generic x86_64
UpgradeStatus: Upgraded to raring on 2013-04-25 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 09/11/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: G2ET82WW (2.02 )
dmi.board.asset.tag: Not Available
dmi.board.name: 2324HF4
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET82WW(2.02):bd09/11/2012:svnLENOVO:pn2324HF4:pvrThinkPadX230:rvnLENOVO:rn2324HF4:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 2324HF4
dmi.product.version: ThinkPad X230
dmi.sys.vendor: LENOVO

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: apport-collected raring

** Package changed: gnome-control-center (Ubuntu) = linux (Ubuntu)

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

Title:
  pointstick and mouse buttons isn't working (on thinkpad) after
  upgrade to 13.04

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  pointstick and mouse buttons isn't working (on thinkpad) after upgrade to 
13.04
  --- 
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jumper 2039 F pulseaudio
  CRDA:
   country GB:
(2402 - 2482 @ 40), (N/A, 20)
(5170 - 5250 @ 40), (N/A, 20)
(5250 - 5330 @ 40), (N/A, 20), DFS
(5490 - 5710 @ 40), (N/A, 27), DFS
  DistroRelease: Ubuntu 13.04
  HibernationDevice: RESUME=UUID=ba603f6d-230a-4479-a307-bc030929dabb
  InstallationDate: Installed on 2013-01-18 (97 days ago)
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  MachineType: LENOVO 2324HF4
  MarkForUpload: True
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic 
root=UUID=e189f839-8390-44b5-abff-dd8b750a7a20 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-19-generic N/A
   linux-backports-modules-3.8.0-19-generic  N/A
   linux-firmware1.106
  Tags:  raring
  Uname: Linux 3.8.0-19-generic x86_64
  UpgradeStatus: Upgraded to raring on 2013-04-25 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 09/11/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET82WW (2.02 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2324HF4
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET82WW(2.02):bd09/11/2012:svnLENOVO:pn2324HF4:pvrThinkPadX230:rvnLENOVO:rn2324HF4:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2324HF4
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1172823/+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 1131072] Re: Test page is printed on available printer if the printer under test is unavailable

2013-02-28 Thread Oleg Moiseichuk
** Summary changed:

- Test page is always printed on default printer
+ Test page is printed on available printer if the printer under test is 
unavailable

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

Title:
  Test page is printed on available printer if the printer under test is
  unavailable

Status in “system-config-printer” package in Ubuntu:
  New

Bug description:
  I'm using Ubuntu 12.04.1 with GNOME Classic.
  I've got one printer in my system, HP LaserJet 3052, which is connected as 
network printer. Obviously, it is set as default. Its URI is 
'hp:/net/HP_LaserJet_3052?zc=NPIE50CCB' and its driver is 'HP LaserJet 3052 
Postscript (recommended)'.
  Later I added second printer using GNOME Printers applet. Second printer 
model is HP LaserJet 1220, it is connected via SAMBA with URI 
'smb://XX.XX.XX.XX/HPLaserJ' and I used recommended driver for this printer.
  When the setup was finished I sent test page to this printer and nothing 
happened. I switched from recommended driver to CUPS+Gutenprint v5.2.8 driver 
and sent another test page, but nothing happened again.
  My default HP LaserJet 3052 pinter was turned off at this moment, but when I 
switched it on, both test pages were printed on this printer instead. They got 
Job ID, Driver Version and Description of HP LaserJet 1220, but both tests were 
sent from the spool to the default HP LaserJet 3052 printer, not to the printer 
they were intended for.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1131072/+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 1131072] Re: Test page is printed on available printer if the printer under test is unavailable

2013-02-28 Thread Oleg Moiseichuk
Actually if printer not available then test page is printed on available
printer. It seems to me that more consistent behavior is to send an
error rather then redirect printing job to available printer.

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

Title:
  Test page is printed on available printer if the printer under test is
  unavailable

Status in “system-config-printer” package in Ubuntu:
  New

Bug description:
  I'm using Ubuntu 12.04.1 with GNOME Classic.
  I've got one printer in my system, HP LaserJet 3052, which is connected as 
network printer. Obviously, it is set as default. Its URI is 
'hp:/net/HP_LaserJet_3052?zc=NPIE50CCB' and its driver is 'HP LaserJet 3052 
Postscript (recommended)'.
  Later I added second printer using GNOME Printers applet. Second printer 
model is HP LaserJet 1220, it is connected via SAMBA with URI 
'smb://XX.XX.XX.XX/HPLaserJ' and I used recommended driver for this printer.
  When the setup was finished I sent test page to this printer and nothing 
happened. I switched from recommended driver to CUPS+Gutenprint v5.2.8 driver 
and sent another test page, but nothing happened again.
  My default HP LaserJet 3052 pinter was turned off at this moment, but when I 
switched it on, both test pages were printed on this printer instead. They got 
Job ID, Driver Version and Description of HP LaserJet 1220, but both tests were 
sent from the spool to the default HP LaserJet 3052 printer, not to the printer 
they were intended for.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1131072/+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 1136216] Re: gnome control center crash when try to open sound settings menu

2013-02-28 Thread Galushko Oleg
** Also affects: gnome-control-center
   Importance: Undecided
   Status: New

** No longer affects: gnome-control-center

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

Title:
  gnome control center crash when try to open sound settings menu

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

Bug description:
  after  the last upgrde I tryed to open the sound settings menu from the sound 
indicator but the gnome control center was opened instead of the sound settings 
menu.
  I have tryed to close it but dont close.
  If I try to kill the control center another istance will be open.
  I have restart the computer and i have opened the control center from the 
terminal, and then I have select sound but dont work also. this is what the 
terminal say:
  /usr/lib/control-center-1/panels/libsoundnua.so: undefined symbol: 
gvc_mixer_ui_device_is_output
  Failed to load module: /usr/lib/control-center-1/panels/libsoundnua.so
  /usr/lib/control-center-1/panels/libsoundnua.so: undefined symbol: 
gvc_mixer_ui_device_is_output
  Failed to load module: /usr/lib/control-center-1/panels/libsoundnua.so
  /usr/lib/control-center-1/panels/libsoundnua.so: undefined symbol: 
gvc_mixer_ui_device_is_output
  Failed to load module: /usr/lib/control-center-1/panels/libsoundnua.so
  /usr/lib/control-center-1/panels/libsoundnua.so: undefined symbol: 
gvc_mixer_ui_device_is_output
  Failed to load module: /usr/lib/control-center-1/panels/libsoundnua.so
  /usr/lib/control-center-1/panels/libsoundnua.so: undefined symbol: 
gvc_mixer_ui_device_is_output
  Failed to load module: /usr/lib/control-center-1/panels/libsoundnua.so
  /usr/lib/control-center-1/panels/libsoundnua.so: undefined symbol: 
gvc_mixer_ui_device_is_output
  Failed to load module: /usr/lib/control-center-1/panels/libsoundnua.so
  /usr/lib/control-center-1/panels/libsoundnua.so: undefined symbol: 
gvc_mixer_ui_device_is_output

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-control-center 1:3.4.2-0ubuntu0.10
  ProcVersionSignature: Ubuntu 3.2.0-38.61-generic 3.2.37
  Uname: Linux 3.2.0-38-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: amd64
  Date: Thu Feb 28 19:54:58 2013
  InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 
(20120823.1)
  MarkForUpload: True
  ProcEnviron:
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu3.2
   deja-dup22.0-0ubuntu3
   gnome-bluetooth 3.2.2-0ubuntu5
   indicator-datetime  0.3.94-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1136216/+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 836945] Re: Screen always goes blank after 10 minutes

2013-02-21 Thread Oleg Moiseichuk
Actually there exist 2 settings, 1st one affects screensaver (blank screen), 
2nd affects monitor power saving mode (suspends monitor):
1. Schema: org.gnome.desktop.session, Key: idle-delay
2. Schema: org.gnome.settings-daemon.plugins.power, Key: sleep-display-ac
System Settings  Brightness and Lock seems to set both of them 
simultaneously, when you choose the timeout Turn screen off when inactive 
for:. But you can set them separately with 'dconf' tool or using gsettings.
If your screen blanks unexpectedly, check these 2 keys and correct them as 
needed.

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

Title:
  Screen always goes blank after 10 minutes

Status in “gnome-settings-daemon” package in Ubuntu:
  Confirmed

Bug description:
  Even though my screen saver settings say to Turn off after: 1 hour,
  my screens always go blank after 10 minutes of inactivity.  This is
  entirely reproducible.  I am using the free glx driver with my Radeon
  HD 4670 card, dual-headed.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: xorg 1:7.6+7ubuntu6
  ProcVersionSignature: Ubuntu 3.0.0-9.14-generic 3.0.3
  Uname: Linux 3.0.0-9-generic x86_64
  Architecture: amd64
  BootLog:
   udevd[362]: error: runtime directory '/run/udev' not writable, for now 
falling back to '/dev/.udev'
   fsck from util-linux 2.19.1
   /dev/sdb2: clean, 142348/90841088 files, 6520516/363354368 blocks
  CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,mousepoll,vpswitch,regex,animation,snap,expo,move,compiztoolbox,place,grid,imgpng,gnomecompat,wall,ezoom,workarounds,staticswitcher,resize,fade,unitymtgrabhandles,scale,session,unitydialog,unityshell]
  CompositorRunning: None
  Date: Mon Aug 29 14:52:39 2011
  DistUpgraded: Fresh install
  DistroCodename: oneiric
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu
  GraphicsCard:
   ATI Technologies Inc RV730XT [Radeon HD 4670] [1002:9490] (prog-if 00 [VGA 
controller])
 Subsystem: Dell Device [1028:2542]
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Alpha amd64 (20110705.1)
  MachineType: Dell Inc. Studio XPS 435MT
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-9-generic 
root=UUID=7ffae0c6-66ea-4bbd-ae3d-f98ddd9603a5 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/05/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.1
  dmi.board.name: 0R849J
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.1:bd05/05/2009:svnDellInc.:pnStudioXPS435MT:pvr:rvnDellInc.:rn0R849J:rvrA03:cvnDellInc.:ct3:cvr:
  dmi.product.name: Studio XPS 435MT
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.5.92+bzr2791-0ubuntu1
  version.ia32-libs: ia32-libs 20090808ubuntu19
  version.libdrm2: libdrm2 2.4.26-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 7.11-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 7.11-0ubuntu3
  version.xserver-xorg: xserver-xorg 1:7.6+7ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.0-1ubuntu13
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:6.14.99~git20110811.g93fc084-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.15.901-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:0.0.16+git20110411+8378443-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/836945/+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 1131072] [NEW] Test page is always printed on default printer

2013-02-20 Thread Oleg Moiseichuk
Public bug reported:

I'm using Ubuntu 12.04.1 with GNOME Classic.
I've got one printer in my system, HP LaserJet 3052, which is connected as 
network printer. Obviously, it is set as default. Its URI is 
'hp:/net/HP_LaserJet_3052?zc=NPIE50CCB' and its driver is 'HP LaserJet 3052 
Postscript (recommended)'.
Later I added second printer using GNOME Printers applet. Second printer model 
is HP LaserJet 1220, it is connected via SAMBA with URI 
'smb://XX.XX.XX.XX/HPLaserJ' and I used recommended driver for this printer.
When the setup was finished I sent test page to this printer and nothing 
happened. I switched from recommended driver to CUPS+Gutenprint v5.2.8 driver 
and sent another test page, but nothing happened again.
My default HP LaserJet 3052 pinter was turned off at this moment, but when I 
switched it on, both test pages were printed on this printer instead. They got 
Job ID, Driver Version and Description of HP LaserJet 1220, but both tests were 
sent from the spool to the default HP LaserJet 3052 printer, not to the printer 
they were intended for.

** Affects: system-config-printer (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Test page is always printed on default printer

Status in “system-config-printer” package in Ubuntu:
  New

Bug description:
  I'm using Ubuntu 12.04.1 with GNOME Classic.
  I've got one printer in my system, HP LaserJet 3052, which is connected as 
network printer. Obviously, it is set as default. Its URI is 
'hp:/net/HP_LaserJet_3052?zc=NPIE50CCB' and its driver is 'HP LaserJet 3052 
Postscript (recommended)'.
  Later I added second printer using GNOME Printers applet. Second printer 
model is HP LaserJet 1220, it is connected via SAMBA with URI 
'smb://XX.XX.XX.XX/HPLaserJ' and I used recommended driver for this printer.
  When the setup was finished I sent test page to this printer and nothing 
happened. I switched from recommended driver to CUPS+Gutenprint v5.2.8 driver 
and sent another test page, but nothing happened again.
  My default HP LaserJet 3052 pinter was turned off at this moment, but when I 
switched it on, both test pages were printed on this printer instead. They got 
Job ID, Driver Version and Description of HP LaserJet 1220, but both tests were 
sent from the spool to the default HP LaserJet 3052 printer, not to the printer 
they were intended for.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1131072/+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 713860] Re: 1st terminal opens at 80x24, subsequent open at 80x22 [classic desktop]

2013-02-15 Thread Oleg Moiseichuk
** This bug is no longer a duplicate of bug 915241
   Update menubar patches

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

Title:
  1st terminal opens at 80x24, subsequent open at 80x22 [classic
  desktop]

Status in “gnome-terminal” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: gnome-terminal

  This odd behavior started showing up a few days ago.  I'm using the
  Ubuntu classic desktop (with metacity).  I generally have two terminal
  windows open when I'm coding (I have a 2560x1600 display).  When I
  open the first terminal, it opens at the default size of 80 columns x
  24 rows.  But subsequent terminals will open at 80x22.

  If I close all terminal windows, behavior starts over - 1st terminal
  is 80x24, all subsequent are 80x22.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: gnome-terminal 2.32.1-0ubuntu2
  ProcVersionSignature: Ubuntu 2.6.38-1.28-generic 2.6.38-rc2
  Uname: Linux 2.6.38-1-generic x86_64
  Architecture: amd64
  CheckboxSubmission: fdbdfcded0c0bb479a6b52e9ec5af131
  CheckboxSystem: edda5d4f616ca792bf437989cb597002
  Date: Sat Feb  5 16:48:12 2011
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 
(20101007.1)
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, user)
   LANG=en_US.UTF-8
   LC_MESSAGES=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: gnome-terminal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/713860/+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


  1   2   >