[Desktop-packages] [Bug 1228765] Re: Need to implement DisplayConfig dbus interface within Unity
** Patch added: gnome-desktop 3.10 update https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1228765/+attachment/4006361/+files/gd310.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/1228765 Title: Need to implement DisplayConfig dbus interface within Unity Status in Ubuntu GNOME: Triaged Status in Unity: Triaged Status in Unity Control Center: In Progress Status in Unity Settings Daemon: In Progress Status in “gnome-desktop3” package in Ubuntu: Triaged Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: For GNOME 3.10, all the display configuration/xrandr code has been moved into Mutter as dbus interface. The Main reason for this move was to abstract away the display server (x11/wayland). This affects gnome-desktop3 and gnome-settings-daemon. In particular the changes in gnome-desktop would create a gigantic mess if we tried to revert these changes for Unity only. As such it seems the cleanest solution would be to copy the display config interface from Mutter into Unity. The code itself is fairly self contained, so apart from the resulting duplication of code, it shouldnt really be much of an issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1228765/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1287584] [NEW] what-did-you-plug-in dialog pops up behind other windows
Public bug reported: If another window is on screen, sometimes the what-did-you-plug-in dialog is popped up *behind* this window, causing the user not to see the dialog. ** Affects: unity-settings-daemon (Ubuntu) Importance: Undecided Assignee: David Henningsson (diwic) Status: In Progress ** Changed in: unity-settings-daemon (Ubuntu) Status: New = In Progress ** Changed in: unity-settings-daemon (Ubuntu) Assignee: (unassigned) = David Henningsson (diwic) -- 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/1287584 Title: what-did-you-plug-in dialog pops up behind other windows Status in “unity-settings-daemon” package in Ubuntu: In Progress Bug description: If another window is on screen, sometimes the what-did-you-plug-in dialog is popped up *behind* this window, causing the user not to see the dialog. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1287584/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1287326] Re: [FFe] Include Temporal Deinterlacer into libvdpau1-drivers-mesa
** Summary changed: - FFe Include Temporal Deinterlacer into libvdpau1-drivers-mesa + [FFe] Include Temporal Deinterlacer into libvdpau1-drivers-mesa -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1287326 Title: [FFe] Include Temporal Deinterlacer into libvdpau1-drivers-mesa Status in “mesa” package in Ubuntu: New Bug description: Beginning with Ubuntu 14.04 mesa will be shipping with vdpau drivers that can be used by e.g. radeon / radeonsi OSS drivers. This allows low power systems, like AMD E350, Kabini and so on to playback Full HD h264, vc1, mpeg4 and mpeg2 videos. Sady the wolrd is not only progressive. LiveTV is most of the time broadcasted as 1080i h264 or 576i mpeg2, which means, that it has to be deinterlaced after decoding. In current mesa vdpau (as is in 10.1) code only simple Bobbing [a] is implemented. This low quality method produces one full frame out of every field. This introduces flickering first and last line, when not taking care to cut those correctly. Grigori Goronzy (zgreg) has developed a high quality / state of the art Temporal deinterlacer [1][a] for mesa, which introduces far better quality than simple bobbing would do. This deinterlacer was already included into mesa master and was furthermore tested since more than 4 months via a special ppa in combination with xbmc [2]. This ppa was used by some thousand unique people. We would really like to see this deinterlacer in Ubuntu 14.04. This would make the new version a great basis for every htpc out there. I will attach the current patches, fetched via git format-patch out of mesa git tree. [a] http://en.wikipedia.org/wiki/Deinterlacing (Motion Adaptive vs. Bobbing) [1] Original Patch: http://anzwix.com/a/Mesa/StvdpauAddSupportForDEINTERLACETEMPORAL [2] http://forum.xbmc.org/showthread.php?tid=174854 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1287326/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1228765] Re: [FFe] Implement DisplayConfig dbus interface and transition to gnome-desktop 3.10
** Summary changed: - Need to implement DisplayConfig dbus interface within Unity + [FFe] Implement DisplayConfig dbus interface and transition to gnome-desktop 3.10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/1228765 Title: [FFe] Implement DisplayConfig dbus interface and transition to gnome- desktop 3.10 Status in Ubuntu GNOME: Triaged Status in Unity: Triaged Status in Unity Control Center: In Progress Status in Unity Settings Daemon: In Progress Status in “gnome-desktop3” package in Ubuntu: Triaged Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: For GNOME 3.10, all the display configuration/xrandr code has been moved into Mutter as dbus interface. The Main reason for this move was to abstract away the display server (x11/wayland). This affects gnome-desktop3 and gnome-settings-daemon. In particular the changes in gnome-desktop would create a gigantic mess if we tried to revert these changes for Unity only. As such it seems the cleanest solution would be to copy the display config interface from Mutter into Unity. The code itself is fairly self contained, so apart from the resulting duplication of code, it shouldnt really be much of an issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1228765/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1282203] Re: gnome-terminal not respecting Enable menu access keys setting, inside the Unity desktop environment.
In unity and 14.04 64bits desktop too I try to disable the toolbar menu 'Display..show tool bar' to don't have the shortcuts problem (I need Alt+a for weechat :) ). I note that the 'Show tool bar' don't work too. But it's possible to run gnome-terminal in CLI with the --hide-menubar option: gnome-terminal --hide-menubar like that: no menu= no menu's shotcuts :) (I'm not using an EN version, so sorry if menu tiltle don't match exactly) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1282203 Title: gnome-terminal not respecting Enable menu access keys setting, inside the Unity desktop environment. Status in “gnome-terminal” package in Ubuntu: Confirmed Bug description: Under Edit -- Keyboard Shortcuts.. there is a checkbox for Enable menu access keys (such as Alt+F to open the File menu). That checkbox appear to have no affect what so ever. No matter whatever I have it checked or not I still get the same behavior, that menu access keys are enabled. This being a problem since I'd much rather not have the menu get in the way of my readline/emacs bindings. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-terminal 3.6.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-10.30-generic 3.13.3 Uname: Linux 3.13.0-10-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Wed Feb 19 19:15:57 2014 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-terminal InstallationDate: Installed on 2013-09-06 (166 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130906) SourcePackage: gnome-terminal UpgradeStatus: Upgraded to trusty on 2013-10-23 (119 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1282203/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1173679] Re: Login to Flickr using Google ID
I managed to get correct login page (with Google and Facebook as login options). I achieved this by changing endpoint URLs in /usr/share/accounts/providers/flickr.provider from secure.flickr.com to www.flickr.com (changed only host part, the rest stayed the same). When I clicked Google login link nothing happened. It seems like that internal browser does not support popup windows or something like this. Is there any way to use external (system default?) web browser to perform authorization? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1173679 Title: Login to Flickr using Google ID Status in “account-plugins” package in Ubuntu: Confirmed Bug description: I login to Flickr via my Google account. When I try to connect through the online accounts the only option I have is to use a Yahoo! ID, which I don't have. The login should allow all valid Flickr sign in methods. (Ubuntu 13.04 64bit, Friends version 0.1.3daily13.04.17.1~13.04-0ubuntu1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1173679/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1173679] Re: Login to Flickr using Google ID
Attaching screenshot and modified version of flickr.provider file. ** Attachment added: flickr.png https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1173679/+attachment/4006421/+files/flickr.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1173679 Title: Login to Flickr using Google ID Status in “account-plugins” package in Ubuntu: Confirmed Bug description: I login to Flickr via my Google account. When I try to connect through the online accounts the only option I have is to use a Yahoo! ID, which I don't have. The login should allow all valid Flickr sign in methods. (Ubuntu 13.04 64bit, Friends version 0.1.3daily13.04.17.1~13.04-0ubuntu1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1173679/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1173679] Re: Login to Flickr using Google ID
** Attachment added: flickr.provider https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1173679/+attachment/4006422/+files/flickr.provider -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1173679 Title: Login to Flickr using Google ID Status in “account-plugins” package in Ubuntu: Confirmed Bug description: I login to Flickr via my Google account. When I try to connect through the online accounts the only option I have is to use a Yahoo! ID, which I don't have. The login should allow all valid Flickr sign in methods. (Ubuntu 13.04 64bit, Friends version 0.1.3daily13.04.17.1~13.04-0ubuntu1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1173679/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1287590] [NEW] Stop import does not do anything
Public bug reported: Neither clicking File-Stop Import nor the red x button next to the Preparing to import... progress bar will stop the actual import. At the moment An auto import was running and I tried to import from a folder. Once the Auto import was finished and the CPU settled shotwell is showing the working mouse cursor but is responsive on all but the folders item, and no images at all shows. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: shotwell 0.17.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 NonfreeKernelModules: btrfs raid6_pq xor ufs msdos xfs libcrc32c bnep rfcomm bluetooth binfmt_misc joydev snd_usb_audio snd_usbmidi_lib intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm ppdev snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep microcode snd_pcm snd_page_alloc snd_seq_midi snd_seq_midi_event psmouse snd_rawmidi serio_raw snd_seq lpc_ich snd_seq_device mei_me snd_timer mei snd soundcore parport_pc intel_smartconnect mac_hid lp parport dm_crypt hid_generic usbhid hid i915 radeon crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd ttm i2c_algo_bit r8169 8139too 8139cp drm_kms_helper mii drm floppy video ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 Date: Tue Mar 4 08:50:27 2014 InstallationDate: Installed on 2014-02-13 (18 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140211) SourcePackage: shotwell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: shotwell (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 shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1287590 Title: Stop import does not do anything Status in “shotwell” package in Ubuntu: New Bug description: Neither clicking File-Stop Import nor the red x button next to the Preparing to import... progress bar will stop the actual import. At the moment An auto import was running and I tried to import from a folder. Once the Auto import was finished and the CPU settled shotwell is showing the working mouse cursor but is responsive on all but the folders item, and no images at all shows. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: shotwell 0.17.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 NonfreeKernelModules: btrfs raid6_pq xor ufs msdos xfs libcrc32c bnep rfcomm bluetooth binfmt_misc joydev snd_usb_audio snd_usbmidi_lib intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm ppdev snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep microcode snd_pcm snd_page_alloc snd_seq_midi snd_seq_midi_event psmouse snd_rawmidi serio_raw snd_seq lpc_ich snd_seq_device mei_me snd_timer mei snd soundcore parport_pc intel_smartconnect mac_hid lp parport dm_crypt hid_generic usbhid hid i915 radeon crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd ttm i2c_algo_bit r8169 8139too 8139cp drm_kms_helper mii drm floppy video ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 Date: Tue Mar 4 08:50:27 2014 InstallationDate: Installed on 2014-02-13 (18 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140211) SourcePackage: shotwell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1287590/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1261301] Re: Double nm-applet icon in system tray (lxde)
It's not a duplicate nm-applet icon, rather the next-gen indicator- network (currently only used on the phone). You can just remove that package to get rid of it. -- 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/1261301 Title: Double nm-applet icon in system tray (lxde) Status in Network Menu: New Status in “network-manager-applet” package in Ubuntu: Confirmed Bug description: Installed clean 14.04 on toshiba ac100 netbook (tegra2 based). After installation I have two icons of nm-applet in system tray. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager-gnome 0.9.8.0-1ubuntu6 Uname: Linux 3.1.10-6-ac100 armv7l ApportVersion: 2.12.7-0ubuntu2 Architecture: armhf CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDesktop: LXDE Date: Mon Dec 16 11:49:43 2013 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d IpRoute: default via 10.0.2.1 dev wlan0 proto static 10.0.2.0/24 dev wlan0 proto kernel scope link src 10.0.2.2 metric 9 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true PciNetwork: SourcePackage: network-manager-applet UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH macbooknet805db024-c88c-45c3-b523-39994f3b6ac7 802-11-wireless 1387179995 Пн. 16 дек. 2013 11:46:35 yes no /org/freedesktop/NetworkManager/Settings/1 stuwhome 70785e55-2770-49ff-aeb0-62cdbb667e86 802-11-wireless 1387133892 Вс. 15 дек. 2013 22:58:12 yes 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.8.4connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-network/+bug/1261301/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1228765] Re: [FFe] Implement DisplayConfig dbus interface and transition to gnome-desktop 3.10
** Tags added: patch -- 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/1228765 Title: [FFe] Implement DisplayConfig dbus interface and transition to gnome- desktop 3.10 Status in Ubuntu GNOME: Triaged Status in Unity: Triaged Status in Unity Control Center: In Progress Status in Unity Settings Daemon: In Progress Status in “gnome-desktop3” package in Ubuntu: Triaged Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: For GNOME 3.10, all the display configuration/xrandr code has been moved into Mutter as dbus interface. The Main reason for this move was to abstract away the display server (x11/wayland). This affects gnome-desktop3 and gnome-settings-daemon. In particular the changes in gnome-desktop would create a gigantic mess if we tried to revert these changes for Unity only. As such it seems the cleanest solution would be to copy the display config interface from Mutter into Unity. The code itself is fairly self contained, so apart from the resulting duplication of code, it shouldnt really be much of an issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1228765/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1287594] [NEW] Import fail with error message about photo library not being writeable
Public bug reported: After importing from folder and using the option to copy the photos I get the following dialog: 17 photos failed to import because the photo library folder was not writable Following a list of 17 paths pointing to where the images should have been stored. When closing the dialog noting is showing up, as if they failed to import, which is what the dialog said. However the photos were actually copied to the location the error dialog claimed not to be writable. Only the database was not updated. The console show no error messages. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: shotwell 0.17.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 NonfreeKernelModules: btrfs raid6_pq xor ufs msdos xfs libcrc32c bnep rfcomm bluetooth binfmt_misc joydev snd_usb_audio snd_usbmidi_lib intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm ppdev snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep microcode snd_pcm snd_page_alloc snd_seq_midi snd_seq_midi_event psmouse snd_rawmidi serio_raw snd_seq lpc_ich snd_seq_device mei_me snd_timer mei snd soundcore parport_pc intel_smartconnect mac_hid lp parport dm_crypt hid_generic usbhid hid i915 radeon crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd ttm i2c_algo_bit r8169 8139too 8139cp drm_kms_helper mii drm floppy video ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 Date: Tue Mar 4 08:56:17 2014 InstallationDate: Installed on 2014-02-13 (18 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140211) SourcePackage: shotwell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: shotwell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Attachment added: Shotwell Import Log.txt https://bugs.launchpad.net/bugs/1287594/+attachment/4006427/+files/Shotwell%20Import%20Log.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1287594 Title: Import fail with error message about photo library not being writeable Status in “shotwell” package in Ubuntu: New Bug description: After importing from folder and using the option to copy the photos I get the following dialog: 17 photos failed to import because the photo library folder was not writable Following a list of 17 paths pointing to where the images should have been stored. When closing the dialog noting is showing up, as if they failed to import, which is what the dialog said. However the photos were actually copied to the location the error dialog claimed not to be writable. Only the database was not updated. The console show no error messages. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: shotwell 0.17.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 NonfreeKernelModules: btrfs raid6_pq xor ufs msdos xfs libcrc32c bnep rfcomm bluetooth binfmt_misc joydev snd_usb_audio snd_usbmidi_lib intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm ppdev snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep microcode snd_pcm snd_page_alloc snd_seq_midi snd_seq_midi_event psmouse snd_rawmidi serio_raw snd_seq lpc_ich snd_seq_device mei_me snd_timer mei snd soundcore parport_pc intel_smartconnect mac_hid lp parport dm_crypt hid_generic usbhid hid i915 radeon crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd ttm i2c_algo_bit r8169 8139too 8139cp drm_kms_helper mii drm floppy video ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 Date: Tue Mar 4 08:56:17 2014 InstallationDate: Installed on 2014-02-13 (18 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140211) SourcePackage: shotwell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1287594/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1280053] Re: eclipse is a crashy mess on trusty
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: eclipse (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eclipse in Ubuntu. https://bugs.launchpad.net/bugs/1280053 Title: eclipse is a crashy mess on trusty Status in “eclipse” package in Ubuntu: Confirmed Bug description: It seems apport has stopped catching eclipse crashes, so I'm reporting this issue by hand. To reproduce, all I have to do is open a medium sized Java project in eclipse and try to navigate around (using F3 and F4 etc.). After 3 or 4 operations, eclipse always crashes. This started right after upgrading to trusty. What can I do to help folks debug this further? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: eclipse-platform 3.8.1-5.1 ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.13.2-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Thu Feb 13 21:11:10 2014 InstallationDate: Installed on 2011-09-18 (879 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110426) SourcePackage: eclipse UpgradeStatus: Upgraded to trusty on 2014-02-02 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1280053/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1287433] Re: Progress bar doesn't work in nautilus for sftp file transfers
(not sure if sftp != ssh, but copying to a ssh location gives me a bar regularly updated as well as a number nMb/totalMb -- 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/1287433 Title: Progress bar doesn't work in nautilus for sftp file transfers Status in “nautilus” package in Ubuntu: New Bug description: When doing SFTP file transfers, nautilus's progress window shows Preparing to transfer, and then the progressbar does not update until the end of the file transfer, at which point the window just closes. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nautilus 1:3.10.1-0ubuntu7 Uname: Linux 3.13.4-hyper1 x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 4 07:58:37 2014 GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-zoom-level' b'smaller' b'org.gnome.nautilus.list-view' b'default-column-order' b['name', 'size', 'type', 'date_modified', 'owner', 'group', 'permissions', 'mime_type', 'where'] SourcePackage: nautilus UpgradeStatus: Upgraded to trusty on 2014-03-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1287433/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1287433] Re: Progress bar doesn't work in nautilus for sftp file transfers
Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance. ** Changed in: nautilus (Ubuntu) Importance: Undecided = Low -- 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/1287433 Title: Progress bar doesn't work in nautilus for sftp file transfers Status in “nautilus” package in Ubuntu: New Bug description: When doing SFTP file transfers, nautilus's progress window shows Preparing to transfer, and then the progressbar does not update until the end of the file transfer, at which point the window just closes. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nautilus 1:3.10.1-0ubuntu7 Uname: Linux 3.13.4-hyper1 x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 4 07:58:37 2014 GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-zoom-level' b'smaller' b'org.gnome.nautilus.list-view' b'default-column-order' b['name', 'size', 'type', 'date_modified', 'owner', 'group', 'permissions', 'mime_type', 'where'] SourcePackage: nautilus UpgradeStatus: Upgraded to trusty on 2014-03-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1287433/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1287421] Re: Nautilus no icon view options
Thank you for your bug report, what icon theme do you use? ** Changed in: nautilus (Ubuntu) Status: New = Incomplete ** Changed in: nautilus (Ubuntu) Importance: Undecided = Low -- 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/1287421 Title: Nautilus no icon view options Status in “nautilus” package in Ubuntu: Incomplete Bug description: After the upgrade, the icon is gone 'view options' for WM (e.g. jwm). Ubuntu not only Unity. Please fix it. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nautilus 1:3.10.1-0ubuntu7 ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5 Uname: Linux 3.13.0-14-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 Date: Tue Mar 4 01:18:27 2014 GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' b['name', 'size', 'type', 'date_modified', 'owner', 'group', 'permissions', 'mime_type', 'where', 'date_accessed'] InstallationDate: Installed on 2014-02-01 (30 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) SourcePackage: nautilus UpgradeStatus: Upgraded to trusty on 2014-02-01 (30 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1287421/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 262241] Re: Cannot edit Cyrillic pdf
@lioncub: don't reopen bugs closed for years, please open a new one with your description of issue instead ** Changed in: evince (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/262241 Title: Cannot edit Cyrillic pdf Status in “evince” package in Ubuntu: Invalid Bug description: Binary package hint: evince I tried to fill pdf form in Russian( Cyrillic) letters. I found that I can type and see correct results, but when input focus move outside of field then text change to something quoted-printable like =AB0=B8=. Returning focus back to field restores correct text. Form was partially filled in Windows and there is no problem with fields already filled unless you try to edit them. I use ubuntu 8.04 and evince 2.22.2 pdf file ( passport application form can be found at http://www.fms.gov.ru/documents/passport/zp25.pdf I use gnome, XKB and ru_RU.UTF-8 locale ProblemType: Bug Architecture: i386 Date: Thu Aug 28 16:11:46 2008 DistroRelease: Ubuntu 8.04 ExecutablePath: /usr/bin/evince NonfreeKernelModules: nvidia Package: evince 2.22.2-0ubuntu1 PackageArchitecture: i386 ProcEnviron: LC_TIME=C PATH=/bin:/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/home/oracle/app/oracle/product/11.1.0/db_2/bin:/home/username/bin:. LANG=ru_RU.UTF-8 LC_MESSAGES=C SHELL=/bin/bash SourcePackage: evince Uname: Linux 2.6.24-21-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/262241/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1239186] Re: External screens shut off randomly
I think I have the same issue as the original poster. Regarding comment #29, is it enough to boot into a live CD and try to reproduce? (I'm a bit reluctant to upgrade my work laptop to an unofficial release) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1239186 Title: External screens shut off randomly Status in “xserver-xorg-video-intel” package in Ubuntu: Incomplete Bug description: I've been trying to figure out what's going on with my external display port screens with no luckbut I think I'm getting closer to the right direction. I upgraded to the latest 13.10 build and turned on DRM debugging with: # /etc/modprobe.d/drm.conf # We are turning on debug information here options drm debug=0xe In doing so my logs lit up with lots of graphics activity. However the two events that actually had some meaning in terms of a pain point where lines like this: Oct 12 11:22:02 rnavarro-thinkpad kernel: [ 673.201706] [drm:ironlake_irq_handler], Pipe B FIFO underrun Oct 12 11:22:02 rnavarro-thinkpad kernel: [ 673.201719] [drm:cpt_serr_int_handler], PCH transcoder B FIFO underrun and Oct 12 11:22:31 rnavarro-thinkpad kernel: [ 702.411812] [drm:ironlake_irq_handler], Pipe A FIFO underrun I noticed that right before either one of my monitors would blank and shut off, this message would be emitted in my kern.log I think there was some stuff added upstream to detect this, as noted here: http://lists.freedesktop.org/archives/intel-gfx/2013-July/029882.html But i'm not sure what's causing it, much less how to fix it. What other information can I give that would help debug? ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xserver-xorg-video-intel 2:2.99.904-0ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,regex,mousepoll,imgpng,vpswitch,grid,wall,gnomecompat,animation,compiztoolbox,move,place,snap,resize,unitymtgrabhandles,workarounds,fade,expo,session,scale,ezoom,unityshell] CompositorRunning: None Date: Sat Oct 12 11:45:47 2013 DistUpgraded: 2013-10-12 10:47:24,030 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: i915-3.9-3.8, 0.02, 3.8.0-31-generic, x86_64: installed vboxhost, 4.2.18, 3.11.0-12-generic, x86_64: installed vboxhost, 4.2.18, 3.8.0-31-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21da] InstallationDate: Installed on 2013-06-30 (103 days ago) InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: LENOVO 4286CTO MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-12-generic root=/dev/mapper/vg_rnavarro--leno-lv_root ro quiet splash i915.semaphores=0 vt.handoff=7 SourcePackage: xserver-xorg-video-intel UpgradeStatus: Upgraded to saucy on 2013-10-12 (0 days ago) XorgConf: Section Device Identifier intel Driver intel Option AccelMethod sna EndSection dmi.bios.date: 02/14/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET58WW (1.28 ) dmi.board.asset.tag: Not Available dmi.board.name: 4286CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET58WW(1.28):bd02/14/2012:svnLENOVO:pn4286CTO:pvrThinkPadX220:rvnLENOVO:rn4286CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4286CTO dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental 9.2.1-1ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Sat Oct 12 11:20:57 2013 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16510 vendor
[Desktop-packages] [Bug 1287326] Re: [FFe] Include Temporal Deinterlacer into libvdpau1-drivers-mesa
** Description changed: Beginning with Ubuntu 14.04 mesa will be shipping with vdpau drivers that can be used by e.g. radeon / radeonsi OSS drivers. This allows low power systems, like AMD E350, Kabini and so on to playback Full HD h264, vc1, mpeg4 and mpeg2 videos. - Sady the wolrd is not only progressive. LiveTV is most of the time + Sadly the wolrd is not only progressive. LiveTV is most of the time broadcasted as 1080i h264 or 576i mpeg2, which means, that it has to be deinterlaced after decoding. In current mesa vdpau (as is in 10.1) code only simple Bobbing [a] is implemented. This low quality method produces one full frame out of every field. This introduces flickering first and last line, when not taking care to cut those correctly. Grigori Goronzy (zgreg) has developed a high quality / state of the art Temporal deinterlacer [1][a] for mesa, which introduces far better quality than simple bobbing would do. This deinterlacer was already included into mesa master and was furthermore tested since more than 4 months via a special ppa in combination with xbmc [2]. This ppa was used by some thousand unique people. We would really like to see this deinterlacer in Ubuntu 14.04. This would make the new version a great basis for every htpc out there. I will attach the current patches, fetched via git format-patch out of mesa git tree. [a] http://en.wikipedia.org/wiki/Deinterlacing (Motion Adaptive vs. Bobbing) [1] Original Patch: http://anzwix.com/a/Mesa/StvdpauAddSupportForDEINTERLACETEMPORAL [2] http://forum.xbmc.org/showthread.php?tid=174854 ** Description changed: Beginning with Ubuntu 14.04 mesa will be shipping with vdpau drivers that can be used by e.g. radeon / radeonsi OSS drivers. This allows low power systems, like AMD E350, Kabini and so on to playback Full HD h264, vc1, mpeg4 and mpeg2 videos. - Sadly the wolrd is not only progressive. LiveTV is most of the time + Sadly the world is not only progressive. LiveTV is most of the time broadcasted as 1080i h264 or 576i mpeg2, which means, that it has to be deinterlaced after decoding. In current mesa vdpau (as is in 10.1) code only simple Bobbing [a] is implemented. This low quality method produces one full frame out of every field. This introduces flickering first and last line, when not taking care to cut those correctly. Grigori Goronzy (zgreg) has developed a high quality / state of the art Temporal deinterlacer [1][a] for mesa, which introduces far better quality than simple bobbing would do. This deinterlacer was already included into mesa master and was furthermore tested since more than 4 months via a special ppa in combination with xbmc [2]. This ppa was used by some thousand unique people. We would really like to see this deinterlacer in Ubuntu 14.04. This would make the new version a great basis for every htpc out there. I will attach the current patches, fetched via git format-patch out of mesa git tree. [a] http://en.wikipedia.org/wiki/Deinterlacing (Motion Adaptive vs. Bobbing) [1] Original Patch: http://anzwix.com/a/Mesa/StvdpauAddSupportForDEINTERLACETEMPORAL [2] http://forum.xbmc.org/showthread.php?tid=174854 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1287326 Title: [FFe] Include Temporal Deinterlacer into libvdpau1-drivers-mesa Status in “mesa” package in Ubuntu: New Bug description: Beginning with Ubuntu 14.04 mesa will be shipping with vdpau drivers that can be used by e.g. radeon / radeonsi OSS drivers. This allows low power systems, like AMD E350, Kabini and so on to playback Full HD h264, vc1, mpeg4 and mpeg2 videos. Sadly the world is not only progressive. LiveTV is most of the time broadcasted as 1080i h264 or 576i mpeg2, which means, that it has to be deinterlaced after decoding. In current mesa vdpau (as is in 10.1) code only simple Bobbing [a] is implemented. This low quality method produces one full frame out of every field. This introduces flickering first and last line, when not taking care to cut those correctly. Grigori Goronzy (zgreg) has developed a high quality / state of the art Temporal deinterlacer [1][a] for mesa, which introduces far better quality than simple bobbing would do. This deinterlacer was already included into mesa master and was furthermore tested since more than 4 months via a special ppa in combination with xbmc [2]. This ppa was used by some thousand unique people. We would really like to see this deinterlacer in Ubuntu 14.04. This would make the new version a great basis for every htpc out there. I will attach the current patches, fetched via git format-patch out of mesa git tree. [a] http://en.wikipedia.org/wiki/Deinterlacing (Motion Adaptive vs. Bobbing) [1] Original Patch:
[Desktop-packages] [Bug 1228765] Re: [FFe] Implement DisplayConfig dbus interface and transition to gnome-desktop 3.10
** Description changed: - For GNOME 3.10, all the display configuration/xrandr code has been moved - into Mutter as dbus interface. The Main reason for this move was to - abstract away the display server (x11/wayland). + Ubuntu GNOME would like to transition for gnome-settings-daemon/gnome- + control-center 3.10. This however requires a transition to gnome-desktop + 3-10. I have been working on this for quite some time however this work + was essentially blocked waiting on the unity- forks for settings daemon + and control center. These were only finalised the day before feature + freeze. + + Right now there are quite a few features that are not available for + configuration in g-c-c given it is so old. We are also hitting some odd + bugs with mutter using its own display config separate to what gnome- + settings-daemon is doing with xrandr. + + + For GNOME 3.10, all the display configuration/xrandr code has been moved into Mutter as dbus interface. The Main reason for this move was to abstract away the display server (x11/wayland). Apart from these changes there were no significant changes in the API. This affects gnome-desktop3 and gnome-settings-daemon. In particular the changes in gnome-desktop would create a gigantic mess if we tried to - revert these changes for Unity only. As such it seems the cleanest - solution would be to copy the display config interface from Mutter into - Unity. The code itself is fairly self contained, so apart from the - resulting duplication of code, it shouldnt really be much of an issue. + revert these changes for Unity only. As such have forked the display + config code from mutter and ported *-settings-daemon and *-control- + center to the new api. The code itself is fairly self contained, so + apart from the resulting duplication of code, it shouldnt really be much + of an issue. + + ultimately it was We did do some testing via a ppa, however it was hard + to get extensive testing, due to the amount of archive churn in the + affected packages. I am pretty confident there are no much regressions + and I will commit to fixing any issues to do appear. + + Essentially this transition will involve: + new displayconfig package: This is the relevant code forked from mutter 3.10.4 (with a couple of fixes from 3.11 backported), wrapped up in a daemon. This gets autostarted when required by g/u-s-d (although dbus activation may be broken in flashback session) + + gnome/unity-settings-daemon, have backported patches to adapt to the new API. + Likewise for gnome/unity-control-center. + All other rdepends just require a no-change rebuild to adapt to the new soname. ** Description changed: Ubuntu GNOME would like to transition for gnome-settings-daemon/gnome- control-center 3.10. This however requires a transition to gnome-desktop 3-10. I have been working on this for quite some time however this work was essentially blocked waiting on the unity- forks for settings daemon and control center. These were only finalised the day before feature freeze. Right now there are quite a few features that are not available for configuration in g-c-c given it is so old. We are also hitting some odd bugs with mutter using its own display config separate to what gnome- settings-daemon is doing with xrandr. - - For GNOME 3.10, all the display configuration/xrandr code has been moved into Mutter as dbus interface. The Main reason for this move was to abstract away the display server (x11/wayland). Apart from these changes there were no significant changes in the API. + For GNOME 3.10, all the display configuration/xrandr code has been moved + into Mutter as dbus interface. The Main reason for this move was to + abstract away the display server (x11/wayland). Apart from these changes + there were no significant changes in the API. This affects gnome-desktop3 and gnome-settings-daemon. In particular the changes in gnome-desktop would create a gigantic mess if we tried to revert these changes for Unity only. As such have forked the display config code from mutter and ported *-settings-daemon and *-control- center to the new api. The code itself is fairly self contained, so apart from the resulting duplication of code, it shouldnt really be much of an issue. - ultimately it was We did do some testing via a ppa, however it was hard - to get extensive testing, due to the amount of archive churn in the - affected packages. I am pretty confident there are no much regressions - and I will commit to fixing any issues to do appear. + We have tested this via a ppa, however it was hard to get extensive + testing, due to the amount of archive churn in the affected packages. I + am pretty confident there are no much regressions and I will commit to + fixing any issues to do appear. Essentially this transition will involve: new displayconfig package: This is the relevant code forked from mutter 3.10.4 (with a couple of fixes from 3.11
Re: [Desktop-packages] [Bug 675189] Re: scrolling goes beyond targed when using enlarged font size
I just tested again in iceweasel 24.3.0 firegestures 1.10.1 mouse gestures redox 2.0.3 incompatible and turned off. The scroll problem is gone. thanks for looking into it, Tom On 01-03-14 14:28, Rolf Leggewie wrote: Do I understand you correctly that to run into this bug you have to have Firegesture extension installed and loaded? ** Changed in: firefox (Ubuntu) Status: New = Incomplete ** Changed in: firefox (Ubuntu) Assignee: (unassigned) = Rolf Leggewie (r0lf) -- 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/675189 Title: scrolling goes beyond targed when using enlarged font size Status in “firefox” package in Ubuntu: Incomplete Bug description: Binary package hint: firefox When using a bigger text size display, and clicing an anchor, firefox scrolls further than the target (actually to the end of the page, but possibly that's only symptomatic), and resets the text size to normal. This only occurs when the text size is set through my shortcut, using firegestures 1.5.7 (mouse gestures redox 2.0.3 is turned off). The problem does NOT occur when text size is enlarged using CTRL +. found the problem on page: http://en.wikipedia.org/wiki/Citizen_Kane#In_popular_culture by the way: font size also resets to default after navigating through tabs, similarly : when text size is set by the mouse gesture, but not when set using CTRL +. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: firefox 3.6.12+build1+nobinonly-0ubuntu0.10.10.1 ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic i686 Architecture: i386 Date: Sun Nov 14 15:21:09 2010 FirefoxPackages: firefox 3.6.12+build1+nobinonly-0ubuntu0.10.10.1 firefox-gnome-support 3.6.12+build1+nobinonly-0ubuntu0.10.10.1 firefox-branding 3.6.12+build1+nobinonly-0ubuntu0.10.10.1 abroswer N/A abrowser-branding N/A ProcEnviron: LANGUAGE=nl_BE:nl LANG=nl_BE.UTF-8 SHELL=/bin/bash SourcePackage: firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/675189/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1287621] [NEW] Java Swing Application windows with corrupt bottom area
Public bug reported: Java Swing application windows tend to have some corrupt area at the bottom when running under compiz. This problem is similiar to the one reported in https://bugs.launchpad.net/archlinux/+source/compiz/+bug/1138517 . Unfortunately, the fix made for this bug solves the problem only for popup dialog windows. It is still present for main application windows (and also for splash images, which do not have window decorations). The problem does not happen everytime, but quite often enough. Please see a screenshot of IntelliJ IDEA showing it (the bottom area is corrupted, thus not displaying important information to the user). This is NOT a problem related to IntelliJ, as it happens with other swing applications as well. Workaround: Closing and re-opening the application helps (sometimes, it must be closed and re-opened several times). ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: compiz 1:0.9.10+13.10.20131011-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Ist ein Verzeichnis: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 319.60 Wed Sep 25 14:28:26 PDT 2013 GCC version: gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu9) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,regex,animation,gnomecompat,move,dbus,place,annotate,snap,resize,mousepoll,wall,grid,imgpng,workarounds,unitymtgrabhandles,session,expo,ezoom,fade,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Mar 4 10:11:36 2014 DistUpgraded: 2013-12-24 11:35:42,920 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation G80GL [Quadro FX 4600] [10de:019e] (rev a2) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation Device [10de:0408] InstallationDate: Installed on 2011-12-30 (795 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) JockeyStatus: kmod:nvidia_319_updates - nvidia_319_updates (Proprietär, Aktiviert, Nicht benutzt) kmod:nvidia_304 - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietär, Deaktiviert, Nicht benutzt) kmod:nvidia_173 - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietär, Deaktiviert, Nicht benutzt) kmod:nvidia_304_updates - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietär, Deaktiviert, Nicht benutzt) kmod:nvidia_319 - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietär, Deaktiviert, Nicht benutzt) MachineType: Dell Inc. Precision WorkStation T3400 MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=de_AT:de PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_AT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic root=UUID=0dfc1c6c-de63-400f-9103-3ef9f0cd3f34 ro quiet splash SourcePackage: compiz UpgradeStatus: Upgraded to saucy on 2013-12-24 (69 days ago) dmi.bios.date: 12/09/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0TP412 dmi.board.vendor: Dell Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd12/09/2010:svnDellInc.:pnPrecisionWorkStationT3400:pvr:rvnDellInc.:rn0TP412:rvr:cvnDellInc.:ct7:cvr: dmi.product.name: Precision WorkStation T3400 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Tue Mar 4 09:19:33 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.14.5-1ubuntu2~saucy1 ** Affects: compiz (Ubuntu)
[Desktop-packages] [Bug 1287621] Re: Java Swing Application windows with corrupt bottom area
Adding another attachment to show how the window does look like if its initialized correctly. ** Attachment added: window-ok.png https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1287621/+attachment/4006501/+files/window-ok.png ** Description changed: Java Swing application windows tend to have some corrupt area at the bottom when running under compiz. This problem is similiar to the one reported in https://bugs.launchpad.net/archlinux/+source/compiz/+bug/1138517 . - Unfortunately, the fix made for this bug fixes the problem only for dialog windows. It is still present for main application windows (and also for splash images, which do not have window decorations). + Unfortunately, the fix made for this bug solves the problem only for popup dialog windows. It is still present for main application windows (and also for splash images, which do not have window decorations). The problem does not happen everytime, but quite often enough. Please see a screenshot of IntelliJ IDEA showing it (the bottom area is corrupted, thus not displaying important information to the user). This is NOT a problem related to IntelliJ, as it happens with other swing applications as well. Workaround: Closing and re-opening the application helps (sometimes, it must be closed and re-opened several times). ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: compiz 1:0.9.10+13.10.20131011-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Ist ein Verzeichnis: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: - NVRM version: NVIDIA UNIX x86_64 Kernel Module 319.60 Wed Sep 25 14:28:26 PDT 2013 - GCC version: gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu9) + NVRM version: NVIDIA UNIX x86_64 Kernel Module 319.60 Wed Sep 25 14:28:26 PDT 2013 + GCC version: gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu9) .proc.driver.nvidia.warnings.fbdev: - Your system is not currently configured to drive a VGA console - on the primary VGA device. The NVIDIA Linux graphics driver - requires the use of a text-mode VGA console. Use of other console - drivers including, but not limited to, vesafb, may result in - corruption and stability problems, and is not supported. + Your system is not currently configured to drive a VGA console + on the primary VGA device. The NVIDIA Linux graphics driver + requires the use of a text-mode VGA console. Use of other console + drivers including, but not limited to, vesafb, may result in + corruption and stability problems, and is not supported. .tmp.unity.support.test.0: - + ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,regex,animation,gnomecompat,move,dbus,place,annotate,snap,resize,mousepoll,wall,grid,imgpng,workarounds,unitymtgrabhandles,session,expo,ezoom,fade,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Mar 4 10:11:36 2014 DistUpgraded: 2013-12-24 11:35:42,920 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu GraphicsCard: - NVIDIA Corporation G80GL [Quadro FX 4600] [10de:019e] (rev a2) (prog-if 00 [VGA controller]) -Subsystem: NVIDIA Corporation Device [10de:0408] + NVIDIA Corporation G80GL [Quadro FX 4600] [10de:019e] (rev a2) (prog-if 00 [VGA controller]) + Subsystem: NVIDIA Corporation Device [10de:0408] InstallationDate: Installed on 2011-12-30 (795 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) JockeyStatus: - kmod:nvidia_319_updates - nvidia_319_updates (Proprietär, Aktiviert, Nicht benutzt) - kmod:nvidia_304 - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietär, Deaktiviert, Nicht benutzt) - kmod:nvidia_173 - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietär, Deaktiviert, Nicht benutzt) - kmod:nvidia_304_updates - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietär, Deaktiviert, Nicht benutzt) - kmod:nvidia_319 - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietär, Deaktiviert, Nicht benutzt) + kmod:nvidia_319_updates - nvidia_319_updates (Proprietär, Aktiviert, Nicht benutzt) + kmod:nvidia_304 - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietär, Deaktiviert, Nicht benutzt) + kmod:nvidia_173 - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietär, Deaktiviert, Nicht benutzt) + kmod:nvidia_304_updates - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietär, Deaktiviert, Nicht benutzt) + kmod:nvidia_319 - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietär, Deaktiviert, Nicht benutzt) MachineType: Dell Inc.
[Desktop-packages] [Bug 1228765] Re: [FFe] Implement DisplayConfig dbus interface and transition to gnome-desktop 3.10
gnome-desktop buildlog https://launchpadlibrarian.net/168292752/buildlog_ubuntu-trusty-amd64.gnome-desktop3_3.10.1-0ubuntu1~trusty2_UPLOADING.txt.gz displayconfig buildlog https://launchpadlibrarian.net/168120073/buildlog_ubuntu-trusty-amd64.displayconfig_3.10.4-0ubuntu1~trusty1_UPLOADING.txt.gz logs for the other packages should be at https://launchpad.net/~noskcaj/+archive/build ** Changed in: gnome-desktop3 (Ubuntu) Status: Triaged = New -- 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/1228765 Title: [FFe] Implement DisplayConfig dbus interface and transition to gnome- desktop 3.10 Status in Ubuntu GNOME: Triaged Status in Unity: Triaged Status in Unity Control Center: In Progress Status in Unity Settings Daemon: In Progress Status in “gnome-desktop3” package in Ubuntu: New Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: Ubuntu GNOME would like to transition for gnome-settings-daemon/gnome- control-center 3.10. This however requires a transition to gnome- desktop 3-10. I have been working on this for quite some time however this work was essentially blocked waiting on the unity- forks for settings daemon and control center. These were only finalised the day before feature freeze. Right now there are quite a few features that are not available for configuration in g-c-c given it is so old. We are also hitting some odd bugs with mutter using its own display config separate to what gnome-settings-daemon is doing with xrandr. For GNOME 3.10, all the display configuration/xrandr code has been moved into Mutter as dbus interface. The Main reason for this move was to abstract away the display server (x11/wayland). Apart from these changes there were no significant changes in the API. This affects gnome-desktop3 and gnome-settings-daemon. In particular the changes in gnome-desktop would create a gigantic mess if we tried to revert these changes for Unity only. As such have forked the display config code from mutter and ported *-settings-daemon and *-control-center to the new api. The code itself is fairly self contained, so apart from the resulting duplication of code, it shouldnt really be much of an issue. We have tested this via a ppa, however it was hard to get extensive testing, due to the amount of archive churn in the affected packages. I am pretty confident there are no much regressions and I will commit to fixing any issues to do appear. Essentially this transition will involve: new displayconfig package: This is the relevant code forked from mutter 3.10.4 (with a couple of fixes from 3.11 backported), wrapped up in a daemon. This gets autostarted when required by g/u-s-d (although dbus activation may be broken in flashback session) my upstream branch is at https://github.com/darkxst/displayconfig (I had trouble working out how to import a git branch into bzr, but I imagine it should live in bzr once approved) gnome/unity-settings-daemon, have backported patches to adapt to the new API. Likewise for gnome/unity-control-center. All other rdepends just require a no-change rebuild to adapt to the new soname. Assuming this gets a approved, subsequent FFe's for gnome-settings- daemon and gnome-control-center 3.10 will follow. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1228765/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 675189] Re: scrolling goes beyond targed when using enlarged font size
Thank you for reporting back. I'll close this ticket as invalid. If anything it sounds like a bug in the extension you were using. Firefox bugs need to be reproducible with extensions turned off (AKA safe-mode). ** Changed in: firefox (Ubuntu) Status: Incomplete = Invalid -- 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/675189 Title: scrolling goes beyond targed when using enlarged font size Status in “firefox” package in Ubuntu: Invalid Bug description: Binary package hint: firefox When using a bigger text size display, and clicing an anchor, firefox scrolls further than the target (actually to the end of the page, but possibly that's only symptomatic), and resets the text size to normal. This only occurs when the text size is set through my shortcut, using firegestures 1.5.7 (mouse gestures redox 2.0.3 is turned off). The problem does NOT occur when text size is enlarged using CTRL +. found the problem on page: http://en.wikipedia.org/wiki/Citizen_Kane#In_popular_culture by the way: font size also resets to default after navigating through tabs, similarly : when text size is set by the mouse gesture, but not when set using CTRL +. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: firefox 3.6.12+build1+nobinonly-0ubuntu0.10.10.1 ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic i686 Architecture: i386 Date: Sun Nov 14 15:21:09 2010 FirefoxPackages: firefox 3.6.12+build1+nobinonly-0ubuntu0.10.10.1 firefox-gnome-support 3.6.12+build1+nobinonly-0ubuntu0.10.10.1 firefox-branding 3.6.12+build1+nobinonly-0ubuntu0.10.10.1 abroswer N/A abrowser-branding N/A ProcEnviron: LANGUAGE=nl_BE:nl LANG=nl_BE.UTF-8 SHELL=/bin/bash SourcePackage: firefox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/675189/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1283782] Re: Xorg assert failure: X: ../../../../include/privates.h:122: dixGetPrivateAddr: Assertion `key-initialized' failed.
** Changed in: xorg-server (Ubuntu) Status: New = Fix Released -- 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/1283782 Title: Xorg assert failure: X: ../../../../include/privates.h:122: dixGetPrivateAddr: Assertion `key-initialized' failed. Status in “xorg-server” package in Ubuntu: Fix Released Bug description: I accidentally updated to 14.04 and Unity won't start ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: xserver-xorg-core 2:1.15.0-1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 AssertionMessage: X: ../../../../include/privates.h:122: dixGetPrivateAddr: Assertion `key-initialized' failed. CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Feb 22 17:52:02 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExecutablePath: /usr/bin/Xorg ExecutableTimestamp: 1392305363 ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:220b] Subsystem: Lenovo Device [17aa:220b] InstallationDate: Installed on 2013-12-31 (53 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: LENOVO 20B00050HV ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcCwd: /etc/X11 ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=4e6f0290-e885-4e03-9086-23baa555019c ro quiet splash acpi_backlight=vendor pcie_aspm=force radeon.modeset=0 vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: __assert_fail_base (fmt=0x7f37ad8144b8 %s%s%s:%u: %s%sAssertion `%s' failed.\n%n, assertion=assertion@entry=0x7f37afd31806 key-initialized, file=file@entry=0x7f37afd35a98 ../../../../include/privates.h, line=line@entry=122, function=function@entry=0x7f37afd37890 dixGetPrivateAddr) at assert.c:92 __GI___assert_fail (assertion=0x7f37afd31806 key-initialized, file=0x7f37afd35a98 ../../../../include/privates.h, line=122, function=0x7f37afd37890 dixGetPrivateAddr) at assert.c:101 ?? () xf86HandleColormaps () ?? () from /usr/lib/xorg/modules/drivers/radeon_drv.so Title: Xorg assert failure: X: ../../../../include/privates.h:122: dixGetPrivateAddr: Assertion `key-initialized' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 11/26/2013 dmi.bios.vendor: LENOVO dmi.bios.version: GKET31WW (1.11 ) dmi.board.asset.tag: Not Available dmi.board.name: 20B00050HV dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGKET31WW(1.11):bd11/26/2013:svnLENOVO:pn20B00050HV:pvrThinkPadS5-S531:rvnLENOVO:rn20B00050HV:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20B00050HV dmi.product.version: ThinkPad S5-S531 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11+14.04.20140218-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52+git20140121.46d451c9-0ubuntu0sarvatt version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.0~git20140221.9b2fe7cf-0ubuntu0sarvatt3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.0~git20140221.9b2fe7cf-0ubuntu0sarvatt3 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.99+git20140206.8de6f7b2-0ubuntu0sarvatt version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910+git20140221.0b92b128-0ubuntu0sarvatt version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sun Feb 23 18:00:22 2014 xserver.configfile: default xserver.errors: Failed to load module modesetting (module does not exist, 0) Failed to load module vesa (module does not exist, 0) Failed to load module modesetting (module does not exist, 0) Failed to load module vesa (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 44306 vendor ACR xserver.version: 2:1.15.0-1ubuntu6 To manage notifications about this bug go to:
[Desktop-packages] [Bug 1228765] Re: [FFe] Implement DisplayConfig dbus interface and transition to gnome-desktop 3.10
Thanks for the work you guys put on this. I'm not part of the release team but from an Ubuntu Desktop/Unity perspective that transition seems risky just before the LTS. The new version does change quite some APIs, when I looked at it those API were used e.g in gnome-screensaver. Could you include on the FFe the list of API changes in the next version and the reverse depends of those APIs? We need to make sure everything in the archive get ported if we transition. During the call for testing on the ubuntu-desktop list there was some feedback about existing configurations not being respected on upgrade and unity barrier not working, have those issues been resolved? -- 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/1228765 Title: [FFe] Implement DisplayConfig dbus interface and transition to gnome- desktop 3.10 Status in Ubuntu GNOME: Triaged Status in Unity: Triaged Status in Unity Control Center: In Progress Status in Unity Settings Daemon: In Progress Status in “gnome-desktop3” package in Ubuntu: New Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: Ubuntu GNOME would like to transition for gnome-settings-daemon/gnome- control-center 3.10. This however requires a transition to gnome- desktop 3-10. I have been working on this for quite some time however this work was essentially blocked waiting on the unity- forks for settings daemon and control center. These were only finalised the day before feature freeze. Right now there are quite a few features that are not available for configuration in g-c-c given it is so old. We are also hitting some odd bugs with mutter using its own display config separate to what gnome-settings-daemon is doing with xrandr. For GNOME 3.10, all the display configuration/xrandr code has been moved into Mutter as dbus interface. The Main reason for this move was to abstract away the display server (x11/wayland). Apart from these changes there were no significant changes in the API. This affects gnome-desktop3 and gnome-settings-daemon. In particular the changes in gnome-desktop would create a gigantic mess if we tried to revert these changes for Unity only. As such have forked the display config code from mutter and ported *-settings-daemon and *-control-center to the new api. The code itself is fairly self contained, so apart from the resulting duplication of code, it shouldnt really be much of an issue. We have tested this via a ppa, however it was hard to get extensive testing, due to the amount of archive churn in the affected packages. I am pretty confident there are no much regressions and I will commit to fixing any issues to do appear. Essentially this transition will involve: new displayconfig package: This is the relevant code forked from mutter 3.10.4 (with a couple of fixes from 3.11 backported), wrapped up in a daemon. This gets autostarted when required by g/u-s-d (although dbus activation may be broken in flashback session) my upstream branch is at https://github.com/darkxst/displayconfig (I had trouble working out how to import a git branch into bzr, but I imagine it should live in bzr once approved) gnome/unity-settings-daemon, have backported patches to adapt to the new API. Likewise for gnome/unity-control-center. All other rdepends just require a no-change rebuild to adapt to the new soname. Assuming this gets a approved, subsequent FFe's for gnome-settings- daemon and gnome-control-center 3.10 will follow. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1228765/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1287326] Re: [FFe] Include Temporal Deinterlacer into libvdpau1-drivers-mesa
It sounds reasonable. Please could you subscribe to bug reports and watch out for problems coming up. Ack. ** Changed in: mesa (Ubuntu) Status: New = Triaged ** Changed in: mesa (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1287326 Title: [FFe] Include Temporal Deinterlacer into libvdpau1-drivers-mesa Status in “mesa” package in Ubuntu: Triaged Bug description: Beginning with Ubuntu 14.04 mesa will be shipping with vdpau drivers that can be used by e.g. radeon / radeonsi OSS drivers. This allows low power systems, like AMD E350, Kabini and so on to playback Full HD h264, vc1, mpeg4 and mpeg2 videos. Sadly the world is not only progressive. LiveTV is most of the time broadcasted as 1080i h264 or 576i mpeg2, which means, that it has to be deinterlaced after decoding. In current mesa vdpau (as is in 10.1) code only simple Bobbing [a] is implemented. This low quality method produces one full frame out of every field. This introduces flickering first and last line, when not taking care to cut those correctly. Grigori Goronzy (zgreg) has developed a high quality / state of the art Temporal deinterlacer [1][a] for mesa, which introduces far better quality than simple bobbing would do. This deinterlacer was already included into mesa master and was furthermore tested since more than 4 months via a special ppa in combination with xbmc [2]. This ppa was used by some thousand unique people. We would really like to see this deinterlacer in Ubuntu 14.04. This would make the new version a great basis for every htpc out there. I will attach the current patches, fetched via git format-patch out of mesa git tree. [a] http://en.wikipedia.org/wiki/Deinterlacing (Motion Adaptive vs. Bobbing) [1] Original Patch: http://anzwix.com/a/Mesa/StvdpauAddSupportForDEINTERLACETEMPORAL [2] http://forum.xbmc.org/showthread.php?tid=174854 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1287326/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1228765] Re: [FFe] Implement DisplayConfig dbus interface and transition to gnome-desktop 3.10
The ffe also lists unity, should those lines be set to invalid since the current solution feature a new component rather than unity changes? -- 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/1228765 Title: [FFe] Implement DisplayConfig dbus interface and transition to gnome- desktop 3.10 Status in Ubuntu GNOME: Triaged Status in Unity: Triaged Status in Unity Control Center: In Progress Status in Unity Settings Daemon: In Progress Status in “gnome-desktop3” package in Ubuntu: New Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: Ubuntu GNOME would like to transition for gnome-settings-daemon/gnome- control-center 3.10. This however requires a transition to gnome- desktop 3-10. I have been working on this for quite some time however this work was essentially blocked waiting on the unity- forks for settings daemon and control center. These were only finalised the day before feature freeze. Right now there are quite a few features that are not available for configuration in g-c-c given it is so old. We are also hitting some odd bugs with mutter using its own display config separate to what gnome-settings-daemon is doing with xrandr. For GNOME 3.10, all the display configuration/xrandr code has been moved into Mutter as dbus interface. The Main reason for this move was to abstract away the display server (x11/wayland). Apart from these changes there were no significant changes in the API. This affects gnome-desktop3 and gnome-settings-daemon. In particular the changes in gnome-desktop would create a gigantic mess if we tried to revert these changes for Unity only. As such have forked the display config code from mutter and ported *-settings-daemon and *-control-center to the new api. The code itself is fairly self contained, so apart from the resulting duplication of code, it shouldnt really be much of an issue. We have tested this via a ppa, however it was hard to get extensive testing, due to the amount of archive churn in the affected packages. I am pretty confident there are no much regressions and I will commit to fixing any issues to do appear. Essentially this transition will involve: new displayconfig package: This is the relevant code forked from mutter 3.10.4 (with a couple of fixes from 3.11 backported), wrapped up in a daemon. This gets autostarted when required by g/u-s-d (although dbus activation may be broken in flashback session) my upstream branch is at https://github.com/darkxst/displayconfig (I had trouble working out how to import a git branch into bzr, but I imagine it should live in bzr once approved) gnome/unity-settings-daemon, have backported patches to adapt to the new API. Likewise for gnome/unity-control-center. All other rdepends just require a no-change rebuild to adapt to the new soname. Assuming this gets a approved, subsequent FFe's for gnome-settings- daemon and gnome-control-center 3.10 will follow. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1228765/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1287640] [NEW] UbuntuOne account plugin does not work
Public bug reported: When ubuntuone-credentials-common is installed, the Ubuntu One account is listed under the possible account types in gnome-control-center, but upon opening only a grey page is visible and errors are reported: (unity-control-center:22553): account-plugin-WARNING **: ap_client_load_plugin: module /usr/lib/libaccount- plugin-1.0/providers/libubuntuone.so not found: /usr/lib/libaccount- plugin-1.0/providers/libubuntuone.so: nie można otworzyć pliku obiektu dzielonego: Nie ma takiego pliku ani katalogu (unity-control-center:22553): credentials-cc-panel-CRITICAL **: cc- credentials-authorization-page.vala:54: No valid plugin found for provider ubuntuone What's more, it's currently possible to remove account-plugin-ubuntuone, but that doesn't remove the -common package above, so the account type is still listed as available. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center-signon 0.1.7~+14.04.20140211.2-0ubuntu3 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 4 11:30:18 2014 SourcePackage: gnome-control-center-signon UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center-signon (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 gnome-control-center-signon in Ubuntu. https://bugs.launchpad.net/bugs/1287640 Title: UbuntuOne account plugin does not work Status in “gnome-control-center-signon” package in Ubuntu: New Bug description: When ubuntuone-credentials-common is installed, the Ubuntu One account is listed under the possible account types in gnome-control-center, but upon opening only a grey page is visible and errors are reported: (unity-control-center:22553): account-plugin-WARNING **: ap_client_load_plugin: module /usr/lib/libaccount- plugin-1.0/providers/libubuntuone.so not found: /usr/lib/libaccount- plugin-1.0/providers/libubuntuone.so: nie można otworzyć pliku obiektu dzielonego: Nie ma takiego pliku ani katalogu (unity-control-center:22553): credentials-cc-panel-CRITICAL **: cc- credentials-authorization-page.vala:54: No valid plugin found for provider ubuntuone What's more, it's currently possible to remove account-plugin- ubuntuone, but that doesn't remove the -common package above, so the account type is still listed as available. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center-signon 0.1.7~+14.04.20140211.2-0ubuntu3 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Tue Mar 4 11:30:18 2014 SourcePackage: gnome-control-center-signon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center-signon/+bug/1287640/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1287584] Re: what-did-you-plug-in dialog pops up behind other windows
** Branch linked: lp:~diwic/unity-settings-daemon/lp1287584 -- 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/1287584 Title: what-did-you-plug-in dialog pops up behind other windows Status in “unity-settings-daemon” package in Ubuntu: In Progress Bug description: If another window is on screen, sometimes the what-did-you-plug-in dialog is popped up *behind* this window, causing the user not to see the dialog. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1287584/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1228765] Re: [FFe] Implement DisplayConfig dbus interface and transition to gnome-desktop 3.10
(oh, another note, g-c-c 3.10 depends on a new gnome-bluetooth apparently, might might depends on bluez5, I just crossed bug #1267909 which is about that) -- 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/1228765 Title: [FFe] Implement DisplayConfig dbus interface and transition to gnome- desktop 3.10 Status in Ubuntu GNOME: Triaged Status in Unity: Triaged Status in Unity Control Center: In Progress Status in Unity Settings Daemon: In Progress Status in “gnome-desktop3” package in Ubuntu: New Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: Ubuntu GNOME would like to transition for gnome-settings-daemon/gnome- control-center 3.10. This however requires a transition to gnome- desktop 3-10. I have been working on this for quite some time however this work was essentially blocked waiting on the unity- forks for settings daemon and control center. These were only finalised the day before feature freeze. Right now there are quite a few features that are not available for configuration in g-c-c given it is so old. We are also hitting some odd bugs with mutter using its own display config separate to what gnome-settings-daemon is doing with xrandr. For GNOME 3.10, all the display configuration/xrandr code has been moved into Mutter as dbus interface. The Main reason for this move was to abstract away the display server (x11/wayland). Apart from these changes there were no significant changes in the API. This affects gnome-desktop3 and gnome-settings-daemon. In particular the changes in gnome-desktop would create a gigantic mess if we tried to revert these changes for Unity only. As such have forked the display config code from mutter and ported *-settings-daemon and *-control-center to the new api. The code itself is fairly self contained, so apart from the resulting duplication of code, it shouldnt really be much of an issue. We have tested this via a ppa, however it was hard to get extensive testing, due to the amount of archive churn in the affected packages. I am pretty confident there are no much regressions and I will commit to fixing any issues to do appear. Essentially this transition will involve: new displayconfig package: This is the relevant code forked from mutter 3.10.4 (with a couple of fixes from 3.11 backported), wrapped up in a daemon. This gets autostarted when required by g/u-s-d (although dbus activation may be broken in flashback session) my upstream branch is at https://github.com/darkxst/displayconfig (I had trouble working out how to import a git branch into bzr, but I imagine it should live in bzr once approved) gnome/unity-settings-daemon, have backported patches to adapt to the new API. Likewise for gnome/unity-control-center. All other rdepends just require a no-change rebuild to adapt to the new soname. Assuming this gets a approved, subsequent FFe's for gnome-settings- daemon and gnome-control-center 3.10 will follow. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1228765/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1257956] Re: Headphones stopped working after use of Audacity. They are detected, but no sound is produced.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1257956 Title: Headphones stopped working after use of Audacity. They are detected, but no sound is produced. Status in “pulseaudio” package in Ubuntu: Confirmed Bug description: I'm running 13.10 and the latest GNOME. I've just fresh installed everything and the problem has occured again the same way. I would like to be able to use audacity, but I suppose in the mean time I will just reinstall everything. I'm unsure of what outputs I should attach. Sorry I'm quite newbish. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1257956/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1287472] Re: compiz unnecessarily shrinks new windows
Indeed, this behavior affects video applications that need to keep aspect ratio in window mode. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1287472 Title: compiz unnecessarily shrinks new windows Status in “compiz” package in Ubuntu: Confirmed Bug description: Ubuntu 14.04 Trusty, compiz 1:0.9.11+14.04.20140303-0ubuntu1. The fix for bug 1282304, just released, has introduced the following regression. Problem: All new non-fullscreen windows are now shrunk by the decoration size. This produces gnome-terminals of 79 columns by 22 rows, and applications that remember their window size when closed shrink further each time. Expected behaviour: Windows should not be resized unless they exceed the viewport size. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1287472/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1257956] Re: Headphones stopped working after use of Audacity. They are detected, but no sound is produced.
I have the exact same problem. I was not sure what it came from at the beginning but today it was clearly Audacity that stops my headphone port from working. I was listening to music before through the same headphones, with different apps. As soon as I opened the same sound with Audacity, my headphone port stopped working whereas I can unplug them and use my laptop speakers. After that, even out of Audacity, I can not use my headphones with the apps that worked before then. I only hear little breathing sounds every time a sound/song is supposed to start, or when the sound/song is supposed to finish and the app releases the sound system. It takes several reboots before it eventually start working again, sometimes after a few days. I have no idea what happens but it is an extremely disrupting problem as I can not make any music without good quality headphones. I am using Ubuntu 13.10 64bits with Audacity 2.0.5 Please let me know if I can give you something else to help fix this. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1257956 Title: Headphones stopped working after use of Audacity. They are detected, but no sound is produced. Status in “pulseaudio” package in Ubuntu: Confirmed Bug description: I'm running 13.10 and the latest GNOME. I've just fresh installed everything and the problem has occured again the same way. I would like to be able to use audacity, but I suppose in the mean time I will just reinstall everything. I'm unsure of what outputs I should attach. Sorry I'm quite newbish. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1257956/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1287326] Re: [FFe] Include Temporal Deinterlacer into libvdpau1-drivers-mesa
** Branch linked: lp:ubuntu/trusty-proposed/mesa -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1287326 Title: [FFe] Include Temporal Deinterlacer into libvdpau1-drivers-mesa Status in “mesa” package in Ubuntu: Triaged Bug description: Beginning with Ubuntu 14.04 mesa will be shipping with vdpau drivers that can be used by e.g. radeon / radeonsi OSS drivers. This allows low power systems, like AMD E350, Kabini and so on to playback Full HD h264, vc1, mpeg4 and mpeg2 videos. Sadly the world is not only progressive. LiveTV is most of the time broadcasted as 1080i h264 or 576i mpeg2, which means, that it has to be deinterlaced after decoding. In current mesa vdpau (as is in 10.1) code only simple Bobbing [a] is implemented. This low quality method produces one full frame out of every field. This introduces flickering first and last line, when not taking care to cut those correctly. Grigori Goronzy (zgreg) has developed a high quality / state of the art Temporal deinterlacer [1][a] for mesa, which introduces far better quality than simple bobbing would do. This deinterlacer was already included into mesa master and was furthermore tested since more than 4 months via a special ppa in combination with xbmc [2]. This ppa was used by some thousand unique people. We would really like to see this deinterlacer in Ubuntu 14.04. This would make the new version a great basis for every htpc out there. I will attach the current patches, fetched via git format-patch out of mesa git tree. [a] http://en.wikipedia.org/wiki/Deinterlacing (Motion Adaptive vs. Bobbing) [1] Original Patch: http://anzwix.com/a/Mesa/StvdpauAddSupportForDEINTERLACETEMPORAL [2] http://forum.xbmc.org/showthread.php?tid=174854 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1287326/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1287659] [NEW] python2 crash traceback was not caught, yet python3 one was
You have been subscribed to a public bug: Whilst investigating dial-number crash induced by dialer-app AP tests, we noticed that whilst both python2+pygtk and python3+gi based scripts crash, only the python3+gi edition generated a .crash file, the python2 edition does not. This falsely suggested there was a regression, when python2 crash was simply not caught... ** Affects: apport (Ubuntu) Importance: Undecided Status: New -- python2 crash traceback was not caught, yet python3 one was https://bugs.launchpad.net/bugs/1287659 You received this bug notification because you are a member of Desktop Packages, which is subscribed to apport in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1282804] Re: [FFe] Move DPI settings over to use u-c-c settings.
** Changed in: unity Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1282804 Title: [FFe] Move DPI settings over to use u-c-c settings. Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: [FFe] Connects the existing scale slider in the control center to existing code in the Unity shell so it will produce an effect. Default settings are unchanged from current desktop defaults. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1282804/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1228765] Re: [FFe] Implement DisplayConfig dbus interface and transition to gnome-desktop 3.10
** Changed in: unity Status: Triaged = Invalid -- 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/1228765 Title: [FFe] Implement DisplayConfig dbus interface and transition to gnome- desktop 3.10 Status in Ubuntu GNOME: Triaged Status in Unity: Invalid Status in Unity Control Center: In Progress Status in Unity Settings Daemon: In Progress Status in “gnome-desktop3” package in Ubuntu: New Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: Ubuntu GNOME would like to transition for gnome-settings-daemon/gnome- control-center 3.10. This however requires a transition to gnome- desktop 3-10. I have been working on this for quite some time however this work was essentially blocked waiting on the unity- forks for settings daemon and control center. These were only finalised the day before feature freeze. Right now there are quite a few features that are not available for configuration in g-c-c given it is so old. We are also hitting some odd bugs with mutter using its own display config separate to what gnome-settings-daemon is doing with xrandr. For GNOME 3.10, all the display configuration/xrandr code has been moved into Mutter as dbus interface. The Main reason for this move was to abstract away the display server (x11/wayland). Apart from these changes there were no significant changes in the API. This affects gnome-desktop3 and gnome-settings-daemon. In particular the changes in gnome-desktop would create a gigantic mess if we tried to revert these changes for Unity only. As such have forked the display config code from mutter and ported *-settings-daemon and *-control-center to the new api. The code itself is fairly self contained, so apart from the resulting duplication of code, it shouldnt really be much of an issue. We have tested this via a ppa, however it was hard to get extensive testing, due to the amount of archive churn in the affected packages. I am pretty confident there are no much regressions and I will commit to fixing any issues to do appear. Essentially this transition will involve: new displayconfig package: This is the relevant code forked from mutter 3.10.4 (with a couple of fixes from 3.11 backported), wrapped up in a daemon. This gets autostarted when required by g/u-s-d (although dbus activation may be broken in flashback session) my upstream branch is at https://github.com/darkxst/displayconfig (I had trouble working out how to import a git branch into bzr, but I imagine it should live in bzr once approved) gnome/unity-settings-daemon, have backported patches to adapt to the new API. Likewise for gnome/unity-control-center. All other rdepends just require a no-change rebuild to adapt to the new soname. Assuming this gets a approved, subsequent FFe's for gnome-settings- daemon and gnome-control-center 3.10 will follow. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1228765/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1287664] Re: cannot login login screen
*** This bug is a duplicate of bug 128 *** https://bugs.launchpad.net/bugs/128 ** This bug has been marked a duplicate of bug 128 Can't type my password after cold boot -- 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/1287664 Title: cannot login login screen Status in “lightdm” package in Ubuntu: New Bug description: When I start and I arrive in login screen, I cannot login. Cannot type password. But if I go hereafter to visitor and I login without password no problem. Then hereafter I logged out. And then I can login just with my username as mentioned in the first step. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1287664/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1287664] [NEW] cannot login login screen
Public bug reported: When I start and I arrive in login screen, I cannot login. Cannot type password. But if I go hereafter to visitor and I login without password no problem. Then hereafter I logged out. And then I can login just with my username as mentioned in the first step. ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New -- 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/1287664 Title: cannot login login screen Status in “lightdm” package in Ubuntu: New Bug description: When I start and I arrive in login screen, I cannot login. Cannot type password. But if I go hereafter to visitor and I login without password no problem. Then hereafter I logged out. And then I can login just with my username as mentioned in the first step. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1287664/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1287326] Re: [FFe] Include Temporal Deinterlacer into libvdpau1-drivers-mesa
FWIW, here's a quick comparison, bob vs temporal deinterlacing: http://imgur.com/4WVj8ii,AEAucba Notice the increased sharpness in the second image. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1287326 Title: [FFe] Include Temporal Deinterlacer into libvdpau1-drivers-mesa Status in “mesa” package in Ubuntu: Triaged Bug description: Beginning with Ubuntu 14.04 mesa will be shipping with vdpau drivers that can be used by e.g. radeon / radeonsi OSS drivers. This allows low power systems, like AMD E350, Kabini and so on to playback Full HD h264, vc1, mpeg4 and mpeg2 videos. Sadly the world is not only progressive. LiveTV is most of the time broadcasted as 1080i h264 or 576i mpeg2, which means, that it has to be deinterlaced after decoding. In current mesa vdpau (as is in 10.1) code only simple Bobbing [a] is implemented. This low quality method produces one full frame out of every field. This introduces flickering first and last line, when not taking care to cut those correctly. Grigori Goronzy (zgreg) has developed a high quality / state of the art Temporal deinterlacer [1][a] for mesa, which introduces far better quality than simple bobbing would do. This deinterlacer was already included into mesa master and was furthermore tested since more than 4 months via a special ppa in combination with xbmc [2]. This ppa was used by some thousand unique people. We would really like to see this deinterlacer in Ubuntu 14.04. This would make the new version a great basis for every htpc out there. I will attach the current patches, fetched via git format-patch out of mesa git tree. [a] http://en.wikipedia.org/wiki/Deinterlacing (Motion Adaptive vs. Bobbing) [1] Original Patch: http://anzwix.com/a/Mesa/StvdpauAddSupportForDEINTERLACETEMPORAL [2] http://forum.xbmc.org/showthread.php?tid=174854 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1287326/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 272584] Re: No colour conversion when image does not have embedded ICC profile
** Changed in: eog Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/272584 Title: No colour conversion when image does not have embedded ICC profile Status in Eye of GNOME: Fix Released Status in “eog” package in Ubuntu: Triaged Bug description: Ubuntu Hardy amd64, eog 2.22.3-0ubuntu2 Eye of Gnome correctly displays colours of images, which have embedded ICC profile. Other images are displayed without any colour conversion to the colour space of the monitor (as defined by tools like xcalib, xicc). Correct behaviour would be to assign sRGB profile to images without embedded profile. (sRGB colour space is de facto standard for PCs and images on the internet. Mozilla Firefox 3.x does so, too.) To manage notifications about this bug go to: https://bugs.launchpad.net/eog/+bug/272584/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1287663] [NEW] unlock from lancher not working
Public bug reported: After updating to 14.04 I recently found that the right click on any icon on launcher shows the unlock from launcher button but when i try to do that it does not unlock the icon from launcher ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140303-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5 Uname: Linux 3.13.0-14-generic i686 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu5 Architecture: i386 CompizPlugins: [core,bailer,detection,composite,opengl,decor,resize,snap,imgpng,grid,gnomecompat,unitymtgrabhandles,mousepoll,vpswitch,regex,move,place,compiztoolbox,session,animation,wall,workarounds,expo,fade,ezoom,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Mar 4 15:37:19 2014 DistUpgraded: 2014-01-30 09:50:42,576 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.141+bdcom, 3.13.0-13-generic, i686: installed bcmwl, 6.30.223.141+bdcom, 3.13.0-14-generic, i686: installed GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 12) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:1423] InstallationDate: Installed on 2012-03-24 (709 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha i386 (20120324) MachineType: Hewlett-Packard HP ProBook 4420s ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-14-generic root=UUID=8a691df1-94b5-42e2-9bc9-58195c3ca7ac ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-01-30 (33 days ago) dmi.bios.date: 06/29/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68AHH Ver. F.09 dmi.board.name: 1423 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 53.1D dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68AHHVer.F.09:bd06/29/2010:svnHewlett-Packard:pnHPProBook4420s:pvr:rvnHewlett-Packard:rn1423:rvrKBCVersion53.1D:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 4420s dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11+14.04.20140303-0ubuntu1 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: Tue Mar 4 19:09:52 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 593 vendor LGD xserver.version: 2:1.15.0-1ubuntu6 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 trusty ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1287663 Title: unlock from lancher not working Status in “unity” package in Ubuntu: New Bug description: After updating to 14.04 I recently found that the right click on any icon on launcher shows the unlock from launcher button but when i try to do that it does not unlock the icon from launcher ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140303-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5 Uname: Linux 3.13.0-14-generic i686 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu5 Architecture: i386 CompizPlugins: [core,bailer,detection,composite,opengl,decor,resize,snap,imgpng,grid,gnomecompat,unitymtgrabhandles,mousepoll,vpswitch,regex,move,place,compiztoolbox,session,animation,wall,workarounds,expo,fade,ezoom,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Mar 4 15:37:19 2014 DistUpgraded: 2014-01-30 09:50:42,576 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.141+bdcom, 3.13.0-13-generic, i686: installed bcmwl, 6.30.223.141+bdcom, 3.13.0-14-generic, i686: installed GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 12) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:1423]
[Desktop-packages] [Bug 1287659] Re: python2 crash traceback was not caught, yet python3 one was
ev says to move this to apport. ** Package changed: whoopsie (Ubuntu) = apport (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1287659 Title: python2 crash traceback was not caught, yet python3 one was Status in “apport” package in Ubuntu: New Bug description: Whilst investigating dial-number crash induced by dialer-app AP tests, we noticed that whilst both python2+pygtk and python3+gi based scripts crash, only the python3+gi edition generated a .crash file, the python2 edition does not. This falsely suggested there was a regression, when python2 crash was simply not caught... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1287659/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1282304] Re: Bottom-edge window placement doesn't take decoration height into consideration
Also this introduce introduce bizarre behavior of main window of many applications. Example with gnome screenshot: - Then open gnome sreenshot, show up without Take Screenshot button which is placed in the bottom of main window. This button becomes visible only when the window is moved. (see video in attachament). ** Attachment added: gnome-screenshot.ogv https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1282304/+attachment/4006609/+files/gnome-screenshot.ogv ** Tags added: regression-update -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1282304 Title: Bottom-edge window placement doesn't take decoration height into consideration Status in Compiz: Fix Committed Status in Unity: Invalid Status in “compiz” package in Ubuntu: Fix Released Bug description: With the new compiz, bottom-edge window placement doesn't take decoration height into account, and thus leads to placing windows slightly off-screen. Easily reproducible by hitting Ctrl-Alt-T four times and noting that the top top-edge terminals are placed correctly, but the two bottom-edge ones are placed just below the bottom of the workspace. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1282304/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1287326] Re: [FFe] Include Temporal Deinterlacer into libvdpau1-drivers-mesa
I've got to admit, i'm struggling to see the improvement, and I *want* to, agreeing with the request of this bug. But perhaps the conversion to jpeg is wiping it out? Should be using a lossless capture there, I reckon. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1287326 Title: [FFe] Include Temporal Deinterlacer into libvdpau1-drivers-mesa Status in “mesa” package in Ubuntu: Triaged Bug description: Beginning with Ubuntu 14.04 mesa will be shipping with vdpau drivers that can be used by e.g. radeon / radeonsi OSS drivers. This allows low power systems, like AMD E350, Kabini and so on to playback Full HD h264, vc1, mpeg4 and mpeg2 videos. Sadly the world is not only progressive. LiveTV is most of the time broadcasted as 1080i h264 or 576i mpeg2, which means, that it has to be deinterlaced after decoding. In current mesa vdpau (as is in 10.1) code only simple Bobbing [a] is implemented. This low quality method produces one full frame out of every field. This introduces flickering first and last line, when not taking care to cut those correctly. Grigori Goronzy (zgreg) has developed a high quality / state of the art Temporal deinterlacer [1][a] for mesa, which introduces far better quality than simple bobbing would do. This deinterlacer was already included into mesa master and was furthermore tested since more than 4 months via a special ppa in combination with xbmc [2]. This ppa was used by some thousand unique people. We would really like to see this deinterlacer in Ubuntu 14.04. This would make the new version a great basis for every htpc out there. I will attach the current patches, fetched via git format-patch out of mesa git tree. [a] http://en.wikipedia.org/wiki/Deinterlacing (Motion Adaptive vs. Bobbing) [1] Original Patch: http://anzwix.com/a/Mesa/StvdpauAddSupportForDEINTERLACETEMPORAL [2] http://forum.xbmc.org/showthread.php?tid=174854 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1287326/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1228765] Re: [FFe] Implement DisplayConfig dbus interface and transition to gnome-desktop 3.10
- I fixed the issue with configurations not being read from the gnome-settings-daemon monitors.xml config file, I',m not entirely sure what wrote this file, but Laney suggested it was maybe copied across by one of the indicators? - I couldn't reproduce the pointer barrier issue here on my dual monitor setup. I actually don't believe there is any code dealing with pointer barriers involved here either. - Right, Unity no longer requires changes with this solution. marked invalid. - Our build of g-c-c 3.10 has the bluetooth changes reverted, so no need for BlueZ 5 this cycle (will definitely need that for next cycle however). - I will add a list of the changed API tomorrow, however I don't believe gnome-screensaver is affected by this and certainly built fine when I tested it. Most of the API changes are pretty internal (i.e. limited to g-s-d and g-c-c). The api's that most apps are using (background, thumbnailer, etc) are unaffected. As a side note, I have spoken with upstream about splitting out all app dependencies from gnome-desktop, at which point it would become feasible to fork gnome-desktop, however this won't happen until atleast 3.14 anyway. -- 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/1228765 Title: [FFe] Implement DisplayConfig dbus interface and transition to gnome- desktop 3.10 Status in Ubuntu GNOME: Triaged Status in Unity: Invalid Status in Unity Control Center: In Progress Status in Unity Settings Daemon: In Progress Status in “gnome-desktop3” package in Ubuntu: New Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: Ubuntu GNOME would like to transition for gnome-settings-daemon/gnome- control-center 3.10. This however requires a transition to gnome- desktop 3-10. I have been working on this for quite some time however this work was essentially blocked waiting on the unity- forks for settings daemon and control center. These were only finalised the day before feature freeze. Right now there are quite a few features that are not available for configuration in g-c-c given it is so old. We are also hitting some odd bugs with mutter using its own display config separate to what gnome-settings-daemon is doing with xrandr. For GNOME 3.10, all the display configuration/xrandr code has been moved into Mutter as dbus interface. The Main reason for this move was to abstract away the display server (x11/wayland). Apart from these changes there were no significant changes in the API. This affects gnome-desktop3 and gnome-settings-daemon. In particular the changes in gnome-desktop would create a gigantic mess if we tried to revert these changes for Unity only. As such have forked the display config code from mutter and ported *-settings-daemon and *-control-center to the new api. The code itself is fairly self contained, so apart from the resulting duplication of code, it shouldnt really be much of an issue. We have tested this via a ppa, however it was hard to get extensive testing, due to the amount of archive churn in the affected packages. I am pretty confident there are no much regressions and I will commit to fixing any issues to do appear. Essentially this transition will involve: new displayconfig package: This is the relevant code forked from mutter 3.10.4 (with a couple of fixes from 3.11 backported), wrapped up in a daemon. This gets autostarted when required by g/u-s-d (although dbus activation may be broken in flashback session) my upstream branch is at https://github.com/darkxst/displayconfig (I had trouble working out how to import a git branch into bzr, but I imagine it should live in bzr once approved) gnome/unity-settings-daemon, have backported patches to adapt to the new API. Likewise for gnome/unity-control-center. All other rdepends just require a no-change rebuild to adapt to the new soname. Assuming this gets a approved, subsequent FFe's for gnome-settings- daemon and gnome-control-center 3.10 will follow. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1228765/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1286539] Re: adding a printer through GUI doesn't work
*** This bug is a duplicate of bug 1248303 *** https://bugs.launchpad.net/bugs/1248303 Your printer, the Brother DCP-330C, is neither explicitly supported locally by Ubuntu, nor is it listed on the OpenPrinting web site. What happened is that due to the missing local support system-config-printer has searched on OpenPrinting and a bug in the search facility of the OpenPrinting server made it answering the search with the Canon CP-330, a completely different printer. I have fixed the server now so that the search gives the correct, empty answer, lettin system-config-printer pass on to manual model/driver selection. Note that this prevents system-config-printer from hanging but does not make your printer working. If your printer supports any standard language (many laser printers do, but inkjets usually not), like PDF, PostScript, PCL, ..., you can set up one of the Generic printers, otherwise have a look at Brother's web site whether a Linux driver for your printer is available. ** Changed in: system-config-printer (Ubuntu) Status: Incomplete = Confirmed ** This bug has been marked a duplicate of bug 1248303 Regression: installing gutenprint printer driver fails -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1286539 Title: adding a printer through GUI doesn't work Status in “system-config-printer” package in Ubuntu: Confirmed Bug description: #papercut Credits to this question: https://answers.launchpad.net/ubuntu/+source/cups/+question/238504 Tried adding new printer (Brother DCP-330C ) and the config menu hangs on adding a printer name (manually or server). went to http://localhost:631/admin and added it the same way - and it worked flawlessly. cheers. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: system-config-printer-gnome 1.4.2+20130920-0ubuntu1.2 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Sat Mar 1 14:46:57 2014 InstallationDate: Installed on 2014-03-01 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) Lpstat: device for Brother_DCP-330C: usb://Brother/DCP-330C?serial=BROB7F533166 MachineType: MSI MS-7680 MarkForUpload: True PackageArchitecture: all Papersize: a4 PpdFiles: Brother_DCP-330C: Brother DCP-330C CUPS v1.1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic root=UUID=c4c980e1-90a7-41c7-aa26-b7a5577004f8 ro quiet splash vt.handoff=7 SourcePackage: system-config-printer UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/21/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V12.0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61M-E23(G3)(MS-7680) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV12.0:bd03/21/2012:svnMSI:pnMS-7680:pvr2.0:rvnMSI:rnH61M-E23(G3)(MS-7680):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.name: MS-7680 dmi.product.version: 2.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1286539/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1286539] Re: adding a printer through GUI doesn't work
*** This bug is a duplicate of bug 1248303 *** https://bugs.launchpad.net/bugs/1248303 A fix in system-config-printer concerning this got already applied earlier, see bug 1248303. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1286539 Title: adding a printer through GUI doesn't work Status in “system-config-printer” package in Ubuntu: Confirmed Bug description: #papercut Credits to this question: https://answers.launchpad.net/ubuntu/+source/cups/+question/238504 Tried adding new printer (Brother DCP-330C ) and the config menu hangs on adding a printer name (manually or server). went to http://localhost:631/admin and added it the same way - and it worked flawlessly. cheers. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: system-config-printer-gnome 1.4.2+20130920-0ubuntu1.2 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Sat Mar 1 14:46:57 2014 InstallationDate: Installed on 2014-03-01 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) Lpstat: device for Brother_DCP-330C: usb://Brother/DCP-330C?serial=BROB7F533166 MachineType: MSI MS-7680 MarkForUpload: True PackageArchitecture: all Papersize: a4 PpdFiles: Brother_DCP-330C: Brother DCP-330C CUPS v1.1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic root=UUID=c4c980e1-90a7-41c7-aa26-b7a5577004f8 ro quiet splash vt.handoff=7 SourcePackage: system-config-printer UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/21/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V12.0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61M-E23(G3)(MS-7680) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV12.0:bd03/21/2012:svnMSI:pnMS-7680:pvr2.0:rvnMSI:rnH61M-E23(G3)(MS-7680):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.name: MS-7680 dmi.product.version: 2.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1286539/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1287326] Re: [FFe] Include Temporal Deinterlacer into libvdpau1-drivers-mesa
Hint: Make both fullscreen and check the power supply lines. Bob clearly has artifacts, e.g. line is not even continuous differentiable vs temporal: all fine -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1287326 Title: [FFe] Include Temporal Deinterlacer into libvdpau1-drivers-mesa Status in “mesa” package in Ubuntu: Triaged Bug description: Beginning with Ubuntu 14.04 mesa will be shipping with vdpau drivers that can be used by e.g. radeon / radeonsi OSS drivers. This allows low power systems, like AMD E350, Kabini and so on to playback Full HD h264, vc1, mpeg4 and mpeg2 videos. Sadly the world is not only progressive. LiveTV is most of the time broadcasted as 1080i h264 or 576i mpeg2, which means, that it has to be deinterlaced after decoding. In current mesa vdpau (as is in 10.1) code only simple Bobbing [a] is implemented. This low quality method produces one full frame out of every field. This introduces flickering first and last line, when not taking care to cut those correctly. Grigori Goronzy (zgreg) has developed a high quality / state of the art Temporal deinterlacer [1][a] for mesa, which introduces far better quality than simple bobbing would do. This deinterlacer was already included into mesa master and was furthermore tested since more than 4 months via a special ppa in combination with xbmc [2]. This ppa was used by some thousand unique people. We would really like to see this deinterlacer in Ubuntu 14.04. This would make the new version a great basis for every htpc out there. I will attach the current patches, fetched via git format-patch out of mesa git tree. [a] http://en.wikipedia.org/wiki/Deinterlacing (Motion Adaptive vs. Bobbing) [1] Original Patch: http://anzwix.com/a/Mesa/StvdpauAddSupportForDEINTERLACETEMPORAL [2] http://forum.xbmc.org/showthread.php?tid=174854 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1287326/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1287326] Re: [FFe] Include Temporal Deinterlacer into libvdpau1-drivers-mesa
ok, i *can* see the improvement if i view the images at full size switching between browser tabs (which the site's own page doesn't seem to let you do, bizarrely; initially i'd just thought they were SD captures). Yes, 2nd image is better; but *still* it would probably be better reflection if not captured lossily. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1287326 Title: [FFe] Include Temporal Deinterlacer into libvdpau1-drivers-mesa Status in “mesa” package in Ubuntu: Triaged Bug description: Beginning with Ubuntu 14.04 mesa will be shipping with vdpau drivers that can be used by e.g. radeon / radeonsi OSS drivers. This allows low power systems, like AMD E350, Kabini and so on to playback Full HD h264, vc1, mpeg4 and mpeg2 videos. Sadly the world is not only progressive. LiveTV is most of the time broadcasted as 1080i h264 or 576i mpeg2, which means, that it has to be deinterlaced after decoding. In current mesa vdpau (as is in 10.1) code only simple Bobbing [a] is implemented. This low quality method produces one full frame out of every field. This introduces flickering first and last line, when not taking care to cut those correctly. Grigori Goronzy (zgreg) has developed a high quality / state of the art Temporal deinterlacer [1][a] for mesa, which introduces far better quality than simple bobbing would do. This deinterlacer was already included into mesa master and was furthermore tested since more than 4 months via a special ppa in combination with xbmc [2]. This ppa was used by some thousand unique people. We would really like to see this deinterlacer in Ubuntu 14.04. This would make the new version a great basis for every htpc out there. I will attach the current patches, fetched via git format-patch out of mesa git tree. [a] http://en.wikipedia.org/wiki/Deinterlacing (Motion Adaptive vs. Bobbing) [1] Original Patch: http://anzwix.com/a/Mesa/StvdpauAddSupportForDEINTERLACETEMPORAL [2] http://forum.xbmc.org/showthread.php?tid=174854 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1287326/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1287326] Re: [FFe] Include Temporal Deinterlacer into libvdpau1-drivers-mesa
A fix for this is only showing the top or bottom fields, but that means losing half of the horizontal resolution. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1287326 Title: [FFe] Include Temporal Deinterlacer into libvdpau1-drivers-mesa Status in “mesa” package in Ubuntu: Triaged Bug description: Beginning with Ubuntu 14.04 mesa will be shipping with vdpau drivers that can be used by e.g. radeon / radeonsi OSS drivers. This allows low power systems, like AMD E350, Kabini and so on to playback Full HD h264, vc1, mpeg4 and mpeg2 videos. Sadly the world is not only progressive. LiveTV is most of the time broadcasted as 1080i h264 or 576i mpeg2, which means, that it has to be deinterlaced after decoding. In current mesa vdpau (as is in 10.1) code only simple Bobbing [a] is implemented. This low quality method produces one full frame out of every field. This introduces flickering first and last line, when not taking care to cut those correctly. Grigori Goronzy (zgreg) has developed a high quality / state of the art Temporal deinterlacer [1][a] for mesa, which introduces far better quality than simple bobbing would do. This deinterlacer was already included into mesa master and was furthermore tested since more than 4 months via a special ppa in combination with xbmc [2]. This ppa was used by some thousand unique people. We would really like to see this deinterlacer in Ubuntu 14.04. This would make the new version a great basis for every htpc out there. I will attach the current patches, fetched via git format-patch out of mesa git tree. [a] http://en.wikipedia.org/wiki/Deinterlacing (Motion Adaptive vs. Bobbing) [1] Original Patch: http://anzwix.com/a/Mesa/StvdpauAddSupportForDEINTERLACETEMPORAL [2] http://forum.xbmc.org/showthread.php?tid=174854 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1287326/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1287326] Re: [FFe] Include Temporal Deinterlacer into libvdpau1-drivers-mesa
Conversion to .jpg is probably destroying it. But yes it's very visible in mostly static images. 'bob' deinterlacing is called that way because objects bob up and down when top and bottom fields are shown alternately. The horizontal resolution of each field is only half a frame, so vertical sharpness is lost. Both effects aren't easy to show in a single image, but it's VERY visible when playing any kind of movie. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1287326 Title: [FFe] Include Temporal Deinterlacer into libvdpau1-drivers-mesa Status in “mesa” package in Ubuntu: Triaged Bug description: Beginning with Ubuntu 14.04 mesa will be shipping with vdpau drivers that can be used by e.g. radeon / radeonsi OSS drivers. This allows low power systems, like AMD E350, Kabini and so on to playback Full HD h264, vc1, mpeg4 and mpeg2 videos. Sadly the world is not only progressive. LiveTV is most of the time broadcasted as 1080i h264 or 576i mpeg2, which means, that it has to be deinterlaced after decoding. In current mesa vdpau (as is in 10.1) code only simple Bobbing [a] is implemented. This low quality method produces one full frame out of every field. This introduces flickering first and last line, when not taking care to cut those correctly. Grigori Goronzy (zgreg) has developed a high quality / state of the art Temporal deinterlacer [1][a] for mesa, which introduces far better quality than simple bobbing would do. This deinterlacer was already included into mesa master and was furthermore tested since more than 4 months via a special ppa in combination with xbmc [2]. This ppa was used by some thousand unique people. We would really like to see this deinterlacer in Ubuntu 14.04. This would make the new version a great basis for every htpc out there. I will attach the current patches, fetched via git format-patch out of mesa git tree. [a] http://en.wikipedia.org/wiki/Deinterlacing (Motion Adaptive vs. Bobbing) [1] Original Patch: http://anzwix.com/a/Mesa/StvdpauAddSupportForDEINTERLACETEMPORAL [2] http://forum.xbmc.org/showthread.php?tid=174854 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1287326/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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] Re: Obscene content in music search results
** Changed in: unity-music-lens Status: New = Invalid -- 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 Music Lens: Invalid Status in Unity SoundCloud Scope: Confirmed Status in “unity” package in Ubuntu: Invalid 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/unity-music-lens/+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 1040259] Re: FFE: libmessaging-menu transitions for quantal
Invaliding since quantal reaches EOL. ** Changed in: liferea (Ubuntu Quantal) Status: Triaged = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gwibber in Ubuntu. https://bugs.launchpad.net/bugs/1040259 Title: FFE: libmessaging-menu transitions for quantal Status in Gmail Watcher: Triaged Status in Lightread: Triaged Status in Quassel Irc Client: New Status in Skype-wrapper: In Progress Status in “evolution-indicator” package in Ubuntu: Fix Released Status in “gm-notify” package in Ubuntu: Triaged Status in “guayadeque” package in Ubuntu: Fix Released Status in “gwibber” package in Ubuntu: Fix Released Status in “indicator-messages” package in Ubuntu: Fix Released Status in “kdenetwork” package in Ubuntu: New Status in “kdepim” package in Ubuntu: New Status in “libdbusmenu-qt” package in Ubuntu: New Status in “libunity-webapps” package in Ubuntu: Fix Released Status in “liferea” package in Ubuntu: Fix Released Status in “openfetion” package in Ubuntu: New Status in “pidgin” package in Ubuntu: Fix Released Status in “pidgin-libnotify” package in Ubuntu: Fix Released Status in “quassel” package in Ubuntu: New Status in “smuxi” package in Ubuntu: Fix Released Status in “telepathy-indicator” package in Ubuntu: Fix Released Status in “thunderbird” package in Ubuntu: Fix Released Status in “unity-mail” package in Ubuntu: Fix Released Status in “xchat-indicator” package in Ubuntu: Fix Released Status in “gm-notify” source package in Quantal: Triaged Status in “guayadeque” source package in Quantal: New Status in “gwibber” source package in Quantal: Fix Released Status in “indicator-messages” source package in Quantal: Fix Released Status in “kdenetwork” source package in Quantal: New Status in “kdepim” source package in Quantal: New Status in “libdbusmenu-qt” source package in Quantal: New Status in “libunity-webapps” source package in Quantal: Fix Released Status in “liferea” source package in Quantal: Invalid Status in “openfetion” source package in Quantal: New Status in “pidgin” source package in Quantal: Confirmed Status in “pidgin-libnotify” source package in Quantal: In Progress Status in “quassel” source package in Quantal: New Status in “smuxi” source package in Quantal: Fix Released Status in “telepathy-indicator” source package in Quantal: Fix Released Status in “thunderbird” source package in Quantal: Fix Released Status in “unity-mail” source package in Quantal: Fix Released Status in “xchat-indicator” source package in Quantal: Fix Released Bug description: indicator-messages got updated, introducing a new libmessaging-menu api (deprecating the old libindicate library) which should make application developper's life easier. The indicator work is done and the library is ready and we started porting applications The current stack is being tested in https://launchpad.net/~ubuntu- desktop/+archive/ppa/ It includes - indicator-messages - gwibber - indicator-telepathy - thunderbird (soon, work is being finished) which is what we consider the minimal set for landing the feature for quantal we will add those soon: - pidgin - xchat-indicator - evolution-indicator To manage notifications about this bug go to: https://bugs.launchpad.net/gmailwatcher/+bug/1040259/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1287326] Re: [FFe] Include Temporal Deinterlacer into libvdpau1-drivers-mesa
There are other advanced methods, e.g. combining temporal information with spatial information, that you find in the nvidia proprietary implementation for example. Also intel tries to get something done in their MADI and MACI implementations, but with only one forward reference i am not so sure about the quality outcome. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1287326 Title: [FFe] Include Temporal Deinterlacer into libvdpau1-drivers-mesa Status in “mesa” package in Ubuntu: Triaged Bug description: Beginning with Ubuntu 14.04 mesa will be shipping with vdpau drivers that can be used by e.g. radeon / radeonsi OSS drivers. This allows low power systems, like AMD E350, Kabini and so on to playback Full HD h264, vc1, mpeg4 and mpeg2 videos. Sadly the world is not only progressive. LiveTV is most of the time broadcasted as 1080i h264 or 576i mpeg2, which means, that it has to be deinterlaced after decoding. In current mesa vdpau (as is in 10.1) code only simple Bobbing [a] is implemented. This low quality method produces one full frame out of every field. This introduces flickering first and last line, when not taking care to cut those correctly. Grigori Goronzy (zgreg) has developed a high quality / state of the art Temporal deinterlacer [1][a] for mesa, which introduces far better quality than simple bobbing would do. This deinterlacer was already included into mesa master and was furthermore tested since more than 4 months via a special ppa in combination with xbmc [2]. This ppa was used by some thousand unique people. We would really like to see this deinterlacer in Ubuntu 14.04. This would make the new version a great basis for every htpc out there. I will attach the current patches, fetched via git format-patch out of mesa git tree. [a] http://en.wikipedia.org/wiki/Deinterlacing (Motion Adaptive vs. Bobbing) [1] Original Patch: http://anzwix.com/a/Mesa/StvdpauAddSupportForDEINTERLACETEMPORAL [2] http://forum.xbmc.org/showthread.php?tid=174854 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1287326/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 784055] Re: compiz CPU usage increases dramatically when running indicator-multiload
This bug was fixed in the package libindicator - 12.10.2+14.04.20140304-0ubuntu1 --- libindicator (12.10.2+14.04.20140304-0ubuntu1) trusty; urgency=low [ Marco Trevisan (Treviño) ] * IndicatorImageHelper: always try to use a GIcon or the filename as source of the GdkImage We don't need to fallback to pure pixbuf, unless an indicator provided a custom icon that is not in the current theme path. This helps a lot in reducing the Unity7 workload as this decreases the cases where we need to encode the pixbuf contents, send them via dbus to unity, encode them back, reload to a new pixbuf... Also thanks to this, the library clients can load the actual icon, scaled at the value they want. (LP: #784055) -- Ubuntu daily release ps-jenk...@lists.canonical.com Tue, 04 Mar 2014 10:58:35 + ** Changed in: libindicator (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/784055 Title: compiz CPU usage increases dramatically when running indicator- multiload Status in System Load Indicator: Confirmed Status in Libindicator: In Progress Status in The Ubuntu Power Consumption Project: New Status in Unity: Won't Fix Status in “indicator-multiload” package in Ubuntu: Confirmed Status in “libindicator” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Triaged Bug description: using 0.1-0~5~natty1 on mostly up to date natty system, when running the indicator-multiload with with just cpu monitor and the default update interval of 500 milliseconds, I see (via top) that compiz usage when generally idle goes from either 0 or 1% of CPU to 3 or 4% of CPU. Reducing the update interval does seem to have an affect. I realize that a.) top is not scientific b.) there could be something I'm missing here c.) saying 300% (in the subject) is not scientific To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-multiload/+bug/784055/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 840777] Re: Muting sound indicator in Unity Greeter does not mute sound on login
Unfortunately the Desired solution here seems to contradict itself. I agree with Lars and John that volume should be system-wide: changes made to the volume control in the Unity Greeter should carry through to the logged in session and vice versa. That's unfortunate if one of your family is hard of hearing and the rest are not: you'll often be changing the volume when switching users, same as you have to with a shared TV or radio. But the alternative would be more common and worse: you'd mute sound in the session, only for startup or login screen sounds to wake everyone or scare the cat. And while on a PC it might be just annoying, on a phone it would seem especially silly to have one volume setting for the lock screen and one volume setting for everything else. But apply that to the example given. User B logs in, mutes the sound, and locks or logs out; the login screen now has muted sound too. User A logs in, sets the volume to 100%, and locks or logs out; the login screen now has volume 100% too. User B returns and selects themselves in the login screen. What, then, would be the point of the sound indicator [changing] to display the muted state? After all, when B finishes logging in, they'll have volume of 100%! I've updated the spec to define volume and sound output as global settings. https://wiki.ubuntu.com/Sound?action=diffrev2=104rev1=103 ** Changed in: pulseaudio (Ubuntu) Status: New = Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/840777 Title: Muting sound indicator in Unity Greeter does not mute sound on login Status in Ayatana Design: Fix Committed Status in Sound Menu: Invalid Status in Unity Greeter: Invalid Status in “pulseaudio” package in Ubuntu: Triaged Status in “pulseaudio” source package in Raring: New Bug description: I am using beta edition of Ubuntu 11.10,with lightdm 0.9.3-0ubuntu8,and unity 4.12.0-0ubuntu2, There is a new feature in Display Manager(well,I didn't notice it in gdm,but it might have been there as well),That you can mute the sound so that login sound wont play(This option exists in the top of the lightdm login page,when you turn on ubuntu and load it)However,Login sound will still play and sound settings will change regardless of what you choose. I should add that,this happens only after a reboot or shutdown,boot again,and not when you logout and login again Desired solution: - Any changes made to the volume control in the Unity Greeter should carry through to the logged in session and vice versa. - For example, if a user changes or mutes the volume in the Unity Greeter, when they are logged in to their session this value should be carried over - The other way around is also true, if a user changes or mutes the volume in their session, when they log out this value should be displayed in the greeter. - Sound settings are stored individually on a per user account basis. The sound settings displayed in the greeter should change in line with the currently focused user account. So for example User A is currently focused and has has volume at 100%. If the focus in the greeter is changed to User B (who has volume muted), the sound indicator should change to display the muted state. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/840777/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1041790]
Created attachment 95090 Another version of the same hang - directed here from bug 75502 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1041790 Title: [snb] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001, workaround i915.semaphores=0 Status in X.org xf86-video-intel: Confirmed Status in “linux” package in Ubuntu: Incomplete Status in “sandybridge-meta” package in Ubuntu: Confirmed Status in “xserver-xorg-video-intel” package in Ubuntu: Triaged Bug description: X locks up periodically for a 2 to ten seconds at a time and this crash log gets generated. It's significantly more than several times a day but not quite continuous. If you indeed have this bug, that should stop the lockups from happening. Irrespective, please file a new bug report so your hardware may be tracked. WORKAROUND: Edit your /etc/default/grub from: GRUB_CMDLINE_LINUX_DEFAULT=quiet splash to: GRUB_CMDLINE_LINUX_DEFAULT=quiet splash i915.semaphores=0 run the following and reboot: sudo update-grub The side effects of this is rendering throughput is dropped by 10% with SNA, or as much as 3x with UXA. OpenGL performance is likely to be reduced by about 30%. More CPU time is spent waiting for the GPU with rc6 disabled, so increased power consumption. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: xserver-xorg-video-intel 2:2.20.3-0ubuntu1 Uname: Linux 3.6.0-rc3-git-20120826.1015 x86_64 ApportVersion: 2.5.1-0ubuntu2 Architecture: amd64 Chipset: sandybridge-m-gt2 Date: Sun Aug 26 16:06:32 2012 DistroCodename: quantal DistroVariant: ubuntu DuplicateSignature: [sandybridge-m-gt2] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001 Ubuntu 12.10 EcryptfsInUse: Yes ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py GpuHangFrequency: Continuously InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120724.2) InterpreterPath: /usr/bin/python3.2mu MachineType: Dell Inc. Dell System XPS L502X ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.0-rc3-git-20120826.1015 root=UUID=135c8090-427c-460a-909d-eff262cd44b6 ro quiet splash vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu3 libdrm2 2.4.38-0ubuntu2 xserver-xorg-video-intel 2:2.20.3-0ubuntu1 SourcePackage: xserver-xorg-video-intel Title: [sandybridge-m-gt2] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001 UdevDb: Error: [Errno 2] No such file or directory: 'udevadm' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/29/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0NJT03 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.:bvrA11:bd05/29/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L502X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1041790/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1201659] Re: gnome-panel crashed with SIGSEGV in gweather_location_equal()
This bug affects me. I've reduced it to: 1) Go to panel, 1.1) expand locations, 1.2) click on edit. 2) Close. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/1201659 Title: gnome-panel crashed with SIGSEGV in gweather_location_equal() Status in “gnome-panel” package in Ubuntu: Confirmed Bug description: Not sure what the context of this crash was, unfortunately. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: gnome-panel 1:3.6.2-0ubuntu11 ProcVersionSignature: Ubuntu 3.10.0-2.11-generic 3.10.0 Uname: Linux 3.10.0-2-generic x86_64 ApportVersion: 2.10.2-0ubuntu4 Architecture: amd64 Date: Mon Jul 15 21:43:59 2013 ExecutablePath: /usr/bin/gnome-panel GsettingsChanges: InstallationDate: Installed on 2012-08-21 (328 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120821) MarkForUpload: True ProcCmdline: gnome-panel SegvAnalysis: Segfault happened at: 0x7fca3278cc45 gweather_location_equal+21: mov 0x20(%rdi),%eax PC (0x7fca3278cc45) ok source 0x20(%rdi) (0x0020) not located in a known VMA region (needed readable region)! destination %eax ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-panel StacktraceTop: gweather_location_equal () from /usr/lib/libgweather-3.so.3 gweather_location_entry_set_location () from /usr/lib/libgweather-3.so.3 ?? () from /usr/lib/gnome-panel/4.0/libclock-applet.so ?? () from /usr/lib/gnome-panel/4.0/libclock-applet.so g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-panel crashed with SIGSEGV in gweather_location_equal() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1201659/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 784055] Re: compiz CPU usage increases dramatically when running indicator-multiload
** Changed in: libindicator Status: In Progress = Fix Committed ** Changed in: unity (Ubuntu) Status: Triaged = Invalid ** Changed in: libindicator (Ubuntu) Assignee: (unassigned) = Marco Trevisan (Treviño) (3v1n0) -- 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/784055 Title: compiz CPU usage increases dramatically when running indicator- multiload Status in System Load Indicator: Confirmed Status in Libindicator: Fix Committed Status in The Ubuntu Power Consumption Project: New Status in Unity: Won't Fix Status in “indicator-multiload” package in Ubuntu: Confirmed Status in “libindicator” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Invalid Bug description: using 0.1-0~5~natty1 on mostly up to date natty system, when running the indicator-multiload with with just cpu monitor and the default update interval of 500 milliseconds, I see (via top) that compiz usage when generally idle goes from either 0 or 1% of CPU to 3 or 4% of CPU. Reducing the update interval does seem to have an affect. I realize that a.) top is not scientific b.) there could be something I'm missing here c.) saying 300% (in the subject) is not scientific To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-multiload/+bug/784055/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1287472] Re: compiz unnecessarily shrinks new windows
Mh, I think I forgot to commit a change that was avoiding this :/ ** Changed in: compiz (Ubuntu) Assignee: (unassigned) = Marco Trevisan (Treviño) (3v1n0) ** Also affects: compiz Importance: Undecided Status: New ** Changed in: compiz Status: New = Triaged ** Changed in: compiz Importance: Undecided = Medium ** Changed in: compiz Assignee: (unassigned) = Marco Trevisan (Treviño) (3v1n0) ** Changed in: compiz Milestone: None = 0.9.11.0 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1287472 Title: compiz unnecessarily shrinks new windows Status in Compiz: Triaged Status in “compiz” package in Ubuntu: Confirmed Bug description: Ubuntu 14.04 Trusty, compiz 1:0.9.11+14.04.20140303-0ubuntu1. The fix for bug 1282304, just released, has introduced the following regression. Problem: All new non-fullscreen windows are now shrunk by the decoration size. This produces gnome-terminals of 79 columns by 22 rows, and applications that remember their window size when closed shrink further each time. Expected behaviour: Windows should not be resized unless they exceed the viewport size. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1287472/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 996150] Re: Rhythmbox writes wrong ID3 tags when multiple files are changed
The importance of this bug for a LTS release shouldn't be set to low. It takes a lot of time to correct the ID3 tags, the fastest way is probably to recover the files from a backup. I'll try to upgrade to 2.97 from the PPA linked in here http://www.webupd8.org/2012/10/rhythmbox-298-released-install-it-in.html (they say 2.98 has another bug). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/996150 Title: Rhythmbox writes wrong ID3 tags when multiple files are changed Status in The Rhythmbox Music Management Application: Fix Released Status in “rhythmbox” package in Ubuntu: Fix Released Status in “rhythmbox” source package in Precise: Triaged Status in Baltix GNU/Linux: Confirmed Bug description: Changing the ID3 tags (e.g. 'Title') of multiple files in Rhythmbox will write the first changed 'Title' to all subsequently changes files. How to reproduce: 1. Open Rhythmbox in Ubuntu 12.04 2. Select an Album or Artist with more than one song 3. Change the title of the first song (right click, preferences, change title, next or submit) 4. Change the title of the next song and so on 5. Open the folder for that Album in Nautilus and check the ID3 tags in the preferences of each file 6. Recognize that all changed titles have the title of the first changed song Example Before change: Abba - blablub1 Abba - blablub2 Abba - blablub3 Change in Rhythmbox to: Abba - Dancing Queen Abba - Thank you for the music Abba - Money Money Money After change (in ID3 tags of the files): Abba - Dancing Queen Abba - Dancing Queen (although this is 'Thank you for the music') Abba - Dancing Queen (although this is 'Money Money Money') I could reproduce this error on 3 completely different PCs with completely different songs. To manage notifications about this bug go to: https://bugs.launchpad.net/rhythmbox/+bug/996150/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1261301] Re: Double nm-applet icon in system tray (lxde)
Michal, what package? -- 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/1261301 Title: Double nm-applet icon in system tray (lxde) Status in Network Menu: New Status in “network-manager-applet” package in Ubuntu: Confirmed Bug description: Installed clean 14.04 on toshiba ac100 netbook (tegra2 based). After installation I have two icons of nm-applet in system tray. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager-gnome 0.9.8.0-1ubuntu6 Uname: Linux 3.1.10-6-ac100 armv7l ApportVersion: 2.12.7-0ubuntu2 Architecture: armhf CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDesktop: LXDE Date: Mon Dec 16 11:49:43 2013 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d IpRoute: default via 10.0.2.1 dev wlan0 proto static 10.0.2.0/24 dev wlan0 proto kernel scope link src 10.0.2.2 metric 9 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true PciNetwork: SourcePackage: network-manager-applet UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH macbooknet805db024-c88c-45c3-b523-39994f3b6ac7 802-11-wireless 1387179995 Пн. 16 дек. 2013 11:46:35 yes no /org/freedesktop/NetworkManager/Settings/1 stuwhome 70785e55-2770-49ff-aeb0-62cdbb667e86 802-11-wireless 1387133892 Вс. 15 дек. 2013 22:58:12 yes 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.8.4connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-network/+bug/1261301/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1261301] Re: Double nm-applet icon in system tray (lxde)
indicator-network? A few other packages are dependant on it. -- 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/1261301 Title: Double nm-applet icon in system tray (lxde) Status in Network Menu: New Status in “network-manager-applet” package in Ubuntu: Confirmed Bug description: Installed clean 14.04 on toshiba ac100 netbook (tegra2 based). After installation I have two icons of nm-applet in system tray. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager-gnome 0.9.8.0-1ubuntu6 Uname: Linux 3.1.10-6-ac100 armv7l ApportVersion: 2.12.7-0ubuntu2 Architecture: armhf CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDesktop: LXDE Date: Mon Dec 16 11:49:43 2013 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d IpRoute: default via 10.0.2.1 dev wlan0 proto static 10.0.2.0/24 dev wlan0 proto kernel scope link src 10.0.2.2 metric 9 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true PciNetwork: SourcePackage: network-manager-applet UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH macbooknet805db024-c88c-45c3-b523-39994f3b6ac7 802-11-wireless 1387179995 Пн. 16 дек. 2013 11:46:35 yes no /org/freedesktop/NetworkManager/Settings/1 stuwhome 70785e55-2770-49ff-aeb0-62cdbb667e86 802-11-wireless 1387133892 Вс. 15 дек. 2013 22:58:12 yes 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.8.4connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-network/+bug/1261301/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
Did you activate printer sharing some time ago? -- 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 1278062] Re: firefox crashes on startup (but apparently layunched properly to enable me to post this)
Tested XFCE. Everything works fine. Using Box for GTK and icons (AMD64).
--
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/1278062
Title:
firefox crashes on startup (but apparently layunched properly to
enable me to post this)
Status in “firefox” package in Ubuntu:
Confirmed
Bug description:
I tried launching from a terminal window after the first crash and got
this:
~$ firefox
(process:2974): GLib-CRITICAL **: g_slice_set_config: assertion
'sys_page_size == 0' failed
Segmentation fault (core dumped)
~$
~$ lsb_release -rd
Description: Ubuntu Trusty Tahr (development branch)
Release: 14.04
~$ apt-cache policy firefox
firefox:
Installed: 25.0+build3-0ubuntu0.13.10.1
Candidate: 25.0+build3-0ubuntu0.13.10.1
Version table:
*** 25.0+build3-0ubuntu0.13.10.1 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
100 /var/lib/dpkg/status
~$
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: firefox 25.0+build3-0ubuntu0.13.10.1
ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2
Uname: Linux 3.13.0-8-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.13.2-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: a 1919 F pulseaudio
BuildID: 20131028112446
CRDA: Error: [Errno 2] No such file or directory: 'iw'
Channel: Unavailable
CrashCounter: 1
CurrentDesktop: LXDE
Date: Sun Feb 9 05:43:26 2014
ExecutablePath: /usr/lib/firefox/firefox
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
InstallationDate: Installed on 2013-11-22 (78 days ago)
InstallationMedia: Lubuntu 14.04 Trusty Tahr - Alpha amd64 (20131102)
IpRoute:
default via 192.168.0.1 dev wlan0 proto static
192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.101
metric 9
MostRecentCrashID: bp-3359569a-fc3a-40e2-978d-e68d72120711
PrefSources:
prefs.js
[Profile]/extensions/{3d7eb24f-2740-49df-8937-200b1cc08f8a}/defaults/preferences/flashblock.js
[Profile]/extensions/{0545b830-f0aa-4d7e-8820-50a4629a56fe}/defaults/preferences/defaults.js
ProcCmdline: /usr/lib/firefox/firefox
Profiles: Profile0 (Default) - LastVersion=25.0/20131028112446
RelatedPackageVersions: gecko-mediaplayer 1.0.8-4ubuntu1
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
RunningIncompatibleAddons: False
SegvAnalysis: Skipped: missing required field Disassembly
Signal: 11
SourcePackage: firefox
SubmittedCrashIDs: bp-3359569a-fc3a-40e2-978d-e68d72120711
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 02/17/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.12
dmi.board.name: NutMeg
dmi.board.vendor: PEGATRON CORPORATION
dmi.board.version: 1.02
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd02/17/2009:svnHP-Pavilion:pnFQ578AAR-ABAs3707c:pvr:rvnPEGATRONCORPORATION:rnNutMeg:rvr1.02:cvnHewlett-Packard:ct3:cvrChassisVersion:
dmi.product.name: FQ578AAR-ABA s3707c
dmi.sys.vendor: HP-Pavilion
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1278062/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-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 1245878] Re: Cannot connect to open network with captive portal
** Changed in: network-manager (Ubuntu) Assignee: TheAvengers (avengers) = (unassigned) -- 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/1245878 Title: Cannot connect to open network with captive portal Status in “network-manager” package in Ubuntu: New Bug description: Visit a location with an open wireless network which requires you to click agree or similar before connecting to the internet proper - a so-called captive portal. Using system image 5 on mako I am unable to make such a connection. I can see the network, click on it in the network-indicator, but I don't get an IP address, and no way to visit the agree page. I can connect to other open (and secure) networks just fine, and other devices can connect to the problem network (but prompt to agree in a browser). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1245878/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
Perhaps you turned something on one time and later off again. There is an extra BrowseAddress @LOCAL in your cupsd.conf, and a SystemGroup lpadmin. The latter has moved into /etc/cups/cups-files.conf with CUPS 1.6.x. -- 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 1280869] Re: Please provide -dbg packages for glamor-egl
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: glamor-egl (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glamor-egl in Ubuntu. https://bugs.launchpad.net/bugs/1280869 Title: Please provide -dbg packages for glamor-egl Status in “glamor-egl” package in Ubuntu: Confirmed Bug description: If glamor crashes, one needs to rebuild the package with debugging symbols to debug. It would be nice if the symbols could be installed from the repository, like many of the other xserver-xorg-video packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glamor-egl/+bug/1280869/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1285349] Re: While hovering indicator menus and crossing to a different monitor, the hover does does not continue on the second monitor
Based on Marco's comments, this bug is invalid. However, the Autopilot test that fails needs to be fixed to account for the new behavior. That will be handled in a separate bug. ** Changed in: unity Status: Triaged = Invalid ** Changed in: unity (Ubuntu) Status: Triaged = Invalid ** Changed in: unity Assignee: Christopher Townsend (townsend) = (unassigned) ** Changed in: unity (Ubuntu) Assignee: Christopher Townsend (townsend) = (unassigned) -- 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/1285349 Title: While hovering indicator menus and crossing to a different monitor, the hover does does not continue on the second monitor Status in Unity: Invalid Status in “unity” package in Ubuntu: Invalid Bug description: When hovering over indicator entries to reveal the menu and switching to different indicators and then crossing into a second monitor, the last indicator that was hovered on the first monitor stays open and the hovering will not continue on the second monitor. This is a regression found in the unity.tests.test_panel.PanelCrossMonitorsTests.test_hovering_indicators_on_multiple_monitors Autopilot test. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1285349/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1281091] Re: Xorg crashed with SIGABRT in xdl_xs115_atiddxPixmapIsTypeOf()
*** This bug is a duplicate of bug 1279412 *** https://bugs.launchpad.net/bugs/1279412 Thank you for taking the time to help Ubuntu and for reporting this bug, but I believe this bug is a duplicate of #1279412 so I have marked it as so. ** This bug has been marked a duplicate of bug 1279412 Xorg crashed with SIGABRT in xdl_xs115_atiddxPixmapIsTypeOf() -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1281091 Title: Xorg crashed with SIGABRT in xdl_xs115_atiddxPixmapIsTypeOf() Status in “fglrx-installer” package in Ubuntu: Confirmed Bug description: while starting to play 3gp on vlc. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: xserver-xorg-core 2:1.15.0-1ubuntu6 ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.13.2-0ubuntu4 Architecture: amd64 CrashCounter: 1 Date: Mon Feb 17 12:11:52 2014 ExecutablePath: /usr/bin/Xorg ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: Signal: 6 SourcePackage: xorg-server StacktraceTop: xdl_xs115_atiddxPixmapIsTypeOf () from /usr/lib/x86_64-linux-gnu/xorg/extra-modules/modules/drivers/fglrx_drv.so atiddxPixmapIsTypeOf () from /usr/lib/x86_64-linux-gnu/xorg/extra-modules/modules/drivers/fglrx_drv.so X740XvPutImage () from /usr/lib/x86_64-linux-gnu/xorg/extra-modules/modules/amdxmm.so ?? () ?? () Title: Xorg crashed with SIGABRT in xdl_xs115_atiddxPixmapIsTypeOf() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1281091/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1099755] Re: Upgrade wpa_supplicant from 1.0 to 2.1
Filing this as a Feature Freeze Exception now, 1.0 is very old (two years old), now considered end of life, and 2.0 has been released a year ago. I have built 2.0 in my PPA and provided it for testing with no issues reported so far, and have been running it for over a month. I will prepare an updated package for 2.1 and provide it for more spot checking. In the interest of continued upstream support for the support lifetime of trusty, I think we should upgrade to 2.1. ** Summary changed: - Upgrade wpa_supplicant from 1.0 to 2.1 + [FFE] Upgrade wpa_supplicant from 1.0 to 2.1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1099755 Title: [FFE] Upgrade wpa_supplicant from 1.0 to 2.1 Status in “wpa” package in Ubuntu: Triaged Status in “wpa” package in Debian: New Bug description: New releases of wpa_supplicant are available: 1.1 (released 2012-11-06) and 2.0 (released 2013-01-12). They have bugfixes that look like they’re relevant to the frequent disconnects I’m seeing on the MIT network; in particular, * improved PMKSA cache expiration to avoid unnecessary disconnections To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1099755/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1261301] Re: Double nm-applet icon in system tray (lxde)
Yes, none of those packages are in use on a traditional unity7 desktop. If you want the preview unity8 session, I'm afraid you'll have to deal with the double indicator, otherwise no network control under unity8 will be possible. -- 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/1261301 Title: Double nm-applet icon in system tray (lxde) Status in Network Menu: New Status in “network-manager-applet” package in Ubuntu: Confirmed Bug description: Installed clean 14.04 on toshiba ac100 netbook (tegra2 based). After installation I have two icons of nm-applet in system tray. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager-gnome 0.9.8.0-1ubuntu6 Uname: Linux 3.1.10-6-ac100 armv7l ApportVersion: 2.12.7-0ubuntu2 Architecture: armhf CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDesktop: LXDE Date: Mon Dec 16 11:49:43 2013 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d IpRoute: default via 10.0.2.1 dev wlan0 proto static 10.0.2.0/24 dev wlan0 proto kernel scope link src 10.0.2.2 metric 9 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true PciNetwork: SourcePackage: network-manager-applet UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH macbooknet805db024-c88c-45c3-b523-39994f3b6ac7 802-11-wireless 1387179995 Пн. 16 дек. 2013 11:46:35 yes no /org/freedesktop/NetworkManager/Settings/1 stuwhome 70785e55-2770-49ff-aeb0-62cdbb667e86 802-11-wireless 1387133892 Вс. 15 дек. 2013 22:58:12 yes 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.8.4connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-network/+bug/1261301/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 840777] Re: Muting sound indicator in Unity Greeter does not mute sound on login
mpt, I think there's some confusion. Lars and you want a system-wide volume. John wants a per-user volume (i.e. like we have today, just with the greeter reflecting the user's volume). With per-user volume, in your example when B logs in, B will have a muted sound. That's the point of changing the greeter volume when B is selected. I have implemented this in the attached branch inside indicator-sound (it uses AccountsService to synchronize user volume like we do for other settings -- keyboard layout, preferred desktop session, etc). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/840777 Title: Muting sound indicator in Unity Greeter does not mute sound on login Status in Ayatana Design: Fix Committed Status in Sound Menu: Invalid Status in Unity Greeter: Invalid Status in “pulseaudio” package in Ubuntu: Triaged Status in “pulseaudio” source package in Raring: New Bug description: I am using beta edition of Ubuntu 11.10,with lightdm 0.9.3-0ubuntu8,and unity 4.12.0-0ubuntu2, There is a new feature in Display Manager(well,I didn't notice it in gdm,but it might have been there as well),That you can mute the sound so that login sound wont play(This option exists in the top of the lightdm login page,when you turn on ubuntu and load it)However,Login sound will still play and sound settings will change regardless of what you choose. I should add that,this happens only after a reboot or shutdown,boot again,and not when you logout and login again Desired solution: - Any changes made to the volume control in the Unity Greeter should carry through to the logged in session and vice versa. - For example, if a user changes or mutes the volume in the Unity Greeter, when they are logged in to their session this value should be carried over - The other way around is also true, if a user changes or mutes the volume in their session, when they log out this value should be displayed in the greeter. - Sound settings are stored individually on a per user account basis. The sound settings displayed in the greeter should change in line with the currently focused user account. So for example User A is currently focused and has has volume at 100%. If the focus in the greeter is changed to User B (who has volume muted), the sound indicator should change to display the muted state. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/840777/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1099755] Re: [FFE] Upgrade wpa_supplicant from 1.0 to 2.1
I will attach the usual changelog diffs and build logs specific to 2.1 shortly. Manual esting that was done for 2.0: - scanning, connecting, etc. (via NM) - WPA2 personal - WPA2 enterprise (PEAP, with certificates and password) There are also autopkgtests run via network-manager which exercise wpasupplicant features, which should trigger for every new upload of wpa. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1099755 Title: [FFE] Upgrade wpa_supplicant from 1.0 to 2.1 Status in “wpa” package in Ubuntu: New Status in “wpa” package in Debian: New Bug description: New releases of wpa_supplicant are available: 1.1 (released 2012-11-06) and 2.0 (released 2013-01-12) and 2.1 (released 2014-02-04). 2.1 contains a number of bugfixes relevant to frequent disconnects some might be seeing on networks where there is a lot of roaming, some IBSS (ad-hoc) fixes, etc. http://lists.shmoo.com/pipermail/hostap/2014-February/029440.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1099755/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.
How can dowload this SW http://nl.archive.ubuntu.com/ubuntu/pool/main/k/kde4libs/libnepomukutils4_4.11.3-0ubuntu0.1_amd64.deb -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1218322 Title: Can't set keyboard layout change to alt+shift, ctrl+shift, etc. Status in Gnome Settings Daemon: Invalid Status in Ubuntu GNOME: Confirmed Status in “gnome-control-center” package in Ubuntu: Fix Released Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “gnome-settings-daemon” source package in Saucy: Triaged Status in “gnome-control-center” package in ALT Linux: Unknown Status in “gnome-control-center” package in Baltix: New Status in “gnome-control-center” package in Gentoo Linux: Invalid Status in “gnome-control-center” package in Mandriva: Invalid Bug description: *** The old PPA, ppa:attente/1218322 is superceded by the following one. You can remove the old repository using ppa-purge. *** A PPA which should provide some relief for this issue is available at https://launchpad.net/~attente/+archive/modifier-only-input-switch. To install: sudo add-apt-repository ppa:attente/modifier-only-input-switch sudo apt-get update sudo apt-get upgrade (log out, log in) If the packages improve the situation for you, you can pin them using: sudo apt-mark hold compiz sudo apt-mark hold gnome-settings-daemon sudo apt-mark hold unity If the packages don't work for you, you can purge them using: sudo ppa-purge ppa:attente/modifier-only-input-switch === compiz === Impact: modifier-only key bindings need to be independent of key-press order, there's no support for double tapping two modifier keys of the same type Test case: - add at least two input sources through gnome-control-center's text entry settings - use gsettings to set the input switching shortcut to ctrl+left shift: gsettings set org.gnome.desktop.wm.keybindings switch-input-source ['PrimaryShift_L'] - holding left shift, press and release ctrl - the current input source should change Regression potential: possible, but highly unlikely, that some key bindings may be triggered due to the removal of some code that would normally prevent a possible tap from occurring. === unity === Impact: gnome-settings-daemon eats modifier-only shortcuts preventing them from propagating down to applications Test case: - open gnome-control-center's text input settings - set the next input source key binding to ctrl+left shift - open gnome-terminal - press ctrl+shift+t - gnome-terminal should open a new tab Regression potential: the additional input switch key bindings could collide with other functionality such as opening the dash or hud === gnome-control-center === Impact: the UI to change the layout switching keys doesn't work Test case: - open gnome-control-center's text input settings - click on the next layout key entry - try entering a key combinaison (e.g ctrl-space) - the UI should reflect the new keys Regression potential: that UI was not working before, it should only be an improvement (some key combos are not working as expected, that's another issue and shouldn't be mixed with this one) === gnome-settings-daemon === Impact: attempting to change keyboard layouts using only modifier keys doesn't work Test case: - add at least two input sources through gnome-control-center's text entry settings - use gsettings to set the input switching shortcut to ctrl+left shift: gsettings set org.gnome.desktop.wm.keybindings switch-input-source ['PrimaryShift_L'] - press and release ctrl+left shift - the current input source should change Regression potential: The input switching shortcut might capture other non-modifier shortcuts, but users will need to consider this when choosing their switching shortcut anyways. For users this bug affects, this represents a working solution for a critical bug. -- Test results for different keyboard layout change hotkeys may be viewed and added in the Google Docs table, created by Norbert (https://docs.google.com/spreadsheet/ccc?key=0Ao5e713Ig9g_dEJrX2NRYlpLWWVzSWxsVXU4ck9HYVEusp=sharing). -- Recent discovered bugs related to keyboard layouts: * keyboard layout settings must be consistent between gnome-control-center keyboard, indicator-keyboard and gnome-tweak-tool and /etc/default/keyboard (bug 1270574) * Ubuntu 14.04 should have gnome-tweak-tool installed by default because of many settings that are missed gnome-control-center (bug 1270572) Separate bug reports for individual layout switching hotkey combinations: Super+Space and Shift+Super+Space: * Unity greeter (bug 1245137); * Unity session (bug 1245136); * lock screen - gnome-screensaver (bug
[Desktop-packages] [Bug 1099755] Re: [FFE] Upgrade wpa_supplicant from 1.0 to 2.1
Back to NEW, will transition to Triaged when the FFE is acked by the release team. ** Description changed: New releases of wpa_supplicant are available: 1.1 (released 2012-11-06) - and 2.0 (released 2013-01-12). They have bugfixes that look like - they’re relevant to the frequent disconnects I’m seeing on the MIT - network; in particular, + and 2.0 (released 2013-01-12) and 2.1 (released 2014-02-04). - * improved PMKSA cache expiration to avoid unnecessary - disconnections + 2.1 contains a number of bugfixes relevant to frequent disconnects some + might be seeing on networks where there is a lot of roaming, some IBSS + (ad-hoc) fixes, etc. + + http://lists.shmoo.com/pipermail/hostap/2014-February/029440.html ** Changed in: wpa (Ubuntu) Status: Triaged = New ** Changed in: wpa (Ubuntu) Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1099755 Title: [FFE] Upgrade wpa_supplicant from 1.0 to 2.1 Status in “wpa” package in Ubuntu: New Status in “wpa” package in Debian: New Bug description: New releases of wpa_supplicant are available: 1.1 (released 2012-11-06) and 2.0 (released 2013-01-12) and 2.1 (released 2014-02-04). 2.1 contains a number of bugfixes relevant to frequent disconnects some might be seeing on networks where there is a lot of roaming, some IBSS (ad-hoc) fixes, etc. http://lists.shmoo.com/pipermail/hostap/2014-February/029440.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1099755/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1283736] Re: Xorg crashed with SIGABRT
** Information type changed from Private to Public ** Package changed: xorg-server (Ubuntu) = xserver-xorg-video-ati (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1283736 Title: Xorg crashed with SIGABRT Status in “xserver-xorg-video-ati” package in Ubuntu: Confirmed Bug description: After logging in a crash notification popped-up. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: xserver-xorg-core 2:1.15.0-1ubuntu6 [modified: usr/lib/xorg/modules/extensions/libglx.so] ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CrashCounter: 1 Date: Sun Feb 23 00:08:01 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.6, 3.13.0-11-generic, x86_64: installed virtualbox, 4.3.6, 3.13.0-8-generic, x86_64: installed ExecutablePath: /usr/bin/Xorg ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Bonaire XTX [Radeon R7 260X] [1002:6658] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:2274] InstallationDate: Installed on 2014-02-08 (15 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140206) MachineType: Gigabyte Technology Co., Ltd. P55A-UD3 ProcCmdline: /usr/bin/X :0 -background none -verbose -auth /var/run/gdm/auth-for-gdm-QbU80P/database -seat seat0 -nolisten tcp vt7 ProcEnviron: LANG=en_US.UTF-8 TERM=linux PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-11-generic root=UUID=07a1c257-b925-4127-85b7-ece7b274321d ro rootflags=subvol=@ quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so Title: Xorg crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 08/10/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F11 dmi.board.name: P55A-UD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF11:bd08/10/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55A-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55A-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: P55A-UD3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0~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-1ubuntu2 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: Sun Feb 23 15:32:55 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech Logitech USB Headset KEYBOARD, id 8 inputLogitech USB-PS/2 Optical Mouse MOUSE, id 9 inputAT Translated Set 2 keyboard KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.0-1ubuntu6 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1283736/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1282024] Re: Xorg crashed with SIGSEGV in _XSERVTransClose()
** Information type changed from Private to Public -- 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/1282024 Title: Xorg crashed with SIGSEGV in _XSERVTransClose() Status in “xorg-server” package in Ubuntu: New Bug description: Xorg crashed with SIGSEGV in CloseWellKnownConnections() ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: xserver-xorg-core 2:1.15.0-1ubuntu6 ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2 Uname: Linux 3.13.0-8-generic i686 ApportVersion: 2.13.2-0ubuntu5 Architecture: i386 Date: Wed Feb 19 12:28:27 2014 ExecutablePath: /usr/bin/Xorg InstallationDate: Installed on 2014-01-14 (36 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140113) ProcCmdline: /usr/bin/X :0 -background none -verbose -auth /var/run/gdm/auth-for-gdm-AHbqOw/database -seat seat0 -nolisten tcp vt7 ProcEnviron: LANG=ru_RU.UTF-8 TERM=linux PATH=(custom, no user) SegvAnalysis: Segfault happened at: 0xb6ff5b5e:cmpw $0xb858,(%eax) PC (0xb6ff5b5e) ok source $0xb858 ok destination (%eax) (0xd27f074e) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: xorg-server StacktraceTop: ?? () ?? () CloseWellKnownConnections () ?? () FatalError () Title: Xorg crashed with SIGSEGV in CloseWellKnownConnections() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1282024/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1277985] Re: Xorg crashed with SIGABRT in OsAbort()
** Information type changed from Private to Public -- 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/1277985 Title: Xorg crashed with SIGABRT in OsAbort() Status in “xorg-server” package in Ubuntu: New Bug description: restarted computer after installing updates, system booted into wallpaper, no menu bar, and this error message, after a few seconds it reloaded the display system and now everything is working fine. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: xserver-xorg-core 2:1.15.0-1ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2 Uname: Linux 3.13.0-7-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu2 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CrashCounter: 1 Date: Fri Feb 7 15:50:50 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExecutablePath: /usr/bin/Xorg ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GF104 [GeForce GTX 460] [10de:0e22] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:835d] InstallationDate: Installed on 2014-01-17 (22 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20131231) MachineType: Hewlett-Packard p7-1154 ProcCmdline: /usr/bin/X -hostname :0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-8-generic root=UUID=324d18bb-aec8-4a28-b39c-023102955f99 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: OsAbort () ?? () FatalError () ?? () ?? () SystemImageInfo: Error: [Errno 2] No such file or directory: 'system-image-cli' Title: Xorg crashed with SIGABRT in OsAbort() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: audio pulse pulse-access video dmi.bios.date: 08/16/2011 dmi.bios.vendor: AMI dmi.bios.version: 7.07 dmi.board.name: 2ACD dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.01 dmi.chassis.asset.tag: 4CE135014F dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvr7.07:bd08/16/2011:svnHewlett-Packard:pnp7-1154:pvr:rvnPEGATRONCORPORATION:rn2ACD:rvr1.01:cvnHewlett-Packard:ct3:cvr: dmi.product.name: p7-1154 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu4 version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.0.1-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.0.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu3 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-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.909-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sat Feb 8 18:37:15 2014 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) open /dev/fb0: No such file or directory open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.0-1ubuntu3 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1277985/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1281562] Re: Xorg problem (apport gave no details, sorry)
** Information type changed from Private to Public -- 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/1281562 Title: Xorg problem (apport gave no details, sorry) Status in “xorg-server” package in Ubuntu: Confirmed Bug description: Apport came up for unknown reason, bug seems to be in Xorg according to apport. Everything seems to work OK though. Sorry I can't be more clear ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: xserver-xorg-core 2:1.15.0-1ubuntu6 ProcVersionSignature: Ubuntu 3.13.0-8.28-generic 3.13.2 Uname: Linux 3.13.0-8-generic i686 ApportVersion: 2.13.2-0ubuntu4 Architecture: i386 Date: Tue Feb 18 13:13:34 2014 ExecutablePath: /usr/bin/Xorg InstallationDate: Installed on 2014-01-09 (40 days ago) InstallationMedia: Lubuntu 14.04 Trusty Tahr - Alpha i386 (20140102) ProcCmdline: /usr/bin/X -core :1 -seat seat0 -auth /var/run/lightdm/root/:1 -nolisten tcp vt8 -novtswitch ProcEnviron: Signal: 6 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1281562/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1279274] Re: Xorg crashed with SIGABRT in OsAbort()
** Information type changed from Private to Public -- 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/1279274 Title: Xorg crashed with SIGABRT in OsAbort() Status in “xorg-server” package in Ubuntu: New Bug description: Xorg crashed ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: xserver-xorg-core 2:1.15.0-1ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CrashCounter: 1 Date: Wed Feb 12 13:22:32 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExecutablePath: /usr/bin/Xorg ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7560D] [1002:9904] (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:0123] InstallationDate: Installed on 2013-12-31 (42 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-8-generic root=UUID=131b0a13-564c-47ff-8d9d-642c2f13f5f9 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: OsAbort () ?? () FatalError () ?? () from /usr/lib/xorg/modules/libexa.so ?? () from /usr/lib/xorg/modules/libexa.so SystemImageInfo: Error: [Errno 2] No such file or directory: 'system-image-cli' Title: Xorg crashed with SIGABRT in OsAbort() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 01/09/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A88XM-HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd01/09/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XM-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu4 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.0.1-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.0.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.15.0-1ubuntu4 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-1ubuntu2 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: Wed Feb 12 13:22:38 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.0-1ubuntu4 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1279274/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1283719] Re: Xorg crashed with SIGABRT in do_sigtimedwait(), black screen after boot
** Information type changed from Private to Public -- 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/1283719 Title: Xorg crashed with SIGABRT in do_sigtimedwait(), black screen after boot Status in “xorg-server” package in Ubuntu: New Bug description: I'm using Ubuntu gnome 14.04,everything up to date. Since yesterday I couldn't start Ubuntu: after plymouth the screen remained all black. I could only access to ttyx and typed startx (after I logged on) and it keept saying no protocol specified ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: xserver-xorg-core 2:1.15.0-1ubuntu6 ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4 Uname: Linux 3.13.0-12-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CrashCounter: 1 Date: Sun Feb 23 12:02:17 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExecutablePath: /usr/bin/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV560 [Radeon X1650 XT] [1002:7291] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Device [174b:e140] Subsystem: PC Partner Limited / Sapphire Technology Device [174b:e141] InstallationDate: Installed on 2014-01-26 (27 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140121.1) MachineType: MSI MS-7519 ProcCmdline: /usr/bin/X :0 -background none -verbose -auth /var/run/gdm/auth-for-gdm-YHFhlX/database -seat seat0 -nolisten tcp vt7 ProcEnviron: LANG=fr_FR.UTF-8 TERM=linux PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-12-generic root=UUID=a38cfe0c-de6f-4f34-8c1e-61fd6aa3c9af ro rootflags=subvol=@ quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: vbeDoEDID () from /usr/lib/xorg/modules/libvbe.so ?? () from /usr/lib/xorg/modules/drivers/vesa_drv.so InitOutput () ?? () __libc_start_main (main=0x7f36f091ee50, argc=12, argv=0x7fff19147d48, init=optimized out, fini=optimized out, rtld_fini=optimized out, stack_end=0x7fff19147d38) at libc-start.c:285 Title: Xorg crashed with SIGABRT in vbeDoEDID() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 01/18/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.12 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P43 Neo-F (MS-7519) 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: MICRO-STAR INTERNATIONAL CO.,LTD dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.12:bd01/18/2010:svnMSI:pnMS-7519:pvr1.0:rvnMSI:rnP43Neo-F(MS-7519):rvr1.0:cvnMICRO-STARINTERNATIONALCO.,LTD:ct3:cvr1.0: dmi.product.name: MS-7519 dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52+git20140121.46d451c9-0ubuntu0sarvatt version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.0~git20140221.9b2fe7cf-0ubuntu0sarvatt3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.0~git20140221.9b2fe7cf-0ubuntu0sarvatt3 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.99+git20140206.8de6f7b2-0ubuntu0sarvatt version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910+git20140221.0b92b128-0ubuntu0sarvatt version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10+git20140220.480f0998-0ubuntu0sarvatt xserver.bootTime: Sun Feb 23 14:25:35 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.0-1ubuntu6 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1283719/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1275586] Re: Xorg crashed with SIGABRT in OsAbort()
** Package changed: xorg-server (Ubuntu) = xserver-xorg-video-intel (Ubuntu) ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1275586 Title: Xorg crashed with SIGABRT in OsAbort() Status in “xserver-xorg-video-intel” package in Ubuntu: Confirmed Bug description: I was watching a flash video, if that helps. I experienced a slight hang and switched to tty1 to check for error messages, where I found the following two: [47315.472858] [drm:i915_hangcheck_elapsed] *ERROR* stuck on render ring [47315.499808] [drm:i915_set_reset_status] *ERROR* render ring hung inside bo (0x1fa3000 ctx 2) at 0x1fa31c8 As I have this happen sometimes (about once a month) without further errors or noticeable effects, I switched back to my graphical session and continued, when the screen went black for a while and then went back to login, as usual when X would be terminated. Without logging back in, I checked the running processes and there were several user processes of graphical applications still running even though the user wasn't logged in anywhere. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Feb 3 01:13:37 2014 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.6, 3.11.0-14-generic, x86_64: installed vboxhost, 4.3.6, 3.11.0-15-generic, x86_64: installed ExecutablePath: /usr/bin/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer Device [1297:2020] InstallationDate: Installed on 2013-10-29 (96 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 005: ID 05ac:0304 Apple, Inc. Optical USB Mouse [Mitsumi] Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: A15HV01 A15HV01 MarkForUpload: True ProcCmdline: /usr/bin/X -core -gamma 0.7 :0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: OsAbort () ?? () FatalError () xf86VTSwitch () WakeupHandler () Title: Xorg crashed with SIGABRT in OsAbort() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 09/02/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.04.QUA dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: HURONRIVER dmi.board.vendor: INTEL Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.04.QUA:bd09/02/2011:svnA15HV01:pnA15HV01:pvrTobefilledbyO.E.M.:rvnINTELCorporation:rnHURONRIVER:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: A15HV01 dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: A15HV01 version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Mon Feb 3 01:14:41 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs:
[Desktop-packages] [Bug 1099755] Re: [FFE] Upgrade wpa_supplicant from 1.0 to 2.1
Just a question, isn't better to upload in debian and then sync rather than uploading on ubuntu only? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1099755 Title: [FFE] Upgrade wpa_supplicant from 1.0 to 2.1 Status in “wpa” package in Ubuntu: New Status in “wpa” package in Debian: New Bug description: New releases of wpa_supplicant are available: 1.1 (released 2012-11-06) and 2.0 (released 2013-01-12) and 2.1 (released 2014-02-04). 2.1 contains a number of bugfixes relevant to frequent disconnects some might be seeing on networks where there is a lot of roaming, some IBSS (ad-hoc) fixes, etc. http://lists.shmoo.com/pipermail/hostap/2014-February/029440.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1099755/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1261301] Re: Double nm-applet icon in system tray (lxde)
Thanks @saviq, you are correct. -- 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/1261301 Title: Double nm-applet icon in system tray (lxde) Status in Network Menu: New Status in “network-manager-applet” package in Ubuntu: Confirmed Bug description: Installed clean 14.04 on toshiba ac100 netbook (tegra2 based). After installation I have two icons of nm-applet in system tray. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager-gnome 0.9.8.0-1ubuntu6 Uname: Linux 3.1.10-6-ac100 armv7l ApportVersion: 2.12.7-0ubuntu2 Architecture: armhf CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDesktop: LXDE Date: Mon Dec 16 11:49:43 2013 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d IpRoute: default via 10.0.2.1 dev wlan0 proto static 10.0.2.0/24 dev wlan0 proto kernel scope link src 10.0.2.2 metric 9 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true PciNetwork: SourcePackage: network-manager-applet UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH macbooknet805db024-c88c-45c3-b523-39994f3b6ac7 802-11-wireless 1387179995 Пн. 16 дек. 2013 11:46:35 yes no /org/freedesktop/NetworkManager/Settings/1 stuwhome 70785e55-2770-49ff-aeb0-62cdbb667e86 802-11-wireless 1387133892 Вс. 15 дек. 2013 22:58:12 yes 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.8.4connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-network/+bug/1261301/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1232454] Re: Computer will suspend very soon because of inactivity. dialog when resuming from suspend
Sorry, I give up -- 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/1232454 Title: Computer will suspend very soon because of inactivity. dialog when resuming from suspend Status in Gnome Settings Daemon: Unknown Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Bug description: After upgrading to 13.10 today, every time I unlock my computer after leaving it for a long time I get this prompt: -- Power Automatic suspend Computer will suspend very soon because of inactivity. -- However, the computer doesn't actually suspend. And even if I do this manually (which works) and then resume, the prompt is still there (and in that case, not true at all). This is ugly and seems broken! As suggested by the upstream Gnome bug report, this is an issue pertaining to Ubuntu's lack of systemd integration. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: ubuntu-desktop 1.304 ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 Uname: Linux 3.11.0-8-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu1 Architecture: i386 Date: Sat Sep 28 15:32:42 2013 InstallationDate: Installed on 2012-08-03 (420 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) MarkForUpload: True SourcePackage: ubuntu-meta UpgradeStatus: Upgraded to saucy on 2013-09-28 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1232454/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1287745] [NEW] Some more Autopilot Panel tests need fixing
Public bug reported: In drilling down on some more Autopilot test failures, some Panel tests will fail, either 100% of the time or occasionally. 1. Some Panel tests will fail if the previous test leaves the system with only the Launcher on the primary monitor. 2. test_window_buttons_show_when_holding_show_menu_key can fail due to a race when pressing and releasing the Alt key. This sometimes opens the Hud during the test which is not expected. 3. test_hovering_indicators_on_multiple_monitors fails due to a change in how multi-monitor Panels are handled. The test needs fixed to account for the new behavior. ** Affects: unity Importance: Medium Assignee: Christopher Townsend (townsend) Status: In Progress ** Affects: unity (Ubuntu) Importance: Medium Assignee: Christopher Townsend (townsend) Status: In Progress ** Also affects: unity (Ubuntu) Importance: Undecided Status: New ** Changed in: unity Status: New = In Progress ** Changed in: unity (Ubuntu) Status: New = In Progress ** Changed in: unity Importance: Undecided = Medium ** Changed in: unity (Ubuntu) Importance: Undecided = Medium ** Changed in: unity (Ubuntu) Assignee: (unassigned) = Christopher Townsend (townsend) ** Changed in: unity Assignee: (unassigned) = Christopher Townsend (townsend) ** Changed in: unity Milestone: None = 7.2.0 -- 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/1287745 Title: Some more Autopilot Panel tests need fixing Status in Unity: In Progress Status in “unity” package in Ubuntu: In Progress Bug description: In drilling down on some more Autopilot test failures, some Panel tests will fail, either 100% of the time or occasionally. 1. Some Panel tests will fail if the previous test leaves the system with only the Launcher on the primary monitor. 2. test_window_buttons_show_when_holding_show_menu_key can fail due to a race when pressing and releasing the Alt key. This sometimes opens the Hud during the test which is not expected. 3. test_hovering_indicators_on_multiple_monitors fails due to a change in how multi-monitor Panels are handled. The test needs fixed to account for the new behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1287745/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1287747] [NEW] Trying to open an indicator on a second monitor when an indicator is open on the first monitor does not work correctly
Public bug reported: When you have an indicator opened on the first monitor and then cross over to the second monitor and then try to open an indicator on that monitor, the indicator opens in the wrong position on the second monitor and hovering does not work. ** Affects: unity Importance: Medium Status: Triaged ** Affects: unity (Ubuntu) Importance: Medium Status: Triaged ** Also affects: unity Importance: Undecided Status: New ** Changed in: unity Importance: Undecided = Medium ** Changed in: unity (Ubuntu) Importance: Undecided = Medium ** Changed in: unity Status: New = Triaged ** Changed in: unity (Ubuntu) Status: New = Triaged -- 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/1287747 Title: Trying to open an indicator on a second monitor when an indicator is open on the first monitor does not work correctly Status in Unity: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: When you have an indicator opened on the first monitor and then cross over to the second monitor and then try to open an indicator on that monitor, the indicator opens in the wrong position on the second monitor and hovering does not work. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1287747/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 994427] Re: Headphone doesn't mute loudpeakers on Fujitsu Siemens Lifebook S7110
I confirm this affecting 12.04.4 on a S7110 with NM10/ICH7 audio. -- 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/994427 Title: Headphone doesn't mute loudpeakers on Fujitsu Siemens Lifebook S7110 Status in “alsa-driver” package in Ubuntu: Confirmed Bug description: Under 11.10, when pluggin in a headphone, the loudspeakers were muted. Under 12.10 - even after a clean install - this doesn't work anymore. Additionally, there is no switch in alsamixer to manually mute the speakers. Headphones and speakers are always treated in parallel. No distinction possible. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alsa-base 1.0.25+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hss1850 F pulseaudio /dev/snd/pcmC1D0p: hss1850 F...m pulseaudio /dev/snd/controlC0: hss1847 F xfce4-volumed hss1850 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xf064 irq 46' Mixer name : 'Realtek ALC262' Components : 'HDA:10ec0262,10cf,0012 HDA:11c11040,11c10001,00100200' Controls : 29 Simple ctrls : 16 Card1.Amixer.info: Card hw:1 'Audio'/'C-Media INC. USB Audio at usb-:00:1d.1-1, full speed' Mixer name : 'USB Mixer' Components : 'USB0d8c:0001' Controls : 2 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'PCM',0 Capabilities: pvolume pvolume-joined pswitch pswitch-joined penum Playback channels: Mono Limits: Playback 0 - 37 Mono: Playback 37 [100%] [28.00dB] [on] Date: Fri May 4 09:21:21 2012 InstallationMedia: Xubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) PackageArchitecture: all ProcEnviron: LANGUAGE=de_DE:en TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/07/2008 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.34 dmi.board.name: FJNB1B5 dmi.board.vendor: FUJITSU dmi.board.version: CP279611-02 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU SIEMENS dmi.chassis.version: S7110 dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.34:bd02/07/2008:svnFUJITSUSIEMENS:pnLIFEBOOKS7110:pvr:rvnFUJITSU:rnFJNB1B5:rvrCP279611-02:cvnFUJITSUSIEMENS:ct10:cvrS7110: dmi.product.name: LIFEBOOK S7110 dmi.sys.vendor: FUJITSU SIEMENS mtime.conffile..etc.modprobe.d.alsa.base.conf: 2012-04-29T12:58:07.762933 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/994427/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1281158] Re: Firefox geolocation does not work
** 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/1281158 Title: Firefox geolocation does not work Status in The Mozilla Firefox Browser: Won't Fix Status in One Hundred Papercuts: New Status in “firefox” package in Ubuntu: New Bug description: The ability for websites to detect location does not work in the Ubuntu version of Firefox. For example: http://noc.to/geoloc The call to the Geolocation API will wait indefinitely or time out. This is because Ubuntu's Firefox packagers need to include a key for the Google Maps Geolocation API. See https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1231273/comments/7 and https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1231273/comments/8 To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1281158/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1275586] Re: EnterVT failed after chrome crashed the GPU
** Summary changed: - Xorg crashed with SIGABRT in OsAbort() + EnterVT failed after chrome crashed the GPU ** Summary changed: - EnterVT failed after chrome crashed the GPU + EnterVT failed after chrome crashed (but not wedged?) the GPU ** Summary changed: - EnterVT failed after chrome crashed (but not wedged?) the GPU + xf86VTSwitch failed after chrome crashed (but not wedged?) the GPU -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1275586 Title: xf86VTSwitch failed after chrome crashed (but not wedged?) the GPU Status in “xserver-xorg-video-intel” package in Ubuntu: Confirmed Bug description: I was watching a flash video, if that helps. I experienced a slight hang and switched to tty1 to check for error messages, where I found the following two: [47315.472858] [drm:i915_hangcheck_elapsed] *ERROR* stuck on render ring [47315.499808] [drm:i915_set_reset_status] *ERROR* render ring hung inside bo (0x1fa3000 ctx 2) at 0x1fa31c8 As I have this happen sometimes (about once a month) without further errors or noticeable effects, I switched back to my graphical session and continued, when the screen went black for a while and then went back to login, as usual when X would be terminated. Without logging back in, I checked the running processes and there were several user processes of graphical applications still running even though the user wasn't logged in anywhere. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Feb 3 01:13:37 2014 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.6, 3.11.0-14-generic, x86_64: installed vboxhost, 4.3.6, 3.11.0-15-generic, x86_64: installed ExecutablePath: /usr/bin/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer Device [1297:2020] InstallationDate: Installed on 2013-10-29 (96 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 005: ID 05ac:0304 Apple, Inc. Optical USB Mouse [Mitsumi] Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: A15HV01 A15HV01 MarkForUpload: True ProcCmdline: /usr/bin/X -core -gamma 0.7 :0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: OsAbort () ?? () FatalError () xf86VTSwitch () WakeupHandler () Title: Xorg crashed with SIGABRT in OsAbort() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 09/02/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.04.QUA dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: HURONRIVER dmi.board.vendor: INTEL Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.04.QUA:bd09/02/2011:svnA15HV01:pnA15HV01:pvrTobefilledbyO.E.M.:rvnINTELCorporation:rnHURONRIVER:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: A15HV01 dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: A15HV01 version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10
[Desktop-packages] [Bug 1232454] Re: Computer will suspend very soon because of inactivity. dialog when resuming from suspend
Does anyone know if this bug remains in 14.04? If so I suggest it adding it to the One Hundred Papercuts project. https://launchpad.net/hundredpapercuts Papercuts are easily fixable but very annoying bugs. -- 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/1232454 Title: Computer will suspend very soon because of inactivity. dialog when resuming from suspend Status in Gnome Settings Daemon: Unknown Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Bug description: After upgrading to 13.10 today, every time I unlock my computer after leaving it for a long time I get this prompt: -- Power Automatic suspend Computer will suspend very soon because of inactivity. -- However, the computer doesn't actually suspend. And even if I do this manually (which works) and then resume, the prompt is still there (and in that case, not true at all). This is ugly and seems broken! As suggested by the upstream Gnome bug report, this is an issue pertaining to Ubuntu's lack of systemd integration. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: ubuntu-desktop 1.304 ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 Uname: Linux 3.11.0-8-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu1 Architecture: i386 Date: Sat Sep 28 15:32:42 2013 InstallationDate: Installed on 2012-08-03 (420 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release i386 (20120423) MarkForUpload: True SourcePackage: ubuntu-meta UpgradeStatus: Upgraded to saucy on 2013-09-28 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1232454/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1275586] Re: xf86VTSwitch failed after chrome crashed (but not wedged?) the GPU
The root cause here is that the VT switch away from X fails [ioctl(xf86Info.consoleFd, VT_RELDISP, 1)] and the recovery mechanism of reacquiring DRM_MASTER also fails. I have no idea why. If you can provoke this bug, stracing X may be useful. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1275586 Title: xf86VTSwitch failed after chrome crashed (but not wedged?) the GPU Status in “xserver-xorg-video-intel” package in Ubuntu: Confirmed Bug description: I was watching a flash video, if that helps. I experienced a slight hang and switched to tty1 to check for error messages, where I found the following two: [47315.472858] [drm:i915_hangcheck_elapsed] *ERROR* stuck on render ring [47315.499808] [drm:i915_set_reset_status] *ERROR* render ring hung inside bo (0x1fa3000 ctx 2) at 0x1fa31c8 As I have this happen sometimes (about once a month) without further errors or noticeable effects, I switched back to my graphical session and continued, when the screen went black for a while and then went back to login, as usual when X would be terminated. Without logging back in, I checked the running processes and there were several user processes of graphical applications still running even though the user wasn't logged in anywhere. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Feb 3 01:13:37 2014 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.6, 3.11.0-14-generic, x86_64: installed vboxhost, 4.3.6, 3.11.0-15-generic, x86_64: installed ExecutablePath: /usr/bin/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer Device [1297:2020] InstallationDate: Installed on 2013-10-29 (96 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 005: ID 05ac:0304 Apple, Inc. Optical USB Mouse [Mitsumi] Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: A15HV01 A15HV01 MarkForUpload: True ProcCmdline: /usr/bin/X -core -gamma 0.7 :0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: OsAbort () ?? () FatalError () xf86VTSwitch () WakeupHandler () Title: Xorg crashed with SIGABRT in OsAbort() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 09/02/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.04.QUA dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: HURONRIVER dmi.board.vendor: INTEL Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.04.QUA:bd09/02/2011:svnA15HV01:pnA15HV01:pvrTobefilledbyO.E.M.:rvnINTELCorporation:rnHURONRIVER:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: A15HV01 dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: A15HV01 version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1
[Desktop-packages] [Bug 1283685] Re: Xorg crashed with SIGABRT in RRCrtcDetachScanoutPixmap()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg-server (Ubuntu) Status: New = Confirmed -- 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/1283685 Title: Xorg crashed with SIGABRT in RRCrtcDetachScanoutPixmap() Status in “xorg-server” package in Ubuntu: Confirmed Bug description: PlayonLInux with Starcraft2 : error with nvidia-prime ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: xserver-xorg-core 2:1.15.0-1ubuntu6 ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3 Uname: Linux 3.13.0-11-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 Date: Sun Feb 23 11:39:58 2014 ExecutablePath: /usr/bin/Xorg InstallationDate: Installed on 2014-02-17 (5 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140217) ProcCmdline: /usr/bin/X -core :1 -seat seat0 -auth /var/run/lightdm/root/:1 -nolisten tcp vt8 -novtswitch ProcEnviron: Signal: 6 SourcePackage: xorg-server StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so ?? () from /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so ?? () from /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so ?? () from /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so RRCrtcDetachScanoutPixmap () Title: Xorg crashed with SIGABRT in RRCrtcDetachScanoutPixmap() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1283685/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1287753] [NEW] Nvidia 334.21
Public bug reported: Provide Nvidia 334.21 drivers for ubuntu 14.04. This driver provides alot of performance improvements. Changlog: http://www.nvidia.com/download/driverResults.aspx/73666/en-us Added support for the following GPUs: GeForce GTX 750 Ti GeForce GTX 750 GeForce GTX 745 GeForce GTX TITAN Black Fixed a regression in the NVIDIA kernel module which caused it to improperly dereference a userspace pointer. This potential security issue was initially reported to the public at: http://forums.grsecurity.net/viewtopic.php?f=3t=3922 The regression did not affect NVIDIA GPU drivers before release 334. Fixed a bug that could cause OpenGL programs to hang after calling fork(2). Fixed a bug that could cause a multi-threaded OpenGL application to crash when one of its threads exits after the application has unloaded libGL. Added support for GPUs with VDPAU Feature Set E. See the README for details. On GPUs with VDPAU Feature Set E, VDPAU now supports more robust decode error handling at the cost of a minor performance impact. This can be disabled by setting the VDPAU_NVIDIA_DISABLE_ERROR_CONCEALMENT environment variable to 1. Added support for application profile rule patterns which are logical operations of subpatterns. See the README for details. Added support for a findfile application profile feature which allows the driver to apply profiles based on matching files in the same directory as the process executable. See the README for details. Fixed a bug that caused nvidia-installer to log the automatically selected answers to some user prompts without logging the prompt text itself, when running in silent mode. Improved performance of OpenGL applications when used in conjunction with the X driver's composition pipeline. The composition pipeline may be explicitly enabled by using the ForceCompositionPipeline or ForceFullCompositionPipeline MetaMode options, or implicitly enabled when certain features such as some XRandR transformations, rotation,Warp Blend, PRIME, and NvFBC are used. Fixed a bug that could cause nvidia-settings to compute incorrect gamma ramps when adjusting the color correction sliders. Updated the nvidia-settings control panel to allow the selection of display devices using RandR and target ID names when making queries targeted towards specific display devices. Fixed a bug that prevented some dropdown menus in the nvidia-settings control panel from working correctly on older versions of GTK+ (e.g. 2.10.x). Updated the nvidia-settings control panel to provide help text for application profile keys and suggestions for valid key names when configuring application profiles. Updated the nvidia-settings control panel to populate the dropdown menu of stereo modes with only those modes which are available. Fixed a bug that could cause applications using the OpenGL extension ARB_query_buffer_object to crash under Xinerama. Fixed a bug that caused high pixelclock HDMI modes (e.g. as used with 4K resolutions) to be erroneously reported as dual-link in the nvidia-settings control panel. Fixed a bug that could cause poor stereo synchronization in large multi-monitor setups using 3D Vision, due to failed hardwarehandshaking on some of the monitors. Fixed a bug that prevented some DisplayPort 1.2 displays from being properly restored after a VT switch. Renamed per GPU proc directories in /proc/driver/nvidia/gpus/ with GPU's bus location represented in domain:bus:device.function format. Added 64-bit EGL and OpenGL ES libraries to 64-bit driver packages. Changed format of Bus Location field reported in the /proc/driver/nvidia/gpus/0..N/information files from domain:bus.device.function to domain:bus:device.function to match the lspci format. Fixed a bug in the GLX_EXT_buffer_age extension where incorrect ages would be returned unless triple buffering was enabled. Updated the NVIDIA X driver to load the NVIDIA kernel module using `nvidia-modprobe`, rather than the XFree86 DDX helper function xf86LoadKernelModule(). Changed the driver's default behavior to stop deleting RandR 1.2 output corresponding to unused DisplayPort 1.2 devices. Deleting these outputs can confuse some applications. Added a new option, DeleteUnusedDP12Displays, which can be used to turn this behavior back on. This option can be enabled by running sudo nvidia-xconfig --delete- unused-dp12-displays Improved support for the __GL_SYNC_DISPLAY_DEVICE and VDPAU_NVIDIA_SYNC_DISPLAY_DEVICE environment variables in certain configurations. Both environment variables will now recognize all supported display device names. See Appendix C. Display Device Names and Appendix G. VDPAU Support in the README for more details. Improved performance of the X driver when handling large numbers of surface allocations. ** Affects:
[Desktop-packages] [Bug 1284458] Re: Xorg crashed with SIGABRT in RRCrtcDetachScanoutPixmap()
*** This bug is a duplicate of bug 1283685 *** https://bugs.launchpad.net/bugs/1283685 ** This bug has been marked a duplicate of bug 1283685 Xorg crashed with SIGABRT in RRCrtcDetachScanoutPixmap() ** Information type changed from Private to Public -- 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/1284458 Title: Xorg crashed with SIGABRT in RRCrtcDetachScanoutPixmap() Status in “xorg-server” package in Ubuntu: New Bug description: After suspend to ram. (I mean...) ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: xserver-xorg-core 2:1.15.0-1ubuntu6 ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4 Uname: Linux 3.13.0-12-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Feb 25 06:25:05 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExecutablePath: /usr/bin/Xorg GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0566] NVIDIA Corporation GF106M [GeForce GT 555M] [10de:0dce] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0566] MachineType: Acer Aspire 8951G ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-12-generic root=UUID=4c1d10ec-c93a-4910-a6f5-2520535de499 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: RRCrtcDetachScanoutPixmap () ?? () ?? () FreeClientResources () FreeAllResources () Title: Xorg crashed with SIGABRT in RRCrtcDetachScanoutPixmap() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 12/30/2011 dmi.bios.vendor: INSYDE dmi.bios.version: V1.13 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SM81_HR dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvrV1.13:bd12/30/2011:svnAcer:pnAspire8951G:pvrV1.13:rvnAcer:rnSM81_HR:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire 8951G dmi.product.version: V1.13 dmi.sys.vendor: Acer 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: Tue Feb 25 06:26:06 2014 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id6151 vendor CMO xserver.version: 2:1.15.0-1ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1284458/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
