[Desktop-packages] [Bug 2038591] [NEW] package thunderbird-locale-en-us 1:102.15.1+build1-0ubuntu0.22.04.1 failed to install/upgrade: подпроцесс dpkg-deb --control возвратил код ошибки 2

2023-10-05 Thread artem
Public bug reported:

Try to update
sudo apt update && sudo apt -y upgrade

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: thunderbird-locale-en-us 1:115.3.1+build1-0ubuntu0.22.04.2
Uname: Linux 6.4.0-060400-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  artem  1561 F pulseaudio
 /dev/snd/controlC0:  artem  1561 F pulseaudio
BuildID: 20230912052514
CasperMD5CheckResult: pass
Channel: Unavailable
Date: Fri Oct  6 06:24:30 2023
ErrorMessage: подпроцесс dpkg-deb --control возвратил код ошибки 2
ForcedLayersAccel: False
InstallationDate: Installed on 2023-08-31 (35 days ago)
InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
IpRoute:
 default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600 
 169.254.0.0/16 dev wlp2s0 scope link metric 1000 
 192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.105 metric 600
NoProfiles: True
PackageArchitecture: all
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.2
 apt  2.4.10
RunningIncompatibleAddons: False
SourcePackage: thunderbird
Title: package thunderbird-locale-en-us 1:102.15.1+build1-0ubuntu0.22.04.1 
failed to install/upgrade: подпроцесс dpkg-deb --control возвратил код ошибки 2
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/10/2023
dmi.bios.release: 5.16
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: M1402IA.310
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: M1402IA
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.:bvrM1402IA.310:bd01/10/2023:br5.16:svnASUSTeKCOMPUTERINC.:pnVivobook_ASUSLaptopM1402IA_M1402IA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnM1402IA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
dmi.product.family: Vivobook
dmi.product.name: Vivobook_ASUSLaptop M1402IA_M1402IA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-package jammy

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

Title:
  package thunderbird-locale-en-us 1:102.15.1+build1-0ubuntu0.22.04.1
  failed to install/upgrade: подпроцесс dpkg-deb --control возвратил код
  ошибки 2

Status in thunderbird package in Ubuntu:
  New

Bug description:
  Try to update
  sudo apt update && sudo apt -y upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: thunderbird-locale-en-us 1:115.3.1+build1-0ubuntu0.22.04.2
  Uname: Linux 6.4.0-060400-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  artem  1561 F pulseaudio
   /dev/snd/controlC0:  artem  1561 F pulseaudio
  BuildID: 20230912052514
  CasperMD5CheckResult: pass
  Channel: Unavailable
  Date: Fri Oct  6 06:24:30 2023
  ErrorMessage: подпроцесс dpkg-deb --control возвратил код ошибки 2
  ForcedLayersAccel: False
  InstallationDate: Installed on 2023-08-31 (35 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  IpRoute:
   default via 192.168.0.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.105 metric 
600
  NoProfiles: True
  PackageArchitecture: all
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.10
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  Title: package thunderbird-locale-en-us 1:102.15.1+build1-0ubuntu0.22.04.1 
failed to install/upgrade: подпроцесс dpkg-deb --control возвратил код ошибки 2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/10/2023
  dmi.bios.release: 5.16
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: M1402IA.310
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: M1402IA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1

[Desktop-packages] [Bug 1926165] Re: Bass speakers not enabled on Lenovo Yoga 9i

2022-02-20 Thread Artem
Yoga Slim 9 14ITL5 Ubuntu 20.04 kernel 5.13.0-30-generic
No sound on front speakers

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

Title:
  Bass speakers not enabled on Lenovo Yoga 9i

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  The Lenovo Yoga 9i has two sets of speakers: regular ones and bass
  speakers. The former work but while latter are detected and show up in
  alsamixer, they play no sound. Plugging headphones in and out or
  toggling any of the volume options does not fix the issue.

  A possibly related issue for a different Yoga version:
  https://bugzilla.kernel.org/show_bug.cgi?id=205755

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 4466 F pulseaudio
ubuntu 6219 F alsamixer
   /dev/snd/pcmC0D0p:   ubuntu 4466 F...m pulseaudio
  CasperMD5CheckResult: pass
  CasperVersion: 1.461
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 26 15:10:05 2021
  LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp 
successful
  Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - 
sof-hda-dsp
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [82BG, Realtek ALC287, Speaker, Internal] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/28/2021
  dmi.bios.release: 1.40
  dmi.bios.vendor: LENOVO
  dmi.bios.version: EHCN40WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Yoga 9 14ITL5
  dmi.ec.firmware.release: 1.40
  dmi.modalias: 
dmi:bvnLENOVO:bvrEHCN40WW:bd01/28/2021:br1.40:efr1.40:svnLENOVO:pn82BG:pvrYoga914ITL5:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrYoga914ITL5:
  dmi.product.family: Yoga 9 14ITL5
  dmi.product.name: 82BG
  dmi.product.sku: LENOVO_MT_82BG_BU_idea_FM_Yoga 9 14ITL5
  dmi.product.version: Yoga 9 14ITL5
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1926165/+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 1943130] Re: Nvidia drivers info

2021-09-09 Thread Artem Mikhalev
Sending this bug after, solved by change drivers, i can change it back
to 470, and perform debug commands if needed (gather logs etc.)

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

Title:
  Nvidia drivers info

Status in xorg package in Ubuntu:
  New

Bug description:
  After turn on mu PC, it doesn't send signal to the second monitor. (with 
driver "nvidia-driver-470(proprietary tested)"
  After change it to: "nvidia-driver-460(proprietary)" problem solved.

  Looks like new kernel update have conflict with nvidia - 470 driver.
  (because yesterday it was fine but today is broken, and made me to
  change the driver)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-34-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..2b.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  460.91.03  Fri Jul  2 
06:04:10 UTC 2021
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  BootLog: Error: [Errno 13] Відмовлено у доступі: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  9 15:15:39 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 460.91.03, 5.11.0-34-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation Device [10de:2208] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:8803]
  InstallationDate: Installed on 2021-08-31 (8 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: Micro-Star International Co., Ltd. MS-7C91
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=uk_UA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic 
root=UUID=1bb75479-3578-4389-a29e-40823860bbbc ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] 
failed with exit code 126: Error executing command as another user: Request 
dismissed
  dmi.bios.date: 05/12/2021
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: A.60
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MAG B550 TOMAHAWK (MS-7C91)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrA.60:bd05/12/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C91:pvr2.0:skuTobefilledbyO.E.M.:rvnMicro-StarInternationalCo.,Ltd.:rnMAGB550TOMAHAWK(MS-7C91):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7C91
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 2.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1943130/+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 1943130] [NEW] Nvidia drivers info

2021-09-09 Thread Artem Mikhalev
Public bug reported:

After turn on mu PC, it doesn't send signal to the second monitor. (with driver 
"nvidia-driver-470(proprietary tested)"
After change it to: "nvidia-driver-460(proprietary)" problem solved.

Looks like new kernel update have conflict with nvidia - 470 driver.
(because yesterday it was fine but today is broken, and made me to
change the driver)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-34-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..2b.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  460.91.03  Fri Jul  2 06:04:10 
UTC 2021
 GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
BootLog: Error: [Errno 13] Відмовлено у доступі: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep  9 15:15:39 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus: nvidia, 460.91.03, 5.11.0-34-generic, x86_64: installed
GraphicsCard:
 NVIDIA Corporation Device [10de:2208] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:8803]
InstallationDate: Installed on 2021-08-31 (8 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
MachineType: Micro-Star International Co., Ltd. MS-7C91
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=uk_UA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-34-generic 
root=UUID=1bb75479-3578-4389-a29e-40823860bbbc ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] 
failed with exit code 126: Error executing command as another user: Request 
dismissed
dmi.bios.date: 05/12/2021
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: A.60
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: MAG B550 TOMAHAWK (MS-7C91)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 2.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 2.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrA.60:bd05/12/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C91:pvr2.0:skuTobefilledbyO.E.M.:rvnMicro-StarInternationalCo.,Ltd.:rnMAGB550TOMAHAWK(MS-7C91):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7C91
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 2.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.105-3~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal 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/1943130

Title:
  Nvidia drivers info

Status in xorg package in Ubuntu:
  New

Bug description:
  After turn on mu PC, it doesn't send signal to the second monitor. (with 
driver "nvidia-driver-470(proprietary tested)"
  After change it to: "nvidia-driver-460(proprietary)" problem solved.

  Looks like new kernel update have conflict with nvidia - 470 driver.
  (because yesterday it was fine but today is broken, and made me to
  change the driver)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-34-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  

