[Desktop-packages] [Bug 1041916] Re: Touchpad of Fujitsu LifeBook AH532 not recognized
Thanks to Vince, #14 resolved my problems. Dave Turvene's driver works flawlessly. My touchpad now works as it should... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1041916 Title: Touchpad of Fujitsu LifeBook AH532 not recognized Status in “xserver-xorg-input-synaptics” package in Ubuntu: Confirmed Bug description: Hi, on Ubuntu Precise 12.04.1 with kernel 3.2.0-29-generic the touchpad of the Fujitsu LifeBook AH532 (http://www.fujitsu.com/fts/products/computing/pc/notebooks-tablets/all-round/l is not recognized by the kernel. [Update: Same problem on Quantal as of 20120825] /proc/bus/input/device shows only a generic mouse: I: Bus=0011 Vendor=0002 Product=0001 Version= N: Name=PS/2 Generic Mouse Consequently, xinput shows Virtual core pointer id=2[master pointer ↳ Virtual core XTEST pointerid=4[slave pointer ↳ PS/2 Generic Mouseid=13 [slave pointer tpconfig --info reveals that it *is* a synaptic: Found Synaptics Touchpad. Firmware: 8.96 (multiple-byte mode). Sensor type: unknown (0). Geometry: rectangular/landscape/up. Packets: absolute, 80 packets per second. Corner taps disabled; no tap gestures. Edge motion: none. Z threshold: 6 of 7. 2 button mode; corner tap is right button click. Kernel: linux-image-3.2.0-29-generic 3.2.0-29.46 xorg: xserver-xorg-input-synaptics 1.6.2-1ubuntu1~precise1 Yours, Steffen ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xserver-xorg-input-synaptics 1.6.2-1ubuntu1~precise1 [modified: usr/share/X11/xorg.conf.d/50-synaptics.conf] ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24 Uname: Linux 3.2.0-29-generic x86_64 ApportVersion: 2.0.1-0ubuntu12 Architecture: amd64 Date: Sun Aug 26 20:43:59 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64+mac (20120822.4) MachineType: FUJITSU LIFEBOOK AH532 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-29-generic root=/dev/mapper/fujiama-precise ro persistent quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-synaptics UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/22/2012 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.09 dmi.board.name: FJNBB1C dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.09:bd05/22/2012:svnFUJITSU:pnLIFEBOOKAH532:pvr:rvnFUJITSU:rnFJNBB1C:rvr:cvnFUJITSU:ct10:cvr: dmi.product.name: LIFEBOOK AH532 dmi.sys.vendor: FUJITSU version.compiz: compiz 1:0.9.7.8-0ubuntu1.4 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.3+8.0.2-0ubuntu3.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.3+8.0.2-0ubuntu3.2 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1041916/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1262086] Re: [RZ537AA-ABA SR5010NX, Realtek ALC888, Green Headphone Out, Front] No sound at all
post the output of alsa-info.sh
https://wiki.ubuntu.com/Audio/AlsaInfo
ports:
analog-output: Analog Output (priority 9900, available: unknown)
properties:
analog-output-headphones: Headphones (priority 9000, available:
no)
properties:
seem no headphone jack detected
do your computer chassis have HDA front audio panel which support jack
detection ?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1262086
Title:
[RZ537AA-ABA SR5010NX, Realtek ALC888, Green Headphone Out, Front] No
sound at all
Status in “alsa-driver” package in Ubuntu:
New
Bug description:
It is not just the headphone jack, but the speaker jack as well.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: alsa-base 1.0.25+dfsg-0ubuntu1.1
ProcVersionSignature: Ubuntu 3.8.0-34.49~precise1-generic 3.8.13.12
Uname: Linux 3.8.0-34-generic i686
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k3.8.0-34-generic.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC888 Analog [ALC888 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: drako 1736 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xf9ffc000 irq 41'
Mixer name : 'Realtek ALC888'
Components : 'HDA:10ec0888,103c2a57,0011'
Controls : 42
Simple ctrls : 20
Date: Wed Dec 18 02:46:01 2013
InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release i386
(20130820.1)
MarkForUpload: True
PackageArchitecture: all
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
Symptom_Card: Built-in Audio - HDA Intel
Symptom_DevicesInUse:
1736/dev/snd/controlC0: drako F pulseaudio
AND
Symptom_Jack: Green Headphone Out, Front
Symptom_Type: No sound at all
Title: [RZ537AA-ABA SR5010NX, Realtek ALC888, Green Headphone Out, Front] No
sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/18/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.12
dmi.board.name: Livermore
dmi.board.vendor: ECS
dmi.board.version: 1.0
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd04/18/2007:svnCompaq-Presario:pnRZ537AA-ABASR5010NX:pvr:rvnECS:rnLivermore:rvr1.0:cvnHewlett-Packard:ct3:cvr:
dmi.product.name: RZ537AA-ABA SR5010NX
dmi.sys.vendor: Compaq-Presario
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1262086/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1262086] Re: [RZ537AA-ABA SR5010NX, Realtek ALC888, Green Headphone Out, Front] No sound at all
** Changed in: alsa-driver (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1262086
Title:
[RZ537AA-ABA SR5010NX, Realtek ALC888, Green Headphone Out, Front] No
sound at all
Status in “alsa-driver” package in Ubuntu:
Incomplete
Bug description:
It is not just the headphone jack, but the speaker jack as well.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: alsa-base 1.0.25+dfsg-0ubuntu1.1
ProcVersionSignature: Ubuntu 3.8.0-34.49~precise1-generic 3.8.13.12
Uname: Linux 3.8.0-34-generic i686
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k3.8.0-34-generic.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC888 Analog [ALC888 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: drako 1736 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xf9ffc000 irq 41'
Mixer name : 'Realtek ALC888'
Components : 'HDA:10ec0888,103c2a57,0011'
Controls : 42
Simple ctrls : 20
Date: Wed Dec 18 02:46:01 2013
InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release i386
(20130820.1)
MarkForUpload: True
PackageArchitecture: all
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
Symptom_Card: Built-in Audio - HDA Intel
Symptom_DevicesInUse:
1736/dev/snd/controlC0: drako F pulseaudio
AND
Symptom_Jack: Green Headphone Out, Front
Symptom_Type: No sound at all
Title: [RZ537AA-ABA SR5010NX, Realtek ALC888, Green Headphone Out, Front] No
sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/18/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.12
dmi.board.name: Livermore
dmi.board.vendor: ECS
dmi.board.version: 1.0
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd04/18/2007:svnCompaq-Presario:pnRZ537AA-ABASR5010NX:pvr:rvnECS:rnLivermore:rvr1.0:cvnHewlett-Packard:ct3:cvr:
dmi.product.name: RZ537AA-ABA SR5010NX
dmi.sys.vendor: Compaq-Presario
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1262086/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1222670] Re: [nVidia GTX645][10de:11c4] Unable to boot to desktop with nvidia-319 driver
According to the log there are two graphics cards on a desktop system. Jockey tries to offload rendering to the discrete card. This, however, should not happen on a desktop system, where I would expect users to use the NVIDIA card directly (and have the monitor connected to it). When LP: #1259237 is approved, nvidia-prime will do the offloading only when dealing with a laptop. The ideal solution would be to disable the integrated card from the BIOS. We should probably also update Jockey so that it doesn't provide the nvidia driver on desktop systems with Intel+NVIDIA. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-319-updates in Ubuntu. https://bugs.launchpad.net/bugs/1222670 Title: [nVidia GTX645][10de:11c4] Unable to boot to desktop with nvidia-319 driver Status in “nvidia-graphics-drivers-319” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-319-updates” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-319” source package in Precise: Triaged Status in “nvidia-graphics-drivers-319-updates” source package in Precise: Fix Committed Bug description: CID: 201303-13031 Dell Alienware X51 According to bug 1199342, this video card should be supported by nvidia-graphics-drivers-319. But it can't boot to desktop with nvidia-319 / nvidia-319-updates driver. Steps: 1. Install 12.04.3, boot to desktop. 2. Install the proprietary nvidia-319 video driver via jockey. 3. Reboot. Expected results: 1. System should be able to boot to desktop with the proprietary driver. Actual results: 1. Unable to boot to destop, the screen is totally black (screen won't enter idle mode). But I can still access this system via ssh. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: nvidia-319 319.32-0ubuntu0.0.1 ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.4 Architecture: amd64 Date: Mon Sep 9 02:01:57 2013 InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release amd64 (20130820.1) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers-319 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.modprobe.d.nvidia.319.hybrid.conf: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-319/+bug/1222670/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1238410] Re: Inconsistent cursor visibility with cursor plugin enabled
I am NOT sure if this is the same as this bug but in my case, the cursor has disappeared after the monitor was off/screensaver - once I moved the mouse to see the desktop, there was no cursor but I was able to click, I just can NOT see the cursor and it is hard to use a ghost cursor and keep clicking blindly :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1238410 Title: Inconsistent cursor visibility with cursor plugin enabled Status in GNOME Desktop Common Files: Fix Released Status in X.Org X server: In Progress Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Status in “xorg-server” package in Ubuntu: Fix Released Status in “gnome-settings-daemon” source package in Saucy: New Status in “xorg-server” source package in Saucy: Fix Committed Bug description: On fresh boots the greeter desktop may have the cursor visible or may not until mouse is moved. On a log out/in the cursor is almost always invisible until mouse is moved. (unless made visible in greeter screen, then visible on Desktop This is all well good, maybe some intentional aesthetics/design (https://bugzilla.gnome.org/show_bug.cgi?id=687791) , however sometimes the cursor never becomes visible. In that case hitting some keys or context menu can cause it to show, though most times a log out is needed. (with the removal of ctrl+alt+delete log out this means most users will need to either blindly find the session indicator or hit power button. When the g-s-d cursor plugin is disabled then the cursor is always visible, it the plugin has no use in an ubuntu session then maybe it should be default disabled There is also the possibility, particularly on ssd drives, of a login with no session indicator. This occasionally combines with no visible cursor. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-settings-daemon 3.8.5-0ubuntu7 ProcVersionSignature: Ubuntu 3.11.0-12.18-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Fri Oct 11 00:38:16 2013 InstallationDate: Installed on 2013-10-03 (8 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20131002) MarkForUpload: True SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-desktop/+bug/1238410/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1262068] Re: nvidia-prime should support gdm also
If gdm supports running scripts when starting a greeter seession or right after stopping X, then it's doable. These are the relevant fields in the lightdm configuration file: # display-setup-script = Script to run when starting a greeter session (runs as root) # display-stopped-script = Script to run after stopping the display server (runs as root) ** Changed in: nvidia-prime (Ubuntu) Importance: Undecided = Wishlist ** Changed in: nvidia-prime (Ubuntu) Status: New = Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1262068 Title: nvidia-prime should support gdm also Status in Ubuntu GNOME: Confirmed Status in “nvidia-prime” package in Ubuntu: Triaged Bug description: On Ubuntu GNOME we ship gdm by default, however nvidia-prime depends on lightdm. This means that 1. Anyone installing nvidia binary drivers will pull in nvidia-prime and subsequently lightdm. As a consequence of this they are also going to get the potentially confusing dconf pop-up asking them to choose a DM. 2. nvidia-prime probably won't work when using gdm I haven't looked to closely at how deeply integrated this is with lightdm, however we particularly don't want #1 happening, and it would be nice if #2 worked. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nvidia-prime (not installed) ProcVersionSignature: Ubuntu 3.12.0-5.13-generic 3.12.2 Uname: Linux 3.12.0-5-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Dec 18 16:56:19 2013 InstallationDate: Installed on 2012-09-23 (451 days ago) InstallationMedia: Ubuntu GNOME Remix 12.10 Quantal Quetzal - Alpha amd64(20120922) SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1262068/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1262071] Re: Cannot add/configure printer - Epson SX125 USB
Also tested on: Ubuntu - 14.04 dev release - 20131217. Offers a Epson proprietary driver to download and install, even though install was a 'Free software only'. This driver when selected does download, but fails to install. Choosing a local driver. The system searches and just hangs at this stage. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1262071 Title: Cannot add/configure printer - Epson SX125 USB Status in “cups” package in Ubuntu: New Bug description: Ubuntu Gnome - 14.04 dev release - 20131217. Cannot add/configure printer - Epson SX125 USB. See screentshot. I get hung on the dialog shown in the screenshot or am told in the pop-up indicator that there is no driver. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: cups 1.7.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.12.7-0ubuntu2 Architecture: amd64 CupsErrorLog: CurrentDesktop: GNOME Date: Wed Dec 18 06:19:21 2013 InstallationDate: Installed on 2013-12-18 (0 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20131217) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Gigabyte Technology Co., Ltd. GA-970A-DS3 Papersize: a4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.12.0-7-generic root=UUID=13483b2e-166e-4fdf-8977-674bdf71a712 ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/24/2013 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F7a dmi.board.name: GA-970A-DS3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF7a:bd01/24/2013:svnGigabyteTechnologyCo.,Ltd.:pnGA-970A-DS3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-970A-DS3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-970A-DS3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1262071/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1261733] Re: YouTube Videos does not work on Chromium BUT same video works on Firefox on the same system and machine
@Chad Miller (cmiller) I do hope you change this bug to confirmed :) I am glad that I am not the only one who is affected - see: http://code.google.com/p/chromium/issues/detail?id=250139 Thank you! ** Bug watch added: code.google.com/p/chromium/issues #250139 http://code.google.com/p/chromium/issues/detail?id=250139 -- 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/1261733 Title: YouTube Videos does not work on Chromium BUT same video works on Firefox on the same system and machine Status in “chromium-browser” package in Ubuntu: Incomplete Bug description: More details here: http://ubuntuforums.org/showthread.php?t=2194128 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: chromium-browser 31.0.1650.63-0ubuntu0.12.04.1~20131204.1 ProcVersionSignature: Ubuntu 3.2.0-57.87-generic 3.2.52 Uname: Linux 3.2.0-57-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Tue Dec 17 16:29:34 2013 Desktop-Session: DESKTOP_SESSION = xubuntu XDG_CONFIG_DIRS = /etc/xdg/xdg-xubuntu:/etc/xdg:/etc/xdg XDG_DATA_DIRS = /usr/share/xubuntu:/usr/local/share/:/usr/share/:/usr/share DetectedPlugins: (no entry found in the Preferences file) Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None InstallationMedia: Xubuntu 12.04.3 LTS Precise Pangolin - Release amd64 (20130820) MarkForUpload: True ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) chromium-default: CHROMIUM_FLAGS= To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1261733/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1261936] Re: Nimbus Sans L font metrics messed up in LibreOffice
apport information ** Tags added: apport-collected saucy ** Description changed: Regression in Saucy Salamander 13.10, worked fine in 13.04 and previous releases. Affects LibreOffice Writer (Other Libre Office modules not tested so far.) Font rendering and cursor positioning in texts is messed up, the letters look slightly distorted, letter spacing is incorrect with even partially overlapping letters and the cursor positioning in a line of text does not always match the actual editing position. Wrong font rendering also effects PDF files generated with LibreOffice writer in Saucy. Nimbus Sans L font rendering looks fine in kCharSelect. - PDFs generated before the update also are not affected and are rendered - fine by Okular. + PDFs generated before the update also are not affected and are rendered fine by Okular. + --- + ApportVersion: 2.12.5-0ubuntu2.1 + Architecture: amd64 + DistroRelease: Ubuntu 13.10 + MarkForUpload: True + Package: libreoffice 1:4.1.3-0ubuntu1 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 + Tags: saucy + Uname: Linux 3.11.0-14-generic x86_64 + UpgradeStatus: Upgraded to saucy on 2013-12-17 (0 days ago) + UserGroups: adm admin cdrom davfs2 dialout disk lp lpadmin plugdev sambashare www-data ** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/1261936/+attachment/3931719/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1261936 Title: Nimbus Sans L font metrics messed up in LibreOffice Status in “libreoffice” package in Ubuntu: Incomplete Bug description: Regression in Saucy Salamander 13.10, worked fine in 13.04 and previous releases. Affects LibreOffice Writer (Other Libre Office modules not tested so far.) (At least) Nimbus Sans L font rendering and cursor positioning in texts is messed up, the letters look slightly distorted, letter spacing is incorrect with even partially overlapping letters and the cursor positioning in a line of text does not always match the actual editing position. Wrong font rendering also effects PDF files generated with LibreOffice writer in Saucy. Nimbus Sans L font rendering looks fine in kCharSelect. PDFs generated before the update also are not affected and are rendered fine by Okular. --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 DistroRelease: Ubuntu 13.10 MarkForUpload: True Package: libreoffice 1:4.1.3-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Tags: saucy Uname: Linux 3.11.0-14-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-12-17 (0 days ago) UserGroups: adm admin cdrom davfs2 dialout disk lp lpadmin plugdev sambashare www-data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1261936/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1261936] ProcEnviron.txt
apport information ** Attachment added: ProcEnviron.txt https://bugs.launchpad.net/bugs/1261936/+attachment/3931720/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1261936 Title: Nimbus Sans L font metrics messed up in LibreOffice Status in “libreoffice” package in Ubuntu: Incomplete Bug description: Regression in Saucy Salamander 13.10, worked fine in 13.04 and previous releases. Affects LibreOffice Writer (Other Libre Office modules not tested so far.) (At least) Nimbus Sans L font rendering and cursor positioning in texts is messed up, the letters look slightly distorted, letter spacing is incorrect with even partially overlapping letters and the cursor positioning in a line of text does not always match the actual editing position. Wrong font rendering also effects PDF files generated with LibreOffice writer in Saucy. Nimbus Sans L font rendering looks fine in kCharSelect. PDFs generated before the update also are not affected and are rendered fine by Okular. --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 DistroRelease: Ubuntu 13.10 MarkForUpload: True Package: libreoffice 1:4.1.3-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Tags: saucy Uname: Linux 3.11.0-14-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-12-17 (0 days ago) UserGroups: adm admin cdrom davfs2 dialout disk lp lpadmin plugdev sambashare www-data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1261936/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1261936] Re: Nimbus Sans L font metrics messed up in LibreOffice
HTH, although there seems to be little detail about packages related to the actual problem in the data submitted by apport. Do you need any additional information? ** Description changed: Regression in Saucy Salamander 13.10, worked fine in 13.04 and previous releases. Affects LibreOffice Writer (Other Libre Office modules not tested so far.) - Font rendering and cursor positioning in texts is messed up, the letters - look slightly distorted, letter spacing is incorrect with even partially - overlapping letters and the cursor positioning in a line of text does - not always match the actual editing position. + (At least) Nimbus Sans L font rendering and cursor positioning in texts + is messed up, the letters look slightly distorted, letter spacing is + incorrect with even partially overlapping letters and the cursor + positioning in a line of text does not always match the actual editing + position. Wrong font rendering also effects PDF files generated with LibreOffice writer in Saucy. Nimbus Sans L font rendering looks fine in kCharSelect. PDFs generated before the update also are not affected and are rendered fine by Okular. - --- + --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 DistroRelease: Ubuntu 13.10 MarkForUpload: True Package: libreoffice 1:4.1.3-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Tags: saucy Uname: Linux 3.11.0-14-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-12-17 (0 days ago) UserGroups: adm admin cdrom davfs2 dialout disk lp lpadmin plugdev sambashare www-data -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1261936 Title: Nimbus Sans L font metrics messed up in LibreOffice Status in “libreoffice” package in Ubuntu: Incomplete Bug description: Regression in Saucy Salamander 13.10, worked fine in 13.04 and previous releases. Affects LibreOffice Writer (Other Libre Office modules not tested so far.) (At least) Nimbus Sans L font rendering and cursor positioning in texts is messed up, the letters look slightly distorted, letter spacing is incorrect with even partially overlapping letters and the cursor positioning in a line of text does not always match the actual editing position. Wrong font rendering also effects PDF files generated with LibreOffice writer in Saucy. Nimbus Sans L font rendering looks fine in kCharSelect. PDFs generated before the update also are not affected and are rendered fine by Okular. --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 DistroRelease: Ubuntu 13.10 MarkForUpload: True Package: libreoffice 1:4.1.3-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Tags: saucy Uname: Linux 3.11.0-14-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-12-17 (0 days ago) UserGroups: adm admin cdrom davfs2 dialout disk lp lpadmin plugdev sambashare www-data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1261936/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1244619]
downgrading to thunderbird 24.1.0 does also help. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1244619 Title: Thunderbird must be upgraded to Thunderbird 24.0.1 for lightning 2.6.1 Status in Lightning extension: Confirmed Status in Mozilla Thunderbird Mail and News: Confirmed Status in “thunderbird” package in Ubuntu: Fix Released Status in “thunderbird” package in Gentoo Linux: Fix Released Status in “thunderbird” package in openSUSE: Fix Released Bug description: Since the upgrade of Lightning 2.6.0 to Lightning 2.6.1, this extension need Thunderbird 24.0.1 but Ubuntu only give Thunderbird 24.0.0 https://blog.mozilla.org/calendar/2013/10/dont-upgrade-to-thunderbird-24-0-1-yet/ Update 4: Lightning 2.6.1 is now public. On Linux, it is compatible ONLY with Thunderbird 24.0.1, so go ahead and upgrade now. A lot of people don't use the Ubuntu package for Lightning but those of Mozilla. Ubuntu should give an upgrade to Thunderbird 24.0.1 and Lightning 2.6.1 Step: 1) Silent update of Lightning 2.6.0 to Lightning 2.6.1 on Thunderbird 24.0.0 2) Open your calendar and see nothing (see screencast) A work form it's to downgrade to Lightning 2.6 until waiting Ubuntu upgrade to Thunderbird 24.0.1. You could find it here: https://addons.mozilla.org/fr/thunderbird/addon/lightning/versions/?page=1#version-2.6 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: thunderbird 1:24.0+build1-0ubuntu0.12.04.1 ProcVersionSignature: Ubuntu 3.8.0-32.47~precise1-generic 3.8.13.10 Uname: Linux 3.8.0-32-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 BuildID: 20130913160939 Date: Fri Oct 25 12:30:44 2013 InstallationMedia: Ubuntu 12.04 Precise - Build amd64 LIVE Binary 20120425-15:28 MarkForUpload: True SourcePackage: thunderbird UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/lightning-extension/+bug/1244619/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1260396] Re: Ubiquity window spans width of screen
** Changed in: gtk+3.0 (Ubuntu) Importance: Undecided = High ** Changed in: gtk+3.0 (Ubuntu) Assignee: (unassigned) = Canonical Desktop Team (canonical-desktop-team) ** Also affects: ubiquity (Ubuntu Trusty) Importance: High Status: Confirmed ** Also affects: gtk+3.0 (Ubuntu Trusty) Importance: High Assignee: Canonical Desktop Team (canonical-desktop-team) Status: Confirmed ** Tags added: rls-t-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1260396 Title: Ubiquity window spans width of screen Status in “gtk+3.0” package in Ubuntu: Confirmed Status in “ubiquity” package in Ubuntu: Confirmed Status in “gtk+3.0” source package in Trusty: Confirmed Status in “ubiquity” source package in Trusty: Confirmed Bug description: Bug in trusty daily iso build number 20131212 From both ubiquity-dm and the live session the window spans the width of the screen until the install gets to the Slideshow/progress page where the window flickers/dissapears and then comes back to the correct width. I have attached screenshots of the bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1260396/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1262104] [NEW] fglrx 2:8.960-0ubuntu1: fglrx kernel module failed to build
Public bug reported: How can it get fixed? Because I need this for my study. Cheers ProblemType: Package DistroRelease: Ubuntu 12.04 Package: fglrx 2:8.960-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic i686 .tmp.unity.support.test.0: .tmp.unity.support.test.1: ApportVersion: 2.0.1-0ubuntu17.4 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz DKMSBuildLog: DKMS make.log for fglrx-8.960 for kernel 3.8.0-29-generic (i686) Wed Dec 18 16:34:06 WST 2013 AMD kernel module generator version 2.1 kernel includes at /lib/modules/3.8.0-29-generic/build/include not found or incomplete file: /lib/modules/3.8.0-29-generic/build/include/linux/version.h DKMSKernelVersion: 3.8.0-29-generic Date: Wed Dec 18 16:34:13 2013 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu DkmsStatus: fglrx, 8.960: added DuplicateSignature: DKMS make.log for fglrx-8.960 for kernel 3.8.0-29-generic (i686) AMD kernel module generator version 2.1 kernel includes at /lib/modules/3.8.0-29-generic/build/include not found or incomplete file: /lib/modules/3.8.0-29-generic/build/include/linux/version.h GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release i386 (20130820.1) Lsusb: Bus 001 Device 003: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox MarkForUpload: True PackageVersion: 2:8.960-0ubuntu1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic root=UUID=8e17e54d-6593-493c-ab47-fd361a5d0762 ro quiet splash vt.handoff=7 Renderer: Software SourcePackage: fglrx-installer Title: fglrx 2:8.960-0ubuntu1: fglrx kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH make.log: DKMS make.log for fglrx-8.960 for kernel 3.8.0-29-generic (i686) Wed Dec 18 16:34:06 WST 2013 AMD kernel module generator version 2.1 kernel includes at /lib/modules/3.8.0-29-generic/build/include not found or incomplete file: /lib/modules/3.8.0-29-generic/build/include/linux/version.h version.compiz: compiz 1:0.9.7.12-0ubuntu2 version.libdrm2: libdrm2 2.4.43-0ubuntu0.0.3 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: fglrx-installer (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package compiz-0.9 i386 precise referred-by-support ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1262104 Title: fglrx 2:8.960-0ubuntu1: fglrx kernel module failed to build Status in “fglrx-installer” package in Ubuntu: New Bug description: How can it get fixed? Because I need this for my study. Cheers ProblemType: Package DistroRelease: Ubuntu 12.04 Package: fglrx 2:8.960-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic i686 .tmp.unity.support.test.0: .tmp.unity.support.test.1: ApportVersion: 2.0.1-0ubuntu17.4 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz DKMSBuildLog: DKMS make.log for fglrx-8.960 for kernel 3.8.0-29-generic (i686) Wed Dec 18 16:34:06 WST 2013 AMD kernel module generator version 2.1 kernel includes at /lib/modules/3.8.0-29-generic/build/include not found or incomplete file: /lib/modules/3.8.0-29-generic/build/include/linux/version.h DKMSKernelVersion: 3.8.0-29-generic Date: Wed Dec 18 16:34:13 2013 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu DkmsStatus: fglrx, 8.960: added DuplicateSignature: DKMS make.log for fglrx-8.960 for kernel 3.8.0-29-generic (i686) AMD kernel module generator version 2.1 kernel includes at
[Desktop-packages] [Bug 1262104] Re: fglrx 2:8.960-0ubuntu1: fglrx kernel module failed to build
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1262104 Title: fglrx 2:8.960-0ubuntu1: fglrx kernel module failed to build Status in “fglrx-installer” package in Ubuntu: New Bug description: How can it get fixed? Because I need this for my study. Cheers ProblemType: Package DistroRelease: Ubuntu 12.04 Package: fglrx 2:8.960-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic i686 .tmp.unity.support.test.0: .tmp.unity.support.test.1: ApportVersion: 2.0.1-0ubuntu17.4 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz DKMSBuildLog: DKMS make.log for fglrx-8.960 for kernel 3.8.0-29-generic (i686) Wed Dec 18 16:34:06 WST 2013 AMD kernel module generator version 2.1 kernel includes at /lib/modules/3.8.0-29-generic/build/include not found or incomplete file: /lib/modules/3.8.0-29-generic/build/include/linux/version.h DKMSKernelVersion: 3.8.0-29-generic Date: Wed Dec 18 16:34:13 2013 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu DkmsStatus: fglrx, 8.960: added DuplicateSignature: DKMS make.log for fglrx-8.960 for kernel 3.8.0-29-generic (i686) AMD kernel module generator version 2.1 kernel includes at /lib/modules/3.8.0-29-generic/build/include not found or incomplete file: /lib/modules/3.8.0-29-generic/build/include/linux/version.h GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release i386 (20130820.1) Lsusb: Bus 001 Device 003: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox MarkForUpload: True PackageVersion: 2:8.960-0ubuntu1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic root=UUID=8e17e54d-6593-493c-ab47-fd361a5d0762 ro quiet splash vt.handoff=7 Renderer: Software SourcePackage: fglrx-installer Title: fglrx 2:8.960-0ubuntu1: fglrx kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH make.log: DKMS make.log for fglrx-8.960 for kernel 3.8.0-29-generic (i686) Wed Dec 18 16:34:06 WST 2013 AMD kernel module generator version 2.1 kernel includes at /lib/modules/3.8.0-29-generic/build/include not found or incomplete file: /lib/modules/3.8.0-29-generic/build/include/linux/version.h version.compiz: compiz 1:0.9.7.12-0ubuntu2 version.libdrm2: libdrm2 2.4.43-0ubuntu0.0.3 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1262104/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 911622] Re: [12.04] GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/i386-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache': Datei oder Verzeichnis nicht gefu
Added Trusty cause i got the same error there after installation from a daily build. ** Tags added: trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/911622 Title: [12.04] GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/i386-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache': Datei oder Verzeichnis nicht gefunden (file not found) Status in “gdk-pixbuf” package in Ubuntu: Confirmed Bug description: after the latest dist-upgrade on 12.04 there are a lot of these messages (Datei oder Verzeichnis not found == file not found) GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/i386-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache': Datei oder Verzeichnis nicht gefunden ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libgdk-pixbuf2.0-0 2.25.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-7.13-generic 3.2.0-rc7 Uname: Linux 3.2.0-7-generic i686 ApportVersion: 1.90-0ubuntu1 Architecture: i386 Date: Wed Jan 4 07:30:55 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110426) ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gdk-pixbuf UpgradeStatus: Upgraded to precise on 2011-12-04 (30 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/911622/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1259237] Re: Hybrid graphics enablement in 12.04.4
** Also affects: nvidia-settings (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-settings (Ubuntu) Importance: Undecided = Medium ** Changed in: nvidia-settings (Ubuntu) Status: New = In Progress ** Changed in: nvidia-settings (Ubuntu) Assignee: (unassigned) = Alberto Milone (albertomilone) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-304-updates in Ubuntu. https://bugs.launchpad.net/bugs/1259237 Title: Hybrid graphics enablement in 12.04.4 Status in “bbswitch” package in Ubuntu: Invalid Status in “nvidia-graphics-drivers-173” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-304” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-331” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: In Progress Status in “nvidia-prime” package in Ubuntu: Invalid Status in “nvidia-settings” package in Ubuntu: In Progress Status in “screen-resolution-extra” package in Ubuntu: Invalid Status in “bbswitch” source package in Precise: In Progress Status in “nvidia-prime” source package in Precise: In Progress Status in “screen-resolution-extra” source package in Precise: In Progress Bug description: SRU request: Please accept the following packages in precise-proposed. lightdm nvidia-prime nvidia-graphics-drivers-331 nvidia-graphics-drivers-331-updates nvidia-graphics-drivers-304 nvidia-graphics-drivers-304-updates nvidia-graphics-drivers-173 nvidia-settings screen-resolution-extra bbswitch [Rationale] This is the result of the HWE effort to bring power management to systems with NVIDIA Optimus. [Impact] Without this work, we keep both GPUs on all the time, thus heavily impacting on battery life. Thanks to this work, it is now possible to easily disable the discrete card when raw power is not needed. Furthermore nvidia-prime has better hardware detection now, and won't try to enable hybrid graphics on desktop systems any more. As for the technical details: * bbswitch is a backport of the package that now lives in main in 14.04. * The actual work happened in lightdm, nvidia-331, nvidia-331-updates, nvidia-prime, screen-resolution-extra, and nvidia-settings. * nvidia-settings now replaces all the different nvidia-settings flavours, so as to reduce the maintainance effort. I patched the app so that it checks the driver version (at runtime) and doesn't expose features that older driver releases do not support. * nvidia-331 and nvidia-331-updates replace 319 and 319-updates. These are the new LTS releases by NVIDIA. * nvidia-304 and nvidia-304-updates recommend the new nvidia-settings, include a security update, and build against the upcoming Linux 3.11 (lts-saucy). * nvidia-173, in addition to being compatible with Linux 3.11 (lts-saucy), also introduces transitional packages for 173-updates, as it doesn't make sense to maintain a separate -updates flavour any more. [Test Case] After installing the update, users should be able to boot the system as usual, with no regressions of any kind. * Systems with a single NVIDIA card: nvidia-prime will detect the hardware and do nothing at all on unsupported systems (such as the one card use case, or the desktop use case) * Systems with NVIDIA Optimus: nvidia-prime will preserve its previous behaviour by leaving both GPUs on. Users can launch nvidia-settings and switch to the power profile that they need. [Regression Potential] Low. The new features are enabled only if the user manually selects them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1259237/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1201372] Re: Losing sound in Windows after rebooting from Linux (Realtek ALC269VB)
I have the same trouble in Ubuntu 12.04, Notebook: Acer aspire 5553G Soundcard: Realtek ALC271X (Windows say that it is ALC269). First I want to say that this is NOT Linux bug, this is Windows 7 bug, or Realtek audio driver for Windows 7 bug. So, I have not found a solution for Windows, but I found a workaround for Linux. Workaround: edit file: /etc/init.d/reboot In function do_stop () replace command reboot -d -f -i to the command sequence: =-=-=-=- sync echo u /proc/sysrq-trigger sleep 1s echo b /proc/sysrq-trigger =-=-=-=- Now I have working sound in Windows 7 after reboot from Ubuntu 12.04. Workaround explanation: I found that the driver (shd_hda_intel) during unloading/uninit completely disables sound card. So this buggy Windows 7 cannot enable it again. To prevent driver uninit while reboot, I do emergency reboot (like pressing Alt+SysRq+B) instead of normal reboot, so kernel and drivers does not do uninit functions, and soundcard stay enabled. Using this workaround two days, seems like all goes fine. But be carefully, there may be consequences. P.S. Sorry for my english. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1201372 Title: Losing sound in Windows after rebooting from Linux (Realtek ALC269VB) Status in “alsa-driver” package in Ubuntu: Confirmed Bug description: When I reboot from Xubuntu 12.10 to Windows 7 I loose headphone sound in Windows. I checked the volume levels and even reinstalled Realtek audio drivers in Windows, but nothing has helped so far. Only workaround is to shutdown notebook from Xubuntu 12.10 rather than rebooting directly to Windows. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: alsa-base 1.0.25+dfsg-0ubuntu3.1 ProcVersionSignature: Ubuntu 3.5.0-36.57-generic 3.5.7.14 Uname: Linux 3.5.0-36-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.6.1-0ubuntu11 Architecture: amd64 Date: Mon Jul 15 13:18:40 2013 InstallationDate: Installed on 2013-01-17 (178 days ago) InstallationMedia: Xubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 207 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: K53BR dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr207:bd04/25/2012:svnASUSTeKComputerInc.:pnK53BR:pvr1.0:rvnASUSTeKComputerInc.:rnK53BR:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: K53BR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. mtime.conffile..etc.modprobe.d.alsa.base.conf: 2013-07-15T12:54:29.052652 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1201372/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1262110] [NEW] Ubuntu Gnome - running ubuntu-bug leaves 'Report a problem' icon in frequent apps menu
Public bug reported: Ubuntu Gnome - 14.04 dev release - 20131217. Running 'ubuntu-bug' leaves 'Report a problem' icon (blue paint splash) in frequent apps menu. This icon if clicked does nothing and should not be there after running 'ubuntu-bug' from the terminal. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apport 2.12.7-0ubuntu2 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.12.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Dec 18 09:00:48 2013 InstallationDate: Installed on 2013-12-18 (0 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20131217) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug gnome3 trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1262110 Title: Ubuntu Gnome - running ubuntu-bug leaves 'Report a problem' icon in frequent apps menu Status in “apport” package in Ubuntu: New Bug description: Ubuntu Gnome - 14.04 dev release - 20131217. Running 'ubuntu-bug' leaves 'Report a problem' icon (blue paint splash) in frequent apps menu. This icon if clicked does nothing and should not be there after running 'ubuntu-bug' from the terminal. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apport 2.12.7-0ubuntu2 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.12.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Dec 18 09:00:48 2013 InstallationDate: Installed on 2013-12-18 (0 days ago) InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20131217) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1262110/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1236945] Re: 32-bit vdpau acceleration not available
** Branch linked: lp:ubuntu/precise-proposed/nvidia-graphics-drivers-304 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-319 in Ubuntu. https://bugs.launchpad.net/bugs/1236945 Title: 32-bit vdpau acceleration not available Status in “nvidia-graphics-drivers-319” package in Ubuntu: In Progress Bug description: On a 64-bit Ubuntu 12.04 system, a 32-bit application doesn't find the NVIDIA VDPAU accelerated driver in /usr/lib32 by default. I discussed this with Alberto Milone, and he writes: The fix is trivial. It's just a matter of adding the /usr/lib32/ path in /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf (or in /etc/ld.so.conf.d/i386-linux-gnu_GL.conf). Here's what ldconfig currently says in my chroot: # ldconfig -p | grep pau libvdpau_nvidia.so (libc6,x86-64, OS ABI: Linux 2.3.99) = /usr/lib/libvdpau_nvidia.so libvdpau.so.1 (libc6,x86-64) = /usr/lib/x86_64-linux-gnu/libvdpau.so.1 This is what I get after I add the line that I mentioned: # ldconfig -p | grep pau libvdpau_nvidia.so (libc6,x86-64, OS ABI: Linux 2.3.99) = /usr/lib/libvdpau_nvidia.so libvdpau_nvidia.so (libc6, OS ABI: Linux 2.3.99) = /usr/lib32/libvdpau_nvidia.so libvdpau.so.1 (libc6,x86-64) = /usr/lib/x86_64-linux-gnu/libvdpau.so.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-319/+bug/1236945/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1212425] Re: SDK applications require /tmp access with nvidia (should honor TMPDIR)
** Branch linked: lp:ubuntu/precise-proposed/nvidia-graphics-drivers-304 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-319-updates in Ubuntu. https://bugs.launchpad.net/bugs/1212425 Title: SDK applications require /tmp access with nvidia (should honor TMPDIR) Status in “apparmor-easyprof-ubuntu” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-319” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-319-updates” package in Ubuntu: Fix Released Status in “apparmor-easyprof-ubuntu” source package in Saucy: Fix Released Status in “nvidia-graphics-drivers-319” source package in Saucy: Triaged Status in “nvidia-graphics-drivers-319-updates” source package in Saucy: Fix Released Status in “nvidia-graphics-drivers-tegra” source package in Saucy: Invalid Status in “nvidia-graphics-drivers-tegra3” source package in Saucy: Invalid Bug description: Nvidia desktop users need the following AppArmor permissions to avoid denials: owner /tmp/gl* mrw, But this rule breaks application confinement such that apps are able to tamper with each other. Interestingly, apps still run without the rule, so we can explicitly deny it for now. The use of /tmp is apparently hardcoded and does not honor TMPDIR (application confinement will setup TMPDIR to a private area for the app). strace confirms this: 24603 mkdir(/tmp, 0777) = -1 EEXIST (File exists) 24603 open(/tmp/glBRPYmm, O_RDWR|O_CREAT|O_EXCL, 0600) = -1 EACCES (Permission denied) While the use of O_EXCL is safe, we don't allow access to /tmp for confined apps and libraries/applications should always honor TMPDIR. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor-easyprof-ubuntu/+bug/1212425/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1255592] Re: IPv6 Automatic, only DHCP configuration results in no default route
Hi AZ, does your bug happen also without network manager from proposed? We need to know if this is a regression between 0.9.4.0-0ubuntu4.3 and 0.9.4.0-0ubuntu4.4. Can you please try network manager from updates? thanks -- 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/1255592 Title: IPv6 Automatic, only DHCP configuration results in no default route Status in “network-manager” package in Ubuntu: New Bug description: The local network uses SLAAC configuration (with the OtherConfig-Bit in the RA set) as default configuration for devices. Some devices however should use a different IPv6 address assigned by statefull dhcp. Obviously, the ManagedConfiguration bit in the RA is not set, as this would break the SLAAC clients. When choosing Automatic, only DHCP for IPv6 configuration in the network manager (which translates into method=dhcp or NM_SETTING_IP6_CONFIG_METHOD_DHCP), the IPv6 address and the IPv6 DNS Servers are successfully assigned, but there is no ipv6 default route. This is because NM_SETTING_IP6_CONFIG_METHOD_DHCP reconfigures sysctl to drop all RAs (accept_ra=0), but DHCPv6 still has no option to set the gateway IPv6 address (neither its link-local or globally valid address). So I currently cannot have only some clients use statefull DHCPv6, which is what I want. Solution: either a) add an option to set sysctl accept_ra=1, autoconf=0 ; so the client will not use a SLAAC address but still add a default route based on RA or b) add a gateway option to DHCPv6. This bug is to change network manager so the solution a) gets implemented, as this can be implemented in NetworkManager. Solution b) would need to be implemented in isc-dhcp-client and might need an updated RFC, but would allow for different use cases (i.e. http://www.ietf.org/mail-archive/web/ipv6/current/msg08684.html). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager 0.9.4.0-0ubuntu4.4 ProcVersionSignature: Ubuntu 3.2.0-56.86-generic 3.2.51 Uname: Linux 3.2.0-56-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Wed Nov 27 17:25:05 2013 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release amd64 (20101007) IpRoute: default via 141.24.40.126 dev eth0 proto static 141.24.40.64/26 dev eth0 proto kernel scope link src 141.24.40.77 metric 1 169.254.0.0/16 dev eth0 scope link metric 1000 IwConfig: lono wireless extensions. eth0 no wireless extensions. MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash RfKill: SourcePackage: network-manager UpgradeStatus: Upgraded to precise on 2012-09-19 (434 days ago) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Kabelnetzwerkverbindung 1 a32a6fb7-ed99-432f-acc8-c97cc3834e76 802-3-ethernet1385569506 Mi 27 Nov 2013 17:25:06 CETyes no /org/freedesktop/NetworkManager/Settings/1 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.4.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1255592/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1259237] Re: Hybrid graphics enablement in 12.04.4
Hello Alberto, or anyone else affected, Accepted nvidia-settings into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/nvidia- settings/331.20-0ubuntu0.0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags added: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1259237 Title: Hybrid graphics enablement in 12.04.4 Status in “bbswitch” package in Ubuntu: Invalid Status in “nvidia-graphics-drivers-173” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-304” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-331” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: In Progress Status in “nvidia-prime” package in Ubuntu: Invalid Status in “nvidia-settings” package in Ubuntu: In Progress Status in “screen-resolution-extra” package in Ubuntu: Invalid Status in “bbswitch” source package in Precise: In Progress Status in “nvidia-prime” source package in Precise: In Progress Status in “screen-resolution-extra” source package in Precise: In Progress Bug description: SRU request: Please accept the following packages in precise-proposed. lightdm nvidia-prime nvidia-graphics-drivers-331 nvidia-graphics-drivers-331-updates nvidia-graphics-drivers-304 nvidia-graphics-drivers-304-updates nvidia-graphics-drivers-173 nvidia-settings screen-resolution-extra bbswitch [Rationale] This is the result of the HWE effort to bring power management to systems with NVIDIA Optimus. [Impact] Without this work, we keep both GPUs on all the time, thus heavily impacting on battery life. Thanks to this work, it is now possible to easily disable the discrete card when raw power is not needed. Furthermore nvidia-prime has better hardware detection now, and won't try to enable hybrid graphics on desktop systems any more. As for the technical details: * bbswitch is a backport of the package that now lives in main in 14.04. * The actual work happened in lightdm, nvidia-331, nvidia-331-updates, nvidia-prime, screen-resolution-extra, and nvidia-settings. * nvidia-settings now replaces all the different nvidia-settings flavours, so as to reduce the maintainance effort. I patched the app so that it checks the driver version (at runtime) and doesn't expose features that older driver releases do not support. * nvidia-331 and nvidia-331-updates replace 319 and 319-updates. These are the new LTS releases by NVIDIA. * nvidia-304 and nvidia-304-updates recommend the new nvidia-settings, include a security update, and build against the upcoming Linux 3.11 (lts-saucy). * nvidia-173, in addition to being compatible with Linux 3.11 (lts-saucy), also introduces transitional packages for 173-updates, as it doesn't make sense to maintain a separate -updates flavour any more. [Test Case] After installing the update, users should be able to boot the system as usual, with no regressions of any kind. * Systems with a single NVIDIA card: nvidia-prime will detect the hardware and do nothing at all on unsupported systems (such as the one card use case, or the desktop use case) * Systems with NVIDIA Optimus: nvidia-prime will preserve its previous behaviour by leaving both GPUs on. Users can launch nvidia-settings and switch to the power profile that they need. [Regression Potential] Low. The new features are enabled only if the user manually selects them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1259237/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1259237] Re: Hybrid graphics enablement in 12.04.4
** Branch linked: lp:ubuntu/precise-proposed/bbswitch ** Branch linked: lp:~ubuntu-branches/ubuntu/precise/nvidia-graphics- drivers-331/precise-proposed ** Branch linked: lp:~ubuntu-branches/ubuntu/precise/nvidia-graphics- drivers-331-updates/precise-proposed ** Branch linked: lp:ubuntu/precise-proposed/nvidia-graphics-drivers-304 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-304-updates in Ubuntu. https://bugs.launchpad.net/bugs/1259237 Title: Hybrid graphics enablement in 12.04.4 Status in “bbswitch” package in Ubuntu: Invalid Status in “nvidia-graphics-drivers-173” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-304” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-331” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: In Progress Status in “nvidia-prime” package in Ubuntu: Invalid Status in “nvidia-settings” package in Ubuntu: In Progress Status in “screen-resolution-extra” package in Ubuntu: Invalid Status in “bbswitch” source package in Precise: In Progress Status in “nvidia-prime” source package in Precise: In Progress Status in “screen-resolution-extra” source package in Precise: In Progress Bug description: SRU request: Please accept the following packages in precise-proposed. lightdm nvidia-prime nvidia-graphics-drivers-331 nvidia-graphics-drivers-331-updates nvidia-graphics-drivers-304 nvidia-graphics-drivers-304-updates nvidia-graphics-drivers-173 nvidia-settings screen-resolution-extra bbswitch [Rationale] This is the result of the HWE effort to bring power management to systems with NVIDIA Optimus. [Impact] Without this work, we keep both GPUs on all the time, thus heavily impacting on battery life. Thanks to this work, it is now possible to easily disable the discrete card when raw power is not needed. Furthermore nvidia-prime has better hardware detection now, and won't try to enable hybrid graphics on desktop systems any more. As for the technical details: * bbswitch is a backport of the package that now lives in main in 14.04. * The actual work happened in lightdm, nvidia-331, nvidia-331-updates, nvidia-prime, screen-resolution-extra, and nvidia-settings. * nvidia-settings now replaces all the different nvidia-settings flavours, so as to reduce the maintainance effort. I patched the app so that it checks the driver version (at runtime) and doesn't expose features that older driver releases do not support. * nvidia-331 and nvidia-331-updates replace 319 and 319-updates. These are the new LTS releases by NVIDIA. * nvidia-304 and nvidia-304-updates recommend the new nvidia-settings, include a security update, and build against the upcoming Linux 3.11 (lts-saucy). * nvidia-173, in addition to being compatible with Linux 3.11 (lts-saucy), also introduces transitional packages for 173-updates, as it doesn't make sense to maintain a separate -updates flavour any more. [Test Case] After installing the update, users should be able to boot the system as usual, with no regressions of any kind. * Systems with a single NVIDIA card: nvidia-prime will detect the hardware and do nothing at all on unsupported systems (such as the one card use case, or the desktop use case) * Systems with NVIDIA Optimus: nvidia-prime will preserve its previous behaviour by leaving both GPUs on. Users can launch nvidia-settings and switch to the power profile that they need. [Regression Potential] Low. The new features are enabled only if the user manually selects them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1259237/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1259237] Re: Hybrid graphics enablement in 12.04.4
** Branch linked: lp:ubuntu/precise-proposed/nvidia-settings -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1259237 Title: Hybrid graphics enablement in 12.04.4 Status in “bbswitch” package in Ubuntu: Invalid Status in “nvidia-graphics-drivers-173” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-304” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-331” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: In Progress Status in “nvidia-prime” package in Ubuntu: Invalid Status in “nvidia-settings” package in Ubuntu: In Progress Status in “screen-resolution-extra” package in Ubuntu: Invalid Status in “bbswitch” source package in Precise: In Progress Status in “nvidia-prime” source package in Precise: In Progress Status in “screen-resolution-extra” source package in Precise: In Progress Bug description: SRU request: Please accept the following packages in precise-proposed. lightdm nvidia-prime nvidia-graphics-drivers-331 nvidia-graphics-drivers-331-updates nvidia-graphics-drivers-304 nvidia-graphics-drivers-304-updates nvidia-graphics-drivers-173 nvidia-settings screen-resolution-extra bbswitch [Rationale] This is the result of the HWE effort to bring power management to systems with NVIDIA Optimus. [Impact] Without this work, we keep both GPUs on all the time, thus heavily impacting on battery life. Thanks to this work, it is now possible to easily disable the discrete card when raw power is not needed. Furthermore nvidia-prime has better hardware detection now, and won't try to enable hybrid graphics on desktop systems any more. As for the technical details: * bbswitch is a backport of the package that now lives in main in 14.04. * The actual work happened in lightdm, nvidia-331, nvidia-331-updates, nvidia-prime, screen-resolution-extra, and nvidia-settings. * nvidia-settings now replaces all the different nvidia-settings flavours, so as to reduce the maintainance effort. I patched the app so that it checks the driver version (at runtime) and doesn't expose features that older driver releases do not support. * nvidia-331 and nvidia-331-updates replace 319 and 319-updates. These are the new LTS releases by NVIDIA. * nvidia-304 and nvidia-304-updates recommend the new nvidia-settings, include a security update, and build against the upcoming Linux 3.11 (lts-saucy). * nvidia-173, in addition to being compatible with Linux 3.11 (lts-saucy), also introduces transitional packages for 173-updates, as it doesn't make sense to maintain a separate -updates flavour any more. [Test Case] After installing the update, users should be able to boot the system as usual, with no regressions of any kind. * Systems with a single NVIDIA card: nvidia-prime will detect the hardware and do nothing at all on unsupported systems (such as the one card use case, or the desktop use case) * Systems with NVIDIA Optimus: nvidia-prime will preserve its previous behaviour by leaving both GPUs on. Users can launch nvidia-settings and switch to the power profile that they need. [Regression Potential] Low. The new features are enabled only if the user manually selects them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1259237/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1219908] Update Released
The verification of the Stable Release Update for nvidia-graphics- drivers-304-updates has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-304-updates in Ubuntu. https://bugs.launchpad.net/bugs/1219908 Title: [needs-packaging] All nvidia-current and nvidia-updates need repackaging to mirror official Nvidia releases... Status in Nvidia Feature Request and Bug Reporting: New Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-319-updates” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-304-updates” source package in Precise: Fix Released Status in “nvidia-graphics-drivers-319-updates” source package in Precise: Fix Committed Bug description: The official Nvidia long-lived-branch stable driver is now 319.49. That means that the recommended official driver is 319.49 and should be used by all Nvidia users except those using old legacy devices. There are important fixes that are in this driver and the previous 319.17 that affect Chromium browser users especially: + Fixed a memory leak that occurred when destroying a GLX window but not its associated X window. These can crash machines using Nvidia GPU's according to a Chromium- bug http://crbug.com/145600 NVIDIA linux drivers are unstable when using multiple Open GL contexts and with low memory.: and if check `about:gpu` you will see this is a major reason most if not all Nvidia GPU's are currently blacklisted. Also, when using Windows 7 I am at liberty to install any driver version I want, keeping my machine up to date with the latest official Nvidia fixes. With Ubuntu I'm stuck with older drivers that affect performance and contain old bugs that have already been fixed. This leads to a lower quality experience than with Windows. Drivers need to be kept current with upstream in my opinion. For the time being I have been cherry-picking *.deb packages from X-Org-Edgers so that I can replicate that Windows experience and it's been working. However, all Ubuntu users should have this experience as well and most do not know how to manually install packages using DPKG so it is out of their reach. The current Nvidia driver versions are as follows: http://www.nvidia.com/object/unix.html Long Lived Branch version: 319.49 -- `nvidia-current` should be here as stable Short Lived Branch version: 325.15 -- `nvidia-updates` should be here as unstable Legacy GPU version (304.xx series): 304.108 -- `nvidia-current-legacy` should be here. This situation has to be solved, Ubuntu cannot be so far behind the curve that it cannot keep Nvidia drivers fresh and in sync with the upstream Nvidia release schedule... To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia/+bug/1219908/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1219908] Re: [needs-packaging] All nvidia-current and nvidia-updates need repackaging to mirror official Nvidia releases...
This bug was fixed in the package nvidia-graphics-drivers-304-updates - 304.108-0ubuntu0.0.1 --- nvidia-graphics-drivers-304-updates (304.108-0ubuntu0.0.1) precise-proposed; urgency=low * debian/dkms/patches/buildfix_kernel_3.11.patch: - Add support for Linux 3.11. * debian/templates/dkms.conf.in: - Drop patch for Linux 3.10. * debian/rules: - Add the download-sources target. * New upstream release (LP: #1219908): - Implemented workarounds for two Adobe Flash bugs by applying libvdpau commit ca9e637c61e80145f0625a590c91429db67d0a40 to the version of libvdpau shipped with the NVIDIA driver. - Fixed a bug in nvidia-settings that could cause the wrong resolution to be set in basic mode for setups based on one display per X screen. -- Alberto Milone alberto.mil...@canonical.com Tue, 24 Sep 2013 11:15:58 +0200 ** Changed in: nvidia-graphics-drivers-304-updates (Ubuntu Precise) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-304-updates in Ubuntu. https://bugs.launchpad.net/bugs/1219908 Title: [needs-packaging] All nvidia-current and nvidia-updates need repackaging to mirror official Nvidia releases... Status in Nvidia Feature Request and Bug Reporting: New Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-319-updates” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-304-updates” source package in Precise: Fix Released Status in “nvidia-graphics-drivers-319-updates” source package in Precise: Fix Committed Bug description: The official Nvidia long-lived-branch stable driver is now 319.49. That means that the recommended official driver is 319.49 and should be used by all Nvidia users except those using old legacy devices. There are important fixes that are in this driver and the previous 319.17 that affect Chromium browser users especially: + Fixed a memory leak that occurred when destroying a GLX window but not its associated X window. These can crash machines using Nvidia GPU's according to a Chromium- bug http://crbug.com/145600 NVIDIA linux drivers are unstable when using multiple Open GL contexts and with low memory.: and if check `about:gpu` you will see this is a major reason most if not all Nvidia GPU's are currently blacklisted. Also, when using Windows 7 I am at liberty to install any driver version I want, keeping my machine up to date with the latest official Nvidia fixes. With Ubuntu I'm stuck with older drivers that affect performance and contain old bugs that have already been fixed. This leads to a lower quality experience than with Windows. Drivers need to be kept current with upstream in my opinion. For the time being I have been cherry-picking *.deb packages from X-Org-Edgers so that I can replicate that Windows experience and it's been working. However, all Ubuntu users should have this experience as well and most do not know how to manually install packages using DPKG so it is out of their reach. The current Nvidia driver versions are as follows: http://www.nvidia.com/object/unix.html Long Lived Branch version: 319.49 -- `nvidia-current` should be here as stable Short Lived Branch version: 325.15 -- `nvidia-updates` should be here as unstable Legacy GPU version (304.xx series): 304.108 -- `nvidia-current-legacy` should be here. This situation has to be solved, Ubuntu cannot be so far behind the curve that it cannot keep Nvidia drivers fresh and in sync with the upstream Nvidia release schedule... To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia/+bug/1219908/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1262120] [NEW] Sync qpdf 5.1.0-1 (main) from Debian unstable (main)
Public bug reported: Please sync qpdf 5.1.0-1 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * Use dh-autoreconf in order to update libtool.m4 for new ports. Applied in the new upload. Changelog entries since current trusty version 5.0.1-1ubuntu1: qpdf (5.1.0-1) unstable; urgency=medium * New upstream release * Use dh-autoreconf (Closes: #732093) * Update stanards to 3.9.5. No changes required. -- Jay Berkenbilt q...@debian.org Tue, 17 Dec 2013 15:50:11 -0500 ** Affects: qpdf (Ubuntu) Importance: Wishlist Status: New ** Changed in: qpdf (Ubuntu) Importance: Undecided = Wishlist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to qpdf in Ubuntu. https://bugs.launchpad.net/bugs/1262120 Title: Sync qpdf 5.1.0-1 (main) from Debian unstable (main) Status in “qpdf” package in Ubuntu: New Bug description: Please sync qpdf 5.1.0-1 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * Use dh-autoreconf in order to update libtool.m4 for new ports. Applied in the new upload. Changelog entries since current trusty version 5.0.1-1ubuntu1: qpdf (5.1.0-1) unstable; urgency=medium * New upstream release * Use dh-autoreconf (Closes: #732093) * Update stanards to 3.9.5. No changes required. -- Jay Berkenbilt q...@debian.org Tue, 17 Dec 2013 15:50:11 -0500 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qpdf/+bug/1262120/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1254028] Re: [precise] network manager set incorrect /64 prefix from dhcpv6 client
I prepared the patch. -- 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/1254028 Title: [precise] network manager set incorrect /64 prefix from dhcpv6 client Status in “network-manager” package in Ubuntu: New Bug description: network-manager in ubuntu precise use incorrect /64 prefix from dhcpv6 client which cause that internet connection not working on some ipv6 networks. this problem was fixed in upstream network-manager version 0.9.6 which is already available in ubuntu quantal and newer - but not in ubuntu precise. because this is critical problem (non working network/internet) new version of network manager (e.g 0.9.6) or at least patch which fixing this problem should be included in ubuntu precise which is LTS. upstream commit which fixing this problem: http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=eb460b70dad82d366d35fa5703c0e79a1389e4d1 more info about it: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661885 http://bugzilla.gnome.org/show_bug.cgi?id=656610 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1254028/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1254028] Re: [precise] network manager set incorrect /64 prefix from dhcpv6 client
I pushed the updated package in my ppa [1] can you please test it? thanks [1] https://launchpad.net/~costamagnagianfranco/+archive/firefox -- 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/1254028 Title: [precise] network manager set incorrect /64 prefix from dhcpv6 client Status in “network-manager” package in Ubuntu: New Bug description: network-manager in ubuntu precise use incorrect /64 prefix from dhcpv6 client which cause that internet connection not working on some ipv6 networks. this problem was fixed in upstream network-manager version 0.9.6 which is already available in ubuntu quantal and newer - but not in ubuntu precise. because this is critical problem (non working network/internet) new version of network manager (e.g 0.9.6) or at least patch which fixing this problem should be included in ubuntu precise which is LTS. upstream commit which fixing this problem: http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=eb460b70dad82d366d35fa5703c0e79a1389e4d1 more info about it: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661885 http://bugzilla.gnome.org/show_bug.cgi?id=656610 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1254028/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1254028] Re: [precise] network manager set incorrect /64 prefix from dhcpv6 client
This is the patch against the 0.9.4.0-0ubuntu4.4 version ** Patch added: fix-1254028-precise.patch https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1254028/+attachment/3931786/+files/fix-1254028-precise.patch -- 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/1254028 Title: [precise] network manager set incorrect /64 prefix from dhcpv6 client Status in “network-manager” package in Ubuntu: New Bug description: network-manager in ubuntu precise use incorrect /64 prefix from dhcpv6 client which cause that internet connection not working on some ipv6 networks. this problem was fixed in upstream network-manager version 0.9.6 which is already available in ubuntu quantal and newer - but not in ubuntu precise. because this is critical problem (non working network/internet) new version of network manager (e.g 0.9.6) or at least patch which fixing this problem should be included in ubuntu precise which is LTS. upstream commit which fixing this problem: http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=eb460b70dad82d366d35fa5703c0e79a1389e4d1 more info about it: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661885 http://bugzilla.gnome.org/show_bug.cgi?id=656610 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1254028/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 460944] Re: Update Site list is empty in Install New Software
resolved the issue with this workaround:
rm
${YOUR_WORKSPACE_FOLDER}/.metadata/.plugins/org.eclipse.equinox.p2.ui/dialog_settings.xml
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to eclipse in Ubuntu.
https://bugs.launchpad.net/bugs/460944
Title:
Update Site list is empty in Install New Software
Status in “eclipse” package in Ubuntu:
Fix Released
Status in “eclipse” source package in Karmic:
Fix Released
Bug description:
Binary package hint: eclipse
Description: Ubuntu 9.10
Release: 9.10
eclipse (3.5.1+repack~1-0ubuntu1) [universe]
- Installed eclipse
- Launched eclipse
- Gone to Install New Software
- Expected to find the default update sites with the so-called enabling
features and so on just as if I downloaded the package from eclipse.org
Found nothing, empty list.
This is not the GDK_NATIVE_WINDOWS bug: the list is properly rendered, but
is empty.
I cannot install any plugin like subversive, m2eclipse, some WTP
parts, because they all require some components from the default
update sites which are not shown anywhere.
Solution:
Add http://download.eclipse.org/releases/galileo/; as update site.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/460944/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 10910]
I'm also annoyed that every firefox i run have the letter as default page size... and of course, one only discovers this after trying to print and nothing show up on the printer. If in the past, print was little used, with the PDFjs, people start to print a lot more from firefox, making this issue more important. If this can not be fixed, at very least remove the default, leave it BLANK... on first printing, ask what paper size one wants... is not as friendly as a default, but having a broken default, trying to print and getting nothing is even worst. Most people will never know that the problem is the wrong paper size and don't understand why they don't have any printout. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/10910 Title: Default page size for printing is letter Status in The Mozilla Firefox Browser: In Progress Status in “firefox” package in Ubuntu: Triaged Status in “thunderbird” package in Ubuntu: Triaged Status in “firefox” package in Baltix: Confirmed Bug description: (Default warty install, dist-upgraded to hoary, language chosen is Norwegian) about:config reports that print.postscript.paper_size is letter, which is wrong for Norway, it should be A4. It should probably look at LC_PAPER or /etc/papersize To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/10910/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 10910]
https://bugzilla.mozilla.org/show_bug.cgi?id=947125 Actually, while the windows version works better, it is screwed too, specially on unusually paper sizes and margins. The main problem with letter is, that the gtk code part can't understand ps paper names, and the ps paper names doesn't understand iso_a4. The right solution would be to drop the whole thing and query printer and paper names directly via ipp or use only gtk code and throw the old cups lib and ps based query solution. Considering the other bug #629500 is stuck as well. My solution will be my own private inhouse addon as can no longer wait for a solution. The win32 version works more or less, except CSS2 Margins are still broken. For the linux version I plan to to use a ipp based solution or directly accessing cups via js-ctypes. Accessing CUPS via socket and ipp protocol, query paper sizes, create a postscript file and send it directly should be a more future proof technology. Technical that should work on OSX and if you have the right url with any ipp aware network printer, but that isn't my goal. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/10910 Title: Default page size for printing is letter Status in The Mozilla Firefox Browser: In Progress Status in “firefox” package in Ubuntu: Triaged Status in “thunderbird” package in Ubuntu: Triaged Status in “firefox” package in Baltix: Confirmed Bug description: (Default warty install, dist-upgraded to hoary, language chosen is Norwegian) about:config reports that print.postscript.paper_size is letter, which is wrong for Norway, it should be A4. It should probably look at LC_PAPER or /etc/papersize To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/10910/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 10910] Re: Default page size for printing is letter
** Bug watch added: Mozilla Bugzilla #947125 https://bugzilla.mozilla.org/show_bug.cgi?id=947125 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/10910 Title: Default page size for printing is letter Status in The Mozilla Firefox Browser: In Progress Status in “firefox” package in Ubuntu: Triaged Status in “thunderbird” package in Ubuntu: Triaged Status in “firefox” package in Baltix: Confirmed Bug description: (Default warty install, dist-upgraded to hoary, language chosen is Norwegian) about:config reports that print.postscript.paper_size is letter, which is wrong for Norway, it should be A4. It should probably look at LC_PAPER or /etc/papersize To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/10910/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1059633] Re: Emacs 'Ediff' Window Shrinks Horizontally To One Column Wide
The problem still persists for me. I use Ubuntu 14.04 (development branch) + emacs 23 . More precisely: GNU Emacs 23.4.1 (i686-pc-linux-gnu, GTK+ Version 2.24.21) of 2013-10-25 on akateko, modified by Debian -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to emacs24 in Ubuntu. https://bugs.launchpad.net/bugs/1059633 Title: Emacs 'Ediff' Window Shrinks Horizontally To One Column Wide Status in “compiz” package in Ubuntu: Invalid Status in “emacs23” package in Ubuntu: Confirmed Status in “emacs24” package in Ubuntu: Fix Released Status in “compiz” source package in Precise: Invalid Status in “emacs23” source package in Precise: Fix Released Status in “emacs24” source package in Precise: Invalid Status in “compiz” source package in Raring: Invalid Status in “emacs23” source package in Raring: Confirmed Status in “emacs24” source package in Raring: Fix Released Bug description: [Impact] Emacs users can't access the help screen for the ediff tool. [Test case] (For non emacsy people) Run emacs in a graphical environment Menu option: Tools-Compare-Two Buffers ENTER and ENTER to the two questions prompted A new window, 'Ediff', opens and contains the text Type ? for help In the 'Ediff' window, type the character '?', This is supposed to display helpful info on the ediff commands If broken: Ediff window will expand, then shrink horizontally to one character wide Grabbing the frame and resizing will cause the shrinking behavior to repeat If fixed: Ediff window will expand and show the contents of the help [Regression potential] It could be that some other graphical environment relies on the bug being present, working around it in a way that if it's not present anymore, the window resizing will break there. The current patch is tested for Unity and Cinnamon, and has been taken from the fix already applied upstream. [Original description] Unlike previously reported bug #941790, this bug involves a horizontal shrinkage to one column wide (multiple rows), and is still present in GNU Emacs 23.3.1. Resizing the window isn't a work-around, as the window immediately shrinks again. The behavior is observed as follows: Run ediff-buffers A new window, 'Ediff', opens and contains the text Type ? for hlep In the 'Ediff' window, type the character '?', This is supposed to display helpful info on the ediff commands Ediff window will expand, then shrink horizontally to one character wide Grabbing the frame and reszing will cause the shrinking behavior to repeat Releveant packages / versions: Ubuntu 12.04.1 LTS GNU Emacs 23.3.1 Unity 5.16.0-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1059633/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1260068] Re: Unity continuous-integration fails in armhf due possibly to a libegl issue
I would prefer not to revert it for now, but instead fix the bug. I've made a trusty chroot for testing on my pandaboard, how do I run those tests myself? -- 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/1260068 Title: Unity continuous-integration fails in armhf due possibly to a libegl issue Status in “mesa” package in Ubuntu: Confirmed Bug description: Since mesa 10.0 has been released, our Unity continuous-integration tests are failing on armhf builds. This is a snippet of the log: libEGL warning: DRI2: failed to authenticate Segmentation fault (core dumped) The log can be found here for reference: https://jenkins.qa.ubuntu.com/view/Trusty/view/All/job/unity-trusty- armhf-ci/56/console I don't have the core file or have access to an armhf machine to reproduce, so I'm only going on evidence based on the warning and the timing of the issue. *Note* This is blocking automerging of Unity code, so this issue is pretty critical. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1260068/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1262120] Re: Sync qpdf 5.1.0-1 (main) from Debian unstable (main)
Thank you for the report. Done. ** Changed in: qpdf (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to qpdf in Ubuntu. https://bugs.launchpad.net/bugs/1262120 Title: Sync qpdf 5.1.0-1 (main) from Debian unstable (main) Status in “qpdf” package in Ubuntu: Fix Released Bug description: Please sync qpdf 5.1.0-1 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * Use dh-autoreconf in order to update libtool.m4 for new ports. Applied in the new upload. Changelog entries since current trusty version 5.0.1-1ubuntu1: qpdf (5.1.0-1) unstable; urgency=medium * New upstream release * Use dh-autoreconf (Closes: #732093) * Update stanards to 3.9.5. No changes required. -- Jay Berkenbilt q...@debian.org Tue, 17 Dec 2013 15:50:11 -0500 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qpdf/+bug/1262120/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 526330] Re: Transitional/dummy packages unhelpfully shown by default
** Description changed: - Binary package hint: software-center + software-center 1.1.12, Ubuntu 10.04 It could be useful to hide transitional packages, so that unexperienced users don't install them thinking it's an additional software - ProblemType: Bug - Architecture: amd64 - Date: Tue Feb 23 11:08:00 2010 - DistroRelease: Ubuntu 10.04 - Package: software-center 1.1.12 - PackageArchitecture: all - ProcVersionSignature: Ubuntu 2.6.32-14.20-generic - SourcePackage: software-center - Uname: Linux 2.6.32-14-generic x86_64 + The Software Updater equivalent is bug 1166230. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-center in Ubuntu. https://bugs.launchpad.net/bugs/526330 Title: Transitional/dummy packages unhelpfully shown by default Status in “software-center” package in Ubuntu: Confirmed Bug description: software-center 1.1.12, Ubuntu 10.04 It could be useful to hide transitional packages, so that unexperienced users don't install them thinking it's an additional software The Software Updater equivalent is bug 1166230. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/526330/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1041790]
*** Bug 72829 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1041790 Title: [snb] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001, workaround i915.semaphores=0 Status in X.org xf86-video-intel: Confirmed Status in “linux” package in Ubuntu: Confirmed Status in “sandybridge-meta” package in Ubuntu: Confirmed Status in “xserver-xorg-video-intel” package in Ubuntu: Triaged Bug description: X locks up periodically for a 2 to ten seconds at a time and this crash log gets generated. It's significantly more than several times a day but not quite continuous. Temporarily disabiling semaphores seems to eliminate the problem. E.g.: $ sudo -s # echo 0 /sys/modules/i915/parameters/semaphores [Workaround] 1. Edit your /etc/default/grub file. 2. Change this line: GRUB_CMDLINE_LINUX_DEFAULT=quiet splash to GRUB_CMDLINE_LINUX_DEFAULT=quiet splash i915.semaphores=0 3. Then run sudo update-grub 4. And reboot If you indeed have this bug, that should stop the lockups from happening. If it doesn't, then file a new bug report. Side Effects: Rendering throughput is dropped by 10% with SNA, or as much as 3x with UXA. OpenGL performance is likely to be reduced by about 30%. More CPU time is spent waiting for the GPU with rc6 disabled, so increased power consumption. [Original Report] ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: xserver-xorg-video-intel 2:2.20.3-0ubuntu1 Uname: Linux 3.6.0-rc3-git-20120826.1015 x86_64 ApportVersion: 2.5.1-0ubuntu2 Architecture: amd64 Chipset: sandybridge-m-gt2 Date: Sun Aug 26 16:06:32 2012 DistroCodename: quantal DistroVariant: ubuntu DuplicateSignature: [sandybridge-m-gt2] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001 Ubuntu 12.10 EcryptfsInUse: Yes ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py GpuHangFrequency: Continuously InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120724.2) InterpreterPath: /usr/bin/python3.2mu MachineType: Dell Inc. Dell System XPS L502X ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.0-rc3-git-20120826.1015 root=UUID=135c8090-427c-460a-909d-eff262cd44b6 ro quiet splash vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu3 libdrm2 2.4.38-0ubuntu2 xserver-xorg-video-intel 2:2.20.3-0ubuntu1 SourcePackage: xserver-xorg-video-intel Title: [sandybridge-m-gt2] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001 UdevDb: Error: [Errno 2] No such file or directory: 'udevadm' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/29/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0NJT03 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA11:bd05/29/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L502X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1041790/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1259237] Please test proposed package
Hello Alberto, or anyone else affected, Accepted nvidia-graphics-drivers-304-updates into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/nvidia-graphics- drivers-304-updates/304.116-0ubuntu0.0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1259237 Title: Hybrid graphics enablement in 12.04.4 Status in “bbswitch” package in Ubuntu: Invalid Status in “nvidia-graphics-drivers-173” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-304” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-331” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: In Progress Status in “nvidia-prime” package in Ubuntu: Invalid Status in “nvidia-settings” package in Ubuntu: In Progress Status in “screen-resolution-extra” package in Ubuntu: Invalid Status in “bbswitch” source package in Precise: In Progress Status in “nvidia-prime” source package in Precise: In Progress Status in “screen-resolution-extra” source package in Precise: In Progress Bug description: SRU request: Please accept the following packages in precise-proposed. lightdm nvidia-prime nvidia-graphics-drivers-331 nvidia-graphics-drivers-331-updates nvidia-graphics-drivers-304 nvidia-graphics-drivers-304-updates nvidia-graphics-drivers-173 nvidia-settings screen-resolution-extra bbswitch [Rationale] This is the result of the HWE effort to bring power management to systems with NVIDIA Optimus. [Impact] Without this work, we keep both GPUs on all the time, thus heavily impacting on battery life. Thanks to this work, it is now possible to easily disable the discrete card when raw power is not needed. Furthermore nvidia-prime has better hardware detection now, and won't try to enable hybrid graphics on desktop systems any more. As for the technical details: * bbswitch is a backport of the package that now lives in main in 14.04. * The actual work happened in lightdm, nvidia-331, nvidia-331-updates, nvidia-prime, screen-resolution-extra, and nvidia-settings. * nvidia-settings now replaces all the different nvidia-settings flavours, so as to reduce the maintainance effort. I patched the app so that it checks the driver version (at runtime) and doesn't expose features that older driver releases do not support. * nvidia-331 and nvidia-331-updates replace 319 and 319-updates. These are the new LTS releases by NVIDIA. * nvidia-304 and nvidia-304-updates recommend the new nvidia-settings, include a security update, and build against the upcoming Linux 3.11 (lts-saucy). * nvidia-173, in addition to being compatible with Linux 3.11 (lts-saucy), also introduces transitional packages for 173-updates, as it doesn't make sense to maintain a separate -updates flavour any more. [Test Case] After installing the update, users should be able to boot the system as usual, with no regressions of any kind. * Systems with a single NVIDIA card: nvidia-prime will detect the hardware and do nothing at all on unsupported systems (such as the one card use case, or the desktop use case) * Systems with NVIDIA Optimus: nvidia-prime will preserve its previous behaviour by leaving both GPUs on. Users can launch nvidia-settings and switch to the power profile that they need. [Regression Potential] Low. The new features are enabled only if the user manually selects them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1259237/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1236945] Re: 32-bit vdpau acceleration not available
Hello Sam, or anyone else affected, Accepted nvidia-graphics-drivers-304-updates into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/nvidia-graphics- drivers-304-updates/304.116-0ubuntu0.0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags added: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-319 in Ubuntu. https://bugs.launchpad.net/bugs/1236945 Title: 32-bit vdpau acceleration not available Status in “nvidia-graphics-drivers-319” package in Ubuntu: In Progress Bug description: On a 64-bit Ubuntu 12.04 system, a 32-bit application doesn't find the NVIDIA VDPAU accelerated driver in /usr/lib32 by default. I discussed this with Alberto Milone, and he writes: The fix is trivial. It's just a matter of adding the /usr/lib32/ path in /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf (or in /etc/ld.so.conf.d/i386-linux-gnu_GL.conf). Here's what ldconfig currently says in my chroot: # ldconfig -p | grep pau libvdpau_nvidia.so (libc6,x86-64, OS ABI: Linux 2.3.99) = /usr/lib/libvdpau_nvidia.so libvdpau.so.1 (libc6,x86-64) = /usr/lib/x86_64-linux-gnu/libvdpau.so.1 This is what I get after I add the line that I mentioned: # ldconfig -p | grep pau libvdpau_nvidia.so (libc6,x86-64, OS ABI: Linux 2.3.99) = /usr/lib/libvdpau_nvidia.so libvdpau_nvidia.so (libc6, OS ABI: Linux 2.3.99) = /usr/lib32/libvdpau_nvidia.so libvdpau.so.1 (libc6,x86-64) = /usr/lib/x86_64-linux-gnu/libvdpau.so.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-319/+bug/1236945/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1212425] Re: SDK applications require /tmp access with nvidia (should honor TMPDIR)
Hello Jamie, or anyone else affected, Accepted nvidia-graphics-drivers-304-updates into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/nvidia-graphics- drivers-304-updates/304.116-0ubuntu0.0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags added: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-319 in Ubuntu. https://bugs.launchpad.net/bugs/1212425 Title: SDK applications require /tmp access with nvidia (should honor TMPDIR) Status in “apparmor-easyprof-ubuntu” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-319” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-319-updates” package in Ubuntu: Fix Released Status in “apparmor-easyprof-ubuntu” source package in Saucy: Fix Released Status in “nvidia-graphics-drivers-319” source package in Saucy: Triaged Status in “nvidia-graphics-drivers-319-updates” source package in Saucy: Fix Released Status in “nvidia-graphics-drivers-tegra” source package in Saucy: Invalid Status in “nvidia-graphics-drivers-tegra3” source package in Saucy: Invalid Bug description: Nvidia desktop users need the following AppArmor permissions to avoid denials: owner /tmp/gl* mrw, But this rule breaks application confinement such that apps are able to tamper with each other. Interestingly, apps still run without the rule, so we can explicitly deny it for now. The use of /tmp is apparently hardcoded and does not honor TMPDIR (application confinement will setup TMPDIR to a private area for the app). strace confirms this: 24603 mkdir(/tmp, 0777) = -1 EEXIST (File exists) 24603 open(/tmp/glBRPYmm, O_RDWR|O_CREAT|O_EXCL, 0600) = -1 EACCES (Permission denied) While the use of O_EXCL is safe, we don't allow access to /tmp for confined apps and libraries/applications should always honor TMPDIR. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor-easyprof-ubuntu/+bug/1212425/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1259237] Re: Hybrid graphics enablement in 12.04.4
** Branch linked: lp:ubuntu/precise-proposed/nvidia-graphics- drivers-304-updates -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1259237 Title: Hybrid graphics enablement in 12.04.4 Status in “bbswitch” package in Ubuntu: Invalid Status in “nvidia-graphics-drivers-173” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-304” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-331” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: In Progress Status in “nvidia-prime” package in Ubuntu: Invalid Status in “nvidia-settings” package in Ubuntu: In Progress Status in “screen-resolution-extra” package in Ubuntu: Invalid Status in “bbswitch” source package in Precise: In Progress Status in “nvidia-prime” source package in Precise: In Progress Status in “screen-resolution-extra” source package in Precise: In Progress Bug description: SRU request: Please accept the following packages in precise-proposed. lightdm nvidia-prime nvidia-graphics-drivers-331 nvidia-graphics-drivers-331-updates nvidia-graphics-drivers-304 nvidia-graphics-drivers-304-updates nvidia-graphics-drivers-173 nvidia-settings screen-resolution-extra bbswitch [Rationale] This is the result of the HWE effort to bring power management to systems with NVIDIA Optimus. [Impact] Without this work, we keep both GPUs on all the time, thus heavily impacting on battery life. Thanks to this work, it is now possible to easily disable the discrete card when raw power is not needed. Furthermore nvidia-prime has better hardware detection now, and won't try to enable hybrid graphics on desktop systems any more. As for the technical details: * bbswitch is a backport of the package that now lives in main in 14.04. * The actual work happened in lightdm, nvidia-331, nvidia-331-updates, nvidia-prime, screen-resolution-extra, and nvidia-settings. * nvidia-settings now replaces all the different nvidia-settings flavours, so as to reduce the maintainance effort. I patched the app so that it checks the driver version (at runtime) and doesn't expose features that older driver releases do not support. * nvidia-331 and nvidia-331-updates replace 319 and 319-updates. These are the new LTS releases by NVIDIA. * nvidia-304 and nvidia-304-updates recommend the new nvidia-settings, include a security update, and build against the upcoming Linux 3.11 (lts-saucy). * nvidia-173, in addition to being compatible with Linux 3.11 (lts-saucy), also introduces transitional packages for 173-updates, as it doesn't make sense to maintain a separate -updates flavour any more. [Test Case] After installing the update, users should be able to boot the system as usual, with no regressions of any kind. * Systems with a single NVIDIA card: nvidia-prime will detect the hardware and do nothing at all on unsupported systems (such as the one card use case, or the desktop use case) * Systems with NVIDIA Optimus: nvidia-prime will preserve its previous behaviour by leaving both GPUs on. Users can launch nvidia-settings and switch to the power profile that they need. [Regression Potential] Low. The new features are enabled only if the user manually selects them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1259237/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1212425] Re: SDK applications require /tmp access with nvidia (should honor TMPDIR)
** Branch linked: lp:ubuntu/precise-proposed/nvidia-graphics- drivers-304-updates -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-319 in Ubuntu. https://bugs.launchpad.net/bugs/1212425 Title: SDK applications require /tmp access with nvidia (should honor TMPDIR) Status in “apparmor-easyprof-ubuntu” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-319” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-319-updates” package in Ubuntu: Fix Released Status in “apparmor-easyprof-ubuntu” source package in Saucy: Fix Released Status in “nvidia-graphics-drivers-319” source package in Saucy: Triaged Status in “nvidia-graphics-drivers-319-updates” source package in Saucy: Fix Released Status in “nvidia-graphics-drivers-tegra” source package in Saucy: Invalid Status in “nvidia-graphics-drivers-tegra3” source package in Saucy: Invalid Bug description: Nvidia desktop users need the following AppArmor permissions to avoid denials: owner /tmp/gl* mrw, But this rule breaks application confinement such that apps are able to tamper with each other. Interestingly, apps still run without the rule, so we can explicitly deny it for now. The use of /tmp is apparently hardcoded and does not honor TMPDIR (application confinement will setup TMPDIR to a private area for the app). strace confirms this: 24603 mkdir(/tmp, 0777) = -1 EEXIST (File exists) 24603 open(/tmp/glBRPYmm, O_RDWR|O_CREAT|O_EXCL, 0600) = -1 EACCES (Permission denied) While the use of O_EXCL is safe, we don't allow access to /tmp for confined apps and libraries/applications should always honor TMPDIR. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor-easyprof-ubuntu/+bug/1212425/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1236945] Re: 32-bit vdpau acceleration not available
** Branch linked: lp:ubuntu/precise-proposed/nvidia-graphics- drivers-304-updates -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-319 in Ubuntu. https://bugs.launchpad.net/bugs/1236945 Title: 32-bit vdpau acceleration not available Status in “nvidia-graphics-drivers-319” package in Ubuntu: In Progress Bug description: On a 64-bit Ubuntu 12.04 system, a 32-bit application doesn't find the NVIDIA VDPAU accelerated driver in /usr/lib32 by default. I discussed this with Alberto Milone, and he writes: The fix is trivial. It's just a matter of adding the /usr/lib32/ path in /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf (or in /etc/ld.so.conf.d/i386-linux-gnu_GL.conf). Here's what ldconfig currently says in my chroot: # ldconfig -p | grep pau libvdpau_nvidia.so (libc6,x86-64, OS ABI: Linux 2.3.99) = /usr/lib/libvdpau_nvidia.so libvdpau.so.1 (libc6,x86-64) = /usr/lib/x86_64-linux-gnu/libvdpau.so.1 This is what I get after I add the line that I mentioned: # ldconfig -p | grep pau libvdpau_nvidia.so (libc6,x86-64, OS ABI: Linux 2.3.99) = /usr/lib/libvdpau_nvidia.so libvdpau_nvidia.so (libc6, OS ABI: Linux 2.3.99) = /usr/lib32/libvdpau_nvidia.so libvdpau.so.1 (libc6,x86-64) = /usr/lib/x86_64-linux-gnu/libvdpau.so.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-319/+bug/1236945/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1200277] Re: [LibreOffice] - libreoffice-writer.desktop when drag/drop to desktop, 100% broken.
** Patch added: proposed patch for trusty https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1200277/+attachment/3931815/+files/lo-shortcut.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1200277 Title: [LibreOffice] - libreoffice-writer.desktop when drag/drop to desktop, 100% broken. Status in Desktop panel for GNOME: Invalid Status in “libreoffice” package in Ubuntu: New Bug description: Attempting to drag and drop within gnome-session-fallback (to create a desktop shortcut) creates a broken link. I was able to test and validate this appears in 12.04.2+current updates, 13.04+current updates and also 13.10-Daily. Please see attached screenshots. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-panel/+bug/1200277/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1200277] Re: [LibreOffice] - libreoffice-writer.desktop when drag/drop to desktop, 100% broken.
gnome-panel is deprecated. Will focus the fix on lo, to copy the desktop entry rather than symlink to create a trusted link. ** Changed in: gnome-panel Status: New = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1200277 Title: [LibreOffice] - libreoffice-writer.desktop when drag/drop to desktop, 100% broken. Status in Desktop panel for GNOME: Invalid Status in “libreoffice” package in Ubuntu: New Bug description: Attempting to drag and drop within gnome-session-fallback (to create a desktop shortcut) creates a broken link. I was able to test and validate this appears in 12.04.2+current updates, 13.04+current updates and also 13.10-Daily. Please see attached screenshots. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-panel/+bug/1200277/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1251369] Re: [Lenovo ThinkPad X220 Tablet] Disable while typing does not disable touchpad completely (only scrolling)
I have tried the daily image in a virtual machine (VirtualBox). The setting to control the touchpad is not available in the Mouse and Touchpad settings there. Is it supposed to be there, and the touchpad just does not get detected in the VM? (at least this is what appears to be the case for the Wacom Tablet settings) Let me know, if I need to test it from a Live stick directly on the host. OTOH, I got used to not using tap to click now, and therefore my interest in getting this fixed/debugged is rather low. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1251369 Title: [Lenovo ThinkPad X220 Tablet] Disable while typing does not disable touchpad completely (only scrolling) Status in “xorg” package in Ubuntu: Incomplete Bug description: The Disable while typing option in the Mouse and Touchpad settings only work for scrolling, but not the regular movement of the pointer. To reproduce: 1. enable the option 2. Open a window where you can type (editor, terminal) 3. type with one hand constantly, and move the mouse pointer with the other one The mouse pointer should not move, but does for me. When two-finger scrolling instead, this gets blocked successfully while typing. This is with Ubuntu 13.10 on a Lenovo X220t. (The touchscreen appears to be completely unaffected by this setting (you can scroll while typing), but that is OK.) According to the documentation (https://help.ubuntu.com/community/SynapticsTouchpad#Disabling_Touchpad_while_Typing) I have now also disabled Tap to click, which works around the main annoyance of this: accidentally clicking with the palm/part of your hand while typing - the pointer can still be moved. --- .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,resize,compiztoolbox,put,vpswitch,snap,mousepoll,regex,place,session,move,grid,animation,imgpng,wall,expo,unitymtgrabhandles,workarounds,ezoom,staticswitcher,fade,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true DistUpgraded: 2013-10-08 21:37:21,390 DEBUG enabling apt cron job DistroCodename: saucy DistroRelease: Ubuntu 13.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21db] InstallationDate: Installed on 2012-05-28 (567 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MachineType: LENOVO 42992PG MarkForUpload: True Package: xorg 1:7.7+1ubuntu6 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-14-generic root=/dev/mapper/vg0-rootlv ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Tags: saucy ubuntu compiz-0.9 Uname: Linux 3.11.0-14-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-10-08 (70 days ago) UserGroups: adm cdrom davfs2 dip docker fuse lastfm libvirtd lpadmin plugdev sambashare sudo www-data dmi.bios.date: 04/11/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET68WW (1.38 ) dmi.board.asset.tag: Not Available dmi.board.name: 42992PG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET68WW(1.38):bd04/11/2013:svnLENOVO:pn42992PG:pvrThinkPadX220Tablet:rvnLENOVO:rn42992PG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 42992PG dmi.product.version: ThinkPad X220 Tablet dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs 1:0.5 version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Mon Dec 16 17:08:49 2013 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 728 vendor LGD xserver.version: 2:1.14.3-3ubuntu2 To manage notifications about this bug go to:
[Desktop-packages] [Bug 107854]
Bug are still here T_T Tested on Ubuntu 12.04 x86_64: LibreOffice 4.2.0.0.beta2 (Build ID: 1a27be92e320f97c20d581a69ef1c8b99ea9885d ) and LibreOffice 4.1.4.2 (Build ID: 0a0440ccc0227ad9829de5f46be37cfb6edcf72) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/107854 Title: [upstream] Impress shows black underline in Slide Show despite colored underline Status in LibreOffice Productivity Suite: Confirmed Status in The OpenOffice.org Suite: Confirmed Status in “libreoffice” package in Ubuntu: Triaged Status in “openoffice.org” package in Ubuntu: Won't Fix Bug description: Binary package hint: openoffice.org-impress 1) lsb_release -rd Description: Ubuntu 11.04 Release: 11.04 2) apt-cache policy libreoffice-impress libreoffice-impress: Installed: 1:3.3.2-1ubuntu5 Candidate: 1:3.3.2-1ubuntu5 Version table: *** 1:3.3.2-1ubuntu5 0 500 http://us.archive.ubuntu.com/ubuntu/ natty-updates/main i386 Packages 100 /var/lib/dpkg/status 1:3.3.2-1ubuntu4 0 500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages OOo 2.x Impress (19.04.07) 3) What is expected to happen in LibreOffice Impress via the Terminal: cd ~/Desktop wget https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/107854/+attachment/2143745/+files/underline.odp loimpress -nologo underline.odp the text with colored underlines should remain colored in Slide Show. 4) What happens instead is the underlines are black in Slide Show. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/107854/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 192056]
May http://opengrok.libreoffice.org/xref/core/sw/source/filter/ww8/ww8par.cxx#5563 be an example to follow? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/192056 Title: [Upstream] [hardy] Cannot Open password-encrypted MS Office 2003 files Status in LibreOffice Productivity Suite: Confirmed Status in The OpenOffice.org Suite: Confirmed Status in “libreoffice” package in Ubuntu: Won't Fix Status in “openoffice.org” package in Ubuntu: Won't Fix Bug description: Binary package hint: openoffice.org2 1) lsb_release -rd Description:Ubuntu 11.04 Release:11.04 2) apt-cache policy libreoffice-impress libreoffice-impress: Installed: 1:3.3.2-1ubuntu5 Candidate: 1:3.3.2-1ubuntu5 Version table: *** 1:3.3.2-1ubuntu5 0 500 http://us.archive.ubuntu.com/ubuntu/ natty-proposed/main i386 Packages 100 /var/lib/dpkg/status 1:3.3.2-1ubuntu4 0 500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages 3) What is expected to happen using LibreOffice Impress via the Terminal: cd ~/Desktop wget https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/192056/+attachment/2125234/+files/B2R%20Veranstaltungen%202004%20Thomas%20Berger%20CP-F.ppt loimpress -nologo B2R\ Veranstaltungen\ 2004\ Thomas\ Berger\ CP-F.ppt and one is prompted for the password. 4) What happens instead is a window pops up noting: LibreOffice 3.3 Read-Error. The Loading of password-encrypted Microsoft PowerPoint presentation is not supported. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/192056/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 496231] Re: copy file from smb share directly to bluetooth obex device
** Changed in: gvfs Status: New = Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/496231 Title: copy file from smb share directly to bluetooth obex device Status in GVFS: Incomplete Status in “gvfs” package in Ubuntu: Triaged Bug description: Binary package hint: yelp when i try directly copieng a file from an smb or ssh share to an obex bluetooth mobile phone i get the followed error message: Vorgang wird vom Backend nicht unterstützt Fehler beim Kopieren nach obex://[] Speicherkarte ist ein Fehler aufgetreten Vorgang wird vom Backend nicht unterstützt ProblemType: Bug Architecture: i386 CheckboxSubmission: b85ac3dab8e04d09f8dbd07a90a2b237 CheckboxSystem: b62ae224500b03a9fc2c9b6caf3feb14 Date: Sun Dec 13 17:52:27 2009 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/bin/yelp InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5) Package: yelp 2.28.0-0ubuntu2 ProcEnviron: PATH=(custom, user) LANG=de_AT.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-16.53-generic SourcePackage: yelp Uname: Linux 2.6.31-16-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/496231/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1262104] Re: fglrx 2:8.960-0ubuntu1: fglrx kernel module failed to build
Why are you trying to install fglrx in a VM? Virtualbox uses its own virtual graphics adapter and fglrx will only bork it. ** Changed in: fglrx-installer (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1262104 Title: fglrx 2:8.960-0ubuntu1: fglrx kernel module failed to build Status in “fglrx-installer” package in Ubuntu: Incomplete Bug description: How can it get fixed? Because I need this for my study. Cheers ProblemType: Package DistroRelease: Ubuntu 12.04 Package: fglrx 2:8.960-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic i686 .tmp.unity.support.test.0: .tmp.unity.support.test.1: ApportVersion: 2.0.1-0ubuntu17.4 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz DKMSBuildLog: DKMS make.log for fglrx-8.960 for kernel 3.8.0-29-generic (i686) Wed Dec 18 16:34:06 WST 2013 AMD kernel module generator version 2.1 kernel includes at /lib/modules/3.8.0-29-generic/build/include not found or incomplete file: /lib/modules/3.8.0-29-generic/build/include/linux/version.h DKMSKernelVersion: 3.8.0-29-generic Date: Wed Dec 18 16:34:13 2013 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu DkmsStatus: fglrx, 8.960: added DuplicateSignature: DKMS make.log for fglrx-8.960 for kernel 3.8.0-29-generic (i686) AMD kernel module generator version 2.1 kernel includes at /lib/modules/3.8.0-29-generic/build/include not found or incomplete file: /lib/modules/3.8.0-29-generic/build/include/linux/version.h GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release i386 (20130820.1) Lsusb: Bus 001 Device 003: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox MarkForUpload: True PackageVersion: 2:8.960-0ubuntu1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-29-generic root=UUID=8e17e54d-6593-493c-ab47-fd361a5d0762 ro quiet splash vt.handoff=7 Renderer: Software SourcePackage: fglrx-installer Title: fglrx 2:8.960-0ubuntu1: fglrx kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH make.log: DKMS make.log for fglrx-8.960 for kernel 3.8.0-29-generic (i686) Wed Dec 18 16:34:06 WST 2013 AMD kernel module generator version 2.1 kernel includes at /lib/modules/3.8.0-29-generic/build/include not found or incomplete file: /lib/modules/3.8.0-29-generic/build/include/linux/version.h version.compiz: compiz 1:0.9.7.12-0ubuntu2 version.libdrm2: libdrm2 2.4.43-0ubuntu0.0.3 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1262104/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1202190] Re: upgrade xscreensaver to latest version
*** This bug is a duplicate of bug 1261863 *** https://bugs.launchpad.net/bugs/1261863 ** This bug has been marked a duplicate of bug 1261863 Update xscreensaver to the latest version -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xscreensaver in Ubuntu. https://bugs.launchpad.net/bugs/1202190 Title: upgrade xscreensaver to latest version Status in “xscreensaver” package in Ubuntu: Triaged Status in “xscreensaver” package in Debian: Fix Released Bug description: The latest version is 5.22 as released on 16 July 2013 as opposed to 5.15 in raring released on 14 July 2011. Please confer: http://www.jwz.org/blog/2013/07/xscreensaver-5-22/ ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: xscreensaver 5.15-2ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2 Uname: Linux 3.8.0-26-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Wed Jul 17 15:10:07 2013 InstallationDate: Installed on 2013-06-14 (32 days ago) InstallationMedia: Ubuntu-GNOME 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: xscreensaver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+bug/1202190/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1261863] Re: Update xscreensaver to the latest version
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xscreensaver (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xscreensaver in Ubuntu. https://bugs.launchpad.net/bugs/1261863 Title: Update xscreensaver to the latest version Status in “xscreensaver” package in Ubuntu: Triaged Bug description: Please update xscreensaver to the latest version in Ubuntu 14.04. This would fix at least Bug #103975 and maybe some more. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xscreensaver 5.15-3ubuntu1 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.12.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Dec 17 19:11:37 2013 InstallationDate: Installed on 2013-12-16 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131216) SourcePackage: xscreensaver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+bug/1261863/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1261863] Re: Update xscreensaver to the latest version
** Changed in: xscreensaver (Ubuntu) Importance: Undecided = Wishlist ** Changed in: xscreensaver (Ubuntu) Status: Confirmed = Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xscreensaver in Ubuntu. https://bugs.launchpad.net/bugs/1261863 Title: Update xscreensaver to the latest version Status in “xscreensaver” package in Ubuntu: Triaged Bug description: Please update xscreensaver to the latest version in Ubuntu 14.04. This would fix at least Bug #103975 and maybe some more. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xscreensaver 5.15-3ubuntu1 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.12.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Dec 17 19:11:37 2013 InstallationDate: Installed on 2013-12-16 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20131216) SourcePackage: xscreensaver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+bug/1261863/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1246929] Re: no audio in KVM virtual machines : cannot select alsa or pa
http://libvirt.org/git/?p=libvirt.git;a=commit;h=a216e6487255d3b65d97c7ec1fa5da63dbced902 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1246929 Title: no audio in KVM virtual machines : cannot select alsa or pa Status in “libvirt” package in Ubuntu: Confirmed Status in “pulseaudio” package in Ubuntu: New Status in “virt-manager” package in Ubuntu: Confirmed Bug description: I am on Ubuntu 13.10 desktop 16GB ram asus sabertooth 990fx r2.0 motherboard amd 8346 cpu nvidia gtx650 video card Since upgrading to Ubuntu 13.10 audio no longer works in KVM. Checking SYSLOG I found this error being logged: Oct 31 15:32:31 bmullan-virtual-machine pulseaudio[1814]: [alsa-source-ID 21 Analog] alsa-source.c: ALSA woke us up to read new data from the device, but there was actually nothing to read! Oct 31 15:32:31 bmullan-virtual-machine pulseaudio[1814]: [alsa-source-ID 21 Analog] alsa-source.c: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers. Oct 31 15:32:31 bmullan-virtual-machine pulseaudio[1814]: [alsa-source-ID 21 Analog] alsa-source.c: We were woken up with POLLIN set -- however a subsequent snd_pcm_avail() returned 0 or another value min_avail. brian ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Thu Oct 31 19:45:53 2013 InstallationDate: Installed on 2013-10-31 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20131003) MarkForUpload: True PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1708 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH 990FX R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1708:bd04/09/2013:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FXR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1246929/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Ubuntu-elisp] [Bug 1059633] Re: Emacs 'Ediff' Window Shrinks Horizontally To One Column Wide
On Dec 18, 2013, at 10:07 AM, Kasim Tasdemir wrote: The problem still persists for me. I use Ubuntu 14.04 (development branch) + emacs 23 . More precisely: GNU Emacs 23.4.1 (i686-pc-linux-gnu, GTK+ Version 2.24.21) of 2013-10-25 on akateko, modified by Debian You might consider upgrading to Emacs 24.3. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to emacs24 in Ubuntu. https://bugs.launchpad.net/bugs/1059633 Title: Emacs 'Ediff' Window Shrinks Horizontally To One Column Wide Status in “compiz” package in Ubuntu: Invalid Status in “emacs23” package in Ubuntu: Confirmed Status in “emacs24” package in Ubuntu: Fix Released Status in “compiz” source package in Precise: Invalid Status in “emacs23” source package in Precise: Fix Released Status in “emacs24” source package in Precise: Invalid Status in “compiz” source package in Raring: Invalid Status in “emacs23” source package in Raring: Confirmed Status in “emacs24” source package in Raring: Fix Released Bug description: [Impact] Emacs users can't access the help screen for the ediff tool. [Test case] (For non emacsy people) Run emacs in a graphical environment Menu option: Tools-Compare-Two Buffers ENTER and ENTER to the two questions prompted A new window, 'Ediff', opens and contains the text Type ? for help In the 'Ediff' window, type the character '?', This is supposed to display helpful info on the ediff commands If broken: Ediff window will expand, then shrink horizontally to one character wide Grabbing the frame and resizing will cause the shrinking behavior to repeat If fixed: Ediff window will expand and show the contents of the help [Regression potential] It could be that some other graphical environment relies on the bug being present, working around it in a way that if it's not present anymore, the window resizing will break there. The current patch is tested for Unity and Cinnamon, and has been taken from the fix already applied upstream. [Original description] Unlike previously reported bug #941790, this bug involves a horizontal shrinkage to one column wide (multiple rows), and is still present in GNU Emacs 23.3.1. Resizing the window isn't a work-around, as the window immediately shrinks again. The behavior is observed as follows: Run ediff-buffers A new window, 'Ediff', opens and contains the text Type ? for hlep In the 'Ediff' window, type the character '?', This is supposed to display helpful info on the ediff commands Ediff window will expand, then shrink horizontally to one character wide Grabbing the frame and reszing will cause the shrinking behavior to repeat Releveant packages / versions: Ubuntu 12.04.1 LTS GNU Emacs 23.3.1 Unity 5.16.0-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1059633/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1260957] Re: Libreoffice Impress crashes when inserting an image
*** This bug is a duplicate of bug 1261040 *** https://bugs.launchpad.net/bugs/1261040 ** This bug has been marked a duplicate of private bug 1261040 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1260957 Title: Libreoffice Impress crashes when inserting an image Status in “libreoffice” package in Ubuntu: Invalid Bug description: I'm using Impress in LibreOffice 4.1.3.2 and Kubuntu 13.10 (KDE4). Sometimes, randomly, when I'm preparing a presentation and just try to insert an image, the program crashes after choosing the file in the file dialog, or in the moment that the file dialog opens. The version of my libreoffice-kde (the package I suspect this is related with), is 1:4.1.3-0ubuntu1 I've followed some instructions found in the web and I'm using the LibreOffice dialogs, which are ugly compared to KDE UI. As I've read this post about Gentoo, and maybe it helps: http://dilfridge.blogspot.com.es/2013/12/libreoffice-kde-integration.html it would be great if Kubuntu/Ubuntu team integrates this, or solves the annoying crash bug in any other way. Thanks a lot in advance for your so good work ;) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1260957/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1259237] Re: Hybrid graphics enablement in 12.04.4
** Also affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Changed in: lightdm (Ubuntu) Importance: Undecided = Medium ** Changed in: lightdm (Ubuntu) Status: New = In Progress ** Changed in: lightdm (Ubuntu) Milestone: None = ubuntu-12.04.4 ** Changed in: lightdm (Ubuntu) Assignee: (unassigned) = Alberto Milone (albertomilone) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-304-updates in Ubuntu. https://bugs.launchpad.net/bugs/1259237 Title: Hybrid graphics enablement in 12.04.4 Status in “bbswitch” package in Ubuntu: Invalid Status in “lightdm” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-173” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-304” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-331” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: In Progress Status in “nvidia-prime” package in Ubuntu: Invalid Status in “nvidia-settings” package in Ubuntu: In Progress Status in “screen-resolution-extra” package in Ubuntu: Invalid Status in “bbswitch” source package in Precise: In Progress Status in “nvidia-prime” source package in Precise: In Progress Status in “screen-resolution-extra” source package in Precise: In Progress Bug description: SRU request: Please accept the following packages in precise-proposed. lightdm nvidia-prime nvidia-graphics-drivers-331 nvidia-graphics-drivers-331-updates nvidia-graphics-drivers-304 nvidia-graphics-drivers-304-updates nvidia-graphics-drivers-173 nvidia-settings screen-resolution-extra bbswitch [Rationale] This is the result of the HWE effort to bring power management to systems with NVIDIA Optimus. [Impact] Without this work, we keep both GPUs on all the time, thus heavily impacting on battery life. Thanks to this work, it is now possible to easily disable the discrete card when raw power is not needed. Furthermore nvidia-prime has better hardware detection now, and won't try to enable hybrid graphics on desktop systems any more. As for the technical details: * bbswitch is a backport of the package that now lives in main in 14.04. * The actual work happened in lightdm, nvidia-331, nvidia-331-updates, nvidia-prime, screen-resolution-extra, and nvidia-settings. * nvidia-settings now replaces all the different nvidia-settings flavours, so as to reduce the maintainance effort. I patched the app so that it checks the driver version (at runtime) and doesn't expose features that older driver releases do not support. * nvidia-331 and nvidia-331-updates replace 319 and 319-updates. These are the new LTS releases by NVIDIA. * nvidia-304 and nvidia-304-updates recommend the new nvidia-settings, include a security update, and build against the upcoming Linux 3.11 (lts-saucy). * nvidia-173, in addition to being compatible with Linux 3.11 (lts-saucy), also introduces transitional packages for 173-updates, as it doesn't make sense to maintain a separate -updates flavour any more. [Test Case] After installing the update, users should be able to boot the system as usual, with no regressions of any kind. * Systems with a single NVIDIA card: nvidia-prime will detect the hardware and do nothing at all on unsupported systems (such as the one card use case, or the desktop use case) * Systems with NVIDIA Optimus: nvidia-prime will preserve its previous behaviour by leaving both GPUs on. Users can launch nvidia-settings and switch to the power profile that they need. [Regression Potential] Low. The new features are enabled only if the user manually selects them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1259237/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1206760] Re: Zenity text windows too tall with long text
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: zenity (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to zenity in Ubuntu. https://bugs.launchpad.net/bugs/1206760 Title: Zenity text windows too tall with long text Status in “zenity” package in Ubuntu: Confirmed Bug description: It seems that with many versions of zenity 3.60 and below, 3 of the text type dialogs ( --info --warning --error ) have significant sizing issues with text wrapping enabled. Long strings of text seem to cause extreemly tall dialogs such as this first example zenity --info --text Hello there friends. Hello there friends. Hello there friends. Hello there friends. d d d d d d d d d d d dd asdfsadf sdf sad fas dfas dfas df a adsfasfas one workaround might be to turn off wrapping zenity --info --text Hello there friends. Hello there friends. Hello there friends. Hello there friends. d d d d d d d d d d d dd asdfsadf sdf sad fas dfas dfas df a adsfasfas --no-wrap but this can cause dialogs to be too large vertically I noticed that by forcing the minimal width as so, (I pass 1, but it seems that zenity uses a hardcoded minimum) zenity --info --text Hello there friends. Hello there friends. Hello there friends. Hello there friends. d d d d d d d d d d d dd asdfsadf sdf sad fas dfas dfas df a adsfasfas --width=1 the height of the dialog seems to be the same as the first example. However, with the skinny dialog, the full dialog is used, and the text is wrapped much better. Therefore, my guess is that when text wrapping is enabled (which it is by default) for --info --warning and --error Zenity is wrapping the text with the hardcoded minimal width, and calculating the needed height for wrapping the text with the minimal width. However, zenity usually later on uses a different much wider width when the dialog is displayed, which therefore causes the text wrapping to use less height. However zenity still ends up setting the height of the window to what it would need to be to fit the text if the window was the minimal width, in cases causing excessivly large and tall zenity windows. This is just my guess from what I can see. dialogs with --question seem to be sized a bit more sanely. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zenity/+bug/1206760/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1259237] Re: Hybrid graphics enablement in 12.04.4
Hello Alberto, or anyone else affected, Accepted screen-resolution-extra into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source /screen-resolution-extra/0.14ubuntu2.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: screen-resolution-extra (Ubuntu Precise) Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1259237 Title: Hybrid graphics enablement in 12.04.4 Status in “bbswitch” package in Ubuntu: Invalid Status in “lightdm” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-173” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-304” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-331” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: In Progress Status in “nvidia-prime” package in Ubuntu: Invalid Status in “nvidia-settings” package in Ubuntu: In Progress Status in “screen-resolution-extra” package in Ubuntu: Invalid Status in “bbswitch” source package in Precise: In Progress Status in “nvidia-prime” source package in Precise: In Progress Status in “screen-resolution-extra” source package in Precise: Fix Committed Bug description: SRU request: Please accept the following packages in precise-proposed. lightdm nvidia-prime nvidia-graphics-drivers-331 nvidia-graphics-drivers-331-updates nvidia-graphics-drivers-304 nvidia-graphics-drivers-304-updates nvidia-graphics-drivers-173 nvidia-settings screen-resolution-extra bbswitch [Rationale] This is the result of the HWE effort to bring power management to systems with NVIDIA Optimus. [Impact] Without this work, we keep both GPUs on all the time, thus heavily impacting on battery life. Thanks to this work, it is now possible to easily disable the discrete card when raw power is not needed. Furthermore nvidia-prime has better hardware detection now, and won't try to enable hybrid graphics on desktop systems any more. As for the technical details: * bbswitch is a backport of the package that now lives in main in 14.04. * The actual work happened in lightdm, nvidia-331, nvidia-331-updates, nvidia-prime, screen-resolution-extra, and nvidia-settings. * nvidia-settings now replaces all the different nvidia-settings flavours, so as to reduce the maintainance effort. I patched the app so that it checks the driver version (at runtime) and doesn't expose features that older driver releases do not support. * nvidia-331 and nvidia-331-updates replace 319 and 319-updates. These are the new LTS releases by NVIDIA. * nvidia-304 and nvidia-304-updates recommend the new nvidia-settings, include a security update, and build against the upcoming Linux 3.11 (lts-saucy). * nvidia-173, in addition to being compatible with Linux 3.11 (lts-saucy), also introduces transitional packages for 173-updates, as it doesn't make sense to maintain a separate -updates flavour any more. [Test Case] After installing the update, users should be able to boot the system as usual, with no regressions of any kind. * Systems with a single NVIDIA card: nvidia-prime will detect the hardware and do nothing at all on unsupported systems (such as the one card use case, or the desktop use case) * Systems with NVIDIA Optimus: nvidia-prime will preserve its previous behaviour by leaving both GPUs on. Users can launch nvidia-settings and switch to the power profile that they need. [Regression Potential] Low. The new features are enabled only if the user manually selects them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1259237/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1261936] Re: Nimbus Sans L font metrics messed up in LibreOffice
Funter Ohrner, thank you for performing the requested apport-collect. Could you please attach an example document that demonstrates this problem, along with a screenshot of the problem? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1261936 Title: Nimbus Sans L font metrics messed up in LibreOffice Status in “libreoffice” package in Ubuntu: Incomplete Bug description: Regression in Saucy Salamander 13.10, worked fine in 13.04 and previous releases. Affects LibreOffice Writer (Other Libre Office modules not tested so far.) (At least) Nimbus Sans L font rendering and cursor positioning in texts is messed up, the letters look slightly distorted, letter spacing is incorrect with even partially overlapping letters and the cursor positioning in a line of text does not always match the actual editing position. Wrong font rendering also effects PDF files generated with LibreOffice writer in Saucy. Nimbus Sans L font rendering looks fine in kCharSelect. PDFs generated before the update also are not affected and are rendered fine by Okular. --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 DistroRelease: Ubuntu 13.10 MarkForUpload: True Package: libreoffice 1:4.1.3-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Tags: saucy Uname: Linux 3.11.0-14-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-12-17 (0 days ago) UserGroups: adm admin cdrom davfs2 dialout disk lp lpadmin plugdev sambashare www-data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1261936/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1108610] Re: Please provide vala bindings.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: telepathy-logger (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to telepathy-logger in Ubuntu. https://bugs.launchpad.net/bugs/1108610 Title: Please provide vala bindings. Status in “telepathy-logger” package in Ubuntu: Confirmed Bug description: Dear Maintainer, Please provide vala bindings for telepathy-logger. Currently we have gir file. It is easy to generate vala bindings from the gir file by vapigen. For example, vapigen --library=telepathy-logger-0.2 --pkg=telepathy-glib --vapidir=. /usr/share/gir-1.0/TelepathyLogger-0.2.gir generates the .vapi file. Yours, Paul To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telepathy-logger/+bug/1108610/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1187483] Re: wireless wpa2/enterprise authentication issues
Confirm this bug in Xubuntu 13.10 (no surprise, as Ubuntu 13.10 is affected), and the workaround in https://bugs.launchpad.net/linuxmint/+bug/1187483/comments/3 is working for me as well. -- 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/1187483 Title: wireless wpa2/enterprise authentication issues Status in The Linux Mint Distribution: Confirmed Status in “network-manager” package in Ubuntu: New Bug description: Using Linux Mint 15 and trying to connect to wireless ssid with wpa2/enterprise certificate authentication. When I create the key file with openssl I enter the private key password. When trying to access the wireless with this key and certificate it keeps asking for this password when trying to authenticate. It should except my private key password and connect me to wireless. This same setup worked on Ubuntu 11.04 for me (this is the distro I was on before I switched to Mint 15) and another user has verified wpa2/enterprise working with Linux Mint 14. This issues happens always as I have not been able to get it to connect using wpa2/enterprise with certificates. To reproduce it you will need to setup wpa2/enterprise wireless and try to authenticate or I can test anything you need or provide output. Please see some more details from the blog at: http://forum.linuxmint.com/viewtopic.php?f=53t=135462sid=f4d7b54f0acd39937a54b4527ce4afa5 Thanks and let me know if you need me to try anything else. Dusty To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1187483/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1262199] [NEW] Disk Usage thinks screen is 3000 pixels or so wide
Public bug reported: See attached. I'm unable to horizontally resize the window. The grab bar is available, but dragging does nothing. Perhaps it would be a good idea to make sure the Disk Usage window is no wider than the actual screen. $ lsb_release -rd Description:Ubuntu 13.10 Release:13.10 My apologies if this is is misfiled. I have two programs running related to disks, and neither are listed in the Choose Package search: $ ps -A | grep -i disk 2024 ?00:00:00 gvfs-udisks2-vo 2033 ?00:00:00 udisksd When I tried to file against, for example, udisks, I received There is 1 error. with no feedback on what the error is/was. I think this website is broken. Sigh... ** Affects: deja-dup (Ubuntu) Importance: Undecided Status: New ** Tags: disk screen usage width window -- 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/1262199 Title: Disk Usage thinks screen is 3000 pixels or so wide Status in “deja-dup” package in Ubuntu: New Bug description: See attached. I'm unable to horizontally resize the window. The grab bar is available, but dragging does nothing. Perhaps it would be a good idea to make sure the Disk Usage window is no wider than the actual screen. $ lsb_release -rd Description: Ubuntu 13.10 Release: 13.10 My apologies if this is is misfiled. I have two programs running related to disks, and neither are listed in the Choose Package search: $ ps -A | grep -i disk 2024 ?00:00:00 gvfs-udisks2-vo 2033 ?00:00:00 udisksd When I tried to file against, for example, udisks, I received There is 1 error. with no feedback on what the error is/was. I think this website is broken. Sigh... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1262199/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1251369] Re: [Lenovo ThinkPad X220 Tablet] Disable while typing does not disable touchpad completely (only scrolling)
Daniel Hahler, could you please ensure all current and future testing is done on the host? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1251369 Title: [Lenovo ThinkPad X220 Tablet] Disable while typing does not disable touchpad completely (only scrolling) Status in “xorg” package in Ubuntu: Incomplete Bug description: The Disable while typing option in the Mouse and Touchpad settings only work for scrolling, but not the regular movement of the pointer. To reproduce: 1. enable the option 2. Open a window where you can type (editor, terminal) 3. type with one hand constantly, and move the mouse pointer with the other one The mouse pointer should not move, but does for me. When two-finger scrolling instead, this gets blocked successfully while typing. This is with Ubuntu 13.10 on a Lenovo X220t. (The touchscreen appears to be completely unaffected by this setting (you can scroll while typing), but that is OK.) According to the documentation (https://help.ubuntu.com/community/SynapticsTouchpad#Disabling_Touchpad_while_Typing) I have now also disabled Tap to click, which works around the main annoyance of this: accidentally clicking with the palm/part of your hand while typing - the pointer can still be moved. --- .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,resize,compiztoolbox,put,vpswitch,snap,mousepoll,regex,place,session,move,grid,animation,imgpng,wall,expo,unitymtgrabhandles,workarounds,ezoom,staticswitcher,fade,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true DistUpgraded: 2013-10-08 21:37:21,390 DEBUG enabling apt cron job DistroCodename: saucy DistroRelease: Ubuntu 13.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21db] InstallationDate: Installed on 2012-05-28 (567 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MachineType: LENOVO 42992PG MarkForUpload: True Package: xorg 1:7.7+1ubuntu6 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-14-generic root=/dev/mapper/vg0-rootlv ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Tags: saucy ubuntu compiz-0.9 Uname: Linux 3.11.0-14-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-10-08 (70 days ago) UserGroups: adm cdrom davfs2 dip docker fuse lastfm libvirtd lpadmin plugdev sambashare sudo www-data dmi.bios.date: 04/11/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET68WW (1.38 ) dmi.board.asset.tag: Not Available dmi.board.name: 42992PG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET68WW(1.38):bd04/11/2013:svnLENOVO:pn42992PG:pvrThinkPadX220Tablet:rvnLENOVO:rn42992PG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 42992PG dmi.product.version: ThinkPad X220 Tablet dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs 1:0.5 version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Mon Dec 16 17:08:49 2013 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 728 vendor LGD xserver.version: 2:1.14.3-3ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1251369/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1261351]
Well, bug 678345 would fix it.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1261351
Title:
Save All for same-named attachments defaults to only one saved file
Status in Mozilla Thunderbird Mail and News:
Confirmed
Status in “thunderbird” package in Ubuntu:
New
Bug description:
thunderbird 1:24.2.0+build1-0ubuntu0.13.10.1, Ubuntu 13.10
1. Send yourself a message containing more than one attachment with the same
filename, e.g. image.jpeg.
2. Open the message in Thunderbird, and choose Save All.
3. Select a folder to save the attachments in, and choose Open [sic].
What happens: For n attachments, n–1 Confirm alerts appear with the
text: {pathname} already exists. Do you want to replace it?
If you choose Cancel, a Save Attachment dialog appears for
choosing a different path/filename.
But the default is OK, and if you choose that each attachment
overwrites the previous one, something that nobody would ever want.
To manage notifications about this bug go to:
https://bugs.launchpad.net/thunderbird/+bug/1261351/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1239151] Re: nmcli Segmentation fault (core dumped)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New = Confirmed -- 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/1239151 Title: nmcli Segmentation fault (core dumped) Status in “network-manager” package in Ubuntu: Confirmed Bug description: command /usr/bin/nmcli dev list terminates unexpectedly with a error Segmentation fault (core dumped) @jupiter:~$ nmcli dev list GENERAL.DEVICE: ttyUSB1 GENERAL.TYPE: gsm GENERAL.VENDOR: Qualcomm Incorporated GENERAL.PRODUCT:HP un2420 Mobile Broadband Module GENERAL.DRIVER: qcserial . . . IP6.DNS[1]: fd00::c225:6ff:fe4e:1582 GENERAL.DEVICE: eth0 GENERAL.TYPE: 802-3-ethernet GENERAL.VENDOR: Intel Corporation GENERAL.PRODUCT:82577LM Gigabit Network Connection GENERAL.DRIVER: e1000e GENERAL.DRIVER-VERSION: 2.1.4-k GENERAL.FIRMWARE-VERSION: 0.12-3 GENERAL.HWADDR: 70:5A:B6:B1:E1:A4 GENERAL.STATE: 20 (unavailable) GENERAL.REASON: 2 (Device is now managed) GENERAL.UDI: /sys/devices/pci:00/:00:19.0/net/eth0 GENERAL.IP-IFACE: GENERAL.NM-MANAGED: yes GENERAL.AUTOCONNECT:yes GENERAL.FIRMWARE-MISSING: no GENERAL.CONNECTION: not connected CAPABILITIES.CARRIER-DETECT:yes CAPABILITIES.SPEED: unknown Segmentation fault (core dumped) @jupiter:~$ ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: network-manager 0.9.8.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8 Uname: Linux 3.8.0-31-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Sat Oct 12 17:14:06 2013 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-05-08 (156 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) IpRoute: default via 10.10.10.1 dev wlan0 proto static 10.10.10.0/24 dev wlan0 proto kernel scope link src 10.10.10.100 metric 9 169.254.0.0/16 dev wlan0 scope link metric 1000 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH ttyUSB1gsm disconnected /org/freedesktop/NetworkManager/Devices/2 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1239151/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1239151] Re: nmcli Segmentation fault (core dumped)
Got just the same effect^
nmcli d list
GENERAL.DEVICE: 00:0C:E7:B0:3D:DD
GENERAL.TYPE: bluetooth
GENERAL.VENDOR: --
GENERAL.PRODUCT:--
GENERAL.DRIVER: bluez
GENERAL.DRIVER-VERSION:
GENERAL.FIRMWARE-VERSION:
GENERAL.HWADDR: (unknown)
GENERAL.STATE: 30 (disconnected)
GENERAL.REASON: 0 (No reason given)
GENERAL.UDI:
/org/bluez/1041/hci0/dev_00_0C_E7_B0_3D_DD
GENERAL.IP-IFACE:
GENERAL.NM-MANAGED: yes
GENERAL.AUTOCONNECT:yes
GENERAL.FIRMWARE-MISSING: no
GENERAL.CONNECTION: not connected
CAPABILITIES.CARRIER-DETECT:no
CAPABILITIES.SPEED: unknown
CONNECTIONS.AVAILABLE-CONNECTION-PATHS:
/org/freedesktop/NetworkManager/Settings/{0}
CONNECTIONS.AVAILABLE-CONNECTIONS[1]: 7fb41ad4-c284-4815-98d6-7c2f51b14422 |
ThL W7 Network
GENERAL.DEVICE: wlan0
GENERAL.TYPE: 802-11-wireless
GENERAL.VENDOR: Atheros Communications Inc.
GENERAL.PRODUCT:AR9462 Wireless Network Adapter
GENERAL.DRIVER: ath9k
GENERAL.DRIVER-VERSION: 3.8.0-34-generic
GENERAL.FIRMWARE-VERSION: N/A
GENERAL.HWADDR: 50:B7:C3:D2:C1:E2
GENERAL.STATE: 100 (connected)
GENERAL.REASON: 0 (No reason given)
GENERAL.UDI:
/sys/devices/pci:00/:00:15.0/:03:00.0/net/wlan0
GENERAL.IP-IFACE: wlan0
GENERAL.NM-MANAGED: yes
GENERAL.AUTOCONNECT:yes
GENERAL.FIRMWARE-MISSING: no
GENERAL.CONNECTION:
/org/freedesktop/NetworkManager/ActiveConnection/2
CAPABILITIES.CARRIER-DETECT:no
CAPABILITIES.SPEED: 115 Mb/s
CONNECTIONS.AVAILABLE-CONNECTION-PATHS:
/org/freedesktop/NetworkManager/Settings/{5,13,12,2,6,1}
CONNECTIONS.AVAILABLE-CONNECTIONS[1]: 9f1935ee-5531-473b-bc0d-0b5b379f477b |
Pluto
CONNECTIONS.AVAILABLE-CONNECTIONS[2]: 379565ac-e20d-4abf-bc6b-b504d6f52623 |
Neptun
CONNECTIONS.AVAILABLE-CONNECTIONS[3]: 173ba863-ec2c-4caa-abbb-dc07ba8f1758 |
Neptun5
CONNECTIONS.AVAILABLE-CONNECTIONS[4]: 3e1009b7-dbb8-4291-b46d-424a382de539 |
Pluto5
CONNECTIONS.AVAILABLE-CONNECTIONS[5]: c6b058ff-c35c-497a-a72b-b874073081a0 |
Neptun5 1
CONNECTIONS.AVAILABLE-CONNECTIONS[6]: 6bb903c4-ddd7-4fe6-a6dc-ecd628bb859d |
Pluto_xt
WIFI-PROPERTIES.WEP:yes
WIFI-PROPERTIES.WPA:yes
WIFI-PROPERTIES.WPA2: yes
WIFI-PROPERTIES.TKIP: yes
WIFI-PROPERTIES.CCMP: yes
WIFI-PROPERTIES.AP: yes
WIFI-PROPERTIES.ADHOC: yes
AP[1].SSID: 'Keenetic'
AP[1].BSSID:FE:F5:28:49:0E:F0
AP[1].MODE: Infrastructure
AP[1].FREQ: 2417 MHz
AP[1].RATE: 54 MB/s
AP[1].SIGNAL: 75
AP[1].SECURITY: WPA2
AP[1].ACTIVE: no
AP[2].SSID: 'Neptun'
AP[2].BSSID:60:A4:4C:D2:3D:68
AP[2].MODE: Infrastructure
AP[2].FREQ: 2412 MHz
AP[2].RATE: 54 MB/s
AP[2].SIGNAL: 100
AP[2].SECURITY: WPA2
AP[2].ACTIVE: no
AP[3].SSID: 'Neptun'
AP[3].BSSID:50:46:5D:01:66:88
AP[3].MODE: Infrastructure
AP[3].FREQ: 2452 MHz
AP[3].RATE: 54 MB/s
AP[3].SIGNAL: 100
AP[3].SECURITY: WPA2
AP[3].ACTIVE: no
AP[4].SSID: 'Neptun5'
AP[4].BSSID:50:46:5D:01:66:8C
AP[4].MODE: Infrastructure
AP[4].FREQ: 5240 MHz
AP[4].RATE: 54 MB/s
AP[4].SIGNAL: 60
AP[4].SECURITY: WPA2
AP[4].ACTIVE: no
AP[5].SSID: 'Neptun'
AP[5].BSSID:74:D0:2B:5D:5A:20
AP[5].MODE: Infrastructure
AP[5].FREQ: 2472 MHz
AP[5].RATE: 54 MB/s
AP[5].SIGNAL: 70
AP[5].SECURITY: WPA2
AP[5].ACTIVE:
[Desktop-packages] [Bug 1259237] Re: Hybrid graphics enablement in 12.04.4
** Branch linked: lp:ubuntu/precise-proposed/screen-resolution-extra -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1259237 Title: Hybrid graphics enablement in 12.04.4 Status in “bbswitch” package in Ubuntu: Invalid Status in “lightdm” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-173” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-304” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-331” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: In Progress Status in “nvidia-prime” package in Ubuntu: Invalid Status in “nvidia-settings” package in Ubuntu: In Progress Status in “screen-resolution-extra” package in Ubuntu: Invalid Status in “bbswitch” source package in Precise: In Progress Status in “nvidia-prime” source package in Precise: In Progress Status in “screen-resolution-extra” source package in Precise: Fix Committed Bug description: SRU request: Please accept the following packages in precise-proposed. lightdm nvidia-prime nvidia-graphics-drivers-331 nvidia-graphics-drivers-331-updates nvidia-graphics-drivers-304 nvidia-graphics-drivers-304-updates nvidia-graphics-drivers-173 nvidia-settings screen-resolution-extra bbswitch [Rationale] This is the result of the HWE effort to bring power management to systems with NVIDIA Optimus. [Impact] Without this work, we keep both GPUs on all the time, thus heavily impacting on battery life. Thanks to this work, it is now possible to easily disable the discrete card when raw power is not needed. Furthermore nvidia-prime has better hardware detection now, and won't try to enable hybrid graphics on desktop systems any more. As for the technical details: * bbswitch is a backport of the package that now lives in main in 14.04. * The actual work happened in lightdm, nvidia-331, nvidia-331-updates, nvidia-prime, screen-resolution-extra, and nvidia-settings. * nvidia-settings now replaces all the different nvidia-settings flavours, so as to reduce the maintainance effort. I patched the app so that it checks the driver version (at runtime) and doesn't expose features that older driver releases do not support. * nvidia-331 and nvidia-331-updates replace 319 and 319-updates. These are the new LTS releases by NVIDIA. * nvidia-304 and nvidia-304-updates recommend the new nvidia-settings, include a security update, and build against the upcoming Linux 3.11 (lts-saucy). * nvidia-173, in addition to being compatible with Linux 3.11 (lts-saucy), also introduces transitional packages for 173-updates, as it doesn't make sense to maintain a separate -updates flavour any more. [Test Case] After installing the update, users should be able to boot the system as usual, with no regressions of any kind. * Systems with a single NVIDIA card: nvidia-prime will detect the hardware and do nothing at all on unsupported systems (such as the one card use case, or the desktop use case) * Systems with NVIDIA Optimus: nvidia-prime will preserve its previous behaviour by leaving both GPUs on. Users can launch nvidia-settings and switch to the power profile that they need. [Regression Potential] Low. The new features are enabled only if the user manually selects them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1259237/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1251369] Re: [Lenovo ThinkPad X220 Tablet] Disable while typing does not disable touchpad completely (only scrolling)
Christopher, it was just a quick shot, using the virtual image. This does not bug me enough to create a bootable stick, to test it on the host. Especially given, that I think that it is the expected behavior - given the link to the documentation in the report. You have added the regression-potential tag, but I would say that it never worked properly. Does it work on your system/touchpad? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1251369 Title: [Lenovo ThinkPad X220 Tablet] Disable while typing does not disable touchpad completely (only scrolling) Status in “xorg” package in Ubuntu: Incomplete Bug description: The Disable while typing option in the Mouse and Touchpad settings only work for scrolling, but not the regular movement of the pointer. To reproduce: 1. enable the option 2. Open a window where you can type (editor, terminal) 3. type with one hand constantly, and move the mouse pointer with the other one The mouse pointer should not move, but does for me. When two-finger scrolling instead, this gets blocked successfully while typing. This is with Ubuntu 13.10 on a Lenovo X220t. (The touchscreen appears to be completely unaffected by this setting (you can scroll while typing), but that is OK.) According to the documentation (https://help.ubuntu.com/community/SynapticsTouchpad#Disabling_Touchpad_while_Typing) I have now also disabled Tap to click, which works around the main annoyance of this: accidentally clicking with the palm/part of your hand while typing - the pointer can still be moved. --- .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,resize,compiztoolbox,put,vpswitch,snap,mousepoll,regex,place,session,move,grid,animation,imgpng,wall,expo,unitymtgrabhandles,workarounds,ezoom,staticswitcher,fade,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true DistUpgraded: 2013-10-08 21:37:21,390 DEBUG enabling apt cron job DistroCodename: saucy DistroRelease: Ubuntu 13.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21db] InstallationDate: Installed on 2012-05-28 (567 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MachineType: LENOVO 42992PG MarkForUpload: True Package: xorg 1:7.7+1ubuntu6 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-14-generic root=/dev/mapper/vg0-rootlv ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Tags: saucy ubuntu compiz-0.9 Uname: Linux 3.11.0-14-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-10-08 (70 days ago) UserGroups: adm cdrom davfs2 dip docker fuse lastfm libvirtd lpadmin plugdev sambashare sudo www-data dmi.bios.date: 04/11/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET68WW (1.38 ) dmi.board.asset.tag: Not Available dmi.board.name: 42992PG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET68WW(1.38):bd04/11/2013:svnLENOVO:pn42992PG:pvrThinkPadX220Tablet:rvnLENOVO:rn42992PG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 42992PG dmi.product.version: ThinkPad X220 Tablet dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs 1:0.5 version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Mon Dec 16 17:08:49 2013 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 728 vendor LGD xserver.version: 2:1.14.3-3ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1251369/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to :
[Desktop-packages] [Bug 919809] Re: [CMI8788] Xonar DG: no front panel or recording support
You would have to compile the kernel modules yourself using those
patches. They have not been accepted by ALSA yet, so it' probably best
to wait. Maybe they'll make into kernel 3.14.x
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/919809
Title:
[CMI8788] Xonar DG: no front panel or recording support
Status in ALSA driver:
New
Status in “alsa-driver” package in Ubuntu:
Triaged
Bug description:
Running precise, though I don't recall this working in oneiric either.
None of the front panel outputs/inputs on the Xonar DG are detected at
all. They are hooked up, as it works fine on Windows. Plugging in
headphones doesn't switch the output, and a microphone on the front is
not detected.
In sound preferences and pavucontrol, the card is listed as having
three connectors: Analog Output / Speaker (works), Analog Output /
Headphones 1, and Analog Output / Headphones 2. Changing the
selected connector has no effect, and reverts back to Speaker when the
settings view is reloaded. Additionally, setting via pacmd results in
failed to set sink port.[1]
Interestingly enough, alsamixer has an Analog Output selector with
different outputs than reported by PulseAudio. These are Speakers,
Headphones, and FP Headphones. Switching between these produces an
audible click from the sound card (normal, it's in the switching
circuit) so it's definitely communicating with the card. However, the
front panel audio still does not work. Both Speakers and FP Headphones
play out of the speakers, while Headphones outputs nothing at all.
Interestingly, alsamixer has no volume sliders for output, but that's
a separate issue. (The output sliders do work in PulseAudio, so that's
good enough for now.)
[1] http://askubuntu.com/questions/87581
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: alsa-base 1.0.24+dfsg-0ubuntu3
ProcVersionSignature: Ubuntu 3.2.0-10.17-generic 3.2.1
Uname: Linux 3.2.0-10-generic x86_64
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: DG [Xonar DG], device 0: Multichannel [Multichannel]
Subdevices: 0/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: jacob 1801 F pulseaudio
/dev/snd/pcmC0D0c: jacob 1801 F...m pulseaudio
Card0.Amixer.info:
Card hw:0 'DG'/'C-Media Oxygen HD Audio at 0xde00, irq 19'
Mixer name : 'CMI8786'
Components : 'CS4245 CMI8786'
Controls : 15
Simple ctrls : 10
Date: Sat Jan 21 15:17:04 2012
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:DG successful
Symptom_Card: CMI8788 [Oxygen HD Audio] - Xonar DG
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: Only some of outputs are working
Title: [CMI8786 - Xonar DG, playback] Playback problem
UpgradeStatus: Upgraded to precise on 2012-01-19 (1 days ago)
UserAsoundrc:
#pcm.!surround51 {
#type vdownmix
#slave.pcm hw:1
#}
modified.conffile..etc.modprobe.d.alsa.base.conf: [modified]
mtime.conffile..etc.modprobe.d.alsa.base.conf: 2012-01-17T23:40:21.034567
To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/919809/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1262199] Re: Disk Usage thinks screen is 3000 pixels or so wide
Please can you attach a screendump from this bug? ** Changed in: deja-dup (Ubuntu) Assignee: (unassigned) = Jörg Frings-Fürst (jff-de) ** Changed in: deja-dup (Ubuntu) Status: New = In Progress -- 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/1262199 Title: Disk Usage thinks screen is 3000 pixels or so wide Status in “deja-dup” package in Ubuntu: In Progress Bug description: See attached. I'm unable to horizontally resize the window. The grab bar is available, but dragging does nothing. Perhaps it would be a good idea to make sure the Disk Usage window is no wider than the actual screen. $ lsb_release -rd Description: Ubuntu 13.10 Release: 13.10 My apologies if this is is misfiled. I have two programs running related to disks, and neither are listed in the Choose Package search: $ ps -A | grep -i disk 2024 ?00:00:00 gvfs-udisks2-vo 2033 ?00:00:00 udisksd When I tried to file against, for example, udisks, I received There is 1 error. with no feedback on what the error is/was. I think this website is broken. Sigh... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1262199/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1259457] Re: Thunderbird Lightning no sound
SOLVED! Bug closed - stupid me... What happened was due to two things, I guess. (1) The unorthodox location of Tunderbird Profile. (2) *.wav file association was broken, probably because I removed distro based music player. Solution: (a) Right clicked on a wav file, Properties, and set Open with to VLC media player. (b) In Thunderbird and Lightnin Edit Preferences Browse and point back again to my chosen sound file. Tested and it works. Hope it'll help someone, jankom ** Changed in: thunderbird (Ubuntu) Status: New = Opinion -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1259457 Title: Thunderbird Lightning no sound Status in “thunderbird” package in Ubuntu: Opinion Bug description: Cannot activate sound alerts in Xubuntu 12.04 installation of Tunderbird 24.1.0. I googled and checked ubuntu forums. Lightning 2.6.2 is also installed, but calendar sound notification is silent. Same with 24.1.1 and 2.6.3. No answer in Ubuntu Launchpad questions forum (expired open after 15 days), and no answer in Mozilla Get Satisfaction forum. Sound works in VVindooz... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1259457/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1257668] Re: Snapping nautilus to the right and then to the top freezes the system
** Changed in: nautilus (Ubuntu) Status: Invalid = Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1257668 Title: Snapping nautilus to the right and then to the top freezes the system Status in “nautilus” package in Ubuntu: Incomplete Bug description: I experienced this bug since the update from 13.04 to 13.10 This is probably a unity bug, but it only occurs with nautilus file manager. Steps to reproduce: - Drag nautilus to the right or left edge to activate unity snapping feature - Then drag nautilus to the top edge to maximize the window Expected behaviour: - The nautilus window maximizes and fills the whole screen What happens instead: - The whole user interface freezes and does not react to any kind of input, making the system unusable. Mouse curser can be moved around but nothing is clickable. Snapping and maximizing all other applications using the edges of the screen works fine. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: nautilus 1:3.8.2-0ubuntu2.1 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Wed Dec 4 10:49:30 2013 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b'775x847+49+24' b'org.gnome.nautilus.window-state' b'sidebar-width' b'265' InstallationDate: Installed on 2012-05-22 (560 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: Upgraded to saucy on 2013-12-02 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1257668/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1251369] Re: [Lenovo ThinkPad X220 Tablet] Disable while typing does not disable touchpad completely (only scrolling)
Daniel Hahler, thank you for your comments. Regarding them: This does not bug me enough to create a bootable stick, to test it on the host. Ok. If you get bugged enough, this could always be resumed with your testing results. Especially given, that I think that it is the expected behavior - given the link to the documentation in the report. What one would expect is up to you, given you filed the report. You have added the regression-potential tag, but I would say that it never worked properly. What was the earliest release tested on your host? Does it work on your system/touchpad? Yes, but I don't have your hardware. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1251369 Title: [Lenovo ThinkPad X220 Tablet] Disable while typing does not disable touchpad completely (only scrolling) Status in “xorg” package in Ubuntu: Incomplete Bug description: The Disable while typing option in the Mouse and Touchpad settings only work for scrolling, but not the regular movement of the pointer. To reproduce: 1. enable the option 2. Open a window where you can type (editor, terminal) 3. type with one hand constantly, and move the mouse pointer with the other one The mouse pointer should not move, but does for me. When two-finger scrolling instead, this gets blocked successfully while typing. This is with Ubuntu 13.10 on a Lenovo X220t. (The touchscreen appears to be completely unaffected by this setting (you can scroll while typing), but that is OK.) According to the documentation (https://help.ubuntu.com/community/SynapticsTouchpad#Disabling_Touchpad_while_Typing) I have now also disabled Tap to click, which works around the main annoyance of this: accidentally clicking with the palm/part of your hand while typing - the pointer can still be moved. --- .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,resize,compiztoolbox,put,vpswitch,snap,mousepoll,regex,place,session,move,grid,animation,imgpng,wall,expo,unitymtgrabhandles,workarounds,ezoom,staticswitcher,fade,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true DistUpgraded: 2013-10-08 21:37:21,390 DEBUG enabling apt cron job DistroCodename: saucy DistroRelease: Ubuntu 13.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:21db] InstallationDate: Installed on 2012-05-28 (567 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MachineType: LENOVO 42992PG MarkForUpload: True Package: xorg 1:7.7+1ubuntu6 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-14-generic root=/dev/mapper/vg0-rootlv ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Tags: saucy ubuntu compiz-0.9 Uname: Linux 3.11.0-14-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-10-08 (70 days ago) UserGroups: adm cdrom davfs2 dip docker fuse lastfm libvirtd lpadmin plugdev sambashare sudo www-data dmi.bios.date: 04/11/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET68WW (1.38 ) dmi.board.asset.tag: Not Available dmi.board.name: 42992PG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET68WW(1.38):bd04/11/2013:svnLENOVO:pn42992PG:pvrThinkPadX220Tablet:rvnLENOVO:rn42992PG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 42992PG dmi.product.version: ThinkPad X220 Tablet dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs 1:0.5 version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Mon Dec 16 17:08:49 2013 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 728 vendor LGD
[Desktop-packages] [Bug 1257668] Re: Snapping nautilus to the right and then to the top freezes the system
** Attachment added: bugreport-Xorg.0.log https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1257668/+attachment/3931881/+files/bugreport-Xorg.0.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1257668 Title: Snapping nautilus to the right and then to the top freezes the system Status in “nautilus” package in Ubuntu: Incomplete Bug description: I experienced this bug since the update from 13.04 to 13.10 This is probably a unity bug, but it only occurs with nautilus file manager. Steps to reproduce: - Drag nautilus to the right or left edge to activate unity snapping feature - Then drag nautilus to the top edge to maximize the window Expected behaviour: - The nautilus window maximizes and fills the whole screen What happens instead: - The whole user interface freezes and does not react to any kind of input, making the system unusable. Mouse curser can be moved around but nothing is clickable. Snapping and maximizing all other applications using the edges of the screen works fine. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: nautilus 1:3.8.2-0ubuntu2.1 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Wed Dec 4 10:49:30 2013 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b'775x847+49+24' b'org.gnome.nautilus.window-state' b'sidebar-width' b'265' InstallationDate: Installed on 2012-05-22 (560 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: Upgraded to saucy on 2013-12-02 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1257668/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1257668] Re: Snapping nautilus to the right and then to the top freezes the system
** Attachment added: bugreport-syslog https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1257668/+attachment/3931880/+files/bugreport-syslog -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1257668 Title: Snapping nautilus to the right and then to the top freezes the system Status in “nautilus” package in Ubuntu: Incomplete Bug description: I experienced this bug since the update from 13.04 to 13.10 This is probably a unity bug, but it only occurs with nautilus file manager. Steps to reproduce: - Drag nautilus to the right or left edge to activate unity snapping feature - Then drag nautilus to the top edge to maximize the window Expected behaviour: - The nautilus window maximizes and fills the whole screen What happens instead: - The whole user interface freezes and does not react to any kind of input, making the system unusable. Mouse curser can be moved around but nothing is clickable. Snapping and maximizing all other applications using the edges of the screen works fine. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: nautilus 1:3.8.2-0ubuntu2.1 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Wed Dec 4 10:49:30 2013 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b'775x847+49+24' b'org.gnome.nautilus.window-state' b'sidebar-width' b'265' InstallationDate: Installed on 2012-05-22 (560 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: Upgraded to saucy on 2013-12-02 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1257668/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1257668] Re: Snapping nautilus to the right and then to the top freezes the system
** Attachment added: bugreport-Xorg.0.log.old https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1257668/+attachment/3931883/+files/bugreport-Xorg.0.log.old -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1257668 Title: Snapping nautilus to the right and then to the top freezes the system Status in “nautilus” package in Ubuntu: Incomplete Bug description: I experienced this bug since the update from 13.04 to 13.10 This is probably a unity bug, but it only occurs with nautilus file manager. Steps to reproduce: - Drag nautilus to the right or left edge to activate unity snapping feature - Then drag nautilus to the top edge to maximize the window Expected behaviour: - The nautilus window maximizes and fills the whole screen What happens instead: - The whole user interface freezes and does not react to any kind of input, making the system unusable. Mouse curser can be moved around but nothing is clickable. Snapping and maximizing all other applications using the edges of the screen works fine. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: nautilus 1:3.8.2-0ubuntu2.1 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Wed Dec 4 10:49:30 2013 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b'775x847+49+24' b'org.gnome.nautilus.window-state' b'sidebar-width' b'265' InstallationDate: Installed on 2012-05-22 (560 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: Upgraded to saucy on 2013-12-02 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1257668/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1257668] Re: Snapping nautilus to the right and then to the top freezes the system
The bug has reappeared. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1257668 Title: Snapping nautilus to the right and then to the top freezes the system Status in “nautilus” package in Ubuntu: Incomplete Bug description: I experienced this bug since the update from 13.04 to 13.10 This is probably a unity bug, but it only occurs with nautilus file manager. Steps to reproduce: - Drag nautilus to the right or left edge to activate unity snapping feature - Then drag nautilus to the top edge to maximize the window Expected behaviour: - The nautilus window maximizes and fills the whole screen What happens instead: - The whole user interface freezes and does not react to any kind of input, making the system unusable. Mouse curser can be moved around but nothing is clickable. Snapping and maximizing all other applications using the edges of the screen works fine. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: nautilus 1:3.8.2-0ubuntu2.1 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Wed Dec 4 10:49:30 2013 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b'775x847+49+24' b'org.gnome.nautilus.window-state' b'sidebar-width' b'265' InstallationDate: Installed on 2012-05-22 (560 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: Upgraded to saucy on 2013-12-02 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1257668/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1257668] Re: Snapping nautilus to the right and then to the top freezes the system
** Attachment added: bugreport-dmesg https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1257668/+attachment/3931879/+files/bugreport-dmesg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1257668 Title: Snapping nautilus to the right and then to the top freezes the system Status in “nautilus” package in Ubuntu: Incomplete Bug description: I experienced this bug since the update from 13.04 to 13.10 This is probably a unity bug, but it only occurs with nautilus file manager. Steps to reproduce: - Drag nautilus to the right or left edge to activate unity snapping feature - Then drag nautilus to the top edge to maximize the window Expected behaviour: - The nautilus window maximizes and fills the whole screen What happens instead: - The whole user interface freezes and does not react to any kind of input, making the system unusable. Mouse curser can be moved around but nothing is clickable. Snapping and maximizing all other applications using the edges of the screen works fine. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: nautilus 1:3.8.2-0ubuntu2.1 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Wed Dec 4 10:49:30 2013 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b'775x847+49+24' b'org.gnome.nautilus.window-state' b'sidebar-width' b'265' InstallationDate: Installed on 2012-05-22 (560 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: Upgraded to saucy on 2013-12-02 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1257668/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1257668] Re: Snapping nautilus to the right and then to the top freezes the system
Video card: NVIDIA Corporation GT218M [NVS 3100M] (rev a2) Graphics driver: proprietary nvidia driver v304 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1257668 Title: Snapping nautilus to the right and then to the top freezes the system Status in “nautilus” package in Ubuntu: Incomplete Bug description: I experienced this bug since the update from 13.04 to 13.10 This is probably a unity bug, but it only occurs with nautilus file manager. Steps to reproduce: - Drag nautilus to the right or left edge to activate unity snapping feature - Then drag nautilus to the top edge to maximize the window Expected behaviour: - The nautilus window maximizes and fills the whole screen What happens instead: - The whole user interface freezes and does not react to any kind of input, making the system unusable. Mouse curser can be moved around but nothing is clickable. Snapping and maximizing all other applications using the edges of the screen works fine. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: nautilus 1:3.8.2-0ubuntu2.1 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Wed Dec 4 10:49:30 2013 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b'775x847+49+24' b'org.gnome.nautilus.window-state' b'sidebar-width' b'265' InstallationDate: Installed on 2012-05-22 (560 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Release amd64 (20120425) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: Upgraded to saucy on 2013-12-02 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1257668/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1260068] Re: Unity continuous-integration fails in armhf due possibly to a libegl issue
To build Unity and run the tests in an up-to-date Trusty build environment you need to use the GTK fix branch (API changes in GTK prevent Unity from building using trunk). # apt-get build-dep unity # bzr branch lp:~townsend/unity/fix-gtk-build-error/ # cd fix-gtk-build-error # dpkg-buildpackage The unit tests are run as a part of the packaging build. The file tests/dummy-xorg-test-runner.sh is a shell script use to invoke a headless X.org server against which the tests get run. I believe this is where the problem lies. It looks like the headless X.org server does not start properly on armhf targets with the new Mesa. It may be possible to avoid building Unity to reproduce this problem if it occurs just running that script. -- 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/1260068 Title: Unity continuous-integration fails in armhf due possibly to a libegl issue Status in “mesa” package in Ubuntu: Confirmed Bug description: Since mesa 10.0 has been released, our Unity continuous-integration tests are failing on armhf builds. This is a snippet of the log: libEGL warning: DRI2: failed to authenticate Segmentation fault (core dumped) The log can be found here for reference: https://jenkins.qa.ubuntu.com/view/Trusty/view/All/job/unity-trusty- armhf-ci/56/console I don't have the core file or have access to an armhf machine to reproduce, so I'm only going on evidence based on the warning and the timing of the issue. *Note* This is blocking automerging of Unity code, so this issue is pretty critical. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1260068/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1244989] Re: LightDM won't load: Stopping startpar bridge for notification of upstart job start/stop
Same problem -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1244989 Title: LightDM won't load: Stopping startpar bridge for notification of upstart job start/stop Status in “lightdm” package in Ubuntu: Confirmed Bug description: Installed the Ubuntu 14.04 Trusty Tahr daily image (21-Oct-2013 13:57) into Virtualbox 4.2.18 r88780 and it won't load LightDM, I switched to tty1 and I see the following message: Stopping startpar bridge for notification of upstart job start/stop On several lines alternating between `[start]` and `[stop]` messages at the end. If I use `sudo lightdm restart` it just brings up a blank screen. I didn't have this specific problem when I was running the Saucy development branch. When I try to use `sudo lightdm restart` I get the error: Failed to use bus name org.freedesktop.DisplayManager, do you have appropriate permissions? and I get a blank screen again. Guest: lightdm 1.8.2 1851 MB of RAM Host: Pentium Dual-Core CPU E5200 @ 2.50GHz 4GB (3.7GiB) DDR2 RAM + 1.8GiB Swap nVidia GeForce 7100 (512MB GRAM) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1244989/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1253962] Re: hangs on startup
Same here, but it also happen on the play button in Rhythmbox itself. It is an almost-certainty after the first login or boot (for me this is virtually the same thing). Time counter and slider stay on 0:00, one core goes to 100%, UI freezes. Closing brings up the dialog if I want to kill it. Doing so and restarting Rhythmbox most of the times fixes the problem, but not always. Most definately started after moving from 13:04 to 13:10. Hope this helps. Jeroen -- 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/1253962 Title: hangs on startup Status in “rhythmbox” package in Ubuntu: Confirmed Bug description: Rhthmbox Hangs on every first time startup. Mostly happens when I clicks on Play button directly placed on dropdown on system indicator area on right top. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: rhythmbox 2.99.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Fri Nov 22 15:19:14 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2013-11-08 (13 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1253962/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1262202] [NEW] ubuntu-bug tomcat7 is crashing with permission denied
You have been subscribed to a public bug: On Ubuntu 12.04 i wanted to report a bug against tomcat7, so i used ubuntu-bug tomcat7 and i got this traceback: The first two german lines are just collecting information can be send to the developers to improve the application Die gesammelten Informationen können an die Entwickler gesendet werden um die Anwendung zu verbessern. Dies kann einige Minuten dauern. ..ERROR: hook /usr/share/apport/general-hooks/ubuntu.py crashed: Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/apport/report.py, line 719, in add_hooks_info symb['add_info'](self, ui) File /usr/share/apport/general-hooks/ubuntu.py, line 92, in add_info attach_conffiles(report, package, ui=ui) File /usr/lib/python2.7/dist-packages/apport/hookutils.py, line 107, in attach_conffiles modified = packaging.get_modified_conffiles(package) File /usr/lib/python2.7/dist-packages/apport/packaging_impl.py, line 263, in get_modified_conffiles with open(path, 'rb') as fd: IOError: [Errno 13] Permission denied: u'/etc/tomcat7/tomcat-users.xml' ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: tomcat7 7.0.26-1ubuntu1.2 ProcVersionSignature: Ubuntu 3.5.0-43.66~precise1-generic 3.5.7.23 Uname: Linux 3.5.0-43-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Wed Dec 18 14:04:59 2013 InstallationMedia: Ubuntu-Server 12.04.2 LTS Precise Pangolin - Release amd64 (20130214) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: tomcat7 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- ubuntu-bug tomcat7 is crashing with permission denied https://bugs.launchpad.net/bugs/1262202 You received this bug notification because you are a member of Desktop Packages, which is subscribed to apport in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1262238] [NEW] [SRU] Add support for Linux 3.11
Public bug reported: [SRU] Add support for Linux 3.11 in 12.04.4 ** Affects: fglrx-installer (Ubuntu) Importance: Undecided Status: Invalid ** Affects: fglrx-installer-updates (Ubuntu) Importance: Undecided Status: Invalid ** Affects: fglrx-installer (Ubuntu Precise) Importance: Medium Assignee: Alberto Milone (albertomilone) Status: In Progress ** Affects: fglrx-installer-updates (Ubuntu Precise) Importance: Medium Assignee: Alberto Milone (albertomilone) Status: In Progress ** Also affects: fglrx-installer-updates (Ubuntu) Importance: Undecided Status: New ** Also affects: fglrx-installer (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: fglrx-installer-updates (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: fglrx-installer (Ubuntu) Status: New = Invalid ** Changed in: fglrx-installer-updates (Ubuntu) Status: New = Invalid ** Changed in: fglrx-installer (Ubuntu Precise) Status: New = In Progress ** Changed in: fglrx-installer-updates (Ubuntu Precise) Status: New = In Progress ** Changed in: fglrx-installer-updates (Ubuntu Precise) Importance: Undecided = Medium ** Changed in: fglrx-installer (Ubuntu Precise) Importance: Undecided = Medium ** Changed in: fglrx-installer (Ubuntu Precise) Assignee: (unassigned) = Alberto Milone (albertomilone) ** Changed in: fglrx-installer-updates (Ubuntu Precise) Assignee: (unassigned) = Alberto Milone (albertomilone) ** Changed in: fglrx-installer (Ubuntu Precise) Milestone: None = ubuntu-12.04.4 ** Changed in: fglrx-installer-updates (Ubuntu Precise) Milestone: None = ubuntu-12.04.4 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1262238 Title: [SRU] Add support for Linux 3.11 Status in “fglrx-installer” package in Ubuntu: Invalid Status in “fglrx-installer-updates” package in Ubuntu: Invalid Status in “fglrx-installer” source package in Precise: In Progress Status in “fglrx-installer-updates” source package in Precise: In Progress Bug description: [SRU] Add support for Linux 3.11 in 12.04.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1262238/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1262202] Re: ubuntu-bug tomcat7 is crashing with permission denied
I think this is likely an issue in apport rather than in tomcat7. Changed package to reflect that. Will test later to determine the reproducibility of this issue. ** Package changed: tomcat7 (Ubuntu) = apport (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1262202 Title: ubuntu-bug tomcat7 is crashing with permission denied Status in “apport” package in Ubuntu: New Bug description: On Ubuntu 12.04 i wanted to report a bug against tomcat7, so i used ubuntu-bug tomcat7 and i got this traceback: The first two german lines are just collecting information can be send to the developers to improve the application Die gesammelten Informationen können an die Entwickler gesendet werden um die Anwendung zu verbessern. Dies kann einige Minuten dauern. ..ERROR: hook /usr/share/apport/general-hooks/ubuntu.py crashed: Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/apport/report.py, line 719, in add_hooks_info symb['add_info'](self, ui) File /usr/share/apport/general-hooks/ubuntu.py, line 92, in add_info attach_conffiles(report, package, ui=ui) File /usr/lib/python2.7/dist-packages/apport/hookutils.py, line 107, in attach_conffiles modified = packaging.get_modified_conffiles(package) File /usr/lib/python2.7/dist-packages/apport/packaging_impl.py, line 263, in get_modified_conffiles with open(path, 'rb') as fd: IOError: [Errno 13] Permission denied: u'/etc/tomcat7/tomcat-users.xml' ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: tomcat7 7.0.26-1ubuntu1.2 ProcVersionSignature: Ubuntu 3.5.0-43.66~precise1-generic 3.5.7.23 Uname: Linux 3.5.0-43-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Wed Dec 18 14:04:59 2013 InstallationMedia: Ubuntu-Server 12.04.2 LTS Precise Pangolin - Release amd64 (20130214) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: tomcat7 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1262202/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1246929] Re: no audio in KVM virtual machines : cannot select alsa or pa
To be clear, the qemu process is launched as my userid and /proc/$$/environ shows QEMU_AUDIO_DRV=pa. The 'outout' file in comment #41 shows the strace output which shows qemu opening some pulse cookies and doing some dbus transactions, presumably related to pulse. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1246929 Title: no audio in KVM virtual machines : cannot select alsa or pa Status in “libvirt” package in Ubuntu: Confirmed Status in “pulseaudio” package in Ubuntu: New Status in “virt-manager” package in Ubuntu: Confirmed Bug description: I am on Ubuntu 13.10 desktop 16GB ram asus sabertooth 990fx r2.0 motherboard amd 8346 cpu nvidia gtx650 video card Since upgrading to Ubuntu 13.10 audio no longer works in KVM. Checking SYSLOG I found this error being logged: Oct 31 15:32:31 bmullan-virtual-machine pulseaudio[1814]: [alsa-source-ID 21 Analog] alsa-source.c: ALSA woke us up to read new data from the device, but there was actually nothing to read! Oct 31 15:32:31 bmullan-virtual-machine pulseaudio[1814]: [alsa-source-ID 21 Analog] alsa-source.c: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers. Oct 31 15:32:31 bmullan-virtual-machine pulseaudio[1814]: [alsa-source-ID 21 Analog] alsa-source.c: We were woken up with POLLIN set -- however a subsequent snd_pcm_avail() returned 0 or another value min_avail. brian ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Thu Oct 31 19:45:53 2013 InstallationDate: Installed on 2013-10-31 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20131003) MarkForUpload: True PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1708 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH 990FX R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1708:bd04/09/2013:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FXR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1246929/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1246929] Re: no audio in KVM virtual machines : cannot select alsa or pa
Quoting Raymond (1246...@bugs.launchpad.net): http://libvirt.org/git/?p=libvirt.git;a=commit;h=a216e6487255d3b65d97c7ec1fa5da63dbced902 We're not running with -nographic though. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1246929 Title: no audio in KVM virtual machines : cannot select alsa or pa Status in “libvirt” package in Ubuntu: Confirmed Status in “pulseaudio” package in Ubuntu: New Status in “virt-manager” package in Ubuntu: Confirmed Bug description: I am on Ubuntu 13.10 desktop 16GB ram asus sabertooth 990fx r2.0 motherboard amd 8346 cpu nvidia gtx650 video card Since upgrading to Ubuntu 13.10 audio no longer works in KVM. Checking SYSLOG I found this error being logged: Oct 31 15:32:31 bmullan-virtual-machine pulseaudio[1814]: [alsa-source-ID 21 Analog] alsa-source.c: ALSA woke us up to read new data from the device, but there was actually nothing to read! Oct 31 15:32:31 bmullan-virtual-machine pulseaudio[1814]: [alsa-source-ID 21 Analog] alsa-source.c: Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA developers. Oct 31 15:32:31 bmullan-virtual-machine pulseaudio[1814]: [alsa-source-ID 21 Analog] alsa-source.c: We were woken up with POLLIN set -- however a subsequent snd_pcm_avail() returned 0 or another value min_avail. brian ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Thu Oct 31 19:45:53 2013 InstallationDate: Installed on 2013-10-31 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20131003) MarkForUpload: True PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1708 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH 990FX R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1708:bd04/09/2013:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FXR2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1246929/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1252776] Re: Can't change input language (layout) in screensaver unlock window.
*** This bug is a duplicate of bug 1225514 *** https://bugs.launchpad.net/bugs/1225514 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-screensaver (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1252776 Title: Can't change input language (layout) in screensaver unlock window. Status in “gnome-screensaver” package in Ubuntu: Confirmed Bug description: Can't change input language (layout) in screensaver unlock window. Hotkeys doesn't work totally. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-screensaver 3.6.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Tue Nov 19 16:51:54 2013 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session idle-delay uint32 300 org.gnome.desktop.session session-name 'ubuntu' InstallationDate: Installed on 2013-11-10 (8 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: gnome-screensaver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1252776/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1252776] Vacation reply
*** This bug is a duplicate of bug 1225514 *** https://bugs.launchpad.net/bugs/1225514 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1252776 Title: Can't change input language (layout) in screensaver unlock window. Status in “gnome-screensaver” package in Ubuntu: Confirmed Bug description: Can't change input language (layout) in screensaver unlock window. Hotkeys doesn't work totally. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-screensaver 3.6.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Tue Nov 19 16:51:54 2013 GnomeSessionIdleInhibited: No GnomeSessionInhibitors: None GsettingsGnomeSession: org.gnome.desktop.session idle-delay uint32 300 org.gnome.desktop.session session-name 'ubuntu' InstallationDate: Installed on 2013-11-10 (8 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: gnome-screensaver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1252776/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 631989] Re: keyboard layout indicator cannot be hidden
Fixed in Ubuntu 13.10. ** Changed in: ayatana-design Status: New = Fix Released ** Changed in: gnome-settings-daemon (Ubuntu) Status: Confirmed = Fix Released ** Changed in: ubuntu-indicator-mods Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/631989 Title: keyboard layout indicator cannot be hidden Status in Ayatana Design: Fix Released Status in Ubuntu network, Bluetooth, keyboard menus: Fix Released Status in “gnome-settings-daemon” package in Ubuntu: Fix Released Bug description: Binary package hint: indicator-application The indicator-applet in Maverick now shows the keyboard layout indicator. However, it ignores the setting allowing it to be hidden that was introduced by the fix to bug #519372 (/desktop/gnome/peripherals/keyboard/general/disable_indicator), and it appears that there is no other way to turn it off. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: indicator-application 0.2.6-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.35-19.28-generic 2.6.35.3 Uname: Linux 2.6.35-19-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 CheckboxSubmission: 1bd8e90541d49b96c13cbfcc9baf103b CheckboxSystem: d00f84de8a555815fa1c4660280da308 Date: Tue Sep 7 05:49:47 2010 InstallationMedia: Ubuntu 10.04 Lucid Lynx - Alpha amd64 (20100224.1) ProcEnviron: LANG=en_AU.utf8 SHELL=/bin/bash SourcePackage: indicator-application To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/631989/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1261936] Re: Nimbus Sans L font metrics messed up in LibreOffice
** Attachment added: 20131218_KDE-System-Settings-Font-Chooser-All-Packages-Installed.png https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1261936/+attachment/3931921/+files/20131218_KDE-System-Settings-Font-Chooser-All-Packages-Installed.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1261936 Title: Nimbus Sans L font metrics messed up in LibreOffice Status in “libreoffice” package in Ubuntu: Incomplete Bug description: Regression in Saucy Salamander 13.10, worked fine in 13.04 and previous releases. Affects LibreOffice Writer (Other Libre Office modules not tested so far.) (At least) Nimbus Sans L font rendering and cursor positioning in texts is messed up, the letters look slightly distorted, letter spacing is incorrect with even partially overlapping letters and the cursor positioning in a line of text does not always match the actual editing position. Wrong font rendering also effects PDF files generated with LibreOffice writer in Saucy. Nimbus Sans L font rendering looks fine in kCharSelect. PDFs generated before the update also are not affected and are rendered fine by Okular. --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 DistroRelease: Ubuntu 13.10 MarkForUpload: True Package: libreoffice 1:4.1.3-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Tags: saucy Uname: Linux 3.11.0-14-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-12-17 (0 days ago) UserGroups: adm admin cdrom davfs2 dialout disk lp lpadmin plugdev sambashare www-data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1261936/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1261936] Re: Nimbus Sans L font metrics messed up in LibreOffice
** Attachment added: 20131218_KDE-System-Settings-Font-Chooser-Only-Gsfonts-Installed.png https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1261936/+attachment/3931924/+files/20131218_KDE-System-Settings-Font-Chooser-Only-Gsfonts-Installed.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1261936 Title: Nimbus Sans L font metrics messed up in LibreOffice Status in “libreoffice” package in Ubuntu: Incomplete Bug description: Regression in Saucy Salamander 13.10, worked fine in 13.04 and previous releases. Affects LibreOffice Writer (Other Libre Office modules not tested so far.) (At least) Nimbus Sans L font rendering and cursor positioning in texts is messed up, the letters look slightly distorted, letter spacing is incorrect with even partially overlapping letters and the cursor positioning in a line of text does not always match the actual editing position. Wrong font rendering also effects PDF files generated with LibreOffice writer in Saucy. Nimbus Sans L font rendering looks fine in kCharSelect. PDFs generated before the update also are not affected and are rendered fine by Okular. --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 DistroRelease: Ubuntu 13.10 MarkForUpload: True Package: libreoffice 1:4.1.3-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Tags: saucy Uname: Linux 3.11.0-14-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-12-17 (0 days ago) UserGroups: adm admin cdrom davfs2 dialout disk lp lpadmin plugdev sambashare www-data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1261936/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1261936] Re: Nimbus Sans L font metrics messed up in LibreOffice
** Attachment added: 20131218_LibreOffice-Font-Chooser-New-Document-All-Packages-Installed.png https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1261936/+attachment/3931922/+files/20131218_LibreOffice-Font-Chooser-New-Document-All-Packages-Installed.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1261936 Title: Nimbus Sans L font metrics messed up in LibreOffice Status in “libreoffice” package in Ubuntu: Incomplete Bug description: Regression in Saucy Salamander 13.10, worked fine in 13.04 and previous releases. Affects LibreOffice Writer (Other Libre Office modules not tested so far.) (At least) Nimbus Sans L font rendering and cursor positioning in texts is messed up, the letters look slightly distorted, letter spacing is incorrect with even partially overlapping letters and the cursor positioning in a line of text does not always match the actual editing position. Wrong font rendering also effects PDF files generated with LibreOffice writer in Saucy. Nimbus Sans L font rendering looks fine in kCharSelect. PDFs generated before the update also are not affected and are rendered fine by Okular. --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 DistroRelease: Ubuntu 13.10 MarkForUpload: True Package: libreoffice 1:4.1.3-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Tags: saucy Uname: Linux 3.11.0-14-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-12-17 (0 days ago) UserGroups: adm admin cdrom davfs2 dialout disk lp lpadmin plugdev sambashare www-data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1261936/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1261936] Re: Nimbus Sans L font metrics messed up in LibreOffice
** Attachment added: 20131218_LibreOffice-Font-Chooser-Existing-Document-Only-Gsfonts-Installed.png https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1261936/+attachment/3931926/+files/20131218_LibreOffice-Font-Chooser-Existing-Document-Only-Gsfonts-Installed.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1261936 Title: Nimbus Sans L font metrics messed up in LibreOffice Status in “libreoffice” package in Ubuntu: Incomplete Bug description: Regression in Saucy Salamander 13.10, worked fine in 13.04 and previous releases. Affects LibreOffice Writer (Other Libre Office modules not tested so far.) (At least) Nimbus Sans L font rendering and cursor positioning in texts is messed up, the letters look slightly distorted, letter spacing is incorrect with even partially overlapping letters and the cursor positioning in a line of text does not always match the actual editing position. Wrong font rendering also effects PDF files generated with LibreOffice writer in Saucy. Nimbus Sans L font rendering looks fine in kCharSelect. PDFs generated before the update also are not affected and are rendered fine by Okular. --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 DistroRelease: Ubuntu 13.10 MarkForUpload: True Package: libreoffice 1:4.1.3-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Tags: saucy Uname: Linux 3.11.0-14-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-12-17 (0 days ago) UserGroups: adm admin cdrom davfs2 dialout disk lp lpadmin plugdev sambashare www-data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1261936/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1261936] Re: Nimbus Sans L font metrics messed up in LibreOffice
** Attachment added: 20131218_LibreOffice-Font-Chooser-Existing-Document-All-Packages-Installed.png https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1261936/+attachment/3931923/+files/20131218_LibreOffice-Font-Chooser-Existing-Document-All-Packages-Installed.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1261936 Title: Nimbus Sans L font metrics messed up in LibreOffice Status in “libreoffice” package in Ubuntu: Incomplete Bug description: Regression in Saucy Salamander 13.10, worked fine in 13.04 and previous releases. Affects LibreOffice Writer (Other Libre Office modules not tested so far.) (At least) Nimbus Sans L font rendering and cursor positioning in texts is messed up, the letters look slightly distorted, letter spacing is incorrect with even partially overlapping letters and the cursor positioning in a line of text does not always match the actual editing position. Wrong font rendering also effects PDF files generated with LibreOffice writer in Saucy. Nimbus Sans L font rendering looks fine in kCharSelect. PDFs generated before the update also are not affected and are rendered fine by Okular. --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 DistroRelease: Ubuntu 13.10 MarkForUpload: True Package: libreoffice 1:4.1.3-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Tags: saucy Uname: Linux 3.11.0-14-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-12-17 (0 days ago) UserGroups: adm admin cdrom davfs2 dialout disk lp lpadmin plugdev sambashare www-data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1261936/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1261936] Re: Nimbus Sans L font metrics messed up in LibreOffice
** Attachment added: 20131218_LibreOffice-Font-Chooser-New-Document-Only-Gsfonts-Installed.png https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1261936/+attachment/3931925/+files/20131218_LibreOffice-Font-Chooser-New-Document-Only-Gsfonts-Installed.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1261936 Title: Nimbus Sans L font metrics messed up in LibreOffice Status in “libreoffice” package in Ubuntu: Incomplete Bug description: Regression in Saucy Salamander 13.10, worked fine in 13.04 and previous releases. Affects LibreOffice Writer (Other Libre Office modules not tested so far.) (At least) Nimbus Sans L font rendering and cursor positioning in texts is messed up, the letters look slightly distorted, letter spacing is incorrect with even partially overlapping letters and the cursor positioning in a line of text does not always match the actual editing position. Wrong font rendering also effects PDF files generated with LibreOffice writer in Saucy. Nimbus Sans L font rendering looks fine in kCharSelect. PDFs generated before the update also are not affected and are rendered fine by Okular. --- ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 DistroRelease: Ubuntu 13.10 MarkForUpload: True Package: libreoffice 1:4.1.3-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7 Tags: saucy Uname: Linux 3.11.0-14-generic x86_64 UpgradeStatus: Upgraded to saucy on 2013-12-17 (0 days ago) UserGroups: adm admin cdrom davfs2 dialout disk lp lpadmin plugdev sambashare www-data To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1261936/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
