[Desktop-packages] [Bug 1247990] Re: dbus: Fix endianness bug in Frequency and Signal properties
Confirmed the patch fixes the issues in steps 3-5 above. Tested on a Powerbook G4 running 12.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpasupplicant in Ubuntu. https://bugs.launchpad.net/bugs/1247990 Title: dbus: Fix endianness bug in Frequency and Signal properties Status in “wpasupplicant” package in Ubuntu: Confirmed Bug description: Please include the attached patch in the next update to wpasupplicant in Ubuntu 12.04 (Precise). The patch is based on this upstream commit http://w1.fi/gitweb/gitweb.cgi?p=hostap-1.git;a=commitdiff;h=42f93a9a0f1858ba8492a1349515624965a64e34;hp=5045a668201f1027dbcc91bd8d092bbcee15a2e3 The version of wpasupplicant currently in precise has the following PowerPC bug: To reproduce: 1. connect to a wireless network by clicking on the name in the applet. 2. check that the connection works. 3. see that there is no network listed under Wireless Networks in the applet menu. (Although the Disconnect word is there and functional.) 4. see that the signal strength is apparantly empty on the applet icon. (Yet the signal strength is actually quite strong.) 5. check nmcli command and see that signal strength always shows 100 and frequency 0. Applying the patch to wpasupplicant 0.7.3-6ubuntu2.1 fixes the problem (on my PowerPC G4 iBook). Before finding this patch I've had to work around the problem by installing wicd. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpasupplicant/+bug/1247990/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1247990] Re: dbus: Fix endianness bug in Frequency and Signal properties
** Changed in: wpasupplicant (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpasupplicant in Ubuntu. https://bugs.launchpad.net/bugs/1247990 Title: dbus: Fix endianness bug in Frequency and Signal properties Status in “wpasupplicant” package in Ubuntu: Confirmed Bug description: Please include the attached patch in the next update to wpasupplicant in Ubuntu 12.04 (Precise). The patch is based on this upstream commit http://w1.fi/gitweb/gitweb.cgi?p=hostap-1.git;a=commitdiff;h=42f93a9a0f1858ba8492a1349515624965a64e34;hp=5045a668201f1027dbcc91bd8d092bbcee15a2e3 The version of wpasupplicant currently in precise has the following PowerPC bug: To reproduce: 1. connect to a wireless network by clicking on the name in the applet. 2. check that the connection works. 3. see that there is no network listed under Wireless Networks in the applet menu. (Although the Disconnect word is there and functional.) 4. see that the signal strength is apparantly empty on the applet icon. (Yet the signal strength is actually quite strong.) 5. check nmcli command and see that signal strength always shows 100 and frequency 0. Applying the patch to wpasupplicant 0.7.3-6ubuntu2.1 fixes the problem (on my PowerPC G4 iBook). Before finding this patch I've had to work around the problem by installing wicd. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpasupplicant/+bug/1247990/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1326414] [NEW] Hang in change password dialog
Public bug reported: The change password dialog can hang in certain situations. To reproduce: 1) Launch system settings 2) Open the User accounts control panel 3) Click the password 'dots' to open the Changing password dialog 4) Enter the current password, and enter a password that the system thinks is weak, like 'ubuntu' 5) Press the 'change' button'. A dialog should appear that says, The new password is too simple. Please choose another password.. Close the dialog. 6) In the change password dialog, re-enter the weak password from step 4 7) Press the change button Expected results: Either the system accepts the new password, or the The new password is too simple dialog from step 5 appears. Actual results: The Changing password dialog is greyed out and the cursor changes to the spinning please wait cursor. The password is not changed. This is 100% reproducible for me. May be related to https://bugzilla.gnome.org/show_bug.cgi?id=701701 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-control-center 1:3.4.2-0ubuntu0.13.2 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 ApportVersion: 2.0.1-0ubuntu5 Architecture: amd64 Date: Wed Jun 4 10:54:45 2014 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu3 deja-dup22.0-0ubuntu2 gnome-bluetooth 3.2.2-0ubuntu5 indicator-datetime 0.3.94-0ubuntu2 ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- 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/1326414 Title: Hang in change password dialog Status in “gnome-control-center” package in Ubuntu: New Bug description: The change password dialog can hang in certain situations. To reproduce: 1) Launch system settings 2) Open the User accounts control panel 3) Click the password 'dots' to open the Changing password dialog 4) Enter the current password, and enter a password that the system thinks is weak, like 'ubuntu' 5) Press the 'change' button'. A dialog should appear that says, The new password is too simple. Please choose another password.. Close the dialog. 6) In the change password dialog, re-enter the weak password from step 4 7) Press the change button Expected results: Either the system accepts the new password, or the The new password is too simple dialog from step 5 appears. Actual results: The Changing password dialog is greyed out and the cursor changes to the spinning please wait cursor. The password is not changed. This is 100% reproducible for me. May be related to https://bugzilla.gnome.org/show_bug.cgi?id=701701 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-control-center 1:3.4.2-0ubuntu0.13.2 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 ApportVersion: 2.0.1-0ubuntu5 Architecture: amd64 Date: Wed Jun 4 10:54:45 2014 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu3 deja-dup22.0-0ubuntu2 gnome-bluetooth 3.2.2-0ubuntu5 indicator-datetime 0.3.94-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1326414/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1287341] Re: Touchscreen controls both screens in dual-monitor setup
@Alberto: The package in http://people.canonical.com/~amilone/lp1287341/ fixes the behavior of the touchscreen for me. The touschreen now works as expected with and without an external monitor. Tested on a Dell XPS13 with factory-installed touchscreen. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1287341 Title: Touchscreen controls both screens in dual-monitor setup Status in Gnome Settings Daemon: Fix Released Status in OEM Priority Project: New Status in OEM Priority Project trusty series: New Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “unity-settings-daemon” package in Ubuntu: In Progress Bug description: My laptop has a touchscreen. It works fine in 14.04 until I plug in an external monitor. When using an external monitor, input from the touchscreen is remapped so that the touchscreen provides input to both monitors. The result is that there is no longer a 1:1 correspondence between moving your finger and the cursor. This is confusing and difficult to use. A touchscreen is a direct input device (vs an indirect one like a mouse/touchpad); input from the touchscreen should be bound to the physical display that it's attached to. To reproduce: 1) On a computer with a touchscreen, use the touchscreen to move a window around, including to the edges of the screen. Note that the window moves exactly with your finger. 2) Plug in an external monitor 3) Try the same actions as in step 1 Expected results: The touchscreen continues to operate as in step 1, allowing you to manipulate items on the display that contains the touchscreen. The touchscreen does not interact with windows, etc on the external monitor Actual results: The touchscreen is remapped across both displays. The result is that touch events no longer happen 'under the finger'. Assuming the two displays are the same size and resolution, moving your finger 1cm will cause the window or other objects to move 2cm onscreen. It becomes impossible to use the touchscreen to interact with widgets (menus, buttons, etc). This is described in couple places: http://askubuntu.com/questions/51445/how-do-i-calibrate-a-touchscreen-on-a-dual-monitor-system http://askubuntu.com/questions/71768/touchscreen-and-additional-external-monitor ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xinput 1.6.1-1 ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5 Uname: Linux 3.13.0-14-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: [core,commands,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 CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Mar 3 14:41:14 2014 DistUpgraded: 2014-02-12 13:40:42,704 DEBUG enabling apt cron job DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: oem-audio-hda-daily-lts-quantal, 0.201308192259~precise1, 3.5.0-45-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-12-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-14-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-8-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:060a] InstallationDate: Installed on 2013-12-02 (90 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 MachineType: Dell Inc. XPS13 9333 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-14-generic root=UUID=0b9db31c-747b-40ad-bbbd-13a9a29caece ro quiet splash vt.handoff=7 SourcePackage: xinput UpgradeStatus: Upgraded to trusty on 2014-02-12 (19 days ago) dmi.bios.date: 11/11/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 0GFTRT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA01:bd11/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc1-1ubuntu4
[Desktop-packages] [Bug 1307701] Re: xserver mouse pointer emulation from touch breaks with QML app.
I can no longer reproduce this with qtbase 5.2.1+dfsg-1ubuntu14.2 - nice work! -- 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/1307701 Title: xserver mouse pointer emulation from touch breaks with QML app. Status in OEM Priority Project: New Status in OEM Priority Project trusty series: Triaged Status in X.Org X server: Confirmed Status in “qtbase-opensource-src” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Invalid Status in “xorg-server” package in Ubuntu: In Progress Status in “qtbase-opensource-src” source package in Trusty: Fix Committed Status in “unity” source package in Trusty: Invalid Status in “xorg-server” source package in Trusty: Confirmed Bug description: When running an SDK app on the desktop, it's not possible to use the touchscreen to move windows, use the launcher, etc. The SDK app seems to consume all touchscreen events. To reproduce: 1) On a desktop/laptop with a touchscreen (I am using a Dell XPS13), install 14.04 and check that the touchscreen works for moving windows 2) Install the camera-app package from universe (I have 2.9.1+14.04.20140331-0ubuntu1) 3) Launch the camera app 4) Touch once inside the camera-app window 5) Use the touchscreen to drag the camera-app window Expected results: You can move the camera-app window using the touchscreen Actual results: You cannot move the camera-app window, or perform any other touch tasks in unity, with the touchscreen This only affects touchscreen input - mouse/touchpad input is not affected This affects all apps written with the SDK (I tried camera-app, gallery-app, reminders-app). It's 100% reproducible. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CurrentDesktop: Unity Date: Mon Apr 14 14:59:09 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-02 (132 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-02-12 (61 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1307701/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1287341] Re: Touchscreen controls both screens in dual-monitor setup
@Alberto: steve@aether:~$ xinput list ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ SYNAPTICS Synaptics Large Touch Screenid=12 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPadid=15 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Button id=8[slave keyboard (3)] ↳ Integrated_Webcam_HD id=13 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=14 [slave keyboard (3)] ↳ Dell WMI hotkeys id=16 [slave keyboard (3)] ↳ Integrated_Webcam_HD id=9[slave keyboard (3)] steve@aether:~$ xinput list-props 12 Device 'SYNAPTICS Synaptics Large Touch Screen': Device Enabled (135): 1 Coordinate Transformation Matrix (137): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 Device Accel Profile (260): 0 Device Accel Constant Deceleration (261): 1.00 Device Accel Adaptive Deceleration (262): 1.00 Device Accel Velocity Scaling (263):10.00 Device Product ID (252):1739, 2808 Device Node (253): /dev/input/event12 Evdev Axis Inversion (264): 0, 0 Evdev Axis Calibration (265): no items Evdev Axes Swap (266): 0 Axis Labels (267): Abs MT Position X (283), Abs MT Position Y (284), None (0), None (0) Button Labels (268):Button Unknown (256), Button Unknown (256), Button Unknown (256), Button Wheel Up (141), Button Wheel Down (142) Evdev Middle Button Emulation (269):0 Evdev Middle Button Timeout (270): 50 Evdev Third Button Emulation (271): 0 Evdev Third Button Emulation Timeout (272): 1000 Evdev Third Button Emulation Button (273): 3 Evdev Third Button Emulation Threshold (274): 20 Evdev Wheel Emulation (275):0 Evdev Wheel Emulation Axes (276): 0, 0, 4, 5 Evdev Wheel Emulation Inertia (277):10 Evdev Wheel Emulation Timeout (278):200 Evdev Wheel Emulation Button (279): 4 Evdev Drag Lock Buttons (280): 0 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1287341 Title: Touchscreen controls both screens in dual-monitor setup Status in Gnome Settings Daemon: New Status in OEM Priority Project: New Status in OEM Priority Project trusty series: New Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “unity-settings-daemon” package in Ubuntu: Triaged Bug description: My laptop has a touchscreen. It works fine in 14.04 until I plug in an external monitor. When using an external monitor, input from the touchscreen is remapped so that the touchscreen provides input to both monitors. The result is that there is no longer a 1:1 correspondence between moving your finger and the cursor. This is confusing and difficult to use. A touchscreen is a direct input device (vs an indirect one like a mouse/touchpad); input from the touchscreen should be bound to the physical display that it's attached to. To reproduce: 1) On a computer with a touchscreen, use the touchscreen to move a window around, including to the edges of the screen. Note that the window moves exactly with your finger. 2) Plug in an external monitor 3) Try the same actions as in step 1 Expected results: The touchscreen continues to operate as in step 1, allowing you to manipulate items on the display that contains the touchscreen. The touchscreen does not interact with windows, etc on the external monitor Actual results: The touchscreen is remapped across both displays. The result is that touch events no longer happen 'under the finger'. Assuming the two displays are the same size and resolution, moving your finger 1cm will cause the window or other objects to move 2cm onscreen. It becomes impossible to use the touchscreen to interact with widgets (menus, buttons, etc). This is described in couple places: http://askubuntu.com/questions/51445/how-do-i-calibrate-a-touchscreen-on-a-dual-monitor-system http://askubuntu.com/questions/71768/touchscreen-and-additional-external-monitor ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xinput 1.6.1-1 ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5 Uname: Linux 3.13.0-14-generic x86_64
[Desktop-packages] [Bug 1307559] [NEW] Window decorations not drawn on external monitor
Public bug reported: Window decorations (close / minimize / maximize buttons) do not draw on the external monitor on a laptop with external display. Windows on the laptop display are not affected. UI scale on the built-in display is 1.25; it's 1.0 on the external display. I am not sure if this is relevant. To reproduce: 1) Plug in an external monitor to a laptop; ensure that it is running in extended display mode 2) Launch an application such as the terminal 3) The terminal launches on the laptop's built-in display. Observe the window decorations draw as expected 4) Drag the terminal window to the second display Expected results; The terminal window is drawn on the extended display Actual results: The terminal window is drawn on the extended display but the close, minimize, and maximize buttons are missing. The problem happens on windows from all applications I've tried (firefox, terminal, emacs, thunderbird) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CompizPlugins: [core,commands,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 CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Apr 14 10:56:46 2014 DistUpgraded: 2014-02-12 13:40:42,704 DEBUG enabling apt cron job DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fwts-efi-runtime-dkms, 14.03.01, 3.13.0-23-generic, x86_64: installed fwts-efi-runtime-dkms, 14.03.01, 3.13.0-24-generic, x86_64: installed virtualbox, 4.3.10, 3.13.0-23-generic, x86_64: installed virtualbox, 4.3.10, 3.13.0-24-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:060a] InstallationDate: Installed on 2013-12-02 (132 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 MachineType: Dell Inc. XPS13 9333 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=0b9db31c-747b-40ad-bbbd-13a9a29caece ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-02-12 (60 days ago) dmi.bios.date: 11/11/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 0GFTRT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA01:bd11/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon Apr 14 08:54:29 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4933 vendor CMN xserver.version: 2:1.15.0-1ubuntu7 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 rls-t-incoming third-party-packages trusty ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1307559 Title: Window decorations not drawn on external monitor Status in “unity” package in Ubuntu: New Bug description: Window decorations (close / minimize / maximize buttons) do not draw on the external monitor on a laptop with external display. Windows on the laptop display are not affected. UI scale on the built-in display is 1.25; it's 1.0 on the external display. I am not sure if this is relevant. To reproduce: 1) Plug in an external monitor to a laptop; ensure that it is
[Desktop-packages] [Bug 1307701] [NEW] Unity does not get touch events when SDK apps running
Public bug reported: When running an SDK app on the desktop, it's not possible to use the touchscreen to move windows, use the launcher, etc. The SDK app seems to consume all touchscreen events. To reproduce: 1) On a desktop/laptop with a touchscreen (I am using a Dell XPS13), install 14.04 and check that the touchscreen works for moving windows 2) Install the camera-app package from universe (I have 2.9.1+14.04.20140331-0ubuntu1) 3) Launch the camera app 4) Touch once inside the camera-app window 5) Use the touchscreen to drag the camera-app window Expected results: You can move the camera-app window using the touchscreen Actual results: You cannot move the camera-app window, or perform any other touch tasks in unity, with the touchscreen This only affects touchscreen input - mouse/touchpad input is not affected This affects all apps written with the SDK (I tried camera-app, gallery- app, reminders-app). It's 100% reproducible. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CurrentDesktop: Unity Date: Mon Apr 14 14:59:09 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-02 (132 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-02-12 (61 days ago) ** Affects: oem-priority Importance: Undecided Status: New ** Affects: oem-priority/trusty Importance: Undecided Status: New ** Affects: unity (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug desktop-touch third-party-packages trusty ** Tags added: rls-t-incoming -- 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/1307701 Title: Unity does not get touch events when SDK apps running Status in OEM Priority Project: New Status in OEM Priority Project trusty series: New Status in “unity” package in Ubuntu: Confirmed Bug description: When running an SDK app on the desktop, it's not possible to use the touchscreen to move windows, use the launcher, etc. The SDK app seems to consume all touchscreen events. To reproduce: 1) On a desktop/laptop with a touchscreen (I am using a Dell XPS13), install 14.04 and check that the touchscreen works for moving windows 2) Install the camera-app package from universe (I have 2.9.1+14.04.20140331-0ubuntu1) 3) Launch the camera app 4) Touch once inside the camera-app window 5) Use the touchscreen to drag the camera-app window Expected results: You can move the camera-app window using the touchscreen Actual results: You cannot move the camera-app window, or perform any other touch tasks in unity, with the touchscreen This only affects touchscreen input - mouse/touchpad input is not affected This affects all apps written with the SDK (I tried camera-app, gallery-app, reminders-app). It's 100% reproducible. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CurrentDesktop: Unity Date: Mon Apr 14 14:59:09 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-02 (132 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-02-12 (61 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1307701/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1307701] Re: Unity does not get touch events when SDK apps running
** Also affects: oem-priority Importance: Undecided Status: New ** Also affects: oem-priority/trusty Importance: Undecided Status: New -- 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/1307701 Title: Unity does not get touch events when SDK apps running Status in OEM Priority Project: New Status in OEM Priority Project trusty series: New Status in “unity” package in Ubuntu: Confirmed Bug description: When running an SDK app on the desktop, it's not possible to use the touchscreen to move windows, use the launcher, etc. The SDK app seems to consume all touchscreen events. To reproduce: 1) On a desktop/laptop with a touchscreen (I am using a Dell XPS13), install 14.04 and check that the touchscreen works for moving windows 2) Install the camera-app package from universe (I have 2.9.1+14.04.20140331-0ubuntu1) 3) Launch the camera app 4) Touch once inside the camera-app window 5) Use the touchscreen to drag the camera-app window Expected results: You can move the camera-app window using the touchscreen Actual results: You cannot move the camera-app window, or perform any other touch tasks in unity, with the touchscreen This only affects touchscreen input - mouse/touchpad input is not affected This affects all apps written with the SDK (I tried camera-app, gallery-app, reminders-app). It's 100% reproducible. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140411-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CurrentDesktop: Unity Date: Mon Apr 14 14:59:09 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-02 (132 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-02-12 (61 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1307701/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1292935] Re: New Lockscreen inhibits putting the screens to sleep.
** Also affects: oem-priority Importance: Undecided Status: New ** Also affects: oem-priority/trusty Importance: Undecided Status: New -- 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/1292935 Title: New Lockscreen inhibits putting the screens to sleep. Status in OEM Priority Project: New Status in OEM Priority Project trusty series: New Status in “unity” package in Ubuntu: Triaged Bug description: Ok, so since the new lockscreen landed in Trusty, I've been observing inconsistent behavior with the power settings on my screens. I managed to do a little bit of troubleshooting and this is what I discovered: My power settings are set such that the screens turn off prior to the screen locking (5 minutes and 10 minutes respectively but I don't think the times are relevant). If I walk away from my computer and leave it unlocked, the screens will successfully power down, and the next time I come back then the lock screen will appear when I wake up the screens. This part is good. If I type Ctrl-Alt-L, the screen locks, but it keeps the screens on, even for extended periods of time (eg, overnight. On several occaisions I've locked my screen, gone to bed, and then woken up to discover both my screens powered on at maximum brightness just displaying that sexy lockscreen). Oddly, when I unlock the screens in this state, what will happen is that just a few seconds after unlocking, some kind of timer will trigger and say oh yeah, time to power down the screens! so even though I *just unlocked my desktop*, both screens power down for about 5 seconds and then turn back on, and *then* they fade to black and snap back to maximum brightness. It's very discordant. So, the workaround for me is don't lock the screen, and that's probably fine at home, but obviously that's not a viable solution in any kind of security context, eg in an office. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140313-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sat Mar 15 10:56:14 2014 InstallationDate: Installed on 2013-12-06 (99 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-12-06 (99 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1292935/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1291365] Re: gnome screensaver locks again shortly after unlocking
** Also affects: oem-priority/trusty Importance: Undecided Status: New -- 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/1291365 Title: gnome screensaver locks again shortly after unlocking Status in OEM Priority Project: New Status in OEM Priority Project trusty series: New Status in “gnome-screensaver” package in Ubuntu: Confirmed Bug description: When I unlock my screen, I sometimes get only a few seconds of interaction with my desktop before the screen inexplicably locks itself again. I believe this only happens when I manually lock it with my ThinkVantage key that I have bound to the lock-screen shortcut, but I can't be sure of that. I've seen this for a while now, but assumed it was some bug caused by either a borked compiz or some kind of delay catch-up happening because gnome-screensaver took too long to swap in. But I just upgraded to the latest trusty compiz that has tons of bugfixes, and the new lock screen keeps gnome-screensaver swapped in nicely. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-screensaver 3.6.1-0ubuntu10 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Mar 12 13:13:43 2014 EcryptfsInUse: Yes GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'ubuntu' org.gnome.desktop.session idle-delay uint32 600 SourcePackage: gnome-screensaver UpgradeStatus: Upgraded to trusty on 2014-02-25 (14 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1291365/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1304672] [NEW] unknown audio device dialog on resume from suspend
Public bug reported: Sometimes when I resume from suspend, I get the Unknown Audio Device dialog that asks whether a device is headphones/microphone/headset. This happens sometimes when there are no audio devices plugged in, which seems like a bug. To reproduce: 1) Suspend 2) Unplug any audio devices such as headphones or USB headsets 3) Resume Expected results: The machine resumes normally; there is no Unknown Audio Device dialog Actual results: The machine resumes normally. The Unknown Audio Device dialog appears onscreen when you resume. alsa-info.sh output for my machine (Dell XPS 13) is attached ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-settings-daemon 14.04.0+14.04.20140407-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 8 16:55:47 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-02 (126 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 SourcePackage: unity-settings-daemon UpgradeStatus: Upgraded to trusty on 2014-02-12 (55 days ago) ** Affects: unity-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty ** Attachment added: alsa-info.sh output, captured after resume https://bugs.launchpad.net/bugs/1304672/+attachment/4075806/+files/alsa-info.txt.VoMh02RkTA -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1304672 Title: unknown audio device dialog on resume from suspend Status in “unity-settings-daemon” package in Ubuntu: New Bug description: Sometimes when I resume from suspend, I get the Unknown Audio Device dialog that asks whether a device is headphones/microphone/headset. This happens sometimes when there are no audio devices plugged in, which seems like a bug. To reproduce: 1) Suspend 2) Unplug any audio devices such as headphones or USB headsets 3) Resume Expected results: The machine resumes normally; there is no Unknown Audio Device dialog Actual results: The machine resumes normally. The Unknown Audio Device dialog appears onscreen when you resume. alsa-info.sh output for my machine (Dell XPS 13) is attached ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-settings-daemon 14.04.0+14.04.20140407-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 8 16:55:47 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-02 (126 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 SourcePackage: unity-settings-daemon UpgradeStatus: Upgraded to trusty on 2014-02-12 (55 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1304672/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1302155] [NEW] Chromium UI is very large
Public bug reported: I'm using the chromium-browser build from https://launchpad.net/~cmiller/+archive/chromium-browser-dev-daily so that I can test touchscreen functionality. The entire app looks like it's been scaled up by a factor of at least 2x, so all UI elements/fonts/images are very large. To reproduce: 1) Launch chromium Expected resuilts: Chromium uses system widget + font sizes Actual results: Chromium renders all UI elements at least 2x larger than normal. Browser version is: Version 35.0.1870.2 Ubuntu 14.04 aura (254650) This behavior happens regardless of whether I have the UI scale slider in the displays control panel set to 1 or some other value like 1.25. Deleting the cache + preferences from ~/.cache/chromium and ~/.config/chromium does not fix the problem. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: chromium-browser 35.0.1870.2-0~devtesting032301~s~pkg988.1 [origin: LP-PPA-cmiller-chromium-browser-dev-daily] ProcVersionSignature: Ubuntu 3.13.0-21.43-generic 3.13.8 Uname: Linux 3.13.0-21-generic x86_64 ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Thu Apr 3 16:06:01 2014 Desktop-Session: DESKTOP_SESSION = ubuntu XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg XDG_DATA_DIRS = /usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/ DetectedPlugins: DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None InstallationDate: Installed on 2013-12-02 (121 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 SourcePackage: chromium-browser ThirdParty: True UpgradeStatus: Upgraded to trusty on 2014-02-12 (50 days ago) chromium-default: CHROMIUM_FLAGS= gconf-keys: /desktop/gnome/applications/browser/exec = b'firefox\n'/desktop/gnome/url-handlers/https/command = b''/desktop/gnome/url-handlers/https/enabled = b''/desktop/gnome/url-handlers/http/command = b''/desktop/gnome/url-handlers/http/enabled = b''/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n' modified.conffile..etc.default.chromium.browser: [deleted] ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1302155 Title: Chromium UI is very large Status in “chromium-browser” package in Ubuntu: New Bug description: I'm using the chromium-browser build from https://launchpad.net/~cmiller/+archive/chromium-browser-dev-daily so that I can test touchscreen functionality. The entire app looks like it's been scaled up by a factor of at least 2x, so all UI elements/fonts/images are very large. To reproduce: 1) Launch chromium Expected resuilts: Chromium uses system widget + font sizes Actual results: Chromium renders all UI elements at least 2x larger than normal. Browser version is: Version 35.0.1870.2 Ubuntu 14.04 aura (254650) This behavior happens regardless of whether I have the UI scale slider in the displays control panel set to 1 or some other value like 1.25. Deleting the cache + preferences from ~/.cache/chromium and ~/.config/chromium does not fix the problem. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: chromium-browser 35.0.1870.2-0~devtesting032301~s~pkg988.1 [origin: LP-PPA-cmiller-chromium-browser-dev-daily] ProcVersionSignature: Ubuntu 3.13.0-21.43-generic 3.13.8 Uname: Linux 3.13.0-21-generic x86_64 ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Thu Apr 3 16:06:01 2014 Desktop-Session: DESKTOP_SESSION = ubuntu XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg XDG_DATA_DIRS = /usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/ DetectedPlugins: DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None InstallationDate: Installed on 2013-12-02 (121 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 SourcePackage: chromium-browser ThirdParty: True UpgradeStatus: Upgraded to trusty on 2014-02-12 (50 days ago) chromium-default: CHROMIUM_FLAGS= gconf-keys: /desktop/gnome/applications/browser/exec =
[Desktop-packages] [Bug 1302155] Re: Chromium UI is very large
Attached screenshot shows the extra-large chromium UI. In the screen on the left, the UI scale (from the displays control panel) is set to 1.25 and the UI scale for the screen on the right is set to 1. The UI scale setting does not seem to affect the size of chromium though - it's big even if I reset the scale to 1.0 on both screens. ** Attachment added: Screenshot showing Chromium in giganto-mode https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1302155/+attachment/4063895/+files/Screenshot%20from%202014-04-03%2016%3A05%3A45.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1302155 Title: Chromium UI is very large Status in “chromium-browser” package in Ubuntu: New Bug description: I'm using the chromium-browser build from https://launchpad.net/~cmiller/+archive/chromium-browser-dev-daily so that I can test touchscreen functionality. The entire app looks like it's been scaled up by a factor of at least 2x, so all UI elements/fonts/images are very large. To reproduce: 1) Launch chromium Expected resuilts: Chromium uses system widget + font sizes Actual results: Chromium renders all UI elements at least 2x larger than normal. Browser version is: Version 35.0.1870.2 Ubuntu 14.04 aura (254650) This behavior happens regardless of whether I have the UI scale slider in the displays control panel set to 1 or some other value like 1.25. Deleting the cache + preferences from ~/.cache/chromium and ~/.config/chromium does not fix the problem. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: chromium-browser 35.0.1870.2-0~devtesting032301~s~pkg988.1 [origin: LP-PPA-cmiller-chromium-browser-dev-daily] ProcVersionSignature: Ubuntu 3.13.0-21.43-generic 3.13.8 Uname: Linux 3.13.0-21-generic x86_64 ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Thu Apr 3 16:06:01 2014 Desktop-Session: DESKTOP_SESSION = ubuntu XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg XDG_DATA_DIRS = /usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/ DetectedPlugins: DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None InstallationDate: Installed on 2013-12-02 (121 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 SourcePackage: chromium-browser ThirdParty: True UpgradeStatus: Upgraded to trusty on 2014-02-12 (50 days ago) chromium-default: CHROMIUM_FLAGS= gconf-keys: /desktop/gnome/applications/browser/exec = b'firefox\n'/desktop/gnome/url-handlers/https/command = b''/desktop/gnome/url-handlers/https/enabled = b''/desktop/gnome/url-handlers/http/command = b''/desktop/gnome/url-handlers/http/enabled = b''/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n' modified.conffile..etc.default.chromium.browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1302155/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1300360] [NEW] Confusing keyboard navigation in dash
Public bug reported: Keyboard navigation in the dash does not work as expected - pressing left arrow after pressing right arrow does not necessarily return you to the original location. To reproduce: 1. Press the super key to open the dash 2. Press down arrow twice to select the first application in the list of applications 3. Press the right arrow repeatedly to select the right-most application in the list of apps 4. Press the right arrow again. The Filter results button is selected 5. Press the left arrow Expected results: The application selected in #3 is re-selected Actual results: The input field is selected This was surprising on a couple of levels: 1) The filter results button is directly above the search results, not to the right 2) You can't retrace your steps using the arrow keys: tapping the left arrow does not 'undo' the effects of tapping right arrow 3) The filter results button is immeidately to the right of the search input field, but you can't get to the filter results button by pressing the right arrow when the search input field is selected. Therefore It's extra-surprising that right arrow gets you to filter results from other places in the dash. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140328.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CurrentDesktop: Unity Date: Mon Mar 31 13:28:12 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-02 (118 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-02-12 (46 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty -- 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/1300360 Title: Confusing keyboard navigation in dash Status in “unity” package in Ubuntu: New Bug description: Keyboard navigation in the dash does not work as expected - pressing left arrow after pressing right arrow does not necessarily return you to the original location. To reproduce: 1. Press the super key to open the dash 2. Press down arrow twice to select the first application in the list of applications 3. Press the right arrow repeatedly to select the right-most application in the list of apps 4. Press the right arrow again. The Filter results button is selected 5. Press the left arrow Expected results: The application selected in #3 is re-selected Actual results: The input field is selected This was surprising on a couple of levels: 1) The filter results button is directly above the search results, not to the right 2) You can't retrace your steps using the arrow keys: tapping the left arrow does not 'undo' the effects of tapping right arrow 3) The filter results button is immeidately to the right of the search input field, but you can't get to the filter results button by pressing the right arrow when the search input field is selected. Therefore It's extra-surprising that right arrow gets you to filter results from other places in the dash. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140328.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CurrentDesktop: Unity Date: Mon Mar 31 13:28:12 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-02 (118 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-02-12 (46 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1300360/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages
[Desktop-packages] [Bug 1296966] Re: Displays: Can't modify UI scale slide with keyboard
** Changed in: unity-control-center (Ubuntu) Status: Fix Released = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1296966 Title: Displays: Can't modify UI scale slide with keyboard Status in “unity-control-center” package in Ubuntu: Confirmed Bug description: It should be possible to modify the UI Scale slider using the keyboard. To reproduce: 1) Launch the Displays control panel 2) Click the thumb/handle in the UI scale slider once, to select it. Notice that the handle gets an orange border, to indicate that it's selected 3) Press the left/right arrow keys to modify the UI scale Expected results: The UI scale slider responds to the arrow keys Actual results: Nothing happens when you use the keyboard to manipulate the UI scale slider This is an accessibility issue. It's also a problem if you set the UI scale so big that the UI scale widget is no longer drawn onscreen - you can't use keyboard navigation to reset it. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.3+14.04.20140319-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-19.39-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 24 17:40:33 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-02 (111 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 SourcePackage: unity-control-center UpgradeStatus: Upgraded to trusty on 2014-02-12 (40 days ago) usr_lib_unity-control-center: activity-log-manager 0.9.7-0ubuntu10 deja-dup 29.5-0ubuntu2 gnome-control-center 1:3.6.3-0ubuntu54 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1296966/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1296966] Re: Displays: Can't modify UI scale slide with keyboard
This is only partially fixed in u-c-c 14.04.3+14.04.20140328-0ubuntu1. The keyboard can now move the slider, but the UI scale does not change when you do this. The UI scale does change when you use the mouse to move the slider. To reproduce, follow the instructions in the original description Expected results: UI slider moves and the UI scales up/down with the slider Actual results: UI slider moves and the UI does not scale up/down with the slider -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1296966 Title: Displays: Can't modify UI scale slide with keyboard Status in “unity-control-center” package in Ubuntu: Confirmed Bug description: It should be possible to modify the UI Scale slider using the keyboard. To reproduce: 1) Launch the Displays control panel 2) Click the thumb/handle in the UI scale slider once, to select it. Notice that the handle gets an orange border, to indicate that it's selected 3) Press the left/right arrow keys to modify the UI scale Expected results: The UI scale slider responds to the arrow keys Actual results: Nothing happens when you use the keyboard to manipulate the UI scale slider This is an accessibility issue. It's also a problem if you set the UI scale so big that the UI scale widget is no longer drawn onscreen - you can't use keyboard navigation to reset it. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.3+14.04.20140319-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-19.39-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 24 17:40:33 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-02 (111 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 SourcePackage: unity-control-center UpgradeStatus: Upgraded to trusty on 2014-02-12 (40 days ago) usr_lib_unity-control-center: activity-log-manager 0.9.7-0ubuntu10 deja-dup 29.5-0ubuntu2 gnome-control-center 1:3.6.3-0ubuntu54 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1296966/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1292041] Re: Lockscreen doesn't turn off the screen
** Tags added: rls-t-incoming -- 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/1292041 Title: Lockscreen doesn't turn off the screen Status in Unity: Invalid Status in “gnome-screensaver” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Invalid Bug description: The new Unity lock screen doesn't turn off the monitor screen. I can wait as long as 10 minutes after activating the lock screen and the monitor still doesn't trun off. Then when I unlock the screen and don't use mouse or keyboard monitor will turn off (it's about 5 seconds after unlocking). To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1292041/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1292041] Re: Lockscreen doesn't turn off the screen
** Also affects: oem-priority Importance: Undecided Status: New ** Also affects: oem-priority/trusty Importance: Undecided Status: New ** Changed in: oem-priority/trusty Importance: Undecided = Critical ** Changed in: oem-priority/trusty Importance: Critical = High -- 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/1292041 Title: Lockscreen doesn't turn off the screen Status in OEM Priority Project: New Status in OEM Priority Project trusty series: New Status in Unity: Invalid Status in “gnome-screensaver” package in Ubuntu: Confirmed Status in “unity” package in Ubuntu: Invalid Bug description: The new Unity lock screen doesn't turn off the monitor screen. I can wait as long as 10 minutes after activating the lock screen and the monitor still doesn't trun off. Then when I unlock the screen and don't use mouse or keyboard monitor will turn off (it's about 5 seconds after unlocking). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1292041/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1284395] Re: conf file prompt on trusty package upgrade
@Till: It's possible that I turned printer sharing on then off (this machine is new, and I do not recall doing it). I have never touched cuspd.conf by hand on this machine. Any printer setup I did was through the GUI tools. If the setting moved into a different file, we should migrate it as part of the upgrade. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1284395 Title: conf file prompt on trusty package upgrade Status in “cups” package in Ubuntu: Incomplete Bug description: I am running trusty. When I upgraded to cups 1.7.1-5ubuntu3, I got a conffile prompt. I don't believe I've manually modified any cups- related conf files, so I didn't expect a prompt - I expected the package upgrade to handle this for me without a prompt. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: cups 1.7.1-5ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Mon Feb 24 20:01:48 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-02 (84 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 MachineType: Dell Inc. XPS13 9333 Papersize: letter PpdFiles: Xerox-WorkCentre-7345: Xerox WorkCentre 7345 Foomatic/pxlcolor (recommended) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-8-generic root=UUID=0b9db31c-747b-40ad-bbbd-13a9a29caece ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to trusty on 2014-02-12 (12 days ago) dmi.bios.date: 11/11/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 0GFTRT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA01:bd11/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.cups.cupsd.conf: 2014-02-12T13:36:32.106432 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1284395/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1295105] Re: Wrong background color in Back Up window
** Tags added: rls-t-incoming -- 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/1295105 Title: Wrong background color in Back Up window Status in “deja-dup” package in Ubuntu: New Bug description: The background colors in the Back Up window are wrong. I think window is supposed to be light grey, but it's black. There is dark gray text on the black background, which is impossible to read. See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: deja-dup 29.5-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 20 08:42:13 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-02 (107 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 SourcePackage: deja-dup UpgradeStatus: Upgraded to trusty on 2014-02-12 (35 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1295105/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1280300] Re: Desktop contents displayed on resume, before lock screen is shown
** Tags added: rls-t-incoming -- 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/1280300 Title: Desktop contents displayed on resume, before lock screen is shown Status in “gnome-screensaver” package in Ubuntu: Confirmed Bug description: I am running 14.04. When I resume from sleep, the contents of my desktop (including any open windows, emails, etc) are displayed onscreen briefly before the unlock screen is shown. This potentially allows an attacker to view the contents of a locked screen. To reproduce: 1) Suspend a machine, e.g. by closing the lid 2) Resume the machine Expected results: Upon resume, the first thing shown onscreen is the screensaver unlock screen. Actual results: Upon resume, the first thing shown onscreen is the set of open windows that were displayed before the machine was put to sleep. After a second or two, the unlock screen is drawn and you have to enter a password to unlock the machine. This is reproducible on my system. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-screensaver 3.6.1-0ubuntu9 ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 14 09:05:50 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'ubuntu' org.gnome.desktop.session idle-delay uint32 300 InstallationDate: Installed on 2013-12-02 (73 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 SourcePackage: gnome-screensaver UpgradeStatus: Upgraded to trusty on 2014-02-12 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1280300/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1287341] Re: Touchscreen controls both screens in dual-monitor setup
** Tags added: rls-t-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1287341 Title: Touchscreen controls both screens in dual-monitor setup Status in Gnome Settings Daemon: New Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “unity-settings-daemon” package in Ubuntu: Triaged Bug description: My laptop has a touchscreen. It works fine in 14.04 until I plug in an external monitor. When using an external monitor, input from the touchscreen is remapped so that the touchscreen provides input to both monitors. The result is that there is no longer a 1:1 correspondence between moving your finger and the cursor. This is confusing and difficult to use. A touchscreen is a direct input device (vs an indirect one like a mouse/touchpad); input from the touchscreen should be bound to the physical display that it's attached to. To reproduce: 1) On a computer with a touchscreen, use the touchscreen to move a window around, including to the edges of the screen. Note that the window moves exactly with your finger. 2) Plug in an external monitor 3) Try the same actions as in step 1 Expected results: The touchscreen continues to operate as in step 1, allowing you to manipulate items on the display that contains the touchscreen. The touchscreen does not interact with windows, etc on the external monitor Actual results: The touchscreen is remapped across both displays. The result is that touch events no longer happen 'under the finger'. Assuming the two displays are the same size and resolution, moving your finger 1cm will cause the window or other objects to move 2cm onscreen. It becomes impossible to use the touchscreen to interact with widgets (menus, buttons, etc). This is described in couple places: http://askubuntu.com/questions/51445/how-do-i-calibrate-a-touchscreen-on-a-dual-monitor-system http://askubuntu.com/questions/71768/touchscreen-and-additional-external-monitor ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xinput 1.6.1-1 ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5 Uname: Linux 3.13.0-14-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: [core,commands,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 CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Mar 3 14:41:14 2014 DistUpgraded: 2014-02-12 13:40:42,704 DEBUG enabling apt cron job DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: oem-audio-hda-daily-lts-quantal, 0.201308192259~precise1, 3.5.0-45-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-12-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-14-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-8-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:060a] InstallationDate: Installed on 2013-12-02 (90 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 MachineType: Dell Inc. XPS13 9333 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-14-generic root=UUID=0b9db31c-747b-40ad-bbbd-13a9a29caece ro quiet splash vt.handoff=7 SourcePackage: xinput UpgradeStatus: Upgraded to trusty on 2014-02-12 (19 days ago) dmi.bios.date: 11/11/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 0GFTRT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA01:bd11/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc1-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc1-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
[Desktop-packages] [Bug 1287341] Re: Touchscreen controls both screens in dual-monitor setup
** Also affects: oem-priority Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1287341 Title: Touchscreen controls both screens in dual-monitor setup Status in Gnome Settings Daemon: New Status in OEM Priority Project: New Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “unity-settings-daemon” package in Ubuntu: Triaged Bug description: My laptop has a touchscreen. It works fine in 14.04 until I plug in an external monitor. When using an external monitor, input from the touchscreen is remapped so that the touchscreen provides input to both monitors. The result is that there is no longer a 1:1 correspondence between moving your finger and the cursor. This is confusing and difficult to use. A touchscreen is a direct input device (vs an indirect one like a mouse/touchpad); input from the touchscreen should be bound to the physical display that it's attached to. To reproduce: 1) On a computer with a touchscreen, use the touchscreen to move a window around, including to the edges of the screen. Note that the window moves exactly with your finger. 2) Plug in an external monitor 3) Try the same actions as in step 1 Expected results: The touchscreen continues to operate as in step 1, allowing you to manipulate items on the display that contains the touchscreen. The touchscreen does not interact with windows, etc on the external monitor Actual results: The touchscreen is remapped across both displays. The result is that touch events no longer happen 'under the finger'. Assuming the two displays are the same size and resolution, moving your finger 1cm will cause the window or other objects to move 2cm onscreen. It becomes impossible to use the touchscreen to interact with widgets (menus, buttons, etc). This is described in couple places: http://askubuntu.com/questions/51445/how-do-i-calibrate-a-touchscreen-on-a-dual-monitor-system http://askubuntu.com/questions/71768/touchscreen-and-additional-external-monitor ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xinput 1.6.1-1 ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5 Uname: Linux 3.13.0-14-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: [core,commands,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 CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Mar 3 14:41:14 2014 DistUpgraded: 2014-02-12 13:40:42,704 DEBUG enabling apt cron job DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: oem-audio-hda-daily-lts-quantal, 0.201308192259~precise1, 3.5.0-45-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-12-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-14-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-8-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:060a] InstallationDate: Installed on 2013-12-02 (90 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 MachineType: Dell Inc. XPS13 9333 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-14-generic root=UUID=0b9db31c-747b-40ad-bbbd-13a9a29caece ro quiet splash vt.handoff=7 SourcePackage: xinput UpgradeStatus: Upgraded to trusty on 2014-02-12 (19 days ago) dmi.bios.date: 11/11/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 0GFTRT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA01:bd11/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc1-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc1-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev
[Desktop-packages] [Bug 1287341] Re: Touchscreen controls both screens in dual-monitor setup
** Also affects: oem-priority/trusty Importance: Undecided Status: New ** Changed in: oem-priority/trusty Importance: Undecided = High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1287341 Title: Touchscreen controls both screens in dual-monitor setup Status in Gnome Settings Daemon: New Status in OEM Priority Project: New Status in OEM Priority Project trusty series: New Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “unity-settings-daemon” package in Ubuntu: Triaged Bug description: My laptop has a touchscreen. It works fine in 14.04 until I plug in an external monitor. When using an external monitor, input from the touchscreen is remapped so that the touchscreen provides input to both monitors. The result is that there is no longer a 1:1 correspondence between moving your finger and the cursor. This is confusing and difficult to use. A touchscreen is a direct input device (vs an indirect one like a mouse/touchpad); input from the touchscreen should be bound to the physical display that it's attached to. To reproduce: 1) On a computer with a touchscreen, use the touchscreen to move a window around, including to the edges of the screen. Note that the window moves exactly with your finger. 2) Plug in an external monitor 3) Try the same actions as in step 1 Expected results: The touchscreen continues to operate as in step 1, allowing you to manipulate items on the display that contains the touchscreen. The touchscreen does not interact with windows, etc on the external monitor Actual results: The touchscreen is remapped across both displays. The result is that touch events no longer happen 'under the finger'. Assuming the two displays are the same size and resolution, moving your finger 1cm will cause the window or other objects to move 2cm onscreen. It becomes impossible to use the touchscreen to interact with widgets (menus, buttons, etc). This is described in couple places: http://askubuntu.com/questions/51445/how-do-i-calibrate-a-touchscreen-on-a-dual-monitor-system http://askubuntu.com/questions/71768/touchscreen-and-additional-external-monitor ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xinput 1.6.1-1 ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5 Uname: Linux 3.13.0-14-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: [core,commands,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 CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Mar 3 14:41:14 2014 DistUpgraded: 2014-02-12 13:40:42,704 DEBUG enabling apt cron job DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: oem-audio-hda-daily-lts-quantal, 0.201308192259~precise1, 3.5.0-45-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-12-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-14-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-8-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:060a] InstallationDate: Installed on 2013-12-02 (90 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 MachineType: Dell Inc. XPS13 9333 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-14-generic root=UUID=0b9db31c-747b-40ad-bbbd-13a9a29caece ro quiet splash vt.handoff=7 SourcePackage: xinput UpgradeStatus: Upgraded to trusty on 2014-02-12 (19 days ago) dmi.bios.date: 11/11/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 0GFTRT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA01:bd11/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc1-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc1-1ubuntu4
[Desktop-packages] [Bug 1295105] Re: Wrong background color in Back Up window
** Description changed: The background colors in the Back Up window are wrong. I think window is supposed to be light grey, but it's black. There is dark gray text on the black background, which is impossible to read. See attached screenshot. + + Steps to reproduce: + 1) Ensure the backup app is configured to make backups + 2) Launch the backup app. The background will be grey (normal) + 3) Click the 'Details' twisty + + Expected results: + The Details pane is shown. The background of the app does not change + + Actual results: + The Details pane is shown. The background of the app becomes black. It stays black if you close the Details pane. + + This is 100% reproducible on my system. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: deja-dup 29.5-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 20 08:42:13 2014 DistributionChannelDescriptor: - # This is a distribution channel descriptor - # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor - canonical-oem-somerville-precise-amd64-20130203-1 + # This is a distribution channel descriptor + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-02 (107 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 SourcePackage: deja-dup UpgradeStatus: Upgraded to trusty on 2014-02-12 (35 days ago) ** Also affects: oem-priority Importance: Undecided Status: New ** Also affects: oem-priority/trusty Importance: Undecided Status: New ** Changed in: oem-priority/trusty Importance: Undecided = Medium -- 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/1295105 Title: Wrong background color in Back Up window Status in OEM Priority Project: New Status in OEM Priority Project trusty series: New Status in “deja-dup” package in Ubuntu: Confirmed Bug description: The background colors in the Back Up window are wrong. I think window is supposed to be light grey, but it's black. There is dark gray text on the black background, which is impossible to read. See attached screenshot. Steps to reproduce: 1) Ensure the backup app is configured to make backups 2) Launch the backup app. The background will be grey (normal) 3) Click the 'Details' twisty Expected results: The Details pane is shown. The background of the app does not change Actual results: The Details pane is shown. The background of the app becomes black. It stays black if you close the Details pane. This is 100% reproducible on my system. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: deja-dup 29.5-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 20 08:42:13 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-02 (107 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 SourcePackage: deja-dup UpgradeStatus: Upgraded to trusty on 2014-02-12 (35 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1295105/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1297566] [NEW] Dialpad does not accept touchscreen input
Public bug reported: I am using empathy to make VOIP calls to a conference call system. I am trying to use my touchscreen to enter numbers in the dialpad, but that does not work. Using the mouse to enter numbers in the dialpad works just fine. To reproduce: 1) Start a new VOIP call (Ctrl-M); make a call (I am dialed into a conference line) 2) In the call window, click the dialpad button to show the dialpad 3) Use the touchscreen to enter numbers in the dialpad Expected results: Using the touchscreen to enter numbers in the dialpad works: pressing a number on the dialpad results in the number being displayed in the small text field above the dialpad Actual results: Using the touchscreen to enter numbers in the dialpad does not work. The dialpad buttons depress as if the button was being pressed, but the numbers are not entered in the small text field above the dialpad Using the mouse to click buttons in the dialpad works just fine for me. The touchscreen itself is working fine on this machine. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: empathy 3.8.6-0ubuntu7 ProcVersionSignature: Ubuntu 3.13.0-19.39-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 25 20:58:36 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-02 (113 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 SourcePackage: empathy UpgradeStatus: Upgraded to trusty on 2014-02-12 (41 days ago) ** Affects: empathy (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/1297566 Title: Dialpad does not accept touchscreen input Status in “empathy” package in Ubuntu: New Bug description: I am using empathy to make VOIP calls to a conference call system. I am trying to use my touchscreen to enter numbers in the dialpad, but that does not work. Using the mouse to enter numbers in the dialpad works just fine. To reproduce: 1) Start a new VOIP call (Ctrl-M); make a call (I am dialed into a conference line) 2) In the call window, click the dialpad button to show the dialpad 3) Use the touchscreen to enter numbers in the dialpad Expected results: Using the touchscreen to enter numbers in the dialpad works: pressing a number on the dialpad results in the number being displayed in the small text field above the dialpad Actual results: Using the touchscreen to enter numbers in the dialpad does not work. The dialpad buttons depress as if the button was being pressed, but the numbers are not entered in the small text field above the dialpad Using the mouse to click buttons in the dialpad works just fine for me. The touchscreen itself is working fine on this machine. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: empathy 3.8.6-0ubuntu7 ProcVersionSignature: Ubuntu 3.13.0-19.39-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 25 20:58:36 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-02 (113 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 SourcePackage: empathy UpgradeStatus: Upgraded to trusty on 2014-02-12 (41 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1297566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1296966] [NEW] Displays: Can't modify UI scale slide with keyboard
Public bug reported: It should be possible to modify the UI Scale slider using the keyboard. To reproduce: 1) Launch the Displays control panel 2) Click the thumb/handle in the UI scale slider once, to select it. Notice that the handle gets an orange border, to indicate that it's selected 3) Press the left/right arrow keys to modify the UI scale Expected results: The UI scale slider responds to the arrow keys Actual results: Nothing happens when you use the keyboard to manipulate the UI scale slider This is an accessibility issue. It's also a problem if you set the UI scale so big that the UI scale widget is no longer drawn onscreen - you can't use keyboard navigation to reset it. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.3+14.04.20140319-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-19.39-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 24 17:40:33 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-02 (111 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 SourcePackage: unity-control-center UpgradeStatus: Upgraded to trusty on 2014-02-12 (40 days ago) usr_lib_unity-control-center: activity-log-manager 0.9.7-0ubuntu10 deja-dup 29.5-0ubuntu2 gnome-control-center 1:3.6.3-0ubuntu54 ** Affects: unity-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1296966 Title: Displays: Can't modify UI scale slide with keyboard Status in “unity-control-center” package in Ubuntu: New Bug description: It should be possible to modify the UI Scale slider using the keyboard. To reproduce: 1) Launch the Displays control panel 2) Click the thumb/handle in the UI scale slider once, to select it. Notice that the handle gets an orange border, to indicate that it's selected 3) Press the left/right arrow keys to modify the UI scale Expected results: The UI scale slider responds to the arrow keys Actual results: Nothing happens when you use the keyboard to manipulate the UI scale slider This is an accessibility issue. It's also a problem if you set the UI scale so big that the UI scale widget is no longer drawn onscreen - you can't use keyboard navigation to reset it. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.3+14.04.20140319-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-19.39-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 24 17:40:33 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-02 (111 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 SourcePackage: unity-control-center UpgradeStatus: Upgraded to trusty on 2014-02-12 (40 days ago) usr_lib_unity-control-center: activity-log-manager 0.9.7-0ubuntu10 deja-dup 29.5-0ubuntu2 gnome-control-center 1:3.6.3-0ubuntu54 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1296966/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1295105] [NEW] Wrong background color in Back Up window
Public bug reported: The background colors in the Back Up window are wrong. I think window is supposed to be light grey, but it's black. There is dark gray text on the black background, which is impossible to read. See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: deja-dup 29.5-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 20 08:42:13 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-02 (107 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 SourcePackage: deja-dup UpgradeStatus: Upgraded to trusty on 2014-02-12 (35 days ago) ** Affects: deja-dup (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty ** Attachment added: Screenshot from 2014-03-20 08:42:05.png https://bugs.launchpad.net/bugs/1295105/+attachment/4033775/+files/Screenshot%20from%202014-03-20%2008%3A42%3A05.png -- 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/1295105 Title: Wrong background color in Back Up window Status in “deja-dup” package in Ubuntu: New Bug description: The background colors in the Back Up window are wrong. I think window is supposed to be light grey, but it's black. There is dark gray text on the black background, which is impossible to read. See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: deja-dup 29.5-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 20 08:42:13 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-02 (107 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 SourcePackage: deja-dup UpgradeStatus: Upgraded to trusty on 2014-02-12 (35 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1295105/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1287341] Re: Touchscreen controls both screens in dual-monitor setup
@Maarten: I did not try 13.10, but I did try in 12.04. It was broken in 12.04 too. -- 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/1287341 Title: Touchscreen controls both screens in dual-monitor setup Status in Gnome Settings Daemon: New Status in “gnome-settings-daemon” package in Ubuntu: Incomplete Bug description: My laptop has a touchscreen. It works fine in 14.04 until I plug in an external monitor. When using an external monitor, input from the touchscreen is remapped so that the touchscreen provides input to both monitors. The result is that there is no longer a 1:1 correspondence between moving your finger and the cursor. This is confusing and difficult to use. A touchscreen is a direct input device (vs an indirect one like a mouse/touchpad); input from the touchscreen should be bound to the physical display that it's attached to. To reproduce: 1) On a computer with a touchscreen, use the touchscreen to move a window around, including to the edges of the screen. Note that the window moves exactly with your finger. 2) Plug in an external monitor 3) Try the same actions as in step 1 Expected results: The touchscreen continues to operate as in step 1, allowing you to manipulate items on the display that contains the touchscreen. The touchscreen does not interact with windows, etc on the external monitor Actual results: The touchscreen is remapped across both displays. The result is that touch events no longer happen 'under the finger'. Assuming the two displays are the same size and resolution, moving your finger 1cm will cause the window or other objects to move 2cm onscreen. It becomes impossible to use the touchscreen to interact with widgets (menus, buttons, etc). This is described in couple places: http://askubuntu.com/questions/51445/how-do-i-calibrate-a-touchscreen-on-a-dual-monitor-system http://askubuntu.com/questions/71768/touchscreen-and-additional-external-monitor ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xinput 1.6.1-1 ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5 Uname: Linux 3.13.0-14-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: [core,commands,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 CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Mar 3 14:41:14 2014 DistUpgraded: 2014-02-12 13:40:42,704 DEBUG enabling apt cron job DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: oem-audio-hda-daily-lts-quantal, 0.201308192259~precise1, 3.5.0-45-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-12-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-14-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-8-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:060a] InstallationDate: Installed on 2013-12-02 (90 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 MachineType: Dell Inc. XPS13 9333 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-14-generic root=UUID=0b9db31c-747b-40ad-bbbd-13a9a29caece ro quiet splash vt.handoff=7 SourcePackage: xinput UpgradeStatus: Upgraded to trusty on 2014-02-12 (19 days ago) dmi.bios.date: 11/11/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 0GFTRT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA01:bd11/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc1-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc1-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
[Desktop-packages] [Bug 1290108] [NEW] Exception upgrading ubuntu-drivers-common
Public bug reported: I got the following exception from a dist-upgrade of ubuntu-drivers- common: Unpacking ubuntu-drivers-common (1:0.2.89.6) over (1:0.2.89.5) ... [...] Setting up ubuntu-drivers-common (1:0.2.89.6) ... Exception ignored in: bound method Popen.__del__ of subprocess.Popen object at 0x7f392445d080 Traceback (most recent call last): File /usr/lib/python3.4/subprocess.py, line 897, in __del__ TypeError: 'NoneType' object is not callable Despite that, apt reports the installation completed successfully. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubuntu-drivers-common 1:0.2.89.6 ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5 Uname: Linux 3.13.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Mar 9 16:00:20 2014 InstallationDate: Installed on 2010-09-17 (1269 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1) SourcePackage: ubuntu-drivers-common UpgradeStatus: Upgraded to trusty on 2013-12-13 (86 days ago) ** Affects: ubuntu-drivers-common (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 ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1290108 Title: Exception upgrading ubuntu-drivers-common Status in “ubuntu-drivers-common” package in Ubuntu: New Bug description: I got the following exception from a dist-upgrade of ubuntu-drivers- common: Unpacking ubuntu-drivers-common (1:0.2.89.6) over (1:0.2.89.5) ... [...] Setting up ubuntu-drivers-common (1:0.2.89.6) ... Exception ignored in: bound method Popen.__del__ of subprocess.Popen object at 0x7f392445d080 Traceback (most recent call last): File /usr/lib/python3.4/subprocess.py, line 897, in __del__ TypeError: 'NoneType' object is not callable Despite that, apt reports the installation completed successfully. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubuntu-drivers-common 1:0.2.89.6 ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5 Uname: Linux 3.13.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Mar 9 16:00:20 2014 InstallationDate: Installed on 2010-09-17 (1269 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1) SourcePackage: ubuntu-drivers-common UpgradeStatus: Upgraded to trusty on 2013-12-13 (86 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1290108/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1288789] [NEW] Super-W sometimes opens the dash instead of showing all windows
Public bug reported: The Super-W keystroke sometimes opens the dash instead of showing all windows. The behavior seems to depend on how long you hold down the super key. Tapping + releasing both the super key and w key will open the dash. Holding down the super key for more than about 0.5sec will open the spread, no matter how long you hold down the w key. Oddly I can't reproduce the problem with other super- keystrokes such as Super-S or Super-T. It only happens with Super-W. A quick tap of Super-S will reliably open expo mode. To reproduce: 1) Quickly tap Super-W Expected results: The spread opens Actual results: The dash opens I can reproduce this on multiple keyboards from different manufacturers, so I don't think it's anything unique to the keyboard itself. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140303-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-15.35-generic 3.13.5 Uname: Linux 3.13.0-15-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CurrentDesktop: Unity Date: Thu Mar 6 09:54:47 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-02 (93 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-02-12 (21 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty -- 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/1288789 Title: Super-W sometimes opens the dash instead of showing all windows Status in “unity” package in Ubuntu: New Bug description: The Super-W keystroke sometimes opens the dash instead of showing all windows. The behavior seems to depend on how long you hold down the super key. Tapping + releasing both the super key and w key will open the dash. Holding down the super key for more than about 0.5sec will open the spread, no matter how long you hold down the w key. Oddly I can't reproduce the problem with other super- keystrokes such as Super-S or Super-T. It only happens with Super-W. A quick tap of Super-S will reliably open expo mode. To reproduce: 1) Quickly tap Super-W Expected results: The spread opens Actual results: The dash opens I can reproduce this on multiple keyboards from different manufacturers, so I don't think it's anything unique to the keyboard itself. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140303-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-15.35-generic 3.13.5 Uname: Linux 3.13.0-15-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CurrentDesktop: Unity Date: Thu Mar 6 09:54:47 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-02 (93 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-02-12 (21 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1288789/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1288855] [NEW] Shrinking windows - each new window is smaller than the previous one
Public bug reported: Each time I open a nautilus window, the window is smaller than the previous window I opened. The windows shrink only in the vertical dimension. The first window might be 400px high. The next window might be 380px high. The next one is 360px high. And so on. To reproduce: 1) Open a window in nautilus. Observe the size. 2) Close the window 3) Open a new window Expected results: The window from step 3 is the same size as the one in step 1 Actual results: The window from step 3 is not as tall as the one in step 1 This is 100% reproducible on my system. It's a recent regression in 14.04. I suspect it's related to recent changes to give the option of in-window menus for this app (I have not enabled the in-window menus, I am still using global menus). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nautilus 1:3.10.1-0ubuntu7 ProcVersionSignature: Ubuntu 3.13.0-15.35-generic 3.13.5 Uname: Linux 3.13.0-15-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 6 11:33:40 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes GsettingsChanges: InstallationDate: Installed on 2013-12-02 (93 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 SourcePackage: nautilus UpgradeStatus: Upgraded to trusty on 2014-02-12 (21 days ago) ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty -- 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/1288855 Title: Shrinking windows - each new window is smaller than the previous one Status in “nautilus” package in Ubuntu: New Bug description: Each time I open a nautilus window, the window is smaller than the previous window I opened. The windows shrink only in the vertical dimension. The first window might be 400px high. The next window might be 380px high. The next one is 360px high. And so on. To reproduce: 1) Open a window in nautilus. Observe the size. 2) Close the window 3) Open a new window Expected results: The window from step 3 is the same size as the one in step 1 Actual results: The window from step 3 is not as tall as the one in step 1 This is 100% reproducible on my system. It's a recent regression in 14.04. I suspect it's related to recent changes to give the option of in-window menus for this app (I have not enabled the in-window menus, I am still using global menus). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nautilus 1:3.10.1-0ubuntu7 ProcVersionSignature: Ubuntu 3.13.0-15.35-generic 3.13.5 Uname: Linux 3.13.0-15-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 6 11:33:40 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes GsettingsChanges: InstallationDate: Installed on 2013-12-02 (93 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 SourcePackage: nautilus UpgradeStatus: Upgraded to trusty on 2014-02-12 (21 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1288855/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1288855] Re: Shrinking windows - each new window is smaller than the previous one
*** This bug is a duplicate of bug 1287472 *** https://bugs.launchpad.net/bugs/1287472 Per seb128, this is a compiz issue ** This bug has been marked a duplicate of bug 1287472 compiz unnecessarily shrinks new windows -- 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/1288855 Title: Shrinking windows - each new window is smaller than the previous one Status in “nautilus” package in Ubuntu: Invalid Bug description: Each time I open a nautilus window, the window is smaller than the previous window I opened. The windows shrink only in the vertical dimension. The first window might be 400px high. The next window might be 380px high. The next one is 360px high. And so on. To reproduce: 1) Open a window in nautilus. Observe the size. 2) Close the window 3) Open a new window Expected results: The window from step 3 is the same size as the one in step 1 Actual results: The window from step 3 is not as tall as the one in step 1 This is 100% reproducible on my system. It's a recent regression in 14.04. I suspect it's related to recent changes to give the option of in-window menus for this app (I have not enabled the in-window menus, I am still using global menus). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nautilus 1:3.10.1-0ubuntu7 ProcVersionSignature: Ubuntu 3.13.0-15.35-generic 3.13.5 Uname: Linux 3.13.0-15-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 6 11:33:40 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes GsettingsChanges: InstallationDate: Installed on 2013-12-02 (93 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 SourcePackage: nautilus UpgradeStatus: Upgraded to trusty on 2014-02-12 (21 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1288855/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1284395] Re: conf file prompt on trusty package upgrade
@Till: I don't have printer sharing enabled, but I am using some network printers. See attached screenshot for my printer settings ** Attachment added: Screenshot showing printer settings https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1284395/+attachment/4006660/+files/Screenshot%20from%202014-03-04%2009%3A07%3A44.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1284395 Title: conf file prompt on trusty package upgrade Status in “cups” package in Ubuntu: Incomplete Bug description: I am running trusty. When I upgraded to cups 1.7.1-5ubuntu3, I got a conffile prompt. I don't believe I've manually modified any cups- related conf files, so I didn't expect a prompt - I expected the package upgrade to handle this for me without a prompt. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: cups 1.7.1-5ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Mon Feb 24 20:01:48 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-02 (84 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 MachineType: Dell Inc. XPS13 9333 Papersize: letter PpdFiles: Xerox-WorkCentre-7345: Xerox WorkCentre 7345 Foomatic/pxlcolor (recommended) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-8-generic root=UUID=0b9db31c-747b-40ad-bbbd-13a9a29caece ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to trusty on 2014-02-12 (12 days ago) dmi.bios.date: 11/11/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 0GFTRT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA01:bd11/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.cups.cupsd.conf: 2014-02-12T13:36:32.106432 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1284395/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1287341] [NEW] Touchscreen controls both screens in dual-monitor setup
Public bug reported: My laptop has a touchscreen. It works fine in 14.04 until I plug in an external monitor. When using an external monitor, input from the touchscreen is remapped so that the touchscreen provides input to both monitors. The result is that there is no longer a 1:1 correspondence between moving your finger and the cursor. This is confusing and difficult to use. A touchscreen is a direct input device (vs an indirect one like a mouse/touchpad); input from the touchscreen should be bound to the physical display that it's attached to. To reproduce: 1) On a computer with a touchscreen, use the touchscreen to move a window around, including to the edges of the screen. Note that the window moves exactly with your finger. 2) Plug in an external monitor 3) Try the same actions as in step 1 Expected results: The touchscreen continues to operate as in step 1, allowing you to manipulate items on the display that contains the touchscreen. The touchscreen does not interact with windows, etc on the external monitor Actual results: The touchscreen is remapped across both displays. The result is that touch events no longer happen 'under the finger'. Assuming the two displays are the same size and resolution, moving your finger 1cm will cause the window or other objects to move 2cm onscreen. It becomes impossible to use the touchscreen to interact with widgets (menus, buttons, etc). This is described in couple places: http://askubuntu.com/questions/51445/how-do-i-calibrate-a-touchscreen-on-a-dual-monitor-system http://askubuntu.com/questions/71768/touchscreen-and-additional-external-monitor ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xinput 1.6.1-1 ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5 Uname: Linux 3.13.0-14-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: [core,commands,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 CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Mar 3 14:41:14 2014 DistUpgraded: 2014-02-12 13:40:42,704 DEBUG enabling apt cron job DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: oem-audio-hda-daily-lts-quantal, 0.201308192259~precise1, 3.5.0-45-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-12-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-14-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-8-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:060a] InstallationDate: Installed on 2013-12-02 (90 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 MachineType: Dell Inc. XPS13 9333 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-14-generic root=UUID=0b9db31c-747b-40ad-bbbd-13a9a29caece ro quiet splash vt.handoff=7 SourcePackage: xinput UpgradeStatus: Upgraded to trusty on 2014-02-12 (19 days ago) dmi.bios.date: 11/11/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 0GFTRT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA01:bd11/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~rc1-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0~rc1-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon Mar 3 11:02:50 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4933 vendor CMN xserver.version: 2:1.15.0-1ubuntu6 ** Affects: xinput (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu -- You received this bug notification
[Desktop-packages] [Bug 1279913] Re: xrandr missing after upgrade to trusty
*** This bug is a duplicate of bug 1280155 *** https://bugs.launchpad.net/bugs/1280155 ** This bug has been marked a duplicate of bug 1280155 test for /usr/bin/xrandr when upgrading from lts -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-lts-transitional in Ubuntu. https://bugs.launchpad.net/bugs/1279913 Title: xrandr missing after upgrade to trusty Status in “xorg-lts-transitional” package in Ubuntu: New Bug description: I have an XPS 13 that shipped with Ubuntu 12.04.2 and the quantal LTS stack. When I upgraded to 14.04, the xrandr binary went missing. steve@aether:~$ ls /usr/bin/xrandr* /usr/bin/xrandr.orig /usr/bin/xrandr-tool steve@aether:~$ dpkg -S /usr/bin/xrandr.orig diversion by x11-xserver-utils-lts-quantal from: /usr/bin/xrandr diversion by x11-xserver-utils-lts-quantal to: /usr/bin/xrandr.orig I have x11-xserver-utils installed, but not x11-xserver-utils-lts- quantal. I think x11-xsever-utils-lts-quantal was removed during the upgrade to 14.04 but it seems the diversion was never removed (is it missing from the postrm?). /var/log/dpkg.log snippet from the upgrade to 14.04: 2014-02-12 13:40:12 status installed x11-xserver-utils-lts-quantal:amd64 3:3 2014-02-12 13:40:12 remove x11-xserver-utils-lts-quantal:amd64 3:3 none 2014-02-12 13:40:12 status half-configured x11-xserver-utils-lts-quantal:amd64 3:3 2014-02-12 13:40:12 status half-installed x11-xserver-utils-lts-quantal:amd64 3:3 2014-02-12 13:40:12 status config-files x11-xserver-utils-lts-quantal:amd64 3:3 2014-02-12 13:40:12 status config-files x11-xserver-utils-lts-quantal:amd64 3:3 2014-02-12 13:40:12 status config-files x11-xserver-utils-lts-quantal:amd64 3:3 2014-02-12 13:40:12 status not-installed x11-xserver-utils-lts-quantal:amd64 none To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-lts-transitional/+bug/1279913/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1284395] Re: conf file prompt on trusty package upgrade
@Till: I have used a printer setup tool to set up a printer I assert that setting up a printer should not cause the user to be promoted about conf file changes during an upgrade. This is a normal case, and users should not be required to understand/analyze conf files in order to use a printer. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1284395 Title: conf file prompt on trusty package upgrade Status in “cups” package in Ubuntu: Incomplete Bug description: I am running trusty. When I upgraded to cups 1.7.1-5ubuntu3, I got a conffile prompt. I don't believe I've manually modified any cups- related conf files, so I didn't expect a prompt - I expected the package upgrade to handle this for me without a prompt. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: cups 1.7.1-5ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Mon Feb 24 20:01:48 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-02 (84 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 MachineType: Dell Inc. XPS13 9333 Papersize: letter PpdFiles: Xerox-WorkCentre-7345: Xerox WorkCentre 7345 Foomatic/pxlcolor (recommended) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-8-generic root=UUID=0b9db31c-747b-40ad-bbbd-13a9a29caece ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to trusty on 2014-02-12 (12 days ago) dmi.bios.date: 11/11/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 0GFTRT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA01:bd11/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.cups.cupsd.conf: 2014-02-12T13:36:32.106432 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1284395/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1284395] [NEW] conf file prompt on trusty package upgrade
Public bug reported: I am running trusty. When I upgraded to cups 1.7.1-5ubuntu3, I got a conffile prompt. I don't believe I've manually modified any cups-related conf files, so I didn't expect a prompt - I expected the package upgrade to handle this for me without a prompt. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: cups 1.7.1-5ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Mon Feb 24 20:01:48 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-02 (84 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 MachineType: Dell Inc. XPS13 9333 Papersize: letter PpdFiles: Xerox-WorkCentre-7345: Xerox WorkCentre 7345 Foomatic/pxlcolor (recommended) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-8-generic root=UUID=0b9db31c-747b-40ad-bbbd-13a9a29caece ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to trusty on 2014-02-12 (12 days ago) dmi.bios.date: 11/11/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 0GFTRT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA01:bd11/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.cups.cupsd.conf: 2014-02-12T13:36:32.106432 ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty ** Attachment added: diff reported by update-manager dialog https://bugs.launchpad.net/bugs/1284395/+attachment/3995169/+files/cups-conf-diff.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1284395 Title: conf file prompt on trusty package upgrade Status in “cups” package in Ubuntu: New Bug description: I am running trusty. When I upgraded to cups 1.7.1-5ubuntu3, I got a conffile prompt. I don't believe I've manually modified any cups- related conf files, so I didn't expect a prompt - I expected the package upgrade to handle this for me without a prompt. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: cups 1.7.1-5ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Mon Feb 24 20:01:48 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-02 (84 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 MachineType: Dell Inc. XPS13 9333 Papersize: letter PpdFiles: Xerox-WorkCentre-7345: Xerox WorkCentre 7345 Foomatic/pxlcolor (recommended) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-8-generic root=UUID=0b9db31c-747b-40ad-bbbd-13a9a29caece ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to trusty on 2014-02-12 (12 days ago) dmi.bios.date: 11/11/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 0GFTRT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA01:bd11/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.cups.cupsd.conf: 2014-02-12T13:36:32.106432 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1284395/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1281640] [NEW] Obscene content in music search results
Public bug reported: Some search terms return obscene content in the dash To reproduce: 1) Search for 'rhy' in the dash Expected results: Rhythmbox and other search results are returned, all of which I could show to a customer Actual results: The music scope returns offensive/obscene results, such as WORDS MOTHERF*CKER or Absolute Bullsh*t (see attached screenshot) I am not aware of any way to filter search results (similar to Google's Safe Search). If there is a way, it should be turned on by default. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20131106.1-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 ApportVersion: 2.13.2-0ubuntu3 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CurrentDesktop: Unity Date: Tue Feb 18 10:50:44 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-02 (77 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-02-12 (5 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty ** Attachment added: Screenshot showing search results https://bugs.launchpad.net/bugs/1281640/+attachment/3985426/+files/Screenshot%20from%202014-02-18%2010%3A53%3A00.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/1281640 Title: Obscene content in music search results Status in “unity” package in Ubuntu: New Bug description: Some search terms return obscene content in the dash To reproduce: 1) Search for 'rhy' in the dash Expected results: Rhythmbox and other search results are returned, all of which I could show to a customer Actual results: The music scope returns offensive/obscene results, such as WORDS MOTHERF*CKER or Absolute Bullsh*t (see attached screenshot) I am not aware of any way to filter search results (similar to Google's Safe Search). If there is a way, it should be turned on by default. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20131106.1-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 ApportVersion: 2.13.2-0ubuntu3 Architecture: amd64 CompizPlugins: [core,commands,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CurrentDesktop: Unity Date: Tue Feb 18 10:50:44 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes InstallationDate: Installed on 2013-12-02 (77 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-02-12 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1281640/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1280300] [NEW] Desktop contents displayed on resume, before lock screen is shown
Public bug reported: I am running 14.04. When I resume from sleep, the contents of my desktop (including any open windows, emails, etc) are displayed onscreen briefly before the unlock screen is shown. This potentially allows an attacker to view the contents of a locked screen. To reproduce: 1) Suspend a machine, e.g. by closing the lid 2) Resume the machine Expected results: Upon resume, the first thing shown onscreen is the screensaver unlock screen. Actual results: Upon resume, the first thing shown onscreen is the set of open windows that were displayed before the machine was put to sleep. After a second or two, the unlock screen is drawn and you have to enter a password to unlock the machine. This is reproducible on my system. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-screensaver 3.6.1-0ubuntu9 ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 14 09:05:50 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'ubuntu' org.gnome.desktop.session idle-delay uint32 300 InstallationDate: Installed on 2013-12-02 (73 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 SourcePackage: gnome-screensaver UpgradeStatus: Upgraded to trusty on 2014-02-12 (1 days ago) ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty -- 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/1280300 Title: Desktop contents displayed on resume, before lock screen is shown Status in “gnome-screensaver” package in Ubuntu: New Bug description: I am running 14.04. When I resume from sleep, the contents of my desktop (including any open windows, emails, etc) are displayed onscreen briefly before the unlock screen is shown. This potentially allows an attacker to view the contents of a locked screen. To reproduce: 1) Suspend a machine, e.g. by closing the lid 2) Resume the machine Expected results: Upon resume, the first thing shown onscreen is the screensaver unlock screen. Actual results: Upon resume, the first thing shown onscreen is the set of open windows that were displayed before the machine was put to sleep. After a second or two, the unlock screen is drawn and you have to enter a password to unlock the machine. This is reproducible on my system. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-screensaver 3.6.1-0ubuntu9 ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 14 09:05:50 2014 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 EcryptfsInUse: Yes GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'ubuntu' org.gnome.desktop.session idle-delay uint32 300 InstallationDate: Installed on 2013-12-02 (73 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20130203-13:50 SourcePackage: gnome-screensaver UpgradeStatus: Upgraded to trusty on 2014-02-12 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1280300/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1276833] [NEW] indicator icon invisible using radiance theme
Public bug reported: I use the radiance theme. A recent update to indicator-keyboard changed the icon so it is now effectively invisible on the panel. To reproduce: 1) Boot with the radiance theme, look at the panel Expected results: I can see the keyboard indicator icon in the panel Actual results: There is an empty space in the panel where the keyboard indicator is. If I look closely I can see a faint outline of the icon. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-keyboard 0.0.0+14.04.20131125-0ubuntu1 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 CurrentDesktop: Unity Date: Wed Feb 5 16:47:50 2014 InstallationDate: Installed on 2010-09-17 (1237 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1) SourcePackage: indicator-keyboard UpgradeStatus: Upgraded to trusty on 2013-12-13 (54 days ago) ** Affects: indicator-keyboard (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 indicator-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1276833 Title: indicator icon invisible using radiance theme Status in “indicator-keyboard” package in Ubuntu: New Bug description: I use the radiance theme. A recent update to indicator-keyboard changed the icon so it is now effectively invisible on the panel. To reproduce: 1) Boot with the radiance theme, look at the panel Expected results: I can see the keyboard indicator icon in the panel Actual results: There is an empty space in the panel where the keyboard indicator is. If I look closely I can see a faint outline of the icon. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: indicator-keyboard 0.0.0+14.04.20131125-0ubuntu1 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 CurrentDesktop: Unity Date: Wed Feb 5 16:47:50 2014 InstallationDate: Installed on 2010-09-17 (1237 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1) SourcePackage: indicator-keyboard UpgradeStatus: Upgraded to trusty on 2013-12-13 (54 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-keyboard/+bug/1276833/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1274241] [NEW] Typo in libpciaccess debian/control
Public bug reported: The libpciaccess debian/control file spells 'independent' incorrectly in 2 places: Description: Generic PCI access library for X Provides functionality for X to access the PCI bus and devices in a platform-independant way. and Description: Generic PCI access library for X - development files Provides functionality for X to access the PCI bus and devices in a platform-independant way. . This package contains the development files for libpciaccess. The fix is to s/independant/independent/g . Reproducible in libpaciaccess 0.13.2-1 ** Affects: libpciaccess (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libpciaccess in Ubuntu. https://bugs.launchpad.net/bugs/1274241 Title: Typo in libpciaccess debian/control Status in “libpciaccess” package in Ubuntu: New Bug description: The libpciaccess debian/control file spells 'independent' incorrectly in 2 places: Description: Generic PCI access library for X Provides functionality for X to access the PCI bus and devices in a platform-independant way. and Description: Generic PCI access library for X - development files Provides functionality for X to access the PCI bus and devices in a platform-independant way. . This package contains the development files for libpciaccess. The fix is to s/independant/independent/g . Reproducible in libpaciaccess 0.13.2-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libpciaccess/+bug/1274241/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 912702] Re: [MASTER] Endlessly many Wireless Network Authentication Required dialogs put up
I've been running the test package (network-manager 0.9.8.4-0ubuntu4~mtrudel1) from comment #38 for about a week. So far I have not seen a single authentication failed dialog. Normally I'd see at least 10 of the dialogs during this time period, if not many more. I have not noticed any bad side effects of the test package. -- 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/912702 Title: [MASTER] Endlessly many Wireless Network Authentication Required dialogs put up Status in One Hundred Papercuts: Fix Released Status in The Linux Mint Distribution: New Status in NetworkManager: Confirmed Status in “network-manager” package in Ubuntu: In Progress Status in “network-manager-applet” package in Ubuntu: Triaged Bug description: I left the computer turned on for the night and in the morning I found not less than 65, yes 65!! instances of the same window. my system was responding very slowly. and closing one took more than a minute, so I had to kill it manually. take a look on my screenshots, they look really weird. this is very annoying solution: this window shouldn't pop up when the previous one was not closed! ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: network-manager-gnome 0.9.1.90-0ubuntu6 ProcVersionSignature: Ubuntu 3.0.0-14.23-generic 3.0.9 Uname: Linux 3.0.0-14-generic i686 ApportVersion: 1.23-0ubuntu4 Architecture: i386 CRDA: Error: [Errno 2] No such file or directory Date: Fri Jan 6 11:38:28 2012 ExecutablePath: /usr/bin/nm-applet Gconf: IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta i386 (20110921.2) IpRoute: default via 158.195.192.1 dev eth0 proto static 158.195.192.0/19 dev eth0 proto kernel scope link src 158.195.196.69 metric 1 169.254.0.0/16 dev eth0 scope link metric 1000 Keyfiles: Error: [Errno 2] No such file or directory NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: network-manager-applet UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/912702/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 692755] Re: Corrupt graphics on resume from S4
@Christopher - I no longer have access to the hardware in the original report, sorry. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/692755 Title: Corrupt graphics on resume from S4 Status in X.org XServer - ATI gfx chipset driver: Confirmed Status in “xserver-xorg-video-ati” package in Ubuntu: Incomplete Bug description: Binary package hint: xorg I'm unable to resume from S4 on a Lenovo ThinkPad SL510 w/ ATI Mobility Radeon 4570 (1002:9553). Upon entering S4, the graphics become corrupt - it looks a bit like an X11 stipple or that checkerboard that used to be the X background (though it's not just BW, there is some R/G/B in the pattern. The pattern is not as random as static; it appears tiled, as if we're displaying tiles populated with corrupt video memory. On resume from hibernate, the BIOS logo is not corrupt and the (not- corrupted) plymouth logo flashes for an instant. There are several seconds of a flashing white cursor at the top left of the screen too. Once X comes back I see the stipple pattern/corruption again. Both the X and console sessions are corrupted. There is a separate corrupt tile surrounding the mouse cursor (the cursor itself is not visible). Moving the mouse cursor results in the mouse-tile moving around. The machine is otherwise functional - I can (blindly) login to a console on a VT and execute commands. Syslog from the failed resume session shows errors from drm:radeon, starting with: Dec 19 14:36:49 ubuntu-ThinkPad-SL510 kernel: [ 1026.671568] [drm:r600_ring_test] *ERROR* radeon: ring test failed (scratch(0x8504)=0xCAFEDEAD) Dec 19 14:36:49 ubuntu-ThinkPad-SL510 kernel: [ 1026.671570] [drm:rv770_resume] *ERROR* r600 startup failed on resume If I disable the radeon driver by adding, e.g., the made-up 'radeon.nofailboat=1' kernel parameter, the machine enters and resumes from S4 normally, with no corruption upon either entering or resuming from S4. I've reproduced in both the stock 10.10 kernel and the daily natty kernel (2.6.37-999-generic #201012200905). ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: xorg 1:7.5+6ubuntu3 Uname: Linux 2.6.37-999-generic i686 Architecture: i386 Date: Mon Dec 20 16:16:40 2010 InstallationMedia: Ubuntu 10.10 Maverick - Build i386 LIVE Binary 20101216-14:50 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xorg system: distro: Ubuntu codename: maverick architecture: i686 kernel: 2.6.37-999-generic To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-driver-ati/+bug/692755/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1059529] Re: Multiple Network Authentication Dialogs
I reproduced this in 14.04 by leaving a machine idle for 2 weeks. When I returned to it, there were (if my math is right) 3196 authentication dialogs onscreen. -- 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/1059529 Title: Multiple Network Authentication Dialogs Status in “network-manager” package in Ubuntu: Confirmed Bug description: Network Manager opens multiple windows asking network authentication. If network signal is weak, this can happen automatically as NM loses the network then finds it again, asking for authentication. This can result in tens of windows after a few hours, if unsupervised. To test manually: 1. Select a wireless network for which no password has been saved from nm-applet. 2. The dialog pops up. 3. Without closing the dialog, reselect the network from nm-applet. 4. A second (identical) dialog pops up. (Expected: The old dialog is reused, or is closed as stale.) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager 0.9.4.0-0ubuntu4.1 ProcVersionSignature: Ubuntu 3.2.0-29.46-generic-pae 3.2.24 Uname: Linux 3.2.0-29-generic-pae i686 ApportVersion: 2.0.1-0ubuntu12 Architecture: i386 CasperVersion: 1.315 Date: Mon Oct 1 14:22:27 2012 IfupdownConfig: auto lo iface lo inet loopback IpRoute: default via 192.168.0.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.15 metric 2 LiveMediaBuild: Ubuntu 12.04.1 LTS Precise Pangolin - Release i386 (20120817.3) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Wired connection 112cd62ad-698e-4507-a944-0d89176544fd 802-3-ethernet1349083407 Mon 01 Oct 2012 12:23:27 PM EEST yes no /org/freedesktop/NetworkManager/Settings/2 penthouse a48953a3-d68b-41b9-81bb-4d2027587186 802-11-wireless 1349090319 Mon 01 Oct 2012 02:18:39 PM EEST yes no /org/freedesktop/NetworkManager/Settings/1 temp d3d7b612-ca12-4fe1-8cfd-2d0d1b2eb3f6 802-11-wireless 1348708389 Thu 27 Sep 2012 04:13:09 AM EEST yes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.4.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1059529/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1260751] [NEW] Conffile prompt on upgrade from 13.10 to 14.04
Public bug reported: I got a conffile prompt for /etc/avserver.conf when upgrading from 13.10 to 14.04. I have never touched this file by hand, and the diff looks like it was caused by a rename from 'FFServer' to 'AVServer'. This file should be updated automatically, without user intervention, during a dist upgrade. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libav-tools 6:9.10-1ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 NonfreeKernelModules: vboxpci vboxnetadp vboxnetflt vboxdrv nvidia ApportVersion: 2.12.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Dec 13 09:30:26 2013 InstallationDate: Installed on 2010-09-17 (1183 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1) SourcePackage: libav UpgradeStatus: Upgraded to trusty on 2013-12-13 (0 days ago) mtime.conffile..etc.avserver.conf: 2011-08-26T06:12:12 ** Affects: libav (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 libav in Ubuntu. https://bugs.launchpad.net/bugs/1260751 Title: Conffile prompt on upgrade from 13.10 to 14.04 Status in “libav” package in Ubuntu: New Bug description: I got a conffile prompt for /etc/avserver.conf when upgrading from 13.10 to 14.04. I have never touched this file by hand, and the diff looks like it was caused by a rename from 'FFServer' to 'AVServer'. This file should be updated automatically, without user intervention, during a dist upgrade. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libav-tools 6:9.10-1ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 NonfreeKernelModules: vboxpci vboxnetadp vboxnetflt vboxdrv nvidia ApportVersion: 2.12.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Dec 13 09:30:26 2013 InstallationDate: Installed on 2010-09-17 (1183 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1) SourcePackage: libav UpgradeStatus: Upgraded to trusty on 2013-12-13 (0 days ago) mtime.conffile..etc.avserver.conf: 2011-08-26T06:12:12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1260751/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1260751] Re: Conffile prompt on upgrade from 13.10 to 14.04
Here is the diff: --- /etc/avserver.conf 2011-08-26 06:12:12.0 -0400 +++ /etc/avserver.conf.dpkg-new 2013-11-03 08:51:39.0 -0500 @@ -12,7 +12,7 @@ # MaxClients maximum limit. MaxHTTPConnections 2000 -# Number of simultaneous requests that can be handled. Since FFServer +# Number of simultaneous requests that can be handled. Since AVServer # is very fast, it is more likely that you will want to leave this high # and use MaxBandwidth, below. MaxClients 1000 @@ -25,24 +25,21 @@ # '-' is the standard output. CustomLog - -# Suppress that if you want to launch ffserver as a daemon. -NoDaemon - ## # Definition of the live feeds. Each live feed contains one video -# and/or audio sequence coming from an ffmpeg encoder or another -# ffserver. This sequence may be encoded simultaneously with several +# and/or audio sequence coming from an avconv encoder or another +# avserver. This sequence may be encoded simultaneously with several # codecs at several resolutions. Feed feed1.ffm -# You must use 'ffmpeg' to send a live feed to ffserver. In this +# You must use 'avconv' to send a live feed to avserver. In this # example, you can type: # -# ffmpeg http://localhost:8090/feed1.ffm +# avconv http://localhost:8090/feed1.ffm -# ffserver can also do time shifting. It means that it can stream any +# avserver can also do time shifting. It means that it can stream any # previously recorded live stream. The request should contain: # http://?date=[-MM-DDT][[HH:]MM:]SS[.m...].You must specify # a path where the feed is stored on disk. You also specify the @@ -55,10 +52,10 @@ # ReadOnlyFile /saved/specialvideo.ffm # This marks the file as readonly and it will not be deleted or updated. -# Specify launch in order to start ffmpeg automatically. -# First ffmpeg must be defined with an appropriate path if needed, +# Specify launch in order to start avconv automatically. +# First avconv must be defined with an appropriate path if needed, # after that options can follow, but avoid adding the http:// field -#Launch ffmpeg +#Launch avconv # Only allow connections from localhost to the feed. ACL allow 127.0.0.1 @@ -69,7 +66,7 @@ ## # Now you can define each stream which will be generated from the # original audio and video stream. Each format has a filename (here -# 'test1.mpg'). FFServer will send this stream when answering a +# 'test1.mpg'). AVServer will send this stream when answering a # request containing this filename. Stream test1.mpg @@ -334,7 +331,7 @@ # multicast address with MulticastAddress. The port and the TTL can # also be set. # -# An SDP file is automatically generated by ffserver by adding the +# An SDP file is automatically generated by avserver by adding the # 'sdp' extension to the stream name (here # http://localhost:8090/test1-sdp.sdp). You should usually give this # file to your player to play the stream. @@ -373,5 +370,3 @@ Redirect index.html URL http://www.libav.org/ /Redirect - - -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libav in Ubuntu. https://bugs.launchpad.net/bugs/1260751 Title: Conffile prompt on upgrade from 13.10 to 14.04 Status in “libav” package in Ubuntu: New Bug description: I got a conffile prompt for /etc/avserver.conf when upgrading from 13.10 to 14.04. I have never touched this file by hand, and the diff looks like it was caused by a rename from 'FFServer' to 'AVServer'. This file should be updated automatically, without user intervention, during a dist upgrade. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libav-tools 6:9.10-1ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Uname: Linux 3.11.0-14-generic x86_64 NonfreeKernelModules: vboxpci vboxnetadp vboxnetflt vboxdrv nvidia ApportVersion: 2.12.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Dec 13 09:30:26 2013 InstallationDate: Installed on 2010-09-17 (1183 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1) SourcePackage: libav UpgradeStatus: Upgraded to trusty on 2013-12-13 (0 days ago) mtime.conffile..etc.avserver.conf: 2011-08-26T06:12:12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1260751/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1239886] Re: regression: hotkeys no longer functional
@Doug: gnome-screensaver is installed, yes After updating to the latest available updates from today I can no longer reproduce this problem; the hotkeys work fine. ** Changed in: gnome-settings-daemon (Ubuntu) Status: New = Invalid -- 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/1239886 Title: regression: hotkeys no longer functional Status in “gnome-settings-daemon” package in Ubuntu: Invalid Bug description: [edit: originally this bug was just about keyboard backlight hotkeys, but it turns out all hotkeys are broken] A recent change to 13.10 has broken hotkeys on my MacbookPro3,1. This was working well until about a week ago (1st week of October 2013). The underlying (kernel) functionality still works; for example this will turn off the keyboard backlight with no problem: echo 0 | sudo tee -a /sys/class/leds/smc\:\:kbd_backlight/brightness Therefore I assume it's a gnome-settings-daemon (or upower?) regression. To reproduce: 1) Login 2) Press a hotkey (for example screen brightness; keyboard backlight; etc) Expected results: Keyboard backlight changes when you press the hotkey Actual results: Nothing happens when you press any of the hotkeys ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-settings-daemon 3.8.5-0ubuntu7 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Mon Oct 14 20:09:56 2013 InstallationDate: Installed on 2010-09-17 (1123 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1) MarkForUpload: True SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to saucy on 2013-08-07 (68 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1239886/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1239886] [NEW] regression: keyboard backlight hotkeys no longer functional
Public bug reported: A recent change to 13.10 has broken userspace control of the keyboard backlight on my MacbookPro3,1. This was working well until about a week ago (1st week of October 2013). The backlight device in the kernel still works; for example this will turn off the keyboard backlight: echo 0 | sudo tee -a /sys/class/leds/smc\:\:kbd_backlight/brightness Therefore I assume it's a gnome-settings-daemon (or upower?) regression. To reproduce: 1) Login. Note the state of the keyboard backlight (should beon, 100%) 2) Press a keyboard backlight hotkey Expected results: Keyboard backlight changes when you press the hotkey Actual results: Nothing happens when you press any of the keyboard backlight hotkeys ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-settings-daemon 3.8.5-0ubuntu7 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Mon Oct 14 20:09:56 2013 InstallationDate: Installed on 2010-09-17 (1123 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1) MarkForUpload: True SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to saucy on 2013-08-07 (68 days ago) ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy ** Summary changed: - regression: keyboard backlight control no longer functional + regression: keyboard backlight hotkeys no longer functional -- 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/1239886 Title: regression: keyboard backlight hotkeys no longer functional Status in “gnome-settings-daemon” package in Ubuntu: New Bug description: A recent change to 13.10 has broken userspace control of the keyboard backlight on my MacbookPro3,1. This was working well until about a week ago (1st week of October 2013). The backlight device in the kernel still works; for example this will turn off the keyboard backlight: echo 0 | sudo tee -a /sys/class/leds/smc\:\:kbd_backlight/brightness Therefore I assume it's a gnome-settings-daemon (or upower?) regression. To reproduce: 1) Login. Note the state of the keyboard backlight (should beon, 100%) 2) Press a keyboard backlight hotkey Expected results: Keyboard backlight changes when you press the hotkey Actual results: Nothing happens when you press any of the keyboard backlight hotkeys ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-settings-daemon 3.8.5-0ubuntu7 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Mon Oct 14 20:09:56 2013 InstallationDate: Installed on 2010-09-17 (1123 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1) MarkForUpload: True SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to saucy on 2013-08-07 (68 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1239886/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1239886] Re: regression: hotkeys no longer functional
** Summary changed: - regression: keyboard backlight hotkeys no longer functional + regression: hotkeys no longer functional ** Description changed: - A recent change to 13.10 has broken userspace control of the keyboard - backlight on my MacbookPro3,1. This was working well until about a week - ago (1st week of October 2013). + [edit: originally this bug was just about keyboard backlight hotkeys, + but it turns out all hotkeys are broken] - The backlight device in the kernel still works; for example this will turn off the keyboard backlight: + A recent change to 13.10 has broken hotkeys on my MacbookPro3,1. This + was working well until about a week ago (1st week of October 2013). + + The underlying (kernel) functionality still works; for example this will turn off the keyboard backlight with no problem: echo 0 | sudo tee -a /sys/class/leds/smc\:\:kbd_backlight/brightness Therefore I assume it's a gnome-settings-daemon (or upower?) regression. To reproduce: - 1) Login. Note the state of the keyboard backlight (should beon, 100%) - 2) Press a keyboard backlight hotkey + 1) Login + 2) Press a hotkey (for example screen brightness; keyboard backlight; etc) Expected results: Keyboard backlight changes when you press the hotkey Actual results: - Nothing happens when you press any of the keyboard backlight hotkeys + Nothing happens when you press any of the hotkeys ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-settings-daemon 3.8.5-0ubuntu7 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Mon Oct 14 20:09:56 2013 InstallationDate: Installed on 2010-09-17 (1123 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1) MarkForUpload: True SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to saucy on 2013-08-07 (68 days ago) -- 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/1239886 Title: regression: hotkeys no longer functional Status in “gnome-settings-daemon” package in Ubuntu: New Bug description: [edit: originally this bug was just about keyboard backlight hotkeys, but it turns out all hotkeys are broken] A recent change to 13.10 has broken hotkeys on my MacbookPro3,1. This was working well until about a week ago (1st week of October 2013). The underlying (kernel) functionality still works; for example this will turn off the keyboard backlight with no problem: echo 0 | sudo tee -a /sys/class/leds/smc\:\:kbd_backlight/brightness Therefore I assume it's a gnome-settings-daemon (or upower?) regression. To reproduce: 1) Login 2) Press a hotkey (for example screen brightness; keyboard backlight; etc) Expected results: Keyboard backlight changes when you press the hotkey Actual results: Nothing happens when you press any of the hotkeys ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-settings-daemon 3.8.5-0ubuntu7 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Mon Oct 14 20:09:56 2013 InstallationDate: Installed on 2010-09-17 (1123 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1) MarkForUpload: True SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to saucy on 2013-08-07 (68 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1239886/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1228970] Re: [Dell System XPS L322X, Realtek ALC275, Black Headphone Out, Front] Intermittant crackly sound output
I was unable to reproduce this on my XPS13, which is the original model (Sandy Bridge CPU, not Ivy Bridge). I'm running 13.10. There is some crackling through the headphones when you are plugging/unplugging the headphones. Once the headphones are plugged in on this system, playback sounds fine. Jack sense is reliable on this system. -- 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/1228970 Title: [Dell System XPS L322X, Realtek ALC275, Black Headphone Out, Front] Intermittant crackly sound output Status in “alsa-driver” package in Ubuntu: New Bug description: Hi, After upgrading my Dell XPS13 laptop to Saucy, I am unable to hear any useful sound out of the headphone jack. When I plug my headphones into the jack I can see the Built-in Audio for the Speakers briefly flick over to Headphones and then either flick back to Speakers most of the time or occasionally it will stay on headphones, but any sound output is extremely crackly and useless. On the times that it won't stay as headphones I can force it by running: $ pactl set-sink-port alsa_output.pci-_00_1b.0.analog-stereo analog-output-headphones This just forces it into the crackly output state as above. I've attached a verbose pulse log from attaching the headphones as pulseverbose.log. Please let me know if you need any more information. Thanks, Brad ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1 Uname: Linux 3.11.0-7-generic x86_64 ApportVersion: 2.12.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bradm 3486 F pulseaudio /dev/snd/pcmC0D0c: bradm 3486 F...m pulseaudio Date: Mon Sep 23 09:13:26 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2013-08-19 (34 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bradm 3486 F pulseaudio /dev/snd/pcmC0D0c: bradm 3486 F...m pulseaudio Symptom_Jack: Black Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: No sound at all Title: [Dell System XPS L322X, Realtek ALC275, Black Headphone Out, Front] No sound at all UpgradeStatus: Upgraded to saucy on 2013-09-13 (9 days ago) dmi.bios.date: 05/15/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0PJHXN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd05/15/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L322X dmi.sys.vendor: Dell Inc. modified.conffile..etc.modprobe.d.alsa.base.conf: [modified] mtime.conffile..etc.modprobe.d.alsa.base.conf: 2013-09-23T09:09:56.448103 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1228970/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1224040] [NEW] 13.10: Multiple network manager authentication dialogs for saved network
Public bug reported: I'm using 13.10 on a Dell XPS13. Network Manager will sometimes put up multiple (10+) authentication dialogs asking me for the password to reconnect to my wireless network. Network Manager already knows the password for the network, and automatically joins the network after reboot/resume/etc. I think there are 2 issues: 1) Network Manager asks for the password even though it already knows the password 2) Network Manager puts up too many dialogs (this issue is reported elsewhere, for example bug 1059529) Steps to reproduce: 1) Connect to a wireless network 2) Leave the machine idle for awhile 3) Unlock the machine from the lock screen Expected results: After unlocking the machine, the desktop and all windows are onscreen. There are no authentication dialogs from network manager Actual results: After unlocking the machine, the desktop and all windows are onscreen. There are 10+ authentication dialogs from network manager Regression info: I thought this was fixed in 12.10/13.04 but it's happening for me in 13.10. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: network-manager 0.9.8.0-0ubuntu20 ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0 Uname: Linux 3.11.0-5-generic x86_64 ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 Date: Wed Sep 11 14:11:40 2013 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20120703-2 IfupdownConfig: auto lo iface lo inet loopback InstallationDate: Installed on 2012-11-29 (286 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20120703-15:08 IpRoute: default via 10.0.1.1 dev wlan0 proto static 10.0.1.0/24 dev wlan0 proto kernel scope link src 10.0.1.55 metric 9 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to saucy on 2013-07-19 (54 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.0connected enabled enabled enabledenabled disabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- 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/1224040 Title: 13.10: Multiple network manager authentication dialogs for saved network Status in “network-manager” package in Ubuntu: New Bug description: I'm using 13.10 on a Dell XPS13. Network Manager will sometimes put up multiple (10+) authentication dialogs asking me for the password to reconnect to my wireless network. Network Manager already knows the password for the network, and automatically joins the network after reboot/resume/etc. I think there are 2 issues: 1) Network Manager asks for the password even though it already knows the password 2) Network Manager puts up too many dialogs (this issue is reported elsewhere, for example bug 1059529) Steps to reproduce: 1) Connect to a wireless network 2) Leave the machine idle for awhile 3) Unlock the machine from the lock screen Expected results: After unlocking the machine, the desktop and all windows are onscreen. There are no authentication dialogs from network manager Actual results: After unlocking the machine, the desktop and all windows are onscreen. There are 10+ authentication dialogs from network manager Regression info: I thought this was fixed in 12.10/13.04 but it's happening for me in 13.10. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: network-manager 0.9.8.0-0ubuntu20 ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0 Uname: Linux 3.11.0-5-generic x86_64 ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 Date: Wed Sep 11 14:11:40 2013 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20120703-2 IfupdownConfig: auto lo iface lo inet loopback InstallationDate: Installed on 2012-11-29 (286 days ago) InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20120703-15:08 IpRoute: default via 10.0.1.1 dev wlan0 proto static 10.0.1.0/24 dev wlan0 proto kernel scope link src 10.0.1.55 metric 9
[Desktop-packages] [Bug 950160] Re: Unity blocks other programs from binding globally to Super+* (* = any key)
Dropping the oem-priority escalation; OEMs are shipping a workaround. ** Changed in: oem-priority Status: In Progress = Won't Fix ** Changed in: oem-priority/precise Status: In Progress = Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/950160 Title: Unity blocks other programs from binding globally to Super+* (* = any key) Status in Compiz: Fix Released Status in Compiz 0.9.8 series: In Progress Status in Compiz Core: Confirmed Status in Gnome Settings Daemon: Fix Released Status in OEM Priority Project: Won't Fix Status in OEM Priority Project precise series: Won't Fix Status in Unity: Fix Released Status in Unity 5.0 series: Triaged Status in Unity 6.0 series: In Progress Status in “compiz” package in Ubuntu: Fix Released Status in “gnome-settings-daemon” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: In Progress Status in “compiz” source package in Precise: Triaged Status in “gnome-settings-daemon” source package in Precise: Fix Released Status in “unity” source package in Precise: Triaged Status in “compiz” source package in Quantal: Triaged Status in “gnome-settings-daemon” source package in Quantal: Fix Released Status in “unity” source package in Quantal: In Progress Bug description: WORKAROUND 1: Run CCSM and under Ubuntu Unity Plugin change the key binding for Key to show the launcher to something else (e.g. Super+U). Then log out and in again. As long as no compiz plugin is bound to the single Super key any more, compiz will no longer block other apps from binding to Super+other_keys. WORKAROUND 2: 1. Write a script or figure out the command to do the action you want. 2. Run ccsm. 3. Enable the Commands plugin 4. In the Commands settings, fill in the command line you want and bind it to key Super+P. Now Unity will run your specified command on Super+P, but still handle the Super key as usual. [Precise SRU Justification] [Impact] Any shortcut with Super, Hyper, Meta virtual modifiers does not work [Test Case] Attach an external monitor to the laptop, press Super+P, it should do the video switch as this function is implemented in gnome-settings-daemon. A patch in comment #12 is now accepted upstream and a test package with that patch is available in comment #14. From the test result, the patch at least fixes Unity-2D. [Regression Potential] The patch is accepted upstream and is also cherry-picked in the gnome-3-4 branch of g-s-d git tree. g-s-d version in Precise is 3.4.2. So the risk of regression should be rather low. [Other] I prepare a debdiff in comment #31 for convenience. I hope the patch can be in both Quantal and Precise. ORIGINAL DESCRIPTION: Using : 12.04 Beta 1, updated. and Unity. In 11.10 clicking: - the function key (Fn) + (F1) allowed to switch between the laptop screen and the external monitor. After upgrading to 12.04 this no more works and instead I get an unexpected behavior: see the video. https://www.youtube.com/watch?v=-vEnrV5TwXo System: Dell XPS 15 L502X ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: ubuntu-sso-client 2.99.90-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9 Uname: Linux 3.2.0-18-generic x86_64 ApportVersion: 1.94.1-0ubuntu1 Architecture: amd64 Date: Thu Mar 8 19:18:42 2012 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) PackageArchitecture: all SourcePackage: ubuntu-sso-client UpgradeStatus: Upgraded to precise on 2012-03-02 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/950160/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1177381] Re: Backup failed with unknown error
Deja dup occasionally runs a full backup (looks like once every 3 months on my system). Today it chose to do a full backup for me, which seems to have cleared this error - the full backup completed successfully with no reported errors. I'm not sure how to trigger a full backup manually; I waited for deja dup to do it. -- 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/1177381 Title: Backup failed with unknown error Status in “deja-dup” package in Ubuntu: Confirmed Bug description: My backups have been working normally for months, but today they failed with this error: Failed with an unknown error: Traceback (most recent call last): File /usr/bin/duplicity, line 1411, in module with_tempdir(main) File /usr/bin/duplicity, line 1404, in with_tempdir fn() File /usr/bin/duplicity, line 1386, in main incremental_backup(sig_chain) File /usr/bin/duplicity, line 581, in incremental_backup globals.backend) File /usr/bin/duplicity, line 394, in write_multivol vi.set_hash(SHA1, gpg.get_hash(SHA1, tdp)) File /usr/lib/python2.7/dist-packages/duplicity/gpg.py, line 401, in get_hash fp = path.open(rb) File /usr/lib/python2.7/dist-packages/duplicity/path.py, line 542, in open result = open(self.name, mode) IOError: [Errno 2] No such file or directory: '/tmp/duplicity-rWgqMw-tempdir/mktemp-fvN6e5-5' ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: deja-dup 26.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Tue May 7 09:12:25 2013 InstallationDate: Installed on 2010-09-17 (962 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: deja-dup UpgradeStatus: Upgraded to raring on 2013-01-25 (101 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1177381/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1034999] Re: libreoffice-calc very slow to open/save documents with large cell contents
This is reproducible in raring (13.04) with libreoffice 1:4.0.2-0ubuntu1. I used the sample document attached to this bug. ** Changed in: libreoffice (Ubuntu) Status: Incomplete = Confirmed -- 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/1034999 Title: libreoffice-calc very slow to open/save documents with large cell contents Status in “libreoffice” package in Ubuntu: Confirmed Bug description: Libreoffice-calc 3.6 takes a long time (30sec to minutes) to open/save spreadsheets containing cells with a lot of content. This is a regression from libreoffice 3.5 in 12.04 (tested with 1:3.5.4-0ubuntu1) To reproduce: 1) Open the attached spreadsheet, which contains 1 cell with ~4k characters in it Expected results: Spreadsheet opens quickly (2sec on my 2.4Ghz Core2Duo w/ SSD) Actual results: Libreoffice splash screen shows, libreoffice window is displayed as a gray rectangle with no content, and libreoffice window then becomes unresponsive. CPU usage is at 100% on one core. The system stays in this state for ~30sec. The document eventually opens and libreoffice functions normally. Saving documents with lots of data in a cell takes just as long as opening/reading those documents, with similar symptoms - libreoffice becomes unresponsive, one CPU core is at full utilization, etc. The amount of text in the cell is directly correlated to the length of time required to open/save the doc. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: libreoffice-calc 1:3.6.0~rc4-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-8.8-generic 3.5.0 Uname: Linux 3.5.0-8-generic x86_64 ApportVersion: 2.4-0ubuntu6 Architecture: amd64 Date: Thu Aug 9 13:20:27 2012 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1) ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to quantal on 2012-08-07 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1034999/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1048684] Re: soffice.bin crashed with SIGSEGV
@Christopher - I can't provide the example, sorry. It contains confidential information that I cannot share in a public forum like Launchpad. -- 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/1048684 Title: soffice.bin crashed with SIGSEGV Status in “libreoffice” package in Ubuntu: Incomplete Bug description: libreoffice crashed while opening a .docx document attached to an email. Unfortunately I can't share the document - it's confidential. To reproduce: 1) Double-click a docx document Expected results: Document opens Actual results: LibreOffice splash screen displays briefly, then disappears. Apport reports that soffice.bin crashed. Libreoffice does not open the document. This is reproducible on my system - I reliably cannot open the document in libreoffice. There is no related output when I open the doc from a terminal by invoking 'libreoffice docname.docx' ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: libreoffice-core 1:3.6.1~rc2-1ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-14.15-generic 3.5.3 Uname: Linux 3.5.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 CrashCounter: 1 Date: Mon Sep 10 10:46:13 2012 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1) ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --writer /tmp/Linux\ Requirements\ Specification\ for\ Lenovo\ IdeaPad\ 2013\ WW.docx --splash-pipe=6 ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f2f88991b1f:mov0x8(%rax),%rax PC (0x7f2f88991b1f) ok source 0x8(%rax) (0x0008) not located in a known VMA region (needed readable region)! destination %rax ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: libreoffice StacktraceTop: ?? () from /usr/lib/libreoffice/program/../program/libswlo.so ?? () from /usr/lib/libreoffice/program/../program/libswlo.so ?? () from /usr/lib/libreoffice/program/../program/libswlo.so ?? () from /usr/lib/libreoffice/program/../program/libswlo.so ?? () from /usr/lib/libreoffice/program/../program/libwriterfilterlo.so Title: soffice.bin crashed with SIGSEGV UpgradeStatus: Upgraded to quantal on 2012-08-07 (33 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1048684/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1176018] Re: Error when doing backup in 13.4
*** This bug is a duplicate of bug 1155345 *** https://bugs.launchpad.net/bugs/1155345 ** This bug has been marked a duplicate of bug 1155345 Backup fails on verifying files backed up -- 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/1176018 Title: Error when doing backup in 13.4 Status in “deja-dup” package in Ubuntu: Confirmed Bug description: I just upgraded to 13.4 when I try to do a backup it says unknown error. This is the info it gives in the box. Traceback (most recent call last): File /usr/bin/duplicity, line 1411, in module with_tempdir(main) File /usr/bin/duplicity, line 1404, in with_tempdir fn() File /usr/bin/duplicity, line 1338, in main restore(col_stats) File /usr/bin/duplicity, line 632, in restore restore_get_patched_rop_iter(col_stats)): File /usr/lib/python2.7/dist-packages/duplicity/patchdir.py, line 526, in Write_ROPaths for ropath in rop_iter: File /usr/lib/python2.7/dist-packages/duplicity/patchdir.py, line 499, in integrate_patch_iters final_ropath = patch_seq2ropath( normalize_ps( patch_seq ) ) File /usr/lib/python2.7/dist-packages/duplicity/patchdir.py, line 466, in patch_seq2ropath assert len( patch_seq ) == 1, len( patch_seq ) AssertionError: 3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1176018/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1162320] Re: Backup failed during verification.
*** This bug is a duplicate of bug 1155345 *** https://bugs.launchpad.net/bugs/1155345 ** This bug has been marked a duplicate of bug 1155345 Backup fails on verifying files backed up -- 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/1162320 Title: Backup failed during verification. Status in “deja-dup” package in Ubuntu: New Bug description: This happens every time (in Raring) when backing up to my external USB drive (USB 3.0 connection). Not sure why it might fail at the verification stage, but this leaves me with an uneasy feeling whether my backup is okay or not. See error message in screenshot attached. Thanks. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: deja-dup 26.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-8.17-generic 3.8.0 Uname: Linux 3.8.0-8-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 Date: Sat Mar 30 14:23:10 2013 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: deja-dup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1162320/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1155345] Re: Backup fails on verifying files backed up
This is a regression from 12.10. I reliably get this error when backing up to my external disk on 13.04. -- 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/1155345 Title: Backup fails on verifying files backed up Status in “deja-dup” package in Ubuntu: Confirmed Bug description: Backup fails to verify the files backed up to my external USB3 drive. Here's the output from the GUI: Traceback (most recent call last): File /usr/bin/duplicity, line 1411, in module with_tempdir(main) File /usr/bin/duplicity, line 1404, in with_tempdir fn() File /usr/bin/duplicity, line 1338, in main restore(col_stats) File /usr/bin/duplicity, line 632, in restore restore_get_patched_rop_iter(col_stats)): File /usr/lib/python2.7/dist-packages/duplicity/patchdir.py, line 526, in Write_ROPaths for ropath in rop_iter: File /usr/lib/python2.7/dist-packages/duplicity/patchdir.py, line 499, in integrate_patch_iters final_ropath = patch_seq2ropath( normalize_ps( patch_seq ) ) File /usr/lib/python2.7/dist-packages/duplicity/patchdir.py, line 466, in patch_seq2ropath assert len( patch_seq ) == 1, len( patch_seq ) AssertionError: 4 ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: deja-dup 25.5-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-8.17-generic 3.8.0 Uname: Linux 3.8.0-8-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.1-0ubuntu1 Architecture: amd64 Date: Thu Mar 14 17:03:18 2013 EcryptfsInUse: Yes MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: deja-dup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1155345/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1177381] [NEW] Backup failed with unknown error
Public bug reported: My backups have been working normally for months, but today they failed with this error: Failed with an unknown error: Traceback (most recent call last): File /usr/bin/duplicity, line 1411, in module with_tempdir(main) File /usr/bin/duplicity, line 1404, in with_tempdir fn() File /usr/bin/duplicity, line 1386, in main incremental_backup(sig_chain) File /usr/bin/duplicity, line 581, in incremental_backup globals.backend) File /usr/bin/duplicity, line 394, in write_multivol vi.set_hash(SHA1, gpg.get_hash(SHA1, tdp)) File /usr/lib/python2.7/dist-packages/duplicity/gpg.py, line 401, in get_hash fp = path.open(rb) File /usr/lib/python2.7/dist-packages/duplicity/path.py, line 542, in open result = open(self.name, mode) IOError: [Errno 2] No such file or directory: '/tmp/duplicity-rWgqMw-tempdir/mktemp-fvN6e5-5' ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: deja-dup 26.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Tue May 7 09:12:25 2013 InstallationDate: Installed on 2010-09-17 (962 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: deja-dup UpgradeStatus: Upgraded to raring on 2013-01-25 (101 days ago) ** Affects: deja-dup (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- 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/1177381 Title: Backup failed with unknown error Status in “deja-dup” package in Ubuntu: New Bug description: My backups have been working normally for months, but today they failed with this error: Failed with an unknown error: Traceback (most recent call last): File /usr/bin/duplicity, line 1411, in module with_tempdir(main) File /usr/bin/duplicity, line 1404, in with_tempdir fn() File /usr/bin/duplicity, line 1386, in main incremental_backup(sig_chain) File /usr/bin/duplicity, line 581, in incremental_backup globals.backend) File /usr/bin/duplicity, line 394, in write_multivol vi.set_hash(SHA1, gpg.get_hash(SHA1, tdp)) File /usr/lib/python2.7/dist-packages/duplicity/gpg.py, line 401, in get_hash fp = path.open(rb) File /usr/lib/python2.7/dist-packages/duplicity/path.py, line 542, in open result = open(self.name, mode) IOError: [Errno 2] No such file or directory: '/tmp/duplicity-rWgqMw-tempdir/mktemp-fvN6e5-5' ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: deja-dup 26.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Tue May 7 09:12:25 2013 InstallationDate: Installed on 2010-09-17 (962 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: deja-dup UpgradeStatus: Upgraded to raring on 2013-01-25 (101 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1177381/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1068994] Re: button1 gets stuck after a while
** Also affects: oem-priority/precise Importance: Undecided Status: New ** Changed in: oem-priority/precise Status: New = In Progress ** Changed in: oem-priority/precise Importance: Undecided = Critical -- 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/1068994 Title: button1 gets stuck after a while Status in OEM Priority Project: In Progress Status in OEM Priority Project precise series: In Progress Status in OEM Priority Project raring series: In Progress Status in Ubuntu on the Nexus 7: Confirmed Status in X.Org X server: In Progress Status in “xorg-server” package in Ubuntu: Confirmed Bug description: distro bug 1015183 after using the tablet for a while, the touchscreen fails to register button clicks anymore, since the button appears to be stuck down. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1068994/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1174789] [NEW] Restore failure with librsync error 103
Public bug reported: I'm trying to restore my Thunderbird profile from a recent (2 week old) backup. The restore failed with a set of errors. To reproduce: 0) Backup ~/ to a local disk using deja-dup 1) Quit Thunderbird then navigate to the .thunderbird directory in nautilus 2) Right-click the Thunderbird profile directory (e.g. .default) in nautilus and choose, Revert to previous version 3) Choose the backup location (an external disk in my case) 4) Choose the backup to restore from 5) On the Summary screen of the Restore window, choose Restore Expected results: Deja-dup restores the previous version of the folder Actual results: After some time, the Restore window shows the message, Restore Failed with the following additional data: Failed with an unknown error. Traceback (most recent call last): File /usr/bin/duplicity, line 1411, in module with_tempdir(main) File /usr/bin/duplicity, line 1404, in with_tempdir fn() File /usr/bin/duplicity, line 1338, in main restore(col_stats) File /usr/bin/duplicity, line 632, in restore restore_get_patched_rop_iter(col_stats)): File /usr/lib/python2.7/dist-packages/duplicity/patchdir.py, line 526, in Write_ROPaths for ropath in rop_iter: File /usr/lib/python2.7/dist-packages/duplicity/patchdir.py, line 499, in integrate_patch_iters final_ropath = patch_seq2ropath( normalize_ps( patch_seq ) ) File /usr/lib/python2.7/dist-packages/duplicity/patchdir.py, line 479, in patch_seq2ropath misc.copyfileobj( current_file, tempfp ) File /usr/lib/python2.7/dist-packages/duplicity/misc.py, line 166, in copyfileobj buf = infp.read(blocksize) File /usr/lib/python2.7/dist-packages/duplicity/librsync.py, line 80, in read self._add_to_outbuf_once() File /usr/lib/python2.7/dist-packages/duplicity/librsync.py, line 94, in _add_to_outbuf_once raise librsyncError(str(e)) librsyncError: librsync error 103 while in patch cycle ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: deja-dup 26.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Tue Apr 30 10:54:03 2013 InstallationDate: Installed on 2010-09-17 (956 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: deja-dup UpgradeStatus: Upgraded to raring on 2013-01-25 (94 days ago) ** Affects: deja-dup (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring -- 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/1174789 Title: Restore failure with librsync error 103 Status in “deja-dup” package in Ubuntu: New Bug description: I'm trying to restore my Thunderbird profile from a recent (2 week old) backup. The restore failed with a set of errors. To reproduce: 0) Backup ~/ to a local disk using deja-dup 1) Quit Thunderbird then navigate to the .thunderbird directory in nautilus 2) Right-click the Thunderbird profile directory (e.g. .default) in nautilus and choose, Revert to previous version 3) Choose the backup location (an external disk in my case) 4) Choose the backup to restore from 5) On the Summary screen of the Restore window, choose Restore Expected results: Deja-dup restores the previous version of the folder Actual results: After some time, the Restore window shows the message, Restore Failed with the following additional data: Failed with an unknown error. Traceback (most recent call last): File /usr/bin/duplicity, line 1411, in module with_tempdir(main) File /usr/bin/duplicity, line 1404, in with_tempdir fn() File /usr/bin/duplicity, line 1338, in main restore(col_stats) File /usr/bin/duplicity, line 632, in restore restore_get_patched_rop_iter(col_stats)): File /usr/lib/python2.7/dist-packages/duplicity/patchdir.py, line 526, in Write_ROPaths for ropath in rop_iter: File /usr/lib/python2.7/dist-packages/duplicity/patchdir.py, line 499, in integrate_patch_iters final_ropath = patch_seq2ropath( normalize_ps( patch_seq ) ) File /usr/lib/python2.7/dist-packages/duplicity/patchdir.py, line 479, in patch_seq2ropath misc.copyfileobj( current_file, tempfp ) File /usr/lib/python2.7/dist-packages/duplicity/misc.py, line 166, in copyfileobj buf = infp.read(blocksize) File /usr/lib/python2.7/dist-packages/duplicity/librsync.py, line 80, in read self._add_to_outbuf_once() File /usr/lib/python2.7/dist-packages/duplicity/librsync.py, line 94, in _add_to_outbuf_once raise librsyncError(str(e)) librsyncError: librsync error 103 while in patch cycle ProblemType: Bug
[Desktop-packages] [Bug 1174789] Re: Restore failure with librsync error 103
I've found this is 100% reproducible on my system, and it affects each of the 6 backups I tried. -- 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/1174789 Title: Restore failure with librsync error 103 Status in “deja-dup” package in Ubuntu: New Bug description: I'm trying to restore my Thunderbird profile from a recent (2 week old) backup. The restore failed with a set of errors. To reproduce: 0) Backup ~/ to a local disk using deja-dup 1) Quit Thunderbird then navigate to the .thunderbird directory in nautilus 2) Right-click the Thunderbird profile directory (e.g. .default) in nautilus and choose, Revert to previous version 3) Choose the backup location (an external disk in my case) 4) Choose the backup to restore from 5) On the Summary screen of the Restore window, choose Restore Expected results: Deja-dup restores the previous version of the folder Actual results: After some time, the Restore window shows the message, Restore Failed with the following additional data: Failed with an unknown error. Traceback (most recent call last): File /usr/bin/duplicity, line 1411, in module with_tempdir(main) File /usr/bin/duplicity, line 1404, in with_tempdir fn() File /usr/bin/duplicity, line 1338, in main restore(col_stats) File /usr/bin/duplicity, line 632, in restore restore_get_patched_rop_iter(col_stats)): File /usr/lib/python2.7/dist-packages/duplicity/patchdir.py, line 526, in Write_ROPaths for ropath in rop_iter: File /usr/lib/python2.7/dist-packages/duplicity/patchdir.py, line 499, in integrate_patch_iters final_ropath = patch_seq2ropath( normalize_ps( patch_seq ) ) File /usr/lib/python2.7/dist-packages/duplicity/patchdir.py, line 479, in patch_seq2ropath misc.copyfileobj( current_file, tempfp ) File /usr/lib/python2.7/dist-packages/duplicity/misc.py, line 166, in copyfileobj buf = infp.read(blocksize) File /usr/lib/python2.7/dist-packages/duplicity/librsync.py, line 80, in read self._add_to_outbuf_once() File /usr/lib/python2.7/dist-packages/duplicity/librsync.py, line 94, in _add_to_outbuf_once raise librsyncError(str(e)) librsyncError: librsync error 103 while in patch cycle ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: deja-dup 26.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Tue Apr 30 10:54:03 2013 InstallationDate: Installed on 2010-09-17 (956 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: deja-dup UpgradeStatus: Upgraded to raring on 2013-01-25 (94 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1174789/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 982889] Re: X trying to start before plymouth has finished using the drm driver
** Changed in: oem-priority Status: New = In Progress -- 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/982889 Title: X trying to start before plymouth has finished using the drm driver Status in OEM Priority Project: In Progress Status in OEM Priority Project precise series: In Progress Status in “libdrm” package in Ubuntu: Invalid Status in “lightdm” package in Ubuntu: Triaged Status in “linux” package in Ubuntu: Invalid Status in “plymouth” package in Ubuntu: Confirmed Status in “xorg-server” package in Ubuntu: Fix Released Bug description: X server fails to start the first time after boot, it works fine when I start it again. Looks like a race condition with intel drm initialization, i guess X tries to start faster than drm driver is initialized so it fails. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu3 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: Mon Apr 16 10:35:28 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. Device [1462:7750] Advanced Micro Devices [AMD] nee ATI Barts XT [ATI Radeon HD 6800 Series] [1002:6738] (prog-if 00 [VGA controller]) Subsystem: Giga-byte Technology Device [1458:21fa] InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120301) MachineType: MSI MS-7750 ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-23-generic root=/dev/mapper/ssd-ubuntu--precise ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/25/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V4.0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z68A-G43 (G3) (MS-7750) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV4.0:bd08/25/2011:svnMSI:pnMS-7750:pvr1.0:rvnMSI:rnZ68A-G43(G3)(MS-7750):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7750 dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz 1:0.9.7.6-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/982889/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 982889] Re: X trying to start before plymouth has finished using the drm driver
** Also affects: oem-priority Importance: Undecided Status: New ** Also affects: oem-priority/precise Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided = Critical ** Changed in: oem-priority/precise Importance: Undecided = Critical -- 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/982889 Title: X trying to start before plymouth has finished using the drm driver Status in OEM Priority Project: New Status in OEM Priority Project precise series: New Status in “libdrm” package in Ubuntu: Invalid Status in “lightdm” package in Ubuntu: Triaged Status in “linux” package in Ubuntu: Invalid Status in “plymouth” package in Ubuntu: Confirmed Status in “xorg-server” package in Ubuntu: Fix Released Bug description: X server fails to start the first time after boot, it works fine when I start it again. Looks like a race condition with intel drm initialization, i guess X tries to start faster than drm driver is initialized so it fails. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xorg 1:7.6+12ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu3 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: Mon Apr 16 10:35:28 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. Device [1462:7750] Advanced Micro Devices [AMD] nee ATI Barts XT [ATI Radeon HD 6800 Series] [1002:6738] (prog-if 00 [VGA controller]) Subsystem: Giga-byte Technology Device [1458:21fa] InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120301) MachineType: MSI MS-7750 ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-23-generic root=/dev/mapper/ssd-ubuntu--precise ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/25/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V4.0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z68A-G43 (G3) (MS-7750) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV4.0:bd08/25/2011:svnMSI:pnMS-7750:pvr1.0:rvnMSI:rnZ68A-G43(G3)(MS-7750):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7750 dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz 1:0.9.7.6-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.2-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.2-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/982889/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1110528] Re: Properties menu item not functional
This is still reproducible with totem 3.6.3-0ubuntu3 on 13.04. ** Changed in: totem (Ubuntu) Status: Incomplete = New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1110528 Title: Properties menu item not functional Status in “totem” package in Ubuntu: New Bug description: The Properties item in the Movie menu does nothing. To reproduce: 1) Launch totem. For example run `totem /usr/share/example-content/Ubuntu_Free_Culture_Showcase/How\ fast.ogg` from a shell 2) Select Properties from the Movie menu Expected results: A properties window opens, or a properties pane is displayed in the sidebar (similar to the way the playlists are displayed in the sidebar) Actual results: Nothing happens If you run totem from a terminal, you'll see this when invoking the properties menu item: Totem-WARNING **: Tried to set sidebar page 'properties' but it does not exist ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: totem 3.6.3-0ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-2.6-generic 3.8.0-rc4 Uname: Linux 3.8.0-2-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.8-0ubuntu2 Architecture: amd64 Date: Wed Jan 30 10:55:38 2013 InstallationDate: Installed on 2010-09-17 (866 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: totem UpgradeStatus: Upgraded to raring on 2013-01-25 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1110528/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1118446] Re: NetworkManager[14155]: warn nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted
I just saw this on a MacbookPro3,1 with Atheros wireless (AR5418 Wireless Network Adapter [AR5008E 802.11(a)bgn]). I'm running 13.04, and I have the 3.8.0-8.17 kernel. I'm connected to an 802.11 network in the 5GHz spectrum. Similar to comment #5 I lost name resolution. Other than Dump inconsistency message in syslog, there is no indication in dmesg or syslog that something is amiss. Unloading/reloading the ath9k driver worked around the problem for me. The AP I'm connected to is a Cisco of some sort; I can get details if necessary. -- 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/1118446 Title: NetworkManager[14155]: warn nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted Status in “network-manager” package in Ubuntu: Triaged Bug description: I see the following messages in /var/log/syslog: NetworkManager[14155]: warn nl_recvmsgs() error: (-33) Dump inconsistency detected, interrupted When it goes down, I have to bounce network-manager to resolve it. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: network-manager 0.9.7.995+git201301311547.17123fc-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-4.8-generic 3.8.0-rc6 Uname: Linux 3.8.0-4-generic x86_64 ApportVersion: 2.8-0ubuntu4 Architecture: amd64 Date: Thu Feb 7 08:59:00 2013 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-01-26 (12 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) IpRoute: default via 10.0.1.1 dev wlan0 proto static 10.0.1.0/24 dev wlan0 proto kernel scope link src 10.0.1.11 metric 9 169.254.0.0/16 dev wlan0 scope link metric 1000 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to raring on 2013-01-26 (11 days ago) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Ubuntuac3b296c-3250-4464-8ee0-ebd6e5d8e9ca 802-11-wireless 1360249035 Thu 07 Feb 2013 08:57:15 AM CSTyes no /org/freedesktop/NetworkManager/Settings/2 Palms 2e5ef890-c77c-466e-92ee-d9dcb777cf12 802-11-wireless 1359750784 Fri 01 Feb 2013 02:33:04 PM CSTyes no /org/freedesktop/NetworkManager/Settings/1 MIA-WiFi ea25a58d-9cb8-48a8-843a-2dc3231a1e17 802-11-wireless 1359754973 Fri 01 Feb 2013 03:42:53 PM CSTyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.7.995 connected enabled enabled enabledenabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1118446/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1124408] [NEW] wav file garbled in totem, plays fine in gst-launch and mplayer
Public bug reported: I tried to pay a .wav file in totem. The audio is garbled in totem but plays back fine in mplayer or when using gst-launch from the command line. This is a problem because Thunderbird uses Totem as the default handler for .wav audio, so .wav attachments to mails will be opened in Totem. To reproduce: 1) Open the attached .wav file in Movie Player (totem) Expected results: The audio file plays back with no errors Actual results: The audio is garbled during playback The file plays fine through gst-launch: ~$ gst-launch-0.10 playbin uri=file:///path/to/msg0001.WAV Mplayer also plays it without garbling the audio. Not all .wav files are affected. For example the files in /usr/share/sound/alsa/ work fine in totem. The audio was recorded from a voicemail box on an asterisk phone system. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: libgstreamer0.10-0 0.10.36-1ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-5.10-generic 3.8.0-rc6 Uname: Linux 3.8.0-5-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.8-0ubuntu4 Architecture: amd64 Date: Wed Feb 13 13:44:06 2013 InstallationDate: Installed on 2010-09-17 (880 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gstreamer0.10 UpgradeStatus: Upgraded to raring on 2013-01-25 (19 days ago) ** Affects: gstreamer0.10 (Ubuntu) Importance: Undecided Status: New ** Affects: totem (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring running-unity -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer0.10 in Ubuntu. https://bugs.launchpad.net/bugs/1124408 Title: wav file garbled in totem, plays fine in gst-launch and mplayer Status in “gstreamer0.10” package in Ubuntu: New Status in “totem” package in Ubuntu: New Bug description: I tried to pay a .wav file in totem. The audio is garbled in totem but plays back fine in mplayer or when using gst-launch from the command line. This is a problem because Thunderbird uses Totem as the default handler for .wav audio, so .wav attachments to mails will be opened in Totem. To reproduce: 1) Open the attached .wav file in Movie Player (totem) Expected results: The audio file plays back with no errors Actual results: The audio is garbled during playback The file plays fine through gst-launch: ~$ gst-launch-0.10 playbin uri=file:///path/to/msg0001.WAV Mplayer also plays it without garbling the audio. Not all .wav files are affected. For example the files in /usr/share/sound/alsa/ work fine in totem. The audio was recorded from a voicemail box on an asterisk phone system. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: libgstreamer0.10-0 0.10.36-1ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-5.10-generic 3.8.0-rc6 Uname: Linux 3.8.0-5-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.8-0ubuntu4 Architecture: amd64 Date: Wed Feb 13 13:44:06 2013 InstallationDate: Installed on 2010-09-17 (880 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gstreamer0.10 UpgradeStatus: Upgraded to raring on 2013-01-25 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/1124408/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1124408] Re: wav file garbled in totem, plays fine in gst-launch and mplayer
** Attachment added: msg0001.WAV https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/1124408/+attachment/3527043/+files/msg0001.WAV ** Also affects: totem (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer0.10 in Ubuntu. https://bugs.launchpad.net/bugs/1124408 Title: wav file garbled in totem, plays fine in gst-launch and mplayer Status in “gstreamer0.10” package in Ubuntu: New Status in “totem” package in Ubuntu: New Bug description: I tried to pay a .wav file in totem. The audio is garbled in totem but plays back fine in mplayer or when using gst-launch from the command line. This is a problem because Thunderbird uses Totem as the default handler for .wav audio, so .wav attachments to mails will be opened in Totem. To reproduce: 1) Open the attached .wav file in Movie Player (totem) Expected results: The audio file plays back with no errors Actual results: The audio is garbled during playback The file plays fine through gst-launch: ~$ gst-launch-0.10 playbin uri=file:///path/to/msg0001.WAV Mplayer also plays it without garbling the audio. Not all .wav files are affected. For example the files in /usr/share/sound/alsa/ work fine in totem. The audio was recorded from a voicemail box on an asterisk phone system. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: libgstreamer0.10-0 0.10.36-1ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-5.10-generic 3.8.0-rc6 Uname: Linux 3.8.0-5-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.8-0ubuntu4 Architecture: amd64 Date: Wed Feb 13 13:44:06 2013 InstallationDate: Installed on 2010-09-17 (880 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gstreamer0.10 UpgradeStatus: Upgraded to raring on 2013-01-25 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/1124408/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1124449] [NEW] Incorrect playback of 1080p movie from phone
Public bug reported: I took the attached movie of my unity desktop using my phone's camera. The top half of the movie renders properly in totem, but the bottom half is blurred and does not draw correctly. It looks like the bottom half of the movie is really a single row of pixels that's been scaled vertically (see the attached screenshot). To reproduce: 1) Play back the attached movie in totem Expected results: The movie plays normally Actual results: The bottom half of the movie is either decoded or rendered incorrectly. Playback from gst-launch works fine: ~$ gst-launch-0.10 playbin uri=file:///home/steve/Desktop/IMG_1433.MOV Other movies seem to play fine; I'm not sure what's special about this one. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: libgstreamer0.10-0 0.10.36-1ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-5.10-generic 3.8.0-rc6 Uname: Linux 3.8.0-5-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.8-0ubuntu4 Architecture: amd64 Date: Wed Feb 13 14:23:01 2013 InstallationDate: Installed on 2010-09-17 (880 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gstreamer0.10 UpgradeStatus: Upgraded to raring on 2013-01-25 (19 days ago) ** Affects: gstreamer0.10 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring running-unity ** Attachment added: IMG_1433.MOV https://bugs.launchpad.net/bugs/1124449/+attachment/3527185/+files/IMG_1433.MOV -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer0.10 in Ubuntu. https://bugs.launchpad.net/bugs/1124449 Title: Incorrect playback of 1080p movie from phone Status in “gstreamer0.10” package in Ubuntu: New Bug description: I took the attached movie of my unity desktop using my phone's camera. The top half of the movie renders properly in totem, but the bottom half is blurred and does not draw correctly. It looks like the bottom half of the movie is really a single row of pixels that's been scaled vertically (see the attached screenshot). To reproduce: 1) Play back the attached movie in totem Expected results: The movie plays normally Actual results: The bottom half of the movie is either decoded or rendered incorrectly. Playback from gst-launch works fine: ~$ gst-launch-0.10 playbin uri=file:///home/steve/Desktop/IMG_1433.MOV Other movies seem to play fine; I'm not sure what's special about this one. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: libgstreamer0.10-0 0.10.36-1ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-5.10-generic 3.8.0-rc6 Uname: Linux 3.8.0-5-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.8-0ubuntu4 Architecture: amd64 Date: Wed Feb 13 14:23:01 2013 InstallationDate: Installed on 2010-09-17 (880 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gstreamer0.10 UpgradeStatus: Upgraded to raring on 2013-01-25 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/1124449/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1124449] Re: Incorrect playback of 1080p movie from phone
** Attachment added: Screenshot showing blurred playback https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/1124449/+attachment/3527193/+files/blurry-totem.png ** Also affects: totem (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer0.10 in Ubuntu. https://bugs.launchpad.net/bugs/1124449 Title: Incorrect playback of 1080p movie from phone Status in “gstreamer0.10” package in Ubuntu: New Status in “totem” package in Ubuntu: New Bug description: I took the attached movie of my unity desktop using my phone's camera. The top half of the movie renders properly in totem, but the bottom half is blurred and does not draw correctly. It looks like the bottom half of the movie is really a single row of pixels that's been scaled vertically (see the attached screenshot). To reproduce: 1) Play back the attached movie in totem Expected results: The movie plays normally Actual results: The bottom half of the movie is either decoded or rendered incorrectly. Playback from gst-launch works fine: ~$ gst-launch-0.10 playbin uri=file:///home/steve/Desktop/IMG_1433.MOV Other movies seem to play fine; I'm not sure what's special about this one. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: libgstreamer0.10-0 0.10.36-1ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-5.10-generic 3.8.0-rc6 Uname: Linux 3.8.0-5-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.8-0ubuntu4 Architecture: amd64 Date: Wed Feb 13 14:23:01 2013 InstallationDate: Installed on 2010-09-17 (880 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gstreamer0.10 UpgradeStatus: Upgraded to raring on 2013-01-25 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/1124449/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1123492] [NEW] LibreOffice menus missing from global menu bar
Public bug reported: In 13.04, opening a libreoffice document on my system reliably results in a missing global menubar. I think this is a regression of bug 1064962 - I believe the menubar was working in 12.10 (with quantal-proposed) and in earlier versions of 13.04. I can reproduce this by: * Opening a doc from the command line: ~$ libreoffice /path/to/foo.ods * Opening a doc from Nautilus by double-clicking on the doc * Opening a doc attached to a mail in Thunderbird, by selecting LibreOffice (Calc) from the Opening dialog that appears when you click on an attachment. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: libreoffice-base-core 1:3.6.2~rc2-0ubuntu6 ProcVersionSignature: Ubuntu 3.8.0-5.10-generic 3.8.0-rc6 Uname: Linux 3.8.0-5-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.8-0ubuntu4 Architecture: amd64 Date: Tue Feb 12 16:14:07 2013 InstallationDate: Installed on 2010-09-17 (879 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to raring on 2013-01-25 (18 days ago) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring running-unity -- 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/1123492 Title: LibreOffice menus missing from global menu bar Status in “libreoffice” package in Ubuntu: New Bug description: In 13.04, opening a libreoffice document on my system reliably results in a missing global menubar. I think this is a regression of bug 1064962 - I believe the menubar was working in 12.10 (with quantal- proposed) and in earlier versions of 13.04. I can reproduce this by: * Opening a doc from the command line: ~$ libreoffice /path/to/foo.ods * Opening a doc from Nautilus by double-clicking on the doc * Opening a doc attached to a mail in Thunderbird, by selecting LibreOffice (Calc) from the Opening dialog that appears when you click on an attachment. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: libreoffice-base-core 1:3.6.2~rc2-0ubuntu6 ProcVersionSignature: Ubuntu 3.8.0-5.10-generic 3.8.0-rc6 Uname: Linux 3.8.0-5-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.8-0ubuntu4 Architecture: amd64 Date: Tue Feb 12 16:14:07 2013 InstallationDate: Installed on 2010-09-17 (879 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: Upgraded to raring on 2013-01-25 (18 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1123492/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 998278] Re: Can't read Debian changelog
The bug is still present in 13.04 with libreoffice 1:3.6.2~rc2-0ubuntu6 -- 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/998278 Title: Can't read Debian changelog Status in “libreoffice” package in Ubuntu: Confirmed Bug description: $ zless /usr/share/doc/libreoffice-gtk/changelog.Debian.gz gzip: /usr/share/doc/libreoffice-gtk/changelog.Debian.gz: Too many levels of symbolic links /usr/share/doc/libreoffice-gtk/changelog.Debian.gz: Too many levels of symbolic links $ ls -l /usr/share/doc/libreoffice-gtk/changelog.Debian.gz lrwxrwxrwx 1 root root 32 May 2 20:25 /usr/share/doc/libreoffice-gtk/changelog.Debian.gz - ../uno-libs3/changelog.Debian.gz $ ls -l /usr/share/doc/uno-libs3/changelog.Debian.gz lrwxrwxrwx 1 root root 26 May 2 20:25 /usr/share/doc/uno-libs3/changelog.Debian.gz - ../ure/changelog.Debian.gz $ ls -l /usr/share/doc/ure/changelog.Debian.gz lrwxrwxrwx 1 root root 26 May 2 20:25 /usr/share/doc/ure/changelog.Debian.gz - ../ure/changelog.Debian.gz ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: ure 3.5.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Sat May 12 00:59:29 2012 InstallationMedia: Ubuntu 10.04.3 LTS Lucid Lynx - Release amd64 (20110720.1) SourcePackage: libreoffice UpgradeStatus: Upgraded to precise on 2012-03-16 (56 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/998278/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1119700] [NEW] Crash in libglobalmenu.so while accessing GDocs
Public bug reported: The firefox-globalmenu regularly (3 times in just over an hour) crashes Firefox while I'm trying to work in a Google Doc. This affects word processing docs and spreadsheets. The crashes are seemingly random - I get them while editing text, scrolling the page, or performing an operation like refreshing a table of contents within a document. Sample crash reports: https://crash-stats.mozilla.com/report/index/bp-4600c678-575d-4a12-af26-7ebe62130208 https://crash-stats.mozilla.com/report/index/bp-3c5752d1-af48-4abf-ab59-1e0052130208 https://crash-stats.mozilla.com/report/index/bp-24dfd44e-ef6e-42ae-a657-bec6e2130208 The signature in in Mozilla's crash DB is 'libglobalmenu.so@0xa772' This problem occurred in Firefox 18 on 12.10, and it remains in FF19 on 13.04 ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: firefox 19.0~b5+build1-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-4.8-generic 3.8.0-rc6 Uname: Linux 3.8.0-4-generic x86_64 NonfreeKernelModules: nvidia AddonCompatCheckDisabled: False ApportVersion: 2.8-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steve 2237 F pulseaudio BuildID: 20130206204007 Channel: Unavailable Date: Fri Feb 8 14:40:41 2013 ForcedLayersAccel: False IfupdownConfig: auto lo iface lo inet loopback InstallationDate: Installed on 2010-09-17 (875 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1) IpRoute: default via 192.168.3.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.3.0/24 dev wlan0 proto kernel scope link src 192.168.3.119 metric 9 MarkForUpload: True MostRecentCrashID: bp-4600c678-575d-4a12-af26-7ebe62130208 Plugins: iTunes Application Detector - /usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so (rhythmbox-mozilla) Google Talk Plugin Video Accelerator - /opt/google/talkplugin/libnpgtpo3dautoplugin.so (google-talkplugin) Google Talk Plugin - /opt/google/talkplugin/libnpgoogletalk.so (google-talkplugin) Shockwave Flash - /usr/lib/mozilla/plugins/libflashplayer.so HP Virtual Rooms Plug-in - [HomeDir]/.mozilla/plugins/hpvirtualrooms-plugin.so PrefSources: prefs.js ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=19.0/20130206204007 (In use) RelatedPackageVersions: rhythmbox-mozilla 2.98-0ubuntu3 google-talkplugin 3.10.2.0-1 RfKill: 3: phy3: Wireless LAN Soft blocked: no Hard blocked: no RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: Upgraded to raring on 2013-01-25 (14 days ago) dmi.bios.date: 03/05/08 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP31.88Z.0070.B07.0803051658 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F4238BC8 dmi.board.vendor: Apple Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 2 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F4238BC8 dmi.modalias: dmi:bvnAppleInc.:bvrMBP31.88Z.0070.B07.0803051658:bd03/05/08:svnAppleInc.:pnMacBookPro3,1:pvr1.0:rvnAppleInc.:rnMac-F4238BC8:rvrPVT:cvnAppleInc.:ct2:cvrMac-F4238BC8: dmi.product.name: MacBookPro3,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring running-unity -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1119700 Title: Crash in libglobalmenu.so while accessing GDocs Status in “firefox” package in Ubuntu: New Bug description: The firefox-globalmenu regularly (3 times in just over an hour) crashes Firefox while I'm trying to work in a Google Doc. This affects word processing docs and spreadsheets. The crashes are seemingly random - I get them while editing text, scrolling the page, or performing an operation like refreshing a table of contents within a document. Sample crash reports: https://crash-stats.mozilla.com/report/index/bp-4600c678-575d-4a12-af26-7ebe62130208 https://crash-stats.mozilla.com/report/index/bp-3c5752d1-af48-4abf-ab59-1e0052130208 https://crash-stats.mozilla.com/report/index/bp-24dfd44e-ef6e-42ae-a657-bec6e2130208 The signature in in Mozilla's crash DB is 'libglobalmenu.so@0xa772' This problem occurred in Firefox 18 on 12.10, and it remains in FF19 on 13.04 ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: firefox 19.0~b5+build1-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-4.8-generic 3.8.0-rc6 Uname: Linux 3.8.0-4-generic x86_64 NonfreeKernelModules: nvidia AddonCompatCheckDisabled: False ApportVersion: 2.8-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steve 2237 F pulseaudio BuildID: 20130206204007 Channel: Unavailable Date: Fri Feb 8
[Desktop-packages] [Bug 1041432] Re: Any application which uses v4l2src element can be froze when recording video (e.x. cheese)
@Seb: The 'LTS backport stack' is the quantal kernel + xorg that was backported to precise for hardware enablement. The packages in the lts backport stack include linux-lts-quantal and xserver-org-lts-quantal. The bug can occur when that backport stack is used with a precise userspace. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-good0.10 in Ubuntu. https://bugs.launchpad.net/bugs/1041432 Title: Any application which uses v4l2src element can be froze when recording video (e.x. cheese) Status in Cheese Camera Application: Unknown Status in GStreamer Plugins (Good): Unknown Status in OEM Priority Project: In Progress Status in OEM Priority Project precise series: In Progress Status in OEM Priority Project quantal series: In Progress Status in OEM Priority Project raring series: In Progress Status in “cheese” package in Ubuntu: Invalid Status in “gst-plugins-good0.10” package in Ubuntu: Triaged Bug description: This is a bug in gstreamer-plugins-good. -- Quantal 3.5.0-11 becomes totally unresponsive when starting a video from the built in webcam. Both mouse and keyboard are frozen. I tried both 32 and 64 bit versions of both cheese and camorama and the result was the same. This was not an issue with Precise. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: cheese 3.5.5-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-11.11-generic 3.5.2 Uname: Linux 3.5.0-11-generic i686 NonfreeKernelModules: wl ApportVersion: 2.5.1-0ubuntu2 Architecture: i386 Date: Fri Aug 24 21:57:00 2012 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) SourcePackage: cheese UpgradeStatus: Upgraded to quantal on 2012-08-17 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/cheese/+bug/1041432/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1095823] Re: Incorrect path for oem descriptor
** Changed in: oem-priority/precise Status: New = Fix Committed ** Changed in: oem-priority Status: New = Fix Committed -- 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/1095823 Title: Incorrect path for oem descriptor Status in OEM Priority Project: Fix Committed Status in OEM Priority Project precise series: Fix Committed Status in “software-center” package in Ubuntu: Fix Released Status in “software-center” source package in Precise: Fix Committed Status in “software-center” source package in Quantal: Fix Committed Bug description: Recent versions of SW Center include the Distribution Channel Descriptor in the user agent string passed to the server. This feature was introduced for bug 1042749. However the original implementation used an incorrect path and the DCD information will never be passed to SW Center. The DCD is referred to as the oem channel descriptor in SW Center. The spec for the DCD is here: https://wiki.ubuntu.com/FoundationsTeam/Specs/OemTrackingId = Test Case = grep OEM_CHANNEL /usr/share/software-center/softwarecenter/paths.py The affected file is /usr/share/software- center/softwarecenter/paths.py Incorrect: # OEM OEM_CHANNEL_DESCRIPTOR = /var/lib/ubuntu-dist-channel Correct (change hyphens to underscores): # OEM OEM_CHANNEL_DESCRIPTOR = /var/lib/ubuntu_dist_channel The problem was introduced in this branch: https://code.launchpad.net/~mvo/software-center/oem-descriptor-in-user-agent-5.2 Note that the tests in that branch use the correct path, but the path in OEM_CHANNEL_DESCRIPTOR is incorrect. The following versions of sw center contain the bug: precise: 5.2.7 quantal: 5.4.1.2 I believe the bug is in raring too. Please SRU a fix to precise and quantal. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1095823/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1095823] Re: Incorrect path for oem descriptor
The updated path is correct in software-center 5.4.1.4 from quantal- proposed ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-center in Ubuntu. https://bugs.launchpad.net/bugs/1095823 Title: Incorrect path for oem descriptor Status in OEM Priority Project: Fix Committed Status in OEM Priority Project precise series: Fix Committed Status in “software-center” package in Ubuntu: Fix Released Status in “software-center” source package in Precise: Fix Committed Status in “software-center” source package in Quantal: Fix Committed Bug description: Recent versions of SW Center include the Distribution Channel Descriptor in the user agent string passed to the server. This feature was introduced for bug 1042749. However the original implementation used an incorrect path and the DCD information will never be passed to SW Center. The DCD is referred to as the oem channel descriptor in SW Center. The spec for the DCD is here: https://wiki.ubuntu.com/FoundationsTeam/Specs/OemTrackingId = Test Case = grep OEM_CHANNEL /usr/share/software-center/softwarecenter/paths.py The affected file is /usr/share/software- center/softwarecenter/paths.py Incorrect: # OEM OEM_CHANNEL_DESCRIPTOR = /var/lib/ubuntu-dist-channel Correct (change hyphens to underscores): # OEM OEM_CHANNEL_DESCRIPTOR = /var/lib/ubuntu_dist_channel The problem was introduced in this branch: https://code.launchpad.net/~mvo/software-center/oem-descriptor-in-user-agent-5.2 Note that the tests in that branch use the correct path, but the path in OEM_CHANNEL_DESCRIPTOR is incorrect. The following versions of sw center contain the bug: precise: 5.2.7 quantal: 5.4.1.2 I believe the bug is in raring too. Please SRU a fix to precise and quantal. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1095823/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1110528] [NEW] Properties menu item not functional
Public bug reported: The Properties item in the Movie menu does nothing. To reproduce: 1) Launch totem. For example run `totem /usr/share/example-content/Ubuntu_Free_Culture_Showcase/How\ fast.ogg` from a shell 2) Select Properties from the Movie menu Expected results: A properties window opens, or a properties pane is displayed in the sidebar (similar to the way the playlists are displayed in the sidebar) Actual results: Nothing happens If you run totem from a terminal, you'll see this when invoking the properties menu item: Totem-WARNING **: Tried to set sidebar page 'properties' but it does not exist ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: totem 3.6.3-0ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-2.6-generic 3.8.0-rc4 Uname: Linux 3.8.0-2-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.8-0ubuntu2 Architecture: amd64 Date: Wed Jan 30 10:55:38 2013 InstallationDate: Installed on 2010-09-17 (866 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: totem UpgradeStatus: Upgraded to raring on 2013-01-25 (5 days ago) ** Affects: totem (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring running-unity -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1110528 Title: Properties menu item not functional Status in “totem” package in Ubuntu: New Bug description: The Properties item in the Movie menu does nothing. To reproduce: 1) Launch totem. For example run `totem /usr/share/example-content/Ubuntu_Free_Culture_Showcase/How\ fast.ogg` from a shell 2) Select Properties from the Movie menu Expected results: A properties window opens, or a properties pane is displayed in the sidebar (similar to the way the playlists are displayed in the sidebar) Actual results: Nothing happens If you run totem from a terminal, you'll see this when invoking the properties menu item: Totem-WARNING **: Tried to set sidebar page 'properties' but it does not exist ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: totem 3.6.3-0ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-2.6-generic 3.8.0-rc4 Uname: Linux 3.8.0-2-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.8-0ubuntu2 Architecture: amd64 Date: Wed Jan 30 10:55:38 2013 InstallationDate: Installed on 2010-09-17 (866 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: totem UpgradeStatus: Upgraded to raring on 2013-01-25 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1110528/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1109251] [NEW] pidgin hangs on startup
Public bug reported: After upgrading to a recent set of bits in raring, pidgin reliably hangs on startup. This is a regression from 12.10. To reproduce: 1) Launch pidgin Expected results: The Buddy List window loads a list of buddies (IRC channels in my case), and pidgin opens a new chat window to auto-join a set of IRC channels Actual results: The Buddy List window is created but it's completely blank - there is no content at all, not even the account status popup menu. The OS greys out the Buddy List window. Pidgin is completely unresponsive. GDB shows pidgin is hung in purple_gnome_proxy_get_parameter: Thread 1 (Thread 0x7f3629f809c0 (LWP 2713)): #0 0x7f362681339d in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f362738b87c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f362738bd52 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f36273cd3e1 in g_spawn_sync () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f36273cd858 in g_spawn_command_line_sync () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f36270942ad in purple_gnome_proxy_get_parameter (gnome_version=optimized out, parameter=optimized out) at /build/buildd/pidgin-2.10.6/./libpurple/proxy.c:270 #6 purple_gnome_proxy_get_parameter (parameter=optimized out, gnome_version=optimized out) at /build/buildd/pidgin-2.10.6/./libpurple/proxy.c:260 #7 0x7f3627094920 in purple_gnome_proxy_get_info () at /build/buildd/pidgin-2.10.6/./libpurple/proxy.c:307 #8 purple_proxy_get_setup (account=optimized out) at /build/buildd/pidgin-2.10.6/./libpurple/proxy.c:2257 #9 0x7f36270a5102 in initiate_resolving (data=0x7f362bdf6040) at /build/buildd/pidgin-2.10.6/./libpurple/dnsquery.c:896 #10 0x7f362738c1ab in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #11 0x7f362738b5a5 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x7f362738b8e8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #13 0x7f362738bd52 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x7f3628601f17 in gtk_main () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 #15 0x7f3629ffd119 in main (argc=1, argv=0x7fffaf9259d8) at /build/buildd/pidgin-2.10.6/./pidgin/gtkmain.c:933 ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: pidgin 1:2.10.6-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-2.6-generic 3.8.0-rc4 Uname: Linux 3.8.0-2-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.8-0ubuntu2 Architecture: amd64 Date: Tue Jan 29 15:13:17 2013 InstallationDate: Installed on 2010-09-17 (865 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pidgin UpgradeStatus: Upgraded to raring on 2013-01-25 (4 days ago) ** Affects: pidgin (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring running-unity -- 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/1109251 Title: pidgin hangs on startup Status in “pidgin” package in Ubuntu: New Bug description: After upgrading to a recent set of bits in raring, pidgin reliably hangs on startup. This is a regression from 12.10. To reproduce: 1) Launch pidgin Expected results: The Buddy List window loads a list of buddies (IRC channels in my case), and pidgin opens a new chat window to auto-join a set of IRC channels Actual results: The Buddy List window is created but it's completely blank - there is no content at all, not even the account status popup menu. The OS greys out the Buddy List window. Pidgin is completely unresponsive. GDB shows pidgin is hung in purple_gnome_proxy_get_parameter: Thread 1 (Thread 0x7f3629f809c0 (LWP 2713)): #0 0x7f362681339d in poll () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f362738b87c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f362738bd52 in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f36273cd3e1 in g_spawn_sync () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f36273cd858 in g_spawn_command_line_sync () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f36270942ad in purple_gnome_proxy_get_parameter (gnome_version=optimized out, parameter=optimized out) at /build/buildd/pidgin-2.10.6/./libpurple/proxy.c:270 #6 purple_gnome_proxy_get_parameter (parameter=optimized out, gnome_version=optimized out) at /build/buildd/pidgin-2.10.6/./libpurple/proxy.c:260 #7 0x7f3627094920 in purple_gnome_proxy_get_info () at /build/buildd/pidgin-2.10.6/./libpurple/proxy.c:307 #8 purple_proxy_get_setup (account=optimized out) at /build/buildd/pidgin-2.10.6/./libpurple/proxy.c:2257 #9
[Desktop-packages] [Bug 1041432] Re: cheese and camorama freeze system when recording video
Added precise task because this may affect the lts backport stack on precise ** Also affects: oem-priority/precise Importance: Undecided Status: New ** Changed in: oem-priority/precise Importance: Undecided = High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1041432 Title: cheese and camorama freeze system when recording video Status in Cheese Camera Application: Unknown Status in OEM Priority Project: New Status in OEM Priority Project precise series: New Status in OEM Priority Project quantal series: New Status in OEM Priority Project r-series series: New Status in “cheese” package in Ubuntu: Confirmed Bug description: Quantal 3.5.0-11 becomes totally unresponsive when starting a video from the built in webcam. Both mouse and keyboard are frozen. I tried both 32 and 64 bit versions of both cheese and camorama and the result was the same. This was not an issue with Precise. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: cheese 3.5.5-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-11.11-generic 3.5.2 Uname: Linux 3.5.0-11-generic i686 NonfreeKernelModules: wl ApportVersion: 2.5.1-0ubuntu2 Architecture: i386 Date: Fri Aug 24 21:57:00 2012 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) SourcePackage: cheese UpgradeStatus: Upgraded to quantal on 2012-08-17 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/cheese/+bug/1041432/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1095823] Re: Incorrect path for oem descriptor
The updated path is correct in software-center 5.2.9 from precise- proposed ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-center in Ubuntu. https://bugs.launchpad.net/bugs/1095823 Title: Incorrect path for oem descriptor Status in OEM Priority Project: New Status in OEM Priority Project precise series: New Status in “software-center” package in Ubuntu: Fix Released Status in “software-center” source package in Precise: Fix Committed Status in “software-center” source package in Quantal: In Progress Bug description: Recent versions of SW Center include the Distribution Channel Descriptor in the user agent string passed to the server. This feature was introduced for bug 1042749. However the original implementation used an incorrect path and the DCD information will never be passed to SW Center. The DCD is referred to as the oem channel descriptor in SW Center. The spec for the DCD is here: https://wiki.ubuntu.com/FoundationsTeam/Specs/OemTrackingId = Test Case = grep OEM_CHANNEL /usr/share/software-center/softwarecenter/paths.py The affected file is /usr/share/software- center/softwarecenter/paths.py Incorrect: # OEM OEM_CHANNEL_DESCRIPTOR = /var/lib/ubuntu-dist-channel Correct (change hyphens to underscores): # OEM OEM_CHANNEL_DESCRIPTOR = /var/lib/ubuntu_dist_channel The problem was introduced in this branch: https://code.launchpad.net/~mvo/software-center/oem-descriptor-in-user-agent-5.2 Note that the tests in that branch use the correct path, but the path in OEM_CHANNEL_DESCRIPTOR is incorrect. The following versions of sw center contain the bug: precise: 5.2.7 quantal: 5.4.1.2 I believe the bug is in raring too. Please SRU a fix to precise and quantal. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1095823/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1034090] Re: Hotkeys not functional after upgrade to quantal's xorg (new xinput version)
I installed the xorg LTS backport stack on a Dell XPS13 running 12.04. I confirmed that the hotkeys were not functional. I installed gnome- settings-daemon 3.4.2-0ubuntu0.6.1 from precise-proposed and rebooted. The hotkeys are now functional. Thanks! ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1034090 Title: Hotkeys not functional after upgrade to quantal's xorg (new xinput version) Status in Gnome Settings Daemon: Fix Released Status in “gnome-settings-daemon” package in Ubuntu: Fix Released Status in “gnome-settings-daemon” source package in Precise: Fix Committed Bug description: Impact: the multimedia keys will stop working when using the new xorg stack (which is being backported for hardware enablement reasons) Test Case: - install xserver-xorg-lts-quantal - try using multimedia keys (stop, play, run media player, ...) - see if they work Regression potential: Try with both the lts stack and the backported stack of those keys are working correctly - After upgrading from 12.04 to 12.10, none of the hotkeys/media keys on my keyboard are no longer functional. Specifically, the brightness up/dn, volume up/dn/mute, keyboard backlight up/dn/off keys and the media control keys (rew/play/ff) don't work perform the expected functions. I've confirmed that the underlying functionality works- for example I can adjust the keyboard backlight from the command line via: `echo 0 /sys/class/leds/smc\:\:kbd_backlight/brightness` Machine is a MacbookPro 3,1 with an external Apple USB keyboard. Hotkeys are non-functional on both the internal and external keyboards. To reproduce: 1) Press the volume mute hotkey Expected results: Mute is toggled, and the indicator + OSD are displayed reflecting the new volume state Actual results: Nothing happens xev (run from gnome terminal) reports the following when I press the volume mute hotkey: KeyPress event, serial 41, synthetic NO, window 0x401, root 0x15d, subw 0x0, time 6834066, (118,-23), root:(184,698), state 0x0, keycode 121 (keysym 0x1008ff12, XF86AudioMute), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 41, synthetic NO, window 0x401, root 0x15d, subw 0x0, time 6834162, (118,-23), root:(184,698), state 0x0, keycode 121 (keysym 0x1008ff12, XF86AudioMute), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-settings-daemon 3.4.2-0ubuntu6 ProcVersionSignature: Ubuntu 3.5.0-8.8-generic 3.5.0 Uname: Linux 3.5.0-8-generic x86_64 ApportVersion: 2.4-0ubuntu6 Architecture: amd64 Date: Tue Aug 7 13:44:02 2012 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1) ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to quantal on 2012-08-07 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1034090/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1108185] [NEW] Page up/dn keys stop working on a page
Public bug reported: Occasionally Firefox stops responding to my keyboard's page up/down keys. When this happens, it only affects a single page. Page up/down will keep working in other tabs. Reloading the page or navigating to a new page is enough to clear the problem. I can reproduce this most frequently with launchpad bug pages. When this happens, the scroll bars continue to function and so does the scroll wheel on my mouse; it's just the page up/dn keys that stop working. It's not a focus problem; clicking inside the browser window to ensure it has focus does not help. To reproduce: 1) Open a few browser tabs 2) In one tab, load a launchpad bug page like https://bugs.launchpad.net/ubuntu/+source/linux-lts-quantal/+bug/1088454 3) Use page up/down on your keyboard to scroll the page up/down Expected results: The page up/down keys scroll the page up/down Actual results: The page up/down keys have no discernable effect on the affected browser tab If I had to guess I'd say this happens on about 0.1-0.5% of the web pages I load, which is enough to see it a few times a week. I observed the problem in FF 18 on 12.10. It happens in FF 19 on 13.04 too ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: firefox 19.0~b2+build1-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4 Uname: Linux 3.8.0-1-generic x86_64 NonfreeKernelModules: nvidia AddonCompatCheckDisabled: False ApportVersion: 2.8-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steve 2350 F pulseaudio /dev/snd/pcmC0D0p: steve 2350 F...m pulseaudio BuildID: 20130117090125 Channel: Unavailable Date: Mon Jan 28 14:47:57 2013 ForcedLayersAccel: False IfupdownConfig: auto lo iface lo inet loopback InstallationDate: Installed on 2010-09-17 (864 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1) IpRoute: default via 10.0.1.1 dev wlan0 proto static 10.0.1.0/24 dev wlan0 proto kernel scope link src 10.0.1.121 metric 9 169.254.0.0/16 dev wlan0 scope link metric 1000 MarkForUpload: True MostRecentCrashID: bp-f68bddea-16ef-4f42-bc63-916352121120 Plugins: iTunes Application Detector - /usr/lib/mozilla/plugins/librhythmbox-itms-detection-plugin.so (rhythmbox-mozilla) Google Talk Plugin Video Accelerator - /opt/google/talkplugin/libnpgtpo3dautoplugin.so (google-talkplugin) Google Talk Plugin - /opt/google/talkplugin/libnpgoogletalk.so (google-talkplugin) Shockwave Flash - /usr/lib/mozilla/plugins/libflashplayer.so HP Virtual Rooms Plug-in - [HomeDir]/.mozilla/plugins/hpvirtualrooms-plugin.so PrefSources: prefs.js ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=19.0/20130117090125 (In use) RelatedPackageVersions: rhythmbox-mozilla 2.98-0ubuntu3 google-talkplugin 3.10.2.0-1 RfKill: 1: phy1: Wireless LAN Soft blocked: no Hard blocked: no RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: Upgraded to raring on 2013-01-25 (3 days ago) dmi.bios.date: 03/05/08 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP31.88Z.0070.B07.0803051658 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F4238BC8 dmi.board.vendor: Apple Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 2 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F4238BC8 dmi.modalias: dmi:bvnAppleInc.:bvrMBP31.88Z.0070.B07.0803051658:bd03/05/08:svnAppleInc.:pnMacBookPro3,1:pvr1.0:rvnAppleInc.:rnMac-F4238BC8:rvrPVT:cvnAppleInc.:ct2:cvrMac-F4238BC8: dmi.product.name: MacBookPro3,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring running-unity -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1108185 Title: Page up/dn keys stop working on a page Status in “firefox” package in Ubuntu: New Bug description: Occasionally Firefox stops responding to my keyboard's page up/down keys. When this happens, it only affects a single page. Page up/down will keep working in other tabs. Reloading the page or navigating to a new page is enough to clear the problem. I can reproduce this most frequently with launchpad bug pages. When this happens, the scroll bars continue to function and so does the scroll wheel on my mouse; it's just the page up/dn keys that stop working. It's not a focus problem; clicking inside the browser window to ensure it has focus does not help. To reproduce: 1) Open a few browser tabs 2) In one tab, load a launchpad bug page like https://bugs.launchpad.net/ubuntu/+source/linux-lts-quantal/+bug/1088454 3) Use page up/down on your keyboard to scroll the page up/down Expected results: The page up/down keys scroll the page
[Desktop-packages] [Bug 1078290] Re: Add package fglrx-experimental for tracking fglrx beta drivers
On a ThinkPad E435 running 12.04, I updated to jockey 0.9.7-0ubuntu7.7. I confirmed that the new version of jockey presents fglrx-experimental-9 and installs the package correctly. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1078290 Title: Add package fglrx-experimental for tracking fglrx beta drivers Status in “fglrx-installer” package in Ubuntu: In Progress Status in “fglrx-installer-experimental-9” package in Ubuntu: Confirmed Status in “jockey” package in Ubuntu: Invalid Status in “fglrx-installer” source package in Precise: In Progress Status in “fglrx-installer-experimental-9” source package in Precise: In Progress Status in “jockey” source package in Precise: Fix Committed Status in “fglrx-installer” source package in Quantal: In Progress Status in “fglrx-installer-experimental-9” source package in Quantal: Confirmed Status in “jockey” source package in Quantal: Invalid Status in “fglrx-installer” source package in Raring: In Progress Status in “fglrx-installer-experimental-9” source package in Raring: Confirmed Status in “jockey” source package in Raring: Invalid Bug description: [Impact] AMD posts beta versions of their drivers to be tested over several weeks. These drivers usually include important features and fixes but also sometimes include known issues or regressions that make them unsuitable or too risky for us to consider inclusion in the fglrx-updates package. However certain commercial Linux games require features/fixes present only in these AMD beta drivers at the time of their release. Ubuntu users who purchase these games currently have to manually install the beta driver (or wait a month or two for it to appear in -updates). Providing these drivers via fglrx-experimental will enable them to install and run the game within the Ubuntu packaging system. [Fix] The fglrx-experimental-NNN binary package is established (provided by the fglrx-installer-experimental source package) for quantal 12.10 and precise 12.04. This uses the packaging scripts from fglrx-updates, with the renamed package and new .run files. The fglrx-experimental-NNN package will be visible to users via Jockey as normal. When a user installs the experimental package, any other fglrx drivers will be disabled. They will remain on the selected fglrx-experimental-NNN until they upgrade to a new Ubuntu release or LTS point release, at which point they'll be returned to fglrx- current. They can of course manually switch from fglrx-experimental- NNN back to fglrx or fglrx-updates (or some newer fglrx-experimental- MMM) if they wish. The control file for the experimental package proposed for precise has some differences from the one in quantal, and also has some differences against the non-experimental fglrx driver in precise. Here is an explanation of those differences in turn: * Conflicts/Replaces on fglrx-*-modaliases (from precise's fglrx package) are no longer needed. The modaliases packages were used in previous releases but no longer exist in precise. Since people can't upgrade from those previous versions directly to fglrx*experimental, there is no need to have Conflicts/Replaces. * Conflicts/Replaces/Provides of various nvidia/fglrx packages (from quantal's fglrx-experimental package) are only needed for quantal forward. These are required by the new restricted drivers UI in quantal. Since that UI is not in precise, we don't need it in precise. [Regression Potential] The reason we're adding this package in the first place is because of concerns that beta drivers will have a high risk of regressions. Thus, users need to be aware they are taking these risks when they opt-in to the driver. As mentioned above, fglrx and fglrx-updates will still be available to them in case they have problems. In a worst case scenario they may need to do this from a recovery session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1078290/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 445872] Re: disable-disconnect-notification option ignored
@James: Who is responsible for pulling the nm-applet package from precise and when will that happen? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/445872 Title: disable-disconnect-notification option ignored Status in OEM Priority Project: Fix Released Status in OEM Priority Project precise series: In Progress Status in OEM Priority Project quantal series: Fix Released Status in “network-manager-applet” package in Ubuntu: Fix Released Status in “network-manager-applet” source package in Precise: In Progress Status in “network-manager-applet” source package in Quantal: Fix Released Bug description: [Impact] For OEM's, we offer a video that runs on first boot kick things off. Invariably, nm-applet winds up printing a disconnect notification, which detracts from the quality feeling of the video. We would like to get this working in Ubuntu so for 12.04.2 we can use disable- disconnect-notification instead of our hard-coded workaround. [Test Case] The popups can be disabled by either running the following commands and then restarting or logging off / on: gconftool -s /apps/nm-applet/disable-disconnected-notifications --type=bool true gconftool -s /apps/nm-applet/disable-connected-notifications --type=bool true gconftool -s /apps/nm-applet/suppress-wireless-networks-available = true OR The following can be hard-coded into /var/lib/gconf/debian.mandatory/%gconf.xml ?xml version=1.0? gconf dir name=apps dir name=nm-applet entry name=suppress-wireless-networks-available mtime=1334087625 type=bool value=true/ entry name=disable-connected-notifications mtime=1334087553 type=bool value=true/ entry name=disable-disconnected-notifications mtime=1334087516 type=bool value=true/ /dir /dir /gconf [Regression Potential] Minimal. This change is only 2 changed lines, and we've already released in 12.10 without problems. [Original Description] the gconf key /apps/nm-applet/disable-disconnected-notifications does not disable disconnect notifications, while the other works for connected notifications. ProblemType: Bug Architecture: amd64 CRDA: Error: [Errno 2] No such file or directory Date: Thu Oct 8 00:50:27 2009 DistroRelease: Ubuntu 9.10 Gconf: IfupdownConfig: auto lo iface lo inet loopback IpRoute: 192.168.5.0/24 dev wlan0 proto kernel scope link src 192.168.5.2 metric 2 169.254.0.0/16 dev wlan0 scope link metric 1000 default via 192.168.5.1 dev wlan0 proto static Package: network-manager-gnome 0.8~a~git.20091002t194214.8515a07-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.31-12.40-generic RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager-applet Uname: Linux 2.6.31-12-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/445872/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 445872] Re: disable-disconnect-notification option ignored
@James: What is the other SRU that we're waiting on? Can you provide a link to the bug(s) for the other SRU? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/445872 Title: disable-disconnect-notification option ignored Status in OEM Priority Project: Fix Released Status in OEM Priority Project precise series: Confirmed Status in OEM Priority Project quantal series: Fix Released Status in “network-manager-applet” package in Ubuntu: Fix Released Status in “network-manager-applet” source package in Precise: In Progress Status in “network-manager-applet” source package in Quantal: Fix Released Bug description: [Impact] For OEM's, we offer a video that runs on first boot kick things off. Invariably, nm-applet winds up printing a disconnect notification, which detracts from the quality feeling of the video. We would like to get this working in Ubuntu so for 12.04.2 we can use disable- disconnect-notification instead of our hard-coded workaround. [Test Case] The popups can be disabled by either running the following commands and then restarting or logging off / on: gconftool -s /apps/nm-applet/disable-disconnected-notifications --type=bool true gconftool -s /apps/nm-applet/disable-connected-notifications --type=bool true gconftool -s /apps/nm-applet/suppress-wireless-networks-available = true OR The following can be hard-coded into /var/lib/gconf/debian.mandatory/%gconf.xml ?xml version=1.0? gconf dir name=apps dir name=nm-applet entry name=suppress-wireless-networks-available mtime=1334087625 type=bool value=true/ entry name=disable-connected-notifications mtime=1334087553 type=bool value=true/ entry name=disable-disconnected-notifications mtime=1334087516 type=bool value=true/ /dir /dir /gconf [Regression Potential] Minimal. This change is only 2 changed lines, and we've already released in 12.10 without problems. [Original Description] the gconf key /apps/nm-applet/disable-disconnected-notifications does not disable disconnect notifications, while the other works for connected notifications. ProblemType: Bug Architecture: amd64 CRDA: Error: [Errno 2] No such file or directory Date: Thu Oct 8 00:50:27 2009 DistroRelease: Ubuntu 9.10 Gconf: IfupdownConfig: auto lo iface lo inet loopback IpRoute: 192.168.5.0/24 dev wlan0 proto kernel scope link src 192.168.5.2 metric 2 169.254.0.0/16 dev wlan0 scope link metric 1000 default via 192.168.5.1 dev wlan0 proto static Package: network-manager-gnome 0.8~a~git.20091002t194214.8515a07-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.31-12.40-generic RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager-applet Uname: Linux 2.6.31-12-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/445872/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1086345] Re: Quantal-LTS-stack: Showing low-resolution screen on shutdown/reboot
** Changed in: oem-priority/precise Status: New = Fix Committed ** Changed in: oem-priority/precise Importance: Undecided = Critical -- 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/1086345 Title: Quantal-LTS-stack: Showing low-resolution screen on shutdown/reboot Status in OEM Priority Project: Fix Committed Status in OEM Priority Project precise series: Fix Committed Status in “libdrm” package in Ubuntu: Invalid Status in “lightdm” package in Ubuntu: Invalid Status in “libdrm” source package in Precise: Fix Committed Status in “lightdm” source package in Precise: Invalid Bug description: Hardware is an Hashwell SDP with an Intel SSD. Fresh install from 12.04.1 alternate image, then added the quantal-lts kernel and the x-stack (ppa:ubuntu-x-swat/q-lts-backport, pulled via xserver-xorg- lts-quantal meta package). Monitor is connected to VGA. With the new stack graphics on VGA does actually work and the system snaps from the grub-efi prompt to lightdm in a blink (2s at most which probably can be attributed to the Intel SSD). Everything is fine and the system definitely is running in a high resolution mode. However when shutting down or rebooting, the system drops into a screen telling me it is running in low-resolution mode instead of showing plymouth (or the terminal). The system will continue to shut down or reboot even without pressing the ok button, but it can be done for a bit and then would show the next screen about how to resolve the issue. I was not quick or daring enough to go on from the second screen. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: plymouth 0.8.2-2ubuntu30 ProcVersionSignature: Ubuntu 3.5.0-20.31~hswv4-generic 3.5.7 Uname: Linux 3.5.0-20-generic x86_64 ApportVersion: 2.0.1-0ubuntu15 Architecture: amd64 Date: Tue Dec 4 12:44:55 2012 DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120822.4) Lsusb: Bus 001 Device 002: ID 0b39:cd02 Omnidirectional Control Technology, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: Intel Corporation Shark Bay Client platform MarkForUpload: True ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-20-generic root=UUID=b77c2e0f-0611-4b74-9319-0c5c92b55a69 ro quiet splash ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-20-generic root=UUID=b77c2e0f-0611-4b74-9319-0c5c92b55a69 ro quiet splash SourcePackage: plymouth TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/05/2012 dmi.bios.vendor: Intel Corporation dmi.bios.version: HSWLPTU1.86C.0086.R00.1208052028 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Flathead Creek Crb dmi.board.vendor: Intel Corp. dmi.board.version: 1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnIntelCorporation:bvrHSWLPTU1.86C.0086.R00.1208052028:bd08/05/2012:svnIntelCorporation:pnSharkBayClientplatform:pvr0.1:rvnIntelCorp.:rnFlatheadCreekCrb:rvr1:cvnIntelCorporation:ct3:cvr0.1: dmi.product.name: Shark Bay Client platform dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1086345/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1080588] Re: jockey suggests not installable packages on renamed stack
** Also affects: oem-priority/precise Importance: Undecided Status: New ** Changed in: oem-priority/precise Importance: Undecided = High ** Changed in: oem-priority/precise Status: New = In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1080588 Title: jockey suggests not installable packages on renamed stack Status in OEM Priority Project: In Progress Status in OEM Priority Project precise series: In Progress Status in “fglrx-installer-experimental-9” package in Ubuntu: New Status in “fglrx-installer-updates” package in Ubuntu: In Progress Status in “jockey” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-173-updates” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-experimental-310” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-updates” package in Ubuntu: In Progress Status in “fglrx-installer-experimental-9” source package in Precise: In Progress Status in “fglrx-installer-updates” source package in Precise: In Progress Status in “jockey” source package in Precise: In Progress Status in “nvidia-graphics-drivers-173-updates” source package in Precise: Fix Committed Status in “nvidia-graphics-drivers-experimental-310” source package in Precise: In Progress Status in “nvidia-graphics-drivers-updates” source package in Precise: In Progress Bug description: None of the nvidia and fglrx drivers can be installed through the gui, because they have a versioned depends on xserver-xorg-core. For example: # LANG=C apt-get install nvidia-experimental-304 The following packages have unmet dependencies: nvidia-experimental-304 : Depends: xserver-xorg-core (= 2:1.10.99.901) E: Unable to correct problems, you have held broken packages. Furthermore even some packages are shown that cannot be installed on the renamed x server, because the drivers haven't been updated to work on them. For example nvidia-current: nvidia-current : Depends: xorg-video-abi-11 Depends: xserver-xorg-core (= 2:1.10.99.901) E: Unable to correct problems, you have held broken packages. nvidia-common needs to be updated to hide versions of nvidia drivers that won't work on x 1.13 or later, and make them installable. I think the xserver-xorg-core version check can be removed, in favor of checking the video abi version. Furthermore drivers should have an alternative dependency on the new xserver To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1080588/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1100329] Re: When Firefox sets itself as default browser, all links open the Ubuntu tour
The OS on the Sputnik systems includes the ubuntu-online-tour package. This bug doesn't occur if ubuntu-online-tour is not install (or if it is purged before the user sets the default browser back to firefox). Specifically the bug doesn't occur if /usr/share/applications/ubuntu- online-tour.desktop is not present. /usr/share/applications/ubuntu- online-tour doesn't assert any MIME type associations or protocol handlers, so I suspect the problem is in firefox or GNOME rather than ubuntu-online-tour itself. ** Also affects: firefox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1100329 Title: When Firefox sets itself as default browser, all links open the Ubuntu tour Status in Dell Sputnik: Confirmed Status in “firefox” package in Ubuntu: New Bug description: To reproduce: 1) Install chromium-browser 2) Launch chromium-browser and set it to the default browser (in preferences) 3) Launch firefox and set it back to the default browser (in preferences/advanced) 4) Go to the terminal and type gvfs-open http://dell.com; (or click on a link in any external program) What happens: The Ubuntu tour opens What I expect: Dell's homepage to open More info: Looking at ~/.local/share/applications/mimeapps.list you can see that a bunch of handlers get set to ubuntu-online-tour.desktop instead of firefox.desktop. This does not affect stock Ubuntu 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1100329/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1095823] Re: Incorrect path for oem descriptor
** Also affects: oem-priority Importance: Undecided Status: New ** Also affects: oem-priority/precise Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided = Medium ** Changed in: oem-priority/precise Importance: Undecided = Medium -- 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/1095823 Title: Incorrect path for oem descriptor Status in OEM Priority Project: New Status in OEM Priority Project precise series: New Status in “software-center” package in Ubuntu: New Bug description: Recent versions of SW Center include the Distribution Channel Descriptor in the user agent string passed to the server. This feature was introduced for bug 1042749. However the original implementation used an incorrect path and the DCD information will never be passed to SW Center. The DCD is referred to as the oem channel descriptor in SW Center. The spec for the DCD is here: https://wiki.ubuntu.com/FoundationsTeam/Specs/OemTrackingId The affected file is /usr/share/software- center/softwarecenter/paths.py Incorrect: # OEM OEM_CHANNEL_DESCRIPTOR = /var/lib/ubuntu-dist-channel Correct (change hyphens to underscores): # OEM OEM_CHANNEL_DESCRIPTOR = /var/lib/ubuntu_dist_channel The problem was introduced in this branch: https://code.launchpad.net/~mvo/software-center/oem-descriptor-in-user-agent-5.2 Note that the tests in that branch use the correct path, but the path in OEM_CHANNEL_DESCRIPTOR is incorrect. The following versions of sw center contain the bug: precise: 5.2.7 quantal: 5.4.1.2 I believe the bug is in raring too. Please SRU a fix to precise and quantal. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1095823/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1034928] Re: Fontconfig warning: Having multiple values in test isn't supported and may not works as expected
@Andrea: The libreoffice bug is reproducible in 12.10 (LibreOffice version 1:3.6.2~rc2-0ubuntu4) steve@steve-laptop:~$ libreoffice Fontconfig warning: /usr/lib/libreoffice/share/fonts/truetype/fc_local.conf, line 13: Having multiple family in alias isn't supported and may not works as expected /usr/lib/libreoffice/share/fonts/truetype/fc_local.conf pretty clearly has multiple family elements nested inside alias elements: alias binding=same familyLiberation Sans Narrow/family familyArial Narrow/family default familyArial Narrow/family /default /alias I can't load the patch from paste.debian.net from above, but this should be pretty straightforward to correct. -- 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/1034928 Title: Fontconfig warning: Having multiple values in test isn't supported and may not works as expected Status in “culmus” package in Ubuntu: Fix Released Status in “fonts-arphic-ukai” package in Ubuntu: Fix Released Status in “fonts-arphic-uming” package in Ubuntu: Fix Released Status in “fonts-baekmuk” package in Ubuntu: Fix Released Status in “fonts-droid” package in Ubuntu: Fix Released Status in “fonts-nanum” package in Ubuntu: Fix Released Status in “fonts-nanum-coding” package in Ubuntu: Fix Released Status in “fonts-sil-andika” package in Ubuntu: Fix Released Status in “fonts-tlwg” package in Ubuntu: Fix Released Status in “fonts-unfonts-core” package in Ubuntu: Fix Released Status in “fonts-unfonts-extra” package in Ubuntu: Fix Released Status in “language-selector” package in Ubuntu: Fix Released Status in “libreoffice” package in Ubuntu: Triaged Status in “ttf-wqy-zenhei” package in Ubuntu: Fix Released Status in “culmus” source package in Quantal: Fix Released Status in “fonts-arphic-ukai” source package in Quantal: Fix Released Status in “fonts-arphic-uming” source package in Quantal: Fix Released Status in “fonts-baekmuk” source package in Quantal: Fix Released Status in “fonts-droid” source package in Quantal: Fix Released Status in “fonts-nanum” source package in Quantal: Fix Released Status in “fonts-nanum-coding” source package in Quantal: Fix Released Status in “fonts-sil-andika” source package in Quantal: Fix Released Status in “fonts-tlwg” source package in Quantal: Fix Released Status in “fonts-unfonts-core” source package in Quantal: Fix Released Status in “fonts-unfonts-extra” source package in Quantal: Fix Released Status in “language-selector” source package in Quantal: Fix Released Status in “libreoffice” source package in Quantal: Confirmed Status in “ttf-wqy-zenhei” source package in Quantal: Fix Released Status in “fonts-arphic-ukai” package in Debian: New Status in “fonts-arphic-uming” package in Debian: Fix Committed Status in “fonts-baekmuk” package in Debian: Fix Released Status in “fonts-droid” package in Debian: Fix Released Status in “fonts-nanum” package in Debian: Fix Released Status in “fonts-sil-andika” package in Debian: Fix Committed Status in “fonts-unfonts-core” package in Debian: Fix Released Status in “fonts-unfonts-extra” package in Debian: Fix Released Status in “ttf-wqy-zenhei” package in Debian: New Status in Fedora: Unknown Bug description: In 12.10, fontconfig prints warnings similar to the following whenever fontconfig is invoked: Fontconfig warning: /etc/fonts/conf.d/90-fonts-unfonts-core.conf, line 11: Having multiple values in test isn't supported and may not works as expected This affects fonts from a number of packages: fonts-arphic-ukai: /etc/fonts/conf.d/41-arphic-ukai.conf fonts-arphic-uming: /etc/fonts/conf.d/41-arphic-uming.conf fonts-droid: /etc/fonts/conf.d/65-droid-sans-fonts.conf fonts-tlwg-garuda: /etc/fonts/conf.d/89-tlwg-garuda-synthetic.conf fonts-tlwg-kinnari: /etc/fonts/conf.d/89-tlwg-kinnari-synthetic.conf fonts-tlwg-loma: /etc/fonts/conf.d/89-tlwg-loma-synthetic.conf fonts-tlwg-umpush: /etc/fonts/conf.d/89-tlwg-umpush-synthetic.conf fonts-nanum: /etc/fonts/conf.d/90-fonts-nanum.conf fonts-unfonts-core: /etc/fonts/conf.d/90-fonts-unfonts-core.conf [Test Case] 1) Install the fonts in question 2) Open a terminal 3) Launch 'gedit' from the terminal Expected results: gedit launches, no fontconfig warnings in the terminal Actual results: gedit launches, fontconfig warnings are displayed in the terminal [Regression Potential] In case of a regression, the font in question can be affected. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: fonts-unfonts-core 1.0.3.is.1.0.2-080608-5ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-8.8-generic 3.5.0 Uname: Linux 3.5.0-8-generic x86_64 ApportVersion: 2.4-0ubuntu6 Architecture: amd64 Date: Thu Aug 9 10:02:59 2012 Dependencies:
[Desktop-packages] [Bug 1086019] Re: cupsd crashes regularly (daily)
I reproduced again. There is a different stack trace, but it's still triggered from avahi calling into dbus_watch_handle. ** Attachment added: another stacktrace https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1086019/+attachment/3456394/+files/Stacktrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1086019 Title: cupsd crashes regularly (daily) Status in “cups” package in Ubuntu: Confirmed Bug description: Every day I get a 'System Problem Detected' dialog that says that cupsd has crashed. The symptom is similar to the one described in bug 1034045. I expected this would be fixed by cups 1.6.1-0ubuntu11, but I have that version installed and the errors persist. The test case in bug 1034045 does not result in an immediate crash of cupsd. Specifically, this does not produce a crash on my system: 1. Run 'sudo rm -f /var/crash/_usr_sbin_cupsd.0.crash' 2. Run 'sudo service cupsd restart' 3. Verify that a new /var/crash/_usr_sbin_cupsd.0.crash file has been created (and if on a desktop, that a new crash notification has been shown). ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: cups 1.6.1-0ubuntu11 ProcVersionSignature: Error: [Errno 2] No such file or directory: '/proc/version_signature' Uname: Linux 3.6.3-030603-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 CupsErrorLog: Date: Mon Dec 3 10:49:54 2012 InstallationDate: Installed on 2010-09-17 (808 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1) KernLog: Dec 3 10:41:14 steve-laptop kernel: [71466.813974] type=1400 audit(1354549274.550:29): apparmor=STATUS operation=profile_replace name=/usr/lib/cups/backend/cups-pdf pid=15433 comm=apparmor_parser Dec 3 10:41:14 steve-laptop kernel: [71466.814450] type=1400 audit(1354549274.550:30): apparmor=STATUS operation=profile_replace name=/usr/sbin/cupsd pid=15433 comm=apparmor_parser MachineType: Apple Inc. MacBookPro3,1 MarkForUpload: True Papersize: letter ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.3-030603-generic root=UUID=4b3d81ed-fb5d-4946-97c0-ec537e1bfa3f ro quiet splash SourcePackage: cups UpgradeStatus: Upgraded to quantal on 2012-08-07 (118 days ago) dmi.bios.date: 03/05/08 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP31.88Z.0070.B07.0803051658 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F4238BC8 dmi.board.vendor: Apple Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 2 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F4238BC8 dmi.modalias: dmi:bvnAppleInc.:bvrMBP31.88Z.0070.B07.0803051658:bd03/05/08:svnAppleInc.:pnMacBookPro3,1:pvr1.0:rvnAppleInc.:rnMac-F4238BC8:rvrPVT:cvnAppleInc.:ct2:cvrMac-F4238BC8: dmi.product.name: MacBookPro3,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1086019/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1086019] Re: cupsd crashes regularly (daily)
I reproduced the crash again today, this time with dbus debug symbols installed. The stack trace is attached. The stack is entirely avahi + dbus code, and the signature is very similar to other crashes reported in other applications. Looks like there might be a locking problem in the way cups uses avahi? This thread describes a similar stack trace, and has some tips about using avahi in a threaded environment: http://marc.info/?l=freedesktop-avahim=122021745832173 Comment #12 of bug 524566 shows a very similar stack (without avahi), and the remainder of the bug has additional analysis. Bug 1055060 has a crash at the same location within dbus, though the bottom of the stack is much different. ** Attachment added: stack trace w/ dbus debug symbols https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1086019/+attachment/3453990/+files/Stacktrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1086019 Title: cupsd crashes regularly (daily) Status in “cups” package in Ubuntu: New Bug description: Every day I get a 'System Problem Detected' dialog that says that cupsd has crashed. The symptom is similar to the one described in bug 1034045. I expected this would be fixed by cups 1.6.1-0ubuntu11, but I have that version installed and the errors persist. The test case in bug 1034045 does not result in an immediate crash of cupsd. Specifically, this does not produce a crash on my system: 1. Run 'sudo rm -f /var/crash/_usr_sbin_cupsd.0.crash' 2. Run 'sudo service cupsd restart' 3. Verify that a new /var/crash/_usr_sbin_cupsd.0.crash file has been created (and if on a desktop, that a new crash notification has been shown). ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: cups 1.6.1-0ubuntu11 ProcVersionSignature: Error: [Errno 2] No such file or directory: '/proc/version_signature' Uname: Linux 3.6.3-030603-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 CupsErrorLog: Date: Mon Dec 3 10:49:54 2012 InstallationDate: Installed on 2010-09-17 (808 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1) KernLog: Dec 3 10:41:14 steve-laptop kernel: [71466.813974] type=1400 audit(1354549274.550:29): apparmor=STATUS operation=profile_replace name=/usr/lib/cups/backend/cups-pdf pid=15433 comm=apparmor_parser Dec 3 10:41:14 steve-laptop kernel: [71466.814450] type=1400 audit(1354549274.550:30): apparmor=STATUS operation=profile_replace name=/usr/sbin/cupsd pid=15433 comm=apparmor_parser MachineType: Apple Inc. MacBookPro3,1 MarkForUpload: True Papersize: letter ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.3-030603-generic root=UUID=4b3d81ed-fb5d-4946-97c0-ec537e1bfa3f ro quiet splash SourcePackage: cups UpgradeStatus: Upgraded to quantal on 2012-08-07 (118 days ago) dmi.bios.date: 03/05/08 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP31.88Z.0070.B07.0803051658 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F4238BC8 dmi.board.vendor: Apple Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 2 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F4238BC8 dmi.modalias: dmi:bvnAppleInc.:bvrMBP31.88Z.0070.B07.0803051658:bd03/05/08:svnAppleInc.:pnMacBookPro3,1:pvr1.0:rvnAppleInc.:rnMac-F4238BC8:rvrPVT:cvnAppleInc.:ct2:cvrMac-F4238BC8: dmi.product.name: MacBookPro3,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1086019/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1087697] Re: /usr/sbin/cupsd:11:link_before:_dbus_list_prepend:_dbus_list_append:_dbus_validate_signature_with_reason:validate_body_helper
*** This bug is a duplicate of bug 1086019 *** https://bugs.launchpad.net/bugs/1086019 @Till: I marked this as a duplicate of bug 1086019. That bug is the same issue, and has more detail including stack trace. If you need additional data let me know, I still have the .crash file. ** This bug has been marked a duplicate of bug 1086019 cupsd crashes regularly (daily) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1087697 Title: /usr/sbin/cupsd:11:link_before:_dbus_list_prepend:_dbus_list_append:_dbus_validate_signature_with_reason:validate_body_helper Status in “apport” package in Ubuntu: New Status in “cups” package in Ubuntu: New Bug description: https://errors.ubuntu.com/bucket/?id=/usr/sbin/cupsd:11:link_before:_dbus_list_prepend:_dbus_list_append:_dbus_validate_signature_with_reason:validate_body_helper To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1087697/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1086019] [NEW] cupsd crashes regularly (daily)
Public bug reported: Every day I get a 'System Problem Detected' dialog that says that cupsd has crashed. The symptom is similar to the one described in bug 1034045. I expected this would be fixed by cups 1.6.1-0ubuntu11, but I have that version installed and the errors persist. The test case in bug 1034045 does not result in an immediate crash of cupsd. Specifically, this does not produce a crash on my system: 1. Run 'sudo rm -f /var/crash/_usr_sbin_cupsd.0.crash' 2. Run 'sudo service cupsd restart' 3. Verify that a new /var/crash/_usr_sbin_cupsd.0.crash file has been created (and if on a desktop, that a new crash notification has been shown). ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: cups 1.6.1-0ubuntu11 ProcVersionSignature: Error: [Errno 2] No such file or directory: '/proc/version_signature' Uname: Linux 3.6.3-030603-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 CupsErrorLog: Date: Mon Dec 3 10:49:54 2012 InstallationDate: Installed on 2010-09-17 (808 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1) KernLog: Dec 3 10:41:14 steve-laptop kernel: [71466.813974] type=1400 audit(1354549274.550:29): apparmor=STATUS operation=profile_replace name=/usr/lib/cups/backend/cups-pdf pid=15433 comm=apparmor_parser Dec 3 10:41:14 steve-laptop kernel: [71466.814450] type=1400 audit(1354549274.550:30): apparmor=STATUS operation=profile_replace name=/usr/sbin/cupsd pid=15433 comm=apparmor_parser MachineType: Apple Inc. MacBookPro3,1 MarkForUpload: True Papersize: letter ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.3-030603-generic root=UUID=4b3d81ed-fb5d-4946-97c0-ec537e1bfa3f ro quiet splash SourcePackage: cups UpgradeStatus: Upgraded to quantal on 2012-08-07 (118 days ago) dmi.bios.date: 03/05/08 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP31.88Z.0070.B07.0803051658 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F4238BC8 dmi.board.vendor: Apple Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 2 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F4238BC8 dmi.modalias: dmi:bvnAppleInc.:bvrMBP31.88Z.0070.B07.0803051658:bd03/05/08:svnAppleInc.:pnMacBookPro3,1:pvr1.0:rvnAppleInc.:rnMac-F4238BC8:rvrPVT:cvnAppleInc.:ct2:cvrMac-F4238BC8: dmi.product.name: MacBookPro3,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug quantal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1086019 Title: cupsd crashes regularly (daily) Status in “cups” package in Ubuntu: New Bug description: Every day I get a 'System Problem Detected' dialog that says that cupsd has crashed. The symptom is similar to the one described in bug 1034045. I expected this would be fixed by cups 1.6.1-0ubuntu11, but I have that version installed and the errors persist. The test case in bug 1034045 does not result in an immediate crash of cupsd. Specifically, this does not produce a crash on my system: 1. Run 'sudo rm -f /var/crash/_usr_sbin_cupsd.0.crash' 2. Run 'sudo service cupsd restart' 3. Verify that a new /var/crash/_usr_sbin_cupsd.0.crash file has been created (and if on a desktop, that a new crash notification has been shown). ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: cups 1.6.1-0ubuntu11 ProcVersionSignature: Error: [Errno 2] No such file or directory: '/proc/version_signature' Uname: Linux 3.6.3-030603-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 CupsErrorLog: Date: Mon Dec 3 10:49:54 2012 InstallationDate: Installed on 2010-09-17 (808 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1) KernLog: Dec 3 10:41:14 steve-laptop kernel: [71466.813974] type=1400 audit(1354549274.550:29): apparmor=STATUS operation=profile_replace name=/usr/lib/cups/backend/cups-pdf pid=15433 comm=apparmor_parser Dec 3 10:41:14 steve-laptop kernel: [71466.814450] type=1400 audit(1354549274.550:30): apparmor=STATUS operation=profile_replace name=/usr/sbin/cupsd pid=15433 comm=apparmor_parser MachineType: Apple Inc. MacBookPro3,1 MarkForUpload: True Papersize: letter ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.3-030603-generic root=UUID=4b3d81ed-fb5d-4946-97c0-ec537e1bfa3f ro quiet splash SourcePackage: cups UpgradeStatus: Upgraded to quantal on 2012-08-07 (118 days ago) dmi.bios.date: 03/05/08 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP31.88Z.0070.B07.0803051658 dmi.board.asset.tag:
[Desktop-packages] [Bug 950160] Re: Unity blocks other programs from binding globally to Super+* (* = any key)
@Daniel: The user never touches the super key in the scenarios we care most about; the user only presses the display switch hotkeys on the laptop. Maybe this is not relevant, and reducing the timeout in Unity will still help. It seems like an important detail though. Note that in our testing in comment #86, the dash still opens if you hold the 'F1' for ~1 second - it does not have to be a quick tap. -- 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/950160 Title: Unity blocks other programs from binding globally to Super+* (* = any key) Status in Compiz: Fix Committed Status in Compiz 0.9.8 series: In Progress Status in Compiz Core: Confirmed Status in Gnome Settings Daemon: Fix Released Status in OEM Priority Project: In Progress Status in OEM Priority Project precise series: In Progress Status in Unity: Fix Committed Status in Unity 5.0 series: Triaged Status in Unity 6.0 series: In Progress Status in “compiz” package in Ubuntu: Fix Committed Status in “gnome-settings-daemon” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: In Progress Status in “compiz” source package in Precise: Triaged Status in “gnome-settings-daemon” source package in Precise: Fix Released Status in “unity” source package in Precise: Triaged Status in “compiz” source package in Quantal: Triaged Status in “gnome-settings-daemon” source package in Quantal: Fix Released Status in “unity” source package in Quantal: In Progress Bug description: WORKAROUND 1: Run CCSM and under Ubuntu Unity Plugin change the key binding for Key to show the launcher to something else (e.g. Super+U). Then log out and in again. As long as no compiz plugin is bound to the single Super key any more, compiz will no longer block other apps from binding to Super+other_keys. WORKAROUND 2: 1. Write a script or figure out the command to do the action you want. 2. Run ccsm. 3. Enable the Commands plugin 4. In the Commands settings, fill in the command line you want and bind it to key Super+P. Now Unity will run your specified command on Super+P, but still handle the Super key as usual. [Precise SRU Justification] [Impact] Any shortcut with Super, Hyper, Meta virtual modifiers does not work [Test Case] Attach an external monitor to the laptop, press Super+P, it should do the video switch as this function is implemented in gnome-settings-daemon. A patch in comment #12 is now accepted upstream and a test package with that patch is available in comment #14. From the test result, the patch at least fixes Unity-2D. [Regression Potential] The patch is accepted upstream and is also cherry-picked in the gnome-3-4 branch of g-s-d git tree. g-s-d version in Precise is 3.4.2. So the risk of regression should be rather low. [Other] I prepare a debdiff in comment #31 for convenience. I hope the patch can be in both Quantal and Precise. ORIGINAL DESCRIPTION: Using : 12.04 Beta 1, updated. and Unity. In 11.10 clicking: - the function key (Fn) + (F1) allowed to switch between the laptop screen and the external monitor. After upgrading to 12.04 this no more works and instead I get an unexpected behavior: see the video. https://www.youtube.com/watch?v=-vEnrV5TwXo System: Dell XPS 15 L502X ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: ubuntu-sso-client 2.99.90-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9 Uname: Linux 3.2.0-18-generic x86_64 ApportVersion: 1.94.1-0ubuntu1 Architecture: amd64 Date: Thu Mar 8 19:18:42 2012 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) PackageArchitecture: all SourcePackage: ubuntu-sso-client UpgradeStatus: Upgraded to precise on 2012-03-02 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/950160/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 950160] Re: Unity blocks other programs from binding globally to Super+* (* = any key)
There is a fix in testing here: https://launchpad.net/~timo-jyrinki/+archive/quantal-compiz-unity-testing (ppa:timo-jyrinki/quantal-compiz-unity-testing). My findings: I tested the packages in the PPA on a Dell XPS13 with 12.04 and all of the latest updates from precise-updates. My findings: 1) The display switch hotkey now works; pressing it cycles through video modes as expected. The 'p' character is not emitted. 2) A side effect of the fix is that the dash opens when you press the display switch hotkey I think the side effect needs to be fixed. Some more information about the side effect: * The display switch hotkey is Fn-F1 * If you press Fn-F1 and release both Fn and F1 at the same time, the dash opens * If you press Fn-F1 and release F1 before releasing Fn, the the dash does not open * If you press Fn-F1 and release Fn before releasing F1, the dash opens * If you press Fn-F1 and do not release either key, the Unity keyboard shortcuts window opens The packages I tested from the PPA were: compiz 1:0.9.7.8+bzr3121-0ubuntu2~test1 unity 5.18.0-0ubuntu2~test1 and the corresponding versions of libunity-core-5.0-5, unity-common, unity-services, compiz-core, compiz-gnome, and compiz-plugins-default -- 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/950160 Title: Unity blocks other programs from binding globally to Super+* (* = any key) Status in Compiz: Fix Committed Status in Compiz 0.9.8 series: In Progress Status in Compiz Core: Confirmed Status in Gnome Settings Daemon: Fix Released Status in OEM Priority Project: In Progress Status in OEM Priority Project precise series: In Progress Status in Unity: Fix Committed Status in Unity 5.0 series: Triaged Status in Unity 6.0 series: In Progress Status in “compiz” package in Ubuntu: Fix Committed Status in “gnome-settings-daemon” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: In Progress Status in “compiz” source package in Precise: Triaged Status in “gnome-settings-daemon” source package in Precise: Fix Released Status in “unity” source package in Precise: Triaged Status in “compiz” source package in Quantal: Triaged Status in “gnome-settings-daemon” source package in Quantal: Fix Released Status in “unity” source package in Quantal: In Progress Bug description: WORKAROUND 1: Run CCSM and under Ubuntu Unity Plugin change the key binding for Key to show the launcher to something else (e.g. Super+U). Then log out and in again. As long as no compiz plugin is bound to the single Super key any more, compiz will no longer block other apps from binding to Super+other_keys. WORKAROUND 2: 1. Write a script or figure out the command to do the action you want. 2. Run ccsm. 3. Enable the Commands plugin 4. In the Commands settings, fill in the command line you want and bind it to key Super+P. Now Unity will run your specified command on Super+P, but still handle the Super key as usual. [Precise SRU Justification] [Impact] Any shortcut with Super, Hyper, Meta virtual modifiers does not work [Test Case] Attach an external monitor to the laptop, press Super+P, it should do the video switch as this function is implemented in gnome-settings-daemon. A patch in comment #12 is now accepted upstream and a test package with that patch is available in comment #14. From the test result, the patch at least fixes Unity-2D. [Regression Potential] The patch is accepted upstream and is also cherry-picked in the gnome-3-4 branch of g-s-d git tree. g-s-d version in Precise is 3.4.2. So the risk of regression should be rather low. [Other] I prepare a debdiff in comment #31 for convenience. I hope the patch can be in both Quantal and Precise. ORIGINAL DESCRIPTION: Using : 12.04 Beta 1, updated. and Unity. In 11.10 clicking: - the function key (Fn) + (F1) allowed to switch between the laptop screen and the external monitor. After upgrading to 12.04 this no more works and instead I get an unexpected behavior: see the video. https://www.youtube.com/watch?v=-vEnrV5TwXo System: Dell XPS 15 L502X ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: ubuntu-sso-client 2.99.90-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9 Uname: Linux 3.2.0-18-generic x86_64 ApportVersion: 1.94.1-0ubuntu1 Architecture: amd64 Date: Thu Mar 8 19:18:42 2012 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) PackageArchitecture: all SourcePackage: ubuntu-sso-client UpgradeStatus: Upgraded to precise on 2012-03-02 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/950160/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1084690] [NEW] Duplicate launcher icons when restoring files
Public bug reported: There are 2 identical 'Backup' icons when you try to restore files. To reproduce: 1) Launch the backup application; notice that there is an icon in the launcher 2) In the backup app, click I want to restore files from a previous backup Expected results: The 'Restore' window opens. There is a single icon with 2 'active window' triangles in the launcher Actual results: The 'Restore' window opens. There is a second icon for the Backup app in the launcher. The application and window switchers (alt-tab, alt-`) show only a single window for the backup application, and 2 instances of the application (one is the main screen, one is the 'restore' window). ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: deja-dup 24.0-0ubuntu1 Uname: Linux 3.6.3-030603-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Thu Nov 29 14:40:04 2012 InstallationDate: Installed on 2010-09-17 (804 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: deja-dup UpgradeStatus: Upgraded to quantal on 2012-08-07 (114 days ago) ** Affects: deja-dup (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug quantal running-unity -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1084690 Title: Duplicate launcher icons when restoring files Status in “deja-dup” package in Ubuntu: New Bug description: There are 2 identical 'Backup' icons when you try to restore files. To reproduce: 1) Launch the backup application; notice that there is an icon in the launcher 2) In the backup app, click I want to restore files from a previous backup Expected results: The 'Restore' window opens. There is a single icon with 2 'active window' triangles in the launcher Actual results: The 'Restore' window opens. There is a second icon for the Backup app in the launcher. The application and window switchers (alt-tab, alt-`) show only a single window for the backup application, and 2 instances of the application (one is the main screen, one is the 'restore' window). ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: deja-dup 24.0-0ubuntu1 Uname: Linux 3.6.3-030603-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Thu Nov 29 14:40:04 2012 InstallationDate: Installed on 2010-09-17 (804 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: deja-dup UpgradeStatus: Upgraded to quantal on 2012-08-07 (114 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1084690/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1084697] [NEW] Canceling restore does not stop in-progress restore process
Public bug reported: There is a cancel button in the 'restore' dialog. The button closes the dialog but does not kill the underlying `deja-dup --restore` process. To reproduce: 1) Launch Backup app 2) Click the I want to restore files from a previous backup button. The Restore dialog opens. 3) In the Restore dialog, select an external disk that does NOT have backups on it and click Forward. The dialog should now say Checking for backups with a progress bar. 4) In a terminal, look for a restore process (e.g. `ps ax | grep restore`). Note that there should be exactly one `deja-dup --restore` process 5) Click the cancel button in the Restore dialog 6) Repeat step 4 to check for running processes Expected results: The Restore dialog closes and the underlying deja-dup process is killed Actual results: The Restore dialog closes. The underlying deja-dup --restore process is not killed. If the user tries to relaunch the backup app and restore files, they will be presented with the error, Restore Failed: Another backup operation is already running The workaround is to kill the deja-dup --restore process ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: deja-dup 24.0-0ubuntu1 Uname: Linux 3.6.3-030603-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Thu Nov 29 14:46:08 2012 InstallationDate: Installed on 2010-09-17 (804 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: deja-dup UpgradeStatus: Upgraded to quantal on 2012-08-07 (114 days ago) ** Affects: deja-dup (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug quantal running-unity -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1084697 Title: Canceling restore does not stop in-progress restore process Status in “deja-dup” package in Ubuntu: New Bug description: There is a cancel button in the 'restore' dialog. The button closes the dialog but does not kill the underlying `deja-dup --restore` process. To reproduce: 1) Launch Backup app 2) Click the I want to restore files from a previous backup button. The Restore dialog opens. 3) In the Restore dialog, select an external disk that does NOT have backups on it and click Forward. The dialog should now say Checking for backups with a progress bar. 4) In a terminal, look for a restore process (e.g. `ps ax | grep restore`). Note that there should be exactly one `deja-dup --restore` process 5) Click the cancel button in the Restore dialog 6) Repeat step 4 to check for running processes Expected results: The Restore dialog closes and the underlying deja-dup process is killed Actual results: The Restore dialog closes. The underlying deja-dup --restore process is not killed. If the user tries to relaunch the backup app and restore files, they will be presented with the error, Restore Failed: Another backup operation is already running The workaround is to kill the deja-dup --restore process ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: deja-dup 24.0-0ubuntu1 Uname: Linux 3.6.3-030603-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Thu Nov 29 14:46:08 2012 InstallationDate: Installed on 2010-09-17 (804 days ago) InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Beta amd64 (20100901.1) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: deja-dup UpgradeStatus: Upgraded to quantal on 2012-08-07 (114 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1084697/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