[Desktop-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode

2021-04-26 Thread Artem
Same problem:
- Kernel: 5.8.0-50-generic
- OS: Ubuntu 20.04.1
- Machine: HP EliteBook 830 G6
- Headset: BUXTON BHP 7501

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

Title:
  [Bluetooth] No audio output/input in HSP/HFP mode

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I'm testing with Sony bluetooth headset SBH20, works fine in A2DP
  profile, but I can't get audio input and output work in HSP/HFP
  profile.

  [Reproduce steps]
  1. Scan and pair BT headset in Bluetooth setting
  2. Switch to HSP/HFP profile in Sound setting
  3. Test sound output/input

  [Machine information]
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  9 16:26:52 2020
  InstallationDate: Installed on 2020-04-09 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: SBH20
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  Symptom_Type: No sound at all
  Title: [SBH20, recording] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/17/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.13
  dmi.board.name: 0188D1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390 2-in-1
  dmi.product.sku: 08B0
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+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 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa

2021-04-26 Thread Artem
*** This bug is a duplicate of bug 1871794 ***
https://bugs.launchpad.net/bugs/1871794

Same problem:
- Kernel: 5.8.0-50-generic
- OS: Ubuntu 20.04.1
- Machine: HP EliteBook 830 G6
- Headset: BUXTON BHP 7501

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

Title:
  [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting
  HSP/HFP audio profile in Focal Fossa

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After updating the release from Ubuntu 19.10 to 20.04, the bluetooth
  headset doesn't work anymore when HSP/HFP profile is selected.

  With Ubuntu 19.10 the headset was working, there was audio and the mic
  was perfect for video conferencing.

  [Steps to reproduce]
  1. Connect headset (used blueman to setup and connect)
  1.1. When connected the system automatically selects A2DP profile
  2. Start playing audio (browser or other)
  3. Change profile to HSP/HFP with pavucontrol (or blueman)
  4. The audio disappears and microphone is not working (no input)
  5. Optionally switch back to A2DP and the audio comes back

  [Expected]
  When switching to HSP/HFP the audio should keep playing and the microphone 
should start working

  [Notes]
  I tried with pavucontrol to switch between profiles while playing audio from 
a browser.
  As side note there's a led in the headset that still blinks when switching 
profile.

  I tried deleting the pulse folder under user's profile .config without
  success, also reinstalled packages and did a `sudo alsa force-reload`
  and rebooting several times.

  Note: not sure this is a duplicate of [Bug #1576559], it looks quite
  different since the profile changes but the headset stops working.

  [System info]
  Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64
  pulseaudio: 1:13.99.1-1ubuntu3
  bluez: 5.53-0ubuntu3

  Headset: Sennheiser HD 4.50 BTNC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+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 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa

2020-10-09 Thread Shatakhtsyan Artem
*** This bug is a duplicate of bug 1871794 ***
https://bugs.launchpad.net/bugs/1871794

This is also happening with my JBL TUNE120TWS on Ubuntu 20.04.1
Can not switch to HFP/HSP profile in a GUI-settings menu.
Sound works fine, but have nothing to pick up from in the list of inputs.
Hope this could help.

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

Title:
  [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting
  HSP/HFP audio profile in Focal Fossa

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After updating the release from Ubuntu 19.10 to 20.04, the bluetooth
  headset doesn't work anymore when HSP/HFP profile is selected.

  With Ubuntu 19.10 the headset was working, there was audio and the mic
  was perfect for video conferencing.

  [Steps to reproduce]
  1. Connect headset (used blueman to setup and connect)
  1.1. When connected the system automatically selects A2DP profile
  2. Start playing audio (browser or other)
  3. Change profile to HSP/HFP with pavucontrol (or blueman)
  4. The audio disappears and microphone is not working (no input)
  5. Optionally switch back to A2DP and the audio comes back

  [Expected]
  When switching to HSP/HFP the audio should keep playing and the microphone 
should start working

  [Notes]
  I tried with pavucontrol to switch between profiles while playing audio from 
a browser.
  As side note there's a led in the headset that still blinks when switching 
profile.

  I tried deleting the pulse folder under user's profile .config without
  success, also reinstalled packages and did a `sudo alsa force-reload`
  and rebooting several times.

  Note: not sure this is a duplicate of [Bug #1576559], it looks quite
  different since the profile changes but the headset stops working.

  [System info]
  Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64
  pulseaudio: 1:13.99.1-1ubuntu3
  bluez: 5.53-0ubuntu3

  Headset: Sennheiser HD 4.50 BTNC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+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 1825593] Re: Display scale not remembered when X11 Fractional Scaling is enabled

2020-05-21 Thread Artem P
Update fixed it for me.

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

Title:
  Display scale not remembered when X11 Fractional Scaling is enabled

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Focal:
  Fix Released

Bug description:
  [ Impact ]

  After upgrading to 19.04, I enabled the experimental 'x11-randr-
  fractional-scaling' setting.  If I set scaling to 125, 150, or 200%,
  the setting is remembered and used the next time I log in.  If I set
  scaling to 100%, however, the next time I log in the scaling switches
  back to 200% automatically.  I only want to use fractional scaling for
  external monitors.

  [ Test case ]

  - Use a multi-monitor setup
  - Enable Fractional scaling under X11 (from display settings)
  - Setup mixed-DPI settings in gnome-control-center
  - Log-out
  - Log-in again
+ Settings should be preserved

  [ Regression potential ]

  It's not possible to set some scaling combinations any more with
  multiple or single monitors.

  - Configuration is not restored at all.

  [ Known issue ]

  Monitor settings won't be preserved disabling fractional scaling or
  enabling it in the wayland session.

  
  -

  Background: This is on a Dell XPS 9360 with a 1920x1080 ~168 DPI
  screen.  Pretty standard configuration.  I have my DisplaySize set to
  294x165 in Xorg.conf, Xft.dpi=168, GTK font scaling factor 1.0.

  I have been unable to find an appropriate combination of settings
  where 168 DPI is respected for accurate font rendering, while at the
  same time not scaling up the rest of the UI to unusable proportions.
  Fractional scaling seems to be the only way to adjust some Gnome UI
  elements.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1825593/+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 1875424] [NEW] The image breaks after exiting the mode suspend

2020-04-27 Thread Artem
Public bug reported:

radeon :01:00.0: ring 0 stalled for more than 30212msec

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
Date: Mon Apr 27 18:19:08 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] RV620/M82 [Mobility Radeon HD 
3450/3470] [1002:95c4] (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. RV620/M82 [Mobility Radeon HD 3450/3470] 
[1043:19d3]
InstallationDate: Installed on 2020-04-25 (2 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: ASUSTeK Computer Inc. M51SE
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=1407f934-4717-4e84-bb64-fef8e4687821 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/20/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 204
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: M51SE
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr204:bd02/20/2008:svnASUSTeKComputerInc.:pnM51SE:pvr1.0:rvnASUSTeKComputerInc.:rnM51SE:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: M51SE
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug corruption focal ubuntu

** Attachment added: "20200427_182027.jpg"
   
https://bugs.launchpad.net/bugs/1875424/+attachment/5361731/+files/20200427_182027.jpg

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

Title:
  The image breaks after exiting the mode suspend

Status in xorg package in Ubuntu:
  New

Bug description:
  radeon :01:00.0: ring 0 stalled for more than 30212msec

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Apr 27 18:19:08 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV620/M82 [Mobility Radeon HD 
3450/3470] [1002:95c4] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. RV620/M82 [Mobility Radeon HD 3450/3470] 
[1043:19d3]
  InstallationDate: Installed on 2020-04-25 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: ASUSTeK Computer Inc. M51SE
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=1407f934-4717-4e84-bb64-fef8e4687821 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/20/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: M51SE
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr204:bd02/20/2008:svnASUSTeKComputerInc.:pnM51SE:pvr1.0:rvnASUSTeKComputerInc.:rnM51SE:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: M51SE
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: 

[Desktop-packages] [Bug 1210807] Re: Ukrainian translation problem for "Clean" button in Trash Bin

2019-11-08 Thread Artem Polivanchuk
** Changed in: ubuntu-translations
   Status: Fix Committed => Fix Released

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

Title:
  Ukrainian translation problem for "Clean" button in Trash Bin

Status in Ubuntu Translations:
  Fix Released
Status in language-pack-gnome-uk package in Ubuntu:
  Fix Committed
Status in nautilus package in Ubuntu:
  Invalid

Bug description:
  It's the wrong translation for "Clean" button in Trash Bin - "Пусто".

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: nautilus 1:3.6.3-0ubuntu16
  ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8
  Uname: Linux 3.8.0-19-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  Date: Sat Aug 10 18:22:40 2013
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'geometry' b"'800x550+49+24'"
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'213'
  InstallationDate: Installed on 2013-04-26 (105 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1210807/+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 1792085] Re: MTP not working/very slow on Bionic

2019-11-05 Thread Artem Astafyev
As a temporary workaround ADB push/pull can be used. Mine worked with
speed around 20 Mb/s.

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

Title:
  MTP not working/very slow on Bionic

Status in libmtp:
  New
Status in gvfs package in Ubuntu:
  Incomplete

Bug description:
  Hi, unfortunately (for me) MTP android devices no more work on Ubuntu
  18.04.

  I have used MTP on 16.04 without problems, but on 18.04 it does not
  work. When I connect my Android devices (Samsung A5 and Samsung J3)
  and I try to list directories with many files (e.g. /DCIM/Camera) the
  window hangs until I disconnect the device. Same issue if I try to
  post the command "ls /var/run/1000/gvfs/".

  I have installed Ubuntu 18.04 on two different machines - an older HP
  laptop and a recent DELL laptop - and the issue is present on the all
  of them.

  I suspect a defect on the "libmtp". I tried many alternative solutions
  suggested by the net (e.g. jmtpfs and so on) but anyone worked.

  That's all!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gvfs-fuse 1.36.1-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CasperVersion: 1.394
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 12 06:20:07 2018
  LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gvfs
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/libmtp/+bug/1792085/+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 1768976] Re: Ubuntu 18.04 is overheating after upgrade from 16.04

2019-10-31 Thread Artem
Acer aspire a715-71g. Same problem. Laptop overheating when i switch on
nvidia proprietary driver. On ubuntu 17.10 it worked fine.

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

Title:
  Ubuntu 18.04 is overheating after upgrade from 16.04

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

Bug description:
  Ubuntu is overheating at my laptop. Opening youtube on firefox is
  enough for critical temperature shutdown.

  Using lm-sensors for monitoring on 18.04 the temp varies between 70 and 85°C 
with only firefox or chrome open and doing nothing. 
  On my old 16.04 with same using, the temp varies between 55 and 70°C.

  First thought was the driver nouveau is the problem, and finally I was
  able to install by add "nouveau.modeset=0" at livecd boot options,
  without temp shutdown.

  After install I disable the nouveau at modprobe blacklist, but the
  system continues overheating and shutdown with basic usage.

  
  I have no idea what's happening with the bionic at my laptop.

  My laptop is a Samsung RF411 i5 2nd Generation and Geforce 540M.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.17
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  3 16:22:40 2018
  InstallationDate: Installed on 2018-04-27 (6 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeAptHistorylog:
   Start-Date: 2018-04-27  15:46:02
   End-Date: 2018-04-27  15:46:02
  VarLogDistupgradeAptlog:
   Log time: 2018-04-27 15:45:39.753331
   Starting pkgProblemResolver with broken count: 0
   Starting 2 pkgProblemResolver with broken count: 0
   Done
   Log time: 2018-04-27 15:46:04.859979
  VarLogDistupgradeApttermlog:
   Log started: 2018-04-27  15:46:02
   Log ended: 2018-04-27  15:46:02
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  edir   2354 F pulseaudio
  CompositorRunning: None
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd 2nd Generation Core Processor Family 
Integrated Graphics Controller [144d:c0a5]
 Subsystem: Samsung Electronics Co Ltd GF108M [GeForce GT 540M] [144d:c0a5]
  HibernationDevice: RESUME=UUID=e7a61aee-64c2-4c88-b4e1-4de481d0f88d
  InstallationDate: Installed on 2018-04-27 (36 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. RF511/RF411/RF711
  NonfreeKernelModules: wl
  Package: xserver-xorg-video-nouveau 1:1.0.15-2
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=db38a22c-0e9f-4e1a-b9f7-f7aac2544394 ro quiet splash nouveau.runpm=0
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic ubuntu
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 04/26/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 10HX.M034.20110426.SSH
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: RF511/RF411/RF711
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: 10HX
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 

[Desktop-packages] [Bug 1828775] Re: [amdgpu] High memory consumption

2019-05-20 Thread Artem
Greetings! I deleted everything from the desktop, I also deleted the
packages installed from oibaf-ppa and the problem no longer manifested
itself.

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

Title:
  [amdgpu] High memory consumption

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  High memory consumption

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0+git20190410-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 13 09:47:53 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2019-01-10 (122 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-04-25 (17 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1828775/+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 1828775] Re: [amdgpu] High memory consumption

2019-05-14 Thread Artem
glxinfo | grep Open
OpenGL vendor string: X.Org
OpenGL renderer string: AMD RAVEN (DRM 3.31.0, 5.0.0-13-generic, LLVM 8.0.0)
OpenGL core profile version string: 4.5 (Core Profile) Mesa 19.1.0-devel 
(git-d946cbe 2019-04-26 disco-oibaf-ppa)
OpenGL core profile shading language version string: 4.50
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 4.5 (Compatibility Profile) Mesa 19.1.0-devel 
(git-d946cbe 2019-04-26 disco-oibaf-ppa)
OpenGL shading language version string: 4.50
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.2 Mesa 19.1.0-devel (git-d946cbe 
2019-04-26 disco-oibaf-ppa)
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
OpenGL ES profile extensions:

I will try to disable AMDGPU, a little later.

There are a lot of icons, 8 directories, 150 other elements. I notice
the flickering of the panels and the re-sorting of snits, running
applications, on the panel. I also notice a very long reaction to
pressing the "Open" button in the file selection dialog box, for
example, to send a file to this topic.

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

Title:
  [amdgpu] High memory consumption

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  High memory consumption

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0+git20190410-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 13 09:47:53 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2019-01-10 (122 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-04-25 (17 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1828775/+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 1828775] Re: High memory consumption

2019-05-13 Thread Artem
After 5 hours of work
uptime 
 17:23:23 up  7:32,  1 user,  load average: 2,18, 1,67, 1,56

top -bn 1 | grep gnome-shell
PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+ COMMAND
 1623 articc20   0 5185752   1,2g  47040 S  12,5  16,8  77:12.13 gnome-shell

Attached
cat /proc/`pidof -s gnome-shell`/status > status.txt

** Attachment added: "status.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1828775/+attachment/5263452/+files/status.txt

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

Title:
  High memory consumption

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  High memory consumption

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0+git20190410-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 13 09:47:53 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2019-01-10 (122 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-04-25 (17 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1828775/+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 1828775] Re: High memory consumption

2019-05-13 Thread Artem
** Attachment added: "Xorg.0.log.old"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1828775/+attachment/5263414/+files/Xorg.0.log.old

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

Title:
  High memory consumption

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  High memory consumption

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0+git20190410-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 13 09:47:53 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2019-01-10 (122 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-04-25 (17 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1828775/+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 1828775] Re: High memory consumption

2019-05-13 Thread Artem
At the time of the manifestation of the problem was the following:
VmPeak:  6626452 kB
VmSize:  6564988 kB
VmLck: 0 kB
VmPin: 0 kB
VmHWM:   2261316 kB
VmRSS:   2129212 kB
RssAnon: 2083888 kB
RssFile:   31008 kB
RssShmem:  14316 kB
VmData:  2640704 kB
VmStk:   296 kB
VmExe:16 kB
VmLib:116916 kB
VmPTE:  5900 kB
VmSwap:   405628 kB

RssAnon 2GB too much.


** Attachment added: "lspcik.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1828775/+attachment/5263413/+files/lspcik.txt

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

Title:
  High memory consumption

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  High memory consumption

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0+git20190410-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 13 09:47:53 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2019-01-10 (122 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-04-25 (17 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1828775/+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 1828775] Re: High memory consumption

2019-05-13 Thread Artem
I did not install additional extensions. And I did not find an easy way
to create a list of installed extensions, except for dpkg -l.

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

Title:
  High memory consumption

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  High memory consumption

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0+git20190410-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 13 09:47:53 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2019-01-10 (122 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-04-25 (17 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1828775/+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 1828775] Re: High memory consumption

2019-05-13 Thread Artem
I have already restarted the computer. But 'status.txt' =
'ProcStatus.txt' from the second post.

uptime 
 11:53:00 up  2:02,  1 user,  load average: 1,07, 1,34, 1,22

dpkg -l | grep gnome-shell
ii  gnome-shell  3.32.0+git20190410-1ubuntu1
  amd64graphical shell for the GNOME desktop
ii  gnome-shell-common   3.32.0+git20190410-1ubuntu1
  all  common files for the GNOME graphical shell
ii  gnome-shell-extension-appindicator   28-1   
  all  AppIndicator/KStatusNotifierItem support for GNOME Shell
ii  gnome-shell-extension-desktop-icons  19.01.1-1  
  all  desktop icon support for GNOME Shell
ii  gnome-shell-extension-ubuntu-dock64ubuntu7  
  all  Ubuntu Dock for GNOME Shell
ii  yaru-theme-gnome-shell   19.04.2
  all  Yaru GNOME Shell desktop theme from the Ubuntu Community


** Attachment added: "freshstatus.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1828775/+attachment/5263405/+files/freshstatus.txt

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

Title:
  High memory consumption

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  High memory consumption

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0+git20190410-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 13 09:47:53 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2019-01-10 (122 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-04-25 (17 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1828775/+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 1828775] Re: High CPU utilization, high memory consumption, does not respond to mouse movement.

2019-05-13 Thread Artem
Please focus on high memory consumption, everything else is due to this.

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

Title:
  High CPU utilization, high memory consumption, does not respond to
  mouse movement.

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  High CPU utilization, high memory consumption, does not respond to
  mouse movement.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0+git20190410-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 13 09:47:53 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2019-01-10 (122 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-04-25 (17 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1828775/+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 1828775] [NEW] High CPU utilization, high memory consumption, does not respond to mouse movement.

2019-05-13 Thread Artem
Public bug reported:

High CPU utilization, high memory consumption, does not respond to mouse
movement.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-shell 3.32.0+git20190410-1ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon May 13 09:47:53 2019
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
 b'org.gnome.shell' b'app-picker-view' b'uint32 1'
 b'org.gnome.shell' b'favorite-apps' redacted by apport
 b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
InstallationDate: Installed on 2019-01-10 (122 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to disco on 2019-04-25 (17 days ago)

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


** Tags: amd64 apport-bug disco third-party-packages

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

Title:
  High CPU utilization, high memory consumption, does not respond to
  mouse movement.

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  High CPU utilization, high memory consumption, does not respond to
  mouse movement.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell 3.32.0+git20190410-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 13 09:47:53 2019
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   b'org.gnome.shell' b'app-picker-view' b'uint32 1'
   b'org.gnome.shell' b'favorite-apps' redacted by apport
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2019-01-10 (122 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to disco on 2019-04-25 (17 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1828775/+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 1815615] [NEW] Xorg freeze

2019-02-12 Thread Artem
Public bug reported:


[  290.765205] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma0 timeout, 
signaled seq=20358, emitted seq=20361
[  290.765212] [drm] GPU recovery disabled.
[  485.063911] INFO: task kworker/u32:1:50 blocked for more than 120 seconds.
[  485.063922]   Tainted: G   OE 4.20.7-042007-generic 
#201902061234
[  485.063925] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[  485.063929] kworker/u32:1   D050  2 0x8000
[  485.063952] Workqueue: events_unbound commit_work [drm_kms_helper]
[  485.063955] Call Trace:
[  485.063967]  __schedule+0x29e/0x840
[  485.063971]  schedule+0x2c/0x80
[  485.063974]  schedule_preempt_disabled+0xe/0x10
[  485.063977]  __ww_mutex_lock.isra.11+0x3d8/0x760
[  485.063981]  __ww_mutex_lock_slowpath+0x16/0x20
[  485.063983]  ww_mutex_lock+0x34/0x50
[  485.064115]  amdgpu_dm_do_flip+0xeb/0x3a0 [amdgpu]
[  485.064213]  amdgpu_dm_atomic_commit_tail+0x738/0xe20 [amdgpu]
[  485.064216]  ? __switch_to_asm+0x40/0x70
[  485.064219]  ? __switch_to_asm+0x34/0x70
[  485.064221]  ? wait_for_completion_timeout+0x38/0x140
[  485.064223]  ? __switch_to_asm+0x40/0x70
[  485.064225]  ? __switch_to_asm+0x34/0x70
[  485.064227]  ? __switch_to_asm+0x40/0x70
[  485.064239]  commit_tail+0x42/0x70 [drm_kms_helper]
[  485.064248]  commit_work+0x12/0x20 [drm_kms_helper]
[  485.064253]  process_one_work+0x20f/0x410
[  485.064256]  worker_thread+0x34/0x400
[  485.064258]  kthread+0x120/0x140
[  485.064261]  ? pwq_unbound_release_workfn+0xd0/0xd0
[  485.064263]  ? __kthread_parkme+0x70/0x70
[  485.064266]  ret_from_fork+0x22/0x40
[  485.064463] INFO: task kworker/u32:14:2793 blocked for more than 120 seconds.
[  485.064467]   Tainted: G   OE 4.20.7-042007-generic 
#201902061234
[  485.064468] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[  485.064470] kworker/u32:14  D0  2793  2 0x8000
[  485.064483] Workqueue: events_unbound commit_work [drm_kms_helper]
[  485.064484] Call Trace:
[  485.064487]  __schedule+0x29e/0x840
[  485.064489]  schedule+0x2c/0x80
[  485.064491]  schedule_timeout+0x258/0x360
[  485.064584]  ? optc1_get_crtc_scanoutpos+0x69/0xa0 [amdgpu]
[  485.064590]  dma_fence_default_wait+0x20a/0x280
[  485.064592]  ? dma_fence_release+0xa0/0xa0
[  485.064595]  dma_fence_wait_timeout+0xe7/0x110
[  485.064598]  reservation_object_wait_timeout_rcu+0x201/0x340
[  485.064663]  ? amdgpu_get_vblank_counter_kms+0x111/0x160 [amdgpu]
[  485.064757]  amdgpu_dm_do_flip+0x12c/0x3a0 [amdgpu]
[  485.064852]  amdgpu_dm_atomic_commit_tail+0x738/0xe20 [amdgpu]
[  485.064855]  ? __switch_to_asm+0x40/0x70
[  485.064857]  ? __switch_to_asm+0x34/0x70
[  485.064859]  ? wait_for_completion_timeout+0x38/0x140
[  485.064861]  ? __switch_to_asm+0x40/0x70
[  485.064863]  ? __switch_to_asm+0x34/0x70
[  485.064865]  ? __switch_to_asm+0x40/0x70
[  485.064876]  commit_tail+0x42/0x70 [drm_kms_helper]
[  485.064886]  commit_work+0x12/0x20 [drm_kms_helper]
[  485.064889]  process_one_work+0x20f/0x410
[  485.064891]  worker_thread+0x34/0x400
[  485.064894]  kthread+0x120/0x140
[  485.064896]  ? pwq_unbound_release_workfn+0xd0/0xd0
[  485.064898]  ? __kthread_parkme+0x70/0x70
[  485.064901]  ret_from_fork+0x22/0x40
[  538.507722] r8169 :02:00.0: invalid short VPD tag 00 at offset 1
[  538.507750] pcieport :00:01.3: AER: Multiple Corrected error received: 
:00:01.0
[  538.507772] pcieport :00:01.3: PCIe Bus Error: severity=Corrected, 
type=Data Link Layer, (Transmitter ID)
[  538.507781] pcieport :00:01.3:   device [1022:15d3] error 
status/mask=1100/6000
[  538.507787] pcieport :00:01.3:[ 8] Rollover
[  538.507791] pcieport :00:01.3:[12] Timeout
[  574.828588] RTW: WARN [TXFOVW]
[  574.831312] RTW: WARN [TXFOVW]
[  605.900149] INFO: task kworker/u32:1:50 blocked for more than 120 seconds.
[  605.900156]   Tainted: G   OE 4.20.7-042007-generic 
#201902061234
[  605.900159] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[  605.900162] kworker/u32:1   D050  2 0x8000
[  605.900183] Workqueue: events_unbound commit_work [drm_kms_helper]
[  605.900185] Call Trace:
[  605.900195]  __schedule+0x29e/0x840
[  605.900199]  schedule+0x2c/0x80
[  605.900202]  schedule_preempt_disabled+0xe/0x10
[  605.900204]  __ww_mutex_lock.isra.11+0x3d8/0x760
[  605.900208]  __ww_mutex_lock_slowpath+0x16/0x20
[  605.900210]  ww_mutex_lock+0x34/0x50
[  605.900322]  amdgpu_dm_do_flip+0xeb/0x3a0 [amdgpu]
[  605.900420]  amdgpu_dm_atomic_commit_tail+0x738/0xe20 [amdgpu]
[  605.900423]  ? __switch_to_asm+0x40/0x70
[  605.900425]  ? __switch_to_asm+0x34/0x70
[  605.900428]  ? wait_for_completion_timeout+0x38/0x140
[  605.900430]  ? __switch_to_asm+0x40/0x70
[  605.900432]  ? __switch_to_asm+0x34/0x70
[  605.900434]  ? __switch_to_asm+0x40/0x70
[  605.900445]  commit_tail+0x42/0x70 [drm_kms_helper]
[  605.900455]  

[Desktop-packages] [Bug 1532508] Re: Screen contents revealed briefly on resume, before even unlocking

2019-01-25 Thread Artem Mikhmel
Still having the same issue:
Linux DEll-XPS15 4.16.7-041607-generic #201805021131 SMP Wed May 2 15:34:55 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
Ubuntu 18.04.1 LTS

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

Title:
  Screen contents revealed briefly on resume, before even unlocking

Status in GNOME Shell:
  In Progress
Status in Ubuntu GNOME:
  Confirmed
Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Xenial:
  Fix Released
Status in gnome-shell package in Debian:
  Confirmed

Bug description:
  [Impact]

  When lock is enabled, the screen doesn't get blank/covered by
  lockscreen before suspending, thus on early resume the content might
  be shown.

  Video showing the bug: https://youtu.be/dDOgtK1MldI

  Reproduced on Ubuntu 2015.10, Ubuntu 2014.04

  [Test case]

  1. Work on highly secret files
  2. Close the lid of your laptop and go have a break
  3. Anyone who opens the lid of the laptop can see the secret files for a half 
second before the lock screen appears

  [Possible Regression]

  Content on screen isn't painted anymore and screen stays black.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1532508/+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 1788286] [NEW] The screen collapses after getting out of sleep

2018-08-21 Thread Artem
Public bug reported:

E): enp2s0: link becomes ready
Aug 20 13:49:02 M51SE kernel: [  272.572110] radeon :01:00.0: ring 0 
stalled for more than 10236msec
Aug 20 13:49:02 M51SE kernel: [  272.572126] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
Aug 20 13:49:03 M51SE kernel: [  273.084086] radeon :01:00.0: ring 0 
stalled for more than 10748msec
Aug 20 13:49:03 M51SE kernel: [  273.084099] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
Aug 20 13:49:03 M51SE kernel: [  273.596091] radeon :01:00.0: ring 0 
stalled for more than 11260msec
Aug 20 13:49:03 M51SE kernel: [  273.596107] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
Aug 20 13:49:04 M51SE kernel: [  274.108084] radeon :01:00.0: ring 0 
stalled for more than 11772msec
Aug 20 13:49:04 M51SE kernel: [  274.108098] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
Aug 20 13:49:04 M51SE kernel: [  274.620076] radeon :01:00.0: ring 0 
stalled for more than 12284msec
Aug 20 13:49:04 M51SE kernel: [  274.620088] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
Aug 20 13:49:05 M51SE kernel: [  275.136059] radeon :01:00.0: ring 0 
stalled for more than 12800msec
Aug 20 13:49:05 M51SE kernel: [  275.136069] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
Aug 20 13:49:05 M51SE kernel: [  275.644077] radeon :01:00.0: ring 0 
stalled for more than 13308msec
Aug 20 13:49:05 M51SE kernel: [  275.644090] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
Aug 20 13:49:06 M51SE kernel: [  276.156083] radeon :01:00.0: ring 0 
stalled for more than 13820msec
Aug 20 13:49:06 M51SE kernel: [  276.156097] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
Aug 20 13:49:06 M51SE kernel: [  276.668078] radeon :01:00.0: ring 0 
stalled for more than 14332msec
Aug 20 13:49:06 M51SE kernel: [  276.668090] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
Aug 20 13:49:07 M51SE kernel: [  277.180071] radeon :01:00.0: ring 0 
stalled for more than 14844msec
Aug 20 13:49:07 M51SE kernel: [  277.180083] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
Aug 20 13:49:07 M51SE kernel: [  277.692072] radeon :01:00.0: ring 0 
stalled for more than 15356msec
Aug 20 13:49:07 M51SE kernel: [  277.692085] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
Aug 20 13:49:08 M51SE kernel: [  278.204077] radeon :01:00.0: ring 0 
stalled for more than 15868msec
Aug 20 13:49:08 M51SE kernel: [  278.204090] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
Aug 20 13:49:08 M51SE kernel: [  278.716072] radeon :01:00.0: ring 0 
stalled for more than 16380msec
Aug 20 13:49:08 M51SE kernel: [  278.716085] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
Aug 20 13:49:09 M51SE kernel: [  279.228080] radeon :01:00.0: ring 0 
stalled for more than 16892msec
Aug 20 13:49:09 M51SE kernel: [  279.228093] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
Aug 20 13:49:09 M51SE kernel: [  279.740071] radeon :01:00.0: ring 0 
stalled for more than 17404msec
Aug 20 13:49:09 M51SE kernel: [  279.740083] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
Aug 20 13:49:10 M51SE kernel: [  280.252071] radeon :01:00.0: ring 0 
stalled for more than 17916msec
Aug 20 13:49:10 M51SE kernel: [  280.252083] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
Aug 20 13:49:10 M51SE kernel: [  280.764076] radeon :01:00.0: ring 0 
stalled for more than 18428msec
Aug 20 13:49:10 M51SE kernel: [  280.764089] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
Aug 20 13:49:11 M51SE kernel: [  281.276048] radeon :01:00.0: ring 0 
stalled for more than 18940msec
Aug 20 13:49:11 M51SE kernel: [  281.276059] radeon :01:00.0: GPU lockup 
(current fence id 0x48db last fence id 0x48f6 on ring 0)
Aug 20 13:49:11 M51SE kernel: [  281.788070] radeon :01:00.0: ring 0 
stalled for more than 19452msec
Aug 20 13:49:11 M51SE kernel: [  281.788082] radeon :01:00.0: GPU 

[Desktop-packages] [Bug 202300] Re: default colors provide bad contrast to default background

2018-04-06 Thread Artem
Can i ask Ubuntu team to add good Light terminal theme into new 18.04
LTS release? I mean professionally made theme. Because this Tango light
or Solarized light looks not really good. Some colors don't go together
and barely readable on light background.

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

Title:
  default colors provide bad contrast to default background

Status in GNOME Terminal:
  Confirmed
Status in gnome-terminal package in Ubuntu:
  Invalid

Bug description:
  The default colors of gnome-terminal are not optimally readable on a
  white background. They should be more saturated.

  The original submitter especially did not like the "light blue" color,
  which should be darker in his opinion.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-terminal/+bug/202300/+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 36812] Re: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts

2017-08-16 Thread Artem Kovalov
Applying a patch indicated tlk saved my day. Hope some day this issue
will be resolved forever.

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

Title:
  Keyboard layout change on hotkeys press instead of release and do not
  work well with shortcuts

Status in gnome-control-center:
  Unknown
Status in X.Org X server:
  In Progress
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Fix Released

Bug description:
  This is a bug about shortcuts mapped to combinations which include
  each other.

  For example, if we have Ctrl+Shift (for keyboard layout) and Ctrl+Shift+N (to 
open a new terminal), then we are practically unable to use the second 
shortcut; this is what happens:
  Ctrl press  (nothing happens)
  Shift press (keyboard layout change)
  N (a simple N appears, since a shortcut has already fired)

  The expected behavior is to fire shortcuts on the release (not on
  press) of the special keys (ctrl,shift,alt, etc) which is also how
  Windows behave. This is a serious problem for bilingual layouts,
  typically using Alt+Shift or Ctrl+Shift for keyboard layout change.

  For users being affected by this problem, the easiest solution for now is to 
add this PPA in your repositories:
  https://launchpad.net/~oded-geek/+archive/xorg-patches

  Practical summary of this bug for ubuntu developers (since reading 120 
comments is impractical for most):
  This problem is a really old (since 2004) issue of the xkb part of xorg; the 
main discussion was made upstream in freedesktop-bugs #865. There has been a 
patch from Ilya Murav'jov for upstream (#55), and attached here (#61).
  Upstream xorg has refused to apply the patch, mainly because it "explicitly 
contradicts the (xkb) spec"  (#84, #91).
  This patch has been reported to work for many people without any problems, 
and there is also a PPA by Oded Arbel (#95) where he maintains a patched 
version of the ubuntu xorg.
  The proper resolution of this bug would be to apply this patch to the 
upstream xorg, or at minimum to the official ubuntu xorg package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/36812/+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 1683383] Re: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts (reopen)

2017-08-16 Thread Artem Kovalov
Пересобрать таки помогло) Аж выдохнул. Жаль, что мейнтейнеры ppa не
обновляют оперативно билды для свежих релизов.

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

Title:
  Keyboard layout change on hotkeys press instead of release and do not
  work well with shortcuts (reopen)

Status in X.Org X server:
  In Progress
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  This is a reopen of bug #36812, which has reappeared in Kubuntu 17.04
  Zesty Zapus.

  This is a bug about shortcuts mapped to combinations which include
  each other.

  For example, if we have Ctrl+Shift (for keyboard layout) and Ctrl+Shift+N (to 
open a new terminal), then we are practically unable to use the second 
shortcut; this is what happens:
  Ctrl press (nothing happens)
  Shift press (keyboard layout change)
  N (a simple N appears, since a shortcut has already fired)

  The expected behavior is to fire shortcuts on the release (not on
  press) of the special keys (ctrl,shift,alt, etc) which is also how
  Windows behave. This is a serious problem for bilingual layouts,
  typically using Alt+Shift or Ctrl+Shift for keyboard layout change.

  Apparently, the bug has reappeared after the patch that used to fix
  the problem (208_switch_on_release.diff) has been removed from X.Org
  1.19 packages. There is an updated patch in the upstream ticket
  https://bugs.freedesktop.org/show_bug.cgi?id=865 (link to the
  attachment: https://bugs.freedesktop.org/attachment.cgi?id=129861).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xserver-xorg-core 2:1.19.3-1ubuntu1
  Uname: Linux 4.9.0-22.1-liquorix-amd64 x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Apr 17 17:46:35 2017
  InstallationDate: Installed on 2015-05-01 (716 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: xorg-server
  UpgradeStatus: Upgraded to zesty on 2017-04-16 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1683383/+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 1244548] Re: Keyboard shortcut for changing keyboard layout does not work on lock and login screen

2017-07-19 Thread Artem V L
Keyboard layout changing shortcuts does not work for me on Ubuntu 16.04.2 LTS 
x64 with the latest updates when the screen is locked from the Unity session 
(anyway it is done by the gnome-screensav).
I have installed Caffeine app, but it seems it has not changed any screensaver 
parameters. And after Caffeine killing the issue is not fixed.

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

Title:
  Keyboard shortcut for changing keyboard layout does not work on lock
  and login screen

Status in GNOME Screensaver:
  New
Status in gnome-screensaver package in Ubuntu:
  Confirmed

Bug description:
  Shortcut for changing keyboard layout does not work on lock screen (to
  change keyboard layout for entering password).

  - Switch to some non-english layout (otherwise lock screen will not have 
layout indicator at all)
  - Lock the screen
  - Press your shortcut for changing keyboard layout (i.e. ctrl+shift) -- it 
will not change layout
  - Clicking layout indicator near password entry box works
  --
  For other layout switching problems introduced in Ubuntu 13.10 you can see 
bug 1218322.
  --

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-screensaver 3.6.1-0ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
  Uname: Linux 3.11.0-13-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Fri Oct 25 11:01:10 2013
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  GsettingsGnomeSession:
   org.gnome.desktop.session idle-delay uint32 300
   org.gnome.desktop.session session-name 'ubuntu'
  InstallationDate: Installed on 2013-10-23 (1 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  SourcePackage: gnome-screensaver
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-screensaver/+bug/1244548/+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 1694692] [NEW] Some GTK apps have empty window on the kernel 4.11.3

2017-05-31 Thread Artem V L
Public bug reported:

After the kernel update on Linux Ubuntu 16.04 x64 from 4.11.2 to 4.11.3 some 
GUI apps become broken, the visual image is attached.
For example, geary email app has empty GUI window and the following log:

$ grep gear /var/log/syslog
May 31 13:02:58 A2XLab gnome-session[3212]: (geary:3533): Gtk-CRITICAL **: 
gtk_widget_event: assertion 'WIDGET_REALIZED_FOR_EVENT (widget, event)' failed
May 31 13:02:59 A2XLab gnome-session[3212]: (geary:3533): Gtk-CRITICAL **: 
gtk_widget_event: assertion 'WIDGET_REALIZED_FOR_EVENT (widget, event)' failed
May 31 13:04:21 A2XLab gnome-session[3212]: (gnome-software:3523): As-WARNING 
**: failed to rescan: Failed to parse 
/usr/share/applications/geary.desktop.dpkg-new file: cannot process file of 
type text/plain
May 31 13:04:21 A2XLab gnome-session[3212]: (gnome-software:3523): As-WARNING 
**: failed to rescan: Failed to parse 
/usr/share/applications/geary.desktop.dpkg-tmp file: cannot process file of 
type text/plain
May 31 13:04:21 A2XLab gnome-session[3212]: (gnome-software:3523): As-WARNING 
**: failed to rescan: Failed to parse 
/usr/share/applications/geary-autostart.desktop.dpkg-new file: cannot process 
file of type text/plain
May 31 13:04:21 A2XLab gnome-session[3212]: (gnome-software:3523): As-WARNING 
**: failed to rescan: Failed to parse 
/usr/share/applications/geary-autostart.desktop.dpkg-tmp file: cannot process 
file of type text/plain
May 31 13:04:21 A2XLab gnome-session[3212]: (gnome-software:3523): As-WARNING 
**: failed to rescan: Failed to parse /usr/share/applications/geary.desktop 
file: cannot process file of type application/x-desktop
May 31 13:04:21 A2XLab gnome-session[3212]: (gnome-software:3523): As-WARNING 
**: failed to rescan: Failed to parse 
/usr/share/applications/geary-autostart.desktop file: cannot process file of 
type application/x-desktop
May 31 13:05:51 A2XLab gnome-session[3212]: (gnome-software:3523): As-WARNING 
**: failed to rescan: Failed to parse 
/usr/share/applications/geary.desktop.dpkg-new file: cannot process file of 
type text/plain
May 31 13:05:51 A2XLab gnome-session[3212]: (gnome-software:3523): As-WARNING 
**: failed to rescan: Failed to parse 
/usr/share/applications/geary-autostart.desktop.dpkg-new file: cannot process 
file of type text/plain
May 31 13:05:51 A2XLab gnome-session[3212]: (gnome-software:3523): As-WARNING 
**: failed to rescan: Failed to parse /usr/share/applications/geary.desktop 
file: cannot process file of type application/x-desktop
May 31 13:05:51 A2XLab gnome-session[3212]: (gnome-software:3523): As-WARNING 
**: failed to rescan: Failed to parse 
/usr/share/applications/geary-autostart.desktop file: cannot process file of 
type application/x-desktop
May 31 13:08:46 A2XLab gnome-session[3212]: (gnome-software:3523): As-WARNING 
**: failed to rescan: Failed to parse 
/usr/share/applications/geary.desktop.dpkg-new file: cannot process file of 
type text/plain
May 31 13:08:46 A2XLab gnome-session[3212]: (gnome-software:3523): As-WARNING 
**: failed to rescan: Failed to parse 
/usr/share/applications/geary-autostart.desktop.dpkg-new file: cannot process 
file of type text/plain
May 31 13:08:47 A2XLab gnome-session[3212]: (gnome-software:3523): As-WARNING 
**: failed to rescan: Failed to parse /usr/share/applications/geary.desktop 
file: cannot process file of type application/x-desktop
May 31 13:08:47 A2XLab gnome-session[3212]: (gnome-software:3523): As-WARNING 
**: failed to rescan: Failed to parse 
/usr/share/applications/geary-autostart.desktop file: cannot process file of 
type application/x-desktop
May 31 13:12:10 A2XLab gnome-session[3212]: (geary:3533): Gtk-CRITICAL **: 
gtk_widget_event: assertion 'WIDGET_REALIZED_FOR_EVENT (widget, event)' failed
May 31 13:21:51 A2XLab gnome-session[3212]: (geary:3533): Gtk-CRITICAL **: 
gtk_widget_event: assertion 'WIDGET_REALIZED_FOR_EVENT (widget, event)' failed

Updating the Geary itself from the Ubuntu-default version 0.10 to 0.11 did not 
fixed the issue.
Most of other apps works fine.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg (not installed)
Uname: Linux 4.11.3-041103-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
BootLog:
 
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: Wed May 31 13:13:14 2017
DistUpgraded: 2016-09-11 19:36:31,920 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: xenial
DistroVariant: ubuntu
EcryptfsInUse: Yes
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
0b) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:2218]
InstallationDate: Installed on 2014-10-25 (948 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release 

[Desktop-packages] [Bug 1690520] Re: Scaling resets from 1.5 to 1 after screen lock / unlock

2017-05-15 Thread Artem Korzhenevskiy
*** This bug is a duplicate of bug 1689356 ***
https://bugs.launchpad.net/bugs/1689356

** This bug has been marked a duplicate of bug 1689356
   UI scale being reset to 1 everytime when display sleeps for a while

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

Title:
  Scaling resets from 1.5 to 1 after screen lock / unlock

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.04, I have a 4K (3840x2160) monitor connected to my
  computer.

  I have set the scaling to 1.5 (System Settings / Displays / Scale for
  menu and title bars).

  When I walk away from the computer, after a while the screen is
  locked. When I unlock it by entering my password, the scaling is reset
  to 1 and the Ubuntu menu bar at the top of the screen, the launcher
  and windows are all small.

  I have to go back to System Settings / Displays and set it back to
  1.5.

  Locking / unlocking the desktop should not affect the scaling factor
  setting.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7
  Date: Sat May 13 11:06:24 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Iris Graphics 540 [8086:1926] (rev 0a) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation Iris Graphics 540 [8086:2063]
  InstallationDate: Installed on 2017-05-06 (6 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 046d:c31d Logitech, Inc. Media Keyboard K200
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed 
root=UUID=2278e5dc-858b-486d-9d4f-363aef26fab7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.vendor: Intel Corp.
  dmi.board.vendor: Intel corporation
  version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.14-0ubuntu1
  xserver.bootTime: Sat May 13 09:02:20 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1
  xserver.video_driver: modeset

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

2017-01-28 Thread Artem
Exactly the same issue on Ubuntu 14.04.5 LTS, laptop DELL Latitude E6440 with 
Intel Graphics.
Sometimes it happens ones per 2 weeks, sometimes every 2 days.

-- 
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:
  Expired

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 1532544] Re: Window becomes unresponsive and sound stops when skipping to next track

2016-07-24 Thread Artem S.
I fogot copypaste 'fi' as last line in the script

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

Title:
  Window becomes unresponsive and sound stops when skipping to next
  track

Status in rhythmbox package in Ubuntu:
  New

Bug description:
  When skipping to the next track rhythmbox will sometimes become
  unresponsive and rapidly send the error

  (rhythmbox:4897): GStreamer-CRITICAL **: gst_poll_write_control:
  assertion 'set != NULL' failed

  (rhythmbox:4897): GStreamer-WARNING **: gstsystemclock: write control
  failed in wakeup_async, trying again: 11:Resource temporarily
  unavailable

  
  to ~/.cache/upstart/indicator-sound.log which takes up most of the CPU and 
quickly fills all hard drive space.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: rhythmbox 3.2.1-1ubuntu3.1
  ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6
  Uname: Linux 4.2.0-23-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Jan 10 23:04:18 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-26 (168 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: rhythmbox
  UpgradeStatus: Upgraded to wily on 2015-10-23 (79 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1532544/+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 1532544] Re: Window becomes unresponsive and sound stops when skipping to next track

2016-07-24 Thread Artem S.
Please raise improtance of the issue. It's not Low!

indicator-sound.log very quickly eats all free space. It also tries to
do this constantly. My 13G of free space it took in less then hour.

And since it tries to write log line tens times in a second, I have got
several apps that lost their settings, because when they tried to save
them (overwrite files with settings) they failed to do this and wrote
file with 0 size. All settings were lost.

It's huge impact.

I had to create script to protect me from this:
--
 ~ -> cat ~/.local/indicator-workaround.sh 
#!/bin/bash

echo $(date) "Check for indicator-sound size"

if [ $(stat -c %s ~/.cache/upstart/indicator-sound.log) -ge 1000 ] ; then
echo $(date) "Killing indicator-sound!"
rm ~/.cache/upstart/indicator-sound.log
pkill -f indicator-sound-service
--

And add it to 'crontab -e':
-
SHELL=/bin/bash

*/5 * * * *  ~/.local/indicator-workaround.sh >>~/.cache/cron.log 2>&1
-

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

Title:
  Window becomes unresponsive and sound stops when skipping to next
  track

Status in rhythmbox package in Ubuntu:
  New

Bug description:
  When skipping to the next track rhythmbox will sometimes become
  unresponsive and rapidly send the error

  (rhythmbox:4897): GStreamer-CRITICAL **: gst_poll_write_control:
  assertion 'set != NULL' failed

  (rhythmbox:4897): GStreamer-WARNING **: gstsystemclock: write control
  failed in wakeup_async, trying again: 11:Resource temporarily
  unavailable

  
  to ~/.cache/upstart/indicator-sound.log which takes up most of the CPU and 
quickly fills all hard drive space.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: rhythmbox 3.2.1-1ubuntu3.1
  ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6
  Uname: Linux 4.2.0-23-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Jan 10 23:04:18 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-26 (168 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: rhythmbox
  UpgradeStatus: Upgraded to wily on 2015-10-23 (79 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1532544/+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 1587730] Re: graphic system freezes after a while, can still ssh into machine

2016-06-02 Thread Artem
Have the similar issue under lubuntu 16.04. Virtualbox 5.20. i5 GTX 960
Freez in firefox/libreoffice/chromium..
It helps to switch terminals CtrlAlt-F1 and back CtrlAlt-F7

Usaly I killall firefox from CtrlAlt-F1 (terminal alway works)
But today I have just switched to new terminal and back and it helps.

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

Title:
  graphic system freezes after a while, can still ssh into machine

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.04 desktop with all updates up to date
  Gigagyte GA-Z170 motherboard, Intel i7-6700 3.4gHz, 64GB RAM, Samsung 840 
SSD, Gigabyte GEForce GT710 graphics (nvidia chipset)

  Very light load. A few terminal windows, a few Firefox pages,
  Thunderbird, and VirtualBox (with the extension pack loaded) running
  one small Linux VM with 512Mb memory (very lightly loaded as it's only
  running bind9). I think (but don't have perfect certainty on this)
  that some of the crashes have happened without VirtualBox running.
  Also running rsync so that backuppc on a separate machine can back it
  up over the network (backuppc has been a real lifesaver with all the
  reinstallations!)

  After booting the system runs happily for a while then the GUI
  freezes. This can take a few hours or up to a day or two. You can
  still ssh into the system, and if you do "top" it typically shows 100%
  CPU load on systemd-timesync.

  The same happens whether I use nouveau or the proprietary nvidia driver (361)
  I have tried a complete reinstallation (4 times already, starting to get 
quite frustrating) using the proprietary drivers and NOT using the proprietary 
drivers and the same still happens. The most recent time was with nouveau, and 
Xorg.log has a number of entries like this:
  (EE) [mi] EQ overflowing.  Additional events will be discarded until existing 
events are processed.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x5652cde325ce]
  (EE) 1: /usr/lib/xorg/Xorg (mieqEnqueue+0x253) [0x5652cde14083]
  (EE) 2: /usr/lib/xorg/Xorg (QueuePointerEvents+0x52) [0x5652cdcec662]
  (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f31f985c000+0x61f3) 
[0x7f31f98621f3]
  (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f31f985c000+0x6a5d) 
[0x7f31f9862a5d]
  (EE) 5: /usr/lib/xorg/Xorg (0x5652cdc8+0x94228) [0x5652cdd14228]
  (EE) 6: /usr/lib/xorg/Xorg (0x5652cdc8+0xb96f2) [0x5652cdd396f2]
  (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (0x7f3202cef000+0x354a0) 
[0x7f3202d244a0]
  (EE) 8: /usr/lib/xorg/Xorg (GiveUp+0x0) [0x5652cde37330]
  (EE) 9: /lib/x86_64-linux-gnu/libc.so.6 (0x7f3202cef000+0x354a0) 
[0x7f3202d244a0]
  (EE) 10: /lib/x86_64-linux-gnu/libc.so.6 (__select+0x13) [0x7f3202debcf3]
  (EE) 11: /usr/lib/xorg/Xorg (WaitForSomething+0x1d7) [0x5652cde2f307]
  (EE) 12: /usr/lib/xorg/Xorg (0x5652cdc8+0x539ee) [0x5652cdcd39ee]
  (EE) 13: /usr/lib/xorg/Xorg (0x5652cdc8+0x57c33) [0x5652cdcd7c33]
  (EE) 14: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) 
[0x7f3202d0f830]
  (EE) 15: /usr/lib/xorg/Xorg (_start+0x29) [0x5652cdcc1f59]
  (EE) 
  (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up 
the stack.
  (EE) [mi] mieq is *NOT* the cause.  It is a victim.
  (EE) [mi] EQ overflow continuing.  100 events have been dropped.
   
  Then at the end the last few are:

  [  6265.543] [mi] Increasing EQ size to 1024 to prevent dropped events.
  [  6265.543] [mi] EQ processing has resumed after 1070 dropped events.
  [  6265.543] [mi] This may be caused by a misbehaving driver monopolizing the 
server's resources.

  What cna the problem possibly be, especially as 16.04 is meant to be a
  stable release and an Nvidia GT710 card is hardly bleeding-edge? Help
  greatly appreciated!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-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: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Jun  1 13:22:13 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.18, 4.4.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation Device [10de:128b] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Device [1458:36ec]
  InstallationDate: Installed on 2016-06-01 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Gigabyte Technology Co., Ltd. Z170-D3H
  

[Desktop-packages] [Bug 1288182] Re: Cyrillic not displayed in the input field

2016-03-01 Thread Artem
Tooo tired of this bug. Sometimes i need to fill some forms in Russian
but Evince still doesn't provide this feature working properly. Do
something please!

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

Title:
  Cyrillic not displayed in the input field

Status in Evince:
  Unknown
Status in Poppler:
  Confirmed
Status in evince package in Ubuntu:
  Triaged
Status in poppler package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 14.04 x64
  Evince 3.10.3
  Cyrillic not displayed in the input field.

  In attach screenshot: input field with text 'This сyrillic:
  "Кириллица"'

  Upd.

  Still actual for Ubuntu 16.04 x64
  Evince 3.18.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/evince/+bug/1288182/+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 875672] Re: Rhythmbox window isn't raised when clicking on it in the sound menu

2015-09-17 Thread Artem Baguinski
Can this be solved without having to install CompizConfig Settings Manager? 
Can ubuntu ship with this option set to Off by default?

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

Title:
  Rhythmbox window isn't raised when clicking on it in the sound menu

Status in banshee package in Ubuntu:
  Confirmed
Status in compiz package in Ubuntu:
  Confirmed

Bug description:
  [Originally reported for banshee.  Re-tested with Rhythymbox on Ubuntu
  12.04].

  1) Start rhythymbox.  Leave the window open
  2) Open another application e.g. gnome-terminal or firefox.
  3) Click on sound menu (volume icon in the top panel).  Click on banshee.

  Normally (when the rhythymbox window is closed, but still playing),
  you'd see the banshee window appear.  As a new window, it would appear
  in front of the other application.

  But in this case, the rhythymbox window is already open.  Instead of
  being raised to the front, as I'd expect, the Unity sidebar pops up,
  with the Banshee icon jiggling about.

  I know very roughly why this happens.  The rhythymbox window _is_
  demanding attention.  But it's clearly doing the wrong thing.  There's
  no reason why the user should have to click on the jiggling banshee
  icon - they've already said that they want to see the Banshee window!

  I don't think Unity needs a new API for this.  I don't have this
  problem with the integration of Thunderbird and the Mail application
  notifier.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: banshee-extension-soundmenu 2.2.0-1ubuntu2
  ProcVersionSignature: Ubuntu 2.6.38-11.50-generic 2.6.38.8
  Uname: Linux 2.6.38-11-generic x86_64
  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  Date: Sun Oct 16 12:47:07 2011
  ProcEnviron:
   PATH=(custom, user)
   SHELL=/bin/bash
  SourcePackage: banshee
  UpgradeStatus: Upgraded to oneiric on 2011-10-14 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/banshee/+bug/875672/+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 600631] Re: Password does not unlock screen

2015-07-28 Thread Artem Nikulkov
Still happening from time to time for me as well.

This is the cure - http://superuser.com/questions/460075/why-does-
xscreensaver-not-allow-me-to-enter-my-password

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

Title:
  Password does not unlock screen

Status in gnome-screensaver package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: gnome-screensaver

  On some machines I have 10.40 installed on gnome-screensaver does not
  unlock screen with the correct password. With switch user I can go to
  login screen and use that very same password to go back to the Gnome
  session.

  I can reproduce this, every time I hit Control+Alt+L screen locks, and
  password does not unlock it. Workaround is to switch user and login
  back to the account with the locked session.

  taleman@myrsky:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 10.04 LTS
  Release:  10.04
  Codename: lucid

  taleman@myrsky:~$ apt-cache policy gnome-screensaver
  gnome-screensaver:
Asennettu: 2.30.0-0ubuntu2
Ehdokas: 2.30.0-0ubuntu2
Versiotaulukko:
   *** 2.30.0-0ubuntu2 0
  500 http://fi.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages
  100 /var/lib/dpkg/status
   2.30.0-0ubuntu1 0
  500 http://fi.archive.ubuntu.com/ubuntu/ lucid/main Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: gnome-screensaver 2.30.0-0ubuntu2
  ProcVersionSignature: Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5
  Uname: Linux 2.6.32-23-generic i686
  NonfreeKernelModules: nvidia
  Architecture: i386
  Date: Thu Jul  1 16:19:01 2010
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429)
  ProcEnviron:
   LANG=fi_FI.utf8
   SHELL=/bin/bash
  SourcePackage: gnome-screensaver
  WindowManager: gnome-wm

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/600631/+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 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.

2015-05-27 Thread Artem
The same at Lubuntu 15.04 vivid , all updates 05.27.2015

-- 
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:
  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-settings-daemon source package in Saucy:
  Won't Fix
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:
  [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_dEJrX2NRYlpLWWVzSWxsVXU4ck9HYVEusp=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=set
   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 1352975] Re: GUI symbol for Wi-fi in 14.10 shows not connected even when connected

2014-12-13 Thread Artem
The same for me - question mark instead of connection strength.
Ubuntu 14.10, GNOME Shell 3.12.2, asus ux303ln.
iwlist scan shows the strength.

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

Title:
  GUI symbol for Wi-fi in 14.10 shows not connected even when connected

Status in One Hundred Papercuts:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed
Status in wifi-radar package in Ubuntu:
  Invalid

Bug description:
  Using Ubuntu 14.10 alpha 2 with all updates. Clean install.
  Network manager 0.9.8.8-0ubuntu23
  Wifi-card: Intel Wireless 7260 (Rev 73)

  The Wi-fi symbol in the top right corner does not indicate that it is
  connected to Wi-fi even when it is connected. (It shows a question
  mark instead)

  Expected behavior is that it would show signal strength, or at the
  very least make it grey and remove the question mark.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: network-manager 0.9.8.8-0ubuntu23
  ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
  Uname: Linux 3.16.0-6-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.5-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Aug  5 17:42:57 2014
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-08-05 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 Utopic Unicorn - Alpha amd64 
(20140730)
  IpRoute:
   default via 192.168.0.1 dev wlan0  proto static 
   192.168.0.0/24 dev wlan0  proto kernel  scope link  src 192.168.0.110  
metric 9
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   Wired connection 18b6987c1-3f15-4b41-be88-ea9f5ae9eff6   
802-3-ethernet1407252000   ti. 05. aug. 2014 kl. 17.20 +0200  yes   
no /org/freedesktop/NetworkManager/Settings/1
   Diskokatt 5Ghz6a2433b7-9e20-4c4a-9c9d-455fee3505ef   
802-11-wireless   1407253201   ti. 05. aug. 2014 kl. 17.40 +0200  yes   
no /org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/1  
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1352975/+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 1381530] [NEW] the system crashes and restarts.

2014-10-15 Thread Artem
Public bug reported:

the system crashes and restarts.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8
ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
Uname: Linux 3.13.0-37-generic i686
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.5
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: Wed Oct 15 20:29:41 2014
DistUpgraded: 2014-05-05 22:15:46,699 DEBUG enabling apt cron job
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GraphicsCard:
 Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000]
 NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA 
controller])
   Subsystem: Gigabyte Technology Co., Ltd Device [1458:3530]
InstallationDate: Installed on 2014-02-01 (255 days ago)
InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1)
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic 
root=UUID=b0cad534-93c5-43ff-afd9-ad7cb8e505f4 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to trusty on 2014-05-05 (162 days ago)
dmi.bios.date: 08/23/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F2
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H77N-WIFI
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd08/23/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH77N-WIFI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
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.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.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Wed Oct 15 20:04:24 2014
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputVideo BusKEYBOARD, id 7
 inputPower Button KEYBOARD, id 8
 inputGenius NetScroll + Traveler MOUSE, id 9
 inputAT Translated Set 2 keyboard KEYBOARD, id 10
xserver.errors:
 Failed to load module nvidia (module does not exist, 0)
 Failed to load module nvidia (module does not exist, 0)
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.15.1-0ubuntu2.1
xserver.video_driver: nouveau

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

Title:
  the system crashes and restarts.

Status in “xorg” package in Ubuntu:
  New

Bug description:
  the system crashes and restarts.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.5
  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: Wed Oct 15 20:29:41 2014
  DistUpgraded: 2014-05-05 22:15:46,699 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000]
   NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA 
controller])
 Subsystem: Gigabyte Technology Co., Ltd Device [1458:3530]
  InstallationDate: Installed on 2014-02-01 (255 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic 

[Desktop-packages] [Bug 1357922] Re: active shadow is visible underneath inactive shadow on inactive windows

2014-08-17 Thread Artem Gabrielyan
** Attachment added: in this picture traces of active shadow are visible on 
entire border
   
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1357922/+attachment/4179810/+files/Untitled.png

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

Title:
  active shadow is visible underneath inactive shadow on inactive
  windows

Status in “compiz” package in Ubuntu:
  New

Bug description:
  I have shadows enabled both for active and inactive windows. Both of
  white colour; active is 16 in radius, inactive is 8. There is a bug in
  drawing inactive shadow on inactive window, because traces of active
  shadow are still visible from underbeath the inactive shadow.

  how to reproduce:
  - open a window (regular window with borders and shadows enabled)
  - click outside the window (for example, on desktop)
  - the window becomes inactive, its border becomes inactive, inactive shadow 
is displayed, but traces of active shadow are still visible

  Active shadow (or its traces) should not be visible on inactive
  windows

  It doesn't happen all the time. Sometimes inactive window and its
  shadows are displayed correctly, sometimes shadows are correctly
  displayed only on a part of inactive window's border, as shown in
  attached image.

  $ lsb_release -rd
  Description:  Linux Mint 17 Qiana
  Release:  17

  $ apt-cache policy compiz
  compiz:
Installed: 1:0.9.11.2+14.04.20140714-0ubuntu1
Candidate: 1:0.9.11.2+14.04.20140714-0ubuntu1
Version table:
   *** 1:0.9.11.2+14.04.20140714-0ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:0.9.11+14.04.20140409-0ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1357922/+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 1357922] [NEW] active shadow is visible underneath inactive shadow on inactive windows

