[Desktop-packages] [Bug 1334495] Re: Two different fonts mixed to display Chinese text in all desktop applications
I experimented a bit more yesterday. I didn't find a option for the sub- locales in KDE, but installed language-selector-gnome, where it is possible to change. To be on the safe side, I just also directly edited /etc/default/locale as suggested by you. After reboot: cat /etc/default/locale LANG=de_DE.UTF-8 locale LANG=de_DE.UTF-8 LANGUAGE=de:en:zh:en LC_CTYPE=de_DE.UTF-8 LC_NUMERIC=de_DE.UTF-8 LC_TIME=de_DE.UTF-8 LC_COLLATE=de_DE.UTF-8 LC_MONETARY=de_DE.UTF-8 LC_MESSAGES=de_DE.UTF-8 LC_PAPER=de_DE.UTF-8 LC_NAME=de_DE.UTF-8 LC_ADDRESS=de_DE.UTF-8 LC_TELEPHONE=de_DE.UTF-8 LC_MEASUREMENT=de_DE.UTF-8 LC_IDENTIFICATION=de_DE.UTF-8 LC_ALL= The problem still exists. Additionally I tried some more programmes. My impression now is that the problem only exists with KDE, e.g. QT programmes and things like all window titles. In Gnome applications (I tried Geany and Pidgin) Chinese text is displayed normally, in Thunderbird too (not sure what toolkit thunderbird uses). I deinstalled fonts-arphic-ukai which seemed to be the italic font used. Now, text is still displayed using two different fonts, but the italic font changed. (I am using italic and normal to describe how the fonts look, but it is not equal to a text's attribute in Latin script. The difference between the two fonts could perhaps be compared to serif and sans serif in Latin script) In the font settings, everything is set to Ubuntu, except for the monospace font which is set to Monospace. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1334495 Title: Two different fonts mixed to display Chinese text in all desktop applications Status in “language-selector” package in Ubuntu: Incomplete Bug description: Bug: In all desktop applications, two different fonts are mixed to display Chinese text. I attached a screenshot of a paragraph of Chinese text in Kmail - some characters are displayed using a italic font, others in a normal font. The same problem exists in other applications, for example Dolphin or even Konsole. In Xterm, only the normal characters are displayed, where Dolphin displays italic characters Xterm leaves a white space. Websites are displayed fine, if I open the same mail in the web interface only one font is used. Background I' am using Kubuntu 14.04 with the language set to German in KDE settings. The output of locale looks a bit messed up, I don't know why, as in the KDE settings all formats are consistently set to German standard. locale LANG=de_DE.UTF-8 LANGUAGE=de:en:zh:en LC_CTYPE=de_DE.UTF-8 LC_NUMERIC=zh_CN.UTF-8 LC_TIME=zh_CN.UTF-8 LC_COLLATE=de_DE.UTF-8 LC_MONETARY=zh_CN.UTF-8 LC_MESSAGES=de_DE.UTF-8 LC_PAPER=zh_CN.UTF-8 LC_NAME=zh_CN.UTF-8 LC_ADDRESS=zh_CN.UTF-8 LC_TELEPHONE=zh_CN.UTF-8 LC_MEASUREMENT=zh_CN.UTF-8 LC_IDENTIFICATION=zh_CN.UTF-8 LC_ALL= fc-match: »DejaVuSans.ttf: DejaVu Sans Book« This is my first bug filed at launchpad. I filed it for language-selector as other related bugs I found were filed for the same package. If it isn't language-selector, perhaps you can point me to the right package? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1334495/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1334495] Re: Two different fonts mixed to display Chinese text in all desktop applications
Also, all characters in the attached text are very common, so it shouldn't be the case that some characters are displayed by a fall back font because they don't exist in the first choice. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1334495 Title: Two different fonts mixed to display Chinese text in all desktop applications Status in “language-selector” package in Ubuntu: Incomplete Bug description: Bug: In all desktop applications, two different fonts are mixed to display Chinese text. I attached a screenshot of a paragraph of Chinese text in Kmail - some characters are displayed using a italic font, others in a normal font. The same problem exists in other applications, for example Dolphin or even Konsole. In Xterm, only the normal characters are displayed, where Dolphin displays italic characters Xterm leaves a white space. Websites are displayed fine, if I open the same mail in the web interface only one font is used. Background I' am using Kubuntu 14.04 with the language set to German in KDE settings. The output of locale looks a bit messed up, I don't know why, as in the KDE settings all formats are consistently set to German standard. locale LANG=de_DE.UTF-8 LANGUAGE=de:en:zh:en LC_CTYPE=de_DE.UTF-8 LC_NUMERIC=zh_CN.UTF-8 LC_TIME=zh_CN.UTF-8 LC_COLLATE=de_DE.UTF-8 LC_MONETARY=zh_CN.UTF-8 LC_MESSAGES=de_DE.UTF-8 LC_PAPER=zh_CN.UTF-8 LC_NAME=zh_CN.UTF-8 LC_ADDRESS=zh_CN.UTF-8 LC_TELEPHONE=zh_CN.UTF-8 LC_MEASUREMENT=zh_CN.UTF-8 LC_IDENTIFICATION=zh_CN.UTF-8 LC_ALL= fc-match: »DejaVuSans.ttf: DejaVu Sans Book« This is my first bug filed at launchpad. I filed it for language-selector as other related bugs I found were filed for the same package. If it isn't language-selector, perhaps you can point me to the right package? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1334495/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1334954] Re: Complete HUAWEI Mobile broadband E352 support
Please state which Ubuntu version, linux kernel version, and usb_modeswitch version you are using and also the content of the udev popup message. The usb_modeswitch.conf file is for global configs and should not be used for individual device configuration, there should be a device config file named 12d1:14fe in the usb_modeswitch data package which you can find in /usr/share/usb_modeswitch/configPack.tar.gz What you have entered in usb_modeswitch.conf is an incomplete device config (no switch method/switch message) so I doubt it has any effect, you should remove that. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1334954 Title: Complete HUAWEI Mobile broadband E352 support Status in “usb-modeswitch” package in Ubuntu: New Bug description: usb_modeswitch kernel module tells me to report this bug :) The modem works fine, it's just not stable. Unplugging and reinserting creates a kernel oops that seems to prevent halting the system. First time I plugged it in, I got an U-DEV popup error message. A little after that, there was a question about PIN code and the modem worked. Unplugging and reinstering the device, it won't work. I have to reboot. I added four lines in usb_modeswitch.conf: DefaultVendor=12d1 DefaultProduct=14fe TargetVendor=12d1 TargetProduct=1506 At the last reboot, this made the U-DEV popup disappear and the modem asks for the PIN and works. The work_device.txt attachment shows the kernel log for this event. I will upload the log for when I unplug and reinsert the device as a separate file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1334954/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1334954] Re: Complete HUAWEI Mobile broadband E352 support
The kernel oops is btw from ModemManager and not from usb_modeswitch. Make sure by checking the system log (after removing the faulty config in usb_modeswitch.conf) that usb_modeswitch switches the dongle from 12d1:14fe to 12d1:1506 at every insert. If it does, then assign the bug to NetworkManager which should handle the dongles direct ethernet interface (cdc_ncm, huawei_cdc_ncm, and cdc_wdm. see the log for those). It should not be handled by ModemManager which is for ppp dialup even though the dongle supports that mode. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1334954 Title: Complete HUAWEI Mobile broadband E352 support Status in “usb-modeswitch” package in Ubuntu: New Bug description: usb_modeswitch kernel module tells me to report this bug :) The modem works fine, it's just not stable. Unplugging and reinserting creates a kernel oops that seems to prevent halting the system. First time I plugged it in, I got an U-DEV popup error message. A little after that, there was a question about PIN code and the modem worked. Unplugging and reinstering the device, it won't work. I have to reboot. I added four lines in usb_modeswitch.conf: DefaultVendor=12d1 DefaultProduct=14fe TargetVendor=12d1 TargetProduct=1506 At the last reboot, this made the U-DEV popup disappear and the modem asks for the PIN and works. The work_device.txt attachment shows the kernel log for this event. I will upload the log for when I unplug and reinsert the device as a separate file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1334954/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1256642] Re: Chromium shows aw snap error on every page
Started getting this also a few days ago. Nvidia and AMD64 Trusty chromium-browser --version Chromium 34.0.1847.116 Ubuntu 14.04 aura Side note - I had problems with chromium before the Aw, Snap's started. It would launch on my main monitor, but if I tried to move te window to another monitor (I have 6) the chromium window would go black. Moving it back to the main screen caused it to properly display content. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1256642 Title: Chromium shows aw snap error on every page Status in “chromium-browser” package in Ubuntu: Confirmed Bug description: I am using Chromium 30.0.1599.114 on Ubuntu 13.10 and I get a aw snap error message on every page I try to load, including the settings page. I tried reinstalling, deleting ~/.config/chrome and ~/.cache/chromium and I still have the same issue. The debug log shows a [6:6:1201/143302:WARNING:plugin_module.cc(673)] PPP_InitializeModule returned failure -2, but I don't know what that means. I would appreciate any help. Cheers, Oier To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1256642/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1332873] Re: Unity UI ignores mouse input when Firefox is running in another logged-in account
Update: I've been able to reproduce this without Firefox running, so it's not specific to that application. The most noteworthy thing I've noticed about the problem is that there are two instances of the X server running in gnome-system-monitor. I can provide more detailed info on this if needed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1332873 Title: Unity UI ignores mouse input when Firefox is running in another logged-in account Status in “xorg” package in Ubuntu: New Bug description: This could either be an X bug, a Firefox bug, a Unity bug, or something else; filing here to start. Steps to repro: 1. Log in as a normal user. 2. Open Firefox to a normal browsing session (multiple tabs, etc). 3. Select Switch Account from the top right settings menu and log in as another user on the system Observe: The Unity sidebar and top bar doesn't accept mouse clicks. Logging back into the first account, closing Firefox, and logging back in to the second account restores proper function. Expected result: Unity always responds to mouse input. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.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 CurrentDesktop: Unity Date: Sat Jun 21 12:49:54 2014 DistUpgraded: 2014-04-17 21:08:36,277 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: ASRock Incorporation Motherboard [1849:0162] NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:8422] InstallationDate: Installed on 2013-04-28 (418 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic root=UUID=7e9aaad1-2e08-4726-9451-b5a3d38ccc36 ro quiet splash nomdmonddf nomdmonisw SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to trusty on 2014-04-18 (64 days ago) dmi.bios.date: 07/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.90 dmi.board.name: Z77 Extreme4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.90:bd07/11/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ77Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sat Jun 21 11:47:35 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1332873/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1283003] Re: [Bluetooth + 14.04] Bluetooth headsets are not working after last couple of updates
When using the deb version (1.23-git201406261335-deb-1) and running blueman-applet in a terminal, what output do you get? There should be things like: Starting source redirector Found source Source not found :( module-loopback load result Loopback module unload result Destroying redirector And some IDs from the Module class. Basically every output from the PulseAudio.py file is relevant. -- 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/1283003 Title: [Bluetooth + 14.04] Bluetooth headsets are not working after last couple of updates Status in Blueman - Bluetooth Manager: Confirmed Status in “blueman” package in Ubuntu: Confirmed Status in “gnome-bluetooth” package in Ubuntu: Confirmed Status in “pulseaudio” package in Ubuntu: Invalid Bug description: Hi, I found a bug in Ubuntu 14.04 ! I tried to pair a bluetooth stereo headset (A2DP compatible). The pairing process goes well, but after that I can't select it on the audio preferences. When I select it, it only shows the last selected item options and don't do anything. (he should switch to the headset output). I must mention that it worked very well on Ubuntu 12.04. This bug can be in the bluetooth stack or in unity-control-center or maybe pulseaudio. I actually have no idea. To manage notifications about this bug go to: https://bugs.launchpad.net/blueman/+bug/1283003/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1240673] Re: Reports 0% charged for fully charged batteries
I have the same finding as Sergey, and I'm tried both the nvidia driver from nvidia-311, and nvidia-311-updates $ upower --dump Device: /org/freedesktop/UPower/devices/battery_BAT0 native-path: BAT0 vendor: Panasonic model:42T4801 serial: 1495 power supply: yes updated: fre 27 jun 2014 08:59:18 (5 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable:yes state: charging energy: 78,43 Wh energy-empty:0 Wh energy-full: 81,17 Wh energy-full-design: 84,24 Wh energy-rate: 11,605 W voltage: 12,268 V time to full:14,1 minutes percentage: 96% capacity:96,3557% technology: lithium-ion History (rate): 1403852358 11,605 charging 1403852328 12,460 charging 1403852298 12,456 charging 1403852268 12,672 charging Device: /org/freedesktop/UPower/devices/line_power_AC native-path: AC power supply: yes updated: fre 27 jun 2014 08:41:42 (1061 seconds ago) has history: no has statistics: no line-power online: yes Device: /org/freedesktop/UPower/devices/mouse_hid_00o02o76o34oafoe3_battery native-path: hid-00:02:76:34:af:e3-battery model:ThinkPad Bluetooth Laser Mouse power supply: no updated: fre 27 jun 2014 08:58:55 (28 seconds ago) has history: yes has statistics: yes mouse present: yes rechargeable:yes state: discharging percentage: 0% Daemon: daemon-version: 0.9.23 can-suspend: yes can-hibernate: no on-battery: no on-low-battery: no lid-is-closed: no lid-is-present: yes is-docked: no -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1240673 Title: Reports 0% charged for fully charged batteries Status in “upower” package in Ubuntu: Fix Released Status in “upower” source package in Saucy: Fix Released Status in “upower” source package in Trusty: Fix Released Bug description: SRU INFORMATION: Explanation: This bug was introduced with http://cgit.freedesktop.org/upower/commit/?id=07b95b8e which preferred the kernel's reported percentage (capacity sysfs attribute) over calculating it from energy/charge. This exposed some buggy batteries/drivers which sometimes report 100% charge. As the GObject percentage property is defined to be between 0 and 100, trying to set a value 100% resulted in a warning and defaulting to 0%. Fix: http://cgit.freedesktop.org/upower/commit/?id=22da1a0bc ; this clamping already happens at several other points in the code. Regression potential: Very low. The code change only applies to the explicit cases of 0% and 100%, and these values could have never actually appeared in practice as setting the property to these values fails. It has a test case, and the other test cases prove that this change did not break other configurations. In the worst case (compiler bugs etc.) this update could cause currently working battery information to be wrong, but upower is mostly an informational service these days and thus won't have the ability to completely break the system. ORIGINAL BUG: See the following upower dump: $ upower --dump Device: /org/freedesktop/UPower/devices/line_power_AC native-path: AC power supply: yes updated: Wed 16 Oct 2013 12:58:28 PM EDT (7198 seconds ago) has history: no has statistics: no line-power online: yes Device: /org/freedesktop/UPower/devices/battery_BAT0 native-path: BAT0 vendor: SMP model:DELL Y61CV22 serial: 3840 power supply: yes updated: Wed 16 Oct 2013 12:58:33 PM EDT (7193 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable:yes state: fully-charged energy: 66.6 Wh energy-empty:0 Wh energy-full: 66.6 Wh energy-full-design: 66.6 Wh energy-rate: 0.0111 W voltage: 12.836 V percentage: 0% capacity:76.9167% technology: lithium-ion Device: /org/freedesktop/UPower/devices/battery_BAT2 native-path: BAT2 vendor: Samsung SDI model:DELL W1GGM26 serial: 12515 power supply: yes updated: Wed 16 Oct 2013 12:58:33 PM EDT (7193
[Desktop-packages] [Bug 1248368] Re: Volume up/down keyboard keys stoped working after gnome-settings-daemon package update
Hi, I was suffering from the same problem. For everybody who ends up here looking for a quick fix, you can manually downgrade the package by downloading it from here (select your platform on the right side of the page below builds): https://launchpad.net/ubuntu/+source/gnome-settings-daemon/3.4.2-0ubuntu0.6.4 then open a terminal and install it using dpkg (replace the path with the file you downloaded, amd64bit for me): sudo dpkg -i ~/Downloads/gnome-settings-daemon_3.4.2-0ubuntu0.6.4_amd64.deb -- 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/1248368 Title: Volume up/down keyboard keys stoped working after gnome-settings- daemon package update Status in “gnome-settings-daemon” package in Ubuntu: Triaged Bug description: After updating gnome-settings-daemon from version 3.4.2-0ubuntu0.6.4 to version 3.4.2-0ubuntu0.6.5 the keyboard volume keys are not working. Pressing the keys does not produce the volume OSD, neither the volume is increased or decreased. The following packages were updated by synaptic: cjs (2.0.0-20131021020602-precise) to 2.0.0-20131105020703-precise duplicity (0.6.18-0ubuntu3.2) to 0.6.18-0ubuntu3.3 gimp (2.8.6-0precise1~ppa) to 2.8.8-0precise0~ppa gimp-data (2.8.6-0precise1~ppa) to 2.8.8-0precise0~ppa gnome-settings-daemon (3.4.2-0ubuntu0.6.4) to 3.4.2-0ubuntu0.6.5 libcjs0c (2.0.0-20131021020602-precise) to 2.0.0-20131105020703-precise libgimp2.0 (2.8.6-0precise1~ppa) to 2.8.8-0precise0~ppa xkb-data (2.5-1ubuntu1.4) to 2.5-1ubuntu1.5 xserver-common-lts-quantal (2:1.13.0-0ubuntu6.3~precise1) to 2:1.13.0-0ubuntu6.5~precise1 xserver-xorg-core-lts-quantal (2:1.13.0-0ubuntu6.3~precise1) to 2:1.13.0-0ubuntu6.5~precise1 I suspected that the bug might be in xkb-data and/or gnome-settings-daemon. Downgrading the xkb-data package the previous version (2.5-1ubuntu1.4) didn't work. Downgrading the gnome-settings-daemon package to the previous version (3.4.2-0ubuntu0.6.4) worked! Afterwords I upgraded xkb-data to the latest version (2.5-1ubuntu1.5) and left gnome-settings-daemon package to the previous version (3.4.2-0ubuntu0.6.4). And this works!!! In conclusion there is some regression introduced into gnome-settings- daemon 3.4.2-0ubuntu0.6.5. lsb_release -rd Description: Ubuntu 12.04.3 LTS Release: 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1248368/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1248368] Re: Volume up/down keyboard keys stoped working after gnome-settings-daemon package update
I forgot to mention that I'm running kernel 3.13.0-30, and my keyboard is a Logitech Illuminated keyboard -- 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/1248368 Title: Volume up/down keyboard keys stoped working after gnome-settings- daemon package update Status in “gnome-settings-daemon” package in Ubuntu: Triaged Bug description: After updating gnome-settings-daemon from version 3.4.2-0ubuntu0.6.4 to version 3.4.2-0ubuntu0.6.5 the keyboard volume keys are not working. Pressing the keys does not produce the volume OSD, neither the volume is increased or decreased. The following packages were updated by synaptic: cjs (2.0.0-20131021020602-precise) to 2.0.0-20131105020703-precise duplicity (0.6.18-0ubuntu3.2) to 0.6.18-0ubuntu3.3 gimp (2.8.6-0precise1~ppa) to 2.8.8-0precise0~ppa gimp-data (2.8.6-0precise1~ppa) to 2.8.8-0precise0~ppa gnome-settings-daemon (3.4.2-0ubuntu0.6.4) to 3.4.2-0ubuntu0.6.5 libcjs0c (2.0.0-20131021020602-precise) to 2.0.0-20131105020703-precise libgimp2.0 (2.8.6-0precise1~ppa) to 2.8.8-0precise0~ppa xkb-data (2.5-1ubuntu1.4) to 2.5-1ubuntu1.5 xserver-common-lts-quantal (2:1.13.0-0ubuntu6.3~precise1) to 2:1.13.0-0ubuntu6.5~precise1 xserver-xorg-core-lts-quantal (2:1.13.0-0ubuntu6.3~precise1) to 2:1.13.0-0ubuntu6.5~precise1 I suspected that the bug might be in xkb-data and/or gnome-settings-daemon. Downgrading the xkb-data package the previous version (2.5-1ubuntu1.4) didn't work. Downgrading the gnome-settings-daemon package to the previous version (3.4.2-0ubuntu0.6.4) worked! Afterwords I upgraded xkb-data to the latest version (2.5-1ubuntu1.5) and left gnome-settings-daemon package to the previous version (3.4.2-0ubuntu0.6.4). And this works!!! In conclusion there is some regression introduced into gnome-settings- daemon 3.4.2-0ubuntu0.6.5. lsb_release -rd Description: Ubuntu 12.04.3 LTS Release: 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1248368/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1334998] [NEW] When using Super+L keys autohide not working properly
Public bug reported: When using the super+l keys to lock the screen, the unity panel gets stuck. This happens whenever the user first clicks on the super key and then the L key. Clicking simutaniously works as expected. The issue was also reported on Ask Ubuntu: http://askubuntu.com/questions/459585/launcher-auto-hide-not-working- ubuntu-14-04/469732?noredirect=1#comment652314_469732 There is a workaround (the user has to double tap the super key) however, this is one of those papercuts that gets rather annoying over time. I would expect the system to be a little more tolerant in terms of the sequnce of keys pressed. If I first click on the super key and then the L key, the panel will not be locked when I log back in. === Description:Ubuntu 14.04 LTS Release:14.04 === unity: Installed: 7.2.1+14.04.20140513-0ubuntu2 Candidate: 7.2.1+14.04.20140513-0ubuntu2 Version table: *** 7.2.1+14.04.20140513-0ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 7.2.0+14.04.20140423-0ubuntu1.2 0 500 http://archive.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 7.2.0+14.04.20140416-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages === Screenshot: http://i.imgur.com/e3AePQ8.png ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.1+14.04.20140513-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Jun 27 09:23:52 2014 InstallationDate: Installed on 2014-03-16 (103 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140313) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 lockscreen trusty unity -- 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/1334998 Title: When using Super+L keys autohide not working properly Status in “unity” package in Ubuntu: New Bug description: When using the super+l keys to lock the screen, the unity panel gets stuck. This happens whenever the user first clicks on the super key and then the L key. Clicking simutaniously works as expected. The issue was also reported on Ask Ubuntu: http://askubuntu.com/questions/459585/launcher-auto-hide-not-working- ubuntu-14-04/469732?noredirect=1#comment652314_469732 There is a workaround (the user has to double tap the super key) however, this is one of those papercuts that gets rather annoying over time. I would expect the system to be a little more tolerant in terms of the sequnce of keys pressed. If I first click on the super key and then the L key, the panel will not be locked when I log back in. === Description: Ubuntu 14.04 LTS Release: 14.04 === unity: Installed: 7.2.1+14.04.20140513-0ubuntu2 Candidate: 7.2.1+14.04.20140513-0ubuntu2 Version table: *** 7.2.1+14.04.20140513-0ubuntu2 0 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 7.2.0+14.04.20140423-0ubuntu1.2 0 500 http://archive.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 7.2.0+14.04.20140416-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages === Screenshot: http://i.imgur.com/e3AePQ8.png ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.1+14.04.20140513-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Jun 27 09:23:52 2014 InstallationDate: Installed on 2014-03-16 (103 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140313) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1334998/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1283003] Re: [Bluetooth + 14.04] Bluetooth headsets are not working after last couple of updates
@Kiori audio.conf is attached. This is as installed as standard as far as I know. @cschramm As a simple user I'm starting to get out of my depth with the diagnostic procedures, please bear that in mind if I've misinterpreted your instructions. When I originally ran blueman-applet in terminal I got: Loading configuration plugins blueman-applet version 1.23 starting There is an instance already running So issuing killall blueman-applet and then reissuing blueman-applet I did not get any of the output you specified, simply a load of app load and initialisation messages. I've copied these into the attached file. I've also included the relevant part of var/log/syslog although there's not much to see. Apologies in advance if there is a delay over the next few days. I may be able to get back online on Sunday. Regards ** Attachment added: Contains audio.conf, terminal and syslog messages https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1283003/+attachment/4140439/+files/blueman-diagnostic-messages -- 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/1283003 Title: [Bluetooth + 14.04] Bluetooth headsets are not working after last couple of updates Status in Blueman - Bluetooth Manager: Confirmed Status in “blueman” package in Ubuntu: Confirmed Status in “gnome-bluetooth” package in Ubuntu: Confirmed Status in “pulseaudio” package in Ubuntu: Invalid Bug description: Hi, I found a bug in Ubuntu 14.04 ! I tried to pair a bluetooth stereo headset (A2DP compatible). The pairing process goes well, but after that I can't select it on the audio preferences. When I select it, it only shows the last selected item options and don't do anything. (he should switch to the headset output). I must mention that it worked very well on Ubuntu 12.04. This bug can be in the bluetooth stack or in unity-control-center or maybe pulseaudio. I actually have no idea. To manage notifications about this bug go to: https://bugs.launchpad.net/blueman/+bug/1283003/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1334558] [NEW] news bin is emptied at every session end
Hello Paul, sorry, I wish to refrain from releasing access to my computer. Is there another way I can retrieve and post a bug report to launchpad? thank you, regards. J. On 06/26/2014 06:26 PM, Paul Gevers wrote: Hi punjabi, We are missing all relevant information to be able to investigate this bug. Could you please run apport-collect 1334558 on the same system where you experience this issue? It will make sure that the minimal information that we need is attached to this bug report. Paul -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to liferea in Ubuntu. https://bugs.launchpad.net/bugs/1334558 Title: news bin is emptied at every session end Status in “liferea” package in Ubuntu: New Bug description: Hello liferea developers, I also sent an email about this problem to your mailing list. I'd recently reinstalled liferea, and since then the news bin doesnt keep feed items, it deletes them every time I end the liferea session. in previous installs this wasn't the case. could you please help me solve it? many thanks, regards, Jamro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/liferea/+bug/1334558/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1309145] Re: Chromium 34 ignores ComposeKey
Confirming: I switched to xim input method yesterday (for custom compose combinations), and today I noticed that indeed the compose key does not work in Chromium. http://code.google.com/p/chromium/issues/detail?id=351230 Browser: Version 34.0.1847.116 Ubuntu 14.04 aura (260972) [34.0.1847.116-0ubuntu2] OS: Trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1309145 Title: Chromium 34 ignores ComposeKey Status in Chromium Browser: Unknown Status in “chromium-browser” package in Ubuntu: Incomplete Bug description: When entering the key combination AltGr + [ a in any text input field or address bar, it does not translate to ä (a umlaut) anymore. This worked in the pre-aura Chromium 33. --- Ubuntu 14.04 UK International Keyboard $ echo $GTK_IM_MODULE xim Chromium 34.0.1847.116 (Developer Build 260972) Ubuntu 14.04 aura OSLinux Blink 537.36 (@170605) JavaScriptV8 3.24.35.22 Flash 13.0.0.182 User AgentMozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/34.0.1847.116 Chrome/34.0.1847.116 Safari/537.36 Command Line /usr/lib/chromium-browser/chromium-browser --ppapi-flash-path=/usr/lib/pepflashplugin-installer/libpepflashplayer.so --ppapi-flash-version=13.0.0.182 --enable-pinch --flag-switches-begin --enable-experimental-extension-apis --flag-switches-end (See also https://code.google.com/p/chromium/issues/detail?id=351230) To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1309145/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1283003] Re: [Bluetooth + 14.04] Bluetooth headsets are not working after last couple of updates
Thanks for the output! Did you connect the audio device? Then it looks like the applet plugin indeed does not do anything... But then again the version without the plugin (1.23-git201406231750-nopahandling) should not make any difference... :/ -- 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/1283003 Title: [Bluetooth + 14.04] Bluetooth headsets are not working after last couple of updates Status in Blueman - Bluetooth Manager: Confirmed Status in “blueman” package in Ubuntu: Confirmed Status in “gnome-bluetooth” package in Ubuntu: Confirmed Status in “pulseaudio” package in Ubuntu: Invalid Bug description: Hi, I found a bug in Ubuntu 14.04 ! I tried to pair a bluetooth stereo headset (A2DP compatible). The pairing process goes well, but after that I can't select it on the audio preferences. When I select it, it only shows the last selected item options and don't do anything. (he should switch to the headset output). I must mention that it worked very well on Ubuntu 12.04. This bug can be in the bluetooth stack or in unity-control-center or maybe pulseaudio. I actually have no idea. To manage notifications about this bug go to: https://bugs.launchpad.net/blueman/+bug/1283003/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1283003] Re: [Bluetooth + 14.04] Bluetooth headsets are not working after last couple of updates
@cschramm I've just received a new version of the ppa which seems to include additional debugging messages. I've attached the output from the new version Regards ** Attachment added: blueman-messages-2 https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1283003/+attachment/4140447/+files/blueman-messages-2 -- 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/1283003 Title: [Bluetooth + 14.04] Bluetooth headsets are not working after last couple of updates Status in Blueman - Bluetooth Manager: Confirmed Status in “blueman” package in Ubuntu: Confirmed Status in “gnome-bluetooth” package in Ubuntu: Confirmed Status in “pulseaudio” package in Ubuntu: Invalid Bug description: Hi, I found a bug in Ubuntu 14.04 ! I tried to pair a bluetooth stereo headset (A2DP compatible). The pairing process goes well, but after that I can't select it on the audio preferences. When I select it, it only shows the last selected item options and don't do anything. (he should switch to the headset output). I must mention that it worked very well on Ubuntu 12.04. This bug can be in the bluetooth stack or in unity-control-center or maybe pulseaudio. I actually have no idea. To manage notifications about this bug go to: https://bugs.launchpad.net/blueman/+bug/1283003/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1308451] Re: Epson Perfection 1670 (Snapscan) isn't working, some kind of crash after first initialisation
Also does not work for me anymore ever since the update to 14.04. Have to reboot to Windows to use the device. scanimage -L does list the device at first, it also is listed (always) doing an lsusb. Trying to use a scanning application (skanlite, xsane or vuescan) each app is not able to find the device and it does not show up any longer with scanimage -L but still under lsusb. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1308451 Title: Epson Perfection 1670 (Snapscan) isn't working, some kind of crash after first initialisation Status in “sane-backends” package in Ubuntu: Confirmed Bug description: I have an Epson Perfection 1670, which worked with the snapscan - Module very good with older ubuntu releases. In 14.04 there is a bug, which causes the following behaviour: 1. Connect scanner, sane-find-scanner recognize it and xsane find it, too. 2. Click on scan or even only on preview the scanner seems to initialize (moves shortly), after that nothing happens and after about 30 seconds a error message pops up, can't find scanner. (similar behavior with scanimage on terminal) 3. scanner could not found with xsane or sane-find-scanner. 4. Disconnect / Reconnect scanner from power - begin with 1 again. Installed packages: dpkg -l |grep sane ii libksane-data 4:4.13.0-0ubuntu1 all scanner library (data files) ii libksane0 4:4.13.0-0ubuntu1 amd64scanner library (runtime) ii libsane:amd64 1.0.23-3ubuntu3 amd64API library for scanners ii libsane-common 1.0.23-3ubuntu3 amd64API library for scanners -- documentation and support files ii libsane-hpaio 3.14.3-0ubuntu3 amd64HP SANE backend for multi-function peripherals ii libsane-perl0.05-2build1 amd64Perl bindings for the SANE (Scanner Access Now Easy) Project ii sane1.0.14-9 amd64scanner graphical frontends ii sane-utils 1.0.23-3ubuntu3 amd64API library for scanners -- utilities ii xsane 0.998-5ubuntu1 amd64featureful graphical frontend for SANE (Scanner Access Now Easy) ii xsane-common0.998-5ubuntu1 all featureful graphical frontend for SANE (Scanner Access Now Easy) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1308451/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1308451] Re: Epson Perfection 1670 (Snapscan) isn't working, some kind of crash after first initialisation
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: sane-backends (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1308451 Title: Epson Perfection 1670 (Snapscan) isn't working, some kind of crash after first initialisation Status in “sane-backends” package in Ubuntu: Confirmed Bug description: I have an Epson Perfection 1670, which worked with the snapscan - Module very good with older ubuntu releases. In 14.04 there is a bug, which causes the following behaviour: 1. Connect scanner, sane-find-scanner recognize it and xsane find it, too. 2. Click on scan or even only on preview the scanner seems to initialize (moves shortly), after that nothing happens and after about 30 seconds a error message pops up, can't find scanner. (similar behavior with scanimage on terminal) 3. scanner could not found with xsane or sane-find-scanner. 4. Disconnect / Reconnect scanner from power - begin with 1 again. Installed packages: dpkg -l |grep sane ii libksane-data 4:4.13.0-0ubuntu1 all scanner library (data files) ii libksane0 4:4.13.0-0ubuntu1 amd64scanner library (runtime) ii libsane:amd64 1.0.23-3ubuntu3 amd64API library for scanners ii libsane-common 1.0.23-3ubuntu3 amd64API library for scanners -- documentation and support files ii libsane-hpaio 3.14.3-0ubuntu3 amd64HP SANE backend for multi-function peripherals ii libsane-perl0.05-2build1 amd64Perl bindings for the SANE (Scanner Access Now Easy) Project ii sane1.0.14-9 amd64scanner graphical frontends ii sane-utils 1.0.23-3ubuntu3 amd64API library for scanners -- utilities ii xsane 0.998-5ubuntu1 amd64featureful graphical frontend for SANE (Scanner Access Now Easy) ii xsane-common0.998-5ubuntu1 all featureful graphical frontend for SANE (Scanner Access Now Easy) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1308451/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1308451] Re: Epson Perfection 1670 (Snapscan) isn't working, some kind of crash after first initialisation
I solved my problem by redownloading the firmware file which I had place in /etc/sane.d. The file that works for me : fc6ef4674ffe8d2afa403f79cc8dbc0e esfw30.bin Scanning works now. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1308451 Title: Epson Perfection 1670 (Snapscan) isn't working, some kind of crash after first initialisation Status in “sane-backends” package in Ubuntu: Confirmed Bug description: I have an Epson Perfection 1670, which worked with the snapscan - Module very good with older ubuntu releases. In 14.04 there is a bug, which causes the following behaviour: 1. Connect scanner, sane-find-scanner recognize it and xsane find it, too. 2. Click on scan or even only on preview the scanner seems to initialize (moves shortly), after that nothing happens and after about 30 seconds a error message pops up, can't find scanner. (similar behavior with scanimage on terminal) 3. scanner could not found with xsane or sane-find-scanner. 4. Disconnect / Reconnect scanner from power - begin with 1 again. Installed packages: dpkg -l |grep sane ii libksane-data 4:4.13.0-0ubuntu1 all scanner library (data files) ii libksane0 4:4.13.0-0ubuntu1 amd64scanner library (runtime) ii libsane:amd64 1.0.23-3ubuntu3 amd64API library for scanners ii libsane-common 1.0.23-3ubuntu3 amd64API library for scanners -- documentation and support files ii libsane-hpaio 3.14.3-0ubuntu3 amd64HP SANE backend for multi-function peripherals ii libsane-perl0.05-2build1 amd64Perl bindings for the SANE (Scanner Access Now Easy) Project ii sane1.0.14-9 amd64scanner graphical frontends ii sane-utils 1.0.23-3ubuntu3 amd64API library for scanners -- utilities ii xsane 0.998-5ubuntu1 amd64featureful graphical frontend for SANE (Scanner Access Now Easy) ii xsane-common0.998-5ubuntu1 all featureful graphical frontend for SANE (Scanner Access Now Easy) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1308451/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1334171] Re: [Dell OptiPlex 3011] AMD Radeon HD 8490 [1002:6771] Unable to run hybrid suspend.
** Summary changed: - [Dell OptiPlex 9020] AMD Radeon HD 8490 [1002:6771] Unable to run hybrid suspend. + [Dell OptiPlex 3011] AMD Radeon HD 8490 [1002:6771] Unable to run hybrid suspend. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1334171 Title: [Dell OptiPlex 3011] AMD Radeon HD 8490 [1002:6771] Unable to run hybrid suspend. Status in “xserver-xorg-video-ati” package in Ubuntu: New Bug description: CID: 201302-12681 Dell OptiPlex 9020 This system cannot enter the hybird-suspend mode with the open source driver (Probably caused by bug 1334167, it can't enter S4) Step: 1. Install 14.04, boot to desktop 2. Hibernate with sudo pm-suspend-hybrid Expected result: * System should work properly before / after S3-hybrid Actual result: * Display turned off and system seems to be freezed, unable to enter S3-hybrid. You have to hold the power button to turn it off. Note: this issue could be solved by using the proprietary fglrx driver. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-29-generic 3.13.0-29.53 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1659 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Wed Jun 25 05:05:17 2014 HibernationDevice: RESUME=UUID=04babaca-baed-40aa-b8bf-bb2c15683021 InstallationDate: Installed on 2014-06-23 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Dell Inc. OptiPlex 3011 AIO ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic.efi.signed root=UUID=15538075-2577-4d2e-8108-db9a3dfd6e8b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-29-generic N/A linux-backports-modules-3.13.0-29-generic N/A linux-firmware 1.127 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/10/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.vendor: Dell Inc. dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd09/10/2013:svnDellInc.:pnOptiPlex3011AIO:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct13:cvr: dmi.product.name: OptiPlex 3011 AIO dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1334171/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1295900] Re: lubuntu screen corruption only on cold boot.
[probably SOLVED] the bug seems to have disappeared completely. this might probably be due to newer kernel. Linux 3.13.0-30-generic #54-Ubuntu SMP Mon Jun 9 22:45:01 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1295900 Title: lubuntu screen corruption only on cold boot. Status in “xorg” package in Ubuntu: New Bug description: steps: 1) cold boot (power on) 2) choose boot (grub) 3) login (lightdm) When logging in, the login rectangle doesn't disappear like it should. 4) Xorg starts Desktop appears but the outline of the login-rectangle is still there. Also everything else that is drawn on the screen stays drawn (i.e. closed windows are still visable, a moved window leaves a trail) as if the system forgets to erase previously drawn objects. Strangely enough, the mousepointer doesn't seem to be affected. 5) sudo restart lightdm 6) login again Everything is suddenly working as it should ( high order magic ?? ) I have had this problem before with kernels newer than 3.13.0-8 but a kernel header install followed by a kernel image reinstall would always fix it. Since kernel 3.13.0-18 this fix doesn't work anymore. I assume the problem is not directly in X (??) maybe in kernel (??) since it first appears in lightdm (before X starts) Processor: dual core turion Chipset: AMD RS780 Videochip: RS780M [Mobility Radeon HD 3200] Driver (lsmod): radeon ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic i686 ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 CurrentDesktop: LXDE Date: Sat Mar 22 01:15:43 2014 InstallationDate: Installed on 2014-01-04 (76 days ago) InstallationMedia: Lubuntu 14.04 Trusty Tahr - Alpha i386 (20140102) SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1295900/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1334167] Re: [Dell OptiPlex 3011] AMD Radeon HD 8490 [1002:6771] Unable to hibernate with the open-source driver
** Summary changed: - [Dell OptiPlex 9020] AMD Radeon HD 8490 [1002:6771] Unable to hibernate with the open-source driver + [Dell OptiPlex 3011] AMD Radeon HD 8490 [1002:6771] Unable to hibernate with the open-source driver -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1334167 Title: [Dell OptiPlex 3011] AMD Radeon HD 8490 [1002:6771] Unable to hibernate with the open-source driver Status in “xserver-xorg-video-ati” package in Ubuntu: New Bug description: CID: 201302-12681 Dell OptiPlex 9020 This system cannot be hibernated with the open source driver Step: 1. Install 14.04, boot to desktop 2. Hibernate with sudo pm-hibernate Expected result: * System should work properly before / after S4 Actual result: * Display turned off and system seems to be freezed, unable to enter S4. You have to hold the power button to turn it off. Note: this issue could be solved by using the proprietary fglrx driver. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 [modified: boot/vmlinuz-3.13.0-24-generic] ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1443 F pulseaudio ubuntu 6484 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Wed Jun 25 03:24:58 2014 HibernationDevice: RESUME=UUID=04babaca-baed-40aa-b8bf-bb2c15683021 InstallationDate: Installed on 2014-06-23 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: Dell Inc. OptiPlex 3011 AIO ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=15538075-2577-4d2e-8108-db9a3dfd6e8b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/10/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.vendor: Dell Inc. dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd09/10/2013:svnDellInc.:pnOptiPlex3011AIO:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct13:cvr: dmi.product.name: OptiPlex 3011 AIO dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1334167/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1334722] Re: Add an accounts click hook
As far as I'm aware, the use case is for vendor/OEM provided scopes - so they can add their own account types. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to signon in Ubuntu. https://bugs.launchpad.net/bugs/1334722 Title: Add an accounts click hook Status in “signon” package in Ubuntu: New Bug description: Click packages need to be able to add new account types just as debian packages can. I would suggest a click manifest definition similar to below. manifest.json: { description: My Description, framework: ubuntu-sdk-14.10-dev2, architecture: all, hooks: { my-application: { accounts: my-accounts -- this refers to the name of a dir in your click package } }, icon: icon, maintainer: Ubuntu Developers ubuntu-devel-disc...@lists.ubuntu.com, name: com.package.name, title: A click package providing account types, version: 1.0.0 } And then in your click package provide the directory my-accounts, following the same structure as in /usr/share/accounts: my-accounts: ├── applications │ └── something.application ├── providers │ └── something.provider ├── qml-plugins │ ├── something │ └ Main.qml ├── services │ └── yahoo-mail.service └── service_types └── ubuntuone.service-type Your actual click hook file could be something like this: Pattern: ${home}/.local/share/accounts/${id} User-Level: yes Hook-Name: accounts You'd obviously need to monitor ~/.local/share/accounts/. In there the click machinery will create symlinks to the directories specified above. Any click packaging would satisfy the requirements really, but I think what I have specified above is pretty simple to both use and implement. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon/+bug/1334722/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1330037] Re: upower 0.99 transition
** Tags added: ubuntugnome-blocker -- 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/1330037 Title: upower 0.99 transition Status in “cairo-dock-plug-ins” package in Ubuntu: Fix Committed Status in “gnome-applets” package in Ubuntu: New Status in “gnome-control-center” package in Ubuntu: New Status in “gnome-packagekit” package in Ubuntu: Fix Released Status in “gnome-power-manager” package in Ubuntu: New Status in “gnome-session” package in Ubuntu: New Status in “gnome-settings-daemon” package in Ubuntu: New Status in “gnome-shell” package in Ubuntu: New Status in “indicator-power” package in Ubuntu: Triaged Status in “kde4libs” package in Ubuntu: New Status in “mate-applets” package in Ubuntu: New Status in “mate-power-manager” package in Ubuntu: New Status in “mate-session-manager” package in Ubuntu: New Status in “mutter” package in Ubuntu: New Status in “powerd” package in Ubuntu: New Status in “python-dbusmock” package in Ubuntu: New Status in “razorqt” package in Ubuntu: New Status in “sugar-0.96” package in Ubuntu: New Status in “sugar-0.98” package in Ubuntu: New Status in “telepathy-mission-control-5” package in Ubuntu: New Status in “tracker” package in Ubuntu: New Status in “ubuntu-system-settings” package in Ubuntu: New Status in “unity-control-center” package in Ubuntu: New Status in “unity-settings-daemon” package in Ubuntu: New Status in “upower” package in Ubuntu: New Status in “xfce4-power-manager” package in Ubuntu: New Status in “xfce4-session” package in Ubuntu: New Status in “xfce4-settings” package in Ubuntu: New Status in “xfce4-systemload-plugin” package in Ubuntu: Fix Committed Status in “wmbattery” package in Debian: New Bug description: upower 0.99 needs uploading for gnome 3.12. This bug tracks the transition. A transition is required as some features were removed and the SONAME was changed Some packages are staged in https://launchpad.net/~noskcaj/+archive/upower/+packages wmbattery will probably need removing. If a package only needs a rebuild, mark it fix commited, if something else is needed, in progress. cairo-dock-plug-ins: needs rebuilding gnome-applets - patch at bgo:730588 gnome-shell - ready, just need to drop upower revert. gnome-control-center: WIP gnome-packagekit: Upower dropped from newest upstream release. Merge from debian gnome-power-manager: Fixed in newest upstream release. Merge from debian experimental gnome-session: Done in ppa, needs patches from git or new upstream release gnome-settings-daemon: 3.12 is ready out of the box, however that also requires gnome-desktop transition. 3.8 and also u-s-d: I have a package that is mostly working, however had to cherry-pick quite a few patches and may just be better to backport 3.12 power plugin. (considering g-s-d patches will be temporary, but u-s-d not so) kde: needs sc 4.13.3 (http://quickgit.kde.org/?p=kdelibs.gita=commith=44afff90921b8b27d40e810684715d16278b335f) mate: all mate packages need rebuilding python-dbusmock: lp:1324791 sugar: no idea. telepathy-mission-control-5: Debian has dropped upower support, needs merging wmbattery: needs removal. orphaned upstream/debian and doesn't work with new kernals xfce4-power-manager: Fixed upstream. Merge at lp:1334185. Will need rebuilding xfce4-session: patch is upstream, needs work to apply with our current patchset xfce4-settings: Patch from upstream in ppa xfce4-systemload-plugin: needs rebuild To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo-dock-plug-ins/+bug/1330037/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1335056] [NEW] GTK+3 apps ignore bold and italic font settings
Public bug reported: I use Xubuntu 14.04. When I try to set the application font to bold or italic, GTK+3 apps (e.g. Synaptic, Transmission) don't respect that, their font doesn't get bold or italic. They respect only the change of the font name and size. The system is fully updated (with apt-get dist-upgrade). GTK+3 version is 3.10.8-0ubuntu1.1. ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Affects: gtk+3.0 (Debian) Importance: Unknown Status: Unknown ** Tags: fonts gtk ** Attachment added: Xubuntu 14.04 - bold https://bugs.launchpad.net/bugs/1335056/+attachment/4140553/+files/Xubuntu%2014.04%20-%20bold -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1335056 Title: GTK+3 apps ignore bold and italic font settings Status in “gtk+3.0” package in Ubuntu: New Status in “gtk+3.0” package in Debian: Unknown Bug description: I use Xubuntu 14.04. When I try to set the application font to bold or italic, GTK+3 apps (e.g. Synaptic, Transmission) don't respect that, their font doesn't get bold or italic. They respect only the change of the font name and size. The system is fully updated (with apt-get dist-upgrade). GTK+3 version is 3.10.8-0ubuntu1.1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1335056/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1335056] Re: GTK+3 apps ignore bold and italic font settings
Attached two screenshots that show how GTK+2 apps (Xfce terminal) and GTK+3 apps (Synaptic, Transmission) look with the font set to bold and italic, respectively. ** Bug watch added: Debian Bug tracker #752871 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752871 ** Also affects: gtk+3.0 (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752871 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1335056 Title: GTK+3 apps ignore bold and italic font settings Status in “gtk+3.0” package in Ubuntu: New Status in “gtk+3.0” package in Debian: Unknown Bug description: I use Xubuntu 14.04. When I try to set the application font to bold or italic, GTK+3 apps (e.g. Synaptic, Transmission) don't respect that, their font doesn't get bold or italic. They respect only the change of the font name and size. The system is fully updated (with apt-get dist-upgrade). GTK+3 version is 3.10.8-0ubuntu1.1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1335056/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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: ubuntugnome-blocker -- 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/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 Settings Daemon: In Progress Status in “gnome-desktop3” package in Ubuntu: Confirmed Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Triaged Status in “unity-control-center” package in Ubuntu: In Progress Status in “unity-settings-daemon” package in Ubuntu: New 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 1334072] Re: Kanji don't appear in omnibox
I'm suffering from the same issue. I hope this will be fixed soon. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1334072 Title: Kanji don't appear in omnibox Status in “chromium-browser” package in Ubuntu: Confirmed Bug description: After a certain upgrade, kanji don't appear in the tab title and omnibox. This is very inconvenient when you search Japanese word using the ominibox. The attached image (chromium-bug.png) shows the symptom. It show the case when I searched 犬の散歩 in Google. Although the string 犬の散歩 is processed properly, it shows の in the tab title and omnibox. 犬, 散, and 歩 are treated as blanks while の is shown correctly. Since this symptom come to occur after a certain upgrade, I paste a suspicious part of the log of apt as follows: --- Start-Date: 2014-06-23 18:02:51 Commandline: aptdaemon role='role-commit-packages' sender=':1.95' Upgrade: whoopsie:amd64 (0.2.24.5, 0.2.24.6), thunderbird-locale-en-us:amd64 (24.5.0+build1-0ubuntu0.14.04.1, 24.6.0+build1-0ubuntu0.14.04.1), libfontconfig1:amd64 (2.11.0-0ubuntu4, 2.11.0-0ubuntu4.1), libfontconfig1:i386 (2.11.0-0ubuntu4, 2.11.0-0ubuntu4.1), thunderbird:amd64 (24.5.0+build1-0ubuntu0.14.04.1, 24.6.0+build1-0ubuntu0.14.04.1), mount:amd64 (2.20.1-5.1ubuntu20, 2.20.1-5.1ubuntu20.1), libcgmanager0:amd64 (0.24-0ubuntu6, 0.24-0ubuntu7), libcgmanager0:i386 (0.24-0ubuntu6, 0.24-0ubuntu7), fontconfig:amd64 (2.11.0-0ubuntu4, 2.11.0-0ubuntu4.1), thunderbird-globalmenu:amd64 (24.5.0+build1-0ubuntu0.14.04.1, 24.6.0+build1-0ubuntu0.14.04.1), libuuid1:amd64 (2.20.1-5.1ubuntu20, 2.20.1-5.1ubuntu20.1), libuuid1:i386 (2.20.1-5.1ubuntu20, 2.20.1-5.1ubuntu20.1), libmount1:amd64 (2.20.1-5.1ubuntu20, 2.20.1-5.1ubuntu20.1), fontconfig-config:amd64 (2.11.0-0ubuntu4, 2.11.0-0ubuntu4.1), libunity-control-center1:amd64 (14.04.3+14.04.20140410-0ubuntu1, 14.04.3+14.04.20140604-0ubuntu1), thunderbird-locale-en:amd64 (24.5.0+build1-0ubuntu0.14.04.1, 24.6.0+build1-0ubuntu0.14.04.1), libwhoopsie0:amd64 (0.2.24.5, 0.2.24.6), bsdutils:amd64 (2.20.1-5.1ubuntu20, 2.20.1-5.1ubuntu20.1), thunderbird-locale-ja:amd64 (24.5.0+build1-0ubuntu0.14.04.1, 24.6.0+build1-0ubuntu0.14.04.1), uuid-runtime:amd64 (2.20.1-5.1ubuntu20, 2.20.1-5.1ubuntu20.1), thunderbird-gnome-support:amd64 (24.5.0+build1-0ubuntu0.14.04.1, 24.6.0+build1-0ubuntu0.14.04.1), libhud2:amd64 (13.10.1+14.04.20140402-0ubuntu1, 14.04+14.04.20140604-0ubuntu1), hud:amd64 (13.10.1+14.04.20140402-0ubuntu1, 14.04+14.04.20140604-0ubuntu1), unity-control-center:amd64 (14.04.3+14.04.20140410-0ubuntu1, 14.04.3+14.04.20140604-0ubuntu1), libblkid1:amd64 (2.20.1-5.1ubuntu20, 2.20.1-5.1ubuntu20.1), util-linux:amd64 (2.20.1-5.1ubuntu20, 2.20.1-5.1ubuntu20.1), libfontconfig1-dev:amd64 (2.11.0-0ubuntu4, 2.11.0-0ubuntu4.1), thunderbird-locale-en-gb:amd64 (24.5.0+build1-0ubuntu0.14.04.1, 24.6.0+build1-0ubuntu0.14.04.1) End-Date: 2014-06-23 18:03:11 Start-Date: 2014-06-24 11:25:02 Commandline: aptdaemon role='role-commit-packages' sender=':1.91' Upgrade: libreoffice-pdfimport:amd64 (4.2.3~rc3-0ubuntu2, 4.2.4-0ubuntu2), libreoffice-base-core:amd64 (4.2.3~rc3-0ubuntu2, 4.2.4-0ubuntu2), ure:amd64 (4.2.3~rc3-0ubuntu2, 4.2.4-0ubuntu2), libreoffice-writer:amd64 (4.2.3~rc3-0ubuntu2, 4.2.4-0ubuntu2), libssl1.0.0:amd64 (1.0.1f-1ubuntu2.3, 1.0.1f-1ubuntu2.4), libssl1.0.0:i386 (1.0.1f-1ubuntu2.3, 1.0.1f-1ubuntu2.4), libapache2-mod-php5:amd64 (5.5.9+dfsg-1ubuntu4, 5.5.9+dfsg-1ubuntu4.1), libreoffice-impress:amd64 (4.2.3~rc3-0ubuntu2, 4.2.4-0ubuntu2), uno-libs3:amd64 (4.2.3~rc3-0ubuntu2, 4.2.4-0ubuntu2), libreoffice-avmedia-backend-gstreamer:amd64 (4.2.3~rc3-0ubuntu2, 4.2.4-0ubuntu2), php5-common:amd64 (5.5.9+dfsg-1ubuntu4, 5.5.9+dfsg-1ubuntu4.1), libreoffice-draw:amd64 (4.2.3~rc3-0ubuntu2, 4.2.4-0ubuntu2), libreoffice-help-en-gb:amd64 (4.2.3~rc3-0ubuntu1, 4.2.4-0ubuntu2), fonts-opensymbol:amd64 (102.6+LibO4.2.3~rc3-0ubuntu2, 102.6+LibO4.2.4-0ubuntu2), libreoffice-core:amd64 (4.2.3~rc3-0ubuntu2, 4.2.4-0ubuntu2), libreoffice-help-ja:amd64 (4.2.3~rc3-0ubuntu1, 4.2.4-0ubuntu2), libreoffice-gnome:amd64 (4.2.3~rc3-0ubuntu2, 4.2.4-0ubuntu2), php5-readline:amd64 (5.5.9+dfsg-1ubuntu4, 5.5.9+dfsg-1ubuntu4.1), libreoffice-presentation-minimizer:amd64 (4.2.3~rc3-0ubuntu2, 4.2.4-0ubuntu2), libreoffice-style-human:amd64 (4.2.3~rc3-0ubuntu2, 4.2.4-0ubuntu2), libreoffice-l10n-en-gb:amd64 (4.2.3~rc3-0ubuntu1, 4.2.4-0ubuntu2), libreoffice-help-en-us:amd64 (4.2.3~rc3-0ubuntu1, 4.2.4-0ubuntu2), libreoffice-ogltrans:amd64 (4.2.3~rc3-0ubuntu2, 4.2.4-0ubuntu2), libssl-dev:amd64 (1.0.1f-1ubuntu2.3, 1.0.1f-1ubuntu2.4), python3-uno:amd64 (4.2.3~rc3-0ubuntu2, 4.2.4-0ubuntu2), libreoffice-common:amd64 (4.2.3~rc3-0ubuntu2, 4.2.4-0ubuntu2), php5-cli:amd64 (5.5.9+dfsg-1ubuntu4, 5.5.9+dfsg-1ubuntu4.1), libreoffice-gtk:amd64 (4.2.3~rc3-0ubuntu2, 4.2.4-0ubuntu2),
[Desktop-packages] [Bug 1334072] Re: Kanji don't appear in omnibox
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: chromium-browser (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1334072 Title: Kanji don't appear in omnibox Status in “chromium-browser” package in Ubuntu: Confirmed Bug description: After a certain upgrade, kanji don't appear in the tab title and omnibox. This is very inconvenient when you search Japanese word using the ominibox. The attached image (chromium-bug.png) shows the symptom. It show the case when I searched 犬の散歩 in Google. Although the string 犬の散歩 is processed properly, it shows の in the tab title and omnibox. 犬, 散, and 歩 are treated as blanks while の is shown correctly. Since this symptom come to occur after a certain upgrade, I paste a suspicious part of the log of apt as follows: --- Start-Date: 2014-06-23 18:02:51 Commandline: aptdaemon role='role-commit-packages' sender=':1.95' Upgrade: whoopsie:amd64 (0.2.24.5, 0.2.24.6), thunderbird-locale-en-us:amd64 (24.5.0+build1-0ubuntu0.14.04.1, 24.6.0+build1-0ubuntu0.14.04.1), libfontconfig1:amd64 (2.11.0-0ubuntu4, 2.11.0-0ubuntu4.1), libfontconfig1:i386 (2.11.0-0ubuntu4, 2.11.0-0ubuntu4.1), thunderbird:amd64 (24.5.0+build1-0ubuntu0.14.04.1, 24.6.0+build1-0ubuntu0.14.04.1), mount:amd64 (2.20.1-5.1ubuntu20, 2.20.1-5.1ubuntu20.1), libcgmanager0:amd64 (0.24-0ubuntu6, 0.24-0ubuntu7), libcgmanager0:i386 (0.24-0ubuntu6, 0.24-0ubuntu7), fontconfig:amd64 (2.11.0-0ubuntu4, 2.11.0-0ubuntu4.1), thunderbird-globalmenu:amd64 (24.5.0+build1-0ubuntu0.14.04.1, 24.6.0+build1-0ubuntu0.14.04.1), libuuid1:amd64 (2.20.1-5.1ubuntu20, 2.20.1-5.1ubuntu20.1), libuuid1:i386 (2.20.1-5.1ubuntu20, 2.20.1-5.1ubuntu20.1), libmount1:amd64 (2.20.1-5.1ubuntu20, 2.20.1-5.1ubuntu20.1), fontconfig-config:amd64 (2.11.0-0ubuntu4, 2.11.0-0ubuntu4.1), libunity-control-center1:amd64 (14.04.3+14.04.20140410-0ubuntu1, 14.04.3+14.04.20140604-0ubuntu1), thunderbird-locale-en:amd64 (24.5.0+build1-0ubuntu0.14.04.1, 24.6.0+build1-0ubuntu0.14.04.1), libwhoopsie0:amd64 (0.2.24.5, 0.2.24.6), bsdutils:amd64 (2.20.1-5.1ubuntu20, 2.20.1-5.1ubuntu20.1), thunderbird-locale-ja:amd64 (24.5.0+build1-0ubuntu0.14.04.1, 24.6.0+build1-0ubuntu0.14.04.1), uuid-runtime:amd64 (2.20.1-5.1ubuntu20, 2.20.1-5.1ubuntu20.1), thunderbird-gnome-support:amd64 (24.5.0+build1-0ubuntu0.14.04.1, 24.6.0+build1-0ubuntu0.14.04.1), libhud2:amd64 (13.10.1+14.04.20140402-0ubuntu1, 14.04+14.04.20140604-0ubuntu1), hud:amd64 (13.10.1+14.04.20140402-0ubuntu1, 14.04+14.04.20140604-0ubuntu1), unity-control-center:amd64 (14.04.3+14.04.20140410-0ubuntu1, 14.04.3+14.04.20140604-0ubuntu1), libblkid1:amd64 (2.20.1-5.1ubuntu20, 2.20.1-5.1ubuntu20.1), util-linux:amd64 (2.20.1-5.1ubuntu20, 2.20.1-5.1ubuntu20.1), libfontconfig1-dev:amd64 (2.11.0-0ubuntu4, 2.11.0-0ubuntu4.1), thunderbird-locale-en-gb:amd64 (24.5.0+build1-0ubuntu0.14.04.1, 24.6.0+build1-0ubuntu0.14.04.1) End-Date: 2014-06-23 18:03:11 Start-Date: 2014-06-24 11:25:02 Commandline: aptdaemon role='role-commit-packages' sender=':1.91' Upgrade: libreoffice-pdfimport:amd64 (4.2.3~rc3-0ubuntu2, 4.2.4-0ubuntu2), libreoffice-base-core:amd64 (4.2.3~rc3-0ubuntu2, 4.2.4-0ubuntu2), ure:amd64 (4.2.3~rc3-0ubuntu2, 4.2.4-0ubuntu2), libreoffice-writer:amd64 (4.2.3~rc3-0ubuntu2, 4.2.4-0ubuntu2), libssl1.0.0:amd64 (1.0.1f-1ubuntu2.3, 1.0.1f-1ubuntu2.4), libssl1.0.0:i386 (1.0.1f-1ubuntu2.3, 1.0.1f-1ubuntu2.4), libapache2-mod-php5:amd64 (5.5.9+dfsg-1ubuntu4, 5.5.9+dfsg-1ubuntu4.1), libreoffice-impress:amd64 (4.2.3~rc3-0ubuntu2, 4.2.4-0ubuntu2), uno-libs3:amd64 (4.2.3~rc3-0ubuntu2, 4.2.4-0ubuntu2), libreoffice-avmedia-backend-gstreamer:amd64 (4.2.3~rc3-0ubuntu2, 4.2.4-0ubuntu2), php5-common:amd64 (5.5.9+dfsg-1ubuntu4, 5.5.9+dfsg-1ubuntu4.1), libreoffice-draw:amd64 (4.2.3~rc3-0ubuntu2, 4.2.4-0ubuntu2), libreoffice-help-en-gb:amd64 (4.2.3~rc3-0ubuntu1, 4.2.4-0ubuntu2), fonts-opensymbol:amd64 (102.6+LibO4.2.3~rc3-0ubuntu2, 102.6+LibO4.2.4-0ubuntu2), libreoffice-core:amd64 (4.2.3~rc3-0ubuntu2, 4.2.4-0ubuntu2), libreoffice-help-ja:amd64 (4.2.3~rc3-0ubuntu1, 4.2.4-0ubuntu2), libreoffice-gnome:amd64 (4.2.3~rc3-0ubuntu2, 4.2.4-0ubuntu2), php5-readline:amd64 (5.5.9+dfsg-1ubuntu4, 5.5.9+dfsg-1ubuntu4.1), libreoffice-presentation-minimizer:amd64 (4.2.3~rc3-0ubuntu2, 4.2.4-0ubuntu2), libreoffice-style-human:amd64 (4.2.3~rc3-0ubuntu2, 4.2.4-0ubuntu2), libreoffice-l10n-en-gb:amd64 (4.2.3~rc3-0ubuntu1, 4.2.4-0ubuntu2), libreoffice-help-en-us:amd64 (4.2.3~rc3-0ubuntu1, 4.2.4-0ubuntu2), libreoffice-ogltrans:amd64 (4.2.3~rc3-0ubuntu2, 4.2.4-0ubuntu2), libssl-dev:amd64 (1.0.1f-1ubuntu2.3, 1.0.1f-1ubuntu2.4), python3-uno:amd64 (4.2.3~rc3-0ubuntu2, 4.2.4-0ubuntu2), libreoffice-common:amd64 (4.2.3~rc3-0ubuntu2, 4.2.4-0ubuntu2), php5-cli:amd64 (5.5.9+dfsg-1ubuntu4,
[Desktop-packages] [Bug 1335093] [NEW] chromium-browser closes/crashes on Save image as...
Public bug reported: Chromium closes/crashes when you right-click on a http:// image served on a https:// page and choose Save image as... $ chromium-browser [18405:18436:0627/135735:FATAL:url_request.cc(707)] Trying to send secure referrer for insecure load Aborted $ uname -a Linux RedFenix 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a Distributor ID: LinuxMint Description:Linux Mint 17 Qiana Release:17 Codename: qiana $ dpkg -s chromium-browser Package: chromium-browser Status: install ok installed Priority: optional Section: web Installed-Size: 153832 Maintainer: Ubuntu Developers ubuntu-devel-disc...@lists.ubuntu.com Architecture: amd64 Version: 34.0.1847.116-0ubuntu2 Replaces: chromium-browser-inspector Provides: chromium-browser-inspector, www-browser Depends: gconf-service, libasound2 (= 1.0.16), libatk1.0-0 (= 1.12.4), libc6 (= 2.15), libcairo2 (= 1.6.0), libcap2 (= 2.10), libcomerr2 (= 1.01), libcups2 (= 1.4.0), libdbus-1-3 (= 1.2.14), libexpat1 (= 2.0.1), libfontconfig1 (= 2.9.0), libfreetype6 (= 2.3.9), libgcc1 (= 1:4.1.1), libgconf-2-4 (= 2.31.1), libgcrypt11 (= 1.5.1), libgdk-pixbuf2.0-0 (= 2.22.0), libglib2.0-0 (= 2.37.3), libgnome-keyring0 (= 3.2.2-2~), libgnutls26 (= 2.12.17-0), libgssapi-krb5-2 (= 1.6.dfsg.2), libgtk2.0-0 (= 2.24.0), libk5crypto3 (= 1.6.dfsg.2), libkrb5-3 (= 1.6.dfsg.2), libnspr4 (= 2:4.9-2~) | libnspr4-0d (= 1.8.0.10), libnss3 (= 2:3.14.3), libpango-1.0-0 (= 1.22.0), libpangocairo-1.0-0 (= 1.14.0), libpangoft2-1.0-0 (= 1.14.0), libstdc++6 (= 4.6), libudev1 (= 183), libx11-6 (= 2:1.2.99.901), libxcomposite1 (= 1:0.3-1), libxcursor1 ( 1.1.2), libxdamage1 (= 1:1.1), libxext6, libxfixes3 (= 1:5.0), libxi6 (= 2:1.2.99.4), libxrandr2 (= 2:1.2.99.2), libxrender1, libxss1, libxtst6, zlib1g (= 1:1.1.4), xdg-utils, chromium-codecs-ffmpeg-extra (= 0.6) | chromium-codecs-ffmpeg (= 0.6) Pre-Depends: dpkg (= 1.15.6) Recommends: chromium-browser-l10n Suggests: webaccounts-chromium-extension, unity-chromium-extension, pepperflashplugin-nonfree Conflicts: chromium-browser-inspector Conffiles: /etc/default/chromium-browser 00f6b60b3a6a0b3ec9816ac3bae285eb /etc/chromium-browser/default 00f6b60b3a6a0b3ec9816ac3bae285eb Description: Chromium browser Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. . Chromium serves as a base for Google Chrome, which is Chromium rebranded (name and logo) with very few additions such as usage tracking and an auto-updater system. . This package contains the Chromium browser Homepage: http://code.google.com/chromium/ $ apt-cache showpkg chromium-browser Package: chromium-browser Versions: 34.0.1847.116-0ubuntu2 (/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_trusty_universe_binary-amd64_Packages) (/var/lib/dpkg/status) Description Language: File: /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_trusty_universe_binary-amd64_Packages MD5: f899058e5c597ae295f6ef23b467dade Description Language: en File: /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_trusty_universe_i18n_Translation-en MD5: f899058e5c597ae295f6ef23b467dade Reverse Depends: chromium-browser:i386,chromium-browser mythbuntu-desktop,chromium-browser webaccounts-chromium-extension,chromium-browser unity-chromium-extension,chromium-browser 20.0.1132.47~r144678-0ubuntu4 ubuntukylin-default-settings,chromium-browser mozplugger,chromium-browser lxde-core,chromium-browser lxde,chromium-browser djview-plugin,chromium-browser djview-plugin,chromium-browser chromium-chromedriver,chromium-browser 4.0.203.0~ chromium-browser-l10n,chromium-browser chromium-browser-l10n,chromium-browser 34.0.1847.116-0ubuntu2.1~ chromium-browser-l10n,chromium-browser 34.0.1847.116-0ubuntu2 chromium-browser-dbg,chromium-browser 34.0.1847.116-0ubuntu2 Dependencies: 34.0.1847.116-0ubuntu2 - gconf-service (0 (null)) libasound2 (2 1.0.16) libatk1.0-0 (2 1.12.4) libc6 (2 2.15) libcairo2 (2 1.6.0) libcap2 (2 2.10) libcomerr2 (2 1.01) libcups2 (2 1.4.0) libdbus-1-3 (2 1.2.14) libexpat1 (2 2.0.1) libfontconfig1 (2 2.9.0) libfreetype6 (2 2.3.9) libgcc1 (2 1:4.1.1) libgconf-2-4 (2 2.31.1) libgcrypt11 (2 1.5.1) libgdk-pixbuf2.0-0 (2 2.22.0) libglib2.0-0 (2 2.37.3) libgnome-keyring0 (2 3.2.2-2~) libgnutls26 (2 2.12.17-0) libgssapi-krb5-2 (2 1.6.dfsg.2) libgtk2.0-0 (2 2.24.0) libk5crypto3 (2 1.6.dfsg.2) libkrb5-3 (2 1.6.dfsg.2) libnspr4 (18 2:4.9-2~) libnspr4-0d (2 1.8.0.10) libnss3 (2 2:3.14.3) libpango-1.0-0 (2 1.22.0) libpangocairo-1.0-0 (2 1.14.0) libpangoft2-1.0-0 (2 1.14.0) libstdc++6 (2 4.6) libudev1 (2 183) libx11-6 (2 2:1.2.99.901) libxcomposite1 (2 1:0.3-1) libxcursor1 (4 1.1.2) libxdamage1 (2 1:1.1) libxext6 (0 (null)) libxfixes3 (2 1:5.0) libxi6 (2 2:1.2.99.4) libxrandr2 (2 2:1.2.99.2)
[Desktop-packages] [Bug 1041790]
*** Bug 80592 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1041790 Title: [snb] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001, workaround i915.semaphores=0 Status in X.org xf86-video-intel: In Progress 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 1335093] Re: chromium-browser closes/crashes on Save image as...
Similarly https://code.google.com/p/chromium/issues/detail?id=357473 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1335093 Title: chromium-browser closes/crashes on Save image as... Status in “chromium-browser” package in Ubuntu: New Bug description: Chromium closes/crashes when you right-click on a http:// image served on a https:// page and choose Save image as... $ chromium-browser [18405:18436:0627/135735:FATAL:url_request.cc(707)] Trying to send secure referrer for insecure load Aborted $ uname -a Linux RedFenix 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a Distributor ID: LinuxMint Description: Linux Mint 17 Qiana Release: 17 Codename: qiana $ dpkg -s chromium-browser Package: chromium-browser Status: install ok installed Priority: optional Section: web Installed-Size: 153832 Maintainer: Ubuntu Developers ubuntu-devel-disc...@lists.ubuntu.com Architecture: amd64 Version: 34.0.1847.116-0ubuntu2 Replaces: chromium-browser-inspector Provides: chromium-browser-inspector, www-browser Depends: gconf-service, libasound2 (= 1.0.16), libatk1.0-0 (= 1.12.4), libc6 (= 2.15), libcairo2 (= 1.6.0), libcap2 (= 2.10), libcomerr2 (= 1.01), libcups2 (= 1.4.0), libdbus-1-3 (= 1.2.14), libexpat1 (= 2.0.1), libfontconfig1 (= 2.9.0), libfreetype6 (= 2.3.9), libgcc1 (= 1:4.1.1), libgconf-2-4 (= 2.31.1), libgcrypt11 (= 1.5.1), libgdk-pixbuf2.0-0 (= 2.22.0), libglib2.0-0 (= 2.37.3), libgnome-keyring0 (= 3.2.2-2~), libgnutls26 (= 2.12.17-0), libgssapi-krb5-2 (= 1.6.dfsg.2), libgtk2.0-0 (= 2.24.0), libk5crypto3 (= 1.6.dfsg.2), libkrb5-3 (= 1.6.dfsg.2), libnspr4 (= 2:4.9-2~) | libnspr4-0d (= 1.8.0.10), libnss3 (= 2:3.14.3), libpango-1.0-0 (= 1.22.0), libpangocairo-1.0-0 (= 1.14.0), libpangoft2-1.0-0 (= 1.14.0), libstdc++6 (= 4.6), libudev1 (= 183), libx11-6 (= 2:1.2.99.901), libxcomposite1 (= 1:0.3-1), libxcursor1 ( 1.1.2), libxdamage1 (= 1:1.1), libxext6, libxfixes3 (= 1:5.0), libxi6 (= 2:1.2.99.4), libxrandr2 (= 2:1.2.99.2), libxrender1, libxss1, libxtst6, zlib1g (= 1:1.1.4), xdg-utils, chromium-codecs-ffmpeg-extra (= 0.6) | chromium-codecs-ffmpeg (= 0.6) Pre-Depends: dpkg (= 1.15.6) Recommends: chromium-browser-l10n Suggests: webaccounts-chromium-extension, unity-chromium-extension, pepperflashplugin-nonfree Conflicts: chromium-browser-inspector Conffiles: /etc/default/chromium-browser 00f6b60b3a6a0b3ec9816ac3bae285eb /etc/chromium-browser/default 00f6b60b3a6a0b3ec9816ac3bae285eb Description: Chromium browser Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. . Chromium serves as a base for Google Chrome, which is Chromium rebranded (name and logo) with very few additions such as usage tracking and an auto-updater system. . This package contains the Chromium browser Homepage: http://code.google.com/chromium/ $ apt-cache showpkg chromium-browser Package: chromium-browser Versions: 34.0.1847.116-0ubuntu2 (/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_trusty_universe_binary-amd64_Packages) (/var/lib/dpkg/status) Description Language: File: /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_trusty_universe_binary-amd64_Packages MD5: f899058e5c597ae295f6ef23b467dade Description Language: en File: /var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_trusty_universe_i18n_Translation-en MD5: f899058e5c597ae295f6ef23b467dade Reverse Depends: chromium-browser:i386,chromium-browser mythbuntu-desktop,chromium-browser webaccounts-chromium-extension,chromium-browser unity-chromium-extension,chromium-browser 20.0.1132.47~r144678-0ubuntu4 ubuntukylin-default-settings,chromium-browser mozplugger,chromium-browser lxde-core,chromium-browser lxde,chromium-browser djview-plugin,chromium-browser djview-plugin,chromium-browser chromium-chromedriver,chromium-browser 4.0.203.0~ chromium-browser-l10n,chromium-browser chromium-browser-l10n,chromium-browser 34.0.1847.116-0ubuntu2.1~ chromium-browser-l10n,chromium-browser 34.0.1847.116-0ubuntu2 chromium-browser-dbg,chromium-browser 34.0.1847.116-0ubuntu2 Dependencies: 34.0.1847.116-0ubuntu2 - gconf-service (0 (null)) libasound2 (2 1.0.16) libatk1.0-0 (2 1.12.4) libc6 (2 2.15) libcairo2 (2 1.6.0) libcap2 (2 2.10) libcomerr2 (2 1.01) libcups2 (2 1.4.0) libdbus-1-3 (2 1.2.14) libexpat1 (2 2.0.1) libfontconfig1 (2 2.9.0) libfreetype6 (2 2.3.9) libgcc1 (2 1:4.1.1) libgconf-2-4 (2 2.31.1) libgcrypt11 (2 1.5.1) libgdk-pixbuf2.0-0 (2 2.22.0) libglib2.0-0 (2 2.37.3) libgnome-keyring0 (2 3.2.2-2~) libgnutls26 (2 2.12.17-0)
[Desktop-packages] [Bug 1285752] Re: X freezes with EQ overflowing error in the log
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1285752 Title: X freezes with EQ overflowing error in the log Status in “xorg” package in Ubuntu: Confirmed Bug description: The symptom is always the same: the cursor starts to move choppily, soon it stops moving at all, keyboard input is mostly ignored although Ctrl+Alt+PrtSc+REISUB works and is the only option remaining. It doesn't seem to be connected to running any particular application. The only common attribute is that it always occur during higher RAM load = over 50% (on a 2GB RAM system). I've tested, re-tested and tested again RAM in Memtest for 6h periods and no error was ever reported so in my opinion the hardware issue of the RAM can be ruled out. NOTE: This is an incredibly frustrating problem as it affects system stability/usability. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-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: Thu Feb 27 16:46:52 2014 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:366b] InstallationDate: Installed on 2014-01-03 (55 days ago) InstallationMedia: It MachineType: LENOVO 10115 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic root=UUID=38a215c9-0e4f-4726-9b3b-3f749f762783 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: EZKT16AUS dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnLENOVO:bvrEZKT16AUS:bd01/18/2013:svnLENOVO:pn10115:pvrIdeaCenterQ190:rvnLENOVO:rnINVALID:rvrNoDPK:cvnLENOVO:ct3:cvrChassisVersion: dmi.product.name: 10115 dmi.product.version: IdeaCenter Q190 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.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: Thu Feb 27 16:27:06 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 22052 vendor IVM xserver.version: 2:1.14.5-1ubuntu2~saucy1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1285752/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 915059]
Please read this message in its entirety before responding. Your bug was confirmed at least 1 year ago and has not had any activity on it for over a year. Your bug is still set to NEW which means that it is open and confirmed. It would be nice to have the bug confirmed on a newer version than the version reported in the original report to know that the bug is still present -- sometimes a bug is inadvertently fixed over time and just never closed. If you have time please do the following: 1) Test to see if the bug is still present on a currently supported version of LibreOffice (preferably 4.2 or newer). 2) If it is present please leave a comment telling us what version of LibreOffice and your operating system. 3) If it is NOT present please set the bug to RESOLVED-WORKSFORME and leave a short comment telling us your version and Operating System Please DO NOT 1) Update the version field 2) Reply via email (please reply directly on the bug tracker) 3) Set the bug to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link: https://wiki.documentfoundation.org/QA/BugTriage There are also other ways to get involved including with marketing, UX, documentation, and of course developing - http://www.libreoffice.org /get-help/mailing-lists/. Lastly, good bug reports help tremendously in making the process go smoother, please always provide reproducible steps (even if it seems easy) and attach any and all relevant material -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/915059 Title: [Upstream] Compare Document highlighting unchanged words as changed Status in LibreOffice Productivity Suite: Confirmed Status in “libreoffice” package in Ubuntu: Triaged Bug description: 1) lsb_release -rd Description: Ubuntu 11.10 Release: 11.10 2) apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:3.4.4-0ubuntu1 Candidate: 1:3.4.4-0ubuntu1 Version table: *** 1:3.4.4-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ oneiric-updates/main i386 Packages 100 /var/lib/dpkg/status 1:3.4.3-3ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages 3) What is expected to happen in LibreOffice Writer via the Terminal: cd ~/Desktop wget https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/915059/+attachment/2671476/+files/versions.zip file-roller -h versions.zip cd versions lowriter -nologo version1.odt Edit - Compare Document - version2.odt - Insert button is under Actions regarding the first Deletion top to bottom, one tan hyphen is shown to the left of LibreOffice Writer and LibreOffice Writer is not marked tan with a tan underline. An example of how it should look may be found via the Terminal: cd ~/Desktop wget https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/915059/+attachment/2671477/+files /versions-space.zip file-roller -h versions-space.zip cd versions-space lowriter -nologo version1-space.odt Edit - Compare Document - version2-space.odt - Insert button 4) What happens instead is the hyphen to the left of LibreOffice Writer is not shown and LibreOffice Writer is marked tan with a tan underline. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/915059/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1333073] Re: PPA Fatal error when opening…loading libexpwraplo.so failed
in terminal type : sudo rm /usr/share/mime/packages/kde.xml (look at 'kde.xml', suits 'kde.xml' for your distro) sudo update-mime-database /usr/share/mime sudo apt-get remove libreoffice* sudo apt-get install libreoffice I solved. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1333073 Title: PPA Fatal error when opening…loading libexpwraplo.so failed Status in “libreoffice” package in Ubuntu: Confirmed Bug description: When I install the libreoffice package (1:4.3.0~rc1-0ubuntu1~trusty0) on Ubuntu 14.04 from ppa:libreoffice/libreoffice-prereleases, both 32-bit and 64-bit, the splash screen appears, soon followed by a Fatal Error dialog: The application cannot be started. service not supplied: loading component library file:///usr/lib/libreoffice/program/../program/libexpwraplo.so failed I have not tested if any upstream packaging produces the error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1333073/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1325273] Re: Samsung Note II does not mount as drives after upgrade to 14.04
I switched usb cables. Apparently something was wrong with my cable. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1325273 Title: Samsung Note II does not mount as drives after upgrade to 14.04 Status in “gvfs” package in Ubuntu: New Bug description: $ lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 When plugging my Samsung Note II into the USB port, I expect two Nautilus windows to pop up on the screen. This worked fine before my upgrade. There is no logging to /var/log/syslog when I plug in the device. lsusb does not list the device. $ lsusb Bus 001 Device 003: ID 046d:082c Logitech, Inc. Bus 001 Device 002: ID 03f0:c211 Hewlett-Packard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 003: ID 1130:1620 Tenx Technology, Inc. Bus 003 Device 002: ID 046d:c517 Logitech, Inc. LX710 Cordless Desktop Laser Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub I have also an HTC Vivid that would not mount after the upgrade. Recently however, it has started mounting properly. The Samsung Note however, does not mount at all. Thanks, John To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1325273/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1247572] Re: Nokia Lumia 620 (WP8) fails to mount reliably via gvfs-mtp in nautilus
** Changed in: gvfs Status: Incomplete = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1247572 Title: Nokia Lumia 620 (WP8) fails to mount reliably via gvfs-mtp in nautilus Status in GVFS: Fix Released Status in Nautilus: New Status in “gvfs” package in Ubuntu: Confirmed Status in “nautilus” package in Ubuntu: Invalid Bug description: Summary: You have to run mtp-detect in terminal until you get output similar to the excerpt in the steps to reproduce section, then you can connect via nautilus as usual. - I just got a Nokia Lumia 620 as a backup phone. I'd say I can mount my Nexus 4 reliably with Ubuntu via nautilus using gvfs-mtp. Users with Android devices like the Nexus 4 still get error messages on a regularly basis of the device not being able to mount, but replugging the device mostly fixes the issue. However, the experience with the Lumia 620 is far worse (the desktop sometimes freezes) and the workaround I found to get the device to work very crude. I was prompted with a apport-collector window when nautilus froze during testing and send a report (this happend twice), but it didn't take me to Launchpad to open a report. I can also seen no bug regarding that topic that I am subscribed to. The Lumia 620 itself was added to libmtp with this report: http://sourceforge.net/p/libmtp/bugs/780/ ## Steps to reproduce: 1. Reboot (or cold boot) computer and phone. Login to computers destop and unlock the phone by entering PIN. 2. Plug the phone via USB into the computer. (Cable works with Nexus 4 or another Android device.) The phone will give a signal that it is connected to the computer. 3. Try to open the phone in Nautilus. My desktop either freezes (cold boot) here or nautilus hangs (reboot). 3.a) If nautilus hangs: Open a terminal with Ctrl+Alt+T and kill nautilus with xkill. 3.b) If your desktop froze: Go to a virtual terminal with Ctrl+Alt+F1. 3.c) If you just get an error message: Open a terminal with Ctrl+Alt+T and go to step 4. 4. Execute 'mtp-detect' (from mtp-tools package) from terminal (either via Dektop or virtual terminal). If you get one of the following messages wait a few seconds and try again. $ mtp-detect Unable to open ~/.mtpz-data for reading, MTPZ disabled.libmtp version: 1.1.6 Listing raw device(s) Device 0 (VID=0421 and PID=0661) is a Nokia Nokia Lumia WP8. Found 1 device(s): Nokia: Nokia Lumia WP8 (0421:0661) @ bus 2, dev 22 Attempting to connect device(s) ignoring libusb_claim_interface() = -6PTP_ERROR_IO: failed to open session, trying again after resetting USB interface LIBMTP libusb: Attempt to reset device LIBMTP PANIC: failed to open session on second attempt Unable to open raw device 0 OK. --- $ mtp-detect Unable to open ~/.mtpz-data for reading, MTPZ disabled.libmtp version: 1.1.6 Listing raw device(s) Device 0 (VID=0421 and PID=0661) is a Nokia Nokia Lumia WP8. Found 1 device(s): Nokia: Nokia Lumia WP8 (0421:0661) @ bus 2, dev 22 Attempting to connect device(s) PTP_ERROR_IO: failed to open session, trying again after resetting USB interface LIBMTP libusb: Attempt to reset device LIBMTP PANIC: failed to open session on second attempt Unable to open raw device 0 OK. --- Repeat this until you get a long list of scrolling text that ends with something similar to this: MTP-specific device properties: Friendly name: Windows Phone Synchronization partner: (NULL) Battery level 74 of 100 (74%) libmtp supported (playable) filetypes: Folder Text file ISO MPEG-1 Audio Layer 3 Audio Video Interleave JPEG file Microsoft Windows Media Audio Advanced Audio Coding (AAC)/MPEG-2 Part 7/MPEG-4 Part 3 Microsoft Windows Media Video Abstract Album file Abstract Playlist file GIF bitmap file JFIF file Portable Network Graphics TIFF bitmap file BMP bitmap file MPEG-4 Part 14 Container Format (Audio+Video Emphasis) MPEG-4 Part 14 Container Format (Audio Emphasis) DOC file XLS file PPT file OK. --- 5. Go to a virtual terminal and do 'sudo service lightdm restart'. Login again, you hear the phone reconnecting to your computer and should now be able to open your phone in nautilus seeing the phones internal storage and the SD card (if there is) als sub devices. 6. Unplug the phone from the computer and start with step 2 if you want to connect the phone again. ## Additional information $ lsb_release -rd Description: Ubuntu 13.10 Release: 13.10 $ apt-cache policy gvfs gvfs-backends mtp-tools gvfs: Installed: 1.18.2-0ubuntu1 Candidate:
[Desktop-packages] [Bug 763148] Re: Adding/Removing an external monitor causes open windows to move to another workspace
** Changed in: compiz-core Milestone: None = 0.9.7.14 -- 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/763148 Title: Adding/Removing an external monitor causes open windows to move to another workspace Status in Compiz: Fix Released Status in Compiz 0.9.9 series: Fix Committed Status in Compiz Core: Fix Committed Status in “compiz” package in Ubuntu: Fix Released Bug description: [Impact] Many users will put different windows in different workspaces for better work flow. If a user connects and/or disconnects an external monitor or projector, all of these windows will be put in the first workspace. Having to go back and move all of the windows back to their workspaces is very frustrating and time consuming. [Test Case] #. Open some applications in different workspaces. #. Plug in an external monitor. [Regression Potential] Very low possibility that a window still ends up in the wrong workspace. Original description: well, i plug in my external screen. expected behaviour would be, if all of my windows would stay in the workspaces i aligned them to, and if they'd be on the same screen i had them in the first place. unfortunatly in unity, if i plug-in (or plug-off) my external screen the windows are all around, but not where i'd expect them to be (namely in the same place they were before). so i always have to toggle expo-mode and re-align all of my windows. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/763148/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1171878] Re: Adding/Removing an external monitor causes maximized windows to move to another workspace
** Also affects: compiz-core Importance: Undecided Status: New ** Changed in: compiz-core Milestone: None = 0.9.7.14 ** Changed in: compiz-core Status: New = Confirmed ** Changed in: compiz-core Importance: Undecided = Medium ** Changed in: compiz-core Assignee: (unassigned) = Christopher Townsend (townsend) ** Changed in: compiz-core Status: Confirmed = In Progress -- 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/1171878 Title: Adding/Removing an external monitor causes maximized windows to move to another workspace Status in Compiz: Fix Committed Status in Compiz Core: In Progress Status in “compiz” package in Ubuntu: Fix Released Status in “compiz” source package in Precise: Triaged Bug description: [Impact] If I plug in external monitor, move a window to it, maximize window and remove external monitor, window is moved to the same workspace primary screen - this is correct behavior, but when I un-maximize it - window moves to different workspace. This most likely is because original window positions are not updated after removing the monitor and un-maximize still uses those old values to move the window to supposedly original position. Another use case is when window movement is somewhat wrong - external monitor plugged in, window is maximized on primary screen, move focus to different workspace, unplug the monitor, move back to the workspace when we have fullscreen window, unmaximize it - window un-maximizes not to original position, it's moved away by the same mount of pixels as external monitor width is. I expect that window stays on the same workspace - once it's on it it should not move unless I do that manually, also I expect that un- maximizing moves window to original position, not different. This is continuation of bug https://bugs.launchpad.net/compiz/+bug/763148, fullscreen window bug was separated as per Christopher Townsend (townsend) wrote on 2013-04-18. P.S. Most likely bug can be fixed quite easy as behavior is similar to bug I mentioned, hopefully this can be included in the same SRU. thanks in advance Eduards [Test Case] ** Test Case 1 1. plug in external monitor and move a windows to it 2. maximize window 3. unplug external monitor 4. window moves to the primary display of the same workspace (this is correct) 5. un-maximize window 6. window un-maximizes to a different workspace (this is incorrect) ** Test Case 2 1. plug in external monitor 2. maximize window on primary (laptop display) 3. change to a different workspace 4. unplug external monitor 5. return to workspace with maximized window 6. un-maximize window 7. window un-maximizes to wrong position. instead of the original position it is shifted over by the same number of pixels as the width of the external monitor (also incorrect) [Other information] The bug fix also address bug LP: #763148 on precise. [Regression] None determined expected. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1171878/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1171658] Re: unity panel opacity is affected by Background Color opacity
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: compiz (Ubuntu) Status: New = Confirmed -- 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/1171658 Title: unity panel opacity is affected by Background Color opacity Status in Unity: New Status in “compiz” package in Ubuntu: Confirmed Bug description: In the past the Background Color opacity setting only affected the Dash as both the panel launcher have their own opacity settings. Now the Background color opacity does alter the panel's opacity actually is the only way to get a fully transparent panel. To see: Lower the panel opacity to 0., panel does not go transparent Now set a very low value for Background Color opacity (1-3 will do Panel will now go transparent. Raise the Background Color opacity from the above low value the panel will become darker (more opaque This also affects using no blur with a high Background Color opacity for readability having a panel that's not opaque ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu8 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 Apr 22 19:38:04 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation G86M [GeForce 8400M GS] [10de:0427] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0209] InstallationDate: Installed on 2013-04-21 (1 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130418) MachineType: Dell Inc. XPS M1330 MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=3e94c135-77e1-4935-b850-0ece6b279b02 ro quiet splash vt.handoff=7 SourcePackage: compiz UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/26/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd12/26/2008:svnDellInc.:pnXPSM1330:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: XPS M1330 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.43-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.1-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.1-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1171658/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1171658] Re: unity panel opacity is affected by Background Color opacity
this bug also appears in ubuntu trusty (14.04) -- 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/1171658 Title: unity panel opacity is affected by Background Color opacity Status in Unity: New Status in “compiz” package in Ubuntu: Confirmed Bug description: In the past the Background Color opacity setting only affected the Dash as both the panel launcher have their own opacity settings. Now the Background color opacity does alter the panel's opacity actually is the only way to get a fully transparent panel. To see: Lower the panel opacity to 0., panel does not go transparent Now set a very low value for Background Color opacity (1-3 will do Panel will now go transparent. Raise the Background Color opacity from the above low value the panel will become darker (more opaque This also affects using no blur with a high Background Color opacity for readability having a panel that's not opaque ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu8 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 Apr 22 19:38:04 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation G86M [GeForce 8400M GS] [10de:0427] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0209] InstallationDate: Installed on 2013-04-21 (1 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130418) MachineType: Dell Inc. XPS M1330 MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=3e94c135-77e1-4935-b850-0ece6b279b02 ro quiet splash vt.handoff=7 SourcePackage: compiz UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/26/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd12/26/2008:svnDellInc.:pnXPSM1330:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: XPS M1330 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.43-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.1-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.1-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1171658/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1310023] Re: 14.04: Nvidia Prime is unable to switch to the Nvidia card
Hi, I want to report this because I think the devs can take some conclusions. Tired with the problem I proceed with a new clean install in my laptop Lenovo Ideapad S410p Nvidia GT 720M (format / and /boot keep my /home the same) after the process I run the apt-get update and install new packages, after I put ON Cannonical partners repos and keep OFF trusty-propossed Now my Nvidia works perfect! I install nvidia from Ubuntu sources (not xorg-edgers) with this: mario@mario-IdeaPad-S410p:~$ sudo apt-get install nvidia-331 nvidia- settings nvidia-prime mario@mario-IdeaPad-S410p:~$ uname -a Linux mario-IdeaPad-S410p 3.13.0-30-generic #54-Ubuntu SMP Mon Jun 9 22:45:01 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Nvidia settings works fine show me full info Previous installation: I can see some problems in the normal works for Thunderbird and Firefox, lags for the hole graphic system, some screens run slowly and suddenly black screen for a windows minimized like you can see in the attachment (with Ctrl+tab I can restore normal work for it) . Now all looks very fine no lags normal behavior, TB and FF work very smooth, so for me the new clean install fixed all. Let me know if you need more info. ** Attachment added: Black screen https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1310023/+attachment/4140665/+files/Captura%20de%20pantalla%20de%202014-06-23%2017%3A00%3A09.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1310023 Title: 14.04: Nvidia Prime is unable to switch to the Nvidia card Status in “nvidia-prime” package in Ubuntu: Fix Released Status in “ubuntu-drivers-common” package in Ubuntu: Fix Released Status in “ubuntu-drivers-common” source package in Trusty: Fix Committed Bug description: SRU Request On some systems bbswitch requires the skip_optimus_dsm=1 option in order to load properly. So far we have dealt with this problem with system specific quirks based on DMI information. This some times gives us false positives or doesn't cover all systems (it's hard to quirk all systems). We should simply try with and without that option and use whatever works best for the system. This should cover all cases with no need for additional quirks. [Impact] * Loading bbswitch with the wrong option causes the module to fail from loading which, in turn, prevents hybrid graphics from working properly. [Test Case] * Install the nvidia binary driver, reboot, and check that the NVIDIA GPU is enabled (attach your /var/log/gpu-manager.log) - Expected: the NVIDIA GPU is enabled. - Bad behavior: the system switches back to the intel driver and the NVIDIA GPU is not used. [Regression Potential] * Low. Systems that currently work will keep working as usual, the ones that currently fail should finally work. [Other Info] * N/A -- I did a fresh install of 14.04 the day it was released. I use a XPS 15z laptop form Dell with hybrid graphics (Intel HD 3000 (probably) and Nvidia Geforce GT 525M). Booting doesn't work out of the box, but by setting GRUB_CMDLINE_LINUX_DEFAULT=acpi_backlight=vendor dell_laptop.backlight=0 quiet splash in /etc/default/grub it works. acpi=off when installing, removed that from the grub file when installed. I expected that the Prime feature introduced in kernel 3.12 (kernel 3.13.x here) would let me switch between the Intel and Nvidia cards as i like, instead of using Bumblebee, which doesn't work properly with everything. I've installed and tried both the nvidia-331 and nvidia-304 drivers. Exactly the same result from both. Attempting to switch to the Nvidia card in nvidia-settings (tried on almost all of the drivers available, including 331.38) resulted in an error message, in a new window, with no text. prime-switch in terminal gives this output: Segmentation fault (core dumped) Sudoing the process gives no output at all. No graphical performance boost either, still the Intel card... sudo prime-select nvidia gives this output: Error: alternatives are not set up properly Error: nvidia mode can't be enabled I've also tried Bumblebee (not PPA) a few times, but it's also unable to switch. I'm able to use the Intel card temporary, but I would really like to be able to use the full power of my computer... ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nvidia-prime 0.6.2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Sat Apr 19 20:52:42 2014 InstallationDate: Installed on 2014-04-17 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications
[Desktop-packages] [Bug 1335125] [NEW] Wrong number of ticks by application icon in launcher
Public bug reported: Since upgrade to 14.04 I've noticed that the number of ticks/markers that indicates the number of windows a the side of an application's icon is often incorrect. This seems to apply to Gnome Terminal, Firefox and Thunderbird and more. Reproduction #1: Open a terminal. Right click the launcher icon and choose New terminal. Observe there's only one ticks. Left click the launcher icon to expose both terminals. Observe the number of ticks is corrected. Choose either, it doesn't matter. Close one of the terminals. Observe there's still two ticks. The number of ticks doesn't seem to refresh until something happens in the launcher - either you click on something in the launcher, but the ticks seems to correct themselves at other times that I can't quite put my finger on. This is extremely distracting and interrupts work all the time checking to see what's left open to find that there's nothing there. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: compiz-core 1:0.9.11+14.04.20140423-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.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 CurrentDesktop: Unity Date: Fri Jun 27 14:26:07 2014 DistUpgraded: 2014-04-28 12:24:37,637 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu EcryptfsInUse: Yes ExecutablePath: /usr/bin/compiz GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:1033] InstallationDate: Installed on 2013-05-07 (415 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Micro-Star International Calpella platform ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic root=UUID=1aab217a-e362-4aab-9283-0b04525b2bdf ro quiet splash vt.handoff=7 SourcePackage: compiz UpgradeStatus: Upgraded to trusty on 2014-04-28 (60 days ago) dmi.bios.date: 07/21/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1681IG6 VER.109 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: Micro-Star International dmi.board.version: Ver.001 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 9 dmi.chassis.vendor: Micro-Star International dmi.chassis.version: Ver.001 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1681IG6VER.109:bd07/21/2010:svnMicro-StarInternational:pnCalpellaplatform:pvrVer.001:rvnMicro-StarInternational:rnTobefilledbyO.E.M.:rvrVer.001:cvnMicro-StarInternational:ct9:cvrVer.001: dmi.product.name: Calpella platform dmi.product.version: Ver.001 dmi.sys.vendor: Micro-Star International version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu Jun 26 09:47:01 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputVideo BusKEYBOARD, id 7 inputAT Translated Set 2 keyboard KEYBOARD, id 8 inputSynPS/2 Synaptics TouchPad TOUCHPAD, id 9 inputMSI WMI hotkeys KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16705 vendor SEC xserver.version: 2:1.15.1-0ubuntu2 ** Affects: compiz (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu -- 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/1335125 Title: Wrong number of ticks by application icon in launcher Status
[Desktop-packages] [Bug 1334515] Re: Gedit don't show preferences
** Package changed: unity-control-center (Ubuntu) = gedit (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1334515 Title: Gedit don't show preferences Status in Ubuntu GNOME: New Bug description: I use ubuntu gnome 14.04. after install gnome 3.12 by adding 2 ppas : ppa:gnome3-team/gnome3-staging and ppa:gnome3-team/gnome3. my gedit don' show preferences anymore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1334515/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1334515] Re: Gedit don't show preferences
THank you for your bug report, that's an issue with the GNOME3 ppa, not Ubuntu, reassigning to ubuntu-gnome ** Package changed: gedit (Ubuntu) = ubuntu-gnome -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1334515 Title: Gedit don't show preferences Status in Ubuntu GNOME: New Bug description: I use ubuntu gnome 14.04. after install gnome 3.12 by adding 2 ppas : ppa:gnome3-team/gnome3-staging and ppa:gnome3-team/gnome3. my gedit don' show preferences anymore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1334515/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1171658] Re: unity panel opacity is affected by Background Color opacity
** Tags removed: saucy ** Tags added: trusty utopic -- 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/1171658 Title: unity panel opacity is affected by Background Color opacity Status in Unity: New Status in “compiz” package in Ubuntu: Confirmed Bug description: In the past the Background Color opacity setting only affected the Dash as both the panel launcher have their own opacity settings. Now the Background color opacity does alter the panel's opacity actually is the only way to get a fully transparent panel. To see: Lower the panel opacity to 0., panel does not go transparent Now set a very low value for Background Color opacity (1-3 will do Panel will now go transparent. Raise the Background Color opacity from the above low value the panel will become darker (more opaque This also affects using no blur with a high Background Color opacity for readability having a panel that's not opaque ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu8 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 Apr 22 19:38:04 2013 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation G86M [GeForce 8400M GS] [10de:0427] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0209] InstallationDate: Installed on 2013-04-21 (1 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130418) MachineType: Dell Inc. XPS M1330 MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=3e94c135-77e1-4935-b850-0ece6b279b02 ro quiet splash vt.handoff=7 SourcePackage: compiz UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/26/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd12/26/2008:svnDellInc.:pnXPSM1330:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: XPS M1330 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.43-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.1-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.1-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1171658/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1335119] [NEW] telepathy-haze does not give KDE telepathy access to AIM, Windows Live (MSN), Yahoo!, Gadu-Gadu, Groupwise and ICQ.
Public bug reported: A freshly installed Kubuntu 14.04 contains telepathy-haze. In System Settings Instant Messaging and VoIP Accounts Add Account All there is a list of IM accounts, but these are missing: * AIM * Windows Live (MSN) * Yahoo! * Gadu-Gadu * Groupwise * ICQ ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: telepathy-haze 0.8.0-1 ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: KDE Date: Fri Jun 27 15:12:20 2014 InstallationDate: Installed on 2014-06-26 (1 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.1) SourcePackage: telepathy-haze UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: telepathy-haze (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 telepathy-haze in Ubuntu. https://bugs.launchpad.net/bugs/1335119 Title: telepathy-haze does not give KDE telepathy access to AIM, Windows Live (MSN), Yahoo!, Gadu-Gadu, Groupwise and ICQ. Status in “telepathy-haze” package in Ubuntu: New Bug description: A freshly installed Kubuntu 14.04 contains telepathy-haze. In System Settings Instant Messaging and VoIP Accounts Add Account All there is a list of IM accounts, but these are missing: * AIM * Windows Live (MSN) * Yahoo! * Gadu-Gadu * Groupwise * ICQ ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: telepathy-haze 0.8.0-1 ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: KDE Date: Fri Jun 27 15:12:20 2014 InstallationDate: Installed on 2014-06-26 (1 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.1) SourcePackage: telepathy-haze UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telepathy-haze/+bug/1335119/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 942634] Re: Alt-tab switcher view should be pre-loaded to improve the startup time
** Changed in: unity-distro-priority 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/942634 Title: Alt-tab switcher view should be pre-loaded to improve the startup time Status in Unity: Fix Released Status in Unity Distro Priority: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: The alt-tab view is slow to be loaded the first time, so it should be pre-loaded after few seconds that the unity desktop is setup to improve the first-time experience. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/942634/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1335138] [NEW] Paired, but bluetooth is not working
Public bug reported: I paired my desktop (Ubuntu 14.04 64 bits) and my Nexus 4 Android phone a long time ago, but I can't exchange files between them. When I send files from the desktop, I get transfer failed (0x4b) or a time out error message from openobex. If I try to send files from mobile phone to desktop, it reports a connection failure and nothing happens in the desktop. In bluetooth settings, after selecting my mobile phone device, it says Paired Yes, Type Phone, but the connection is always off. Both bluetooth and visibility are on. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- 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/1335138 Title: Paired, but bluetooth is not working Status in “pulseaudio” package in Ubuntu: New Bug description: I paired my desktop (Ubuntu 14.04 64 bits) and my Nexus 4 Android phone a long time ago, but I can't exchange files between them. When I send files from the desktop, I get transfer failed (0x4b) or a time out error message from openobex. If I try to send files from mobile phone to desktop, it reports a connection failure and nothing happens in the desktop. In bluetooth settings, after selecting my mobile phone device, it says Paired Yes, Type Phone, but the connection is always off. Both bluetooth and visibility are on. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1335138/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1311443] Re: switching input method is not reliable
** Also affects: gnome-settings-daemon (Baltix) Importance: Undecided Status: 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/1311443 Title: switching input method is not reliable Status in “gnome-settings-daemon” package in Ubuntu: Fix Released Status in “unity-settings-daemon” package in Ubuntu: Invalid Status in “gnome-settings-daemon” package in Baltix: New Bug description: [Impact] Under GNOME Shell, sometimes the input switcher popup (accessible via Super+Space by default) doesn't allow switching beyond the second input source. [Test Case] Under GNOME Shell, open gnome-control-center Region Language Input Sources + Add at least two input sources (I use us, ru, and gr). Then open gnome-control-center Keyboard Shortcuts Typing Switch to next source Set to Super+Space. Try pressing Super+Space to pop open the input switcher. Then press Super+Space again. The input switcher might not switch the second time. It happens unreliably, so if it works, restarting gnome- settings-daemon may allow reproducing the bug. [Regression Potential] The reason this is happening is because of an old patch that enables input switching for non-GNOME desktops (Unity, GNOME Flashback) by handling it in gnome-settings-daemon. But GNOME Shell handles it itself, so gnome-settings-daemon's shortcuts may be conflicting with GNOME Shell's sometimes. The fix is to remove it, which is ok because that code isn't used by those other non-GNOME desktops any more (they use unity-settings-daemon instead). For that reason, there should be low risk of regression. -- The behaviour of switching input method is strange. There are 2 ways to change input method. And both behave against expectation: 1. super-space: When hitting super-space, the system can only switch from English to Chinese. But not the other way round. 2. indicator: When switching language with the indicator, I can select both language. But the indicator is always showing en. OS: Ubuntu 14.04 Input Method: English (US), Chinese (Cangjie) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1311443/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1278223] Re: Mouse Flickering after adding 3rd Monitor
I get the exact same issue using my Lenovo LT1421 Displaylink screen. This has happened for ages and is not new to 14.x or a recent kernel, randr, xorg whatever. Tried it all. Once i get the monitor up and working with the correct modelines the mouse pointer on my main screen routinely flickers. If i run my charting software (high update frequency) or a video on the displaylink screen the mouse pointer on my laptop screen goes into maniac flicker mode. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1278223 Title: Mouse Flickering after adding 3rd Monitor Status in “xorg” package in Ubuntu: Confirmed Bug description: My issues is, after adding a 3rd monitor to Ubuntu 14.04, the mouse flickers (or blinks) when the cursor is on monitors one or two, but not 3. Monitor 1: 1440 x 900 - Laptop's Native Monitor Monitor 2: 1920 x 1080 - Laptop's HDMI Port's External Monitor Monitor 3: 1024 x 768 - SIIG USB 2.0 to VGA Pro Monitor Here's the video card that feeds my laptop's native monitor, monitor 2 (hdmi). lspci | grep 'VGA\|Display' 00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) 00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) The 3rd Monitor is powered through a Display Link certified SIIG USB 2.0 to VGA Pro adapter (A2H1320X1374 - not sure what this number, but it is a sticker on back of the device): lsusb -tv /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 6: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 6: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M dmesg [1.688343] usb 2-1: New USB device found, idVendor=17e9, idProduct=02ee [1.688348] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [1.688351] usb 2-1: Product: VGA Display Adapter [1.688353] usb 2-1: Manufacturer: DisplayLink [1.688356] usb 2-1: SerialNumber: 119785 Additionally, unity-control-center crashes sometimes after I Restore previous settings, after selecting a resolution too high. This freezed my laptop, requiring a hard reboot. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.1-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2 Uname: Linux 3.13.0-8-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Feb 9 18:43:13 2014 InstallationDate: Installed on 2014-02-02 (7 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140202) SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1278223/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1307163] Re: not work gnome-screensaver-command -d
Same bug here. I've installed and configured Blueproximity (I've used it for months with 10.04 but never with 12.04) but gnome-screensaver- command -d seems not work. Same issue with xscreensaver (xscreensaver- command -d). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1307163 Title: not work gnome-screensaver-command -d Status in “blueproximity” package in Ubuntu: Confirmed Status in “gnome-screensaver” package in Ubuntu: Confirmed Bug description: After the upgrade not work gnome-screensaver-command --deactivate jwm + gnome-screensaver impossible to see video because not working gnome-screensaver-command -d not works: gnome-screensaver-command -a gnome-screensaver-command -d gnome-screensaver-command -l ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-screensaver 3.6.1-0ubuntu13 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Apr 13 18:47:32 2014 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session session-name 'ubuntu' org.gnome.desktop.session idle-delay uint32 0 InstallationDate: Installed on 2014-04-11 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140410) SourcePackage: gnome-screensaver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/blueproximity/+bug/1307163/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 886478] Re: New Alt + tab switcher doesn't follow system font
** Also affects: unity/7.2 Importance: Undecided Status: New ** Changed in: unity/7.2 Milestone: None = 7.2.2 ** Changed in: unity Milestone: 7.2.2 = 7.3.1 -- 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/886478 Title: New Alt + tab switcher doesn't follow system font Status in Ayatana Design: Fix Committed Status in Unity: In Progress Status in Unity 7.2 series: New Status in “unity” package in Ubuntu: In Progress Bug description: In my laptop, I have to change from default ubuntu font to droid font because the default one doesn't fully support vietnamese. Let it sit there will make the overall system feel awkward. And now, while the whole system is in droid, only the switcher is still using the ubuntu font. Plz make the switcher follow the system font or at least, make a way to configure its appearance. -- Desired solution: - Alt+tab switcher should use the system font - This change should result in ZERO change to the appearance of the font in Alt+Tab on a fresh installation of Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/886478/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1332562] Re: DefaultTopGrubBootKernel3.15.0-6doesn't finish job, as the autoremoved3.15.0-5[i965gm] GPU lockup EIR: 0x00000010 PGTBL_ER: 0x00000101 IPEHR: 0xf000ff53
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: New = Confirmed -- 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/1332562 Title: DefaultTopGrubBootKernel3.15.0-6doesn't finish job, as the autoremoved3.15.0-5[i965gm] GPU lockup EIR: 0x0010 PGTBL_ER: 0x0101 IPEHR: 0xf000ff53 Status in “xserver-xorg-video-intel” package in Ubuntu: Confirmed Bug description: When booting, i need to choose an older kernel, as 3.13.0-29. If i let boot by the default one (3.15.0-6 which has substituded the autoremoved 3.15.0-5), the NB Acer Extensa 5620 stop after a screen with written ubuntu in a dark pink field, which comes after 2 screens with vertical brightly coloured strips. I had upgraded from 14.04 Trusty Thar to 14.10 Utopic Unicorn when bug went out. I 'm a not strong user of software, it's not long time i descover ubuntu/linux... Thank! Best regards. pino ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-29.52-generic 3.13.11.2 Uname: Linux 3.15.0-6-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.3-0ubuntu2 Architecture: amd64 Chipset: i965gm CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Jun 20 15:10:05 2014 DistUpgraded: 2014-06-03 21:34:00,157 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu DuplicateSignature: [i965gm] GPU lockup EIR: 0x0010 PGTBL_ER: 0x0101 IPEHR: 0xf000ff53 Ubuntu 14.10 ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:011f] Subsystem: Acer Incorporated [ALI] Device [1025:011f] InstallationDate: Installed on 2014-06-02 (17 days ago) InstallationMedia: Ubuntu 12.04.4 LTS Precise Pangolin - Release amd64 (20140204) InterpreterPath: /usr/bin/python3.4 MachineType: Acer Extensa 5620 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic root=UUID=6f5ce81b-5a89-4c62-b14d-695a51e7c561 ro quiet splash vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu8 libdrm2 2.4.54-1 xserver-xorg-video-intel 2:2.99.910-0ubuntu1 SourcePackage: xserver-xorg-video-intel Title: [i965gm] GPU lockup EIR: 0x0010 PGTBL_ER: 0x0101 IPEHR: 0xf000ff53 UpgradeStatus: Upgraded to utopic on 2014-06-03 (16 days ago) UserGroups: dmi.bios.date: 04/15/2008 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: V1.34 dmi.board.name: Columbia dmi.board.vendor: Acer dmi.board.version: Rev dmi.chassis.asset.tag: None dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.34:bd04/15/2008:svnAcer:pnExtensa5620:pvr0100:rvnAcer:rnColumbia:rvrRev:cvnAcer:ct10:cvrN/A: dmi.product.name: Extensa 5620 dmi.product.version: 0100 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.11+14.10.20140606-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.54-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu5 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-1ubuntu4 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: Fri Jun 20 15:12:03 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 32884 vendor AUO xserver.version: 2:1.15.1-0ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1332562/+subscriptions --
[Desktop-packages] [Bug 1298903] Re: Lockscreen: ibus input method selection doesn't work in lock screen
** Also affects: unity/7.2 Importance: Undecided Status: New ** Changed in: unity/7.2 Status: New = Triaged ** Changed in: unity/7.2 Importance: Undecided = Medium ** Changed in: unity/7.2 Milestone: None = 7.2.2 ** Changed in: unity Milestone: 7.2.2 = 7.3.1 -- 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/1298903 Title: Lockscreen: ibus input method selection doesn't work in lock screen Status in Unity: Triaged Status in Unity 7.2 series: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: Earlier, I switched my ibus daemon to the Japanese/anthy input mode and locked my screen. I couldn't key in my password (consisting solely of ascii characters), as it appeared to be inputting everything in Japanese (the typical underlines were there, but everything was starred as it was a password input field). There didn't appear to be a way to switch it back to a standard qwerty input mode, so I was kind of stuck. Workaround: I managed to get back in by activating the switch user menu item and logging back in from there. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140321-0ubuntu1 Uname: Linux 3.13.4-hyper1 x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,copytex,compiztoolbox,decor,vpswitch,extrawm,text,resize,ring,screenshot,place,commands,put,mousepoll,move,gnomecompat,annotate,blur,clone,widget,regex,imgpng,animation,obs,workarounds,neg,bicubic,resizeinfo,grid,expo,session,wall,showmouse,ezoom,unitymtgrabhandles,fade,scale,scalefilter,showdesktop,scaleaddon,unityshell] CurrentDesktop: Unity Date: Fri Mar 28 17:56:06 2014 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-03-03 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1298903/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1314871] Re: Ubuntu 14.04 random screen freeze while Normal OS activites
one of the two monitors is freezing randomly: Ubuntu 14.04 // current- nvidia (even tried latest driver from NVIDIA, but the same) can get it to work, when I press Ctrl-Alt-F1 for changing to console and Ctrl- Alt-F7 to gain graphical interface again. Then it working till the next freezing ... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1314871 Title: Ubuntu 14.04 random screen freeze while Normal OS activites Status in “xorg” package in Ubuntu: Confirmed Bug description: same symptom described in https://bugs.launchpad.net/ubuntu/+source /xorg-server/+bug/1184451 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia wl .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 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 CurrentDesktop: Unity Date: Thu May 1 09:21:51 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-24-generic, x86_64: installed bcmwl, 6.30.223.141+bdcom, 3.13.0-24-generic, x86_64: installed nvidia-331-updates, 331.38, 3.13.0-24-generic, x86_64: installed virtualbox, 4.3.10, 3.13.0-24-generic, x86_64: installed GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 18) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:044d] NVIDIA Corporation GT218M [GeForce 310M] [10de:0a75] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:044d] InstallationDate: Installed on 2014-04-27 (3 days ago) InstallationMedia: Ubuntu-Kylin 14.04 LTS Trusty Tahr - Release amd64 (20140417.1) MachineType: Dell Inc. Vostro 3400 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=96cf6b4d-5e19-4d7a-b765-b71e4b0b94da ro locale=zh_CN quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0RXV7H dmi.board.vendor: Dell Inc. dmi.board.version: A10 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A10 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd10/25/2010:svnDellInc.:pnVostro3400:pvrA10:rvnDellInc.:rn0RXV7H:rvrA10:cvnDellInc.:ct8:cvrA10: dmi.product.name: Vostro 3400 dmi.product.version: A10 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1314871/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1335138] Re: Paired, but bluetooth is not working
I was able to send files to Ubuntu after going to Personal File Sharing and enabling Receive Files over Bluetooth. Unfortunately, there is a gap between bluetooth errors and Personal File Sharing. I had no clues besides searching the Internet, and it was not a fast search. It would be better if the user is pointed to Personal FIle Sharing from bluetooth errors. -- 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/1335138 Title: Paired, but bluetooth is not working Status in “pulseaudio” package in Ubuntu: New Bug description: I paired my desktop (Ubuntu 14.04 64 bits) and my Nexus 4 Android phone a long time ago, but I can't exchange files between them. When I send files from the desktop, I get transfer failed (0x4b) or a time out error message from openobex. If I try to send files from mobile phone to desktop, it reports a connection failure and nothing happens in the desktop. In bluetooth settings, after selecting my mobile phone device, it says Paired Yes, Type Phone, but the connection is always off. Both bluetooth and visibility are on. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1335138/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1334617] Re: [X550LB, Realtek ALC233, Mic, Internal] not working Ubuntu 14.04
** Changed in: alsa-driver (Ubuntu) Status: New = Incomplete -- 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/1334617 Title: [X550LB, Realtek ALC233, Mic, Internal] not working Ubuntu 14.04 Status in “alsa-driver” package in Ubuntu: Incomplete Bug description: http://www.alsa- project.org/db/?f=70fd0de0d58f680c5a74ff1fbcf6dc46de5e5dc8 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alexander 2433 F pulseaudio /dev/snd/controlC1: alexander 2433 F pulseaudio alexander 3242 F alsamixer CurrentDesktop: Unity Date: Thu Jun 26 13:22:07 2014 InstallationDate: Installed on 2014-06-23 (3 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Встроенное аудио - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alexander 2433 F pulseaudio /dev/snd/controlC1: alexander 2433 F pulseaudio alexander 3242 F alsamixer Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [X550LB, Realtek ALC233, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550LB.402 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550LB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550LB.402:bd11/19/2013:svnASUSTeKCOMPUTERINC.:pnX550LB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550LB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550LB dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1334617/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1335000] [NEW] Launcher regression super + shift + number doesn't work properly
You have been subscribed to a public bug: Looks like it correspondig to this issue: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/754565 Steps to reproduce: Pin some application on launcher panel in position 1 (it must be accesible by super+1 Press super + shift + 1 - no any visible changes will be occuried Expected behaviour: New instance of application must be started, just simmilar with shift + mouse1 on application icon. Reproduced since 14.04, was tested in 12.04, 13.04, 13.10 ** Affects: unity (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: bot-comment trusty -- Launcher regression super + shift + number doesn't work properly https://bugs.launchpad.net/bugs/1335000 You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity 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 1335000] Re: Launcher regression super + shift + number doesn't work properly
** Tags added: trusty ** Package changed: ubuntu = unity (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/1335000 Title: Launcher regression super + shift + number doesn't work properly Status in “unity” package in Ubuntu: Confirmed Bug description: Looks like it correspondig to this issue: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/754565 Steps to reproduce: Pin some application on launcher panel in position 1 (it must be accesible by super+1 Press super + shift + 1 - no any visible changes will be occuried Expected behaviour: New instance of application must be started, just simmilar with shift + mouse1 on application icon. Reproduced since 14.04, was tested in 12.04, 13.04, 13.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1335000/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1251399] Re: [Inspiron 1010, Realtek ALC269, Speaker, Internal] Sound is distorted
https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/?id=051a8cb6550d917225ead1cd008b5966350f6d53 it use post_fix_lpib http://www.alsa-project.org/main/index.php/XRUN_Debug does hwptr increase by one period for any period size ? https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/sound/pci/hda/hda_intel.c?id=2ae66c26550cd94b0e2606a9275eb0ab7070ad0e https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/log/sound/pci/hda/hda_intel.c?qt=grepq=lpib -- 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/1251399 Title: [Inspiron 1010, Realtek ALC269, Speaker, Internal] Sound is distorted Status in “alsa-driver” package in Ubuntu: Incomplete Bug description: Went to ubuntu-bug last night, everything worked great after (audio). Today the sound became choppy and distorted again. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alsa-base 1.0.25+dfsg-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.8.0-33.48~precise1-generic 3.8.13.11 Uname: Linux 3.8.0-33-generic i686 NonfreeKernelModules: wl AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.8.0-33-generic. ApportVersion: 2.0.1-0ubuntu17.6 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: MID [HDA Intel MID], device 0: ALC269 Analog [ALC269 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: adam 1582 F pulseaudio Card0.Amixer.info: Card hw:0 'MID'/'HDA Intel MID at 0xd83a irq 22' Mixer name : 'Silicon Image SiI1392 HDMI' Components : 'HDA:10ec0269,102802c6,0014 HDA:10951392,,0010' Controls : 27 Simple ctrls : 10 Date: Thu Nov 14 13:48:33 2013 InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release i386 (20130820.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful Symptom_Card: Built-in Audio - HDA Intel MID Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Digital clip or distortion, or overdriven sound Title: [Inspiron 1010, Realtek ALC269, Speaker, Internal] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/27/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0R990K dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.asset.tag: ** dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A03 dmi.modalias: dmi:bvnDellInc.:bvrA03:bd02/27/2009:svnDellInc.:pnInspiron1010:pvrA03:rvnDellInc.:rn0R990K:rvrA03:cvnDellInc.:ct8:cvrA03: dmi.product.name: Inspiron 1010 dmi.product.version: A03 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1251399/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 806039] Re: Items added to Startup Applications disappear
*** This bug is a duplicate of bug 523796 *** https://bugs.launchpad.net/bugs/523796 I am not convinced this is a duplicate. I have a few notification programs that will work for a while and then suddenly disappear. This has been occurring for me since 13.04. I have created a script that copies over a backup of the autostart directory before shutdown, and it has not occurred since. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/806039 Title: Items added to Startup Applications disappear Status in “gnome-session” package in Ubuntu: Confirmed Bug description: A possible earlier instance of this bug was marked fixed over at https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/444993, but this must be another problem as I'm now getting this in 11.04 (Natty), and even when I wait 10 seconds before closing. Steps to reproduce: 1) System - Preferences - Startup Applications. 2) Click Add. 3) Name = Terminal; Command = /usr/bin/gnome-terminal; Comment = Start a terminal. 4) Click Add. 5) Click Close. 6) System - Preferences - Startup Applications.. 7) The newly added Terminal startup program is missing. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: gnome-session-bin 2.32.1-0ubuntu20 ProcVersionSignature: Ubuntu 2.6.38-10.44-generic 2.6.38.7 Uname: Linux 2.6.38-10-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Tue Jul 5 12:07:07 2011 ExecutablePath: /usr/bin/gnome-session-properties InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100427.1) ProcEnviron: LANGUAGE=en_CA:en LANG=en_CA.UTF-8 SHELL=/bin/zsh SourcePackage: gnome-session UpgradeStatus: Upgraded to natty on 2011-04-30 (65 days ago) XsessionErrors: (rhythmbox:18515): libsoup-WARNING **: No feature manager for feature of type 'U1RequestChrome' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/806039/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1292041] Re: Lockscreen doesn't turn off the screen
Behavior for me is still identical to what I posted in #10 above. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1292041 Title: Lockscreen doesn't turn off the screen Status in OEM Priority Project: Fix Released Status in OEM Priority Project trusty series: Fix Released Status in Unity: Fix Released Status in “gnome-screensaver” package in Ubuntu: Invalid Status in “unity” package in Ubuntu: Fix Released Bug description: The new Unity lock screen doesn't turn off the monitor screen. I can wait as long as 10 minutes after activating the lock screen and the monitor still doesn't trun off. Then when I unlock the screen and don't use mouse or keyboard monitor will turn off (it's about 5 seconds after unlocking). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1292041/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1292041] Vacation reply
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1292041 Title: Lockscreen doesn't turn off the screen Status in OEM Priority Project: Fix Released Status in OEM Priority Project trusty series: Fix Released Status in Unity: Fix Released Status in “gnome-screensaver” package in Ubuntu: Invalid Status in “unity” package in Ubuntu: Fix Released Bug description: The new Unity lock screen doesn't turn off the monitor screen. I can wait as long as 10 minutes after activating the lock screen and the monitor still doesn't trun off. Then when I unlock the screen and don't use mouse or keyboard monitor will turn off (it's about 5 seconds after unlocking). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1292041/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1334716] Re: FATAL ERROR: Unable to initialize display
Not sure is it related, found only this one, ** Attachment added: _usr_lib_x86_64-linux-gnu_ubuntu-geoip-provider.1000.crash.zip https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1334716/+attachment/4140834/+files/_usr_lib_x86_64-linux-gnu_ubuntu-geoip-provider.1000.crash.zip -- 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/1334716 Title: FATAL ERROR: Unable to initialize display Status in “compiz” package in Ubuntu: Incomplete Bug description: I went to the appearance settings by right-clicking on the desktop to change the visibility of the launcher, have set the sensitivity, exited after changes were made, after a few times of showing and hiding the launcher Compiz crashed and the display couldn't be restored not even after going into TTY and using compiz --replace. compiz-core has shown what appeared to be a fatal error that it was unable to initialize the display, so the only option was to do a hard shutdown. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: compiz-core 1:0.9.11+14.04.20140423-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.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 CurrentDesktop: Unity Date: Thu Jun 26 17:07:13 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:fd10] InstallationDate: Installed on 2014-06-12 (13 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) MachineType: TOSHIBA Satellite L650 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic root=UUID=5f0421c6-35ae-44ea-a80a-60c2dae71af1 ro quiet splash vt.handoff=7 SourcePackage: compiz UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/01/2010 dmi.bios.vendor: INSYDE dmi.bios.version: 1.80 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr1.80:bd09/01/2010:svnTOSHIBA:pnSatelliteL650:pvrPSK1EE-00Y007SK:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Satellite L650 dmi.product.version: PSK1EE-00Y007SK dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu Jun 26 15:22:32 2014 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 560 vendor LGD xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1334716/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1296415] Re: [security] please use apparmor to restrict access to ofono to approved services
** Description changed: NOTE: After further review from the security team, unfortunately what is presented as a solution in this bug is not sufficient to block unconfined processes from connecting to ofono for essentially two reasons: a) anything that is unconfined can change into another profile, so an unconfined process can simply change into the profile of one of the allowed services, and b) this doesn't protect against scenarios where the user is able to alter the behavior of the allowed services running in the user session (eg, indicator-network and ubuntu-system-settings) 'a' is solvable by making sure that the user's session starts under a new AppArmor user-session profile that prevents changing profile in to one of the allowed services (of course, the user session services continue to run under their own profiles). We'd have to investigate the - best method for profile attachment in this case as well. + best method for profile attachment in this case as well. An alternative + might be to store the profile attachment in the inode of the binary when + AppArmor adds this. 'b' is perhaps solvable by more strictly confining these allowed user session services (eg, 'audit deny ptrace tracedby peer=user-session, audit deny owner /** m, preventing QML loading, future AppArmor environment filtering, etc') along with, importantly, hardening these services to the point that they can't be controlled via environment, configuration, library loading, etc, etc. An alternative solution would be to run these services as another user in such a way that the user cannot alter their behavior beyond what is exposed in the UI. Preventing unconfined from doing things is a difficult prospect and while I think with the recent improvements with AppArmor over the last two cycles finally makes the notion plausible, significant work remains to solve 'a' and 'b'. This is cannot be achieved for RTM (note, this only affected limiting unconfined and has no effect on application isolation, which is in full effect and does not suffer from this at all). Description: It would be useful to limit the services that can connect to ofonod over DBus. We can implement this be creating an otherwise permissive AppArmor profile for ofonod that will limit any DBus calls to ofonod to a list of peer profiles (specifically excluding 'unconfined'). The list of peer profiles is: - indicator-network - network-manager (and dispatcher.d/03mmsproxy) - nuntium - telepathy-ofono - ofono-scripts - powerd - ubuntu-download-manager - system-settings - urfkill Each of the above needs to have a profile created for it, adjusting the boot scripts as necessary to ensure that the profile is loaded before the service starts. The peer profile implementation will be wide open as the purpose of the profile is (currently) to simply ensure the process of the service has the correct AppArmor labeling (though this opens the possibility to confine these services down the road if desired). Merge requests have been requested for everything except urfkill, which has a debdiff attached to this bug. As mentioned, the AppArmor profiles for everything except ofonod is wide open so the risk of regression is very low for these. In fact, if it is helpful, everything except ofono could be uploaded to the archive independently and at any time. For ofono, as mentioned, the AppArmor profile is also lenient except for the policy for its DBus interface. It is critical that ofono is updated at the same time or after all the other packages in this bug, otherwise any packages that aren't updated will fail to connect to ofono. I've been running this configuration on my phone for weeks with no denials (excepting 03mmsproxy which I adjusted for yesterday). I've tested the packaging on x86 emulator to make sure that the profiles are installed and loaded properly on boot. Test Plan (additional to any existing appropriate test plans) 1. Install all services on a device 2. reboot (important to restart the session and any services that aren't restarted automatically, like nuntium. reboot is easiest). Note the time of the reboot on the device 3. in addition to any applicable test plans, after full boot: adb shell grep DEN /var/log/syslog # there should be no denials for # ofono after the system boots (there # likely will be denials during # upgrade) adb shell tail -f /var/log/syslog | grep DEN # run this during all tests 4. make a call 5. send a text 6. send an mms (if possible) 7. connect to wifi 8. connect to 3G 9. download an app 10. toggle wifi in system-settings 11. verify ofono-scripts (eg, /usr/share/ofono/scripts/list-modems and
[Desktop-packages] [Bug 1335211] [NEW] Config details of networked printer aren't saved
You have been subscribed to a public bug: Mint 17 64 bit. When I run the printer configuration application (system-config-printer) it detects my network printer. If I then access Priner properties I can set the manufacturer and model number in the usual way and the printer works. However the settings don't survive a reboot. The workround is to make a change to the Description field: the Apply button is then enabled and I can save the changes. Evidently the application doesn't register the changes to the printer's properties as a change requiring saving, and so leaves the Apply button greyed out. This behaviour is consistent and repeatable under Mate and Xfce. While the workround is simple the behaviour is confusing particularly to a new user. ** Affects: system-config-printer (Ubuntu) Importance: Undecided Status: New -- Config details of networked printer aren't saved https://bugs.launchpad.net/bugs/1335211 You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer 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 1266656] Re: Unity Launcher sub menus contain code blauncher description/b to Orca
** Changed in: unity Milestone: 7.2.2 = None ** Changed in: unity Status: Triaged = 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/1266656 Title: Unity Launcher sub menus contain code blauncher description/b to Orca Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: When in the Unity Launcher, right clicking or for Orca users right arrowing presents a context menu. The item is described as Firefox, Files, Thunderbird etc but Orca reads out the descriptoin enclosed in code ' bFirefox/b. The expected result should be without the code, I do not know if this is also presented visually but Orca does read it. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20131106.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.12.0-8.16-generic 3.12.6 Uname: Linux 3.12.0-8-generic x86_64 ApportVersion: 2.12.7-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Jan 7 17:29:32 2014 InstallationDate: Installed on 2013-11-14 (53 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131113) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1266656/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1335211] Re: Config details of networked printer aren't saved
** Project changed: linuxmint = system-config-printer (Ubuntu) -- 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/1335211 Title: Config details of networked printer aren't saved Status in “system-config-printer” package in Ubuntu: New Bug description: Mint 17 64 bit. When I run the printer configuration application (system-config-printer) it detects my network printer. If I then access Priner properties I can set the manufacturer and model number in the usual way and the printer works. However the settings don't survive a reboot. The workround is to make a change to the Description field: the Apply button is then enabled and I can save the changes. Evidently the application doesn't register the changes to the printer's properties as a change requiring saving, and so leaves the Apply button greyed out. This behaviour is consistent and repeatable under Mate and Xfce. While the workround is simple the behaviour is confusing particularly to a new user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1335211/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1329677] Re: NVIDIA GF119M [GeForce 705M][10de:105b] unable to rotate display with proprietary driver
*** This bug is a duplicate of bug 1308515 *** https://bugs.launchpad.net/bugs/1308515 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-331 (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1329677 Title: NVIDIA GF119M [GeForce 705M][10de:105b] unable to rotate display with proprietary driver Status in “nvidia-graphics-drivers-331” package in Ubuntu: Confirmed Bug description: CID: 201301-12638 The display cannot be rotated on this system. There is only a Normal option in the Dispay applet The video controler in-use is: 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF119M [GeForce 705M] [10de:105b] (rev a1) With nvidia-331 (331.38-0ubuntu7) driver ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-29-generic 3.13.0-29.53 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1521 F pulseaudio CurrentDesktop: Unity Date: Fri Jun 13 04:21:29 2014 HibernationDevice: RESUME=UUID=276cb423-5fa1-4d04-a04f-a4263d200c53 InstallationDate: Installed on 2014-06-13 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard TEST ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic.efi.signed root=UUID=163fe54d-854d-403e-845b-f0b952070d74 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-29-generic N/A linux-backports-modules-3.13.0-29-generic N/A linux-firmware 1.127 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/14/2012 dmi.bios.vendor: AMI dmi.bios.version: 3.04 dmi.board.name: 2AFB dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.02 dmi.chassis.asset.tag: TBW1010026 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvr3.04:bd12/14/2012:svnHewlett-Packard:pnTEST:pvr1.00:rvnPEGATRONCORPORATION:rn2AFB:rvr1.02:cvnHewlett-Packard:ct3:cvr: dmi.product.name: TEST dmi.product.version: 1.00 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1329677/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1335246] [NEW] yelp crashed after closing it, while it was still loading, a few seconds after I accidentally started it.
Public bug reported: yelp crashed after closing it, while it was still loading, a few seconds after I accidentally started it. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: yelp 3.12.0-1ubuntu1 ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0 Uname: Linux 3.15.0-6-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.3-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jun 27 18:58:42 2014 ExecutablePath: /usr/bin/yelp InstallationDate: Installed on 2013-02-27 (485 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130226) ProcCmdline: yelp help:gnome-terminal SegvAnalysis: Skipped: missing required field Disassembly Signal: 11 SourcePackage: yelp UpgradeStatus: Upgraded to utopic on 2014-05-03 (55 days ago) UserGroups: adm cdrom debian-tor dip lpadmin plugdev sambashare sudo video ** Affects: yelp (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace utopic ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yelp in Ubuntu. https://bugs.launchpad.net/bugs/1335246 Title: yelp crashed after closing it, while it was still loading, a few seconds after I accidentally started it. Status in “yelp” package in Ubuntu: New Bug description: yelp crashed after closing it, while it was still loading, a few seconds after I accidentally started it. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: yelp 3.12.0-1ubuntu1 ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0 Uname: Linux 3.15.0-6-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.3-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jun 27 18:58:42 2014 ExecutablePath: /usr/bin/yelp InstallationDate: Installed on 2013-02-27 (485 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130226) ProcCmdline: yelp help:gnome-terminal SegvAnalysis: Skipped: missing required field Disassembly Signal: 11 SourcePackage: yelp UpgradeStatus: Upgraded to utopic on 2014-05-03 (55 days ago) UserGroups: adm cdrom debian-tor dip lpadmin plugdev sambashare sudo video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/1335246/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1296275] Re: PTP Cameras not working on 14.04, works flawlessly on 12.04
Mounting my android phone with mtp worked flawlessly in 12.04 but not in 14.04. It seems that was not fixed by this change. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1296275 Title: PTP Cameras not working on 14.04, works flawlessly on 12.04 Status in GVFS: Confirmed Status in libgphoto: New Status in Rapid Photo Downloader: Invalid Status in “gvfs” package in Ubuntu: Triaged Status in “libgphoto2” package in Ubuntu: Fix Released Status in “gvfs” source package in Trusty: Won't Fix Status in “libgphoto2” source package in Trusty: Fix Released Status in “gvfs” source package in Utopic: Triaged Status in “libgphoto2” source package in Utopic: Fix Released Bug description: I have a Canon Powershot A3200 camera. It works perfectly on 12.04, pops right up when I plug it in. However on 14.04 nothing happens. lsusb outputs shows that the camera is detected, with the right model. SRU INFORMATION: IMPACT: All PtP cameras which don't have an explicit vendor/model match in /lib/udev/hwdb.d/20-libgphoto2-6.hwdb stop working in gvfs/shotwell/etc. This is a regression since Saucy. FIX: Bring back the udev rule to tag generic PtP devices that we had had for many releases. This will tag the udev_device with the ID_GPHOTO2 property which is where gvfs and friends are looking (not on the usb_interface child). Patch: http://launchpadlibrarian.net/177343655/libgphoto2_2.5.4-1ubuntu1_2.5.4-1ubuntu2.diff.gz REGRESSION POTENTIAL: Very low. Adding tags to the wrong device might confuse gvfs/shotwell and friends, but this rule had been in production for many years. Broken udev rules are harmless except for error spew in syslog, and this doesn't interfere with the hwdb database as it only matches on usb_devices, not on usb_interfaces. To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1296275/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1335246]
StacktraceTop: yelp_uri_get_query (uri=0x0, key=0x7ff7eb32a450 terms) at yelp-uri.c:502 view_document_loaded (view=0x251c4e0, frame=optimized out, user_data=optimized out) at yelp-view.c:1489 ?? () ?? () ?? () -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yelp in Ubuntu. https://bugs.launchpad.net/bugs/1335246 Title: yelp crashed after closing it, while it was still loading, a few seconds after I accidentally started it. Status in “yelp” package in Ubuntu: Invalid Bug description: yelp crashed after closing it, while it was still loading, a few seconds after I accidentally started it. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: yelp 3.12.0-1ubuntu1 ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0 Uname: Linux 3.15.0-6-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.3-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jun 27 18:58:42 2014 ExecutablePath: /usr/bin/yelp InstallationDate: Installed on 2013-02-27 (485 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130226) ProcCmdline: yelp help:gnome-terminal SegvAnalysis: Skipped: missing required field Disassembly Signal: 11 SourcePackage: yelp UpgradeStatus: Upgraded to utopic on 2014-05-03 (55 days ago) UserGroups: adm cdrom debian-tor dip lpadmin plugdev sambashare sudo video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/1335246/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1335246] Stacktrace.txt
** Attachment added: Stacktrace.txt https://bugs.launchpad.net/bugs/1335246/+attachment/4140851/+files/Stacktrace.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yelp in Ubuntu. https://bugs.launchpad.net/bugs/1335246 Title: yelp crashed after closing it, while it was still loading, a few seconds after I accidentally started it. Status in “yelp” package in Ubuntu: Invalid Bug description: yelp crashed after closing it, while it was still loading, a few seconds after I accidentally started it. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: yelp 3.12.0-1ubuntu1 ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0 Uname: Linux 3.15.0-6-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.3-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jun 27 18:58:42 2014 ExecutablePath: /usr/bin/yelp InstallationDate: Installed on 2013-02-27 (485 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130226) ProcCmdline: yelp help:gnome-terminal SegvAnalysis: Skipped: missing required field Disassembly Signal: 11 SourcePackage: yelp UpgradeStatus: Upgraded to utopic on 2014-05-03 (55 days ago) UserGroups: adm cdrom debian-tor dip lpadmin plugdev sambashare sudo video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/1335246/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1292041] Re: Lockscreen doesn't turn off the screen
Doug what you describe in comment #10 is a different bug. This bug was for situation when you locked the screen with Super+L or Ctrl+Alt+L and while you had the lockscreen the monitor never blanked off. BTW I tested the situation described by you in comment #10 and didn't have any problems. I set the screen blanking to 1 minute and screen locking to 2 minutes and the screen didn't turn on even after 5 minutes. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1292041 Title: Lockscreen doesn't turn off the screen Status in OEM Priority Project: Fix Released Status in OEM Priority Project trusty series: Fix Released Status in Unity: Fix Released Status in “gnome-screensaver” package in Ubuntu: Invalid Status in “unity” package in Ubuntu: Fix Released Bug description: The new Unity lock screen doesn't turn off the monitor screen. I can wait as long as 10 minutes after activating the lock screen and the monitor still doesn't trun off. Then when I unlock the screen and don't use mouse or keyboard monitor will turn off (it's about 5 seconds after unlocking). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1292041/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1335246] Crash report cannot be processed
Thank you for your report! However, processing it in order to get sufficient information for the developers failed (it does not generate a useful symbolic stack trace). This might be caused by some outdated packages which were installed on your system at the time of the report: libgcc1 version 1:4.9.0-8ubuntu1 required, but 1:4.9.0-7ubuntu2 is available no debug symbol package found for libbz2-1.0 outdated debug symbol package for fglrx: package version 2:13.350.1-0ubuntu3 dbgsym version 2:13.350.1-0ubuntu2 libstdc++6 version 4.9.0-8ubuntu1 required, but 4.9.0-7ubuntu2 is available Please upgrade your system to the latest package versions. If you still encounter the crash, please file a new report. Thank you for your understanding, and sorry for the inconvenience! ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1335246/+attachment/4140842/+files/CoreDump.gz ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yelp in Ubuntu. https://bugs.launchpad.net/bugs/1335246 Title: yelp crashed after closing it, while it was still loading, a few seconds after I accidentally started it. Status in “yelp” package in Ubuntu: Invalid Bug description: yelp crashed after closing it, while it was still loading, a few seconds after I accidentally started it. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: yelp 3.12.0-1ubuntu1 ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0 Uname: Linux 3.15.0-6-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.3-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jun 27 18:58:42 2014 ExecutablePath: /usr/bin/yelp InstallationDate: Installed on 2013-02-27 (485 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130226) ProcCmdline: yelp help:gnome-terminal SegvAnalysis: Skipped: missing required field Disassembly Signal: 11 SourcePackage: yelp UpgradeStatus: Upgraded to utopic on 2014-05-03 (55 days ago) UserGroups: adm cdrom debian-tor dip lpadmin plugdev sambashare sudo video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/1335246/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1335246] StacktraceSource.txt
** Attachment added: StacktraceSource.txt https://bugs.launchpad.net/bugs/1335246/+attachment/4140852/+files/StacktraceSource.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yelp in Ubuntu. https://bugs.launchpad.net/bugs/1335246 Title: yelp crashed after closing it, while it was still loading, a few seconds after I accidentally started it. Status in “yelp” package in Ubuntu: Invalid Bug description: yelp crashed after closing it, while it was still loading, a few seconds after I accidentally started it. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: yelp 3.12.0-1ubuntu1 ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0 Uname: Linux 3.15.0-6-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.3-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jun 27 18:58:42 2014 ExecutablePath: /usr/bin/yelp InstallationDate: Installed on 2013-02-27 (485 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130226) ProcCmdline: yelp help:gnome-terminal SegvAnalysis: Skipped: missing required field Disassembly Signal: 11 SourcePackage: yelp UpgradeStatus: Upgraded to utopic on 2014-05-03 (55 days ago) UserGroups: adm cdrom debian-tor dip lpadmin plugdev sambashare sudo video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/1335246/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1335246] ThreadStacktrace.txt
** Attachment added: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1335246/+attachment/4140853/+files/ThreadStacktrace.txt ** Changed in: yelp (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yelp in Ubuntu. https://bugs.launchpad.net/bugs/1335246 Title: yelp crashed after closing it, while it was still loading, a few seconds after I accidentally started it. Status in “yelp” package in Ubuntu: Invalid Bug description: yelp crashed after closing it, while it was still loading, a few seconds after I accidentally started it. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: yelp 3.12.0-1ubuntu1 ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0 Uname: Linux 3.15.0-6-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.3-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jun 27 18:58:42 2014 ExecutablePath: /usr/bin/yelp InstallationDate: Installed on 2013-02-27 (485 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130226) ProcCmdline: yelp help:gnome-terminal SegvAnalysis: Skipped: missing required field Disassembly Signal: 11 SourcePackage: yelp UpgradeStatus: Upgraded to utopic on 2014-05-03 (55 days ago) UserGroups: adm cdrom debian-tor dip lpadmin plugdev sambashare sudo video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/1335246/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 784228] Re: evince fails to print PS file to PDF file
Still broken in 14.04 -- 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/784228 Title: evince fails to print PS file to PDF file Status in Evince document viewer: New Status in “evince” package in Ubuntu: Confirmed Status in “evince” package in Fedora: New Bug description: Binary package hint: evince Askubuntu user sdaau reports the following [1]: This is my problem: Open a document in Evince, choose Print Choose Printer: Print to file Choose Output Format: PDF (add a filename output.pdf in the box if not there) Click on Print Experience the following message: Failed to print document. Printing is not supported on this printer. By the way, printing to an Output Format .ps file works fine. I can reproduce this bug trying to print a PS file to PDF. Sample file is attached, created with LibreOffice 3.3 on Natty. evince 2.32.0-0ubuntu12.1 libreoffice-calc 1:3.3.2-1ubuntu4 Ubuntu 11.04 fresh install with all ~/.* user settings copied from 10.10 installation. [1] http://askubuntu.com/questions/37066/evince-print-to-pdf-file- fails-to-print To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/784228/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1335119] Re: telepathy-haze does not give KDE telepathy access to AIM, Windows Live (MSN), Yahoo!, Gadu-Gadu, Groupwise and ICQ.
Apparently, the reason is due to apparmor denying these protocols to be visible (on a side note, none of the others can connect for the same reason). If I boot with apparmor=0 in the kernel line, all protocols appear. These can be found in syslog: Jun 27 19:55:20 alia kernel: [ 1142.179652] type=1400 audit(1403891720.295:89): apparmor=ALLOWED operation=file_mmap profile=/usr/lib/telepathy/telepathy-* name=/lib /x86_64-linux-gnu/libdbus-1.so.3.7.6 pid=4148 comm=telepathy-gabbl requested_mask=m denied_mask=m fsuid=1001 ouid=1001 Jun 27 19:55:20 alia kernel: [ 1142.190849] type=1400 audit(1403891720.307:90): apparmor=ALLOWED operation=file_mmap profile=/usr/lib/telepathy/telepathy-* name=/lib /x86_64-linux-gnu/libpthread-2.19.so pid=4148 comm=telepathy-gabbl requested_mask=m denied_mask=m fsuid=1001 ouid=1001 Jun 27 19:55:20 alia kernel: [ 1142.190998] type=1400 audit(1403891720.307:91): apparmor=ALLOWED operation=file_mmap profile=/usr/lib/telepathy/telepathy-* name=/lib /x86_64-linux-gnu/libc-2.19.so pid=4148 comm=telepathy-gabbl requested_mask=m denied_mask=m fsuid=1001 ouid=1001 Jun 27 19:55:20 alia kernel: [ 1142.191154] type=1400 audit(1403891720.307:92): apparmor=ALLOWED operation=file_mmap profile=/usr/lib/telepathy/telepathy-* name=/lib /x86_64-linux-gnu/librt-2.19.so pid=4148 comm=telepathy-gabbl requested_mask=m denied_mask=m fsuid=1001 ouid=1001 Jun 27 19:55:20 alia kernel: [ 1142.193241] type=1400 audit(1403891720.311:93): apparmor=ALLOWED operation=file_mmap profile=/usr/lib/telepathy/telepathy-* name=/lib /x86_64-linux-gnu/libresolv-2.19.so pid=4148 comm=telepathy-gabbl requested_mask=m denied_mask=m fsuid=1001 ouid=1001 Jun 27 19:55:20 alia kernel: [ 1142.193346] type=1400 audit(1403891720.311:94): apparmor=ALLOWED operation=file_mmap profile=/usr/lib/telepathy/telepathy-* name=/lib /x86_64-linux-gnu/libdl-2.19.so pid=4148 comm=telepathy-gabbl requested_mask=m denied_mask=m fsuid=1001 ouid=1001 Jun 27 19:55:20 alia kernel: [ 1142.193493] type=1400 audit(1403891720.311:95): apparmor=ALLOWED operation=file_mmap profile=/usr/lib/telepathy/telepathy-* name=/lib /x86_64-linux-gnu/libm-2.19.so pid=4148 comm=telepathy-gabbl requested_mask=m denied_mask=m fsuid=1001 ouid=1001 Jun 27 19:55:20 alia kernel: [ 1142.202491] type=1400 audit(1403891720.319:96): apparmor=ALLOWED operation=file_mmap profile=/usr/lib/telepathy/telepathy-* name=/lib /x86_64-linux-gnu/libuuid.so.1.3.0 pid=4148 comm=telepathy-gabbl requested_mask=m denied_mask=m fsuid=1001 ouid=1001 Jun 27 19:55:20 alia kernel: [ 1142.247933] type=1400 audit(1403891720.363:97): apparmor=ALLOWED operation=file_mmap profile=/usr/lib/telepathy/telepathy-* name=/lib /x86_64-linux-gnu/libudev.so.1.3.5 pid=4148 comm=telepathy-gabbl requested_mask=m denied_mask=m fsuid=1001 ouid=1001 Jun 27 19:55:20 alia kernel: [ 1142.248042] type=1400 audit(1403891720.363:98): apparmor=ALLOWED operation=file_mmap profile=/usr/lib/telepathy/telepathy-* name=/lib /x86_64-linux-gnu/libcgmanager.so.0.0.0 pid=4148 comm=telepathy-gabbl requested_mask=m denied_mask=m fsuid=1001 ouid=1001 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to telepathy-haze in Ubuntu. https://bugs.launchpad.net/bugs/1335119 Title: telepathy-haze does not give KDE telepathy access to AIM, Windows Live (MSN), Yahoo!, Gadu-Gadu, Groupwise and ICQ. Status in “telepathy-haze” package in Ubuntu: New Bug description: A freshly installed Kubuntu 14.04 contains telepathy-haze. In System Settings Instant Messaging and VoIP Accounts Add Account All there is a list of IM accounts, but these are missing: * AIM * Windows Live (MSN) * Yahoo! * Gadu-Gadu * Groupwise * ICQ ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: telepathy-haze 0.8.0-1 ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: KDE Date: Fri Jun 27 15:12:20 2014 InstallationDate: Installed on 2014-06-26 (1 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.1) SourcePackage: telepathy-haze UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telepathy-haze/+bug/1335119/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1335119] Re: telepathy-haze does not give KDE telepathy access to AIM, Windows Live (MSN), Yahoo!, Gadu-Gadu, Groupwise and ICQ.
I'm messing up. The above logs are when apparmor is set to 'complain'. The normal situation is: [ 78.421203] type=1400 audit(1403892610.235:40): apparmor=DENIED operation=file_mmap profile=/usr/lib/telepathy/telepathy-* name=/lib/x86_64-linux-gnu/libdbus-1.so.3.7.6 pid=2545 comm =telepathy-gabbl requested_mask=m denied_mask=m fsuid=1001 ouid=1001 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to telepathy-haze in Ubuntu. https://bugs.launchpad.net/bugs/1335119 Title: telepathy-haze does not give KDE telepathy access to AIM, Windows Live (MSN), Yahoo!, Gadu-Gadu, Groupwise and ICQ. Status in “telepathy-haze” package in Ubuntu: New Bug description: A freshly installed Kubuntu 14.04 contains telepathy-haze. In System Settings Instant Messaging and VoIP Accounts Add Account All there is a list of IM accounts, but these are missing: * AIM * Windows Live (MSN) * Yahoo! * Gadu-Gadu * Groupwise * ICQ ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: telepathy-haze 0.8.0-1 ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: KDE Date: Fri Jun 27 15:12:20 2014 InstallationDate: Installed on 2014-06-26 (1 days ago) InstallationMedia: Kubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.1) SourcePackage: telepathy-haze UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telepathy-haze/+bug/1335119/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1201128] Re: missing icons for .directory files
Still affects Saucy. Still affects Trusty. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1201128 Title: missing icons for .directory files Status in “gnome-icon-theme” package in Ubuntu: Confirmed Status in “gnome-menus” package in Ubuntu: Confirmed Bug description: Directory files have been shipped with incorrect Icon= fields. For example, ActionGames.directory contains Icon=weather-storm. This should instead read Icons=applications-action (1) which is included in many icon sets (2), leaving this kind of substitution to the theme author using symlinks. Including references to these substitutions directly in the .directory files is an inappropriate and unecessary kludge which breaks themes, including the default one. I've only checked the Games .directory files so far, since that is what I was doing when I encountered the bug, but they all exhibit this problem. I'm using Ubuntu 13.04, but it's the kind of thing that could have been sitting undone for a while. It's probably worth checking whether this bug exists upstream or whether it's been introduced by the Ubuntu team. Upon further checking, Bug #421294 is a particular case of this bug, where the line reads Icon=system-run rather than Icon=applications- puzzles. From this report and Bug #421695 it seems likely that this bug was introduced in Karmic. (1) or similar - I'm not entirely sure on whether this will shake out as applications-action or applications-games-action; Gnome currently goes one way and KDE the other but, either way, symlinks are cheap and it can be sorted out through freedesktop. (2) Ubuntu's own Humanity icon set includes icons of this form, but they are not used because of this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-icon-theme/+bug/1201128/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1335290] [NEW] Inappropriate Default Resolution change commands are not available
Public bug reported: Macmini i7-3515@2.30GHz. OS X 10.9 with Parallels. Ubuntu 14.04 (64b) has this issue. Monitor is FPD1730. Display defaults to Built-in Display 800x600. Change commands are greyed out. Been unchanged since original installation. All updates are installed. Makes no difference. It's too coarse to work with. U 12.04(32bit) does not have this issue. Default resolution recognizes resolution set on host system and scales the window appropriately to display the whole U desktop. Help! Thanx ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14.1-0ubuntu3.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 CurrentDesktop: Unity Date: Fri Jun 27 11:19:53 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Parallels, Inc. Accelerated Virtual Video Adapter [1ab8:4005] (prog-if 00 [VGA controller]) Subsystem: Parallels, Inc. Device [1ab8:0400] InstallationDate: Installed on 2014-05-29 (29 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64+mac (20140417) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Parallels Software International Inc. Parallels Virtual Platform ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-30-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: Tue, 01 Apr 2014 16:28:49 dmi.bios.vendor: Parallels Software International Inc. dmi.bios.version: 9.0.24229.991745 dmi.board.name: Parallels Virtual Platform dmi.board.vendor: Parallels Software International Inc. dmi.board.version: None dmi.chassis.type: 16 dmi.chassis.vendor: Parallels Software International Inc. dmi.modalias: dmi:bvnParallelsSoftwareInternationalInc.:bvr9.0.24229.991745:bdTue,01Apr2014162849:svnParallelsSoftwareInternationalInc.:pnParallelsVirtualPlatform:pvrNone:rvnParallelsSoftwareInternationalInc.:rnParallelsVirtualPlatform:rvrNone:cvnParallelsSoftwareInternationalInc.:ct16:cvr: dmi.product.name: Parallels Virtual Platform dmi.product.version: None dmi.sys.vendor: Parallels Software International Inc. version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu Jun 26 15:00:23 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputSleep Button KEYBOARD, id 7 inputAT Translated Set 2 keyboard KEYBOARD, id 8 inputImExPS/2 Generic Explorer Mouse MOUSE, id 9 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.1-0ubuntu2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 resolution trusty ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1335290 Title: Inappropriate Default Resolution change commands are not available Status in “xorg” package in Ubuntu: New Bug description: Macmini i7-3515@2.30GHz. OS X 10.9 with Parallels. Ubuntu 14.04 (64b) has this issue. Monitor is FPD1730. Display defaults to Built-in Display 800x600. Change commands are greyed out. Been unchanged since original installation. All updates are installed. Makes no difference. It's too coarse to work with. U 12.04(32bit) does not have this issue. Default resolution recognizes resolution set on host system and scales the window appropriately to display the whole U desktop. Help! Thanx ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8
[Desktop-packages] [Bug 1335312] [NEW] When opening the trash from the launcher, the sidebar is reduced to its minimum width
Public bug reported: If you increase the width, then navigate away and back, or open Nautilus somewhere else and navigate to the trash, nothing happens. Screenshot attached. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: nautilus 1:3.4.2-0ubuntu9 Uname: Linux 3.2.0-65-generic x86_64 Architecture: amd64 Date: Fri Jun 27 21:58:19 2014 GsettingsChanges: org.gnome.nautilus.window-state geometry '607x972+160+200' org.gnome.nautilus.window-state maximized true org.gnome.nautilus.window-state sidebar-width 239 InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20120905-10:42 LiveMediaBuild: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20120905-10:42 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: nautilus ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages ** Attachment added: trash.png https://bugs.launchpad.net/bugs/1335312/+attachment/4140945/+files/trash.png -- 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/1335312 Title: When opening the trash from the launcher, the sidebar is reduced to its minimum width Status in “nautilus” package in Ubuntu: New Bug description: If you increase the width, then navigate away and back, or open Nautilus somewhere else and navigate to the trash, nothing happens. Screenshot attached. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: nautilus 1:3.4.2-0ubuntu9 Uname: Linux 3.2.0-65-generic x86_64 Architecture: amd64 Date: Fri Jun 27 21:58:19 2014 GsettingsChanges: org.gnome.nautilus.window-state geometry '607x972+160+200' org.gnome.nautilus.window-state maximized true org.gnome.nautilus.window-state sidebar-width 239 InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20120905-10:42 LiveMediaBuild: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20120905-10:42 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: nautilus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1335312/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1334495] Re: Two different fonts mixed to display Chinese text in all desktop applications
Thanks for the additional information. It indicates that qt based applications don't play well with fontconfig. However: On 2014-06-27 07:50, Lukas Bunsen wrote: In the font settings, everything is set to Ubuntu, except for the monospace font which is set to Monospace. Which font settings are those? Is it possibly something KDE specific that overrides fontconfig for KDE apps? If so, is there possibly a way to change them to 'neutral' values? In 14.04 the default font for rendering Chinese was changed from WenQuanYi Zen Hei to Droid Sans. This might have something to do with it. It's still not clear to me which packages are affected, but I added a few candidates so this bug report gets more attention. ** Package changed: language-selector (Ubuntu) = fontconfig (Ubuntu) ** Also affects: fonts-droid (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1334495 Title: Two different fonts mixed to display Chinese text in all desktop applications Status in “fontconfig” package in Ubuntu: Incomplete Status in “fonts-droid” package in Ubuntu: New Bug description: Bug: In all desktop applications, two different fonts are mixed to display Chinese text. I attached a screenshot of a paragraph of Chinese text in Kmail - some characters are displayed using a italic font, others in a normal font. The same problem exists in other applications, for example Dolphin or even Konsole. In Xterm, only the normal characters are displayed, where Dolphin displays italic characters Xterm leaves a white space. Websites are displayed fine, if I open the same mail in the web interface only one font is used. Background I' am using Kubuntu 14.04 with the language set to German in KDE settings. The output of locale looks a bit messed up, I don't know why, as in the KDE settings all formats are consistently set to German standard. locale LANG=de_DE.UTF-8 LANGUAGE=de:en:zh:en LC_CTYPE=de_DE.UTF-8 LC_NUMERIC=zh_CN.UTF-8 LC_TIME=zh_CN.UTF-8 LC_COLLATE=de_DE.UTF-8 LC_MONETARY=zh_CN.UTF-8 LC_MESSAGES=de_DE.UTF-8 LC_PAPER=zh_CN.UTF-8 LC_NAME=zh_CN.UTF-8 LC_ADDRESS=zh_CN.UTF-8 LC_TELEPHONE=zh_CN.UTF-8 LC_MEASUREMENT=zh_CN.UTF-8 LC_IDENTIFICATION=zh_CN.UTF-8 LC_ALL= fc-match: »DejaVuSans.ttf: DejaVu Sans Book« This is my first bug filed at launchpad. I filed it for language-selector as other related bugs I found were filed for the same package. If it isn't language-selector, perhaps you can point me to the right package? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1334495/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1335289] [NEW] Shutdown timer regression
You have been subscribed to a public bug: Description:Ubuntu 14.04 LTS Release:14.04 In older (12.*) versions of Ubuntu, pressing the physical power button on a computer would popup a dialog box asking the user what to do, along with a timer counting down from 60 seconds. After the time elapsed, the computer would shutdown. This feature is now missing in 14.*. As a user who absolutely loved this feature, I consider this a regression. ** Affects: gnome-power-manager (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment shutdown -- Shutdown timer regression https://bugs.launchpad.net/bugs/1335289 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager 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 1335289] Re: Shutdown timer regression
Based on the FindRightPackage page, I believe the package is gnome- power-manager, although I am not certain of this. ** Package changed: ubuntu = gnome-power-manager (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1335289 Title: Shutdown timer regression Status in “gnome-power-manager” package in Ubuntu: New Bug description: Description: Ubuntu 14.04 LTS Release: 14.04 In older (12.*) versions of Ubuntu, pressing the physical power button on a computer would popup a dialog box asking the user what to do, along with a timer counting down from 60 seconds. After the time elapsed, the computer would shutdown. This feature is now missing in 14.*. As a user who absolutely loved this feature, I consider this a regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1335289/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1334819] Re: unity (Ubuntu 14.10)
** Changed in: unity (Ubuntu) Status: Fix Committed = New ** Changed in: unity (Ubuntu) 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/1334819 Title: unity (Ubuntu 14.10) Status in “unity” package in Ubuntu: Invalid Bug description: stick with icons in desktop nothing else can be used also I tried too many things I can't collect all of tries ... otherwise I'll never end here! ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.0+14.10.20140619-0ubuntu1 ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0 Uname: Linux 3.15.0-6-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.3-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Thu Jun 26 22:22:55 2014 InstallationDate: Installed on 2014-06-07 (19 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1334819/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1330037] Re: upower 0.99 transition
** Description changed: upower 0.99 needs uploading for gnome 3.12. This bug tracks the transition. A transition is required as some features were removed and the SONAME was changed Some packages are staged in https://launchpad.net/~noskcaj/+archive/upower/+packages wmbattery will probably need removing. If a package only needs a rebuild, mark it fix commited, if something else is needed, in progress. cairo-dock-plug-ins: needs rebuilding gnome-applets - patch at bgo:730588 gnome-shell - ready, just need to drop upower revert. gnome-control-center: WIP gnome-packagekit: Upower dropped from newest upstream release. Merge from debian gnome-power-manager: Fixed in newest upstream release. Merge from debian experimental gnome-session: Done in ppa, needs patches from git or new upstream release gnome-settings-daemon: 3.12 is ready out of the box, however that also requires gnome-desktop transition. 3.8 and also u-s-d: I have a package that is mostly working, however had to cherry-pick quite a few patches and may just be better to backport 3.12 power plugin. (considering g-s-d patches will be temporary, but u-s-d not so) kde: needs sc 4.13.3 (http://quickgit.kde.org/?p=kdelibs.gita=commith=44afff90921b8b27d40e810684715d16278b335f) mate: all mate packages need rebuilding python-dbusmock: lp:1324791 - sugar: no idea. + sugar: Upstream bug now filed. Unlikely to be ready in time for 14.10. We should remove this from the archive till the next upstream release telepathy-mission-control-5: Debian has dropped upower support, needs merging wmbattery: needs removal. orphaned upstream/debian and doesn't work with new kernals xfce4-power-manager: Fixed upstream. Merge at lp:1334185. Will need rebuilding xfce4-session: patch is upstream, needs work to apply with our current patchset xfce4-settings: Patch from upstream in ppa xfce4-systemload-plugin: needs rebuild -- 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/1330037 Title: upower 0.99 transition Status in “cairo-dock-plug-ins” package in Ubuntu: Fix Committed Status in “gnome-applets” package in Ubuntu: New Status in “gnome-control-center” package in Ubuntu: New Status in “gnome-packagekit” package in Ubuntu: Fix Released Status in “gnome-power-manager” package in Ubuntu: New Status in “gnome-session” package in Ubuntu: New Status in “gnome-settings-daemon” package in Ubuntu: New Status in “gnome-shell” package in Ubuntu: New Status in “indicator-power” package in Ubuntu: Triaged Status in “kde4libs” package in Ubuntu: New Status in “mate-applets” package in Ubuntu: New Status in “mate-power-manager” package in Ubuntu: New Status in “mate-session-manager” package in Ubuntu: New Status in “mutter” package in Ubuntu: New Status in “powerd” package in Ubuntu: New Status in “python-dbusmock” package in Ubuntu: New Status in “razorqt” package in Ubuntu: New Status in “sugar-0.96” package in Ubuntu: New Status in “sugar-0.98” package in Ubuntu: New Status in “telepathy-mission-control-5” package in Ubuntu: New Status in “tracker” package in Ubuntu: New Status in “ubuntu-system-settings” package in Ubuntu: New Status in “unity-control-center” package in Ubuntu: New Status in “unity-settings-daemon” package in Ubuntu: New Status in “upower” package in Ubuntu: New Status in “xfce4-power-manager” package in Ubuntu: New Status in “xfce4-session” package in Ubuntu: New Status in “xfce4-settings” package in Ubuntu: New Status in “xfce4-systemload-plugin” package in Ubuntu: Fix Committed Status in “wmbattery” package in Debian: New Bug description: upower 0.99 needs uploading for gnome 3.12. This bug tracks the transition. A transition is required as some features were removed and the SONAME was changed Some packages are staged in https://launchpad.net/~noskcaj/+archive/upower/+packages wmbattery will probably need removing. If a package only needs a rebuild, mark it fix commited, if something else is needed, in progress. cairo-dock-plug-ins: needs rebuilding gnome-applets - patch at bgo:730588 gnome-shell - ready, just need to drop upower revert. gnome-control-center: WIP gnome-packagekit: Upower dropped from newest upstream release. Merge from debian gnome-power-manager: Fixed in newest upstream release. Merge from debian experimental gnome-session: Done in ppa, needs patches from git or new upstream release gnome-settings-daemon: 3.12 is ready out of the box, however that also requires gnome-desktop transition. 3.8 and also u-s-d: I have a package that is mostly working, however had to cherry-pick quite a few patches and may just be better to backport 3.12 power plugin. (considering g-s-d patches will be temporary, but u-s-d not so) kde: needs sc 4.13.3
[Desktop-packages] [Bug 1335125] Re: Wrong number of ticks by application icon in launcher
Workaround: pressing Super+W forces the tick count to correct itself. ** Package changed: compiz (Ubuntu) = unity (Ubuntu) ** Changed in: unity (Ubuntu) Status: New = Confirmed ** Changed in: unity (Ubuntu) Importance: Undecided = Medium ** Also affects: unity Importance: Undecided Status: New ** Changed in: unity Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1335125 Title: Wrong number of ticks by application icon in launcher Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: Since upgrade to 14.04 I've noticed that the number of ticks/markers that indicates the number of windows a the side of an application's icon is often incorrect. This seems to apply to Gnome Terminal, Firefox and Thunderbird and more. Reproduction #1: Open a terminal. Right click the launcher icon and choose New terminal. Observe there's only one ticks. Left click the launcher icon to expose both terminals. Observe the number of ticks is corrected. Choose either, it doesn't matter. Close one of the terminals. Observe there's still two ticks. The number of ticks doesn't seem to refresh until something happens in the launcher - either you click on something in the launcher, but the ticks seems to correct themselves at other times that I can't quite put my finger on. This is extremely distracting and interrupts work all the time checking to see what's left open to find that there's nothing there. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: compiz-core 1:0.9.11+14.04.20140423-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.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 CurrentDesktop: Unity Date: Fri Jun 27 14:26:07 2014 DistUpgraded: 2014-04-28 12:24:37,637 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu EcryptfsInUse: Yes ExecutablePath: /usr/bin/compiz GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:1033] InstallationDate: Installed on 2013-05-07 (415 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Micro-Star International Calpella platform ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic root=UUID=1aab217a-e362-4aab-9283-0b04525b2bdf ro quiet splash vt.handoff=7 SourcePackage: compiz UpgradeStatus: Upgraded to trusty on 2014-04-28 (60 days ago) dmi.bios.date: 07/21/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1681IG6 VER.109 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: Micro-Star International dmi.board.version: Ver.001 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 9 dmi.chassis.vendor: Micro-Star International dmi.chassis.version: Ver.001 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1681IG6VER.109:bd07/21/2010:svnMicro-StarInternational:pnCalpellaplatform:pvrVer.001:rvnMicro-StarInternational:rnTobefilledbyO.E.M.:rvrVer.001:cvnMicro-StarInternational:ct9:cvrVer.001: dmi.product.name: Calpella platform dmi.product.version: Ver.001 dmi.sys.vendor: Micro-Star International version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu Jun 26 09:47:01
[Desktop-packages] [Bug 1335332] [NEW] package texlive-base (not installed) failed to install/upgrade: cannot copy extracted data for './usr/share/texlive/texmf-dist/tex/generic/hyph-utf8/patterns/txt
Public bug reported: Happened while installing TeX Live for LaTeX. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: texlive-base (not installed) ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 Date: Fri Jun 27 16:16:36 2014 DuplicateSignature: package:texlive-base:(not installed):cannot copy extracted data for './usr/share/texlive/texmf-dist/tex/generic/hyph-utf8/patterns/txt/hyph-ru.pat.txt' to '/usr/share/texlive/texmf-dist/tex/generic/hyph-utf8/patterns/txt/hyph-ru.pat.txt.dpkg-new': unexpected end of file or stream ErrorMessage: cannot copy extracted data for './usr/share/texlive/texmf-dist/tex/generic/hyph-utf8/patterns/txt/hyph-ru.pat.txt' to '/usr/share/texlive/texmf-dist/tex/generic/hyph-utf8/patterns/txt/hyph-ru.pat.txt.dpkg-new': unexpected end of file or stream InstallationDate: Installed on 2014-06-04 (23 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: texlive-base Title: package texlive-base (not installed) failed to install/upgrade: cannot copy extracted data for './usr/share/texlive/texmf-dist/tex/generic/hyph-utf8/patterns/txt/hyph-ru.pat.txt' to '/usr/share/texlive/texmf-dist/tex/generic/hyph-utf8/patterns/txt/hyph-ru.pat.txt.dpkg-new': unexpected end of file or stream UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: texlive-base (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texlive-base in Ubuntu. https://bugs.launchpad.net/bugs/1335332 Title: package texlive-base (not installed) failed to install/upgrade: cannot copy extracted data for './usr/share/texlive/texmf-dist/tex/generic /hyph-utf8/patterns/txt/hyph-ru.pat.txt' to '/usr/share/texlive/texmf- dist/tex/generic/hyph-utf8/patterns/txt/hyph-ru.pat.txt.dpkg-new': unexpected end of file or stream Status in “texlive-base” package in Ubuntu: New Bug description: Happened while installing TeX Live for LaTeX. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: texlive-base (not installed) ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 Date: Fri Jun 27 16:16:36 2014 DuplicateSignature: package:texlive-base:(not installed):cannot copy extracted data for './usr/share/texlive/texmf-dist/tex/generic/hyph-utf8/patterns/txt/hyph-ru.pat.txt' to '/usr/share/texlive/texmf-dist/tex/generic/hyph-utf8/patterns/txt/hyph-ru.pat.txt.dpkg-new': unexpected end of file or stream ErrorMessage: cannot copy extracted data for './usr/share/texlive/texmf-dist/tex/generic/hyph-utf8/patterns/txt/hyph-ru.pat.txt' to '/usr/share/texlive/texmf-dist/tex/generic/hyph-utf8/patterns/txt/hyph-ru.pat.txt.dpkg-new': unexpected end of file or stream InstallationDate: Installed on 2014-06-04 (23 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) SourcePackage: texlive-base Title: package texlive-base (not installed) failed to install/upgrade: cannot copy extracted data for './usr/share/texlive/texmf-dist/tex/generic/hyph-utf8/patterns/txt/hyph-ru.pat.txt' to '/usr/share/texlive/texmf-dist/tex/generic/hyph-utf8/patterns/txt/hyph-ru.pat.txt.dpkg-new': unexpected end of file or stream UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/1335332/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1335334] [NEW] [HP EliteBook 8730w, Analog Devices AD1984A, Grey Headphone Out, Front] fails after a while
Public bug reported: When playing videos or audio in Totem sound is stuttering or repeting itself like a broken vinyl record. This happens even if Totem is minimized. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anmihovil 1850 F pulseaudio /dev/snd/pcmC0D0p: anmihovil 1850 F...m pulseaudio CurrentDesktop: Unity Date: Fri Jun 27 23:02:49 2014 InstallationDate: Installed on 2014-06-10 (17 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel Symptom_Jack: Grey Headphone Out, Front Symptom_Type: Sound works for a while, then breaks Title: [HP EliteBook 8730w, Analog Devices AD1984A, Grey Headphone Out, Front] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2008 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PAD Ver. F.08 dmi.board.name: 30EC dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 91.1E dmi.chassis.asset.tag: CNU90358BB dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PADVer.F.08:bd09/26/2008:svnHewlett-Packard:pnHPEliteBook8730w:pvrF.08:rvnHewlett-Packard:rn30EC:rvrKBCVersion91.1E:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8730w dmi.product.version: F.08 dmi.sys.vendor: Hewlett-Packard ** Affects: alsa-driver (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 alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1335334 Title: [HP EliteBook 8730w, Analog Devices AD1984A, Grey Headphone Out, Front] fails after a while Status in “alsa-driver” package in Ubuntu: New Bug description: When playing videos or audio in Totem sound is stuttering or repeting itself like a broken vinyl record. This happens even if Totem is minimized. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anmihovil 1850 F pulseaudio /dev/snd/pcmC0D0p: anmihovil 1850 F...m pulseaudio CurrentDesktop: Unity Date: Fri Jun 27 23:02:49 2014 InstallationDate: Installed on 2014-06-10 (17 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel Symptom_Jack: Grey Headphone Out, Front Symptom_Type: Sound works for a while, then breaks Title: [HP EliteBook 8730w, Analog Devices AD1984A, Grey Headphone Out, Front] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2008 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PAD Ver. F.08 dmi.board.name: 30EC dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 91.1E dmi.chassis.asset.tag: CNU90358BB dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PADVer.F.08:bd09/26/2008:svnHewlett-Packard:pnHPEliteBook8730w:pvrF.08:rvnHewlett-Packard:rn30EC:rvrKBCVersion91.1E:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8730w dmi.product.version: F.08 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1335334/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 449198] Re: No GUI option to change login theme
** Changed in: baltix Status: New = Invalid ** Changed in: gdm (Ubuntu) Status: Triaged = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/449198 Title: No GUI option to change login theme Status in GDM: The Gnome Display Manager: Won't Fix Status in “gdm” package in Ubuntu: Invalid Status in Baltix GNU/Linux: Invalid Bug description: Ubuntu 9.10 (Karmic Koala) doesn't allow to change the login screen theme. The System / Administration / Login Screen tool doesn't allow to change the GDM's background (wallpaper) or theme. This can be seen as a regression from previous Ubuntu versions. Currently users have to run the following command to change the GDM 2.28 theme: gksudo -u gdm dbus-launch gnome-appearance-properties More information: http://wiki.archlinux.org/index.php/Gnome_2.28_Changes#Configuring_gdm_2.28 This is not user friendly at all. See http://ubuntuforums.org/showthread.php?t=1292533page=2 To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/449198/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1335342] [NEW] Image #100 is sufferring audio dropouts and high CPU usage on mako
Public bug reported: 1) Ensure the device is on utopic #100 or above 2) Start the music app 3) Start playing music (flac files are easier to hear) 4) Notice that audible drops/pops/glitches can be heard in the output (changing the volume also causes more drops) 5) Note when running a terminal with top that the CPU usage of pulseaudio is ~25% (this may be related to the dropouts) It was expected that the audio should be played without any dropouts. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Description changed: 1) Ensure the device is on utopic #100 or above 2) Start the music app 3) Start playing music (flac files are easier to hear) 4) Notice that audible drops/pops/glitches can be heard in the output (changing the volume also causes more drops) + 5) Note when running a terminal with top that the CPU usage of pulseaudio is ~25% (this may be related to the dropouts) It was expected that the audio should be played without any dropouts. ** Summary changed: - Image #100 is sufferring audio dropouts on mako + Image #100 is sufferring audio dropouts and high CPU usage on mako -- 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/1335342 Title: Image #100 is sufferring audio dropouts and high CPU usage on mako Status in “pulseaudio” package in Ubuntu: New Bug description: 1) Ensure the device is on utopic #100 or above 2) Start the music app 3) Start playing music (flac files are easier to hear) 4) Notice that audible drops/pops/glitches can be heard in the output (changing the volume also causes more drops) 5) Note when running a terminal with top that the CPU usage of pulseaudio is ~25% (this may be related to the dropouts) It was expected that the audio should be played without any dropouts. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1335342/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1256654] Re: FireFox 25.0.1 Plugin Container CPU usage
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: firefox (Ubuntu) Status: New = Confirmed -- 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/1256654 Title: FireFox 25.0.1 Plugin Container CPU usage Status in “firefox” package in Ubuntu: Confirmed Bug description: Ubuntu 12.04.2, 32bit 2.1Ghz dou-core 2.5Gb RAM After upgrade from ver 25 to 25.0.1 many pages are now using 50-100% CPU usage after being fully loaded. Verified Plugin Container is the process hoging the CPU. Plugin Container is not crashing, but at 100% CPU load, you sure as heck can not use FF. Also I watch TV shows that are flash based. These show now show 50% or more CPU load, but the SAME show under version 25.0 only used 20-30% CPU. Is there any way I can roll back to ver 25? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1256654/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1332721] Re: Add patch to allow toolbar dragging
Do you know how I should contact upstream? For example, is there an appropriate mailing list? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1332721 Title: Add patch to allow toolbar dragging Status in “gtk+2.0” package in Ubuntu: Confirmed Bug description: Ubuntu already has a patch - 062_dnd_menubar.patch - that allows the window to be dragged by clicking on empty space in the menubar. The attached patch builds on this and allows empty space in the toolbar to be also dragged. It is essentially commit 7491e9e97aa6b0f9950897c4f1282b470c79d451 that went into gtk+3.0 way back in 2010. This would make GTK2 themes behave much more like GTK3 themes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1332721/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 463026] Re: User list search box should be disabled when user list is disabled.
** Changed in: gdm (Ubuntu) Status: Triaged = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm in Ubuntu. https://bugs.launchpad.net/bugs/463026 Title: User list search box should be disabled when user list is disabled. Status in GDM: The Gnome Display Manager: Expired Status in “gdm” package in Ubuntu: Invalid Bug description: Binary package hint: gdm If the gdm user list (face browser) is enabled, then beginning to type a username locates the appropriate entry in the user list. If the user list is disabled, this search box serves no purpose and should be disabled. Since users are accustomed to typing their username at a login screen, the fact that this search box appears is confusing, leading them to believe that they are entering their username which is not true. If they continue to press enter and begin typing their password, which is a rather standard and reflexive behavior, then their password winds up appearing in plain text on the screen. The combination of this useless search box with the requirement of clicking a Log In button leads to a very confusing environment for users who disable the face browser. In an enterprise environment, this is a serious problem. To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/463026/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1303462] Re: [Regression] Window titlebars placed behind panel
I've just enabled proposed and updated my system. I can also confirm the bug has been fixed. Thanks! -- 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/1303462 Title: [Regression] Window titlebars placed behind panel Status in Compiz: Fix Committed Status in Compiz 0.9.11 series: In Progress Status in Unity: Invalid Status in “compiz” package in Ubuntu: Fix Released Status in “compiz” source package in Trusty: Fix Committed Bug description: [Impact] Some windows that open from within another window such as a Firefox popup window will be placed with the decorations under the Panel. Also, some windows will just open with the decoration under the Panel such as virt-manager. This can cause confusion for the user on how to move the window and how to close it. This can be very disruptive to a user's workflow. [Test case] 1. Install virt-manager. 2. Make sure no other windows are open. 3. Start virt-manager. virt-manager should start in the top left. With this fix, the decoration should be visible. [Regression potential] None identified. * Debdiff is found at https://launchpadlibrarian.net/178439518/compiz- trusty-sru-2.debdiff * Original description: Windows with a height of (Display Height - Panel Height) get placed at y=0 (behind the top panel) which means window titlebars are not reachable without alt-moving the window. I assume this happens with windows that want to resize themselves if their height exceeds the display resolution. Reproducable on my 1366x768 screen with LibreOffice and a Qt 5 desktop application I'm working on. TEMPORARY WORKAROUND: Use the Cntrl+SuperKey+Right or Left Arrow Key This will resize your currently focused window to occupy the Right (Left) half of the screen. The Title Bar should now be visible, so you need to drag it and resize it at your prefered position. This will save the new position in place of the previously hidden state. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140403-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sun Apr 6 21:45:41 2014 InstallationDate: Installed on 2014-04-04 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140404) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1303462/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1335357] [NEW] nvidia-331 331.38-0ubuntu7: nvidia-331 kernel module failed to build
Public bug reported: Failed to install when processing list of upgrades ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331 331.38-0ubuntu7 ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 DKMSKernelVersion: 3.13.0-30-generic Date: Fri Jun 27 19:13:24 2014 InstallationDate: Installed on 2014-05-11 (47 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) PackageVersion: 331.38-0ubuntu7 SourcePackage: nvidia-graphics-drivers-331 Title: nvidia-331 331.38-0ubuntu7: nvidia-331 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-331 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1335357 Title: nvidia-331 331.38-0ubuntu7: nvidia-331 kernel module failed to build Status in “nvidia-graphics-drivers-331” package in Ubuntu: New Bug description: Failed to install when processing list of upgrades ProblemType: Package DistroRelease: Ubuntu 14.04 Package: nvidia-331 331.38-0ubuntu7 ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 DKMSKernelVersion: 3.13.0-30-generic Date: Fri Jun 27 19:13:24 2014 InstallationDate: Installed on 2014-05-11 (47 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) PackageVersion: 331.38-0ubuntu7 SourcePackage: nvidia-graphics-drivers-331 Title: nvidia-331 331.38-0ubuntu7: nvidia-331 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1335357/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1246272] Re: Keyboard layout changing randomly
*** This bug is a duplicate of bug 1240198 *** https://bugs.launchpad.net/bugs/1240198 The bug is not fixed, even though the suggestion from the other thread concerning ibus settings does fix it. What I mean is - without going into dconf and making the necessary changes, my system still sets the keyboard to english, despite the fact I don't have it as a layout option and didn't even have it during installation. -- 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/1246272 Title: Keyboard layout changing randomly Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Status in “unity-settings-daemon” package in Ubuntu: Confirmed Bug description: Just upgraded from 12.04 (raring) to 12.10 (saucy) and keyboard layout keeps changing from pt_br to what I think is en_us. It seems random so I don't know what trigger this, but sometimes just alt-tabbing is enough to mess with keyboard layout in one of the windows. I already removed the en_us from my keyboard sources, double checked the use of one source for all windows, and even removed accelerators to switch between layouts but none have worked. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu44 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 Date: Wed Oct 30 09:12:48 2013 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2013-05-20 (163 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: Upgraded to saucy on 2013-10-22 (8 days ago) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu4 deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20131016.2-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3+13.10.20131004-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1246272/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp