[Desktop-packages] [Bug 1226962] Re: Hotkeys not functional in non-latin keyboard layout in 13.10 and 14.04
Thanks a lot to Michael Zheludkov for the fix, but I want Intellij Idea hotkeys to work out of the box without any workarounds. Just as they worked before. When will this be possible in ubuntu? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1226962 Title: Hotkeys not functional in non-latin keyboard layout in 13.10 and 14.04 Status in LibreOffice Productivity Suite: Invalid Status in IBus: New Status in Indicator keyboard: Fix Released Status in Mutter: New Status in The OpenOffice.org Suite: New Status in Unity: Invalid Status in “gnome-settings-daemon” package in Ubuntu: In Progress Status in “indicator-keyboard” package in Ubuntu: Fix Released Status in “gnome-settings-daemon” package in Fedora: Unknown Bug description: New keyboard layout changer in Ubuntu 13.10 introduce old-new bug. Any system or application hotkey witch use char (for example: ctrl+alt+t for terminal or ctrl+t for new tab in browser) become unfunctional when selected non-latin keyboard layout. Hotkeys with F1-12, numbers and other non-character buttons works perfectly. Window manager hotkeys not affected by this bug. All hotkeys in system parameters-keyboard-hotkeys-windows works perfect with any keyboard layout. Workaround for some system hotkeys and two layouts (english and non- latin): rebind all hotkeys in your local layout. For example instead of ctrl+alt+t use ctrl+alt+τ (greek tau). That hotkey still work with english layout. If you use english and two different non-latin layouts this workaround helps only with one of them. -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1226962/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1276354] Re: False GPU lockup IPEHR: 0x0a000001 IPEHR: 0x01000000
*** This bug is a duplicate of bug 1274779 *** https://bugs.launchpad.net/bugs/1274779 ** This bug has been marked a duplicate of bug 1274779 [ivb] hang on pageflip (IPEHR: 0x0a01) -- 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/1276354 Title: False GPU lockup IPEHR: 0x0a01 IPEHR: 0x0100 Status in “xserver-xorg-video-intel” package in Ubuntu: New Bug description: I'm not sure what caused this, but if it matters I was using Chrome when it happened. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-intel 2:2.99.907-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0 Uname: Linux 3.13.0-6-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Feb 4 15:58:48 2014 DistUpgraded: 2014-02-03 23:06:12,804 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.2, 3.11.0-17-generic, x86_64: installed virtualbox, 4.3.2, 3.13.0-6-generic, x86_64: installed DuplicateSignature: GPU lockup IPEHR: 0x0a01 IPEHR: 0x0100 Ubuntu 14.04 ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:0240] InstallationDate: Installed on 2014-01-22 (13 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130402.1) InterpreterPath: /usr/bin/python3.3 MachineType: System76, Inc. Pangolin Performance ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-6-generic root=UUID=fa99195d-c106-4086-99fe-186bd84be2b4 ro acpi_os_name=Linux acpi_osi= RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu8 libdrm2 2.4.52-1 xserver-xorg-video-intel 2:2.99.907-0ubuntu1 SourcePackage: xserver-xorg-video-intel Title: False GPU lockup IPEHR: 0x0a01 IPEHR: 0x0100 UpgradeStatus: Upgraded to trusty on 2014-02-04 (0 days ago) UserGroups: dmi.bios.date: 06/25/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: Pangolin Performance dmi.board.vendor: System76, Inc. dmi.board.version: panp9 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd06/25/2012:svnSystem76,Inc.:pnPangolinPerformance:pvrpanp9:rvnSystem76,Inc.:rnPangolinPerformance:rvrpanp9:cvnNoEnclosure:ct10:cvrN/A: dmi.product.name: Pangolin Performance dmi.product.version: panp9 dmi.sys.vendor: System76, Inc. version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.0.1-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.0.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.907-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu1 xserver.bootTime: Mon Feb 3 23:06:45 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 826 vendor LGD xserver.version: 2:1.14.5-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1276354/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1275703] Re: unity-greeter crashed with signal 5 in atspi_dbus_connection_setup_with_g_main()
** Changed in: unity-greeter (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1275703 Title: unity-greeter crashed with signal 5 in atspi_dbus_connection_setup_with_g_main() Status in “unity-greeter” package in Ubuntu: Fix Released Bug description: . ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: unity-greeter 14.04.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0 Uname: Linux 3.13.0-6-generic x86_64 ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 Date: Mon Feb 3 11:57:23 2014 ExecutablePath: /usr/sbin/unity-greeter InstallationDate: Installed on 2013-06-05 (242 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130605) ProcCmdline: /usr/sbin/unity-greeter Signal: 5 SourcePackage: unity-greeter StacktraceTop: atspi_dbus_connection_setup_with_g_main () from /usr/lib/x86_64-linux-gnu/libatspi.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libatk-bridge-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libatk-bridge-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: unity-greeter crashed with signal 5 in atspi_dbus_connection_setup_with_g_main() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1275703/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1265065] Re: Desktop freeze while drag-maximizing window
I have what I assume is the same problem. This only happens on 2 of my 3 machines that run Ubuntu 13.10. Both of these use the Nvidia proprientary driver. The one is a GTX 560 while the other is a GTX610M. I've attached a picture of what it looks like when it freezes. The mouse pointer sill moves but there is no response to input. I can use ctrl- alt-f1 to switch to a terminal though and restarting lightdm restores my computer to a working state. ** Attachment added: IMG_20140204_133427.jpg https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1265065/+attachment/3969633/+files/IMG_20140204_133427.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1265065 Title: Desktop freeze while drag-maximizing window Status in “xorg” package in Ubuntu: Incomplete Bug description: It has happened today twice at 22:23 and 22:54. I laft click with mouse on firefox titlebar and try to drag it up against taskbar to make FF windo to maximize. I see this shadow/animation of window about to extend its borders and desktop freezes. I do not remember if mouse still moves. I go to another console Ctrl+Alt+1, log in, and execute pkill -U username that brings me back to logon screen. Ubuntu 13.10 64-bit ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Dec 30 22:32:14 2013 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Once a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: I don't know GraphicsCard: NVIDIA Corporation GF104 [GeForce GTX 460] [10de:0e22] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:350c] InstallationDate: Installed on 2013-11-30 (30 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Gigabyte Technology Co., Ltd. Z68X-UD3-B3 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=9ee8cef8-09ae-4ab5-8422-7392354e9e26 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F1 dmi.board.name: Z68X-UD3-B3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd04/15/2011:svnGigabyteTechnologyCo.,Ltd.:pnZ68X-UD3-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnZ68X-UD3-B3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: Z68X-UD3-B3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Mon Dec 30 11:53:22 2013 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB-PS/2 Optical Mouse MOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 inputWC060 Series HD Webcam KEYBOARD, id 10 xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.14.5-1ubuntu2~saucy1 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1265065/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1276443] Re: Please merge poppler 0.24.5-2 from Debian experimental
Note: our fix_qt52_build.patch is named upstream_fix_qt5_moc_detection.diff in Debian. ** Description changed: Debian recently uploaded new Poppler with Qt 5 support and merged some our changes. Also, Qt 5 support there is done more properly, i.e. qt4-visiblity.diff was extended to Qt 5, and the symbols file was added. Thus I have prepared yet another merge. + + This also greatly reduces our delta, and will make next merges easier. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1276443 Title: Please merge poppler 0.24.5-2 from Debian experimental Status in “poppler” package in Ubuntu: New Bug description: Debian recently uploaded new Poppler with Qt 5 support and merged some our changes. Also, Qt 5 support there is done more properly, i.e. qt4-visiblity.diff was extended to Qt 5, and the symbols file was added. Thus I have prepared yet another merge. This also greatly reduces our delta, and will make next merges easier. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1276443/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1276443] Re: Please merge poppler 0.24.5-2 from Debian experimental
** Patch added: ubuntu-ubuntu.debdiff https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1276443/+attachment/3969645/+files/ubuntu-ubuntu.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1276443 Title: Please merge poppler 0.24.5-2 from Debian experimental Status in “poppler” package in Ubuntu: New Bug description: Debian recently uploaded new Poppler with Qt 5 support and merged some our changes. Also, Qt 5 support there is done more properly, i.e. qt4-visiblity.diff was extended to Qt 5, and the symbols file was added. Thus I have prepared yet another merge. This also greatly reduces our delta, and will make next merges easier. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1276443/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1276443] [NEW] Please merge poppler 0.24.5-2 from Debian experimental
Public bug reported: Debian recently uploaded new Poppler with Qt 5 support and merged some our changes. Also, Qt 5 support there is done more properly, i.e. qt4-visiblity.diff was extended to Qt 5, and the symbols file was added. Thus I have prepared yet another merge. This also greatly reduces our delta, and will make next merges easier. ** Affects: poppler (Ubuntu) Importance: Undecided Status: New ** Tags: patch trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1276443 Title: Please merge poppler 0.24.5-2 from Debian experimental Status in “poppler” package in Ubuntu: New Bug description: Debian recently uploaded new Poppler with Qt 5 support and merged some our changes. Also, Qt 5 support there is done more properly, i.e. qt4-visiblity.diff was extended to Qt 5, and the symbols file was added. Thus I have prepared yet another merge. This also greatly reduces our delta, and will make next merges easier. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1276443/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1276443] Re: Please merge poppler 0.24.5-2 from Debian experimental
** Patch added: debian-ubuntu.debdiff https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1276443/+attachment/3969644/+files/debian-ubuntu.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1276443 Title: Please merge poppler 0.24.5-2 from Debian experimental Status in “poppler” package in Ubuntu: New Bug description: Debian recently uploaded new Poppler with Qt 5 support and merged some our changes. Also, Qt 5 support there is done more properly, i.e. qt4-visiblity.diff was extended to Qt 5, and the symbols file was added. Thus I have prepared yet another merge. This also greatly reduces our delta, and will make next merges easier. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1276443/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1139712] Re: Not possible to get audio output via internal speakers, when plug is inserted in heaphone jack
Manual muting of Speaker and Headphone works even if Auto-mute is
enabled. I am satisfied with the current behavior.
** Summary changed:
- Not possible to get audio output via internal speakers, when plug is inserted
in heaphone jack
+ Not possible to get audio output via internal speakers, when a plug is
inserted in the heaphone jack, and Auto-Mute Mode is Enabled.
** Changed in: alsa-driver (Ubuntu)
Status: New = Invalid
--
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/1139712
Title:
Not possible to get audio output via internal speakers, when a plug is
inserted in the heaphone jack, and Auto-Mute Mode is Enabled.
Status in “alsa-driver” package in Ubuntu:
Invalid
Bug description:
Note: not using pulseaudio
I have a mixer for speakers in alsamixer, but it is not effective,
when a plug is inserted in headphone jack.
I want this to happen:
Speaker mixer should be effective in alsamixer always. It should be
configurable, what happens to internal speaker sound, when a plug is inserted
in headphone jack.
BTW. I tried pulseaudio, but it does not work there either. It is even
more confusing and there are also other issues why I am not using
pulseaudio.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: alsa-base 1.0.25+dfsg-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-38.61-generic 3.2.37
Uname: Linux 3.2.0-38-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
Subdevices: 0/1
Subdevice #0: subdevice #0
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xf034 irq 43'
Mixer name : 'Realtek ALC272'
Components : 'HDA:10ec0272,144dca00,0011'
Controls : 21
Simple ctrls : 12
Date: Sat Mar 2 12:10:03 2013
EcryptfsInUse: Yes
InstallationMedia: Xubuntu 10.04 Lucid Lynx - Release i386 (20100429)
MarkForUpload: True
PackageArchitecture: all
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
SourcePackage: alsa-driver
Symptom: audio
UpgradeStatus: Upgraded to precise on 2012-11-03 (118 days ago)
dmi.bios.date: 09/08/2009
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 11CA.M015.20090908.RHU
dmi.board.name: NC10
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnPhoenixTechnologiesLtd.:bvr11CA.M015.20090908.RHU:bd09/08/2009:svnSAMSUNGELECTRONICSCO.,LTD.:pnNC10:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNC10:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
dmi.product.name: NC10
dmi.product.version: Not Applicable
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1139712/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1182522] Re: Replugging a Usb headphone does not restore the previous output and level
Hi Raymond, could you at least confirm the Bug please ? It's not only a problem of storing the level, the USB headphone is getting sound without being selected in the ubuntu sound Panel. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1182522 Title: Replugging a Usb headphone does not restore the previous output and level Status in “pulseaudio” package in Ubuntu: New Bug description: ubuntu 12.04.2 (Upgraded from ubuntu 12.04.1 ) How to reproduce the problem: - Plug a USB headset, select it in the sound prefs and set the volume. - Unplug/replug the headset - Open the sound preferences : the headset is not selected but the sound is output through the usb headset at maximum volume. This killed my ears several times, I'm almost deaf now To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1182522/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1276448] [NEW] Please update pidgin to 2.10.9
*** This bug is a security vulnerability *** Public security bug reported: New version contains important security updates: CVE-2013-6484 CVE-2013-6479 CVE-2013-6485 CVE-2013-6478 CVE-2013-6486 CVE-2013-6487 CVE-2014-0020 CVE-2013-6482 CVE-2013-6489 CVE-2013-6490 CVE-2013-6483 CVE-2013-6477 CVE-2012-6152 CVE-2013-6481 It also add Unity integration plugin. lsb_release -rd Description:Ubuntu 13.10 Release:13.10 apt-cache policy pidgin pidgin: Installed: 1:2.10.7-0ubuntu4.1 Candidate: 1:2.10.7-0ubuntu4.1 Version table: *** 1:2.10.7-0ubuntu4.1 0 500 http://ru.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: pidgin (Ubuntu) Importance: Undecided Status: New ** Tags: upgrade-software-version ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pidgin in Ubuntu. https://bugs.launchpad.net/bugs/1276448 Title: Please update pidgin to 2.10.9 Status in “pidgin” package in Ubuntu: New Bug description: New version contains important security updates: CVE-2013-6484 CVE-2013-6479 CVE-2013-6485 CVE-2013-6478 CVE-2013-6486 CVE-2013-6487 CVE-2014-0020 CVE-2013-6482 CVE-2013-6489 CVE-2013-6490 CVE-2013-6483 CVE-2013-6477 CVE-2012-6152 CVE-2013-6481 It also add Unity integration plugin. lsb_release -rd Description: Ubuntu 13.10 Release: 13.10 apt-cache policy pidgin pidgin: Installed: 1:2.10.7-0ubuntu4.1 Candidate: 1:2.10.7-0ubuntu4.1 Version table: *** 1:2.10.7-0ubuntu4.1 0 500 http://ru.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/1276448/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1264543] Re: Trusty sometimes boots with inactive keyboard .....
Is this a duplicate of bug 128? -- 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/1264543 Title: Trusty sometimes boots with inactive keyboard . Status in “lightdm” package in Ubuntu: Confirmed Status in “xorg-server” package in Ubuntu: Confirmed Bug description: Every third or fourth boot, the keyboard is not found although it is accessible by grub2 and by pressing CTRL+ALT+F2 and withing the terminal. Logout and login from the terminal followed by CTRL+ALT+F7 to reaccess X does not bring back the keyboard. My current workaround is to use suspend and then reactivate. This always finds the keyboard after which all is normal. The problem began after an update to something (I'm not sure what as the problem is spasmodic). It was first noticed some two or three weeks ago. WORKAROUND: Works in Lubuntu 14.04. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-input-all 1:7.7+1ubuntu7 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.12.7-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity CurrentDmesg: [ 26.884218] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready [ 550.563790] audit_printk_skb: 138 callbacks suppressed [ 550.563794] type=1400 audit(1388145574.597:67): apparmor=STATUS operation=profile_replace parent=2768 profile=unconfined name=/usr/lib/cups/backend/cups-pdf pid=2772 comm=apparmor_parser [ 550.563802] type=1400 audit(1388145574.597:68): apparmor=STATUS operation=profile_replace parent=2768 profile=unconfined name=/usr/sbin/cupsd pid=2772 comm=apparmor_parser [ 550.564387] type=1400 audit(1388145574.597:69): apparmor=STATUS operation=profile_replace parent=2768 profile=unconfined name=/usr/sbin/cupsd pid=2772 comm=apparmor_parser Date: Fri Dec 27 16:23:05 2013 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7560D] [1002:9904] (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation Device [1849:9901] InstallationDate: Installed on 2013-10-21 (67 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20131021) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.12.0-7-generic root=UUID=b0a5ccea-5d55-4be4-838d-195afa498cc5 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/03/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: FM2A55M-VG3 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd05/03/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A55M-VG3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.libdrm2: libdrm2 2.4.50-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.0.1-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.0.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu1 xserver.bootTime: Fri Dec 27 11:50:49 2013 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech Optical USB Mouse MOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.14.5-1ubuntu2 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1264543/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages
[Desktop-packages] [Bug 1048131] Re: unity-greeter crashed with SIGSEGV in gdk_window_get_type_hint()
** Branch linked: lp:unity-greeter/0.2 ** Branch linked: lp:unity-greeter/12.10 ** Branch linked: lp:unity-greeter/13.04 ** Branch linked: lp:unity-greeter/13.10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1048131 Title: unity-greeter crashed with SIGSEGV in gdk_window_get_type_hint() Status in “unity-greeter” package in Ubuntu: Triaged Status in “unity-greeter” source package in Precise: Confirmed Status in “unity-greeter” source package in Quantal: Won't Fix Bug description: [Impact] Unity Greeter can crash when X clients create X windows. This results in Ubuntu going to failsafe mode. When an X window appears Unity Greeter receives a Map event. Unity Greeter attempts to get a GdkWindow object for the window in the event. If the window was destroyed before it does this it gets a NULL pointer. Unity Greeter did not check for this case. [Test Case] This is a bug that only occurs if windows rapidly appear and disappear. Can be verified on machines that are exhibiting the problem (perhaps linked to indicators failing to start). Check errors.ubuntu.com shows problem does not occur when fix applied. [Regression Potential] Low, the change just checks for the NULL pointer and ignores the map event. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1048131/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1276463] [NEW] Unity broken after latest Trusty upgrade: unable to load module ccp
Public bug reported: Unity does not work after latest upgrade in Trusty. ~$ unity compiz (core) - Info: Loading plugin: core compiz (core) - Info: Starting plugin: core compiz (core) - Info: Loading plugin: ccp compiz (core) - Error: Failed to load plugin: ccp ~$ unity -v compiz (core) - Info: Loading plugin: core compiz (core) - Debug: Trying to load core from: /home/franck/.compiz-1/plugins/libcore.so compiz (core) - Debug: dlopen failed: /home/franck/.compiz-1/plugins/libcore.so: cannot open shared object file: No such file or directory compiz (core) - Debug: Trying to load core from: /usr/lib/compiz/libcore.so compiz (core) - Debug: dlopen failed: /usr/lib/compiz/libcore.so: cannot open shared object file: No such file or directory compiz (core) - Info: Starting plugin: core compiz (core) - Debug: Started plugin: core compiz (core) - Debug: pending request: compiz (core) - Debug: - event serial: 1560 compiz (core) - Debug: - event window 0x290 compiz (core) - Debug: - x: 0 y: 0 width: 0 height: 0 border: 0, sibling: 0x0 compiz (core) - Debug: pending request: compiz (core) - Debug: - event serial: 1624 compiz (core) - Debug: - event window 0x293 compiz (core) - Debug: - x: 0 y: 0 width: 722 height: 434 border: 0, sibling: 0x290 compiz (core) - Debug: pending request: compiz (core) - Debug: - event serial: 1689 compiz (core) - Debug: - event window 0x296 compiz (core) - Debug: - x: 0 y: 0 width: 1920 height: 1080 border: 0, sibling: 0x293 compiz (core) - Debug: pending request: compiz (core) - Debug: - event serial: 1754 compiz (core) - Debug: - event window 0x299 compiz (core) - Debug: - x: 0 y: 0 width: 722 height: 434 border: 0, sibling: 0x296 compiz (core) - Debug: pending request: compiz (core) - Debug: - event serial: 1819 compiz (core) - Debug: - event window 0x29c compiz (core) - Debug: - x: 0 y: 0 width: 1920 height: 1080 border: 0, sibling: 0x299 compiz (core) - Debug: pending request: compiz (core) - Debug: - event serial: 1884 compiz (core) - Debug: - event window 0x29f compiz (core) - Debug: - x: 0 y: 0 width: 722 height: 434 border: 0, sibling: 0x29c compiz (core) - Debug: pending request: compiz (core) - Debug: - event serial: 1949 compiz (core) - Debug: - event window 0x2a2 compiz (core) - Debug: - x: 0 y: 0 width: 1920 height: 1080 border: 0, sibling: 0x29f compiz (core) - Debug: pending request: compiz (core) - Debug: - event serial: 2014 compiz (core) - Debug: - event window 0x2a5 compiz (core) - Debug: - x: 0 y: 0 width: 722 height: 434 border: 0, sibling: 0x2a2 compiz (core) - Info: Loading plugin: ccp compiz (core) - Debug: Trying to load ccp from: /home/franck/.compiz-1/plugins/libccp.so compiz (core) - Debug: dlopen failed: /home/franck/.compiz-1/plugins/libccp.so: cannot open shared object file: No such file or directory compiz (core) - Debug: Trying to load ccp from: /usr/lib/compiz/libccp.so compiz (core) - Debug: dlopen failed: /usr/lib/libcompizconfig.so.0: undefined symbol: _ZN6google8protobuf18GoogleOnceInitImplEPlPNS0_7ClosureE compiz (core) - Debug: Trying to load ccp from: libccp.so compiz (core) - Debug: dlopen failed: libccp.so: cannot open shared object file: No such file or directory compiz (core) - Error: Failed to load plugin: ccp compiz (core) - Debug: refusing to manage window 0x290 compiz (core) - Debug: received event: compiz (core) - Debug: - event serial: 1560 compiz (core) - Debug: - event window 0x290 compiz (core) - Debug: - x: 0 y: 0 width: 0 height: 0 border: 0, sibling: 0x0 compiz (core) - Debug: refusing to manage window 0x293 compiz (core) - Debug: received event: compiz (core) - Debug: - event serial: 1624 compiz (core) - Debug: - event window 0x293 compiz (core) - Debug: - x: 0 y: 0 width: 722 height: 434 border: 0, sibling: 0x290 compiz (core) - Debug: refusing to manage window 0x296 compiz (core) - Debug: received event: compiz (core) - Debug: - event serial: 1689 compiz (core) - Debug: - event window 0x296 compiz (core) - Debug: - x: 0 y: 0 width: 1920 height: 1080 border: 0, sibling: 0x293 compiz (core) - Debug: refusing to manage window 0x299 compiz (core) - Debug: received event: compiz (core) - Debug: - event serial: 1754 compiz (core) - Debug: - event window 0x299 compiz (core) - Debug: - x: 0 y: 0 width: 722 height: 434 border: 0, sibling: 0x296 compiz (core) - Debug: refusing to manage window 0x29c compiz (core) - Debug: received event: compiz (core) - Debug: - event serial: 1819 compiz (core) - Debug: - event window 0x29c compiz (core) - Debug: - x: 0 y: 0 width: 1920 height: 1080 border: 0, sibling: 0x299 compiz (core) - Debug: refusing to manage window 0x29f compiz (core) - Debug: received event: compiz (core) - Debug: - event serial: 1884 compiz (core) - Debug: - event window 0x29f compiz (core) - Debug: - x: 0 y: 0 width: 722 height: 434 border: 0, sibling: 0x29c compiz (core) -
[Desktop-packages] [Bug 903194] Re: multiseat not set up correctly
** Tags added: precise
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/903194
Title:
multiseat not set up correctly
Status in Light Display Manager:
In Progress
Status in “lightdm” package in Ubuntu:
In Progress
Bug description:
I have a multiseat xorg.conf setup on Arch Linux (with ServerLayouts
called seat-chris and seat-brynn)
Based on the below details, it seems that -sharevts is needed, but not
handled correctly by lightdm
If I use a fairly minimal config, I get:
When lightdm starts, Seat 0 is activated
Ctrl-Alt-F8 on Seat 0 kbd activates Seat 1 (deactivates Seat 0)
Ctrl-Alt-F7 on Seat 1 kbd activates Seat 0 (deactivates Seat 1)
lightdm.conf:
[LightDM]
start-default-seat=false
[SeatDefaults]
session-wrapper=/etc/lightdm/Xsession
xserver-config=xorg.conf.multiseat
[Seat:0]
xserver-layout=seat-chris
[Seat:1]
xserver-layout=seat-brynn
pstree
---
lightdm,9833 /etc/init.d/lightdm start
`-lightdm,9834
|-X,9839 :0 -config xorg.conf.multiseat -layout seat-chris -auth
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
|-X,9841 :1 -config xorg.conf.multiseat -layout seat-brynn -auth
/var/run/lightdm/root/:1 -nolisten tcp vt8 -novtswitch
|-lightdm-gtk-gre,9860
| `-{lightdm-gtk-gr},9861
|-lightdm-gtk-gre,9881
| `-{lightdm-gtk-gr},9882
|-{lightdm},9837
|-{lightdm},9840
|-{lightdm},9863
`-{lightdm},9884
When I use the sharevts flag on Seat 1, I see the following:
On lightdm start, Seat 0 is activated
After a second or so, Seat 0 goes blank, and Seat 1 is activated
Pressing Ctrl-Alt-F7 on Seat 1 activates Seat 0 again, and I can log in on
both correctly
lightdm.conf
-
[LightDM]
start-default-seat=false
[SeatDefaults]
session-wrapper=/etc/lightdm/Xsession
xserver-config=xorg.conf.multiseat
greeter-hide-users=false
[Seat:0]
xserver-layout=seat-chris
[Seat:1]
xserver-command=/usr/bin/X -sharevts
xserver-layout=seat-brynn
pstree
---
lightdm,21164 /etc/init.d/lightdm start
`-lightdm,21165
|-X,21171 :0 -config xorg.conf.multiseat -layout seat-chris -auth
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
|-X,21173 -sharevts :1 -config xorg.conf.multiseat -layout seat-brynn
-auth /var/run/lightdm/root/:1 -nolisten tcp vt8 -novtswitch
|-lightdm-gtk-gre,21192
| `-{lightdm-gtk-gr},21193
|-lightdm-gtk-gre,21210
| `-{lightdm-gtk-gr},21211
|-{lightdm},21168
|-{lightdm},21172
|-{lightdm},21195
`-{lightdm},21215
If I try sharevts on both sessions, I see the following:
On lightdm start, Seat 1 starts up
Seat 0 shows a mouse pointer on a text mode console printing the kernel
message 'Invalid Framebuffer ID'
If I force kill lightdm and restart it using the init.d service, then it
starts correctly
lightdm.conf
--
[LightDM]
start-default-seat=false
[SeatDefaults]
session-wrapper=/etc/lightdm/Xsession
xserver-config=xorg.conf.multiseat
greeter-hide-users=false
[Seat:0]
xserver-command=/usr/bin/X -sharevts
xserver-layout=seat-chris
[Seat:1]
xserver-command=/usr/bin/X -sharevts
xserver-layout=seat-brynn
pstree
lightdm,32594 /etc/init.d/lightdm start
`-lightdm,32595
|-X,32599 -sharevts :0 -config xorg.conf.multiseat -layout seat-chris
-auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
|-X,32603 -sharevts :1 -config xorg.conf.multiseat -layout seat-brynn
-auth /var/run/lightdm/root/:1 -nolisten tcp vt8 -novtswitch
|-lightdm-gtk-gre,32620
| `-{lightdm-gtk-gr},32623
|-lightdm-gtk-gre,32640
| `-{lightdm-gtk-gr},32643
|-{lightdm},32598
|-{lightdm},32600
|-{lightdm},32645
`-{lightdm},4109
To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/903194/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1276443] Re: Please merge poppler 0.24.5-2 from Debian experimental
** Patch added: ubuntu-ubuntu.debdiff https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1276443/+attachment/3969689/+files/ubuntu-ubuntu.debdiff ** Description changed: Debian recently uploaded new Poppler with Qt 5 support and merged some our changes. Also, Qt 5 support there is done more properly, i.e. qt4-visiblity.diff was extended to Qt 5, and the symbols file was added. Thus I have prepared yet another merge. This also greatly reduces our delta, and will make next merges easier. + + Upd: reuploaded debdiffs with correct changelogs merging. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1276443 Title: Please merge poppler 0.24.5-2 from Debian experimental Status in “poppler” package in Ubuntu: New Bug description: Debian recently uploaded new Poppler with Qt 5 support and merged some our changes. Also, Qt 5 support there is done more properly, i.e. qt4-visiblity.diff was extended to Qt 5, and the symbols file was added. Thus I have prepared yet another merge. This also greatly reduces our delta, and will make next merges easier. Upd: reuploaded debdiffs with correct changelogs merging. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1276443/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1276443] Re: Please merge poppler 0.24.5-2 from Debian experimental
** Patch removed: debian-ubuntu.debdiff https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1276443/+attachment/3969644/+files/debian-ubuntu.debdiff ** Patch added: debian-ubuntu.debdiff https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1276443/+attachment/3969688/+files/debian-ubuntu.debdiff ** Patch removed: ubuntu-ubuntu.debdiff https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1276443/+attachment/3969645/+files/ubuntu-ubuntu.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1276443 Title: Please merge poppler 0.24.5-2 from Debian experimental Status in “poppler” package in Ubuntu: New Bug description: Debian recently uploaded new Poppler with Qt 5 support and merged some our changes. Also, Qt 5 support there is done more properly, i.e. qt4-visiblity.diff was extended to Qt 5, and the symbols file was added. Thus I have prepared yet another merge. This also greatly reduces our delta, and will make next merges easier. Upd: reuploaded debdiffs with correct changelogs merging. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1276443/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1276379] Re: fglrx-installer 2:13.101-0ubuntu0.0.1 not suitable on AMD RV710/M92 Mobility Radeon HD 4570
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: fglrx-installer (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1276379 Title: fglrx-installer 2:13.101-0ubuntu0.0.1 not suitable on AMD RV710/M92 Mobility Radeon HD 4570 Status in “fglrx-installer” package in Ubuntu: Confirmed Bug description: 1)Description:Ubuntu 12.04.4 LTS Release: 12.04 Architecture: amd64 2) apt-cache policy fglrx fglrx-amdcccle fglrx: Installé : 2:13.101-0ubuntu0.0.1 Candidat : 2:13.101-0ubuntu0.0.1 Table de version : *** 2:13.101-0ubuntu0.0.1 0 500 http://fr.archive.ubuntu.com/ubuntu/ precise-updates/restricted amd64 Packages 100 /var/lib/dpkg/status 2:8.960-0ubuntu1 0 500 http://fr.archive.ubuntu.com/ubuntu/ precise/restricted amd64 Packages fglrx-amdcccle: Installé : 2:13.101-0ubuntu0.0.1 Candidat : 2:13.101-0ubuntu0.0.1 3) I expected that the driver will : - set up - work 4) It did'nt work : - Ubuntu was very slow - Unity was in lo-fi - when I taped CTRL+SUPER, desktops appears blue - fglrx-amdcccle failed - fans were turning at a high speed ~$ sudo aticonfig aticonfig: No supported adapters detected ~$ lspci -nn | grep VGA02:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] RV710/M92 [Mobility Radeon HD 4530/4570/545v] [1002:9553] ~$ grep /drivers/ /var/log/Xorg.0.log [26.888] (II) Loading /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so [27.015] (II) Loading /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so [27.016] (II) Loading /usr/lib/xorg/modules/drivers/ati_drv.so [27.017] (II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so [27.018] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so [27.019] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so [27.122] (II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so ~$ dmesg | grep fglrx [ 28.612217] [fglrx] Maximum main memory to use for locked dma buffers: 3657 MBytes. [ 28.613015] [fglrx:firegl_init_device_list] *ERROR* No supported display adapters were found [ 28.613021] [fglrx:firegl_init_module] *ERROR* firegl_init_devices failed [ 28.775649] [fglrx] Maximum main memory to use for locked dma buffers: 3657 MBytes. [ 28.776032] [fglrx:firegl_init_device_list] *ERROR* No supported display adapters were found [ 28.776036] [fglrx:firegl_init_module] *ERROR* firegl_init_devices failed ~$ fglrxinfo X Error of failed request: BadRequest (invalid request code or no such operation) Major opcode of failed request: 153 (GLX) Minor opcode of failed request: 19 (X_GLXQueryServerString) Serial number of failed request: 12 Current serial number in output stream: 12 ~$ glxinfo name of display: :0.0 X Error of failed request: BadRequest (invalid request code or no such operation) Major opcode of failed request: 153 (GLX) Minor opcode of failed request: 19 (X_GLXQueryServerString) Serial number of failed request: 12 Current serial number in output stream: 12 5) Workaround I had to downgrade manually the driver to the old 8.960 which works without problem. I tried to do an apt-get remove fglrx fglrx-amdcccle but apt-get gaves me fglrx-updates in replacement , with the same issues. I experimented fglrx-update some months (a year?) ago with similar problems, but at that time it was a conscient experimentation. The 13.101-0ubuntu0.0.1 could maybe stay in fglrx-updates, and no fglrx ? ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: fglrx 2:8.960-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.2.0-58.88-generic 3.2.53 Uname: Linux 3.2.0-58-generic x86_64 NonfreeKernelModules: wl fglrx .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz Date: Wed Feb 5 00:59:13 2014 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu DkmsStatus: bcmwl, 6.20.155.1+bdcom, 3.2.0-55-generic, x86_64: installed bcmwl, 6.20.155.1+bdcom, 3.2.0-56-generic, x86_64: installed bcmwl, 6.20.155.1+bdcom, 3.2.0-57-generic, x86_64: installed bcmwl, 6.20.155.1+bdcom, 3.2.0-58-generic, x86_64: installed fglrx, 8.960, 3.2.0-58-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV710/M92 [Mobility Radeon HD 4530/4570/545v]
[Desktop-packages] [Bug 1250312] Re: Numerous RadeonSI and RadeonCI issues
mesa is at 10.0.1 now, 10.1 will follow later.. so no issues left here - closing ** Changed in: mesa (Ubuntu) Status: New = Invalid -- 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/1250312 Title: Numerous RadeonSI and RadeonCI issues Status in “mesa” package in Ubuntu: Invalid Bug description: Ubuntu 14.04 Firstly, there is the problem that Mesa is heavily outdated (9.2.2). Mesa 10 officially releases on November 27th but it would be highly admirable to see it arrive here earlier. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-radeon 1:7.2.0-0ubuntu10 ProcVersionSignature: Ubuntu 3.12.0-2.5-generic 3.12.0 Uname: Linux 3.12.0-2-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.6-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDmesg: [ 17.232779] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 33.631080] RPC: AUTH_GSS upcall timed out. [ 33.631080] Please check user daemon is running. [ 107.097114] systemd-hostnamed[3494]: Warning: nss-myhostname is not installed. Changing the local hostname might make it unresolveable. Please install nss-myhostname! Date: Mon Nov 11 22:51:25 2013 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti PRO [Radeon HD 7950] [1002:679a] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:254c] InstallationDate: Installed on 2013-11-12 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (2013) MachineType: To be filled by O.E.M. To be filled by O.E.M. MarkForUpload: True ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.12.0-2-generic root=UUID=dd113cbe-a785-4235-a179-2dc66efcf1c1 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1604 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH 990FX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1604:bd10/16/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-4 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu1 xserver.bootTime: Mon Nov 11 22:26:43 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.14.3-3ubuntu4 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1250312/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1276379] Re: fglrx-installer 2:13.101-0ubuntu0.0.1 not suitable on AMD RV710/M92 Mobility Radeon HD 4570
Hi, I have the samme issue with 'ATI Radeon HD 3470'. $ fglrxinfo display: :0 screen: 0 OpenGL vendor string: Advanced Micro Devices, Inc. OpenGL renderer string: ATI Radeon HD 3470 OpenGL version string: 3.3.11627 Compatibility Profile Context $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 12.04.4 LTS Release:12.04 Codename: precise -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1276379 Title: fglrx-installer 2:13.101-0ubuntu0.0.1 not suitable on AMD RV710/M92 Mobility Radeon HD 4570 Status in “fglrx-installer” package in Ubuntu: Confirmed Bug description: 1)Description:Ubuntu 12.04.4 LTS Release: 12.04 Architecture: amd64 2) apt-cache policy fglrx fglrx-amdcccle fglrx: Installé : 2:13.101-0ubuntu0.0.1 Candidat : 2:13.101-0ubuntu0.0.1 Table de version : *** 2:13.101-0ubuntu0.0.1 0 500 http://fr.archive.ubuntu.com/ubuntu/ precise-updates/restricted amd64 Packages 100 /var/lib/dpkg/status 2:8.960-0ubuntu1 0 500 http://fr.archive.ubuntu.com/ubuntu/ precise/restricted amd64 Packages fglrx-amdcccle: Installé : 2:13.101-0ubuntu0.0.1 Candidat : 2:13.101-0ubuntu0.0.1 3) I expected that the driver will : - set up - work 4) It did'nt work : - Ubuntu was very slow - Unity was in lo-fi - when I taped CTRL+SUPER, desktops appears blue - fglrx-amdcccle failed - fans were turning at a high speed ~$ sudo aticonfig aticonfig: No supported adapters detected ~$ lspci -nn | grep VGA02:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] RV710/M92 [Mobility Radeon HD 4530/4570/545v] [1002:9553] ~$ grep /drivers/ /var/log/Xorg.0.log [26.888] (II) Loading /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so [27.015] (II) Loading /usr/lib/x86_64-linux-gnu/xorg/extra-modules/extra-modules.dpkg-tmp/modules/drivers/fglrx_drv.so [27.016] (II) Loading /usr/lib/xorg/modules/drivers/ati_drv.so [27.017] (II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so [27.018] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so [27.019] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so [27.122] (II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so ~$ dmesg | grep fglrx [ 28.612217] [fglrx] Maximum main memory to use for locked dma buffers: 3657 MBytes. [ 28.613015] [fglrx:firegl_init_device_list] *ERROR* No supported display adapters were found [ 28.613021] [fglrx:firegl_init_module] *ERROR* firegl_init_devices failed [ 28.775649] [fglrx] Maximum main memory to use for locked dma buffers: 3657 MBytes. [ 28.776032] [fglrx:firegl_init_device_list] *ERROR* No supported display adapters were found [ 28.776036] [fglrx:firegl_init_module] *ERROR* firegl_init_devices failed ~$ fglrxinfo X Error of failed request: BadRequest (invalid request code or no such operation) Major opcode of failed request: 153 (GLX) Minor opcode of failed request: 19 (X_GLXQueryServerString) Serial number of failed request: 12 Current serial number in output stream: 12 ~$ glxinfo name of display: :0.0 X Error of failed request: BadRequest (invalid request code or no such operation) Major opcode of failed request: 153 (GLX) Minor opcode of failed request: 19 (X_GLXQueryServerString) Serial number of failed request: 12 Current serial number in output stream: 12 5) Workaround I had to downgrade manually the driver to the old 8.960 which works without problem. I tried to do an apt-get remove fglrx fglrx-amdcccle but apt-get gaves me fglrx-updates in replacement , with the same issues. I experimented fglrx-update some months (a year?) ago with similar problems, but at that time it was a conscient experimentation. The 13.101-0ubuntu0.0.1 could maybe stay in fglrx-updates, and no fglrx ? ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: fglrx 2:8.960-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.2.0-58.88-generic 3.2.53 Uname: Linux 3.2.0-58-generic x86_64 NonfreeKernelModules: wl fglrx .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz Date: Wed Feb 5 00:59:13 2014 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu DkmsStatus: bcmwl, 6.20.155.1+bdcom, 3.2.0-55-generic, x86_64: installed bcmwl, 6.20.155.1+bdcom, 3.2.0-56-generic, x86_64: installed bcmwl, 6.20.155.1+bdcom, 3.2.0-57-generic, x86_64:
[Desktop-packages] [Bug 997483] Re: VT_WAITACTIVE does not work well with a multiseat setup
** Tags added: precise -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/997483 Title: VT_WAITACTIVE does not work well with a multiseat setup Status in Light Display Manager: In Progress Status in “lightdm” package in Ubuntu: In Progress Bug description: Related to the fix introduced in bug #851612 . Saw this in lightdm.log (system call interrupted because of ctrl-alt-del pressed): [+2.97s] DEBUG: New display ready, switching to it [+2.97s] DEBUG: Activating VT 8 [+77.56s] WARNING: Error using VT_WAITACTIVE 8 on /dev/console: Interrupted system call [+77.56s] DEBUG: Got signal 15 from process 1 [+77.56s] DEBUG: Caught Terminated signal, shutting down And in x-1-greeter.log: [+0.48s] DEBUG: Loading users from org.freedesktop.Accounts [+0.48s] DEBUG: Loading user /org/freedesktop/Accounts/User1001 [+0.50s] DEBUG: Loading user /org/freedesktop/Accounts/User1000 [+50.56s] WARNING: Error getting session list from org.freedesktop.DisplayManager: Timeout was reached On vt7, unity-greeter would get stuck after password input. On vt8, unity-greeter appears after that getting session list timeout, which is about a minute later than vt7, and does not have a password input field. lightdm blocked by VT_WAITACTIVE may be the cause... Tested with lightdm 1.2.0-0ubuntu2 in precise. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/997483/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1048131] Re: unity-greeter crashed with SIGSEGV in gdk_window_get_type_hint()
** Also affects: unity-greeter (Ubuntu Saucy) Importance: Undecided Status: New ** Changed in: unity-greeter (Ubuntu Saucy) Importance: Undecided = Medium ** Changed in: unity-greeter (Ubuntu Precise) Status: Confirmed = In Progress ** Changed in: unity-greeter (Ubuntu) Status: Triaged = In Progress ** Changed in: unity-greeter (Ubuntu Precise) Assignee: (unassigned) = Robert Ancell (robert-ancell) ** Changed in: unity-greeter (Ubuntu Quantal) Status: Won't Fix = Triaged ** Changed in: unity-greeter (Ubuntu Saucy) Status: New = Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1048131 Title: unity-greeter crashed with SIGSEGV in gdk_window_get_type_hint() Status in “unity-greeter” package in Ubuntu: In Progress Status in “unity-greeter” source package in Precise: In Progress Status in “unity-greeter” source package in Quantal: Triaged Status in “unity-greeter” source package in Saucy: Triaged Bug description: [Impact] Unity Greeter can crash when X clients create X windows. This results in Ubuntu going to failsafe mode. When an X window appears Unity Greeter receives a Map event. Unity Greeter attempts to get a GdkWindow object for the window in the event. If the window was destroyed before it does this it gets a NULL pointer. Unity Greeter did not check for this case. [Test Case] This is a bug that only occurs if windows rapidly appear and disappear. Can be verified on machines that are exhibiting the problem (perhaps linked to indicators failing to start). Check errors.ubuntu.com shows problem does not occur when fix applied. [Regression Potential] Low, the change just checks for the NULL pointer and ignores the map event. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1048131/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 977547] Re: doesn't switch to graphical VT when auto login is turned on, (multiseat)
** Tags added: precise -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/977547 Title: doesn't switch to graphical VT when auto login is turned on, (multiseat) Status in Light Display Manager: In Progress Status in “lightdm” package in Ubuntu: In Progress Bug description: I have a working multiseat system with the 2nd seat Displaylink-based USB touchscreen. the 2nd seat auto-logs in fine, and the first seat (AMD) comes up fine to lightdm. If i set autologinup, then the 2nd seat starts fine, but the first seat is blank until i ctrl-alt-f7 at which it logs in. is it this in my Xorg, does it need to VT switch agressively like lightdm usually does, or is it this in my Xorg: Section ServerLayout Option AllowEmptyInput true EndSection To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/977547/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1276443] Re: Please merge poppler 0.24.5-2 from Debian experimental
Thanks for the work! ** Changed in: poppler (Ubuntu) Importance: Undecided = Wishlist ** Changed in: poppler (Ubuntu) Status: New = Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1276443 Title: Please merge poppler 0.24.5-2 from Debian experimental Status in “poppler” package in Ubuntu: Fix Committed Bug description: Debian recently uploaded new Poppler with Qt 5 support and merged some our changes. Also, Qt 5 support there is done more properly, i.e. qt4-visiblity.diff was extended to Qt 5, and the symbols file was added. Thus I have prepared yet another merge. This also greatly reduces our delta, and will make next merges easier. Upd: reuploaded debdiffs with correct changelogs merging. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1276443/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1276448] Re: Please update pidgin to 2.10.9
** Description changed: New version contains important security updates: CVE-2013-6484 CVE-2013-6479 CVE-2013-6485 CVE-2013-6478 CVE-2013-6486 CVE-2013-6487 CVE-2014-0020 CVE-2013-6482 CVE-2013-6489 CVE-2013-6490 CVE-2013-6483 CVE-2013-6477 CVE-2012-6152 CVE-2013-6481 - It also add Unity integration plugin. + It also add Unity integration plugin. + + https://developer.pidgin.im/wiki/ChangeLog lsb_release -rd Description: Ubuntu 13.10 Release: 13.10 apt-cache policy pidgin pidgin: - Installed: 1:2.10.7-0ubuntu4.1 - Candidate: 1:2.10.7-0ubuntu4.1 - Version table: - *** 1:2.10.7-0ubuntu4.1 0 - 500 http://ru.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages - 100 /var/lib/dpkg/status + Installed: 1:2.10.7-0ubuntu4.1 + Candidate: 1:2.10.7-0ubuntu4.1 + Version table: + *** 1:2.10.7-0ubuntu4.1 0 + 500 http://ru.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages + 100 /var/lib/dpkg/status -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pidgin in Ubuntu. https://bugs.launchpad.net/bugs/1276448 Title: Please update pidgin to 2.10.9 Status in “pidgin” package in Ubuntu: New Bug description: New version contains important security updates: CVE-2013-6484 CVE-2013-6479 CVE-2013-6485 CVE-2013-6478 CVE-2013-6486 CVE-2013-6487 CVE-2014-0020 CVE-2013-6482 CVE-2013-6489 CVE-2013-6490 CVE-2013-6483 CVE-2013-6477 CVE-2012-6152 CVE-2013-6481 It also add Unity integration plugin. https://developer.pidgin.im/wiki/ChangeLog lsb_release -rd Description: Ubuntu 13.10 Release: 13.10 apt-cache policy pidgin pidgin: Installed: 1:2.10.7-0ubuntu4.1 Candidate: 1:2.10.7-0ubuntu4.1 Version table: *** 1:2.10.7-0ubuntu4.1 0 500 http://ru.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/1276448/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1275113] Re: Update to 2.10.9
Thanks, the debdiff in the current comment fails to apply though, patch says it's incorrectly formatted ... does it work for you? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pidgin in Ubuntu. https://bugs.launchpad.net/bugs/1275113 Title: Update to 2.10.9 Status in “pidgin” package in Ubuntu: New Bug description: Please update pidgin to 2.10.8. This adds python3 support The depends may need changing, but i'm not sure how To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/1275113/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1249067] Re: nvidia prime causes freeze at start up
it looks like a configuration problem: Error: alternatives are not set up properly what's the output of the following commands? 1) update-alternatives --display x86_64-linux-gnu_gl_conf 2) update-alternatives --display i386-linux-gnu_gl_conf -- 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/1249067 Title: nvidia prime causes freeze at start up Status in “nvidia-prime” package in Ubuntu: Fix Released Bug description: I believe nvidia-prime modified my xorg.conf to use intel during boot. I had to remove xorg.conf to enable my system to boot to unity again. I've attached the file that caused the problem. My system has onboard intel graphics on the motherboard, and a beefcake nvidia card to which my monitors are connected. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: nvidia-prime 0.4.2~hybrid0.0.1 ProcVersionSignature: Ubuntu 3.8.0-33.48~precise1-generic 3.8.13.11 Uname: Linux 3.8.0-33-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Fri Nov 8 06:07:51 2013 InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release amd64 (20130820.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1249067/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1262856] Re: cannot report xorg bug in precise daily image
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apport (Ubuntu) Status: New = Confirmed -- 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/1262856 Title: cannot report package issues using ubuntu-bug in precise daily image Status in “apport” package in Ubuntu: Confirmed Status in “xorg” package in Ubuntu: Invalid Status in “apport” source package in Precise: Confirmed Status in “xorg” source package in Precise: Invalid Bug description: I noticed a display server bug whilst running a precise desktop image. I've attempted to execute ubuntu-bug xorg but I have been informed firstly if i require, desire, or already have technical support and later I've answered questions if I know how to do git bisect and want to attach logs. After all these steps, I was informed that this problem cannot be reported. (screenshot to be attached) Is there something I'm doing wrong, or should we not suggest people to file X bugs with ubuntu-bug xorg as documented on the iso tracker? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1262856/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1262856] Re: cannot report xorg bug in precise daily image
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apport (Ubuntu Precise) Status: New = Confirmed -- 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/1262856 Title: cannot report package issues using ubuntu-bug in precise daily image Status in “apport” package in Ubuntu: Confirmed Status in “xorg” package in Ubuntu: Invalid Status in “apport” source package in Precise: Confirmed Status in “xorg” source package in Precise: Invalid Bug description: I noticed a display server bug whilst running a precise desktop image. I've attempted to execute ubuntu-bug xorg but I have been informed firstly if i require, desire, or already have technical support and later I've answered questions if I know how to do git bisect and want to attach logs. After all these steps, I was informed that this problem cannot be reported. (screenshot to be attached) Is there something I'm doing wrong, or should we not suggest people to file X bugs with ubuntu-bug xorg as documented on the iso tracker? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1262856/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1274822] Re: latest update breaks nvidia-prime and produces blank screen
The fact that /var/log/prime-offload.log is missing, means that the program that is supposed to tell the system to use prime is not being used. Please attach the following files: 1) /etc/lightdm/lightdm.conf 2) all the files in /etc/lightdm/lightdm.conf.d/ You can still use pastebin as you did before. -- 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/1274822 Title: latest update breaks nvidia-prime and produces blank screen Status in “nvidia-prime” package in Ubuntu: Incomplete Bug description: I'm currently using a laptop with optimus technology and NVidia graphic card. Last year (2013) I installed NVidia-prime and it worked perfectly. However, the very recent update (2014/1/29) broke NVidia- prime. The screen turned into complete blackness after Ubuntu splash screen (the purple one), and was even not showing cursor. However, from several difference behaviors I am sure that everything else (like terminals, keyboard inputs and even games) is working properly after login. Ubuntu version: 14.04 (Trusty Tahr) nvidia-prime version: 0.5.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1274822/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 329898] Re: The HP 1018 printer not work out of the box if used non-US locale
This issue is still is. Should we create a new report or can we change the status of this old one? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/329898 Title: The HP 1018 printer not work out of the box if used non-US locale Status in HP Linux Imaging and Printing: New Status in Release Notes for Ubuntu: Won't Fix Status in “hplip” package in Ubuntu: Fix Released Status in “ibus” package in Ubuntu: Fix Released Status in “hplip” source package in Lucid: Won't Fix Status in “ibus” source package in Lucid: Invalid Status in “hplip” source package in Maverick: Won't Fix Status in “ibus” source package in Maverick: Won't Fix Bug description: This bug is continuation of the bug 217215. To avoid any problems related to attempts describe I decided to start with 'clean account'. (and created the new bug entry) Clean account means: 1) Remove hplip*, foo2zjs, footomatic package. 2) Remove any further files related to hp1018 find /usr/share -name *1018* ./foo2zjs/firmware/sihp1018.img ./ppd/hpijs/HP/hp_laserjet_1018-hpijs.ppd 3) Remove orphaned /usr/share/hplip directory After restarting the printer a system message appear pointing that new hardware had been installed and suggesting that hpijs package support the HP 1018 printer. I: - installed hpijs with depends - Ran Printer configure tool: a driver for HP 1018 hadn't been found - so I chose suggested HP 1015 driver - printer didn't react for send packages. To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/329898/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1262856] Re: cannot report xorg bug in precise daily image
Using the 2014-02-05 ISO for Precise (12.04.04), I have the same issue with every package that I tried. It seems that ubuntu-bug will not work with a live CD or USB thumb drive boot. ** Summary changed: - cannot report xorg bug in precise daily image + cannot report package issues using ubuntu-bug in precise daily image -- 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/1262856 Title: cannot report package issues using ubuntu-bug in precise daily image Status in “apport” package in Ubuntu: Confirmed Status in “xorg” package in Ubuntu: Invalid Status in “apport” source package in Precise: Confirmed Status in “xorg” source package in Precise: Invalid Bug description: I noticed a display server bug whilst running a precise desktop image. I've attempted to execute ubuntu-bug xorg but I have been informed firstly if i require, desire, or already have technical support and later I've answered questions if I know how to do git bisect and want to attach logs. After all these steps, I was informed that this problem cannot be reported. (screenshot to be attached) Is there something I'm doing wrong, or should we not suggest people to file X bugs with ubuntu-bug xorg as documented on the iso tracker? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1262856/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1276072] Re: Language selection always falls back to English
Well, after a few complementary tests, I found out that this is a lightdm bug! In fact, on one computer (using Xubuntu), the session's options, as session's type (Unity, Gnome, xfce, openbox, ...) and language (!), are not kept from one session to the next, as it used to be, and need to set manually at each connection. On the other computer (using Lubuntu), only the type option seems to be kept, not the language which has to be set manually... I did not find any bug report about lightdm. Can this bug be changed, or should I create a new one? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1276072 Title: Language selection always falls back to English Status in “language-selector” package in Ubuntu: Incomplete Bug description: I upgraded two amd64 computers from 13.04 to 13.10, and discovered on both that the language is set to English (whereas I selected French language at the beginning of the upgrade). Moreover, each time I set it back to French, dragging both French (France and Canada) and some English (UK US) on top of the default English in the language selection list, default English comes back on top at next login. I even tried to modify my .pam_environment (in console mode) and the /etc/environment to set fr_FR as the default, no way: gnome-language- selector seems to force default English as default at each connection! Hopefully, I do understand English, but this is turning me mad. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: language-selector-gnome 0.116 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Tue Feb 4 10:48:33 2014 InstallationDate: Installed on 2013-07-29 (190 days ago) InstallationMedia: Xubuntu 13.04 Raring Ringtail - Release amd64 (20130423.1) MarkForUpload: True PackageArchitecture: all SourcePackage: language-selector UpgradeStatus: Upgraded to saucy on 2014-02-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1276072/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1276098] Re: Sound: Background tints around listboxes and sliders
Turns out this is a bug in the Ubuntu theme's styling of GtkFrame, not a bug in either -control-center. You can also see it in software- properties-gtk, behind many of the checkboxes and a few of the listboxes. ** Also affects: ubuntu-themes (Ubuntu) Importance: Undecided Status: New ** No longer affects: gnome-control-center (Ubuntu) ** No longer affects: unity-control-center (Ubuntu) ** Summary changed: - Sound: Background tints around listboxes and sliders + Ugly background tint for GtkFrame inside a tab ** Changed in: ubuntu-themes (Ubuntu) Assignee: (unassigned) = Lars Uebernickel (larsu) -- 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/1276098 Title: Ugly background tint for GtkFrame inside a tab Status in “ubuntu-themes” package in Ubuntu: In Progress Bug description: gnome-control-center 1:3.6.3-0ubuntu45.2, Ubuntu 13.10 1. Open the Sound panel. 2. Flip through the tabs and look at the listboxes and sliders. What you see: the background is tinted darker than the rest of the tab (a) above all listboxes (b) to the right of the Play sound through listbox (c) to the right of the Record sound from listbox (d) behind all sliders. What you should see: The background color in these areas is the same as the rest of the tab. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1276098/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1276536] [NEW] Compiz CPU load with open radeon drivers on Trusty
Public bug reported: lsb_release -rd Description:Ubuntu Trusty Tahr (development branch) Release:14.04 apt-cache policy compiz compiz: Установлен: 1:0.9.10+13.10.20131011-0ubuntu4 Кандидат: 1:0.9.10+13.10.20131011-0ubuntu4 Таблица версий: *** 1:0.9.10+13.10.20131011-0ubuntu4 0 500 http://ru.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status I have AMD Phenom II X4 975 (3.6 x 4) and AMD Radeon R7 260X (and tried HD 7770 instead R7 260X). Use open video drivers. Compiz load 30-40 % per 1 core of my CPU without any action on screen. If I tried to move window CPU load (all 4 cores) is about 70-80%. Other PC with CPU Intel i5-2500 (Intel HD Graphics) do not have that problem. ** Affects: compiz (Ubuntu) Importance: Undecided Status: New ** Attachment added: screenshot 2014-02-05 21:06:23.png https://bugs.launchpad.net/bugs/1276536/+attachment/3969777/+files/screenshot%202014-02-05%2021%3A06%3A23.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1276536 Title: Compiz CPU load with open radeon drivers on Trusty Status in “compiz” package in Ubuntu: New Bug description: lsb_release -rd Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 apt-cache policy compiz compiz: Установлен: 1:0.9.10+13.10.20131011-0ubuntu4 Кандидат: 1:0.9.10+13.10.20131011-0ubuntu4 Таблица версий: *** 1:0.9.10+13.10.20131011-0ubuntu4 0 500 http://ru.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status I have AMD Phenom II X4 975 (3.6 x 4) and AMD Radeon R7 260X (and tried HD 7770 instead R7 260X). Use open video drivers. Compiz load 30-40 % per 1 core of my CPU without any action on screen. If I tried to move window CPU load (all 4 cores) is about 70-80%. Other PC with CPU Intel i5-2500 (Intel HD Graphics) do not have that problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1276536/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1276536] Re: Compiz CPU load with open radeon drivers on Trusty
** Package changed: unity (Ubuntu) = compiz (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1276536 Title: Compiz CPU load with open radeon drivers on Trusty Status in “compiz” package in Ubuntu: New Bug description: lsb_release -rd Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 apt-cache policy compiz compiz: Установлен: 1:0.9.10+13.10.20131011-0ubuntu4 Кандидат: 1:0.9.10+13.10.20131011-0ubuntu4 Таблица версий: *** 1:0.9.10+13.10.20131011-0ubuntu4 0 500 http://ru.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status I have AMD Phenom II X4 975 (3.6 x 4) and AMD Radeon R7 260X (and tried HD 7770 instead R7 260X). Use open video drivers. Compiz load 30-40 % per 1 core of my CPU without any action on screen. If I tried to move window CPU load (all 4 cores) is about 70-80%. Other PC with CPU Intel i5-2500 (Intel HD Graphics) do not have that problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1276536/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 491310] Re: htmldoc crashed with SIGSEGV in __libc_start_main()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: htmldoc (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to htmldoc in Ubuntu. https://bugs.launchpad.net/bugs/491310 Title: htmldoc crashed with SIGSEGV in __libc_start_main() Status in “htmldoc” package in Ubuntu: Confirmed Bug description: Binary package hint: htmldoc while converting this document : http://www.kofax.com/support/ascent/capture/8/docs/KC8_API_Reference_Guide.zip with commandline : chm2pdf --book APIRef.chm APIRef_book.pdf ended with : ERR003: Too many chapters/files in document (1000 1000)! ERR003: Too many chapters/files in document (1000 1000)! ERR003: Too many chapters/files in document (1000 1000)! PAGES: 4614 BYTES: 6835186 Something wrong happened when launching htmldoc. exit value: 1280 Check if output exists or if it is good. Done. ProblemType: Crash Architecture: amd64 Date: Wed Dec 2 11:35:41 2009 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/bin/htmldoc InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027) NonfreeKernelModules: nvidia Package: htmldoc 1.8.27-4 ProcCmdline: htmldoc --duplex --format pdf14 --jpeg=100 --linkcolor blue --header c\ C --size a4 --linkstyle plain --embedfonts --bodyfont times --book --footer c\ C /tmp/tmpl_wfEH/APIRef/temp0001.html /tmp/tmpl_wfEH/APIRef/temp0002.html /tmp/tmpl_wfEH/APIRef/temp0003.html /tmp/tmpl_wfEH/APIRef/temp0004.html /tmp/tmpl_wfEH/APIRef/temp0005.html /tmp/tmpl_wfEH/APIRef/temp0006.html /tmp/tmpl_wfEH/APIRef/temp0007.html /tmp/tmpl_wfEH/APIRef/temp0008.html /tmp/tmpl_wfEH/APIRef/temp0009.html /tmp/tmpl_wfEH/APIRef/temp0010.html /tmp/tmpl_wfEH/APIRef/temp0011.html /tmp/tmpl_wfEH/APIRef/temp0012.html /tmp/tmpl_wfEH/APIRef/temp0013.html /tmp/tmpl_wfEH/APIRef/temp0014.html /tmp/tmpl_wfEH/APIRef/temp0015.html /tmp/tmpl_wfEH/APIRef/temp0016.html /tmp/tmpl_wfEH/APIRef/temp0017.html /tmp/tmpl_wfEH/APIRef/temp0018.html /tmp/tmpl_wfEH/APIRef/temp0019.html /tmp/tmpl_wfEH/APIRef/temp0020.html /tmp/tmpl_wfEH/APIRef/temp0021.html /tmp/tmpl_wfEH/APIRef/temp0022.html /tmp/tmpl_wfEH/APIRef/temp0023.html /tmp/tmpl_wfEH/APIRef/temp0024.html /tmp/tmpl_wfEH/APIRef/temp0025.html /tmp/tmpl_wfEH/APIRef/temp0026.html /tmp/tmpl_wfEH/APIRef/temp0027.html /tmp/tmpl_wfEH/APIRef/temp0028.html /tmp/tmpl_wfEH/APIRef/temp0029.html /tmp/tmpl_wfEH/APIRef/temp0030.html /tmp/tmpl_wfEH/APIRef/temp0031.html /tmp/tmpl_wfEH/APIRef/temp0032.html /tmp/tmpl_wfEH/APIRef/temp0033.html /tmp/tmpl_wfEH/APIRef/temp0034.html /tmp/tmpl_wfEH/APIRef/temp0035.html /tmp/tmpl_wfEH/APIRef/temp0036.html /tmp/tmpl_wfEH/APIRef/temp0037.html /tmp/tmpl_wfEH/APIRef/temp0038.html /tmp/tmpl_wfEH/APIRef/temp0039.html /tmp/tmpl_wfEH/APIRef/temp0040.html /tmp/tmpl_wfEH/APIRef/temp0041.html /tmp/tmpl_wfEH/APIRef/temp0042.html /tmp/tmpl_wfEH/APIRef/temp0043.html /tmp/tmpl_wfEH/APIRef/temp0044.html /tmp/tmpl_wfEH/APIRef/temp0045.html /tmp/tmpl_wfEH/APIRef/temp0046.html /tmp/tmpl_wfEH/APIRef/temp0047.html /tmp/tmpl_wfEH/APIRef/temp0048.html /tmp/tmpl_wfEH/APIRef/temp0049.html /tmp/tmpl_wfEH/APIRef/temp0050.html /tmp/tmpl_wfEH/APIRef/temp0051.html /tmp/tmpl_wfEH/APIRef/temp0052.html /tmp/tmpl_wfEH/APIRef/temp0053.html /tmp/tmpl_wfEH/APIRef/temp0054.html /tmp/tmpl_wfEH/APIRef/temp0055.html /tmp/tmpl_wfEH/APIRef/temp0056.html /tmp/tmpl_wfEH/APIRef/temp0057.html /tmp/tmpl_wfEH/APIRef/temp0058.html /tmp/tmpl_wfEH/APIRef/temp0059.html /tmp/tmpl_wfEH/APIRef/temp0060.html /tmp/tmpl_wfEH/APIRef/temp0061.html /tmp/tmpl_wfEH/APIRef/temp0062.html /tmp/tmpl_wfEH/APIRef/temp0063.html /tmp/tmpl_wfEH/APIRef/temp0064.html /tmp/tmpl_wfEH/APIRef/temp0065.html /tmp/tmpl_wfEH/APIRef/temp0066.html /tmp/tmpl_wfEH/APIRef/temp0067.html /tmp/tmpl_wfEH/APIRef/temp0068.html /tmp/tmpl_wfEH/APIRef/temp0069.html /tmp/tmpl_wfEH/APIRef/temp0070.html /tmp/tmpl_wfEH/APIRef/temp0071.html /tmp/tmpl_wfEH/APIRef/temp0072.html /tmp/tmpl_wfEH/APIRef/temp0073.html /tmp/tmpl_wfEH/APIRef/temp0074.html /tmp/tmpl_wfEH/APIRef/temp0075.html /tmp/tmpl_wfEH/APIRef/temp0076.html /tmp/tmpl_wfEH/APIRef/temp0077.html /tmp/tmpl_wfEH/APIRef/temp0078.html /tmp/tmpl_wfEH/APIRef/temp0079.html /tmp/tmpl_wfEH/APIRef/temp0080.html /tmp/tmpl_wfEH/APIRef/temp0081.html /tmp/tmpl_wfEH/APIRef/temp0082.html /tmp/tmpl_wfEH/APIRef/temp0083.html /tmp/tmpl_wfEH/APIRef/temp0084.html /tmp/tmpl_wfEH/APIRef/temp0085.html /tmp/tmpl_wfEH/APIRef/temp0086.html /tmp/tmpl_wfEH/APIRef/temp0087.html /tmp/tmpl_wfEH/APIRef/temp0088.html /tmp/tmpl_wfEH/APIRef/temp0089.html /tmp/tmpl_wfEH/APIRef/temp0090.html /tmp/tmpl_wfEH/APIRef/temp0091.html /tmp/tmpl_wfEH/APIRef/temp0092.html /tmp/tmpl_wfEH/APIRef/temp0093.html /tmp/tmpl_wfEH/APIRef/temp0094.html /tmp/tmpl_wfEH/APIRef/temp0095.html
[Desktop-packages] [Bug 1048131] Re: unity-greeter crashed with SIGSEGV in gdk_window_get_type_hint()
** Branch linked: lp:ubuntu/trusty-proposed/unity-greeter -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1048131 Title: unity-greeter crashed with SIGSEGV in gdk_window_get_type_hint() Status in “unity-greeter” package in Ubuntu: In Progress Status in “unity-greeter” source package in Precise: In Progress Status in “unity-greeter” source package in Quantal: Triaged Status in “unity-greeter” source package in Saucy: Triaged Bug description: [Impact] Unity Greeter can crash when X clients create X windows. This results in Ubuntu going to failsafe mode. When an X window appears Unity Greeter receives a Map event. Unity Greeter attempts to get a GdkWindow object for the window in the event. If the window was destroyed before it does this it gets a NULL pointer. Unity Greeter did not check for this case. [Test Case] This is a bug that only occurs if windows rapidly appear and disappear. Can be verified on machines that are exhibiting the problem (perhaps linked to indicators failing to start). Check errors.ubuntu.com shows problem does not occur when fix applied. [Regression Potential] Low, the change just checks for the NULL pointer and ignores the map event. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1048131/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1266366] Re: Lightdm session chooser does not read the Back button to Orca
** Branch linked: lp:ubuntu/trusty-proposed/unity-greeter -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1266366 Title: Lightdm session chooser does not read the Back button to Orca Status in “unity-greeter” package in Ubuntu: Triaged Bug description: When slecting from available desktops installed, the Back button is just labelled button as far as Orca is concerned, the expected label is 'back'. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.9.5-0ubuntu1 ProcVersionSignature: Ubuntu 3.12.0-2.7-generic 3.12.0 Uname: Linux 3.12.0-2-generic x86_64 NonfreeKernelModules: btrfs raid6_pq xor ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c reiserfs ext2 btusb joydev hid_generic snd_usb_audio usbhid snd_usbmidi_lib hid snd_hda_codec_realtek snd_hda_codec_hdmi bnep rfcomm bluetooth x86_pkg_temp_thermal coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd ppdev snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_page_alloc snd_seq_midi snd_seq_midi_event snd_rawmidi psmouse microcode serio_raw snd_seq i915 snd_seq_device snd_timer drm_kms_helper snd drm lpc_ich mei_me soundcore i2c_algo_bit parport_pc mei mac_hid video pcspkr lp parport speakup_soft speakup r8169 ahci libahci mii ApportVersion: 2.12.7-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jan 6 18:26:07 2014 InstallationDate: Installed on 2013-11-14 (52 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131113) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1266366/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1262066] Re: 'Personal File Sharing Preferences' dialog is too large and out of screen bounds
Cannot reproduce in Ubuntu-GNOME 14.04 (latest updates) Possibly it depends on screen resolution - which screen resolution do you have? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-share in Ubuntu. https://bugs.launchpad.net/bugs/1262066 Title: 'Personal File Sharing Preferences' dialog is too large and out of screen bounds Status in Ubuntu GNOME: New Status in “gnome-user-share” package in Ubuntu: New Bug description: Ubuntu Gnome - 14.04 dev release - 20131217. 'Personal File Sharing Preferences' dialog is too large and out of screen bounds. See screenshot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-user-share 3.0.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.12.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Dec 18 05:50:32 2013 InstallationDate: Installed on 2013-12-18 (0 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20131217) SourcePackage: gnome-user-share UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1262066/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1276545] [NEW] nautilus crashed with SIGSEGV
Public bug reported: Nautilus crashed while I was not using it. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: nautilus 1:3.10.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0 Uname: Linux 3.13.0-6-generic i686 ApportVersion: 2.13.2-0ubuntu2 Architecture: i386 CurrentDesktop: LXDE Date: Wed Feb 5 06:31:24 2014 Disassembly: = 0xb69ae1f5: Cannot access memory at address 0xb69ae1f5 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' b['name', 'size', 'type', 'date_modified', 'owner', 'group', 'permissions', 'mime_type', 'where'] ProcCmdline: nautilus SegvAnalysis: Segfault happened at: 0xb69ae1f5: Cannot access memory at address 0xb69ae1f5 PC (0xb69ae1f5) ok Stack memory exhausted (SP below stack segment) SP (0xb4439d60) ok Reason could not be automatically determined. Signal: 11 SourcePackage: nautilus Stacktrace: #0 0xb69ae1f5 in ?? () No symbol table info available. #1 0xb6a4fb80 in ?? () No symbol table info available. Backtrace stopped: previous frame inner to this frame (corrupt stack?) StacktraceTop: ?? () ?? () Title: nautilus crashed with SIGSEGV UpgradeStatus: Upgraded to trusty on 2013-12-29 (38 days ago) UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: apport-crash i386 need-i386-retrace trusty ** Information type changed from Private to Public -- 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/1276545 Title: nautilus crashed with SIGSEGV Status in “nautilus” package in Ubuntu: New Bug description: Nautilus crashed while I was not using it. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: nautilus 1:3.10.1-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0 Uname: Linux 3.13.0-6-generic i686 ApportVersion: 2.13.2-0ubuntu2 Architecture: i386 CurrentDesktop: LXDE Date: Wed Feb 5 06:31:24 2014 Disassembly: = 0xb69ae1f5: Cannot access memory at address 0xb69ae1f5 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' b['name', 'size', 'type', 'date_modified', 'owner', 'group', 'permissions', 'mime_type', 'where'] ProcCmdline: nautilus SegvAnalysis: Segfault happened at: 0xb69ae1f5:Cannot access memory at address 0xb69ae1f5 PC (0xb69ae1f5) ok Stack memory exhausted (SP below stack segment) SP (0xb4439d60) ok Reason could not be automatically determined. Signal: 11 SourcePackage: nautilus Stacktrace: #0 0xb69ae1f5 in ?? () No symbol table info available. #1 0xb6a4fb80 in ?? () No symbol table info available. Backtrace stopped: previous frame inner to this frame (corrupt stack?) StacktraceTop: ?? () ?? () Title: nautilus crashed with SIGSEGV UpgradeStatus: Upgraded to trusty on 2013-12-29 (38 days ago) UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1276545/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 329898] Re: The HP 1018 printer not work out of the box if used non-US locale
BakLan, probably your problem has a different cause. Please report a new bug. Tell us which locale you are using. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/329898 Title: The HP 1018 printer not work out of the box if used non-US locale Status in HP Linux Imaging and Printing: New Status in Release Notes for Ubuntu: Won't Fix Status in “hplip” package in Ubuntu: Fix Released Status in “ibus” package in Ubuntu: Fix Released Status in “hplip” source package in Lucid: Won't Fix Status in “ibus” source package in Lucid: Invalid Status in “hplip” source package in Maverick: Won't Fix Status in “ibus” source package in Maverick: Won't Fix Bug description: This bug is continuation of the bug 217215. To avoid any problems related to attempts describe I decided to start with 'clean account'. (and created the new bug entry) Clean account means: 1) Remove hplip*, foo2zjs, footomatic package. 2) Remove any further files related to hp1018 find /usr/share -name *1018* ./foo2zjs/firmware/sihp1018.img ./ppd/hpijs/HP/hp_laserjet_1018-hpijs.ppd 3) Remove orphaned /usr/share/hplip directory After restarting the printer a system message appear pointing that new hardware had been installed and suggesting that hpijs package support the HP 1018 printer. I: - installed hpijs with depends - Ran Printer configure tool: a driver for HP 1018 hadn't been found - so I chose suggested HP 1015 driver - printer didn't react for send packages. To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/329898/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1276095] Re: Update to 2.39.4
** Branch linked: lp:ubuntu/trusty-proposed/glib2.0 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1276095 Title: Update to 2.39.4 Status in “glib2.0” package in Ubuntu: Triaged Bug description: Update to 2.39.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1276095/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 878836] Re: Unity Greeter - Use Unity Greeter to fulfil lock screen as well as login functions
When you're at the lock screen, sound keeps playing as it should. And the microphone and camera keep working as they should. It would be a pain if a Skype call, for example, was effectively cut off just because the screen saver momentarily came on. Any accessibility options you were using during the session should also be in effect at the lock screen, because it's your session that you're unlocking, and ignoring them would be gratuitously annoying. And on Touch, apps like the camera may be available in a limited way at the lock screen, and when they are, they should store data for you and not for any other user. When you're at the login screen, on the other hand, sound output is cut off as it should be. The microphone and camera should also no longer receive input. Any accessibility configuration should be system-wide, because it's not necessarily you who is logging in. And on Touch, apps that store data can be available only if there is one user account. (In theory you could select a user and then launch an app before logging in, but selecting a user already prompts you to log in and may even log you in automatically, so there's barely any point.) This makes the greeter fundamentally different from the lock screen in many non-visual ways. So the answer to your question, Bence, is that this feature was not completely designed. For a long time it was treated as merely a visual design problem, without these other issues being tackled. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/878836 Title: Unity Greeter - Use Unity Greeter to fulfil lock screen as well as login functions Status in Ayatana Design: Fix Committed Status in The Session Menu: Fix Released Status in Light Display Manager: Triaged Status in “gnome-screensaver” package in Ubuntu: Triaged Status in “indicator-session” package in Ubuntu: Fix Released Status in “lightdm” package in Ubuntu: Triaged Status in “unity-greeter” package in Ubuntu: Triaged Status in “indicator-session” source package in Precise: Fix Released Bug description: Use Unity Greeter to fulfil lock screen as well as login functions. Desired Solution: - Replace the current lock screen with the Unity Greeter - perhaps use 'light locker', see http://www.webupd8.org/2013/08/lightdm-session-locker-light-locker.html - also see https://plus.google.com/u/0/106086509626546157534/posts/5hQVYARYCkh To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/878836/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1272860] Re: gvfsd-trash crashed with SIGABRT in g_assertion_message()
** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1272860 Title: gvfsd-trash crashed with SIGABRT in g_assertion_message() Status in “gvfs” package in Ubuntu: New Bug description: Ubuntu prompted me thus bug when it started. It took a bit more time than usual to display the login screen. Anything went normal the last time I shut it down. Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 Impossible to find pkgname ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: gvfs-daemons 1.19.4+git20140116-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 Uname: Linux 3.13.0-5-generic i686 ApportVersion: 2.13.1-0ubuntu2 Architecture: i386 CurrentDesktop: Unity Date: Sun Jan 26 09:43:53 2014 EcryptfsInUse: Yes ExecutablePath: /usr/lib/gvfs/gvfsd-trash InstallationDate: Installed on 2013-12-15 (41 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) ProcCmdline: /usr/lib/gvfs/gvfsd-trash --spawner :1.3 /org/gtk/gvfs/exec_spaw/0 ProcEnviron: XDG_RUNTIME_DIR=set SHELL=/bin/bash LANGUAGE=fr_FR PATH=(custom, no user) LANG=fr_FR.UTF-8 Signal: 6 SourcePackage: gvfs StacktraceTop: g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0 ?? () ?? () ?? () Title: gvfsd-trash crashed with SIGABRT in g_assertion_message() UpgradeStatus: Upgraded to trusty on 2013-12-15 (41 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1272860/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1262856] Re: cannot report package issues using ubuntu-bug in precise daily image
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1262856 ** Tags added: iso-testing -- 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/1262856 Title: cannot report package issues using ubuntu-bug in precise daily image Status in “apport” package in Ubuntu: Confirmed Status in “xorg” package in Ubuntu: Invalid Status in “apport” source package in Precise: Confirmed Status in “xorg” source package in Precise: Invalid Bug description: I noticed a display server bug whilst running a precise desktop image. I've attempted to execute ubuntu-bug xorg but I have been informed firstly if i require, desire, or already have technical support and later I've answered questions if I know how to do git bisect and want to attach logs. After all these steps, I was informed that this problem cannot be reported. (screenshot to be attached) Is there something I'm doing wrong, or should we not suggest people to file X bugs with ubuntu-bug xorg as documented on the iso tracker? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1262856/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1276343] Re: [needs-packaging] PAC Manager needs-packaging
** Package changed: software-center (Ubuntu) = ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-center in Ubuntu. https://bugs.launchpad.net/bugs/1276343 Title: [needs-packaging] PAC Manager needs-packaging Status in Ubuntu: New Bug description: Description: PAC is a Perl/GTK replacement for SecureCRT/Putty/etc (linux ssh/telnet/... gui)... It provides a GUI to configure connections: users, passwords, EXPECT regular expressions, macros, etc. Features Unique linux app to implement SecureCRT's functionality (more or less!) Remote and local macros Remotely send commands with EXPECT regexp Cluster connections!! Connections on same cluster share keystrokes!! Scripting support! (vía Perl code) Serial/tty connection via cu/tip/remote-tty connections!! Pre/post connections local executions TABS OR WINDOWS for connections!! Proxy support KeePass integration! Wake On LAN capabilities Possibility to split terminals in the same TAB! Quick acces to configured connections via tray menu icon Best linux GUI for ssh, telnet, sftp, rdesktop, vnc, cu, remote-tty, ftp, etc DEB, RPM .TAR.GZ packages available!! More to come (ASA I find time!) FREE (GNU GPLv3) http://sourceforge.net/projects/pacmanager/ This package is not currently in the Ubuntu Repositories, but I look forward to its arrival. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1276343/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1266366] Re: Lightdm session chooser does not read the Back button to Orca
This bug was fixed in the package unity-greeter - 14.04.2-0ubuntu1 --- unity-greeter (14.04.2-0ubuntu1) trusty; urgency=medium * New upstream release: - Handle a window being destroyed after we get the map event and try and focus it (LP: #1048131) - Add accessible description to back button (LP: #1266366) - Fix attempted removal of dead source - Apply the same unity color corrections to the average color in shutdown dialog -- Robert Ancell robert.anc...@canonical.com Wed, 05 Feb 2014 10:01:12 + ** Changed in: unity-greeter (Ubuntu) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1266366 Title: Lightdm session chooser does not read the Back button to Orca Status in “unity-greeter” package in Ubuntu: Fix Released Bug description: When slecting from available desktops installed, the Back button is just labelled button as far as Orca is concerned, the expected label is 'back'. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.9.5-0ubuntu1 ProcVersionSignature: Ubuntu 3.12.0-2.7-generic 3.12.0 Uname: Linux 3.12.0-2-generic x86_64 NonfreeKernelModules: btrfs raid6_pq xor ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c reiserfs ext2 btusb joydev hid_generic snd_usb_audio usbhid snd_usbmidi_lib hid snd_hda_codec_realtek snd_hda_codec_hdmi bnep rfcomm bluetooth x86_pkg_temp_thermal coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd ppdev snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_page_alloc snd_seq_midi snd_seq_midi_event snd_rawmidi psmouse microcode serio_raw snd_seq i915 snd_seq_device snd_timer drm_kms_helper snd drm lpc_ich mei_me soundcore i2c_algo_bit parport_pc mei mac_hid video pcspkr lp parport speakup_soft speakup r8169 ahci libahci mii ApportVersion: 2.12.7-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jan 6 18:26:07 2014 InstallationDate: Installed on 2013-11-14 (52 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131113) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1266366/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1048131] Re: unity-greeter crashed with SIGSEGV in gdk_window_get_type_hint()
This bug was fixed in the package unity-greeter - 14.04.2-0ubuntu1 --- unity-greeter (14.04.2-0ubuntu1) trusty; urgency=medium * New upstream release: - Handle a window being destroyed after we get the map event and try and focus it (LP: #1048131) - Add accessible description to back button (LP: #1266366) - Fix attempted removal of dead source - Apply the same unity color corrections to the average color in shutdown dialog -- Robert Ancell robert.anc...@canonical.com Wed, 05 Feb 2014 10:01:12 + ** Changed in: unity-greeter (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1048131 Title: unity-greeter crashed with SIGSEGV in gdk_window_get_type_hint() Status in “unity-greeter” package in Ubuntu: Fix Released Status in “unity-greeter” source package in Precise: In Progress Status in “unity-greeter” source package in Quantal: Triaged Status in “unity-greeter” source package in Saucy: Triaged Bug description: [Impact] Unity Greeter can crash when X clients create X windows. This results in Ubuntu going to failsafe mode. When an X window appears Unity Greeter receives a Map event. Unity Greeter attempts to get a GdkWindow object for the window in the event. If the window was destroyed before it does this it gets a NULL pointer. Unity Greeter did not check for this case. [Test Case] This is a bug that only occurs if windows rapidly appear and disappear. Can be verified on machines that are exhibiting the problem (perhaps linked to indicators failing to start). Check errors.ubuntu.com shows problem does not occur when fix applied. [Regression Potential] Low, the change just checks for the NULL pointer and ignores the map event. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1048131/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1264619] Re: When deja-dup backends for 's3', 'ubuntuone' and 'cloudfiles' are removed they should not appear in possible storage locations
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: deja-dup (Ubuntu) Status: New = Confirmed -- 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/1264619 Title: When deja-dup backends for 's3', 'ubuntuone' and 'cloudfiles' are removed they should not appear in possible storage locations Status in Ubuntu GNOME: Confirmed Status in “deja-dup” package in Ubuntu: Confirmed Bug description: When deja-dup backends for 's3', 'ubuntuone' and 'cloudfiles' are removed they should not appear in possible storage locations. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: deja-dup 29.1-0ubuntu4 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.12.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Dec 28 03:23:12 2013 InstallationDate: Installed on 2013-12-28 (0 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20131227) SourcePackage: deja-dup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1264619/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1264619] Re: When deja-dup backends for 's3', 'ubuntuone' and 'cloudfiles' are removed they should not appear in possible storage locations
I can reproduce this issue in Ubuntu-GNOME 14.04 (latest updates) i.e. still can see s3 and cloudfiles in the list of locations to store files after packages have been deleted(and system restarted) ** Changed in: ubuntu-gnome Status: New = Confirmed -- 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/1264619 Title: When deja-dup backends for 's3', 'ubuntuone' and 'cloudfiles' are removed they should not appear in possible storage locations Status in Ubuntu GNOME: Confirmed Status in “deja-dup” package in Ubuntu: Confirmed Bug description: When deja-dup backends for 's3', 'ubuntuone' and 'cloudfiles' are removed they should not appear in possible storage locations. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: deja-dup 29.1-0ubuntu4 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.12.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Dec 28 03:23:12 2013 InstallationDate: Installed on 2013-12-28 (0 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20131227) SourcePackage: deja-dup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1264619/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1276072] Re: Language selection always falls back to English
What makes you think that lightdm has anything to do with it? Actually, lightdm is not involved at all when you set the language from Language Support. L-S calls accountsservice, which both saves the language as an accountsservice property and updates ~/.pam_environment. This should work the same way in Ubuntu, Xubuntu and Lubuntu. If you have studied the ~/.dmrc file, I can tell you that lightdm does not use those settings since accountsservice is installed. This bug report can be changed to whichever package is affected, so don't file a new report. But before you change that, let's try to figure out what the real problem is. It would be valuable if you could provide a detailed step- by-step description with the steps you take and your observations. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1276072 Title: Language selection always falls back to English Status in “language-selector” package in Ubuntu: Incomplete Bug description: I upgraded two amd64 computers from 13.04 to 13.10, and discovered on both that the language is set to English (whereas I selected French language at the beginning of the upgrade). Moreover, each time I set it back to French, dragging both French (France and Canada) and some English (UK US) on top of the default English in the language selection list, default English comes back on top at next login. I even tried to modify my .pam_environment (in console mode) and the /etc/environment to set fr_FR as the default, no way: gnome-language- selector seems to force default English as default at each connection! Hopefully, I do understand English, but this is turning me mad. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: language-selector-gnome 0.116 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Tue Feb 4 10:48:33 2014 InstallationDate: Installed on 2013-07-29 (190 days ago) InstallationMedia: Xubuntu 13.04 Raring Ringtail - Release amd64 (20130423.1) MarkForUpload: True PackageArchitecture: all SourcePackage: language-selector UpgradeStatus: Upgraded to saucy on 2014-02-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1276072/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1275240] Re: Impress background is dark when I am using a dark theme
Solved in version 4.2.0.4 ** Changed in: libreoffice (Ubuntu) Status: New = Fix Released -- 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/1275240 Title: Impress background is dark when I am using a dark theme Status in “libreoffice” package in Ubuntu: Fix Released Bug description: Slides or document background is the same that my dark theme, I changed the document and aplication background color from auto to white in Impress's preferences and it didnt change. Ubuntu 13.10 64 Bits Libreoffice 4.2.0~rc4-0ubuntu1~saucy1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1275240/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1265065] Re: Desktop freeze while drag-maximizing window
Yes, your photo looks like the problem I see. It did however not appear for quite a time now (not in several weeks). Is there anything you can do to reproduce it? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1265065 Title: Desktop freeze while drag-maximizing window Status in “xorg” package in Ubuntu: Incomplete Bug description: It has happened today twice at 22:23 and 22:54. I laft click with mouse on firefox titlebar and try to drag it up against taskbar to make FF windo to maximize. I see this shadow/animation of window about to extend its borders and desktop freezes. I do not remember if mouse still moves. I go to another console Ctrl+Alt+1, log in, and execute pkill -U username that brings me back to logon screen. Ubuntu 13.10 64-bit ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Dec 30 22:32:14 2013 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Once a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: I don't know GraphicsCard: NVIDIA Corporation GF104 [GeForce GTX 460] [10de:0e22] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:350c] InstallationDate: Installed on 2013-11-30 (30 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Gigabyte Technology Co., Ltd. Z68X-UD3-B3 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=9ee8cef8-09ae-4ab5-8422-7392354e9e26 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F1 dmi.board.name: Z68X-UD3-B3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd04/15/2011:svnGigabyteTechnologyCo.,Ltd.:pnZ68X-UD3-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnZ68X-UD3-B3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: Z68X-UD3-B3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Mon Dec 30 11:53:22 2013 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB-PS/2 Optical Mouse MOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 inputWC060 Series HD Webcam KEYBOARD, id 10 xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.14.5-1ubuntu2~saucy1 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1265065/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1205643] Re: VIA P4M800 graphics broken in Lubuntu/Xubuntu Saucy 12.04.4 candidate
I reported this on the QA Tracker for 12.04.4 just in case the Release Team thinks it warrants a mention in the release notes. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-openchrome in Ubuntu. https://bugs.launchpad.net/bugs/1205643 Title: VIA P4M800 graphics broken in Lubuntu/Xubuntu Saucy 12.04.4 candidate Status in “xserver-xorg-video-openchrome” package in Ubuntu: Fix Released Status in “xserver-xorg-video-openchrome” source package in Saucy: Won't Fix Status in “xserver-xorg-video-openchrome” source package in Trusty: Fix Released Bug description: Please bear with me and read all of this. Since I can't get a working display in Saucy with that graphics chip I need to use this method to file the initial bug report, but I can provide info using a chroot or replacing the quiet splash boot parameter with text which takes me to a tty interface. I hope using the tty interface provided by using the text boot parameter I can use apport-collect to collect the info needed from an installed Lubuntu 13.10 but I won't do so until asked by a dev in case some switch needs to be set to collect the appropriate info. I also want to say that I'm fully aware that graphics chip is not supported by Ubuntu/compiz itself, or even GNOME's mutter window manager, but I think it should still work with the openbox, metacity, and Xfwm window managers .. at least I hope so :^) So onto what actually happens. When I try to boot either Lubuntu or Xubuntu Saucy Alpha 2, either the live image or an installed version, I just get a frozen progress bar. So it's just 5 frozen dots on the screen. If I try booting through the recovery mode or otherwise trying to startx or 'sudo service lightdm start' I just get a blank screen. I can see the backlight is working but that's all. This is the specific hardware: VIA C7 CPU @ 1500MHz VIA CN700/P4M800 Pro/P4M800 CE/VN800 Graphics [S3 UniChrome Pro] (rev 01) VIA VT8233/A/8235/8237 AC97 Audio Controller (rev 60) Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 78) 1GB DDR2 RAM I did take a pic of the live image boot process while dealing with an unrelated d-i bug during Lubuntu Alpha 2 testing process: https://launchpadlibrarian.net/145894508/P4M800_xfreeze.JPG Now I'm wondering what else to say ... the same Saucy images and installs work with two other totally different sets of hardware. I'm ready to roll up my sleeves to help gather any needed info. Thanks in advance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-openchrome/+bug/1205643/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1276443] Re: Please merge poppler 0.24.5-2 from Debian experimental
This bug was fixed in the package poppler - 0.24.5-2ubuntu1 --- poppler (0.24.5-2ubuntu1) trusty; urgency=medium * Merge with Debian experimental (LP: #1276443), remaining changes: - Drop libopenjpeg-dev build depends, it is in universe. - Lower poppler-data to Suggests, it is too big for CD images, handled by language-selector. - Have libpoppler-dev Depend on libpoppler-private-dev, to help with the transition after the split of the two packages. - Add libpoppler-glib-doc Breaks/Replaces on libpoppler-glib-dev (= 0.24.4). - Add simple compile/link/run autopkgtest. - Backport duplex printing fixes (pdftops-origpagesizes-fixes.diff, pdftops-origpagesizes-papersize-setpagedevice-fix.diff). - Build with dh-autoreconf. - Build with -O0 until LP #1273779 is addressed. poppler (0.24.5-2) experimental; urgency=medium * Backport upstream commits a766c55f68db38feed91cf003a0d5710e2f925a8 and e238c1f83fd5f667336bfbb0e9a59569ff638ecc to fix the detection of Qt 5's moc; patch upstream_fix_qt5_moc_detection.diff. * Rename patch qt4-visibility.diff to qt-visibility.diff, and extend to qt5. * Provide poppler-qt5: (Closes: #716685) - add the qtbase5-dev build dependency - add the libpoppler-qt5-1 and libpoppler-qt5-dev binaries - pass --enable-poppler-qt5 to configure - add symbols file for libpoppler-qt5-1 poppler (0.24.5-1) experimental; urgency=low * New upstream release: - poppler can handle documents bigger than 2GB. (Closes: #642530) - fixes a typo in an error message. (Closes: #708972) * Rename packages according to the new SONAMEs: - libpoppler37 - libpoppler44 * debian/patches: - qt4-visibility.diff: refresh - upstream_pdfseparate-improve-the-path-building.patch: drop, backported - upstream_Allow-only-one-d-in-the-filename.diff: drop, backported * Update copyright. * Update symbols files. * Remove the manual link to pthreads, introduced in 0.18.4-10, as it is no more needed now (poppler does it on its own now). poppler (0.22.5-4) unstable; urgency=medium * Upload to unstable. poppler (0.22.5-3) experimental; urgency=low * Merge changes from 0.18.4-9 and 0.18.4-10: - upstream_Allow-only-one-d-in-the-filename.diff: pick it unmodified from upstream poppler (0.22.5-2) experimental; urgency=low * Merge changes from 0.18.4-7 and 0.18.4-8: - CVE-2012-2142.diff: drop, fixed upstream - upstream_pdfseparate.1-Syntax-fixes.patch: drop, backported poppler (0.22.5-1) experimental; urgency=low * New upstream release: - fixes case sensitive search in poppler-glib. (Closes: #299657) - poppler passes correct UTF-8 strings to cairo. (Closes: #697766) * Rename packages according to the new SONAMEs: - libpoppler28 - libpoppler37 * debian/patches: - qt4-visibility.diff: refresh - upstream_fix-GooString-insert.diff: drop, applied upstream - upstream_Fix-another-invalid-memory-access-in-1091.pdf.asan.7.patch: drop, backported - upstream_Fix-invalid-memory-access-in-2030.pdf.asan.69.463.patch: drop, backported - upstream_Fix-invalid-memory-access-in-1150.pdf.asan.8.69.patch: drop, backported - upstream_Initialize-refLine-totally.patch: drop, backported - upstream_cairo-support-parameterized-Gouraud-shading.patch: drop, applied upstream * Update copyright. * Update symbols files. * Update configure arguments: - Add: --enable-libpng, --enable-libtiff, --enable-cms=lcms2 (no actual changes, just enforce their usage) * Update recommends and suggests: - libpoppler-private-dev: drop the libpng-dev, libtiff-dev suggests. - poppler-utils: drop the ghostscript recommend. * Split the API documentation from libpoppler-glib-dev to an own libpoppler-glib-doc. poppler (0.20.5-3) experimental; urgency=low * Merge changes from 0.18.4-6: - upstream_Fix-another-invalid-memory-access-in-1091.pdf.asan.7.patch: update from upstream repository - upstream_Fix-invalid-memory-access-in-2030.pdf.asan.69.463.patch: update from upstream repository - upstream_Fix-invalid-memory-access-in-1150.pdf.asan.8.69.patch: update from upstream repository - upstream_Initialize-refLine-totally.patch: update from upstream repository poppler (0.20.5-2) experimental; urgency=low * Merge changes from 0.18.4-4 and 0.18.4-5: - psoutputdev-initialize-vars.diff: drop, obsolete * Backport upstream commit ae8fc0cbfc6123189e17b3cf1286e0540f181646 to support parameterized Gouraud shading in CairoOutputDev; patch upstream_cairo-support-parameterized-Gouraud-shading.patch. (Closes: #699467) -- Dmitry Shachnev mity...@ubuntu.com Wed, 05 Feb 2014 12:16:35 +0400 ** Changed in: poppler (Ubuntu) Status: Fix Committed = Fix Released ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2012-2142 -- You received this bug notification
[Desktop-packages] [Bug 1276572] [NEW] gnome control center crashes after switching between lock/display and security/privacy thru breadcrumb
Public bug reported: 1) Using ubuntu 13.10 64-bit 2) gnome-control-center: Installed: 1:3.6.3-0ubuntu45.2 Candidate: 1:3.6.3-0ubuntu45.2 Version table: *** 1:3.6.3-0ubuntu45.2 0 500 http://nl.archive.ubuntu.com/ubuntu/ saucy-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.6.3-0ubuntu44 0 500 http://nl.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages 3) expected behaviour: The control center doesn't crash 4) observed behaviour: The control center crashes/just closes. Steps to reproduce: 1. Open control center (doesn't matter how) 2. Go to Display Lock 3. Turn the option to lock your screen to off 4. Go back to all settings by clicking on the breadcrumb 'All Settings' 5. Open Security Privacy Terminal give these errors: ** (gnome-control-center:6324): CRITICAL **: gee_abstract_map_set: assertion 'self != NULL' failed ** (gnome-control-center:6324): CRITICAL **: gee_abstract_map_set: assertion 'self != NULL' failed ** (gnome-control-center:6324): CRITICAL **: gee_abstract_map_set: assertion 'self != NULL' failed ** (gnome-control-center:6324): CRITICAL **: gee_abstract_map_set: assertion 'self != NULL' failed ** (gnome-control-center:6324): CRITICAL **: gee_abstract_map_set: assertion 'self != NULL' failed ** (gnome-control-center:6324): CRITICAL **: gee_abstract_map_set: assertion 'self != NULL' failed ** (gnome-control-center:6324): CRITICAL **: gee_abstract_map_set: assertion 'self != NULL' failed ** (gnome-control-center:6324): CRITICAL **: gee_abstract_map_set: assertion 'self != NULL' failed 6. In the security tab change tik the box marked 'returning from blank screen' 7. Go back to all settings by clicking on the breadcrumb 'All Settings' Terminal give error: (gnome-control-center:2894): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed (gnome-control-center:2894): GLib-GObject-WARNING **: invalid unclassed pointer in cast to 'WhoopsieDaisyPreferences' (gnome-control-center:2894): Gtk-CRITICAL **: gtk_builder_get_object: assertion 'GTK_IS_BUILDER (builder)' failed (gnome-control-center:2894): Gtk-CRITICAL **: gtk_builder_get_object: assertion 'GTK_IS_BUILDER (builder)' failed (gnome-control-center:2894): Gtk-CRITICAL **: gtk_toggle_button_set_active: assertion 'GTK_IS_TOGGLE_BUTTON (toggle_button)' failed (gnome-control-center:2894): Gtk-CRITICAL **: gtk_toggle_button_set_active: assertion 'GTK_IS_TOGGLE_BUTTON (toggle_button)' failed 8. Go to Display Lock 9. Turn the option to lock your screen back off 10. click on breadcrumb 'all settings' 11. Control Center disapears /crashes (if not directly repeat steps 5 - 10) Terminal gives errors: ** (gnome-control-center:2894): CRITICAL **: gee_abstract_map_set: assertion 'self != NULL' failed ** (gnome-control-center:2894): CRITICAL **: gee_abstract_map_set: assertion 'self != NULL' failed ** (gnome-control-center:2894): CRITICAL **: gee_abstract_map_set: assertion 'self != NULL' failed ** (gnome-control-center:2894): CRITICAL **: gee_abstract_map_set: assertion 'self != NULL' failed ** (gnome-control-center:2894): CRITICAL **: gee_abstract_map_set: assertion 'self != NULL' failed ** (gnome-control-center:2894): CRITICAL **: gee_abstract_map_set: assertion 'self != NULL' failed ** (gnome-control-center:2894): CRITICAL **: gee_abstract_map_set: assertion 'self != NULL' failed ** (gnome-control-center:2894): CRITICAL **: gee_abstract_map_set: assertion 'self != NULL' failed (gnome-control-center:2894): Gtk-CRITICAL **: gtk_tree_model_get_iter_first: assertion 'GTK_IS_TREE_MODEL (tree_model)' failed (gnome-control-center:2894): Gtk-CRITICAL **: gtk_tree_model_get: assertion 'GTK_IS_TREE_MODEL (tree_model)' failed (gnome-control-center:2894): Gtk-CRITICAL **: gtk_tree_model_iter_next: assertion 'GTK_IS_TREE_MODEL (tree_model)' failed (gnome-control-center:2894): GLib-GObject-WARNING **: invalid cast from 'GtkButtonBox' to 'WhoopsieDaisyPreferences' Segmentation fault (core dumped) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu45.2 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Wed Feb 5 13:17:40 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-01-30 (5 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu4 deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20131023.2-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3+13.10.20131004-0ubuntu1 ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy --
[Desktop-packages] [Bug 1276572] Re: gnome control center crashes after switching between lock/display and security/privacy thru breadcrumb
*** This bug is a duplicate of bug 1275736 *** https://bugs.launchpad.net/bugs/1275736 Thanks for your bug report, that issue is fixed in bug #1275736 ** Package changed: gnome-control-center (Ubuntu) = activity-log- manager (Ubuntu) ** Changed in: activity-log-manager (Ubuntu) Importance: Undecided = Low ** Changed in: activity-log-manager (Ubuntu) Status: New = Fix Released ** This bug has been marked a duplicate of bug 1275736 /usr/bin/gnome-control-center.real:11:gtk_builder_get_object:on_properties_changed:ffi_call_unix64:ffi_call:g_cclosure_marshal_generic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to activity-log-manager in Ubuntu. https://bugs.launchpad.net/bugs/1276572 Title: gnome control center crashes after switching between lock/display and security/privacy thru breadcrumb Status in “activity-log-manager” package in Ubuntu: Fix Released Bug description: 1) Using ubuntu 13.10 64-bit 2) gnome-control-center: Installed: 1:3.6.3-0ubuntu45.2 Candidate: 1:3.6.3-0ubuntu45.2 Version table: *** 1:3.6.3-0ubuntu45.2 0 500 http://nl.archive.ubuntu.com/ubuntu/ saucy-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.6.3-0ubuntu44 0 500 http://nl.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages 3) expected behaviour: The control center doesn't crash 4) observed behaviour: The control center crashes/just closes. Steps to reproduce: 1. Open control center (doesn't matter how) 2. Go to Display Lock 3. Turn the option to lock your screen to off 4. Go back to all settings by clicking on the breadcrumb 'All Settings' 5. Open Security Privacy Terminal give these errors: ** (gnome-control-center:6324): CRITICAL **: gee_abstract_map_set: assertion 'self != NULL' failed ** (gnome-control-center:6324): CRITICAL **: gee_abstract_map_set: assertion 'self != NULL' failed ** (gnome-control-center:6324): CRITICAL **: gee_abstract_map_set: assertion 'self != NULL' failed ** (gnome-control-center:6324): CRITICAL **: gee_abstract_map_set: assertion 'self != NULL' failed ** (gnome-control-center:6324): CRITICAL **: gee_abstract_map_set: assertion 'self != NULL' failed ** (gnome-control-center:6324): CRITICAL **: gee_abstract_map_set: assertion 'self != NULL' failed ** (gnome-control-center:6324): CRITICAL **: gee_abstract_map_set: assertion 'self != NULL' failed ** (gnome-control-center:6324): CRITICAL **: gee_abstract_map_set: assertion 'self != NULL' failed 6. In the security tab change tik the box marked 'returning from blank screen' 7. Go back to all settings by clicking on the breadcrumb 'All Settings' Terminal give error: (gnome-control-center:2894): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed (gnome-control-center:2894): GLib-GObject-WARNING **: invalid unclassed pointer in cast to 'WhoopsieDaisyPreferences' (gnome-control-center:2894): Gtk-CRITICAL **: gtk_builder_get_object: assertion 'GTK_IS_BUILDER (builder)' failed (gnome-control-center:2894): Gtk-CRITICAL **: gtk_builder_get_object: assertion 'GTK_IS_BUILDER (builder)' failed (gnome-control-center:2894): Gtk-CRITICAL **: gtk_toggle_button_set_active: assertion 'GTK_IS_TOGGLE_BUTTON (toggle_button)' failed (gnome-control-center:2894): Gtk-CRITICAL **: gtk_toggle_button_set_active: assertion 'GTK_IS_TOGGLE_BUTTON (toggle_button)' failed 8. Go to Display Lock 9. Turn the option to lock your screen back off 10. click on breadcrumb 'all settings' 11. Control Center disapears /crashes (if not directly repeat steps 5 - 10) Terminal gives errors: ** (gnome-control-center:2894): CRITICAL **: gee_abstract_map_set: assertion 'self != NULL' failed ** (gnome-control-center:2894): CRITICAL **: gee_abstract_map_set: assertion 'self != NULL' failed ** (gnome-control-center:2894): CRITICAL **: gee_abstract_map_set: assertion 'self != NULL' failed ** (gnome-control-center:2894): CRITICAL **: gee_abstract_map_set: assertion 'self != NULL' failed ** (gnome-control-center:2894): CRITICAL **: gee_abstract_map_set: assertion 'self != NULL' failed ** (gnome-control-center:2894): CRITICAL **: gee_abstract_map_set: assertion 'self != NULL' failed ** (gnome-control-center:2894): CRITICAL **: gee_abstract_map_set: assertion 'self != NULL' failed ** (gnome-control-center:2894): CRITICAL **: gee_abstract_map_set: assertion 'self != NULL' failed (gnome-control-center:2894): Gtk-CRITICAL **: gtk_tree_model_get_iter_first: assertion 'GTK_IS_TREE_MODEL (tree_model)' failed (gnome-control-center:2894): Gtk-CRITICAL **: gtk_tree_model_get: assertion 'GTK_IS_TREE_MODEL (tree_model)' failed (gnome-control-center:2894): Gtk-CRITICAL **: gtk_tree_model_iter_next: assertion 'GTK_IS_TREE_MODEL (tree_model)' failed (gnome-control-center:2894): GLib-GObject-WARNING **: invalid cast from
[Desktop-packages] [Bug 1276095] Re: Update to 2.39.4
This bug was fixed in the package glib2.0 - 2.39.4-0ubuntu1 --- glib2.0 (2.39.4-0ubuntu1) trusty; urgency=medium * New upstream release (LP: #1276095) * debian/patches/04_homedir_env.patch: Drop; this change is no longer needed due to upstream honouring $HOME, and we've converted everything in the archive to use this now. * Drop DEB_ENABLE_PARALLEL from ubuntu3 ( Debian) as it causes build failures in gtkdoc-scan. Will be investigated properly upstream. -- Iain Lane iain.l...@canonical.com Wed, 05 Feb 2014 10:39:48 + ** Changed in: glib2.0 (Ubuntu) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1276095 Title: Update to 2.39.4 Status in “glib2.0” package in Ubuntu: Fix Released Bug description: Update to 2.39.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1276095/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1131664] Re: The default apps should have standard menubars under Unity
** Branch linked: lp:ubuntu/trusty-proposed/evince -- 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/1131664 Title: The default apps should have standard menubars under Unity Status in Ayatana Design: Fix Committed Status in File Roller: New Status in The Rhythmbox Music Management Application: New Status in “evince” package in Ubuntu: Triaged Status in “file-roller” package in Ubuntu: Triaged Status in “gnome-calculator” package in Ubuntu: Fix Released Status in “gnome-control-center” package in Ubuntu: Fix Released Status in “rhythmbox” package in Ubuntu: Triaged Bug description: When fixing this bug, also take a look at bug #1130722 at the same time if possible. -- In Raring, the 'Calculator' app should have the following menu items: === Edit === Copy Paste - Undo Redo - Preferences - Quit === Mode === Basic Advanced Financial Programming === Help === Contents About In Raring, the 'System Settings' app should have the following menu items: === Help === Contents [Optional link to help doc for the currently selected settings panel] - Quit To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1131664/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 35223] Re: Laptop TFT monitor - brightness level is not saved
Hi, i have the same problem since ubuntu 12.04, and right now i am using ubuntu 14.04 but the problem persist, i would like for ubuntu 14.04 this bug will be fixed My laptop is a lenovo ideapad s406, it has Procesador AMD® A8-4555M Quad core Gráficos A8 Integrate AMD® Radeon™ HD 7640 -- 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/35223 Title: Laptop TFT monitor - brightness level is not saved Status in Gnome Powermanager: Fix Released Status in “gnome-power-manager” package in Ubuntu: Triaged Status in “gnome-power-manager” source package in Lucid: Triaged Bug description: Every time I restart my computer, the monitors brightness has changed to the maximum possible. Please make it remember the settings. The computer is an IBM Thinkpad X-31 [2673-PXG] laptop. Full specification is available here : http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovolndocid=MIGR-58212 PLEASE NOTE: This bug has been filed on the WRONG package. I don't know which package or part of Ubuntu this error is part of. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-power/+bug/35223/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1276463] Re: Unity broken after latest Trusty upgrade: unable to load module ccp
Latest libprotobuf8 version fixed the problem ** Changed in: unity (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1276463 Title: Unity broken after latest Trusty upgrade: unable to load module ccp Status in “unity” package in Ubuntu: Fix Released Bug description: Unity does not work after latest upgrade in Trusty. ~$ unity compiz (core) - Info: Loading plugin: core compiz (core) - Info: Starting plugin: core compiz (core) - Info: Loading plugin: ccp compiz (core) - Error: Failed to load plugin: ccp ~$ unity -v compiz (core) - Info: Loading plugin: core compiz (core) - Debug: Trying to load core from: /home/franck/.compiz-1/plugins/libcore.so compiz (core) - Debug: dlopen failed: /home/franck/.compiz-1/plugins/libcore.so: cannot open shared object file: No such file or directory compiz (core) - Debug: Trying to load core from: /usr/lib/compiz/libcore.so compiz (core) - Debug: dlopen failed: /usr/lib/compiz/libcore.so: cannot open shared object file: No such file or directory compiz (core) - Info: Starting plugin: core compiz (core) - Debug: Started plugin: core compiz (core) - Debug: pending request: compiz (core) - Debug: - event serial: 1560 compiz (core) - Debug: - event window 0x290 compiz (core) - Debug: - x: 0 y: 0 width: 0 height: 0 border: 0, sibling: 0x0 compiz (core) - Debug: pending request: compiz (core) - Debug: - event serial: 1624 compiz (core) - Debug: - event window 0x293 compiz (core) - Debug: - x: 0 y: 0 width: 722 height: 434 border: 0, sibling: 0x290 compiz (core) - Debug: pending request: compiz (core) - Debug: - event serial: 1689 compiz (core) - Debug: - event window 0x296 compiz (core) - Debug: - x: 0 y: 0 width: 1920 height: 1080 border: 0, sibling: 0x293 compiz (core) - Debug: pending request: compiz (core) - Debug: - event serial: 1754 compiz (core) - Debug: - event window 0x299 compiz (core) - Debug: - x: 0 y: 0 width: 722 height: 434 border: 0, sibling: 0x296 compiz (core) - Debug: pending request: compiz (core) - Debug: - event serial: 1819 compiz (core) - Debug: - event window 0x29c compiz (core) - Debug: - x: 0 y: 0 width: 1920 height: 1080 border: 0, sibling: 0x299 compiz (core) - Debug: pending request: compiz (core) - Debug: - event serial: 1884 compiz (core) - Debug: - event window 0x29f compiz (core) - Debug: - x: 0 y: 0 width: 722 height: 434 border: 0, sibling: 0x29c compiz (core) - Debug: pending request: compiz (core) - Debug: - event serial: 1949 compiz (core) - Debug: - event window 0x2a2 compiz (core) - Debug: - x: 0 y: 0 width: 1920 height: 1080 border: 0, sibling: 0x29f compiz (core) - Debug: pending request: compiz (core) - Debug: - event serial: 2014 compiz (core) - Debug: - event window 0x2a5 compiz (core) - Debug: - x: 0 y: 0 width: 722 height: 434 border: 0, sibling: 0x2a2 compiz (core) - Info: Loading plugin: ccp compiz (core) - Debug: Trying to load ccp from: /home/franck/.compiz-1/plugins/libccp.so compiz (core) - Debug: dlopen failed: /home/franck/.compiz-1/plugins/libccp.so: cannot open shared object file: No such file or directory compiz (core) - Debug: Trying to load ccp from: /usr/lib/compiz/libccp.so compiz (core) - Debug: dlopen failed: /usr/lib/libcompizconfig.so.0: undefined symbol: _ZN6google8protobuf18GoogleOnceInitImplEPlPNS0_7ClosureE compiz (core) - Debug: Trying to load ccp from: libccp.so compiz (core) - Debug: dlopen failed: libccp.so: cannot open shared object file: No such file or directory compiz (core) - Error: Failed to load plugin: ccp compiz (core) - Debug: refusing to manage window 0x290 compiz (core) - Debug: received event: compiz (core) - Debug: - event serial: 1560 compiz (core) - Debug: - event window 0x290 compiz (core) - Debug: - x: 0 y: 0 width: 0 height: 0 border: 0, sibling: 0x0 compiz (core) - Debug: refusing to manage window 0x293 compiz (core) - Debug: received event: compiz (core) - Debug: - event serial: 1624 compiz (core) - Debug: - event window 0x293 compiz (core) - Debug: - x: 0 y: 0 width: 722 height: 434 border: 0, sibling: 0x290 compiz (core) - Debug: refusing to manage window 0x296 compiz (core) - Debug: received event: compiz (core) - Debug: - event serial: 1689 compiz (core) - Debug: - event window 0x296 compiz (core) - Debug: - x: 0 y: 0 width: 1920 height: 1080 border: 0, sibling: 0x293 compiz (core) - Debug: refusing to manage window 0x299 compiz (core) - Debug: received event: compiz (core) - Debug: - event serial: 1754 compiz (core) - Debug: - event window 0x299 compiz (core) - Debug: - x: 0 y: 0 width: 722 height: 434 border: 0,
[Desktop-packages] [Bug 1276143] Re: Please merge ibus 1.5.5-1ubuntu1 (main) from Debian unstable (main)
Commit log is here: https://github.com/ibus/ibus/commit/29edaf32d31e1c98047288c54a23edb5979b On Ubuntu 13.10, user doesn't know input mode like direct input or zenkaku (full width) input and so on. Property panel shows input mode and property icon. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1276143 Title: Please merge ibus 1.5.5-1ubuntu1 (main) from Debian unstable (main) Status in “ibus” package in Ubuntu: Confirmed Bug description: Please merge ibus 1.5.5-1ubuntu1. It has very important feature property panel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1276143/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 293139] Re: NetworkManager does not use dhclient-exit-hooks.d
I've encountered this problem lately as well. Impressive that it's reported since 2009 with no fixes :-/ -- 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/293139 Title: NetworkManager does not use dhclient-exit-hooks.d Status in NetworkManager: Invalid Status in “network-manager” package in Ubuntu: Triaged Status in “network-manager” package in Fedora: Won't Fix Bug description: Binary package hint: network-manager I am running intrepid i386 and amd64 on a handful of systems. On every system, both upgraded and fresh installs, i use a script (first attachment) for updating a DNS record through DNSSEC. Using /etc/network/interfaces or invoking dhclient directly correctly updates the DNS record (second attachment). Using network-manager the DNS record update script doesn't seem to run (third attachment). On a laptop it is inconvenient to constantly reconfigure devices. For desktops, a workaround is to have a dhcp entry in /etc/network/interfaces for the relevant connection. As a side note, the script is designed to work with PPP ip-up.d as well. However, I haven't yet found a way to configure network-manager to dial up to 3G over a bluetooth connected modem. It may apply here similarily though. Wvdial works with the script. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/293139/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1276072] Re: Language selection always falls back to English
Well, the point is that my ~/.pam_environment is modified (even if it is write-protected, funny) when I connect through the session manager (which is lightdm), and precisely at that moment (I did monitor this on tty1), but not when I connect on console mode (on tty1, for example). And even now that I found the way to correct the language setting (by selecting it in the language selector of the session manager), I have to do it at each connection (it is set back to English) - in fact, I found that the session's type is correctly kept on both my computers, only the language is a problem. Otherwise (if it let English), the two first lines of my ~/.pam_environment are modified (to LANGUAGE=en \\ LANG=en_US.UTF-8). I add an archive with my current versions of /etc/environment and ~/.pam_environment. And, at last, even now that I corrected the language setting, I found out that some translation are missing (update manager, synaptic, Gimp, evince, emacs, calculator, ...). I think I did not have this problem when I connected before (but I may be mistaken). The language setting does not seems correct, in fact: gnome-language-selector still shows English on top, and French at the bottom (and thus grey)... I however have some (about a half) of the main menu items in French... As a conclusion, it only partially works with my turnaround. ** Attachment added: envir.tbz https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1276072/+attachment/3969887/+files/envir.tbz -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1276072 Title: Language selection always falls back to English Status in “language-selector” package in Ubuntu: Incomplete Bug description: I upgraded two amd64 computers from 13.04 to 13.10, and discovered on both that the language is set to English (whereas I selected French language at the beginning of the upgrade). Moreover, each time I set it back to French, dragging both French (France and Canada) and some English (UK US) on top of the default English in the language selection list, default English comes back on top at next login. I even tried to modify my .pam_environment (in console mode) and the /etc/environment to set fr_FR as the default, no way: gnome-language- selector seems to force default English as default at each connection! Hopefully, I do understand English, but this is turning me mad. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: language-selector-gnome 0.116 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Tue Feb 4 10:48:33 2014 InstallationDate: Installed on 2013-07-29 (190 days ago) InstallationMedia: Xubuntu 13.04 Raring Ringtail - Release amd64 (20130423.1) MarkForUpload: True PackageArchitecture: all SourcePackage: language-selector UpgradeStatus: Upgraded to saucy on 2014-02-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1276072/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1263436] Re: unity-greeter fails to build from source on all arches
** Changed in: unity-greeter (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1263436 Title: unity-greeter fails to build from source on all arches Status in “unity-greeter” package in Ubuntu: Fix Released Bug description: First noticed with the ppc64el port, but then I retried a clean build on amd64, and it fails the same way: UBUNTU_MENUPROXY=0 top_srcdir=.. . xvfb-run -a ./unity-greeter-test (./unity-greeter-test:27427): Gtk-WARNING **: cannot open display: :99 /usr/bin/xvfb-run: line 184: 27427 Trace/breakpoint trap (core dumped) DISPLAY=:$SERVERNUM XAUTHORITY=$AUTHFILE $@ 21 make[2]: *** [check] Error 133 make[2]: Leaving directory `/«PKGBUILDDIR»/tests' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/«PKGBUILDDIR»' dh_auto_test: make -j1 check returned exit code 2 Would be lovely to have someone look into what's regressed here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1263436/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1276585] [NEW] Typos in ttf-opensymbol package description
Public bug reported: 1. apt-cache show ttf-opensymbol What you see: Description: transitional package for fonts-opensymbol This package is a transitiional package for font-opensymbol. It can be removed when fonts-opensymbol is installed. What you should see: * The description refers consistently to fonts-opensymbol, not font-opensymbol * transitiional should be transitional ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: string-fix -- 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/1276585 Title: Typos in ttf-opensymbol package description Status in “libreoffice” package in Ubuntu: New Bug description: 1. apt-cache show ttf-opensymbol What you see: Description: transitional package for fonts-opensymbol This package is a transitiional package for font-opensymbol. It can be removed when fonts-opensymbol is installed. What you should see: * The description refers consistently to fonts-opensymbol, not font-opensymbol * transitiional should be transitional To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1276585/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1274822] Re: latest update breaks nvidia-prime and produces blank screen
@Alberto today i have installed some updates from proposed. This broke my system (xorg etc.) so i had to do a fresh 14.04 installation. I hav einstalled also nvidia 331 and this ad dependency installed nvidia-prime. All seems to work just fine now so maybe the problem was with some old configuration on previous installation (update from 13.10 - 14.04) -- 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/1274822 Title: latest update breaks nvidia-prime and produces blank screen Status in “nvidia-prime” package in Ubuntu: Incomplete Bug description: I'm currently using a laptop with optimus technology and NVidia graphic card. Last year (2013) I installed NVidia-prime and it worked perfectly. However, the very recent update (2014/1/29) broke NVidia- prime. The screen turned into complete blackness after Ubuntu splash screen (the purple one), and was even not showing cursor. However, from several difference behaviors I am sure that everything else (like terminals, keyboard inputs and even games) is working properly after login. Ubuntu version: 14.04 (Trusty Tahr) nvidia-prime version: 0.5.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1274822/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 952401] Re: Shutting the lid interrupts laptop suspend
Christopher Penalver, I installed xdiagnose, but now apport-collect just hangs. -- 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/952401 Title: Shutting the lid interrupts laptop suspend Status in “xorg” package in Ubuntu: Incomplete Bug description: When I select Turn off the screen as the action to be performed when my laptop lid is closed I get the following behavior: If I direct the computer to suspend (sleep) and then close lid of the laptop before it's finished going to sleep then the suspend process never completes. I think the laptop ought to go to sleep regardless of how quickly I close the lid. I believe this issue is related to the bugs reported at https://bugs.launchpad.net/ubuntu/+source/acpi/+bug/859178 and https://bugs.launchpad.net/hundredpapercuts/+bug/387553, though I was unable to reproduce these bugs. (It is presumably also related to the fact that when I had Sleep selected as the action to be performed when my laptop lid was closed putting the laptop to sleep and then closing the lid too fast would result in two suspends. That is, the laptop would suspend, but when I woke it it, it would suspend a second time.) This is not a pressing issue for me since I have discovered that selecting Do nothing as the action to be performed when my laptop lid is closed results in the correct behavior and turning my screen off when the lid is closed but the computer is still on is not a huge priority. Nevertheless, it would be nice to fix this. WORKAROUND: Wait until suspend initiated via command line or GUI to finish before closing the lid. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: xorg 1:7.6+7ubuntu7.1 ProcVersionSignature: Ubuntu 3.0.0-16.29-generic 3.0.20 Uname: Linux 3.0.0-16-generic x86_64 ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Sun Mar 11 11:15:38 2012 InstallationMedia: Kubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) ProcEnviron: LANGUAGE= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/952401/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1276630] [NEW] cups-browsed upstart job does not load the apparmor profile for cups-browsed
*** This bug is a security vulnerability *** Public security bug reported: On up to date trust I noticed that: $ sudo aa-status apparmor module is loaded. 124 profiles are loaded. ... /usr/sbin/cups-browsed 0 profiles are in complain mode. 32 processes have profiles defined. 31 processes are in enforce mode. ... 0 processes are in complain mode. 1 processes are unconfined but have a profile defined. /usr/sbin/cups-browsed (1222) This means that while there is an apparmor profile for cups-browsed and it is loaded (good), it is being loaded into the kernel after /usr/sbin /cups-browsed is started which means that /usr/sbin/cups-browsed is running unconfined (bad). Fix is to adjust the upstart job to either use /lib/init/apparmor- profile-load in the pre-start or to use the new apparmor stanza in the upstart job. Since cups itself is still using /lib/init/apparmor- profile-load, attached is a patch to use it for cups-browsed. ** Affects: cups-filters (Ubuntu) Importance: High Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1276630 Title: cups-browsed upstart job does not load the apparmor profile for cups- browsed Status in “cups-filters” package in Ubuntu: New Bug description: On up to date trust I noticed that: $ sudo aa-status apparmor module is loaded. 124 profiles are loaded. ... /usr/sbin/cups-browsed 0 profiles are in complain mode. 32 processes have profiles defined. 31 processes are in enforce mode. ... 0 processes are in complain mode. 1 processes are unconfined but have a profile defined. /usr/sbin/cups-browsed (1222) This means that while there is an apparmor profile for cups-browsed and it is loaded (good), it is being loaded into the kernel after /usr/sbin/cups-browsed is started which means that /usr/sbin/cups- browsed is running unconfined (bad). Fix is to adjust the upstart job to either use /lib/init/apparmor- profile-load in the pre-start or to use the new apparmor stanza in the upstart job. Since cups itself is still using /lib/init/apparmor- profile-load, attached is a patch to use it for cups-browsed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1276630/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1276327] Re: deja-dup/duplicity fails gpg encrypted backup in trusty
As a workaround, set LANG=en_US.UTF-8 Proper fix on the way. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to duplicity in Ubuntu. https://bugs.launchpad.net/bugs/1276327 Title: deja-dup/duplicity fails gpg encrypted backup in trusty Status in “duplicity” package in Ubuntu: New Bug description: Failed with an unknown error. Traceback (most recent call last): File /usr/bin/duplicity, line 1489, in module with_tempdir(main) File /usr/bin/duplicity, line 1483, in with_tempdir fn() File /usr/bin/duplicity, line 1332, in main do_backup(action) File /usr/bin/duplicity, line 1414, in do_backup globals.gpg_profile.passphrase = get_passphrase(1, action) File /usr/bin/duplicity, line 168, in get_passphrase pass1 = getpass.getpass(_(GnuPG passphrase:)+ ) File /usr/lib/python2.7/getpass.py, line 83, in unix_getpass passwd = fallback_getpass(prompt, stream) File /usr/lib/python2.7/getpass.py, line 118, in fallback_getpass return _raw_input(prompt, stream) File /usr/lib/python2.7/getpass.py, line 128, in _raw_input prompt = str(prompt) UnicodeEncodeError: 'ascii' codec can't encode character u'\xfc' in position 10: ordinal not in range(128) 1) lsb_release -rd Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 2) apt-cache policy duplicity duplicity: Installed: 0.6.23-0ubuntu1 Candidate: 0.6.23-0ubuntu1 Version table: *** 0.6.23-0ubuntu1 0 500 http://de.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status 3) I expected the scheduled backups to succeed as the used to do in the past. 4) The backup aborts with the error message listed above Additonally deja-dup-preferences vanished from System Preferences, but that should perhaps be logged as a different bug. Downgrading deja-dup/duplicity to the saucy versions restores functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1276327/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1276630] Re: cups-browsed upstart job does not load the apparmor profile for cups-browsed
** Patch added: lp1276630.patch https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1276630/+attachment/3969889/+files/lp1276630.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1276630 Title: cups-browsed upstart job does not load the apparmor profile for cups- browsed Status in “cups-filters” package in Ubuntu: New Bug description: On up to date trust I noticed that: $ sudo aa-status apparmor module is loaded. 124 profiles are loaded. ... /usr/sbin/cups-browsed 0 profiles are in complain mode. 32 processes have profiles defined. 31 processes are in enforce mode. ... 0 processes are in complain mode. 1 processes are unconfined but have a profile defined. /usr/sbin/cups-browsed (1222) This means that while there is an apparmor profile for cups-browsed and it is loaded (good), it is being loaded into the kernel after /usr/sbin/cups-browsed is started which means that /usr/sbin/cups- browsed is running unconfined (bad). Fix is to adjust the upstart job to either use /lib/init/apparmor- profile-load in the pre-start or to use the new apparmor stanza in the upstart job. Since cups itself is still using /lib/init/apparmor- profile-load, attached is a patch to use it for cups-browsed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1276630/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1171342] Re: mouse scroll wheel not working in gedit System Monitor
It seemed that my problem was related to Bug #1200829. For those of you who experience the same problem I had, the fix is given in the PPA: ppa:mc3man/test-scroll -- 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/1171342 Title: mouse scroll wheel not working in gedit System Monitor Status in GTK+ GUI Toolkit: Fix Released Status in X.Org X server: Confirmed Status in “gtk+3.0” package in Ubuntu: Fix Released Status in “xorg-server” package in Ubuntu: Triaged Bug description: Open System Monitor Using mouse wheel button - scroll up or down - list does not move. If Press the wheel button and then scroll up or down the list will move. This also occurs in Gedit. Firefox and Terminal work as expected. IE do not need to press the wheel and then scroll Linux kylea-hpxt 3.8.0-19-generic #29-Ubuntu SMP Wed Apr 17 18:16:28 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Description: Ubuntu 13.04 Release: 13.04 To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1171342/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1276072] Re: Language selection always falls back to English
~/.pam_environment write protected?? That breaks everything. You should: 1. Ensure that you have read/write access to ~/.pam_environment, so the system can do its job with respect to the language settings. 2. Remove all those language/locale entries in /etc/environment - only the PATH line should be kept. Can you please do so, and let us know if that fixes it. The partial translation is probably explained by a typo in ~/.pam_environment: There is no fr-FR language code, should be fr_FR. ( Language Support/accountsservice would never have made such a typo. ;-) ) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1276072 Title: Language selection always falls back to English Status in “language-selector” package in Ubuntu: Incomplete Bug description: I upgraded two amd64 computers from 13.04 to 13.10, and discovered on both that the language is set to English (whereas I selected French language at the beginning of the upgrade). Moreover, each time I set it back to French, dragging both French (France and Canada) and some English (UK US) on top of the default English in the language selection list, default English comes back on top at next login. I even tried to modify my .pam_environment (in console mode) and the /etc/environment to set fr_FR as the default, no way: gnome-language- selector seems to force default English as default at each connection! Hopefully, I do understand English, but this is turning me mad. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: language-selector-gnome 0.116 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Tue Feb 4 10:48:33 2014 InstallationDate: Installed on 2013-07-29 (190 days ago) InstallationMedia: Xubuntu 13.04 Raring Ringtail - Release amd64 (20130423.1) MarkForUpload: True PackageArchitecture: all SourcePackage: language-selector UpgradeStatus: Upgraded to saucy on 2014-02-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1276072/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 376464] Re: Software Centre, Synaptic should point to the DDTP
Pierre, is Nightmonkey still being developed? There's nothing for me to do here until anyone demonstrates that a simple translation crowdsourcing system is viable. Linking from USC to a translation service would be pretty easy, but I wouldn't be happy to see USC linking to anything more complicated than something that takes you directly from an Ubuntu SSO sign-in to a focused field for entering the suggested translation. Nightmonkey might become that simple, but it looks far from there at the moment, and I don't see any activity in the past six months. ** Changed in: software-center (Ubuntu) Assignee: Matthew Paul Thomas (mpt) = (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-center in Ubuntu. https://bugs.launchpad.net/bugs/376464 Title: Software Centre, Synaptic should point to the DDTP Status in AppCenter: New Status in Package Descriptions for Ubuntu (to make translation easy): New Status in The synaptic package manager: New Status in Ubuntu Translations: Triaged Status in Unity Applications Lens: Triaged Status in “software-center” package in Ubuntu: Incomplete Bug description: There are a lot of untranslated software descriptions in WebCatalog, Software Center and Synaptic (6+ strings in most languages, https://translations.launchpad.net/ddtp-ubuntu/ ). Relying solely on translators doesn't scale. Would it be possible to add a mechanism to enable translation suggestion crowdsourcing ? The basic idea would be a button to Translate this software description below each untranslated description that would enable users to easily provide a translation suggestion to the DDTP using Launchpad. We could point the user to the DDTP translations in each individual software summary shown in Ubuntu App Center or Synaptic. There would be a button called Translate those descriptions http://nightmonkey.ubuntu.hu/#release=raringlanguage=frview=apprepo=REPOSITORYisok=falserownumber=100sortpopcon=dscpackagename=KEYWORDpage=null Two variables: keyword repository Mockup: - Software Centre: https://bugs.launchpad.net/ubuntu-translations/+bug/376464/+attachment/3657387/+files/Logith%C3%A8que-Ubuntu_001.png - Synaptic: https://bugs.launchpad.net/ubuntu-translations/+bug/376464/+attachment/3657359/+files/synaptic.jpg - Application Lens: https://bugs.launchpad.net/ubuntu-translations/+bug/376464/+attachment/3650567/+files/mockup.png To manage notifications about this bug go to: https://bugs.launchpad.net/appcenter/+bug/376464/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1276630] Re: cups-browsed upstart job does not load the apparmor profile for cups-browsed
** Changed in: cups-filters (Ubuntu) Assignee: (unassigned) = Didier Raboud (odyx) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1276630 Title: cups-browsed upstart job does not load the apparmor profile for cups- browsed Status in “cups-filters” package in Ubuntu: Triaged Bug description: On up to date trust I noticed that: $ sudo aa-status apparmor module is loaded. 124 profiles are loaded. ... /usr/sbin/cups-browsed 0 profiles are in complain mode. 32 processes have profiles defined. 31 processes are in enforce mode. ... 0 processes are in complain mode. 1 processes are unconfined but have a profile defined. /usr/sbin/cups-browsed (1222) This means that while there is an apparmor profile for cups-browsed and it is loaded (good), it is being loaded into the kernel after /usr/sbin/cups-browsed is started which means that /usr/sbin/cups- browsed is running unconfined (bad). Fix is to adjust the upstart job to either use /lib/init/apparmor- profile-load in the pre-start or to use the new apparmor stanza in the upstart job. Since cups itself is still using /lib/init/apparmor- profile-load, attached is a patch to use it for cups-browsed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1276630/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1276630] Re: cups-browsed upstart job does not load the apparmor profile for cups-browsed
Didier, can you apply this patch to cups-filters and upload to Debian so that it syncs into Ubuntu? Thanks. ** Changed in: cups-filters (Ubuntu) Status: New = Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1276630 Title: cups-browsed upstart job does not load the apparmor profile for cups- browsed Status in “cups-filters” package in Ubuntu: Triaged Bug description: On up to date trust I noticed that: $ sudo aa-status apparmor module is loaded. 124 profiles are loaded. ... /usr/sbin/cups-browsed 0 profiles are in complain mode. 32 processes have profiles defined. 31 processes are in enforce mode. ... 0 processes are in complain mode. 1 processes are unconfined but have a profile defined. /usr/sbin/cups-browsed (1222) This means that while there is an apparmor profile for cups-browsed and it is loaded (good), it is being loaded into the kernel after /usr/sbin/cups-browsed is started which means that /usr/sbin/cups- browsed is running unconfined (bad). Fix is to adjust the upstart job to either use /lib/init/apparmor- profile-load in the pre-start or to use the new apparmor stanza in the upstart job. Since cups itself is still using /lib/init/apparmor- profile-load, attached is a patch to use it for cups-browsed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1276630/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1274779]
*** Bug 74569 has been marked as a duplicate of this bug. *** -- 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/1274779 Title: [ivb] hang on pageflip (IPEHR: 0x0a01) Status in X.org xf86-video-intel: Confirmed Status in “xserver-xorg-video-intel” package in Ubuntu: Confirmed Bug description: False GPU lockup IPEHR: 0x0a01 ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-intel 2:2.99.907-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 Uname: Linux 3.13.0-5-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Jan 29 23:32:19 2014 DistUpgraded: 2013-12-25 22:45:46,524 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DuplicateSignature: GPU lockup IPEHR: 0x0a01 Ubuntu 14.04 ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21f4] NVIDIA Corporation GF108M [NVS 5400M] [10de:0def] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21f4] InstallationDate: Installed on 2013-05-30 (245 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) InterpreterPath: /usr/bin/python3.3 MachineType: LENOVO 2342CTO ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-5-generic root=UUID=db82f5ed-cf1b-4bea-bcd8-8ec4fb76a850 ro acpi_backlight=vendor acpi_osi=Linux quiet splash i915.i915_enable_rc6=1 pcie_aspm=force vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu7 libdrm2 2.4.52-1 xserver-xorg-video-intel 2:2.99.907-0ubuntu1 SourcePackage: xserver-xorg-video-intel Title: False GPU lockup IPEHR: 0x0a01 UpgradeStatus: Upgraded to trusty on 2013-12-26 (35 days ago) UserGroups: dmi.bios.date: 10/19/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G1ET73WW (2.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 2342CTO dmi.board.vendor: LENOVO dmi.board.version: Win8 STD DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG1ET73WW(2.09):bd10/19/2012:svnLENOVO:pn2342CTO:pvrThinkPadT430:rvnLENOVO:rn2342CTO:rvrWin8STDDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2342CTO dmi.product.version: ThinkPad T430 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.0.1-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.0.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.907-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu1 xserver.bootTime: Thu Jan 30 20:19:46 2014 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id8510 vendor AUO xserver.version: 2:1.14.5-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1274779/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1276072] Re: Language selection always falls back to English
OK, you're right, the problems came from this typo. Everything is fine, now (I did modified manually the ~/.pam_environment because the language selection at the session opening did not correct it once - I don't know why it works now). I just insist on the fact that a write-protected ~/.pam_environment does not break anything: it is modified whatsoever (I will try it again, but I am quite confident on it). And I still have to select the correct language at connection, it is not kept from one session to the next. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1276072 Title: Language selection always falls back to English Status in “language-selector” package in Ubuntu: Incomplete Bug description: I upgraded two amd64 computers from 13.04 to 13.10, and discovered on both that the language is set to English (whereas I selected French language at the beginning of the upgrade). Moreover, each time I set it back to French, dragging both French (France and Canada) and some English (UK US) on top of the default English in the language selection list, default English comes back on top at next login. I even tried to modify my .pam_environment (in console mode) and the /etc/environment to set fr_FR as the default, no way: gnome-language- selector seems to force default English as default at each connection! Hopefully, I do understand English, but this is turning me mad. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: language-selector-gnome 0.116 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Tue Feb 4 10:48:33 2014 InstallationDate: Installed on 2013-07-29 (190 days ago) InstallationMedia: Xubuntu 13.04 Raring Ringtail - Release amd64 (20130423.1) MarkForUpload: True PackageArchitecture: all SourcePackage: language-selector UpgradeStatus: Upgraded to saucy on 2014-02-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1276072/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1272338] Re: Xorg memory leak on trusty
This bug was fixed in the package xserver-xorg-video-intel - 2:2.99.909-0ubuntu2 --- xserver-xorg-video-intel (2:2.99.909-0ubuntu2) trusty; urgency=medium * Refresh xmir patch. -- Maarten Lankhorst maarten.lankho...@ubuntu.com Wed, 05 Feb 2014 14:33:04 + ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: Fix Committed = Fix Released -- 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/1272338 Title: Xorg memory leak on trusty Status in “xserver-xorg-video-intel” package in Ubuntu: Fix Released Bug description: After a few hours Xorg process was consuming a GB of RAM, after a day or so it was 2GB, now after 2 days it's over 4GB. I'd rather X wasn't eating all my RAM. PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1710 root 20 0 5270636 4.300g 277872 S 14.2 27.6 229:09.97 Xorg ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu7 ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 Uname: Linux 3.13.0-5-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,grid,imgpng,gnomecompat,scale,workarounds,mousepoll,regex,wall,move,place,vpswitch,resize,unitymtgrabhandles,snap,session,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Jan 24 13:36:48 2014 DistUpgraded: 2014-01-20 08:54:25,315 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21da] InstallationDate: Installed on 2012-06-29 (573 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MachineType: LENOVO 4287CTO ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-5-generic root=UUID=6088859e-4fc3-4ec8-903f-5b52cdc1d0eb ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-01-20 (4 days ago) dmi.bios.date: 12/05/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET67WW (1.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 4287CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET67WW(1.37):bd12/05/2012:svnLENOVO:pn4287CTO:pvrThinkPadX220:rvnLENOVO:rn4287CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4287CTO dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.51-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.0.1-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.0.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu11 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.907-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu1 xserver.bootTime: Wed Jan 22 12:54:42 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 728 vendor LGD xserver.version: 2:1.14.5-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1272338/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1263127] Re: High Contrast theme does not work with Skype on Ubuntu 12.04 amd64
** Changed in: gnome-icon-theme-symbolic (Ubuntu) Status: New = Invalid ** Changed in: skype (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-icon-theme-symbolic in Ubuntu. https://bugs.launchpad.net/bugs/1263127 Title: High Contrast theme does not work with Skype on Ubuntu 12.04 amd64 Status in “gnome-icon-theme-symbolic” package in Ubuntu: Invalid Status in “skype” package in Ubuntu: Invalid Bug description: Unable to see the skype icon through the hi-contrast theme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-icon-theme-symbolic/+bug/1263127/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1131664] Re: The default apps should have standard menubars under Unity
This bug was fixed in the package evince - 3.10.3-0ubuntu3 --- evince (3.10.3-0ubuntu3) trusty; urgency=medium * Add GMenuModel port (lp: #1131664) -- Lars Uebernickel lars.uebernic...@ubuntu.com Tue, 04 Feb 2014 15:22:45 + ** Changed in: evince (Ubuntu) Status: Triaged = Fix Released -- 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/1131664 Title: The default apps should have standard menubars under Unity Status in Ayatana Design: Fix Committed Status in File Roller: New Status in The Rhythmbox Music Management Application: New Status in “evince” package in Ubuntu: Fix Released Status in “file-roller” package in Ubuntu: Triaged Status in “gnome-calculator” package in Ubuntu: Fix Released Status in “gnome-control-center” package in Ubuntu: Fix Released Status in “rhythmbox” package in Ubuntu: Triaged Bug description: When fixing this bug, also take a look at bug #1130722 at the same time if possible. -- In Raring, the 'Calculator' app should have the following menu items: === Edit === Copy Paste - Undo Redo - Preferences - Quit === Mode === Basic Advanced Financial Programming === Help === Contents About In Raring, the 'System Settings' app should have the following menu items: === Help === Contents [Optional link to help doc for the currently selected settings panel] - Quit To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1131664/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1276653] [NEW] udisksd crashed with SIGSEGV in ffi_call_SYSV()
Public bug reported: . ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: udisks2 2.1.2-1 ProcVersionSignature: Ubuntu 3.13.0-7.25-generic 3.13.1 Uname: Linux 3.13.0-6-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.13.2-0ubuntu2 Architecture: i386 CustomUdevRuleFiles: 51-android.rules Date: Tue Feb 4 09:23:58 2014 ExecutablePath: /usr/lib/udisks2/udisksd InstallationDate: Installed on 2010-10-21 (1203 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) MachineType: LENOVO 2516CTO ProcCmdline: /usr/lib/udisks2/udisksd --no-debug ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-7-generic root=UUID=7ad192e9-7b26-49d1-8e1c-fefc7dc495cb ro quiet splash intel_pstate=enable SegvAnalysis: Segfault happened at: 0x807dca4: mov(%eax),%esi PC (0x0807dca4) ok source (%eax) (0x) not located in a known VMA region (needed readable region)! destination %esi ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: udisks2 StacktraceTop: ?? () ?? () ffi_call_SYSV () from /usr/lib/i386-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/i386-linux-gnu/libffi.so.6 g_cclosure_marshal_generic () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 Title: udisksd crashed with SIGSEGV in ffi_call_SYSV() UpgradeStatus: Upgraded to trusty on 2013-11-01 (95 days ago) UserGroups: dmi.bios.date: 08/27/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET72WW (1.32 ) dmi.board.name: 2516CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6IET72WW(1.32):bd08/27/2010:svnLENOVO:pn2516CTO:pvrThinkPadT410:rvnLENOVO:rn2516CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2516CTO dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO ** Affects: udisks2 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-crash i386 need-i386-retrace trusty ** Information type changed from Private to Public -- 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/1276653 Title: udisksd crashed with SIGSEGV in ffi_call_SYSV() Status in “udisks2” package in Ubuntu: New Bug description: . ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: udisks2 2.1.2-1 ProcVersionSignature: Ubuntu 3.13.0-7.25-generic 3.13.1 Uname: Linux 3.13.0-6-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.13.2-0ubuntu2 Architecture: i386 CustomUdevRuleFiles: 51-android.rules Date: Tue Feb 4 09:23:58 2014 ExecutablePath: /usr/lib/udisks2/udisksd InstallationDate: Installed on 2010-10-21 (1203 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) MachineType: LENOVO 2516CTO ProcCmdline: /usr/lib/udisks2/udisksd --no-debug ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-7-generic root=UUID=7ad192e9-7b26-49d1-8e1c-fefc7dc495cb ro quiet splash intel_pstate=enable SegvAnalysis: Segfault happened at: 0x807dca4: mov(%eax),%esi PC (0x0807dca4) ok source (%eax) (0x) not located in a known VMA region (needed readable region)! destination %esi ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: udisks2 StacktraceTop: ?? () ?? () ffi_call_SYSV () from /usr/lib/i386-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/i386-linux-gnu/libffi.so.6 g_cclosure_marshal_generic () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 Title: udisksd crashed with SIGSEGV in ffi_call_SYSV() UpgradeStatus: Upgraded to trusty on 2013-11-01 (95 days ago) UserGroups: dmi.bios.date: 08/27/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET72WW (1.32 ) dmi.board.name: 2516CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6IET72WW(1.32):bd08/27/2010:svnLENOVO:pn2516CTO:pvrThinkPadT410:rvnLENOVO:rn2516CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2516CTO dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1276653/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1271628] Re: Xorg crashed with SIGSEGV in memset()
This bug was fixed in the package xserver-xorg-video-intel - 2:2.99.909-0ubuntu2 --- xserver-xorg-video-intel (2:2.99.909-0ubuntu2) trusty; urgency=medium * Refresh xmir patch. -- Maarten Lankhorst maarten.lankho...@ubuntu.com Wed, 05 Feb 2014 14:33:04 + ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: Fix Committed = Fix Released -- 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/1271628 Title: Xorg crashed with SIGSEGV in memset() Status in X.org xf86-video-intel: Fix Released Status in “xserver-xorg-video-intel” package in Ubuntu: Fix Released Bug description: Xorg has been crashing for me every few days when resuming from suspend or switching virtual consoles. The backtrace looks identical to https://bugs.freedesktop.org/show_bug.cgi?id=73351, which has an upstream patch: http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/patch/?id=5f3ee21a307a4ff4db189bd53e58a70ec01ee6bc ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: xserver-xorg-core 2:1.14.5-1ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8 Uname: Linux 3.13.0-4-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Jan 22 10:53:15 2014 DistUpgraded: 2013-10-31 06:18:59,114 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExecutablePath: /usr/bin/Xorg ExecutableTimestamp: 1387144570 ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21d9] NVIDIA Corporation GT218M [NVS 3100M] [10de:0a6c] (rev ff) (prog-if ff) InstallationDate: Installed on 2010-12-05 (1144 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Alpha amd64 (20101202) MachineType: LENOVO 4313CTO ProcCmdline: /usr/bin/X :0 -background none -verbose -auth /var/run/gdm/auth-for-gdm-8buhR3/database -seat seat0 -nolisten tcp vt7 ProcCwd: /etc/X11 ProcEnviron: LANG=en_US.UTF-8 TERM=linux PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-4-generic root=/dev/mapper/fdisk-ubuntu ro quiet splash crashkernel=384M-2G:64M,2G-:128M crashkernel=384M-2G:64M,2G-:128M crashkernel=384M-2G:64M,2G-:128M crashkernel=384M-:128M vt.handoff=7 SegvAnalysis: Segfault happened at: 0x7f805edd4da4 memset+84:movdqu %xmm8,(%rdi) PC (0x7f805edd4da4) ok source %xmm8 ok destination (%rdi) (0x7f8056069000) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: xorg-server StacktraceTop: memset () at ../sysdeps/x86_64/memset.S:82 memset (__len=optimized out, __ch=optimized out, __dest=optimized out) at /usr/include/x86_64-linux-gnu/bits/string3.h:84 _sna_pixmap_move_to_cpu (pixmap=pixmap@entry=0x7f8062d26db0, flags=flags@entry=3) at ../../../src/sna/sna_accel.c:2118 sna_drawable_move_region_to_cpu (drawable=optimized out, region=region@entry=0x72c0a920, flags=flags@entry=3) at ../../../src/sna/sna_accel.c:2567 sna_composite_fb (op=optimized out, src=src@entry=0x7f806327c4a0, mask=mask@entry=0x0, dst=dst@entry=0x7f8062b8b010, region=region@entry=0x72c0a920, src_x=src_x@entry=0, src_y=src_y@entry=0, msk_x=msk_x@entry=0, msk_y=msk_y@entry=0, dst_x=16, dst_y=dst_y@entry=16, width=width@entry=16, height=height@entry=16) at ../../../src/sna/sna_composite.c:519 Title: Xorg crashed with SIGSEGV in memset() UpgradeStatus: Upgraded to trusty on 2013-10-31 (83 days ago) UserGroups: XorgConf: Section ServerFlags Option NoTrapSignals EndSection _LogindSession: / _MarkForUpload: True dmi.bios.date: 09/26/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6MET92WW (1.52 ) dmi.board.name: 4313CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6MET92WW(1.52):bd09/26/2012:svnLENOVO:pn4313CTO:pvrThinkPadT510:rvnLENOVO:rn4313CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4313CTO dmi.product.version: ThinkPad T510 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.50-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.0.1-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.0.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core
[Desktop-packages] [Bug 1276661] [NEW] EOG - Image Viewer freezes when changing extension
Public bug reported: 13.10 64bit Ubuntu; EOG ver 3.8.2-1ubuntu1 I frequently change image formats from .png to .jpg for compatibility with other systems. Since 13.10, whenever I attempt to rename an image that is open in Image Viewer (eog) using save as, the new file is properly saved, but the image viewer window freezes and the Save window above it remains open and cannot be closed. The only way out is to force close/kill Image Viewer, after which the Save window closes as well. This freeze is repeatable. ** Affects: eog (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1276661 Title: EOG - Image Viewer freezes when changing extension Status in “eog” package in Ubuntu: New Bug description: 13.10 64bit Ubuntu; EOG ver 3.8.2-1ubuntu1 I frequently change image formats from .png to .jpg for compatibility with other systems. Since 13.10, whenever I attempt to rename an image that is open in Image Viewer (eog) using save as, the new file is properly saved, but the image viewer window freezes and the Save window above it remains open and cannot be closed. The only way out is to force close/kill Image Viewer, after which the Save window closes as well. This freeze is repeatable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1276661/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1276072] Re: Language selection always falls back to English
I confirm both points (no problem with write-protected ~/.pam_environment, still have to select French). Is there a way to set French as the default language (that is what I wanted when I changed the /etc/environment, but it did not work)? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1276072 Title: Language selection always falls back to English Status in “language-selector” package in Ubuntu: Incomplete Bug description: I upgraded two amd64 computers from 13.04 to 13.10, and discovered on both that the language is set to English (whereas I selected French language at the beginning of the upgrade). Moreover, each time I set it back to French, dragging both French (France and Canada) and some English (UK US) on top of the default English in the language selection list, default English comes back on top at next login. I even tried to modify my .pam_environment (in console mode) and the /etc/environment to set fr_FR as the default, no way: gnome-language- selector seems to force default English as default at each connection! Hopefully, I do understand English, but this is turning me mad. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: language-selector-gnome 0.116 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Tue Feb 4 10:48:33 2014 InstallationDate: Installed on 2013-07-29 (190 days ago) InstallationMedia: Xubuntu 13.04 Raring Ringtail - Release amd64 (20130423.1) MarkForUpload: True PackageArchitecture: all SourcePackage: language-selector UpgradeStatus: Upgraded to saucy on 2014-02-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1276072/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1244578] Re: lightdm-session runs xrdb with -nocpp option
xrdb has supported this feature for longer than the operating system kernel we're all using has even existed. I see no reason to break backwards compatibility just for the sake of breaking it. Thanks -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1244578 Title: lightdm-session runs xrdb with -nocpp option Status in “lightdm” package in Ubuntu: Confirmed Bug description: lightdm-session runs xrdb for .Xresources file with the -nocpp option (Line 37 and 43), which prevents the xrdb from preprocessing the .Xresources file. Many configurations like the popular solarized color theme (https://github.com/solarized/xresources/blob/master/solarized) use this and you find some complaints about in on the internet https://bbs.archlinux.org/viewtopic.php?id=164108 https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1163129 http://superuser.com/questions/655857/urxvt-uses-pink-instead-of-solarized-until-i-run-xrdb-xresources/656213 I don't see a reason for not using the preprocessor and so did the editor of Xsession (the option is not used in /etc/X11/Xsession.d/30x11-common_xresources) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1244578/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 293139] Re: NetworkManager does not use dhclient-exit-hooks.d
So, one thing to note is that dispatcher.d only works for up and down actions, but it doesn't work for obtaining new leases on an interface that is already up, which dhclient hooks do. -- 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/293139 Title: NetworkManager does not use dhclient-exit-hooks.d Status in NetworkManager: Invalid Status in “network-manager” package in Ubuntu: Triaged Status in “network-manager” package in Fedora: Won't Fix Bug description: Binary package hint: network-manager I am running intrepid i386 and amd64 on a handful of systems. On every system, both upgraded and fresh installs, i use a script (first attachment) for updating a DNS record through DNSSEC. Using /etc/network/interfaces or invoking dhclient directly correctly updates the DNS record (second attachment). Using network-manager the DNS record update script doesn't seem to run (third attachment). On a laptop it is inconvenient to constantly reconfigure devices. For desktops, a workaround is to have a dhcp entry in /etc/network/interfaces for the relevant connection. As a side note, the script is designed to work with PPP ip-up.d as well. However, I haven't yet found a way to configure network-manager to dial up to 3G over a bluetooth connected modem. It may apply here similarily though. Wvdial works with the script. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/293139/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1174921] Re: [gen2] Depth 15 by default show rendering bugs in bad clients and mesa
This bug was fixed in the package xserver-xorg-video-intel - 2:2.99.909-0ubuntu2 --- xserver-xorg-video-intel (2:2.99.909-0ubuntu2) trusty; urgency=medium * Refresh xmir patch. -- Maarten Lankhorst maarten.lankho...@ubuntu.com Wed, 05 Feb 2014 14:33:04 + ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: Fix Committed = Fix Released -- 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/1174921 Title: [gen2] Depth 15 by default show rendering bugs in bad clients and mesa Status in “xserver-xorg-video-intel” package in Ubuntu: Fix Released Bug description: Intel Graphics 82865G dont work well. Bad colors. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: openbox 3.5.0-7 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic i686 ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 CasperVersion: 1.330 Date: Tue Apr 30 20:50:11 2013 LiveMediaBuild: Lubuntu 13.04 Raring Ringtail - Release i386 (20130423.1) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: openbox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1174921/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1273246] Re: [gen4] gpu hang due to batch overflow
This bug was fixed in the package xserver-xorg-video-intel - 2:2.99.909-0ubuntu2 --- xserver-xorg-video-intel (2:2.99.909-0ubuntu2) trusty; urgency=medium * Refresh xmir patch. -- Maarten Lankhorst maarten.lankho...@ubuntu.com Wed, 05 Feb 2014 14:33:04 + ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: Fix Committed = Fix Released -- 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/1273246 Title: [gen4] gpu hang due to batch overflow Status in “xserver-xorg-video-intel” package in Ubuntu: Fix Released Bug description: I'm seeing in dmesg logs: [15869.816016] [drm] stuck on render ring [15869.816022] [drm] GPU crash dump saved to /sys/class/drm/card0/error [15869.816023] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [15869.816024] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI - DRM/Intel [15869.816026] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [15869.816027] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. This started sometime in the last couple weeks on trusty. It is moderately annoying in that apport kicks in and walks me through a collection process and then (I think) *it* dies, so I was unable to actually report the bug. Instead, I reported this bug with: ubuntu-bug xserver-xorg-video-intel One thing that might be interesting is that /sys/class/drm/card0/error is an empty file. (and so is /sys/kernel/debug/dri/0/i915_error_state) $ ls -l /sys/class/drm/card0/error -rw--- 1 root root 0 Jan 27 09:35 /sys/class/drm/card0/error ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-intel 2:2.99.907-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 Uname: Linux 3.13.0-5-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.1-0ubuntu2 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,snap,commands,mousepoll,grid,move,place,imgpng,session,vpswitch,resize,regex,gnomecompat,unitymtgrabhandles,wall,resizeinfo,animation,workarounds,fade,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Jan 27 09:32:17 2014 DistUpgraded: 2013-05-20 08:14:41,880 DEBUG openCache() DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: tp-smapi, 0.41, 3.13.0-4-generic, x86_64: installed tp-smapi, 0.41, 3.13.0-5-generic, x86_64: installed virtualbox, 4.3.2, 3.13.0-4-generic, x86_64: installed virtualbox, 4.3.2, 3.13.0-5-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:20e4] Subsystem: Lenovo Device [17aa:20e4] InstallationDate: Installed on 2011-10-19 (831 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MachineType: LENOVO 7417CTO PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-5-generic root=UUID=f9832678-e9fb-41c5-8edb-5edd5200ed0a ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-intel UpgradeStatus: Upgraded to trusty on 2013-05-20 (252 days ago) dmi.bios.date: 12/06/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 7UET91WW (3.21 ) dmi.board.name: 7417CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7UET91WW(3.21):bd12/06/2010:svnLENOVO:pn7417CTO:pvrThinkPadT400:rvnLENOVO:rn7417CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 7417CTO dmi.product.version: ThinkPad T400 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.0.1-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.0.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu11 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.907-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu1
[Desktop-packages] [Bug 1274822] Re: latest update breaks nvidia-prime and produces blank screen
Yes, that's exactly why I was asking about those files. ** Changed in: nvidia-prime (Ubuntu) Status: Incomplete = Fix Released -- 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/1274822 Title: latest update breaks nvidia-prime and produces blank screen Status in “nvidia-prime” package in Ubuntu: Fix Released Bug description: I'm currently using a laptop with optimus technology and NVidia graphic card. Last year (2013) I installed NVidia-prime and it worked perfectly. However, the very recent update (2014/1/29) broke NVidia- prime. The screen turned into complete blackness after Ubuntu splash screen (the purple one), and was even not showing cursor. However, from several difference behaviors I am sure that everything else (like terminals, keyboard inputs and even games) is working properly after login. Ubuntu version: 14.04 (Trusty Tahr) nvidia-prime version: 0.5.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1274822/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1275960] Re: [Peppy, Realtek ALC283, Speaker, Internal] AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd
hw is haswel audio -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1275960 Title: [Peppy, Realtek ALC283, Speaker, Internal] AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/pcmC1D2c', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D8p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit Status in “pulseaudio” package in Ubuntu: Incomplete Bug description: Having trouble getting sound to work in ubuntu (saucy) unity. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: pulseaudio 1:4.0-0ubuntu6 Uname: Linux 3.8.11 x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/pcmC1D2c', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D8p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied Date: Mon Feb 3 17:16:59 2014 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [Peppy, Realtek ALC283, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2013 dmi.bios.vendor: coreboot dmi.bios.version: Google_Peppy.4389.81.0 dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvncoreboot:bvrGoogle_Peppy.4389.81.0:bd10/29/2013:svnAcer:pnPeppy:pvr1.0:cvnAcer:ct3:cvr: dmi.product.name: Peppy dmi.product.version: 1.0 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1275960/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 982316] Re: Deja Dup is unable to detect network connection
I have the same problem on ubuntu 13.10 I currently change the ip of my nas server inside the .ssh/config file on a regular basis (similar to the ProxyCommand) - I've found a workaround based on the comments here, basically add the Host alias from .ssh/config to /etc/hosts (even just pointing to 127.0.0.1, this'll trick deja-dup into always believing a connection is available) -- 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/982316 Title: Deja Dup is unable to detect network connection Status in Déjà Dup Backup Tool: Confirmed Status in “deja-dup” package in Ubuntu: Confirmed Bug description: There is a problem with network detection for scheduled backup. I get the following notification : Scheduled backup delayed Backup will begin when a network connection becomes available. The network is working and manual backup is working as well. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: deja-dup 22.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu3 Architecture: amd64 Date: Sun Apr 15 15:12:36 2012 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) ProcEnviron: PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: deja-dup UpgradeStatus: Upgraded to precise on 2012-04-02 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/982316/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1276684] [NEW] lightdm isn't showing a greeter
Public bug reported: Not sure why... but lightdm has just stopped loading for me. I couldn't find anything interesting in the logs... but switching to gdm worked. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.9.6-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-7.25-generic 3.13.1 Uname: Linux 3.13.0-7-generic x86_64 ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Feb 5 11:10:41 2014 InstallationDate: Installed on 2014-01-17 (18 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140115) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1276684 Title: lightdm isn't showing a greeter Status in “lightdm” package in Ubuntu: New Bug description: Not sure why... but lightdm has just stopped loading for me. I couldn't find anything interesting in the logs... but switching to gdm worked. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.9.6-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-7.25-generic 3.13.1 Uname: Linux 3.13.0-7-generic x86_64 ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Feb 5 11:10:41 2014 InstallationDate: Installed on 2014-01-17 (18 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140115) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1276684/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1276630] Re: cups-browsed upstart job does not load the apparmor profile for cups-browsed
** Tags added: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1276630 Title: cups-browsed upstart job does not load the apparmor profile for cups- browsed Status in “cups-filters” package in Ubuntu: Triaged Bug description: On up to date trust I noticed that: $ sudo aa-status apparmor module is loaded. 124 profiles are loaded. ... /usr/sbin/cups-browsed 0 profiles are in complain mode. 32 processes have profiles defined. 31 processes are in enforce mode. ... 0 processes are in complain mode. 1 processes are unconfined but have a profile defined. /usr/sbin/cups-browsed (1222) This means that while there is an apparmor profile for cups-browsed and it is loaded (good), it is being loaded into the kernel after /usr/sbin/cups-browsed is started which means that /usr/sbin/cups- browsed is running unconfined (bad). Fix is to adjust the upstart job to either use /lib/init/apparmor- profile-load in the pre-start or to use the new apparmor stanza in the upstart job. Since cups itself is still using /lib/init/apparmor- profile-load, attached is a patch to use it for cups-browsed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1276630/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1276674] Re: Suspend works flawlessly however resume leads to a checker board screen rather that lightdm
** Attachment added: P130.JPG https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1276674/+attachment/3969969/+files/P130.JPG -- 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/1276674 Title: Suspend works flawlessly however resume leads to a checker board screen rather that lightdm Status in “nvidia-graphics-drivers-331” package in Ubuntu: New Bug description: Upon installing nvidia-331 and nvidia-prime if I suspend the laptop everything goes down as expected. However upon resume I get a checkerboard style page rather than the lightdm login page. If I disable the nvidia stuff from the optimus box and just have the intel gfx running suspend and resume work again. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nvidia-331 331.38-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-7.25-generic 3.13.1 Uname: Linux 3.13.0-7-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 Date: Wed Feb 5 15:57:56 2014 InstallationDate: Installed on 2014-01-10 (26 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140109) SourcePackage: nvidia-graphics-drivers-331 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1276674/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1276674] Re: Suspend works flawlessly however resume leads to a checker board screen rather that lightdm
** Attachment added: nvidia-bug-report.log.gz https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1276674/+attachment/3969970/+files/nvidia-bug-report.log.gz -- 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/1276674 Title: Suspend works flawlessly however resume leads to a checker board screen rather that lightdm Status in “nvidia-graphics-drivers-331” package in Ubuntu: New Bug description: Upon installing nvidia-331 and nvidia-prime if I suspend the laptop everything goes down as expected. However upon resume I get a checkerboard style page rather than the lightdm login page. If I disable the nvidia stuff from the optimus box and just have the intel gfx running suspend and resume work again. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nvidia-331 331.38-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-7.25-generic 3.13.1 Uname: Linux 3.13.0-7-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 Date: Wed Feb 5 15:57:56 2014 InstallationDate: Installed on 2014-01-10 (26 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140109) SourcePackage: nvidia-graphics-drivers-331 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1276674/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1276674] [NEW] Suspend works flawlessly however resume leads to a checker board screen rather that lightdm
Public bug reported: Upon installing nvidia-331 and nvidia-prime if I suspend the laptop everything goes down as expected. However upon resume I get a checkerboard style page rather than the lightdm login page. If I disable the nvidia stuff from the optimus box and just have the intel gfx running suspend and resume work again. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nvidia-331 331.38-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-7.25-generic 3.13.1 Uname: Linux 3.13.0-7-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 Date: Wed Feb 5 15:57:56 2014 InstallationDate: Installed on 2014-01-10 (26 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140109) SourcePackage: nvidia-graphics-drivers-331 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-331 (Ubuntu) Importance: Undecided Assignee: Alberto Milone (albertomilone) Status: New ** Tags: amd64 apport-bug 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/1276674 Title: Suspend works flawlessly however resume leads to a checker board screen rather that lightdm Status in “nvidia-graphics-drivers-331” package in Ubuntu: New Bug description: Upon installing nvidia-331 and nvidia-prime if I suspend the laptop everything goes down as expected. However upon resume I get a checkerboard style page rather than the lightdm login page. If I disable the nvidia stuff from the optimus box and just have the intel gfx running suspend and resume work again. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nvidia-331 331.38-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-7.25-generic 3.13.1 Uname: Linux 3.13.0-7-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 Date: Wed Feb 5 15:57:56 2014 InstallationDate: Installed on 2014-01-10 (26 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140109) SourcePackage: nvidia-graphics-drivers-331 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1276674/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1276564] [NEW] [Toshiba Satellite Pro N10] Black screen during boot
You have been subscribed to a public bug: I helped a user set up his Toshiba Satellite Pro N10 during FOSDEM (so I cannot easily do further tests). Default installation of saucy from USB media, after reboot, screen turns purple for five seconds, then black (backlight off). No logo is shown on purple background. Forums suggest that backlight control and kernel mode switching on this hardware do not work together well. Disabling kernel mode switch and removing quiet and splash options shows normal boot, but X refuses to start (Screens present but no usable configuration). ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- [Toshiba Satellite Pro N10] Black screen during boot https://bugs.launchpad.net/bugs/1276564 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1276564] Re: [Toshiba Satellite Pro N10] Black screen during boot
(This might also affect plymouth, but the main issue is that xorg does not have backlight) ** Package changed: ubuntu = xorg (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1276564 Title: [Toshiba Satellite Pro N10] Black screen during boot Status in “xorg” package in Ubuntu: New Bug description: I helped a user set up his Toshiba Satellite Pro N10 during FOSDEM (so I cannot easily do further tests). Default installation of saucy from USB media, after reboot, screen turns purple for five seconds, then black (backlight off). No logo is shown on purple background. Forums suggest that backlight control and kernel mode switching on this hardware do not work together well. Disabling kernel mode switch and removing quiet and splash options shows normal boot, but X refuses to start (Screens present but no usable configuration). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1276564/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