2014-08-17 Thread Artem Gabrielyan
Public bug reported:

I have shadows enabled both for active and inactive windows. Both of
white colour; active is 16 in radius, inactive is 8. There is a bug in
drawing inactive shadow on inactive window, because traces of active
shadow are still visible from underbeath the inactive shadow.

how to reproduce:
- open a window (regular window with borders and shadows enabled)
- click outside the window (for example, on desktop)
- the window becomes inactive, its border becomes inactive, inactive shadow is 
displayed, but traces of active shadow are still visible

Active shadow (or its traces) should not be visible on inactive windows

It doesn't happen all the time. Sometimes inactive window and its
shadows are displayed correctly, sometimes shadows are correctly
displayed only on a part of inactive window's border, as shown in
attached image.

$ lsb_release -rd
Description:Linux Mint 17 Qiana
Release:17

$ apt-cache policy compiz
compiz:
  Installed: 1:0.9.11.2+14.04.20140714-0ubuntu1
  Candidate: 1:0.9.11.2+14.04.20140714-0ubuntu1
  Version table:
 *** 1:0.9.11.2+14.04.20140714-0ubuntu1 0
500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
100 /var/lib/dpkg/status
 1:0.9.11+14.04.20140409-0ubuntu1 0
500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

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

** Attachment added: Untitled2.png
   
