[Desktop-packages] [Bug 2025538] Re: Unrequested kernel update
In lunar / 23.04, there is no linux-objects-nvidia-535-6.2.0-25-generic package, but the linux-image-6.2.0-25-generic package has been available for some time. Package upgrades therefore insist on switching to nvidia- dkms, no matter what I try to do. So I'm still on 6.2.0-24. Is this just another aspect of this bug, or is the linux-objects- nvidia-* package discontinued and we are actually supposed to switch to dkms? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/2025538 Title: Unrequested kernel update Status in linux-restricted-modules package in Ubuntu: Triaged Status in linux-signed-nvidia-5.19 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-535 package in Ubuntu: In Progress Status in ubuntu-drivers-common package in Ubuntu: Triaged Bug description: Running Kubuntu 22.04 LTS (lsb_release -a: Ubuntu 22.04.2 LTS) I was informed that new packages are available and I just hit update. This caused my system running 5.15.0-76-generic to be switched to 5.19.0-1010-nvidia-lowlatency. I noted this as I was now running into bugs like https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/2017980 The update was, as stated in history.log: Start-Date: 2023-07-01 00:25:40 Commandline: packagekit role='update-packages' Requested-By: cm (1000) Install: linux-objects-nvidia-510-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-signatures-nvidia-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-image-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-nvidia-510-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-nvidia-510-nvidia-lowlatency-edge:amd64 (5.19.0-1010.10, automatic) Upgrade: libmm-glib0:amd64 (1.20.0-1~ubuntu22.04.1, 1.20.0-1~ubuntu22.04.2), modemmanager:amd64 (1.20.0-1~ubuntu22.04.1, 1.20.0-1~ubuntu22.04.2) => This simple update was changing my kernel from 5.15 to 5.19 without a request from my side ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-1010-nvidia-lowlatency 5.19.0-1010.10 ProcVersionSignature: Ubuntu 5.19.0-1010.10-nvidia-lowlatency 5.19.17 Uname: Linux 5.19.0-1010-nvidia-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Jul 1 21:16:09 2023 InstallationDate: Installed on 2018-10-10 (1724 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: linux-signed-nvidia-5.19 UpgradeStatus: Upgraded to jammy on 2022-07-24 (342 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/2025538/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1848009] Re: Delay launching application launcher gets longer the more apps are open
Upstream fix is most likely https://gitlab.gnome.org/GNOME/gnome-
shell/merge_requests/763
I have installed gnome-shell{,-common}
3.34.1+git20191024-1ubuntu1~19.10.1 from eoan-proposed and verified that
the "opening activities" delay goes down from ~4 seconds in
3.34.1-1ubuntu1 to <1 second in the -proposed package, while having a
total of 22 windows open.
I have not done any serious regression testing, so not changing the tag.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1848009
Title:
Delay launching application launcher gets longer the more apps are
open
Status in gnome-shell package in Ubuntu:
Fix Released
Status in gnome-shell source package in Eoan:
Fix Committed
Bug description:
[ Impact ]
On latest up to date daily image on my ThinkPad X220 / i7 / 16GB / 150GB SSD.
If I launch a bunch of applications - possibly a slightly unreasonable
number, but a lot anyway - with minimal CPU or memory in use, the button to
launch applications in the bottom left takes progressively longer to run.
Video showing it: https://www.youtube.com/watch?v=BRbFk-n9KzQ
[ Test case ]
- Launch lots of applications
- Click in the applications icon in the launcher (or press super+A)
- Animation should not be delayed (some delay is still expected depending
on the number of installed applications)
[ Regression potential ]
Windows in activities overview might have wrong positioning
This is uploaded under the GNOME MRE:
https://wiki.ubuntu.com/StableReleaseUpdates/GNOME
---
Steps to reproduce.
Open application launcher
Note a ~0.6s delay before the icons fly onto the screen
Open GNOME Software
Install all the editors picks
Launch a bunch of applications
Click the application launcher
Note a 4s delay before icons fly onto the screen.
Expectation
Honestly, no delay at all, but it should be at least consistent with when no
applications are running, so 0.6s delay as per the state when no apps are
launched.
ProblemType: BugDistroRelease: Ubuntu 19.10
Package: gnome-shell 3.34.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
Uname: Linux 5.3.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 14 13:02:04 2019
DisplayManager: gdm3
InstallationDate: Installed on 2019-10-13 (0 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191012)
RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1SourcePackage:
gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1848009/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1600299] Re: Giving up after 5 attempts. Error: g-io-error-quark: The specified location is not mounted
I see this in journalctl at approx. the time of this "giving up after 5 attempts", I also use sftp: (where XXX is my user name) Okt 25 17:51:09 XXX kernel: gvfsd-sftp[10782]: segfault at 55b30002 ip 7f0a424e63ae sp 7fffe1c32c00 error 4 in libc-2.30.so[7f0a4246e000+178000] Okt 25 17:51:09 XXX kernel: Code: 84 5c ff ff ff 0f 1f 80 00 00 00 00 48 8d 0c 58 0f b7 11 66 85 d2 0f 84 45 ff ff ff 48 8d 04 d8 83 ea 01 4c 8b 80 80 00 00 00 <49> 8b 30 48 89 b0 80 00 00 00 66 8 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1600299 Title: Giving up after 5 attempts. Error: g-io-error-quark: The specified location is not mounted Status in Déjà Dup: Triaged Status in deja-dup package in Ubuntu: Triaged Status in deja-dup package in Mandriva: New Bug description: I've got my system set up with off-site backup over sftp. This works fine but the problem is that while deja-dup is gathering files and calculating the backup delta the connection to the server times out. This means that it's not available when deja-dup actually tries to push files to the server and results in this error message: Giving up after 5 attempts. Error: g-io-error-quark: The specified location is not mounted (16) By sitting in the file manager and jumping between folders the connection can be kept alive but that's rather annoying and requires my presence. Would really like to see deja-dup actually trying to set up the connection again instead. Using: Manjaro 16.06.1 deja-dup 34.2-1 To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1600299/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1720890] Re: vulkan-smoketest segfaults steam vulkan games segfault
Using artful, I updated these packages (everything that used to have version "17.2.2-0ubuntu1" on my system) to version "17.2.4-0ubuntu1~17.10.1" from -proposed: libegl1-mesa:amd64 libgbm1:amd64 libgl1-mesa-dev:amd64 libgl1-mesa-dri:amd64 libgl1-mesa-dri:i386 libgl1-mesa-glx:amd64 libgl1-mesa-glx:i386 libglapi-mesa:amd64 libglapi-mesa:i386 libgles2-mesa:amd64 libwayland-egl1-mesa:amd64 libxatracker2:amd64 mesa-common-dev:amd64 mesa-vdpau-drivers:amd64 mesa-vulkan-drivers:amd64 After a reboot, I can confirm Lawrence's observation that vulkan- smoketest segfaulted on the old version, but seems to work fine using the version from -proposed. Since Lawrence forgot to remove the verification-needed-artful tag, I'm going to remove it now. ** Tags removed: verification-needed-artful -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1720890 Title: vulkan-smoketest segfaults steam vulkan games segfault Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Xenial: Fix Committed Status in mesa source package in Artful: Fix Committed Bug description: $ lsb_release -rd Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 $ apt-cache policy mesa-vulkan-drivers mesa-vulkan-drivers: Installed: 17.2.1-0ubuntu1 Candidate: 17.2.1-0ubuntu1 Version table: *** 17.2.1-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu artful/universe amd64 Packages 100 /var/lib/dpkg/status Easily reproducible : apt-get install mesa-vulkan-drivers apt-get install vulkan-utils Open a terminal type vulkan-smoketest instead of a glxgears type window it will segfault. message from kernel.log: Sep 29 16:23:53 Tardis-1 kernel: [17709.532915] vulkan-smoketes[11798]: segfault at 0 ip 7fed61a17914 sp 7ffedcb8f850 error 6 in libvulkan_radeon.so[7fed619ab000+18b000] syslog: Sep 28 10:38:13 Tardis-1 kernel: [18292.174313] vulkan-smoketes[13385]: segfault at 0 ip 7f62705a7914 sp 7ffd0edc6260 error 6 in libvulkan_radeon.so[7f627053b000+18b000] What should happen is a glxgears like window will open and render properly instead of segfaulting. It appears that the culprit is an old or broken libvulkan_radeon.so provided by mesa-vulkan-drivers. As a test I renamed the old lib and dropped in a newer version from oibaf's ppa. smoketest now passes steam's The Talos Princible and Mad Max now work properly in Vulkan mode as well instead of segfaulting. This issue is also present on Zesty and fixed in both Oibaf's and Padoka's ppa's since April back when they were rolling 17.2 mesa. I have no idea if libvulkan_intel.so also needs updating no hardware to check. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1720890/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1641380] Re: chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec certs
Flash not working is less of a show stopper than half of the internet not working because of trust issues. (Who needs flash anyway? I use it maybe once a month, but now I can't do my christmas shopping in Chromium because amazon doesn't work no matter what.) So if you can't get flash to work, I'd recommend just pushing the new chromium anyway. :-) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1641380 Title: chromium-browser: ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for Symantec certs Status in chromium-browser package in Ubuntu: Fix Committed Bug description: Chromium browser in xenial no longer trusts Symantec issued certificates. See [1]. 1. https://bugs.chromium.org/p/chromium/issues/detail?id=664177 Ubuntu release: 16.04 chromium-browser: 53.0.2785.143-0ubuntu0.16.04.1.1254 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1641380/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1622893] Re: NetworkManager takes very long to start, or times out, blocked on RNG
Concerning the "bootspeed" tag, the NM issue would be less noticable if "rc-local.service" was removed from "After=" in plymouth-quit.service. That way, my boot-to-graphical-login is a few seconds faster because plymouth is only visible for a very very short time instead of waiting up to 8 seconds for the network to come up. I did that using systemd override, and now my boot on kernel 4.4 is almost as fast as it was in 16.04. Of course, technically the full boot including nmbd etc. still takes the same time because NM is still slow, but I don't really care if nmbd is up when I type my password into lightdm. The only thing that matters to me is that I can type my password and then fire up Chromium, by which time the network generally is ready to use in my case. But maybe there's a good reason for some people to have rc.local executed (and therefor network ready to use) before starting lightdm. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1622893 Title: NetworkManager takes very long to start, or times out, blocked on RNG Status in Auto Package Testing: Fix Released Status in gnutls28 package in Ubuntu: Triaged Status in network-manager package in Ubuntu: New Status in network-manager package in Debian: New Bug description: Since a few days ago, NetworkManager.service takes awfully long to start, or even times out on failure and then gets restarted. This happens in a 16.10 desktop amd64 installation in QEMU, or e. g. in the systemd "boot-smoke" autopkgtest where every boot takes > 1:30 minutes due to the NM timeout. In the journal there is no actual logging from /usr/sbin/NetworkManager yet, just the start timeout. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: network-manager 1.2.2-0ubuntu8 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: i3 Date: Tue Sep 13 10:05:05 2016 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback source-directory interfaces.d NetworkManager.conf: [main] plugins=ifupdown,keyfile,ofono [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.2connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1622893/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1621278] [NEW] package printer-driver-gutenprint 5.2.11-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 4
Public bug reported: Error displayed during GUI-based upgrade from 14.04 to 16.04. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: printer-driver-gutenprint 5.2.11-1 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Thu Sep 8 01:53:22 2016 DuplicateSignature: package:printer-driver-gutenprint:5.2.11-1 Setting up printer-driver-gutenprint (5.2.11-1) ... sed: Kann /var/cache/cups/ppd-updates nicht bearbeiten: Das ist keine normale Datei dpkg: error processing package printer-driver-gutenprint (--configure): subprocess installed post-installation script returned error exit status 4 ErrorMessage: subprocess installed post-installation script returned error exit status 4 InstallationDate: Installed on 2013-03-10 (1277 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: gutenprint Title: package printer-driver-gutenprint 5.2.11-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 4 UpgradeStatus: Upgraded to xenial on 2016-09-07 (0 days ago) ** Affects: gutenprint (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gutenprint in Ubuntu. https://bugs.launchpad.net/bugs/1621278 Title: package printer-driver-gutenprint 5.2.11-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 4 Status in gutenprint package in Ubuntu: New Bug description: Error displayed during GUI-based upgrade from 14.04 to 16.04. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: printer-driver-gutenprint 5.2.11-1 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Thu Sep 8 01:53:22 2016 DuplicateSignature: package:printer-driver-gutenprint:5.2.11-1 Setting up printer-driver-gutenprint (5.2.11-1) ... sed: Kann /var/cache/cups/ppd-updates nicht bearbeiten: Das ist keine normale Datei dpkg: error processing package printer-driver-gutenprint (--configure): subprocess installed post-installation script returned error exit status 4 ErrorMessage: subprocess installed post-installation script returned error exit status 4 InstallationDate: Installed on 2013-03-10 (1277 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: gutenprint Title: package printer-driver-gutenprint 5.2.11-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 4 UpgradeStatus: Upgraded to xenial on 2016-09-07 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gutenprint/+bug/1621278/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1463598] Re: Chromium 43 fails to use hardware acceleration
Hi, I'm just wondering if WebGL is still disabled in 14.04, even though we are on chromium 44 now? I wanted to enable WebGL just to see if I could watch 360° Youtube vids then, and now noticed that it no longer works at all, apparently due to this Ubuntu change. I realize that lots of crashes are GPU-related, but IMHO ripping that feature out of chromium completely is bad, as most chromium GPU features are blacklisted (by Google) on my AMD system anyway because they tend to cause problems. If it's too much of an issue, maybe GPU stuff could be blacklisted for all drivers, and those who would like to use WebGL etc. could manually override the blacklist in about:flags? That's what I have done repeatedly in the past, although I'm well aware that any strange behaviour could be related to disabling the blacklist. -- 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/1463598 Title: Chromium 43 fails to use hardware acceleration Status in chromium-browser package in Ubuntu: Fix Released Bug description: After installing package chromium-browser 43.0.2357.81-0ubuntu0.14.04.1.1089 hardware acceleration becomes disabled. I had no problem with previous chromium version. Console output: $ chromium-browser [3150:3191:0609/190556:ERROR:browser_gpu_channel_host_factory.cc(134)] Failed to launch GPU process. [3150:3150:0609/190556:ERROR:url_pattern_set.cc(240)] Invalid url pattern: chrome://print/* [3150:3191:0609/190556:ERROR:browser_gpu_channel_host_factory.cc(134)] Failed to launch GPU process. [3150:3191:0609/190556:ERROR:browser_gpu_channel_host_factory.cc(134)] Failed to launch GPU process. chrome://gpu: Graphics Feature Status Canvas: Software only, hardware acceleration unavailable Flash: Software only, hardware acceleration unavailable Flash Stage3D: Software only, hardware acceleration unavailable Flash Stage3D Baseline profile: Software only, hardware acceleration unavailable Compositing: Software only, hardware acceleration unavailable Multiple Raster Threads: Unavailable Rasterization: Software only, hardware acceleration unavailable Threaded Rasterization: Unavailable Video Decode: Software only, hardware acceleration unavailable Video Encode: Software only, hardware acceleration unavailable WebGL: Unavailable Driver Bug Workarounds clear_uniforms_before_first_program_use count_all_in_varyings_packing disable_chromium_framebuffer_multisample disable_ext_occlusion_query disable_post_sub_buffers_for_onscreen_surfaces scalarize_vec_and_mat_constructor_args Problems Detected GPU process was unable to boot: GPU access is disabled in chrome://settings. Disabled Features: all - - - Actually GPU access is *not* disabled from settings. Workarounds like "--disable-gpu-sandbox" or "LIBGL_DRI3_DISABLE=1" didn't helped at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1463598/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1132063] Re: Mouse settings missing from Mouse Touchpad dialog
I've built (on trusty) and installed the unity-control-center package from the PPA, and unity-settings-daemon from utopic, and now I have a mouse pointer speed option in the settings. That setting was missing when I used the original trusty packages. Now another problem is that the mouse cursor is pretty fast, even when using the slowest setting. My mouse has a hardware DPI change button though, so I can fix that. :-) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1132063 Title: Mouse settings missing from Mouse Touchpad dialog Status in gnome-control-center package in Ubuntu: Confirmed Status in unity-control-center package in Ubuntu: In Progress Bug description: On up to date Raring alpha, on System Settings Mouse Touchpad the Mouse settings are completely missing. The General and Touchpad sections are there but none for mouse. See attached screenshot. xinput --list shows ~$ xinput --list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MOSART Semi. 2.4G Keyboard Mouseid=11 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=14 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Sleep Buttonid=9[slave keyboard (3)] ↳ MOSART Semi. 2.4G Keyboard Mouseid=10 [slave keyboard (3)] ↳ Dell Dell USB Keyboard id=12 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=13 [slave keyboard (3)] and from lsusb: Bus 003 Device 002: ID 062a:3286 Creative Labs Nano Receiver [Sandstrom Laser Mouse SMWLL11] ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-control-center 1:3.6.3-0ubuntu13 ProcVersionSignature: Ubuntu 3.8.0-7.15-generic 3.8.0 Uname: Linux 3.8.0-7-generic i686 ApportVersion: 2.8-0ubuntu4 Architecture: i386 Date: Sat Feb 23 09:40:41 2013 InstallationDate: Installed on 2012-08-01 (205 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha i386 (20120730.1) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu6.1 deja-dup25.5-0ubuntu1 gnome-control-center-signon 0.1.2bzr12.12.05-0ubuntu1 gnome-control-center-unity 1.2daily13.02.15-0ubuntu1 indicator-datetime 12.10.3daily13.02.06-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1132063/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1132063] Re: Mouse settings missing from Mouse Touchpad dialog
Sorry, the unity-control-center package was not taken from the PPA, but from the bzr branch linked in this bug report. Not sure if these packages use the same code. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1132063 Title: Mouse settings missing from Mouse Touchpad dialog Status in gnome-control-center package in Ubuntu: Confirmed Status in unity-control-center package in Ubuntu: In Progress Bug description: On up to date Raring alpha, on System Settings Mouse Touchpad the Mouse settings are completely missing. The General and Touchpad sections are there but none for mouse. See attached screenshot. xinput --list shows ~$ xinput --list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MOSART Semi. 2.4G Keyboard Mouseid=11 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=14 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Sleep Buttonid=9[slave keyboard (3)] ↳ MOSART Semi. 2.4G Keyboard Mouseid=10 [slave keyboard (3)] ↳ Dell Dell USB Keyboard id=12 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=13 [slave keyboard (3)] and from lsusb: Bus 003 Device 002: ID 062a:3286 Creative Labs Nano Receiver [Sandstrom Laser Mouse SMWLL11] ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-control-center 1:3.6.3-0ubuntu13 ProcVersionSignature: Ubuntu 3.8.0-7.15-generic 3.8.0 Uname: Linux 3.8.0-7-generic i686 ApportVersion: 2.8-0ubuntu4 Architecture: i386 Date: Sat Feb 23 09:40:41 2013 InstallationDate: Installed on 2012-08-01 (205 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha i386 (20120730.1) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu6.1 deja-dup25.5-0ubuntu1 gnome-control-center-signon 0.1.2bzr12.12.05-0ubuntu1 gnome-control-center-unity 1.2daily13.02.15-0ubuntu1 indicator-datetime 12.10.3daily13.02.06-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1132063/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1132063] Re: Mouse settings missing from Mouse Touchpad dialog
Lorenzo, have you tried the PPA referenced by Iain Lane (#35)? I'd love to test that, but I'm still on trusty and the debs don't work. Let me try to build the package locally. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1132063 Title: Mouse settings missing from Mouse Touchpad dialog Status in gnome-control-center package in Ubuntu: Confirmed Status in unity-control-center package in Ubuntu: In Progress Bug description: On up to date Raring alpha, on System Settings Mouse Touchpad the Mouse settings are completely missing. The General and Touchpad sections are there but none for mouse. See attached screenshot. xinput --list shows ~$ xinput --list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MOSART Semi. 2.4G Keyboard Mouseid=11 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=14 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Sleep Buttonid=9[slave keyboard (3)] ↳ MOSART Semi. 2.4G Keyboard Mouseid=10 [slave keyboard (3)] ↳ Dell Dell USB Keyboard id=12 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=13 [slave keyboard (3)] and from lsusb: Bus 003 Device 002: ID 062a:3286 Creative Labs Nano Receiver [Sandstrom Laser Mouse SMWLL11] ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-control-center 1:3.6.3-0ubuntu13 ProcVersionSignature: Ubuntu 3.8.0-7.15-generic 3.8.0 Uname: Linux 3.8.0-7-generic i686 ApportVersion: 2.8-0ubuntu4 Architecture: i386 Date: Sat Feb 23 09:40:41 2013 InstallationDate: Installed on 2012-08-01 (205 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha i386 (20120730.1) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu6.1 deja-dup25.5-0ubuntu1 gnome-control-center-signon 0.1.2bzr12.12.05-0ubuntu1 gnome-control-center-unity 1.2daily13.02.15-0ubuntu1 indicator-datetime 12.10.3daily13.02.06-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1132063/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1400626] Re: Please backport xtrans, libdrm, x11proto-{fonts, core} packages for 14.04.2
I tried this again now, and after installing libgl1-mesa-dev-lts-utopic
I was able to re-install qt5-default and qtbase5-dev, and then ubuntu-
sdk.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to x11proto-core in Ubuntu.
https://bugs.launchpad.net/bugs/1400626
Title:
Please backport xtrans, libdrm, x11proto-{fonts,core} packages for
14.04.2
Status in libdrm package in Ubuntu:
Invalid
Status in llvm-toolchain-snapshot package in Ubuntu:
Invalid
Status in x11proto-core package in Ubuntu:
Invalid
Status in x11proto-fonts package in Ubuntu:
Invalid
Status in xorg package in Ubuntu:
Invalid
Status in xtrans package in Ubuntu:
Invalid
Status in libdrm source package in Trusty:
Fix Released
Status in llvm-toolchain-snapshot source package in Trusty:
Fix Released
Status in x11proto-core source package in Trusty:
Fix Released
Status in x11proto-fonts source package in Trusty:
Fix Released
Status in xorg source package in Trusty:
Fix Committed
Status in xtrans source package in Trusty:
Fix Released
Bug description:
In order to upload the new xorg-server we need to backport the following
packages from utopic:
libdrm
x11proto-core
x11proto-fonts
xtrans
libdrm 2.4.52-1-2.4.56-1 seems to have the following changes:
- Hides private symbols from all libdrm libraries
- fixes MSAA on Hawaii (radeon).
- Adds cherryview pci-ids (intel).
- Makes libdrm-nouveau threadsafe with concurrent access to the drm fd.
- Fixes to exynos and freedreno.
- Enables building libdrm-freedreno1 and libdrm-exynos1
x11proto-core's main change appears to be changing from the 'pointer' type to
'void *':
https://launchpadlibrarian.net/173873109/x11proto-core_7.0.24-1_7.0.26-1.diff.gz
x11proto-fonts' main change is the same as x11proto-core, but the
documentation is reformatted too:
https://launchpadlibrarian.net/173873038/x11proto-fonts_2.1.2-1_2.1.3-1.diff.gz
xtrans seems to have 2 minor changes, increase default unix pipe size and add
support for systemd socket activation:
https://launchpadlibrarian.net/173873112/xtrans_1.3.2-1_1.3.4-1.diff.gz
xorg needs to be slightly updated, to allow xserver-xorg to provide
the unrenamed lts-utopic, and to allow xorg to be installed with the
renamed xorg-server.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1400626/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1400626] Re: Please backport xtrans, libdrm, x11proto-{fonts, core} packages for 14.04.2
Is there any way to preserve wine, libsdl-*-dev and qt5 when installing
the hardware enablement bits on 14.04 (with -proposed disabled)?
I tried the suggested apt command lines, but none of them seemed to
install the new mesa/xorg stack and preserve wine/qt5/libsdl at the same
time. See the attached apt output.
** Attachment added: apt-hwe.txt
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1400626/+attachment/4315207/+files/apt-hwe.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to x11proto-core in Ubuntu.
https://bugs.launchpad.net/bugs/1400626
Title:
Please backport xtrans, libdrm, x11proto-{fonts,core} packages for
14.04.2
Status in libdrm package in Ubuntu:
Invalid
Status in llvm-toolchain-snapshot package in Ubuntu:
Invalid
Status in x11proto-core package in Ubuntu:
Invalid
Status in x11proto-fonts package in Ubuntu:
Invalid
Status in xorg package in Ubuntu:
Invalid
Status in xtrans package in Ubuntu:
Invalid
Status in libdrm source package in Trusty:
Fix Released
Status in llvm-toolchain-snapshot source package in Trusty:
Fix Released
Status in x11proto-core source package in Trusty:
Fix Released
Status in x11proto-fonts source package in Trusty:
Fix Released
Status in xorg source package in Trusty:
Fix Committed
Status in xtrans source package in Trusty:
Fix Released
Bug description:
In order to upload the new xorg-server we need to backport the following
packages from utopic:
libdrm
x11proto-core
x11proto-fonts
xtrans
libdrm 2.4.52-1-2.4.56-1 seems to have the following changes:
- Hides private symbols from all libdrm libraries
- fixes MSAA on Hawaii (radeon).
- Adds cherryview pci-ids (intel).
- Makes libdrm-nouveau threadsafe with concurrent access to the drm fd.
- Fixes to exynos and freedreno.
- Enables building libdrm-freedreno1 and libdrm-exynos1
x11proto-core's main change appears to be changing from the 'pointer' type to
'void *':
https://launchpadlibrarian.net/173873109/x11proto-core_7.0.24-1_7.0.26-1.diff.gz
x11proto-fonts' main change is the same as x11proto-core, but the
documentation is reformatted too:
https://launchpadlibrarian.net/173873038/x11proto-fonts_2.1.2-1_2.1.3-1.diff.gz
xtrans seems to have 2 minor changes, increase default unix pipe size and add
support for systemd socket activation:
https://launchpadlibrarian.net/173873112/xtrans_1.3.2-1_1.3.4-1.diff.gz
xorg needs to be slightly updated, to allow xserver-xorg to provide
the unrenamed lts-utopic, and to allow xorg to be installed with the
renamed xorg-server.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1400626/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1400626] Re: Please backport xtrans, libdrm, x11proto-{fonts, core} packages for 14.04.2
Thanks, Maarten. I just noticed my comment was missing the apt command
that I used.
I now use
LANG=C sudo apt install --install-recommends libgles2-mesa-lts-utopic
libglapi-mesa-lts-utopic linux-generic-lts-utopic xserver-xorg-lts-
utopic libgl1-mesa-dri-lts-utopic libegl1-mesa-drivers-lts-utopic libgl1
-mesa-glx-lts-utopic:i386
and now wine is preserved. However, I still lose qt5-default,
qtbase5-dev and some other qt5 libs, and also libsdl2-2.0-0 and related
sdl libs, and some random other libs where I'm not sure I really need
them (I guess not). Adding qt5-default and qtbase5-dev to the command
leads to http://paste.ubuntu.com/10141032/ (I already have the utopic
kernel, so that note there by apt is correct).
I'm not sure if this is a bug in one of the backported packages, or
another package, or even my system setup or apt skills. Since #16 and
#13 apparently had the same issue, it might be related. Let me know if
this is not the right place to post this. :-)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to x11proto-core in Ubuntu.
https://bugs.launchpad.net/bugs/1400626
Title:
Please backport xtrans, libdrm, x11proto-{fonts,core} packages for
14.04.2
Status in libdrm package in Ubuntu:
Invalid
Status in llvm-toolchain-snapshot package in Ubuntu:
Invalid
Status in x11proto-core package in Ubuntu:
Invalid
Status in x11proto-fonts package in Ubuntu:
Invalid
Status in xorg package in Ubuntu:
Invalid
Status in xtrans package in Ubuntu:
Invalid
Status in libdrm source package in Trusty:
Fix Released
Status in llvm-toolchain-snapshot source package in Trusty:
Fix Released
Status in x11proto-core source package in Trusty:
Fix Released
Status in x11proto-fonts source package in Trusty:
Fix Released
Status in xorg source package in Trusty:
Fix Committed
Status in xtrans source package in Trusty:
Fix Released
Bug description:
In order to upload the new xorg-server we need to backport the following
packages from utopic:
libdrm
x11proto-core
x11proto-fonts
xtrans
libdrm 2.4.52-1-2.4.56-1 seems to have the following changes:
- Hides private symbols from all libdrm libraries
- fixes MSAA on Hawaii (radeon).
- Adds cherryview pci-ids (intel).
- Makes libdrm-nouveau threadsafe with concurrent access to the drm fd.
- Fixes to exynos and freedreno.
- Enables building libdrm-freedreno1 and libdrm-exynos1
x11proto-core's main change appears to be changing from the 'pointer' type to
'void *':
https://launchpadlibrarian.net/173873109/x11proto-core_7.0.24-1_7.0.26-1.diff.gz
x11proto-fonts' main change is the same as x11proto-core, but the
documentation is reformatted too:
https://launchpadlibrarian.net/173873038/x11proto-fonts_2.1.2-1_2.1.3-1.diff.gz
xtrans seems to have 2 minor changes, increase default unix pipe size and add
support for systemd socket activation:
https://launchpadlibrarian.net/173873112/xtrans_1.3.2-1_1.3.4-1.diff.gz
xorg needs to be slightly updated, to allow xserver-xorg to provide
the unrenamed lts-utopic, and to allow xorg to be installed with the
renamed xorg-server.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1400626/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1359265] Re: Characters mixing up in address bar
I was still able to reproduce this using Version 39.0.2171.65-0ubuntu0.14.04.1.1064 (hope we can get an update soon btw :D), but it appears to be much more difficult now. It no longer happens when I type at my normal typing speed. Maybe that's because the omnibar suggestions apparently load pretty fast now, it used to be much slower. Only characters typed while the suggestions load (i.e. chromium appears to be frozen during that time) are mixed up. The only way I can reproduce this now is: - Open a new tab - Concentrate and try to type asdf as fast as possible using the left hand - Usually comes up as adsf in omnibar, like in 90% of attempts I verified that my asdf typing skills are okay by opening gedit and typing asdf as fast as possible 20 times. That worked correctly. I'm not sure which input method I'm using. It's a USB keyboard. I tried to find out how to identify my system's input method, but Google just tells me how to type Japanese characters. ** Changed in: chromium-browser (Ubuntu) Status: Incomplete = 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/1359265 Title: Characters mixing up in address bar Status in chromium-browser package in Ubuntu: Confirmed Bug description: I hope this wasn't reported already, but couldn't find any recent reports. This is a relatively new bug, I don't think it was in v34. I often move the cursor to the address bar using F6 and instantly start typing my URL / search term afterwards. F6 leads to a quite noticable freeze while the suggestions box (or whatever that box below the bar is called) loads, at least on my aging ~5 years old system. Same issue when opening a new tab and starting to type, the suggestions take a while to load so chromium freezes for some time. That's not a big issue, but any characters I type during the freeze may come up in wrong order once chromium unfreezes. Sometimes they are ordered correctly, but quite often some of the letters are swapped. So it's not just in rare circumstances, but the freeze is not that easily reproducible because it seems to happen only when the bar wasn't used for some time. When there's no (or only a very short) freeze, there's no bug. At first I thought that my typing skills have suffered a lot because I was googling for slightly wrong terms all the time, but then noticed that chromium (or something that handles input and passes it to chromium?) is to blame, not me. [Or maybe I really hit the keys in a wrong order all the time while thinking that it is correct, but that seems unlikely, since I usually fix those finger syncing typos unconsciously.] ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: chromium-browser 36.0.1985.125-0ubuntu1.14.04.0~pkg1029 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: Unity Date: Wed Aug 20 17:23:39 2014 Desktop-Session: DESKTOP_SESSION = ubuntu XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg XDG_DATA_DIRS = /usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/ Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None InstallationDate: Installed on 2013-03-10 (527 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) SourcePackage: chromium-browser UpgradeStatus: Upgraded to trusty on 2014-04-22 (120 days ago) gconf-keys: /desktop/gnome/applications/browser/exec = b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/http/enabled = b'true\n'/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n' modified.conffile..etc.default.chromium.browser: [deleted] mtime.conffile..etc.chromium.browser.default: 2014-04-23T00:11:40.712095 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1359265/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1391348] Re: [Errno 101] download chrome via china gfw
This is probably either a network connectivity issue or related to censorship / nation-wide firewall in china, as you mention. So you'd need to fix your internet connection or ask your government to allow access to the google chrome download (not sure if there's a place where you can ask for great firewall exceptions or if that'd be dangerous / illegal). There's nothing that can be fixed in the package, as far as I can tell. -- 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/1391348 Title: [Errno 101] download chrome via china gfw Status in “chromium-browser” package in Ubuntu: New Bug description: this might not be a true bug. i now cannot install flash for ubuntu1204 because of gfw. how can i get help??? shell@ubuntu:~$ shell@ubuntu:~$ sudo apt-get install pepflashplugin-installer Reading package lists... Done Building dependency tree Reading state information... Done Suggested packages: x-ttcidfont-conf ttf-mscorefonts-installer ttf-bitstream-vera ttf-dejavu ttf-xfree86-nonfree xfs The following NEW packages will be installed: pepflashplugin-installer 0 upgraded, 1 newly installed, 0 to remove and 24 not upgraded. Need to get 0 B/6,370 B of archives. After this operation, 56.3 kB of additional disk space will be used. Preconfiguring packages ... Selecting previously unselected package pepflashplugin-installer. (Reading database ... 140769 files and directories currently installed.) Unpacking pepflashplugin-installer (from .../pepflashplugin-installer_15.0.0.189~cr38.0.2125.111-1-0skunk0_amd64.deb) ... Processing triggers for update-notifier-common ... pepflashplugin-installer: downloading https://dl-ssl.google.com/linux/chrome/deb/pool/main/g/google-chrome-stable/google-chrome-stable_38.0.2125.111-1_amd64.deb Traceback (most recent call last): File /usr/lib/update-notifier/package-data-downloader, line 234, in process_download_requests dest_file = urllib.urlretrieve(files[i])[0] File /usr/lib/python2.7/urllib.py, line 93, in urlretrieve return _urlopener.retrieve(url, filename, reporthook, data) File /usr/lib/python2.7/urllib.py, line 239, in retrieve fp = self.open(url, data) File /usr/lib/python2.7/urllib.py, line 207, in open return getattr(self, name)(url) File /usr/lib/python2.7/urllib.py, line 436, in open_https h.endheaders(data) File /usr/lib/python2.7/httplib.py, line 954, in endheaders self._send_output(message_body) File /usr/lib/python2.7/httplib.py, line 814, in _send_output self.send(msg) File /usr/lib/python2.7/httplib.py, line 776, in send self.connect() File /usr/lib/python2.7/httplib.py, line 1157, in connect self.timeout, self.source_address) File /usr/lib/python2.7/socket.py, line 571, in create_connection raise err IOError: [Errno socket error] [Errno 101] Network is unreachable Setting up pepflashplugin-installer (15.0.0.189~cr38.0.2125.111-1-0skunk0) ... shell@ubuntu:~$ shell@ubuntu:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1391348/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1386455] Re: Chromium 37 has 159 known security issues
** Changed in: chromium-browser (Ubuntu) Status: Confirmed = Fix Released -- 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/1386455 Title: Chromium 37 has 159 known security issues Status in “chromium-browser” package in Ubuntu: Fix Released Bug description: Chromium 38 (released 3 weeks ago) fixes at least $52k worth of security issues: http://googlechromereleases.blogspot.de/2014/10/stable-channel-update.html So 159 chromium security fixes (with 113 relatively minor) are waiting for a MOTU to be packaged in Ubuntu. Thanks to anyone taking care of that, and special thanks to Chad Miller for having done so repeatedly. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: chromium-browser 37.0.2062.120-0ubuntu0.14.04.1~pkg1049 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Tue Oct 28 00:09:44 2014 InstallationDate: Installed on 2013-03-10 (596 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) SourcePackage: chromium-browser UpgradeStatus: Upgraded to trusty on 2014-04-22 (188 days ago) modified.conffile..etc.default.chromium.browser: [deleted] mtime.conffile..etc.chromium.browser.default: 2014-04-23T00:11:40.712095 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1386455/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1359265] Re: Characters mixing up in address bar
Someone recently confirmed this, but I haven't experienced the bug in recent weeks. Possibly since updating to 37? Does this still affect anyone? If not, I'll close the bug in a few days. -- 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/1359265 Title: Characters mixing up in address bar Status in “chromium-browser” package in Ubuntu: Confirmed Bug description: I hope this wasn't reported already, but couldn't find any recent reports. This is a relatively new bug, I don't think it was in v34. I often move the cursor to the address bar using F6 and instantly start typing my URL / search term afterwards. F6 leads to a quite noticable freeze while the suggestions box (or whatever that box below the bar is called) loads, at least on my aging ~5 years old system. Same issue when opening a new tab and starting to type, the suggestions take a while to load so chromium freezes for some time. That's not a big issue, but any characters I type during the freeze may come up in wrong order once chromium unfreezes. Sometimes they are ordered correctly, but quite often some of the letters are swapped. So it's not just in rare circumstances, but the freeze is not that easily reproducible because it seems to happen only when the bar wasn't used for some time. When there's no (or only a very short) freeze, there's no bug. At first I thought that my typing skills have suffered a lot because I was googling for slightly wrong terms all the time, but then noticed that chromium (or something that handles input and passes it to chromium?) is to blame, not me. [Or maybe I really hit the keys in a wrong order all the time while thinking that it is correct, but that seems unlikely, since I usually fix those finger syncing typos unconsciously.] ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: chromium-browser 36.0.1985.125-0ubuntu1.14.04.0~pkg1029 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: Unity Date: Wed Aug 20 17:23:39 2014 Desktop-Session: DESKTOP_SESSION = ubuntu XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg XDG_DATA_DIRS = /usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/ Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None InstallationDate: Installed on 2013-03-10 (527 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) SourcePackage: chromium-browser UpgradeStatus: Upgraded to trusty on 2014-04-22 (120 days ago) gconf-keys: /desktop/gnome/applications/browser/exec = b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/http/enabled = b'true\n'/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n' modified.conffile..etc.default.chromium.browser: [deleted] mtime.conffile..etc.chromium.browser.default: 2014-04-23T00:11:40.712095 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1359265/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1386455] [NEW] Chromium 37 has 159 known security issues
*** This bug is a security vulnerability *** Public security bug reported: Chromium 38 (released 3 weeks ago) fixes at least $52k worth of security issues: http://googlechromereleases.blogspot.de/2014/10/stable-channel-update.html So 159 chromium security fixes (with 113 relatively minor) are waiting for a MOTU to be packaged in Ubuntu. Thanks to anyone taking care of that, and special thanks to Chad Miller for having done so repeatedly. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: chromium-browser 37.0.2062.120-0ubuntu0.14.04.1~pkg1049 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Tue Oct 28 00:09:44 2014 InstallationDate: Installed on 2013-03-10 (596 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) SourcePackage: chromium-browser UpgradeStatus: Upgraded to trusty on 2014-04-22 (188 days ago) modified.conffile..etc.default.chromium.browser: [deleted] mtime.conffile..etc.chromium.browser.default: 2014-04-23T00:11:40.712095 ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Information type changed from Private Security to Public Security ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2014-3188 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2014-3189 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2014-3190 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2014-3191 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2014-3192 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2014-3193 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2014-3194 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2014-3195 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2014-3196 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2014-3197 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2014-3198 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2014-3199 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2014-3200 -- 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/1386455 Title: Chromium 37 has 159 known security issues Status in “chromium-browser” package in Ubuntu: New Bug description: Chromium 38 (released 3 weeks ago) fixes at least $52k worth of security issues: http://googlechromereleases.blogspot.de/2014/10/stable-channel-update.html So 159 chromium security fixes (with 113 relatively minor) are waiting for a MOTU to be packaged in Ubuntu. Thanks to anyone taking care of that, and special thanks to Chad Miller for having done so repeatedly. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: chromium-browser 37.0.2062.120-0ubuntu0.14.04.1~pkg1049 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Tue Oct 28 00:09:44 2014 InstallationDate: Installed on 2013-03-10 (596 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) SourcePackage: chromium-browser UpgradeStatus: Upgraded to trusty on 2014-04-22 (188 days ago) modified.conffile..etc.default.chromium.browser: [deleted] mtime.conffile..etc.chromium.browser.default: 2014-04-23T00:11:40.712095 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1386455/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1360505] Re: Security fixes from 36.0.1985.143 and 37.0.2062.94
This is fixed, right? I just got updated to 37 through update-manager. Thanks a lot, Chad :-) I'm not closing it because it's not my bug, but I guess it can be closed. -- 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/1360505 Title: Security fixes from 36.0.1985.143 and 37.0.2062.94 Status in “chromium-browser” package in Ubuntu: Confirmed Bug description: Security fixes from 37.0.2062.94 and earlier (some of them were classified as Critical severity by the Chromium development team, i.e. can lead to remote code execution outside of the sandbox) should be either backported to the respective Chromium versions in all current desktop-supported releases of Ubuntu, or the repositories should be updated to include the new version of Chromium. Information on the new releases can be found at: http://googlechromereleases.blogspot.de/2014/08/stable-channel-update.html http://googlechromereleases.blogspot.de/2014/08/stable-channel-update_26.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1360505/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1360026] Re: Libav11 for Utopic
So in Debian, all the packages in testing are now built against libav11 AFAICT. I (as a user) hope we can still get libav11 for Utopic. In case this helps with your decision, these are the packages in sid which are not built against libav11 (yet?): - bino (unrelated to libav, some gettext related version mismatch) - gnash (probably unrelated, FTBFS on armel because armel has std::future issues, and FTBFS on mips for whatever reason) - gstreamer0.10-ffmpeg (FTBFS since libav9) - jitsi (unrelated, complains about invalid -d command line option for apt … ?!) - mrpt (there was no attempt to build against libav11 for any main arch yet, since there seem to be unrelated build issues on some arches. Building on alpha architecture at ports.debian.org against libav11 succeeded recently.) - taoframework (language bindings that need updating for libav9+. Upstream probably cared about ffmpeg only and is dead now anyway.) - visp (probably unrelated, test suite failure on powerpc) - zoneminder (FTBFS since libav10 at least, still using CODEC_ID_*) I'm not sure if Ubuntu carries any additional packages that would fail to build against libav11. Also not sure about the current Ubuntu state of the packages I mentioned. Maybe some of them need to be dropped from the archive. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libav in Ubuntu. https://bugs.launchpad.net/bugs/1360026 Title: Libav11 for Utopic Status in “libav” package in Ubuntu: Confirmed Status in “libav” package in Debian: Fix Committed Bug description: This ticket is to track the Libav11 transition in Utopic. See the discussion on the Mailing list on https://lists.ubuntu.com/archives/ubuntu-devel/2014-August/038435.html The transition is being staged in https://launchpad.net/~motumedia/+archive/ubuntu/libav11/+packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1360026/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1360026] Re: Libav11 for Utopic
To clarify: - So in Debian, all the packages in testing are now built against libav11 AFAICT. I actually meant: The packages that are both in sid and in testing were successfully rebuilt against libav11. However, they are still in sid and waiting to migrate. :-) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libav in Ubuntu. https://bugs.launchpad.net/bugs/1360026 Title: Libav11 for Utopic Status in “libav” package in Ubuntu: Confirmed Status in “libav” package in Debian: Fix Committed Bug description: This ticket is to track the Libav11 transition in Utopic. See the discussion on the Mailing list on https://lists.ubuntu.com/archives/ubuntu-devel/2014-August/038435.html The transition is being staged in https://launchpad.net/~motumedia/+archive/ubuntu/libav11/+packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1360026/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1359615] Re: [precise] critical: flash stopped working after last update
Chromium is not in main, i.e. it's officially unsupported by Canonical. Formally, only approved Ubuntu community members (MOTUs) support chromium in Ubuntu, while Canonical does not guarantee any support at all. That's the formal aspect at least. In practice, it seems like a Canonical employee, Chad Miller, thankfully does most (all?) of the Chromium work. It's a pretty important package after all, but as you can tell from the not quite optimal security support (still 50+ open security vulnerabilities right now and generally lagging a few weeks or months behind with security fixes), it's on a best-effort basis. Maybe Chad does the work in his free time, or it's just a low priority work task for him. So don't expect an official statement from an Ubuntu representative because formally, Chromium is not a part of Ubuntu that Canonical cares about. Use Firefox which is in main and the default browser if you want Canonical support (or maybe if you can pay some signficant amount of money, Canonical would offer to support Chromium for you). It is important to note that shipping Chromium in a distro is very difficult. Google seems to care about their own packaging, and that's it. It's not an easy upstream to work with. It has bundled source copies of libraries, until some time ago not even official release tarballs, it's a very fast moving target and there is no backwards compatibility for anything. -- 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/1359615 Title: [precise] critical: flash stopped working after last update Status in “chromium-browser” package in Ubuntu: New Bug description: Ubuntu released new version of chromium-browser (36.0.1985.125-0ubuntu1.12.04.0~pkg897) for LTS 12.04 precise relase. After updating chromium-browser from previous version (34.0.1847.116-0ubuntu~1.12.04.0~pkg884) flash plugin stopped working. Flash plugin is properly installed but it chromium does not see it and show message that is not installed. Firefox has no problem and can load flash object. I suspect that this is because of dropping NPAPI support in chrome 36. But ubuntu does not have pepper flash in repositories so it is not possible to use flash on 12.04 anymore. So this is critical problem because one month ago everything worked fine and new *broken* version of chromium-browser is in precise- security/universe archive. I suggest to revert chromium back to *working* version or do something else -- because new *security* update totally broke flash support on 12.04 LTS release. Once again 12.04 is LTS release where is expected that updates marked as security will *not* break existing application support -- this is not *experimental* update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1359615/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1353185] Re: Chromium 36 upgrade will not execute
Michael Gilbert of Debian apparently carries some patches for chromium that supposedly get rid of SSE2 instructions in the Debian chromium package (at least in experimental?). User opera posted a link to the corresponding bug report in Debian. I'm not sure what the status of this is or if Ubuntu would be willing to use the same patches, as they seem pretty untested and impact/maintenance burden for future chromium releases is not clear. I wouldn't recommend using Chromium 34, as each of 35, 36 and 37 has a lot of security fixes that are not in 34. So that would be somewhat dangerous. I also don't know about an easy way to revert to 34, as most PPAs or other repositories are probably updated by now. Maybe you can find the old deb files somewhere. Consider using a different browser :/ -- 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/1353185 Title: Chromium 36 upgrade will not execute Status in “chromium-browser” package in Ubuntu: Incomplete Bug description: Chromium will no longer start after version 36 upgrade. Previous version worked ok. Execution from command line reports Illegal instruction (core dumped). Nothing displayed on screen. lshw reports: description: Tower Computer version: System Version width: 32 bits capabilities: smbios-2.3 dmi-2.3 configuration: boot=normal chassis=tower *-core description: Motherboard product: A7V8X vendor: ASUSTeK Computer INC. *-firmware description: BIOS vendor: Award Software, Inc. physical id: 0 version: ASUS A7V8X ACPI BIOS Revision 1010 *-cpu description: CPU product: AMD Athlon(TM) XP 2400+ vendor: Hynix Semiconductor (Hyundai Electronics) *-memory description: System Memory slot: System board or motherboard size: 1GiB ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: chromium-browser 36.0.1985.125-0ubuntu1.12.04.0~pkg897 ProcVersionSignature: Ubuntu 3.2.0-67.101-generic 3.2.60 Uname: Linux 3.2.0-67-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.6 Architecture: i386 Date: Tue Aug 5 19:35:30 2014 Desktop-Session: DESKTOP_SESSION = ubuntu-2d XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu-2d:/etc/xdg XDG_DATA_DIRS = /usr/share/ubuntu-2d:/usr/share/gnome:/usr/local/share/:/usr/share/ DmesgChromium: [ 28.356536] type=1400 audit(1407283433.748:15): apparmor=STATUS operation=profile_load name=/usr/lib/lightdm/lightdm/lightdm-guest-session-wrapper//chromium_browser pid=853 comm=apparmor_parser Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: chromium-browser UpgradeStatus: Upgraded to precise on 2012-09-15 (689 days ago) chromium-default: CHROMIUM_FLAGS= modified.conffile..etc.default.chromium.browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1353185/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1359615] Re: [precise] critical: flash stopped working after last update
Well, I didn't push the update. I'm just a user. But if Ubuntu didn't push newer chromium releases to stable, there'd be a ton of security flaws by the time even the next STS Ubuntu release is published 6 months later. And that would basically mean that any user who cares at least a little bit for the security of his operating system would be unlikely to use the Ubuntu chromium. I'd actually switch to Arch Linux completely in that case, since I don't want the Chrome compiled by Google and trying to find up to date PPAs or compiling myself appears to be more work than just fixing the occasional Arch breakage. The only sane thing any responsible distribution can do about chromium is to either NOT package it at all (this is what Fedora does), or ship the latest stable chromium at all times. If they just ship whatever was the latest chromium at the time of distro release, their users would be at risk and most users wouldn't even realize how dangerous it is to use the distro packaged browser. So yeah, this is a very difficult situation and I agree it's unfortunate that plugins have stopped working. However, this is not an experiment, it's a required security update. Just shipping chrome 34 without the fixes would be irresponsible and unprofessional, it's almost like still using Windows XP today. If you really want 34 back, I'd recommend you to start backporting all the security fixes from 35, 36 and 37 to version 34. Maybe Ubuntu would be willing to ship your 34 + backported fixes. Better ask them first. If you can't do that, you could pay someone to do it, but that will be pretty expensive I guess seeing how there are ~50-100 issues in chromium 34 to be fixed. :) -- 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/1359615 Title: [precise] critical: flash stopped working after last update Status in “chromium-browser” package in Ubuntu: New Bug description: Ubuntu released new version of chromium-browser (36.0.1985.125-0ubuntu1.12.04.0~pkg897) for LTS 12.04 precise relase. After updating chromium-browser from previous version (34.0.1847.116-0ubuntu~1.12.04.0~pkg884) flash plugin stopped working. Flash plugin is properly installed but it chromium does not see it and show message that is not installed. Firefox has no problem and can load flash object. I suspect that this is because of dropping NPAPI support in chrome 36. But ubuntu does not have pepper flash in repositories so it is not possible to use flash on 12.04 anymore. So this is critical problem because one month ago everything worked fine and new *broken* version of chromium-browser is in precise- security/universe archive. I suggest to revert chromium back to *working* version or do something else -- because new *security* update totally broke flash support on 12.04 LTS release. Once again 12.04 is LTS release where is expected that updates marked as security will *not* break existing application support -- this is not *experimental* update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1359615/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1343081] Re: chromium: missing http:// in URL bar on non-ssl http URLs
I'll repeat it again: What you are describing works for me, and it works for Saikrishna. 1) Go to http://www.spiegel.de 2) Observe the location bar shows just www.spiegel.de 3) Copy that text by starting to click somewhere to the right of www.spiegel.de, then move the cursor to the left until all of www.spiegel.de is selected, then release the mouse button – Note: 3) does not work when just selecting the URL by clicking the location bar, which selects all the text as well but leaves the clipboard contents unchanged – 4) Use xsel -o or xclip -o 5) Observe that both commands correctly print the URL including the http:// scheme part, http://www.spiegel.de; So either my system contains a magical fix for this issue, maybe because I'm on Unity and you are on something else (though I can't imagine how the desktop environment would influence the X clipboard, but I don't really know much about that stuff), or you are doing it in a different way. BTW I'm on chromium 36 by now, perhaps you're still on 34? I think I haven't tested this on 34. -- 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/1343081 Title: chromium: missing http://; in URL bar on non-ssl http URLs Status in “chromium-browser” package in Ubuntu: Incomplete Bug description: Version 34.0.1847.116 Ubuntu 14.04 aura (260972) On http URLs (non-ssl), the url bar misses the http://; prefix. This is especially ugly when copying URLs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1343081/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1353185] Re: Chromium 36 upgrade will not execute
Frederick, there was no chromium 35 in Ubuntu if I remember correctly, so you are probably talking about Chromium 34 (that was the current version in Ubuntu until a few weeks ago when it was upgraded to 36). Chromium 35 has stopped supporting non-SSE2 Linux systems because, according to Google, there are exactly 0 Linux users without SSE2. I'm sorry, you don't exist. See the chrome bugtracker link above: The good news is that for Linux (as opposed to for Windows), there are zero pre-SSE2 users out there, so bumping the minimum requirement from P3 to P4 [..] Also, AMD processors apparently do not exist in the Google universe, so now we have Pentium 4 as the minimum CPU requirement. :-) -- 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/1353185 Title: Chromium 36 upgrade will not execute Status in “chromium-browser” package in Ubuntu: Incomplete Bug description: Chromium will no longer start after version 36 upgrade. Previous version worked ok. Execution from command line reports Illegal instruction (core dumped). Nothing displayed on screen. lshw reports: description: Tower Computer version: System Version width: 32 bits capabilities: smbios-2.3 dmi-2.3 configuration: boot=normal chassis=tower *-core description: Motherboard product: A7V8X vendor: ASUSTeK Computer INC. *-firmware description: BIOS vendor: Award Software, Inc. physical id: 0 version: ASUS A7V8X ACPI BIOS Revision 1010 *-cpu description: CPU product: AMD Athlon(TM) XP 2400+ vendor: Hynix Semiconductor (Hyundai Electronics) *-memory description: System Memory slot: System board or motherboard size: 1GiB ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: chromium-browser 36.0.1985.125-0ubuntu1.12.04.0~pkg897 ProcVersionSignature: Ubuntu 3.2.0-67.101-generic 3.2.60 Uname: Linux 3.2.0-67-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.6 Architecture: i386 Date: Tue Aug 5 19:35:30 2014 Desktop-Session: DESKTOP_SESSION = ubuntu-2d XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu-2d:/etc/xdg XDG_DATA_DIRS = /usr/share/ubuntu-2d:/usr/share/gnome:/usr/local/share/:/usr/share/ DmesgChromium: [ 28.356536] type=1400 audit(1407283433.748:15): apparmor=STATUS operation=profile_load name=/usr/lib/lightdm/lightdm/lightdm-guest-session-wrapper//chromium_browser pid=853 comm=apparmor_parser Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: chromium-browser UpgradeStatus: Upgraded to precise on 2012-09-15 (689 days ago) chromium-default: CHROMIUM_FLAGS= modified.conffile..etc.default.chromium.browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1353185/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1360505] Re: Security fixes from 36.0.1985.143
37.0.2062.94 has 50 more security fixes: http://googlechromereleases.blogspot.de/2014/08/stable-channel- update_26.html CVE-2014-3176, CVE-2014-3177 (critical, sandbox breakage) CVE-2014-3168 CVE-2014-3169 CVE-2014-3170 CVE-2014-3171 CVE-2014-3172 CVE-2014-3173 CVE-2014-3174 CVE-2014-3175 (various fixes) ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2014-3168 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2014-3169 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2014-3170 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2014-3171 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2014-3172 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2014-3173 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2014-3174 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2014-3175 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2014-3176 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2014-3177 -- 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/1360505 Title: Security fixes from 36.0.1985.143 Status in “chromium-browser” package in Ubuntu: New Bug description: Security fixes from 36.0.1985.143 (some of them were classified as High severity by the Chromium development team) should be either backported to the respective Chromium versions in all current desktop- supported releases of Ubuntu, or the repositories should be updated to include the new version of Chromium. Information on the new release can be found at: http://googlechromereleases.blogspot.de/2014/08/stable-channel- update.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1360505/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1359615] Re: [precise] critical: flash stopped working after last update
There is no way (or at least no way that does not involve forking chromium and quite a lot of coding work) to get chromium to work with Adobe Flash and have no security issues at the same time. Ubuntu decided to prefer breaking flash over having precise users exposed to a growing number of threats. This is simply because chromium no longer supports NPAPI on Linux as you have mentioned, but old chromium versions are a security hell. You have four options: 1) Use e.g. firefox + NPAPI Adobe Flash for your flash viewing pleasure. 2) Install Google Chrome (instead of chromium) that comes with bundled pepperflash. 3) Install pepperflash separatly (sudo apt-get install pepperflashplugin-nonfree) and use it with chromium. Please note that pepperflash DOES NOT AUTO UPDATE, even though it has critical security updates regularly. Use sudo update-pepperflashplugin-nonfree --status to see if there is an update available, and sudo update-pepperflashplugin-nonfree --install to install the update. 4) Don't use flash. Obviously that's not always an option, but some sites like youtube have HTML5 alternatives ready to be enabled. This is not a bug, it's the intended deprecation of an old plugin API. ** Changed in: chromium-browser (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1359615 Title: [precise] critical: flash stopped working after last update Status in “chromium-browser” package in Ubuntu: Invalid Bug description: Ubuntu released new version of chromium-browser (36.0.1985.125-0ubuntu1.12.04.0~pkg897) for LTS 12.04 precise relase. After updating chromium-browser from previous version (34.0.1847.116-0ubuntu~1.12.04.0~pkg884) flash plugin stopped working. Flash plugin is properly installed but it chromium does not see it and show message that is not installed. Firefox has no problem and can load flash object. I suspect that this is because of dropping NPAPI support in chrome 36. But ubuntu does not have pepper flash in repositories so it is not possible to use flash on 12.04 anymore. So this is critical problem because one month ago everything worked fine and new *broken* version of chromium-browser is in precise- security/universe archive. I suggest to revert chromium back to *working* version or do something else -- because new *security* update totally broke flash support on 12.04 LTS release. Once again 12.04 is LTS release where is expected that updates marked as security will *not* break existing application support -- this is not *experimental* update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1359615/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1359615] Re: [precise] critical: flash stopped working after last update
I'm sorry, you don't have option 3). Only after upgrading to Trusty. Pepperflash is not available in Precise. -- 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/1359615 Title: [precise] critical: flash stopped working after last update Status in “chromium-browser” package in Ubuntu: Invalid Bug description: Ubuntu released new version of chromium-browser (36.0.1985.125-0ubuntu1.12.04.0~pkg897) for LTS 12.04 precise relase. After updating chromium-browser from previous version (34.0.1847.116-0ubuntu~1.12.04.0~pkg884) flash plugin stopped working. Flash plugin is properly installed but it chromium does not see it and show message that is not installed. Firefox has no problem and can load flash object. I suspect that this is because of dropping NPAPI support in chrome 36. But ubuntu does not have pepper flash in repositories so it is not possible to use flash on 12.04 anymore. So this is critical problem because one month ago everything worked fine and new *broken* version of chromium-browser is in precise- security/universe archive. I suggest to revert chromium back to *working* version or do something else -- because new *security* update totally broke flash support on 12.04 LTS release. Once again 12.04 is LTS release where is expected that updates marked as security will *not* break existing application support -- this is not *experimental* update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1359615/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1360505] Re: Security fixes from 36.0.1985.143 and 37.0.2062.94
** Summary changed: - Security fixes from 36.0.1985.143 + Security fixes from 36.0.1985.143 and 37.0.2062.94 -- 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/1360505 Title: Security fixes from 36.0.1985.143 and 37.0.2062.94 Status in “chromium-browser” package in Ubuntu: Confirmed Bug description: Security fixes from 36.0.1985.143 (some of them were classified as High severity by the Chromium development team) should be either backported to the respective Chromium versions in all current desktop- supported releases of Ubuntu, or the repositories should be updated to include the new version of Chromium. Information on the new release can be found at: http://googlechromereleases.blogspot.de/2014/08/stable-channel- update.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1360505/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1343081] Re: chromium: missing http:// in URL bar on non-ssl http URLs
The http:// is prepended when using either the select text - middle click clipboard or the ctrl-c/ctrl-v clipboard. At least for me. So I'd say this is not a bug, unless the reporter confirms there is some way to copy/paste the almost complete URL without http://. In fact, this new feature only removes the ability to copy only part of a URL starting from (e.g.) www., like the hostname part, because http:// appears to be always included when copying at least the host name. -- 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/1343081 Title: chromium: missing http://; in URL bar on non-ssl http URLs Status in “chromium-browser” package in Ubuntu: Confirmed Bug description: Version 34.0.1847.116 Ubuntu 14.04 aura (260972) On http URLs (non-ssl), the url bar misses the http://; prefix. This is especially ugly when copying URLs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1343081/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1359265] [NEW] Characters mixing up in address bar
Public bug reported: I hope this wasn't reported already, but couldn't find any recent reports. This is a relatively new bug, I don't think it was in v34. I often move the cursor to the address bar using F6 and instantly start typing my URL / search term afterwards. F6 leads to a quite noticable freeze while the suggestions box (or whatever that box below the bar is called) loads, at least on my aging ~5 years old system. Same issue when opening a new tab and starting to type, the suggestions take a while to load so chromium freezes for some time. That's not a big issue, but any characters I type during the freeze may come up in wrong order once chromium unfreezes. Sometimes they are ordered correctly, but quite often some of the letters are swapped. So it's not just in rare circumstances, but the freeze is not that easily reproducible because it seems to happen only when the bar wasn't used for some time. When there's no (or only a very short) freeze, there's no bug. At first I thought that my typing skills have suffered a lot because I was googling for slightly wrong terms all the time, but then noticed that chromium (or something that handles input and passes it to chromium?) is to blame, not me. [Or maybe I really hit the keys in a wrong order all the time while thinking that it is correct, but that seems unlikely, since I usually fix those finger syncing typos unconsciously.] ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: chromium-browser 36.0.1985.125-0ubuntu1.14.04.0~pkg1029 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: Unity Date: Wed Aug 20 17:23:39 2014 Desktop-Session: DESKTOP_SESSION = ubuntu XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg XDG_DATA_DIRS = /usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/ Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None InstallationDate: Installed on 2013-03-10 (527 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) SourcePackage: chromium-browser UpgradeStatus: Upgraded to trusty on 2014-04-22 (120 days ago) gconf-keys: /desktop/gnome/applications/browser/exec = b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/http/enabled = b'true\n'/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n' modified.conffile..etc.default.chromium.browser: [deleted] mtime.conffile..etc.chromium.browser.default: 2014-04-23T00:11:40.712095 ** Affects: chromium-browser (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 chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1359265 Title: Characters mixing up in address bar Status in “chromium-browser” package in Ubuntu: New Bug description: I hope this wasn't reported already, but couldn't find any recent reports. This is a relatively new bug, I don't think it was in v34. I often move the cursor to the address bar using F6 and instantly start typing my URL / search term afterwards. F6 leads to a quite noticable freeze while the suggestions box (or whatever that box below the bar is called) loads, at least on my aging ~5 years old system. Same issue when opening a new tab and starting to type, the suggestions take a while to load so chromium freezes for some time. That's not a big issue, but any characters I type during the freeze may come up in wrong order once chromium unfreezes. Sometimes they are ordered correctly, but quite often some of the letters are swapped. So it's not just in rare circumstances, but the freeze is not that easily reproducible because it seems to happen only when the bar wasn't used for some time. When there's no (or only a very short) freeze, there's no bug. At first I thought that my typing skills have suffered a lot because I was googling for slightly wrong terms all the time, but then noticed that chromium (or something that handles input and passes it to chromium?) is to blame, not me. [Or maybe I really hit the keys in a wrong order all the time while thinking that it is correct, but that seems unlikely, since I usually fix those finger syncing typos unconsciously.] ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: chromium-browser 36.0.1985.125-0ubuntu1.14.04.0~pkg1029 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 ApportVersion:
[Desktop-packages] [Bug 1331375] Re: Update Chromium to = 36.0.1985.125 (including security fixes)
FYI, stable Chromium 36.0.1985.125 is now out for Linux, containing 26 security fixes for two more CVEs. ** Summary changed: - Update Chromium to = 35.0.1916.153 (including security fixes) + Update Chromium to = 36.0.1985.125 (including security fixes) ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2014-3160 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2014-3162 -- 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/1331375 Title: Update Chromium to = 36.0.1985.125 (including security fixes) Status in “chromium-browser” package in Ubuntu: Confirmed Bug description: Updating fixes security bugs, see the linked CVEs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1331375/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1331375] Re: Update Chromium to = 35.0.1916.153 (including security fixes)
Are there any issues preventing chromium from being updated to a version without known security vulnerabilities? Even debian has v35 in stable- security since June 15, and Arch Linux (unsurprisingly) since June 11, and the vulnerabilites are public since June 10. Since most other distributions (ignoring Fedora, which probably handles chromium in the sanest way…) have switched to v35 two weeks ago, the problems with the new version can't be that bad I guess. At least better than browsing with 4 CVEs. Or is this repeated chromium update delay due to a lack of manpower? In that case, is there any reason not to use and contribute to the debian packaging work directly? -- 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/1331375 Title: Update Chromium to = 35.0.1916.153 (including security fixes) Status in “chromium-browser” package in Ubuntu: Confirmed Bug description: Updating fixes security bugs, see the linked CVEs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1331375/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1035701] Re: grilo plugins should be enabled in Totem
Thanks Doug for your extensive plugin review. Maybe we should continue this in a new grilo-plugins bug (I noticed we can report bugs at https://bugs.launchpad.net/ubuntu/+source/grilo-plugins , is that a bad idea?). One of them might be an actual totem bug though: jamendo works in rhythmbox (at least on 14.04). Though I noticed there is at least 1 empty folder called Westing*House, not sure if that is a bug (related to the non-alphanumeric character?) or if it's simply served empty by jamendo. The other folders I tested work and I can listen to the contained media. I agree that screen-scraping youtube is probably a bad idea, if that's how the youtube plugin works. I'm not opposed to disabling most of the apparently(?) under-maintained plugins after testing them in the special grilo browse test tool. Most of the content can easily be retrieved using a web browser. While it'd be nice to search and watch youtube through totem, it's almost impossible to listen to/watch DLNA shared media without a proper client. VLC has a strange fetch all media from the media share before doing anything implementation leading to a few minutes wait time before I can listen to my music, XBMC is not what I'm looking for, and the other clients I know need grilo. While this bug and the rhythmbox bug have few affects me too clicks, that's probably because the average user has no idea what grilo is, they just want DLNA and from a quick google search, there's almost no DLNA support in Ubuntu, so… :-) [Sorry for evangelizing all the time BTW. I'm a big fan of UPnP, but I realize this might be annoying so I'll stop now.] -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1035701 Title: grilo plugins should be enabled in Totem Status in One Hundred Papercuts: Triaged Status in “totem” package in Ubuntu: Triaged Bug description: I see no good reason why they're not. For the most part they all work, any that don't are a grilo bug, (like vimeo), shouldn't affect being enabled. If sticking with 3.4.3/gstreamer .10/grilo 0.1 (0.1.2 is available) it would seem straightforward to enable have installed (inc. it in totem-plugins here in a test rebuild If moving to totem 3.4.4+/gstreamer1.0/grilo 0.2 then have tested that here, works ok though ATM not as good as 0.1 , though again any grilo issies are grilo bugs ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: totem 3.4.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-9.9-generic 3.5.0 Uname: Linux 3.5.0-9-generic x86_64 ApportVersion: 2.4-0ubuntu6 Architecture: amd64 Date: Sat Aug 11 14:32:15 2012 InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120707) ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1035701/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 973295] Re: Enable grilo plugin
Thanks Timo, it's really nice to see some DLNA love in Ubuntu. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/973295 Title: Enable grilo plugin Status in “rhythmbox” package in Ubuntu: Triaged Bug description: At the moment grilo plugin is not being built thus leaving Jamendo and UPnP out of rhythmbox. This is only a packaging issue and can be easily fixed: debian/control: - Add libgrilo-0.1-dev to Build-Depends - Add gir1.2-grilo-0.1 to Depends on rhythmbox-plugins (or create a new package) debian/rhythmbox-plugins.install (or specific to a new package) - Add usr/lib/rhythmbox/plugins/grilo All grilo packages are now in Universe so this may not be done that easily though. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/973295/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1035701] Re: grilo plugins should be enabled in Totem
Doug: I can't test totem with grilo (I'm on trusty) so I can only speak for rhythmbox with grilo, which works almost perfectly fine (the rhythmbox-grilo plugin itself shows some strange behaviour though). I know that rhythmbox has a blacklist of grilo plugins to ignore so maybe the bad plugins are filtered. * DLNA plugin: I have observed no crashes / misbehaviours * Jamendo plugin: Admittedly I don't use it a lot, but I don't remember it crashing or failing * The Guardian Videos, Radio France, Euronews: These just show no contents. Probably no audio items served through those plugins. I noticed the rhythmbox git version has some changes related to filtering out sources without audio content. Adding a blacklist for every application that uses grilo seems overkill. So… The DLNA plugin is probably the most important one for both, rhythmbox and totem. If some of the grilo plugins cause problems, maybe the -plugins package should be split (grilo-plugins-bad / -ugly / -whatever) or broken plugins simply removed from the package. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1035701 Title: grilo plugins should be enabled in Totem Status in One Hundred Papercuts: Triaged Status in “totem” package in Ubuntu: Triaged Bug description: I see no good reason why they're not. For the most part they all work, any that don't are a grilo bug, (like vimeo), shouldn't affect being enabled. If sticking with 3.4.3/gstreamer .10/grilo 0.1 (0.1.2 is available) it would seem straightforward to enable have installed (inc. it in totem-plugins here in a test rebuild If moving to totem 3.4.4+/gstreamer1.0/grilo 0.2 then have tested that here, works ok though ATM not as good as 0.1 , though again any grilo issies are grilo bugs ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: totem 3.4.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-9.9-generic 3.5.0 Uname: Linux 3.5.0-9-generic x86_64 ApportVersion: 2.4-0ubuntu6 Architecture: amd64 Date: Sat Aug 11 14:32:15 2012 InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120707) ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1035701/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1035701] Re: grilo plugins should be enabled in Totem
I tried to make exactly that point: grilo works fine with rhythmbox (on trusty, and ignoring a UI issue with expanding an item in the tree view that has no child containers). If totem segfaults, that must be either due to bad grilo integration or totem uses some grilo plugins that are not used by rhythmbox and those segfault. In the first case, someone should fix totem or totem can't use grilo. In the second case, those plugins should be identified and fixed/removed. In any case, throwing grilo out of [all?] major music players like Ubuntu used to do is a bad idea IMHO. I've read numerous complaints about missing DLNA functionality in Ubuntu. Even getting rid of every grilo plugin other than DLNA and just using that in rhythmbox is an improvement over Trusty, where grilo exists in Universe but no[?] common music player supports it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1035701 Title: grilo plugins should be enabled in Totem Status in One Hundred Papercuts: Triaged Status in “totem” package in Ubuntu: Triaged Bug description: I see no good reason why they're not. For the most part they all work, any that don't are a grilo bug, (like vimeo), shouldn't affect being enabled. If sticking with 3.4.3/gstreamer .10/grilo 0.1 (0.1.2 is available) it would seem straightforward to enable have installed (inc. it in totem-plugins here in a test rebuild If moving to totem 3.4.4+/gstreamer1.0/grilo 0.2 then have tested that here, works ok though ATM not as good as 0.1 , though again any grilo issies are grilo bugs ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: totem 3.4.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-9.9-generic 3.5.0 Uname: Linux 3.5.0-9-generic x86_64 ApportVersion: 2.4-0ubuntu6 Architecture: amd64 Date: Sat Aug 11 14:32:15 2012 InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120707) ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1035701/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 973295] Re: Enable grilo plugin
You know Ubuntu/Canonical processes much better than I do, so I guess that Wiki page might be wrong/misleading: https://wiki.ubuntu.com/MainInclusionProcess It says The MIR team reviews the reports, and sets acceptable ones to [..] Fix Committed. [..] Add the package to a seed, or as a (build-)dependency of a package in main. [..] The archive administrators will promote approved packages to main if some other package or the seeds want it According to that page I'd assume that someone needs to add a main dependency to grilo somewhere, like for example from rhythmbox, in order for the main inclusion process to continue. Something like the debdiff I posted above. If that is not the case, what else needs to happen? Something the MIR team needs to do? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/973295 Title: Enable grilo plugin Status in “rhythmbox” package in Ubuntu: Triaged Bug description: At the moment grilo plugin is not being built thus leaving Jamendo and UPnP out of rhythmbox. This is only a packaging issue and can be easily fixed: debian/control: - Add libgrilo-0.1-dev to Build-Depends - Add gir1.2-grilo-0.1 to Depends on rhythmbox-plugins (or create a new package) debian/rhythmbox-plugins.install (or specific to a new package) - Add usr/lib/rhythmbox/plugins/grilo All grilo packages are now in Universe so this may not be done that easily though. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/973295/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 973295] Re: Enable grilo plugin
This is the debdiff I use in my PPA to enable grilo in the current trusty package (3.0.2-0ubuntu2). Ordering of dependencies etc. is slightly different in the debian package… I noticed too late that it might be a good idea to reduce the debian-ubuntu diff size instead of increasing it. ** Patch added: Enable grilo in rhythmbox https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/973295/+attachment/4107210/+files/grilo-rb.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/973295 Title: Enable grilo plugin Status in “rhythmbox” package in Ubuntu: Triaged Bug description: At the moment grilo plugin is not being built thus leaving Jamendo and UPnP out of rhythmbox. This is only a packaging issue and can be easily fixed: debian/control: - Add libgrilo-0.1-dev to Build-Depends - Add gir1.2-grilo-0.1 to Depends on rhythmbox-plugins (or create a new package) debian/rhythmbox-plugins.install (or specific to a new package) - Add usr/lib/rhythmbox/plugins/grilo All grilo packages are now in Universe so this may not be done that easily though. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/973295/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1035701] Re: grilo plugins should be enabled in Totem
Since the MIR was approved, if I understand the main inclusion process correctly, someone needs to enable the grilo plugins in totem and rhythmbox and possibly other apps (i.e. add a grilo dependency from main). Maybe this happens in time for Utopic? *crosses fingers for out-of-the- box-DLNA-experience* -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1035701 Title: grilo plugins should be enabled in Totem Status in One Hundred Papercuts: Triaged Status in “totem” package in Ubuntu: Triaged Bug description: I see no good reason why they're not. For the most part they all work, any that don't are a grilo bug, (like vimeo), shouldn't affect being enabled. If sticking with 3.4.3/gstreamer .10/grilo 0.1 (0.1.2 is available) it would seem straightforward to enable have installed (inc. it in totem-plugins here in a test rebuild If moving to totem 3.4.4+/gstreamer1.0/grilo 0.2 then have tested that here, works ok though ATM not as good as 0.1 , though again any grilo issies are grilo bugs ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: totem 3.4.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-9.9-generic 3.5.0 Uname: Linux 3.5.0-9-generic x86_64 ApportVersion: 2.4-0ubuntu6 Architecture: amd64 Date: Sat Aug 11 14:32:15 2012 InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120707) ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1035701/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1132063] Re: Mouse settings missing from Mouse Touchpad dialog
According to Peter Hutterer (Xorg developer), it's impossible to tell if a device is a mouse or not. http://who-t.blogspot.de/2009/06/xi2-recipes-part-3.html (see comments) I guess the best fix in that case is to never hide the mouse settings in gnome-control-center. Or maybe hide only if there is no xinput2 device with XIValuatorClassInfo attached to it, i.e. it would be shown if there is a touchpad but no mouse. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1132063 Title: Mouse settings missing from Mouse Touchpad dialog Status in “gnome-control-center” package in Ubuntu: Confirmed Bug description: On up to date Raring alpha, on System Settings Mouse Touchpad the Mouse settings are completely missing. The General and Touchpad sections are there but none for mouse. See attached screenshot. xinput --list shows ~$ xinput --list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MOSART Semi. 2.4G Keyboard Mouseid=11 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=14 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Sleep Buttonid=9[slave keyboard (3)] ↳ MOSART Semi. 2.4G Keyboard Mouseid=10 [slave keyboard (3)] ↳ Dell Dell USB Keyboard id=12 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=13 [slave keyboard (3)] and from lsusb: Bus 003 Device 002: ID 062a:3286 Creative Labs Nano Receiver [Sandstrom Laser Mouse SMWLL11] ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-control-center 1:3.6.3-0ubuntu13 ProcVersionSignature: Ubuntu 3.8.0-7.15-generic 3.8.0 Uname: Linux 3.8.0-7-generic i686 ApportVersion: 2.8-0ubuntu4 Architecture: i386 Date: Sat Feb 23 09:40:41 2013 InstallationDate: Installed on 2012-08-01 (205 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha i386 (20120730.1) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu6.1 deja-dup25.5-0ubuntu1 gnome-control-center-signon 0.1.2bzr12.12.05-0ubuntu1 gnome-control-center-unity 1.2daily13.02.15-0ubuntu1 indicator-datetime 12.10.3daily13.02.06-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1132063/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1132063] Re: Mouse settings missing from Mouse Touchpad dialog
This is really annoying because it makes Ubuntu unusable when using some of the DPI selections of my new mouse. The mouse speed setting won't come up with my old mouse, too. I've added some debug printf() to gnome-control-center gsd-input-helper.c in device_type_is_present: printf(Result %d: name %s type %d\n, i, device_info[i].name, device_info[i].type); printf(Result %d: type %s\n, i, XGetAtomName(GDK_DISPLAY_XDISPLAY (gdk_display_get_default ()), device_info[i].type)); (second line is a memory leak) And in device_info_is_mouse, where atom is the result of the XInternAtom call in that function: printf(Mouse atom: %s - %d\n, XGetAtomName(GDK_DISPLAY_XDISPLAY (gdk_display_get_default ()), atom), atom); This is the output when opening the mouse panel: Result 0: name Virtual core pointer type 0 Result 0: type (null) Mouse atom: MOUSE - 89 Result 1: name Virtual core keyboard type 0 Result 1: type (null) Mouse atom: MOUSE - 89 Result 2: name Virtual core XTEST pointer type 0 Result 2: type (null) Mouse atom: MOUSE - 89 Result 3: name Virtual core XTEST keyboard type 0 Result 3: type (null) Mouse atom: MOUSE - 89 Result 4: name Power Button type 88 Result 4: type KEYBOARD Mouse atom: MOUSE - 89 Result 5: name Power Button type 88 Result 5: type KEYBOARD Mouse atom: MOUSE - 89 Result 6: name AT Translated Set 2 keyboard type 88 Result 6: type KEYBOARD Mouse atom: MOUSE - 89 Result 7: name Holtek USB Gaming Mouse type 88 Result 7: type KEYBOARD Mouse atom: MOUSE - 89 Result 8: name Holtek USB Gaming Mouse type 88 Result 8: type KEYBOARD Mouse atom: MOUSE - 89 Result 9: name USB Multi-Smart Mouse type 88 Result 9: type KEYBOARD Mouse atom: MOUSE - 89 Clearly, all of the mouse entries (old mouse is the Multi-Smart one, new mouse is the Holtek one) use the KEYBOARD type aka atom 88, while no device uses the MOUSE atom number 89. So gnome-control-center assumes there are no mice because mouse_is_present() returns false. At the same time, xinput --list shows this (so one of the KEYBOARD entries for my Holtek mouse was correct, while the second entry should be MOUSE and the Multi-Smart mouse should have a MOUSE entry only): $ xinput --list ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ Holtek USB Gaming Mouse id=9[slave pointer (2)] ⎜ ↳ USB Multi-Smart Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Power Button id=7[slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=10 [slave keyboard (3)] ↳ Holtek USB Gaming Mouse id=8[slave keyboard (3)] So XListInputDevices appears to return the wrong device type? I'm afraid of X server internals, so I guess this is a dead end for me. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1132063 Title: Mouse settings missing from Mouse Touchpad dialog Status in “gnome-control-center” package in Ubuntu: Confirmed Bug description: On up to date Raring alpha, on System Settings Mouse Touchpad the Mouse settings are completely missing. The General and Touchpad sections are there but none for mouse. See attached screenshot. xinput --list shows ~$ xinput --list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MOSART Semi. 2.4G Keyboard Mouseid=11 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=14 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Sleep Buttonid=9[slave keyboard (3)] ↳ MOSART Semi. 2.4G Keyboard Mouseid=10 [slave keyboard (3)] ↳ Dell Dell USB Keyboard id=12 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=13 [slave keyboard (3)] and from lsusb: Bus 003 Device 002: ID 062a:3286 Creative Labs Nano Receiver [Sandstrom Laser Mouse SMWLL11] ProblemType: Bug DistroRelease: Ubuntu 13.04 Package:
[Desktop-packages] [Bug 1132063] Re: Mouse settings missing from Mouse Touchpad dialog
Another note, the xinput utility uses the XIQueryDevice (apparently part of xinput2) function instead of XListInputDevices (xinput1?) if xinput2 is available. gnome-control-center always uses XListInputDevices. That probably explains the difference between xinput --list and the debug output above. It does not explain why results between xinput1 and xinput2 functions differ. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1132063 Title: Mouse settings missing from Mouse Touchpad dialog Status in “gnome-control-center” package in Ubuntu: Confirmed Bug description: On up to date Raring alpha, on System Settings Mouse Touchpad the Mouse settings are completely missing. The General and Touchpad sections are there but none for mouse. See attached screenshot. xinput --list shows ~$ xinput --list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MOSART Semi. 2.4G Keyboard Mouseid=11 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=14 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Sleep Buttonid=9[slave keyboard (3)] ↳ MOSART Semi. 2.4G Keyboard Mouseid=10 [slave keyboard (3)] ↳ Dell Dell USB Keyboard id=12 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=13 [slave keyboard (3)] and from lsusb: Bus 003 Device 002: ID 062a:3286 Creative Labs Nano Receiver [Sandstrom Laser Mouse SMWLL11] ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-control-center 1:3.6.3-0ubuntu13 ProcVersionSignature: Ubuntu 3.8.0-7.15-generic 3.8.0 Uname: Linux 3.8.0-7-generic i686 ApportVersion: 2.8-0ubuntu4 Architecture: i386 Date: Sat Feb 23 09:40:41 2013 InstallationDate: Installed on 2012-08-01 (205 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha i386 (20120730.1) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu6.1 deja-dup25.5-0ubuntu1 gnome-control-center-signon 0.1.2bzr12.12.05-0ubuntu1 gnome-control-center-unity 1.2daily13.02.15-0ubuntu1 indicator-datetime 12.10.3daily13.02.06-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1132063/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 973295] Re: Enable grilo plugin
It looks like grilo is moving to main, so maybe we can get this bug fixed upstream in Trusty+1 or even Trusty? This bug fixed plus the most recent minidlna = nice setup :) [Older minidlna releases like the one in Trusty are not compatible with current grilo.] -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/973295 Title: Enable grilo plugin Status in “rhythmbox” package in Ubuntu: Triaged Bug description: At the moment grilo plugin is not being built thus leaving Jamendo and UPnP out of rhythmbox. This is only a packaging issue and can be easily fixed: debian/control: - Add libgrilo-0.1-dev to Build-Depends - Add gir1.2-grilo-0.1 to Depends on rhythmbox-plugins (or create a new package) debian/rhythmbox-plugins.install (or specific to a new package) - Add usr/lib/rhythmbox/plugins/grilo All grilo packages are now in Universe so this may not be done that easily though. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/973295/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1183086] Re: Please update to 27.0.1453.110
There's an updated chromium package available in chad miller's PPA now: https://launchpad.net/~cmiller/+archive/chromium-browser-stable-daily 28.0.1500.52-0ubuntu1 for precise, quantal, raring, saucy. Thanks Chad! -- 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/1183086 Title: Please update to 27.0.1453.110 Status in “chromium-browser” package in Ubuntu: Triaged Bug description: And again a new stable release with lots of security fixes: http://googlechromereleases.blogspot.de/2013/05/stable-channel- release.html Here are the CVEs: CVE-2013-2837: Use-after-free in SVG. CVE-2013-2838: Out-of-bounds read in v8. CVE-2013-2839: Bad cast in clipboard handling. CVE-2013-2840: Use-after-free in media loader. CVE-2013-2841: Use-after-free in Pepper resource handling. CVE-2013-2842: Use-after-free in widget handling. CVE-2013-2843: Use-after-free in speech handling. CVE-2013-2844: Use-after-free in style resolution. CVE-2013-2845: Memory safety issues in Web Audio. CVE-2013-2846: Use-after-free in media loader. CVE-2013-2847: Use-after-free race condition with workers. CVE-2013-2848: Possible data extraction with XSS Auditor. CVE-2013-2849: Possible XSS with drag+drop or copy+paste. Please update and keep current. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1183086/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1183086] Re: Please update to 27.0.1453.110
The plan for Chromium as the default browser in saucy is probably a joke, seeing how Ubuntu is stuck with Chromium 25 when the latest stable release (for Linux) is 28, and 25 has quite a few known security issues. Debian has shown much more interest in keeping up to date with chromium security fixes in unstable at least since version 18 or so (I haven't followed the process before that), though there were some larger delays as well. If you can't fix this problem, maybe think about joining forces with debian and make sure the packages in unstable are quickly copied to Ubuntu as well, and possibly vice-versa. -- 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/1183086 Title: Please update to 27.0.1453.110 Status in “chromium-browser” package in Ubuntu: Triaged Bug description: And again a new stable release with lots of security fixes: http://googlechromereleases.blogspot.de/2013/05/stable-channel- release.html Here are the CVEs: CVE-2013-2837: Use-after-free in SVG. CVE-2013-2838: Out-of-bounds read in v8. CVE-2013-2839: Bad cast in clipboard handling. CVE-2013-2840: Use-after-free in media loader. CVE-2013-2841: Use-after-free in Pepper resource handling. CVE-2013-2842: Use-after-free in widget handling. CVE-2013-2843: Use-after-free in speech handling. CVE-2013-2844: Use-after-free in style resolution. CVE-2013-2845: Memory safety issues in Web Audio. CVE-2013-2846: Use-after-free in media loader. CVE-2013-2847: Use-after-free race condition with workers. CVE-2013-2848: Possible data extraction with XSS Auditor. CVE-2013-2849: Possible XSS with drag+drop or copy+paste. Please update and keep current. Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1183086/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 880267] Re: join/split lines not working
** Bug watch added: GNOME Bug Tracker #701070
https://bugzilla.gnome.org/show_bug.cgi?id=701070
** Also affects: gedit-plugins via
https://bugzilla.gnome.org/show_bug.cgi?id=701070
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit-plugins in Ubuntu.
https://bugs.launchpad.net/bugs/880267
Title:
join/split lines not working
Status in set of plugins for gedit:
Unknown
Status in “gedit-plugins” package in Ubuntu:
Confirmed
Status in “gedit-plugins” package in Debian:
New
Bug description:
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -
About Ubuntu
Description: Ubuntu 11.10
Release: 11.10
2) The version of the package you are using, via 'apt-cache policy pkgname'
or by checking in Software Center
gedit:
Installiert: 3.2.1-0ubuntu1
Kandidat:3.2.1-0ubuntu1
Versionstabelle:
*** 3.2.1-0ubuntu1 0
500 http://archive.ubuntu.com/ubuntu/ oneiric-proposed/main amd64
Packages
100 /var/lib/dpkg/status
3.2.0-0ubuntu1 0
500 http://archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages
gedit-plugins:
Installiert: 3.2.0-0ubuntu1
Kandidat:3.2.0-0ubuntu1
Versionstabelle:
*** 3.2.0-0ubuntu1 0
500 http://archive.ubuntu.com/ubuntu/ oneiric/universe amd64 Packages
100 /var/lib/dpkg/status
3) What you expected to happen
Lines should be joined or split if I use the plugin
4) What happened instead
Noting happens it doesn't work.
This is the error that I get, if I start gedit in an terminal.
Traceback (most recent call last):
File /usr/lib/gedit/plugins/joinlines.py, line 79, in lambda
lambda a, w: split_lines(w))],
File /usr/lib/gedit/plugins/joinlines.py, line 171, in split_lines
forward_to_word_end(current_word_end)
File /usr/lib/gedit/plugins/joinlines.py, line 218, in forward_to_word_end
while ord(char) and (not (char in (' ', '\t', '\n', '\r'))):
TypeError: ord() expected a character, but string of length 2 found
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: gedit 3.2.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-13.21-generic 3.0.6
Uname: Linux 3.0.0-13-generic x86_64
ApportVersion: 1.23-0ubuntu3
Architecture: amd64
CheckboxSubmission: 13741649d6b2dd56d757d58c3d964436
CheckboxSystem: da9af3b901b5569a389df6337f3d812f
Date: Sun Oct 23 11:35:19 2011
InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110906)
SourcePackage: gedit
UpgradeStatus: Upgraded to oneiric on 2011-09-30 (23 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/gedit-plugins/+bug/880267/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 973295] Re: Enable grilo plugin
I've modified and uploaded (to PPA) the raring rhythmbox package to enable grilo plugin support, in case anyone else wants to use this on raring: https://launchpad.net/~florian-will/+archive/grilo-rb -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/973295 Title: Enable grilo plugin Status in “rhythmbox” package in Ubuntu: Triaged Bug description: At the moment grilo plugin is not being built thus leaving Jamendo and UPnP out of rhythmbox. This is only a packaging issue and can be easily fixed: debian/control: - Add libgrilo-0.1-dev to Build-Depends - Add gir1.2-grilo-0.1 to Depends on rhythmbox-plugins (or create a new package) debian/rhythmbox-plugins.install (or specific to a new package) - Add usr/lib/rhythmbox/plugins/grilo All grilo packages are now in Universe so this may not be done that easily though. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/973295/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1078290] Re: Add package fglrx-experimental for tracking fglrx beta drivers
A fglrx package newer than 12.10 is required in Quantal as well. Team Fortress 2 (and potentially other Valve/Source Engine games?) appear not to work with fglrx 12.10. IMHO, fixing/releasing this for all supported Ubuntu releases should be a high priority. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1078290 Title: Add package fglrx-experimental for tracking fglrx beta drivers Status in “fglrx-installer-experimental-9” package in Ubuntu: Confirmed Status in “jockey” package in Ubuntu: Invalid Status in “fglrx-installer-experimental-9” source package in Precise: Fix Released Status in “jockey” source package in Precise: Fix Released Status in “fglrx-installer-experimental-9” source package in Quantal: Confirmed Status in “jockey” source package in Quantal: Invalid Status in “fglrx-installer-experimental-9” source package in Raring: Confirmed Status in “jockey” source package in Raring: Invalid Bug description: [Impact] AMD posts beta versions of their drivers to be tested over several weeks. These drivers usually include important features and fixes but also sometimes include known issues or regressions that make them unsuitable or too risky for us to consider inclusion in the fglrx-updates package. However certain commercial Linux games require features/fixes present only in these AMD beta drivers at the time of their release. Ubuntu users who purchase these games currently have to manually install the beta driver (or wait a month or two for it to appear in -updates). Providing these drivers via fglrx-experimental will enable them to install and run the game within the Ubuntu packaging system. [Fix] The fglrx-experimental-NNN binary package is established (provided by the fglrx-installer-experimental source package) for quantal 12.10 and precise 12.04. This uses the packaging scripts from fglrx-updates, with the renamed package and new .run files. The fglrx-experimental-NNN package will be visible to users via Jockey as normal. When a user installs the experimental package, any other fglrx drivers will be disabled. They will remain on the selected fglrx-experimental-NNN until they upgrade to a new Ubuntu release or LTS point release, at which point they'll be returned to fglrx- current. They can of course manually switch from fglrx-experimental- NNN back to fglrx or fglrx-updates (or some newer fglrx-experimental- MMM) if they wish. The control file for the experimental package proposed for precise has some differences from the one in quantal, and also has some differences against the non-experimental fglrx driver in precise. Here is an explanation of those differences in turn: * Conflicts/Replaces on fglrx-*-modaliases (from precise's fglrx package) are no longer needed. The modaliases packages were used in previous releases but no longer exist in precise. Since people can't upgrade from those previous versions directly to fglrx*experimental, there is no need to have Conflicts/Replaces. * Conflicts/Replaces/Provides of various nvidia/fglrx packages (from quantal's fglrx-experimental package) are only needed for quantal forward. These are required by the new restricted drivers UI in quantal. Since that UI is not in precise, we don't need it in precise. [Regression Potential] The reason we're adding this package in the first place is because of concerns that beta drivers will have a high risk of regressions. Thus, users need to be aware they are taking these risks when they opt-in to the driver. As mentioned above, fglrx and fglrx-updates will still be available to them in case they have problems. In a worst case scenario they may need to do this from a recovery session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-experimental-9/+bug/1078290/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1078290] Re: Add package fglrx-experimental for tracking fglrx beta drivers
This is probably no longer required, because AMD released a stable Catalyst 13.1 yesterday. So now waiting for it to hit fglrx-updates. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1078290 Title: Add package fglrx-experimental for tracking fglrx beta drivers Status in “fglrx-installer” package in Ubuntu: In Progress Status in “fglrx-installer-experimental-9” package in Ubuntu: Confirmed Status in “jockey” package in Ubuntu: Invalid Status in “fglrx-installer” source package in Precise: In Progress Status in “fglrx-installer-experimental-9” source package in Precise: In Progress Status in “jockey” source package in Precise: Confirmed Status in “fglrx-installer” source package in Quantal: In Progress Status in “fglrx-installer-experimental-9” source package in Quantal: Confirmed Status in “jockey” source package in Quantal: Invalid Status in “fglrx-installer” source package in Raring: In Progress Status in “fglrx-installer-experimental-9” source package in Raring: Confirmed Status in “jockey” source package in Raring: Invalid Bug description: [Impact] AMD posts beta versions of their drivers to be tested over several weeks. These drivers usually include important features and fixes but also sometimes include known issues or regressions that make them unsuitable or too risky for us to consider inclusion in the fglrx-updates package. However certain commercial Linux games require features/fixes present only in these AMD beta drivers at the time of their release. Ubuntu users who purchase these games currently have to manually install the beta driver (or wait a month or two for it to appear in -updates). Providing these drivers via fglrx-experimental will enable them to install and run the game within the Ubuntu packaging system. [Fix] The fglrx-experimental-NNN binary package is established (provided by the fglrx-installer-experimental source package) for quantal 12.10 and precise 12.04. This uses the packaging scripts from fglrx-updates, with the renamed package and new .run files. The fglrx-experimental-NNN package will be visible to users via Jockey as normal. When a user installs the experimental package, any other fglrx drivers will be disabled. They will remain on the selected fglrx-experimental-NNN until they upgrade to a new Ubuntu release or LTS point release, at which point they'll be returned to fglrx- current. They can of course manually switch from fglrx-experimental- NNN back to fglrx or fglrx-updates (or some newer fglrx-experimental- MMM) if they wish. The control file for the experimental package proposed for precise has some differences from the one in quantal, and also has some differences against the non-experimental fglrx driver in precise. Here is an explanation of those differences in turn: * Conflicts/Replaces on fglrx-*-modaliases (from precise's fglrx package) are no longer needed. The modaliases packages were used in previous releases but no longer exist in precise. Since people can't upgrade from those previous versions directly to fglrx*experimental, there is no need to have Conflicts/Replaces. * Conflicts/Replaces/Provides of various nvidia/fglrx packages (from quantal's fglrx-experimental package) are only needed for quantal forward. These are required by the new restricted drivers UI in quantal. Since that UI is not in precise, we don't need it in precise. [Regression Potential] The reason we're adding this package in the first place is because of concerns that beta drivers will have a high risk of regressions. Thus, users need to be aware they are taking these risks when they opt-in to the driver. As mentioned above, fglrx and fglrx-updates will still be available to them in case they have problems. In a worst case scenario they may need to do this from a recovery session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1078290/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1078290] Re: Add package fglrx-experimental for tracking fglrx beta drivers
AFAICT, this *-experimental package was uploaded to precise-proposed, but not to quantal-proposed. I'd like to be able to use this driver on quantal without manually installing it from AMD's web page. The bug description for this bug also states that the package was meant to be available for quantal and precise. So as a quantal user, I'd vote for verification-failed unless the package shows up in quantal-proposed as well. :-) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1078290 Title: Add package fglrx-experimental for tracking fglrx beta drivers Status in “fglrx-installer” package in Ubuntu: In Progress Status in “fglrx-installer-experimental-9” package in Ubuntu: Confirmed Status in “jockey” package in Ubuntu: Invalid Status in “fglrx-installer” source package in Precise: In Progress Status in “fglrx-installer-experimental-9” source package in Precise: In Progress Status in “jockey” source package in Precise: Confirmed Status in “fglrx-installer” source package in Quantal: In Progress Status in “fglrx-installer-experimental-9” source package in Quantal: Confirmed Status in “jockey” source package in Quantal: Invalid Status in “fglrx-installer” source package in Raring: In Progress Status in “fglrx-installer-experimental-9” source package in Raring: Confirmed Status in “jockey” source package in Raring: Invalid Bug description: [Impact] AMD posts beta versions of their drivers to be tested over several weeks. These drivers usually include important features and fixes but also sometimes include known issues or regressions that make them unsuitable or too risky for us to consider inclusion in the fglrx-updates package. However certain commercial Linux games require features/fixes present only in these AMD beta drivers at the time of their release. Ubuntu users who purchase these games currently have to manually install the beta driver (or wait a month or two for it to appear in -updates). Providing these drivers via fglrx-experimental will enable them to install and run the game within the Ubuntu packaging system. [Fix] The fglrx-experimental-NNN binary package is established (provided by the fglrx-installer-experimental source package) for quantal 12.10 and precise 12.04. This uses the packaging scripts from fglrx-updates, with the renamed package and new .run files. The fglrx-experimental-NNN package will be visible to users via Jockey as normal. When a user installs the experimental package, any other fglrx drivers will be disabled. They will remain on the selected fglrx-experimental-NNN until they upgrade to a new Ubuntu release or LTS point release, at which point they'll be returned to fglrx- current. They can of course manually switch from fglrx-experimental- NNN back to fglrx or fglrx-updates (or some newer fglrx-experimental- MMM) if they wish. The control file for the experimental package proposed for precise has some differences from the one in quantal, and also has some differences against the non-experimental fglrx driver in precise. Here is an explanation of those differences in turn: * Conflicts/Replaces on fglrx-*-modaliases (from precise's fglrx package) are no longer needed. The modaliases packages were used in previous releases but no longer exist in precise. Since people can't upgrade from those previous versions directly to fglrx*experimental, there is no need to have Conflicts/Replaces. * Conflicts/Replaces/Provides of various nvidia/fglrx packages (from quantal's fglrx-experimental package) are only needed for quantal forward. These are required by the new restricted drivers UI in quantal. Since that UI is not in precise, we don't need it in precise. [Regression Potential] The reason we're adding this package in the first place is because of concerns that beta drivers will have a high risk of regressions. Thus, users need to be aware they are taking these risks when they opt-in to the driver. As mentioned above, fglrx and fglrx-updates will still be available to them in case they have problems. In a worst case scenario they may need to do this from a recovery session. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1078290/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1087457] Re: jockey-text and jockey-gui crash with failed assertions
Same problem with precise-proposed, the xorg-edgers PPA enabled and Radeon HD6870, but some line numbers are different in the first stack trace. Traceback (most recent call last): File /usr/bin/jockey-text, line 128, in module sys.exit(u.run()) File /usr/lib/python2.7/dist-packages/jockey/ui.py, line 421, in run self.list() File /usr/lib/python2.7/dist-packages/jockey/ui.py, line 477, in list i = self.backend().handler_info(h_id) File /usr/lib/python2.7/dist-packages/dbus/proxies.py, line 145, in __call__ **keywords) File /usr/lib/python2.7/dist-packages/dbus/connection.py, line 651, in call_blocking message, timeout) dbus.exceptions.DBusException: org.freedesktop.DBus.Python.TypeError: Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/dbus/service.py, line 751, in _message_cb _method_reply_return(connection, message, method_name, signature, *retval) File /usr/lib/python2.7/dist-packages/dbus/service.py, line 254, in _method_reply_return reply.append(signature=signature, *retval) TypeError: Expected a string or unicode object -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1087457 Title: jockey-text and jockey-gui crash with failed assertions Status in “jockey” package in Ubuntu: Confirmed Bug description: I'm getting this error message: $ jockey-gtk (jockey-gtk:17364): Gtk-CRITICAL **: gtk_icon_set_render_icon_pixbuf: assertion `icon_set != NULL' failed (jockey-gtk:17364): Gtk-CRITICAL **: gtk_icon_set_render_icon_pixbuf: assertion `icon_set != NULL' failed Traceback (most recent call last): File /usr/bin/jockey-gtk, line 418, in module sys.exit(u.run()) File /usr/lib/python2.7/dist-packages/jockey/ui.py, line 468, in run self.ui_show_main() File /usr/bin/jockey-gtk, line 94, in ui_show_main self.update_tree_model() File /usr/bin/jockey-gtk, line 275, in update_tree_model info = self.get_ui_driver_info(h_id) File /usr/lib/python2.7/dist-packages/jockey/ui.py, line 295, in get_ui_driver_info info = self.backend().handler_info(handler_id) File /usr/lib/python2.7/dist-packages/dbus/proxies.py, line 145, in __call__ **keywords) File /usr/lib/python2.7/dist-packages/dbus/connection.py, line 651, in call_blocking message, timeout) dbus.exceptions.DBusException: org.freedesktop.DBus.Python.TypeError: Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/dbus/service.py, line 751, in _message_cb _method_reply_return(connection, message, method_name, signature, *retval) File /usr/lib/python2.7/dist-packages/dbus/service.py, line 254, in _method_reply_return reply.append(signature=signature, *retval) TypeError: Expected a string or unicode object I've tried `sudo apt-get install module-assistant` as suggested in https://bugs.launchpad.net/ubuntu/+source/fglrx- installer/+bug/937325/comments/2. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: jockey-common 0.9.7-0ubuntu7.6 ProcVersionSignature: Ubuntu 3.2.0-34.53-generic 3.2.33 Uname: Linux 3.2.0-34-generic x86_64 ApportVersion: 2.0.1-0ubuntu17 Architecture: amd64 Date: Thu Dec 6 22:33:43 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MachineType: System manufacturer System Product Name MarkForUpload: True PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-34-generic root=UUID=5d8c4012-b426-4b0e-8f37-cbdf2678cf96 ro quiet splash vt.handoff=7 SourcePackage: jockey UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/10/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0701 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P6X58D-E dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0701:bd05/10/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6X58D-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jockey/+bug/1087457/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 870560] Re: installing fglrx (post-release updates) fails
*** This bug is a duplicate of bug 873058 *** https://bugs.launchpad.net/bugs/873058 Affects me too. The log says: -- [...] Setting up fglrx-updates (2:8.960-0ubuntu1) ... update-alternatives: using /usr/lib/fglrx/ld.so.conf to provide /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf (x86_64-linux-gnu_gl_conf) in auto mode. update-alternatives: warning: skip creation of /etc/OpenCL/vendors/amdocl32.icd because associated file /usr/lib/fglrx/etc/OpenCL/vendors/amdocl32.icd (of link group x86_64-linux-gnu_gl_conf) doesn't exist. update-alternatives: warning: forcing reinstallation of alternative /usr/lib/fglrx/ld.so.conf because link group x86_64-linux-gnu_gl_conf is broken. update-alternatives: warning: skip creation of /etc/OpenCL/vendors/amdocl32.icd because associated file /usr/lib/fglrx/etc/OpenCL/vendors/amdocl32.icd (of link group x86_64-linux-gnu_gl_conf) doesn't exist. update-alternatives: using /usr/lib/fglrx/alt_ld.so.conf to provide /etc/ld.so.conf.d/i386-linux-gnu_GL.conf (i386-linux-gnu_gl_conf) in auto mode. update-initramfs: deferring update (trigger activated) Loading new fglrx-updates-8.960 DKMS files... First Installation: checking all kernels... Building only for 3.2.0-24-generic Building for architecture x86_64 Building initial module for 3.2.0-24-generic Done. fglrx_updates: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/3.2.0-24-generic/updates/dkms/ depmod.. DKMS: install completed. update-initramfs: deferring update (trigger activated) Processing triggers for bamfdaemon ... Rebuilding /usr/share/applications/bamf.index... Setting up fglrx-amdcccle-updates (2:8.960-0ubuntu1) ... Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-3.2.0-24-generic Processing triggers for libc-bin ... ldconfig deferred processing now taking place 2012-04-28 23:56:44,623 WARNING: /sys/module/fglrx_updates/drivers does not exist, cannot rebind fglrx_updates driver 2012-04-28 23:57:09,643 DEBUG: fglrx.enabled(fglrx_updates): target_alt None current_alt /usr/lib/fglrx/ld.so.conf other target alt None other current alt /usr/lib/fglrx/alt_ld.so.conf 2012-04-28 23:57:09,644 DEBUG: fglrx_updates is not the alternative in use 2012-04-28 23:57:09,682 DEBUG: fglrx.enabled(fglrx_updates): target_alt None current_alt /usr/lib/fglrx/ld.so.conf other target alt None other current alt /usr/lib/fglrx/alt_ld.so.conf 2012-04-28 23:57:09,682 DEBUG: fglrx_updates is not the alternative in use [-- EOF --] - /sys/module/fglrx_updates/drivers does not exist, cannot rebind fglrx_updates driver is correct, there is no directory /sys/module/fglrx_updates.- /sys/module/fglrx exists though, and it contains files with about the correct modification time. So maybe Jockey looks at the wrong directory and this is not a duplicate of #873058, as Jack Foy suggested. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/870560 Title: installing fglrx (post-release updates) fails Status in Jockey driver manager: New Status in “fglrx-installer-updates” package in Ubuntu: Confirmed Status in “jockey” package in Ubuntu: Confirmed Bug description: Installing fglrx (post-release updates) on up to date oneiric fails. This happens both with and without the normal fglrx package installed. I have attached the log for the case where the normal fglrx is installed. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: jockey-gtk 0.9.4-0ubuntu10 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 NonfreeKernelModules: fglrx ApportVersion: 1.23-0ubuntu2 Architecture: i386 Date: Sat Oct 8 10:53:16 2011 EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta i386 (20110901) MachineType: Acer Aspire M5500 PackageArchitecture: all ProcEnviron: PATH=(custom, no user) LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-12-generic root=UUID=c3966ea2-ff82-488b-9efc-091a02cf2492 ro quiet splash vt.handoff=7 SourcePackage: jockey UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/18/2007 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: R01-B0 dmi.board.name: FG965M dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrR01-B0:bd06/18/2007:svnAcer:pnAspireM5500:pvrR01-B0:rvnAcer:rnFG965M:rvr:cvnAcer:ct3:cvr: dmi.product.name: Aspire M5500 dmi.product.version: R01-B0 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/jockey/+bug/870560/+subscriptions -- Mailing list:
