[Desktop-packages] [Bug 1082507] [NEW] [Aspire 5920G, Realtek ALC1200, Black Headphone Out, Front] No automute
Public bug reported: not working correctly, unpluged jack do not switch to onboard stereo until reboot ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alsa-base 1.0.25+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-33.52-generic-pae 3.2.31 Uname: Linux 3.2.0-33-generic-pae i686 NonfreeKernelModules: fglrx AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu15 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: anna 1906 F pulseaudio /dev/snd/controlC0: anna 1906 F pulseaudio /dev/snd/pcmC0D0p: anna 1906 F...m pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf060 irq 45' Mixer name : 'Realtek ALC1200' Components : 'HDA:10ec0888,10250121,00100101 HDA:14f12c06,10250121,0010' Controls : 24 Simple ctrls : 14 Card1.Amixer.info: Card hw:1 'HDMI'/'HDA ATI HDMI at 0xf021 irq 47' Mixer name : 'ATI R6xx HDMI' Components : 'HDA:1002aa01,00aa0100,0010' Controls : 6 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Date: Fri Nov 23 23:12:06 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta i386 (20120328) MarkForUpload: True PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Встроенное аудио - HDA Intel Symptom_Jack: Black Headphone Out, Front Symptom_Type: No auto-mute between outputs Title: [Aspire 5920G, Realtek ALC1200, Black Headphone Out, Front] No automute UpgradeStatus: Upgraded to precise on 2012-10-06 (48 days ago) dmi.bios.date: 06/18/2008 dmi.bios.vendor: Acer dmi.bios.version: v1.3813 dmi.board.name: Chapala dmi.board.vendor: Acer, Inc. dmi.board.version: Not Applicable dmi.chassis.type: 1 dmi.chassis.vendor: Acer, Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAcer:bvrv1.3813:bd06/18/2008:svnAcer,inc.:pnAspire5920G:pvrNotApplicable:rvnAcer,Inc.:rnChapala:rvrNotApplicable:cvnAcer,Inc.:ct1:cvrN/A: dmi.product.name: Aspire 5920G dmi.product.version: Not Applicable dmi.sys.vendor: Acer, inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 precise running-unity -- 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/1082507 Title: [Aspire 5920G, Realtek ALC1200, Black Headphone Out, Front] No automute Status in “alsa-driver” package in Ubuntu: New Bug description: not working correctly, unpluged jack do not switch to onboard stereo until reboot ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alsa-base 1.0.25+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-33.52-generic-pae 3.2.31 Uname: Linux 3.2.0-33-generic-pae i686 NonfreeKernelModules: fglrx AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu15 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: anna 1906 F pulseaudio /dev/snd/controlC0: anna 1906 F pulseaudio /dev/snd/pcmC0D0p: anna 1906 F...m pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf060 irq 45' Mixer name : 'Realtek ALC1200' Components : 'HDA:10ec0888,10250121,00100101 HDA:14f12c06,10250121,0010' Controls : 24 Simple ctrls : 14 Card1.Amixer.info: Card hw:1 'HDMI'/'HDA ATI HDMI at 0xf021 irq 47' Mixer name : 'ATI R6xx HDMI' Components : 'HDA:1002aa01,00aa0100,0010' Controls : 6 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Date: Fri Nov 23 23:12:06 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta i386 (20120328) MarkForUpload: True PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Встроенное аудио - HDA Intel Symptom_Jack: Black Headphone Out, Front Symptom_Type: No auto-mute between outputs Title: [Aspire 5920G, Realtek ALC1200, Black Headphone Out, Front] No automute UpgradeStatus: Upgraded to precise on 2012-10-06 (48 days ago) dmi.bios.date: 06/18/2008 dmi.bios.vendor: Acer dmi.bios.version: v1.3813 dmi.board.name: Chapala dmi.board.vendor: Acer, Inc. dmi.board.version: Not Applicable dmi.chassis.type: 1 dmi.chassis.vendor: Acer, Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAcer:bvrv1.3813:bd06/18/2008:svnAcer,inc.:pnAspire5920G:pvrNotApplicable:rvnAcer,Inc.:rnChapala:rvrNotApplicable:cvnAcer,Inc.:ct1:cvrN/A: dmi.product.name: Aspire 5920G dmi.product.version: Not Applicable dmi.sys.vendor: Acer, inc. To manage notifications about this bug go to:
[Desktop-packages] [Bug 974883] [NEW] package gconf2-common 2.28.1-0ubuntu1 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 10
Public bug reported: tried to reinstall all the packages, this one failed ProblemType: Package DistroRelease: Ubuntu 10.04 Package: gconf2-common 2.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-37.81-generic 2.6.32.49+drm33.21 Uname: Linux 2.6.32-37-generic i686 AptOrdering: gconf2-common: Install foomatic-filters: Configure gconf2-common: Configure Architecture: i386 Date: Fri Apr 6 02:00:31 2012 ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код ошибки 10 InstallationMedia: Ubuntu 10.04.3 LTS Lucid Lynx - Release i386 (20110720.1) PackageArchitecture: all SourcePackage: gconf Title: package gconf2-common 2.28.1-0ubuntu1 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 10 ** Affects: gconf (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 gconf in Ubuntu. https://bugs.launchpad.net/bugs/974883 Title: package gconf2-common 2.28.1-0ubuntu1 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 10 Status in “gconf” package in Ubuntu: New Bug description: tried to reinstall all the packages, this one failed ProblemType: Package DistroRelease: Ubuntu 10.04 Package: gconf2-common 2.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-37.81-generic 2.6.32.49+drm33.21 Uname: Linux 2.6.32-37-generic i686 AptOrdering: gconf2-common: Install foomatic-filters: Configure gconf2-common: Configure Architecture: i386 Date: Fri Apr 6 02:00:31 2012 ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код ошибки 10 InstallationMedia: Ubuntu 10.04.3 LTS Lucid Lynx - Release i386 (20110720.1) PackageArchitecture: all SourcePackage: gconf Title: package gconf2-common 2.28.1-0ubuntu1 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/974883/+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 974883] Re: package gconf2-common 2.28.1-0ubuntu1 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 10
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/974883 Title: package gconf2-common 2.28.1-0ubuntu1 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 10 Status in “gconf” package in Ubuntu: New Bug description: tried to reinstall all the packages, this one failed ProblemType: Package DistroRelease: Ubuntu 10.04 Package: gconf2-common 2.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-37.81-generic 2.6.32.49+drm33.21 Uname: Linux 2.6.32-37-generic i686 AptOrdering: gconf2-common: Install foomatic-filters: Configure gconf2-common: Configure Architecture: i386 Date: Fri Apr 6 02:00:31 2012 ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код ошибки 10 InstallationMedia: Ubuntu 10.04.3 LTS Lucid Lynx - Release i386 (20110720.1) PackageArchitecture: all SourcePackage: gconf Title: package gconf2-common 2.28.1-0ubuntu1 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/974883/+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 1310551] Re: NVIDIA proprietary driver 331.38 from package nvidia-331 on Xubuntu 14.04 causes display to hang
Hi, I have same issue on MSI CX61 2OD with Nvidia Geforce 740M, Ubuntu 14.04 64 bits, driver 331.38 (both tested and updates versions). Display hangs randomly when video is set to use Nvidia GPU, but it works fine when switched to Intel GPU. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1310551 Title: NVIDIA proprietary driver 331.38 from package nvidia-331 on Xubuntu 14.04 causes display to hang Status in “nvidia-graphics-drivers-331” package in Ubuntu: Confirmed Bug description: On 14.04 I am getting an issue on my Thinkpad T520 where running the proprietary,tested 331.38 driver causes my display to hang. It seems to stay that way until I switch to tty6 with ctrl+alt+f6 and then back to tty7 which has the display, this causes it to un-hang. This then happens back and forth. I am not sure but it might be triggered by clicking things, opening windows and such. The problem disappears when switching back to the open source driver. Should I try an even newer driver from nvidia, or is there any more information you need for troubleshooting? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nvidia-331 331.38-0ubuntu7 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Apr 21 12:29:36 2014 InstallationDate: Installed on 2014-03-18 (33 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140318) SourcePackage: nvidia-graphics-drivers-331 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.nvidia.331.hybrid.conf: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1310551/+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 1208993] Re: Ubuntu slows down and hangs while copying file from/to USB
The problem still exists in 16.04. And as I can see the ticket is not assigned to anyone... -- 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/1208993 Title: Ubuntu slows down and hangs while copying file from/to USB Status in nautilus package in Ubuntu: Confirmed Bug description: Hi While copying many and large files to and from a USB drive, the system becomes incredibly slow and sometimes hangs. I watched the system monitor while it was running slowly but cpu was not above 50% at any time, the same for memory. I'm using the "WD my passport" HD with a USB3 port of my "ASUS K55VD" laptop. Description: Ubuntu 13.04 Release: 13.04 nautilus: Installed: 1:3.6.3-0ubuntu16 Candidate: 1:3.6.3-0ubuntu16 Version table: *** 1:3.6.3-0ubuntu16 0 500 http://ubuntu-archive.mirror.nucleus.be/ raring/main amd64 Packages 100 /var/lib/dpkg/status Steps to reproduce: 1) Aquire many large files (like your totally legit moviecollection) 2) Copy files to external HD 3) Open your browser and be sad when your system becomes incredibly slow after a few minutes This is my first bugreport so if I'm missing something, please tell me. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: nautilus 1:3.6.3-0ubuntu16 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 Uname: Linux 3.8.0-27-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 Date: Tue Aug 6 22:56:34 2013 EcryptfsInUse: Yes ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'656x715+154+151'" b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2013-05-31 (67 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/+source/nautilus/+bug/1208993/+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 1664979] Re: EQ overflowing. Additional events will be discarded until existing events are processed.
Hi! I can reproduce this bug too. System just going to freeze and does not react to keyboard. After reboot sometimes it happens again (for example while watching youtube video in vivaldi browser). Here's part of syslog attached. ** Attachment added: "syslog.1" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1664979/+attachment/4887785/+files/syslog.1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1664979 Title: EQ overflowing. Additional events will be discarded until existing events are processed. Status in xorg package in Ubuntu: Confirmed Bug description: I was on 14.04 and had no problem, but I started to have EQ overflow after upgrading to 14.04.3. Then I did fresh install of 16.04 on the same PC, but still EQ overflow occurs after closing SMPlayer. [640410.566] (WW) NVIDIA(0): WAIT (2, 8, 0x8000, 0x3d14, 0x4078) [640417.566] (WW) NVIDIA(0): WAIT (1, 8, 0x8000, 0x3d14, 0x4078) [640421.680] (WW) NVIDIA(0): WAIT (2, 8, 0x8000, 0x3d14, 0xf5d4) [640428.680] (WW) NVIDIA(0): WAIT (1, 8, 0x8000, 0x3d14, 0xf5d4) [640439.704] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16dc1, 0x3d14, 0xf680) [640446.704] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16dc1, 0x3d14, 0xf680) [640449.705] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16cf7, 0x3d14, 0xf680) [640456.705] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16cf7, 0x3d14, 0xf680) [640459.706] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16dc2, 0x3d14, 0xf724) [640466.706] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16dc2, 0x3d14, 0xf724) [640469.707] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16cf8, 0x3d14, 0xf724) [640476.707] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16cf8, 0x3d14, 0xf724) [640479.708] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16dc3, 0x3d14, 0xf7c8) [640486.708] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16dc3, 0x3d14, 0xf7c8) [640489.709] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16cf9, 0x3d14, 0xf7c8) [640496.709] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16cf9, 0x3d14, 0xf7c8) [640499.710] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16dc4, 0x3d14, 0xf86c) [640506.710] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16dc4, 0x3d14, 0xf86c) [640509.711] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16cfa, 0x3d14, 0xf86c) [640516.711] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16cfa, 0x3d14, 0xf86c) [640519.712] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16dc5, 0x3d14, 0xf910) [640526.712] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16dc5, 0x3d14, 0xf910) [640529.713] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16cfb, 0x3d14, 0xf910) [640536.713] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16cfb, 0x3d14, 0xf910) [640539.714] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16dc6, 0x3d14, 0xf9b4) [640546.714] (WW) NVIDIA(0): WAIT (1-S, 17, 0x16dc6, 0x3d14, 0xf9b4) [640549.715] (WW) NVIDIA(0): WAIT (2-S, 17, 0x16cfc, 0x3d14, 0xf9b4) (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) [0x55b19d068ade] (EE) 1: /usr/lib/xorg/Xorg (mieqEnqueue+0x253) [0x55b19d04a583] (EE) 2: /usr/lib/xorg/Xorg (QueuePointerEvents+0x52) [0x55b19cf22862] (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7fdc68ed+0x61f3) [0x7fdc68ed61f3] (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0x7fdc68ed+0x6a5d) [0x7fdc68ed6a5d] (EE) 5: /usr/lib/xorg/Xorg (0x55b19ceb6000+0x94538) [0x55b19cf4a538] (EE) 6: /usr/lib/xorg/Xorg (0x55b19ceb6000+0xb9922) [0x55b19cf6f922] (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (0x7fdc6faec000+0x354b0) [0x7fdc6fb214b0] (EE) 8: /lib/x86_64-linux-gnu/libc.so.6 (__sched_yield+0x7) [0x7fdc6fbd5c47] (EE) 9: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so (0x7fdc6ab5d000+0xa7c61) [0x7fdc6ac04c61] (EE) 10: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so (0x7fdc6ab5d000+0xbb7bc) [0x7fdc6ac187bc] (EE) 11: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so (0x7fdc6ab5d000+0x5b1ec2) [0x7fdc6b10eec2] (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. (EE) (EE) Backtrace: (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x55b19d068ade] (EE) 1: /usr/lib/xorg/Xorg (QueuePointerEvents+0x52) [0x55b19cf22862] (EE) 2: /usr/lib/xorg/modules/input/evdev_drv.so (0x7fdc68ed+0x61f3) [0x7fdc68ed61f3] (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7fdc68ed+0x6a5d) [0x7fdc68ed6a5d] (EE) 4: /usr/lib/xorg/Xorg (0x55b19ceb6000+0x94538) [0x55b19cf4a538] (EE) 5: /usr/lib/xorg/Xorg (0x55b19ceb6000+0xb9922) [0x55b19cf6f922] (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (0x7fdc6faec000+0x354b0) [0x7fdc6fb214b0] (EE) 7:
[Desktop-packages] [Bug 1733029] [NEW] Asus N55JM in 2.1 mode alsa SonicMaster subwoofer doesn't work
Public bug reported: I expect my subwoofer working when choosing ALSA 2.1 in VLC audio settings, but in fact it doesn't sound at all AlsaMixer shows BassSpeaker, but changing it's volume has no effect Also I tried the trick described in similar bug I found(https://bugs.launchpad.net/ubuntu/+source/alsa-tools/+bug/1405691, https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/871808) with hdajackretask with pin 0x1a as LFE and hda_analyzer - no effect though System Kubuntu Description:Ubuntu 17.10 Release:17.10 alsaplayer-alsa: Установлен: (отсутствует) Кандидат: 0.99.81-2 Таблица версий: 0.99.81-2 500 500 http://ru.archive.ubuntu.com/ubuntu artful/universe amd64 Packages alsa-base: Установлен: 1.0.25+dfsg-0ubuntu5 Кандидат: 1.0.25+dfsg-0ubuntu5 Таблица версий: *** 1.0.25+dfsg-0ubuntu5 500 500 http://ru.archive.ubuntu.com/ubuntu artful/main amd64 Packages 500 http://ru.archive.ubuntu.com/ubuntu artful/main i386 Packages 100 /var/lib/dpkg/status alsa-source: Установлен: (отсутствует) Кандидат: 1.0.25+dfsg-0ubuntu5 Таблица версий: 1.0.25+dfsg-0ubuntu5 500 500 http://ru.archive.ubuntu.com/ubuntu artful/universe amd64 Packages 500 http://ru.archive.ubuntu.com/ubuntu artful/universe i386 Packages alsamixergui: Установлен: 0.9.0rc2-1-10 Кандидат: 0.9.0rc2-1-10 Таблица версий: *** 0.9.0rc2-1-10 500 500 http://ru.archive.ubuntu.com/ubuntu artful/universe amd64 Packages 100 /var/lib/dpkg/status alsaplayer-output: Установлен: (отсутствует) Кандидат: (отсутствует) Таблица версий: alsaplayer: Установлен: (отсутствует) Кандидат: (отсутствует) Таблица версий: alsaplayer-jack: Установлен: (отсутствует) Кандидат: 0.99.81-2 Таблица версий: 0.99.81-2 500 500 http://ru.archive.ubuntu.com/ubuntu artful/universe amd64 Packages alsaplayer-common: Установлен: (отсутствует) Кандидат: 0.99.81-2 Таблица версий: 0.99.81-2 500 500 http://ru.archive.ubuntu.com/ubuntu artful/universe amd64 Packages alsa: Установлен: (отсутствует) Кандидат: (отсутствует) Таблица версий: alsaplayer-esd: Установлен: (отсутствует) Кандидат: (отсутствует) Таблица версий: alsaplayer-gtk: Установлен: (отсутствует) Кандидат: 0.99.81-2 Таблица версий: 0.99.81-2 500 500 http://ru.archive.ubuntu.com/ubuntu artful/universe amd64 Packages alsa-utils: Установлен: 1.1.3-1ubuntu1 Кандидат: 1.1.3-1ubuntu1 Таблица версий: *** 1.1.3-1ubuntu1 500 500 http://ru.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status alsaplayer-text: Установлен: (отсутствует) Кандидат: 0.99.81-2 Таблица версий: 0.99.81-2 500 500 http://ru.archive.ubuntu.com/ubuntu artful/universe amd64 Packages alsa-firmware-loaders: Установлен: (отсутствует) Кандидат: 1.1.3-1 Таблица версий: 1.1.3-1 500 500 http://ru.archive.ubuntu.com/ubuntu artful/multiverse amd64 Packages alsaplayer-xosd: Установлен: (отсутствует) Кандидат: 0.99.81-2 Таблица версий: 0.99.81-2 500 500 http://ru.archive.ubuntu.com/ubuntu artful/universe amd64 Packages alsa-tools: Установлен: 1.1.3-1 Кандидат: 1.1.3-1 Таблица версий: *** 1.1.3-1 500 500 http://ru.archive.ubuntu.com/ubuntu artful/universe amd64 Packages 100 /var/lib/dpkg/status alsaplayer-nas: Установлен: (отсутствует) Кандидат: 0.99.81-2 Таблица версий: 0.99.81-2 500 500 http://ru.archive.ubuntu.com/ubuntu artful/universe amd64 Packages alsaplayer-oss: Установлен: (отсутствует) Кандидат: 0.99.81-2 Таблица версий: 0.99.81-2 500 500 http://ru.archive.ubuntu.com/ubuntu artful/universe amd64 Packages alsaplayer-interface: Установлен: (отсутствует) Кандидат: (отсутствует) Таблица версий: alsaplayer-daemon: Установлен: (отсутствует) Кандидат: 0.99.81-2 Таблица версий: 0.99.81-2 500 500 http://ru.archive.ubuntu.com/ubuntu artful/universe amd64 Packages alsa-tools-gui: Установлен: 1.1.3-1 Кандидат: 1.1.3-1 Таблица версий: *** 1.1.3-1 500 500 http://ru.archive.ubuntu.com/ubuntu artful/universe amd64 Packages 100 /var/lib/dpkg/status alsa-oss: Установлен: (отсутствует) Кандидат: 1.0.28-1ubuntu1 Таблица версий: 1.0.28-1ubuntu1 500 500 http://ru.archive.ubuntu.com/ubuntu artful/universe amd64 Packages ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: asus n55 sound -- 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/1733029 Title: Asus N55JM in 2.1 mode alsa SonicMaster subwoofer doesn't work Status in alsa-driver package in Ubuntu: New Bug description: I expect my subwoofer working when choosing ALSA 2.1 in VLC audio settings, but in fact it doesn't
[Desktop-packages] [Bug 1733029] Re: Asus N55JM in 2.1 mode alsa SonicMaster subwoofer doesn't work
** Description changed: I expect my subwoofer working when choosing ALSA 2.1 in VLC audio settings, but in fact it doesn't sound at all + Also headphones AlsaMixer shows BassSpeaker, but changing it's volume has no effect Also I tried the trick described in similar bug I found(https://bugs.launchpad.net/ubuntu/+source/alsa-tools/+bug/1405691, https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/871808) with hdajackretask with pin 0x1a as LFE and hda_analyzer - no effect though - System Kubuntu - Description:Ubuntu 17.10 - Release:17.10 - - alsaplayer-alsa: - Установлен: (отсутствует) - Кандидат: 0.99.81-2 - Таблица версий: - 0.99.81-2 500 - 500 http://ru.archive.ubuntu.com/ubuntu artful/universe amd64 Packages - alsa-base: - Установлен: 1.0.25+dfsg-0ubuntu5 - Кандидат: 1.0.25+dfsg-0ubuntu5 - Таблица версий: - *** 1.0.25+dfsg-0ubuntu5 500 - 500 http://ru.archive.ubuntu.com/ubuntu artful/main amd64 Packages - 500 http://ru.archive.ubuntu.com/ubuntu artful/main i386 Packages - 100 /var/lib/dpkg/status - alsa-source: - Установлен: (отсутствует) - Кандидат: 1.0.25+dfsg-0ubuntu5 - Таблица версий: - 1.0.25+dfsg-0ubuntu5 500 - 500 http://ru.archive.ubuntu.com/ubuntu artful/universe amd64 Packages - 500 http://ru.archive.ubuntu.com/ubuntu artful/universe i386 Packages - alsamixergui: - Установлен: 0.9.0rc2-1-10 - Кандидат: 0.9.0rc2-1-10 - Таблица версий: - *** 0.9.0rc2-1-10 500 - 500 http://ru.archive.ubuntu.com/ubuntu artful/universe amd64 Packages - 100 /var/lib/dpkg/status - alsaplayer-output: - Установлен: (отсутствует) - Кандидат: (отсутствует) - Таблица версий: - alsaplayer: - Установлен: (отсутствует) - Кандидат: (отсутствует) - Таблица версий: - alsaplayer-jack: - Установлен: (отсутствует) - Кандидат: 0.99.81-2 - Таблица версий: - 0.99.81-2 500 - 500 http://ru.archive.ubuntu.com/ubuntu artful/universe amd64 Packages - alsaplayer-common: - Установлен: (отсутствует) - Кандидат: 0.99.81-2 - Таблица версий: - 0.99.81-2 500 - 500 http://ru.archive.ubuntu.com/ubuntu artful/universe amd64 Packages - alsa: - Установлен: (отсутствует) - Кандидат: (отсутствует) - Таблица версий: - alsaplayer-esd: - Установлен: (отсутствует) - Кандидат: (отсутствует) - Таблица версий: - alsaplayer-gtk: - Установлен: (отсутствует) - Кандидат: 0.99.81-2 - Таблица версий: - 0.99.81-2 500 - 500 http://ru.archive.ubuntu.com/ubuntu artful/universe amd64 Packages - alsa-utils: - Установлен: 1.1.3-1ubuntu1 - Кандидат: 1.1.3-1ubuntu1 - Таблица версий: - *** 1.1.3-1ubuntu1 500 - 500 http://ru.archive.ubuntu.com/ubuntu artful/main amd64 Packages - 100 /var/lib/dpkg/status - alsaplayer-text: - Установлен: (отсутствует) - Кандидат: 0.99.81-2 - Таблица версий: - 0.99.81-2 500 - 500 http://ru.archive.ubuntu.com/ubuntu artful/universe amd64 Packages - alsa-firmware-loaders: - Установлен: (отсутствует) - Кандидат: 1.1.3-1 - Таблица версий: - 1.1.3-1 500 - 500 http://ru.archive.ubuntu.com/ubuntu artful/multiverse amd64 Packages - alsaplayer-xosd: - Установлен: (отсутствует) - Кандидат: 0.99.81-2 - Таблица версий: - 0.99.81-2 500 - 500 http://ru.archive.ubuntu.com/ubuntu artful/universe amd64 Packages - alsa-tools: - Установлен: 1.1.3-1 - Кандидат: 1.1.3-1 - Таблица версий: - *** 1.1.3-1 500 - 500 http://ru.archive.ubuntu.com/ubuntu artful/universe amd64 Packages - 100 /var/lib/dpkg/status - alsaplayer-nas: - Установлен: (отсутствует) - Кандидат: 0.99.81-2 - Таблица версий: - 0.99.81-2 500 - 500 http://ru.archive.ubuntu.com/ubuntu artful/universe amd64 Packages - alsaplayer-oss: - Установлен: (отсутствует) - Кандидат: 0.99.81-2 - Таблица версий: - 0.99.81-2 500 - 500 http://ru.archive.ubuntu.com/ubuntu artful/universe amd64 Packages - alsaplayer-interface: - Установлен: (отсутствует) - Кандидат: (отсутствует) - Таблица версий: - alsaplayer-daemon: - Установлен: (отсутствует) - Кандидат: 0.99.81-2 - Таблица версий: - 0.99.81-2 500 - 500 http://ru.archive.ubuntu.com/ubuntu artful/universe amd64 Packages - alsa-tools-gui: - Установлен: 1.1.3-1 - Кандидат: 1.1.3-1 - Таблица версий: - *** 1.1.3-1 500 - 500 http://ru.archive.ubuntu.com/ubuntu artful/universe amd64 Packages - 100 /var/lib/dpkg/status - alsa-oss: - Установлен: (отсутствует) - Кандидат: 1.0.28-1ubuntu1 - Таблица версий: - 1.0.28-1ubuntu1 500 - 500 http://ru.archive.ubuntu.com/ubuntu artful/universe amd64 Packages + Debug info + http://www.alsa-project.org/db/?f=b5e564ec981f30eee9346a791fb0f51874e23b59 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu.
[Desktop-packages] [Bug 1733029] Re: Asus N55JM headphones don't work
** Summary changed: - Asus N55JM in 2.1 mode alsa SonicMaster subwoofer doesn't work + Asus N55JM headphones don't work -- 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/1733029 Title: Asus N55JM headphones don't work Status in alsa-driver package in Ubuntu: New Bug description: I USE ASUS N55JM with ALC668 onboard I expect to hear sound from headphones if it's plugged in, at least in parallel with speakers. But I can't set it up. Also I expect my subwoofer working when choosing ALSA and 2.1 mode in VLC audio settings, but in fact it doesn't sound at all I tried the trick described in similar bug I found(https://bugs.launchpad.net/ubuntu/+source/alsa- tools/+bug/1405691, https://bugs.launchpad.net/ubuntu/+source/alsa- driver/+bug/871808) with hdajackretask with pin 0x1a as LFE and hda_analyzer - no effect though Debug info http://www.alsa-project.org/db/?f=b5e564ec981f30eee9346a791fb0f51874e23b59 Actually I even can see right pin detection sudo hdajacksensetest -c 1 -a Pin 0x12 (Internal Mic): present = No Pin 0x14 (Internal Speaker): present = No Pin 0x15 (Black Headphone, Right side): present = Yes Pin 0x16 (Not connected): present = No Pin 0x18 (Not connected): present = No Pin 0x19 (Pink Mic, Left side): present = No Pin 0x1a (Internal Speaker): present = Yes Pin 0x1b (Black Mic, Left side): present = No Pin 0x1d (Not connected): present = No Pin 0x1e (Not connected): present = No Pin 0x1f (Not connected): present = No I see 0x15 - Headphone pin, 0x1a - subwoofer. But I can't make sound headphones nor subwoofer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1733029/+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 1733029] Re: Asus N55JM headphones don't work
** Description changed: - I expect my subwoofer working when choosing ALSA 2.1 in VLC audio settings, but in fact it doesn't sound at all - Also headphones - AlsaMixer shows BassSpeaker, but changing it's volume has no effect - Also I tried the trick described in similar bug I found(https://bugs.launchpad.net/ubuntu/+source/alsa-tools/+bug/1405691, https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/871808) with hdajackretask with pin 0x1a as LFE and hda_analyzer - no effect though + I USE ASUS N55JM with ALC668 onboard + I expect to hear sound from headphones if it's plugged in, at least in parallel with speakers. But I can't set it up. + + Also I expect my subwoofer working when choosing ALSA and 2.1 mode in + VLC audio settings, but in fact it doesn't sound at all + + I tried the trick described in similar bug I + found(https://bugs.launchpad.net/ubuntu/+source/alsa-tools/+bug/1405691, + https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/871808) with + hdajackretask with pin 0x1a as LFE and hda_analyzer - no effect though Debug info http://www.alsa-project.org/db/?f=b5e564ec981f30eee9346a791fb0f51874e23b59 + + Actually I even can see right pin detection + sudo hdajacksensetest -c 1 -a + Pin 0x12 (Internal Mic): present = No + Pin 0x14 (Internal Speaker): present = No + Pin 0x15 (Black Headphone, Right side): present = Yes + Pin 0x16 (Not connected): present = No + Pin 0x18 (Not connected): present = No + Pin 0x19 (Pink Mic, Left side): present = No + Pin 0x1a (Internal Speaker): present = Yes + Pin 0x1b (Black Mic, Left side): present = No + Pin 0x1d (Not connected): present = No + Pin 0x1e (Not connected): present = No + Pin 0x1f (Not connected): present = No + + I see 0x15 - Headphone pin, 0x1a - subwoofer. + But I can't make sound headphones nor subwoofer -- 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/1733029 Title: Asus N55JM headphones don't work Status in alsa-driver package in Ubuntu: New Bug description: I USE ASUS N55JM with ALC668 onboard I expect to hear sound from headphones if it's plugged in, at least in parallel with speakers. But I can't set it up. Also I expect my subwoofer working when choosing ALSA and 2.1 mode in VLC audio settings, but in fact it doesn't sound at all I tried the trick described in similar bug I found(https://bugs.launchpad.net/ubuntu/+source/alsa- tools/+bug/1405691, https://bugs.launchpad.net/ubuntu/+source/alsa- driver/+bug/871808) with hdajackretask with pin 0x1a as LFE and hda_analyzer - no effect though Debug info http://www.alsa-project.org/db/?f=b5e564ec981f30eee9346a791fb0f51874e23b59 Actually I even can see right pin detection sudo hdajacksensetest -c 1 -a Pin 0x12 (Internal Mic): present = No Pin 0x14 (Internal Speaker): present = No Pin 0x15 (Black Headphone, Right side): present = Yes Pin 0x16 (Not connected): present = No Pin 0x18 (Not connected): present = No Pin 0x19 (Pink Mic, Left side): present = No Pin 0x1a (Internal Speaker): present = Yes Pin 0x1b (Black Mic, Left side): present = No Pin 0x1d (Not connected): present = No Pin 0x1e (Not connected): present = No Pin 0x1f (Not connected): present = No I see 0x15 - Headphone pin, 0x1a - subwoofer. But I can't make sound headphones nor subwoofer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1733029/+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 1666681] Re: Drop interactive_search.patch (type-ahead search)
For me it's very annoying. I migrated from Ubuntu 17.04 to 17.10 several days before, and just cant use nautilus. I'm using this type-ahead feature for navigate. At the beginning i tried to switch off recursive search in nautilus to speedup it. But when i want to use recursive search i should go to the setting and switching it on again. I even tried to replace nautilus with another file manager, but gnome can't showing desktop items without nautilus. Why type-ahead can't exists as optional setting? Type-ahead still works in open/save dialogs, why it can't be in nautilus? -- 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/181 Title: Drop interactive_search.patch (type-ahead search) Status in nautilus package in Ubuntu: Confirmed Bug description: Nautilus dropped the popular type-ahead search feature years ago. Ubuntu has been carrying a patch to revert that change. See bug 1164016 for the original LP bug and patch proposal. Nautilus is now under very active development. During the 3.22 cycle, that patch needed to be rebased. I tried to do it and what I came up with caused a crash (it didn't really crash for me, but ricotz and some others experienced it) and the first letter typed activated type- ahead search but the first letter was dropped. In other words, you would need to type "ddow" to activate the Downloads folder instead of just "dow" like in previous releases. (LP: #1635988) I did that rebase in October 2016 and no one has stepped up then to improve the patch. The Nautilus maintainer csoriano has said that the slots and views changed significantly during 3.22 and will likely be refactored more in the future. If there's no one available to maintain the patch, unfortunately, we'll eventually have to drop the patch to not be stuck on an ancient version of Nautilus. I am proposing that we do this at the start of the 17.10 development cycle. This gives 6 months for a developer to step up and try to fix the patch and 12 months before 18.04 LTS. Other Items === - For better performance with the built-in search, we need to reconsider avoiding tracker in Unity (LP: #176) - There is an option in Preferences for users to disable searching in subfolders. I don't think we want to do that by default but maybe it can help some people. The current Nautilus 3.24 packaging is in the GNOME3 Staging PPA with this patch now disabled. https://launchpad.net/~gnome3-team/+archive/ubuntu/gnome3-staging/+packages?field.series_filter=zesty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/181/+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 1302416] Re: deja-dup monitor was taking 6GB of memory
Ubuntu 18.04 htop write about 94G virtual memory usage by deja-dup-monitor Of course I haven't so enough. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1302416 Title: deja-dup monitor was taking 6GB of memory Status in Déjà Dup: New Status in deja-dup package in Ubuntu: Confirmed Status in deja-dup package in Debian: New Bug description: Booted fresh, computer started to be slow and after a while i realized deja-dup monitor was taking 6GB of memory. Haven't tried rebooted again. Will do so in a moment. Sorry can't provide more info :/ ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: deja-dup 30.0-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 Uname: Linux 3.13.0-22-generic x86_64 ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 4 09:40:07 2014 InstallationDate: Installed on 2011-11-21 (864 days ago) InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) ProcEnviron: LANGUAGE=ca_ES TERM=xterm PATH=(custom, no user) LANG=ca_ES.UTF-8 SHELL=/bin/bash SourcePackage: deja-dup UpgradeStatus: Upgraded to trusty on 2012-02-27 (766 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1302416/+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 527157] Re: Brightness controls skips Levels.
Why are you guys marking the g-p-m bug invalid? Because see previous comments. g-s-d handles media keys. This bug is appeared, because we have a case, when g-s-d should handle brightness keys differently. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/527157 Title: Brightness controls skips Levels. Status in Gnome Settings Daemon: New Status in “gnome-power-manager” package in Ubuntu: Invalid Status in “gnome-power-manager” package in Arch Linux: New Bug description: Binary package hint: gnome-power-manager Expected: Hitting brightness up key or brightness down key changes brightness by one level out of 15. Actual: Hitting brightness up key or brightness down key changes brightness by two or three levels out of 15. When I use the brightness control keys from a fresh install, the brightness jumps THREE increments. By creating /etc/modprobe.d/video.conf and setting options video brightness_switch_enabled = 0 I reduce this to consistently TWO brightness events, but this is still double the normal events. If I kill gnome-power-manager, it returns to single brightness events. when hitting brightness up/down with gnome-power-manager, udevmonitor shows UDEV - the event which udev sends out after rule processing KERNEL - the kernel uevent KERNEL[1267026969.897008] change /devices/virtual/backlight/acpi_video0 (backlight) UDEV [1267026969.898270] change /devices/virtual/backlight/acpi_video0 (backlight) KERNEL[1267026969.903078] change /devices/virtual/backlight/acpi_video0 (backlight) UDEV [1267026969.903842] change /devices/virtual/backlight/acpi_video0 (backlight) KERNEL[1267026971.355970] change /devices/virtual/backlight/acpi_video0 (backlight) UDEV [1267026971.357418] change /devices/virtual/backlight/acpi_video0 (backlight) with gnome-power-manager not running, it shows no events. Before: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 25 Brightness up pressed: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 40 With options video brightness_switch_enabled = 0: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 25 Brightness up pressed: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 35 With brightness_switch_enabled=0 and gnome-power-manager not running: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 25 Brightness up pressed: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 30 Description: Ubuntu lucid (development branch) Release: 10.04 xserver-xorg-video-intel: Installed: 2:2.9.1-1ubuntu1 Candidate: 2:2.9.1-1ubuntu1 Version table: *** 2:2.9.1-1ubuntu1 0 500 http://archive.linux.duke.edu lucid/main Packages 100 /var/lib/dpkg/status gnome-power-manager: Installed: 2.29.1-0ubuntu2 Candidate: 2.29.1-0ubuntu2 Version table: *** 2.29.1-0ubuntu2 0 500 http://archive.linux.duke.edu lucid/main Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/527157/+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 835972] Re: after resume the Disconnected - you are now offline notification doesn't disappear
I'm using Xubuntu 11.10 and confirm that the bug still exists. All notifications disappear but notifications from network-manager after resume. I am not such a big professional in building packages and I think I'm not the only one. So can someone build network-manager with patches lp341684 and lp358526 and publish it in ppa just to let us check the problem is solved? -- 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/835972 Title: after resume the Disconnected - you are now offline notification doesn't disappear Status in “network-manager-applet” package in Ubuntu: Confirmed Status in “xfce4-notifyd” package in Ubuntu: Confirmed Bug description: Observed behaviour: When I resume from standby, the Disconnected - you are now offline notification (which probably appeared when standby was started) stays on the screen and doesn't go away until I close it manually. Network (LAN - eth0) works, so in fact I'm online and the notification is false. Notifications are set to disappear after 4 seconds, which they do, except this naughty one. Expected behaviour: The Disconnected - you are now offline notification should not appear or disappear after the selected amount of time. The best thing would be to display a Connected - you are now online notification. used version: 0.2.1-1 on Xubuntu Natty (all updates up to date) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/835972/+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 885730] Re: keyboard layout indicator reacts incorrectly
Please, fix it. -- 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/885730 Title: keyboard layout indicator reacts incorrectly Status in Gnome Settings Daemon: Invalid Status in Ubuntu network, Bluetooth, keyboard menus: Confirmed Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Bug description: Hi there, there are few bug reports similar to this one but from their description I feel like this is a little different. I use three different keyboard layouts, switching between them with shortcut and having Allow different layouts for individual windows option enabled. In this configuration layout switch should be processed when shortcut is triggered or when I switch to another window. Moreover to switch layout means two things. Firstly it means to switch keyboard mappings themself and secondly to change what layout indicator shows. The problem itself: mappings which is used is often not the same as indicator shows. I experimented a little to find out what is wrong and now I see that the mistake is in processing switch-window event which always changes mappings used but doesn't refresh what indicator is showing... Sometimes it's quite annoying as nearly all bugs reported here :) This is my first bug report ever so correct me or reguest mroe info if I have fogotten something. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-settings-daemon 3.2.0-0ubuntu5 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: Thu Nov 3 16:11:18 2011 InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release i386 (20100816.1) SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to oneiric on 2011-10-20 (14 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/885730/+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 527157] Re: Brightness controls skips Levels.
Oh yeah! #24 is really dirty one! But it gave me a clue, how this bug should be fixed: Patching StepUp/StepDown handlers is very bad practice, because these methods may be called by some other applications. We need to prevent calls to these methods depending on some parameter. The problem itself: bios changes brightness on keypress and reports acpi keypress event, instead of just reporting event (this might be fixable in DSDT), then some process handles this event and issues dbus calls to org.gnome.SettingsDaemon.Power.Screen.StepUp/StepDown methods. Then g-p-m changes brightness too; g-p-m has no ways to determine, whether it should change brightness when handling StepUp/StepDown dbus calls, or not. Neither 'some process' do. The solution, how I see it: find code, which handles acpi keypresses (that's not g-p-m, g-s-d may be?) and add user-changeable option there to disable acpi brightness keypresses handle (e.g. gconf parameter). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/527157 Title: Brightness controls skips Levels. Status in “gnome-power-manager” package in Ubuntu: Triaged Status in “gnome-power-manager” package in Arch Linux: New Bug description: Binary package hint: gnome-power-manager Expected: Hitting brightness up key or brightness down key changes brightness by one level out of 15. Actual: Hitting brightness up key or brightness down key changes brightness by two or three levels out of 15. When I use the brightness control keys from a fresh install, the brightness jumps THREE increments. By creating /etc/modprobe.d/video.conf and setting options video brightness_switch_enabled = 0 I reduce this to consistently TWO brightness events, but this is still double the normal events. If I kill gnome-power-manager, it returns to single brightness events. when hitting brightness up/down with gnome-power-manager, udevmonitor shows UDEV - the event which udev sends out after rule processing KERNEL - the kernel uevent KERNEL[1267026969.897008] change /devices/virtual/backlight/acpi_video0 (backlight) UDEV [1267026969.898270] change /devices/virtual/backlight/acpi_video0 (backlight) KERNEL[1267026969.903078] change /devices/virtual/backlight/acpi_video0 (backlight) UDEV [1267026969.903842] change /devices/virtual/backlight/acpi_video0 (backlight) KERNEL[1267026971.355970] change /devices/virtual/backlight/acpi_video0 (backlight) UDEV [1267026971.357418] change /devices/virtual/backlight/acpi_video0 (backlight) with gnome-power-manager not running, it shows no events. Before: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 25 Brightness up pressed: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 40 With options video brightness_switch_enabled = 0: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 25 Brightness up pressed: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 35 With brightness_switch_enabled=0 and gnome-power-manager not running: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 25 Brightness up pressed: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 30 Description: Ubuntu lucid (development branch) Release: 10.04 xserver-xorg-video-intel: Installed: 2:2.9.1-1ubuntu1 Candidate: 2:2.9.1-1ubuntu1 Version table: *** 2:2.9.1-1ubuntu1 0 500 http://archive.linux.duke.edu lucid/main Packages 100 /var/lib/dpkg/status gnome-power-manager: Installed: 2.29.1-0ubuntu2 Candidate: 2.29.1-0ubuntu2 Version table: *** 2.29.1-0ubuntu2 0 500 http://archive.linux.duke.edu lucid/main Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/527157/+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 527157] Re: Brightness controls skips Levels.
I would change status on g-p-m to 'Invalid' and assign bug to other package. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/527157 Title: Brightness controls skips Levels. Status in “gnome-power-manager” package in Ubuntu: Triaged Status in “gnome-power-manager” package in Arch Linux: New Bug description: Binary package hint: gnome-power-manager Expected: Hitting brightness up key or brightness down key changes brightness by one level out of 15. Actual: Hitting brightness up key or brightness down key changes brightness by two or three levels out of 15. When I use the brightness control keys from a fresh install, the brightness jumps THREE increments. By creating /etc/modprobe.d/video.conf and setting options video brightness_switch_enabled = 0 I reduce this to consistently TWO brightness events, but this is still double the normal events. If I kill gnome-power-manager, it returns to single brightness events. when hitting brightness up/down with gnome-power-manager, udevmonitor shows UDEV - the event which udev sends out after rule processing KERNEL - the kernel uevent KERNEL[1267026969.897008] change /devices/virtual/backlight/acpi_video0 (backlight) UDEV [1267026969.898270] change /devices/virtual/backlight/acpi_video0 (backlight) KERNEL[1267026969.903078] change /devices/virtual/backlight/acpi_video0 (backlight) UDEV [1267026969.903842] change /devices/virtual/backlight/acpi_video0 (backlight) KERNEL[1267026971.355970] change /devices/virtual/backlight/acpi_video0 (backlight) UDEV [1267026971.357418] change /devices/virtual/backlight/acpi_video0 (backlight) with gnome-power-manager not running, it shows no events. Before: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 25 Brightness up pressed: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 40 With options video brightness_switch_enabled = 0: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 25 Brightness up pressed: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 35 With brightness_switch_enabled=0 and gnome-power-manager not running: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 25 Brightness up pressed: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 30 Description: Ubuntu lucid (development branch) Release: 10.04 xserver-xorg-video-intel: Installed: 2:2.9.1-1ubuntu1 Candidate: 2:2.9.1-1ubuntu1 Version table: *** 2:2.9.1-1ubuntu1 0 500 http://archive.linux.duke.edu lucid/main Packages 100 /var/lib/dpkg/status gnome-power-manager: Installed: 2.29.1-0ubuntu2 Candidate: 2.29.1-0ubuntu2 Version table: *** 2.29.1-0ubuntu2 0 500 http://archive.linux.duke.edu lucid/main Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/527157/+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 527157] Re: Brightness controls skips Levels.
James: no, there is no need to touch kernel. You should have noticed, that brightness control works as expected, before you login (during boot or even on login screen). Problem is in user-level process running during user session. We have to find that process, than fix will be pretty simple. See plugins/media-keys/gsd-media-keys-manager.c:1528, function do_screen_brightness_action_real(): looks like it is correct place for patch. Later I will think on good solution. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/527157 Title: Brightness controls skips Levels. Status in “gnome-power-manager” package in Ubuntu: Triaged Status in “gnome-power-manager” package in Arch Linux: New Bug description: Binary package hint: gnome-power-manager Expected: Hitting brightness up key or brightness down key changes brightness by one level out of 15. Actual: Hitting brightness up key or brightness down key changes brightness by two or three levels out of 15. When I use the brightness control keys from a fresh install, the brightness jumps THREE increments. By creating /etc/modprobe.d/video.conf and setting options video brightness_switch_enabled = 0 I reduce this to consistently TWO brightness events, but this is still double the normal events. If I kill gnome-power-manager, it returns to single brightness events. when hitting brightness up/down with gnome-power-manager, udevmonitor shows UDEV - the event which udev sends out after rule processing KERNEL - the kernel uevent KERNEL[1267026969.897008] change /devices/virtual/backlight/acpi_video0 (backlight) UDEV [1267026969.898270] change /devices/virtual/backlight/acpi_video0 (backlight) KERNEL[1267026969.903078] change /devices/virtual/backlight/acpi_video0 (backlight) UDEV [1267026969.903842] change /devices/virtual/backlight/acpi_video0 (backlight) KERNEL[1267026971.355970] change /devices/virtual/backlight/acpi_video0 (backlight) UDEV [1267026971.357418] change /devices/virtual/backlight/acpi_video0 (backlight) with gnome-power-manager not running, it shows no events. Before: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 25 Brightness up pressed: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 40 With options video brightness_switch_enabled = 0: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 25 Brightness up pressed: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 35 With brightness_switch_enabled=0 and gnome-power-manager not running: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 25 Brightness up pressed: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 30 Description: Ubuntu lucid (development branch) Release: 10.04 xserver-xorg-video-intel: Installed: 2:2.9.1-1ubuntu1 Candidate: 2:2.9.1-1ubuntu1 Version table: *** 2:2.9.1-1ubuntu1 0 500 http://archive.linux.duke.edu lucid/main Packages 100 /var/lib/dpkg/status gnome-power-manager: Installed: 2.29.1-0ubuntu2 Candidate: 2.29.1-0ubuntu2 Version table: *** 2.29.1-0ubuntu2 0 500 http://archive.linux.duke.edu lucid/main Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/527157/+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 527157] Re: Brightness controls skips Levels.
Oh, that was about g-s-d source! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/527157 Title: Brightness controls skips Levels. Status in “gnome-power-manager” package in Ubuntu: Triaged Status in “gnome-power-manager” package in Arch Linux: New Bug description: Binary package hint: gnome-power-manager Expected: Hitting brightness up key or brightness down key changes brightness by one level out of 15. Actual: Hitting brightness up key or brightness down key changes brightness by two or three levels out of 15. When I use the brightness control keys from a fresh install, the brightness jumps THREE increments. By creating /etc/modprobe.d/video.conf and setting options video brightness_switch_enabled = 0 I reduce this to consistently TWO brightness events, but this is still double the normal events. If I kill gnome-power-manager, it returns to single brightness events. when hitting brightness up/down with gnome-power-manager, udevmonitor shows UDEV - the event which udev sends out after rule processing KERNEL - the kernel uevent KERNEL[1267026969.897008] change /devices/virtual/backlight/acpi_video0 (backlight) UDEV [1267026969.898270] change /devices/virtual/backlight/acpi_video0 (backlight) KERNEL[1267026969.903078] change /devices/virtual/backlight/acpi_video0 (backlight) UDEV [1267026969.903842] change /devices/virtual/backlight/acpi_video0 (backlight) KERNEL[1267026971.355970] change /devices/virtual/backlight/acpi_video0 (backlight) UDEV [1267026971.357418] change /devices/virtual/backlight/acpi_video0 (backlight) with gnome-power-manager not running, it shows no events. Before: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 25 Brightness up pressed: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 40 With options video brightness_switch_enabled = 0: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 25 Brightness up pressed: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 35 With brightness_switch_enabled=0 and gnome-power-manager not running: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 25 Brightness up pressed: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 30 Description: Ubuntu lucid (development branch) Release: 10.04 xserver-xorg-video-intel: Installed: 2:2.9.1-1ubuntu1 Candidate: 2:2.9.1-1ubuntu1 Version table: *** 2:2.9.1-1ubuntu1 0 500 http://archive.linux.duke.edu lucid/main Packages 100 /var/lib/dpkg/status gnome-power-manager: Installed: 2.29.1-0ubuntu2 Candidate: 2.29.1-0ubuntu2 Version table: *** 2.29.1-0ubuntu2 0 500 http://archive.linux.duke.edu lucid/main Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/527157/+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 527157] Re: Brightness controls skips Levels.
** Changed in: gnome-power-manager (Ubuntu) Status: Triaged = Invalid ** Also affects: gnome-settings-daemon Importance: Undecided Status: New ** Changed in: gnome-settings-daemon Assignee: (unassigned) = Dmitriy Geels (dmig) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/527157 Title: Brightness controls skips Levels. Status in Gnome Settings Daemon: New Status in “gnome-power-manager” package in Ubuntu: Invalid Status in “gnome-power-manager” package in Arch Linux: New Bug description: Binary package hint: gnome-power-manager Expected: Hitting brightness up key or brightness down key changes brightness by one level out of 15. Actual: Hitting brightness up key or brightness down key changes brightness by two or three levels out of 15. When I use the brightness control keys from a fresh install, the brightness jumps THREE increments. By creating /etc/modprobe.d/video.conf and setting options video brightness_switch_enabled = 0 I reduce this to consistently TWO brightness events, but this is still double the normal events. If I kill gnome-power-manager, it returns to single brightness events. when hitting brightness up/down with gnome-power-manager, udevmonitor shows UDEV - the event which udev sends out after rule processing KERNEL - the kernel uevent KERNEL[1267026969.897008] change /devices/virtual/backlight/acpi_video0 (backlight) UDEV [1267026969.898270] change /devices/virtual/backlight/acpi_video0 (backlight) KERNEL[1267026969.903078] change /devices/virtual/backlight/acpi_video0 (backlight) UDEV [1267026969.903842] change /devices/virtual/backlight/acpi_video0 (backlight) KERNEL[1267026971.355970] change /devices/virtual/backlight/acpi_video0 (backlight) UDEV [1267026971.357418] change /devices/virtual/backlight/acpi_video0 (backlight) with gnome-power-manager not running, it shows no events. Before: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 25 Brightness up pressed: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 40 With options video brightness_switch_enabled = 0: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 25 Brightness up pressed: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 35 With brightness_switch_enabled=0 and gnome-power-manager not running: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 25 Brightness up pressed: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 30 Description: Ubuntu lucid (development branch) Release: 10.04 xserver-xorg-video-intel: Installed: 2:2.9.1-1ubuntu1 Candidate: 2:2.9.1-1ubuntu1 Version table: *** 2:2.9.1-1ubuntu1 0 500 http://archive.linux.duke.edu lucid/main Packages 100 /var/lib/dpkg/status gnome-power-manager: Installed: 2.29.1-0ubuntu2 Candidate: 2.29.1-0ubuntu2 Version table: *** 2.29.1-0ubuntu2 0 500 http://archive.linux.duke.edu lucid/main Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/527157/+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 527157] Re: Brightness controls skips Levels.
Fix itself is pretty simple, but all that g/dconf mess confuses me. Need to understand, how to create new key in dconf... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/527157 Title: Brightness controls skips Levels. Status in Gnome Settings Daemon: New Status in “gnome-power-manager” package in Ubuntu: Invalid Status in “gnome-power-manager” package in Arch Linux: New Bug description: Binary package hint: gnome-power-manager Expected: Hitting brightness up key or brightness down key changes brightness by one level out of 15. Actual: Hitting brightness up key or brightness down key changes brightness by two or three levels out of 15. When I use the brightness control keys from a fresh install, the brightness jumps THREE increments. By creating /etc/modprobe.d/video.conf and setting options video brightness_switch_enabled = 0 I reduce this to consistently TWO brightness events, but this is still double the normal events. If I kill gnome-power-manager, it returns to single brightness events. when hitting brightness up/down with gnome-power-manager, udevmonitor shows UDEV - the event which udev sends out after rule processing KERNEL - the kernel uevent KERNEL[1267026969.897008] change /devices/virtual/backlight/acpi_video0 (backlight) UDEV [1267026969.898270] change /devices/virtual/backlight/acpi_video0 (backlight) KERNEL[1267026969.903078] change /devices/virtual/backlight/acpi_video0 (backlight) UDEV [1267026969.903842] change /devices/virtual/backlight/acpi_video0 (backlight) KERNEL[1267026971.355970] change /devices/virtual/backlight/acpi_video0 (backlight) UDEV [1267026971.357418] change /devices/virtual/backlight/acpi_video0 (backlight) with gnome-power-manager not running, it shows no events. Before: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 25 Brightness up pressed: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 40 With options video brightness_switch_enabled = 0: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 25 Brightness up pressed: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 35 With brightness_switch_enabled=0 and gnome-power-manager not running: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 25 Brightness up pressed: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 30 Description: Ubuntu lucid (development branch) Release: 10.04 xserver-xorg-video-intel: Installed: 2:2.9.1-1ubuntu1 Candidate: 2:2.9.1-1ubuntu1 Version table: *** 2:2.9.1-1ubuntu1 0 500 http://archive.linux.duke.edu lucid/main Packages 100 /var/lib/dpkg/status gnome-power-manager: Installed: 2.29.1-0ubuntu2 Candidate: 2.29.1-0ubuntu2 Version table: *** 2.29.1-0ubuntu2 0 500 http://archive.linux.duke.edu lucid/main Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/527157/+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 972494] Re: New mobile broadband connection (KZ)
** Also affects: network-manager Importance: Undecided Status: New ** No longer affects: network-manager -- 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/972494 Title: New mobile broadband connection (KZ) Status in “network-manager” package in Ubuntu: New Bug description: In Kazakhstan, the brand of NEO is no longer used. Instead, brand is Tele2. Change to a new name, please. http://img7.imagebanana.com/img/wjr5ppel/20120403194717.png Pruf links: 1) http://www.tele2.com/news-article.html?id=295 2) http://en.wikipedia.org/wiki/Tele2#Kazakhstan 3) http://www.pavlodar.tele2.kz/ru/ gn@gn-desktop:~$ lsb_release -rd Description: Ubuntu precise (development branch) Release: 12.04 gn@gn-desktop:~$ uname -a Linux gn-desktop 3.2.0-21-generic #34-Ubuntu SMP Fri Mar 30 04:25:35 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux beta2 64bit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/972494/+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 527157] Re: Brightness controls skips Levels.
In order for this patch to apply properly, it should be applied last, after all ubuntu patches. In you case you don't have any of them applied. If you got package from packages.ubuntu.com, there are 2 source files: one http://archive.ubuntu.com/ubuntu/pool/main/g/gnome-settings-daemon /gnome-settings-daemon_3.2.0.orig.tar.bz2 -- source itself, second -- http://archive.ubuntu.com/ubuntu/pool/main/g/gnome-settings-daemon /gnome-settings-daemon_3.2.0-0ubuntu5.debian.tar.gz -- all patches. I see that I need to make patch independent of theese ubuntu changes. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/527157 Title: Brightness controls skips Levels. Status in Gnome Settings Daemon: New Status in “gnome-power-manager” package in Ubuntu: Invalid Status in “gnome-power-manager” package in Arch Linux: New Bug description: Binary package hint: gnome-power-manager Expected: Hitting brightness up key or brightness down key changes brightness by one level out of 15. Actual: Hitting brightness up key or brightness down key changes brightness by two or three levels out of 15. When I use the brightness control keys from a fresh install, the brightness jumps THREE increments. By creating /etc/modprobe.d/video.conf and setting options video brightness_switch_enabled = 0 I reduce this to consistently TWO brightness events, but this is still double the normal events. If I kill gnome-power-manager, it returns to single brightness events. when hitting brightness up/down with gnome-power-manager, udevmonitor shows UDEV - the event which udev sends out after rule processing KERNEL - the kernel uevent KERNEL[1267026969.897008] change /devices/virtual/backlight/acpi_video0 (backlight) UDEV [1267026969.898270] change /devices/virtual/backlight/acpi_video0 (backlight) KERNEL[1267026969.903078] change /devices/virtual/backlight/acpi_video0 (backlight) UDEV [1267026969.903842] change /devices/virtual/backlight/acpi_video0 (backlight) KERNEL[1267026971.355970] change /devices/virtual/backlight/acpi_video0 (backlight) UDEV [1267026971.357418] change /devices/virtual/backlight/acpi_video0 (backlight) with gnome-power-manager not running, it shows no events. Before: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 25 Brightness up pressed: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 40 With options video brightness_switch_enabled = 0: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 25 Brightness up pressed: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 35 With brightness_switch_enabled=0 and gnome-power-manager not running: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 25 Brightness up pressed: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 30 Description: Ubuntu lucid (development branch) Release: 10.04 xserver-xorg-video-intel: Installed: 2:2.9.1-1ubuntu1 Candidate: 2:2.9.1-1ubuntu1 Version table: *** 2:2.9.1-1ubuntu1 0 500 http://archive.linux.duke.edu lucid/main Packages 100 /var/lib/dpkg/status gnome-power-manager: Installed: 2.29.1-0ubuntu2 Candidate: 2.29.1-0ubuntu2 Version table: *** 2.29.1-0ubuntu2 0 500 http://archive.linux.duke.edu lucid/main Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/527157/+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 527157] Re: Brightness controls skips Levels.
Patch 16_use_synchronous_notifications.patch -- is the one, that my patch heavily depends on. Also, as far, as I understand, it's incompatible with debian. To make patch for debian, I need to understand, where to get correct params for update_screen_cb(), to call it from do_screen_brightness_action(). You can try to help with this, see plugins/media-keys/gsd-media-keys- manager.c.rej -- second piece from there must be inside do_screen_brightness_action(). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/527157 Title: Brightness controls skips Levels. Status in Gnome Settings Daemon: New Status in “gnome-power-manager” package in Ubuntu: Invalid Status in “gnome-power-manager” package in Arch Linux: New Bug description: Binary package hint: gnome-power-manager Expected: Hitting brightness up key or brightness down key changes brightness by one level out of 15. Actual: Hitting brightness up key or brightness down key changes brightness by two or three levels out of 15. When I use the brightness control keys from a fresh install, the brightness jumps THREE increments. By creating /etc/modprobe.d/video.conf and setting options video brightness_switch_enabled = 0 I reduce this to consistently TWO brightness events, but this is still double the normal events. If I kill gnome-power-manager, it returns to single brightness events. when hitting brightness up/down with gnome-power-manager, udevmonitor shows UDEV - the event which udev sends out after rule processing KERNEL - the kernel uevent KERNEL[1267026969.897008] change /devices/virtual/backlight/acpi_video0 (backlight) UDEV [1267026969.898270] change /devices/virtual/backlight/acpi_video0 (backlight) KERNEL[1267026969.903078] change /devices/virtual/backlight/acpi_video0 (backlight) UDEV [1267026969.903842] change /devices/virtual/backlight/acpi_video0 (backlight) KERNEL[1267026971.355970] change /devices/virtual/backlight/acpi_video0 (backlight) UDEV [1267026971.357418] change /devices/virtual/backlight/acpi_video0 (backlight) with gnome-power-manager not running, it shows no events. Before: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 25 Brightness up pressed: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 40 With options video brightness_switch_enabled = 0: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 25 Brightness up pressed: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 35 With brightness_switch_enabled=0 and gnome-power-manager not running: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 25 Brightness up pressed: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 30 Description: Ubuntu lucid (development branch) Release: 10.04 xserver-xorg-video-intel: Installed: 2:2.9.1-1ubuntu1 Candidate: 2:2.9.1-1ubuntu1 Version table: *** 2:2.9.1-1ubuntu1 0 500 http://archive.linux.duke.edu lucid/main Packages 100 /var/lib/dpkg/status gnome-power-manager: Installed: 2.29.1-0ubuntu2 Candidate: 2.29.1-0ubuntu2 Version table: *** 2.29.1-0ubuntu2 0 500 http://archive.linux.duke.edu lucid/main Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/527157/+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 574663] Re: Evince fails to properly print pdf files
I also affected by this bug with attached PDF. OS: Ubuntu 11.10 x64 evince 3.2.1 ** Attachment added: This file can't be printed by evince https://bugs.launchpad.net/ubuntu/+source/evince/+bug/574663/+attachment/2771820/+files/R1Page.pdf -- 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/574663 Title: Evince fails to properly print pdf files Status in “evince” package in Ubuntu: Confirmed Bug description: Binary package hint: evince I've been having a problem with printing a particular pdf file from Evince. The pdf is opened and displayed correctly but when I want to print all I get is sheets with only punctuation marks on them. These punctuation marks correctly correspond to what is in the document but all the text in between them is missing. The document is printed correctly from xpdf or from Evince on a Jaunty machine. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: evince 2.30.0-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-21-generic x86_64 NonfreeKernelModules: fglrx Architecture: amd64 Date: Mon May 3 19:12:41 2010 InstallationMedia: Ubuntu 10.04 Lucid Lynx - Alpha amd64 (20100410.1) ProcEnviron: LANG=en_GB.utf8 SHELL=/bin/bash SourcePackage: evince To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/574663/+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 527157] Re: Brightness controls skips Levels.
Here is the patch. Please review it. ** Patch added: 52_brightness_in_hardware.patch https://bugs.launchpad.net/archlinux/+source/gnome-power-manager/+bug/527157/+attachment/3063911/+files/52_brightness_in_hardware.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/527157 Title: Brightness controls skips Levels. Status in Gnome Settings Daemon: New Status in “gnome-power-manager” package in Ubuntu: Invalid Status in “gnome-power-manager” package in Arch Linux: New Bug description: Binary package hint: gnome-power-manager Expected: Hitting brightness up key or brightness down key changes brightness by one level out of 15. Actual: Hitting brightness up key or brightness down key changes brightness by two or three levels out of 15. When I use the brightness control keys from a fresh install, the brightness jumps THREE increments. By creating /etc/modprobe.d/video.conf and setting options video brightness_switch_enabled = 0 I reduce this to consistently TWO brightness events, but this is still double the normal events. If I kill gnome-power-manager, it returns to single brightness events. when hitting brightness up/down with gnome-power-manager, udevmonitor shows UDEV - the event which udev sends out after rule processing KERNEL - the kernel uevent KERNEL[1267026969.897008] change /devices/virtual/backlight/acpi_video0 (backlight) UDEV [1267026969.898270] change /devices/virtual/backlight/acpi_video0 (backlight) KERNEL[1267026969.903078] change /devices/virtual/backlight/acpi_video0 (backlight) UDEV [1267026969.903842] change /devices/virtual/backlight/acpi_video0 (backlight) KERNEL[1267026971.355970] change /devices/virtual/backlight/acpi_video0 (backlight) UDEV [1267026971.357418] change /devices/virtual/backlight/acpi_video0 (backlight) with gnome-power-manager not running, it shows no events. Before: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 25 Brightness up pressed: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 40 With options video brightness_switch_enabled = 0: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 25 Brightness up pressed: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 35 With brightness_switch_enabled=0 and gnome-power-manager not running: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 25 Brightness up pressed: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 30 Description: Ubuntu lucid (development branch) Release: 10.04 xserver-xorg-video-intel: Installed: 2:2.9.1-1ubuntu1 Candidate: 2:2.9.1-1ubuntu1 Version table: *** 2:2.9.1-1ubuntu1 0 500 http://archive.linux.duke.edu lucid/main Packages 100 /var/lib/dpkg/status gnome-power-manager: Installed: 2.29.1-0ubuntu2 Candidate: 2.29.1-0ubuntu2 Version table: *** 2.29.1-0ubuntu2 0 500 http://archive.linux.duke.edu lucid/main Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/527157/+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 527157] Re: Brightness controls skips Levels.
My patch is similar to one in comment #15. Differences are: - it uses gsettings api (commonly used by g-s-d now) - it doesn't break StepUp/StepDown dbus methods - it's smaller -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/527157 Title: Brightness controls skips Levels. Status in Gnome Settings Daemon: New Status in “gnome-power-manager” package in Ubuntu: Invalid Status in “gnome-power-manager” package in Arch Linux: New Bug description: Binary package hint: gnome-power-manager Expected: Hitting brightness up key or brightness down key changes brightness by one level out of 15. Actual: Hitting brightness up key or brightness down key changes brightness by two or three levels out of 15. When I use the brightness control keys from a fresh install, the brightness jumps THREE increments. By creating /etc/modprobe.d/video.conf and setting options video brightness_switch_enabled = 0 I reduce this to consistently TWO brightness events, but this is still double the normal events. If I kill gnome-power-manager, it returns to single brightness events. when hitting brightness up/down with gnome-power-manager, udevmonitor shows UDEV - the event which udev sends out after rule processing KERNEL - the kernel uevent KERNEL[1267026969.897008] change /devices/virtual/backlight/acpi_video0 (backlight) UDEV [1267026969.898270] change /devices/virtual/backlight/acpi_video0 (backlight) KERNEL[1267026969.903078] change /devices/virtual/backlight/acpi_video0 (backlight) UDEV [1267026969.903842] change /devices/virtual/backlight/acpi_video0 (backlight) KERNEL[1267026971.355970] change /devices/virtual/backlight/acpi_video0 (backlight) UDEV [1267026971.357418] change /devices/virtual/backlight/acpi_video0 (backlight) with gnome-power-manager not running, it shows no events. Before: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 25 Brightness up pressed: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 40 With options video brightness_switch_enabled = 0: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 25 Brightness up pressed: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 35 With brightness_switch_enabled=0 and gnome-power-manager not running: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 25 Brightness up pressed: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 30 Description: Ubuntu lucid (development branch) Release: 10.04 xserver-xorg-video-intel: Installed: 2:2.9.1-1ubuntu1 Candidate: 2:2.9.1-1ubuntu1 Version table: *** 2:2.9.1-1ubuntu1 0 500 http://archive.linux.duke.edu lucid/main Packages 100 /var/lib/dpkg/status gnome-power-manager: Installed: 2.29.1-0ubuntu2 Candidate: 2.29.1-0ubuntu2 Version table: *** 2.29.1-0ubuntu2 0 500 http://archive.linux.duke.edu lucid/main Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/527157/+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 527157] Re: Brightness controls skips Levels.
Hmm... really strange. I made patch ubuntu 11.10, g-s-d 3.2.2-0ubuntu2.1. May be you upgraded to 12.04 already? Actually, I should make patch for 12.04, as it's latest stable now. Will do this bit later. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/527157 Title: Brightness controls skips Levels. Status in Gnome Settings Daemon: New Status in “gnome-power-manager” package in Ubuntu: Invalid Status in “gnome-power-manager” package in Arch Linux: New Bug description: Binary package hint: gnome-power-manager Expected: Hitting brightness up key or brightness down key changes brightness by one level out of 15. Actual: Hitting brightness up key or brightness down key changes brightness by two or three levels out of 15. When I use the brightness control keys from a fresh install, the brightness jumps THREE increments. By creating /etc/modprobe.d/video.conf and setting options video brightness_switch_enabled = 0 I reduce this to consistently TWO brightness events, but this is still double the normal events. If I kill gnome-power-manager, it returns to single brightness events. when hitting brightness up/down with gnome-power-manager, udevmonitor shows UDEV - the event which udev sends out after rule processing KERNEL - the kernel uevent KERNEL[1267026969.897008] change /devices/virtual/backlight/acpi_video0 (backlight) UDEV [1267026969.898270] change /devices/virtual/backlight/acpi_video0 (backlight) KERNEL[1267026969.903078] change /devices/virtual/backlight/acpi_video0 (backlight) UDEV [1267026969.903842] change /devices/virtual/backlight/acpi_video0 (backlight) KERNEL[1267026971.355970] change /devices/virtual/backlight/acpi_video0 (backlight) UDEV [1267026971.357418] change /devices/virtual/backlight/acpi_video0 (backlight) with gnome-power-manager not running, it shows no events. Before: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 25 Brightness up pressed: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 40 With options video brightness_switch_enabled = 0: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 25 Brightness up pressed: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 35 With brightness_switch_enabled=0 and gnome-power-manager not running: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 25 Brightness up pressed: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 30 Description: Ubuntu lucid (development branch) Release: 10.04 xserver-xorg-video-intel: Installed: 2:2.9.1-1ubuntu1 Candidate: 2:2.9.1-1ubuntu1 Version table: *** 2:2.9.1-1ubuntu1 0 500 http://archive.linux.duke.edu lucid/main Packages 100 /var/lib/dpkg/status gnome-power-manager: Installed: 2.29.1-0ubuntu2 Candidate: 2.29.1-0ubuntu2 Version table: *** 2.29.1-0ubuntu2 0 500 http://archive.linux.duke.edu lucid/main Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/527157/+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 527157] Re: Brightness controls skips Levels.
Sorry, I didn't write instruction: - put the file into debian/patches/ dir - add line 52_brightness_in_hardware.patch to 'series' file in that dir (not sure if this step is required) - build package as usual This patch should be applied last, after all ubuntu/debian patches. That's why it fails. Have you install package source using 'apt-get source gnome-settings-daemon' or just unpacked source tarball? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/527157 Title: Brightness controls skips Levels. Status in Gnome Settings Daemon: New Status in “gnome-power-manager” package in Ubuntu: Invalid Status in “gnome-power-manager” package in Arch Linux: New Bug description: Binary package hint: gnome-power-manager Expected: Hitting brightness up key or brightness down key changes brightness by one level out of 15. Actual: Hitting brightness up key or brightness down key changes brightness by two or three levels out of 15. When I use the brightness control keys from a fresh install, the brightness jumps THREE increments. By creating /etc/modprobe.d/video.conf and setting options video brightness_switch_enabled = 0 I reduce this to consistently TWO brightness events, but this is still double the normal events. If I kill gnome-power-manager, it returns to single brightness events. when hitting brightness up/down with gnome-power-manager, udevmonitor shows UDEV - the event which udev sends out after rule processing KERNEL - the kernel uevent KERNEL[1267026969.897008] change /devices/virtual/backlight/acpi_video0 (backlight) UDEV [1267026969.898270] change /devices/virtual/backlight/acpi_video0 (backlight) KERNEL[1267026969.903078] change /devices/virtual/backlight/acpi_video0 (backlight) UDEV [1267026969.903842] change /devices/virtual/backlight/acpi_video0 (backlight) KERNEL[1267026971.355970] change /devices/virtual/backlight/acpi_video0 (backlight) UDEV [1267026971.357418] change /devices/virtual/backlight/acpi_video0 (backlight) with gnome-power-manager not running, it shows no events. Before: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 25 Brightness up pressed: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 40 With options video brightness_switch_enabled = 0: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 25 Brightness up pressed: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 35 With brightness_switch_enabled=0 and gnome-power-manager not running: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 25 Brightness up pressed: cat /proc/acpi/video/IGD0/LCD/brightness levels: 25 30 35 40 45 50 55 60 65 70 75 80 85 90 95 100 current: 30 Description: Ubuntu lucid (development branch) Release: 10.04 xserver-xorg-video-intel: Installed: 2:2.9.1-1ubuntu1 Candidate: 2:2.9.1-1ubuntu1 Version table: *** 2:2.9.1-1ubuntu1 0 500 http://archive.linux.duke.edu lucid/main Packages 100 /var/lib/dpkg/status gnome-power-manager: Installed: 2.29.1-0ubuntu2 Candidate: 2.29.1-0ubuntu2 Version table: *** 2.29.1-0ubuntu2 0 500 http://archive.linux.duke.edu lucid/main Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/527157/+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 1359983] [NEW] package nvidia-opencl-icd-331 (not installed) failed to install/upgrade: conflicting packages - not installing nvidia-opencl-icd-331
Public bug reported: When i start install this driver from installed driver NVIDIA binary driver-version 331.38 из nvidia-331-updates. Sorry for my english. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-opencl-icd-331 (not installed) ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 Date: Fri Aug 22 01:26:40 2014 DuplicateSignature: package:nvidia-opencl-icd-331:(not installed):conflicting packages - not installing nvidia-opencl-icd-331 ErrorMessage: conflicting packages - not installing nvidia-opencl-icd-331 InstallationDate: Installed on 2013-09-07 (348 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: nvidia-graphics-drivers-331 Title: package nvidia-opencl-icd-331 (not installed) failed to install/upgrade: conflicting packages - not installing nvidia-opencl-icd-331 UpgradeStatus: Upgraded to trusty on 2014-04-18 (125 days ago) ** Affects: nvidia-graphics-drivers-331 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1359983 Title: package nvidia-opencl-icd-331 (not installed) failed to install/upgrade: conflicting packages - not installing nvidia-opencl- icd-331 Status in “nvidia-graphics-drivers-331” package in Ubuntu: New Bug description: When i start install this driver from installed driver NVIDIA binary driver-version 331.38 из nvidia-331-updates. Sorry for my english. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-opencl-icd-331 (not installed) ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 Date: Fri Aug 22 01:26:40 2014 DuplicateSignature: package:nvidia-opencl-icd-331:(not installed):conflicting packages - not installing nvidia-opencl-icd-331 ErrorMessage: conflicting packages - not installing nvidia-opencl-icd-331 InstallationDate: Installed on 2013-09-07 (348 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: nvidia-graphics-drivers-331 Title: package nvidia-opencl-icd-331 (not installed) failed to install/upgrade: conflicting packages - not installing nvidia-opencl-icd-331 UpgradeStatus: Upgraded to trusty on 2014-04-18 (125 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1359983/+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 875504] Re: terrible screen flicker in 11.10
Hi Christofer, I'm using Ubuntu 14.04.1 ans I can still reproduce this issue. It start flickering after some time and for stopping it I have to use sudo xinput set-prop 8 Device Enabled 0. Should I run apport-collect -p xorg-server 875504 while my screen flickering or I can just do it right now? (now it doesn't flicker) Thanks -- 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/875504 Title: terrible screen flicker in 11.10 Status in xorg-server package in Ubuntu: Expired Bug description: After upgrading to 11.10 I am getting terrible screen flicker with the opensourced ATI drivers. Every time I go to the desktop switcher I get crazy flickering across the screen. When I go into my lenses I get horrible flickering. I tried installing gnome-shell to see if there would be flickering there, and I still get occasional flickering, but not nearly as much. I even tried install Kubuntu, but it is also suffering from horrible flickering. I believe the problem has to do with xorg, during the early parts in alpha development I didn't have a flickering problem, but towards the end and now it is extremely bad. Also, when I install the fglrx proprietary drivers the flickering goes away (though the window responsibleness is horrible). Also, I am still having the issue when uninstalling fglrx it breaks my entire desktop. I am running Ubuntu 11.10 x64, on an acer aspire 5553 with a Mobility Radeon HD 4200 series card. Will we be seeing Catalyst 11.9 or 11.10 at all? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/875504/+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 875504] Re: terrible screen flicker in 11.10
Just want to add little bit. I'm using Ubuntu 14.04.1 wyth Unity on my Dell 3550 with ADM Radeon 6630M card. -- 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/875504 Title: terrible screen flicker in 11.10 Status in xorg-server package in Ubuntu: Expired Bug description: After upgrading to 11.10 I am getting terrible screen flicker with the opensourced ATI drivers. Every time I go to the desktop switcher I get crazy flickering across the screen. When I go into my lenses I get horrible flickering. I tried installing gnome-shell to see if there would be flickering there, and I still get occasional flickering, but not nearly as much. I even tried install Kubuntu, but it is also suffering from horrible flickering. I believe the problem has to do with xorg, during the early parts in alpha development I didn't have a flickering problem, but towards the end and now it is extremely bad. Also, when I install the fglrx proprietary drivers the flickering goes away (though the window responsibleness is horrible). Also, I am still having the issue when uninstalling fglrx it breaks my entire desktop. I am running Ubuntu 11.10 x64, on an acer aspire 5553 with a Mobility Radeon HD 4200 series card. Will we be seeing Catalyst 11.9 or 11.10 at all? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/875504/+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 1087428] Re: [K55VD, Realtek ALC270, Black Headphone Out, Right] No sound at all
This bug affects me too. Thahks RadarNyan, now I know how to make sound
play again, but I still don't know why does it mute sometimes. Please
fix this annoying bug!
--
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/1087428
Title:
[K55VD, Realtek ALC270, Black Headphone Out, Right] No sound at all
Status in “alsa-driver” package in Ubuntu:
Confirmed
Bug description:
My headphone jack does not play any audio, but my laptop speakers do.
The Laptop speakers mute when I plug in headphones, but then no audio
plays.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: alsa-base 1.0.25+dfsg-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-34.53-generic-pae 3.2.33
Uname: Linux 3.2.0-34-generic-pae i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu15
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC270 Analog [ALC270 Analog]
Subdevices: 0/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jay1788 F pulseaudio
/dev/snd/pcmC0D0c: jay1788 F...m pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xf7a1 irq 46'
Mixer name : 'Intel PantherPoint HDMI'
Components : 'HDA:10ec0270,10431457,00100100
HDA:80862806,80860101,0010'
Controls : 24
Simple ctrls : 11
Date: Thu Dec 6 13:47:45 2012
InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386
(20120423)
MarkForUpload: True
PackageArchitecture: all
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
1788 1788 jay F pulseaudio
/dev/snd/pcmC0D0c: jay F...m pulseaudio
Symptom_Jack: Black Headphone Out, Right
Symptom_Type: No sound at all
Title: [K55VD, Realtek ALC270, Black Headphone Out, Right] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/24/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: K55VD.304
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: K55VD
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.:bvrK55VD.304:bd05/24/2012:svnASUSTeKCOMPUTERINC.:pnK55VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK55VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: K55VD
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1087428/+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 1218408] Re: nvidia-settings 319.32 Crash on exit (segmentation fault) (core dumped)
** Package changed: nvidia-settings-304 (Ubuntu) = nvidia-settings-319 (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-settings-319 in Ubuntu. https://bugs.launchpad.net/bugs/1218408 Title: nvidia-settings 319.32 Crash on exit (segmentation fault) (core dumped) Status in “nvidia-settings-319” package in Ubuntu: Confirmed Bug description: Ubuntu 12.04.3 Nvidia GTX 460 768MB BUG: Nvidia 319.32 (Current-319-Updates) X Server Settings is hanging and then crashing on Exit. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: nvidia-settings (not installed) ProcVersionSignature: Ubuntu 3.5.0-39.60~precise1-generic 3.5.7.17 Uname: Linux 3.5.0-39-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.4 Architecture: amd64 Date: Thu Aug 29 17:17:50 2013 InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64 (20130213) MarkForUpload: True SourcePackage: nvidia-settings-304 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings-319/+bug/1218408/+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 1220426] Re: [nvidia-prime]Freeze while using touchpad
Asus K55VD, Xubuntu 14.04 LTS I have swithed from bumblebee to prime and now having this issue. Ctrl+Shift+FN helps but it's annoying. I see it is too rather bug. And it is not fixed yet. So probably I have to switch back to bumblebee... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1220426 Title: [nvidia-prime]Freeze while using touchpad Status in “nvidia-graphics-drivers-319” package in Ubuntu: Confirmed Status in “nvidia-graphics-drivers-331” package in Ubuntu: Confirmed Status in “nvidia-prime” package in Ubuntu: Opinion Bug description: I'm using an Optimus laptop (Asus N43SL) nvidia-prime is installed, so my nvidia dedicated graphics card (GT 540m) is in use. Once in a while, my screen will freeze, only when I use my touchpad. This does not happen with my USB mouse. This does not happen either when I uninstall nvidia-prime and use my intel integrated graphics (HD3000). I can temporarily solve the issue by doing a VT switch. In the attached Xorg.0.log, you can see synaptics: ETPS/2 Elantech Touchpad: touchpad found each time I did a VT switch and regained control. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-319/+bug/1220426/+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 1220426] Re: [nvidia-prime]Freeze while using touchpad
Sorry. too rather bug - rather old bug -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1220426 Title: [nvidia-prime]Freeze while using touchpad Status in “nvidia-graphics-drivers-319” package in Ubuntu: Confirmed Status in “nvidia-graphics-drivers-331” package in Ubuntu: Confirmed Status in “nvidia-prime” package in Ubuntu: Opinion Bug description: I'm using an Optimus laptop (Asus N43SL) nvidia-prime is installed, so my nvidia dedicated graphics card (GT 540m) is in use. Once in a while, my screen will freeze, only when I use my touchpad. This does not happen with my USB mouse. This does not happen either when I uninstall nvidia-prime and use my intel integrated graphics (HD3000). I can temporarily solve the issue by doing a VT switch. In the attached Xorg.0.log, you can see synaptics: ETPS/2 Elantech Touchpad: touchpad found each time I did a VT switch and regained control. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-319/+bug/1220426/+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 1220426] Re: [nvidia-prime]Freeze while using touchpad
It was interesting thing when I tried to switch back to bumblebee from nvidia-prime. I have done these steps: sudo apt-get purge nvidia-prime sudo add-apt-repository ppa:bumblebee/stable sudo apt-get update sudo apt-get install nvidia-331 nvidia-settings sudo apt-get install bumblebee bumblebee-nvidia primus primus-libs-ia32 But then I started World of Goo (from Steam) using optirun. And when in game startscreen I've pointed to profiles icon - there has been a freeze again! I removed bumblebee, primus, nvidia-331. After that I installed nvidia-319-updates, then bumblebee and primus. And now i have no freeze at all. So I think the bug is not in nvidia-prime but in nvidia-331driver, because with nvidia-319-updates there's no freeze. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1220426 Title: [nvidia-prime]Freeze while using touchpad Status in “nvidia-graphics-drivers-319” package in Ubuntu: Confirmed Status in “nvidia-graphics-drivers-331” package in Ubuntu: Confirmed Status in “nvidia-prime” package in Ubuntu: Opinion Bug description: I'm using an Optimus laptop (Asus N43SL) nvidia-prime is installed, so my nvidia dedicated graphics card (GT 540m) is in use. Once in a while, my screen will freeze, only when I use my touchpad. This does not happen with my USB mouse. This does not happen either when I uninstall nvidia-prime and use my intel integrated graphics (HD3000). I can temporarily solve the issue by doing a VT switch. In the attached Xorg.0.log, you can see synaptics: ETPS/2 Elantech Touchpad: touchpad found each time I did a VT switch and regained control. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-319/+bug/1220426/+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 1432822] [NEW] package fontconfig 2.11.1-0ubuntu6 failed to install/upgrade: зацикливание триггеров, отмена работы
Public bug reported: This occurred during apt-get dist-upgrade after clean install ProblemType: Package DistroRelease: Ubuntu 15.04 Package: fontconfig 2.11.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 Date: Mon Mar 16 23:28:20 2015 ErrorMessage: зацикливание триггеров, отмена работы InstallationDate: Installed on 2015-03-16 (0 days ago) InstallationMedia: Xubuntu 15.04 Vivid Vervet - Alpha amd64 (20150224) SourcePackage: fontconfig Title: package fontconfig 2.11.1-0ubuntu6 failed to install/upgrade: зацикливание триггеров, отмена работы UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: fontconfig (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package vivid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1432822 Title: package fontconfig 2.11.1-0ubuntu6 failed to install/upgrade: зацикливание триггеров, отмена работы Status in fontconfig package in Ubuntu: New Bug description: This occurred during apt-get dist-upgrade after clean install ProblemType: Package DistroRelease: Ubuntu 15.04 Package: fontconfig 2.11.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 Date: Mon Mar 16 23:28:20 2015 ErrorMessage: зацикливание триггеров, отмена работы InstallationDate: Installed on 2015-03-16 (0 days ago) InstallationMedia: Xubuntu 15.04 Vivid Vervet - Alpha amd64 (20150224) SourcePackage: fontconfig Title: package fontconfig 2.11.1-0ubuntu6 failed to install/upgrade: зацикливание триггеров, отмена работы UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1432822/+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 1362848] Re: ubuntu 14.04 after install nvidia binary driver 331.89 black screen and freeze
Hi all! Same here, on my Dell N5110 with Core i5 Intel HD3000 + GT525M. After upgrade to Ubuntu 15.10 Stable with nvidia-355 the problem is solved. Black screen no longer appears, without applying script, which posted twisted_tits above. Regards, Dmitriy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1362848 Title: ubuntu 14.04 after install nvidia binary driver 331.89 black screen and freeze Status in nvidia-graphics-drivers-331 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-346 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-352 package in Ubuntu: Confirmed Bug description: I'm using Ubuntu 14.04 64bit, after install nvidia binary driver 331.89 from Additional Drivers application then reboot, it shows black screen, no login window, I even can't use ctrl+alt+F2 to switch to text mode, then I reboot and go to recovery mode, use 'prime-select intel' to switch to intel GPU and reboot, everything is fine, but as soon as I switch to nvidia GPU, still same issue. OS: Ubuntu 14.04 64bit Laptop: HP ENVY 15t Nvidia GeForce GT 740M + Intel HD 4600 Desktop: Unity Kernel: 3.13.0 CPU: Intel® Core™ i7-4700MQ Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1362848/+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 1568604] Re: Mouse cursor lost when unlocking with Intel graphics
I think, I found better workaround: after I changed lightdm configuration using 'lightdm greeter settings', I don't face this bug anymore -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1568604 Title: Mouse cursor lost when unlocking with Intel graphics Status in X.Org X server: Confirmed Status in xf86-video-intel: Fix Released Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: Cursor is visible at unlock screen either after returning from suspend or just locking. After unlocking screen cursor is invisible. Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7) cursor returns no matter if you suspend or sleep, to swap or disk when you return from it, the mouse cursor is missing.you can still move the mouse and you can see (because it highlights the window) as you move it around. But the cursor is not displayed on the screen. i am using a lenovo W540 laptop. I downloaded the latest beta on april 8 2016. this is xubuntu using the xfce window manager. the cursor does return if i log off and log back in, but that actually defeats the purpose of going to sleep. --- ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2016-04-08 (2 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia Package: light-locker 1.7.0-2ubuntu1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Tags: xenial Uname: Linux 4.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1568604/+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 1568604] Re: Mouse cursor lost when unlocking with Intel graphics
No, that's not a workaround. Bug appeared again after several hibernate-resume cycles. I never seen this bug with xubuntu 15.10, kernel 4.5 from http://kernel.ubuntu.com/~kernel-ppa/mainline/ and latest Intel graphics from 01.org. But it appeared after installing 16.04. I'll try latest kernel from http://kernel.ubuntu.com/~kernel- ppa/mainline/, may be it helps. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1568604 Title: Mouse cursor lost when unlocking with Intel graphics Status in X.Org X server: Confirmed Status in xf86-video-intel: Fix Released Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: Cursor is visible at unlock screen either after returning from suspend or just locking. After unlocking screen cursor is invisible. Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7) cursor returns no matter if you suspend or sleep, to swap or disk when you return from it, the mouse cursor is missing.you can still move the mouse and you can see (because it highlights the window) as you move it around. But the cursor is not displayed on the screen. i am using a lenovo W540 laptop. I downloaded the latest beta on april 8 2016. this is xubuntu using the xfce window manager. the cursor does return if i log off and log back in, but that actually defeats the purpose of going to sleep. --- ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2016-04-08 (2 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia Package: light-locker 1.7.0-2ubuntu1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Tags: xenial Uname: Linux 4.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1568604/+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 1539513] Re: networkmanager segfaults with 3.2.21-1ubuntu1
Same issue. Just did as #4/#7 and it helped. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1539513 Title: networkmanager segfaults with 3.2.21-1ubuntu1 Status in libnl3 package in Ubuntu: Confirmed Bug description: Description:Ubuntu 14.04.3 LTS Release:14.04 After upgrading to 3.2.21-1ubuntu1 network-manager 0.9.8.8-0ubuntu7.2 segfaults: [ 21.367977] init: network-manager main process (1000) killed by SEGV signal [ 21.367989] init: network-manager main process ended, respawning [ 21.424932] init: network-manager main process (1060) killed by SEGV signal [ 21.424943] init: network-manager main process ended, respawning [ 21.451519] init: network-manager main process (1066) killed by SEGV signal [...] xxx@yyy:/tmp/bla# gdb /usr/sbin/NetworkManager CoreDump [...] Reading symbols from /usr/sbin/NetworkManager...(no debugging symbols found)...done. [New LWP 3550] [New LWP 3551] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `NetworkManager'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00469fee in nm_netlink_monitor_attach () To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1539513/+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 1568604] Re: Mouse cursor lost when unlocking with Intel graphics
When I unlock my elementary os Freya (based on Ubuntu 14.04), mouse pointer dissapears, but if I switch, for example, Youtube video to full screen, pointer appears again till next suspend. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1568604 Title: Mouse cursor lost when unlocking with Intel graphics Status in elementary OS: Fix Released Status in xf86-video-intel: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Fix Released Status in xserver-xorg-video-intel source package in Xenial: Fix Released Status in xserver-xorg-video-intel package in Debian: Fix Released Bug description: [Impact] Mouse cursor is no longer visible after VT-switch for systems with Intel graphics. Switching VTs again may cause the cursor to become visible again. - Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7) This is often observed in systems that lock the session and return to the greeter (including at least Xubuntu, Ubuntu Mate, and elementary OS). [Test Case] (Requires a lightdm-based screen locking solution) 1. Start a new session. 2. Lock your screen. 2a. You are redirected to the lightdm greeter. 3. Login/Unlock your session. 4. Cursor is no longer visible. [Regression Potential] remains to be seen === [Original Report] Cursor is visible at unlock screen either after returning from suspend or just locking. After unlocking screen cursor is invisible. Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7) cursor returns no matter if you suspend or sleep, to swap or disk when you return from it, the mouse cursor is missing.you can still move the mouse and you can see (because it highlights the window) as you move it around. But the cursor is not displayed on the screen. i am using a lenovo W540 laptop. I downloaded the latest beta on april 8 2016. this is xubuntu using the xfce window manager. the cursor does return if i log off and log back in, but that actually defeats the purpose of going to sleep. --- ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2016-04-08 (2 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia Package: light-locker 1.7.0-2ubuntu1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Tags: xenial Uname: Linux 4.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1568604/+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 1641380] Re: chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec certs
Thawte certificates are not accepted: https://life.ru -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1641380 Title: chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec certs Status in chromium-browser package in Ubuntu: Confirmed Bug description: Chromium browser in xenial no longer trusts Symantec issued certificates. See [1]. 1. https://bugs.chromium.org/p/chromium/issues/detail?id=664177 Ubuntu release: 16.04 chromium-browser: 53.0.2785.143-0ubuntu0.16.04.1.1254 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1641380/+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 1730554] Re: gnome-shell (3.24.2) crashed with segfault
ubuntu-bug complains that there is not enough free memory to analyze crash dump. I'm attaching the dump itself. ** Attachment added: "_usr_bin_gnome-shell.1000.crash" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1730554/+attachment/5010747/+files/_usr_bin_gnome-shell.1000.crash -- 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/1730554 Title: gnome-shell (3.24.2) crashed with segfault Status in gnome-shell package in Ubuntu: Incomplete Bug description: This happens when I was navigating through my Google calendar, and the desktop freezes. My music was still playing in the background, it's just the desktop stop responding. A few seconds later, it looks like gnome-shell itself has restarted. Error message in dmesg: [37530.709259] show_signal_msg: 9 callbacks suppressed [37530.709264] gnome-shell[2068]: segfault at 604c3f ip 7fdf96a0560a sp 7ffebbbef8d0 error 4 in libgobject-2.0.so.0.5200.0[7fdf969d1000+51000] ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-shell 3.24.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.10.0-38.42-generic 4.10.17 Uname: Linux 4.10.0-38-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Nov 7 11:17:42 2017 DisplayManager: gdm3 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.shell' b'enabled-extensions' b"['topic...@phocean.net', 'alternate-...@gnome-shell-extensions.gcampax.github.com', 'suspend-button@laserb', 'drive-m...@gnome-shell-extensions.gcampax.github.com', 'places-m...@gnome-shell-extensions.gcampax.github.com']" b'org.gnome.shell' b'command-history' b"['r']" b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['ubiquity.desktop', 'evolution.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 'skypeforlinux.desktop', 'google-chrome.desktop', 'org.gnome.Terminal.desktop', 'hexchat.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-07-12 (117 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1730554/+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 1730554] Re: gnome-shell (3.24.2) crashed with segfault
In my case error messages look like Nov 18 07:50:34 kernel: do_general_protection: 14 callbacks suppressed Nov 18 07:50:34 kernel: traps: gnome-shell[1430] general protection ip:7f3f663c2e0d sp:7ffe9fed66d0 error:0 in libgobject-2.0.so.0.5400.1[7f3f6638 -- 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/1730554 Title: gnome-shell (3.24.2) crashed with segfault Status in gnome-shell package in Ubuntu: Incomplete Bug description: This happens when I was navigating through my Google calendar, and the desktop freezes. My music was still playing in the background, it's just the desktop stop responding. A few seconds later, it looks like gnome-shell itself has restarted. Error message in dmesg: [37530.709259] show_signal_msg: 9 callbacks suppressed [37530.709264] gnome-shell[2068]: segfault at 604c3f ip 7fdf96a0560a sp 7ffebbbef8d0 error 4 in libgobject-2.0.so.0.5200.0[7fdf969d1000+51000] ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-shell 3.24.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.10.0-38.42-generic 4.10.17 Uname: Linux 4.10.0-38-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Nov 7 11:17:42 2017 DisplayManager: gdm3 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.shell' b'enabled-extensions' b"['topic...@phocean.net', 'alternate-...@gnome-shell-extensions.gcampax.github.com', 'suspend-button@laserb', 'drive-m...@gnome-shell-extensions.gcampax.github.com', 'places-m...@gnome-shell-extensions.gcampax.github.com']" b'org.gnome.shell' b'command-history' b"['r']" b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['ubiquity.desktop', 'evolution.desktop', 'rhythmbox.desktop', 'org.gnome.Nautilus.desktop', 'skypeforlinux.desktop', 'google-chrome.desktop', 'org.gnome.Terminal.desktop', 'hexchat.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-07-12 (117 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1730554/+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 1763578] [NEW] gpu-manager syslog reported errors
Public bug reported: syslog contains following error messages: Apr 13 10:31:36 dmig-Inspiron-5379 gpu-manager[858]: /etc/modprobe.d is not a file Apr 13 10:31:36 dmig-Inspiron-5379 gpu-manager[858]: Error: can't open /lib/modules/4.15.0-15-generic/updates/dkms Apr 13 10:31:36 dmig-Inspiron-5379 gpu-manager[858]: Error: can't open /lib/modules/4.15.0-15-generic/updates/dkms None of them represent a real error, gpu-manager shouldn't complain about this ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-drivers-common 1:0.5 Uname: Linux 4.16.2-041602-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 13 12:36:47 2018 InstallationDate: Installed on 2018-03-27 (16 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327) SourcePackage: ubuntu-drivers-common UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1763578 Title: gpu-manager syslog reported errors Status in ubuntu-drivers-common package in Ubuntu: New Bug description: syslog contains following error messages: Apr 13 10:31:36 dmig-Inspiron-5379 gpu-manager[858]: /etc/modprobe.d is not a file Apr 13 10:31:36 dmig-Inspiron-5379 gpu-manager[858]: Error: can't open /lib/modules/4.15.0-15-generic/updates/dkms Apr 13 10:31:36 dmig-Inspiron-5379 gpu-manager[858]: Error: can't open /lib/modules/4.15.0-15-generic/updates/dkms None of them represent a real error, gpu-manager shouldn't complain about this ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-drivers-common 1:0.5 Uname: Linux 4.16.2-041602-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 13 12:36:47 2018 InstallationDate: Installed on 2018-03-27 (16 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327) SourcePackage: ubuntu-drivers-common UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1763578/+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 1763577] [NEW] failed to load modules crypto and mdraid
Public bug reported: udisks daemon complains about loading libbd_crypto and libbd_mdraid, but seems to work fine. I fixed the issue by manually installing packages libblockdev-crypto2 and libblockdev-mdraid2. udisks should depend on these packages or doesn't complain about missing libraries. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: udisks2 2.7.6-2ubuntu6 Uname: Linux 4.16.2-041602-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.core.rules 70-snap.spotify.rules Date: Fri Apr 13 12:22:11 2018 InstallationDate: Installed on 2018-03-27 (16 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327) MachineType: Dell Inc. Inspiron 5379 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.16.2-041602-generic root=UUID=9745e22b-0b19-4a7d-98a0-1a4bc5b19d99 ro rootflags=subvol=@ quiet splash vt.handoff=1 SourcePackage: udisks2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 0C6J64 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd01/31/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn0C6J64:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5379 dmi.sys.vendor: Dell Inc. ** Affects: udisks2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1763577 Title: failed to load modules crypto and mdraid Status in udisks2 package in Ubuntu: New Bug description: udisks daemon complains about loading libbd_crypto and libbd_mdraid, but seems to work fine. I fixed the issue by manually installing packages libblockdev-crypto2 and libblockdev-mdraid2. udisks should depend on these packages or doesn't complain about missing libraries. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: udisks2 2.7.6-2ubuntu6 Uname: Linux 4.16.2-041602-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.core.rules 70-snap.spotify.rules Date: Fri Apr 13 12:22:11 2018 InstallationDate: Installed on 2018-03-27 (16 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327) MachineType: Dell Inc. Inspiron 5379 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.16.2-041602-generic root=UUID=9745e22b-0b19-4a7d-98a0-1a4bc5b19d99 ro rootflags=subvol=@ quiet splash vt.handoff=1 SourcePackage: udisks2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 0C6J64 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd01/31/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn0C6J64:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5379 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1763577/+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 1763577] Re: failed to load modules crypto and mdraid
** Attachment added: "console output showing problem and solution" https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1763577/+attachment/5113324/+files/console.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1763577 Title: failed to load modules crypto and mdraid Status in udisks2 package in Ubuntu: New Bug description: udisks daemon complains about loading libbd_crypto and libbd_mdraid, but seems to work fine. I fixed the issue by manually installing packages libblockdev-crypto2 and libblockdev-mdraid2. udisks should depend on these packages or doesn't complain about missing libraries. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: udisks2 2.7.6-2ubuntu6 Uname: Linux 4.16.2-041602-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.core.rules 70-snap.spotify.rules Date: Fri Apr 13 12:22:11 2018 InstallationDate: Installed on 2018-03-27 (16 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327) MachineType: Dell Inc. Inspiron 5379 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.16.2-041602-generic root=UUID=9745e22b-0b19-4a7d-98a0-1a4bc5b19d99 ro rootflags=subvol=@ quiet splash vt.handoff=1 SourcePackage: udisks2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 0C6J64 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd01/31/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn0C6J64:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5379 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1763577/+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 1760005] [NEW] Dialog 'add custom shortcut dialog' is unusable with keyboard only
Public bug reported: 'Add Custom Shortcut' dialog (Settings -> Keyboard -> '+' at the end of list) never sets focus to 'Set Shortcut...' and 'Add' buttons if used from keyboard. Current field order is: 'Name' -> 'Command' -> 'Cancel' button. Tab key switches focus only between these 3 fields. Arrow keys switch focus only between input fields. Expected field order: 'Name' -> 'Command' -> 'Set Shortcut...' -> 'Add' button (if enabled) -> 'Cancel' button. = Description:Ubuntu Bionic Beaver (development branch) Release:18.04 = gnome-control-center: Installed: 1:3.28.0-0ubuntu6 Candidate: 1:3.28.0-0ubuntu6 Version table: *** 1:3.28.0-0ubuntu6 500 500 http://th.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.0-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 30 10:03:23 2018 InstallationDate: Installed on 2018-03-27 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages ** Attachment added: "Dialog picture" https://bugs.launchpad.net/bugs/1760005/+attachment/5095523/+files/Screenshot%20from%202018-03-30%2010-04-49.png -- 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/1760005 Title: Dialog 'add custom shortcut dialog' is unusable with keyboard only Status in gnome-control-center package in Ubuntu: New Bug description: 'Add Custom Shortcut' dialog (Settings -> Keyboard -> '+' at the end of list) never sets focus to 'Set Shortcut...' and 'Add' buttons if used from keyboard. Current field order is: 'Name' -> 'Command' -> 'Cancel' button. Tab key switches focus only between these 3 fields. Arrow keys switch focus only between input fields. Expected field order: 'Name' -> 'Command' -> 'Set Shortcut...' -> 'Add' button (if enabled) -> 'Cancel' button. = Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 = gnome-control-center: Installed: 1:3.28.0-0ubuntu6 Candidate: 1:3.28.0-0ubuntu6 Version table: *** 1:3.28.0-0ubuntu6 500 500 http://th.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.0-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 30 10:03:23 2018 InstallationDate: Installed on 2018-03-27 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1760005/+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 1697229] Re: GNOME extensions deactivated after lock unlock
Started experiencing this bug after Ubuntu update 18.04->18.10. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1697229 Title: GNOME extensions deactivated after lock unlock Status in gnome-session: New Status in gnome-session package in Ubuntu: Confirmed Bug description: Summary: Lock then unlock GNOME session result in all GNOME extensions to be deactivated. Intermittent bug. Steps to reproduce: 1. Install fresh Debian 8.8 Jessie 2. Using https://extensions.gnome.org install and activate all the following extensions: • https://extensions.gnome.org/extension/310/alt-tab-workspace/ alt-tab-worksp...@kwalo.net (version 10.0) • https://extensions.gnome.org/extension/484/workspace-grid/ workspace-g...@mathematical.coffee.gmail.com (version 18.0) • https://extensions.gnome.org/extension/495/topicons/ topIcons@adel.gadl...@gmail.com (version 29.0) • https://extensions.gnome.org/extension/672/disable-screen-shield/ disable-screenshi...@lgpasquale.com (version 7.0) • https://extensions.gnome.org/extension/425/project-hamster-extension/ hams...@projecthamster.wordpress.com (version 26.0) • https://extensions.gnome.org/extension/1082/cpufreq/ cpufreq@konkor (version 12.0) 3. Lock GNOME session 4. Unlock GNOME session. Notice that all extensions are now deactivated :( Expected result is that they should remaining activated per their configuration. 5. Using "Tweak Tool"/"gnome-tweak-tool" re-activate all those extensions. Restart GNOME by pressing "ALT-F2" keys, type "r", press "Enter" key. The extensions are now working. 6. Lock GNOME session again 7. Unlock GNOME session again. Issue is reproduced again. All extensions are deactivated. This bug is intermittent though. It depends on various factors, including but not limited: • Which extensions are activated • Your personal configuration with "gnome-tweak-tool" and "gnome-session" packages 8. This issue can also be reproduce with rebooting, instead of lock and unlock the session. Same steps to reproduce as above. But simply reboot. Using • Base system: Debian 8.8 Jessie, 64-bit • Gnome: 3.14.1 • gnome-tweak-tool: 3.14.2-2 • gnome-session: 3.14.0-2 • gnome-session-bin: 3.14.0-2 • gnome-session-common: 3.14.0-2 • Kernel: 4.9.0-0.bpo.3-amd64 #1 SMP Debian 4.9.25-1~bpo8+1 (2017-05-19) x86_64 GNU/Linux Notes: This bug was fixed in the package gnome-session - 3.9.90-0ubuntu16.1 with that ticket comment #15 at https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1385572/comments/15 So that ticket #1385572 is closed. But somehow this bug is back and reported by others in tickets #1236749 and #1385572. Maybe a regression? Maybe a zombie-bug, LOL ;) Anyhow I'm reopening this bug with this new ticket #1697229. I would be happy to contribute testing Here is another related ticket which includes some temporary fixes, such as: # 12 at https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1236749/comments/12 # 57 at https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1236749/comments/57 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-session/+bug/1697229/+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 1803849] Re: libgl1-mesa-dri:i386 can not be installed
WTF??? Does this mean you want to get rid of the problem without solving it? There is definitely a dependency problem either in libgl1-mesa-dri:i386 or in libllvm7:i386. == $ apt policy Package files: 100 /var/lib/dpkg/status release a=now 500 http://archive.ubuntu.com/ubuntu cosmic-proposed/main i386 Packages release v=18.10,o=Ubuntu,a=cosmic-proposed,n=cosmic,l=Ubuntu,c=main,b=i386 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu cosmic-proposed/main amd64 Packages release v=18.10,o=Ubuntu,a=cosmic-proposed,n=cosmic,l=Ubuntu,c=main,b=amd64 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu cosmic-proposed/multiverse i386 Packages release v=18.10,o=Ubuntu,a=cosmic-proposed,n=cosmic,l=Ubuntu,c=multiverse,b=i386 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu cosmic-proposed/multiverse amd64 Packages release v=18.10,o=Ubuntu,a=cosmic-proposed,n=cosmic,l=Ubuntu,c=multiverse,b=amd64 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu cosmic-proposed/universe i386 Packages release v=18.10,o=Ubuntu,a=cosmic-proposed,n=cosmic,l=Ubuntu,c=universe,b=i386 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu cosmic-proposed/universe amd64 Packages release v=18.10,o=Ubuntu,a=cosmic-proposed,n=cosmic,l=Ubuntu,c=universe,b=amd64 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu cosmic-security/multiverse i386 Packages release v=18.10,o=Ubuntu,a=cosmic-security,n=cosmic,l=Ubuntu,c=multiverse,b=i386 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu cosmic-security/multiverse amd64 Packages release v=18.10,o=Ubuntu,a=cosmic-security,n=cosmic,l=Ubuntu,c=multiverse,b=amd64 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu cosmic-security/universe i386 Packages release v=18.10,o=Ubuntu,a=cosmic-security,n=cosmic,l=Ubuntu,c=universe,b=i386 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu cosmic-security/universe amd64 Packages release v=18.10,o=Ubuntu,a=cosmic-security,n=cosmic,l=Ubuntu,c=universe,b=amd64 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu cosmic-security/main i386 Packages release v=18.10,o=Ubuntu,a=cosmic-security,n=cosmic,l=Ubuntu,c=main,b=i386 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu cosmic-security/main amd64 Packages release v=18.10,o=Ubuntu,a=cosmic-security,n=cosmic,l=Ubuntu,c=main,b=amd64 origin archive.ubuntu.com 500 http://archive.canonical.com/ubuntu cosmic/partner i386 Packages release v=18.10,o=Canonical,a=cosmic,n=cosmic,l=Partner archive,c=partner,b=i386 origin archive.canonical.com 500 http://archive.canonical.com/ubuntu cosmic/partner amd64 Packages release v=18.10,o=Canonical,a=cosmic,n=cosmic,l=Partner archive,c=partner,b=amd64 origin archive.canonical.com 500 http://archive.ubuntu.com/ubuntu cosmic-updates/multiverse i386 Packages release v=18.10,o=Ubuntu,a=cosmic-updates,n=cosmic,l=Ubuntu,c=multiverse,b=i386 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu cosmic-updates/multiverse amd64 Packages release v=18.10,o=Ubuntu,a=cosmic-updates,n=cosmic,l=Ubuntu,c=multiverse,b=amd64 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu cosmic-updates/universe i386 Packages release v=18.10,o=Ubuntu,a=cosmic-updates,n=cosmic,l=Ubuntu,c=universe,b=i386 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu cosmic-updates/universe amd64 Packages release v=18.10,o=Ubuntu,a=cosmic-updates,n=cosmic,l=Ubuntu,c=universe,b=amd64 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu cosmic-updates/main i386 Packages release v=18.10,o=Ubuntu,a=cosmic-updates,n=cosmic,l=Ubuntu,c=main,b=i386 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages release v=18.10,o=Ubuntu,a=cosmic-updates,n=cosmic,l=Ubuntu,c=main,b=amd64 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu cosmic/multiverse i386 Packages release v=18.10,o=Ubuntu,a=cosmic,n=cosmic,l=Ubuntu,c=multiverse,b=i386 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu cosmic/multiverse amd64 Packages release v=18.10,o=Ubuntu,a=cosmic,n=cosmic,l=Ubuntu,c=multiverse,b=amd64 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu cosmic/universe i386 Packages release v=18.10,o=Ubuntu,a=cosmic,n=cosmic,l=Ubuntu,c=universe,b=i386 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages release v=18.10,o=Ubuntu,a=cosmic,n=cosmic,l=Ubuntu,c=universe,b=amd64 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu cosmic/restricted i386 Packages release
[Desktop-packages] [Bug 1803849] [NEW] libgl1-mesa-dri:i386 can not be installed
Public bug reported: Steam client tries to install a set of i386 libraries. One of them is libgl1-mesa-dri:i386. But since upgrade to Ubuntu 18.10 this package got broken dependency and thus installation fails. >The following packages have unmet dependencies: > libgl1-mesa-dri:i386 : Depends: libllvm7:i386 (>= 1:7~svn298832-1~) but it is > not going to be installed ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libgl1-mesa-dri:i386 (not installed) Uname: Linux 4.19.2-041902-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Nov 18 09:54:04 2018 DistUpgraded: 2018-10-19 13:34:56,068 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: exfat, 1.2.10, 4.18.0-11-generic, x86_64: installed exfat, 1.2.10, 4.18.0-12-generic, x86_64: installed exfat, 1.2.10, 4.19.1-041901-generic, x86_64: installed exfat, 1.2.10, 4.19.2-041902-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0804] InstallationDate: Installed on 2018-03-27 (235 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327) MachineType: Dell Inc. Inspiron 5379 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.2-041902-generic root=UUID=9745e22b-0b19-4a7d-98a0-1a4bc5b19d99 ro rootflags=subvol=@ quiet splash vt.handoff=1 SourcePackage: mesa UpgradeStatus: Upgraded to cosmic on 2018-10-19 (29 days ago) dmi.bios.date: 07/19/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.0 dmi.board.name: 0C6J64 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.0:bd07/19/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn0C6J64:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5379 dmi.product.sku: 0804 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1803849 Title: libgl1-mesa-dri:i386 can not be installed Status in mesa package in Ubuntu: New Bug description: Steam client tries to install a set of i386 libraries. One of them is libgl1-mesa-dri:i386. But since upgrade to Ubuntu 18.10 this package got broken dependency and thus installation fails. >The following packages have unmet dependencies: > libgl1-mesa-dri:i386 : Depends: libllvm7:i386 (>= 1:7~svn298832-1~) but it is not going to be installed ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libgl1-mesa-dri:i386 (not installed) Uname: Linux 4.19.2-041902-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Nov 18 09:54:04 2018 DistUpgraded: 2018-10-19 13:34:56,068 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: exfat, 1.2.10, 4.18.0-11-generic, x86_64: installed exfat, 1.2.10, 4.18.0-12-generic, x86_64: installed exfat, 1.2.10, 4.19.1-041901-generic, x86_64: installed exfat, 1.2.10, 4.19.2-041902-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0804] InstallationDate: Installed on 2018-03-27 (235 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327) MachineType: Dell Inc. Inspiron 5379 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.2-041902-generic root=UUID=9745e22b-0b19-4a7d-98a0-1a4bc5b19d99 ro rootflags=subvol=@ quiet splash vt.handoff=1 SourcePackage: mesa UpgradeStatus: Upgraded to cosmic on 2018-10-19 (29 days ago) dmi.bios.date: 07/19/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.0 dmi.board.name: 0C6J64 dmi.board.vendor: Dell Inc.
[Desktop-packages] [Bug 1998409] Re: [snap] chromium fails to start: unsupported version 0 of Verneed record
Some articles say the issue is SNAP related, and I saw a patch to the SNAP daemon which fixes it. Sorry, I don't remember the link to that post. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1998409 Title: [snap] chromium fails to start: unsupported version 0 of Verneed record Status in chromium-browser package in Ubuntu: New Status in firefox package in Ubuntu: New Bug description: Description:Ubuntu 22.04.1 LTS Release:22.04 Just updated before trying to run the chromium. $ chromium-browser /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8) mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record sed: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record md5sum: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record cp: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record md5sum: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record xdg-user-dirs-update: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/snap/command-chain/desktop-launch: line 406: /home/USER/snap/chromium/2221/.config/fontconfig/fonts.conf: No such file or directory ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/snap/command-chain/desktop-launch: line 500: /home/USER/snap/chromium/common/.cache/gdk-pixbuf-loaders.cache: No such file or directory rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/gnome-platform/usr/lib/x86_64-linux-gnu/glib-2.0/gio-querymodules: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries:
[Desktop-packages] [Bug 1998409] Snap.Connections.txt
apport information ** Attachment added: "Snap.Connections.txt" https://bugs.launchpad.net/bugs/1998409/+attachment/5634621/+files/Snap.Connections.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1998409 Title: [snap] chromium fails to start: unsupported version 0 of Verneed record Status in chromium-browser package in Ubuntu: Incomplete Bug description: Description:Ubuntu 22.04.1 LTS Release:22.04 Just updated before trying to run the chromium. $ chromium-browser /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8) mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record sed: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record md5sum: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record cp: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record md5sum: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record xdg-user-dirs-update: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/snap/command-chain/desktop-launch: line 406: /home/USER/snap/chromium/2221/.config/fontconfig/fonts.conf: No such file or directory ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/snap/command-chain/desktop-launch: line 500: /home/USER/snap/chromium/common/.cache/gdk-pixbuf-loaders.cache: No such file or directory rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/gnome-platform/usr/lib/x86_64-linux-gnu/glib-2.0/gio-querymodules: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported
[Desktop-packages] [Bug 1998409] Snap.Info.chromium.txt
apport information ** Attachment added: "Snap.Info.chromium.txt" https://bugs.launchpad.net/bugs/1998409/+attachment/5634622/+files/Snap.Info.chromium.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1998409 Title: [snap] chromium fails to start: unsupported version 0 of Verneed record Status in chromium-browser package in Ubuntu: Incomplete Bug description: Description:Ubuntu 22.04.1 LTS Release:22.04 Just updated before trying to run the chromium. $ chromium-browser /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8) mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record sed: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record md5sum: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record cp: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record md5sum: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record xdg-user-dirs-update: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/snap/command-chain/desktop-launch: line 406: /home/USER/snap/chromium/2221/.config/fontconfig/fonts.conf: No such file or directory ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/snap/command-chain/desktop-launch: line 500: /home/USER/snap/chromium/common/.cache/gdk-pixbuf-loaders.cache: No such file or directory rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/gnome-platform/usr/lib/x86_64-linux-gnu/glib-2.0/gio-querymodules: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported
[Desktop-packages] [Bug 1998409] Snap.Info.core.txt
apport information ** Attachment added: "Snap.Info.core.txt" https://bugs.launchpad.net/bugs/1998409/+attachment/5634623/+files/Snap.Info.core.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1998409 Title: [snap] chromium fails to start: unsupported version 0 of Verneed record Status in chromium-browser package in Ubuntu: Incomplete Bug description: Description:Ubuntu 22.04.1 LTS Release:22.04 Just updated before trying to run the chromium. $ chromium-browser /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8) mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record sed: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record md5sum: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record cp: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record md5sum: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record xdg-user-dirs-update: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/snap/command-chain/desktop-launch: line 406: /home/USER/snap/chromium/2221/.config/fontconfig/fonts.conf: No such file or directory ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/snap/command-chain/desktop-launch: line 500: /home/USER/snap/chromium/common/.cache/gdk-pixbuf-loaders.cache: No such file or directory rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/gnome-platform/usr/lib/x86_64-linux-gnu/glib-2.0/gio-querymodules: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0
[Desktop-packages] [Bug 1998409] Snap.Info.core18.txt
apport information ** Attachment added: "Snap.Info.core18.txt" https://bugs.launchpad.net/bugs/1998409/+attachment/5634624/+files/Snap.Info.core18.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1998409 Title: [snap] chromium fails to start: unsupported version 0 of Verneed record Status in chromium-browser package in Ubuntu: Incomplete Bug description: Description:Ubuntu 22.04.1 LTS Release:22.04 Just updated before trying to run the chromium. $ chromium-browser /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8) mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record sed: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record md5sum: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record cp: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record md5sum: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record xdg-user-dirs-update: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/snap/command-chain/desktop-launch: line 406: /home/USER/snap/chromium/2221/.config/fontconfig/fonts.conf: No such file or directory ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/snap/command-chain/desktop-launch: line 500: /home/USER/snap/chromium/common/.cache/gdk-pixbuf-loaders.cache: No such file or directory rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/gnome-platform/usr/lib/x86_64-linux-gnu/glib-2.0/gio-querymodules: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported
[Desktop-packages] [Bug 1998409] Snap.Info.gtk-common-themes.txt
apport information ** Attachment added: "Snap.Info.gtk-common-themes.txt" https://bugs.launchpad.net/bugs/1998409/+attachment/5634625/+files/Snap.Info.gtk-common-themes.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1998409 Title: [snap] chromium fails to start: unsupported version 0 of Verneed record Status in chromium-browser package in Ubuntu: Incomplete Bug description: Description:Ubuntu 22.04.1 LTS Release:22.04 Just updated before trying to run the chromium. $ chromium-browser /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8) mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record sed: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record md5sum: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record cp: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record md5sum: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record xdg-user-dirs-update: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/snap/command-chain/desktop-launch: line 406: /home/USER/snap/chromium/2221/.config/fontconfig/fonts.conf: No such file or directory ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/snap/command-chain/desktop-launch: line 500: /home/USER/snap/chromium/common/.cache/gdk-pixbuf-loaders.cache: No such file or directory rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/gnome-platform/usr/lib/x86_64-linux-gnu/glib-2.0/gio-querymodules: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries:
[Desktop-packages] [Bug 1998409] Re: [snap] chromium fails to start: unsupported version 0 of Verneed record
OMG, apport-collect places all these files as individual comments, creating a lot of unnecessary posts here. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1998409 Title: [snap] chromium fails to start: unsupported version 0 of Verneed record Status in chromium-browser package in Ubuntu: Incomplete Bug description: Description:Ubuntu 22.04.1 LTS Release:22.04 Just updated before trying to run the chromium. $ chromium-browser /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8) mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record sed: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record md5sum: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record cp: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record md5sum: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record xdg-user-dirs-update: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/snap/command-chain/desktop-launch: line 406: /home/USER/snap/chromium/2221/.config/fontconfig/fonts.conf: No such file or directory ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/snap/command-chain/desktop-launch: line 500: /home/USER/snap/chromium/common/.cache/gdk-pixbuf-loaders.cache: No such file or directory rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/gnome-platform/usr/lib/x86_64-linux-gnu/glib-2.0/gio-querymodules: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record dirname: error while
[Desktop-packages] [Bug 1998409] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1998409/+attachment/5634626/+files/UdevDb.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1998409 Title: [snap] chromium fails to start: unsupported version 0 of Verneed record Status in chromium-browser package in Ubuntu: Incomplete Bug description: Description:Ubuntu 22.04.1 LTS Release:22.04 Just updated before trying to run the chromium. $ chromium-browser /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8) mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record sed: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record md5sum: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record cp: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record md5sum: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record xdg-user-dirs-update: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/snap/command-chain/desktop-launch: line 406: /home/USER/snap/chromium/2221/.config/fontconfig/fonts.conf: No such file or directory ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/snap/command-chain/desktop-launch: line 500: /home/USER/snap/chromium/common/.cache/gdk-pixbuf-loaders.cache: No such file or directory rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/gnome-platform/usr/lib/x86_64-linux-gnu/glib-2.0/gio-querymodules: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed
[Desktop-packages] [Bug 1998409] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1998409/+attachment/5634627/+files/acpidump.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1998409 Title: [snap] chromium fails to start: unsupported version 0 of Verneed record Status in chromium-browser package in Ubuntu: Incomplete Bug description: Description:Ubuntu 22.04.1 LTS Release:22.04 Just updated before trying to run the chromium. $ chromium-browser /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8) mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record sed: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record md5sum: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record cp: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record md5sum: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record xdg-user-dirs-update: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/snap/command-chain/desktop-launch: line 406: /home/USER/snap/chromium/2221/.config/fontconfig/fonts.conf: No such file or directory ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/snap/command-chain/desktop-launch: line 500: /home/USER/snap/chromium/common/.cache/gdk-pixbuf-loaders.cache: No such file or directory rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/gnome-platform/usr/lib/x86_64-linux-gnu/glib-2.0/gio-querymodules: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed
[Desktop-packages] [Bug 1998409] Snap.ChromiumPrefs.txt
apport information ** Attachment added: "Snap.ChromiumPrefs.txt" https://bugs.launchpad.net/bugs/1998409/+attachment/5634620/+files/Snap.ChromiumPrefs.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1998409 Title: [snap] chromium fails to start: unsupported version 0 of Verneed record Status in chromium-browser package in Ubuntu: Incomplete Bug description: Description:Ubuntu 22.04.1 LTS Release:22.04 Just updated before trying to run the chromium. $ chromium-browser /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8) mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record sed: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record md5sum: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record cp: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record md5sum: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record xdg-user-dirs-update: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/snap/command-chain/desktop-launch: line 406: /home/USER/snap/chromium/2221/.config/fontconfig/fonts.conf: No such file or directory ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/snap/command-chain/desktop-launch: line 500: /home/USER/snap/chromium/common/.cache/gdk-pixbuf-loaders.cache: No such file or directory rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/gnome-platform/usr/lib/x86_64-linux-gnu/glib-2.0/gio-querymodules: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported
[Desktop-packages] [Bug 1998409] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1998409/+attachment/5634618/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1998409 Title: [snap] chromium fails to start: unsupported version 0 of Verneed record Status in chromium-browser package in Ubuntu: Incomplete Bug description: Description:Ubuntu 22.04.1 LTS Release:22.04 Just updated before trying to run the chromium. $ chromium-browser /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8) mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record sed: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record md5sum: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record cp: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record md5sum: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record xdg-user-dirs-update: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/snap/command-chain/desktop-launch: line 406: /home/USER/snap/chromium/2221/.config/fontconfig/fonts.conf: No such file or directory ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/snap/command-chain/desktop-launch: line 500: /home/USER/snap/chromium/common/.cache/gdk-pixbuf-loaders.cache: No such file or directory rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/gnome-platform/usr/lib/x86_64-linux-gnu/glib-2.0/gio-querymodules: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0
[Desktop-packages] [Bug 1998409] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1998409/+attachment/5634619/+files/ProcModules.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1998409 Title: [snap] chromium fails to start: unsupported version 0 of Verneed record Status in chromium-browser package in Ubuntu: Incomplete Bug description: Description:Ubuntu 22.04.1 LTS Release:22.04 Just updated before trying to run the chromium. $ chromium-browser /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8) mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record sed: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record md5sum: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record cp: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record md5sum: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record xdg-user-dirs-update: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/snap/command-chain/desktop-launch: line 406: /home/USER/snap/chromium/2221/.config/fontconfig/fonts.conf: No such file or directory ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/snap/command-chain/desktop-launch: line 500: /home/USER/snap/chromium/common/.cache/gdk-pixbuf-loaders.cache: No such file or directory rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/gnome-platform/usr/lib/x86_64-linux-gnu/glib-2.0/gio-querymodules: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of
[Desktop-packages] [Bug 1998409] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1998409/+attachment/5634614/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1998409 Title: [snap] chromium fails to start: unsupported version 0 of Verneed record Status in chromium-browser package in Ubuntu: Incomplete Bug description: Description:Ubuntu 22.04.1 LTS Release:22.04 Just updated before trying to run the chromium. $ chromium-browser /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8) mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record sed: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record md5sum: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record cp: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record md5sum: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record xdg-user-dirs-update: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/snap/command-chain/desktop-launch: line 406: /home/USER/snap/chromium/2221/.config/fontconfig/fonts.conf: No such file or directory ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/snap/command-chain/desktop-launch: line 500: /home/USER/snap/chromium/common/.cache/gdk-pixbuf-loaders.cache: No such file or directory rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/gnome-platform/usr/lib/x86_64-linux-gnu/glib-2.0/gio-querymodules: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed
[Desktop-packages] [Bug 1998409] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1998409/+attachment/5634613/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1998409 Title: [snap] chromium fails to start: unsupported version 0 of Verneed record Status in chromium-browser package in Ubuntu: Incomplete Bug description: Description:Ubuntu 22.04.1 LTS Release:22.04 Just updated before trying to run the chromium. $ chromium-browser /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8) mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record sed: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record md5sum: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record cp: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record md5sum: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record xdg-user-dirs-update: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/snap/command-chain/desktop-launch: line 406: /home/USER/snap/chromium/2221/.config/fontconfig/fonts.conf: No such file or directory ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/snap/command-chain/desktop-launch: line 500: /home/USER/snap/chromium/common/.cache/gdk-pixbuf-loaders.cache: No such file or directory rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/gnome-platform/usr/lib/x86_64-linux-gnu/glib-2.0/gio-querymodules: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed
[Desktop-packages] [Bug 1998409] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1998409/+attachment/5634615/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1998409 Title: [snap] chromium fails to start: unsupported version 0 of Verneed record Status in chromium-browser package in Ubuntu: Incomplete Bug description: Description:Ubuntu 22.04.1 LTS Release:22.04 Just updated before trying to run the chromium. $ chromium-browser /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8) mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record sed: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record md5sum: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record cp: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record md5sum: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record xdg-user-dirs-update: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/snap/command-chain/desktop-launch: line 406: /home/USER/snap/chromium/2221/.config/fontconfig/fonts.conf: No such file or directory ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/snap/command-chain/desktop-launch: line 500: /home/USER/snap/chromium/common/.cache/gdk-pixbuf-loaders.cache: No such file or directory rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/gnome-platform/usr/lib/x86_64-linux-gnu/glib-2.0/gio-querymodules: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of
[Desktop-packages] [Bug 1998409] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1998409/+attachment/5634616/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1998409 Title: [snap] chromium fails to start: unsupported version 0 of Verneed record Status in chromium-browser package in Ubuntu: Incomplete Bug description: Description:Ubuntu 22.04.1 LTS Release:22.04 Just updated before trying to run the chromium. $ chromium-browser /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8) mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record sed: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record md5sum: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record cp: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record md5sum: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record xdg-user-dirs-update: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/snap/command-chain/desktop-launch: line 406: /home/USER/snap/chromium/2221/.config/fontconfig/fonts.conf: No such file or directory ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/snap/command-chain/desktop-launch: line 500: /home/USER/snap/chromium/common/.cache/gdk-pixbuf-loaders.cache: No such file or directory rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/gnome-platform/usr/lib/x86_64-linux-gnu/glib-2.0/gio-querymodules: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported
[Desktop-packages] [Bug 1998409] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1998409/+attachment/5634617/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1998409 Title: [snap] chromium fails to start: unsupported version 0 of Verneed record Status in chromium-browser package in Ubuntu: Incomplete Bug description: Description:Ubuntu 22.04.1 LTS Release:22.04 Just updated before trying to run the chromium. $ chromium-browser /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8) mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record sed: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record md5sum: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record cp: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record md5sum: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record xdg-user-dirs-update: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/snap/command-chain/desktop-launch: line 406: /home/USER/snap/chromium/2221/.config/fontconfig/fonts.conf: No such file or directory ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/snap/command-chain/desktop-launch: line 500: /home/USER/snap/chromium/common/.cache/gdk-pixbuf-loaders.cache: No such file or directory rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/gnome-platform/usr/lib/x86_64-linux-gnu/glib-2.0/gio-querymodules: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of
[Desktop-packages] [Bug 1998409] DRM.card0-DP-1.txt
apport information ** Attachment added: "DRM.card0-DP-1.txt" https://bugs.launchpad.net/bugs/1998409/+attachment/5634606/+files/DRM.card0-DP-1.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1998409 Title: [snap] chromium fails to start: unsupported version 0 of Verneed record Status in chromium-browser package in Ubuntu: Incomplete Bug description: Description:Ubuntu 22.04.1 LTS Release:22.04 Just updated before trying to run the chromium. $ chromium-browser /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8) mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record sed: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record md5sum: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record cp: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record md5sum: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record xdg-user-dirs-update: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/snap/command-chain/desktop-launch: line 406: /home/USER/snap/chromium/2221/.config/fontconfig/fonts.conf: No such file or directory ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/snap/command-chain/desktop-launch: line 500: /home/USER/snap/chromium/common/.cache/gdk-pixbuf-loaders.cache: No such file or directory rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/gnome-platform/usr/lib/x86_64-linux-gnu/glib-2.0/gio-querymodules: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0
[Desktop-packages] [Bug 1998409] DRM.card0-HDMI-A-1.txt
apport information ** Attachment added: "DRM.card0-HDMI-A-1.txt" https://bugs.launchpad.net/bugs/1998409/+attachment/5634607/+files/DRM.card0-HDMI-A-1.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1998409 Title: [snap] chromium fails to start: unsupported version 0 of Verneed record Status in chromium-browser package in Ubuntu: Incomplete Bug description: Description:Ubuntu 22.04.1 LTS Release:22.04 Just updated before trying to run the chromium. $ chromium-browser /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8) mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record sed: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record md5sum: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record cp: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record md5sum: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record xdg-user-dirs-update: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/snap/command-chain/desktop-launch: line 406: /home/USER/snap/chromium/2221/.config/fontconfig/fonts.conf: No such file or directory ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/snap/command-chain/desktop-launch: line 500: /home/USER/snap/chromium/common/.cache/gdk-pixbuf-loaders.cache: No such file or directory rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/gnome-platform/usr/lib/x86_64-linux-gnu/glib-2.0/gio-querymodules: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported
[Desktop-packages] [Bug 1998409] DRM.card0-eDP-1.txt
apport information ** Attachment added: "DRM.card0-eDP-1.txt" https://bugs.launchpad.net/bugs/1998409/+attachment/5634608/+files/DRM.card0-eDP-1.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1998409 Title: [snap] chromium fails to start: unsupported version 0 of Verneed record Status in chromium-browser package in Ubuntu: Incomplete Bug description: Description:Ubuntu 22.04.1 LTS Release:22.04 Just updated before trying to run the chromium. $ chromium-browser /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8) mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record sed: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record md5sum: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record cp: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record md5sum: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record xdg-user-dirs-update: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/snap/command-chain/desktop-launch: line 406: /home/USER/snap/chromium/2221/.config/fontconfig/fonts.conf: No such file or directory ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/snap/command-chain/desktop-launch: line 500: /home/USER/snap/chromium/common/.cache/gdk-pixbuf-loaders.cache: No such file or directory rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/gnome-platform/usr/lib/x86_64-linux-gnu/glib-2.0/gio-querymodules: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version
[Desktop-packages] [Bug 1998409] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1998409/+attachment/5634609/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1998409 Title: [snap] chromium fails to start: unsupported version 0 of Verneed record Status in chromium-browser package in Ubuntu: Incomplete Bug description: Description:Ubuntu 22.04.1 LTS Release:22.04 Just updated before trying to run the chromium. $ chromium-browser /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8) mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record sed: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record md5sum: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record cp: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record md5sum: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record xdg-user-dirs-update: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/snap/command-chain/desktop-launch: line 406: /home/USER/snap/chromium/2221/.config/fontconfig/fonts.conf: No such file or directory ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/snap/command-chain/desktop-launch: line 500: /home/USER/snap/chromium/common/.cache/gdk-pixbuf-loaders.cache: No such file or directory rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/gnome-platform/usr/lib/x86_64-linux-gnu/glib-2.0/gio-querymodules: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of
[Desktop-packages] [Bug 1998409] Re: [snap] chromium fails to start: unsupported version 0 of Verneed record
apport information ** Tags added: apport-collected jammy ** Description changed: Description:Ubuntu 22.04.1 LTS Release:22.04 Just updated before trying to run the chromium. $ chromium-browser /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8) mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record sed: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record md5sum: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record cp: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record md5sum: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record xdg-user-dirs-update: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/snap/command-chain/desktop-launch: line 406: /home/USER/snap/chromium/2221/.config/fontconfig/fonts.conf: No such file or directory ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/snap/command-chain/desktop-launch: line 500: /home/USER/snap/chromium/common/.cache/gdk-pixbuf-loaders.cache: No such file or directory rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/gnome-platform/usr/lib/x86_64-linux-gnu/glib-2.0/gio-querymodules: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record dirname: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries:
[Desktop-packages] [Bug 1998409] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1998409/+attachment/5634610/+files/Lspci.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1998409 Title: [snap] chromium fails to start: unsupported version 0 of Verneed record Status in chromium-browser package in Ubuntu: Incomplete Bug description: Description:Ubuntu 22.04.1 LTS Release:22.04 Just updated before trying to run the chromium. $ chromium-browser /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8) mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record sed: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record md5sum: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record cp: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record md5sum: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record xdg-user-dirs-update: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/snap/command-chain/desktop-launch: line 406: /home/USER/snap/chromium/2221/.config/fontconfig/fonts.conf: No such file or directory ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/snap/command-chain/desktop-launch: line 500: /home/USER/snap/chromium/common/.cache/gdk-pixbuf-loaders.cache: No such file or directory rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/gnome-platform/usr/lib/x86_64-linux-gnu/glib-2.0/gio-querymodules: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record
[Desktop-packages] [Bug 1998409] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1998409/+attachment/5634611/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1998409 Title: [snap] chromium fails to start: unsupported version 0 of Verneed record Status in chromium-browser package in Ubuntu: Incomplete Bug description: Description:Ubuntu 22.04.1 LTS Release:22.04 Just updated before trying to run the chromium. $ chromium-browser /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8) mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record sed: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record md5sum: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record cp: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record md5sum: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record xdg-user-dirs-update: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/snap/command-chain/desktop-launch: line 406: /home/USER/snap/chromium/2221/.config/fontconfig/fonts.conf: No such file or directory ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/snap/command-chain/desktop-launch: line 500: /home/USER/snap/chromium/common/.cache/gdk-pixbuf-loaders.cache: No such file or directory rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/gnome-platform/usr/lib/x86_64-linux-gnu/glib-2.0/gio-querymodules: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed
[Desktop-packages] [Bug 1998409] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1998409/+attachment/5634612/+files/Lsusb.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1998409 Title: [snap] chromium fails to start: unsupported version 0 of Verneed record Status in chromium-browser package in Ubuntu: Incomplete Bug description: Description:Ubuntu 22.04.1 LTS Release:22.04 Just updated before trying to run the chromium. $ chromium-browser /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8) mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record sed: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record md5sum: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record cp: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record md5sum: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record xdg-user-dirs-update: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/snap/command-chain/desktop-launch: line 406: /home/USER/snap/chromium/2221/.config/fontconfig/fonts.conf: No such file or directory ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/snap/command-chain/desktop-launch: line 500: /home/USER/snap/chromium/common/.cache/gdk-pixbuf-loaders.cache: No such file or directory rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/gnome-platform/usr/lib/x86_64-linux-gnu/glib-2.0/gio-querymodules: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record
[Desktop-packages] [Bug 1998846] [NEW] Adding password manually doesn't work for non-FQDN hosts
Public bug reported: I went to the "Settings", then into "Autofill", then "Password Manager", then clicked on "Add" button to add a new saved password, and tried to enter "Site" as "http://macbook:9000/dev/;. It didn't work because the browser told me "Did you mean http://macbook:9000/dev/.com?;. Which is wrong, I meant what I typed. I have a record in my /etc/hosts file for "macbook", there is nothing wrong with that, chromium is able to navigate there, but it can't save its password. Please, fix this. Thanks, Dima ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Adding password manually doesn't work + Adding password manually doesn't work for non-FQDN hosts ** Description changed: I went to the "Settings", then into "Autofill", then "Password Manager", then clicked on "Add" button to add a new saved password, and tried to enter "Site" as "http://macbook:9000/dev/;. It didn't work because the browser told me "Did you mean http://macbook:9000/dev/.com?;. Which is wrong, I meant what I typed. I have a record in my /etc/hosts - file for "macbook:9000", there is nothing wrong with that, chromium is - able to navigate there, but it can't save its password. + file for "macbook", there is nothing wrong with that, chromium is able + to navigate there, but it can't save its password. Please, fix this. Thanks, Dima -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1998846 Title: Adding password manually doesn't work for non-FQDN hosts Status in chromium-browser package in Ubuntu: New Bug description: I went to the "Settings", then into "Autofill", then "Password Manager", then clicked on "Add" button to add a new saved password, and tried to enter "Site" as "http://macbook:9000/dev/;. It didn't work because the browser told me "Did you mean http://macbook:9000/dev/.com?;. Which is wrong, I meant what I typed. I have a record in my /etc/hosts file for "macbook", there is nothing wrong with that, chromium is able to navigate there, but it can't save its password. Please, fix this. Thanks, Dima To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1998846/+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 1998409] Re: [snap] chromium fails to start: unsupported version 0 of Verneed record
Just reproduced the same error: $ chromium-browser /bin/bash: /lib/x86_64-linux-gnu/libdl.so.2: unsupported version 0 of Verdef record /bin/bash: error while loading shared libraries: /lib/x86_64-linux-gnu/libdl.so.2: unsupported version 0 of Verneed record $ Going to collect more data by "apport-collect 1998409" and here is the output from "journalctl -r": Dec 20 17:24:46 galago systemd[2329]: Started snap.chromium.chromium.da76285a-c22f-4a55-a383-c7d84e4759d2.scope. Dec 20 17:24:34 galago wpa_supplicant[971]: wlp59s0: WPA: Group rekeying completed with e4:8d:8c:49:25:11 [GTK=CCMP] Dec 20 17:24:11 galago CRON[3379539]: pam_unix(cron:session): session closed for user bazil Dec 20 17:24:01 galago CRON[3379536]: pam_unix(cron:session): session closed for user bazil as you can see, nothing interesting there. Btw, the Firefox stopped launching as well: $ firefox /bin/bash: /lib/x86_64-linux-gnu/libdl.so.2: unsupported version 0 of Verdef record /bin/bash: error while loading shared libraries: /lib/x86_64-linux-gnu/libdl.so.2: unsupported version 0 of Verneed record $ $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.04.1 LTS Release:22.04 Codename: jammy $ What is going on, guys ?! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1998409 Title: [snap] chromium fails to start: unsupported version 0 of Verneed record Status in chromium-browser package in Ubuntu: New Bug description: Description:Ubuntu 22.04.1 LTS Release:22.04 Just updated before trying to run the chromium. $ chromium-browser /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8) mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record sed: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record md5sum: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record cp: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record md5sum: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record xdg-user-dirs-update: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/snap/command-chain/desktop-launch: line 406: /home/USER/snap/chromium/2221/.config/fontconfig/fonts.conf: No such file or directory ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries:
[Desktop-packages] [Bug 1998846] Re: Adding password manually doesn't work for non-FQDN hosts
** Changed in: chromium-browser (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1998846 Title: Adding password manually doesn't work for non-FQDN hosts Status in chromium-browser package in Ubuntu: Invalid Bug description: I went to the "Settings", then into "Autofill", then "Password Manager", then clicked on "Add" button to add a new saved password, and tried to enter "Site" as "http://macbook:9000/dev/;. It didn't work because the browser told me "Did you mean http://macbook:9000/dev/.com?;. Which is wrong, I meant what I typed. I have a record in my /etc/hosts file for "macbook", there is nothing wrong with that, chromium is able to navigate there, but it can't save its password. Please, fix this. Thanks, Dima To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1998846/+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 1998846] Re: Adding password manually doesn't work for non-FQDN hosts
oh, yeah, sorry. ! I will -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1998846 Title: Adding password manually doesn't work for non-FQDN hosts Status in chromium-browser package in Ubuntu: New Bug description: I went to the "Settings", then into "Autofill", then "Password Manager", then clicked on "Add" button to add a new saved password, and tried to enter "Site" as "http://macbook:9000/dev/;. It didn't work because the browser told me "Did you mean http://macbook:9000/dev/.com?;. Which is wrong, I meant what I typed. I have a record in my /etc/hosts file for "macbook", there is nothing wrong with that, chromium is able to navigate there, but it can't save its password. Please, fix this. Thanks, Dima To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1998846/+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 1998846] Re: Adding password manually doesn't work for non-FQDN hosts
Put it here: https://bugs.chromium.org/p/chromium/issues/detail?id=1396110 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1998846 Title: Adding password manually doesn't work for non-FQDN hosts Status in chromium-browser package in Ubuntu: New Bug description: I went to the "Settings", then into "Autofill", then "Password Manager", then clicked on "Add" button to add a new saved password, and tried to enter "Site" as "http://macbook:9000/dev/;. It didn't work because the browser told me "Did you mean http://macbook:9000/dev/.com?;. Which is wrong, I meant what I typed. I have a record in my /etc/hosts file for "macbook", there is nothing wrong with that, chromium is able to navigate there, but it can't save its password. Please, fix this. Thanks, Dima To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1998846/+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 1998409] [NEW] chromium fails to start: unsupported version 0 of Verneed record
Public bug reported: Description:Ubuntu 22.04.1 LTS Release:22.04 Just updated before trying to run the chromium. $ chromium-browser /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8) mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record sed: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record md5sum: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record cp: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record md5sum: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record xdg-user-dirs-update: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/snap/command-chain/desktop-launch: line 406: /home/USER/snap/chromium/2221/.config/fontconfig/fonts.conf: No such file or directory ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/snap/command-chain/desktop-launch: line 500: /home/USER/snap/chromium/common/.cache/gdk-pixbuf-loaders.cache: No such file or directory rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/gnome-platform/usr/lib/x86_64-linux-gnu/glib-2.0/gio-querymodules: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record dirname: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record dirname: error while loading
[Desktop-packages] [Bug 1998409] Re: chromium fails to start: unsupported version 0 of Verneed record
Hi Chris, ok, here is the problem - i rebooted the ubuntu and it solved the issue. Does it make sense to run the "apport-collect 1998409" ? I just believe it won't give you evidences which I had. Dima -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1998409 Title: chromium fails to start: unsupported version 0 of Verneed record Status in chromium-browser package in Ubuntu: New Bug description: Description:Ubuntu 22.04.1 LTS Release:22.04 Just updated before trying to run the chromium. $ chromium-browser /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8) mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record sed: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record md5sum: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record cp: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record md5sum: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record xdg-user-dirs-update: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/snap/command-chain/desktop-launch: line 406: /home/USER/snap/chromium/2221/.config/fontconfig/fonts.conf: No such file or directory ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record ln: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/snap/command-chain/desktop-launch: line 500: /home/USER/snap/chromium/common/.cache/gdk-pixbuf-loaders.cache: No such file or directory rm: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record /snap/chromium/2221/gnome-platform/usr/lib/x86_64-linux-gnu/glib-2.0/gio-querymodules: error while loading shared libraries: /snap/chromium/2221/gnome-platform/lib/x86_64-linux-gnu/bindtextdomain.so: unsupported version 0 of Verneed record mkdir: error while loading shared libraries:
[Desktop-packages] [Bug 1891338] Re: apparmor misconfigured for evince
This bug appears again in the package evince 42.3-0ubuntu3 in Xubuntu 22.04.2 It looks the same as described by Kenneth Zadeck in the original report, except the message says: 'Failed to execute child process "/usr/bin/xfce4-mime-helper"(Permission denied).' In the dmesg logs I see the following: [ 804.143236] audit: type=1400 audit(1679303089.957:269): apparmor="DENIED" operation="exec" profile="/usr/bin/evince" name="/usr/bin/xfce4-mime-helper" pid=16286 comm="exo-open" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 I edited /etc/apparmor.d/usr.bin.evince # For Xubuntu to launch the browser #include /usr/bin/xfce4-mime-helper ixr, # < adding this line A new message appeared in dmesg logs: [ 838.828241] audit: type=1400 audit(1679303124.641:304): apparmor="DENIED" operation="exec" profile="/usr/bin/evince" name="/usr/bin/snap" pid=16706 comm="xfce4-mime-help" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 I have two browsers Brave and Firefox; and both installed from snap. So I edited /etc/apparmor.d/usr.bin.evince again: # For Xubuntu to launch the browser #include /usr/bin/xfce4-mime-helper ixr, /usr/bin/snap ixr, # < adding this line And it complained again: [ 1268.978351] audit: type=1400 audit(1679303554.790:432): apparmor="DENIED" operation="connect" profile="/usr/bin/evince" name="/run/snapd.socket" pid=20462 comm="brave" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=0 And I edited /etc/apparmor.d/usr.bin.evince again: # For Xubuntu to launch the browser #include /usr/bin/xfce4-mime-helper ixr, /usr/bin/snap ixr, /run/snapd.socket wr, # < adding this line And then I was overwhelmed by the following messages. [ 1817.693397] audit: type=1400 audit(1679304103.502:3198): apparmor="DENIED" operation="open" profile="/usr/bin/evince" name="/snap/brave/216/meta/snap.yaml" pid=25949 comm="brave" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [ 1822.942739] audit: type=1400 audit(1679304108.750:3199): apparmor="DENIED" operation="open" profile="/usr/bin/evince" name="/sys/kernel/mm/transparent_hugepage/hpage_pmd_size" pid=26810 comm="brave" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [ 1822.947632] audit: type=1400 audit(1679304108.754:3200): apparmor="DENIED" operation="open" profile="/usr/bin/evince" name="/proc/cgroups" pid=26810 comm="brave" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [ 1822.949047] audit: type=1400 audit(1679304108.758:3201): apparmor="DENIED" operation="open" profile="/usr/bin/evince" name="/proc/cmdline" pid=26810 comm="brave" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [ 1822.949070] audit: type=1400 audit(1679304108.758:3202): apparmor="DENIED" operation="open" profile="/usr/bin/evince" name="/snap/snapd/18357/usr/lib/snapd/info" pid=26810 comm="brave" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [ 1822.950430] audit: type=1400 audit(1679304108.758:3203): apparmor="DENIED" operation="open" profile="/usr/bin/evince" name="/proc/sys/kernel/seccomp/actions_avail" pid=26810 comm="brave" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [ 1822.950649] audit: type=1400 audit(1679304108.758:3204): apparmor="DENIED" operation="exec" profile="/usr/bin/evince" name="/usr/lib/snapd/snap-seccomp" pid=26816 comm="brave" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 [ 1822.950883] audit: type=1400 audit(1679304108.758:3205): apparmor="DENIED" operation="exec" profile="/usr/bin/evince" name="/usr/bin/systemctl" pid=26817 comm="brave" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 [ 1822.951929] audit: type=1400 audit(1679304108.758:3206): apparmor="DENIED" operation="open" profile="/usr/bin/evince" name="/snap/brave/216/meta/snap.yaml" pid=26810 comm="brave" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [ 1868.523506] audit: type=1400 audit(1679304154.330:3207): apparmor="DENIED" operation="open" profile="/usr/bin/evince" name="/sys/kernel/mm/transparent_hugepage/hpage_pmd_size" pid=27098 comm="brave" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [ 1868.528801] audit: type=1400 audit(1679304154.338:3208): apparmor="DENIED" operation="open" profile="/usr/bin/evince" name="/proc/cgroups" pid=27098 comm="brave" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [ 1868.530290] audit: type=1400 audit(1679304154.338:3209): apparmor="DENIED" operation="open" profile="/usr/bin/evince" name="/proc/cmdline" pid=27098 comm="brave" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [ 1868.530325] audit: type=1400 audit(1679304154.338:3210): apparmor="DENIED" operation="open" profile="/usr/bin/evince" name="/snap/snapd/18357/usr/lib/snapd/info" pid=27098 comm="brave" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [ 1868.531868] audit: type=1400 audit(1679304154.338:3211): apparmor="DENIED" operation="open" profile="/usr/bin/evince"
[Desktop-packages] [Bug 2017573] Re: Font hinting broken on Plasma 23.04
** Also affects: gnome-desktop (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop in Ubuntu. https://bugs.launchpad.net/bugs/2017573 Title: Font hinting broken on Plasma 23.04 Status in gnome-desktop package in Ubuntu: New Status in plasma-desktop package in Ubuntu: Confirmed Bug description: Just upgraded my laptops to Kubuntu 23.04 Lunar Lobster and hinting for all non-commercial fonts seems broken. I used to have decent if not perfect hinting on Ubuntu and Ubuntu Mono font, but now the only fonts that still hint correctly are Microsoft's Verdana and Tahoma etc. Not sure whether the devide is exactly along this line, but it stands out. Tried regenerating font cache (fc-cache -rv) but that didn't help. Operating System: Kubuntu 23.04 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 6.3.0 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-10510U CPU @ 1.80GHz Memory: 31.1 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics Manufacturer: Notebook Product Name: N141CU System Version: Not Applicable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop/+bug/2017573/+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 484855] Re: Can't open files on WebDAV share
Libreoffice 3.5.4 - problem is still actual . Ubuntu 12.04 x64 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/484855 Title: Can't open files on WebDAV share Status in The OpenOffice.org Suite: New Status in “libreoffice” package in Ubuntu: Fix Released Status in “openoffice.org” package in Ubuntu: Won't Fix Bug description: Binary package hint: openoffice.org I have a home server running Ubuntu 8.04 (Hardy) that shares a folder using WebDAV. I can navigate the folder using Nautilus on a client laptop running 9.10 (Karmic) and open any file by double-clicking on them, except for OpenOffice files, in which case I get an error message (see attached screenshot). I also tried from the File - Open menu item in OO.o with identical results: same error message. Steps to reproduce #1 - via Nautilus - Create a shared directory on a server, share it through WebDAV - Connect to the shared directory using a client machine and add that share to the Nautilus bookmarks - Open the shared drive through Nautilus - Navigate to a directory - Double-click on a non-OO.o file (e.g. a PDF or JPG file) - The file opens normally - Double click on an OO.o file (e.g. a .ods OpenOffice Calc or .odt OpenOffice Writer file) Steps to reproduce #2 - via File - Open - Create a shared directory on a server, share it through WebDAV - Connect to the shared directory using a client machine and add that share to the Nautilus bookmarks - Start OpenOffice - Select File - Open - Navigate to a directory - Select an OO.o file to open (e.g. a .ods OpenOffice Calc or .odt OpenOffice Writer file) Expected behaviour - The selected OO.o file opens in the relevant OO.o application Actual behaviour - An error dialogue with the message: General input/output error while accessing /home/user/.gvfs/WebDAV on host/file.ods (see attached screenshot) ProblemType: Bug Architecture: i386 Date: Wed Nov 18 15:38:39 2009 DistroRelease: Ubuntu 9.10 InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5) Package: openoffice.org-core 1:3.1.1-5ubuntu1 ProcEnviron: PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.48-generic SourcePackage: openoffice.org Uname: Linux 2.6.31-14-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/openoffice/+bug/484855/+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 1040781] Re: Network manager sometimes don't connect to network
For Ubuntu 12.10 x64 beta 2 the problem is actual. -- 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/1040781 Title: Network manager sometimes don't connect to network Status in “network-manager-applet” package in Ubuntu: New Bug description: Sometimes, in ~10% cases when I boot to Ubuntu network manager don't want to connect to wired network. In most cases I need to disable networking and enable it to get it working. Sometimes when I need just to turn on or restart the computer and leave it to work with tasks in the startup it starts to be a problem. Updates are the latest. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager-gnome 0.9.4.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-30.47-generic 3.2.27 Uname: Linux 3.2.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu12 Architecture: amd64 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Thu Aug 23 20:02:43 2012 ExecutablePath: /usr/bin/nm-connection-editor IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120817.3) IpRoute: default via 217.147.162.129 dev eth0 proto static 169.254.0.0/16 dev eth0 scope link metric 1000 217.147.162.128/25 dev eth0 proto kernel scope link src 217.147.162.205 metric 1 IwConfig: lono wireless extensions. eth0 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) LANG=ru_UA.UTF-8 SHELL=/bin/bash RfKill: SourcePackage: network-manager-applet UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Проводное соединение 18d94a35f-8d34-4c2c-886a-c9ca2b6ae597 802-3-ethernet1345741377 Чтв 23 Авг 2012 20:02:57 yes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.4.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1040781/+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 1059650] [NEW] [SB-XFi - Creative X-Fi, playback] Sound is distorted
Public bug reported: I have a sound problem since 12.04 x64 release. After booting the system everything is normal until the first sound event (with any software). After the first sound event I hear a big noise. I can switch it off by muting my input microphone settings. But then I can't use the microphone. In 12.10 x64 sometimes I have sound corruption for 3-7 seconds and for now I have no workaround. Updates are the latest. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: alsa-base 1.0.25+dfsg-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4 Uname: Linux 3.5.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.5.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: simplehuman 2396 F pulseaudio /dev/snd/controlC0: simplehuman 2396 F pulseaudio Date: Mon Oct 1 17:21:50 2012 InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20120929) PackageArchitecture: all ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) LANG=ru_UA.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:XFi successful Symptom_Card: GF110 High Definition Audio Controller - HDA NVidia Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Digital clip or distortion, or overdriven sound Title: [SB-XFi - Creative X-Fi, playback] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1304 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: SABERTOOTH X58 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1304:bd08/02/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnSABERTOOTHX58:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug quantal running-unity -- 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/1059650 Title: [SB-XFi - Creative X-Fi, playback] Sound is distorted Status in “alsa-driver” package in Ubuntu: New Bug description: I have a sound problem since 12.04 x64 release. After booting the system everything is normal until the first sound event (with any software). After the first sound event I hear a big noise. I can switch it off by muting my input microphone settings. But then I can't use the microphone. In 12.10 x64 sometimes I have sound corruption for 3-7 seconds and for now I have no workaround. Updates are the latest. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: alsa-base 1.0.25+dfsg-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4 Uname: Linux 3.5.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.5.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: simplehuman 2396 F pulseaudio /dev/snd/controlC0: simplehuman 2396 F pulseaudio Date: Mon Oct 1 17:21:50 2012 InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20120929) PackageArchitecture: all ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) LANG=ru_UA.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:XFi successful Symptom_Card: GF110 High Definition Audio Controller - HDA NVidia Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Digital clip or distortion, or overdriven sound Title: [SB-XFi - Creative X-Fi, playback] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1304 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: SABERTOOTH X58 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1304:bd08/02/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnSABERTOOTHX58:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to:
[Desktop-packages] [Bug 1059650] Re: [SB-XFi - Creative X-Fi, playback] Sound is distorted
-- 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/1059650 Title: [SB-XFi - Creative X-Fi, playback] Sound is distorted Status in “alsa-driver” package in Ubuntu: New Bug description: I have a sound problem since 12.04 x64 release. After booting the system everything is normal until the first sound event (with any software). After the first sound event I hear a big noise. I can switch it off by muting my input microphone settings. But then I can't use the microphone. In 12.10 x64 sometimes I have sound corruption for 3-7 seconds and for now I have no workaround. Updates are the latest. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: alsa-base 1.0.25+dfsg-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4 Uname: Linux 3.5.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.5.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: simplehuman 2396 F pulseaudio /dev/snd/controlC0: simplehuman 2396 F pulseaudio Date: Mon Oct 1 17:21:50 2012 InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20120929) PackageArchitecture: all ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) LANG=ru_UA.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:XFi successful Symptom_Card: GF110 High Definition Audio Controller - HDA NVidia Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Digital clip or distortion, or overdriven sound Title: [SB-XFi - Creative X-Fi, playback] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1304 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: SABERTOOTH X58 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1304:bd08/02/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnSABERTOOTHX58:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1059650/+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 950655] Re: Libreoffice's Icons is missing from launcher
Unity 6.2, Ubuntu 12.10 x64. Now instead of blank space it sometimes shows 2 icons - an unknown icon and Calc icon under it . See attachment. ** Attachment added: An unknown icon and Calc icon under it https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/950655/+attachment/3261864/+files/libreoffice-bug1.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/950655 Title: Libreoffice's Icons is missing from launcher Status in “bamf” package in Ubuntu: Confirmed Status in “libreoffice” package in Ubuntu: Won't Fix Bug description: Hey Guys, i'm here again, because my icons from libreffice are gone from the launcher after an update sometime ago, and by this I wanna meant hat: Not the accelerators are missing, but any icons, even when the program is opened, is show nothing, but a blank space, when I press Alt+Tab is show nothing but a blank space, when I right click on the 'blank space' in launcher, it show me only options to quit, or lock in launcher, with the 'name' field blank. I've tried the basic: apt-get remove apt-get remove --purge apt-get install aptitude purge aptitude install aptitude reinstall Manually create on my launcher folder accelerators, it creates accelerators, but when the softare was open, it open in the 'black space' cited before. Any extra information just ask, and plz say how to obtain. Thanks all of you. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libreoffice 1:3.5.0-2ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9 Uname: Linux 3.2.0-18-generic i686 ApportVersion: 1.94.1-0ubuntu1 Architecture: i386 Date: Fri Mar 9 05:58:02 2012 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012) SourcePackage: libreoffice UpgradeStatus: Upgraded to precise on 2012-02-12 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/950655/+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 1039750] [NEW] Screen is turning off when it must not to
Public bug reported: In settings Brightings and Lock I'm setting not to turn off the screen, but it turns it off. Sometimes reboot will help, but when I set to turn off the screnn for ex. 1 minute - it don't turn it off. Again, sometimes reboot will help ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-control-center 1:3.4.2-0ubuntu8 ProcVersionSignature: Ubuntu 3.5.0-11.11-generic 3.5.2 Uname: Linux 3.5.0-11-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.4-0ubuntu8 Architecture: amd64 Date: Tue Aug 21 23:47:45 2012 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-control-center InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120815) ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANGUAGE=ru_UA:ru LANG=ru_UA.UTF-8 SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug quantal running-unity -- 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/1039750 Title: Screen is turning off when it must not to Status in “gnome-control-center” package in Ubuntu: New Bug description: In settings Brightings and Lock I'm setting not to turn off the screen, but it turns it off. Sometimes reboot will help, but when I set to turn off the screnn for ex. 1 minute - it don't turn it off. Again, sometimes reboot will help ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-control-center 1:3.4.2-0ubuntu8 ProcVersionSignature: Ubuntu 3.5.0-11.11-generic 3.5.2 Uname: Linux 3.5.0-11-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.4-0ubuntu8 Architecture: amd64 Date: Tue Aug 21 23:47:45 2012 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-control-center InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120815) ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANGUAGE=ru_UA:ru LANG=ru_UA.UTF-8 SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1039750/+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 1039750] Re: Screen is turning off when it must not to
-- 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/1039750 Title: Screen is turning off when it must not to Status in “gnome-control-center” package in Ubuntu: New Bug description: In settings Brightings and Lock I'm setting not to turn off the screen, but it turns it off. Sometimes reboot will help, but when I set to turn off the screnn for ex. 1 minute - it don't turn it off. Again, sometimes reboot will help ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-control-center 1:3.4.2-0ubuntu8 ProcVersionSignature: Ubuntu 3.5.0-11.11-generic 3.5.2 Uname: Linux 3.5.0-11-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.4-0ubuntu8 Architecture: amd64 Date: Tue Aug 21 23:47:45 2012 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-control-center InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120815) ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANGUAGE=ru_UA:ru LANG=ru_UA.UTF-8 SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1039750/+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 1040781] [NEW] Network manager sometimes don't connect to network
Public bug reported: Sometimes, in ~10% cases when I boot to Ubuntu network manager don't want to connect to wired network. In most cases I need to disable networking and enable it to get it working. Sometimes when I need just to turn on or restart the computer and leave it to work with tasks in the startup it starts to be a problem. Updates are the latest. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager-gnome 0.9.4.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-30.47-generic 3.2.27 Uname: Linux 3.2.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu12 Architecture: amd64 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Thu Aug 23 20:02:43 2012 ExecutablePath: /usr/bin/nm-connection-editor IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120817.3) IpRoute: default via 217.147.162.129 dev eth0 proto static 169.254.0.0/16 dev eth0 scope link metric 1000 217.147.162.128/25 dev eth0 proto kernel scope link src 217.147.162.205 metric 1 IwConfig: lono wireless extensions. eth0 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) LANG=ru_UA.UTF-8 SHELL=/bin/bash RfKill: SourcePackage: network-manager-applet UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Проводное соединение 18d94a35f-8d34-4c2c-886a-c9ca2b6ae597 802-3-ethernet1345741377 Чтв 23 Авг 2012 20:02:57 yes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.4.0connected enabled enabled enabledenabled disabled ** Affects: network-manager-applet (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise running-unity -- 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/1040781 Title: Network manager sometimes don't connect to network Status in “network-manager-applet” package in Ubuntu: New Bug description: Sometimes, in ~10% cases when I boot to Ubuntu network manager don't want to connect to wired network. In most cases I need to disable networking and enable it to get it working. Sometimes when I need just to turn on or restart the computer and leave it to work with tasks in the startup it starts to be a problem. Updates are the latest. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager-gnome 0.9.4.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-30.47-generic 3.2.27 Uname: Linux 3.2.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu12 Architecture: amd64 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Thu Aug 23 20:02:43 2012 ExecutablePath: /usr/bin/nm-connection-editor IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120817.3) IpRoute: default via 217.147.162.129 dev eth0 proto static 169.254.0.0/16 dev eth0 scope link metric 1000 217.147.162.128/25 dev eth0 proto kernel scope link src 217.147.162.205 metric 1 IwConfig: lono wireless extensions. eth0 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) LANG=ru_UA.UTF-8 SHELL=/bin/bash RfKill: SourcePackage: network-manager-applet UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Проводное соединение 18d94a35f-8d34-4c2c-886a-c9ca2b6ae597 802-3-ethernet1345741377 Чтв 23 Авг 2012 20:02:57 yes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetconnected
[Desktop-packages] [Bug 1040781] Re: Network manager sometimes don't connect to network
-- 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/1040781 Title: Network manager sometimes don't connect to network Status in “network-manager-applet” package in Ubuntu: New Bug description: Sometimes, in ~10% cases when I boot to Ubuntu network manager don't want to connect to wired network. In most cases I need to disable networking and enable it to get it working. Sometimes when I need just to turn on or restart the computer and leave it to work with tasks in the startup it starts to be a problem. Updates are the latest. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager-gnome 0.9.4.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-30.47-generic 3.2.27 Uname: Linux 3.2.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu12 Architecture: amd64 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Thu Aug 23 20:02:43 2012 ExecutablePath: /usr/bin/nm-connection-editor IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120817.3) IpRoute: default via 217.147.162.129 dev eth0 proto static 169.254.0.0/16 dev eth0 scope link metric 1000 217.147.162.128/25 dev eth0 proto kernel scope link src 217.147.162.205 metric 1 IwConfig: lono wireless extensions. eth0 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) LANG=ru_UA.UTF-8 SHELL=/bin/bash RfKill: SourcePackage: network-manager-applet UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Проводное соединение 18d94a35f-8d34-4c2c-886a-c9ca2b6ae597 802-3-ethernet1345741377 Чтв 23 Авг 2012 20:02:57 yes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.4.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1040781/+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 1041061] Re: gsettings-data-convert crashed with signal 5 in g_settings_set_value()
*** This bug is a duplicate of bug 945144 *** https://bugs.launchpad.net/bugs/945144 What common this bug have with bug bug #945144 ? o_O This is a new bug for Ubuntu 12.10. I appears after updating the system. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1041061 Title: gsettings-data-convert crashed with signal 5 in g_settings_set_value() Status in “gconf” package in Ubuntu: New Bug description: It happens from the next boot after the latest updates. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: gconf2 3.2.5-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-11.11-generic 3.5.2 Uname: Linux 3.5.0-11-generic x86_64 ApportVersion: 2.5.1-0ubuntu1 Architecture: amd64 Date: Fri Aug 24 09:35:47 2012 ExecutablePath: /usr/bin/gsettings-data-convert InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120822) ProcCmdline: gsettings-data-convert --file=/usr/lib/compiz/migration/compiz-profile-active-unity.convert ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) LANG=ru_UA.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: gconf StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_settings_set_value () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_settings_set () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () Title: gsettings-data-convert crashed with signal 5 in g_settings_set_value() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1041061/+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 1041061] Re: gsettings-data-convert crashed with signal 5 in g_settings_set_value()
*** This bug is a duplicate of bug 945144 *** https://bugs.launchpad.net/bugs/945144 It affects epiphany-browser (Ubuntu) and not gconf (Ubuntu). An have status Fix released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1041061 Title: gsettings-data-convert crashed with signal 5 in g_settings_set_value() Status in “gconf” package in Ubuntu: New Bug description: It happens from the next boot after the latest updates. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: gconf2 3.2.5-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-11.11-generic 3.5.2 Uname: Linux 3.5.0-11-generic x86_64 ApportVersion: 2.5.1-0ubuntu1 Architecture: amd64 Date: Fri Aug 24 09:35:47 2012 ExecutablePath: /usr/bin/gsettings-data-convert InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120822) ProcCmdline: gsettings-data-convert --file=/usr/lib/compiz/migration/compiz-profile-active-unity.convert ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) LANG=ru_UA.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: gconf StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_settings_set_value () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_settings_set () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () Title: gsettings-data-convert crashed with signal 5 in g_settings_set_value() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1041061/+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 1039750] Re: Screen is turning off when it must not to
I think the problem is fixed for now. -- 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/1039750 Title: Screen is turning off when it must not to Status in “gnome-control-center” package in Ubuntu: Confirmed Bug description: In settings Brightings and Lock I'm setting not to turn off the screen, but it turns it off. Sometimes reboot will help, but when I set to turn off the screnn for ex. 1 minute - it don't turn it off. Again, sometimes reboot will help ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-control-center 1:3.4.2-0ubuntu8 ProcVersionSignature: Ubuntu 3.5.0-11.11-generic 3.5.2 Uname: Linux 3.5.0-11-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.4-0ubuntu8 Architecture: amd64 Date: Tue Aug 21 23:47:45 2012 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-control-center InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120815) ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANGUAGE=ru_UA:ru LANG=ru_UA.UTF-8 SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1039750/+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 950655] Re: Libreoffice's Icons is missing from launcher
To my last comment: Unity 6.4, Ubuntu 12.10 x64. The problem is still there. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/950655 Title: Libreoffice's Icons is missing from launcher Status in “bamf” package in Ubuntu: Confirmed Status in “libreoffice” package in Ubuntu: Won't Fix Bug description: Hey Guys, i'm here again, because my icons from libreffice are gone from the launcher after an update sometime ago, and by this I wanna meant hat: Not the accelerators are missing, but any icons, even when the program is opened, is show nothing, but a blank space, when I press Alt+Tab is show nothing but a blank space, when I right click on the 'blank space' in launcher, it show me only options to quit, or lock in launcher, with the 'name' field blank. I've tried the basic: apt-get remove apt-get remove --purge apt-get install aptitude purge aptitude install aptitude reinstall Manually create on my launcher folder accelerators, it creates accelerators, but when the softare was open, it open in the 'black space' cited before. Any extra information just ask, and plz say how to obtain. Thanks all of you. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libreoffice 1:3.5.0-2ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9 Uname: Linux 3.2.0-18-generic i686 ApportVersion: 1.94.1-0ubuntu1 Architecture: i386 Date: Fri Mar 9 05:58:02 2012 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111012) SourcePackage: libreoffice UpgradeStatus: Upgraded to precise on 2012-02-12 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bamf/+bug/950655/+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