https://bugs.launchpad.net/bugs/1357922/+attachment/4179809/+files/Untitled2.png

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

Title:
  active shadow is visible underneath inactive shadow on inactive
  windows

Status in “compiz” package in Ubuntu:
  New

Bug description:
  I have shadows enabled both for active and inactive windows. Both of
  white colour; active is 16 in radius, inactive is 8. There is a bug in
  drawing inactive shadow on inactive window, because traces of active
  shadow are still visible from underbeath the inactive shadow.

  how to reproduce:
  - open a window (regular window with borders and shadows enabled)
  - click outside the window (for example, on desktop)
  - the window becomes inactive, its border becomes inactive, inactive shadow 
is displayed, but traces of active shadow are still visible

  Active shadow (or its traces) should not be visible on inactive
  windows

  It doesn't happen all the time. Sometimes inactive window and its
  shadows are displayed correctly, sometimes shadows are correctly
  displayed only on a part of inactive window's border, as shown in
  attached image.

  $ lsb_release -rd
  Description:  Linux Mint 17 Qiana
  Release:  17

  $ apt-cache policy compiz
  compiz:
Installed: 1:0.9.11.2+14.04.20140714-0ubuntu1
Candidate: 1:0.9.11.2+14.04.20140714-0ubuntu1
Version table:
   *** 1:0.9.11.2+14.04.20140714-0ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:0.9.11+14.04.20140409-0ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

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

2014-05-23 Thread Artem Nikulkov
*** This bug is a duplicate of bug 1219407 ***
https://bugs.launchpad.net/bugs/1219407

Running Ubuntu Studio 14.04 - Trusty with Skype Version 4.2.0.13 and still 
experience the hellish buzz when skype plays notification sounds. Hoping for a 
permanent fix.
(Thanks for the script Reuben T. - you da man!)

-- 
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:
  Invalid
Status in “skype” package in Ubuntu:
  Fix Released

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 405294] Re: a2dp skips terribly

2014-04-28 Thread Artem Sheremet
Having the same issue here.

Linux 3.14.1 (from Arch Linux)
BlueZ 5.17

Jabra HALO2 Headset is being used.

A skip is accompanied by the following syslog messages (via systemd):

Apr 28 13:36:07 pulseaudio[15909]: [bluetooth] module-bluez5-device.c: Skipping 
2345806 us (= 413800 bytes) in audio stream
Apr 28 13:36:14 pulseaudio[15909]: [bluetooth] module-bluez5-device.c: Skipping 
2148930 us (= 379068 bytes) in audio stream
Apr 28 13:36:17 pulseaudio[15909]: [bluetooth] module-bluez5-device.c: Skipping 
2336913 us (= 412228 bytes) in audio stream

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

Title:
  a2dp skips terribly

Status in PulseAudio sound server:
  New
Status in “bluez” package in Ubuntu:
  Confirmed
Status in “pulseaudio” package in Ubuntu:
  Confirmed

Bug description:
  As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped
  working properly. It was working fine in Jaunty.

  My headphones are detected and configured by pulse, but the audio
  skips as if it's spending half of each second paused. Music is
  buffered so that after I click stop on rhythmbox (or whatever--it
  happens with whatever player I use) the audio continues until it's
  caught up.

  syslog is full of the following lines:
  Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal 
latency to 1.00 ms
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
15128 us (= 2668 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
36586 us (= 6452 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
35593 us (= 6276 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
36597 us (= 6452 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
32601 us (= 5748 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
32589 us (= 5748 bytes) in audio stream

  This is with
  bluez 4.45-0ubuntu4
  pulseaudio1:0.9.15-4ubuntu2 0

  pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev
  didn't help.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/405294/+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 1304404] Re: The inability to create a connection through Huawei E3531

2014-04-10 Thread Artem
Confirm, without installing software from zero cd network-manager
doesn't see the device Huawei E3531

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

Title:
  The inability to create a connection through Huawei E3531

Status in “network-manager” package in Ubuntu:
  Confirmed

Bug description:
  If you create access to the Internet using usb modem ZTE MF667 then
  the network periodically breaks. Usb Modem Huawei E3531 network-
  manager doesn't see, so you cannot create any connection.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: network-manager 0.9.8.8-0ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
  Uname: Linux 3.13.0-23-generic x86_64
  ApportVersion: 2.14.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Apr  8 16:49:01 2014
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-04-06 (2 days ago)
  InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140405)
  IpRoute:
   default via 10.64.64.64 dev ppp0  proto static 
   10.64.64.64 dev ppp0  proto kernel  scope link  src 10.39.225.164
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   ** (process:23293): WARNING **: Could not create object for 
/org/freedesktop/NetworkManager/Settings/2: uid 1000 has no permission to 
perform this operation
   
   ** (process:23293): WARNING **: handle_property_changed: failed to update 
property 'available-connections' of object type NMDeviceModem.
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
disabled   enabled enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1304404/+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 1280947] Re: Evince freezes Unity on drag to full window

2014-02-17 Thread Artem Korzhenevskiy
Possible duplicate of https://bugs.launchpad.net/compiz/+bug/1244754

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

Title:
  Evince freezes Unity on drag to full window

Status in “evince” package in Ubuntu:
  Confirmed

Bug description:
  Dragging evince from half-side to full window causes a complete freeze
  of Unity.

  Try out:
  1) Open a PDF file
  2) Drag the top bar to the right edge of the screen: the window resizes to 
cover the right half of the screen
  3) Quickly drag the top bar to the top edge of the screen and release: Unity 
will freeze while resizing evince.

  Killing Evince after passing to a console with CTR+ALT+F1 does not
  resolve the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: evince 3.10.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3
  Uname: Linux 3.11.0-17-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Sun Feb 16 20:25:18 2014
  ExecutablePath: /usr/bin/evince
  InstallationDate: Installed on 2013-10-20 (120 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MarkForUpload: True
  SourcePackage: evince
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1280947/+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 1265065] Re: Desktop freeze while drag-maximizing window

2014-02-17 Thread Artem Korzhenevskiy
*** This bug is a duplicate of bug 1244754 ***
https://bugs.launchpad.net/bugs/1244754

** This bug has been marked a duplicate of bug 1244754
   [regression] compiz freezes when dragging a window to the top bar after 
being semi-maximized

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

Title:
  Desktop freeze while drag-maximizing window

Status in “xorg” package in Ubuntu:
  Incomplete

Bug description:
  It has happened today twice at 22:23 and 22:54. I laft click with
  mouse on firefox titlebar and try to drag it up against taskbar to
  make FF windo to maximize. I see this shadow/animation of window about
  to extend its borders and desktop freezes. I do not remember if mouse
  still moves. I go to another console Ctrl+Alt+1, log in, and execute
  pkill -U username that brings me back to logon screen.

  Ubuntu 13.10 64-bit

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: xorg 1:7.7+1ubuntu6
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.12.5-0ubuntu2.2
  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: Mon Dec 30 22:32:14 2013
  DistUpgraded: Fresh install
  DistroCodename: saucy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Once a week
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: I don't know
  GraphicsCard:
   NVIDIA Corporation GF104 [GeForce GTX 460] [10de:0e22] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Device [1458:350c]
  InstallationDate: Installed on 2013-11-30 (30 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MachineType: Gigabyte Technology Co., Ltd. Z68X-UD3-B3
  MarkForUpload: True
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic 
root=UUID=9ee8cef8-09ae-4ab5-8422-7392354e9e26 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2011
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F1
  dmi.board.name: Z68X-UD3-B3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd04/15/2011:svnGigabyteTechnologyCo.,Ltd.:pnZ68X-UD3-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnZ68X-UD3-B3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: Z68X-UD3-B3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.46-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1
  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-0ubuntu10
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.9-2ubuntu1
  xserver.bootTime: Mon Dec 30 11:53:22 2013
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputLogitech USB-PS/2 Optical Mouse MOUSE, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
   inputWC060 Series HD Webcam KEYBOARD, id 10
  xserver.errors:
   Failed to load module nvidia (module does not exist, 0)
   Failed to load module nvidia (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.14.5-1ubuntu2~saucy1
  xserver.video_driver: nouveau

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1265065/+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 1268264] [NEW] Review submission silently fails

2014-01-11 Thread Artem V L
Public bug reported:

Review submission fails without any error description

Environment:
Description:Ubuntu 12.04.4 LTS (x64)
Release:12.04
Codename:   precise
Linux XXX 3.2.0-57-generic #87-Ubuntu SMP Tue Nov 12 21:35:10 UTC 2013 x86_64 
x86_64 x86_64 GNU/Linux

Note: I installed the app from it's latest non-default apt:
https://launchpad.net/~emelfm2/+archive/release instead of the default
package in the Software center, may be this caused the review fail, but
user should be able submit apps review for the latest versions also.

** Affects: software-center (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: fails review submission

** Attachment added: Review submission silently failed
   
https://bugs.launchpad.net/bugs/1268264/+attachment/3946670/+files/UbuntuAppReviewFail.png

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

Title:
  Review submission silently fails

Status in “software-center” package in Ubuntu:
  New

Bug description:
  Review submission fails without any error description

  Environment:
  Description:  Ubuntu 12.04.4 LTS (x64)
  Release:  12.04
  Codename: precise
  Linux XXX 3.2.0-57-generic #87-Ubuntu SMP Tue Nov 12 21:35:10 UTC 2013 x86_64 
x86_64 x86_64 GNU/Linux

  Note: I installed the app from it's latest non-default apt:
  https://launchpad.net/~emelfm2/+archive/release instead of the default
  package in the Software center, may be this caused the review fail,
  but user should be able submit apps review for the latest versions
  also.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1268264/+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 1254438] [NEW] package gdm 2.30.2.is.2.30.0-0ubuntu5.2 failed to install/upgrade: подпроцесс установлен сценарий pre-removal возвратил код ошибки 10

2013-11-24 Thread artem
Public bug reported:

install pasket

ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: gdm 2.30.2.is.2.30.0-0ubuntu5.2
ProcVersionSignature: Ubuntu 2.6.32-45.104-generic-pae 2.6.32.60+drm33.26
Uname: Linux 2.6.32-45-generic-pae i686
NonfreeKernelModules: fglrx
Architecture: i386
Date: Sun Nov 24 17:10:30 2013
ErrorMessage: подпроцесс установлен сценарий pre-removal возвратил код ошибки 10
InstallationMedia: Ubuntu-Server 10.04 LTS Lucid Lynx - Release i386 
(20100427)
SourcePackage: gdm
Title: package gdm 2.30.2.is.2.30.0-0ubuntu5.2 failed to install/upgrade: 
подпроцесс установлен сценарий pre-removal возвратил код ошибки 10

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


** Tags: apport-package i386 lucid

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

Title:
  package gdm 2.30.2.is.2.30.0-0ubuntu5.2 failed to install/upgrade:
  подпроцесс установлен сценарий pre-removal возвратил код ошибки 10

Status in “gdm” package in Ubuntu:
  New

Bug description:
  install pasket

  ProblemType: Package
  DistroRelease: Ubuntu 10.04
  Package: gdm 2.30.2.is.2.30.0-0ubuntu5.2
  ProcVersionSignature: Ubuntu 2.6.32-45.104-generic-pae 2.6.32.60+drm33.26
  Uname: Linux 2.6.32-45-generic-pae i686
  NonfreeKernelModules: fglrx
  Architecture: i386
  Date: Sun Nov 24 17:10:30 2013
  ErrorMessage: подпроцесс установлен сценарий pre-removal возвратил код ошибки 
10
  InstallationMedia: Ubuntu-Server 10.04 LTS Lucid Lynx - Release i386 
(20100427)
  SourcePackage: gdm
  Title: package gdm 2.30.2.is.2.30.0-0ubuntu5.2 failed to install/upgrade: 
подпроцесс установлен сценарий pre-removal возвратил код ошибки 10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1254438/+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 1241929] Re: Lightdm Ubuntu 13.10 fails to start intermittently after cold boot or from shutdown/reboot.

2013-11-17 Thread Artem Vlasov
Hi everyone!
I've faced this annoying gleech too.
After every restart/powerup my laptop I see normal greeter. After login to my 
account I see just wallpaper or black screen with mouse pointer on it. Pointer 
looks correctly, and I can move it without a problem.
But I see no Unity panel on the left side, nor on the top of screen. Then I 
switch to tty1 by Ctrl+Alt+F1, login again in terminal and do sudo service 
lightdm restart. It makes greeter shown again, then I login normally and see 
Unity launcher and panel.
I can send any log if needed.

P.S. My laptop is Lenovo g505s, based on AMD APU A10, so I have to use
fglrx drivers from AMD official site.

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

Title:
  Lightdm Ubuntu 13.10 fails to start intermittently after cold boot
  or from shutdown/reboot.

Status in “lightdm” package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 13.10 official release.
  After a clean install of Ubuntu 13.10 I shut down for the night. Upon boot 
the next morning I found a blank screen with no greeter.
  I rebooted. This time I saw a wallpaper but no menu's.
  I did sudo service lightdm restart and it worked.
  But now after each shutdown or even a reboot I have to manually restart 
lightdm or might get lucky with lightdm greeter... I have added sleep 2 to the 
lightdm.conf.

  Additional info running on a hybrid disc with btrfs  /, /home ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1241929/+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 1251802] [NEW] fglrx-updates 2:12.104-0ubuntu0.0.1: fglrx-updates kernel module failed to build

2013-11-15 Thread Artem
Public bug reported:

apt-get install linux-headers-generic-lts-saucy

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: fglrx-updates 2:12.104-0ubuntu0.0.1
ProcVersionSignature: Ubuntu 3.8.0-33.48~precise1-generic 3.8.13.11
Uname: Linux 3.8.0-33-generic x86_64
NonfreeKernelModules: fglrx wl
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
DKMSKernelVersion: 3.11.0-13-generic
Date: Sat Nov 16 07:03:58 2013
InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release amd64 
(20130820.1)
MarkForUpload: True
PackageVersion: 2:12.104-0ubuntu0.0.1
SourcePackage: fglrx-installer-updates
Title: fglrx-updates 2:12.104-0ubuntu0.0.1: fglrx-updates kernel module failed 
to build
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: fglrx-installer-updates (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package precise

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

Title:
  fglrx-updates 2:12.104-0ubuntu0.0.1: fglrx-updates kernel module
  failed to build

Status in “fglrx-installer-updates” package in Ubuntu:
  New

Bug description:
  apt-get install linux-headers-generic-lts-saucy

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: fglrx-updates 2:12.104-0ubuntu0.0.1
  ProcVersionSignature: Ubuntu 3.8.0-33.48~precise1-generic 3.8.13.11
  Uname: Linux 3.8.0-33-generic x86_64
  NonfreeKernelModules: fglrx wl
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  DKMSKernelVersion: 3.11.0-13-generic
  Date: Sat Nov 16 07:03:58 2013
  InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release amd64 
(20130820.1)
  MarkForUpload: True
  PackageVersion: 2:12.104-0ubuntu0.0.1
  SourcePackage: fglrx-installer-updates
  Title: fglrx-updates 2:12.104-0ubuntu0.0.1: fglrx-updates 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/fglrx-installer-updates/+bug/1251802/+subscriptions

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


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

2013-11-09 Thread Artem M. Pelenitsyn
The workaround by Andreas (#52) seems to be broken (for me, at least) by
the last update of gnome-control-center - 1:3.6.3-0ubuntu45.1 — which
partially fixes 1218322 bug concerning hotkeys for layout switching (
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-
daemon/+bug/1218322 ). It worked before the update, but now switching to
Russian (kbd (m17)) doesn't take effect at all (the layout stays
latin).

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

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

Status in IBus:
  New
Status in Indicator keyboard:
  Fix Released
Status in Unity:
  Invalid
Status in “gnome-settings-daemon” package in Ubuntu:
  Triaged
Status in “indicator-keyboard” package in Ubuntu:
  Fix Released

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

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

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

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

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

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


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

2013-10-27 Thread Artem Popov
Switching layouts in gnome-screensaver dialog doesn't work. Bug report:

https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1244548

-- 
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 One Hundred Papercuts:
  Invalid
Status in Indicator keyboard:
  Invalid
Status in Ubuntu GNOME:
  Fix Committed
Status in “gnome-control-center” package in Ubuntu:
  Invalid
Status in “gnome-settings-daemon” package in Ubuntu:
  Fix Committed
Status in “indicator-keyboard” package in Ubuntu:
  Invalid
Status in “gnome-control-center” source package in Saucy:
  Invalid
Status in “gnome-settings-daemon” source package in Saucy:
  Fix Committed
Status in “indicator-keyboard” source package in Saucy:
  Fix Released

Bug description:
  A PPA which should provide some relief for this issue is available at
  https://launchpad.net/~attente/+archive/1218322. There still remain
  issues regarding keyboard shortcuts though. To install:

  sudo add-apt-repository ppa:attente/1218322
  sudo apt-get update
  sudo apt-get upgrade

  === 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.

  --

  Can't set keyboard layout change to ctrl+shift, Caps Lock, alt+shift
  etc. Shift, CapsLock keys are just ignored in settings. Also the
  default shortcut was set to Super+Space that is inconveniently,
  because Dash is opening when you swich your keyboard layout.

  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=set
   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/hundredpapercuts/+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 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.

2013-10-19 Thread Artem Popov
On a clean Saucy install (Russian layout selected during setup) with the
attente PPA, I have the same behaviour as Valery Kozlov described in
comment #122. No matter if the switch hotkeys are enabled or disabled in
the GUI, I can still switch layouts with ALT+SHIFT.

Strangely, this layout configuration comes from keyboard-configuration
package. This is the setxkbmap output on a clean system:

~$ setxkbmap -print -verbose
Trying to build keymap using the following components:
keycodes:   evdev+aliases(qwerty)
types:  complete
compat: complete+ledscroll(group_lock)
symbols:pc+ru+us:2+inet(evdev)+group(alt_shift_toggle)
geometry:   pc(pc105)
xkb_keymap {
xkb_keycodes  { include evdev+aliases(qwerty) };
xkb_types { include complete  };
xkb_compat{ include complete+ledscroll(group_lock)};
xkb_symbols   { include 
pc+ru+us:2+inet(evdev)+group(alt_shift_toggle)};
xkb_geometry  { include pc(pc105) };
};

Running 'sudo dpkg-reconfigure keyboard-configuration' affects the
setxkbmap output later, so the console keyboard config clearly makes its
way into X (conflicting with the ibus configuration).

-- 
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 Ubuntu:
  Confirmed
Status in “gnome-control-center” package in Ubuntu:
  Confirmed
Status in “gnome-settings-daemon” package in Ubuntu:
  Confirmed
Status in “indicator-keyboard” package in Ubuntu:
  Confirmed

Bug description:
  Can't set keyboard layout change to ctrl+shift, Caps Lock, alt+shift
  etc. Shift, CapsLock keys are just ignored in settings. Also the
  default shortcut was set to Super+Space that is inconveniently,
  because Dash is opening when you swich your keyboard layout.

  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=set
   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/ubuntu/+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 486380] Re: gnome-system-log assert failure: gnome-system-log:ERROR:logview-log.c:910:logview_log_get_uri: assertion failed: (LOGVIEW_IS_LOG (log))

2013-10-01 Thread Artem Kuskis
This bug stay in Centos 6.4 and Ubuntu 12.10 ... found this bug
yesterday, fix it on my home pc, and today found that Cosimo Cecchi did
it in April but current versions of gnome-system-log are old.

Bug: When you press Ctrl+W and there is no log file selected in the
right list widget...

Patch info : https://git.gnome.org/browse/gnome-system-log/commit/src
/logview-manager.c?id=ad9153b8bcd8a2556d7a1f5fcca890680c4677de

Patch file:

From ad9153b8bcd8a2556d7a1f5fcca890680c4677de Mon Sep 17 00:00:00 2001
From: Cosimo Cecchi cosi...@gnome.org
Date: Thu, 11 Apr 2013 21:25:20 +
Subject: manager: add some safety NULL-checks

https://bugzilla.gnome.org/show_bug.cgi?id=697790
---
(limited to 'src/logview-manager.c')

diff --git a/src/logview-manager.c b/src/logview-manager.c
index 29dcba9..b948bfa 100644
--- a/src/logview-manager.c
+++ b/src/logview-manager.c
@@ -398,6 +398,10 @@ logview_manager_close_active_log (LogviewManager *manager)
   g_assert (LOGVIEW_IS_MANAGER (manager));
 
   active_log = manager-priv-active_log;
+  if (active_log == NULL) {
+return;
+  }
+
   log_uri = logview_log_get_uri (active_log);
   file = logview_log_get_gfile (active_log);
 
--
cgit v0.9.2

** Bug watch added: GNOME Bug Tracker #697790
   https://bugzilla.gnome.org/show_bug.cgi?id=697790

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

Title:
  gnome-system-log assert failure: gnome-system-log:ERROR:logview-
  log.c:910:logview_log_get_uri: assertion failed: (LOGVIEW_IS_LOG
  (log))

Status in gnome-utils - GNOME Desktop Utilities:
  New
Status in “gnome-utils” package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: gnome-utils

  to reproduce crash:
  close all files in gnome-system-log fast one by one

  ProblemType: Crash
  Architecture: amd64
  AssertionMessage: 
gnome-system-log:ERROR:logview-log.c:910:logview_log_get_uri: assertion failed: 
(LOGVIEW_IS_LOG (log))
  CrashCounter: 1
  Date: Sat Nov 21 18:23:10 2009
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/bin/gnome-system-log
  Package: gnome-utils 2.28.1-0ubuntu1
  ProcCmdline: gnome-system-log --sync
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=sv_SE.UTF-8
  ProcVersionSignature: Ubuntu 2.6.31-15.50-generic
  Signal: 6
  SourcePackage: gnome-utils
  StacktraceTop:
   *__GI_raise (sig=value optimized out)
   *__GI_abort () at abort.c:92
   g_assertion_message () from /lib/libglib-2.0.so.0
   g_assertion_message_expr ()
   ?? ()
  Title: gnome-system-log assert failure: 
gnome-system-log:ERROR:logview-log.c:910:logview_log_get_uri: assertion failed: 
(LOGVIEW_IS_LOG (log))
  Uname: Linux 2.6.31-15-generic x86_64
  UserGroups: adm admin audio cdrom dialout dip fax floppy fuse kvm libvirtd 
lpadmin netdev plugdev sambashare scanner tape vboxusers video

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-utils/+bug/486380/+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 486380] Re: gnome-system-log assert failure: gnome-system-log:ERROR:logview-log.c:910:logview_log_get_uri: assertion failed: (LOGVIEW_IS_LOG (log))

2013-10-01 Thread Artem Kuskis
PS: not right.. left widget with file names

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

Title:
  gnome-system-log assert failure: gnome-system-log:ERROR:logview-
  log.c:910:logview_log_get_uri: assertion failed: (LOGVIEW_IS_LOG
  (log))

Status in gnome-utils - GNOME Desktop Utilities:
  New
Status in “gnome-utils” package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: gnome-utils

  to reproduce crash:
  close all files in gnome-system-log fast one by one

  ProblemType: Crash
  Architecture: amd64
  AssertionMessage: 
gnome-system-log:ERROR:logview-log.c:910:logview_log_get_uri: assertion failed: 
(LOGVIEW_IS_LOG (log))
  CrashCounter: 1
  Date: Sat Nov 21 18:23:10 2009
  DistroRelease: Ubuntu 9.10
  ExecutablePath: /usr/bin/gnome-system-log
  Package: gnome-utils 2.28.1-0ubuntu1
  ProcCmdline: gnome-system-log --sync
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, user)
   LANG=sv_SE.UTF-8
  ProcVersionSignature: Ubuntu 2.6.31-15.50-generic
  Signal: 6
  SourcePackage: gnome-utils
  StacktraceTop:
   *__GI_raise (sig=value optimized out)
   *__GI_abort () at abort.c:92
   g_assertion_message () from /lib/libglib-2.0.so.0
   g_assertion_message_expr ()
   ?? ()
  Title: gnome-system-log assert failure: 
gnome-system-log:ERROR:logview-log.c:910:logview_log_get_uri: assertion failed: 
(LOGVIEW_IS_LOG (log))
  Uname: Linux 2.6.31-15-generic x86_64
  UserGroups: adm admin audio cdrom dialout dip fax floppy fuse kvm libvirtd 
lpadmin netdev plugdev sambashare scanner tape vboxusers video

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-utils/+bug/486380/+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 1131858] Re: file operations window hangs after completion of file transfer to FAT file system from ext4 file system

2013-05-03 Thread Artem Korzhenevskiy
Have similar problem - progress bar going fast from 0% to 100% and disappear, 
but then I cannot eject usb drive.
Using ubuntu 13.04, have same problem in 12.10.

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

Title:
  file operations window hangs after completion of file transfer to FAT
  file system from ext4 file system

Status in “nautilus” package in Ubuntu:
  Confirmed

Bug description:
  Using 12.04 and attempting to drag-and-drop a large file from my
  Downloads folder to a USB thumb drive, the File Operations window
  displays a full progress bar and the text 777.9 MB of 777.9 MB. This
  dialog box hangs for about five minutes, during which time I ran
  'ubuntu-bug nautilus' in the hopes that the problem details were
  captured.

  This bug seems identical to bug 612076 in 10.04 which was closed due
  to inactivity.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: nautilus 1:3.4.2-0ubuntu6
  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: Fri Feb 22 11:16:35 2013
  GsettingsChanges: org.gnome.nautilus.window-state geometry '1202x621+476+430'
  InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 
(20120822.4)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

2013-04-11 Thread T-artem
(In reply to comment #124)
 I wonder, bearing in mind the fact that Ubuntu has the patch for the
 problem, will Mir be the first Linux display server which implement this
 feature? :)

You've wandered far off.

Both Mir and Wayland have a completely different input architecture -
they simply don't have this problem from the very beginning.

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

Title:
  Keyboard layout change on hotkeys press instead of release and do not
  work well with shortcuts

Status in GNOME Control Center:
  Unknown
Status in X.Org X server:
  In Progress
Status in “control-center” package in Ubuntu:
  Invalid
Status in “xorg-server” package in Ubuntu:
  Fix Released

Bug description:
  This is a bug about shortcuts mapped to combinations which include
  each other.

  For example, if we have Ctrl+Shift (for keyboard layout) and Ctrl+Shift+N (to 
open a new terminal), then we are practically unable to use the second 
shortcut; this is what happens:
  Ctrl press  (nothing happens)
  Shift press (keyboard layout change)
  N (a simple N appears, since a shortcut has already fired)

  The expected behavior is to fire shortcuts on the release (not on
  press) of the special keys (ctrl,shift,alt, etc) which is also how
  Windows behave. This is a serious problem for bilingual layouts,
  typically using Alt+Shift or Ctrl+Shift for keyboard layout change.

  For users being affected by this problem, the easiest solution for now is to 
add this PPA in your repositories:
  https://launchpad.net/~oded-geek/+archive/xorg-patches

  Practical summary of this bug for ubuntu developers (since reading 120 
comments is impractical for most):
  This problem is a really old (since 2004) issue of the xkb part of xorg; the 
main discussion was made upstream in freedesktop-bugs #865. There has been a 
patch from Ilya Murav'jov for upstream (#55), and attached here (#61).
  Upstream xorg has refused to apply the patch, mainly because it explicitly 
contradicts the (xkb) spec  (#84, #91).
  This patch has been reported to work for many people without any problems, 
and there is also a PPA by Oded Arbel (#95) where he maintains a patched 
version of the ubuntu xorg.
  The proper resolution of this bug would be to apply this patch to the 
upstream xorg, or at minimum to the official ubuntu xorg package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/36812/+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 626321]

2013-04-02 Thread T-artem
A workaround/hack for this issue: http://michaelb.org/projects/fsgamer/
(FSGamer runs games in their own X server, which can improve the speed,
reduce annoying interruptions, and make switching between fullscreen
games and your desktop easy and reliable.)

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

Title:
  X.org server should keep track of and restore its initial (desktop)
  resolution and refresh rate

Status in Wine:
  Won't Fix
Status in X.Org X server:
  Confirmed
Status in “xorg-server” package in Ubuntu:
  Triaged

Bug description:
  Applications like games change desktop resolution (graphics mode) for
  their needs. Unfortunately when such applications crash then X.org
  server doesn't revert the resolution back to its initial mode.

To manage notifications about this bug go to:
https://bugs.launchpad.net/wine/+bug/626321/+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 1153976] [NEW] Low CRT refresh rate selected when higher is available

2013-03-12 Thread Artem Baguinski
Public bug reported:

My CRT monitor - ADI Systems 16 - is correctly recognized and the list
of supported resolutions in System Settings  Displays looks good (not
all resolutions are listed, but the one's I'm interested in are). At
higher resolutions the monitor only supports low refresh rate, so I
select a highest resolution where 85Hz rate is supported, but the actual
mode set is that resoltion at 60Hz. Here is the xrandr output:

$ xrandr
Screen 0: minimum 320 x 200, current 1366 x 1536, maximum 8192 x 8192
LVDS1 connected 1366x768+0+768 (normal left inverted right x axis y axis) 344mm 
x 194mm
...
VGA1 connected 1280x768+86+0 (normal left inverted right x axis y axis) 320mm x 
240mm
   1280x1024  60.0
   1280x960   60.0
   1280x800   74.9 59.8
   1152x864   75.0
   1280x768   84.8 74.9 59.9*
   1024x768   85.0 75.1 70.1 60.0 43.5
   800x60085.1 72.2 75.0 60.3 56.2
   848x48060.0
   640x48085.0 72.8 75.0 60.0 63.1
   720x40085.0
   640x40085.1
   640x35085.1
HDMI1 disconnected (normal left inverted right x axis y axis)
DP1 disconnected (normal left inverted right x axis y axis)

I want the OS to select 1280x768 @ 85Hz (or 84.8 as reported). I can
switch to this mode manually with this command:

$ xrandr --output VGA1 --mode 1280x768

after which the corresponding line of xrandr output changes to:

   1280x768   84.8*74.9 59.9

as well as the monitor itself reports that it has switched to 85Hz, and
I didn't even explicitly asked xrandr for it.

That should have happened automatically.

I've been away from desktop linux for couple of years and am not sure
anymore what is the actual package resposible for this and what other
information is useful for developers, but if pointed to the right
direction will supply whatever you need.

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

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

Title:
  Low CRT refresh rate selected when higher is available

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

Bug description:
  My CRT monitor - ADI Systems 16 - is correctly recognized and the
  list of supported resolutions in System Settings  Displays looks good
  (not all resolutions are listed, but the one's I'm interested in are).
  At higher resolutions the monitor only supports low refresh rate, so I
  select a highest resolution where 85Hz rate is supported, but the
  actual mode set is that resoltion at 60Hz. Here is the xrandr output:

  $ xrandr
  Screen 0: minimum 320 x 200, current 1366 x 1536, maximum 8192 x 8192
  LVDS1 connected 1366x768+0+768 (normal left inverted right x axis y axis) 
344mm x 194mm
  ...
  VGA1 connected 1280x768+86+0 (normal left inverted right x axis y axis) 320mm 
x 240mm
 1280x1024  60.0
 1280x960   60.0
 1280x800   74.9 59.8
 1152x864   75.0
 1280x768   84.8 74.9 59.9*
 1024x768   85.0 75.1 70.1 60.0 43.5
 800x60085.1 72.2 75.0 60.3 56.2
 848x48060.0
 640x48085.0 72.8 75.0 60.0 63.1
 720x40085.0
 640x40085.1
 640x35085.1
  HDMI1 disconnected (normal left inverted right x axis y axis)
  DP1 disconnected (normal left inverted right x axis y axis)

  I want the OS to select 1280x768 @ 85Hz (or 84.8 as reported). I can
  switch to this mode manually with this command:

  $ xrandr --output VGA1 --mode 1280x768

  after which the corresponding line of xrandr output changes to:

 1280x768   84.8*74.9 59.9

  as well as the monitor itself reports that it has switched to 85Hz,
  and I didn't even explicitly asked xrandr for it.

  That should have happened automatically.

  I've been away from desktop linux for couple of years and am not sure
  anymore what is the actual package resposible for this and what other
  information is useful for developers, but if pointed to the right
  direction will supply whatever you need.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1153976/+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 1037610] Re: xorg nvidia crashes, ubuntu 12.04 LTS 64 bit

2013-03-01 Thread Artem Badasyan
May I suggest: turn off onboard graphic from the BIOS. Then change the
quiet splash in grub to nomodeset. It resolved the issue with my
nvidia driver, otherwise I had unreadable screen on my desktop. Hope
that helps. Best...

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

Title:
  xorg nvidia crashes, ubuntu 12.04 LTS 64 bit

Status in “nvidia-graphics-drivers” package in Ubuntu:
  Confirmed

Bug description:
  Summary:

  I have used Ubuntu for many years, mostly as a server os. I also use
  it on a netbook. I recently installed Ubuntu on my desktop and well I
  am having a miserable experience.

  So to start. It does not matter what nvidia driver I use, the system
  is unstable. Sometimes it will crash after 5 minutes and sometimes
  after half a day, but it always crashes. Typically it goes to a black
  screen and does not recover. However, I can still ssh from a remote
  machine into the box.

  I have tried the nvidia-current driver/package from all repositories
  including the bleeding edge repository. I have tried the most up to
  date driver from the nvidia website, via manual install 304.37. All to
  no avail.

  This seems to occur, randomly no matter what I am doing. It has
  crashed while using firefox, minecraft, vlc, and sometimes sitting
  idle.

  Opinion/rant:

  Now I have to admit I am sick of this, it is a WELL documented issue,
  I am sure you know about it from all the other bug reports. Now Linus
  had a little fit ranting against nvidia and to be honest they both
  need to get it together. The thing is, is there anything ubuntu can do
  to help? A TON of ppl are having similar issues. Is there a fix? So
  basically this issue makes ubuntu completely unusable as a desktop
  environment at the current time.

  I just built this machine, was phenomenal under Windows 7. However, I
  have been slowly migrating my machines to linux, Ubuntu. What upsets
  me here is that I dumped the windows install and installed it in a
  virtual machine, which required a call to microsoft to reactivate the
  key. So if I decided to put windows back on this box I am sure another
  call will be necessary.

  Question:

  Should I just switch to an ATI video card? if so any suggestions? I
  like the HD 7xxx series, how is the 3d acceleratio support?

  Should I revert to an earlier version of ubuntu? The last version I
  used (and still have on a few machines) is 10.04 LTS.

  Also, where exactly does the issue lie here? In the kernel, in the
  nvidia driver, xserver, etc?

  When will there be a fix, from other bug reports and searches on the
  web, this has been an issue for a LONG time.

  I am thinking about just digging in and making this machine a gentoo
  box (having done gentoo on machines a few years ago) Is this problem
  occuring with gentoo? I see that it occurs with arch linux.

  Info:

  This is NOT an upgrade from one version to 12.04. This problem occurs
  whether I use unity or gnome. I have tried multiple times from a fresh
  install, with always the same outcome.

  Sane response:

  Thanks for you help in advance. Is there any addition information you
  need?

  (dmesg) This occurs no matter what driver I use.

  [   16.712884] Pid: 1368, comm: Xorg Tainted: P C O 3.2.0-23-generic 
#36-Ubuntu
  [   16.712885] Call Trace:
  [   16.712890]  [8106712f] warn_slowpath_common+0x7f/0xc0
  [   16.712892]  [8106718a] warn_slowpath_null+0x1a/0x20
  [   16.712893]  [81040f92] __ioremap_caller+0x312/0x390
  [   16.712944]  [a06b4d45] ? os_map_kernel_space+0x85/0xf0 [nvidia]
  [   16.712946]  [81041044] ioremap_cache+0x14/0x20
  [   16.712983]  [a06b4d45] os_map_kernel_space+0x85/0xf0 [nvidia]
  [   16.713023]  [a0680918] _nv014877rm+0x76/0x92 [nvidia]
  [   16.713056]  [a00afa1e] ? _nv009673rm+0x89/0x142 [nvidia]
  [   16.713089]  [a00afb8f] ? _nv014448rm+0xb8/0x102 [nvidia]
  [   16.713122]  [a00b0042] ? _nv014486rm+0x58/0x9e [nvidia]
  [   16.713155]  [a00abaa8] ? _nv014458rm+0xbe/0x2f0 [nvidia]
  [   16.713187]  [a00abd85] ? _nv014491rm+0xab/0x174 [nvidia]
  [   16.713219]  [a00abe9e] ? _nv014457rm+0x50/0x5d [nvidia]
  [   16.713252]  [a00b2072] ? _nv014432rm+0x82d/0x96b [nvidia]
  [   16.713292]  [a06907ef] ? _nv012658rm+0x174/0x573 [nvidia]
  [   16.713330]  [a069076d] ? _nv012658rm+0xf2/0x573 [nvidia]
  [   16.713373]  [a00fc261] ? _nv004021rm+0x1bb/0x19e9 [nvidia]
  [   16.713456]  [a0453ef9] ? _nv004046rm+0x8690/0xae8b [nvidia]
  [   16.713537]  [a04528bb] ? _nv004046rm+0x7052/0xae8b [nvidia]
  [   16.713567]  [a0084d0c] ? _nv009980rm+0x25/0x40 [nvidia]
  [   16.713606]  [a0690501] ? _nv014932rm+0x7c9/0x943 [nvidia]
  [   16.713645]  [a06914af] ? _nv001095rm+0x42a/0x6b4 

[Desktop-packages] [Bug 884035] Re: Unable to execute .NET programs compiled against the v2.0 runtime: Missing method System.Type::op_Inequality(Type, Type) in assembly /usr/lib/mono/2.0/mscorlib.dll

2013-02-16 Thread Artem Fedyuk
One of the reasons for this error: 
(Missing method System.Type::op_Inequality(Type,Type) in assembly- 
/usr/lib/mono/2.0/mscorlib.dll)
can be the presence of a SomeApplication.config file with saved user 
settings, the runtime version of which is wrong. For example, the prefix part 
of this file might look like this:

?xml version=1.0?
configuration
configSections
sectionGroup name=userSettings 
type=System.Configuration.UserSettingsGroup, System, Version=2.0.0.0, 
Culture=neutral, PublicKeyToken=b77a5c561934e089
section name=ConsTerm.Client.Properties.Settings 
type=System.Configuration.ClientSettingsSection, System, Version=2.0.0.0, 
Culture=neutral, PublicKeyToken=b77a5c561934e089 
allowExeDefinition=MachineToLocalUser requirePermission=false/
/sectionGroup
/configSections

You should recompile the program to version 4 (if you have the source
code) and remove the old version of SomeApplication.config

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

Title:
  Unable to execute .NET programs compiled against the v2.0 runtime:
  Missing method System.Type::op_Inequality(Type,Type) in assembly
  /usr/lib/mono/2.0/mscorlib.dll

Status in “gtk-sharp2” package in Ubuntu:
  Confirmed

Bug description:
  If you try to execute a .NET program not compiled against Mono 4.0
  (but compiled against Mono 2.0 instead), when you try to run it you
  get many exception messages relative to missing methods, such as
  Missing method System.Type::op_Inequality(Type,Type) in assembly
  /usr/lib/mono/2.0/mscorlib.dll.

  More details here:
  http://orangesquash.org.uk/~laney/blog/posts/2011/10/mono-gotcha/

  Temporary workaround:
  Run the application passing the --runtime=v4.0 switch to Mono, like this:
  mono --runtime=v4.0 /usr/lib/myapp/myapp.exe
  (where /usr/lib/myapp/myapp.exe is the complete path to the program you are 
trying to execute) to force Mono to use the v4.0 runtime.
  -
  This is a sample scenario (running WepCrack):
  luis@ubuntu:~$ sudo su
  [sudo] password for luis:
  root@ubuntu:/home/luis# cd Escritorio/WepCrack
  root@ubuntu:/home/luis/Escritorio/WepCrack# sudo ./wepcrack
  Missing method System.Type::op_Inequality(Type,Type) in assembly 
/usr/lib/mono/2.0/mscorlib.dll, referenced in assembly 
/usr/lib/mono/gac/gtk-sharp/2.12.0.0__35e10195dab3c99f/gtk-sharp.dll

  Unhandled Exception: System.MissingMethodException: Method not found: 
'System.Type.op_Inequality'.
    at WepCrackGtk.MainWindow..ctor () [0x0] in filename unknown:0
    at GWepCrackGui.MainClass.Main (System.String[] args) [0x0] in 
filename unknown:0
  [ERROR] FATAL UNHANDLED EXCEPTION: System.MissingMethodException: Method not 
found: 'System.Type.op_Inequality'.
    at WepCrackGtk.MainWindow..ctor () [0x0] in filename unknown:0
    at GWepCrackGui.MainClass.Main (System.String[] args) [0x0] in 
filename unknown:0
  root@ubuntu:/home/luis/Escritorio/WepCrack#

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-terminal 3.0.1-0ubuntu3
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic i686
  ApportVersion: 1.23-0ubuntu3
  Architecture: i386
  Date: Sun Oct 30 21:28:04 2011
  ExecutablePath: /usr/bin/gnome-terminal
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to oneiric on 2011-10-24 (6 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk-sharp2/+bug/884035/+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 1110187] Re: libffado FTBFS in raring (powerpc)

2013-01-30 Thread Artem Popov
A debdiff against raring-proposed.

** Patch added: libffado_2.1.0+svn2240-1ubuntu2.debdiff
   
https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1110187/+attachment/3507231/+files/libffado_2.1.0%2Bsvn2240-1ubuntu2.debdiff

** Description changed:

  libffado fails to build from source in raring, missing inclusion of
- unistd.h.
+ ByteSwap.h.
  
  https://launchpad.net/ubuntu/+archive/test-
  rebuild-20120922/+build/3826942
  
  Affects upstream and Debian, patch forwared upstream.

** Description changed:

  libffado fails to build from source in raring, missing inclusion of
  ByteSwap.h.
  
- https://launchpad.net/ubuntu/+archive/test-
- rebuild-20120922/+build/3826942
+ 
https://launchpad.net/ubuntu/+source/libffado/2.1.0+svn2240-1ubuntu1/+build/4252403
  
  Affects upstream and Debian, patch forwared upstream.

** Description changed:

  libffado fails to build from source in raring, missing inclusion of
  ByteSwap.h.
  
  
https://launchpad.net/ubuntu/+source/libffado/2.1.0+svn2240-1ubuntu1/+build/4252403
  
- Affects upstream and Debian, patch forwared upstream.
+ Affects upstream and Debian, patch forwarded upstream.

** Bug watch added: FFado Bug Tracker #366
   http://subversion.ffado.org/ticket/366

** Also affects: ffado via
   http://subversion.ffado.org/ticket/366
   Importance: Unknown
   Status: Unknown

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

Title:
  libffado FTBFS in raring (powerpc)

Status in FFADO - Free Firewire Audio Drivers:
  Unknown
Status in “libffado” package in Ubuntu:
  New

Bug description:
  libffado fails to build from source in raring, missing inclusion of
  ByteSwap.h.

  
https://launchpad.net/ubuntu/+source/libffado/2.1.0+svn2240-1ubuntu1/+build/4252403

  Affects upstream and Debian, patch forwarded upstream.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ffado/+bug/1110187/+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 1110187] [NEW] libffado FTBFS in raring (powerpc)

2013-01-30 Thread Artem Popov
Public bug reported:

libffado fails to build from source in raring, missing inclusion of
ByteSwap.h.

https://launchpad.net/ubuntu/+source/libffado/2.1.0+svn2240-1ubuntu1/+build/4252403

Affects upstream and Debian, patch forwarded upstream.

** Affects: ffado
 Importance: Unknown
 Status: Unknown

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

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

Title:
  libffado FTBFS in raring (powerpc)

Status in FFADO - Free Firewire Audio Drivers:
  Unknown
Status in “libffado” package in Ubuntu:
  New

Bug description:
  libffado fails to build from source in raring, missing inclusion of
  ByteSwap.h.

  
https://launchpad.net/ubuntu/+source/libffado/2.1.0+svn2240-1ubuntu1/+build/4252403

  Affects upstream and Debian, patch forwarded upstream.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ffado/+bug/1110187/+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 1110187] Re: libffado FTBFS in raring (powerpc)

2013-01-30 Thread Artem Popov
** Branch linked: lp:~artfwo/ubuntu/raring/libffado/ftbfs-1110187

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

Title:
  libffado FTBFS in raring (powerpc)

Status in FFADO - Free Firewire Audio Drivers:
  Unknown
Status in “libffado” package in Ubuntu:
  New

Bug description:
  libffado fails to build from source in raring, missing inclusion of
  ByteSwap.h.

  
https://launchpad.net/ubuntu/+source/libffado/2.1.0+svn2240-1ubuntu1/+build/4252403

  Affects upstream and Debian, patch forwarded upstream.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ffado/+bug/1110187/+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 1105818] Re: Merge libffado 2.1.0+svn2240-1 (main) from Debian experimental (main)

2013-01-30 Thread Artem Popov
The update results in an FTBFS, which is resolved in bug 1110187.

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

Title:
  Merge libffado 2.1.0+svn2240-1 (main) from Debian experimental (main)

Status in “libffado” package in Ubuntu:
  Fix Committed

Bug description:
  Debian changes:

  libffado (2.1.0+svn2240-1) experimental; urgency=low

* Imported Upstream version 2.1.0+svn2240
* Drop all local patches (all integrated upstream)

   -- Adrian Knoth a...@drcomp.erfurt.thur.de  Thu, 04 Oct 2012
  18:40:22 +0200

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1105818/+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 624514] Re: ffado-diag needs listirqinfo from ffado-mixer-qt4

2013-01-27 Thread Artem Popov
** Changed in: libffado (Ubuntu)
   Status: Confirmed = Fix Released

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

Title:
  ffado-diag needs listirqinfo from ffado-mixer-qt4

Status in “libffado” package in Ubuntu:
  Fix Released
Status in “libffado” package in Debian:
  Fix Released

Bug description:
  david@david-desktop:~$ ffado-diag
  Traceback (most recent call last):
File /usr/bin/ffado-diag, line 29, in module
  from listirqinfo import IRQ,SoftIRQ,IRQInfo
  ImportError: No module named listirqinfo

  Listirqinfo is available in ffado-mixer-qt4, suggest moving it to
  ffado-tools and make ffado-mixer-qt4 depend on ffado-tools.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: ffado-tools 2.0.1+svn1856-1ubuntu1
  ProcVersionSignature: Ubuntu 2.6.35-19.25-generic 2.6.35.3
  Uname: Linux 2.6.35-19-generic x86_64
  Architecture: amd64
  Date: Thu Aug 26 10:41:44 2010
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Alpha amd64 (20100826)
  ProcEnviron:
   LANG=sv_SE.utf8
   SHELL=/bin/bash
  SourcePackage: libffado

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/624514/+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 1105818] [NEW] Merge libffado 2.1.0+svn2240-1 (main) from Debian experimental (main)

2013-01-26 Thread Artem Popov
Public bug reported:

Debian changes:

libffado (2.1.0+svn2240-1) experimental; urgency=low

  * Imported Upstream version 2.1.0+svn2240
  * Drop all local patches (all integrated upstream)

 -- Adrian Knoth a...@drcomp.erfurt.thur.de  Thu, 04 Oct 2012 18:40:22
+0200

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

** Branch linked: lp:~artfwo/ubuntu/raring/libffado/bug-1105818

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

Title:
  Merge libffado 2.1.0+svn2240-1 (main) from Debian experimental (main)

Status in “libffado” package in Ubuntu:
  New

Bug description:
  Debian changes:

  libffado (2.1.0+svn2240-1) experimental; urgency=low

* Imported Upstream version 2.1.0+svn2240
* Drop all local patches (all integrated upstream)

   -- Adrian Knoth a...@drcomp.erfurt.thur.de  Thu, 04 Oct 2012
  18:40:22 +0200

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1105818/+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 1105818] Re: Merge libffado 2.1.0+svn2240-1 (main) from Debian experimental (main)

2013-01-26 Thread Artem Popov
Debdiff against merged Debian revision.

** Patch added: debian_ubuntu.debdiff
   
https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1105818/+attachment/3500969/+files/debian_ubuntu.debdiff

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

Title:
  Merge libffado 2.1.0+svn2240-1 (main) from Debian experimental (main)

Status in “libffado” package in Ubuntu:
  New

Bug description:
  Debian changes:

  libffado (2.1.0+svn2240-1) experimental; urgency=low

* Imported Upstream version 2.1.0+svn2240
* Drop all local patches (all integrated upstream)

   -- Adrian Knoth a...@drcomp.erfurt.thur.de  Thu, 04 Oct 2012
  18:40:22 +0200

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1105818/+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 1105818] Re: Merge libffado 2.1.0+svn2240-1 (main) from Debian experimental (main)

2013-01-26 Thread Artem Popov
Debdiff against previous Ubuntu revision.

** Patch added: ubuntu_ubuntu.debdiff
   
https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1105818/+attachment/3500970/+files/ubuntu_ubuntu.debdiff

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

Title:
  Merge libffado 2.1.0+svn2240-1 (main) from Debian experimental (main)

Status in “libffado” package in Ubuntu:
  New

Bug description:
  Debian changes:

  libffado (2.1.0+svn2240-1) experimental; urgency=low

* Imported Upstream version 2.1.0+svn2240
* Drop all local patches (all integrated upstream)

   -- Adrian Knoth a...@drcomp.erfurt.thur.de  Thu, 04 Oct 2012
  18:40:22 +0200

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1105818/+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 1105818] Re: Merge libffado 2.1.0+svn2240-1 (main) from Debian experimental (main)

2013-01-26 Thread Artem Popov
** Patch removed: debian_ubuntu.debdiff
   
https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1105818/+attachment/3500969/+files/debian_ubuntu.debdiff

** Patch removed: ubuntu_ubuntu.debdiff
   
https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1105818/+attachment/3500970/+files/ubuntu_ubuntu.debdiff

** Patch added: debian_ubuntu.debdiff
   
https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1105818/+attachment/3500971/+files/debian_ubuntu.debdiff

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

Title:
  Merge libffado 2.1.0+svn2240-1 (main) from Debian experimental (main)

Status in “libffado” package in Ubuntu:
  New

Bug description:
  Debian changes:

  libffado (2.1.0+svn2240-1) experimental; urgency=low

* Imported Upstream version 2.1.0+svn2240
* Drop all local patches (all integrated upstream)

   -- Adrian Knoth a...@drcomp.erfurt.thur.de  Thu, 04 Oct 2012
  18:40:22 +0200

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1105818/+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 1105818] Re: Merge libffado 2.1.0+svn2240-1 (main) from Debian experimental (main)

2013-01-26 Thread Artem Popov
** Patch added: ubuntu_ubuntu.debdiff
   
https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1105818/+attachment/3500972/+files/ubuntu_ubuntu.debdiff

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

Title:
  Merge libffado 2.1.0+svn2240-1 (main) from Debian experimental (main)

Status in “libffado” package in Ubuntu:
  New

Bug description:
  Debian changes:

  libffado (2.1.0+svn2240-1) experimental; urgency=low

* Imported Upstream version 2.1.0+svn2240
* Drop all local patches (all integrated upstream)

   -- Adrian Knoth a...@drcomp.erfurt.thur.de  Thu, 04 Oct 2012
  18:40:22 +0200

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1105818/+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 855438] Re: [Oneiric] Need to upgrade package with revision 1995 to fix jackd shutdown problem

2013-01-26 Thread Artem Popov
** Changed in: libffado (Ubuntu)
   Status: Confirmed = Fix Released

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

Title:
  [Oneiric] Need to upgrade package with revision 1995 to fix jackd
  shutdown problem

Status in “libffado” package in Ubuntu:
  Fix Released

Bug description:
  How to reproduce:
  1. run jackd with qjackctl or gladish
  2. stop jackd
  3. you can see jackd still exists in top or ps command
  4. especially gladish can't open the other session

  The current package is generated with revision 1985. This still causes
  shutdown problem of jackd compiled with dbus.

  This bug was reported ticket 306 and it seemed to be fixed in revision 1985.
  http://subversion.ffado.org/ticket/306

  But in this week, a guy post a patch related to this. His patch is not 
directly applied but it's a cue to reconsider the bug.
  
http://sourceforge.net/mailarchive/forum.php?thread_name=4E7992BB.1000505%40monom.orgforum_name=ffado-devel

  Now this seems to be fixed in revision 1995.
  http://subversion.ffado.org/changeset/1995

  I'm also realized there is a problem to shudown jackd which we can
  utilize from released package. I personnaly generated package from
  revision 1995 and confirmed this bug seems to be fixed.

  If possible, I hope you to upgrade package with revision 1995.

  Regards

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/855438/+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 860705] Re: jackd assert failure: jackd: tpp.c:63: __pthread_tpp_change_priority: Assertion `new_prio == -1 || (new_prio = __sched_fifo_min_prio new_prio = __sched_fifo_ma

2013-01-26 Thread Artem Popov
** Changed in: jackd2 (Ubuntu)
   Status: Confirmed = Fix Released

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

Title:
  jackd assert failure: jackd: tpp.c:63: __pthread_tpp_change_priority:
  Assertion `new_prio == -1 || (new_prio = __sched_fifo_min_prio 
  new_prio = __sched_fifo_max_prio)' failed.

Status in “jackd2” package in Ubuntu:
  Fix Released

Bug description:
  The following happens when stopping jack (ffado backend) either by
  ctrl+C or from qjackctl.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: jackd2 1.9.7~dfsg-1ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
  Uname: Linux 3.0.0-12-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 1.23-0ubuntu1
  Architecture: i386
  AssertionMessage: jackd: tpp.c:63: __pthread_tpp_change_priority: Assertion 
`new_prio == -1 || (new_prio = __sched_fifo_min_prio  new_prio = 
__sched_fifo_max_prio)' failed.
  CrashCounter: 1
  Date: Tue Sep 27 23:14:53 2011
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/jackd
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta i386 (20110911)
  ProcCmdline: /usr/bin/jackd --sync -P89 -dfirewire -r44100 -p128 -n3
  ProcEnviron:
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: jackd2
  StacktraceTop:
   __kernel_vsyscall ()
   raise () from /lib/i386-linux-gnu/libc.so.6
   abort () from /lib/i386-linux-gnu/libc.so.6
   __assert_fail () from /lib/i386-linux-gnu/libc.so.6
   __pthread_tpp_change_priority () from /lib/i386-linux-gnu/libpthread.so.0
  Title: jackd assert failure: jackd: tpp.c:63: __pthread_tpp_change_priority: 
Assertion `new_prio == -1 || (new_prio = __sched_fifo_min_prio  new_prio = 
__sched_fifo_max_prio)' failed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin audio cdrom dialout lpadmin plugdev sambashare

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

2012-12-23 Thread T-artem
I'd like to add that this feature is also a must if you Alt-Tab
applications, but I guess it's to early to request it to be implemented
since this bug is only 4,5 years of age - it's not yet vintage.

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

Title:
  X.org server should keep track of and restore its initial (desktop)
  resolution and refresh rate

Status in Wine:
  Won't Fix
Status in X.Org X server:
  Confirmed
Status in “xorg-server” package in Ubuntu:
  Triaged

Bug description:
  Applications like games change desktop resolution (graphics mode) for
  their needs. Unfortunately when such applications crash then X.org
  server doesn't revert the resolution back to its initial mode.

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

2012-07-01 Thread T-artem
Am I the only one for whom this page http://blog.neverendingo.de/?p=125
exhibits the same problems? (Jerky scrolling and 100% CPU usage)

Is it the same problem or I should post a separate bug report?

(Firefox 14 beta10 here, NVIDIA 290.10)

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

Title:
  Extremely slow painting of launchpad.net bug details page with nvidia
  driver

Status in The Mozilla Firefox Browser:
  Confirmed
Status in “firefox” package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: firefox

  Launchpad.net bug detail pages are painted extremely slowly by Firefox
  on my machine. I'm running Ubuntu Lucid 64-bit, and I have the
  proprietary nvidia driver (from the Ubuntu repositories) installed,
  version current. The machine has two 8800 GTX GPU's with 768 MB
  each, so the available graphics power should not be a problem.

  It takes many seconds (sometimes tens of seconds) to draw the page,
  during which the entire computer slows to a crawl. Nothing happens on
  the screen during this time. Whenever I scroll the page up so that
  more of the page is revealed at the top of the screen, this is painted
  extremely slowly as well. Scrolling down (once the page is fully
  painted) does not produce slow-downs, so the problem appears to be
  with the content at the top of the page.

  It appears to be an interaction between Firefox, Launchpad.net and the
  proprietary NVidia driver. I don't notice slowdowns like this on any
  other web page (including other launchpad.net pages). Other browsers,
  such as Chrome, draw Launchpad bug detail pages with lighting speed.
  And when I use the nv or nouveau drivers the problem does not appear
  either.

  Since Chrome can paint the pages at fast speeds, Firefox should be
  able to as well, so I still think this is a Firefox problem.

  If there is any way I can determine exactly what it is that is taking
  so much time and slowing down the entire computer, please let me know!
  Or if there is any other way in which I can help debug this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: firefox 3.6.6+nobinonly-0ubuntu0.10.04.1
  ProcVersionSignature: Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5
  Uname: Linux 2.6.32-23-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Wed Jul 14 21:03:25 2010
  FirefoxPackages:
   firefox 3.6.6+nobinonly-0ubuntu0.10.04.1
   firefox-gnome-support 3.6.6+nobinonly-0ubuntu0.10.04.1
   firefox-branding 3.6.6+nobinonly-0ubuntu0.10.04.1
   abroswer N/A
   abrowser-branding N/A
  InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027)
  SourcePackage: firefox

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/605567/+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 973109] [NEW] package libnm-gtk0 0.9.4.1-0ubuntu2 failed to install/upgrade: ErrorMessage: dependency problems - leaving unconfigured

2012-04-04 Thread Artem
Public bug reported:

1

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: libnm-gtk0 0.9.4.1-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13
Uname: Linux 3.2.0-21-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.0-0ubuntu4
Architecture: amd64
Date: Sun Apr  1 15:43:10 2012
ErrorMessage: ErrorMessage: dependency problems - leaving unconfigured
IfupdownConfig:
 auto lo
 iface lo inet loopback
InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: network-manager-applet
Title: package libnm-gtk0 0.9.4.1-0ubuntu2 failed to install/upgrade: 
ErrorMessage: dependency problems - leaving unconfigured
UpgradeStatus: Upgraded to precise on 2012-04-01 (2 days ago)

** Affects: network-manager-applet (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package precise

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

Title:
  package libnm-gtk0 0.9.4.1-0ubuntu2 failed to install/upgrade:
  ErrorMessage: dependency problems - leaving unconfigured

Status in “network-manager-applet” package in Ubuntu:
  New

Bug description:
  1

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: libnm-gtk0 0.9.4.1-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13
  Uname: Linux 3.2.0-21-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0-0ubuntu4
  Architecture: amd64
  Date: Sun Apr  1 15:43:10 2012
  ErrorMessage: ErrorMessage: dependency problems - leaving unconfigured
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager-applet
  Title: package libnm-gtk0 0.9.4.1-0ubuntu2 failed to install/upgrade: 
ErrorMessage: dependency problems - leaving unconfigured
  UpgradeStatus: Upgraded to precise on 2012-04-01 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/973109/+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 973109] Re: package libnm-gtk0 0.9.4.1-0ubuntu2 failed to install/upgrade: ErrorMessage: dependency problems - leaving unconfigured

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

Title:
  package libnm-gtk0 0.9.4.1-0ubuntu2 failed to install/upgrade:
  ErrorMessage: dependency problems - leaving unconfigured

Status in “network-manager-applet” package in Ubuntu:
  New

Bug description:
  1

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: libnm-gtk0 0.9.4.1-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-21.34-generic 3.2.13
  Uname: Linux 3.2.0-21-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0-0ubuntu4
  Architecture: amd64
  Date: Sun Apr  1 15:43:10 2012
  ErrorMessage: ErrorMessage: dependency problems - leaving unconfigured
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager-applet
  Title: package libnm-gtk0 0.9.4.1-0ubuntu2 failed to install/upgrade: 
ErrorMessage: dependency problems - leaving unconfigured
  UpgradeStatus: Upgraded to precise on 2012-04-01 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/973109/+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 893842] Re: Move admin group to sudo

2012-03-27 Thread Artem Popov
** Also affects: indicator-cpufreq (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Move admin group to sudo

Status in Release Notes for Ubuntu:
  New
Status in “accountsservice” package in Ubuntu:
  Fix Released
Status in “command-not-found” package in Ubuntu:
  Fix Released
Status in “indicator-cpufreq” package in Ubuntu:
  Confirmed
Status in “jockey” package in Ubuntu:
  Fix Released
Status in “language-selector” package in Ubuntu:
  Fix Released
Status in “policykit-1” package in Ubuntu:
  Fix Released
Status in “policykit-desktop-privileges” package in Ubuntu:
  Fix Released
Status in “update-notifier” package in Ubuntu:
  Fix Released
Status in “userconfig” package in Ubuntu:
  Fix Released
Status in “accountsservice” source package in Precise:
  Fix Released
Status in “command-not-found” source package in Precise:
  Fix Released
Status in “indicator-cpufreq” source package in Precise:
  Confirmed
Status in “jockey” source package in Precise:
  Fix Released
Status in “language-selector” source package in Precise:
  Fix Released
Status in “policykit-1” source package in Precise:
  Fix Released
Status in “policykit-desktop-privileges” source package in Precise:
  Fix Released
Status in “update-notifier” source package in Precise:
  Fix Released
Status in “userconfig” source package in Precise:
  Fix Released

Bug description:
  Fresh install from daily today, am unable to do many common admin actions, 
the 'root' password is requested
  Attached orig /etc/group

  TEST CASE:
  1. Install Ubuntu Desktop, reboot and login
  2. Click on the user indicator and select 'User Accounts'
  3. On the dialog, click on 'Unlock'

  EXPECTED RESULT
  A authentication dialog is displayed asking for the user's password

  WHAT HAPPENS
  The user is prompted for the root password

  WORKAROUND
  Open a terminal and run the following command:
  $ sudo adduser your_user_name admin
  logout and login

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: ubiquity 2.9.4
  ProcVersionSignature: Ubuntu 3.1.0-2.3-generic 3.1.0
  Uname: Linux 3.1.0-2-generic i686
  ApportVersion: 1.26-0ubuntu1
  Architecture: i386
  Date: Tue Nov 22 20:56:50 2011
  InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha i386 (2022)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/893842/+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 772564] Re: Backspace key doesn't go back in the history anymore

2012-03-14 Thread Gvozdik Artem
Also have this problem through many ubuntu distros, firefox versions and
keyboards. I have no idea why. :|

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

Title:
  Backspace key doesn't go back in the history anymore

Status in “firefox” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: firefox

  I don't know when exactly it started to happen but, suddenly, Firefox
  doesn't walk back to the last page visited when I press the Backspace
  key.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: firefox 4.0+nobinonly-0ubuntu3
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic x86_64
  Architecture: amd64
  Date: Thu Apr 28 15:00:44 2011
  EcryptfsInUse: Yes
  FirefoxPackages:
   firefox 4.0+nobinonly-0ubuntu3
   flashplugin-installer 10.2.159.1ubuntu1
   adobe-flashplugin N/A
   icedtea-plugin 1.1~20110420-0ubuntu1
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007)
  ProcEnviron:
   LANGUAGE=pt_BR:en
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: firefox
  UpgradeStatus: Upgraded to natty on 2011-04-19 (8 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/772564/+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 925503] Re: nautilus segfaults in gtk_ui_manager_new_merge_id()

2012-02-26 Thread Gvozdik Artem
Happened on precise with no reason.

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

Title:
  nautilus segfaults in gtk_ui_manager_new_merge_id()

Status in Nautilus:
  New
Status in “nautilus” package in Ubuntu:
  Triaged

Bug description:
  happened right after an update

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: nautilus 1:3.3.4-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-10.18-generic 3.2.1
  Uname: Linux 3.2.0-10-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.91-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  Date: Thu Feb  2 09:42:02 2012
  ExecutablePath: /usr/bin/nautilus
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  ProcCmdline: nautilus
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f0e8be058d0 gtk_ui_manager_new_merge_id:  mov
0x18(%rdi),%rdx
   PC (0x7f0e8be058d0) ok
   source 0x18(%rdi) (0x0018) not located in a known VMA region (needed 
readable region)!
   destination %rdx ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: nautilus
  StacktraceTop:
   gtk_ui_manager_new_merge_id () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: nautilus crashed with SIGSEGV in gtk_ui_manager_new_merge_id()
  UpgradeStatus: Upgraded to precise on 2012-02-02 (0 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/925503/+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 939498] Re: rhythmbox-metadata crashed with SIGSEGV in _start()

2012-02-23 Thread Gvozdik Artem
*** This bug is a duplicate of bug 820601 ***
https://bugs.launchpad.net/bugs/820601


** Visibility changed to: Public

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

Title:
  rhythmbox-metadata crashed with SIGSEGV in _start()

Status in “rhythmbox” package in Ubuntu:
  New

Bug description:
  Happened when I played .ogg file by sftp connection to server, and
  when I closed it in nautilus, rhythmbox closed too.

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: rhythmbox 2.95-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-17.26-generic-pae 3.2.6
  Uname: Linux 3.2.0-17-generic-pae i686
  NonfreeKernelModules: nvidia
  ApportVersion: 1.92-0ubuntu1
  Architecture: i386
  Date: Thu Feb 23 17:27:04 2012
  ExecutablePath: /usr/lib/rhythmbox/rhythmbox-metadata
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012)
  ProcCmdline: /usr/lib/rhythmbox/rhythmbox-metadata unix:tmpdir=/tmp
  SegvAnalysis:
   Segfault happened at: 0x804e638 _start+2108:   cmp%eax,0x4(%ebx)
   PC (0x0804e638) ok
   source %eax ok
   destination 0x4(%ebx) (0x0005) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: rhythmbox
  Stacktrace:
   #0  0x0804e638 in _start ()
   No symbol table info available.
  StacktraceTop: _start ()
  Title: rhythmbox-metadata crashed with SIGSEGV in _start()
  UpgradeStatus: Upgraded to precise on 2012-02-23 (0 days ago)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/939498/+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 822382] Re: unchecking the Enable the menu shortkey (F10 by default) do not allow to th e midnigth commander to exit using F10 key

2011-10-19 Thread Artem S.
I've found solution:

CompizConfig Settings Manager - Ubuntu Unity Plugin - remove Key
to open the first panel menu

I had to restart unity (unity --replace) to apply configuration at first
time, but then I could change it on the fly.

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

Title:
  unchecking the Enable the menu shortkey (F10 by default) do not allow
  to th e midnigth commander to exit using F10 key

Status in “gnome-terminal” package in Ubuntu:
  Confirmed

Bug description:
  unchecking the Enable the menu shortkey (F10 by default) do not allow
  to th e midnigth commander to exit using F10 key

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-terminal 3.0.1-0ubuntu3
  ProcVersionSignature: Ubuntu 3.0.0-7.9-generic 3.0.0
  Uname: Linux 3.0.0-7-generic x86_64
  Architecture: amd64
  Date: Sun Aug  7 15:41:08 2011
  ExecutablePath: /usr/bin/gnome-terminal
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Alpha amd64 (20110705.1)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/822382/+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 822382] Re: unchecking the Enable the menu shortkey (F10 by default) do not allow to th e midnigth commander to exit using F10 key

2011-10-18 Thread Artem S.
Confirmed on Ubuntu 11.10, gnome-terminal 3.0.1-0ubuntu3.   I've
upgraded to it from 11.04

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

Title:
  unchecking the Enable the menu shortkey (F10 by default) do not allow
  to th e midnigth commander to exit using F10 key

Status in “gnome-terminal” package in Ubuntu:
  Confirmed

Bug description:
  unchecking the Enable the menu shortkey (F10 by default) do not allow
  to th e midnigth commander to exit using F10 key

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-terminal 3.0.1-0ubuntu3
  ProcVersionSignature: Ubuntu 3.0.0-7.9-generic 3.0.0
  Uname: Linux 3.0.0-7-generic x86_64
  Architecture: amd64
  Date: Sun Aug  7 15:41:08 2011
  ExecutablePath: /usr/bin/gnome-terminal
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Alpha amd64 (20110705.1)
  SourcePackage: gnome-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/822382/+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 805154] Re: gdm-simple-slave crashed with SIGSEGV in _nss_compat_getpwnam_r()

2011-09-09 Thread Gvozdik Artem
Happened after upgrading from 11.04 to 11.10, amd64

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

Title:
  gdm-simple-slave crashed with SIGSEGV in _nss_compat_getpwnam_r()

Status in “gdm” package in Ubuntu:
  Triaged

Bug description:
  Chrash happend while trying to change a desktop-icon. Searching the
  icon in a hidden folder . in the user directory.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: gdm 3.0.4-0ubuntu3
  ProcVersionSignature: Ubuntu 3.0-2.3-generic-pae 3.0.0-rc4
  Uname: Linux 3.0-2-generic-pae i686
  NonfreeKernelModules: fglrx
  Architecture: i386
  Date: Sun Jul  3 01:25:08 2011
  ExecutablePath: /usr/lib/gdm/gdm-simple-slave
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Alpha i386 (20110531.1)
  ProcCmdline: /usr/lib/gdm/gdm-simple-slave --display-id 
/org/gnome/DisplayManager/Display2
  ProcEnviron:
   LANGUAGE=de_AT:de
   PATH=(custom, no user)
   LANG=de_AT.UTF-8
  SegvAnalysis:
   Segfault happened at: 0xb77405b7 _nss_compat_getpwnam_r+55:movzbl 
(%edx),%eax
   PC (0xb77405b7) ok
   source (%edx) (0x) not located in a known VMA region (needed 
readable region)!
   destination %eax ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gdm
  StacktraceTop:
   _nss_compat_getpwnam_r () from /lib/i386-linux-gnu/libnss_compat.so.2
   getpwnam_r () from /lib/i386-linux-gnu/libc.so.6
   getpwnam () from /lib/i386-linux-gnu/libc.so.6
   ?? ()
   ?? ()
  Title: gdm-simple-slave crashed with SIGSEGV in _nss_compat_getpwnam_r()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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